World Management & Multi-world Setup

1. Dimension Theory and File Structure

By default, a Minecraft server handles three primary dimensions: world (Overworld), world_nether (Nether), and world_the_end (The End). In 2026, the rise of more complex server types, such as "Earth" maps or "Creative Hubs", has made multi-world management a core requirement. Every world is stored as a folder containing region/ (the blocks), entities/, and the vital level.dat file.

2. Multiverse-Core: The Industry Standard

Multiverse-Core remains the most stable tool for handling dimension registration. It abstracts the complex Bukkit world-loading API into simple commands.

Pro-Level Multiverse Tips:

Auto-Unload: In the worlds.yml, you can set keepSpawnInMemory: false for secondary worlds. This saves significant RAM by only keeping a world active when a player is actually in it.
Alias & Color: Use /mv config alias [name] to change how a world appears in your chat or tab-list, making it easier for players to identify where they are.
Portals Integration: Use the Multiverse-Portals addon to create physical frames that teleport players between worlds without commands.

3. Custom Terrain Generation (Iris & Terraform)

Vanilla terrain generation is functional, but 2026 players expect more. Plugins like Iris or TerraformGenerator allow you to create worlds with realistic mountains, custom biomes, and unique structures.

To use these, you must specify the generator during world creation:
/mv create MyCustomWorld normal -g Iris:OVERWORLD

4. WorldEdit and the "Async" Necessity

WorldEdit is the "god-tool" of construction. However, using //set 1,000,000 will instantly crash a standard server.

The Solution: Use AsyncWorldEdit (AWE) or FastAsyncWorldEdit (FAWE). These "hack" the internal block-placing logic to spread the task over several thousand ticks or perform it off the main server thread. This allows you to paste massive hub schematics or clear entire mountains without a single drop in TPS (Ticks Per Second).

5. The Golden Rule: Chunky Pre-generation

The #1 cause of lag on new Deduck servers is "New Chunk Generation." When a player flies with an elytra into ungenerated territory, the CPU must calculate thousands of block positions and lighting updates instantly.

The Fix: Use Chunky. Before your server goes live, run:
/chunky radius 5000
/chunky start

Chunky: The high-performance world pre-generator

This will generate all chunks within a 5,000-block radius while the server is empty. Since the chunks already exist, players can explore at high speed without causing any CPU strain.

6. Dimension Partitioning for Performance

On high-end Deduck hardware, we recommend separating your heavy worlds. If you run a "Resource World" that resets every month, ensure it has its own paper-world-defaults.yml settings to limit entity spawning and reduce simulation distance specifically for that heavy-load dimension.

World Management & Multi-world