Admin & Developer Tools
Reference for all admin commands and builder utilities in oxide-newspaperjob.
Reference for all admin commands and builder utilities in oxide-newspaperjob.
Builder Command
The newspaper job uses a single menu-driven builder:
| Command | Description | Permission |
|---|---|---|
/newspaperbuilder | Opens the newspaper depot builder UI | Admin only |
Builder Features
The builder menu supports:
- creating a new depot location at your current position
- setting the BMX spawn point
- setting the cinematic menu camera
- adding house delivery zones with labels and minimum level
- quick-adding house zones with auto-detected street names
- undoing the last action
- viewing active build status
- finishing a location
- exporting all finished locations to
exported_locations.lua - importing current
Config.Locationsinto the builder - editing previously finished locations
Suggested Builder Workflow
Go to the depot NPC position and open /newspaperbuilder.
Create a new location.
Stand where the BMX should spawn and set the bike spawn.
Stand where the menu camera should look from and set the camera.
Go to each delivery target and add house zones.
Finish the location once required fields are complete.
Export the finished set to exported_locations.lua.
Copy the exported data into shared/config/locations.lua.
Export Output
Exports are written to:
exported_locations.lua
The server also prints the exported Config.Locations block to the console.
Player Commands
These commands are available to all players:
| Command | Description |
|---|---|
/newspapertutorials | Toggle tutorial prompts on or off |
/newspapertutorialreset | Reset tutorial progress |
Keybinds
| Keybind | Action | Description |
|---|---|---|
H (hold) | Show waypoint | Displays the floating waypoint overlay for the current house |
Permissions
The builder is admin only. It uses the same admin check as every Oxide resource, so if someone is already an admin on your server, they can use it — there's nothing extra to set up per resource.
If you're already running QBCore, QBX, or ESX admins, those admins pass automatically and you can skip this section.
To make someone an admin, add them to the admin group and grant that group the admin ace. Add these two lines to your server.cfg:
add_principal identifier.license:<their-license> group.admin
add_ace group.admin admin allowThe first line puts the player in the admin group; the second grants that group admin access. Replace <their-license> with the player's license identifier, which you can find in your admin tools or the server console when they connect.
Progression Management
Player progression is stored in the unified job_progression table with job = 'newspaper'. To manage progression:
Reset a Player's Progression
UPDATE job_progression
SET level = 1, total_count = 0, daily_streak = 0, complaints = 0, timeout_until = NULL
WHERE char_id = ?
AND job = 'newspaper';Remove a Suspension
UPDATE job_progression
SET timeout_until = NULL
WHERE char_id = ?
AND job = 'newspaper';Clear Complaints
UPDATE job_progression
SET complaints = 0
WHERE char_id = ?
AND job = 'newspaper';Set a Player's Level
UPDATE job_progression
SET level = 5
WHERE char_id = ?
AND job = 'newspaper';View a Player's Stats
SELECT *
FROM job_progression
WHERE char_id = ?
AND job = 'newspaper';Operational Notes
- Clocking out deposits bank pay and removes the active
weapon_newspaperitem. - Bike loss and out-of-ammo incidents clear the active route immediately.
- Hospitalization auto-clocks out the shift and pays any completed route earnings already accumulated in the shift breakdown.