POGGY TICKETS πŸ›ŽοΈ [FREE] Player Tickets, Staff Panel, Warn Kick Ban and Discord

POGGY TICKETS πŸ›ŽοΈ [FREE] Player Tickets, Staff Panel, Warn Kick Ban and Discord

This item is free.

Add to Basket

🌐 See it on our store: rosewoodridge.xyz/store/poggy-tickets

πŸ“Ί Watch the trailer

A ticket desk for your RedM server: players ask for help with one key, staff claim it in a live panel, and every ticket lands in Discord. Warn, kick and ban are built in, with or without a ticket.

πŸ™‹ For players

  • Page Up or /ticket. Two big buttons: I need help right now, or Send a ticket
  • I need help right now is one press: no form, no ticket. It calls staff to where you are
  • The form is radio buttons, not dropdowns: what it is about, how urgent, what happened
  • Reporting someone? Pick them from the players near you (100 m, nearest first). Owners can switch the list to everyone online, or to server ids only
  • An optional video link, and the form says why a clip helps
  • Your position is saved with the ticket
  • No staff on? You are told, and the ticket is saved for when they are
  • A small pop-up with a sound when staff take, answer or close your ticket. News you missed is waiting when you log in
  • My tickets: read the conversation and reply, like a chat

πŸ›ŽοΈ For staff

  • /tickets or Page Down. A large window, not a full-screen takeover
  • Ticket ages count up live. Online players are green; offline are grey and dimmed
  • Every kind of ticket has its own colour, and every priority. Filter by state, kind, priority, online only; search anything
  • Claim a ticket so one person works it, assign it to someone else, or change its kind and it moves to the right staff
  • A chat with the player. The chat scrolls inside itself and the action bar stays put
  • Go to player or go to the ticket's location in one press. You arrive a few metres behind them, invisible and unable to be hurt. Return takes you back; /invis toggles it by hand
  • A claimed ticket whose staff member logged off frees itself after 15 minutes
  • Duty is on by default and is never saved: relog and you are back on duty, so nobody misses tickets by forgetting

πŸ‘₯ Four roles, routed by kind

  • Admin sees and does everything, including bans, adding staff and the audit trail
  • Mod: cheater, player report, help, stuck and other tickets; can warn and kick
  • Helper: help and stuck tickets
  • Developer: bug and other tickets
  • Roles are on the account, so they cover every character. One person can hold several
  • Add staff in the panel: search any character, online or not. Anyone your framework counts as an admin is an Admin from the first start
  • The kinds of ticket and who sees each are yours to change

πŸ”¨ Warn, kick, ban: with or without a ticket

  • On a ticket that names a player, or from the Players menu: /mod, the Players tab, or a button in /poggy
  • The Players menu shows everyone online and, for the one you pick, their record: warnings, bans, and every ticket they sent or were reported in
  • Warn is a full-screen warning the player must acknowledge. They cannot be hurt while it shows. Offline? It waits for their next login
  • Ban is on the account, so it follows them across characters, and it works on someone who has already left. Lifting a ban keeps the record
  • Every one needs a reason. The reported player is never told who reported them
  • Bans belong to poggy_core, so they keep working even if this script is stopped

πŸ“œ An audit trail admins can read

  • Everything staff did: claims, replies, teleports, invisibility, warns, kicks, bans, roles
  • A timeline grouped by day, one sentence per action, filtered by area, by person, or down to one ticket

πŸ’¬ Discord

  • Paste a channel webhook. Each ticket is one post: red when open, amber when claimed, green when closed, with who closed it and how long it took
  • The post is edited, never deleted. A different channel per kind of ticket if you want
  • Player text can never ping anyone

🌐 The Poggy ban network

Part of poggy_core 0.20.0. A ban you mark as cheating is shared with other servers running poggy_core, as one vote; a player with votes from three servers is refused on all of them. Rule-break bans never leave your server. Only scrambled identifiers are shared: no names, no reasons. It is on by default, and both halves (refusing network-banned players, sharing your cheating bans) can be switched off in /poggy. Mods and admins get a pop-up when someone joins who is banned for cheating on one or two other servers.

βš™οΈ Built for your server

  • Change every setting in game with /poggy, or edit config.lua, which has a comment on every line
  • Every command name and both keys are in the config. Every string a player sees is in translations.lua
  • Closed tickets are kept forever by default, or purged after a number of days

πŸ”„ Updates itself

Runs on poggy_core (free): updates install automatically, and your config and translations are merged so your values survive. The database tables are created on the first start, so there is no SQL to import.

πŸ“‹ Requirements

  • poggy_core 0.19.0 or newer (free); 0.20.0 for the ban network and the /poggy Players button
  • VORP Core, RSG Core or QBCore RedM (QBR)
  • oxmysql
  • OneSync, for Go to player

πŸ”“ Open where it matters

config.lua and translations.lua are readable and editable. The rest is escrowed.

Questions? Join the Poggy Scripts Discord.