Back
Daggerheart subclasses
system: dh · type: subclasses
Fields
- titleobjectrequiredAt least one language must be non-empty; also used as the title of every tier card
- enstring
- rustring
- descriptionobject
- enstring
- rustring
- class_idintegerrequired
- spellcaststring | nullSpellcast trait, or null for a subclass without oneOne of: STR, AGL, FNS, INS, PRE, KNW, null
- sourcestringCollection key for the subclass and all of its tier cards (own collection; omit or empty for "My content")
- imgstring
- foundationobjectrequiredOne subclass card, shown as soon as the subclass is taken; required on create. On update, a tier that already exists is patched (description replaced if given, features by ids of your own features only, mechanics replaced); a missing tier is created. A tier cannot be removed and null is rejected.
- descriptionobject
- enstring
- rustring
- featuresarray<object>Named abilities of this record. Each entry is either { "feature_id": <id> } for a feature YOU own, or an inline dh-features item (title, description, type, tier, mechanics) that creates a new feature owned by you. Put a mechanic in the entity's own `mechanics` when it is an unnamed effect of the entity itself (e.g. armor that adds +1 evasion, a potion that is a craft recipe). When the effect is a named ability with its own description text - something the player sees as a separate block (e.g. "Reliable", "Heavy") - create it as a feature (inline in `features`) and put the mechanics on that feature.How features are attached
- mechanicsarray<object>Mechanics of this record itself. Types: add, set, res, craft, dice, pool, text, entity, list. On update, the array replaces all of the record's own mechanics ([] removes them); omit it to keep them. Mechanics work only while the card is in the loadout; add/set/dice with config.vault = true also work while a card sits in the vault.Nested mechanics format
- typestringrequiredOne of: add, set, res, craft, dice, pool, text, entity, list
- levelintegerDefaults to 1
- configobjectrequiredThe fields of config depend on the mechanic type value. The Mechanics page lists the fields of every type.Nested mechanics format
- specializationobjectOne subclass card, shown after the first subclass upgrade. On update, a tier that already exists is patched (description replaced if given, features by ids of your own features only, mechanics replaced); a missing tier is created. A tier cannot be removed and null is rejected.
- descriptionobject
- enstring
- rustring
- featuresarray<object>Named abilities of this record. Each entry is either { "feature_id": <id> } for a feature YOU own, or an inline dh-features item (title, description, type, tier, mechanics) that creates a new feature owned by you. Put a mechanic in the entity's own `mechanics` when it is an unnamed effect of the entity itself (e.g. armor that adds +1 evasion, a potion that is a craft recipe). When the effect is a named ability with its own description text - something the player sees as a separate block (e.g. "Reliable", "Heavy") - create it as a feature (inline in `features`) and put the mechanics on that feature.How features are attached
- mechanicsarray<object>Mechanics of this record itself. Types: add, set, res, craft, dice, pool, text, entity, list. On update, the array replaces all of the record's own mechanics ([] removes them); omit it to keep them. Mechanics work only while the card is in the loadout; add/set/dice with config.vault = true also work while a card sits in the vault.Nested mechanics format
- typestringrequiredOne of: add, set, res, craft, dice, pool, text, entity, list
- levelintegerDefaults to 1
- configobjectrequiredThe fields of config depend on the mechanic type value. The Mechanics page lists the fields of every type.Nested mechanics format
- masteryobjectOne subclass card, shown after the second subclass upgrade. On update, a tier that already exists is patched (description replaced if given, features by ids of your own features only, mechanics replaced); a missing tier is created. A tier cannot be removed and null is rejected.
- descriptionobject
- enstring
- rustring
- featuresarray<object>Named abilities of this record. Each entry is either { "feature_id": <id> } for a feature YOU own, or an inline dh-features item (title, description, type, tier, mechanics) that creates a new feature owned by you. Put a mechanic in the entity's own `mechanics` when it is an unnamed effect of the entity itself (e.g. armor that adds +1 evasion, a potion that is a craft recipe). When the effect is a named ability with its own description text - something the player sees as a separate block (e.g. "Reliable", "Heavy") - create it as a feature (inline in `features`) and put the mechanics on that feature.How features are attached
- mechanicsarray<object>Mechanics of this record itself. Types: add, set, res, craft, dice, pool, text, entity, list. On update, the array replaces all of the record's own mechanics ([] removes them); omit it to keep them. Mechanics work only while the card is in the loadout; add/set/dice with config.vault = true also work while a card sits in the vault.Nested mechanics format
- typestringrequiredOne of: add, set, res, craft, dice, pool, text, entity, list
- levelintegerDefaults to 1
- configobjectrequiredThe fields of config depend on the mechanic type value. The Mechanics page lists the fields of every type.Nested mechanics format
Example
A file with one filled-in subclasses record:
[
{
"system": "dh",
"type": "subclasses",
"data": [
{
"title": {},
"class_id": 1,
"foundation": {
"features": [
{}
],
"mechanics": [
{
"type": "add",
"config": {}
}
]
}
}
]
}
]