Could not find dependency <dep> for resource <name>
A script needs another script that is missing, not turned on, or turned on too late.
Do this first
In server.cfg, make sure the script it names is listed ABOVE the one that failed.
What it means
The resource's fxmanifest declares a dependency the server cannot satisfy. The resource will not start.
What causes it
Ordered by how often it is the answer.
- 1
The dependency is not installed
The name in the message is a resource folder that does not exist.
- 2
Installed but not started
Present in the resources folder, missing from server.cfg. A dependency must be started, not merely present.
- 3
Started AFTER the dependent
server.cfg is read top to bottom.
ensure my-scriptaboveensure ox_libfails even though both are listed. - 4
The folder name differs from the dependency name
dependency 'ox_lib'with a folder calledox_lib-master— the usual result of unzipping a GitHub download without renaming it.
How to tell which one is yours
refresh ensure <dependency-name>
in the server console. "No such resource" means it is not installed or is named differently; a clean start means it was only an ordering problem.
Where to look
The failing resource's fxmanifest.lua, and the order of ensure lines in server.cfg.
How to fix it
# server.cfg — dependencies first, always ensure oxmysql ensure ox_lib ensure es_extended ensure my-script
Folders downloaded from GitHub keep a -main or -master suffix. Rename them.
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