Tags
Creators
Details
2.0.2
Compatibility
Changes
π Major Improvements
β‘ Full Folia Support
- Added native Folia compatibility using region-safe and async-safe schedulers
- Implemented a platform-aware scheduler abstraction (Paper / Folia / Spigot)
- Fixed all threading violations (chunk access, block updates, region execution)
- Zone regeneration now runs safely inside region threads on Folia
π§ Smart Platform Detection
-
Automatic runtime detection of:
- Folia
- Paper
- Spigot
-
The plugin adapts its behavior dynamically depending on the server platform
-
No configuration changes required β everything is automatic
π§ Compatibility & Stability
β Spigot Support Restored
- Added safe fallbacks for missing Paper / Adventure APIs
- Automatic legacy text conversion when Adventure components are unavailable
- Teleport handling now adapts to platform capabilities
π§± Regeneration System Improvements
-
Fixed async chunk access errors on Folia
-
Block regeneration is now:
- Region-safe
- Thread-safe
- Platform-safe
-
Players inside regenerating zones are now handled safely on all platforms
π Metrics & Monitoring
π bStats Enhancements
-
Added new custom chart:
zones_totalβ total number of registered regen zones
-
Improved internal metrics reliability on Folia servers
π Internal Refactors
-
Introduced
RegenSchedulerabstraction layer -
Separated platform-specific logic:
PaperRegenSchedulerFoliaRegenScheduler
-
Cleaner architecture and easier future maintenance
-
Improved logging and debug safety
π Fixes
-
Fixed server crashes caused by:
- Async chunk loading
- Unsafe player teleportation on Folia
-
Fixed compatibility issues with:
- Paper 1.21+
- Folia region threading
-
Improved update checker stability
π§ Notes
- No breaking changes for existing configurations
- Existing zones, databases, and configs are fully compatible
- This version lays the groundwork for future performance optimizations
Optional dependencies
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:6bBEOQoK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KhTpa48q:6bBEOQoK"
}

