AdvancedSensitiveWords vs BanManager

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.

BanManager is a free, open-source suite of moderation plugins and apps for Minecraft servers. It supports bans, IP blocks, mutes, profane-name blocking, and chat moderation that can include shadow muting. Players can report behavior while staff are offline, then staff can track and resolve reports. Configurable warning thresholds can trigger commands with increasing severity. Staff can add notes and review player records, including unbans and who issued them. Downloads are listed for Bukkit variants, BungeeCord, Fabric, Sponge, and Velocity. Data can be stored locally in H2 or remotely with MySQL or MariaDB. The optional self-hosted WebUI adds appeals, reports, role-based permissions, and a dashboard for one or more servers. That interface requires BanManager-WebEnhancer and MySQL 5+ or MariaDB 10+; the default H2 database is unsupported. Its setup page is initially unauthenticated, so the documentation recommends setting a setup token before exposing it to the internet. A developer API lets other plugins read or modify punishment data and receive change events.