Skip to content
Back

Daggerheart communities

system: dh · type: communities

Fields

  • titleobjectrequired
    At least one language must be non-empty
    • enstring
    • rustring
  • descriptionobject
    • enstring
    • rustring
  • 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
    • typestringrequired
      One of: add, set, res, craft, dice, pool, text, entity, list
    • levelinteger
      Defaults to 1
    • configobjectrequired
      The 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 communities record:
[
  {
    "system": "dh",
    "type": "communities",
    "data": [
      {
        "title": {}
      }
    ]
  }
]