Choose the file for the setting you want to change. Check its activation phase1 to see whether it needs Save draft and Publish, a Restaurant restart or an inventory reload.
Main resource files#
Paths below start inside the delivered 0r-restaurant folder.
| Owner | Purpose | How it takes effect |
|---|---|---|
config/settings.lua | Language, global ACE name and debug switch | Restart main resource |
config/kitchen.lua | Production timeouts, render distances, target icons and interaction sizes | Restart main resource |
config/packaging.lua | Delivery-package capacity and content limits | Restart main resource |
config/panel.lua | Panel command, default key and picker settings | Restart main resource; existing player keybinds can persist |
config/business.lua | Order limits, acceptance deadline, alerts and stock/finance settings | Restart main resource; saved order deadlines remain |
config/map_blips.lua | Restaurant map marker presentation defaults | Restart main resource; the published profile owns its marker location/state |
config/operation_points.lua | Manual animations/icons, menu image paths and native Supply-shop opt-in | Restart main resource |
config/item_usage.lua | Finished-item keys, enable/disable, portions, timing, hunger/thirst and controls | Restart main resource; saved item counters keep their recorded totals |
config/item_usage/visuals/<product>.lua | Finished-item models, animations, attachments, liquids and visual variants | Restart main resource |
config/item_usage/effects.lua | Alcohol, extra numeric effects and effect-provider settings | Restart main resource |
config/item_usage/advanced.lua | Usage preparation limits and calibration controls | Restart main resource |
locales/<language>.json | In-game and panel translations | Restart main resource; literal translation edits need no UI build |
config/products/<product>.lua | Product runtime settings and starter step durations | See Product Defaults for restart versus saved-recipe changes |
config/products/<product>/starter.lua | Advanced starter materials and recipe-step wiring | New recipe copies; existing copies need their supported edit or explicit upgrade and publication |
config/products/<product>/recipes.lua | Coffee/Cocktail drink recipe books | Restart main; unchanged station placement needs no publication |
templates/shared/catalog.lua | Starter product selection and template settings | Creation or an offered explicit upgrade; saved restaurants are not rewritten automatically |
templates/shared/maps/<map>.lua | One map's preset placements | New setup or explicit map-placement selection when adding a ready recipe |
modules/bridge/ | Framework, inventory, interaction and presentation adapters | Restart main resource and required providers safely |
Read the comments in the installed config file for its available choices, units and current defaults.
Companion files#
Paths below start inside 0r-restaurant_assets.
| Owner | Purpose | How it takes effect |
|---|---|---|
config/products/<product>.lua | Product models, station/hand poses, cameras and visual effects | Restart companion; coordinate safe kitchen maintenance |
config/manual.lua | Custom-operation tools, device indicators and effects | Restart companion |
stream/ | Streamed models and textures | Deploy matching package resources and restart safely |
Edit how a finished item looks in the player's hands in the main resource's config/item_usage/visuals/ file selected by its presentation name. Edit production tools, such as scoops and knives, in the assets resource's product config. Product keys use underscores where present: french_fries and icecream, for example.
Editor-owned data#
Restaurant names, staff, materials, recipes, operation points, menu locations and placement are edited in the panel. Apply the form, Save draft and Publish. Normal panel edits do not require restarting the resource.
Sales prices and Accept new orders use Save sale settings and affect future orders immediately after success. They do not use recipe publication. Layout-only node view edits need Save draft but do not change gameplay.
Before changing a setting#
Back up the edited file and relevant database when needed. Read the setting's comments, keep its type and unit, then restart the resource listed in the table. Check the changed feature in game. Changing a default does not update an existing saved restaurant automatically.
Continue with General Settings, Product Defaults, Usage Profiles or Providers. Read Safe Updates before template/schema maintenance.
Business or developer settings#
For exact startup keys, see General Settings, Business Settings and Item Usage. For an unsupported provider, use Custom Bridges.
Footnotes
-
The action required for an edited setting to take effect. Read the definition. ↩