Getting your QBCore server settings right is the difference between a smooth, enjoyable experience and a laggy, exploit-ridden mess. QBCore offers extensive configuration options that control everything from economy balance to player limits, resource loading, and server behavior. This guide walks you through the most important settings and how to optimize them for your server.

Server.cfg Essentials

Your server.cfg is the master configuration file for your FiveM server. Here are the critical settings every QBCore server owner should configure:

Player Slots: Set your maximum player count with sv_maxclients. For QBCore servers, 64 players is the standard starting point. You can go higher (128 or even 200+), but performance depends heavily on your hardware and how well your resources are optimized. Start conservative and increase as you verify stability.

Server Name and Tags: Use sv_hostname for your server name and tags to help players find your server in the server list. Include relevant keywords like your framework, language, and server type.

OneSync: Enable OneSync with set onesync on. OneSync is essential for modern QBCore servers — it handles entity synchronization and enables higher player counts. Without it, you are limited to 32 players and will experience worse synchronization.

License and Steam API Key: Configure your Cfx.re license key and Steam Web API key for proper player authentication. The Steam API key enables Steam-based identification alongside FiveM licensing.

Resource Load Order

Resource load order is one of the most common sources of errors on QBCore servers. Loading resources in the wrong order causes dependency failures, missing functions, and mysterious errors. Follow this order:

• 1. Database driver — oxmysql or mysql-async must load first
• 2. Core libraries — ox_lib, if you use it, loads right after the database
• 3. QBCore framework — qb-core is the foundation everything else depends on
• 4. UI and interaction — qb-target, qb-menu, qb-input
• 5. Inventory — qb-inventory or ox_inventory
• 6. Phone — qb-phone or qs-smartphone
• 7. Job scripts — qb-policejob, qb-ambulancejob, qb-mechanicjob, etc.
• 8. Vehicle scripts — qb-garages, qb-fuel, qb-vehiclekeys
• 9. Housing and property — qb-houses or similar
• 10. Miscellaneous — HUDs, clothing, cosmetic resources
• 11. Maps and MLOs — custom interiors load last

If you experience errors on server start, check the console output for dependency warnings. Nine times out of ten, it is a load order issue.

Economy Balancing

A balanced economy is crucial for long-term server health. QBCore economy settings are primarily configured in qb-core/shared/config.lua and individual job configs:

Starting cash: Give new players enough to get started but not so much that money feels meaningless. A common range is $5,000-$15,000 starting cash depending on your server economy scale.

Job salaries: Configure pay rates in each job script config. Balance salaries so that legal jobs provide a viable income while illegal activities offer higher risk-reward. A good rule of thumb: legal jobs should pay enough for basic needs (food, fuel, repairs), while illegal activities fund luxury items.

Item prices: Adjust shop prices in your inventory or shop scripts. Food, drinks, and basic supplies should be affordable. Weapons, vehicles, and luxury items should require significant effort to obtain.

Inflation control: Monitor your server economy regularly. If players accumulate too much money, introduce money sinks — vehicle maintenance costs, property taxes, fines, and business operating costs help drain excess currency.

txAdmin Configuration

Most QBCore servers use txAdmin for server management. Key txAdmin settings to configure:

• Scheduled restarts — Set automatic restarts every 6-8 hours to clear memory leaks and maintain performance. Configure restart warnings so players can save their progress.
• Player manager — Set up ban and kick permissions for your staff team. txAdmin provides a web-based interface for player management without needing in-game access.
• Server monitor — Configure crash detection and automatic restart. txAdmin will detect when your server stops responding and restart it automatically.
• Backups — Enable txAdmin backups of your txData folder. This saves your player data, bans, and server configuration.
• Discord integration — Connect txAdmin to your Discord for player reports, join/leave notifications, and staff alerts.

Common Issues and Fixes

Issue	Cause	Fix
Players stuck on loading screen	Resource error during load	Check server console for errors, fix the failing resource
Inventory not opening	Inventory resource not started or wrong version	Verify inventory is ensured in server.cfg and matches your QB version
Jobs not working	Load order issue or missing dependency	Ensure qb-core loads before job scripts, check for missing ox_lib
Database connection failed	Wrong connection string or MySQL not running	Verify MySQL is running and connection string in server.cfg is correct
Target/interaction not working	qb-target loaded before qb-core	Fix resource load order in server.cfg
Vehicle spawning issues	OneSync not enabled or vehicle list not updated	Enable OneSync, run vehicle seeder if available
Money exploits	Unprotected server events	Use server-side validation for all money transactions, never trust the client

Performance Tweaks

Optimizing QBCore server performance involves both server configuration and resource management:

Convars for performance:

• set sv_enforceGameBuild 2802 — Use a recent game build for latest features and fixes
• set mysql_slow_query_warning 300 — Log slow database queries for optimization
• Thread scheduling — Avoid resources that run on every tick (0ms wait). Use Wait(1000) or event-driven patterns where possible.

Resource optimization:

• Remove unused resources. Every ensured resource consumes server ticks even if players do not interact with it.
• Replace heavy resources with lighter alternatives. For example, replace old phone scripts with modern, optimized versions.
• Use server-side logic where possible. Client-side scripts run on every connected player machine, multiplying their performance impact.
• Monitor with txAdmin performance graphs to identify which resources consume the most server time.

Database optimization:

• Index frequently queried columns (citizenid, identifier, plate)
• Clean up old data periodically (stale vehicles, inactive player data)
• Use prepared statements to reduce query parsing overhead

Final Thoughts

Proper QBCore configuration is an ongoing process, not a one-time setup. Start with the fundamentals — correct load order, balanced economy, and proper txAdmin settings — then refine based on player feedback and performance monitoring. The best-configured server is one where players never think about the technical details because everything just works. Take the time to get these settings right, and your community will thrive.

Premium QBCore Resources on VertexMods

Building a QBCore server? VertexMods offers complete QBCore server templates and premium plugins that work out of the box:

• qbcore-boss-server — 146€ — Complete QBCore Boss Server — fully configured
• yespixel-4-0-inventory-qbcore — 20€ — YesPixel 4.0 Inventory for QBCore
• qbcore-vip-phone — 39€ — QBCore VIP Phone
• quasar-inventory-v3 — 35€ — Quasar Inventory V3 — premium inventory system
• cd-garage — 30€ — CD Garage — multi-location garage system