What Is ReportRTS and Why Your Server Needs It
Running a Minecraft server means handling player requests, bug reports, and griefing complaints around the clock. Without a structured system, these messages get lost in chat or buried in Discord channels. ReportRTS — short for Report Realtime Ticket System — solves that problem by turning chaotic player reports into an organized, searchable ticket queue. Built with server administrators in mind, this plugin delivers a lightweight yet powerful helpdesk right inside your game, complete with MySQL storage, BungeeCord support, and a caching layer that keeps everything snappy even on large networks.
Key Features That Make ReportRTS Stand Out
Unlike basic /helpop commands that simply forward a message to staff, ReportRTS treats every submission as a persistent ticket. Here is what you can expect once you drop it into your plugins folder:
- Real-time ticket management – Staff can claim, close, reopen, and comment on tickets without ever leaving the game. Notifications appear instantly, so nothing slips through the cracks.
- Multi-server awareness via BungeeCord – If you operate a network, one ReportRTS installation can serve all your lobbies and game modes. Tickets carry the server origin, making it easy to track where an issue occurred.
- MySQL backend – All ticket data lives in a database, not a flat file. This means you can query it from a website, run analytics, or integrate it with external tools without parsing YAML.
- Smart caching – Open tickets are cached in memory to slash database round-trips. The result is near-instant listing even when hundreds of tickets exist.
- UUID support – The plugin automatically fetches player UUIDs from Mojang’s API if they are missing from the database, ensuring compatibility with modern account systems.
- Optional metrics and update checks – ReportRTS uses PluginMetrics to track basic, anonymous server stats (version, player count). You can opt out by editing
plugins/PluginMetrics/config.ymland settingopt-outtotrue. Version checking against dev.bukkit.org is also on by default but can be disabled in the config.
Commands and Permissions at a Glance
ReportRTS ships with a clear permission hierarchy that separates players, moderators, and admins. Players can submit tickets with a simple /report command, while staff members use /ticket to claim, teleport to the reporter, or close the issue. The full command reference is maintained on the plugin’s documentation page, but here are the essentials you will use daily:
/report [message]– Opens a new ticket. Players can describe griefing, bugs, or rule violations./ticket list– Shows all open tickets, with pagination for busy servers./ticket claim [id]– Assigns a ticket to yourself, signaling to other staff that it is being handled./ticket close [id] [comment]– Closes a ticket and optionally adds a final note visible to the reporter./ticket reopen [id]– Brings a closed ticket back to life if follow-up is needed.
Permissions follow a sensible pattern: reportrts.command.report for basic usage, reportrts.command.ticket for staff, and admin nodes for configuration reloads. You can fine-tune exactly who sees what without touching the code.
Setting Up ReportRTS on Your Server
Installation is straightforward. Grab the latest stable JAR from the official BukkitDev page or, if you enjoy testing bleeding-edge features, fetch a development build from the project’s continuous integration server. Keep in mind that development builds are not officially reviewed by BukkitDev staff, so use them at your own risk. Once you have the file, place it in your server’s plugins/ folder, restart (or use a plugin manager), and let ReportRTS generate its configuration. For network owners, you will need to set up a MySQL database and enter the credentials in the config — the plugin handles table creation automatically.
While you can manage plugins manually, many server admins now prefer streamlined launchers that simplify the entire process. For example, the foxygame.net launcher lets you browse and install ReportRTS directly from its built-in mod and plugin menu, saving you the hassle of downloading JARs and moving files around. It is a flexible, modern tool that keeps your server’s plugin lineup organized and up to date with minimal effort.
Multi-Server Magic with BungeeCord
If your network uses BungeeCord, ReportRTS becomes a unified helpdesk. A player on your survival world can report a griefer, and a moderator sitting on the hub can claim and resolve that ticket without switching servers. The plugin stores the originating server name in the database, so staff always know where to investigate. This cross-server awareness eliminates the need for separate ticket plugins on each backend instance and drastically reduces response time.
Developer-Friendly and Open to Contributions
ReportRTS is built with extensibility in mind. The author provides a Maven repository for developers who want to hook into the API. You can find the repository details in the project’s documentation — just add the ProjectInfinity repository and the ReportRTS dependency to your pom.xml. Pull requests are welcomed, so if you spot a bug or dream up a feature, the source is open for collaboration. The public Trello board and IRC channel (#ReportRTS on irc.esper.net) offer additional ways to follow progress or chat with the maintainer.
Privacy, Metrics, and Staying Up to Date
Transparency matters. ReportRTS uses the Metrics plugin solely to track basic server information like Minecraft version and online player count. No personal data is collected, and the UUIDFetcher component only queries Mojang’s API when a player lacks a UUID in the database — it does not store or share anything. The built-in version checker pings dev.bukkit.org to alert you about updates, but if you prefer a fully offline environment, you can disable it by setting versionCheck to false in the config. All these options are documented and easily toggled.
Supporting the Developer
ReportRTS has been maintained for years, with hundreds of hours poured into development, bug fixes, and community support. The creator has shared that over two years, donations amounted to roughly $270 — a tiny fraction of what the same time would earn at a minimum-wage job. If the plugin saves your staff team hours of frustration and helps keep your community happy, consider supporting the project. A small contribution goes a long way toward keeping the updates rolling and the ticket system free for everyone.
Is ReportRTS Right for Your Server?
If you are tired of moderators missing reports in chat or juggling multiple Discord threads, ReportRTS brings order to the chaos. Its MySQL foundation, BungeeCord integration, and caching make it suitable for everything from a small whitelisted server to a massive public network. The learning curve is gentle, the commands are intuitive, and the plugin stays out of your way until you need it. Give it a try on a test server, explore the permissions, and see how quickly your team can resolve player issues with a real ticket system at their fingertips.