1.0.0
Compatibility
Changes
Worldrules
Handle your world, your way.
A lightweight permissions toggle for events, minigames, and any moment when you need to lock down chat or interactions on the fly. Unlike WorldGuard or other protection plugins, Worldrules isn't about regions — it's about flipping a switch and changing what your players can do right now.
Why Worldrules
- Built for events. Toggle chat, building, eating, projectiles in seconds.
- Lightweight. One config file, no database, no dependencies.
- Bypass system. Give staff or hosts full freedom while restricting everyone else.
- Per-player or global. Fine-grained control without spreadsheets.
- Customizable deny messages. Full legacy
&color support. - Modern blocks supported. Vault, Crafter, Trial Spawner, Decorated Pot, Chiseled Bookshelf — all covered.
Commands
All commands require the worldrules.admin permission (default: OP).
Chat
| Command | Effect |
|---|---|
/worldrules chat <true|false> |
Enable or disable chat globally |
/worldrules chat <true|false> <player> |
Override chat for a specific player |
/worldrules chat bypass <player> <true|false> |
Grant chat immunity (always allowed) |
Interact
| Command | Effect |
|---|---|
/worldrules interact <true|false> |
Toggle ALL interactions globally (shorthand for all) |
/worldrules interact all <true|false> |
Same as above, explicit form |
/worldrules interact <category> <true|false> |
Toggle one category globally |
/worldrules interact <all|category> <true|false> <player> |
Per-player override |
/worldrules interact bypass <player> <true|false> |
Grant interaction immunity |
Misc
| Command | Effect |
|---|---|
/worldrules reload |
Reload the config file |
/wr |
Alias for /worldrules |
Interaction Categories
| Category | Blocks |
|---|---|
place_blocks |
Placing any block, hanging items, dumping liquid buckets |
break_blocks |
Breaking any block |
open_doors |
Doors, trapdoors, fence gates, levers, buttons, pressure plates, chests, furnaces, anvils, crafting tables, vaults, crafters, and every other openable/utility block |
eat |
Food, milk buckets, regular potions |
use_bow |
Bows and crossbows |
use_projectiles |
Snowballs, ender pearls, splash potions, eggs, wind charges, fishing rods |
all |
Everything above + entity interactions (milking, mounting, item frames, armor stands) |
How it Works
Priority order
- Bypass beats everything. A bypassing player ignores all rules.
- Per-player override beats global. Set someone's chat or interaction independently.
- Global
trueclears overrides. Running/worldrules interact true(orchat true) wipes per-player rules so everyone returns to the global default.
Example flow
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:ZBJcLcFJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:K3ParxTH:ZBJcLcFJ"
}

