Free RedM Ticket and Report Script Poggy Tickets

A free RedM ticket and report system for VORP Core, RSG Core and QBCore RedM: players ask for help with one key, staff claim tickets in a live panel, and warn, kick and ban work with or without a ticket. Every ticket is one Discord post, edited as it moves.

What players can do

• Page Up or /ticket opens two buttons: I need help right now (one press, no form, calls staff to them) or Send a ticket.
• Six kinds: Bug, Cheater, Player report, Help, Stuck or lost items, Other.
• A report names a player picked from those within 100 metres, with an optional video link.
• While they type, the form offers matching solved questions, and it shows the usual wait.
• A pop-up with a sound says when staff take, answer or close their ticket. They reply in a chat-style conversation.

What staff get

• /tickets or Home opens a large panel: live ticket ages, online players in green, a colour per kind and priority, filters and search.
• Claim, assign, or change the kind so it reaches the right staff.
• Escalate brings another role in without taking the ticket off its owner.
• Internal notes are removed on the server before anything reaches the player.
• Ready-made replies, the best match offered first.
• Go to player puts you behind them, invisible and unable to be hurt. Return takes you back.
• Mark the answer and make a closed ticket public: it joins the solved questions with every name hidden.
• A staff chat room per role, never saved.
• An audit timeline for admins.

Staff roles you write yourself

• Admin, Mod, Helper and Developer to start. Rename, colour and add your own.
• Per role, tick its powers (18), which kinds of ticket it sees and whose staff chat it reads.
• Admin is locked, so nobody can lock the team out. Anyone your framework counts as an admin holds it.

Warn, kick and ban

• /mod opens the Players menu: everyone online, with their warnings, bans, staff notes and tickets.
• The ladder suggests the next step; warnings stop counting after 90 days by default.
• Bans are poggy_core account bans: they follow the player across characters and still apply if this script is stopped.
• A ban ticked as cheating can feed the shared ban network in poggy_core.

Commands

Every command name and both keys can be changed.

Settings you will change first

• Config.Discord.Webhook: red when open, amber when claimed, green when closed.
• Config.PlayerList: nearby, all or ids.
• Config.NudgeAfterHours / Config.AutoCloseAfterHours: 24 and 48.
• Config.PurgeClosedAfterDays: 0 keeps closed tickets forever.

Archiving destroys nothing. Deleting an archived ticket needs the poggy_tickets.delete ACE in server.cfg, so no admin can quietly erase a conversation.

Tickets in a browser (poggy.app/tickets) are off by default. Turned on, copies of open tickets are held on a relay run by the script's author, for 7 days after closing; read the note in config.lua first.

What you need to run it

• VORP Core, RSG Core or QBCore RedM (QBR).
• poggy_core 0.27.0 or newer (free).
• oxmysql, and OneSync for Go to player.
• No SQL to import.
• config.lua and translations.lua are open; the rest is escrowed.

Updates

poggy_core installs each new version and merges your config and translations, so your values stay.