Bridging Land Management Plugins with Flags
Managing a Minecraft server often means juggling multiple land claim plugins, each with its own way of defining areas. Developers who want to add per-area features—like disabling PvP or blocking mob spawning—usually have to write separate code for every single land system. The Flags plugin eliminates that headache by acting as a universal interface between cuboid-style land management plugins and any other plugin that needs to interact with them. Inspired by the same design philosophy as Vault, Flags gives developers a single, unified "Area" object, so they can read area information without ever knowing which plugin created it. This means a developer can implement a feature once, and it will automatically work with Factions, Grief Prevention, WorldGuard, and many others.
How the Flags Plugin Works
A Unified Area Object
At its core, Flags provides a common language for areas. When a player stands inside a claimed region, Flags can tell any hooked plugin the name of that area, its owners, and other metadata. Developers simply query the Flags API instead of writing integration for each land plugin individually. This drastically reduces compatibility issues and saves countless hours of coding.
Flags and Switches
The plugin gets its name from the concept of "flags"—simple on/off switches that change game behavior in a specific area. A flag might control whether PvP is allowed, if creepers can explode, or whether players can enter a zone. Plugins that create flags only need to handle the behavior when a flag is active; Flags automatically remembers each player's choices and customizations across restarts. Don't let the name fool you, though: the API can hook into areas without creating any flags at all, making it a powerful tool for pure area detection.
Key Features of Flags
- Multiple land area plugin support – Works with all major claim plugins and includes a built-in fallback system.
- Modular flags – Install only the flag modules you need, keeping your server lightweight.
- Developer API – Anyone can create custom flag modules or interface with areas from their own plugins.
- Area, wilderness, and default scopes – Set flags for a specific claim, for all unclaimed land, or as a world-wide default.
- Trust lists – Choose which players can bypass flag effects in each area.
- Customizable player messages – Personalize all flag feedback per area.
- Flag bundles – Group multiple flags together and set them with a single command.
- Multi-world support – Treat each world as a distinct area with its own wilderness and default settings.
- Flexible data storage – Choose between YAML and MySQL to suit your server’s needs.
- Vault economy support – Charge players for purchasing flags and custom messages.
Supported Area Plugins
Flags currently supports Factions, Factoid, Grief Prevention, InfinitePlots, PlotMe, PreciousStones, Residence, and WorldGuard. If no other land system is detected, Flags uses its own internal area handler, so you can still use flag-based features even without a dedicated claim plugin. For full compatibility details and feature sets, you can consult the Area Plugins page.
Included Modules
Flags ships with a set of optional modules that work with just a standard Bukkit server. Simply place the module JARs you want alongside Flags.jar in your plugins folder. Here is what each module adds:
- Block Module – Flags for controlling block interactions, such as building or breaking.
- Border Patrol Module – Flags that fire when players move into or out of an area.
- Core Module – General flags that don’t fit into the other categories, covering miscellaneous behaviors.
- Creature Spawn Module – Flags to stop specific creatures from spawning inside an area.
- Damage Module – Flags for blocking various types of player damage, from falling to drowning to magic.
- Player Module – Flags based on player actions, like entering, leaving, or teleporting.
- Vehicle Module – Flags that apply to boats, minecarts, and horses.
External Plugins with Flags Support
Several community-made plugins extend Flags with their own unique flags. Flags BlockNotif, for example, notifies moderators when players break certain blocks and uses Flags to report the area name. FancyShop lets you restrict chest shops to specific areas via flags. FlyNCreative enables creative mode and flight per area while keeping inventories separate. HardcoreClaims deletes claims on death based on flag settings, and PetStore manages animal ownership with area restrictions. RocketTeleport adds flare-based teleportation and uses flags to control where rockets and landing zones can be created.
Using Flags: Commands and Tools
Setting Flags for Areas, Wilderness, and Defaults
To set a flag, stand inside the target area and use the /flag <action> <location> <flag> [value] command. You can target the current area, the wilderness (unclaimed land), or the world default. For example, /flag set wilderness NotifyExit true explicitly enables exit notifications in the wild, while /flag set default SpawnMob toggles the mob spawn flag for all areas that haven't overridden it. The /flag help command lists all available flags based on your installed modules.
Handy Tools
Flags includes configurable item-based tools to speed up administration. The Flag Query tool (a feather by default) lets you right-click any area to view its current flags, acting like a quick /flag get area. If sectors are enabled, the Sector tool (a gold hoe) allows you to create subdivisions by right-clicking corners, and you can even nest sectors inside each other.
Flag Bundles
Bundles group multiple flags together so you can apply them with one command. They come with their own permission system, so a player doesn’t need individual flag permissions if they have the bundle permission. Default bundles like Build (golem, snowman, wither building), Jail (entry, leave, teleport controls), Notify (enter/exit alerts), SpawnMonster (invasion, lightning, mob spawning), and Damage (all damage types) serve as examples and can be edited or removed. You can create new bundles via commands or by editing the bundle.yml file directly—just remember to keep bundle names lowercase.
Installation and Management
Getting Flags running is straightforward. Download the main Flags.jar and the module JARs you need, then drop them into your server’s plugins folder. After a restart, Flags will automatically detect your land management plugin and begin working. For server administrators who prefer a more streamlined approach, the foxygame.net launcher provides a convenient, flexible, and modern way to handle plugins. This launcher lets you download Flags and its modules directly from its menu, eliminating the need to manually move files around and helping you keep everything up to date with minimal effort.
Flags also includes an automated updater that can notify console operators and permitted players when a new version is available. You can configure or disable this feature through the config. The plugin reports anonymous usage statistics to MCStats.org, which you can opt out of if desired.
Conclusion
The Flags plugin is an indispensable tool for any Minecraft server that wants to unify area-based features across multiple land management systems. By providing a single API and a rich set of ready-made flag modules, it saves developers from reinventing the wheel and gives server admins precise control over what happens in every corner of their world. Whether you need to stop mob spawning in a faction base, create no-PvP zones in the wilderness, or build custom area-dependent mechanics, Flags makes it possible with minimal configuration and maximum compatibility.