Chunky Pregeneration Guide: mustard.gorgarath.net

This document records the Chunky pregeneration settings and procedures used for creating and maintaining the mustard.gorgarath.net modded Minecraft world dimensions.

The goal of pregeneration is to:

• Reduce server lag caused by first-time chunk generation.
• Prevent players exploring new terrain from competing with normal server activity.
• Allow Distant Horizons to provide smoother long-distance views.
• Account for additional terrain generation from mods.

These values are based on the current modded server configuration and hardware environment and may require adjustment if the modpack, player count, storage capacity, or server hardware changes significantly.

This document should be updated when world generation settings, pregeneration procedures, supported dimensions, or server generation requirements change.

Pregeneration Procedure

Before starting pregeneration:

1. Confirm the server has sufficient storage space available.
2. Confirm current performance settings are appropriate.
3. Stop normal player activity if possible.
4. Perform pregeneration during a maintenance window if possible.

Dimension identifiers used below should match the namespace IDs registered by the server. Verify these values against the active mod configuration if dimensions are added, removed, renamed, or changed.

Chunk generation performance may be affected by:

• CPU allocation and pinning.
• C2ME configuration.
• Java memory settings.
• Server performance configuration.
• Active server workloads.

Overworld

The Overworld should be centered around the actual world spawn point.

Before setting the radius, run:

chunky spawn

This ensures Chunky uses the server's current world spawn location as the center of generation.

Then run:

chunky radius 7500
chunky start

Recommended Overworld radius:

7500 blocks

Reasoning:

• Covers the primary player exploration area.
• Supports Distant Horizons usage.
• Reduces terrain-generation spikes during exploration.
• Accounts for large modded world generation, including:
  • Terralith
  • Tectonic
  • Regions Unexplored
  • Dynamic Trees
  • Structure generation mods
  • Additional biome and world generation mods

Approximate generation area:

• Circular radius of 7500 blocks.
• Bounding area of approximately 15,000 × 15,000 blocks.
• Approximately 690,000 chunks generated within the configured circular radius.

Nether

The Nether does not require chunky spawn.

The Nether is centered at 0,0 to provide predictable coverage around the dimension origin and support portal travel.

Run:

chunky world minecraft:the_nether
chunky center 0 0
chunky radius 2000
chunky start

Recommended Nether radius:

2000 blocks

Reasoning:

• Provides a large portal network area.
• Equivalent to approximately 16,000 Overworld blocks of travel.
• Covers common exploration distances.
• Avoids unnecessary generation of unused terrain.

The End

The End should be centered at 0,0.

Run:

chunky world minecraft:the_end
chunky center 0 0
chunky radius 2500
chunky start

Recommended End radius:

2500 blocks

Reasoning:

• Provides additional exploration space beyond the dragon island.
• Supports additional End generation from mods.
• Accounts for:
  • Better End
  • Additional structures and biome generation

Aether

The Aether should be centered at 0,0.

Run:

chunky world aether:the_aether
chunky center 0 0
chunky radius 3000
chunky start

Recommended Aether radius:

3000 blocks

Reasoning:

• Modded dimensions often spread structures farther apart.
• Players are likely to explore the dimension rather than only visit briefly.
• Reduces generation spikes during exploration.

The Bumblezone

The Bumblezone should be centered at 0,0.

The dimension is centered around generated hive structures and unique terrain rather than a traditional overworld-style spawn area. Centering at the origin provides predictable coverage for exploration and resource gathering.

Run:

chunky world the_bumblezone:the_bumblezone
chunky center 0 0
chunky radius 1500
chunky start

Recommended Bumblezone radius:

1500 blocks

Reasoning:

• Provides sufficient exploration space for normal gameplay.
• Covers a large area around the central hive structures.
• Reduces generation delays while exploring the dimension.
• Avoids excessive storage usage for a dimension that is typically visited less frequently than the primary dimensions.

Deeper Darker Otherside

The Deeper Darker Otherside should be centered at 0,0.

Unlike the Overworld, the Otherside dimension does not require spawn-based centering. The origin provides predictable coverage for dimension exploration and allows players to encounter generated structures and terrain without requiring a large unnecessary pregeneration area.

Run:

chunky world deeperdarker:otherside
chunky center 0 0
chunky radius 2000
chunky start

Recommended Deeper Darker Otherside radius:

2000 blocks

Reasoning:

• Provides enough exploration space for sculk-based terrain and structures.
• Reduces generation spikes when exploring the dimension.
• Accounts for the dimension being primarily exploration-focused rather than a primary building area.
• Balances pregeneration time and storage requirements against expected usage.

After Configuration Changes

If changing:

• CPU pinning.
• C2ME settings.
• Java memory settings.
• Server performance settings.

Before stopping or restarting the server:

save-all flush

Stop the server cleanly.

After restarting, check progress:

chunky progress

Resume an existing task:

chunky continue

Optional console reduction:

chunky quiet 60

This reduces Chunky progress messages while allowing generation to continue and helps keep the logs cleaner.

Recommended Final Values

Related Documentation

The following documents provide additional information about the server configuration and world generation environment.

Change History

2026-08-03

Reviewed and updated pregeneration recommendations for the current server configuration.

Documented dimension namespace verification, corrected Chunky generation area calculations, clarified pregeneration procedures, and updated operational guidance for configuration changes.

2026-07-26

Updated documentation structure to match the infrastructure documentation format.

Documented current Chunky pregeneration procedures, supported dimensions, recommended generation values, and operational considerations.