- Native Minecraft Version:
- Tested Minecraft Versions:
- Source Code:
- https://github.com/Jikoo/RegioneratorDisclaimerCommands require the regionerator.command permission.
Regionerator deletes chunks from your world by directly modifying and deleting region files. This cannot be undone. Keep regular backups. The author is not responsible for any damages to your world or server incurred by using this plugin. Use at your own risk!
Regionerator deletes unused chunks and regions, allowing you to free up disk space and get rid of old builds or devastated land.
Players in Spectator gamemode do not cause land to be marked visited, as they are not actually physically there.
/regionerator - Report current status of all worlds.
/regionerator reload - Reload the configuration and restart all deletion tasks.
/regionerator pause - Pause deletion tasks. To prevent issues, the plugin will finish the region it is currently checking before pausing.
/regionerator resume - Resume deletion tasks.
/regionerator check - Check the status of a chunk.
/regionerator cache - Check cache/queue counts.
/regionerator flag - Permanently flag the relevant area as visited.
/regionerator unflag - Unflag the relevant area.
- No parameters (e.g. /regionerator flag)
- Edit flag on current chunk
- Chunk x and chunk z (e.g. /regionerator unflag 0 0)
- Edit flag on specified chunk
- World name, chunk x, chunk z (e.g. /regionerator flag world 0 0)
- Player/console supported
- Edit flag on specified chunk in world
- Selection (e.g. /regionerator unflag selection)
- Edit flags on all chunks within selection
- Requires WorldEditDevelopers
If you're looking to support Regionerator deleting area in which you have data stored, wipe data when the ChunkPopulateEvent is fired. Regionerator does not guarantee that chunks are deleted on first attempt, so there is no sense firing an unreliable event when an attempt is made.
ConfigurationCode (YAML):# Square around each player's current chunk to flag.
# Every x seconds, chunks around each player online are flagged.
# Flags older than x days can be ignored and the region deleted.
# To disable flagging, set this to 0.
# days-till-flag-expires must be greater than 0 to be used with delete-new-unvisited-chunks
# Chunks generated after the plugin is installed are automatically flagged.
# If false, these chunks will be permanently flagged until visited.
# Setting this value to false will allow you to pre-generate your maps for reduced load from exploration.
# It will also reduce the amount of time wasted deleting untouched areas.
# Time in between deleting regions in ticks (20 ticks = 1 second)
# Chunks checked for deletion per interval. Default (128) handles an entire region every 9 intervals.
# If this value is 1024 or lower (1 or fewer regions per cycle) an entire run cycle is dedicated to deletion to prevent lag.
# Hours between deletion cycles
# Whether or not to remember time for next cycle on plugin load
# Worlds the plugin is able to delete regions in
# Hooks to attempt to check for protections from.
# If your protection plugin of choice isn't here, ask!
# Debug-level enables more and more verbose logging of actions as increased.
# OFF - no debug messages
# LOW - Minimal debug messages, periodic deletion reports
# MEDIUM - More debug messages. Spammy, not recommended.
# HIGH - Lots of debug messages. Don't enable this unless you have a serious issue.
debug-level: LOWFAQMy server is lagging! What can I do?
Try reducing chunks-per-deletion. Deletion must be done on the main thread to prevent potential world corruption, so there isn't much else that can be done. After the initial run, during which there's a lot of area to delete, it runs a lot more smoothly.
Why is it taking so long to start deleting area?
Regionerator doesn't magically know what has and hasn't been visited. It needs to gather data for as long as it takes chunks to become unvisited before it can tell what's safe to delete. Regionerator does fall through to Minecraft's internal last modification timestamp, but this requires the chunk to have actually been modified (entity movement, block changes, etc.), not just visited.
Why does regeneration take so long?
If cycles are taking too long for your taste, try increasing chunks-per-deletion or decreasing ticks-per-deletion.
Do you support custom world generators?
Regionerator doesn't actually regenerate area, it deletes it. Whatever world generator you're using will then provide the chunk when it generates again.
Will you add support for this protection plugin?
Sure, point me to it. Provided it has a way I can efficiently check for claims in a chunk, I'll do it. I can't guarantee it'll happen soon, but Regionerator is open source, you're free to submit a pull request. I also can't effectively test plugins that I do not use myself, so I cannot guarantee that it will function properly.
Which protection systems are supported?
I only test hooks which I have an environment set up for. I'd advise you not to put a plugin of this nature on a live server without testing period anyway, but be even more cautious if you are using an untested hook.
- BSkyBlock (successor of ASkyBlock) has its own deletion system which is sufficient to not require Regionerator present. It's not supported, but it doesn't need to be. Don't run Regionerator on a BSkyBlock world.
- Civs (untested hook)
- Factions / FactionsUUID (untested hook)
- Feudal (vouch)
- GriefDefender (untested hook)
- Kingdoms (untested hook)
- Landlord (untested hook)
- Lands (untested hook)
- PreciousStones (untested hook)
- RedProtect (untested hook)
- Residence (vouch)
- Towny (untested hook)
- Vanilla's spawn protection
If you're using one of the hooks, please tell me if you've tested it and can confirm it works - it'll save future users the initial worry (though I recommend still testing anyway).
How can I test a protection system effectively?
There are two easy ways to go about it:
How can I force deletion to run early?
- Use `/regionerator check` ingame to test the chunk you're standing in. All active hooks will display the chunk's status.
- Force deletion to run early. When complete, log in and examine protections.
There are two methods:
- Set visit duration to 0 days prior to enabling worlds
- Manually set the world's next-cycle to a low number above 0 prior to starting the server.
Available on GitHub.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Gradual deletion of unvisited terrain