WorldGuard Flags
These flags are available when EliteMobs successfully initializes its WorldGuard integration. allow and deny control the behavior named by each flag; allow does not bypass other spawn requirements or protections.
elitemobs-events (allow/deny)
Allows event locations in the region by default; deny rejects them. Event location checks also exclude disabled worlds, EliteMobs dungeon worlds and active match regions. Use ValidWorlds.yml to exclude an entire world from ordinary event location selection; it also affects natural Elite conversion. A pending timed event can retry elsewhere rather than being permanently cancelled by one rejected location.
elitemob-spawning (allow/deny)
Allows ordinary Elite conversion and custom-boss spawning by default; deny blocks those paths in the region, including regional bosses. It does not remove existing mobs or ban normal vanilla spawning. Use ValidWorlds.yml to disable ordinary natural Elite conversion for a whole world; that setting is not a universal ban on authored boss spawns or entities owned by another game mode.
elitemob-only-spawning (allow/deny)
Defaults to deny (restriction off). With allow, the creature-spawn listener removes and cancels creatures that are not tracked Elites. It does not raise the Elite conversion rate. Use it where ordinary non-Elite spawns should be suppressed.
Armor stands are exempt regardless of spawn reason. Villagers with the CUSTOM spawn reason and EliteMobs' forced compatibility spawns are also exempt. Other CUSTOM creatures are not automatically exempt from this flag.
elitemobs-antiexploit (allow/deny)
Defaults to allow. deny skips the regional damage-event anti-exploit checks at the Elite's location. allow still respects other exclusions, including EliteMobs dungeon worlds and Ender Dragons. This does not disable every anti-exploit mechanism or the separate skill-XP farming counter. Use deny only where the terrain and intended combat have been checked.
elitemobs-explosion-regen (allow/deny)
Controls the EliteMobs regeneration handler at the supplied source location (default: allow). With doExplosionRegen: true, deny skips that handler: native explosions may still destroy blocks without repair, while fake explosions using this handler stop before directly removing blocks. Calls without a source location do not check this regional flag. It is not general block protection.
elitemobs-explosion-block-damage (allow/deny)
For tracked Elites, tracked projectiles and native Lua projectiles that opt into protection handling, deny clears the block list of Bukkit's native EntityExplodeEvent at the explosion location; allow is the default. This handler does not cancel entity damage or knockback. It does not intercept arbitrary Lua/EliteScript block edits or every fake-explosion call. Check the actual power's damage path before relying on this flag.
EliteMobs NPCs use a forced-spawn compatibility path that can override WorldGuard's ordinary mob-spawning: deny. Remove unwanted NPCs through their configuration; that flag is not a reliable way to hide them. Regional bosses use the compatibility path only after passing elitemob-spawning.
elitemobs-maximum-level
Sets an integer maximum in the natural conversion level calculation. Custom Bosses ignore this setting. Use whole numbers such as 1 or 2, not 1.5. The regional minimum is applied first, then this maximum, and the global naturalEliteMobsLevelCap can lower the result further. Neither flag changes existing mobs' levels.
elitemobs-minimum-level
Sets an integer minimum in the natural conversion level calculation, including ordinary spawner conversion when enabled. Custom Bosses ignore it. The regional maximum and global natural level cap still apply afterward, so a conflicting minimum is not guaranteed. This does not increase the conversion chance or override disabled spawning.
elitemobs-dungeon
Defaults to deny (restriction off). With allow, the creature-spawn listener cancels and removes non-CUSTOM creatures unless they are armor stands, tracked Custom Bosses or EliteMobs forced compatibility spawns. This blocks more than natural spawning: ordinary breeding and spawner creatures are also affected.
Use it to keep dungeon populations under content control. It does not create a dungeon instance, remove existing mobs, or override elitemob-spawning: deny for custom bosses. If elitemob-only-spawning is also enabled, its separate restrictions still apply to CUSTOM creatures.