[world_blocks_commands]

How to Use the Forceload Command Generator

  1. Pick a sub-command: add, remove, remove all, or query.
  2. For add or remove, enter X1/Z1 for a single chunk, or also fill X2/Z2 to cover a rectangular range of chunks.
  3. For query, optionally enter X/Z to check one specific chunk, or leave blank to list every force-loaded chunk in the dimension.
  4. Copy the generated /forceload command into a command block or the console.

Command Syntax Reference

/forceload add <x1> <z1> [<x2> <z2>]
/forceload remove <x1> <z1> [<x2> <z2>]
/forceload remove all
/forceload query [<x> <z>]

A force-loaded chunk stays fully simulated (redstone ticks, crops grow, hoppers move items, mob farms run) even when no player is anywhere near it – normally chunks unload and stop ticking once every player moves far enough away. Coordinates for this command are X/Z block positions, but they only select the chunk (a 16×16 block column) each position falls inside – Y doesn’t matter since force-loading works per-column across the whole build height, not per specific block.

  • add <x1> <z1> [x2 z2] – force-loads the single chunk containing (x1, z1), or every chunk in the rectangular range between (x1, z1) and (x2, z2) if a second point is given.
  • remove <x1> <z1> [x2 z2] – stops force-loading the specified chunk or range, the same way it accepts a single point or a rectangle.
  • remove all – stops force-loading every chunk currently force-loaded in the dimension the command runs in, with no coordinates needed.
  • query [x z] – with coordinates, reports whether that specific chunk is force-loaded; with none, lists every force-loaded chunk in the current dimension.

Each world has a configurable per-dimension limit on how many chunks can be force-loaded at once (controlled by the forceloadedChunksLimit gamerule, default 100), which exists to stop a server from being forced to fully simulate an unbounded area indefinitely.

Frequently Asked Questions

Does forceload work with block coordinates or chunk coordinates?

You type ordinary block X/Z coordinates, but the command only uses them to identify which 16×16 chunk each point falls in – any coordinate inside a chunk selects that whole chunk. There’s no way to force-load “part” of a chunk; it’s always the full chunk column from bottom to top of the world.

Does force-loading keep a chunk loaded forever, even after a server restart?

Yes, within a single world’s save data – the set of force-loaded chunks is stored persistently per dimension and survives server restarts, so it needs an explicit remove or remove all to actually stop, not just leaving the area.

What’s the point of force-loading a chunk instead of just using a spawn chunk?

Only the Overworld’s designated spawn chunks stay loaded automatically by default (and even that behavior is controlled by the spawnChunkRadius gamerule), and only in the Overworld. /forceload lets you keep any chunk active in any dimension – Nether, End, or Overworld – independent of spawn position, which is essential for redstone contraptions, farms, or minigame arenas that need to run continuously far from spawn.

Is there a limit to how many chunks I can force-load?

Yes – the forceloadedChunksLimit gamerule caps the total force-loaded chunks per dimension (100 by default). Attempting to add more once the limit is hit fails, so large always-on setups may need to raise this gamerule or spread the load across multiple dimensions.

Related Tools