Skip to content

Releases: aromaa/WorldGuardExtraFlags

v4.2.4

16 Jun 10:18
Compare
Choose a tag to compare

Updated to Minecraft 1.20.6. This version is not backwards compatible with older versions!

Improvements

The give-effects and blocked-effects now finally accept resource keys as Bukkit has exposed the registry for plugins.

v4.2.3

25 Feb 22:24
Compare
Choose a tag to compare

A small bug fix update.

Improvements

  • Preserve cases in command on flags. WG was previously lowercasing this, overriding this now.
  • Preserve order of commands in command on flags.
  • Adjusted the order of handlers. Command on flags are now executed last.

Bug fixes

  • Using outdated ProtocolLib would brick the plugin.

4.2.2

07 Oct 19:43
Compare
Choose a tag to compare

A small bug fix update.

Improvements

  • Use chunk plugin tickets for chunk-unload flag. This used to use forced chunks due to legacy reasons but that is no longer necessary.

Bug fixes

  • Account for worlds with disabled regions.
  • Improve compatibility of teleporting commands with on exit flags.

4.2.1

07 Aug 10:11
Compare
Choose a tag to compare

A small bug fix update.

Improvements

  • Allow specifying source, volume and pitch on play-sounds.

Bug fixes

  • Improved the reliability of the fly flag with other plugins.
  • Added the missing bypass check on command-on and speed related flags.

4.2.0

01 Jun 16:41
Compare
Choose a tag to compare

End Of Legacy Support Update

The plugin has supported Minecraft versions even way back to 1.7 for fairly long time (even too long!) and this update finally drops support for all Minecraft versions other than 1.18. With this, I have made few breaking changes I have had my eyes on for a while now. This should also have positive impact on performance.

Breaking Changes

  • Only supports Minecraft 1.18.
  • The permission nodes used to bypass flags is gone and has been replaced with respecting /rg bypass. If you are relying on this behavior you should be switching to using passthrough regions with groups set up to do the right thing to mimic the old behavior.
  • For the worldedit flag, drop support for FAWE API. This has been unsupported scenario since 1.13+ but stayed in as a feature. Its encouraged to use vanilla WE instead of FAWE.