A player stuck on the loading screen — or loading in but never spawning a character — is a frustrating QBCore issue that usually comes down to a handful of causes. Here's how to track it down.
Where the loading process can break
When a player joins a QBCore server, several things happen in sequence: they connect, the framework loads their data from the database, the character/multicharacter system runs, and finally they spawn. A failure anywhere in that chain leaves them stuck. The trick is finding *which* step fails.
Cause 1: Database connection problems
QBCore loads player data from your database via oxmysql. If that connection is failing, players can't load past the framework step.
Fix: Check the console for oxmysql/database errors. Verify your mysql_connection_string is correct and your MySQL/MariaDB server is running. This is the single most common cause. Our oxmysql guide covers it fully.
Cause 2: Multicharacter / spawn resource errors
The multicharacter selection and spawn manager control the final step of loading. If one errors, players hang after the framework loads.
Fix: Check the console for errors from your multicharacter or spawn resource. Try updating it, or temporarily testing with a simpler spawn setup to isolate whether it's the culprit.
Cause 3: A resource erroring during player load
Some scripts run logic when a player loads in. If one throws an error mid-load, it can halt the whole process.
Fix: Watch the console at the exact moment a player joins and gets stuck. Errors printed at that point name the offending resource. Disable it and test.
Cause 4: Corrupted or bad player data
Occasionally a specific player's saved data is malformed and breaks their load, while others load fine.
Fix: If only one player is affected, their database record may be the issue. Check their entry in the players table. As a last resort, resetting that specific character's data can clear it.
Cause 5: Version mismatch after an update
If QBCore or a core resource was updated and something's now out of sync, loading can break for everyone.
Fix: Ensure qb-core and its dependencies are at compatible versions. Review recent updates. See our server-won't-start-after-update guide for the general approach.
The diagnosis process
- Is it everyone or one player? Everyone → framework/database/core issue. One player → their data.
- Watch the console as a stuck player joins — note any errors.
- Check the database connection first; it's the most common cause.
- Isolate the spawn/multicharacter resource.
- Disable suspect resources one at a time.
A stable base matters
Player-load issues often trace to a resource behaving badly during the join process. Clean, well-built scripts handle player loading correctly and don't interfere with the spawn chain. At Viper Development, our scripts are built to integrate cleanly with QBCore's player system. Browse our scripts →.