Stat blocks and character sheets

Reviewed, and settled (D74 to D85)

The owner reviewed the lane on 21 September: “Looks great.” Two asks, both in: a character levels up on the sheet (the Levelling up section), and every computed number is shown once with its components beneath. Q11 to Q14 were yes; Q15 changed D85.

• D74 — a sheet is its own document. Source values, entries with provenance, hot resources; derived values computed from the definition on read, never stored as truth; the page keeps the prose and shows a projection. The sheet autosaves like Prep. Lane 6c’s one Save covers the page’s own parts.
• D75 — two definitions per system, the character sheet and the creature block, sharing one vocabulary; a character projects to a block, one way.
• D76 — definitions are data, in packs: fields, tables, entries, modifiers, generators, views, imports, migrations; validated on upload; no code. First-party: Pathfinder 2e Remaster and D&D 5e (SRD 5.2.1); then Blades, Dungeon World, Fate, Cypher; Call of Cthulhu and Savage Worlds as definitions only. A system with no definition gets the generic sheet.
• D77 — visibility per field with the audience picker. A block is GMs only until shown; a character’s sheet is the party’s except “just you and the GM” fields; the player edits their own, the GM edits any and can lock a field.
• D78 — creation is the system’s own: each field carries its generator — dice, an array, point buy, boosts, a fixed value — and the sheet walks the steps in order. Every roll is shown and kept. Levelling up is the same machinery: the definition’s levels table, walked in order, with What changes before it applies and a version kept first (added on review, IS-437).
• D79 — entries come from the loaded content with provenance; a removed pack degrades a row to its name. D80 — modifiers are declarative and every computed value can show its derivation.
• D81 — prose stays on the page, shown on the sheet with Edit on the page.
• D82 — Foundry both ways, Pathbuilder in, through the pack’s maps, with provenance.
• D83 — versioning per definition; migrations offered, never forced; nothing becomes unreadable.
• D84 — at the table the block is the card’s face; HP and conditions change from the card; the GM shows it whole or by field. D85 — rolling during play is not Quest Board’s: attacks, checks and saves are rolled at the table or in Foundry; the sheet rolls only where creation and levelling roll, and has no roll buttons (amended on review).

Answered

• Q11 Pathfinder 2e and 5e first, the four CC BY systems and Cypher after — yes (D76).
• Q12 A player edits their own sheet; the GM can lock a field — yes (D77).
• Q13 A character sheet is the party’s to read; a creature block is GMs only until shown — yes (D77).
• Q14 The sheet is its own document with its own autosave, outside lane 6c’s one Save — yes (D74).
• Q15 Rolling at the table — Foundry’s, not Quest Board’s; D85 amended and the roll buttons gone.

After the build survey (D200, D208 to D210)

• D200 — Foundry, Pathbuilder, converting between systems and Update to version n wait for #958; Export keeps Quest Board JSON and Print the sheet.
• D208 — the sheet page carries no product explanations; the game’s own printed reminders stay.
• D209 — Notes & actions lists Actions with their cost and full text, and the header gains Rest…; hero points refill when a session starts.
• D210 — reaching a level adds a milestone; the promise about the recap is gone.

The coverage check: 42 placements, none missing. 35 drawn, 5 deferred (a group or party sheet, phase 3; Foundry import, Pathbuilder, conversion and Update to version n, D200) and 2 catalogued for lane 11 to build (levels by XP or milestone, and the milestone a level adds); the seams on other lanes’ surfaces are classified in their scripts. The check is coverage/lane9.py beside the catalogue.