Response card

What to do when the cafe stops feeling normal

Anomaly behavior can change during alpha. Use a response pattern that works before you have memorized every character or scare.

Do this now

When something changes unexpectedly, stop starting new service actions. Say what changed and where you saw it. Keep the team together long enough to compare the room, then use the current objective and visible interface to decide whether to inspect, wait or return to service. Do not turn one uncertain sighting into a confident rule for the next run.

01

Action route

Follow the shift in order

  1. 01

    Stop the task chain

    Finish or safely leave the action in front of you; do not send every player in a different direction.

  2. 02

    Name the change

    Describe the object, character, sound or room area that changed without adding a theory.

  3. 03

    Check the team state

    Confirm who saw it, who is safe and whether the visible HUD changed.

  4. 04

    Resume deliberately

    Once the room is stable, re-read the objective and choose one next action.

02

Decision table

Read the signal, then act

What you seeWhat to doWhy
Only one player saw the changeVerify before spreading outA second view is more useful than a fast guess.
The HUD or objective changedTreat the new text as the routeIt gives the team a shared next step.
Nothing is currently changingReturn to service with one observerThe cafe loop still needs to move forward.
03

Recovery

Replace these mistakes

Naming every odd detail an anomaly

Replacement: compare what changed and how the interface responds.

Following a copied counter

Replacement: use the visible objective and team observation for the run in front of you.

Leaving service abandoned

Replacement: keep one player aware of the order state when it is safe to do so.

04

Quick answers

FAQ

Where is the complete anomaly list?

This page avoids publishing names and counters that are not stable enough yet. Use the response checklist for the version you are playing.

Should the whole team investigate?

Not automatically. First compare what changed, then keep only the people needed on the inspection while the rest hold the shift state.