Assign front-of-house, kitchen, serving, collection, and shop observation roles according to the actual party size and visible queue pressure.
Start with one front-of-house owner and one kitchen owner. Add serving, collection, and restock observation only as the party grows, then move help toward the larger queue.
Each step names the visible decision to make. Exact labels, prices, and timings remain tied to the interface in your current server.
One person watches both visible queues and calls for help when seating or kitchen pressure changes.
Assign one player to usable seating, customer assignment, and spotting a blocked customer state.
Assign one player to active stoves, completed dishes, and the cooking-to-serving handoff.
Add serving, collection, and restock observation only when enough players are present. Rebalance from the queue, not from a fixed six-player diagram.
Reset at the next quiet moment and name one owner for each visible queue.
Combine seat/serve and cook/collect responsibilities, then move help toward the larger pressure.
Do not assume it replaces a player until its current visible task is established.
Keep one front-of-house owner even during a kitchen spike.
A dated cap is not a required party size; scale the role recipe to who is present.
The guide claims coordination value only.
Co-op changes how quickly a team can react, but it does not remove the need to see the whole service loop. Clear ownership prevents two players from solving the same small problem while another queue grows unattended.
A dated metadata snapshot reported up to six, while the official description confirms only that the experience is co-op.
Start with front-of-house and kitchen ownership; add serving, collection, and restock observation as the party grows.
Use paired roles: one handles seating and serving while the other handles cooking and collection, then move help toward the larger queue.
No reliable multiplier was found, so this guide claims coordination benefits only.
