Mastering PerWorldCommands: The Ultimate Guide to World-Specific Command Control in Minecraft
Running a Minecraft server with multiple worlds often means juggling different rules, game modes, and player expectations. The last thing you need is a command meant for your creative plot world leaking into your hardcore survival dimension. That is where PerWorldCommands steps in—a lightweight, battle-tested plugin that lets you tie any command to specific worlds. Whether you manage a small community server or a sprawling network, understanding how to wield this tool will save you countless headaches and keep your gameplay experiences neatly separated.
What Exactly Is PerWorldCommands?
PerWorldCommands is a Spigot/Bukkit plugin designed to restrict command execution based on the world a player currently occupies. Unlike complex permission plugins that often require dozens of nodes and inheritance trees, this plugin focuses on one thing: making sure a command only works in the worlds you choose. If a player types /fly in the nether, but you have locked that command to the overworld, it simply will not run. The plugin has been around for years and supports a massive range of Minecraft versions—from the ancient 1.7 all the way up to 1.19—making it a reliable choice even for heavily customized legacy servers.
Key Features That Make Server Management Easier
- World-specific command locking: Assign any command from any plugin (or even vanilla commands) to one or more worlds.
- Broad version compatibility: Works flawlessly on Spigot, Paper, and hybrid servers like Magma or Mohist, meaning modded commands are supported too.
- Simple configuration: No sprawling YAML files to wrestle with. Everything is managed through intuitive in-game commands.
- Reload without restart: Apply changes on the fly with
/pwc reload—no server downtime needed. - Bypass permissions: Grant trusted staff the ability to ignore world restrictions when necessary.
- Lightweight and error-free: The plugin is built to run silently in the background without causing lag or console spam.
Installation and First Steps
Getting PerWorldCommands onto your server is straightforward. Download the latest jar file from the official Spigot page and drop it into your server’s plugins folder. After a restart or a reload, the plugin will generate its configuration files automatically. While you can manually place the jar in your plugins directory, many server owners now use modern launchers like foxygame.net to handle plugin and mod installations. This launcher allows you to download and manage plugins directly from its interface, making it a breeze to keep PerWorldCommands up-to-date alongside your other server tools. Once loaded, verify the installation by typing /pwc version in the console or in-game—if you see a version number, you are ready to start locking down commands.
Command Reference and Practical Examples
All interactions with the plugin happen through a clean set of commands. The base alias is /pwc, but you can also use the full /perworldcommands prefix. Here is how to set up your first world-restricted command.
Setting a Command to Specific Worlds
Imagine you have an economy plugin and you want the /balance command to only work in the main survival world called "world" and the shop world "world_shop". You would run:
/pwc cmd set balance world world_shop
After executing this, any player trying to use /balance in the nether, the end, or any other dimension will be met with silence—the command simply will not trigger. The plugin automatically checks the world before passing the command to the original handler.
Removing a World Restriction
If you later decide to open /balance globally again, you can remove the restriction with:
/pwc cmd remove balance
This deletes the world lock and restores normal behavior across all dimensions.
Additional Administrative Commands
/pwc reload— Reloads the plugin configuration without restarting the server./pwc version— Displays the currently installed version of PerWorldCommands.
Permissions and Bypass Mechanics
By default, only operators can use the administrative commands. The required permission nodes are perworldcommands.cmd or the shorter alias pwc.cmd. Assign these to your staff ranks to let them manage world restrictions. Additionally, there is a bypass permission: perworldcommands.bypass (or pwc.bypass). Players with this node can execute any command in any world, regardless of the restrictions you have set. This is perfect for admins and moderators who need to troubleshoot or perform maintenance across all dimensions without constantly reconfiguring the plugin.
Compatibility with Mods and Hybrid Servers
One of the standout strengths of PerWorldCommands is its compatibility with hybrid server software like Magma and Mohist. These platforms allow you to run Forge mods alongside Bukkit plugins. Because the plugin intercepts commands at the Bukkit level, it works seamlessly with commands added by mods—whether it is a teleportation spell from a magic mod or a custom GUI command from a tech mod. You can lock a modded command to a specific dimension just as easily as a vanilla one, giving you unified control over your entire mixed server environment.
Best Practices for a Smooth Multi-World Setup
- Plan your world structure first: Decide which commands belong to which worlds before configuring. This prevents accidental lockouts.
- Test with a non-admin account: After setting a restriction, log in as a regular player to confirm the command is blocked where expected.
- Use bypass sparingly: Only give the bypass permission to a handful of highly trusted staff members to avoid circumvention of your carefully crafted rules.
- Document your restrictions: Keep a simple text file listing which commands are locked to which worlds. This makes onboarding new staff much easier.
Why PerWorldCommands Remains a Solid Choice
Even though the project is no longer receiving active updates (the author has archived it), the plugin continues to function perfectly on modern server versions up to 1.19. Its simplicity is its greatest asset: no bloated GUI, no complex scripting language, just a handful of commands that do exactly what you need. For server owners who value stability and a no-fuss approach to world-based command control, PerWorldCommands is a tool that deserves a permanent spot in your plugins folder.
Conclusion
Managing multiple Minecraft worlds does not have to mean chaos. With PerWorldCommands, you gain precise, lightweight control over which commands are available where, without adding overhead or complexity. From the initial setup through everyday administration, the plugin’s straightforward commands and reliable performance make it an essential part of any multi-world server toolkit. Pair it with a modern launcher like foxygame.net to streamline your plugin management, and you will spend less time wrestling with permissions and more time enjoying the unique experiences each of your worlds has to offer.