Troubleshooting Guide
Common checks for shift flow, o-link integrations, phone messages, UI, progression, and animal behavior issues in oxide-animalcontroljob.
Common issues and the current checks for oxide-animalcontroljob.
Shift Issues
Dispatch Issues
Vehicle Issues
Animal Issues
Tranquilizer Issues
Bait and Capture Issues
Delivery Issues
Crew Issues
Payment and Progression Issues
UI Issues
Model Issues
Debugging
Turn on the Debug logging setting (Config.Debug) in-game with /animalcontrol settings (admins only, under General). It saves to the database and applies live — no restart or file edit needed.
This adds [oxide-animalcontroljob] debug output for:
- shift flow
- dispatch timing
- animal spawning and state transitions
- bait and capture events
- tranquilizer hits
- crew actions
- progression saves
- vehicle handling
Debug force job type
To test a specific job type, set Force call type (Config.DebugForceJobType) in /animalcontrol settings (admins only, under General) to the job type you want dispatch to send. Set it back to Off for normal operation. Like every setting, it saves to the database and applies live.
When Reporting Issues
Include:
o-linkversion or current branch- active
o-linkmodules used for target, phone, money, inventory, and vehicle keys - server console errors
- client or F8 errors for UI issues
- reproduction steps
- whether the issue happened solo or in a crew
- the job type when the issue occurred
Support
Need more help?
- Discord: https://discord.gg/dZ6q8FyGhm
- Website: https://www.oxidestudios.dev/
- o-link (required abstraction layer): https://github.com/Oxide-Studios/o-link