Quest complete but movement blocked? Check release states
Give a text AI a simplified state machine and event sequence to draft a minimal reproduction fixture and state table for human review. This is a drafting exercise; the source used Claude Code.
Execution environment and usage
AI / software
General text chat (example: Claude)
Where to operate
A general text-AI conversation; for example, a new chat on the Claude website where available. This is a text exercise, not an agent run.
Getting started
- Open an authorized text-chat tool; Claude’s web entry is claude.ai.
- Paste the relevant text from a simplified state machine and event sequence and the prompt below; request a minimal reproduction fixture and state table.
Setup and plan requirements
Prepare shareable, de-identified a simplified state machine and event sequence; paste only relevant excerpts. An available chat account and allowance are needed; Claude also has location and age requirements. This exercise needs no connector or execution permission from the original source workflow. The chat can produce the text draft. Any later checks of actual files, screens, audio or test results require a person, suitable software and existing outputs. Mark checks unverified when those outputs are absent.
Prompt portability limits
Questions and supplied text can be adapted to another capable chat tool. This produces a draft, not file access, code execution, account connections or the original operational outcome.
Usage limitations
The source reports Claude Code. This page adapts it into a minimal reproduction fixture and state table, not a completed automated workflow in that product. Follow the checks below; source outcomes do not establish this exercise’s results.
Environment sources
適用情境 / When to use
Give a text AI a simplified state machine and event sequence to draft a minimal reproduction fixture and state table for human review. This is a drafting exercise; the source used Claude Code. The page gives an update date, not an established original publication date. Human playtesting still found issues.
步驟 / Steps
- Prepare an owned simplified state machine and reproducible event sequence.
- Compare states before, during and after the release condition.
- Check agreement between messages, allowed actions and state, retaining untested branches.
提示詞 / Prompt
Using [owned state machine/restriction and release rules/synthetic event sequence], design a minimal fixture. List state, displayed message and allowed actions after each event, checking that completion really clears restrictions. Specify tests only; do not claim a fix or complete game coverage.
留意事項 / Cautions
- Do not copy source game content.
- Harness success does not replace full visual acceptance.
來源限制 / Evidence limits
Automation does not establish game feel or correctness on every path.
流程說明 / Workflow note
These steps and prompts are original, untested exercises by this site, not the author’s verbatim workflow. Reported results do not guarantee exercise outcomes.
原始工具組合 / Original tool stack
Claude Code; Sonnet 4.6; Node.js playtest wrapper
Source checked: 2026-10-20