Chunk Reset

A server side mod to reload chunks that players have not visited in a long time.
chunkreset.png

chunkreset.png

Description

Chunk Reset

Chunk Reset

Server-side mod that automatically regenerates chunks nobody has visited for a while, so your world stops turning into a wasteland, without touching your bases, stored loot, pets or respawn points.

Explore a server for a few weeks and the map fills up with scars: stripped hillsides, mined-out caves, looted villages, empty end cities, a landscape that has nothing left to find. Chunk Reset quietly puts the untouched parts of the world back the way they were generated, and leaves everything players actually care about alone.

How it works

  • Tracking: while players are online, the chunks around them are stamped "visited".
  • Sweeping: every few minutes (you choose how many), chunks that nobody has been near for your chosen amount of time are examined on a background thread.
  • Protecting: anything that looks player-made, or that a player depends on, keeps its chunk safe (see below).
  • Regenerating: the remaining chunks are wiped a few per tick. The game regenerates them from the world seed the next time anyone loads them: ores, trees, structures and fresh loot return.

Nothing blocks the server thread for long, and chunks that are loaded or force-loaded at the moment of deletion are always skipped.

What stays safe

By default a chunk is never regenerated if it:

  • is near any player's saved respawn point, online or offline (a bed or respawn anchor only counts if a player is actually linked to it, so abandoned beds protect nothing)
  • is where an offline player last logged out, so nobody returns to terrain that changed under their feet
  • contains a lodestone, or is within a configurable radius of one. Lodestones never generate naturally, so players can place one as a claim marker for their base
  • contains named, tamed or leashed mobs, armor stands, or boats
  • contains blocks such as beacons, conduits, ender chests, enchanting tables, jukeboxes or nether portals
  • is inside a protected region you define (the End's central island is protected by default)
  • is next to another protected or recently visited chunk, so you never get ugly seams

Villages, end cities, fortresses, bastions, mansions and mineshafts are not protected by default, so they reset. Looted structures get their loot back, and so do looted chests.

Ultra configurable

Almost everything is an option, and the config file reloads while the server is running:

  • When: first-sweep delay, sweep interval, how long a chunk must sit unvisited, only run while few or no players are online
  • Where: which dimensions (whitelist or blacklist, modded dimensions supported), plus per-dimension overrides for timing, buffers and dry run
  • What is protected: blocks, entities, structures, biomes and items by id or * glob (so create:* works for modded content), protected regions in block coordinates, named/tamed/leashed mobs, player-stored containers, minimum time spent in a chunk
  • Respawn and logout protection: radius and expiry for each
  • Tracking: radius, square or circular area, sample rate, whether spectators count
  • Deletion: chunks per tick, cap per sweep, oldest/newest/random order, and whether terrain, villager POI data and stored entities are each wiped
  • Safety net: optionally archive every chunk's data before wiping it, with automatic cleanup after N days
  • Logging: quiet, normal or verbose, with example chunk coordinates in dry run

Safety first

  • Dry run is on by default. The first sweeps only log what would be regenerated. Read the log, then switch it off.
  • Back up your world before enabling real deletion. Regenerated chunks cannot be recovered unless you enable the archive.
  • Existing chunks are adopted when the mod is first installed, so the clock starts at install; nothing is wiped on day one.

Compatibility

  • Minecraft 26.3, on NeoForge and on Fabric (the Fabric version needs Fabric API).
  • Server-side only. Players do not need to install it.
  • Works with modded blocks, entities and dimensions through the glob lists. It does not touch worldgen, so mods that add structures or biomes just regenerate like vanilla ones, as long as the mod set doesn't change between generations.
  • Tags (#minecraft:...) are not supported in the lists; use ids and globs.

FAQ

Will it crash if a player logs into a chunk that was wiped? No. A wiped chunk is the same as an unexplored one: the game generates it on demand. Offline players' last positions are protected by default anyway.

Is the new terrain different? No. Regeneration uses the world seed, so terrain comes back as the original world. It is not new terrain.

Do chests protect a chunk? Not by default. A chest that has been looted, or that a player filled, regenerates along with its chunk. If you want player storage to be safe, turn on protectContainersWithItems, or have players place a lodestone in their base.

What about structures I built inside a village? If you left a lodestone, a beacon or a linked bed there, the chunk is protected. Chests and decoration (item frames, paintings) are not protected by default, but you can turn on container protection or add those entities to the protected list.

Where is the config? NeoForge: config/chunkreset-local.toml. Fabric: config/chunkreset.json5. Both are fully commented.

Installation

  1. Install on your server (and nothing else on the client).
  2. Start once to generate the config, then adjust it. Leave dryRun on for the first few sweeps.
  3. Check the log for [chunkreset] lines, then turn dryRun off when you are happy with what it reports.

Chunk Reset Team

profile avatar
  • 2
    Projects
  • 5.1K
    Downloads

I am a Minecraft mod/resource pack creator. You can find more of my stuff on modrinth.

More from Henry_Shaughnessy