Public Anomaly Cafe videos use conflicting labels such as Day 1–6, seven days, and Day 1–10. That means a permanent event-by-event script is not reliable for every alpha build. This walkthrough gives each day a concrete practice goal while the live objective display decides the actual task, unlock, and completion condition. If your server skips, repeats, or renames a day, keep the skill goal and follow the current prompt.
Days 1–2: learn accurate service
On Day 1, orient yourself before increasing the queue. Find customer intake, the preparation route, delivery area, and the tutorial’s current interaction points. Complete one request from start to finish. Read the base and all additions, follow the station prompts, deliver to the intended customer, and clear the work area. The day is productive when you can repeat that route without asking where to go.
On Day 2, reduce errors. Accept one ticket at a time and diagnose every failed delivery before retrying. Check base item, preparation completion, additions, and customer match. In co-op, assign one intake owner so two players do not prepare the same request. Start a quick room scan after each delivery.
Days 3–4: add maintenance and observation
On Day 3, learn how the current build signals upkeep. Do not assume a fixed timer or complete maintenance list. When a visible task appears, decide whether to finish the current one-step action or pause safely, then clear the blocker. Note which routes and stations become difficult when upkeep is ignored.
On Day 4, establish a normal-room baseline. Pick a few references: customer behavior near intake, furniture placement, lighting, ambient sound, and any observation tool the tutorial exposes. Scan those references during normal transitions. The goal is not to call an anomaly; it is to know what “unchanged” looks like in this server.
Days 5–6: practice interruption recovery
On Day 5, rehearse a safe pause. When a credible abnormal cue or game warning appears, stop taking new multi-step work, communicate location plus cue, and follow current feedback. Afterward, list unfinished tickets, clear ambiguous items, handle visible damage or upkeep, and restart from the oldest confirmed request.
On Day 6, formalize team roles. Use intake/check, preparation, runner/recovery, and watcher/floater as a starting split. In a smaller group, combine adjacent jobs. Rotate after a calm period so everyone understands the whole route, but never rotate during an active exception without a clear handoff.
Days 7–8: improve route quality
On Day 7, shorten movement without sacrificing checks. Carry only what the active request needs, face the next station before leaving the current one, and keep customer and emergency paths free of abandoned items. Use the Map guide to name functional zones rather than relying on a screenshot that may become outdated.
On Day 8, improve anomaly decisions. Separate a soft cue from a confirmed event. A single odd animation may be lag; a repeated mismatch, observation-tool difference, or explicit game warning deserves escalation. The spotting guide gives a compare-confirm-communicate routine that avoids both panic calls and dangerous dismissal.
Days 9–10: run a clean long shift
On Day 9, aim for stability across several service and interruption cycles. Track active tickets, ownership, maintenance blockers, and the team’s safe regroup point. Do not chase speed records. A clean day ends with the queue understood and the group able to explain how it recovered.
On Day 10, follow the live objectives exactly and preserve the state that led to any completion or story scene. Avoid changing servers mid-sequence unless the game requires it. If an ending or final scene appears, note the build date, party state, visible objective, and last completed action. Do not assume that a recorded result proves the only ending or a universal ten-day requirement.
Day-by-day quick index
If your day does not match
First confirm that you joined the official place and a current server. Then read the objective text and tutorial again. A patch may have reordered tasks, a party member may own the next interaction, or a previous objective may remain unfinished. Return to the last confirmed task instead of copying a video input whose context you cannot see.
If progression still appears stuck, regroup, clear abandoned cafe work, check visible maintenance, and ask each player whether they hold an objective item or prompt. Rejoining is a last resort because it can discard useful state. Record reproducible alpha bugs for the creator without turning the bug into a permanent walkthrough step.
What this route does not assume
It does not assume that ten days are fixed, that every day has one scripted event, that a specific recipe appears on a specific day, or that one completion scene is the only ending. It gives you a useful progression plan despite those unknowns. For story results, continue to the spoiler-marked Ending Guide; for group roles, use the Co-op Guide.