Incident Replay System — rewind any fight, see who shot first
How a ticket actually goes with IRS
- Player types
/report he just RDM'd me at Legion→ auto-bookmark with his exact position - Staff types
/replay, clicks the bookmark - Playback opens 10 seconds before the moment — trails show the attacker stalking him around the corner, tracer shows the first shot, red X marks the kill
- One click → incident card posted to your staff Discord: who, where, when, shots fired, deaths
- Verdict posted. Next ticket.
What it records — without touching a single client
Positions of every player, continuously (rolling window, default 72 h — configurable)
Shots with attacker → victim tracers
Deaths with killer attribution — every death auto-bookmarked
Vehicle enter/exit, explosions, combat state
/reportbookmarks with the reporter’s exact position
Capture is fully server-side (OneSync). Zero client scripts in the hot path, zero FPS cost, zero extra network traffic — and cheaters can’t spoof or wipe what the authoritative server recorded. Deleted his clip? Doesn’t matter. The server saw it.
The replay
- Top-down satellite map with smooth 60 fps playback from the recorded data
- Timeline scrubber with bookmark ticks, 0.5× / 1× / 2× / 4× speeds
- Fading movement trails, name labels, vehicle icons, combat indicators
- Filter to the players involved — dim everyone else, focus the fight
- Event feed — click any kill to jump straight to it
- Pin important incidents so they survive retention pruning (default 30 days)
One-click Discord export — clean incident card in your staff channel
Performance (measured, not promised)
- ~0.01 ms resmon at 128 players — adaptive sampling drops idle players to 1 Hz automatically
- ~13 MB of disk per hour at 64 players; a full 72 h window stays under 1 GB
- Batched writes, async DB, no per-sample database rows — your MySQL never feels it
Works with your stack
QBCore · Qbox · ESX Legacy · Standalone — auto-detected, character names everywhere- ACE-permission gated (
irs.view) — you decide exactly who can replay - Fully open
config.lua+ locale file — retention, sample rate, commands, Discord, all yours to tune - oxmysql + OneSync (you already have both)
What it deliberately does NOT do
No voice recording. Ever. That’s a consent minefield — IRS records positions and combat metadata only.- No client-side spyware nonsense. The server already knows where everyone is; IRS just remembers it.
Get it
[TEBEX LINK] — escrow, config + locales fully editable
**[YOUTUBE]**
Full install guide included — 5 minutes: drop resource, run one SQL file, add one ACE line
| Code is accessible | No |
| Subscription-based | No |
| Lines (approximately) | 3000 |
| Requirements | no |
| Support | Yes |