Choose the file or panel setting for the change you want. A recipe's ingredients, production camera, inventory image and eating animation have separate settings.
Decide what you are changing#
| Intended result | Owner |
|---|---|
| Change one restaurant's supported recipe duration/placement | Panel recipe draft, then Save draft and Publish |
| Change defaults for future recipe copies | 0r-restaurant/config/products/<product>.lua |
| Change starter composition or supported explicit upgrade | config/products/<product>/starter.lua and templates/shared/catalog.lua |
| Move production camera, station food or carried equipment | 0r-restaurant_assets/config/products/<product>.lua |
| Change how finished food is held/eaten/drunk | 0r-restaurant/config/item_usage/visuals/<product>.lua |
| Change inventory artwork | Installed PNG plus the Material's optional Inventory image |
Changing a file default affects new recipe copies. For an existing restaurant, edit its saved recipe or use the supported upgrade in Templates and Maps.
Editing supported product settings#
Use config/products/<product>.lua for normal product settings. Its starterDurations table sets future recipe-step times in seconds, indexed by recipe key and then step key. The separate starter.lua holds advanced materials and recipe wiring; Coffee/Cocktail recipes.lua holds the drink book. Keep action names unchanged. Adding or renaming an action does not create a new preparation step.
Follow the release's upgrade instructions when a product update changes existing recipes. Review those recipes and their placement before publishing.
Recipe books and saved defaults#
Edit config/products/coffee/recipes.lua or config/products/cocktail/recipes.lua, then restart the main resource. Existing stations can use the new book without a template upgrade1 or republishing unchanged placement.
For other product changes, check whether you need to edit and publish the saved recipe. The Coffee/Cocktail restart rule does not apply to all settings.
Calibrate a production camera#
Open the product's config in 0r-restaurant_assets/config/products/. Adjust the preparation camera's position, rotation or field of view using that file's fields. Restart assets during maintenance, then open the placed station to check the view.
Hamburger and Taco have separate cameras. Aim the selected product's camera at its working surface so players can select and place ingredients.
Place contact frames correctly#
Use the picker preview to check where the station rests on the counter and where food is placed. Correct the station's height and rotation before adjusting its camera or ingredients. Follow the product's placement guide.
For custom points, the permanent station and temporary tool are separate. Tool models/effects belong to companion config/manual.lua. A recipe input cannot select an arbitrary device tool model.
Verify presentation without granting products#
Use Diagnostics to preview models or adjust how a finished item is held. Replace the named config/item_usage/visuals/<product>.lua file with its exported visual definition; save production cameras and tools in the assets resource's product config.
After restarting the edited resource, open the affected station and check the camera or tool position. For finished-item changes, use the item from inventory and check how the character holds and consumes it.
Example setting changes#
| Goal | Exact owner / key | Default / example | Apply and verify |
|---|---|---|---|
| Change future Taco protein cooking time | Main: config/products/taco.lua, Config.products.taco.starterDurations.classic_taco.cook_protein | 15 seconds; example 20 | Restart main; new copies use the new time. Edit and publish an existing recipe to change its saved duration |
| Change Taco warming time | Main: config/products/taco.lua, Config.products.taco.operationDurations.warm_tortilla | 5 seconds; example 6 | Restart main and review the saved recipe/upgrade requirements; test warming on the published copy |
| Change Sandwich parking | Main: config/products/sandwich.lua, Config.products.sandwich.parkedCapacity | 4; example 3 | Restart main; update existing saved recipes through their supported upgrade |
| Change Ice Cream model | Main: config/products/icecream.lua, Config.products.icecream.vehicle.model | 'taco'; use an actually installed compatible vehicle only | Restart main safely; spawn a new vehicle and check both serving sides, target positions and keys. Changing the vehicle model alone needs no recipe publication |
| Move the Taco preparation camera | Assets: config/products/taco.lua, Config.visuals.templates.taco.cameras.preparation.fov | 45 degrees; example 42 | Restart assets during maintenance; check the existing published station in game |
| Add a Coffee book entry | Main: config/products/coffee/recipes.lua, Config.products.coffee.recipes | Table of delivered recipes; copy a valid entry with its own unique id | Restart main; open the book at the existing station and complete the new drink |
Use the exact model name declared in the matching installed config and streamed export. Do not derive a model name from the YTYP filename or replace a custom model with a similarly named GTA prop. After a model change, check saved station selections as explained in Safe Updates.
Camera changes affect appearance. Recipe defaults affect new copies; existing recipes need their own edit or supported upgrade. Use the fields provided by the product and follow Safe Updates.
Footnotes
-
Updating a saved recipe with the latest preset definition. Read the definition. ↩