Tags
Creators
Details
4.3.7
Compatibility
Changes
WorldGuard ExtraFlags Plus v4.3.7
šØ New Flag: permit-workbenches
Block workbench usage and crafting in regions! Supports: ALL, clear, anvil, cartography, craft, ender, grindstone, loom, smithing, stonecutter.
Usage:
/rg flag spawn permit-workbenches ALL
/rg flag spawn permit-workbenches ALL,ender
/rg flag spawn permit-workbenches craft,anvil
/rg flag spawn permit-workbenches clear
Features:
- Blocks right-click on workbenches
- Blocks crafting table GUI and 2x2 inventory crafting
- Optional block placement blocking via config
- New config file:
plugins/WorldGuard/config-wgefp.yml - New message:
permit-workbenches-blockedwith{workbench}placeholder
š« New Flags: deny-item-drops & deny-item-pickup
Deny specific item drops and pickups in regions (works when WorldGuard's default flags are set to allow).
Usage:
/rg flag spawn deny-item-drops diamond,emerald
/rg flag spawn deny-item-pickup apple,bread
Features:
- Denies specific items from being dropped even if WorldGuard allows drops
- Denies specific items from being picked up even if WorldGuard allows pickups
- Works alongside WorldGuard's
item-dropanditem-pickupflags
š§ Improvements
- Messages file renamed:
messages.ymlāmessages-wgefp.yml(avoids conflicts) - Fixed logic: explicit workbench types now take precedence over
ALLkeyword
š Stats
- Total Flags: 37 (was 34)
- Minecraft: 1.20 ā 1.21.10
- WorldGuard: 7.0.13+
- Folia: ā Fully supported
š Migration
- Rename
plugins/WorldGuard/messages.ymltomessages-wgefp.ymlif you have custom messages - New
config-wgefp.ymlwill be auto-created
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:DsxKmIdB:2vufTV6Y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DsxKmIdB:2vufTV6Y"
}

