Operation Points and Devices

An independent operation point¹ supplies a physical location to custom recipes. It owns the world placement; a custom recipe owns its method and material amounts. Ready product steps use their own placement path.

1. Open the point list#

In a manual restaurant, select Kitchen > Operation Points. Add a point for the operation you need, or edit an existing row. The location column distinguishes Placed and Unplaced; publication status is separate.

2. Name it and choose eligible recipes#

Use a practical name such as Left cutting board. A point can allow all matching-operation recipes or only selected recipe identities. A Cutting point cannot execute a Boiling recipe just because their names are similar.

Use a recipe filter to dedicate a station to selected recipes. Without a filter, it can serve compatible recipes you publish later. The node view counts configured matching points; it does not tell you whether a point is busy in game.

3. Select Point or Object#

Point mode² adds no permanent station body. Place the configured operation tool directly at its intended working pose, for example the pan where cooking should appear.

Object mode³ requires a valid station model. Place the station first, keep its preview, then place the work/tool pose independently. Back returns to the previous stage. The final acceptance commits the pair together; cancellation/failure keeps the earlier accepted placement.

New points have no default station model. Changing the typed model clears its staged placement and requires placing the new object again. Temporary operation tools are selected by the companion configuration; the recipe or point form does not choose their model.

4. Apply and activate#

Use the point form's Save to apply it and its nested changes to the shared draft. Then Save draft and Publish. New and duplicated points are active automatically. A duplicate begins Unplaced and needs its own location review.

Deleting a point removes that point and its Supply offers, while retaining recipes and materials. Check that recipes still have usable point coverage before publishing.

Attended work versus device work#

Cooking, Boiling, Frying, Baking and Grilling use unattended devices. Load the ingredients through the short loading action, then wait for the recipe's cooking duration. The ingredients are consumed when loading succeeds. Use Collect when the batch is ready.

Other custom operations require attended processing. Pausing/departure retains accepted work and its remaining attended duration under the common continuation rules. Timed progress has different input restrictions from an interactive ingredient camera; follow the visible controls.

One physical point holds one production per routing bucket, including loading checks in progress. Several compatible recipes share that capacity. Create and place separate points when you need parallel work.

What staff should observe#

Approach the published point as active staff. An empty point opens the custom recipe menu with its operation/name and available recipes. Search filters the visible choices. Selecting one closes the menu before the action begins. Busy work hides new-start choices; paused attended work offers its matching resume, and ready device work offers its matching collection.

Device tools remain through readiness and collection. Definite capacity rejection retains a ready batch. Successful collection removes its temporary tool/food scene, while the permanent station remains. See Shared Work for takeover, timeout and uncertainty.

Try the complete custom example#

Use Your First Custom Production to apply these rules to one Supply point, a Cutting recipe, a Cooking recipe and their exact ingredient quantities.