- Folia/Canvas + FAWE event threading - fly flag cross-world teleport - PlaceholderAPI optional dependency https://github.com/tinsware/WorldGuardExtraFlagsPlus/releases/tag/v4.4.6

### Fixed - **`EntityPotionEffectEvent` on Paper 26.1 / MC 1.21.11** | Fixed `NoSuchMethodError` for `EntityPotionEffectEvent.getEntity()` when running on Paper 26.1 — the listener now resolves the entity via `EntityEvent.getEntity()` for binary compatibility across 26.1 and 26.2. - **Bucket water/lava pickup and placement** | `allow-block-break` / `deny-block-break` and `allow-block-place` / `deny-block-place` now apply correctly to bucket fill and empty actions (including waterlogged blocks). New config `allow-block-break-settings.waterlogged-material-check` (`both` | `host` | `liquid`, default `both`) controls whether the host block, liquid, or both are checked for waterlogged blocks. - **`fixLineWrapping` apostrophe doubling on reload** | `messages-wgefp.yml` no longer grows on every `/wgefp reload` when messages contain apostrophes (e.g. `can't`), which was the root cause of corrupt YAML reports (files ballooning to several MB). The post-ConfigLib line-unwrapping pass now skips files with only single-line values, writes only when content actually changes, uses YAML-aware quote detection (so `can''t` is not mistaken for a closing quote), and outputs double-quoted strings for apostrophe text instead of re-escaping with single quotes. ### Changed - **Minimum Minecraft version** | Minimum supported Minecraft version is now **1.21** (dropped 1.20.x support). `plugin.yml` `api-version: 1.21` unchanged. - **Build dependencies** | Bumped compile-time dependencies for 4.4.5: WorldGuard `7.0.18`, WorldEdit `7.3.19`, Paper API `26.1.2.build.67-stable` (compile target reverted from 26.2 for binary compatibility on 26.1), FAWE-Core `2.15.3`, ConfigLib `4.8.1`, PacketEvents API `2.13.0`, ProtocolLib `5.4.0`, FoliaLib `0.5.1`, EssentialsX `2.21.2`, PlaceholderAPI `2.12.3`, bStats `3.2.1`, Lombok `1.18.46`. WorldGuard moved from `7.0.15-SNAPSHOT` to stable `7.0.18`. - **WGEFP YAML defensive loading** | `config-wgefp.yml` and `messages-wgefp.yml` now quarantine oversize files (>300 KB) to `<name>.corrupt.<timestamp>` and regenerate defaults automatically (plugin keeps loading). At most 3 corrupt backups are kept per file type. YAML parse failures attempt one auto-recovery before disabling the plugin. Direct WGEFP YAML writes use atomic temp-file replacement to reduce crash corruption. - **README and listing docs** | Refreshed for 4.4.5: new flags (`enderchest-access`, `console-command-timer`), bucket/waterlogged fixes, `%uuid%` placeholder, dependency versions, and compatibility table (Paper 1.21 – 26.2+, WorldGuard 7.0.18+). ### Added - **`enderchest-access`** | Controls whether players can open ender chests in a region (like WorldGuard `chest-access`, but ender chests only). Default flag value is allow — set `deny` on a region to block access. Enabled by default (`all-flags-control.enderchest-access: true`). Usage: `/rg flag <region> enderchest-access deny` - **`console-command-timer`** | Repeats a console command at a fixed interval (1-300 seconds) while a player stays in the region. Timer resets on region exit — no cooldown persistence (hold-to-earn / KOTH semantics). Disabled by default — enable via `all-flags-control.console-command-timer: true`. Usage: `/rg flag <region> console-command-timer "60 give %player% diamond 1"` - **`%uuid%` placeholder for command flags** | Parity with upstream [WorldGuardExtraFlags](https://github.com/aromaa/WorldGuardExtraFlags) by [@aromaa](https://github.com/aromaa) (commit [10dd871](https://github.com/aromaa/WorldGuardExtraFlags/commit/10dd871), Jul 2026). Command flags (`command-on-entry`, `command-on-exit`, `console-command-on-entry`, `console-command-on-exit`, `console-command-repeat`, `console-command-timer`) now support `%uuid%` and `{uuid}` in addition to existing `%player%` / `%username%` placeholders.

### Added - **PlaceholderAPI expansion** | New placeholder `%wgefp_players_in_region_<regionId>%` returns the number of online players currently inside a region, summed across all worlds (case-insensitive region id, refreshed once per second, Folia-safe). Requires PlaceholderAPI; toggle via `all-flags-control.papi-placeholders` (default: `false` — opt-in, enable to register the placeholder). - **`all-flags-control.check-order`** | New config option controlling the evaluation order of the block allow/deny flags (`allow-block-place`/`deny-block-place`, `allow-block-break`/`deny-block-break`). `allow-first` (default) keeps the current behavior — a material in the allow list is allowed even if also denied. `deny-first` gives deny priority — a material in the deny list is denied even if also in the allow list. Global setting in `config-wgefp.yml`; existing servers are unaffected by the default. ### New flags - **`deny-mobspawn`** | Blocks spawning of mobs in the listed categories inside a region: `ALL_HOSTILE` (every `Enemy` mob, bosses included), `ALL_NEUTRAL` (provoked-only mobs), `ALL_PEACEFUL` (all other living mobs), `ALL` (all three), or specific `EntityType` names (e.g. `ZOMBIE`, `CREEPER`). Hostile set is derived from the `Enemy` interface so new hostile mobs are auto-covered. See `.media/deny-mobspawn-categories.md` for the exact per-category mob lists. - **`entry-permission`** | Sets the permission required to enter the region (e.g. `/rg flag <region> entry-permission myPlugin.myPermission.1`). Takes priority over `entry-deny-permission` when both are set. - **`entry-deny-permission`** | Denies entry to players holding the given permission (e.g. `/rg flag <region> entry-deny-permission myPlugin.myPermission.1`). If both flags are set, `entry-permission` takes priority. ### Changed - **Default messages** | Unified all default message wording to a consistent WorldGuard-style phrasing (`&c&lHey! &r&7Sorry, but ...`). Idea based on [PR #24](https://github.com/tinsware/WorldGuardExtraFlagsPlus/pull/24) by [@jruk8](https://github.com/jruk8). - **Message cooldown** | Lowered the default `sendMessageCooldown` from 3 to 2 seconds (only affects fresh installs — existing servers keep their configured value). - **`disable-completely`** | `GOAT_HORN` is now a blockable item, so goat horn usage can be disabled in regions (e.g. `/rg flag <region> disable-completely GOAT_HORN`). ### Fixed - **`teleport-on-exit`** | No longer triggers when the player teleports away (`/wild`, `/spawn`, `/warp`, ender pearls, portals) or respawns — it now only fires on real movement out of a region (walking, riding, knockback), so players can't be yanked back to the region's exit location by teleports. Restore the legacy behavior by setting `all-flags-control.teleport-on-exit-ignore-teleports` to `false` (default is `true`).

## 4.4.2 ### New flags - **`lightning-damage`** | Lightning strikes appear visually but don't damage players when set to deny in a region. Useful for PvP arenas. ([PR #21](https://github.com/tinsware/WorldGuardExtraFlagsPlus/pull/21) by [@1wairesd](https://github.com/1wairesd)) - **`console-command-repeat`** | Repeats a console command at a fixed interval (1-60 seconds) while a player stays in the region. Disabled by default — enable via `all-flags-control.console-command-repeat: true`. Usage: `/rg flag <region> console-command-repeat "20 give %player% diamond 1"` ### Fixes - **`disable-completely`** | Fixed hotbar-swap bypass: a player could send `HELD_ITEM_CHANGE` immediately before `STAB` in the same tick, bypassing the region flag. Packet hooks now intercept the slot switch before NMS applies it — if the target slot holds a blocked item, the switch is cancelled outright. (Issue identified by [@1wairesd](https://github.com/1wairesd)) - **`console-command-repeat`** | Fixed `IllegalStateException: Dispatching command async` on Folia servers by routing the command dispatch through `runNextTick`. Fixed flag value parsing: the underlying element flag no longer auto-prepends `/` to entries, so values like `6 say hi` are stored and parsed correctly. - **`console-command-repeat`** | Fixed reward farming by adding persistent cooldown tracking. The handler now records the last execution time for each flag entry. When a player exits and re-enters the region, the remaining interval is calculated from the last payout — preventing instant rewards on re-entry. On first entry, the command waits the full interval before any payout. - **`console-command-repeat`** | Fixed FoliaLib warning about 0-tick delay when the cooldown expired while the player was away. The catch-up command is now dispatched via `runNextTick` instead of passing `0L` to the entity timer.

- blocked-effects, give-effects, and play-sounds skip tick work when the flag is inactive and there’s nothing to restore - blocked-effects avoids calling hasBypass() every tick when no flag value applies (less LuckPerms/cache overhead) - blocked-effects uses one runAtEntity task per tick instead of N+1 separate schedules

### Build & runtime - **Version 4.4.0** — feature and stability release after Folia/performance audit. - **Java 21** bytecode (`--release 21`) for broader Paper **1.21.x** / **26.1–26.3** server compatibility. - **Paper API** compile target: **`26.1.2.build.67-stable`**; **`plugin.yml`** remains **`api-version: '1.21'`**. - **FoliaLib shading** hardened: explicit shade includes + post-package check that **`WrappedBukkitTask`** and **`SpigotImplementation`** exist in the jar (fixes **`NoClassDefFoundError`** breaking command-on-entry and all schedulers on Paper 26.x). ### Command flags - Shared **`CommandFlagHandlerSupport`** for entry/exit player and console command flags. - Entry commands dispatch only from **entered** regions with correct last-set tracking; exit commands run for **all** removed command sets. - Player commands use **`runAtEntity`**; console commands use **`runNextTick`**. - Scheduler self-test on enable logs **SEVERE** if FoliaLib is broken. ### Config & startup ([#14](https://github.com/tinsware/WorldGuardExtraFlagsPlus/issues/14), [#13](https://github.com/tinsware/WorldGuardExtraFlagsPlus/issues/13)) - **`logging.verbose-startup-logs`** (default **`false`**) — quiet console on large servers. - **`Config.initialize()`** in **`onLoad()`** before flag registration — disabled flags (e.g. **`glide`**) are not registered; reduces “plugin not installed” unknown-flag warnings. - Chunk-unload tickets: one summary line per world; collision init only when flag enabled. ### Give-effects ([#15](https://github.com/tinsware/WorldGuardExtraFlagsPlus/issues/15)) - **`PotionEffectFlag`** accepts **`night_vision`**, **`minecraft:night_vision`**, legacy names, and normalized spacing. ### Keep-inventory & combat log - **`keep-inventory-settings.combat-log-restore`** (default **`true`**) — DeluxeCombat soft integration: snapshot inventory on combat-log quit inside keep-inventory regions, restore on next join. - Death handler priority **`HIGHEST`** so other plugins are less likely to clear drops after keep-inventory applies. ### Block flags - **`allow-block-place-settings.require-membership`** / **`allow-block-break-settings.require-membership`** — allow lists apply only to region **members/owners** (e.g. member-only sign placement). ### New flag: hide-players (experimental) - Opt-in via **`all-flags-control.hide-players: true`**, then **`/rg flag <region> hide-players true`**. - Hides players from others while inside the region (hub/lobby optimization via Bukkit **`hidePlayer`**). ### Join-location - Improved Paper/Folia/Canvas detection — prefers **`AsyncPlayerSpawnLocationEvent`** over deprecated **`PlayerSpawnLocationEvent`** on modern servers. ### Folia / performance audit fixes - Collision apply on join/world-change via **`runAtEntity`** (not global **`runNextTick`**). - **Chambered ender pearl** listener rewrite (thread-safety, scheduler). - **Player count limit** uses world-scoped player scan. - **Chunk-unload** batched async chunk tickets. - **Join-location** fallback uses **`teleportAsync`**. - **Fly/godmode** quit cache cleanup; **entry-level** placeholder cache eviction; **`onDisable`** task cancel. ### Config documentation - Inline comments for give-effects syntax, worldedit **`__global__`** usage, glide disable behavior, hide-players setup.

# Changelog - Release 4.3.13 ## 4.3.13 ### `disable-throw` region flag - **`SetFlag`** listing **`EGG`**, **`SNOWBALL`**, **`ENDER_PEARL`**, **`EXPERIENCE_BOTTLE`** only (validated by **`ThrowableItemFlag`**); **`ProjectileLaunchEvent`** cancellation + **`disable-throw-blocked`** message ( **`messages-wgefp.yml`** ). Trident / wind charge remain on **`disable-completely`**. Toggle via **`config-wgefp.yml`** **`all-flags-control.disable-throw`**. ### Build / runtime targets (Maven) - **Minecraft / Paper `26.1.2`**: compile against **`io.papermc.paper:paper-api`** pinned to **`26.1.2.build.60-stable`** (matches Paper repo [`maven-metadata.xml`](https://repo.papermc.io/repository/maven-public/io/papermc/paper/paper-api/maven-metadata.xml) **`release`** at time of update); bump this property when Paper ships newer **`26.1.2.build.*`** builds. **`org.spigotmc:spigot-api`** removed — Paper supplies the Bukkit API ([Paper project setup](https://docs.papermc.io/paper/dev/project-setup/)). - **`javac` `--release 25`** per Paper’s **`26.1.x`** toolchain recommendation (same doc). - **`plugin.yml`**: **`api-version: '1.21'`** so Paper / forks (e.g. Canvas) **1.21.x** accept the jar at load time; declaring **`26.1.2`** causes `Unsupported API version` on those servers ([Paper plugin.yml](https://docs.papermc.io/paper/dev/plugin-yml/)). - Still bundled vs provided: **WorldEdit `7.3.18`**, **WorldGuard `7.0.15-SNAPSHOT`**, **FAWE-Core `2.12.0`**, **bstats `3.1.0`**, **ConfigLib `4.8.0`**, **Lombok `1.18.46`**, **shade `3.6.2`**. **`paper-repo`** remains **last** in `<repositories>` to avoid probing EngineHub coords against Paper first. ### Join location (Paper / Folia) - When `join-location` is enabled and the server provides Paper's [`AsyncPlayerSpawnLocationEvent`](https://jd.papermc.io/paper/io/papermc/paper/event/player/AsyncPlayerSpawnLocationEvent.html), register **`AsyncJoinLocationListener`** instead of deprecated Spigot `PlayerSpawnLocationEvent`, avoiding startup deprecation noise (aligned with [PR #12](https://github.com/tinsware/WorldGuardExtraFlagsPlus/pull/12)). - Plain Spigot (no async API): unchanged **`JoinLocationListener`** and existing deprecation console hint. - **`JoinLocationPlayerJoinListener`** (`PlayerJoinEvent`, monitor): if `join-location` resolves at the player's spawn position and differs by block, teleport on the entity scheduler. Covers **Folia** (and similar cases) where async spawn handlers cannot reliably apply region queries before login ([Issue #1](https://github.com/tinsware/WorldGuardExtraFlagsPlus/issues/1)); uses **`LocalPlayer`** for the query like **`JoinLocationListener`**. ### WorldEdit flag + FastAsyncWorldEdit (FAWE) - **`WorldEditFlagHandler`** now intercepts FAWE batch extent APIs (`setBlocks`, `replaceBlocks`, coordinate `setBlock`, `setBiome`) in addition to per-block `setBlock`, so **`worldedit` DENY** is much harder to bypass under FAWE (addresses [Issue #7](https://github.com/tinsware/WorldGuardExtraFlagsPlus/issues/7)–style gaps). - Compile against **`FastAsyncWorldEdit-Core`** `provided` (Modrinth Maven); WorldGuard’s transitive WorldEdit jars are excluded on the Spigot module so the patched **`AbstractDelegateExtent`** API matches runtime FAWE/WorldEdit. - Optional permissions: **`worldguardextraflagsplus.worldedit.bypass`**, **`worldguardextraflagsplus.worldedit.silent-deny`**. - New message key **`worldedit-denied`** in `messages-wgefp.yml` / `PluginMessages` (reload to customize). ### Disabled flags in `config-wgefp.yml` (handler null-safety) - When **`all-flags-control`** turns off **`fly`** or **`give-effects`**, WorldGuard does not register those session handlers — **`Session#getHandler` returns null**. **`PlayerListener`**, **`EntityPotionEffectEventListener`**, and **`RemoveEffectPacketListener`** now check **`Config.isFlagEnabled`** and null handlers before use (fixes [Issue #9](https://github.com/tinsware/WorldGuardExtraFlagsPlus/issues/9) NPE on e.g. `PlayerChangedWorldEvent`). ### `fly` after PLUGIN teleports (portals) - After **`PlayerTeleportEvent`** (monitor), re-query **`fly`** at the destination and call **`FlyFlagHandler#refreshFlyFromApplicableSet`**, so flight matches regions when session move hooks do not run (e.g. [Issue #8](https://github.com/tinsware/WorldGuardExtraFlagsPlus/issues/8) portal plugins). ### `command-on-entry` / `console-command-on-entry` - **`initialize(LocalPlayer, …)`** added so commands run when the session starts **already inside** a region with the flag (previously only **`onCrossBoundary`** fired, so login/spawn inside the region did nothing). **`console-command-on-entry`** also aligns **`isEmpty`** checks with **`command-on-entry`**. - Command strings: strip a leading **`/`** only when present — YAML pasted without **`/`** no longer turns **`say hi`** into **`ay hi`**. **`command-on-exit`** / **`console-command-on-exit`** use the same helper; skip blank lines after processing.

#### `disable-completely` — Vanilla spears (1.21.11+) - Block **spear** items: tier materials (`WOODEN_SPEAR`, `STONE_SPEAR`, `COPPER_SPEAR`, `IRON_SPEAR`, `GOLDEN_SPEAR`, `DIAMOND_SPEAR`, `NETHERITE_SPEAR`) and the **`SPEAR`** shorthand (all tiers). - **Riptide** interaction blocking extended to **spears** as well as **tridents** when the item is disabled in the region. - Spear **Lunge** (packet **STAB**, including **Lunge** enchant use) is only reliably blocked when **PacketEvents** or **ProtocolLib** is installed; without either, Lunge may bypass Bukkit-only checks. #### Packet-level blocking (optional plugins) - **`disable-completely`** registers **PacketEvents** listeners when the PacketEvents plugin is present (primary): cancels relevant **serverbound** packets including spear **Lunge** via digging action **STAB**, plus use/interact/placement paths as implemented. - **ProtocolLib** is supported as a **fallback** when PacketEvents is not used or hook registration fails. #### Safe startup without PacketEvents / ProtocolLib - Main plugin class avoids hard references to PacketEvents and ProtocolLib APIs; registration uses **reflection** so the jar loads cleanly when optional dependencies are absent (`provided` / `softdepend`). - PacketEvents API entry uses **`com.github.retrooper.packetevents.PacketEvents`** (correct package); avoids bogus `io.github.retrooper...` lookups that broke hook registration at runtime. - **`ProtocolLibHelper`** (`give-effects`) registers its listener via reflection only so the helper class does not require ProtocolLib on the classpath at load time. #### New flag: `chambered-enderpearl` *(experimental)* - **Experimental.** State flag to mitigate **chambered ender pearl** style bypasses: tracks pearls thrown outside flagged regions and removes them when the shooter enters a region where the flag **denies** the behavior (handler + session integration; configurable via `config-wgefp.yml` flag toggle like other flags). Behavior and defaults may change in future releases.

Update log: https://github.com/tins-dev/WorldGuardExtraFlagsPlus/releases/tag/v.4.3.11

### Disable Collision Flag - Major Refactor #### Implementation Changes - **Minecraft teams**: Now uses Minecraft's native scoreboard team system (the only reliable method for entity-to-entity collision) - **Hybrid team-based approach**: - If a player is the only member of their team, the plugin temporarily modifies that team's collision rule - If a player is in a team with multiple members, creates a per-player team (`WGC_<hash>`) to avoid affecting others - If a player has no team, adds them to a per-player team with collision disabled #### TAB Plugin Integration - **Full API integration**: Added TAB plugin support with API integration - **Priority handling**: TAB integration takes priority over direct team manipulation when TAB is installed - **Conflict prevention**: Uses TAB's API to set collision rules, preventing TAB from overwriting collision settings - **Automatic fallback**: If TAB is not available, automatically falls back to direct team manipulation #### Without TAB (Normal Usage) - **Direct team manipulation**: Uses Bukkit's Scoreboard API to directly modify team collision rules - **Team restoration**: Properly restores original team collision rules when players leave regions - **Per-player teams**: Creates temporary per-player teams when needed to avoid conflicts with shared teams - **Cleanup on disable**: Properly cleans up all teams and restores original settings when plugin disables #### Warnings and Compatibility - **Load-time warning**: Displays a warning on plugin load about potential conflicts with team-using plugins - **Known plugin detection**: Warns about potential conflicts with couple known plugin names - **TAB support indication**: Shows supported plugins #### Documentation Updates - **Updated documentation**: Comprehensive documentation file updated with TAB integration details - **Troubleshooting guide**: Added troubleshooting information for team conflicts