ForkMuteManager: Smart Chat Moderation for Minecraft

Mastering Server Chat Control with ForkMuteManager Running a Minecraft server is a rewarding experience, but managing player behavior can quickly become a headache. Toxic language, spam, and disruptive chat can ruin the atmosphere for everyone. That is where a dedicated mute management plugin ste...

Download ForkMuteManager

Original name: ForkMuteManager

FileVersionLoaderSize
ForkMuteManager.jar——58 КБDownload

Mastering Server Chat Control with ForkMuteManager

Running a Minecraft server is a rewarding experience, but managing player behavior can quickly become a headache. Toxic language, spam, and disruptive chat can ruin the atmosphere for everyone. That is where a dedicated mute management plugin steps in, and ForkMuteManager delivers a robust, flexible solution that goes far beyond simple temporary silences. Whether you are an experienced admin or just setting up your first Spigot or Paper server, this plugin gives you the tools to keep conversations clean and your community happy.

What is ForkMuteManager?

ForkMuteManager is a server-side plugin originally forked from the classic MuteManager project, now maintained and enhanced with modern features. It allows staff members to mute individual players or entire groups for a specific duration, ranging from minutes to permanent silences. The plugin shines with its automated word filtering system, which can instantly mute, kick, or even ban players who use predefined bad words. Dynmap support, granular permissions, and a straightforward configuration file make it a must-have for any server that values order without constant manual moderation.

Key Features at a Glance

  • Timed and permanent mutes: Apply mutes using flexible time formats like 5m, 2h, 3d, or perm.
  • Automated actions on bad words: Configure a list of forbidden words with custom consequences — mute, kick, or ban — and set the duration.
  • Dynmap integration: Muted players can be visually marked on your server’s online map, giving everyone a clear heads-up.
  • Notification system: Staff with the right permissions receive alerts when a player is muted or unmuted.
  • Wildcard muting: Use * instead of a player name to mute or unmute all online players at once.
  • Reload command: Apply configuration changes without restarting the server.

Installation and Setup

Getting ForkMuteManager running is refreshingly simple. Just drop the jar file into your server’s plugins directory and restart the server. The plugin will generate a default configuration file and a wrongWords.txt file inside the plugins/ForkMuteManager folder. From there, you can tweak settings to match your server’s rules. If you are also a fan of modded Minecraft on the client side, you might find that the foxygame.net launcher streamlines your entire experience — it is a modern, flexible launcher where you can download mods directly from the menu, making it easy to jump between vanilla server administration and heavily modded singleplayer worlds without juggling multiple tools.

Permissions Overview

ForkMuteManager uses a clear permission node system to control who can issue mutes, view lists, and receive notifications. By default, most administrative nodes are assigned to operators, but you can adjust them for any rank using a permissions plugin like LuckPerms. Here are the essential nodes:

  • mutemanager.mute — Allows use of /mute (default: op).
  • mutemanager.unmute — Allows use of /unmute (default: op).
  • mutemanager.mutelist — Access to /mutelist to see currently muted players (default: op).
  • mutemanager.listen — If set to true, a player can still hear messages from muted players (default: false).
  • mutemanager.mutenotify — Receive notifications when someone is muted (default: op).
  • mutemanager.unmutenotify — Receive notifications when a mute is lifted (default: op).
  • mutemanager.reload — Allows /mutereload to refresh configuration (default: op).

Assigning mutemanager.listen to trusted players can be useful for moderators who need to monitor muted individuals without giving them full unmute powers. The notification nodes keep your staff team instantly informed, reducing the need to constantly check chat logs.

Commands and Usage

The command syntax is intuitive and flexible, making it easy to remember even during busy moderation moments. The core command is /mute, which accepts a player name (or * for all), an optional time parameter, and a reason. Time can be specified in minutes (m), hours (h), days (d), or as perm for a permanent mute. For example, to silence a player for five days with a reason, you would type:

/mute Steve 5d Spamming chat

To lift a mute, simply use /unmute Steve or /unmute * to clear all active mutes. The /mutelist command displays every currently muted player along with the remaining time and reason, giving you a quick overview. Finally, /mutereload applies any changes you made to the config or word list without downtime.

Automated Word Filtering: The Real Power

While manual muting is essential, the automated bad word system is what sets ForkMuteManager apart. The plugin reads a simple text file, wrongWords.txt, where each line defines a forbidden word, a reason, an action, and a duration in minutes. The format is straightforward:

badWord,reason,whatToDo,minutes

The whatToDo field accepts ban, kick, or mute (default is mute). If you omit the minutes, it defaults to 300 (five hours). Here is a practical example:

fvck,Inappropriate language,ban,180
sh1t,Watch your mouth,mute,90
goto my server,Advertising,kick

When a player types any of these exact words or phrases in public chat, the plugin instantly triggers the corresponding action. A ban removes the player from the server for the specified minutes, a kick ejects them, and a mute silences them for the duration. This automation drastically reduces the workload on your staff and catches offenders even when no moderators are online. The system is case-insensitive and matches whole words, so you can target specific slurs or common spam links with precision.

Configuration and Customization

The main config.yml file lets you fine-tune behavior. You can adjust the default mute duration, toggle Dynmap markers, and modify message formats. The plugin’s original source is available on GitHub under the truekenny repository, and the Bukkit project page provides historical context. Because ForkMuteManager is a direct fork, it inherits a stable codebase while adding the automute/kick/ban feature in version 1.0.2 and Dynmap support in 1.0.0. Always back up your configuration before updating to preserve your custom word list and settings.

Building a Healthier Server Community

ForkMuteManager is more than a simple mute tool; it is a proactive chat moderation system that adapts to your server’s unique rules. The combination of timed mutes, wildcard actions, automated word filtering, and Dynmap visibility creates layers of control that keep your community welcoming. By delegating permissions wisely and setting up a comprehensive bad word list, you can foster an environment where players focus on building, exploring, and collaborating instead of arguing. Whether you run a small survival world or a large minigame network, this plugin scales effortlessly and integrates into your existing moderation workflow. Take the time to configure it thoughtfully, and you will spend less time playing police and more time enjoying the game alongside your players.