Recipe, Placement and Interaction Problems

Identify where the problem starts: editing the recipe, publishing it, finding its interaction, opening it or completing a preparation step. Use the matching section below.

Recipe is absent or cannot publish#

Check the restaurant type: Manual supports custom recipes, while Template offers ready presets. Check input/output roles, units, a positive whole-second duration and complete placement.

Use Review draft to open the field needing attention. Finish the owning form before saving again. A custom point can exist in a saved draft while Unplaced still blocks publication.

For an Incompatible preset, follow the repair instructions shown for that recipe. Keep other working copies. See Templates and Maps.

No world interaction appears#

1. Confirm the restaurant is enabled in its published configuration.
2. Verify the exact step/point location was applied, saved and published.
3. Check active staff and current character where required.
4. Check the selected target/TextUI provider is ready.
5. Approach the saved position in the correct routing bucket¹.
6. For model-backed targets, wait for the actual station object to stream and become ready.

If food is visible but its action is missing, check staff access and proximity. The map blip is not a station or menu location. Graph node movement does not move the real point.

Point exists but custom recipe is missing#

Check the point's operation, recipe filter and enabled state. Save and publish its placement. A busy point offers Resume or Collect for its current work instead of starting a different recipe.

One custom physical point holds one production per world instance. Use another correctly placed point for parallel work; a duplicate recipe alone does not add physical capacity.

Model preview fails or food is misplaced#

Confirm the companion is started, model name is valid and the matching asset package is installed. Read the F8 preview error with model/provider context. Changing an object model clears its staged placement, so place the new object before publishing.

Check where that recipe step should touch the counter or hold the food. For an Object custom point, inspect both the station and tool positions. Check rotation as well as height. Use Placement.

Camera clicks do nothing#

Check the product's current stage, required held item, accepted base and operation wait. For example, Hamburger needs a spatula for patties and empty appropriate hands for bread; Taco needs both deposited bases before opening assembly.

If the cursor does not line up with the food, check the saved station position and that product's camera in the assets config. Correct the placement or camera, then restart assets during maintenance.

Work disappears or cannot be collected#

Accepted work can expire by inactivity or be discarded by kitchen-changing publication/deactivation/restart. Personal carries and parked/shared food have different rules. Shared Work explains what can continue.

Check that Restaurant is running, your hands are free, your staff entry is active and you are close enough. Make room in inventory if needed. If the transfer result is unknown, check inventory before trying to collect again. Use Inventory Problems.

For support, include the restaurant, recipe and step, whether you published it, the item in your hands, installed providers and the exact F8/server error. Include a screenshot of the problem and describe what changed in inventory.

Check after correcting placement#

Apply the corrected form, Save draft and Publish, then close the panel and approach that exact station as allowed staff. Confirm the correct interaction appears, complete one preparation and check the inventory output. A fixed kitchen should not require enabling a mobile Everyone policy to admit its staff.