minecraft-worldgenlisted

# Minecraft World Generation ## Purpose Worldgen is data, not code. Since the 1.18 line, biomes, features, placements, structures and dimensions live in **datapack registries** — JSON loaded per world, not Java registered at mod load. Java's role is to register the *types* (feature types, structure types, placement modifier types) and to bootstrap the JSON through data generation. Getting this backwards, or getting the configured/placed feature split wrong, produces the platform's most frustrating failure: everything loads, nothing generates, nothing is logged. This skill covers the model, the per-loader biome modification hook, and how to actually see what is happening. ## When to use - Adding ore generation, plants, boulders, geodes or any other feature. - Adding a custom biome, or changing what generates in vanilla biomes. - Adding a structure, structure set or jigsaw structure. - Adding a dimension. - Content generates in some worlds but not others, or only in newly generated chunks, or not at all. - Deciding whether new content belongs in Java or in JSON. ## When NOT to use - The loader, version and mappings are unresolved. Run `minecraft-project-conventions` first. - The block being placed does not exist yet. Register it first (`minecraft-blocks-items`). - Mob spawn *rules* attached to the entity type. That is `minecraft-entities-mobs`; this skill covers the biome-side spawner list. - Chunk generation cost and server tick impact. Worldgen is the single mos