Adding Spells, Monsters, and the Rest
Every content type has conventions the 1,607 existing records follow. Match them and new content is indistinguishable from the SRD; break them and the sheet's math — or its pickers — quietly go wrong.
Spells
A spell carries its level, school, casting time, range, components, duration, concentration and ritual flags, effect text — and, load-bearing, its classes list, because the sheet's prepared-spell pickers filter on it: a spell missing its classes is invisible to every caster in the project. Subclass bonus lists ride a parallel subclasses field. Use 2024 wording: this revision rebalanced dozens of spells (@Missing file heals 2d8 now, True Strike is a weapon-attack cantrip), so author from the SRD 5.2 text, not memory.
Monsters
The stat block encodes the 2024 conversion math: challengeRating drives XP per the printed tier tables and proficiency bonus as max(2, 1 + ceil(CR/4)). Fill scores, AC, hit points, speed, senses, traits, actions — and put the behavior in the tactics notes, because that is what the GM plays from. @Missing file is the worked example; @Missing file documents every field.
Items
- Weapons: damage die and type, property flags — finesse and ranged feed the attack formulas — and the 2024
masteryproperty (Sap, Vex, Topple, Cleave…), which classweaponMasterytraining unlocks at the table. - Armor:
acBase,addDexterity,dexterityCap, strength minimum, stealth flag. An armor file never states a wearer's final AC. - Magic items: rules text for the reader, wired fields for the sheet — the shared bonus fields, score overrides,
magicBonuson typed magic weapons, armor, and shields, and the attunement flag. If the text promises a bonus the fields don't carry, the sheet cannot keep the promise.
Classes, subclasses, species, backgrounds, feats
A class file is the engine block: hit die, saves, training, weaponMastery count, casterProgression, pactMagic, spellcasting ability, preparedSpellsTable, and featuresLevel1–20 as rules text. Subclasses mirror it from level 3 up — this revision has no level 1 or 2 subclasses, and the schema agrees. Species carry size, Speed, darkvision, and traits — never ability scores. Backgrounds carry abilityScores, skills, a tool, equipment, and their originFeat reference. Feats are categorized Origin / General / Fighting Style / Epic Boon and integrate through the shared bonus fields.
The pickers and the flow
Two consumers care about your new content beyond the sheet: the filtered spell pickers (feed classes honestly) and the creation flow, whose option screens list specific files by reference. Adding a species, subclass, or background the flow should offer means adding an option node to the flow as well — content alone doesn't appear in guided creation.