This example creates Copper Spoon, a Template restaurant using the Taco preset. You will place all three Taco steps, publish the restaurant, make one taco and use it from inventory. Customer ordering is an optional next task.
Before you begin#
- Complete Installation, inventory items and images and administrator ACE access. This example follows the Qbox + Ox start order. Other supported providers use the same panel steps.
- Start 0r-restaurant_assets, then 0r-restaurant. Join with a fully loaded framework character and leave inventory capacity for the output.
- Use a suitable counter area you can access in game. This example uses the world picker, with no map preset. No particular MLO coordinates are required.
- Keep the delivered enabled
taco_productconsumption profile in0r-restaurant/config/item_usage.lua. If your operator changed it, restore or configure the appropriate Taco profile before the consumption check.
1. Create Copper Spoon#
Open /restaurant or the default F7 key and click + beside the restaurant list. Enter:
| Field | Value for this example | Reason |
|---|---|---|
| Restaurant Name | Copper Spoon | A readable test name |
| Interaction type | TextUI | Fixed points use the installed ox_lib prompt; Target is also supported with a working target provider |
| Restaurant Template | Taco | Seeds the ready Taco recipe and its output material |
| Map preset | None / unset | You will place the three steps yourself |
| Map blip | Off | Optional map marker, unnecessary for production |
| Management Point | Leave unset | Optional physical management access; the authorized command remains available |
| Packaging Point | Leave unset | Add later for Storage and packaging |
| Menu Locations | Leave empty | Add later for customer ordering and pickup |
Save the creation form. Restaurant creation does not automatically assign an Owner or make the creator active staff. Keep the restaurant enabled for the final gameplay check.
Creation form layout. Use Copper Spoon, Taco and the choices above; the screenshot is not a completed Taco installation.
2. Hire the test character#
Select Copper Spoon, open Staff Roster, then Hire. In Hire Employee, choose your online player from Nearby Employee / Choose an online player and select Owner. Confirm the hire and keep the resulting membership active.
If your player is not in the selector, Custom Source ID accepts the online player's numeric server ID shown by your server's player list. It is not a character ID or license string. Restaurant resolves the player's loaded framework character and saves that character identity. Verify the resulting employee row before continuing. See Staff Members and Roles.
Your ACE grant allows configuration; active published staff membership allows fixed kitchen work. Test both with the same character.
3. Place all three Taco steps#
Open Kitchen > Recipes, select the Taco recipe and review each step. Keep its delivered ingredients and output. Use the world picker to place these steps at reachable locations:
| Step | Placement for this example | What to check |
|---|---|---|
| Take beef, chicken or tortilla | Place the recommended protein supply object | The supply is visible and reachable from the player's standing position |
| Cook protein and warm tortilla | Choose New countertop griddle, then place its recommended griddle on a suitable surface | The griddle sits at the correct height, with space for its cooking interaction |
| Prepare and collect taco | Place the recommended Taco preparation station | The assembly surface and camera area are clear |
The cooking step also supports an existing cooking surface. That alternative needs careful surface placement; use the new griddle for this first example. Do not enter a model or coordinate copied from another map.
Accept each placement in the picker and apply the recipe form. All three steps need saved locations; placing only the final assembly station is insufficient. A map blip does not place a cooking point. See Taco Setup and World Placement.
4. Save and publish the complete setup#
- Confirm Copper Spoon and its Taco recipe are enabled and the staff row is active.
- Apply any open recipe, placement or roster form first.
- Click Save draft in the header. This persists the draft1; it does not activate the kitchen.
- Review any validation error and correct its named field. Reapply and save the corrected form.
- Click Publish. Check that the header reports Published and The latest saved changes are published.
Publication2 activates the complete saved setup, including staff and locations. For this production-only example, Management, Packaging and Menu locations can remain unset. If you added any Menu location, finish placing it or remove that incomplete entry before publication.
5. Make and collect one taco#
Close the panel and approach the placed supply as the active staff character. Follow Taco Preparation: take beef, cook it, warm a tortilla, then assemble and fold one taco at the preparation station. The delivered cooking step is 15 seconds and tortilla warming is 5 seconds. These are separate actions; visiting the assembly station does not cook the protein automatically.
Collect the taco. Check that inventory receives one finished Taco, logical item taco_product, with the beef appearance and saved contents. Ready Taco preparation supplies its configured ingredients; it does not consume the custom Tomato packets used in the other tutorial.
6. Check eating and remaining portions#
Use the finished product from inventory. With the delivered enabled taco_product profile, Restaurant holds the Taco and offers its consumption controls. Complete a bite, put it away and check that remaining portions are retained. Follow Eating and Drinking for E/X controls and expected removal after the last portion.
If inventory receives the item but using it fails, check the selected usage profile and inventory callback in Inventory Problems.
7. Add customer ordering when needed#
Place a Packaging Point and a Menu Location, then save and publish those location changes. Continue through the complete order verification route: enable a price, deposit finished stock, checkout as a customer, accept, pack exact contents, approve Ready and collect.
Footnotes
-
Configuration saved on the server but not yet active in game. Read the definition. ↩
-
Activate the latest saved restaurant configuration after validation. Read the definition. ↩