Troubleshooting Guide

Common oxide-pestcontroljob issues and fixes — install, shifts, dispatch, the van, the inspection, treatments, wasp nests, reports and callbacks, crews, pay, phone and screen, and settings.

Common issues with oxide-pestcontroljob and how to fix them. Most fixes are a setting in /pestcontrol settings or a step from the Installation Guide.

Install Issues

Shift Issues

Dispatch Issues

Vehicle Issues

Inspection Issues

Treatment Issues

Wasp Nest Issues

Report and Callback Issues

Crew Issues

Payment and Progression Issues

Phone and Screen Issues

Settings Issues

Debugging

Turn on Debug logging (Config.Debug) in /pestcontrol settings under General (Advanced tab). It saves to the database and applies live, with no restart or file edit needed.

This adds [oxide-pestcontroljob] lines to the server console and the F8 console for:

  • clocking in and out, with the depot's free slots
  • shift state changes
  • the dispatch timer and each call sent
  • crew invites and changes
  • progression loads, saves, level-ups and suspensions
  • the clerk and the van spawning
  • where each UV sign was placed and how it sits on the ground (in the F8 console)

Turn it off again afterwards.

Test a specific pest

Admins can set Force pest (Config.DebugForceSpecies) under General (Advanced tab) so normal dispatch sends only that pest. Set it back to Off for normal play. See Testing Every Stage.

Getting Help

If none of the above solves it:

  1. Turn on debug logging and reproduce the problem.
  2. Copy the server console output and any red F8 errors.
  3. Contact Oxide Studios support with:
    • your o-link version
    • your framework (QBCore, Qbox or ESX) and the target, phone, money and vehicle keys resources you run
    • the console and F8 output
    • the steps that cause the problem
    • whether it happened solo or in a crew
    • the pest, the property, and the technician's level