FiveM Resource Conflicts

This guide helps you identify and fix FiveM resource conflicts, script errors, and framework issues that cause server problems.

Types of FiveM Conflicts

Resource Conflicts

Two resources trying to do the same thing:

Multiple HUD systems
Multiple inventory systems
Duplicate job scripts

Framework Conflicts

Mixing incompatible frameworks:

ESX resources on QBCore server
Old ESX versions with new resources
Multiple framework cores loaded

Load Order Issues

Resources loading before their dependencies:

Job script loading before framework
UI loading before its library

Database Conflicts

Resources fighting over the same tables:

Multiple resources using users table differently
Schema mismatches after updates

Reading Console Errors

Where to Find Errors

txAdmin Console — Real-time in the txAdmin panel
Server Console — In your control panel
citizen-server.log — In txData/logs/ folder

Common Error Patterns

Error Contains	Meaning	Fix
`SCRIPT ERROR`	Lua error in resource	Check the named resource
`attempt to index a nil value`	Missing data or function	Resource missing dependency
`mysql-async` errors	Database connection issue	Check database credentials
`resource X not found`	Missing dependency	Install the required resource
`ensure` failed	Resource failed to start	Check resource for errors
`duplicate`	Two resources with same name	Remove duplicate

Reading Stack Traces

When you see an error like:

SCRIPT ERROR: @es_extended/server/main.lua:142: attempt to index a nil value

This tells you:

Resource: es_extended
File: server/main.lua
Line: 142
Error: Something expected data but got nothing

Resource Load Order

Why Order Matters

Resources load in the order listed in server.cfg. Dependencies must load first.

Correct Load Order

# 1. Database connection (ALWAYS first)
ensure oxmysql

# 2. Framework core
ensure es_extended
# OR
ensure qb-core

# 3. Framework dependencies
ensure esx_menu_default
ensure esx_menu_dialog
ensure esx_menu_list

# 4. Core systems
ensure esx_identity
ensure esx_society
ensure esx_billing

# 5. Jobs and features
ensure esx_policejob
ensure esx_ambulancejob

# 6. Third-party resources
ensure custom_hud
ensure custom_inventory

# 7. Optional/cosmetic resources (load last)
ensure loading_screen
ensure custom_sounds

Framework Conflicts: ESX vs QBCore

Don’t Mix Frameworks

ESX and QBCore are completely incompatible:

ESX resources won’t work on QBCore
QBCore resources won’t work on ESX
Running both causes severe conflicts

Check Resource Compatibility

Before installing any resource, check:

What framework it requires (ESX, QBCore, or standalone)
What version of the framework (ESX Legacy, ESX 1.2, etc.)
Dependencies listed in the resource’s README

Common Framework Errors

Error	Cause	Fix
`ESX is nil`	ESX not loaded or wrong resource	Check ESX is loading
`QBCore is nil`	QBCore not loaded	Check qb-core is loading
`GetSharedObject undefined`	Wrong framework version	Update framework or resource
`exports not found`	Resource name mismatch	Check resource folder name

Isolating Problem Resources

The Disable-Test Method

Disable half of your third-party resources (comment out with #)
Restart the server
Test — is the problem gone?
- Yes → Problem is in the disabled resources
- No → Problem is in the still-running resources
Repeat until you find the culprit

Using txAdmin Resource Monitor

Open txAdmin
Go to Resources
Look for resources showing:
- High CPU usage
- Errors in the log
- Failed to start

Quick Disable in server.cfg

# Comment out suspicious resources
#ensure problem_resource_1
#ensure problem_resource_2

# Keep essential resources running
ensure es_extended
ensure oxmysql

Database Conflicts

Symptoms of Database Issues

Players losing items or money
Jobs not saving
“MySQL connection failed” errors
Duplicate key errors

Common Database Fixes

1. Check Connection

Verify your database credentials in server.cfg:

set mysql_connection_string "mysql://user:password@localhost/database?charset=utf8mb4"

2. Check for Duplicate Tables

If two resources try to create the same table:

Check both resources’ SQL files
Remove duplicate table creation
Use the schema from the primary resource

3. Reset Corrupted Data

-- Example: Reset a player's inventory if corrupted
UPDATE users SET inventory = '[]' WHERE identifier = 'steam:123456789';

txAdmin Troubleshooting

txAdmin Won’t Start

Check that the txData folder has proper permissions
Verify your server.cfg path is correct in txAdmin settings
Check for port conflicts (default: 40120)

txAdmin Shows Resource Errors

Look at the Live Console for specific errors
Check Resources page for failed resources
Review System Log for startup issues

Scheduled Restarts Causing Issues

If problems appear after scheduled restarts:

Check if any resources have state that doesn’t survive restarts
Verify database connections are re-established
Look for race conditions in resource startup

Common Resource Issues

Voice Chat (pma-voice, mumble-voip)

Issue	Fix
Voice not working	Check port 30120 UDP is open
Echo or feedback	Adjust voice config distances
Only some players affected	Client-side microphone issue

Inventory Systems

Issue	Fix
Items disappearing	Check database connection
Duplicate items	Look for inventory duplication bugs
Can’t pick up items	Check weight limits and permissions

Vehicle Systems

Issue	Fix
Cars not saving	Check garage resource and database
Duplicate vehicles	Look for spawn script issues
Vehicles despawning	Adjust vehicle cleanup settings

Performance Issues from Resources

Identifying Slow Resources

Use the built-in resource monitor:

resmon 1

This shows CPU time per resource. Look for:

Resources using more than 5ms consistently
Spikes during specific actions

Common Performance Drains

Unoptimized loops — Running every frame instead of on events
Heavy database queries — Fetching too much data
Memory leaks — Resources not cleaning up
Too many markers/blips — Rendering overhead

Prevention Tips

Before Installing Resources

✅ Check framework compatibility
✅ Read installation instructions completely
✅ Check dependencies and install them first
✅ Back up your server before installing
✅ Test on a development server first

Regular Maintenance

Keep framework updated to latest stable version
Remove unused resources
Monitor resource performance regularly
Back up database daily

Still Not Working?

Before contacting support, gather these 3 things:

Server ID — found in your panel URL or dashboard
What you tried — list the steps you already attempted
Error message or screenshot — exact text or image of what you see

Then contact us:

Email: support@mambahost.com
Discord: Open a ticket in our server