Tags
Creators
Details
1.0
Compatibility
Changes
Block commands per region; dialog implementation, other bug fixes.
New
Block commands in a region. A new block_commands flag stops players in a region from running the commands you list. With an empty list, it blocks every command. Entries like tp also catch namespaced forms like /minecraft:tp; aliases have to be listed on their own. Ops and players with realregions.<world>.<region>.block-commands.bypass are not affected. Blocked commands list. Shift-click Block Commands in the region menu, or run /rr blockcommands region@world, to open the list. From there you can add commands, click one to remove it, clear the list, or turn the flag on and off. /rr blockcommands region@world <all | command...> still sets the whole list in one go. Dialogs on 1.21.6+. On servers that support them, typed input, confirmations and the new menus appear as dialog screens. Older servers keep the chat prompts and chest menus. You can turn dialogs off with useDialogs in config.yml. Confirmations. Deleting a region, or unloading or deleting a world, now asks first (on servers with dialogs). In-game settings. /rr settings, or the new Settings icon in the /rr menu, edits config.yml in game without a restart (needs dialogs). /rr tpo <world> <player> now works from the console.
Fixed
Flags set with /rr flag are now saved. Before, they were lost on restart. The Leaf Decay flag is now saved to the config. Ops now see the region enter title and action bar too. /rr tpr, /rr view and other region commands accept region@world again. Missing language lines now show a clear "Missing language entry" message instead of an error or "null".
Upgrading
Requires Java 16 or newer.
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:fG8P1bKI:ytlVyOC5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fG8P1bKI:ytlVyOC5"
}

