Couldn't start resource <name>
The server refused to start a script. Everything that depended on it will fail too, which is why one problem looks like twenty.
Do this first
Read the lines just ABOVE this one — the real reason is printed first.
What it means
The server refused to start the resource. Nothing in it ran, and every resource that depends on it will fail too, which is why one of these usually produces a wall of unrelated-looking errors underneath.
What causes it
Ordered by how often it is the answer.
- 1
A dependency is missing or failed first
The manifest declares
dependency 'ox_lib'and ox_lib is not started. FiveM prints that dependency error separately, usually just above. - 2
A script in it failed to load
See "Failed to load script" above this line.
- 3
The name in server.cfg does not match the folder
ensure my-scriptwith a folder calledmy_script. - 4
The folder is outside any path the cfg scans
Resources under a bracketed category need that category to be scanned. A folder dropped somewhere else is invisible.
- 5
A duplicate resource name
Two folders with the same name in different categories. The server loads one and refuses the other.
How to tell which one is yours
Read the ten lines above it. This message is almost always a consequence and the cause is printed first. If nothing precedes it, the folder name or the ensure line is wrong.
Where to look
server.cfg, and the resource folder name.
How to fix it
ensure oxmysql ensure ox_lib ensure es_extended ensure 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