#WORLDGUARD DISABLE FALLING BLOCKS UPDATE#

This change has been sitting here for a while uncommitted and unpushed.įix Falling blocks may change snow layers to that blockĬhange relocated/shaded artifacts to compileOnly.įix TimedHandler not calling delegated handler (#1727) Not sure why these were here to begin with, Poly doesn't have them eitherĪnd mutating regions after creation leads to undefined behavior.ĭeprecate flags (replaced by RegistryFlag), added some null checks (#1747)

#WORLDGUARD DISABLE FALLING BLOCKS UPDATE#

Update Java version in CONTRIBUTING.md (#1764)ĭeprecate and immediately void setMin/MaxPoint in ProtectedCuboidRegion. * Improve performance by putting UUID checks first. Small performance improvement for `PlayerDomain#contains()` (#1765) Remove unnecessary FlagValueCalculator#getPriority(ProtectedRegion) callsįix doc comment of FlagValueCalculator#getMembership(RegionAssociable) Remove unused RegionGroup.MEMBERS from the teleport flag (#1769) * Add handler for spigot's EntityMountEvent.Īdd nonplayer-protection-domains flag (#1763)įix Dispenser Shulker Box bug and cleanup (#1776) Handle spigot's entity mount event (#1755) Updated build environment, switched to Jupiter Unit Testsįix protections for copper and rooted dirt Update to Java 16, Gradle 7.0.2 and Bstats 2.1.0 Re-add shade config, fix some other gradle black magic. Switch back dependency from Spigot to Paperīump squirrelid to 0.3.0, Deprecated PaperProfileServer (replaced by squirrelid) Protect cave vines and glow berries correctlyįixed wrong dependencies, removed not needed repositoryĬompare items for /stack with ItemStack.isSimilar Protect signs against usage of (glowing) ink sacĪdded use-dripleaf flag, Handle Deepslate Redstone Ore correctly This reverts commit b1cd1303d1d194fef7d1fc6e2811931ca08f4e38.Īdd member inheritance for non-player associablesĬheck all effects for lingering potion clouds.Īdded NPE error message and javadoc hint for WorldGuard.getPlatform Revert 'Add member inheritance for non-player associables' Let me know if I didn't undertstand it correctly. Maybe i understand the 'after' incorrectly but in my mind my customHandler should run after the 'after' not the other way around if that makes sense. I am not sure exactly if this is the source of the problem, but when i tried registering my handlers using ExitFlag.FACTORY as 'after' like how the javadocs said it, it seemed that my handler was running before the ExitFlag handler which means mine will run even if ExitFlag returns false. Additionally block other explosion if the defender is a block like entity to be consitent with 'block' explosion protectionsīlame those pesky WorldEdit devs breaking our builds :^)įix handlers order when registering one with after.

Worldguard disable falling blocks