Tags
Creators
Details
2.4.0-beta.2
Compatibility
Changes
Special thanks to #15 The InPlace regeneration engine will now also be set as the default engine for fresh installations on version 1.21 and above.
Additionally, to address the increasingly cluttered configuration, 2.4.0-beta.2 introduces a full config cleanup.
The config-version will be updated to 20. Legacy settings will be fully migrated to the new configuration format, making settings categorized more clearly and easier to read. Key changes include:
- Removed the redundant
sql-processing-ticksetting. - Moved
messagessettings to thelangfolder.
Important Notes
- Always back up your database and map files before updating NatureRevive.
- Although we have made every effort to ensure full compatibility with claim and spawn plugins, please make sure to back up your map files prior to updating.
- If you need to use FastAsyncWorldEdit, we recommend using this optimized fork
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:fF0VA1ng"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UawBthbH:fF0VA1ng"
}

