Loot, tags and advancements

These use vanilla datapack formats with the NTM additions described below. The Minecraft Wiki data pack reference covers the base formats.

Loot tablesCopy Anchor Link

NTM supplies block, entity and structure loot tables. Use the Minecraft Wiki loot-table reference for the base JSON. A higher-priority file with the same resource ID replaces the complete lower-priority table.

NTM registers one additional number-provider type:

{"type": "hbm:config_scaled", "value": 2}

value is a required vanilla number provider, either a constant or a supported provider object. The result is max(1, floor(value * configured_loot_amount_factor)).

It may appear as a pool's rolls value. The rest of the pool uses vanilla formats and functions.

TagsCopy Anchor Link

Use the Minecraft Wiki tag reference for tag paths, values, and replace. An NTM recipe ingredient refers to an item tag as #example:ingredients; other NTM fields may expect a bare tag ID. Follow the shape documented for that field.

To remove entries contributed by another tag file, use the field for your loader. The generated minecraft:trimmable_armor tag removes NTM items this way:

NTM uses tags for recipe inputs, fluid equivalence, biome scopes, damage behavior and other membership policies. Some consumers snapshot tag membership at world load.

Advancements and NTM criteriaCopy Anchor Link

The enclosing advancement fields follow the Minecraft Wiki advancement reference. Every trigger accepts the optional vanilla player predicate. An item field below is a vanilla item predicate applied to the event stack; level is numeric bounds on the measured radiation or digamma level, and fatal selects a fatal exposure.

Detonation kinds are nuke, rbmk, zirnox, watz, refinery, fluid_tank, digamma_spear, nuclear_creeper, and soyuz_exhaust. Boss kinds are maskman, meltdown, worm, and ufo. Use those exact strings.

A minimal advancement for taking paper from a supported NTM result surface is:

{
  "criteria": {
    "make_paper": {
      "trigger": "hbm:item_crafted",
      "conditions": {"item": {"items": "minecraft:paper"}}
    }
  }
}

The event fires when a player takes the result from an NTM machine result slot. Furnace result surfaces retain vanilla-style recipe accounting.

Damage typesCopy Anchor Link

data/<namespace>/damage_type/<path>.json uses the vanilla damage-type schema described in the Minecraft Wiki data pack reference. For example, a shipped type contains:

{"exhaustion": 0.0, "message_id": "pc", "scaling": "never"}

The resource ID identifies the damage type. message_id selects its death-message family; translated strings are client language resources. Damage tags control properties such as bypass behavior.

Damage-type registry contents load with the world.

Jukebox songsCopy Anchor Link

data/<namespace>/jukebox_song/<path>.json uses the vanilla song schema described in the Minecraft Wiki data pack reference:

{
  "sound_event": "hbm:music.transmission",
  "description": {"translate": "jukebox_song.hbm.glass"},
  "length_in_seconds": 62.229,
  "comparator_output": 15
}

This is the shipped hbm:glass song record. The song registry loads with the world. The item refers to the song through its vanilla jukebox-playable component.