Minecraft:Simulation distance
More actions
Simulation distance is a world option Template:In that controls mob spawning and despawning, and Minecraft:tick updates. Template:IN, simulation distance is a video setting related to render distance, to restrict tick update distance.
Range of simulation distance
| Edition | Template:BE | Template:JE |
|---|---|---|
| Singleplayer (High device performance) | Even number ranging from 4 to 12, 4 in default.<ref group="note">Up to 10 chunks on Xbox and PlayStation</ref> | Integer ranging from 5 to 32, 12 in default. |
| Singleplayer (Low device performance) | Even number ranging from 4 to 8, 4 in default.<ref group="note">Up to 6 chunks on devices with less than 2GB RAM</ref> | Integer from 5 to 16, 8 in default.<ref group="note">Less than 1GB or none 64-bit Java.</ref> |
| Multiplayer | Integer ranging from 4 to 12, 4 in default. | Integer ranging from 3 to 32, 10 in default. |
The simulation distance of the Minecraft server can be modified in the file Minecraft:server.properties.
Bedrock Edition
.png){kind=link}
Control
The simulation distance control appears in the "Advanced" tab of the create new world screen or Minecraft:edit world screen. It is separated by different worlds, and cannot be modified when the world is loading.
Spawning and despawning
Simulation distance restricts the range at which mobs spawn and despawn.
The minimum spawning distance is 24 blocks (Euclidean distance) from the player. The maximum spawning distance and despawning distances are determined by the simulation distance, which is a quasi-spherical shell having the following ranges relative to the player:
| Simulation distance <math>n</math> | Mob spawning range | Mob randomly despawning range | Mob immediately despawning range. |
|---|---|---|---|
| 4 | 24 to 44 blocks of Euclidean distance from player | 32 to 44 blocks of Euclidean distance from player | Greater than 44 blocks of Euclidean distance from player |
| >4 | 24 to 128 blocks of Euclidean distance and no greater than <math>n-1</math> chunks of Minecraft:taxicab distance from player | 32 to 128 blocks of Euclidean distance and no greater than <math>n-1</math> chunks of taxicab distance from player | Greater than 128 blocks of Euclidean distance or greater than <math>n-1</math> chunks of taxicab distance from player |
Within the simulation distance, there is a Template:Frac chance of the mob spawning algorithm attempting to run per chunk, per tick.
Regardless of simulation distance, mobs with Minecraft:persistence do not despawn, and Minecraft:fish always despawn when they are more than 40 blocks from the nearest player.
Tick updates
Simulation distance determines the maximum chunk distance in which entities get updated, and blocks and fluids are ticked. This is not a Euclidean distance, but Minecraft:taxicab distance in Bedrock Edition.
These ticks include random ticking of crops, amethysts and such. The simulation distance is purely chunk based and has nothing to do with the player's position inside the chunk.
Pure redstone circuits continue to function infinitely far away, but break down where they interact with hoppers, pistons, observers, and anything else that needs tick updates to function.
Mob cap
Mobs in chunks outside a ticking area still count toward the per-mob population control caps as long as they were previously loaded within the simulation distance at some time.
Java Edition
Control
All worlds on the client share a simulation distance, and the distance can be modified anytime.
Ticking
Simulation distance defines a square region of chunks around the player where entities are ticked. Using distance of 6 for instance, entities may move normally within a 13×13 chunk column around the player chunk. One more chunk out, within a one-chunk-thick square frame surrounding this region, redstone may run, fluid may flow, and crop may grow (subject to normal chunk ticking rules). Beyond that nothing moves or changes. But these game aspects are also subject to chunk loading rules. See also Minecraft:Chunk#Ticking.
The simulation distance setting is ideally less than render distance because updating all entities within the simulation distance is more taxing on performance than the equivalent level of render distance.
Entity visibility
Not all entities within the loaded and visible chunks are displayed to the player. There are three criteria that hide entities from view. First, the server does not send any information about an entity to the client if the entity is beyond a certain distance from the player, controlled by "entity-broadcast-range-percentage" in the Minecraft:server.properties file. Second, the client does not render entities depending on both "Render distance" and "Entity distance" video settings. Apparently, render distance (in chunks) multiplied by a magic number (about 8.5 for mobs, 2 for items) and scaled by the "entity distance" percentage gives the radius in blocks for a sphere around the player beyond which entities are hidden. For example, using render distance 10 and 100% entity distance, a skeleton disappears from view if the player stands more than 85 blocks directly above it. The magic number varies slightly for different types of mobs, such as being larger for spiders and ghasts, even though ghasts still frequently attack player from beyond visibility range. Finally, the client has a hard visibility limit of 128 blocks horizontally, defining another circular column. Entities are displayed only if they are inside the intersection of this sphere and two cylinders.