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 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).
• 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).
• 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, register AsyncJoinLocationListener instead of deprecated Spigot PlayerSpawnLocationEvent, avoiding startup deprecation noise (aligned with PR #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); 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–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 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 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.