Minecraft
Plan Chunky pregeneration around disk space and play time
Choose a sensible Minecraft pregeneration radius, measure a small run, and estimate the disk and maintenance window before expanding the world.

Pregenerating terrain can move exploration work into a maintenance window. It also writes world data that your server must store and back up. Before starting Chunky across a huge area, choose the land your community needs and measure a smaller run on the same world generator.
Start with the playable area
Write down the world name, centre and shape. A radius describes the distance from the centre to the edge; it does not describe the full width. For a square with radius 5,000 blocks, the width is about 10,000 blocks. That difference matters when you estimate the amount of terrain.
A Minecraft chunk covers 16 by 16 horizontal blocks. As a planning estimate, a square selection contains about (2 × radius ÷ 16)² chunks. A 5,000-block radius gives roughly 390,625 chunks before boundary rounding. Doubling that radius multiplies the area by four. These figures describe area, not a promise about disk usage or generation speed.
Pick a border from your intended season length and exploration habits. A small survival community may not need the same opening area as an organised event with players travelling in several directions. Plan the Nether and other dimensions as separate jobs rather than assuming one overworld task covers them.
Measure a pilot run
Use the same seed, generator, data packs and mod versions as the live world. Note free storage and world size before you start. Choose a small test region whose settings you can record and repeat. Read the Chunky command reference for your installed build before executing the task.
chunky world world
chunky shape square
chunky center 0 0
chunky radius 1000
chunky selection
chunky startReplace world and the centre with your intended values. Confirm the selection before starting. Run these as console commands without a leading slash, or use the command form appropriate to your platform. Do not paste a second task while the first still runs.
After a stable interval, note completed chunks, elapsed time and disk growth. Use those measurements to form a range for the larger task. For example, a measured 50 chunks per second would put 390,625 chunks at about 2.2 hours of generation work. That example excludes pauses and changing terrain costs; it is arithmetic, not a benchmark for your server.
Keep enough room for recovery
Compare the pilot's added bytes with its newly generated chunks. Extrapolate with headroom because terrain, structures and modded data vary between regions. Include the next backup, temporary archives and logs in your free-space calculation. The storage and backup retention guide covers those competing uses of the same disk.
Set a free-space threshold that will make you pause the task. Decide who watches it and where they record progress. A job running overnight needs a storage check as much as a CPU check; a quiet console does not establish that sufficient space remains.
Protect normal play
Take a recoverable pre-task backup and arrange the first run while players are offline. The project FAQ describes how hardware, plugins and generation add-ons affect throughput. Treat your installed combination as the workload to test. Avoid running a full web-map render alongside your pilot.
Record normal tick performance before starting. If you allow players back during generation, compare their experience against that baseline. Follow the spark investigation workflow if tick times rise; adding heap without checking the active workload may leave the cause unchanged.
Use chunky pause when you need to stop work and preserve task progress. Resume with chunky continue after checking storage and player activity. Cancelling a task does not remove chunks it already generated. Keep destructive trimming commands out of this maintenance procedure.
Check restart behaviour and the finished world
Review Chunky's configuration before a planned server restart. The documented continue-on-restart option controls whether saved work resumes; decide which behaviour your maintenance plan needs.
After completion, visit several locations near the selected edge and check the intended world border. Record the final world size, task duration and configuration. Take the next scheduled backup and confirm it completes within your expected window. Use the measured figures when you plan an expansion, so the next radius decision reflects your world rather than another server's benchmark.


