The Workspace

The project's file types fall into five groups, and knowing which group a type belongs to tells you how to treat it.

Rules and references

rule files are the system text — the compendium the handbooks summarize. @Missing file is the anchor. reference holds table-side summaries. Edit rules only when you mean to change the system for every table.

World content (yours to replace)

character, creature, location, lore, faction, species, archetype, game-start. The shipped files here are examples of the format. Replace them. Do not pile new files next to them.

• A species gives +2 in stats total, or +1 to a stat and +5 Health, plus two Species Powers. Humans trade the stat bonus for Human Feats. A plain Human gets two Human Feats, and a Human variant gets +1 to a stat (or +5 Health) and one Human Feat.
• An archetype has a rarity, from Everyday Common to Legendary, and a genre. It gives bonuses plus General Powers that cost no XP. Rarer archetypes get a bigger budget and more powers.
• A game start shows an opening that begins inside a real place.

Catalog content (extend, rarely replace)

The feat types (general-feat, mana-feat, energy-feat, stamina-feat), the single gear type with its currency files, and the creature-building libraries (creature-offensive-feat, creature-defensive-feat, creature-utility-feat, creature-rank). Every item is one Gear file. Its kind (Weapon, Armor, Shield, Worn, Carried, Tool or Consumable) says what it is, and its slot says where it goes on the sheet. These catalogs are big on purpose. The feat library alone is about 1,350 entries. Add to them following the pricing chapters, and prune only what your genre excludes.

GM behavior

gm-instructions files tell the AI GM how to run the system. Each is named for the condition that fires it — "A player character, NPC, or creature takes damage" — and the body names exact schema fields. Keep that convention: a trigger whose name states its condition is discoverable; a slogan is not.

Play-state

encounter-tracker and action-card support play at the table. Ship them empty or with starter shape; never bake world facts into them.

A note on schemas: the file types are already readable in the workspace, so this manual doesn't restate field lists. It states intent — what makes an entry fit.