Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 years ago
Updated last week
All versions
7.0.0
Release
WorldGuard 7.0.0 (for MC 1.13.2)2 years ago 81
Compatibility
Minecraft: Java Edition
1.13
Platforms
Bukkit
Paper
Spigot
Required content
Any compatible version
Changes
WorldGuard 7.0.0 (for MC 1.13.2)
This version is compatible with:
- CraftBukkit/Spigot for 1.13.2 / 1.14.2 (Paper recommended)
- THIS VERSION IS NOT COMPATIBLE WITH VERSIONS PRIOR TO 1.13
Changes
- Added support for MC 1.13, dropped support for previous versions.
- Added lots of interactive text in e.g. /rg info command.
- Added /rg flags command which allows viewing and interactively setting all flags on a region.
- Large behind-the-scenes changes to WorldGuard's API (developers, see https://worldguard.enginehub.org/en/latest/developer/)
- Places that used numeric block ids (e.g. blacklist) should now use Minecraft's new string IDs.
- Fix various interactions with NPCs and region protection.
- Sponge-simulation now destroys kelp and seagrass, and de-waterlogs blocks.
- Added an option to block conduit effects.
- Fix using newlines in string flags such as greeting and farewell.
- Add item-frame-rotation flag.
- Ender chests no longer require chest-access (since they don't have inventories).
- Add kelp to vine-growth flag/config.
- Add block-trampling flag (for turtle eggs and farmland).
- Add snowman-trails flag.
- Track potion area-of-effect cloud causes for pvp etc. protection.
- Add confirmation to /stoplag command.
- Forcefully eject players from vehicles trying to force their way into entry deny regions (and out of exit deny).
- Fix removing child regions when removing a region with children.
- Fix some over-protectiveness of pistons.
- Chat and command flags (send-/receive- and allowed-/blocked-) now respect deny-message flag.
- Misc fixes.
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:Co8Wzc6T"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DKY9btbd:Co8Wzc6T"
}

