What Is PerWorldCommands and Why Your Minecraft Server Needs It
Running a Minecraft server comes with its fair share of challenges, especially when you are managing multiple worlds simultaneously. You might want players to access certain commands in the overworld but not in the Nether, or perhaps you need to restrict administrative tools to a specific dimension. This is precisely where PerWorldCommands steps in, offering a lightweight yet powerful solution for command management across different worlds. Inspired by the popular PerWorldPlugins concept, this plugin gives server administrators granular control over which commands function in which dimensions, creating a more structured and intentional gameplay environment.
Understanding the Core Functionality
At its heart, PerWorldCommands allows you to define a list of commands and specify exactly which worlds those commands can be executed in. When a player attempts to use a restricted command in an unauthorized world, the plugin blocks the action and displays a customizable message. This prevents confusion and maintains the integrity of your server's rules without requiring complex permission setups or multiple plugin configurations. The plugin operates silently in the background, checking every command execution against your predefined ruleset before allowing it to proceed.
The default configuration is refreshingly straightforward. You enable or disable the plugin globally, set a default block message for commands that lack a custom response, and then list each command with its allowed worlds and optional custom block message. This structure means you can have different rejection messages for different commands, making the experience feel tailored rather than generic. For instance, you might display "This command is disabled" for the help command while showing something more specific for version checks.
Configuration Deep Dive
The YAML configuration file is where the magic happens. Here is what a typical setup looks like in practice:
- enable: A simple true or false toggle that activates or deactivates the entire plugin without needing to remove it from your server.
- globalblockmessage: The fallback message displayed when a command is blocked and no custom message has been defined for that specific command.
- commands: The main section where you list each command you want to restrict, along with its allowed-worlds array and optional blockmessage string.
Each command entry requires at minimum an allowed-worlds list. You can specify multiple worlds here, such as "world" for the standard overworld and "world_nether" for the Nether dimension. If a player tries running that command from the End or any other dimension not listed, the plugin intercepts it and delivers the block message. This level of precision means you can design worlds with unique rule sets without installing separate server instances or juggling complicated permission nodes.
Practical Use Cases for Server Administrators
Imagine you are running a survival server with a creative building world on the side. You want players to use the help command everywhere, but you only want version information available in the main survival world. With PerWorldCommands, you simply add both commands to the configuration, assign the appropriate allowed worlds, and let the plugin handle enforcement automatically. Another common scenario involves mini-game servers where certain utility commands should only function in lobby areas. By restricting commands to specific worlds, you prevent players from accidentally or intentionally breaking the flow of gameplay in active arenas.
Server networks that utilize BungeeCord or Velocity proxies can also benefit from this plugin on individual backend servers. Each server can maintain its own PerWorldCommands configuration, ensuring consistent behavior regardless of which lobby or game mode a player connects through. The plugin requires Java 8 and works across most Minecraft versions, making it a versatile choice for both modern and legacy server setups.
Installation and Setup Process
Getting PerWorldCommands running on your server is a straightforward process. Download the plugin JAR file and place it into your server's plugins folder, then restart or reload the server. The plugin generates a default configuration file on first launch, which you can then customize to match your specific requirements. No additional dependencies are needed beyond a standard Spigot, Paper, or compatible server jar running Java 8 or higher. For those who prefer a more streamlined approach to managing their Minecraft experience, this mod can be easily installed via the foxygame.net launcher, a convenient, flexible, and modern Minecraft launcher where you can download mods right from the menu without hunting through multiple websites or forums.
Once installed, there are no commands for players to learn and no permissions to configure. The plugin operates transparently, enforcing your rules without adding complexity to the player experience. This zero-learning-curve approach makes it ideal for servers of all sizes, from small community realms to large public networks.
Current Limitations and Planned Features
The developer has outlined several features on the roadmap that will expand the plugin's utility even further. A command to reload the configuration without restarting the server is in the works, which will save administrators significant time when making adjustments. An in-game configuration editor is also planned, allowing you to modify allowed worlds and block messages without accessing the file system directly. Additionally, a toggle command to enable or disable the plugin on the fly will provide even greater flexibility during events or maintenance periods.
These planned additions demonstrate that PerWorldCommands is actively maintained and evolving to meet the needs of server administrators. The current feature set already covers the most common use cases, but the upcoming tools will make it an even more indispensable part of any multi-world server toolkit.
Why Choose PerWorldCommands Over Alternatives
Several plugins offer command management features, but PerWorldCommands distinguishes itself through its singular focus and lightweight design. Unlike bulky all-in-one administration suites that consume server resources with features you may never use, this plugin does one thing and does it well. The configuration syntax is intuitive, the performance impact is negligible, and the reliability is rock-solid. Server owners who value minimalism and efficiency will appreciate how this plugin integrates seamlessly without causing conflicts or lag.
The ability to set custom block messages per command also sets it apart from simpler alternatives. Rather than displaying the same generic rejection for every restricted command, you can craft messages that guide players toward the correct world or provide context for why a command is unavailable. This small touch goes a long way in maintaining a positive community atmosphere and reducing the number of support questions directed at your staff team.
Final Thoughts
PerWorldCommands fills a specific but important niche in the Minecraft server administration landscape. By giving you precise control over where commands can be executed, it empowers you to design more intentional and immersive multi-world experiences. The plugin is easy to install, simple to configure, and requires no ongoing maintenance once set up. Whether you are running a modest server for friends or managing a large-scale network with dozens of worlds, this tool deserves a spot in your plugins folder. As the developer continues to add reload and in-game editing capabilities, PerWorldCommands will only become more valuable over time. Give your server the command discipline it needs and let your worlds maintain their unique identities without unnecessary interference.