Skip to content
Back

Daggerheart weapons

system: dh · type: weapons

Fields

  • titleobjectrequired
    At least one language must be non-empty
    • enstring
    • rustring
  • tierintegerrequired
    min 1 · max 4
  • typestringrequired
    One of: primary, secondary
  • traitstringrequired
    BEST - the wielder picks their best trait
    One of: STR, AGL, FNS, INS, PRE, KNW, BEST
  • rangestringrequired
    One of: melee, veryclose, close, far, veryfar
  • burdenintegerrequired
    1 - one-handed, 2 - two-handed
    One of: 1, 2
  • damageobjectrequired
    • countintegerrequired
      min 1
    • dieintegerrequired
      One of: 4, 6, 8, 10, 12, 20
    • die2integer
      Second die of the same count, 0 - none
      One of: 0, 4, 6, 8, 10, 12, 20
    • modinteger
    • typestringrequired
      phy - physical, mag - magic, phy_mag - either
      One of: phy, mag, phy_mag
  • magicboolean
  • sourcestring
  • imgstring
  • 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
    • 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

Example

A file with one filled-in weapons record:
[
  {
    "system": "dh",
    "type": "weapons",
    "data": [
      {
        "title": {},
        "tier": 1,
        "type": "primary",
        "trait": "STR",
        "range": "melee",
        "burden": 1,
        "damage": {
          "count": 1,
          "die": 4,
          "type": "phy"
        }
      }
    ]
  }
]