Skip to main content

Pause a Chunky task without discarding its saved progress

Applies to: Chunky; match the linked maintainer documentation to your installed platform and release.
Documentation checked .

Pausing is useful when players arrive during terrain generation or the server needs a maintenance window. Chunky distinguishes pausing from cancelling: cancel removes the task’s progress record. Choose the pause path when your intention is to continue the same job later.

Work through the change

  1. Read the current task status and record the world, shape, centre, radii and completion count. Check that the task you intend to pause belongs to this world rather than another simultaneous job.
  2. Run chunky pause with the exact world argument supported by the installed release. In the game chat include the leading slash; the panel console usually uses the command without it.
  3. Watch the console until the task reports its paused state. Allow outstanding work to settle, then record disk usage and server response so the pause has a measurable operational result.
  4. When the quieter period returns, use chunky continue for that same world. Check the resumed status against your recorded task rather than issuing chunky start with a new selection.

Check the result

The task should resume from its saved work and retain the intended selection. Progress and elapsed-time estimates may change after a long break, so compare completed chunks and world identity rather than expecting the old ETA to remain exact. Test ordinary player movement while the job runs.

Keep the planned continuation time in staff notes so the task is not forgotten after players arrive. Check that the named world remains available before resuming the saved job.

Recover or stop safely

If the task cannot be found, stop and inspect the task files and recent restart logs before starting over. Do not substitute cancel while investigating a pause problem. Existing generated terrain is separate from the progress record, so preserve both the world and the diagnostic evidence.

CloudExa game panel console and log access
Use the CloudExa console and logs to record task status and errors. Check whether each command is intended for a player or the server console before running it.

For the broader setup, read Pre-generate Minecraft terrain with Chunky and monitor disk space. Check the installed plugin version before applying syntax from the official Chunky documentation.

No comments to display