3.0.1
Compatibility
Changes
♻ RecyclePlugin — v3.0.1
🛠 Stability & Code Quality
Small follow-up to the v3.0.0 platform migration. No gameplay or config changes — internal robustness fixes only.
Fixed
- Potential NullPointerException when resolving the fallback sound key for a configured sound effect with no explicit
soundentry - Plugin startup looked up
/recycleand/rpadmincommands twice instead of reusing the result, which could theoretically return inconsistent state between the two lookups
Improved
- Narrowed several overly broad
catch (Exception e)blocks (sound/particle resolution, numeric config parsing) down to the exact exception type each call site can throw
♻ RecyclePlugin — v3.0.0
🧱 PLATFORM MIGRATION — Paper 26.2 / MC 26.2 / JDK 25
This release migrates RecyclePlugin to the current Paper/Minecraft platform, following Mojang/Paper's switch to year-based versioning in 2026.
- 🔧 Build target bumped to JDK 25 (
maven.compiler.release) - 📦
paper-apidependency bumped from1.21.11-R0.1-SNAPSHOTto26.2.build.121-stable - 📝
plugin.ymlapi-versionbumped from1.21to26.2 - ✅ Full codebase audit against the new API — no removed or deprecated methods found (verified via
javac -Xlint:deprecation -Xlint:removalagainst the realpaper-api-26.2jar) - 🚫 No gameplay or configuration logic changed — this is a platform compatibility release only
Why a major bump
This is a breaking compatibility change: builds targeting JDK 25 / Paper 26.2 will no longer run on older Paper/Minecraft servers (pre-26.2), so the major version reflects that boundary rather than new features.
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:fmSo86JZ:h179KOoW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fmSo86JZ:h179KOoW"
}

