GM Bounty is a self-contained bounty-hunting mission for law-enforcement roleplay on RedM: the "quick money / routine breaker" for on-duty lawmen between calls. A single bounty-paper item hands the player a randomly drawn wanted poster*:* ride out to the target's hideout, fight through an armed escort, take the target dead or alive, and haul them back to a sheriff's office for a cash + item reward (alive pays more). It runs on GM (RSGCore), stock RSG, and VORP through the jo.framework bridge, with the core and inventory auto-detected and a pre-built wanted-poster UI, so a normal install needs no SQL import and no build step.
Features:
- The Mission
- Combat & AI
- Setup & Extras
- Wanted poster: NUI with the target's face, a location hint, the reward & a random sheriff signature
- Armed escorts: per-target count, models, weapons, health & aim accuracy
- Multi-framework: GM / RSG / VORP, auto-detected via jo.framework
- Dead or alive: hogtie for the full payout, or gun them down for less
- Spawn zones: scatter escorts across circle or hand-drawn polygon areas
- No database: in-memory cooldowns, zero SQL import
- Drag & deliver: carry the target to any sheriff turn-in office
- Leash & reaper: quest fails if you stray too far; fled/stuck bots auto-cleaned
- Pre-built UI: no Node, npm, or build step
- 14 targets shipped: never handed the same one twice in a row
- Live enemy blips: optional minimap tracking, engaged-only or always-on
- Discord audit: per-event webhooks (accepted / completed / failed)
- Per-character cooldown: starts the moment a bounty is accepted, survives relog
- Fail states: abandon, stray, die, or run out the timer
- Job-gated: restrict the bounty paper to the jobs you choose
> 💡 Tune it to _your_ server. Every target is fully overridable*:* its own escort count, models, weapons, health, spawn zone, trigger radius, leash and timer*:* so you can mix quick shootouts with pitched hideout sieges. Notifications and the inventory-full item drop are swappable through open adapter files (`gm_notify`, `ox_lib`, `vorp_core`, or your own `custom` hook) without ever touching the escrow-protected core, and every payout is audited to Discord per event.
Dependencies: