GFX Deathlog & Reports Script | Discord Anti-RDM | FiveM

This FiveM deathlog script with Discord reports brings ironclad accountability to roleplay servers by logging every character death and giving players one-click reporting straight to staff. RDM and VDM disputes are the number one drain on staff time across FiveM RP, and they almost always come down to one player’s word against another’s. GFX Deathlog ends that argument: every death is captured, every report is timestamped, and every incident lands in Discord with the metadata your moderators actually need to make a call.

🛡️ What This FiveM Deathlog Script with Discord Reports Delivers

Deathlog with Reports is a fully standalone system built to slot into any FiveM RP server without touching your framework — no QBCore patches, no ESX hooks, no Qbox dependencies. The script silently records every character death with cause, location, killer ID, and timestamp, then exposes that history to players through a clean, searchable in-game UI. When something looks wrong, a player taps Report, and a Discord embed flies into your staff channel with the full incident context already attached. Staff stop chasing logs. Players stop feeling ignored. And the gray area between a fair kill and RDM becomes a documented record instead of a forum argument.

⚙️ Complete Feature Set

Every feature here is built around two outcomes: giving players a voice and giving staff the evidence they need to act fairly.

• Standalone architecture that works seamlessly with all frameworks
• Player-facing death history — players can view all character deaths with timestamps and report suspicious incidents later on
• Discord webhook integration that sends reports to any Discord channel you choose
• Full death history with cause of death, location, killer ID and timestamp
• One-click “Report” button for suspicious deaths — straight to staff Discord
• Clean, searchable in-game UI with filtering by date and player
• Configurable retention period to keep your database lean
• Discord embed reports include screenshots-ready context and metadata
• Multi-language support and full locale customization
• Optimized performance — minimal database queries, zero perceptible impact

🎬 Script Showcase

Watch the in-game death log UI, the one-click report flow, and the Discord embed delivery in action — from a player’s first death to the moment staff get notified.

🔌 Compatibility & Setup

This is a standalone anti-RDM report system that drops onto your server with zero dependencies — no framework patches, no inventory hooks, no extra resources required. It runs alongside any setup, from a fresh QBCore install to a heavily customized Qbox build, and the in-game UI works regardless of which HUD or notification system you have layered on top. The Discord webhook is the only external integration you need, and it takes about thirty seconds to paste in.

• Framework: Standalone — compatible with QBCore, ESX, Qbox, and custom frameworks
• Dependencies: None
• External integration: Discord webhook (your staff channel)

❓ Frequently Asked Questions

Q: Do I need a specific framework to run this?

A: No. Deathlog with Reports is fully standalone and works seamlessly with all frameworks, so it runs on QBCore, ESX, Qbox, or any custom setup with no modification. The requirements list is literally “None.”

Q: How do players actually submit a report?

A: Every death is recorded in the in-game death log UI. Players open their history, filter by date or player, find the suspicious incident, and hit the one-click Report button to send it straight to your staff Discord channel via webhook.

Q: What information ends up in the Discord report?

A: Each report is delivered as a Discord embed containing the cause of death, location, killer ID, timestamp, and screenshots-ready context and metadata — everything your moderators need to make a fair call without chasing the player around for screenshots.

Q: Will this hurt my server performance?

A: No. The script is optimized with minimal database queries and zero perceptible impact on tick time. You can also set a configurable retention period so the database stays lean even on busy long-running servers.

Q: Can I translate the UI for my community?

A: Yes. The script ships with multi-language support and full locale customization, so you can translate every player-facing string into whichever language your community plays in.

🚀 Stop Losing Staff Time to RDM Disputes

Every hour your moderators spend mediating he-said-she-said arguments is an hour stolen from actual roleplay. GFX Deathlog with Reports hands players a clear voice and your staff a clear paper trail, turning the most common complaint on any FiveM RP server into a documented, solvable problem. Drop it in tonight and watch your incident queue clean itself up.