Choose what you are trying to fix: start the restaurant, operate the service loop, build around a bottleneck, or coordinate the crew.
New players should complete one customer loop. Waiting or unpaid guests belong in Customer Flow. A stock question belongs in Shop & Restocks. A floor-plan question belongs in Layout. Team duplication belongs in Co-op. Worker timing and price questions stay in the version-sensitive Worker guide.
Every guide includes a quick answer, ordered steps, stuck-state recovery, common mistakes, FAQ, and a useful next action.
Finish the first service loop and reach the current code controls.
Recover waiting, assignment, serving, payment, and shop states.
Use layout and equipment capacity to address the visible bottleneck.
Divide team work and inspect Worker behavior without assumed automation.
The guides use a consistent rule: finish the current visible state, name the queue or handoff that is blocked, change one role or capacity variable, and observe another comparable shift. That keeps a layout, Worker, or shop decision tied to what your restaurant is doing now.
New-game values can change quickly and many exact fields are not available from creator-owned material. The guide desk makes that uncertainty visible instead of turning one video or old list into an evergreen rule.
Start with the beginner guide unless you already have a specific code, customer, shop, layout, Worker, or co-op problem.
Only when a current reliable record supports them. The current guides use visible screen states and keep unstable values unknown.
Read the layout or equipment guide, then enter the current queue counts and optional shop cost into the bottleneck advisor.
