Protect
Address a customer who may be at immediate risk.
A lost customer conflicts directly with the official save and no-death goals.
A role-first comparison for one concrete shift decision, not an unsupported anomaly or upgrade grade.
Protect, Verify, Serve, and Coordinate priority rows with confidence labels help a beginner or returning player choose the next action. Each row explains when to use it: customer safety first, then a verified anomaly response, routine service, and team coordination. No fictional entity grades are published.
Filter customer safety, anomaly response, service, or co-op. The visible cards include the action and its basis.
Address a customer who may be at immediate risk.
A lost customer conflicts directly with the official save and no-death goals.
Confirm the anomaly before applying a specific response.
Only Head Banger coffee is verified; an incorrect match can create avoidable risk.
Cook and serve before guest patience expires.
Time-sensitive service is the base game loop and must continue while anomalies are checked.
Split service, observation, and support attention across 3+ players.
Coordination supports the official shared-shift milestones without inventing player classes.
Customer risk comes first, then response confidence, order patience, and team coverage.
The order will change only when current game conditions support a different player decision.
No. A complete comparable anomaly roster is unavailable, so the page ranks player priorities.
Protect an at-risk customer, verify the anomaly, maintain service, then coordinate the wider team.
No. Badge conditions and the service loop are official; the ordering is an independent decision aid.
Change attention when immediate customer risk, clue confidence, order patience, or team coverage changes.