Suty
Report System

Installation

Installation

1. Drop the resource

Extract suty-reportes into resources/[suty]/suty-reportes.

2. Ensure in server.cfg

ensure ox_lib
ensure oxmysql
ensure screenshot-basic    # optional, only if Config.Screenshot = true
ensure suty-reportes

3. Database

Tables are created automatically on first start. Verify:

SHOW TABLES LIKE 'suty_reports%';

4. Set framework and locale

config.lua:

Config.Framework = 'qbx'    -- 'qbx' | 'qb' | 'esx'
Config.Locale    = 'es'     -- 'es' | 'en'

5. Grant admin permissions

Any group in Config.AllowedGroups can view + manage reports. Default:

Config.AllowedGroups = { 'admin', 'god', 'mod' }

Make sure your admins have one of these ACE groups.

6. Configure revive method

config.lua:

Config.ReviveMethod = 'suty-ems'    -- 'qb-ambulancejob' | 'qbx_medical' | 'suty-ems' | 'wasabi_ambulance' | 'custom'

For custom, fill out Config.ReviveCustom with your own export or event.

7. Discord webhook (optional but recommended)

Config.ScreenshotWebhook = 'https://discord.com/api/webhooks/...'
Config.NoAdminDiscordUrl = 'https://discord.com/channels/SERVER/CHANNEL'

The first uploads screenshot attachments. The second is shown to players when no admins are online (fallback to file a Discord ticket instead).

8. Verify

  • Player: /calladmin — opens the report dialog
  • Admin: a pending-counter badge appears in the corner (style set by Config.AdminBadge); click or run the admin command to open the queue