Skip to main content

NPCs and Monsters Tab

Use this tab as your creature library for prep and encounter execution.

When to Use​

  • building reusable enemy and ally catalogs
  • preparing encounters ahead of session time
  • filtering creatures by campaign rulesets

When Not to Use​

  • tracking active turn-by-turn combat outcomes
  • storing broad campaign journal entries
  • scheduling sessions and attendance workflows

Key Tools​

  • search and pagination controls
  • show-all-systems toggle
  • add NPC/Monster form
  • edit existing records
  • ruleset tagging
  • JSON import/export

Creature Record Fields​

Typical fields include:

  • name and creature type
  • combat stats (HP, AC, initiative bonus)
  • notes and description
  • image
  • grid footprint or token scale fields
  • ruleset tags (system tags)

Ruleset-Aware Filtering​

  • records can be tagged with built-in and custom rulesets
  • filters help keep list views relevant per campaign
  • show-all-systems can temporarily widen the pool

Import and Export​

Use JSON import/export to:

  • migrate bestiary content between campaigns
  • keep backup snapshots of custom creatures
  • bootstrap a campaign quickly with prebuilt stat blocks

NPC Upload JSON Template​

Download a starter template here:

Top-level payload keys:

  • schema_version: optional string for format versioning
  • source: optional string for your own reference
  • default_rulesets: optional array used when a creature omits rulesets
  • creatures: required array of creature records

Per-creature keys:

  • name: required non-empty string
  • type: optional, one of NPC, Monster, Boss (defaults to NPC)
  • hp: optional number or ? string
  • ac: optional number or ? string
  • init_bonus: optional integer (defaults to 0)
  • grid_width: optional integer 1 to 20 (defaults to 1)
  • grid_height: optional integer 1 to 20 (defaults to 1)
  • notes: optional string
  • rulesets: optional array, falls back to default_rulesets
  • image_url: optional string or null

Notes:

  • The importer also accepts a root JSON array of creatures for legacy files.
  • Duplicate detection is name-based and case-insensitive; first matching name wins.
  • At least one valid ruleset must be present per creature (directly or via default_rulesets).

Common Workflow​

  1. Add recurring factions and common enemies.
  2. Tag each entry with the correct ruleset(s).
  3. Import/export snapshots before major edits.