This Anomaly Cafe anomaly list is a currently documented signal index, not a claim that every entity has been named or that the roster is complete. The creator confirms unexpected anomalies as a core threat. Current same-game guides and footage support customer observation, camera comparison in some builds, environmental changes, service interruptions, and active survival pressure. Public evidence does not yet support a reliable named catalog with rates and counters.
How to read the index
Each card lists a signal class, likely place to notice it, response priority, evidence status, and check date. A class may contain several events or may describe different stages of one event. Do not convert these labels into official entity names. When the live game supplies a name, preserve its exact spelling and build context before adding it.
“Community reported” means a directly relevant current guide or walkthrough supports the behavior. “Needs in-game testing” means the broad idea is plausible but not reliable enough to use as a specific rule. “Official” applies only to the creator’s broad service, maintenance, and survival premise.
Currently documented anomaly signal index
Visible customer mismatch
Type: Visual / customer
Source area: Intake or dining view
Effect: A customer detail differs from the current baseline.
Response: Pause acceptance, compare again, and use current feedback.
Status: Community reported · 2026-08-20
Customer behavior mismatch
Type: Behavioral
Source area: Customer route
Effect: Movement or interaction repeats outside normal service.
Response: Confirm from another player or viewpoint; rule out lag.
Status: Community reported · 2026-08-20
Alternate-view mismatch
Type: Observation / visual
Source area: Available camera interface
Effect: The alternate view shows a difference not clear in direct view.
Response: Name camera or viewpoint and follow live response controls.
Status: Community reported · 2026-08-20
Environmental mismatch
Type: Visual, audio, or route
Source area: Cafe landmarks
Effect: Furniture, lighting, sound, or access changes unexpectedly.
Response: Compare with maintenance prompts and seek a second cue.
Status: Needs in-game testing per event · 2026-08-20
Operational interruption
Type: Service disruption
Source area: Intake, preparation, or delivery
Effect: Normal cafe work becomes unsafe or impossible.
Response: Freeze new tickets, secure routes, and restore the loop afterward.
Status: Official broad premise; exact event unresolved
Immediate survival threat
Type: Active danger
Source area: Determined by current event
Effect: Live feedback requires players to prioritize survival.
Response: Follow current prompts, create space, communicate, regroup.
Status: Official broad premise; no universal counter
Add a specific encounter safely
A useful named entry needs the exact in-game name or a clearly marked descriptive label, repeatable cue, location or trigger context, player effect, response that was actually tested, build date, and evidence level. A screenshot or one dramatic video title is not enough to establish a complete rule.
If a source demonstrates the cue but not the counter, publish only the cue. If players disagree about a name, keep the descriptive class. If an update changes behavior, retain the date and revise the active entry instead of pretending both versions apply.
Use the list during a shift
Do not search the entire index while danger is active. Establish a baseline before the shift, choose the class that best matches the first credible cue, and follow current game feedback. The class helps you communicate: visual customer mismatch, behavior mismatch, alternate-view mismatch, environmental change, operational interruption, or active threat.
After the run, compare observations and decide whether the evidence is repeatable. This keeps live decisions quick and prevents unverified details from becoming permanent team folklore.
Distinguish anomaly, maintenance, and bug
Maintenance normally has a visible task or interaction that restores a cafe function. An anomaly is part of the survival pressure and may trigger warning or response feedback. A bug may produce a stuck animation, missing prompt, or server-specific mismatch without a consistent event result.
Use location, timing, repetition, current objective, and teammate observation. If the problem clears through a maintenance prompt, record it as upkeep. If the game confirms danger, switch to survival. If it cannot be reproduced and no feedback appears, keep it uncertain.
Fields still requiring live confirmation
The complete anomaly count, official names, visual forms, sound cues, behavior, rarity, spawn conditions, risk levels, damage, failure outcomes, rewards, and counters remain unresolved. This page does not assign numbers or tier labels to those fields. The spotting guide explains confirmation; the survival guide explains response and recovery.
Frequently asked questions
Why are there no invented entity names?
Names are useful only when players can connect them to the exact live game. A descriptive signal class is safer than copying a label from another game or fan post.
Can one class contain several anomalies?
Yes. The classes organize how a player notices and responds; they are not claims about the game’s internal roster.
What should I do with a new discovery?
Record the build date, location, cue, game feedback, result, and whether another independent run reproduced it. Leave unsupported fields empty.