Anomaly Cafe Known Bugs (Alpha)

Alpha warning, taken seriously

The official Anomaly Cafe description asks players to expect bugs and issues and to report them. This page helps your lobby do that without calling every hitch an eldritch event—or worse, ignoring a real anomaly because “it’s probably lag.”

Game context: Roblox alpha, bi-weekly updates, max 24 players, co-op café + anomaly loop.

Bug vs anomaly quick test

Ask:

1. Does a second player confirm the same detail? If only you see it, suspect replication—or a personal targeted threat. Confirm carefully (Spot Anomalies).
2. Is it patterned or random? Designed tells often feel authored; random pop-in feels like streaming assets.
3. Does it survive a rejoin? Many alpha bugs evaporate after a session reset; many threats do not care.
4. Did it arrive with a patch? Check your Alpha Patch Notes ritual.
5. Does responding like Survive Anomalies change outcomes? If “survival” does nothing and everyone rubber-bands, log a bug.

Common alpha friction buckets

Use these labels in callouts so you do not over-escalate:

• Prompt desync — Interact key needs a re-center or rejoin (Controls).
• Physics jitter — Chairs/props bouncing without meaning.
• Audio one-shot repeats — Glitchy loops vs new layered stingers.
• Character teleport blips — Player avatars hitching in full servers.
• UI flicker — Ticket text vanishing for a beat during rushes.

Still tidy the café (Shift Checklist); clutter plus jitter creates fake horror.

How to report usefully

Bring to the developer community (via official group channels on the Links Hub):

• Platform (PC/mobile), approximate server size
• Steps to reproduce
• Expected vs actual
• Whether it was visible to multiple players
• Clip if possible
• Build timing (today vs right after patch)

Avoid reports that only say “game broken” with no zone language from Café Map.

Lobby etiquette around bugs

• Do not harass teammates for cautious soft calls that become bugs.
• Do not gaslight teammates if you cannot see their tell yet—move to their zone.
• Keep Co-op Tips discipline even when the bug is funny.

Things that are not “bugs to fix with scripts”

Malware peddlers love “bug fix scripts.” Our Working Scripts list is empty for a reason. Fixing alpha means waiting for developers—not injecting mystery code (How to Use Scripts).

When bugs and anomalies stack

Patch week can be spicy: real threats hide inside jank. Policy:

1. Stabilize as if threat is real if wipe potential is high (Danger Tier).
2. After clear, classify with cooler heads.
3. Teach newcomers via Beginner Priority that both layers exist.

Related pages

• Updates Hub
• Anomaly List
• Guides Hub
• Codes Hub (unrelated, but also honesty-first)

Call the weirdness. Sort it after everyone is safe.

Soft-call phrases that keep trust

“Possible desync chair, dining right, 30%, watching.” “Prompt delay on prep, rejoining if it repeats.” “Audio loop feels glitchy, not escalating yet.” These lines let teammates keep serving while logging signal, and still escalate if a second sensor confirms something authored rather than broken. Pair with Spot Anomalies.

Avoiding bug myth drift

A funny desync can become an urban legend (“the haunted chair”) inside a week. Mark legends with dates and repro status. If nobody can reproduce after two patches, retire the myth so it stops wasting scan time. Your binder should be ruthless about dead bugs.

Severity labels for bug binders

Use cosmetic, gameplay annoyance, run-killer, and data-loss labels. Run-killers get pinned; cosmetics do not steal voice time during yellow status. Labeling stops every jitter from becoming an emergency while still respecting that alpha can hide real threats inside messy frames.