Open Resource Dependency Map · All tool guides
Before you start
A folder or ZIP containing several resources, each with its fxmanifest.lua.
Step by step
- Load the resources together so dependency names can be resolved.
- Inspect the dependency map and the unresolved and circular counts.
- For an unresolved dependency, add the missing resource or correct the declared name.
- For a cycle, review the participating manifests and code before changing declarations. Use the findings to check startup order.
What you get
A graph of declared dependencies. Undeclared runtime calls between scripts may not appear.
Troubleshooting
If nothing is found, check for fxmanifest.lua in each resource. A resource outside the scanned set appears unresolved even if it exists elsewhere on your server.
Next steps
Read Installing and checking results before replacing a working resource. For access, failed jobs or download problems, see Troubleshooting tools.