Choose a supported provider1 for your framework, inventory and interactions. A bridge2 connects Restaurant to it. If you use a modified inventory, check its compatibility before opening the server to players.
Built-in paths#
| Service | Supported built-in path |
|---|---|
| Framework | qbx_core, qb-core, es_extended; detection in that order |
| Inventory | ox_inventory or qb-inventory |
| Target | ox_target or qb-target |
| TextUI, notifications and timed progress | Shipped ox_lib-backed adapters |
| Mobile vehicle keys | qbx_vehiclekeys or qb-vehiclekeys |
| Consumption effects | Framework/status-specific adapter behavior |
Start the selected providers before Restaurant. Install the item definitions and images. Do not run another inventory in parallel as an assumed automatic fallback.
Choose and check the installed providers#
Start one framework and one inventory. Built-in framework detection prefers qbx_core, then qb-core, then es_extended. Fixed TextUI uses ox_lib; mobile service still requires a target, and Ice Cream requires supported keys.
Check the selected providers with a complete item transfer, use, storage and denied-access check before opening to players. See Requirements for dependencies.
Custom integration details
Where custom adapters live#
See Custom Bridges.
Inventory integration requirements#
See Custom Bridges.
Progress, targets and notifications#
See Custom Bridges.
Consumption effects#
See Custom Bridges.
Verify a custom provider#
See Custom Bridges.
Fixed-product target requirements#
TextUI covers supported fixed points, but Coffee/Soda stations and Donut baking/decoration use Target. Check that provider even if a different fixed recipe works through TextUI. Mobile service and vehicle keys remain separate feature requirements.
Footnotes
-
An installed framework, inventory or interaction system used by Restaurant. Read the definition. ↩
-
The connection between Restaurant and another resource, such as your inventory. Read the definition. ↩