Ashen March · playtest
Build v0.4.1 · An unfinished wizard roguelike. Allow 20–30 minutes, take breaks, and stop whenever you want. We are testing the game, not your skill.
This page sends no results anywhere. Download your notes below and send them to James through your agreed channel. Ask separately before recording a participant.
- Open the game, craft a spell pair in the grimoire, and choose Walk the Cinder Road. J casts the Mana spell; K casts the Focus signature. Compare a cheap spell with a triggered construction.
- Choose a branch and use its ledges or cover. Try a short and held jump, double jump, dash, crouch under high shots, and a frontal Guard. Explain your most recent damage.
- Compare a reward, cancel, then confirm it. Try a reroll. Explain how your choice changes your next fight.
- Reach an event and the Quiet Hearth. Explain the trade, purchase, or decision to save Embers.
- Suspend during combat, reload, and Continue. Your room restarts; confirmed rewards remain. Fight the Archon. Death is useful evidence, not a failed session.
- For the systems preview, try the separate 24-node route. Later acts currently reuse Cinder encounters. Test Save / transfer between browsers, deny a second tab ownership, and try a discovered-enemy exercise from Chronicle.
- In Controls, compare reduced-impact settings and your usual input device. Note any confusion, fatigue, unexplained damage, or reason to retry.
Builds remain in development. The eight-node slice is the outside-player readability test; the three-act preview tests campaign plumbing, not final regional content or balance.
Optional isolated exercises: Magic lane · Magic ledge · Teaching shots. These older exercises retain their own labeled prototype controls.
James's M2 decision
Record eight outside-player observations on identified builds. At least six should explain their last damage and a meaningful reward decision; look for three viable strategies and recurring unexplained damage. Record named-device limitations, the asset-budget decision, and PASS or REWORK with explicit exceptions. Publishing a build and automated checks do not supply human results.