Exploration can make a server do two jobs at once: run the existing world and create new terrain. Pre-generation moves some of that terrain work into a planned window. The useful trick is choosing a sensible boundary before starting a job that fills the disk.
Back up first, select the correct world, choose a bounded shape and radius, then run generation during a quiet period. Pre-generation does not fix expensive farms or plugin logic.
Plan the area and storage first
Decide how far players actually need to travel and which dimensions need preparation. Back up existing worlds and confirm free disk space. A bigger radius grows the area rapidly: doubling it roughly quadruples the selected area. Do not select an enormous world because an example command makes it easy.
A pre-generation selection is not automatically an enforced gameplay border. Plan the actual world border separately and check its center and dimensions.
Install the compatible Chunky build
Use the project’s official distribution for your server platform and release. Read any dependencies and start once to verify that Chunky loads. Keep the startup log with your installed version so the command reference can be matched later.
Tell players about the maintenance window. Generation competes for resources, and a world that is still being generated can feel slower while the task runs.
Select a small example area
The following example selects a circular area with a 1,000-block radius in a world named world. Replace the world and coordinates for your installation. Check the selection before starting; radius is not diameter. In a panel console, omit the initial slash when required.
/chunky world world
/chunky shape circle
/chunky center 0 0
/chunky radius 1000
/chunky selection
For separate Nether or End worlds, select and plan each one deliberately. Do not assume their dimensions or travel scales should use the same radius.
Start, observe and pause if needed
Start only after reviewing the selected world and area. Watch the task output, available storage and server responsiveness. The pause and continue controls let you defer work when players need the server.
/chunky start
/chunky pause
/chunky continue
These lines show separate actions, not a sequence to paste all at once. Start the task, monitor it, and pause only when you need to. Avoid filling the disk with a generation job and multiple large archive copies.
Verify the result and keep the boundary useful
Wait for completion, then travel through the prepared area during a controlled test. Compare the same route with your earlier observations. Going beyond the generated selection can still create new terrain, and changing generation software or a seed has wider consequences than a performance tweak.
Save the selection and completion details with your maintenance notes. Continue profiling if a crowded base still lags: pre-generation handles one kind of work, not every source of high MSPT.
Before you finish
- Back up and check free disk space.
- Select the intended world, center, shape and radius.
- Review the selection before starting.
- Observe completion and test inside the prepared boundary.
Common questions
Is the radius the full width of the world?
No. A 1,000-block radius describes distance from the center; the corresponding full diameter is about 2,000 blocks.
Will pre-generation remove every lag spike?
No. Plugin tasks, entities, storage stalls and other workloads can still cause slow ticks. Measure the remaining issue.
Official documentation
Commands and configuration depend on your installed software version. Check its current documentation, keep a backup and test one change at a time.
Build a setup that fits your server
Compare monthly allocations and CPU tiers, or use the plan finder for a starting estimate.
Compare Minecraft hosting plans Find a plan