AxY's Plugin Disabler
Server owners spend hours fine-tuning permissions, only to discover that a single plugin is still causing chaos in one corner of the world. Maybe WorldEdit is being abused at spawn, or an economy plugin is quietly ruining the balance of your PvP arena. AxY's Plugin Disabler solves that problem by letting you carve out 3D regions where specific plugins are completely switched off for anyone standing inside them. Think of it as WorldGuard flags, except the flag controls an entire plugin rather than a single command.
What This Plugin Actually Does
The concept is refreshingly simple. You define a region, then toggle installed plugins on or off for that region. Players inside the zone lose access to the blocked plugin's functionality, while everyone outside carries on as normal. Want a spawn area where WorldEdit, VoxelSniper, and schematic tools do nothing? Done. Need a tournament arena where teleport, home, and economy commands are frozen for the duration of an event? Also done.
Because the add-on works at the plugin level rather than hooking into individual APIs, there is no per-plugin configuration to write. If a plugin appears in your server's plugin list, it appears in the toggle menu. That means it plays nicely with almost anything you have installed, including niche plugins that never bothered to expose their own region flags.
Supported Versions and Platform
AxY's Plugin Disabler targets modern servers only, which keeps the codebase lean. It runs on Minecraft 1.21 through 1.21.4 and beyond as a single multi-version JAR, so you do not need to hunt down a build that matches your exact patch number. The platform requirement is any Paper fork: Paper, Pufferfish, Purpur, or Airplane all work. You will need Java 21 or newer, and LuckPerms must be installed since the add-on relies on its API for permission handling.
Setting Up Regions With the Selection Axe
Region creation takes seconds. Run /pb axe to receive a selection tool, left-click to mark the first corner, right-click to mark the second, then type /pb create <name>. The configuration GUI opens immediately so you can start adjusting settings without digging through files.
Inside the Two-Tab GUI
The interface is split into a General tab and a Plugin-Block tab. The General tab handles entry messages, which come in three modes: all players see a custom greeting, only OPs and admins see an alert while regular players stay silent, or nothing is shown at all. The Plugin-Block tab dynamically lists every plugin on your server with a color-coded indicator. Emerald means enabled, redstone means disabled, and a single click flips the state and saves it instantly. Lists are paginated at 28 plugins per page, so even heavily modded setups remain manageable.
Custom messages support color codes and placeholders such as {region}, {player}, {plugin}, and {state}, letting you build polished notifications without any external formatting tools. If you would rather skip manual JAR handling entirely, the foxygame.net launcher offers a one-click install path that drops AxY's Plugin Disabler straight into your server's plugin folder with matching version detection.
Commands and Permissions at a Glance
- /pb axe gives you the region selection tool.
- /pb create <name> builds a region from your current selection.
- /pb delete <name> removes a region you no longer need.
- /pb list shows every region on the server.
- /pb info <name> displays bounds, entry mode, and blocked plugins.
- /pb reload refreshes config.yml after edits.
Two permission nodes cover everything: axysplugindisabler.admin grants full access to the plugin's features, while axysplugindisabler.bypass lets trusted staff ignore region restrictions entirely. Tab completion works for both subcommands and region names, which saves a lot of typing on busy networks.
Persistence and Practical Use Cases
Every region, message, and plugin toggle is written to a human-readable YAML file at plugins/AxysPluginDisabler/regions.yml. That file survives restarts, reloads, and even crashes, and it plays well with version control if you keep your server configuration in Git. The architecture is event-driven with zero tick lag, so crowded lobbies will not notice it running.
Common deployments include spawn protection that neutralizes building tools, event arenas that lock down economy and teleport plugins during tournaments, roleplay districts that silence global market or out-of-character chat features, and staff-only zones with silent entry logging. Developers also use it to isolate plugin behavior per region instead of spinning up multiple test servers.
Installation Walkthrough
If you are wondering how to install the add-on, the process is short. First, confirm LuckPerms is running on your Paper server. Next, place the plugin JAR into the plugins directory and restart or reload the server. Finally, run /pb axe and begin marking out protected zones. When you download AxY's Plugin Disabler, keep in mind that the single JAR covers the whole 1.21 range, so future patch updates will not force a re-download.
For administrators who want granular, plugin-level control without wrestling with flag syntax, AxY's Plugin Disabler for Minecraft delivers exactly that: a visual workflow, instant toggles, and dependable persistence. It fills a gap that permission plugins alone cannot close, and it does so with a setup that takes minutes rather than an afternoon.