PunishmentsSystem vs ReportsGUI

PunishmentsSystem is a self-hosted system for moderators managing player punishments. The /punish command applies configured reasons and durations, helping operators use consistent presets. When a case falls outside those presets, /manualpunish issues a punishment while ignoring them. Operators define reasons, punishment types, and durations for each offense step in the default config.json file. The documented punishment types are mute, ban, and kick. Moderators can use /check to view a player’s punishment history or find a punishment by ID. That command also allows a charge to be forgiven, while /unban provides an alias for forgiving bans. Punishments apply across IP addresses, and /checkip can find accounts associated with an IP or player. The project’s README says its Paper code is in the paper branch. The GitHub repository identifies the license as GPL-3.0. The maker describes it as easy to use. It is free and self-hosted.

ReportsGUI is a self-hosted Minecraft plugin for handling player reports and administering punishments. Staff can report, kick, ban, warn, mute or freeze players. The /reports command shows up to 54 unhandled reports, while /profile displays player information and lets staff issue punishments even without an active report. Team chat is available through /teamchat: logged-in staff can send staff-only messages using @tc or @teamchat. Staff must be logged into Teamchat to receive report and warning notifications and to manage reports and punishments. The listing identifies Minecraft 1.17 as the plugin’s native major version and provides a 422.5 KB JAR download. It says other languages can be used if users translate them themselves. A public GitHub repository is linked, with an invitation to fork, download and edit the project with credit to the author. ReportsGUI costs nothing. Its configuration has a specific limit: adding more than 27 report reasons will cause the plugin to break.