ReportsGUI

ReportsGUI is a free, self-hosted Minecraft plugin for teams that need report intake, private staff communication, and player punishments in one in-game workflow. It is most suitable for small to mid-sized server staffs that can work within its command-based design. The main trade-offs are a strict 27-reason configuration limit and the requirement that moderators stay logged into Teamchat for notifications and report handling.

Overview

ReportsGUI brings the central moderation cycle into the server: staff can review player reports, investigate profiles, and apply disciplinary actions without moving to a separate service. Supported actions include kicking, banning, warning, muting, and freezing players, alongside the ability to submit reports. That range covers routine enforcement as well as more immediate interventions.

The plugin is self-hosted, so deployment stays with the Minecraft server rather than a hosted dashboard. Its public GitHub repository also permits users to fork, download, and edit the project with credit to the author. That is useful for technically capable administrators who want to adapt the plugin, but it places customization and maintenance on the server owner.

Key features

Report queue and direct moderation

Running /reports shows up to 54 unhandled reports. This gives a compact team a clear queue, but the fixed display ceiling can become restrictive when a busy server accumulates more cases than staff can process promptly. The /profile command displays player information and lets staff punish someone even when no active report exists, supporting action based on observed behavior or an established history.

Teamchat workflow

Staff use /teamchat to log in or out, then send private messages with @tc or @teamchat. Report and warning notifications, as well as report and punishment handling, require the moderator to be logged into Teamchat. This creates a defined staff-only channel, but it also makes login status a dependency: a moderator who is not logged in can miss the workflow's notifications.

Configuration and localization

The listing warns that adding more than 27 report reasons will break the plugin. Servers with a short, stable reason list can plan around that boundary; communities wanting a detailed taxonomy of offenses should look elsewhere or keep their categories deliberately broad. Any language can be supported if the administrator performs the translation, offering flexibility for multilingual servers while requiring their own localization work.

Pricing

There is no trial period because the plugin is free, and there is no paid tier or renewal term to budget for. The practical limits are technical rather than commercial: the queue shows up to 54 unhandled reports, and the configuration warning caps report reasons at 27 before the plugin breaks.

Platforms

ReportsGUI is self-hosted and identified with Minecraft 1.17 as its native major version. SpigotMC lists version 1.0, released and last updated on April 12, 2023. Distribution is a 422.5 KB JAR download. Servers on a different Minecraft major version should confirm compatibility before making it their moderation foundation.

Who it's for

This is a sensible fit for Minecraft server owners who want a free, server-side moderation console with a finite report queue and built-in staff chat. It works best when staff can consistently use Teamchat and the server's report categories fit within 27 reasons. It is less appropriate for large or highly customized communities that need a deeper reason hierarchy, a queue beyond 54 visible unhandled cases, or a workflow that does not depend on moderator login state.

Pros and cons

Pros

• Broad enforcement commands: reporting, kicking, banning, warning, muting, and freezing cover common staff responses.
• One in-game workflow: report review, private staff messages, and direct profile-based punishments stay inside the server.
• Free self-hosting: there is no subscription cost, hosted account, or renewal commitment.
• Editable project: the public repository gives capable administrators a route to fork and modify the plugin.

Cons

• 27-reason ceiling: exceeding it can break the plugin, limiting detailed moderation taxonomies.
• 54-report display limit: only up to 54 unhandled reports appear through /reports at once.
• Teamchat dependency: notifications and handling require staff to be logged in, adding an operational step.
• Older version target: the native major version is Minecraft 1.17, and the listed release has not been updated since April 2023.

Alternatives

For a wider comparison of server-side moderation tools, see Minecraft Moderation Plugins.

• ModGUI is another free, self-hosted option, licensed under MIT for Paper 1.21.11 or newer; choose it when that newer Paper baseline and license matter more than ReportsGUI's 1.17 target.
• LibertyBans is free software for API and self-hosted use and requires Java 17; pick it when broader supported Minecraft server platforms are the priority.
• Nimbus AntiCheat is free and self-hosted, combining 43 checks with per-check punishments, player reports, staff inspection tools, and Discord webhook notifications; choose it when anti-cheat coverage and Discord alerts are central.
• Staff+ is a free MIT-licensed self-hosted choice for Paper, Purpur, and Folia 1.20–1.21+, plus Velocity 3.3.0+; select it for that multi-platform modern-server range.
• ExtraBan is a free self-hosted plugin for Paper or a fork at 26.2+ with Java 25+; it suits servers already operating on that newer runtime.
• Player Report is a free self-hosted Minecraft plugin with native/tested major version 1.21; choose it when that version target is a better match.
• BanManager is a free, open-source option spanning API, Linux, self-hosted, and web deployments; pick it when a web-capable administration setup is preferable.
• PunishBAN is a free self-hosted alternative for servers seeking a different punishment plugin.

Verdict

Choose ReportsGUI if you run a Minecraft server whose staff want free, in-game report handling, Teamchat, and direct punishments, and whose categories fit within 27 reasons. Look elsewhere if your queue regularly exceeds 54 unhandled reports, your staff cannot reliably maintain Teamchat login, or you need a current version target and extensive customization.