Sandwich uses a personal cart with bread choices, filling trays, sauces and parking positions. It is a cold assembly workflow, so there is no grill job or cooking timer to complete.
Set up and open the cart#
Add the Sandwich ready recipe1. Configure its mobile access policy and spawn/return locations, place them, save and publish. Mobile targets require a working target provider2. Prepare food on your own cart.
The cart's current operator view presents the stocked assembly area. The selected recipe supplies its allowed ingredients without consuming ordinary ingredient inventory. Names, supported choices and limits belong to its installed product definition.
Settings and dependencies#
This preset belongs to a Template restaurant. Configure the Staff/Everyone policy and all spawn/return points. Mobile service requires a target provider.
| Change | Location | Apply the change |
|---|---|---|
| Labels, supported recipe fields and placement | Kitchen > Recipes | Apply the form, Save draft, then Publish |
| Supported future-product defaults | 0r-restaurant/config/products/sandwich.lua | Restart main; review existing saved copies before any supported upgrade |
| Models, camera and equipment positions | 0r-restaurant_assets/config/products/sandwich.lua | Restart assets during maintenance |
| Portions and hunger/thirst | 0r-restaurant/config/item_usage.lua | Restart main; existing item details remain saved |
| Holding, eating and drinking appearance | 0r-restaurant/config/item_usage/visuals/sandwich.lua | Restart main; keep the item's presentation name matched |
| Alcohol and additional effects | 0r-restaurant/config/item_usage/effects.lua | Restart main; saved ingredient details remain unchanged |
Ready preparation supplies its configured ingredients rather than consuming ordinary custom-material packets. Check Product Defaults before editing files.
Capacity, timing and cleanup#
The delivered ready definition sets parkedCapacity to four. Parked Sandwiches remain on their owner's cart; a full parking area retains the active preparation when leaving. Keep the allowed bread and filling choices consistent with the saved recipe. Mobile access and cart removal use Mobile Setup.
Change supported saved durations through the recipe form, then Save draft and Publish. For source defaults that are copied into a recipe, editing the file and restarting does not rewrite existing copies. Use a supported explicit upgrade when required, review its changed placement and publish it. Before planned restart or kitchen-changing publication, finish temporary work; see Shared Work.
Verify the installation#
- Save and publish a complete enabled recipe.
- Join with a character allowed to use it under the selected mobile access policy.
- Complete one preparation using Sandwich Preparation.
- Check the finished item, its quantity, image and saved contents in inventory. Use a configured consumption profile to check eating or drinking.
For missing stations or placement problems, use Kitchen Problems. For a failed transfer, keep the error and check Inventory Problems. Review Shared Work before a restart or kitchen change.
Detailed preparation steps
1. Choose the bread#
Continue at 1. Choose the bread.
2. Add fillings and sauce#
Continue at 2. Add fillings and sauce.
3. Close with matching bread#
Continue at 3. Close with matching bread.
Understand RMB undo#
Continue at Understand RMB undo.
Park, resume and move#
Continue at Park, resume and move.
Check the result#
Continue at Check the result.
Footnotes
-
A preset recipe with its own preparation steps and an editable copy for your restaurant. Read the definition. ↩
-
An installed framework, inventory or interaction system used by Restaurant. Read the definition. ↩