tools5e

Templates for 5eTools

See the 5eTools template reference for additional information.

• 5eTools default templates
• 5eTools templates with images
• 5eTools alternate monster templates

See also:

• 5eTools mixed templates

5eTools default templates

5eTools default templates

Valid template keys for 5etools: background, class, deck, deity, feat, hazard, index.txt, item, monster, note, object, psionic, race, reward, spell, subclass, vehicle

5eTools templates with images

Some 5eTools data types have fluff images. These templates include those images in the markdown.

• images-background2md.txt
• images-item2md.txt
• images-monster2md.txt
• images-object2md.txt
• images-race2md.txt
• images-spell2md.txt
• images-vehicle2md.txt

5eTools alternate monster templates

See the Monster template reference for additional attributes.

• Fantasy Statblock statblock in the body

  • Monsters, objects, and vehicles that have statblock: inline will populate the Fantasy Statblock bestiary.
  • monster2md-yamlStatblock-body.txt
  • object2md-yamlStatblock-body.txt

  The important frontmatter elements of this example:

  statblock: inline

  In the body of the note:

  ```statblock
  {resource.5eStatblockYaml}
  ```

  Use {resource.5eStatblockYamlNoSource} to remove the source qualifier on the monster name. Note that you may have to choose from a list of otherwise identical Goblins (as an example) when creating encounters without the source attribute in the name.

  [!TIP] If you're using the Fantasy Statblock plugin to render statblocks and you use the Dice Roller plugin, you'll want to set two config values:

  "useDiceRoller" : true,
  "yamlStatblocks" : true,

• Markdown statblock with minimal YAML frontmatter for use with Fantasy Statblock and Initiative Tracker plugins

  • Monsters, objects, and vehicles that have statblock: true will populate the Fantasy Statblock bestiary.
  • Initiative Tracker only needs a few elements from the statblock for encounter building. {resource.5eInitiativeYaml} will emit only those elements.
  • The statblock-link is used by Initiative Tracker to embed the markdown statblock in the creature view.
  • monster2md-yamlStatblock-header.txt
  • object2md-yamlStatblock-header.txt

  The important frontmatter elements of this example:

  statblock: true
  statblock-link: "#^statblock"
  {resource.5eInitiativeYaml}

  In the body of the note:

  ```ad-statblock
  ...statblock content...
  ```
  ^statblock

  Use {resource.5eInitiativeYamlNoSource} to remove the source qualifier on the monster name. Note that you may have to choose from a list of otherwise identical Goblins (as an example) when creating encounters without the source attribute in the name.

• Markdown statblock, alternate score display - monster2md-scores.txt (similar will work for objects)

  ```ad-statblock
  ...
  - STR: {resource.scores.str} `dice: 1d20 {resource.scores.strMod}`
  - DEX: {resource.scores.dex} `dice: 1d20 {resource.scores.dexMod}`
  - CON: {resource.scores.con} `dice: 1d20 {resource.scores.conMod}`
  - INT: {resource.scores.int} `dice: 1d20 {resource.scores.intMod}`
  - WIS: {resource.scores.wis} `dice: 1d20 {resource.scores.wisMod}`
  - CHA: {resource.scores.cha} `dice: 1d20 {resource.scores.chaMod}`
  ...
  ```
  ^statblock

• Split stings in frontmatter - monster2md-scores.txt (similar will work for objects)

  {#if resource.conditionImmune}
  conditionImmunities:
  {#for condition in resource.conditionImmune.split(", ?")}
  - "{condition}"
  {/for}
  {/if}