ScriptsAboutBlogToolsKnowledge BaseReviewsFAQBasketDocsSupport
Resourcecrash

Could not find dependency X for resource Y

Also seen as: Could not find dependency missing dependency FiveM

What causes it

Resource Y declares a dependency on resource X in its fxmanifest.lua, but X isn't started (or isn't present) when Y tries to start. This is almost always a load-order problem or a missing resource.

How to fix it

Make sure the dependency resource exists and is started before the resource that needs it.

  1. Confirm resource X actually exists in your resources folder.
  2. In server.cfg, ensure X BEFORE Y. Core dependencies like oxmysql and ox_lib should be near the top.
  3. If X is present and ordered correctly but still not found, check X itself isn't failing to start (read its own errors first).
  4. Verify the dependency name in Y's fxmanifest matches X's actual folder name exactly.

Related errors

No such export fetchSync in resource oxmysqlCouldn't load resource manifestResource X failed to start

Related guides

Still stuck? We can help.

Optimized, dual-framework scripts for QBCore and ESX from Viper Development — escrow protected, delivered instantly to your Cfx portal.

Join DiscordBrowse Scripts →