The different colored line pieces show the charge levels in your world:
That's all you need to know about how to watch chunk borders in Minecraft, so now that you know all this, we hope you can get a lot of use out of it, especially on large projects. Tags: minecraft classic , education edition, download, pocket edition, update, minecaft, mminecraft, mincecraft, mincrat, free Platform(s): PC, macOS, Linux, PS4, Xbox One, Nintendo Switch Genre(s): Sandbox, survival Developer(s): Mojang, Xbox, Sony, Nintendo eShop Publisher(s): Mojang, Microsoft Studios, Sony Computer Entertainment Release date: 18 November 2011 Mode: Single-player, multiplayer Official Website: Official Website Other Tagsvideo game, gameplay, price, 60fps, steam
A chunk is a 384-block tall 16×16 segment of a world. Chunks are the method used by the world generator to divide maps into manageable pieces. Generation[]Chunks are 16 blocks wide, 16 blocks long, 384 blocks high, and 98,304 blocks total. They extend from the bottom of the world, Y=-64, all the way up to the build limit of Y=320. Chunks generate around players when they first enter the world. As they wander around the world, new chunks generate as needed. Chunks generate with the help 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 same. Spawn chunks, a 19x19 set of chunks around the world spawn, are always loaded, so you can use that to your advantage when making automatic farms. Chunk loading[]Since Minecraft worlds are 30 million blocks in each cardinal direction and contain an extreme amount of chunks, the game loads only certain chunks in order to make the game playable. Unloaded chunks are unprocessed by the game and do not process any of the game aspects. Please note that events that can happen when a chunk is loaded, is not the same as events that only happen around the player. For example, normal mob spawning and random tick (determines crop growth, etc.) can only happen near a player, and will not happen in loaded chunks far away from any players. Java Edition[]Tickets[]Loading starts when a chunk receives ticket. All loaded chunks originate from the ticket. Each load ticket has three 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 above 44 are not possible in vanilla. However, it could be possible by modifying the in-game code. For a given chunk, only its lowest level matters. (Lower levels = higher load type.) There are four chunk load types; each load type has different properties. This excludes unloaded chunks.
Level propagation[]Load levels "propagate" or flow from source chunk with a ticket to neighboring chunks, but 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.
Ticket types[]There are different ticket types, which come from various sources and activate chunks with different load types. Player ticket
This section needs to be updated. Please update this section to reflect recent updates or newly available information. 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 defined by the formulas described below and propagates as described in the table above. In singleplayer, the chunk loading distance is one less than the render distance, as configured in Options. It follows the formula (2r - 3)2 = AoC where r is the selected render distance, and AoC is the area of chunks that are assigned an original player ticket (level 31 - entity ticking). The minimum AoC is 9, which means that there is no difference between having the render distance set to 2 or 3. For example, in a single-player game with a render distance of 5 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 9×9 perimeter surrounding the player have ticking (level 32), and the next enclosing chunks (11×11 perimeter) are border chunks (level 33). In multiplayer, the chunk loading distance is equal to the view-distance, as configured in server.properties. It follows the formula (2v + 1)2 = 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 5 chunks, an area of 11×11 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 13×13 perimeter surrounding the player have ticking (level 32), and the next enclosing chunks (15×15 perimeter) are border chunks (level 33). Forced ticketA ticket can also be created by using the /forceload command. It has a level of 31, so its propagation can be seen in the table above. Chunks remain force-loaded even after closing and opening the game. Start ticketTicket created by the world spawn for the chunk it is located at ("spawn chunks"). Its position can be changed by 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 ticketTicket 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, so it is stronger than the player/force 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 as farms, but can create lag. Dragon ticketTicket created at the start 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. Post-teleport ticketTicket 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 5 game ticks. Temporary ticketTicket 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 chunk or not). It is always level 33 (border) 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 top 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 prevent the chunk from unloading until the world is reloaded.[1] It expires after 1 game tick. Light ticketUnknown, possibly world-generation related. Limitations[]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).
Exceptions[]Events in a chunk may affect blocks in outside chunks. If the outside chunk is inactive, the effects are suspended in most cases. Specifically,
Bedrock Edition[]Main article: Ticking area All game aspects are active 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 within the simulation distance of a player are loading. Command Create with the /tickingarea command.Limit[]
Exception[]Events in a ticking area may affect blocks in outside chunks. If the outside chunk is inactive, the effects are suspended in most cases. Specifically,
Finding chunk edges[]X and Z coordinates that are divisible by 16 represent the boundaries between chunks. EG: (96, -32) is a corner where four chunks meet. One of those chunks is between X coordinates 80 to 96 and Z coordinates -48 to -32. Another one is between X coordinates 96 to 112 and Z coordinates -32 to -16, and so on. When either X or Z crosses a multiple of 16, the player is moving across chunks. Essentially, the player is in the top-left corner (north-western) of a chunk when both X and Z coordinates are divisible by 16. Additionally, the player can know the chunk they are on by this formula: The X of a chunk is floor(X coordinate / 16) The Z of a chunk is floor(Z coordinate / 16) Where floor is the largest previous integer. E.g. Floor( 27.9561 ) is 27 In other words, if X was 27, Z was −15 the chunk is chunk (Floor(27/16), Floor(−15/16)), meaning that the player is on chunk (1, −1). Also, the coordinates of a block within a chunk can be found by taking the coordinate mod 16. |