Skip to main content

Datapack Examples

The examples below chain the common systems into a minimal loop: resources, realms, the aura environment, cultivation actions and item fuel all come from the data pack, while the physical items are still registered by KubeJS or another mod.

Read Datapack Overview first if you are not yet familiar with file locations, IDs and the mxt:disabled tag.

Example Layout​

A small data pack with these files looks like this:

data/example/mxt/resource/spirit_power.json
data/example/mxt/element/common.json
data/example/mxt/realm_stage/qi_condensation.json
data/example/tags/mxt/resource/disabled.json

Disabling a Definition​

This is a tag file, not a registry entry. It belongs to the mxt:disabled tag of the target registry — here resource — and each listed ID stops being used by the matching service while staying resolvable for other definitions.

{
  "replace": false,
  "values": ["example:old_resource"]
}

Do not replace vanilla tags with a custom tags key: tag files always live under data/<namespace>/tags/.... See Disabling a Definition for the fixed path and the full rules.

Resource: Qi​

Registry: resource — Resource.

{
  "default_value": 0,
  "max": "100 + realm_rank * 20 + absorbed_aura * 0.1",
  "regen": 0,
  "first_realm": "example:foundation",
  "bars": [
    {
      "anchor": "left",
      "order": 10,
      "renderer": {"type": "mxt:boss_bar", "bar_index": 1},
      "value_display": "current_and_maximum"
    }
  ]
}

The maximum is a formula that reads the realm rank and the aura the player has absorbed, and the inline bar draws the current and maximum value on a boss bar.

Item Aura: Spirit Stone​

Registry: item_aura — Item Aura.

{
  "items": "mxt:spirit_stone",
  "type": "example:spirit_power",
  "aura": 100,
  "consume_speed": "0.5 + level * 0.05",
  "release_speed": 2,
  "exhausted_action": {"type": "mxt:no_op"}
}

items uses an item matcher, so an item tag works here as well as a single item ID.

Cultivation Action: Meditation​

Registry: cultivate_action — Cultivate Action.

{
  "aura_kinds": ["example:common"],
  "absorb_amount": "1 + level * 0.1",
  "aura_costs": {"example:spirit_power": 1},
  "tick_interval": 20,
  "tick_action": {"type": "mxt:no_op"}
}

The action only absorbs aura whose kind is listed in aura_kinds, and the amount scales with the player's level.

Item Binding: Granting a Spirit Root​

Registry: item_binding — Item Binding.

{
  "items": ["kubejs:root_pellet", "#example:root_pellets"],
  "actions": [
    {"type": "mxt:grant_spirit_root", "spirit_root": "example:fire_root"}
  ],
  "quality_group": "#example:quality/root_pellet"
}

kubejs:root_pellet must already be registered, for example by a KubeJS startup script (KubeJS); the binding only attaches the action to it.

Physique: Innate Sword Bone​

Registry: physique — Physique.

{
  "holder_condition": {
    "type": "mxt:has_spirit_root",
    "spirit_root": "example:fire_root"
  },
  "attribute_modifiers": [
    {"attribute": "minecraft:attack_damage", "id": "example:physique/sword_bone", "amount": 2, "operation": "add_value"}
  ],
  "granted_abilities": ["example:sword_focus"]
}

The entity condition decides who may hold the physique, the attribute modifiers are applied while it is held, and granted_abilities lists the abilities it grants.

Item Binding: Granting a Physique​

Registry: item_binding — Item Binding.

{
  "items": "kubejs:body_pill",
  "actions": [
    {"type": "mxt:grant_physique", "physique": "example:innate_sword_bone"}
  ]
}

This is the other half of the pair: the pill grants the example:innate_sword_bone physique whose own condition is checked when it is applied.

Where to Go Next​