Essential FiveM Scripts for a New Server: A Checklist

Build a new FiveM server in dependency order. Install the database and framework first, then inventory and characters, then dependent systems like vehicles, jobs, police and phones. Test each system's framework, dependencies and edition on staging before adding the next.

Disclosure: RPScripts sells FiveM resources, and the category links below point to its own catalog. They show where to browse a type of resource, not a recommendation of any product. The checklist is based on the framework and Cfx.re documentation linked in each step, reviewed on 13 October 2026. This is a documentation review, not a hands-on test: RPScripts did not install or run the resources named here for this article. Which framework you run decides most answers, so settle that first with FiveM frameworks compared.

Decide three things before you install anything

1. Framework. ESX Legacy, QBCore or Qbox. Every resource you buy has to support the one you pick. See FiveM frameworks compared.
2. Game edition. The Cfx.re Legacy vs Enhanced page lists Mumble voice as deprecated on Enhanced and Asset Escrow as not yet implemented there. A resource that works on Legacy is not proven on Enhanced.
3. Ownership of data. For each system below, know which resource stores the data (inventory items, keys, money, houses) and that only one resource owns it. Two resources writing the same data can cause duplicated or lost items.

The order to install things

The order below is an editorial suggestion, not a Cfx.re rule; maps and phones in particular may need to move earlier if a job or housing resource expects them.

1. Cfx.re license key and a txAdmin recipe for your framework: ESX, QBCore or Qbox.
2. Database and oxmysql, started before everything that uses the database.
3. Framework core and its shared libraries such as ox_lib.
4. Inventory, then characters and spawn.
5. HUD, vehicles, housing, jobs and economy.
6. Police, dispatch and medical, which depend on jobs, inventory and vehicles.
7. Admin tools, voice, phone, loading screen and maps.

Cfx.re's resource manifest reference documents dependency as requiring the named resource to load before the current one. Use each resource's manifest and documentation to confirm its own order. For example, Overextended's ESX page lists oxmysql, ox_lib, es_extended and qtarget before ox_inventory, while the Qbox page says to start ox_inventory immediately after qbx_core.

The checklist, system by system

1. Framework core and recipe

Must do: provide player and character data, jobs, money and the API other resources call. Decide: use the official recipe rather than copying one core folder. Verify: the recipe version, and what it already installs, so you do not add a duplicate.

2. Database and oxmysql

Must do: store everything persistent. Decide: database server and version. Qbox's docs require MariaDB 10.9.0 or newer and say MySQL is not supported; oxmysql's docs strongly recommend MariaDB because many resources written for MySQL 5.7 can break on MySQL 8. Verify: oxmysql starts first and the connection string is set with set mysql_connection_string before resources start (oxmysql docs). Older resources may still call mysql-async; see migrating mysql-async resources. This is infrastructure, so there is no shop category for it.

3. Inventory

Must do: own items, weapons, stashes and metadata. Decide: the inventory every other resource will call. ox_inventory requires oxmysql and ox_lib; its framework setting lists ox, esx, qbx and nd. On ESX it is a complete replacement for the item, inventory and weapon systems, and the ESX page lists standard shops and stashes (esx_shops, esx_weaponshop, esx_policejob) as incompatible. QBCore documents qb-inventory. Verify: every shop, crafting and job script supports your inventory. Catalog: inventory scripts. More: inventory compatibility.

4. Multicharacter and spawn

Must do: character selection, creation and first spawn. ESX ships esx_multicharacter as its default system, with a default of four slots and a /relog command (docs). QBCore documents qb-multicharacter, including a starting-apartment option and a default spawn (docs). Decide: slots and whether players can delete characters. Verify: how the replacement stores character identifiers, and whether it expects your housing and spawn resources. Catalog: multicharacter scripts.

5. HUD

Must do: show status data the framework provides. QBCore's PlayerData includes hunger, thirst and stress in metadata, so HUDs read those. Decide: keep one status source; two needs systems fight over values. Verify: framework, status or needs resource, and fuel and voice integrations in the description. How-to: install and test a HUD.

6. Vehicles, garage, keys and fuel

Must do: sell, store, lock, fuel and recover vehicles. qb-vehiclekeys documents locking, lockpicking and carjacking, but its page lists no exports, so a replacement needs the contract checked in source. Decide: exactly one resource for keys, one for garages, one for fuel. Verify: which resource owns vehicle ownership data, and which exports the key and fuel resources call. Catalog: garages and vehicle scripts.

7. Housing and properties

Must do: ownership, access and storage. ESX documents a Property addon and QBCore documents qb-houses and qb-apartments. Decide: who owns house stashes. ox_inventory includes an optional convertinventory esxproperty step. Verify: the interior or shell type, inventory integration and what happens to ownership when a player is removed. Catalog: housing. More: housing compatibility.

8. Jobs and economy

Must do: pay, grades, duty, society accounts and shops. ESX documents Society, Addon Account, Billing and Banking; QBCore documents qb-management and qb-banking. Decide: one banking and society system. Verify: grade format. Qbox uses numeric job grades while QBCore uses strings, per the conversion guide.

9. Police, dispatch and MDT

Must do: duty, arrests, evidence, records and alerts. qb-policejob documents cuffing, evidence, jail and a basic /911p alert, but its page describes no MDT. Decide: which resource owns dispatch alerts and which owns records. Verify: job names, grade checks and the inventory items they need. Catalog: police scripts. More: police, MDT and dispatch.

10. Medical and EMS

Must do: death state, revive, treatment and hospital flow. ESX has an Ambulance Job addon and QBCore documents qb-ambulancejob. Decide: one death-state source, because HUD, police and inventory read it. QBCore PlayerData has an isdead metadata field. Verify: hospital maps, item names and respawn behavior.

11. Admin tools, permissions and logging

Must do: let staff act, and let nobody else. Cfx.re's server security guidance says to validate on the server and not trust client input. Qbox's server exports page marks its permission exports deprecated as of v1.8.0 in favor of ACE. Decide: staff roles and what is logged. Verify: test an ordinary account is refused every admin command. Any anti-cheat is a separate resource; as an editorial judgment, read what it detects and how it bans before installing. See also server administration.

12. Voice

Must do: proximity voice and radio. Cfx.re's voice documentation describes Mumble-based voice and a new voice implementation on Enhanced that replaces it. Decide: your edition before choosing a voice resource. Verify: edition support and settings. Guide: voice setup.

13. Phone

Must do: contacts, messages, apps and banking links. QBCore stores a phone number in charinfo, so check how a phone derives numbers. Decide: inventory item or no item. Verify: framework, inventory and banking dependencies and whether data is migratable. Catalog: phones. More: phone compatibility.

14. Loading screen

Must do: display during connection. The loadscreen docs say it stays until SHUTDOWN_LOADING_SCREEN is called unless you enable manual shutdown. Verify: it closes on spawn and music respects volume. Guide: create a loading screen.

15. Maps and MLOs

Must do: interiors and locations for jobs. Decide: one map per location to avoid overlaps. Verify: the game edition, collisions with other maps, and which job or housing scripts reference its coordinates. Guides: add an MLO and MLO compatibility.

What to verify before buying any of them

• Exact package and edition. Name, creator, version and whether it covers your framework and inventory.
• Escrow. Cfx.re's Asset Escrow page says purchased assets can be used on any server the buyer owns, an unauthorized server fails with a missing-entitlement message, and developers can exclude files from protection with escrow_ignore. Ask the seller which files you can edit.
• Dependencies. Required libraries, target, inventory and database tables.
• Support and updates. Where to ask and how updates are delivered.
• Documentation. Install steps, config reference and a changelog.

The full list is in the pre-purchase checklist, and the compatibility guide explains product-page badges.

Test every addition on staging

1. Back up the database and the resources folder; confirm you can restore.
2. Add one resource, with its SQL, config and ensure line in dependency order.
3. Read the console. Fix errors before testing features (read txAdmin logs).
4. Test as an ordinary player and as staff: what is allowed, and what must be refused.
5. Relog, then restart the server. Check that items, vehicles, money and ownership persist without duplicating.
6. Watch for events that give items or money from client input, per Cfx.re's security page.
7. Record the version and settings, then promote the change to production.

FAQ

Which scripts does a new FiveM server need first?

The framework recipe, database and oxmysql, then an inventory and character selection. Most other systems build on those, so install and test them before jobs, vehicles, housing, police or phones.

Do I need to buy scripts for a new server?

Not necessarily. Read what your framework's official recipe already deploys, then buy a resource only for a feature you can name, after checking its framework, edition, dependencies and escrow status.

Can I install all the scripts at once?

You can, but fixing failures is harder. Add one system at a time on staging with a backup, so each error has one probable cause.

Do these scripts work on FiveM for GTA V Enhanced?

Not automatically. Check the Legacy vs Enhanced page and each seller's statement, particularly for voice and Asset Escrow.