Links
Tags
Creators
Details
1.3.1
Compatibility
Changes
🚨 RulesPlugin v1.3.1 — "The" RulesPlugin Update
This update focuses on fixing several issues reported by the community and improving the overall reliability of RulesPlugin.
🔧 Fixed
- ✅ Fixed GUI item movement through click, shift-click, number-key swaps, offhand swaps and drag actions
- ✅ Fixed leaked GUI items remaining in player inventories
- ✅ Fixed invalid
config.ymlvalues being silently accepted - ✅ Fixed
/rules reloadapplying broken configurations - ✅ Fixed compatibility issues caused by Paper-only API usage
- ✅ Fixed invalid material names such as
Sticky_pistonandDiamond_Sword
🛡 GUI Security Improvements
RulesPlugin now protects GUI items much more aggressively.
- 🔒 GUI items are automatically detected and removed if they somehow leave the menu
- 🔄 Added automatic cleanup for leaked GUI items
- ⚡ Protection covers desyncs, lag, creative interactions, drag actions and inventory edge cases
🧠 Improved Configuration Handling
- 📄
config.ymlis now validated before changes are applied - 🚫 Invalid YAML configurations are no longer silently accepted
- 🔧 Material names are normalized automatically when possible
- ♻ Safer reload process for
/rules reload
✅ Compatibility
- ✔ Compatible with Minecraft 26.1.x
- ✔ Compatible with Paper
- ✔ Compatible with Spigot
- ✔ Compatible with Bukkit
- ✔ Reduced dependency on Paper-specific APIs
❤️ Thanks
Huge thanks to:
- CarrFN
- Charlie
- Break_Cats
- Some one
- maihari
for reporting bugs and helping improve RulesPlugin.
Your feedback directly shaped this update ❤️
📘 Documentation: https://rulesplugin.netlify.app
⬇ Download: Replace the old JAR with this version and restart your server.
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:qi7dyoZ5:5Kzk2TKI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qi7dyoZ5:5Kzk2TKI"
}

