Tags
Creators
Details
4.3.6
Compatibility
Changes
Bug Fixes Fixed Riptide Enchantment Blocking Fixed: permit-completely flag now fully blocks Riptide enchantment on tridents Prevents Riptide boost, spinning animation, and all movement effects Blocks right-click interactions before Riptide can activate Rotation locking prevents spinning animation if event somehow fires No longer requires enchantment removal (safer approach) ✨ New Features Block Placement & Breaking Control Added 4 new flags for fine-grained block control:
allow-block-place - Whitelist specific blocks that can be placed deny-block-place - Blacklist specific blocks from being placed allow-block-break - Whitelist specific blocks that can be broken deny-block-break - Blacklist specific blocks from being broken Usage Examples:
/rg flag spawn allow-block-place STONE,COBBLESTONE,GRASS_BLOCK /rg flag spawn deny-block-place TNT,LAVA_BUCKET /rg flag spawn allow-block-break STONE,COBBLESTONE /rg flag spawn deny-block-break BEDROCK,SPAWNER
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:ZqKNWzBK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DsxKmIdB:ZqKNWzBK"
}

