Minecraft Bedrock How To Find Chunk Borders

Visualization of the ground portion of a single chunk. The unabridged clamper extends up to a peak of 320.

A chunk is a 384-block alpine 16×16 segment of a globe. Chunks are the method used past the globe generator to divide maps into manageable pieces.

Generation [ ]

Chunks are 16 blocks wide, sixteen blocks long, 384 blocks high, and 98,304 blocks full. They extend from the bottom of the world, Y=-64, all the fashion upwards to the build limit of Y=320. Chunks generate effectually players when they first enter the world. Equally they wander effectually the world, new chunks generate as needed.

Chunks generate with the aid of the map seed, which means that the chunks are always 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 fix of chunks around the world spawn, are always loaded, so yous can apply that to your advantage when making automatic farms.

Clamper loading [ ]

A purlieus between loaded and unloaded chunks.

Since Minecraft worlds are xxx million blocks in each cardinal direction and contain an farthermost amount of chunks, the game loads only certain chunks in lodge to brand the game playable.

Unloaded chunks are unprocessed by the game and practise not process whatever of the game aspects.

Please note that events that tin happen when a chunk is loaded, is not the same as events that but happen effectually the thespian. For example, normal mob spawning and random tick (determines crop growth, etc.) tin just happen near a player, and will not happen in loaded chunks far away from whatsoever players.

Java Edition [ ]

Tickets [ ]

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

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

Level and load type [ ]

Levels are numbers that determine what load type the chunk is.

Load levels range from 22 to 44 in regular gameplay, while just 22 to 33 are relevant. Load levels less than 22 (including negative levels) are valid but only possible with a modded game. Load levels above 44 are non possible in vanilla. However, it could be possible past modifying the in-game code.

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

There are iv chunk load types; each load type has unlike properties. This excludes unloaded chunks.

	Level	Properties
Entity Ticking	31 and below	All game aspects are agile.
Ticking	32	All game aspects are active except that entities are not processed (do non movement) and clamper ticks aren't either.
Border	33	Only some game aspects are active (Redstone and control blocks do not work).
Inaccessible	34 and above	No game aspects are active, but world generation nonetheless occurs.

Level propagation [ ]

Load levels "propagate" or menstruation from source clamper with a ticket to neighboring chunks, just each time it increases its Level by 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. Note that levels 35 and more than are ignored considering 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

Aforementioned 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 different load types.

Player ticket

This ticket is caused past the player and is assigned level 31. A role player ticket is given to each chunk within an area surrounding the player every bit defined past the formulas described below and propagates as described in the table above.

In singleplayer, the clamper loading distance is one less than the render distance, as configured in Options. It follows the formula (2r - 3)² = AoC where r is the selected render distance, and AoC is the surface area of chunks that are assigned an original player ticket (level 31 - entity ticking). The minimum AoC is ix, which means that there is no deviation between having the return altitude fix to 2 or 3.

For case, in a single-player game with a render distance of five chunks, an area of 7×seven chunks centered around the player has a load type of entity ticking (level 31) the immediately enclosing chunks. The strip of chunks at the outer edge of a 9×9 perimeter surrounding the playe accept ticking (level 32), and the next enclosing chunks (eleven×eleven perimeter) are edge chunks (level 33).

In multiplayer, the chunk loading distance is equal to the view-altitude, equally configured in server.properties. Information technology follows the formula (2v + 1)² = AoC where v 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 area of 11×eleven chunks centered effectually the player has a load blazon of entity ticking (level 31), while the immediately enclosing chunks. The strip of chunks at the outer edge of a 13×13 perimeter surrounding the histrion have ticking (level 32), and the next enclosing chunks (fifteen×15 perimeter) are border chunks (level 33).

Forced ticket

A ticket can as well exist created by using the /forceload control. It has a level of 31, so its propagation can be seen in the table higher up.

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

Start ticket

Ticket created by the world spawn for the chunk information technology is located at ("spawn chunks"). Its position can exist changed past a /setworldspawn command. It has a level of 22, the lowest in the game. They are active whenever the player is in the Overworld and are otherwise permanently active.

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, then it is stronger than the player/forcefulness loaded ticket.

Information technology expires later 300 game ticks (equivalent to xv seconds). Because they are created each time an entity passes through the portal, it is possible to create a "clamper loader". Perpetually keeping chunks loaded without the actor existence near, which tin can be used for various in-game mechanics such as farms, but tin create lag.

Dragon ticket

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

It expires after no more players participate in the battle, or the dragon dies.

Postal service-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 after five game ticks.

Temporary ticket

Ticket created when an arbitrary piece of game code calls getChunk. If the game code says the chunk should exist loaded, it places this ticket on that clamper (after possibly creating it).

The load level depends on what kind of chunk the game attempts to load (a fully earth-generated chunk or not). It is always level 33 (border) or greater. In many cases, it involves world generation in some way.

For case, when a generic mob wandering AI is executing, information technology asks if a certain block has a solid peak surface. As part of that check, that chunk has an "unknown" ticket with level 33 placed on it. 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 can forbid the chunk from unloading until the world is reloaded.^[1]

It expires after i game tick.

Light ticket

Unknown, possibly world-generation related.

Limitations [ ]

Idle timeout

Each dimension has its ain 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 deportment. These include entity and block entity ticking, ender dragon fight, and global entities (lightning).

Some game aspects don't always get processed in loading chunks because there may be other conditions for their progress, which includes the post-obit:
- Chunk tick
  - But chunks with centers within 128 blocks of a player are ticked on every game tick. See besides Tick.
- Entities
  - Hostile mobs instantly despawn if they spawn more than than 128 blocks from any player.
    - This includes zombified piglins at Nether portals and witches in witch huts.
  - Passive mobs do not spawn naturally exterior a 240 block 10 240 block area effectually a role player.
    - The passive mob spawn cap is limited past the number of friendly mobs loaded into retention, which ways 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 equally part of a newly generated clamper.
  - See besides Spawn.

Exceptions [ ]

Events in a clamper may impact blocks in outside chunks. If the exterior clamper is inactive, the effects are suspended in nigh 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 cake by block until outside the edge chunks, at which time it creates a temporary ticket to go along propagation.
Block in a chunk with a 33 level tin request a scheduled tick, merely it does non get processed until the chunk gets a load level of 32 or below.
Flowing water or lava can spread to the first adjacent block outside a ticking chunk, but the flow becomes suspended there until the edge chunk has a greater load level.
Fire tin can spread to the first side by side flammable block outside the ticking chunk. Like h2o and lava, it becomes suspended there. It cannot spread further until the outside clamper gets a level of 33 or below.
Grass and mycelium can spread to the kickoff adjacent block outsider an entity ticking chunk.
Pumpkin and melon stem growing on the border of an entity ticking chunk tin place their fruits on an next block exterior an entity ticking chunk.
An entity (mob, minecart, arrow, etc.) that attempts to motion into a ticking chunk from an entity ticking chunk becomes suspended as soon as it leaves the entity ticking chunk. When the ticking chunk gets a greater level, the entity resumes moving.
Exploding TNT in entity ticking chunks tin impairment or destroy blocks in a not-entity-ticking chunk.

Bedrock Edition [ ]

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

Type [ ]

Player: A round-like shape^{[ more than data needed ]}.; Chunks within the simulation distance of a player are loading.

Control: Create with the /tickingarea command.

Limit [ ]

Entities
- Mob spawning is evaluated for every clamper inside a 6 chunk cylindrical radius of the player that is loaded.

Exception [ ]

Events in a ticking expanse may bear on blocks in outside chunks. If the exterior chunk is inactive, the furnishings are suspended in about cases. Specifically,

Cake changing on the edge of a ticking area can spread updates to blocks outside the ticking surface area and respond accordingly.
Flowing h2o or lava tin can spread to the showtime adjacent block in an outside chunk, but the catamenia becomes suspended there until the exterior chunk becomes active.
Burn down tin can spread to the starting time adjacent combustible cake outside the ticking expanse. Similar h2o and lava, it becomes suspended there; although visible, its blitheness does not run, and it cannot spread further until the outside chunk becomes active.
Grass and mycelium can spread to the starting time adjacent block in an exterior clamper, but the affected block does not actually change its appearance until its chunk becomes active; it and so changes instantly. Grass and mycelium cannot spread beyond the first such cake, nor from such a block into the ticking area until the outside clamper becomes agile.
Pumpkin and melon stem growing on the edge of a ticking area tin place their fruits on an next block in an outside chunk.
An entity (mob, minecart, arrow, etc.) that attempts to move into an exterior chunk becomes suspended equally before long every bit it leaves the ticking area. It remains visible only motionless. When the outside cake becomes active, the entity resumes moving.
Exploding TNT tin can damage or destroy blocks in an inactive chunk, and unlike other events, its effects are not limited to adjacent blocks. However, secondary effects in the outside chunk are suspended until the chunk becomes active. For instance, if an explosion destroys a block that supported sand or gravel, the sand or gravel does not fall immediately. The same thing happens with items that were attached to destroyed blocks, such equally particular frames and Redstone torches; they do non drop until the chunk is activated.
Primed TNT launched into an inactive chunk is suspended in mid-air within the first exterior block it enters. It disappears until the outer chunk becomes active, at which time it resumes its flight and countdown.

Finding chunk edges [ ]

X and Z coordinates that are divisible past sixteen represent the boundaries between chunks. EG: (96, -32) is a corner where four chunks meet. One of those chunks is between Ten coordinates 80 to 96 and Z coordinates -48 to -32. Another 1 is between Ten coordinates 96 to 112 and Z coordinates -32 to -16, and so on. When either X or Z crosses a multiple of 16, the thespian is moving across chunks.

Essentially, the histrion is in the acme-left corner (north-western) of a clamper when both X and Z coordinates are divisible by 16.

Additionally, the actor tin know the chunk they are on past this formula:
The X of a clamper is flooring(X coordinate / sixteen)
The Z of a clamper is floor(Z coordinate / 16)
Where floor is the largest previous integer. Eastward.thousand. Floor( 27.9561 ) is 27
In other words, if X was 27, Z was −fifteen the chunk is chunk (Floor(27/sixteen), Flooring(−xv/sixteen)), meaning that the role player is on chunk (one, −1).
Too, the coordinates of a block within a chunk can be found past taking the coordinate mod sixteen.

In Coffee Edition, the cardinal F3 +G tin can be used to display chunk boundaries. Alternately, pressing the "F3" button opens the Debug screen that shows the actor's Ten, Y, and Z coordinates, in addition to the "chunk" variable. These coordinates change equally the player moves around. The histrion can know the chunk they are in by the variable "chunk".

In Bedrock Edition, when toggling fancy graphics, the earth renders again, loading but the chunk the thespian is in for a split 2d, briefly showing the clamper boundaries. When the player changes the return distance rapidly, clamper barriers appear as a blue line. Too, if in mid-air and bridging with full blocks, when a chunk edge is intersected the next block placed volition fade into view, showing the chunk border. This is sometimes unreliable, just useful as it only happens on chunk borders. This does not happen underground or when the block placed is close to more than 1 cake.

Slime chunks [ ]

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

Java Edition [ ]

Slime chunks generate throughout the world (except in mushroom islands). ane in 10 of all chunks is slime clamper. These slime chunks are adamant 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 9 inclusive is generated, and if that number is 0, the chunk can spawn slimes. To convert world coordinates to chunk coordinates, split up by 16 and round down. Notation that xPosition, and zPosition are 32-bit integers (intdue south).

Boulder Edition [ ]

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

History [ ]

Coffee Edition pre-Classic
rd-131655		The precursors to chunks are showcased.
Coffee Edition Infdev
20100227-1		Map height is not custom anymore. The chunk height has been changed to 128.
Coffee Edition
1.ii.ane	12w07a	The clamper height has been increased to 256, as part of the transition from Region to Anvil file format.
one.iv.two	12w39a	The debug screen now shows the coordinates of the chunk the player is in, and the role player's coordinates in that chunk.
1.10	16w20a	`F3` + `G` now toggles the visible clamper borders around the role player.
one.14	?	The method of chunk loading has changed.
1.17	20w49a	Map height is now custom again.
	21w06a	Maximum chunk height has been increased to 320 and minimum summit has been dropped to -64, making chunks 384 blocks high in total.
	21w15a	The chunk peak changes have been reverted.
i.18	Experimental Snapshot 1	Chunks are again 384 blocks high.
i.18	21w37a	Render distance now causes chunks to load in a cylinder shape around the actor instead of a foursquare.

Trivia [ ]

If a thespian stands in a clamper that has non generated yet, the world immediately becomes invisible until they are in a valid chunk. This does not happen if the Y coordinates are beyond the clamper boundaries.
In Bedrock Edition, if 1 of the sixteen xvi×16×16 sections of a chunk doesn't have whatever blocks in information technology, placing a block there shows the same blitheness as a clamper loading. This problems makes the block that the role player placed to turn to the same colour of the sky in the direction the player is facing for about ane second and starts fading away into the normal cake texture. If the fourth dimension is sunrise or sunset and the player places a block there, it actually changes colors constantly for 1 second if the histrion keeps bobbing their head upwardly and downwards. The block too makes blocks behind it appear invisible.

References [ ]

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