Installation and Permission Problems

First identify whether the resource failed to start, the panel could not load, or a specific action was denied. These are different failure points.

Resource does not become ready#

Check the first server-console error in dependency order: database connection/version, framework, inventory, ox_lib, 0r_lib, companion and main resource. Preserve the complete error and resource version.

Keep folder names 0r-restaurant_assets and 0r-restaurant. Start the assets resource first. A renamed folder can break a dependency or inventory export even if some UI files still load.

For migration errors, use Database Startup. Do not delete existing tables to obtain a clean start.

Command works for nobody#

Use the configured chat command independently from the keybind. The delivered command is /restaurant and the default key is F7. Check config/panel.lua and the player's FiveM keybind overrides.

If the command runs but access is denied, finish character selection and check that character's permissions. Read any framework connection error in the console.

Administrator cannot create/edit#

Verify the configured ace permission¹ name matches the actual grant and that the player belongs to its principal/group. Reload the file the server truly executes. Test both the group and the player's exact principal, following Permissions.

txAdmin status alone does not grant Restaurant management access. Use the ACE grant described in the permissions guide.

Owner, manager or employee cannot see an action#

Check the current restaurant and persistent framework character. An owner can configure that restaurant. Manager/employee roles can operate permitted business/kitchen features without receiving owner-level configuration, pricing or banking.

Save and publish staff changes before testing. For physical kitchen and storage work, add an active staff entry even if the player is a global administrator.

Panel opens but the world target is missing#

Confirm enabled publication, placed current point, active staff when needed and the selected Target/TextUI provider. Model-backed interactions need the object streamed and ready. A Menu Location is separate from the public blip.

For mobile service, check targets, ownership of the cart or vehicle, and vehicle keys where needed. Use Kitchen Problems for these checks.

White, empty or stuck panel#

Read the first F8 and server-console errors. Check that all Restaurant files are installed and both resources started successfully. Fix the reported startup or language-file problem, then reopen the panel.

When reporting the issue, include the visible message, first F8/server error, versions, selected providers, current character role and whether the command or only the key failed. Exclude credentials and other sensitive data from shared logs.

Check the result of the fix#

After correcting startup or ACE, join with the intended fully loaded character and open the command as an allowed administrator. If the panel opens but fixed cooking or Storage is denied, check active published membership and proximity next; the ACE grant alone does not provide that physical staff access.