Changing every team role at once
Keep service and observation covered while you learn the changed task.
Re-test the route after an alpha update
An update matters when it changes what you do in the cafe. Re-check the route in a fixed order instead of trusting an old day script.
Do this now
After an update, run one short observation shift. Check whether the objective wording, order and reputation displays, Sanity behavior, CCTV interaction and interruption flow still match your routine. If one part changes, update that decision only; do not discard every useful habit or repeat an old claim that the current game no longer shows.
01
Action route
Follow the shift in order
- 01
Re-read opening state
Check the day/open display, objective wording and visible HUD before moving.
- 02
Test one normal service action
Confirm the current objective advances the way the interface shows.
- 03
Observe one interruption
Compare team movement, HUD response and recovery flow without forcing a hidden rule.
- 04
Keep only repeatable changes
Update your route when the new behavior shows consistently across more than one run.
02
Decision table
Read the signal, then act
What you seeWhat to doWhy
Only wording changedKeep the route, update the calloutThe player job may be the same even when labels change.
Objective order changedFollow the new interface orderA remembered script should not override the current task.
An old counter no longer worksRemove it from the routeA short safe checklist beats a confident outdated rule.
03
Recovery
Replace these mistakes
Repeating an old objective order
Read the current task before moving, especially after an interruption.
Missing the next action
Name the changed task to your teammates and choose one player to handle it.
04
Quick answers
FAQ
Why does the walkthrough avoid a fixed day script?
The experience is in alpha, so the guide follows visible objectives and repeatable decision points that survive changes better.
What should I check first after an update?
Start with the opening objective and HUD, then test one service action and one interruption before trusting an older route.