Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 years ago
Updated last week
All versions
7.0.4
Release
WorldGuard 7.0.4 (superceded)2 years ago 141
Compatibility
Minecraft: Java Edition
1.16
Platforms
Bukkit
Paper
Spigot
Required content
Any compatible version
Changes
WorldGuard 7.0.4 (superceded)
- Add support for MC 1.16. Dropped support for previous versions.
- Add respawn-anchors flag mirroring the sleep flag (e.g. to prevent using respawn anchors to cause explosions in the overworld)
- Add nether vines to vine-growth flag.
- Add config option to disable the bypass permission cache.
- Fix water-flow flags not checking waterlogged blocks.
- Add config option to consider non-player causes (e.g. pistons, flowing water) to only be members of the highest priority region. This should be enabled for plots-within-city-like setups to prevent things in plots from modifying the city.
- Fix items dropping from falling blocks that were suppressed by other plugins.
- Add config option to block turtle egg trampling.
- Fix ride flag being checked on striders that didn't have saddles.
- Add config option to have /rg bypass toggled off on login.
- Developer changes: Methods taking names in Domains are now explicitly deprecated (was previously just a javadoc comment.); These will eventually be removed: there is no reason to use names over UUIDs. Offline players and NPCs alike have stable UUIDs.
- Also for developers; The new com.sk89q.worldguard.protection.util.WorldEditRegionConverter class has some useful static methods to convert to and from WorldEdit's Region and WorldGuard's ProtectedRegion classes.
- See the 7.0.3 changelog for more details, as many changes have happened since 7.0.2.
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:DKY9btbd:VkMhNRQP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DKY9btbd:VkMhNRQP"
}

