Database & Items
How myRP.build sets up and manages your database automatically, and what you still handle yourself for ox_inventory items.
When a feature needs to remember things — owned vehicles, player-owned shops, balances — it needs database tables. myRP.build sets up and manages the database for you, so there's nothing to provision, connect, or configure.
The database is set up for you
You don't bring a database or wire up a connection string. myRP.build provisions the database as part of setting up your server, and keeps it wired to the ox stack — oxmysql and the rest — automatically.
SQL is applied for you
When a generated resource includes a schema (e.g. sql/install.sql), myRP.build runs it for you as part of generation. FiveM and oxmysql do not execute install.sql automatically, so the app does it — the tables exist by the time the resource loads. No manual import step.
oxmysql only. Generated resources never use
mysql-async.
ox resources are wired up too
myRP.build installs the ox stack for you, and the ox resources that ship their own schema (for example ox_inventory) have their tables applied as part of that install — no separate import to run.
Items are not auto-registered
If a feature uses a custom inventory item — a lockpick, a repair kit, a burger — the generated code will reference that item, but myRP.build does not add it to ox_inventory's item data for you. You register custom items yourself, in ox_inventory's items file, the way you would for any ox resource.
When you write a prompt that relies on an item, name the item explicitly so the generated code references the right one — then make sure that item exists in ox_inventory.
If a resource errors on a missing item or table, see Troubleshooting.