How To Find Chunks In Minecraft Bedrock

Visualization of the ground portion of a unmarried chunk. The unabridged chunk extends upward to a peak of 320.

A chunk is a 384-cake tall 16×16 segment of a earth. Chunks are the method used by the earth generator to divide maps into manageable pieces.

Generation [ ]

Chunks are sixteen blocks wide, 16 blocks long, 384 blocks loftier, and 98,304 blocks total. They extend from the bottom of the globe, Y=-64, all the way up to the build limit of Y=320. Chunks generate effectually players when they first enter the world. Every bit they wander around the earth, new chunks generate every bit needed.

Chunks generate with the help of the map seed, which means that the chunks are ever the same if you would use the same seed again, as long as the map generator and version number remain the aforementioned.

Spawn chunks, a 19x19 set of chunks around the globe spawn, are always loaded, so you lot can utilise that to your advantage when making automatic farms.

Chunk loading [ ]

A boundary between loaded and unloaded chunks.

Since Minecraft worlds are xxx million blocks in each key management and comprise an extreme amount of chunks, the game loads simply certain chunks in gild to brand the game playable.

Unloaded chunks are unprocessed by the game and do non procedure any of the game aspects.

Please note that events that can happen when a chunk is loaded, is not the aforementioned as events that but happen around the player. For example, normal mob spawning and random tick (determines crop growth, etc.) tin can just happen nigh a player, and volition non happen in loaded chunks far away from any players.

Coffee Edition [ ]

Tickets [ ]

Loading starts when a chunk receives ticket. All loaded chunks originate from the ticket.

Each load ticket has three backdrop: Level, Ticket type and (optionally) Fourth dimension to Live.

Level and load blazon [ ]

Levels are numbers that make up one's mind what load type the chunk is.

Load levels range from 22 to 44 in regular gameplay, while only 22 to 33 are relevant. Load levels less than 22 (including negative levels) are valid merely only possible with a modded game. Load levels above 44 are not possible in vanilla. Still, it could be possible by modifying the in-game lawmaking.

For a given clamper, only its lowest level matters. (Lower levels = higher load type.)

There are four clamper load types; each load type has different properties. This excludes unloaded chunks.

	Level	Properties
Entity Ticking	31 and beneath	All game aspects are active.
Ticking	32	All game aspects are active except that entities are not processed (do not move) and chunk ticks aren't either.
Border	33	But some game aspects are agile (Redstone and control blocks do not work).
Inaccessible	34 and above	No game aspects are agile, but world generation all the same occurs.

Level propagation [ ]

Load levels "propagate" or period from source chunk with a ticket to neighboring chunks, merely each time it increases its Level past 1 until the maximum of 44.

The chunks that get load level from level expansion activate the assigned load type.

Level propagation with a level of 31. Notation that levels 35 and more are ignored because they are identical to 34.
34	34	34	34	34	34	34
34	33	33	33	33	33	34
34	33	32	32	32	33	34
34	33	32	31	32	33	34
34	33	32	32	32	33	34
34	33	33	33	33	33	34
34	34	34	34	34	34	34

Same level propagation but with load type instead of Level with abbreviations of the load types.
IN	IN	IN	IN	IN	IN	IN
IN	BO	BO	BO	BO	BO	IN
IN	BO	TI	TI	TI	BO	IN
IN	BO	TI	ET	TI	BO	IN
IN	BO	TI	TI	TI	BO	IN
IN	BO	BO	BO	BO	BO	IN
IN	IN	IN	IN	IN	IN	IN

Ticket types [ ]

There are different ticket types, which come from various sources and activate chunks with unlike load types.

Role player ticket

This ticket is caused by the player and is assigned level 31. A player ticket is given to each chunk within an area surrounding the player as divers by the formulas described beneath and propagates as described in the tabular array above.

In singleplayer, the chunk loading distance is ane less than the return altitude, every bit configured in Options. Information technology follows the formula (iir - three)² = AoC where r is the selected render distance, and AoC is the surface area of chunks that are assigned an original thespian ticket (level 31 - entity ticking). The minimum AoC is 9, which means that in that location is no difference between having the return distance set to two or 3.

For case, in a unmarried-histrion game with a render distance of 5 chunks, an expanse of 7×7 chunks centered around the player has a load blazon of entity ticking (level 31) the immediately enclosing chunks. The strip of chunks at the outer edge of a ix×9 perimeter surrounding the playe have ticking (level 32), and the adjacent enclosing chunks (11×11 perimeter) are edge chunks (level 33).

In multiplayer, the chunk loading altitude is equal to the view-altitude, as configured in server.properties. It follows the formula (2v + one)ⁱⁱ = AoC where 5 is the configured view-distance, and AoC is the area of chunks that are assigned an original player ticket (level 31 - entity ticking).

For example, in a multiplayer server with a configured view-distance of v chunks, an surface area of 11×xi chunks centered around the player has a load type of entity ticking (level 31), while the immediately enclosing chunks. The strip of chunks at the outer edge of a thirteen×13 perimeter surrounding the actor have ticking (level 32), and the adjacent enclosing chunks (fifteen×15 perimeter) are border chunks (level 33).

Forced ticket

A ticket can likewise be created by using the /forceload control. It has a level of 31, and so its propagation can be seen in the table above.

Chunks remain force-loaded even after endmost and opening the game.

First ticket

Ticket created by the earth spawn for the clamper it is located at ("spawn chunks"). Its position can be changed past a /setworldspawn control. It has a level of 22, the lowest in the game. They are active whenever the role player is in the Overworld and are otherwise permanently agile.

Portal ticket

Ticket created when an entity is teleported through under portal, given to chunk at the other side of the portal. It has a level of 30, so it is stronger than the player/strength loaded ticket.

It expires after 300 game ticks (equivalent to 15 seconds). Because they are created each time an entity passes through the portal, it is possible to create a "chunk loader". Perpetually keeping chunks loaded without the player being near, which can be used for various in-game mechanics such equally farms, but can create lag.

Dragon ticket

Ticket created at the start of the battle with ender dragon and is given to the 0,0 chunk (the one with leave portal). It has a level of 24.

Information technology expires later no more players participate in the battle, or the dragon dies.

Post-teleport ticket

Ticket created when entity is teleported either by going through the end portal or using /teleport or /spreadplayers commands. The /teleport command has a level of 32, whereas, for /spreadplayers and the end portal, it has a level of 33.

It expires subsequently 5 game ticks.

Temporary ticket

Ticket created when an arbitrary piece of game lawmaking calls getChunk. If the game code says the chunk should be loaded, it places this ticket on that chunk (after peradventure creating information technology).

The load level depends on what kind of clamper the game attempts to load (a fully world-generated chunk or non). Information technology is e'er level 33 (edge) or greater. In many cases, information technology involves earth generation in some style.

For instance, when a generic mob wandering AI is executing, it asks if a certain block has a solid elevation surface. As part of that check, that chunk has an "unknown" ticket with level 33 placed on information technology. Similarly, commands such as /clone, /data, /execute (if|unless) (block|blocks|predicate), /fill and /setblock generate a temporary ticket when reading data from or writing it to a previously loaded chunk; if run every tick, they tin prevent the clamper from unloading until the earth is reloaded.^[i]

It expires after 1 game tick.

Calorie-free ticket

Unknown, maybe world-generation related.

Limitations [ ]

Idle timeout

Each dimension has its own idle timeout. If there are players or forceloaded chunks in the dimension, the timeout is disabled. When entity leaves or enters this dimension, the timeout is reset.

If the timeout reaches 300 game ticks, the dimension stops processing certain actions. These include entity and block entity ticking, ender dragon fight, and global entities (lightning).

Some game aspects don't always get candy in loading chunks because in that location may be other weather for their progress, which includes the following:
- Chunk tick
  - Only chunks with centers within 128 blocks of a player are ticked on every game tick. See as well Tick.
- Entities
  - Hostile mobs instantly despawn if they spawn more than 128 blocks from any thespian.
    - This includes zombified piglins at Nether portals and witches in witch huts.
  - Passive mobs practise non spawn naturally exterior a 240 cake X 240 cake expanse around a player.
    - The passive mob spawn cap is express by the number of friendly mobs loaded into memory, which means that any passive mobs nowadays in the spawn chunks count toward the mob cap and usually prevents friendly mobs from naturally spawning anywhere else in the world. The only exception is when passive mobs spawn as office of a newly generated chunk.
  - See also Spawn.

Exceptions [ ]

Events in a chunk may bear on blocks in exterior chunks. If the outside chunk is inactive, the effects are suspended in near cases. Specifically,

Block changing on the edge of a ticking clamper can spread updates to blocks outside the ticking chunk and make them respond appropriately. The update may exist propagated block by cake until outside the border chunks, at which fourth dimension it creates a temporary ticket to go on propagation.
Block in a chunk with a 33 level can asking a scheduled tick, only it does non become processed until the chunk gets a load level of 32 or below.
Flowing h2o or lava can spread to the commencement adjacent cake outside a ticking chunk, merely the flow becomes suspended in that location until the border chunk has a greater load level.
Burn tin spread to the starting time adjacent flammable block outside the ticking chunk. Like water and lava, it becomes suspended at that place. It cannot spread further until the outside chunk gets a level of 33 or below.
Grass and mycelium tin can spread to the first adjacent block outsider an entity ticking chunk.
Pumpkin and melon stem growing on the edge of an entity ticking chunk can place their fruits on an adjacent cake outside an entity ticking clamper.
An entity (mob, minecart, arrow, etc.) that attempts to move into a ticking chunk from an entity ticking clamper becomes suspended every bit soon as information technology leaves the entity ticking chunk. When the ticking chunk gets a greater level, the entity resumes moving.
Exploding TNT in entity ticking chunks can damage or destroy blocks in a not-entity-ticking chunk.

Boulder Edition [ ]

All game aspects are active in loading chunks, including chunks within a player'southward simulation altitude and chunks loaded by Commands/tickingarea. Unloaded chunks are unprocessed by the game and do non process whatever of the game aspects.

Type [ ]

Role player: A circular-similar shape^{[ more information needed ]}.; Chunks within the simulation altitude of a thespian are loading.

Command: Create with the /tickingarea command.

Limit [ ]

Entities
- Mob spawning is evaluated for every chunk within a 6 chunk cylindrical radius of the thespian that is loaded.

Exception [ ]

Events in a ticking area may bear upon blocks in outside chunks. If the outside clamper is inactive, the effects are suspended in most cases. Specifically,

Block changing on the edge of a ticking area can spread updates to blocks exterior the ticking area and reply appropriately.
Flowing water or lava can spread to the beginning adjacent block in an exterior clamper, only the catamenia becomes suspended there until the outside chunk becomes agile.
Burn can spread to the first adjacent combustible block outside the ticking area. Like water and lava, information technology becomes suspended in that location; although visible, its blitheness does non run, and it cannot spread further until the outside chunk becomes active.
Grass and mycelium can spread to the outset adjacent block in an outside chunk, simply the affected block does not actually modify its appearance until its chunk becomes active; it then changes instantly. Grass and mycelium cannot spread beyond the first such cake, nor from such a block into the ticking area until the exterior chunk becomes active.
Pumpkin and melon stalk growing on the edge of a ticking area tin can identify their fruits on an adjacent block in an outside chunk.
An entity (mob, minecart, arrow, etc.) that attempts to motility into an outside chunk becomes suspended as soon as information technology leaves the ticking area. Information technology remains visible but motionless. When the outside block becomes agile, the entity resumes moving.
Exploding TNT can harm or destroy blocks in an inactive chunk, and unlike other events, its effects are not limited to adjacent blocks. However, secondary furnishings in the outside clamper are suspended until the clamper becomes active. For instance, if an explosion destroys a cake that supported sand or gravel, the sand or gravel does not autumn immediately. The aforementioned matter happens with items that were attached to destroyed blocks, such as item frames and Redstone torches; they practise not drib until the chunk is activated.
Primed TNT launched into an inactive chunk is suspended in mid-air within the first exterior block it enters. Information technology disappears until the outer chunk becomes active, at which time it resumes its flight and inaugural.

Finding chunk edges [ ]

X and Z coordinates that are divisible by 16 stand for the boundaries between chunks. EG: (96, -32) is a corner where four chunks see. Ane of those chunks is betwixt Ten coordinates 80 to 96 and Z coordinates -48 to -32. Another one is between 10 coordinates 96 to 112 and Z coordinates -32 to -xvi, and so on. When either X or Z crosses a multiple of sixteen, the player is moving beyond chunks.

Substantially, the player is in the elevation-left corner (due north-western) of a clamper when both 10 and Z coordinates are divisible by 16.

Additionally, the histrion tin know the clamper they are on by this formula:
The X of a clamper is floor(X coordinate / 16)
The Z of a chunk is flooring(Z coordinate / 16)
Where floor is the largest previous integer. E.yard. Floor( 27.9561 ) is 27
In other words, if X was 27, Z was −15 the chunk is clamper (Flooring(27/16), Floor(−15/sixteen)), meaning that the player is on chunk (one, −1).
Also, the coordinates of a block within a chunk tin can exist found past taking the coordinate mod 16.

In Java Edition, the cardinal F3 +G can be used to display chunk boundaries. Alternately, pressing the "F3" button opens the Debug screen that shows the player's 10, Y, and Z coordinates, in add-on to the "clamper" variable. These coordinates modify as the player moves effectually. The role player can know the chunk they are in past the variable "clamper".

In Boulder Edition, when toggling fancy graphics, the world renders again, loading only the chunk the player is in for a split 2d, briefly showing the clamper boundaries. When the player changes the return distance quickly, chunk barriers appear as a blueish line. As well, if in mid-air and bridging with total blocks, when a chunk edge is intersected the next block placed will fade into view, showing the chunk border. This is sometimes unreliable, just useful every bit it only happens on clamper borders. This does non happen surreptitious or when the block placed is close to more than one block.

Slime chunks [ ]

Slime chunks are specific chunks capable of spawning slimes below Y=twoscore regardless of Light. These chunks are otherwise same as all other chunks.

Java Edition [ ]

Slime chunks generate throughout the globe (except in mushroom islands). ane in 10 of all chunks is slime chunk. These slime chunks are determined pseudo-randomly by combining their clamper coordinates with the seed of the world:

Random rnd = new Random(     seed +     (int) (xPosition * xPosition * 0x4c1906) +     (int) (xPosition * 0x5ac0db) +      (int) (zPosition * zPosition) * 0x4307a7L +     (int) (zPosition * 0x5f24f) ^ 0x3ad8025f ); return rnd.nextInt(x) == 0;

That is, using the chunk coordinates to help generate a seed, a random number between 0 and nine inclusive is generated, and if that number is 0, the chunk can spawn slimes. To catechumen world coordinates to chunk coordinates, divide by sixteen and round down. Annotation that xPosition, and zPosition are 32-chip integers (intsouthward).

Boulder Edition [ ]

The slime chunk algorithm in Bedrock Edition is different from in Coffee Edition. The algorithm doesn't depend on the world seed, thus the chunks that slimes tin can naturally spawn in are the same for every world.^[2]

History [ ]

Coffee Edition pre-Archetype
rd-131655		The precursors to chunks are showcased.
Java Edition Infdev
20100227-1		Map superlative is not custom anymore. The chunk top has been changed to 128.
Java Edition
1.ii.i	12w07a	The clamper height has been increased to 256, equally part of the transition from Region to Anvil file format.
1.4.2	12w39a	The debug screen now shows the coordinates of the clamper the player is in, and the player'south coordinates in that chunk.
1.ten	16w20a	`F3` + `G` now toggles the visible chunk borders effectually the player.
ane.14	?	The method of chunk loading has changed.
1.17	20w49a	Map pinnacle is now custom again.
	21w06a	Maximum chunk height has been increased to 320 and minimum meridian has been dropped to -64, making chunks 384 blocks loftier in total.
	21w15a	The chunk height changes have been reverted.
1.18	Experimental Snapshot i	Chunks are again 384 blocks loftier.
1.18	21w37a	Render distance at present causes chunks to load in a cylinder shape around the player instead of a square.

Trivia [ ]

If a player stands in a chunk that has not generated all the same, the world immediately becomes invisible until they are in a valid chunk. This does not happen if the Y coordinates are beyond the chunk boundaries.
In Boulder Edition, if ane of the sixteen xvi×16×sixteen sections of a clamper doesn't have any blocks in information technology, placing a block there shows the aforementioned animation as a clamper loading. This bug makes the block that the player placed to plough to the same color of the sky in the direction the player is facing for about 1 second and starts fading away into the normal block texture. If the fourth dimension is sunrise or sunset and the player places a block there, it actually changes colors constantly for one second if the histrion keeps bobbing their head up and downwardly. The block too makes blocks behind it appear invisible.

References [ ]

↑ MC-168596
↑ The contrary-engineered Bedrock Edition slime clamper algorithm can be found on GitHub at depressed-pho/slime-finder-pe.