Anomaly Cafe Danger Tier List
Spend panic on what actually wipes Emma's Cafe lobbies.
Danger tiers for attention, not ego
This ranking answers one question: when should the whole café interrupt service? It maps to categories from Anomaly List and the response steps in Survive Anomalies. Alpha will rearrange specifics—update your mental stack after Alpha Patch Notes.
S-tier — Full freeze threats
Includes: Pursuit / multi-signal storms; confirmed identity anomalies that isolate players; any event that simultaneously breaks audio + visuals + pathing.
Why S: Wipe potential is high and hesitation multiplies body count in large lobbies.
Team policy: Hard call. Counter freezes new tickets. Watch + flex only investigate. Count heads. No memes.
A-tier — Fast confirm, likely freeze
Includes: Clear visual breaks in major landmarks; directional hostile audio with matching motion; NPC behavior that invades staff spaces.
Why A: Often real, sometimes alpha jank—but waiting too long is worse than a cautious freeze.
Team policy: Soft-to-hard escalate inside ten seconds. Second eyes mandatory. Prep finishes in-hand work only (Recipes and Serving).
B-tier — Soft call, continue light service
Includes: Single-prop oddities; minor text/menu weirdness; one-off ambience layers without a second signal.
Why B: Good teaching moments. Over-freezing B-tier forever is how tickets explode and people stop trusting callouts (Co-op Tips).
Team policy: Soft call with confidence %. One investigator + global watch coverage. Counter keeps simple tickets moving.
C-tier — Log and learn
Includes: Suspected desync chairs; texture pop-in; temporary collision weirdness that matches Known Bugs.
Why C: Training data for baselines, not crisis.
Team policy: Note it, maybe screenshot, do not derail the shift unless it gains a second signal.
Modifiers that bump a tier upward
- Near 24-player noise floor (missed callouts)
- Newcomer on counter lead
- Patch day instability
- Back-of-house isolation already in progress
- Multiple soft calls in different zones within a minute
Modifiers that bump a tier downward
- Identical glitch reported all week as a bug
- Only one player sees it and refuses a re-check
- Happens during a known hitchy load-in window
Linking tiers to practice
Beginners should not live in S-tier theory. Use Beginner Priority to build detection reps on B-tier visuals first, then audio, then pursuit drills.
Detection habits: Spot Anomalies, Spotting Checklist. Map language: Café Map.
Anti-lists we will not publish
- Pay-to-win script tiers
- Fake “code reward tiers” while Active Codes remains empty
- Cross-game monster ladders from unrelated cafés
Related pages
Rank the threat, not your scream volume. Emma’s Cafe is loud enough already.
Worked example
A single crooked tray is B-tier: soft call, confirm, keep simple tickets alive. A crooked tray plus silenced kitchen hum plus a customer in a staff lane is A/S territory: freeze novelty, buddy investigate, prepare regroup. Teaching that severity jump matters more than memorizing names alpha will rename. Practice the decision with Survive Anomalies.
Recalibrating after a lucky escape
Surviving an S-tier event through pure chaos does not mean your tiering was wrong—it means you got fortunate. In review, still mark it S if wipe potential was real. Conversely, if a hyped threat never threatens tickets or lives across multiple patches, demote it. Evidence over legend keeps this list useful.
Comms budget by tier
S-tier: one talker, everyone else repeat-backs only. A-tier: short confirms allowed. B-tier: teaching sentences OK if tickets are stable. C-tier: chat or after-action notes. Budgeting words prevents the ironic wipe where the anomaly was survivable but the lecture was not. Post the budget in your Discord pin beside Co-op Tips so newcomers absorb it before peak hour.
Frequently Asked Questions
Quick answers to the most common questions.
What counts as S-tier?
Multi-signal or pursuit events with high wipe potential—hard call and freeze new complex tickets immediately.
Should we freeze for every visual oddity?
No. Single-prop B-tier tells need soft calls and confirmation so the lobby still trusts you later.
Can a bug be S-tier?
If it behaves like a wipe threat, stabilize first. Reclassify it as a bug afterward in Known Bugs.
How often will this tier list change?
After meaningful alpha patches or when the community finds consistently deadlier patterns.