Overview
LenoReports provides an in-game ticket system for players and staff. Reports, messages, participant snapshots, and history are stored in the server database.
Features
| Area | Purpose |
|---|---|
| Player reports | Create a ticket with category, subject, description, and involved players |
| Staff queue | Review open reports grouped as Mine, Unclaimed, and Others |
| Ticket workflow | Claim, unclaim, chat, manage participants, and close reports |
| Player snapshots | Capture player data for investigation, including players near the author |
| Screenshots | Capture evidence with screenshot-basic and upload through the configured Discord images webhook |
| Staff actions | Goto, bring, freeze, and unfreeze when enabled |
| Staff chat | A separate staff conversation, mentions, and an on-duty roster |
| History | Closed reports for staff and the player's own authored reports |
| Statistics | Report counts, response/resolution metrics, and staff activity for today, 7 days, 30 days, or 6 months |
| Integrations | Public exports, server lifecycle events, and editable hooks |
Frameworks and identity
| Framework | Resource | Persistent player identity |
|---|---|---|
| ESX | es_extended | ESX identifier |
| QBCore | qb-core | Citizen ID |
| QBox | qbx_core | Citizen ID |
Config.Framework = 'auto' selects a supported framework that has already started. Server IDs are used to select online players; they are different from the persistent identifiers used to store reports.
Inventory and notification adapters are listed in Dependencies, with current integration limitations in Customization.
Where to start
- Server owners: Installation, Configuration, and Customization.
- Players and staff: User Guide and Commands.
- Developers: Exports and Events.
- Problems during setup: FAQ / Troubleshooting.