Skip to content

System Fixture Examples

This folder contains example fixture files that illustrate the data format for System trait definitions. These are reference examples showing how system data is structured — the actual production data is currently seeded via SQL migrations in packages/server-core/migrations/.

Structure

Each system has its own subfolder:

fixtures/
  dnd5e-2014/
    metadata.json             # Core system metadata
    prop-types.json           # Property type definitions
    property-definitions.json # Property definitions (ability scores, HP, etc.)
    conditions.json           # Status condition definitions (with SVG badges)
    bars.json                 # Token bar definitions
    light-source-types.json   # Light source definitions
    vision-types.json         # Vision type definitions
    campaign-functions.json   # Reusable JavaScript functions for Actions
  system8/
    metadata.json
    campaign-functions.json   # System 8 has unique damage/attack formulas

Usage

These files serve as:

  1. Documentation — Shows the exact shape of each trait type
  2. Import format — Future fixture import feature will accept this format
  3. Template — Community system authors can use these as starting points

Notes

  • id fields in these examples use the {systemId}-{name} convention for system-level defaults
  • systemId is set and campaignId is null for all system-level rows
  • isSystemDefault and isEditable are runtime-computed flags, not stored in the fixture
  • SVG badges in conditions are inline SVG strings (64×64 viewBox)