Tags
Creators
Details
2.0.3
Compatibility
Changes
[v2.0.3] β 2026-01-20
π Highlights
This release introduces a brand new public API architecture and establishes a stable foundation for external addons.
β οΈ This release contains breaking changes for addon developers,
but remains fully backward-compatible for server owners and players.
This is the recommended base version for future addon development.
π§© API (Public & Stable)
β New
- Introduced a fully separated API module (
regensystem-api) - Added official API entry point:
RegenSystemAPI
- Added explicit API versioning:
API_VERSIONAPI_MAJOR,API_MINOR,API_PATCH
- Introduced new core API contracts:
ZoneManagerZoneZoneFlagRegenResult
π― Events API
All zone lifecycle events are now officially exposed and documented:
ZoneCreateEvent(cancellable)ZoneDeleteEvent(cancellable)ZoneReloadEvent(cancellable)ZonePreRegenEvent(cancellable)ZonePostRegenEvent(non-cancellable)ZoneFlagChangeEvent(cancellable)
π‘οΈ API Stability & Safety
Added
- Clear separation between public API and internal implementation
@ApiStatus.Internalon non-public methods@ApiStatus.NonExtendableon API events- Strict API boundaries (no core access)
Guarantees
- API stability within the same major version
- No reflection or unsafe hooks required
- Safe event-driven extension model
β Breaking Changes (Addon Developers)
β οΈ Yes β Breaking API Changes
- Complete API redesign
- Old API contracts are not compatible
- Addons targeting versions
< 2.0.3must be updated
Migration required for all external plugins.
β No Breaking Changes (Server Owners)
- Existing zones are preserved
- Configuration files unchanged
- Commands and permissions unchanged
- Database format unchanged
No action required for server administrators.
π Compatibility
- Minecraft: 1.20.x β 1.21.x
- Platforms:
- Paper β
- Folia β
- Spigot β
- Java: 21+
π§ͺ Experimental API
- No experimental APIs exposed in this release
- Future experimental APIs will live under:
fr.darklash.regensystem.api.experimental
π¦ Dependency (JitPack)
compileOnly("com.github.DarkLashDev:RegenSystem:v2.0.3")
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:KhTpa48q:muUY5uq5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KhTpa48q:muUY5uq5"
}

