Stuck Monk Events and Wheel Spins: A Patch-First Recovery Check

Which patch should you check before trying a workaround?

Check whether your installed Demo includes the November 2 notice. It specifically fixes the Monk event becoming stuck and the Trigram Wheel locking when spun twice in the same event. Start from those dated cases rather than applying a pre-fix forum suggestion to every current failure.

The date is the official notice date, not a game version number we invented. The patch confirms a repair was published; it does not independently demonstrate how every old save or every unrelated scene behaves afterward.

What did the older Monk-event report describe?

In the complete original discussion, players reported a loop in the scene where the monk covers the protagonist and a young person’s escape. The stuck dialogue was described as “大師你怎樣了.” A November 1 developer reply suggested clicking 防卡死, then re-entering the game while a fix was being prepared.

A later player in the same thread said the workaround still did not prevent their lock. That counterexample matters: the developer offered a bounded recovery suggestion, not a promise that every scene or save could be repaired that way. The November 2 patch is newer evidence and must remain ahead of the older advice.

What is a useful recovery and reporting order?

1. Record the installed Demo date and exact event or dialogue.
2. Check the November 2 fixes before reproducing an older complaint.
3. Preserve your existing save state; no universal requirement to delete it is documented.
4. If the older named recovery option is present, distinguish trying that suggestion from confirming it repaired the current case.
5. Re-enter as advised and observe whether the scene can proceed; do not mark it fixed merely because the game relaunched.
6. If it still loops, report the choice sequence, build and result, including whether the named workaround was attempted.

No verified filesystem path, cloud-save deletion procedure or forced-reset command is provided here. We also do not recommend an unlimited reload loop. The useful outcome is progress past the scene or a reproducible report that preserves what actually failed.

How do you avoid mixing different problems?

Use the official Steam discussion with your evidence when a current problem persists. This page is checked November 7, through the November 2 Demo notice. It is an editorial recovery checklist, not a personally tested repair service, proof that every bug is gone or permission to overwrite an irreplaceable run.