Chunk Loading and Redstone

Chunk loading determines which 16×16 sections of a Minecraft world are actively processed by the game at any given moment. Because redstone circuits, block entities, and moving items only function in loaded chunks with the proper load level, understanding chunk tickets and boundaries is essential for building reliable farms and long-distance machines.

World & PerformanceAdvancedClocks & timing

What is Chunk Loading?

Minecraft worlds are massive, so the game divides the map into 16×16 block columns called chunks. In the Overworld, each chunk is 384 blocks tall (256 blocks in the Nether and the End) and is split vertically into 16×16×16 subchunks.

To prevent computers from crashing, the game only processes chunks that are currently loaded. Unloaded chunks are completely frozen in time: redstone clocks stop ticking, hoppers stop moving items, and minecarts freeze in place. If a redstone machine crosses a boundary from a loaded chunk into an unloaded one, parts of the machine will stop responding, which can easily break timing-sensitive contraptions.

Tickets, Load Levels, and Propagation

In Java Edition, a chunk is loaded whenever it receives a load ticket. Every ticket carries a numerical load level (ranging from 22 to 44 in vanilla gameplay). A lower number means a stronger load state. Whenever a chunk receives a ticket, that load level propagates outward to neighboring chunks, increasing its level number by 1 for each chunk step away from the source.

  • Level 31 and below (Entity Ticking): Every game aspect runs normally. Redstone updates, hoppers transfer items, and entities (like minecarts, dropped items, and mobs) are actively processed.
  • Level 32 (Block Ticking): Redstone circuits, repeaters, observers, fluids, and block entities continue to function, but entities freeze and are no longer processed.
  • Level 33 (Border): Neither entities nor redstone ticks are processed here, though blocks and entities inside this ring can still be read or modified by events happening in adjacent level 32 chunks.
  • Level 34 and above (Inaccessible): No game mechanics run; only background world generation takes place. Levels above 44 unload immediately.

Ticket Types and Simulation Distance

Different actions in the game generate different tickets:

  • Player Ticket (Level 31): Applied in a square around the player based on Render Distance or server view-distance. However, actual ticking around a player is also restricted by Simulation Distance (s). Entities only tick within a square of side length 2s + 1 chunks around the player, while redstone, block entities, and scheduled ticks run within that square plus a one-chunk-thick outer frame.
  • Start Ticket (Level 22): Generated at the world spawn chunk. Because it starts at level 22 and propagates outward by +1 per chunk, it keeps the "spawn chunks" permanently loaded whenever the Overworld is active.
  • Portal Ticket (Level 30): Created whenever an entity passes through a Nether portal. It gives the destination chunk a level 30 ticket that expires after 300 game ticks (15 seconds).
  • Forced Ticket (Level 31): Created using server commands to keep specific chunks permanently loaded across world reloads.

Worked Example: Building a Nether Portal Chunk Loader

Because a Portal Ticket has a load level of 30, it propagates outward to create a 3×3 area of Entity Ticking chunks (the portal's chunk at level 30, surrounded by 8 chunks at level 31) and a 5×5 outer ring of Block Ticking chunks (level 32). You can keep a remote redstone base loaded indefinitely by sending an entity through a portal every 15 seconds:

  1. Press F3 + G in Java Edition to turn on chunk borders and build a Nether portal inside the central chunk you want to load.
  2. Light the portal and go through to build the matching portal in the Nether.
  3. On the Overworld side, place a dispenser or dropper facing into the portal frame, connected to a hopper clock or repeater timer set to fire faster than once every 300 game ticks (15 seconds).
  4. On the Nether side, set up a collection mechanism (such as a hopper or water stream) that catches the teleported item or minecart and immediately shoots it back through the portal into the Overworld.
  5. When the item returns to the Overworld, collect itback into your dropper. Because an entity crosses the portal threshold in both dimensions before the 300-tick timer runs out, both dimensions maintain a level 30 ticket continuously.

How Players Use and Exploit Chunk Loading

Technical players take advantage of chunk loading rules to optimize farms and run global machinery:

  • Spawn Chunk Farms: Since world spawn chunks never unload while a player is in the Overworld, players build iron farms, sorting systems, and global clocks there so they run 24/7 without needing a portal loader.
  • Remote Redstone Without Entities: Because level 32 (Block Ticking) chunks still process scheduled block ticks and block entities, you can run pure redstone wire, repeaters, and hopper lines across a 5×5 chunk area around a single portal chunk loader—just avoid using minecarts, armor stands, or dropped items outside the inner 3×3 Entity Ticking zone.
  • Understanding Random Ticks vs. Chunk Loading: Keeping a chunk loaded at level 31 is not enough to grow crops or spawn hostile mobs in Java Edition. Random block ticks and natural mob spawns only happen during a chunk tick, which requires an Entity Ticking chunk whose center is within 128 blocks horizontally of a non-spectator player.

Common Mistakes

  • Building across chunk borders: If half of a flying machine or piston door sits in a level 32 chunk and the rest sits in a level 33 border chunk, the half in the level 32 chunk will push blocks into the border chunk and immediately jam or break the contraption. Always press F3 + G and keep sensitive circuits inside a single chunk.
  • Using entities in level 32 chunks: A common error with portal chunk loaders is placing hopper minecarts or water-stream item elevators two chunks away from the portalchunk. At level 32, hoppers and redstone dust still work, but the minecarts and floating items freeze completely.
  • Causing server lag (MSPT spikes): Leaving dozens of chunk loaders running with exposed hoppers and flashing redstone dust generates massive block updates and entity checks. If milliseconds per tick (MSPT) exceed 50 ms, the game drops below 20 ticks per second (TPS). Always place composters on top of open hoppers and add an off-switch to your chunk loaders.

Java vs Bedrock

TopicJava EditionBedrock Edition
Chunk Ticks & Random Ticking DistanceRequires an entity-ticking chunk (level 31 or below) AND a horizontal distance of less than 128 blocks between the chunk center and a non-spectator player.All chunks inside the player's simulation distance (or added via the /tickingarea command) are ticked every game tick; the 128-block horizontal distance rule does not apply.
Random Tick Speed GameruleThe randomTickSpeed gamerule defaults to 3 and sets the exact number of blocks chosen per subchunk each chunk tick.The randomTickSpeed gamerule defaults to 1 and specifies relative speed rather than the exact number of blocks per subchunk.
Scheduled Ticks LimitAllows a maximum of 65,536 scheduled ticks per game tick across the dimension.Allows a maximum of 100 scheduled ticks per chunk per game tick.

Frequently asked questions

Does redstone work in lazy (Block Ticking) chunks?
Yes. In level 32 (Block Ticking) chunks, redstone dust, repeaters, comparators, pistons, observers, and block entities like hoppers still process normally. Only entities (such as minecarts, dropped items, and mobs) are frozen.
How long does a Nether portal keep a chunk loaded?
Whenever an entity passes through a Nether portal, the destination chunk receives a level 30 portal ticket that lasts for 300 game ticks, which is exactly 15 seconds at 20 TPS.
Why won't my crops grow in a chunk loaded by a chunk loader?
In Java Edition, crop growth relies on random block ticks, which only occur in entity-ticking chunks whose center is within 128 blocks horizontally of a player. A portal chunk loader keeps redstone and iron farms running, but cannot cause random ticks without a player nearby.
How big of an area does a Nether portal chunk loader load?
Because a portal ticket starts at level 30 and increases by 1 for each neighboring chunk outward, it creates a 3×3 chunk area of Entity Ticking chunks (levels 30 and 31) surrounded by a 5×5 outer ring of Block Ticking chunks (level 32).

Components involved

More redstone mechanics