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.

Scaled rollsCopy Anchor Link

The hbm:config_scaled number provider scales its input by the world's loot amount factor:

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

The result is:

amount_factor is a field of the loot world settings, read each time the provider rolls. value is sampled as an integer, so a uniform integer provider lies in [\mathrm{min}, \mathrm{max}] before scaling. The provider may appear as a pool's rolls value. The rest of the pool uses vanilla formats and functions.

Entity enchantment levelsCopy Anchor Link

hbm:entity_enchantment_level reads an enchantment level from an entity selected from the loot context, such as the attacker's Looting level.

Container fill policyCopy Anchor Link

When a container unpacks a table with hbm:random_slots: true:

• Each rolled stack keeps its rolled count and goes to a uniformly random slot, replacing that slot's contents, including earlier rolls.
• A stack larger than its maximum stack size is split into single items, each placed in a random slot.

Zero-count stacks also write to a random slot, clearing its contents. A minecraft:empty entry emits no stack and makes no slot write.

Only the table named by the container is checked; nested minecraft:loot_table entries ignore their own flag. Drops and /loot draw the table normally.

Example: data/example/loot_table/chest.json.

{
  "type": "minecraft:chest",
  "hbm:random_slots": true,
  "pools": [
    {
      "rolls": 1,
      "entries": [
        {
          "type": "minecraft:item",
          "name": "minecraft:iron_ingot"
        }
      ],
      "modifier": [
        {
          "type": "minecraft:set_count",
          "count": 16
        }
      ]
    }
  ]
}

NTM chest tablesCopy Anchor Link

NTM structures and features store a roll-table ID in each container. A roll table draws one content table. Every shipped chest table sets hbm:random_slots to true.

Generated chest selectionCopy Anchor Link

The 44 built-in content tables encode their weighted selection as nested minecraft:alternatives entries with minecraft:value_check conditions. To change odds in a copied table, update those selection conditions or replace the pool with a vanilla weighted entry list. Changing leaf weight fields alone leaves the generated branch selection unchanged.

hbm:chests/nuke_fuel now yields hbm:pile_rod_mk2_nu in place of hbm:pile_rod_uranium, and hbm:pile_rod_mk2_ra226be in place of hbm:pile_rod_source. Their count ranges remain 2–5 and 1–2, with weights 3 and 2 respectively.

hbm:chests/vanilla/simple_dungeon fills the library dungeon's chests with one draw of minecraft:chests/simple_dungeon.

Vanilla chest additionsCopy Anchor Link

When loot tables load, NTM appends single-item entries to the first pool of five vanilla chest tables. A replacement table receives them only when it has at least the listed number of pools and first-pool entries; otherwise it is left unchanged.

minecraft:chests/spawn_bonus_chest always receives one extra pool: 10 rolls of hbm:no9 (weight 7) against an empty entry (weight 64).

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.

Membership tagsCopy Anchor Link

NTM code reads these tags. Paths are under data/<namespace>/tags/<directory>/.

Item-hazard bindings target item tags such as hbm:hazard/<name>; see Item hazards. Fluid shares name fluid tags; see the Fluid Trait Reference.

NTM's c:<family>/<name> item tags join their parent c:<family> tag for the families dusts, dyed, dyes, gems, ingots, nuggets, ores, raw_materials and storage_blocks. NTM ore and storage blocks are also listed in c:ores/<name> and c:storage_blocks/<name> block tags, which join the c:ores and c:storage_blocks block tags.

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 is an optional vanilla item predicate applied to the event stack.

A minimal advancement for taking paper from an NTM output slot is:

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

NTM furnace output slots also fire minecraft:recipe_crafted for the smelting recipes used.

Bobmazon offers are gated by hbm:blastfurnace, hbm:assembly, hbm:chemplant, hbm:desh, hbm:technetium and hbm:hidden. Overriding one changes when its offers unlock; a missing gate advancement keeps them locked.

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; NTM also ships hbm:lc, hbm:ss and hbm:vc. The song registry loads with the world. The item refers to the song through its vanilla jukebox-playable component.