AdvancedSensitiveWords vs PunishmentsSystem
AdvancedSensitiveWords
github.comPunishmentsSystem
github.comSide by side
| Figure | AdvancedSensitiveWords | PunishmentsSystem |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 0 |
| Spec score · Minecraft Moderation Plugins | 7.5 (#6) | 6.5 (#12) |
| License | The project is licensed under GNU AGPL-3.0. | The repository displays a GPL-3.0 license. |
| Purpose | AdvancedSensitiveWords is a Paper moderation plugin using DFA word matching, event-based content inspection, modular violation levels, and optional LLM-assisted chat review. | Punishment System is described as an easy-to-use punishment system. |
In their own words
AdvancedSensitiveWords
AdvancedSensitiveWords is a free, open-source moderation plugin for operators of Minecraft servers running Paper. It inspects content through DFA word matching and event-based checks across chat, commands, writable books, signs, anvil results, item names and lore, player names, and optionally broadcasts. Operators can replace or cancel matched content and configure responses such as commands, damage, effects, hostile behavior, or shadowbans. Version 2.x targets Paper 1.21.11 and requires Java 21; installation involves placing a released or locally built Paper artifact in the server’s plugins directory. Optional LLM chat review is off by default and uses a compatible provider and API key to assess messages missed by the other checks. Length, entropy, cooldown, concurrency, and queue safeguards apply. Requests and responses are recorded locally in an llm-history directory identified as sensitive operational data. Optional integrations include Velocity, TrChat, PacketEvents, PlaceholderAPI, Floodgate, and AuthMe. Velocity support handles notifications and proxy commands, not chat filtering. The project is licensed under GNU AGPL-3.0.
PunishmentsSystem
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.