Tags
Creators
Details
2.3.3
Compatibility
Changes
Support has now been updated to 26.2. Based on our testing, everything works correctly on Paper servers.
For the customized Folia FastAsyncWorldEdit plugin:
Previously, it created a new ServerLevel to regenerate chunks, and then unloaded the temporary world by calling cleanup().
However, Folia does not appear to support unloading worlds in this manner, causing the temporary worlds to remain in memory indefinitely.
As a result, every regeneration created another temporary world that could never be unloaded, leading to an ever-growing number of worlds in memory and ultimately causing a severe memory leak.
This release includes a fix for that issue.
Under Folia, the temporary world is now created only once and then reused for all future chunk loading and unloading operations, preventing the memory leak caused by repeatedly creating new worlds.
Regarding the customized FastAsyncWorldEdit required for Folia:
The original project has not been updated to support this protocol version (it currently supports up to 1.21.11 only). Therefore, unless you are capable of maintaining your own build, you should not use this plugin on Folia with protocol versions 26.1 through 26.2.
Warning
- Before updating NatureRevive, make sure to back up both your database and your world files.
- Although we have thoroughly tested compatibility with land protection, respawn, and other related plugins, you should still back up your world files before updating.
- If you intend to use this plugin on Folia, please use the customized FastAsyncWorldEdit build provided below: All changes: https://github.com/BrilliantTeam/FAWE-Folia
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:iuutOM5P"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UawBthbH:iuutOM5P"
}

