How to Reset the Nether/End Without Losing Overworld

After a few weeks on a busy survival server, the Nether turns into a wasteland. Ancient debris gets mined out, bastion remnants are stripped clean, and blaze spawners sit in broken grinders. The End is the same story, chorus trees chopped, end cities looted, shulker boxes farmed to extinction. Resetting these dimensions gives the server fresh resources without touching the Overworld, where players have built their bases and put in hundreds of hours.

Why reset dimensions?

Resource depletion is the primary reason. Once every ancient debris vein within the world border has been mined, Netherite becomes unobtainable for new players. End cities stop spawning elytras once they have all been looted. Resetting regenerates every structure, ore vein, and mob spawner in the dimension while preserving the Overworld entirely.

Some servers also reset to pick up new content. When Mojang adds structures or biomes to the Nether or End in an update, existing chunks keep their old terrain. Deleting the dimension forces the server to generate it fresh with the new worldgen.

Before you delete anything

• Warn players, announce the reset at least 48 hours in advance. Players may have built farms, bases, or stored items in the Nether or End. Give them time to move valuables to the Overworld.
• Create a backup, even though you are only deleting one dimension, back up the entire server. If something goes wrong and you accidentally delete the Overworld folder, the backup saves you.
• Kick all players, if anyone is logged in inside the Nether or End during deletion, their playerdata may reference chunks that no longer exist, causing login errors.

Step-by-step: resetting on a vanilla or Paper server

On a standard Minecraft, Spigot, or Paper server, the Nether and End are stored as subfolders inside the main world directory. If your server.properties file says level-name=world, the structure looks like this:

server/
├── world/              # Overworld, DO NOT DELETE
│   ├── region/
│   ├── DIM-1/          # Nether
│   │   └── region/
│   └── DIM1/           # End
│       └── region/

Resetting the Nether

1. Stop the server completely. Do not just reload, files may be locked.
2. Navigate to world/DIM-1/.
3. Delete the entire DIM-1 folder (or rename it to DIM-1_backup if you want a safety net).
4. Start the server. Minecraft detects the missing folder and generates a fresh Nether.

Resetting the End

1. Stop the server.
2. Delete world/DIM1/.
3. Start the server. A new End dimension generates, including the main island, the dragon fight, and all outer end cities.

Critical: do not delete the world/ folder itself. Only delete the DIM-1 or DIM1 subfolders. Deleting the parent wipes the entire Overworld, playerdata, and advancements.

Resetting with Multiverse

If you use Multiverse-Core, each dimension may be a separate named world (like world_nether and world_the_end). The folder structure differs:

server/
├── world/              # Overworld
├── world_nether/       # Nether (separate folder)
└── world_the_end/      # End (separate folder)

With Multiverse, you can use its built-in commands:

/mv delete world_nether
/mv confirm

This removes the Nether world from Multiverse's registry and deletes its files. Then re-import a fresh one:

/mv create world_nether NETHER

Multiverse handles the linking automatically. The advantage here is that you never need to touch the file system manually, reducing the risk of accidentally deleting the wrong folder.

For the End:

/mv delete world_the_end
/mv confirm
/mv create world_the_end END

Handling playerdata after a reset

If a player was in the Nether when the dimension was deleted, their playerdata file still records their last position in that world. When the server starts with a fresh Nether, the chunk at those coordinates exists again (newly generated), so usually the player loads fine, they just appear in an unfamiliar spot. However, if the world name changed or the playerdata references a world that no longer exists, they may get stuck in a login loop.

The fix: use an NBT editor (like NBTExplorer) to open the player's .dat file and change their Dimension tag to minecraft:overworld and set their position to the Overworld spawn coordinates. Alternatively, use EssentialsX spawn-on-join to force players to the Overworld spawn on login.

Scheduling regular resets

Many servers reset the Nether every 2–4 weeks and the End every 4–8 weeks. You can automate this with a few approaches:

• Script + cron job, write a shell script that stops the server, deletes the dimension folder, and restarts. Schedule it with cron on Linux or Task Scheduler on Windows.
• Panel scheduled tasks, hosting panels like Pterodactyl let you create scheduled tasks that send console commands. Use mv delete and mv create commands in sequence.
• In-game broadcast, use a plugin like EssentialsX or a scheduled command plugin to broadcast a warning 24 hours before the reset, then again 1 hour before.

A typical cron-based reset script for the Nether:

#!/bin/bash
# Send warning to players
screen -S minecraft -p 0 -X stuff "say The Nether resets in 5 minutes. Move your items to the Overworld!$(printf '\r')"
sleep 300
# Stop the server gracefully
screen -S minecraft -p 0 -X stuff "stop$(printf '\r')"
sleep 30
# Delete Nether
rm -rf /home/container/world/DIM-1
# Start the server
cd /home/container && screen -dmS minecraft java -jar server.jar

Keeping Nether and End resets separate

Not every server needs both resets on the same schedule. The Nether depletes faster because it holds ancient debris and quartz, high-demand resources. The End depletes slower because most players only visit for elytras and shulker shells. Running the Nether reset every two weeks and the End reset monthly is a balanced approach that keeps resources available without disrupting players too frequently.

If you use WorldGuard to protect farms or builds in either dimension, remember that those regions reference specific coordinates. After a reset, the terrain at those coordinates changes, but the WorldGuard regions remain valid and still prevent building or breaking. You may want to clear dimension-specific regions before the reset to avoid protecting random generated terrain.

Pair dimension resets with CoreProtect logging so you have a record of what happened before the wipe, useful for disputes about missing items.

Need reliable hosting for your server? Astroworld Hosting offers NVMe SSD, Pterodactyl panel, and DDoS protection. See features , plans from €6.39/mo.