Roblox currently verifies an alpha experience set at Emma's Cafe where players can team up, serve customers, maintain the cafe, and survive anomalies. Creator media shows service and horror scenes, while current players discuss cooking, cameras, numbered days, solo pressure, and progression. Those reports do not yet establish permanent rules, a complete anomaly list, or a code system.
Use four evidence states for every claim
Verified means the current official Roblox record states the fact directly. Promotional means creator-supplied icon or media shows a scene without proving every live rule behind it. Reported means a dated exact-game video or community discussion exposes a player experience or question that still needs replay. Unknown means the checked sources cannot answer safely. These labels matter because Anomaly Cafe is in alpha and current attention is moving quickly. Several people repeating the same comparison or strategy does not make it first-party fact. When a detail changes state, preserve the checked date, exact universe and place, and the source that caused the change.
Verified identity and current official record
The exact experience is universe 10439568447 with root place 121781732399469, published by the Roblox group Anomaly Cafe. Roblox records creation on July 3, 2026 and a current official update on August 15, 2026 at the checked time. The creator warns that the game is alpha and asks players to expect bugs. The official record also displayed current players, visits, and favorites, but those counters are time-sensitive observations, not mechanics or proof of future growth. This package does not claim the game is made by, affiliated with, or officially connected to another anomaly-themed experience; community comparisons cannot establish that relationship.
Verified premise: service, maintenance, teamwork, and anomalies
The current creator description names Emma's Cafe and says players can team up with friends, serve hungry customers, maintain the cafe, and survive anomalies that appear unexpectedly. It also promotes original characters, anomalies, and custom music. This establishes a service-and-survival loop and a social option. It does not publish the full service workflow, required ingredients, workstation controls, maintenance meter, player limit, role system, anomaly schedule, failure condition, win state, reward table, or story ending. A useful reference keeps the verified verbs intact while leaving the missing operational details to current in-game prompts and replayable evidence.
Promotional layer: staff, customers, camera framing, and horror contrast
The checked creator media set contains six images plus the experience icon. The icon shows an orange cafe character holding a plated dessert. Other images show illustrated staff behind a counter, a chaotic service scene, an in-game cafe viewed through a recording overlay, a table scene, an ominous customer at the counter, and a chase-styled image with an order display. These assets help players recognize the setting and the intended contrast between cheerful service and horror. They do not certify a camera mechanic, order number rule, anomaly identity, recipe, character name, chase trigger, or required response. Promotional scenes are clues to inspect, not walkthrough steps.
Reported questions: cooking, cameras, solo pressure, and numbered days
Current exact-name videos include solo play, a long play, cafe work, and an attempt to reach later numbered days. August community discussions separately talk about cooking, camera use, stressful solo sessions, customers, anomalies, long runs, and a code obtained during progression. These are valuable demand signals because they show what players want explained. They remain reported rather than verified here: the checked material does not bind each observation to a stable version, show a complete before-and-after sequence, or prove that every server and account behaves the same way. Use them to choose the next replay task, not to fill tables or promise an ending.
Held layer: anomaly lists, progression, codes, rewards, and rankings
A complete anomaly roster is held because no current creator-owned source or replay package establishes every entity, tell, response, and version. Numbered-day milestones and a win condition are held because current discussions expose uncertainty rather than a verified ending. Codes are held because one community use of the word code does not prove a reward code, redemption box, reward, or expiration state. Tools and tier lists are held because there is no stable formula, event probability, full roster, comparison model, or limitation basis. Refresh this ledger after an official semantic update or a reproducible current capture; do not fill unknown sections with rules borrowed from a neighboring game.
What this guide does not assume
This reference distinguishes current Roblox facts, creator promotional media, dated exact-game videos and discussions, and unknowns. It does not certify affiliation with another game, recipes, controls, anomaly identities or tells, camera rules, day schedules, win conditions, story completion, code strings, redemption steps, rewards, a complete character roster, rankings, or probabilities.
Refresh trigger: Refresh when Roblox changes the title, alpha notice, description, creator identity, icon, media set, or when a replayable current capture resolves a listed service, anomaly, progression, code, or reward unknown.