Storage Optimization Sentinel

WIPING STORAGE BLOAT,
PROTECTING PLY BUILD.

RetroWorldPurger detects chunks loaded briefly by traveling players and discards them upon unload. Pristine terrain generates fresh on return, saving gigabytes of disk bloat safely.

Chunk Purging Simulator

Click on a grid block, trigger player interactions, and then unload chunks to visually observe the purge logic in action.

Chunk Grid View

Unloaded Chunks
Loaded (Clean)
Player Modifications
Visited (>10s)

Selected Chunk Info

Inhabited Time
Modification Bit
Simulate Player Actions:
Storage Reclaimed
Permanent Saves Saved to region files

Why it is 100% Safe

A complete breakdown of our multi-layered boundary protection mechanics.

1

Direct Actions

Any standard player interaction immediately tags a chunk. This includes placing or breaking blocks, striking flint & steel, igniting TNT, and right-clicking items like doors, levers, anvils, and chests.

2

Cross-Border Pistons

Redstone machinery pushes blocks across boundaries. If a piston extends or retracts and shifts block states from one chunk into an adjacent chunk, the destination chunk is flagged instantly.

3

Fluid Flows

When water or lava flows across a chunk border, the destination chunk block states change. If the fluid originates from a modified chunk, the modification flag propagates across the border to preserve cascades.

4

Dispensers & Projectiles

If a dispenser shoots projectiles or sets water buckets across chunk lines, or if a player fires arrows/fireworks landing on target blocks in adjacent chunks, those chunks are protected immediately.

5

Explosions & Structures

Explosions (Creepers, TNT, respawn anchors) and bonemealed saplings (like dark oak/mega spruce) spill over chunk lines. The plugin scans all affected block lists to flag every touched chunk.

6

Inhabited Ticks Buffer

Minecraft natively tracks how long players stand inside chunks. If a player stands still, talks, or idles in a chunk for more than the configurable limit (default: 10s), the chunk is automatically saved.

Configuration

Tune your purge metrics easily. Standard `config.yml` settings file.

config.yml
# Worlds that should be excluded from chunk cleaning
blacklisted-worlds:
  - "lobby"

# Distance from the world spawn (in blocks) where chunks are never purged
spawn-protection-radius: 500

# Minimum player presence (in ticks) inside a chunk before it gets saved permanently
# 200 ticks = 10 seconds.
min-inhabited-time-ticks: 200

# Automatically populated stats tracker
stats:
  total-chunks-deleted: 0
  total-bytes-saved: 0