Skip to main content
vrs_newspaper leans on vrs_bridge for every framework-specific touchpoint, so it does not need to be patched per framework itself.

Framework detection

Auto-detects QBox, QBCore, or ESX on boot, no config needed.

Target script fallback

Uses ox_target or qb-target if present, falls back to markers otherwise.

Route builder

Capture new depots and delivery points in-game with /npbuilder.

Escrow-safe

config/, locales/, and sql/ ship readable, only gameplay Lua is encrypted.

Framework, inventory, and target detection

On boot, vrs_bridge detects the running framework, inventory, target script, and vehicle-key system and reports what it found:
A target script is optional. If ox_target or qb-target is present it is used automatically; if neither is running, the depot and district interactions fall back to a marker/keybind flow. To pin any of these instead of auto-detecting, edit vrs_bridge’s own config.lua.

Registering the newspaper item

The job throws a real weapon under the hood (aliased onto WEAPON_ACIDPACKAGE), so it has to be registered with your inventory the same way any throwable weapon would be. For ox_inventory this means an entry in data/weapons.lua, not items.lua, see Installation for the exact snippet.
New items are usually cached at inventory boot. After registering WEAPON_NEWSPAPER, restart the inventory resource (or the whole server) rather than just the newspaper job.

Depending on the resource

If another resource needs vrs_newspaper running, add it to that resource’s fxmanifest.lua:
fxmanifest.lua
vrs_newspaper itself depends on vrs_bridge v1.3.0+, ensured before it in server.cfg.

Extending delivery points

The depot and every district’s houses live in routes.lua, editable by hand or captured live with the in-game route builder: Paste the exported blocks over the tables in routes.lua to wire a new district into the job.
Leave a point’s label out and it is read from the world at runtime. Points with groundSnap = true correct their height automatically.

Escrow boundaries

escrow_ignore keeps config/, locales/, and sql/ readable after upload, everything else in Lua is encrypted. Two things worth knowing if you are integrating with the resource:

Escrow only encrypts Lua

The contents of html/ ship readable on every escrowed copy. All pay maths and validation live server-side in Lua, and the page only renders what it is handed.

vrs_bridge is escrowed separately

It keeps its own config.lua and detection map open, so it can be retargeted without touching vrs_newspaper.
Last modified on August 12, 2026