You don't have to know what it means. Paste the line (or the whole console) and you get it back in plain words: what broke, what your players are feeling, what to do first, and whether it's yours to fix or a job for a developer. If you want, ORBIE fixes the script and hands you the file to drop in.
SCRIPT ERROR: @qb-garages/server/main.lua:112: attempt to index a nil value (field 'PlayerData')
PlayerData is empty or not loaded yet
A script asked for a player's info before the game sent it. Usually works on join, breaks after a restart.
The one red line, or the whole console dump. It reads here, in your browser.
In plain words: the cause, what your players feel, and the first thing to try.
Do it yourself with the steps, or let ORBIE repair the script and hand back the file.
Rather read about your exact error first? Here are all 85, each with its own page, and 44 you can fix without a developer.
Something tried to continue a job that had already finished or already crashed. There is nearly always a REAL error above this o…
This line is FiveM itself saying an error happened somewhere else. It is a signpost, not the problem.
A script got back a different kind of answer than it expected, often reading a database result the wrong way.
A script tried to wait in a place where waiting is not allowed. It is a coding mistake, not a setup one.
A script called itself over and over until it ran out of room. Something is looping into itself.
A script tried to file something away under a name that was empty, usually a player id that was not ready yet.
A script expected some information to be ready and it was not there yet, so it stopped.
A script tried to use a function that does not exist — usually because it was written for a different version of your framework.
A script tried to do maths with a value that was empty — very often a money or item amount that was never set.
A script tried to build a message out of a value that was missing, usually a player name or a config setting you left blank.
A script passed the wrong kind of value to the game, almost always because something it needed (a vehicle, a model) never loaded.
A script tried to compare two things that cannot be compared, usually a number against something that is missing or is text.
A script needs to build its interface on your server before it can run, and that build failed — usually the server cannot reach …
One of the script's files has a typo in it, so the server could not read it. Often a bad copy-paste or a half-finished edit.
A folder in your resources is missing the file that tells the server what it is. Almost always the zip was unpacked one level to…
You have two copies of the same script installed. The server picks one and ignores the other, and which one it picks is not pred…
The server could not read a script at all, usually because of a bad folder name or a typo in its settings file.
The server refused to start a script. Everything that depended on it will fail too, which is why one problem looks like twenty.
The server could not open one of the files a script is made of, so that script never ran at all.
A script's folder name has characters the server will not accept — usually spaces or capital letters from unzipping a download.
Something asked for a script that is not running. If you have never heard of the name, it is optional and you can ignore it.
A script tried to read its own settings before they had loaded. It is an ordering mistake inside the script.
One script tried to use a feature of another script that is not there — usually because that other script is off, or is a differ…
A script needs another script that is missing, not turned on, or turned on too late.
A script's settings file is missing a line the server requires. It is usually a very old script.
Your server software is too old (or too new) for something you are running on it.
Your server has no Cfx licence key, and it will not start without one. The key is free.
Someone tried to run a command they do not have permission for.
Your server is running but is not showing up in the FiveM server list.
You asked for more player slots than a free server is allowed. The limit is 48 without a paid Cfx subscription.
Something is already using the port your server wants — usually the previous copy of the server that never fully closed.
The server looked for a player and did not find one — usually they disconnected mid-action.
You have two frameworks running at once. Scripts attach to whichever answered first, so things work and break at random.
A script asked for a player's information before the game had sent it. It usually works on join and breaks after restarting the …
A script asked for a money account that this player does not have, usually because the account name does not match your framework.
A script could not find your framework (ESX, QBCore, Qbox) — either it is not running, or it starts after this script does.
A character's saved details could not be read — either they had not finished loading, or that character's data is damaged.
One script called out to another and nothing answered. There is often no error at all — the feature just never happens.
Your jobs list could not be read. One typo in the jobs file breaks every job-related script at once.
A script uses an old way of connecting to ESX that modern ESX removed. There is no error — it just silently never works.
Your server cannot reach its database. Nothing that saves or loads will work until this is fixed.
A script was written for an older database system than the one you have installed.
Too many things asked the database at once and it stopped accepting more. This usually hits at your busiest moment.
Two things tried to save the same record at the same moment and the database cancelled one of them.
Someone had an emoji in their name and your database cannot store emojis.
A script sent the database a request it could not understand.
The database is missing a whole table a script needs. Its setup file was never imported, or was imported into a different databa…
Something was too big for where it was being saved, so it was not saved at all — inventories are the usual case.
A script is looking for information the database does not have — nearly always because its setup file was never imported.
A script tried to save something that already exists — usually a player being added twice.
The game ran out of room for vehicles, people or objects. Something is creating them and never cleaning up.
Something tried to spawn a vehicle, person or object and it did not appear.
A script sent so much to one player that their connection could not keep up, so they were kicked.
A script tried to send too much at once. It may be cut in half without saying so, which is worse than failing.
A player's game was told about something before it had actually arrived on their screen.
A script needs OneSync and your server does not have it turned on. Every modern framework needs it.
A script is updating shared information far too often, so some of those updates are being thrown away.
Players or objects are in separate copies of the world, so they cannot see each other.
A vehicle or character does not exist on your server, so nothing can spawn it.
A script tried to put clothing on a character that does not have that item — usually saved outfit data from a different characte…
A model loaded but its textures did not, so it shows up plain white, black or untextured.
One of your added vehicles or objects is damaged, usually from a bad upload.
A model was made incorrectly and FiveM refuses to load it, because loading it would crash people.
One file is too big for FiveM to load, so it is skipped and everything using it looks broken.
A script tried to send information to its own menu and the information could not be sent, so the menu shows nothing.
A menu opens as a blank or white box, usually because some of its files are missing from the download.
A menu closed but kept control of the mouse and keyboard, so the player cannot move or type.
A button in a script's menu does nothing when clicked, and usually nothing appears in the console either.
A script expected some information and got nothing. It is the same class of problem as the most common Lua error.
A script used up all available memory and took the server down with it. Something is being kept and never released.
A script is missing pieces it needs to run — usually it was downloaded from GitHub without its extras.
A paid script could not confirm you are allowed to run it.
You own the script but this particular server is not the one it was granted to.
Cfx says this server is not licensed for a paid script you are running.
You are running content from a newer GTA update than your server is set to allow, so it simply does not exist in game.
Restarting a script left its old vehicles, characters or menus behind, so now there are two of everything.
One script held everything up. Unlike a general stutter, this one names the resource responsible.
Something ran out of memory. It is not about how busy the server is; something is piling up and never being cleared.
Something froze the server for a moment. Players feel it as a stutter. It is a symptom, not a failure.
A player's game failed to download one of your scripts while joining.
Players connect but never actually spawn in — the loading screen never goes away.
A player could not reach your server in time. Either their connection, or your ports, or your server being too busy to answer.
A player's game could not sign in to Rockstar. Nothing to do with your server.
A player's game and your server were built against different GTA updates. Right after a FiveM update this is normal for a day or…
A player's FiveM will not start. This is on their computer, not on your server.