minecraft-world-generation
Create and debug Minecraft 26.x and legacy 1.21.x world generation for datapacks, NeoForge, or Fabric, including biomes, dimensions, features, structures, and biome modifiers. Use for worldgen data or registration, not general gameplay systems.
Jahrome907 · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Jahrome907/minecraft-agent-skills --skill minecraft-world-generationAbout this skill
name: minecraft-world-generation description: "Create and debug Minecraft 26.x and legacy 1.21.x world generation for datapacks, NeoForge, or Fabric, including biomes, dimensions, features, structures, and biome modifiers. Use for worldgen data or registration, not general gameplay systems."
Minecraft World Generation
Use this skill for biome, dimension, feature, or structure data and their
registration. Use minecraft-datapack for non-worldgen data and
minecraft-modding for non-worldgen gameplay code.
Routing Boundaries
Use when: the task changes worldgen data, registration, or injection.Do not use when: the task is non-worldgen datapack work (minecraft-datapack).Do not use when: the task is non-worldgen mod systems (minecraft-modding).
Choose the delivery path
| Approach | Best When | Platform |
|---|---|---|
| Datapack JSON | Change data supplied by a pack | Vanilla, any server |
| Mod + Datagen | Registering new biomes/dimensions, code-driven | NeoForge / Fabric |
| Biome Modifier (NeoForge) | Adding features/spawns to existing biomes | NeoForge |
| BiomeModification API (Fabric) | Adding features/spawns to existing biomes | Fabric |
Worldgen registries are datapack registries: their files load at world load and their registry path determines the data path. Read the NeoForge registry guide before choosing a mod-specific registry path.
Version boundary
Treat Minecraft 26.x as the current lane for new work. Use Java 25 and start each JSON schema from the exact target's vanilla data or generated output. Do not copy a 1.21 shape into a 26.x pack merely because it parses as JSON.
Preserve an established 1.21.x project on Java 21 and its matching schema unless the task explicitly includes an upgrade. Do not mix compatibility lanes.
The 26.1 migration primer
removes minecraft:random_patch and minecraft:no_bonemeal_flower. It replaces
the random-patch pattern with a separate minecraft:simple_block configured
feature and placements for count, random offset, and block-predicate filtering.
Inspect the relevant primer section before migrating code or data.
Read legacy 1.21 JSON patterns only when the project targets that compatibility lane. Those examples are not release artifacts for 26.x.
Data layout and reference graph
data/<namespace>/
├── worldgen/
│ ├── biome/
│ │ └── my_biome.json
│ ├── configured_feature/
│ │ └── my_ore.json
│ ├── placed_feature/
│ │ └── my_ore_placed.json
│ ├── noise_settings/
│ │ └── my_dimension_noise.json
│ ├── structure/
│ │ └── my_structure.json
│ ├── structure_set/
│ │ └── my_structures.json
│ ├── processor_list/
│ │ └── my_processors.json
│ ├── template_pool/
│ │ └── my_pool.json
│ └── carver/
│ └── my_carver.json
├── dimension/
│ └── my_dimension.json
├── dimension_type/
│ └── my_type.json
├── tags/
│ └── worldgen/
│ └── biome/
│ └── is_forest.json
└── neoforge/
└── biome_modifier/ (NeoForge mod only)
└── add_ores.json
Build and review the graph from its leaves upward:
- Define a configured feature, then its placed feature.
- Reference placed features from a biome or biome modifier at the intended decoration step.
- Define a structure, then its structure set; a jigsaw structure also needs a template pool, processor list, and structure template.
- Define a dimension type and noise settings before a dimension that references them.
Use fully qualified identifiers across namespaces. An external minecraft: or
dependency reference is valid when that dependency supplies the registry entry;
do not create a local copy merely to satisfy static checking. If the same pack
contains that external namespace and registry directory, treat it as local and
verify the target exists.
Biomes and dimensions
For 26.x biome and dimension data, use the exact target's vanilla data or
datagen output as the schema source. The older effects and dimension-type
fields do not model newer environment behavior. The 11 decoration steps still
organize placed features; choose the semantically appropriate step and keep ore
placement in underground_ores.
The version-labeled 1.21.5 biome and dimension examples are in legacy 1.21 JSON patterns.
26.x feature pattern
For the 26.1 replacement for a simple random patch, the migration primer shows
a simple_block configured feature and a placed feature with count, random
offset, and a block-predicate filter. Adapt the exact values and block state to
the target release's generated data.
At data/<namespace>/worldgen/configured_feature/my_plant.json:
{
"type": "minecraft:simple_block",
"config": {
"to_place": {
"type": "minecraft:simple_state_provider",
"state": { "Name": "minecraft:sweet_berry_bush", "Properties": { "age": "3" } }
}
}
}
At data/<namespace>/worldgen/placed_feature/my_plant.json:
{
"feature": "<namespace>:my_plant",
"placement": [
{ "type": "minecraft:count", "count": 96 },
{
"type": "minecraft:random_offset",
"xz_spread": { "type": "minecraft:trapezoid", "min": -7, "max": 7, "plateau": 0 },
"y_spread": { "type": "minecraft:trapezoid", "min": -3, "max": 3, "plateau": 0 }
},
{
"type": "minecraft:block_predicate_filter",
"predicate": {
"type": "minecraft:all_of",
"predicates": [
{ "type": "minecraft:matching_block_tag", "tag": "minecraft:air" },
{ "type": "minecraft:matching_blocks", "blocks": "minecraft:grass_block", "offset": [0, -1, 0] }
]
}
}
]
}
NeoForge biome modifiers
Biome modifiers load from
data/<modid>/neoforge/biome_modifier/<path>.json.