Troubleshooting Guide
Common oxide-newspaperjob problems and fixes — clocking in, routes and cancelling, throws, the newspaper item, the bike, pay, settings, missing models, the UI, and phone messages.
Common problems with oxide-newspaperjob and how to track them down. Work down each list from the top — the first check is the most likely one.
Most settings mentioned here are changed in-game with /newspaper settings (admins only). Once the resource has started for the first time, editing a config file does nothing until you restart the resource and press Reset to default on that setting — see How Settings Work.
Shift Problems
Route Problems
Paper / Inventory Problems
Bike Problems
Pay and Progress Problems
Settings Problems
UI Problems
Uniform Problems
Turning On Debug Output
Turn on Debug logging under General in /newspaper settings (on the Advanced tab). It saves to the database and applies right away, no restart needed. Setting Config.Debug = true in shared/config.lua only changes the factory default (see How Settings Work).
This prints [oxide-newspaperjob] lines to the consoles for shift state changes, route generation, bike spawn/despawn, clock-in/out slot counts, and cleanup. It also draws a visible ring around the active house target, which is handy when tuning hit distances.
Deeper records — payouts, fines, anti-cheat rejections, admin actions, settings changes (and whether each came from the menu or another resource), refused admin attempts at /newspaper settings or the builder (one line per player and action per minute) — are written through o-link's logger. If your server runs oxide-logger (or another logging backend), you'll find them there under the oxide-newspaperjob resource name.
When Reporting an Issue
Include:
- your framework (QBCore, Qbox, or ESX) and inventory script
- any errors from the server console
- any errors from the player's F8 console
- what the player was doing: clocking in, mid-route, losing the bike, clocking out
- steps to make it happen again, if you have them