Setting up a new QBCore server means choosing from thousands of resources — overwhelming when you're starting. This guide cuts it down to the must-have categories every QBCore server needs, in the order to set them up. Get these right and you have a solid foundation.
The absolute core (set up first)
qb-core — The framework itself. Everything depends on it. This is your starting point.
oxmysql — The database layer. Nearly everything stores data through it. Install early, load first.
ox_lib — The shared library modern resources depend on. A near-universal dependency.
These three are non-negotiable foundations.
Core systems (set up next)
An inventory — ox_inventory is the modern standard, giving you slot-based inventory, shops, stashes, and strong security. Get this right early since so much hooks into it.
A target system — ox_target for clean eye/cursor interaction. Modern scripts expect it.
Character creation & spawn — A multicharacter system and appearance/clothing script. This is what new players first experience.
Banking — ATMs, transfers, cash vs bank. Underpins your whole economy.
Jobs and economy
Core jobs — Police, EMS, mechanic, and civilian jobs give your server structure and an economy.
A multijob system — Lets players hold multiple jobs and switch cleanly, with duty toggling. One of the highest-impact additions for player flexibility.
A balanced economy — Not a script but a discipline: income vs money sinks, tuned over time.
Gameplay and identity
Once the foundation is solid, add what makes *your* server unique:
- Robberies, heists, and crime systems
- Drug systems
- Vehicle shops and garages
- Housing/property
- Safe zones for spawn and hospitals
- Whatever activities define your server
Add these gradually, testing performance as you go.
Admin and security
txAdmin — Your management panel. You already have it; use it.
An admin menu — For managing players and situations in-game.
Anti-cheat — Protect your server before going public.
Don't launch publicly without these.
The order matters
Set these up roughly in the order above — foundations first, then core systems, then jobs, then gameplay, then security before launch. Adding gameplay scripts before your inventory works, or launching before securing, causes avoidable pain. And add one at a time, testing each.
Quality over quantity, always
You don't need hundreds of resources — you need the right ones, well-built. A lean server of quality scripts beats a bloated one every time. For the core and identity-defining systems, choose resources that are optimized, secure, and supported.
Solid QBCore resources
At Viper Development, we build QBCore-compatible (and ESX) resources like Viper Multi-Job and Viper Safe-Zone — optimized, server-validated, and supported, ideal for the core systems of a new QBCore server.