Tags
Creators
Details
3.6.0
Compatibility
Required content
Changes
Cleaner Hijacking
Removed PvP mode hijacking of the original WG's protection listener. Overall, this should improve stability of non-default pvpmode setting.
The unfortunate part, the deny-message message is no longer configurable through WGExtender, so consider either setting up the deny-message flag on a __global__ region, or using a translation WG plugin/fork of your liking.
Added an option for less hijacked /rg claim command flow - it disables translatability too, but should be more stable with the future WG updates. Disabled by default for the time being, feel free to test it. Also made hijacked flow more inline with the current WG behavior. /rg claim now supports the polygonal selection type - as WG intended.
/wgex Command
Migrated commands to Mojang's Brigadier API, which should improve the usage experience.
I've also added permission checks for each of plugin's subcommand - wgextender.admin.<subcommand>, e.g. wgextender.admin.update for /wgex update.
Update Checker
Implemented update checker. You can disable it in the config at updater.enabled. The notifications are shown to the admins with wgextender.admin permission.
Messages
Major messages updates:
claim.too-many: Now has the{count}and{limit}placeholdersclaim.too-big: Replaced{maxVolume}placeholder with{limit}claim.only-cuboid>claim.wrong-shape: Remade the message to better reflect the behavior.
For the new messages, see the diff.
Metrics Integration
Added bStats metrics integration. As always with bStats, you can opt-out in ./plugins/bStats/config.yml config file.
Generally speaking, I'm just collecting data on which features of the plugin are used.
Optional dependencies
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:JFMgRt9t:PJeJH2Ec"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JFMgRt9t:PJeJH2Ec"
}

