RX Reports V1 Installation

RX Reports V1 is a QBCore and ESX report workflow with a persistent staff dashboard, report history, screenshots, player blocks, live chat, and post-resolution feedback.

Requirements

RequirementWhy it is needed
oxmysqlSaves reports, screenshots, history, feedback, blocks, and notes.
qb-core or es_extendedSupplies player data, commands, permissions, and notifications.
screenshot-basicCaptures report screenshots and uploads them to the configured webhook.
Discord webhookReceives screenshot uploads when players attach evidence.

1. Import the database

Import reports.sql into the same database used by your server. It creates the report, screenshot, feedback, block, and player-history tables.

Import the SQL before starting the resource for the first time. Do not import it into a different database connection from oxmysql.

2. Set the framework and admin permissions

Open config.lua and choose your framework:

Config.Framework = 'qb' -- or 'esx'

Then configure admin access in permission.lua before staff use /reports:

  • QBCore checks the licenses listed in Config.AdminLicenses.
  • ESX checks each player’s group against Config.AdminGroups.

Continue with Configuration for the full permission setup.

3. Add resources to server.cfg

Start dependencies first, then start RX Reports. setr screenshot_webhook must contain the Discord webhook used for screenshot uploads.

cfg 
ensure oxmysql
ensure qb-core
ensure screenshot-basic
setr screenshot_webhook "https://discord.com/api/webhooks/your-webhook"
ensure ripex-reportsystem

If you renamed the resource folder, replace ripex-reportsystem with that exact folder name.

4. Verify the flow

After a restart, test these paths with a non-admin and an admin account:

  1. A player opens /report and submits a report.
  2. An authorized staff member opens /reports and claims it.
  3. Capture a screenshot attachment to confirm the webhook and screenshot-basic work.
  4. Close the report and use /feedback on the player account.

Never expose the webhook in screenshots, Git repositories, or public config files.