3.7 KiB
3.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.
Next: Roll20 smoke test
- 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. Record the date and result. - 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. - Load one alternate theme (for example
build-steel/) and inspect the sheet and chat cards for legibility and contrast in Roll20. - 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.
- 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.
- Add one technique, attempt to add it again, and activate its chat card. Check that text is readable and free of raw Typst markup.
- 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.
- Roll a skill at the threshold boundary and on a natural 1. Check chat outcome and margin. Try public and secret rolls.
- Roll an attack, use its Défendre chat button with the defender token selected, 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.
- Repeat an attack follow-up after closing and reopening the sheet. Record whether the attack context survives; the current worker stores it in memory.
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, armor integrity, technique costs, and temporary effects should be updated automatically. Record the decision before adding automation or UI controls.
- Add local worker tests to Jenkins only after confirming Node is installed on its build agent, or provision a pinned Node runtime there.