Troubleshooting
Fixes for the most common myRP.build issues: resources that didn't load, missing ox dependencies, and offline servers.
Most issues come down to the server state or the ox stack. Work through these in order.
The resource didn't load
myRP.build loads resources for you, but a server-side error can still stop one from starting.
- Open your server console (txAdmin or the FXServer window) and look for errors mentioning the resource name.
- A Lua syntax or runtime error will be printed there with a line reference.
- Confirm the folder appears under
resources/[local]/<name>/— see Pointing at Your Server.
Missing ox dependency
Generated resources depend on the Overextended stack, which myRP.build installs for you. If the console reports an unknown export or a missing dependency, an ox resource may not have started before your generated one:
ox_lib,oxmysql,ox_core,ox_inventory,ox_target
Confirm those are present in resources/[ox]/ and load before your [local] resources. If one is missing, re-run the generation that needs it — myRP.build installs missing ox resources for you (with your approval).
Server is offline
The app writes to the resources folder, but loading only happens against a running server.
- Confirm the FiveM server is actually up.
- Confirm myRP.build is pointed at the resources folder for the server you're testing — not a different or stale copy.
Windows only
myRP.build runs on Windows 10/11 · 64-bit only. There are no macOS or Linux builds. If you're on another OS, run the app on a Windows machine that can reach your server's resources folder.
Still stuck?
Bring the console error and your prompt to the community — we can usually spot it fast.