Anomaly Cafe Anomaly List (Alpha Catalog)
Category-first threat notes you can update as bi-weekly patches land.
How to read this list during alpha
Anomaly Cafe will not sit still. Named creatures, prop swaps, and audio stingers can appear, rename, or vanish between bi-weekly drops. This page is a category catalog with examples of what counts—not a fake promise that every future entity is already documented.
Use it with Spot Anomalies for detection and Survive Anomalies for response. Severity opinions live on Danger Tier.
Category A — Visual environment breaks
Signals: Missing/extra décor, mirrored posters, impossible furniture placement, lights with wrong color temperature, text that changed meaning.
Why it matters: These are the most teachable tells for new crew members. They reward baseline memory from your first minute in Emma’s Cafe (Café Map).
Team move: Soft call → second eyes → if confirmed, pause new tickets and inspect as a pair.
Category B — Audio layer breaks
Signals: Double music beds, silenced machines, directional footsteps without bodies, dialogue loops with broken timing.
Why it matters: Audio catches threats outside your current camera cone—critical in full 24-player chaos.
Team move: Location-tag the sound; nearest runner peeks while watch keeps global scan (Co-op Tips).
Category C — Customer / NPC behavior breaks
Signals: Pathing through props, staring routines, order nonsense that is not normal alpha jank, guests in staff-only spaces.
Why it matters: The café fantasy weaponizes the mundane. Service players are first witnesses (Recipes and Serving).
Team move: Do not argue with the NPC—argue with your baseline. Confirm, then escalate.
Category D — Pursuit / pressure events
Signals: Direct chase pressure, zone denial, forced separation hooks, sudden multi-signal storms.
Why it matters: This is where detection failures become wipes. Survival playbook takes over (Survive Anomalies).
Team move: Collapse to agreed safe pattern; counter lead holds leftover tickets; no hero splits.
Category E — Identity / cast anomalies
Signals: Familiar faces in wrong contexts, silhouettes that match Characters notes but break rules, “helpfulness” that isolates players.
Why it matters: Story-flavored threats are easy to emotional-trick. Keep callouts mechanical.
Logging a new anomaly (player method)
When you find something not covered:
- Screenshot/clip with timestamp.
- Note patch day (Alpha Patch Notes).
- Write: zone + signals + confidence + outcome.
- Check Known Bugs before you meme it into lore.
- Teach it next session using Beginner Priority if it is common.
What we refuse to list
- Stolen rules from other Roblox café horror titles
- Invented official names presented as fact
- “Always do X” claims that contradict a fresh build without evidence
Cross-links for practice
Keep the catalog honest. Emma’s Cafe earns its fear when the list grows from receipts, not from copy-paste.
Example log entry template
2026-08-10 // post-patch // dining floor left // menu text mirrored // confirmed by 2 // soft to hard // no pursuit // check lighting notes
Receipts beat vibes when someone asks whether “the menu thing” returned. Teach Category A visuals before pursuit stories so newcomers follow Beginner Priority without scream chat.
Category crossover events
Real nights often blend categories: a visual break that becomes audio pressure, or a cast oddity that turns into pursuit. When logging, tag primary and secondary categories so your binder shows crossover patterns after patches. Crossovers usually deserve a temporary bump on Danger Tier until the lobby learns the new shape.
Field kit summary
Carry four habits every session: name the category, tag the zone, declare confidence, and decide freeze vs continue. Those habits turn this catalog into action instead of trivia. When alpha adds a named entity, slot it under the category it behaves like first; rename debates can wait until after the shift survives.
Frequently Asked Questions
Quick answers to the most common questions.
Why aren't anomalies given fixed official names here?
Alpha naming and sets change. Categories stay useful across patches while we fold in confirmed names over time.
Which category should beginners study first?
Visual environment breaks—then audio. See Beginner Priority for a full practice order.
Can bugs look like anomalies?
Yes. Confirm with a second player and check Known Bugs before treating every desync as a designed threat.
Where do I go after identifying a category?
Use Survive Anomalies for response steps and Danger Tier for how hard to prioritize the threat.