All versions
1.3.0
Release
WorldRules 1.3.04 months ago 37
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Folia
Paper
Purpur
Changes
[1.3.0] - 2026-06-23
Added
Granular block interaction
- New per-block interact categories, replacing the single
open_doorscatch-all:use_doors— doors, trapdoors, fence gatesuse_buttons— buttonsuse_levers— leversuse_pressure_plates— pressure plates (stepping)use_containers— chests, barrels, shulker boxes, hoppers, droppers, and other inventory blocksuse_workstations— crafting table, furnaces, anvils, enchanting/brewing, grindstone, smithing table, beacon, bell, and other utility blocks
utilitiesumbrella keyword that flips all six block-interaction categories at once — likeall, but scoped to blocks. Works globally, per-player, and per-team:/worldrules interact utilities <true|false> [player]/worldrules interact team <name> utilities <true|false>
Chat broadcast & visibility controls
/worldrules chat join_messages <true|false>— show/hide join broadcasts (defaulttrue)./worldrules chat leave_messages <true|false>— show/hide leave broadcasts (defaulttrue)./worldrules chat death_messages <true|false>— show/hide death broadcasts (defaulttrue)./worldrules chat command_messages <true|false>— toggles command-execution feedback via thelogAdminCommandsgamerule across all worlds (defaultfalse, matching vanilla where non-ops never see command feedback). Re-applied on enable and on/worldrules reload./worldrules chat see_chat <true|false> [player]— global and per-player. Whenfalsefor a player, they can neither send chat nor see other players' chat. Chat-bypass players always retain access./worldrules chat infonow also reports join/leave/death/command message states and the global + per-playersee_chatsettings.- Tab completion and editable
config.ymlmessages for all of the above.
Changed
- Right-click handling now routes each block to its specific category. Workstations are checked before the generic inventory-holder test, since furnaces and similar blocks also hold inventories.
chat-usage,interact-usage, and the/worldruleshelp screen updated to list the new sub-commands.
Persistence
rules.ymlgainschat.join-messages,chat.leave-messages,chat.death-messages,chat.command-messages, andchat.see-chat.global/chat.see-chat.players.<uuid>.
⚠️ Breaking / migration
- The
open_doorscategory was removed in favour of the granularuse_*categories. Any existingrules.ymlentries underopen_doorsare ignored on load, so previously locked doors/containers/workstations revert to their defaults — re-apply the desired state with the new commands once after updating.
Notes
command_messagescontrols the vanilla op broadcast only; it does not make non-op players see command executions.see_chatfilters player chat. System, join/leave/death, and plugin messages are broadcast all-or-nothing and are not hidden per viewer.
[1.2.0]
Baseline release prior to this changelog. Existing feature set:
/worldrules chat <true|false> [player]with per-player overrides,bypass, andinfo./worldrules interact <all|category> <true|false> [player]with per-player overrides, per-team overrides (interact team),bypass, andinfo.- Fully configurable, colour-coded messages in
config.yml. /worldrules reload.
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:K3ParxTH:TLex3NoA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:K3ParxTH:TLex3NoA"
}

