Back
Daggerheart domain cards
system: dh · type: cards
Fields
- titleobject
- enstring
- rustring
- descriptionobject
- enstring
- rustring
- levelinteger
- domain_idinteger
- typestringCard type. "subclass" is not accepted: subclass tier cards (foundation/specialization/mastery) are created through dh-subclasses; on such a card type, subtype and title are set by its subclass and cannot be changed here (description, features, mechanics, img, stress can). "ancestry" and "community" are not accepted either: those cards are managed through dh-ancestries / dh-communities / dh-transformations. This content type covers domain cards only
- subtypestring
- stressinteger
- sourcestring
- imgstring
- 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
- 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
Example
A file with one filled-in cards record:
[
{
"system": "dh",
"type": "cards",
"data": [
{
"type": "example type",
"source": "example source",
"img": "example img"
}
]
}
]