XS-RestaurantCreator
Restaurants, bars, cafes and food trucks your players build, own and run. Nothing ships with it — you build venues for the interiors your server actually has.
Requirements
ox_lib and oxmysql, plus Qbox or QBCore.
Everything else is auto-detected and optional: your inventory, target and doorlock scripts, and a phone for invoices. There is no ESX support — that was cut deliberately rather than half-done.
Installation
- Import
sql/xs_venues.sql. - Drop the folder into your resources and
ensure XS-RestaurantCreatorafterox_libandoxmysql. - Give yourself the
xs.restaurantsace, or add your admin group toConfig.Admin.groups. - Run
/venuebuildand place your first one.
The folder was called XS-Venues before. If you are upgrading, rename it and update your server.cfg.
The creator
A venue is placed in game: the counter, the kitchen, the stash, the tables. Points, not coordinates in a config file.
No venues ship with it, because every server has different interiors. What you build is what exists.
Invoices and supplies
Invoices go through your phone resource when one is detected. Supplies are bought into the venue's stash, so a venue that has not restocked cannot serve.
Before going live
- Nothing ships pre-made. Build at least one venue before players look for one.
- Food items have to exist in your inventory's items list before a venue can serve them.
- Check the doorlock bridge against whatever you actually run before relying on venue doors.
Troubleshooting
/venuebuild does nothing
Missing the xs.restaurants ace, or your group is not in Config.Admin.groups.
Food is made but never appears
The item name in the venue's menu does not match anything in your inventory's items list. Item names are exact.
Invoices never arrive
No supported phone resource was detected. The sale still completes; only the invoice is skipped.
Updating
- Back up the database first.
- Keep a copy of your edited
config.lua. - Check recent commits for SQL changes before replacing files.
- Replace the resource folder, merge your config back, restart.
Support
Bugs and questions go to the Discord. Include your server's console output — the resource prints the reason when it refuses to do something, and that line is usually the whole answer.