Vanilla data
Minecraft datapack formats used by NTM and loader-provided data.
ntm-next uses Minecraft 26.2's datapack formats. The Minecraft Wiki data pack reference explains the general file layout and vanilla schemas. Use the installed 26.2 jar for exact paths and values when an external reference covers an older version. This page records the loading boundaries and loader data relevant to NTM.
Minecraft data used by NTM
Recipes, advancements, loot tables, predicates, item modifiers, functions and tags use Minecraft's reloadable data paths. NTM adds recipe types, advancement triggers, a loot number provider and tag behavior within those formats. Some NTM consumers snapshot tag membership when a world opens.
World-loaded registries include NTM's configured and placed features, structures, processors, damage types and jukebox songs. See World Generation and Loot, Tags and Advancements for NTM's additions. Reopen the world or restart the server after editing them.
dimension/ definitions, dimension_type/ entries and NTM's per-dimension radiation settings have separate paths. structure/<path>.nbt holds a binary template; worldgen/structure/<path>.json defines generation. A resource-manager reload can refresh templates.
Loader-provided data
(Fabric)
The generated data includes data/fabric/tags/block/can_climb_trapdoor_above.json, listing NTM's five ladder blocks.
(NeoForge)
The generated data includes data/neoforge/data_maps/item/furnace_fuels.json. Its values object maps item IDs to burn times; the generated entry for hbm:biomass is {"burn_time":400}. See the NeoForge data-map reference (26.1) for the base format. The output also includes biome modifiers for NTM placed features.
© 2026 movblock. Original site text is licensed under CC BY-SA 4.0 unless otherwise noted.