1.1.2
Compatibility
Changes
RegenerateX v1.1.2
This update focuses on stability improvements, regeneration reliability, and overall plugin performance. Several internal systems have been refined to provide a smoother experience for both players and server administrators.
Improvements
- improved regeneration system stability
- improved block restoration reliability
- improved arena processing workflow
- improved event handling and synchronization
- improved manager communication and task coordination
- improved command execution consistency
- improved queue handling and regeneration scheduling
- improved plugin startup and shutdown procedures
- improved logging and debugging information
Performance
- reduced unnecessary processing during regeneration tasks
- improved async task handling
- optimized regeneration workflow
- improved memory usage in active arenas
- reduced chances of lag spikes during regeneration
- improved overall server performance while regenerating arenas
Stability Fixes
- fixed several edge-case crashes
- fixed regeneration desync issues
- fixed command misfires under heavy load
- fixed multiple internal task handling issues
- improved recovery from failed regeneration operations
- improved validation checks throughout the plugin
General Changes
- cleaned up internal systems
- refined regeneration manager behavior
- updated project version to v1.1.2
- improved overall plugin reliability and maintainability
Goal
Continue improving RegenerateX into a stable and production-ready arena regeneration solution with reliable performance, smoother regeneration handling, and a better experience for servers of all sizes.
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:OyundisK:AOO6zUbw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OyundisK:AOO6zUbw"
}

