Mastering Server Automation with the MessageCommander Plugin
Minecraft server administration often involves juggling multiple plugins, each with its own set of commands and messages. Sometimes a plugin sends a congratulatory message but lacks a built-in reward system, or you wish a simple chat phrase could trigger a complex command. This is where MessageCommander steps in, turning ordinary chat and console messages into powerful automation triggers. By linking specific text patterns to commands, you can extend the functionality of your existing plugins without touching a single line of Java code.
What Exactly Does MessageCommander Do?
At its core, MessageCommander watches the chat screen, server console, and log files for defined messages. When a match is found, it executes a command of your choice—either as the player who triggered it or as the server console. This opens up endless possibilities: granting in-game currency when a player completes a challenge announced by another plugin, turning friendly phrases like "please teleport me home" into the /home command, or even reacting to server log entries for automated maintenance tasks.
Why Your Server Needs This Plugin
Many popular plugins provide rich feedback through chat messages but stop short of linking those messages to actual rewards or actions. For instance, a minigame plugin might broadcast a victory message, but if it lacks an economy hook, you’re stuck. MessageCommander bridges that gap. You can set up a rule that listens for the victory message and then runs a command to give the player coins. Similarly, you can transform casual chat requests into functional commands, making your server feel more responsive and immersive without requiring players to memorize slash commands.
How the Magic Happens: Rule Definition Files
MessageCommander stores its automation logic in YAML files inside the MessageCommander/rules folder. Each file can contain multiple rules, and you can create as many files as you need to keep things organized. A single rule is defined by a set of parameters that tell the plugin exactly when and how to act.
For server owners who prefer a streamlined modding experience, the foxygame.net launcher provides a convenient way to download and manage plugins directly from its menu, making it a flexible modern Minecraft launcher that saves time when setting up a server.
Breaking Down the Rule Parameters
Every rule revolves around a few key settings. Understanding these will let you craft precise automations:
- Type – Determines how the plugin matches text. You have five options:
- EQUAL – Case-insensitive exact match (e.g., "Aaaa Bbbb" matches "aaaa bbbb").
- CONTAINS – Checks if the message includes a specific substring.
- START – Triggers when the message begins with the provided text.
- END – Triggers when the message ends with the provided text.
- REGEX – Uses regular expressions for complex pattern matching.
- Source – Specifies where the plugin should listen for messages. You can choose from:
- ALL – Any source (chat, console, log).
- CHAT_PLAYER – Messages typed by a player in chat.
- CHAT_CONSOLE – Commands entered in the server console.
- CHAT_MESSAGE – Any message received by a player (from plugins, mods, or other players).
- LOG – Messages in the server log, including plugin prefixes like [MessageCommander].
- message-mask – The text pattern the plugin looks for, based on the chosen type.
- command-line – The command to execute when a match is found. Use the placeholder
%player%to insert the triggering player’s name, and%word1%,%word2%, etc., to capture parts of the original message. - execute-as-console – Set to
trueif you want the command to run with server console privileges, bypassing player permissions. - cooldown-time – Prevents spam by setting a cooldown between rule executions, using a format like
3sfor three seconds.
A Practical Example
Imagine you want to respond whenever a player types “help me” in chat, no matter the capitalization. You could create a rule like this:
test:
type: EQUAL
source: ALL
message-mask: help me
command-line: say %player% need %word1%!
execute-as-console: true
cooldown-time: 3s
With this rule active, if a player says “help me”, the server will announce “PlayerName need help!” and then wait three seconds before the rule can fire again. The %word1% placeholder would capture the first word after the matched text, though in this exact-match scenario it might be empty—using CONTAINS or REGEX would let you extract more dynamic data.
Dependencies and Setup
MessageCommander requires ProtocolLib to be installed on your server, as it hooks into the network layer to intercept messages. There are no in-game commands or permissions to worry about—the plugin works silently in the background once your rule files are in place. An update checker runs every hour to notify you of new versions, but you can disable it by setting check-updates: false in the config.yml file if you prefer manual control.
Creative Use Cases for Your Server
The real power of MessageCommander shines when you start thinking outside the box. Link a chat-based quiz plugin to a reward command so correct answers earn players items. Convert a player’s “I’m stuck” into an automatic teleport request. Monitor the server log for crash-related keywords and trigger a backup script. The plugin’s regex support even lets you parse complex log entries and extract variables for your commands.
Because every rule is stored in plain YAML, you can easily share configurations with other admins or back up your setups. The cooldown system prevents abuse, and the ability to run commands as console ensures you can execute any admin-level task without giving players elevated permissions.
Final Thoughts
MessageCommander fills a unique niche in the Minecraft server ecosystem by turning passive message streams into active automation hubs. Whether you’re patching missing features in other plugins, creating a more natural chat-command interface, or building sophisticated log-driven workflows, this plugin offers a lightweight and flexible solution. With no complex permissions to manage and a straightforward YAML configuration, it’s accessible even to admins who shy away from heavy scripting. Give your server the gift of reactive intelligence—your players will notice the difference, even if they never see the gears turning behind the scenes.