Troubleshooting

Startup Issues

Shift Issues

Dispatch Issues

Vehicle Issues

Job Issues

Target, Prop, and Cone Issues

Crew Issues

Payment and Progression Issues

UI Issues

Debugging

This resource sends all of its logging through the oxide-logger resource. If you have it installed, you can turn up the detail for this resource without restarting anything — run this in the server console:

oxlog level oxide-roadsideassistancejob debug

The console will then show extra lines for shift flow, dispatch timing, crew actions, progression saves, and vehicle tracking. Use trace instead of debug for even more detail. To make the setting survive restarts, set it in oxide-logger/config/config.lua instead:

Config.Levels = {
    ['oxide-roadsideassistancejob'] = 'debug',
}

Set it back to info when you're done — debug output is noisy. If oxide-logger isn't installed, the resource runs normally; there's just no extra logging to turn on.

When Reporting Issues

Include:

• your framework (QBCore, QBX, or ESX) and which phone/target/key resources you run
• server console errors
• client/F8 errors for UI issues
• reproduction steps
• whether the issue happened solo or in a crew

Support

Need more help?

• Discord: https://discord.gg/dZ6q8FyGhm
• Website: https://www.oxidestudios.dev/
• o-link (required abstraction layer): https://github.com/WHEREISDAN/o-link