Accuracy
Can the team make and serve the displayed order without a correction?
Progress by removing uncertainty
A stronger run is not built on one secret item. It is built by making orders, stations, checks, hazards, and recovery predictable as the alpha adds complexity.
Four-stage route
Learn → stabilize → scale → survive
- PHASE 01
Learn
Protect accuracy first
Use the early tutorial shifts to learn where batter, cookware, toppings, dishes, coffee, the camera, and repair points live. Complete one order cleanly before trying to pre-cook a queue.
- PHASE 02
Stabilize
Create fixed stations
In a team, assign a register/check role, a hot-line cook, and a runner/cleaner. Keep urgent hazard work separate from routine prep so the whole line can recover together.
- PHASE 03
Scale
Read the board, not chat memory
As more food and toppings unlock, call out only exceptions—special topping combinations, a customer being checked, or a station that is blocked. The order display carries the routine details.
- PHASE 04
Survive
Treat hazards as team-wide work
A dead appliance or spreading interruption stops the whole line. Pause low-priority prep, solve the blocker, restore sanity, then rebuild the queue from the oldest verified ticket.
Readiness check
Advance when the workflow is stable
Exact shift gates can change. These observable goals stay useful regardless of balance updates.
Coverage
Does every essential station have a clear owner during normal service?
Recovery
Can the team pause for a hazard and resume from the correct ticket?
Awareness
Are customer and camera checks performed even when the queue grows?
Cleanup
Are used dishes cleared as part of the runner’s return route?
Sanity
Does each player know where the staff coffee is and when to step away?
What not to optimize
Do not build around unverified numbers
The current public evidence does not support a stable, complete chart for character prices, rating math, tips, every unlock shift, every recipe, or every anomaly. This guide therefore prioritizes decisions you can verify in the live session: read current descriptions, inspect current prompts, and choose changes that remove a visible bottleneck.