Tags
Creators
Details
2.3.8
Compatibility
Changes
Optimization
- Previously every entry was read on each pass, which consumed a large amount of CPU.
- TTLs are now kept in sorted order (ExpiryIndex), so only the entries at the front, the ones that have actually expired β are examined.
- Measured at the 400,000-chunk scale: usage drops from 5β8% down to under 1%.
Regarding the customised FastAsyncWorldEdit build: upstream has not added support for that version (it only goes up to 1.21.11), so unless you are able to do the development work yourself, you should not use this plugin on 26.X for now.
Please note
- Always back up your database and world files before updating NatureRevive.
- Although we have done our best to ensure that land-claim, regeneration and other plugin features behave correctly, please still back up your world files before updating.
- If you want to run this plugin on Folia, use the FastAsyncWorldEdit build provided below β all changes
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:UawBthbH:JHpzUTAA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UawBthbH:JHpzUTAA"
}

