Couldn't load resource <name>
The server could not read a script at all, usually because of a bad folder name or a typo in its settings file.
Do this first
Check the folder name has no spaces or capital letters.
What it means
The server tried to read the resource and gave up before starting it. This is earlier than "couldn't start": the manifest itself could not be understood, or the folder is not usable.
What causes it
Ordered by how often it is the answer.
- 1
A syntax error in fxmanifest.lua
The manifest is Lua. A missing comma or quote in a script list breaks it, and the error can be printed separately just above.
- 2
A folder name the server will not accept
Spaces, capitals on a case-sensitive host, or characters outside
a-z 0-9 _ -. - 3
A resource inside a bracketed folder that is itself bracketed
[category]/[sub]/resourcenests deeper than the loader scans. - 4
Permissions
On Linux, a resource folder the FXServer user cannot read.
- 5
It is a client-side download failure
The same message appears on the CLIENT when a resource fails to download on join, which is a different problem — see the client-side entry.
How to tell which one is yours
Read the lines above it for a manifest parse error. If the message appeared in YOUR console the folder is the problem; if a PLAYER reported it while joining, it is a download or cache problem on their end.
Where to look
fxmanifest.lua, and the folder name.
How to fix it
fx_version 'cerulean'
game 'gta5'
client_scripts {
'client/main.lua', -- commas matter
}Rename folders to lowercase with no spaces: my-script, not My Script.
Still stuck on your own code?
This page is what this error usually means. Paste your console into Server Fixer and it will rank everything in it and tell you what to do first, and if you would rather not touch it, ORBIE can repair the script and hand the resource back ready to drop in.
bug_reportOpen Server Fixer