How To Turn On Chunk Borders In Minecraft Bedrock

Visualization of the basis portion of a single clamper. The entire chunk extends up to a meridian of 320.

A clamper is a 384-cake alpine sixteen×16 segment of a globe. Chunks are the method used by the world generator to divide maps into manageable pieces.

Generation [ ]

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

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

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

Chunk loading [ ]

A boundary betwixt loaded and unloaded chunks.

Since Minecraft worlds are 30 million blocks in each primal management and contain an farthermost amount of chunks, the game loads just certain chunks in order to make the game playable.

Unloaded chunks are unprocessed by the game and do not procedure whatever of the game aspects.

Please note that events that can happen when a clamper is loaded, is not the aforementioned equally events that only happen around the player. For instance, normal mob spawning and random tick (determines ingather growth, etc.) tin but happen nigh a player, and will not happen in loaded chunks far away from any players.

Java Edition [ ]

Tickets [ ]

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

Each load ticket has iii properties: Level, Ticket type and (optionally) Time 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 only 22 to 33 are relevant. Load levels less than 22 (including negative levels) are valid but only possible with a modded game. Load levels in a higher place 44 are not possible in vanilla. Still, it could be possible past modifying the in-game code.

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

In that location are 4 clamper load types; each load type has different properties. This excludes unloaded chunks.

	Level	Properties
Entity Ticking	31 and below	All game aspects are active.
Ticking	32	All game aspects are active except that entities are not candy (exercise non move) and chunk ticks aren't either.
Edge	33	Only some game aspects are active (Redstone and command blocks exercise not work).
Inaccessible	34 and above	No game aspects are active, just globe generation still occurs.

Level propagation [ ]

Load levels "propagate" or flow from source clamper with a ticket to neighboring chunks, but each fourth dimension it increases its Level past 1 until the maximum of 44.

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

Level propagation with a level of 31. Note 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 dissimilar ticket types, which come from various sources and actuate chunks with unlike load types.

Player ticket

This ticket is acquired by the player and is assigned level 31. A player ticket is given to each chunk within an area surrounding the actor as defined by the formulas described below and propagates as described in the table above.

In singleplayer, the chunk loading altitude is one less than the render distance, as configured in Options. Information technology follows the formula (iir - three)² = AoC where r is the selected render distance, and AoC is the area of chunks that are assigned an original thespian ticket (level 31 - entity ticking). The minimum AoC is nine, which means that there is no departure between having the render distance set up to 2 or iii.

For example, in a single-thespian game with a render altitude of v chunks, an area of 7×7 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 ix×ix perimeter surrounding the playe accept ticking (level 32), and the next enclosing chunks (11×xi perimeter) are edge chunks (level 33).

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

Forced ticket

A ticket tin can as well exist created past using the /forceload command. Information technology has a level of 31, so its propagation can be seen in the table higher up.

Chunks remain force-loaded fifty-fifty after closing and opening the game.

Commencement ticket

Ticket created by the world spawn for the chunk 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 actor is in the Overworld and are otherwise permanently active.

Portal ticket

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

It expires afterward 300 game ticks (equivalent to 15 seconds). Considering 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 player being virtually, which can be used for various in-game mechanics such as farms, but can create lag.

Dragon ticket

Ticket created at the start of the boxing with ender dragon and is given to the 0,0 chunk (the one with exit portal). Information technology has a level of 24.

It expires after no more players participate in the boxing, 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 terminate portal, it has a level of 33.

It expires after 5 game ticks.

Temporary ticket

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

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

For example, when a generic mob wandering AI is executing, it asks if a certain block has a solid tiptop surface. Every bit 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) (cake|blocks|predicate), /make full and /setblock generate a temporary ticket when reading data from or writing it to a previously loaded clamper; if run every tick, they can prevent the chunk from unloading until the globe is reloaded.^[1]

It expires after 1 game tick.

Light ticket

Unknown, possibly 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 processed in loading chunks considering in that location may be other conditions for their progress, which includes the following:
- Chunk tick
  - Simply chunks with centers within 128 blocks of a player are ticked on every game tick. Run across also Tick.
- Entities
  - Hostile mobs instantly despawn if they spawn more than than 128 blocks from whatsoever role player.
    - This includes zombified piglins at Nether portals and witches in witch huts.
  - Passive mobs practise not spawn naturally outside a 240 block Ten 240 block area around a player.
    - The passive mob spawn cap is limited by the number of friendly mobs loaded into memory, which means that whatsoever passive mobs present in the spawn chunks count toward the mob cap and ordinarily prevents friendly mobs from naturally spawning anywhere else in the world. The merely exception is when passive mobs spawn as part of a newly generated chunk.
  - See too Spawn.

Exceptions [ ]

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

Block changing on the border of a ticking chunk can spread updates to blocks exterior the ticking chunk and brand them respond accordingly. The update may exist propagated block past block until outside the border chunks, at which time it creates a temporary ticket to continue propagation.
Block in a chunk with a 33 level can request a scheduled tick, only it does not become processed until the chunk gets a load level of 32 or beneath.
Flowing water or lava can spread to the beginning adjacent block outside a ticking chunk, but the flow becomes suspended there until the border chunk has a greater load level.
Burn down can spread to the first next flammable block outside the ticking clamper. Like h2o and lava, it becomes suspended there. Information technology cannot spread further until the outside chunk gets a level of 33 or below.
Grass and mycelium can spread to the first adjacent block outsider an entity ticking clamper.
Pumpkin and melon stalk growing on the border of an entity ticking chunk tin identify their fruits on an adjacent block outside an entity ticking clamper.
An entity (mob, minecart, arrow, etc.) that attempts to move into a ticking chunk from an entity ticking chunk becomes suspended equally soon as it leaves the entity ticking clamper. When the ticking chunk gets a greater level, the entity resumes moving.
Exploding TNT in entity ticking chunks can harm or destroy blocks in a non-entity-ticking chunk.

Boulder Edition [ ]

All game aspects are agile in loading chunks, including chunks within a player's simulation distance and chunks loaded by Commands/tickingarea. Unloaded chunks are unprocessed by the game and do not process any of the game aspects.

Type [ ]

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

Command: Create with the /tickingarea command.

Limit [ ]

Entities
- Mob spawning is evaluated for every chunk within a half dozen chunk cylindrical radius of the actor that is loaded.

Exception [ ]

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

Block changing on the edge of a ticking area tin can spread updates to blocks outside the ticking surface area and respond appropriately.
Flowing water or lava tin spread to the first side by side block in an exterior chunk, but the catamenia becomes suspended there until the outside chunk becomes active.
Fire can spread to the first adjacent flammable block outside the ticking area. Similar water and lava, it becomes suspended there; although visible, its blitheness does not run, and it cannot spread farther until the outside chunk becomes agile.
Grass and mycelium can spread to the commencement adjacent block in an outside clamper, merely the affected block does not really change its appearance until its chunk becomes active; information technology then changes instantly. Grass and mycelium cannot spread beyond the first such block, 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 expanse can place their fruits on an adjacent block in an outside chunk.
An entity (mob, minecart, arrow, etc.) that attempts to movement into an outside chunk becomes suspended every bit presently as it leaves the ticking expanse. Information technology remains visible but motionless. When the exterior block becomes active, the entity resumes moving.
Exploding TNT tin can impairment or destroy blocks in an inactive chunk, and unlike other events, its effects are not limited to next blocks. However, secondary effects in the outside clamper are suspended until the chunk becomes active. For example, if an explosion destroys a block that supported sand or gravel, the sand or gravel does not fall immediately. The aforementioned matter happens with items that were attached to destroyed blocks, such as detail frames and Redstone torches; they practise not driblet until the chunk is activated.
Primed TNT launched into an inactive chunk is suspended in mid-air inside the get-go exterior block it enters. It disappears until the outer chunk becomes active, at which fourth dimension information technology resumes its flight and inaugural.

Finding chunk edges [ ]

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

Substantially, the player is in the top-left corner (north-western) of a chunk when both X and Z coordinates are divisible past 16.

Additionally, the histrion can know the chunk they are on by this formula:
The X of a chunk is floor(X coordinate / xvi)
The Z of a clamper is floor(Z coordinate / 16)
Where flooring is the largest previous integer. Eastward.1000. Flooring( 27.9561 ) is 27
In other words, if X was 27, Z was −fifteen the clamper is clamper (Floor(27/xvi), Flooring(−15/16)), significant that the player is on chunk (ane, −1).
Also, the coordinates of a block within a clamper can be found by taking the coordinate modern 16.

In Coffee Edition, the key F3 +M can be used to display chunk boundaries. Alternately, pressing the "F3" push button opens the Debug screen that shows the player's X, Y, and Z coordinates, in addition to the "chunk" variable. These coordinates change equally the player moves around. The thespian can know the chunk they are in by the variable "clamper".

In Bedrock Edition, when toggling fancy graphics, the world renders once more, loading simply the chunk the role player is in for a carve up second, briefly showing the chunk boundaries. When the actor changes the render distance speedily, chunk barriers announced as a blueish line. Besides, 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 clamper border. This is sometimes unreliable, but useful as information technology only happens on chunk borders. This does not happen secret or when the cake placed is close to more than than i block.

Slime chunks [ ]

Slime chunks are specific chunks capable of spawning slimes below Y=xl regardless of Low-cal. These chunks are otherwise same as all other chunks.

Java Edition [ ]

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

Random rnd = new Random(     seed +     (int) (xPosition * xPosition * 0x4c1906) +     (int) (xPosition * 0x5ac0db) +      (int) (zPosition * zPosition) * 0x4307a7L +     (int) (zPosition * 0x5f24f) ^ 0x3ad8025f ); return rnd.nextInt(10) == 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 clamper tin spawn slimes. To convert world coordinates to chunk coordinates, divide by 16 and circular downwardly. Note that xPosition, and zPosition are 32-flake integers (ints).

Boulder Edition [ ]

The slime clamper algorithm in Boulder Edition is different from in Java Edition. The algorithm doesn't depend on the globe seed, thus the chunks that slimes tin naturally spawn in are the aforementioned for every world.^[2]

History [ ]

Java Edition pre-Classic
rd-131655		The precursors to chunks are showcased.
Java Edition Infdev
20100227-1		Map height is not custom anymore. The chunk pinnacle has been changed to 128.
Java Edition
one.ii.1	12w07a	The chunk meridian has been increased to 256, equally part of the transition from Region to Anvil file format.
1.four.2	12w39a	The debug screen at present shows the coordinates of the chunk the player is in, and the player's coordinates in that chunk.
1.10	16w20a	`F3` + `Grand` at present toggles the visible chunk borders around the thespian.
ane.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 tiptop has been dropped to -64, making chunks 384 blocks high in full.
	21w15a	The clamper tiptop changes have been reverted.
1.18	Experimental Snapshot 1	Chunks are again 384 blocks high.
1.18	21w37a	Render distance now causes chunks to load in a cylinder shape effectually the role player instead of a square.

Trivia [ ]

If a thespian stands in a chunk that has non generated yet, the earth immediately becomes invisible until they are in a valid chunk. This does non happen if the Y coordinates are across the chunk boundaries.
In Bedrock Edition, if one of the 16 xvi×sixteen×sixteen sections of a clamper doesn't accept whatsoever blocks in information technology, placing a block there shows the same animation as a chunk loading. This bug makes the block that the player placed to plow to the aforementioned colour of the heaven in the management the player is facing for about 1 second and starts fading abroad into the normal block texture. If the time is sunrise or sunset and the thespian places a cake there, information technology really changes colors constantly for 1 2nd if the player keeps bobbing their head upwards and down. The cake too makes blocks behind it appear invisible.

Encounter as well [ ]

Clamper format
Frame rate
Altitude

References [ ]

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