6.7 KiB
Ravenous sheet worklist
This list tracks the next development steps from AGENTS.md. Mark an item complete only after its stated check passes. Keep a note of the Roll20 test date and any failures; local worker tests do not reproduce Roll20's parser, browser, or chat.
Done locally
- Generate the sheet from the pinned
ravenous_typstdata and run the Python build tests (uv run python -m unittest discover -s tests -v). - Add local worker tests (
node tests/test_worker.mjs) for derived values, resistance and protection summaries, technique import, skill outcomes, attack follow-up calculations, and damage mitigation. - Verify generated artifacts with
./scripts/build.sh --check. - Add themed exports from the book palette data, with a separate output directory for alternate CSS and deterministic checks.
- Add a minimal GM-only Roll20 Mod proof of concept that creates one
character from a JSON
name; test valid and invalid commands locally. - Add origin powers from the pinned book data stage by stage in an editable Powers tab, while preserving custom rows and preventing duplicate imports.
- Add a GM-only character JSON export/import Mod script and a monster database converter. Verify round trips, repeating rows, invalid input, and all master-visible monsters locally.
- Define the versioned craft JSON interface and add a GM-only Mod importer for weapons, protections, consumables, and temporary effects. Validate all destinations, handout input, and invalid payloads locally.
Next: Roll20 smoke test
-
Install
roll20_mod/ravenous_craft_import.js, import one entry of each supported type from inline JSON and from a private handout, then reopen the destination sheet and confirm every field persists. -
Install
roll20_mod/ravenous_import_name.jsas a New Script in a test game, run!ravenous-import-name {"name":"Ariane"}as GM, and confirm a single new character appears in the journal. 2026-09-17: user reports that the test worked in Roll20. -
Install
roll20_mod/ravenous_character_io.jsin a test game. Export an edited sheet, save its JSON outside Roll20, import it from a GM handout, and compare notes, abilities, attributes, and repeating rows. Import one converted monster and check each mapped row and any worker recalculations. 2026-09-17: user reports this workflow completed successfully in Roll20;local_exports/character.jsonis the local saved export and is excluded from Git. -
Load
build/ravenous.html,build/ravenous.css, andbuild/translation.jsoninto a Custom Sheet Sandbox with Legacy Sanitization disabled. Record the date, browser, and any console or worker errors. 2026-09-17 attempt: user supplied a Firefox console log (browser inferred from Firefox-specific messages). It showsStarting up WEB WORKER, CSP warnings for inline scripts/event handlers, Sentry CDN CORS/integrity errors, andUncaught SyntaxError: missing ] after element listinvtt.bundle. Follow-up, 2026-09-17: user confirms all Legacy Sanitization is disabled. A new Firefox log reportsSyntaxError: "" string literal contains an unescaped line breakfromsheetsandbox.bundle.jsafter sheet worker startup. The generated worker parses and passes local Node tests. Generated data was split into shorter source lines (the longest is now under 3.5 KB instead of 128 KB) as a compatibility attempt. Final retest, 2026-09-17: user reports the sheet now works with Legacy Sanitization disabled. The supplied console log shows sheet worker startup and no worker syntax error; only VTT startup, a CSP frame notice, and a layout warning remain. -
Load one alternate theme (for example
build-steel/) and inspect the sheet and chat cards for legibility and contrast in Roll20. 2026-09-17: user reports that the themes work perfectly. -
Create an attacker and defender, plus a token representing the defender. Open both sheets; switch every tab; add, edit, delete, and reorder a repeating row. Reopen each sheet and confirm values persist. 2026-09-17: user reports values appear to persist; repeating row reorder still needs explicit confirmation.
-
Change base and temporary characteristics, stage, a skill rank, and a custom skill. Confirm the displayed totals update and that derived stats use the permanent characteristic as intended. 2026-09-17: user reports calculations done in Roll20.
-
Add one technique, attempt to add it again, and activate its chat card. Check that text is readable and free of raw Typst markup. 2026-09-17: user reports techniques work in Roll20.
-
Select an origin, add one stage of powers, try adding it again, then add another stage and a custom power. Change origin and reopen the sheet. Confirm existing rows persist and selection alone adds no rows. 2026-09-17: user reports powers work in Roll20.
-
Roll a skill at the threshold boundary and on a natural 1. Check chat outcome and margin. Try public and secret rolls. 2026-09-17: user reports rolls generally work but CF was marked one above the die maximum. The worker now marks the maximum face as critical failure; retest in Roll20.
-
Roll an attack, use its Défendre chat button with the defender token targeted when prompted, then use Dégâts and Subir. Test zero successes, more successes than RMax, multiple checked resistances, one active protection, depleted integrity, and a fixed location. Confirm DMG and AB against hand calculations. 2026-09-17: user reports repeated missing-selected-token warnings when clicking without a token. The worker now requests one named target; retest.
-
Repeat an attack follow-up after closing and reopening the sheet. Record whether the attack context survives; the current worker stores it in memory. 2026-09-17: user believes it works; verify damage values after reopening.
After smoke test
- Fix each observed Roll20 defect with a focused reproduction and a local test where the behavior can be simulated. Recheck it in the sandbox.
- Compare derived statistics, defense thresholds, damage, and AB formulas with the pinned rulebook. Record the rule reference and any intentional deviation before changing mechanics.
- Decide whether HP should update automatically. 2026-09-17: user decided to keep HP updates manual for now.
- Decide whether armor integrity, technique costs, and temporary effects should update automatically. 2026-09-17: user wants all these updates manual for now.
- Add local worker tests to Jenkins only after confirming Node is installed on its build agent, or provision a pinned Node runtime there.