[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D2SMM6RAVGWQ5SXJ4DAS19":3,"skill-same:01M6D2SMM6RAVGWQ5SXJ4DAS19":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6D2SMM6RAVGWQ5SXJ4DAS19","minecraft-world-generation",null,"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\u002Fminecraft-agent-skills","Jahrome907","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222458345?v=4","01M6D2JFFY1EQCC572G6G3X1R2","Joe ","01M6D2JFS2EE87QN8QCFVFY6M8",201,"MIT","https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fminecraft-codex-skills\u002Fskills\u002Fminecraft-world-generation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"minecraft","world","generation","minecraft world generation","debug","create","fabric","data","use","neoforge","gameplay","Legacy","general","registration","dimensions","systems","2026-11-10 10:12:30",false,"---\nname: minecraft-world-generation\ndescription: \"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.\"\n---\n\n# Minecraft World Generation\n\nUse this skill for biome, dimension, feature, or structure data and their\nregistration. Use `minecraft-datapack` for non-worldgen data and\n`minecraft-modding` for non-worldgen gameplay code.\n\n## Routing Boundaries\n\n- `Use when`: the task changes worldgen data, registration, or injection.\n- `Do not use when`: the task is non-worldgen datapack work (`minecraft-datapack`).\n- `Do not use when`: the task is non-worldgen mod systems (`minecraft-modding`).\n\n## Choose the delivery path\n\n| Approach | Best When | Platform |\n|----------|-----------|----------|\n| Datapack JSON | Change data supplied by a pack | Vanilla, any server |\n| **Mod + Datagen** | Registering new biomes\u002Fdimensions, code-driven | NeoForge \u002F Fabric |\n| **Biome Modifier (NeoForge)** | Adding features\u002Fspawns to existing biomes | NeoForge |\n| **BiomeModification API (Fabric)** | Adding features\u002Fspawns to existing biomes | Fabric |\n\nWorldgen registries are datapack registries: their files load at world load and\ntheir registry path determines the data path. Read the [NeoForge registry\nguide](https:\u002F\u002Fdocs.neoforged.net\u002Fdocs\u002Fconcepts\u002Fregistries\u002F) before choosing a\nmod-specific registry path.\n\n## Version boundary\n\nUse Minecraft 26.x for new work. Use Java 25 and start\neach JSON schema from the exact target's vanilla data or generated output. Do\nnot copy a 1.21 shape into a 26.x pack merely because it parses as JSON.\n\nPreserve an established 1.21.x project on Java 21 and its matching schema unless\nthe task explicitly includes an upgrade. Keep examples matched to the project version.\n\nThe [26.1 migration primer](https:\u002F\u002Fdocs.neoforged.net\u002Fprimer\u002Fdocs\u002F26.1\u002F)\nremoves `minecraft:random_patch` and `minecraft:no_bonemeal_flower`. It replaces\nthe random-patch pattern with a separate `minecraft:simple_block` configured\nfeature and placements for count, random offset, and block-predicate filtering.\nInspect the relevant primer section before migrating code or data.\n\nRead [legacy 1.21 JSON patterns](references\u002Flegacy-1.21-worldgen-json.md) only\nwhen the project targets that version. Those examples are not\nrelease artifacts for 26.x.\n\n---\n\n## Data layout and reference graph\n\n26.3 uses `worldgen\u002Ffeature\u002F`; through 26.2 this was `worldgen\u002Fconfigured_feature\u002F`.\nIn 26.3, feature fields are at the root, block states use `id` \u002F `properties`,\nand biome spawn settings belong in environment attributes. See the\n[26.3 migration primer](https:\u002F\u002Fdocs.neoforged.net\u002Fprimer\u002Fdocs\u002F26.3\u002F).\n\n```\ndata\u002F\u003Cnamespace>\u002F\n├── worldgen\u002F\n│   ├── biome\u002F\n│   │   └── my_biome.json\n│   ├── feature\u002F\n│   │   └── my_ore.json\n│   ├── placed_feature\u002F\n│   │   └── my_ore_placed.json\n│   ├── noise_settings\u002F\n│   │   └── my_dimension_noise.json\n│   ├── structure\u002F\n│   │   └── my_structure.json\n│   ├── structure_set\u002F\n│   │   └── my_structures.json\n│   ├── processor_list\u002F\n│   │   └── my_processors.json\n│   ├── template_pool\u002F\n│   │   └── my_pool.json\n│   └── carver\u002F\n│       └── my_carver.json\n├── dimension\u002F\n│   └── my_dimension.json\n├── dimension_type\u002F\n│   └── my_type.json\n├── tags\u002F\n│   └── worldgen\u002F\n│       └── biome\u002F\n│           └── is_forest.json\n└── neoforge\u002F\n    └── biome_modifier\u002F      (NeoForge mod only)\n        └── add_ores.json\n```\n\nBuild and review the graph from its leaves upward:\n\n1. Define a feature, then its placed feature.\n2. Reference placed features from a biome or biome modifier at the intended\n   decoration step.\n3. Define a structure, then its structure set; a jigsaw structure also needs a\n   template pool, processor list, and structure template.\n4. Define a dimension type and noise settings before a dimension that references\n   them.\n\nUse fully qualified identifiers across namespaces. An external `minecraft:` or\ndependency reference is valid when that dependency supplies the registry entry;\ndo not create a local copy merely to satisfy static checking. If the same pack\ncontains that external namespace and registry directory, treat it as local and\nverify the target exists.\n\n---\n\n## Biomes and dimensions\n\nFor 26.x biome and dimension data, use the exact target's vanilla data or\ndatagen output as the schema source. The older `effects` and dimension-type\nfields do not model newer environment behavior. The 11 decoration steps still\norganize placed features; choose the semantically appropriate step and keep ore\nplacement in `underground_ores`.\n\nThe version-labeled 1.21.5 biome and dimension examples are in\n[legacy 1.21 JSON patterns](references\u002Flegacy-1.21-worldgen-json.md).\n\n## 26.3 feature pattern\n\nThis berry-bush example follows the 26.3 vanilla data. Keep older packs on\ntheir original schema; do not port them by changing metadata alone.\n\nAt `data\u002F\u003Cnamespace>\u002Fworldgen\u002Ffeature\u002Fmy_plant.json`:\n\n```json\n{\n  \"type\": \"minecraft:simple_block\",\n  \"to_place\": {\n    \"id\": \"minecraft:sweet_berry_bush\",\n    \"properties\": { \"age\": \"3\" }\n  }\n}\n```\n\nAt `data\u002F\u003Cnamespace>\u002Fworldgen\u002Fplaced_feature\u002Fmy_plant.json`:\n\n```json\n{\n  \"feature\": \"\u003Cnamespace>:my_plant\",\n  \"placement\": [\n    { \"type\": \"minecraft:count\", \"count\": 96 },\n    {\n      \"type\": \"minecraft:offset\",\n      \"x\": { \"type\": \"minecraft:trapezoid\", \"min\": -7, \"max\": 7, \"plateau\": 0 },\n      \"y\": { \"type\": \"minecraft:trapezoid\", \"min\": -3, \"max\": 3, \"plateau\": 0 },\n      \"z\": { \"type\": \"minecraft:trapezoid\", \"min\": -7, \"max\": 7, \"plateau\": 0 }\n    },\n    {\n      \"type\": \"minecraft:block_predicate_filter\",\n      \"predicate\": {\n        \"type\": \"minecraft:all_of\",\n        \"predicates\": [\n          { \"type\": \"minecraft:matching_block_tag\", \"tag\": \"minecraft:air\" },\n          { \"type\": \"minecraft:matching_blocks\", \"blocks\": \"minecraft:grass_block\", \"offset\": [0, -1, 0] }\n        ]\n      }\n    }\n  ]\n}\n```\n\n---\n\n## NeoForge biome modifiers\n\nBiome modifiers load from\n`data\u002F\u003Cmodid>\u002Fneoforge\u002Fbiome_modifier\u002F\u003Cpath>.json`. They can target a biome id\nor tag and add or remove placed features, among other changes. The current\n[Biome Modifiers guide](https:\u002F\u002Fdocs.neoforged.net\u002Fdocs\u002Fworldgen\u002Fbiomemodifier\u002F)\ndocuments their schemas, decoration steps, and datagen.\n\nFor `neoforge:add_features`, `features` accepts a placed-feature id, list, or\ntag. Vanilla placed features may be referenced in biome JSON or added with a\nmodifier, but NeoForge cautions against doing both because feature-order cycles\ncan crash world loading. Prefer a copy under the mod namespace when an injected\nvanilla feature would create that risk.\n\nWhen targeting a biome from an optional dependency, put the target in a biome\ntag entry with `required: false`, then use that tag in the modifier. This lets\nthe pack load when the dependency is absent.\n\n---\n\n## Structures and dimensions\n\nFor any current release, derive structure, template-pool, dimension, and\ndimension-type JSON from that release's vanilla data or datagen output. Confirm\nthe reference graph before launching a test world:\n\n- `structure_set` references `structure`.\n- Jigsaw `start_pool` references `template_pool`; each single-pool element\n  references its structure template and processor list.\n- `dimension.type` references `dimension_type`; a noise generator's string\n  `settings` references `worldgen\u002Fnoise_settings`.\n\nFor Fabric registration or mod datagen, use the exact loader and API version's\ndocumentation rather than copying 1.21 code into a 26.x project.\n\nThe detailed 1.21 structure and dimension examples are in\n[legacy 1.21 JSON patterns](references\u002Flegacy-1.21-worldgen-json.md).\n\n---\n\n## Development Workflow\n\n1. Create or edit worldgen JSON files in `data\u002F\u003Cnamespace>\u002Fworldgen\u002F` (or equivalent mod resources path).\n2. Run the bundled validator to catch JSON and cross-reference errors before loading:\n   ```bash\n   .\u002Fscripts\u002Fvalidate-worldgen-json.sh --root \u002Fpath\u002Fto\u002Fdatapack-or-mod-resources --feature-registry feature\n   # Strict mode treats warnings as failures:\n   .\u002Fscripts\u002Fvalidate-worldgen-json.sh --root \u002Fpath\u002Fto\u002Fdatapack-or-mod-resources --feature-registry feature --strict\n   ```\n   Omit `--feature-registry feature` for packs through 26.2.\n3. Fix any reported errors and re-validate until clean. The validator checks:\n   - JSON validity for `worldgen\u002F**` and `neoforge\u002Fbiome_modifier\u002F**`\n   - Cross-reference integrity for `placed_feature -> feature` (or legacy `configured_feature`)\n   - Cross-reference integrity for `structure_set -> structure` and biome\u002Fbiome_modifier feature targets\n   - Cross-reference integrity for `jigsaw structure -> start_pool` and `template_pool -> structure template \u002F processor_list`\n4. Compare biome and dimension-type JSON against the exact target's vanilla\n   registry shape before in-game testing. The helper does not run Mojang codecs:\n   valid JSON and local references do not prove that fields such as `carvers`,\n   `effects`, or dimension settings match that release's schema.\n5. In-game biome and structure testing:\n   ```mcfunction\n   \u002Flocate structure \u003Cnamespace>:my_structure\n   \u002Flocate biome \u003Cnamespace>:my_biome\n   \u002Fplace feature \u003Cnamespace>:my_ore\n   ```\n   `place feature` takes a feature ID (`configured_feature` through 26.2),\n   not its placed-feature wrapper.\n6. For dimension testing, use `\u002Fexecute in` (dimension must exist at world load, not added via `\u002Freload`):\n   ```mcfunction\n   execute in \u003Cnamespace>:my_dimension run tp @s 0 100 0\n   ```\n7. Check `latest.log` for worldgen errors (missing biome references, malformed noise settings).\n8. Note: `\u002Freload` refreshes datapack JSON but does **not** re-generate already-generated chunks. Test new worldgen in a fresh world or newly generated chunks. For existing test worlds, use a disposable copy and a purpose-built chunk reset\u002Fregeneration workflow; `\u002Ffill` only replaces blocks and is not a substitute for world generation.\n\n---\n\n## References\n\n- Minecraft Wiki — World generation: https:\u002F\u002Fminecraft.wiki\u002Fw\u002FCustom_world_generation\n- Minecraft Wiki — Biome: https:\u002F\u002Fminecraft.wiki\u002Fw\u002FBiome\u002FJSON_format\n- Minecraft Wiki — Features: https:\u002F\u002Fminecraft.wiki\u002Fw\u002FWorld_generation\u002FConfigured_feature\n- NeoForge Biome Modifiers: https:\u002F\u002Fdocs.neoforged.net\u002Fdocs\u002Fworldgen\u002Fbiomemodifier\u002F\n- Fabric BiomeModifications: https:\u002F\u002Fwiki.fabricmc.net\u002Ftutorial:biomemodification\n- misode's data pack generator (worldgen UI): https:\u002F\u002Fmisode.github.io\u002Fworldgen\u002F\n","# Minecraft World Generation\n\nUse this skill for biome, dimension, feature, or structure data and their\nregistration. Use `minecraft-datapack` for non-worldgen data and\n`minecraft-modding` for non-worldgen gameplay code.\n\n## Routing Boundaries\n\n- `Use when`: the task changes worldgen data, registration, or injection.\n- `Do not use when`: the task is non-worldgen datapack work (`minecraft-datapack`).\n- `Do not use when`: the task is non-worldgen mod systems (`minecraft-modding`).\n\n## Choose the delivery path\n\n| Approach | Best When | Platform |\n|----------|-----------|----------|\n| Datapack JSON | Change data supplied by a pack | Vanilla, any server |\n| **Mod + Datagen** | Registering new biomes\u002Fdimensions, code-driven | NeoForge \u002F Fabric |\n| **Biome Modifier (NeoForge)** | Adding features\u002Fspawns to existing biomes | NeoForge |\n| **BiomeModification API (Fabric)** | Adding features\u002Fspawns to existing biomes | Fabric |\n\nWorldgen registries are datapack registries: their files load at world load and\ntheir registry path determines the data path. Read the [NeoForge registry\nguide](https:\u002F\u002Fdocs.neoforged.net\u002Fdocs\u002Fconcepts\u002Fregistries\u002F) before choosing a\nmod-specific registry path.\n\n## Version boundary\n\nUse Minecraft 26.x for new work. Use Java 25 and start\neach JSON schema from the exact target's vanilla data or generated output. Do\nnot copy a 1.21 shape into a 26.x pack merely because it parses as JSON.\n\nPreserve an established 1.21.x project on Java 21 and its matching schema unless\nthe task explicitly includes an upgrade. Keep examples matched to the project version.\n\nThe [26.1 migration primer](https:\u002F\u002Fdocs.neoforged.net\u002Fprimer\u002Fdocs\u002F26.1\u002F)\nremoves `minecraft:random_patch` and `minecraft:no_bonemeal_flower`. It replaces\nthe random-patch pattern with a separate `minecraft:simple_block` configured\nfeature and placements for count, random offset, and block-predicate filtering.\nInspect the relevant primer section before migrating code or data.\n\nRead [legacy 1.21 JSON patterns](references\u002Flegacy-1.21-worldgen-json.md) only\nwhen the project targets that version. Those examples are not\nrelease artifacts for 26.x.\n\n---\n\n## Data layout and reference graph\n\n26.3 uses `worldgen\u002Ffeature\u002F`; through 26.2 this was `worldgen\u002Fconfigured_feature\u002F`.\nIn 26.3, feature fields are at the root, block states use `id` \u002F `properties`,\nand biome spawn settings belong in environment attributes. See the\n[26.3 migration primer](https:\u002F\u002Fdocs.neoforged.net\u002Fprimer\u002Fdocs\u002F26.3\u002F).\n\n```\ndata\u002F\u003Cnamespace>\u002F\n├── worldgen\u002F\n│   ├── biome\u002F\n│   │   └── my_biome.json\n│   ├── feature\u002F\n│   │   └── my_ore.json\n│   ├── placed_feature\u002F\n│   │   └── my_ore_placed.json\n│   ├── noise_settings\u002F\n│   │   └── my_dimension_noise.json\n│   ├── structure\u002F\n│   │   └── my_structure.json\n│   ├── structure_set\u002F\n│   │   └── my_structures.json\n│   ├── processor_list\u002F\n│   │   └── my_processors.json\n│   ├── template_pool\u002F\n│   │   └── my_pool.json\n│   └── carver\u002F\n│       └── my_carver.json\n├── dimension\u002F\n│   └── my_dimension.json\n├── dimension_type\u002F\n│   └── my_type.json\n├── tags\u002F\n│   └── worldgen\u002F\n│       └── biome\u002F\n│           └── is_forest.json\n└── neoforge\u002F\n    └── biome_modifier\u002F      (NeoForge mod only)\n        └── add_ores.json\n```\n\nBuild and review the graph from its leaves upward:\n\n1. Define a feature, then its placed feature.\n2. Reference placed features from a biome or biome modifier at the intended\n   decoration step.\n3. Define a structure, then its structure set; a jigsaw structure also needs a\n   template pool, processor list, and structure template.\n4. Define a dimension type and noise settings before a dimension that references\n   them.\n\nUse fully qualified identifiers across namespaces. An external `minecraft:` or\ndependency reference is valid when that dependency supplies the registry entry;\ndo not create a local copy merely to satisfy static checking. If the same pack\ncontains that external namespace and registry directory, treat it as local and\nverify the target exists.\n\n---\n\n## Biomes and dimensions\n\nFor 26.x biome and dimension data, use the exact target's vanilla data or\ndatagen output as the schema source. The older `effects` and dimension-type\nfields do not model newer environment behavior. The 11 decoration steps still\norganize placed features; choose the semantically appropriate step and keep ore\nplacement in `underground_ores`.\n\nThe version-labeled 1.21.5 biome and dimension examples are in\n[legacy 1.21 JSON patterns](references\u002Flegacy-1.21-worldgen-json.md).\n\n## 26.3 feature pattern\n\nThis berry-bush example follows the 26.3 vanilla data. Keep older packs on\ntheir original schema; do not port them by changing metadata alone.\n\nAt `data\u002F\u003Cnamespace>\u002Fworldgen\u002Ffeature\u002Fmy_plant.json`:\n\n```json\n{\n  \"type\": \"minecraft:simple_block\",\n  \"to_place\": {\n    \"id\": \"minecraft:sweet_berry_bush\",\n    \"properties\": { \"age\": \"3\" }\n  }\n}\n```\n\nAt `data\u002F\u003Cnamespace>\u002Fworldgen\u002Fplaced_feature\u002Fmy_plant.json`:\n\n```json\n{\n  \"feature\": \"\u003Cnamespace>:my_plant\",\n  \"placement\": [\n    { \"type\": \"minecraft:count\", \"count\": 96 },\n    {\n      \"type\": \"minecraft:offset\",\n      \"x\": { \"type\": \"minecraft:trapezoid\", \"min\": -7, \"max\": 7, \"plateau\": 0 },\n      \"y\": { \"type\": \"minecraft:trapezoid\", \"min\": -3, \"max\": 3, \"plateau\": 0 },\n      \"z\": { \"type\": \"minecraft:trapezoid\", \"min\": -7, \"max\": 7, \"plateau\": 0 }\n    },\n    {\n      \"type\": \"minecraft:block_predicate_filter\",\n      \"predicate\": {\n        \"type\": \"minecraft:all_of\",\n        \"predicates\": [\n          { \"type\": \"minecraft:matching_block_tag\", \"tag\": \"minecraft:air\" },\n          { \"type\": \"minecraft:matching_blocks\", \"blocks\": \"minecraft:grass_block\", \"offset\": [0, -1, 0] }\n        ]\n      }\n    }\n  ]\n}\n```\n\n---\n\n## NeoForge biome modifiers\n\nBiome modifiers load from\n`data\u002F\u003Cmodid>\u002Fneoforge\u002Fbiome_modifier\u002F\u003Cpath>.json`. They can target a biome id\nor tag and add or remove placed features, among other changes. The current\n[Biome Modifiers guide](https:\u002F\u002Fdocs.neoforged.net\u002Fdocs\u002Fworldgen\u002Fbiomemodifier\u002F)\ndocuments their schemas, decoration steps, and datagen.\n\nFor `neoforge:add_features`, `features` accepts a placed-feature id, list, or\ntag. Vanilla placed features may be referenced in biome JSON or added with a\nmodifier, but NeoForge cautions against doing both because feature-order cycles\ncan crash world loading. Prefer a copy under the mod namespace when an injected\nvanilla feature would create that risk.\n\nWhen targeting a biome from an optional dependency, put the target in a biome\ntag entry with `required: false`, then use that tag in the modifier. This lets\nthe pack load when the dependency is absent.\n\n---\n\n## Structures and dimensions\n\nFor any current release, derive structure, template-pool, dimension, and\ndimension-type JSON from that release's vanilla data or datagen output. Confirm\nthe reference graph before launching a test world:\n\n- `structure_set` references `structure`.\n- Jigsaw `start_pool` references `template_pool`; each single-pool element\n  references its structure template and processor list.\n- `dimension.type` references `dimension_type`; a noise generator's string\n  `settings` references `worldgen\u002Fnoise_settings`.\n\nFor Fabric registration or mod datagen, use the exact loader and API version's\ndocumentation rather than copying 1.21 code into a 26.x project.\n\nThe detailed 1.21 structure and dimension examples are in\n[legacy 1.21 JSON patterns](references\u002Flegacy-1.21-worldgen-json.md).\n\n---\n\n## Development Workflow\n\n1. Create or edit worldgen JSON files in `data\u002F\u003Cnamespace>\u002Fworldgen\u002F` (or equivalent mod resources path).\n2. Run the bundled validator to catch JSON and cross-reference errors before loading:\n   ```bash\n   .\u002Fscripts\u002Fvalidate-worldgen-json.sh --root \u002Fpath\u002Fto\u002Fdatapack-or-mod-resources --feature-registry feature\n   # Strict mode treats warnings as failures:\n   .\u002Fscripts\u002Fvalidate-worldgen-json.sh --root \u002Fpath\u002Fto\u002Fdatapack-or-mod-resources --feature-registry feature --strict\n   ```\n   Omit `--feature-registry feature` for packs through 26.2.\n3. Fix any reported errors and re-validate until clean. The validator checks:\n   - JSON validity for `worldgen\u002F**` and `neoforge\u002Fbiome_modifier\u002F**`\n   - Cross-reference integrity for `placed_feature -> feature` (or legacy `configured_feature`)\n   - Cross-reference integrity for `structure_set -> structure` and biome\u002Fbiome_modifier feature targets\n   - Cross-reference integrity for `jigsaw structure -> start_pool` and `template_pool -> structure template \u002F processor_list`\n4. Compare biome and dimension-type JSON against the exact target's vanilla\n   registry shape before in-game testing. The helper does not run Mojang codecs:\n   valid JSON and local references do not prove that fields such as `carvers`,\n   `effects`, or dimension settings match that release's schema.\n5. In-game biome and structure testing:\n   ```mcfunction\n   \u002Flocate structure \u003Cnamespace>:my_structure\n   \u002Flocate biome \u003Cnamespace>:my_biome\n   \u002Fplace feature \u003Cnamespace>:my_ore\n   ```\n   `place feature` takes a feature ID (`configured_feature` through 26.2),\n   not its placed-feature wrapper.\n6. For dimension testing, use `\u002Fexecute in` (dimension must exist at world load, not added via `\u002Freload`):\n   ```mcfunction\n   execute in \u003Cnamespace>:my_dimension run tp @s 0 100 0\n   ```\n7. Check `latest.log` for worldgen errors (missing biome references, malformed noise settings).\n8. Note: `\u002Freload` refreshes datapack JSON but does **not** re-generate already-generated chunks. Test new worldgen in a fresh world or newly generated chunks. For existing test worlds, use a disposable copy and a purpose-built chunk reset\u002Fregeneration workflow; `\u002Ffill` only replaces blocks and is not a substitute for world generation.\n\n---\n\n## References\n\n- Minecraft Wiki — World generation: https:\u002F\u002Fminecraft.wiki\u002Fw\u002FCustom_world_generation\n- Minecraft Wiki — Biome: https:\u002F\u002Fminecraft.wiki\u002Fw\u002FBiome\u002FJSON_format\n- Minecraft Wiki — Features: https:\u002F\u002Fminecraft.wiki\u002Fw\u002FWorld_generation\u002FConfigured_feature\n- NeoForge Biome Modifiers: https:\u002F\u002Fdocs.neoforged.net\u002Fdocs\u002Fworldgen\u002Fbiomemodifier\u002F\n- Fabric BiomeModifications: https:\u002F\u002Fwiki.fabricmc.net\u002Ftutorial:biomemodification\n- misode's data pack generator (worldgen UI): https:\u002F\u002Fmisode.github.io\u002Fworldgen\u002F\n",{"name":5,"description":7},"main","22d61ce6b7a0c5f215008824aa6b94ecc73f2a43","plugins\u002Fminecraft-codex-skills\u002Fskills\u002Fminecraft-world-generation",11,"https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills","https:\u002F\u002Fgithub.com\u002FJahrome907","joe-o.com","Product engineer building field tools, workflow automation, and polished web applications.","2026-10-30 08:19:45",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Jahrome907\u002Fminecraft-agent-skills --skill minecraft-world-generation",{"tool":55,"command":56},"bunx","bunx skills add Jahrome907\u002Fminecraft-agent-skills --skill minecraft-world-generation",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Jahrome907\u002Fminecraft-agent-skills --skill minecraft-world-generation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fminecraft-codex-skills\u002Fskills\u002Fminecraft-world-generation\u002FSKILL.md",true,[63,69,75],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Flegacy-1.21-worldgen-json.md","REFERENCE","参考文档",4669,"https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fminecraft-codex-skills\u002Fskills\u002Fminecraft-world-generation\u002Freferences\u002Flegacy-1.21-worldgen-json.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fjq-shim.mjs","SCRIPT","脚本",7435,"https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fminecraft-codex-skills\u002Fskills\u002Fminecraft-world-generation\u002Fscripts\u002Fjq-shim.mjs",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fvalidate-worldgen-json.sh",18873,"https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fminecraft-codex-skills\u002Fskills\u002Fminecraft-world-generation\u002Fscripts\u002Fvalidate-worldgen-json.sh",[80,96,101,113,121,128],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":35},"01M6D2TV8CBAMB70CEC19VMVX5","minecraft-ci-release","Fixture with valid workflow YAML and a warning-only glob pattern.","https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalidators\u002Fci-release\u002Fwarn-only\u002FSKILL.md",[],[87,19,88,89,90,91,92,93,94,95],"minecraft ci release","ci","release","fixture","pattern","only","yaml","workflow","valid",{"skillNo":97,"name":95,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":35},"01M6D2TR1N9TNJPTRB66WDCY8X","https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalidators\u002Fci-release\u002Fvalid\u002FSKILL.md",[],[95],{"skillNo":102,"name":82,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":111,"publishedAt":35},"01M6D2TNBM97CCTYFCDKCFQ4AR","Fixture for a secretless workflow that passes strict validation.","https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalidators\u002Fci-release\u002Fsecretless-strict\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[87,19,88,89,90,112,94],"validation",{"skillNo":114,"name":115,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":35},"01M6D2TJ9FX4FH1TMGKQPYNZQX","non-workflow-yaml","https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalidators\u002Fci-release\u002Fnon-workflow-yaml\u002FSKILL.md",[118],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},[120,93,94],"non workflow yaml",{"skillNo":122,"name":82,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":35},"01M6D2TFE807BSXTEREYPWFY3G","Fixture with a mutable remote action reference.","https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalidators\u002Fci-release\u002Fmutable-action\u002FSKILL.md",[],[87,19,88,89,127,90],"reference",{"skillNo":129,"name":82,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":35},"01M6D2TBYJ0SM3B79908DH9ECE","Fixture with valid multiline flow collections in workflow YAML.","https:\u002F\u002Fgithub.com\u002FJahrome907\u002Fminecraft-agent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalidators\u002Fci-release\u002Fmultiline-flow\u002FSKILL.md",[],[87,89,19,88,94,93,134,90,135,95],"flow","collections"]