NatureRevive - brilliant

Biome write-back

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](https://github.com/BrilliantTeam/FAWE-Folia)

This also introduces new configuration options:

  # Regenerate chunks containing Towny town blocks, but keep the blocks inside the town blocks.
  towny-strict: false
  # Regenerate chunks containing WorldGuard regions, but keep the blocks inside the regions.
  worldguard-strict: false

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](https://github.com/BrilliantTeam/FAWE-Folia)

Special thanks to [#15](https://github.com/BrilliantTeam/NatureRevive-brilliant/p… 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-tick setting. * Moved messages settings to the lang folder.

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](https://github.com/BrilliantTeam/FAWE-Folia)

Starting from version 1.21, due to changes in chunk generation mechanics, Paper dropped support for the CraftWorld.regenerateChunk() method. As a result, using NatureRevive on 1.21+ required reliance on FastAsyncWorldEdit (FAWE) as an auxiliary tool. However, FAWE regeneration causes substantial performance overhead and has virtually abandoned Folia support. Although I created an optimized fork, it remained inconvenient—and for 26.X versions, Folia support was non-existent. Consequently, I continued searching for a viable solution (briefly mentioned in version 2.2.1). After taking a deep dive into the original Bukkit engine method, I realized it was essentially an enhanced variation of ChunkGenerator + Seed. I believed it was possible to reproduce this behavior on 1.21+, which led to the creation of 2.4.0-beta.1! You can now select the InPlace regeneration engine without needing FAWE installed. It utilizes the game's native chunk generation pipeline supplemented by NatureRevive's content injections (such as vanilla structures, loot chests, etc.) to regenerate chunks in the most efficient, safe, and stable manner possible. However, the Paper team abandoning this method in 1.21 means it is not something a solo developer can fully maintain overnight. With every game update, ChunkGenerator + Seed mechanics or my custom injected content may undergo underlying changes. Therefore, version 2.4.0 is currently released as a beta. I welcome servers running different versions to help test and complete the InPlace engine implementation. (Currently tested and confirmed functional only on 1.21.1 Paper/Folia)

Important Notes

* Always back up your database and world files before updating NatureRevive. * Although we have done our best to ensure compatibility with residence/spawn plugins, please make sure to back up your map files prior to updating. * If you still require FastAsyncWorldEdit, we recommend using [this optimized build](https://github.com/BrilliantTeam/FAWE-Folia).

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](<https://github.com/BrilliantTeam/FAWE-Folia>)

Optimization

- Added ChunkClaimPlugin2 support, no config required - Fixed the startup message incorrectly detecting whether it had loaded itself - A customized build of FastAsyncWorldEdit, for Paper/Folia servers - Structure data is now preserved during regeneration, so map upgrades are handled correctly - Improved FAWE's regen method, substantially reducing CPU and memory usage - Servers with a large amount of regeneration data are recommended to use this customized FastAsyncWorldEdit - For now I do not intend to submit these optimizations upstream to FastAsyncWorldEdit, since it does not support 26.X - That said, I have no objection to other developers taking my code upstream themselves, __as long as you credit the source__ - Contributions adding 26.X support to this customized FastAsyncWorldEdit project are also welcome Regarding the customized FastAsyncWorldEdit plugin: the original project does not support that version (it only goes up to 1.21.11), so unless you are able to do the development work yourself, you should not be using this plugin on 26.X at this time.

Please Read

- Always back up your database and world files before updating NatureRevive. - Although we have done everything we can to ensure that land-claim, regeneration and other plugin features work correctly, please still back up your world files before updating. - To use this plugin on Folia, please use the FastAsyncWorldEdit build provided below — [all changes](<https://github.com/BrilliantTeam/FAWE-Folia>)

Fixed

Fixed a NullPointerException on chunk load when a world could not be resolved ( Bukkit.getWorld() returned null ), this could crash the regeneration flow, most notably right after installing the plugin. The regeneration flow now safely skips any task whose world is unavailable instead of throwing. Also added the in-flight regeneration marker count ( regenInFlight ) to /nr debug . Thanks to @MakeDecisionWorth for the report and fix (#14). --- 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

Fixed

Only process already-generated chunks; ungenerated ones have no player edits to restore, so skip them. --- 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

Fixed

Fixed a crash caused by failure to detect FAWE when the version number includes a plus sign (e.g., 2.15.1+489a5d7) --- 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

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

The plugin now supports up to version 26.1.2, and our tests show it runs smoothly on Paper servers without any issues! However, regarding the customized FastAsyncWorldEdit plugin required for Folia, the original project has not yet been updated to support this version (it only supports up to 1.21.11). Therefore, unless you have development capabilities to modify it yourself, you should not use this plugin on Folia versions 26.1 through 26.1.2 at this time.

Before updating the NatureRevive version, please make sure to back up your database and map files.

Although we have done our best to ensure that all plugin functions (such as claims and reviving) work flawlessly, please be sure to back up your map files before updating.

If you need to use this plugin on Folia, please use the FastAsyncWorldEdit version provided below. [All Changes](https://github.com/BrilliantTeam/FAWE-Folia)

- Fix empty read when migrating out of SQLite (table name was hardcoded; now uses config). - Migrating to YAML now actually saves (used to only write to memory). - Migration reads source then writes target directly, no more queue race / data loss. - Reports failures properly and closes connections when done.

Before updating the NatureRevive version, please make sure to back up your database and map files.

Although we have done our best to ensure that all plugin functions (such as claims and reviving) work flawlessly, please be sure to back up your map files before updating.

If you need to use this plugin on Folia, please use the FastAsyncWorldEdit version provided below. [All Changes](https://github.com/BrilliantTeam/FAWE-Folia)

Language Support Added:* Starting from this version, a new lang folder has been introduced, with the plugin's default language set to en_US. Custom Language Files:* You can now create your own language files within this folder (pre-configured options for zh_TW and en_US are available by default). Platform Expansion: In addition, starting with this release, NatureRevive will be published on Spigot, Hangar, and Modrinth*, making it accessible for more people to discover and download!

Before updating the NatureRevive version, please make sure to back up your database and map files.

Although we have done our best to ensure that all plugin functions (such as claims and reviving) work flawlessly, please be sure to back up your map files before updating.

If you need to use this plugin on Folia, please use the FastAsyncWorldEdit version provided below. [All Changes](https://github.com/BrilliantTeam/FAWE-Folia)