Medicinal Property (medicinal_property)
A medicinal_property is the identity of one medicinal effect: it answers "which property is this", not "how strong is it". The definition has no fields at all — no number, no item binding, no element. Potency is written wherever the property is used.
The ids come from your content pack. Do not reuse the id of an element, an aura or a resource: each is its own identity, and nothing converts between a property and an element.
File Location
Medicinal property files go in data/<namespace>/mxt/medicinal_property/ within your data pack.
Purpose: Medicinal identities.
The filename corresponds to its ID. For example, data/example/mxt/medicinal_property/blood_moving.json has the ID example:blood_moving.
Fields
| Field | Type | Default | Description |
|---|
The file is an empty object: the name and description are both generated from the entry id, and the definition has no writable text field. data/example/mxt/medicinal_property/blood_moving.json has the id example:blood_moving, so its name key is mxt.medicinal_property.example.blood_moving and its description key is that plus .description.
{}
Where It Is Used
| Where It Is Used | Field | Meaning |
|---|---|---|
Alchemy recipes (recipe type mxt:alchemy) | main_requirements / auxiliary_requirements | A map from properties to potency thresholds: which main and auxiliary properties this recipe asks for, and how much of each. |
Spirit herbs (spirit_herb) | main_effects / auxiliary_effects | How much of that property each item contributes in the main or auxiliary role. |
One property can carry different thresholds in different recipes, and one herb can give different potency in its main and auxiliary roles: the property only says which effect it is, and every number lives at the place that references it. How recipes compare potency and how herbs declare it is on alchemy_recipe and spirit_herb.