1.0.9
Compatibility
Changes
RegenerateX v1.0.9
This update mainly focuses on fixing the core regeneration system improving stability and making arena resets finally more reliable for production servers.
Major Fixes
- fixed fake regeneration success messages
- plugin now validates actual block restoration before sending completion messages
- fixed several regeneration queue failures
- fixed async regeneration instability
- fixed silent regeneration cancellation issues
- fixed broken placeholder updates during regeneration
- fixed some schematic corruption problems
- fixed invalid arena snapshot handling
- fixed failed block placement handling
- fixed regeneration tasks randomly stopping
Added
- added schematic snapshot validation system
- added corruption detection for invalid schematic files
- added safer async queue protection
- added automatic regeneration failure detection
- added better regeneration debug logging
- added real-time TPS monitoring system
- added automatic TPS pause and resume support
- added smarter regeneration throttling
TPS & Performance Improvements
- regeneration now pauses automatically on unsafe TPS
- regeneration resumes automatically once TPS stabilizes
- improved chunk batching performance
- improved async scheduler stability
- improved packet handling during large regenerations
- improved server ping stability
- improved multi arena performance
PlaceholderAPI Improvements
added real-time placeholder support for:
- %regeneratex_progress%
- %regeneratex_blocks%
- %regeneratex_timer%
- %regeneratex_tps%
placeholders now update more accurately during active regeneration.
Logging Improvements
improved console logging and debugging:
- real regeneration progress tracking
- live TPS debug messages
- schematic loading validation
- failed chunk operation warnings
- queue processing logs
Goal
make RegenerateX fully stable reliable and production ready with real arena restoration stable async processing stable TPS and smooth lag free regeneration for large Minecraft servers.
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:ZYXq0tSh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OyundisK:ZYXq0tSh"
}

