Installation and Start Order

Install both Restaurant resources together. The companion owns the models and visual presentation; the main resource owns the restaurant systems.

1. Put the folders in your server#

Extract the delivered package into your server resources directory:

resources/
  [0resmon]/
    0r-restaurant_assets/
    0r-restaurant/

Keep these two folder names unchanged. Export names, dependencies and inventory-use registrations refer to them. Install the complete delivered package rather than copying only a UI folder.

2. Install dependencies and configure the database#

Configure the connection used by oxmysql and confirm that it connects successfully. Install oxmysql 2.12.0 or newer. Install 0r_lib from the supplied package and keep its folder name unchanged. Follow the start order below.

On a clean database, Restaurant runs its schema setup after database readiness. Leave the startup service in control. Do not import unrelated legacy SQL, delete existing tables or change migration¹ history to make an error disappear. For existing data, read Safe Updates first.

3. Set the start order#

This example uses Qbox and Ox. Replace each provider² with the one your server actually uses:

ensure ox_lib
ensure oxmysql
ensure qbx_core
ensure 0r_lib
ensure ox_inventory
ensure ox_target
# Start the required map/MLO and vehicle-key resources here.
ensure 0r-restaurant_assets
ensure 0r-restaurant

Use qb-core or es_extended in place of qbx_core when appropriate. Use qb-inventory or qb-target in place of their Ox equivalent when appropriate. Do not add all alternatives to the start list.

The assets resource must be running before the main resource. If a dependency fails, fix its first console error before testing Restaurant again.

4. Install inventory definitions and images#

Follow Inventory Items and Images. This step is required even when you can already open the management panel. Three shared provider items represent Restaurant ingredients, products and delivery bags; metadata distinguishes their actual contents.

Reload the inventory definitions through the provider's normal restart procedure, then start the companion and main Restaurant resources in that order. Schedule restarts when temporary kitchen work can safely be lost.

5. Grant access and open the panel#

Set the ACE grant in Admin Access and Permissions. Join the server with a fully loaded framework character. The default panel command is /restaurant; the default key is F7. Existing player keybind overrides can keep a different key after a config change.

6. Verify the installation#

1. Confirm both Restaurant resources and all required providers are started.
2. Check the server console for database, migration or dependency errors.
3. Open the panel as an authorized administrator.
4. Create one test restaurant, add active staff, configure and publish a complete recipe.
5. Produce a real item and verify its name, metadata, image and inventory use.
6. If using orders, test one checkout through pickup with a customer character.

Continue with Your First Working Restaurant. If startup remains closed, use Database Errors or Access Problems.