3.4
Compatibility
Changes
EXPGems v3.4 โ Modernisation & Optimisation Patch
This update focuses on cleaning up the older EXPGems codebase, improving performance, and fixing several long-standing issues while keeping the plugin behaviour familiar and compatible with existing setups.
โจ Main Changes
- Modernised large parts of the plugin source.
- Reduced repeated code across gem tiers, ore EXP, crop EXP, crafting, and GUI handling.
- Improved internal item checks for EXP gems and tomes.
- Kept the original commands, permissions, config paths, and gameplay flow intact.
- Added a cleaner console startup banner.
- Improved compatibility with newer Spigot/Paper versions.
๐ Gem Improvements
- Fixed gems sometimes doing nothing when right-clicked.
- Gems now correctly work on both right-click air and right-click block.
- Added clearer permission feedback when a player is missing a required gem tier permission.
- Fixed hidden gem reveals sometimes showing a different gem name than the item actually received.
- Fixed Tier VI lore using hardcoded EXP values instead of config values.
- Fixed the
Tier5.Chancetypo issue by supporting the correctTier-5.Chancepath.
โก EXP & Particle Fixes
- Fixed a Spigot 1.21.10 particle crash caused by particles requiring extra data.
- Added safer particle spawning so unsupported/changed particle behaviour no longer breaks gem usage.
- EXP tomes now use the safer particle system too.
- Gem usage should now complete properly instead of erroring before EXP is awarded.
๐พ Ore & Crop EXP Optimisation
- Reworked ore EXP handling into a cleaner mapped system.
- Reworked crop EXP handling into a cleaner mapped system.
- Kept existing ore and crop config paths working.
- Silk Touch checks still prevent ore EXP where intended.
- Fully grown crop checks are preserved.
๐ Crafting & Recipes
- Cleaned up tier crafting permission checks.
- Recipes are now registered in a cleaner and safer way.
- Existing gem upgrade recipes remain the same.
- EXP Tome crafting remains supported.
๐ฆ Admin GUI
- Cleaned up the admin GUI code.
- Removed reliance on one shared static inventory.
- Existing admin buttons and toggles remain available.
- GUI still supports giving gems, toggling ore EXP, crop EXP, gem names, hidden gem cost, and reloading config.
๐งช Commands Kept
/gem admin/gem timer/gem ores/gem crops/gem names/gem cost/gem tome/gem rl
๐ Permissions
The gem tier permissions are still used:
gem.tier1
gem.tier2
gem.tier3
gem.tier4
gem.tier5
gem.tier6
gem.admin
gem.rl
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:8pKhVJ8t:KbB18z5C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8pKhVJ8t:KbB18z5C"
}

