qb-newsjob

qb-newsjob equips the reporter job. It provides a newsroom, a liveried van, and three pieces of equipment: a camera, a handheld microphone, and a boom microphone. Using an item toggles the corresponding client-side view or prop.

It grants no money and holds no persistent state. Reporter income is expected to come from your own roleplay economy rather than from this resource.

The manifest at the commit linked above declares version 1.5.0.

Dependencies and start order

The manifest declares no dependencies and loads config.lua, @qb-core/shared/locale.lua, and locales as shared scripts, then client/main.lua, client/spawner.lua, client/camera.lua, and server/main.lua.

The implementation requires more than the manifest admits:

LegacyFuel is the one to watch. If you run qb-fuel or another fuel resource instead, edit client/spawner.lua before starting this resource.

Start order: qb-core, qb-inventory, qb-vehiclekeys, qb-menu, your fuel resource, then qb-newsjob.

Configuration

Config.VehicleItems at this commit places newscam, newsmic, and newsbmic into slots 1, 2, and 3. All three must exist in your shared items list.

Item and command surface

Both modes carry the same job check. The handler resolves the player from source and requires PlayerData.job.name == 'reporter' before firing the client event.

The Cam: and Mic: event names are not namespaced to this resource. Check for collisions before adding another camera or microphone script.

Trunk stocking

RegisterNetEvent('qb-newsjob:server:addVehicleItems', function(plate)

The one server event. It requires the caller to hold the reporter job and to hold keys for the supplied plate through exports['qb-vehiclekeys']:HasKeys(src, plate), then creates a trunk-<plate> inventory and fills it from Config.VehicleItems.

The key check is what stops a client from stocking an arbitrary plate, so it is load bearing. It also means the whole feature silently does nothing on a server that does not run qb-vehiclekeys.

Nothing prevents the same plate from being stocked repeatedly. Each call rewrites the configured slots, so a reporter can refill a van by re-triggering the flow rather than by finding new equipment.

Integration example

Reacting to a reporter going live from your own client resource:

-- client side
AddEventHandler('Cam:ToggleCam', function()
    -- your own broadcast state, overlay, or voice channel switch
end)

Troubleshooting

Proposed manual smoke test

Not yet executed. On staging:

1. Confirm the three items exist in your shared items list.
2. Take the reporter job, spawn the van, and confirm the trunk is stocked.
3. Use each item and confirm the matching client toggle.
4. Attempt the same without the job and confirm nothing happens.
5. Set Config.UseableItems = false, restart, and confirm the three commands work instead.

Sources

• fxmanifest.lua 
• config.lua 
• server/main.lua 
• client/spawner.lua