Pill Binding

A pill binding maps one existing item to pill-only fields. Like every other binding it only matches already registered items, so the physical pill must come from Minecraft, a content mod, or KubeJS. Pill bindings add a consumption action plus the pill toxicity rules that decide when a consumed pill becomes an overdose; these fields are not mixed with the item, weapon or technique bindings.

File Location

Pill binding JSON files go in data/<namespace>/mxt/pill_binding/ within your data pack.

The filename corresponds to its ID. For example, data/example/mxt/pill_binding/returning_pill.json has the ID example:returning_pill.

Fields

Field	Type	Default	Description
items	ItemMatcher	required	Matches existing edible items
on_consume	EntityAction	mxt:no_op	The action executed after consumption finishes
toxicity_gain	NumberProvider	0	Pill toxicity added by this pill
toxicity_threshold	NumberProvider	Double.MAX_VALUE	The overdose threshold
on_overdose	EntityAction	mxt:no_op	The action executed when the threshold is exceeded
toxicity_after_overdose	NumberProvider	0	The pill toxicity value after an overdose
quality_group	Tag<item_quality>	none	The allowed quality group
conditions	EntityCondition[]	[]	The check performed before consumption; supports inline conditions or described condition objects

items

The items matcher accepts one item ID, one item tag (such as "#example:pills"), or a mixed array of both; one binding can therefore cover many physical pills. When multiple bindings match an item, the matcher selects the definition with the lowest priority first, and all four binding types currently use priority 0.

quality_group

quality_group must be a native item-quality tag reference prefixed with #. Its values order defines the group's quality order. When no explicit mxt:item_quality component or forge result exists, the last member not disabled by the mxt:disabled tag becomes the default quality.

The pill cannot be consumed when its current quality is outside the group, the group has no usable member, a binding condition fails, or the quality's own condition fails. See Item Quality.

conditions

conditions is optional. Each entry may be an inline EntityCondition, or an object with condition and an optional translation-key description. Described entries are shown in the item tooltip with a green ✓ when true or a red ✗ when false; the description text itself keeps its normal style. The check runs before consumption.

Example

// data/example/mxt/pill_binding/returning_pill.json
{
  "items": "kubejs:returning_pill",
  "quality_group": "#example:group/pill",
  "conditions": [{"condition": {"type": "mxt:realm", "realm": "example:foundation"}, "description": "condition.example.pill"}],
  "on_consume": {"type": "mxt:heal", "amount": 4},
  "toxicity_gain": 10,
  "toxicity_threshold": 100,
  "toxicity_after_overdose": 25
}

The behaviour id used inside on_consume and on_overdose comes from the Entity Action Types list, and the condition ids come from the Entity Condition Types list.