Tags
Creators
Details
1.3
Compatibility
Changes
๐ Risers Gemstone Plugin v1.3 โ Bundle Exploit Patched
This update addresses a critical exploit that allowed gems to be stored inside bundles, bypassing intended restrictions. The system now fully blocks this behaviour, preserving gem integrity and gameplay balance.
๐ Exploit Fixes
- ๐ซ Gems can no longer be stored in bundles
- ๐งผ Improved item filtering logic to catch edge cases
- โ๏ธ Internal checks tightened for container interactions
- ๐ Why It Matters Bundles were unintentionally allowing players to bypass gem protection logic. This patch ensures gems remain exclusive, visible, and non-hoardable โ just as intended.
๐ฆ Notes
Thanks to community feedback and testing, this exploit was identified and resolved quickly. If you spot any other edge cases or have ideas for future gem mechanics, share them on GitHub or the Modrinth page.
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:j0hnqF0l:GHBuRNU9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:j0hnqF0l:GHBuRNU9"
}

