Simulation distance

Jump to navigation Jump to search

Simulation distance is a world-creation setting in Bedrock Edition that controls mob spawning and despawning, and tick updates. In Java Edition, simulation distance is a video setting related to render distance, to restrict tick update distance.

Range of simulation distance[edit | edit source]

Edition Bedrock Edition Java Edition
Singleplayer (High device performance) Even number ranging from 4 to 12, 4 in default.[Note 1] Integer ranging from 5 to 32, 12 in default.
Singleplayer (Low device performance) Even number ranging from 4 to 8, 4 in default.[Note 2] Integer from 5 to 16, 8 in default.[Note 3]
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 server.properties.

Bedrock Edition[edit | edit source]

Simulation distance
Green

Spawning and despawning range

Red

Ticking range

Simulation Distance 4 chunks receiving ticks, as well as mob despawn radius from the corners of the central chunk
The Create New World or Edit World Screen "Advanced" Tab Simulation Distance

Control[edit | edit source]

The simulation distance control appears in the settings page when creating a new world. It is separated by different worlds, and cannot be modified when the world is loading.

Spawning and despawning[edit | edit source]

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:

Mob spawning and despawning range in Bedrock Edition
Simulation distance n 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 n1 chunks of taxicab distance from player 32 to 128 blocks of Euclidean distance and no greater than n1 chunks of taxicab distance from player Greater than 128 blocks of Euclidean distance or greater than n1 chunks of taxicab distance from player

Within the simulation distance, there is a 112000 chance of the mob spawning algorithm attempting to run per chunk, per tick.

Regardless of simulation distance, mobs with persistence do not despawn, and fish always despawn when they are more than 40 blocks from the nearest player.

Tick updates[edit | edit source]

Maximum distance of lightning strikes from a lightning rod is determined by simulation distance as taxicab distance, in this case 12 chunks (192 blocks) from the player position at the center of the image.

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 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[edit | edit source]

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[edit | edit source]

This section needs to be updated.
 
Please update this section to reflect recent updates or newly available information.
Reason: Outdated. Chinese version (zh) has the latest version for reference.

Control[edit | edit source]

All worlds on the client share a simulation distance, and the distance can be modified anytime.

Ticking[edit | edit source]

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 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[edit | edit source]

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 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.

History[edit | edit source]

This section is missing information about: something that needs to be specified.
 
Please expand the section to include this information. Further details may exist on the talk page.
[hide]Java Edition
1.1821w38aAdded custom simulation distance.
21w44aNow blocks and liquid are affected by simulation distance.
The minimum simulation distance changed from 2 to 5.
[hide]Bedrock Edition
1.2.10beta 1.2.10.1Added custom simulation distance.
1.17.10beta 1.17.10.22Now the default simulation distance is 4 instead of being determined by device quality.
1.20.50Preview 1.20.50.20When the simulation distance is no less than 6, mobs 6 chunks away from player can now spawn.[1]

Gallery[edit | edit source]

Notelist[edit | edit source]

  1. Up to 10 chunks on Xbox and PlayStation
  2. Up to 6 chunks on devices with less than 2GB RAM
  3. Less than 1GB or none 64-bit Java.

References[edit | edit source]

  1. MCPE-102197 — resolved as "Fixed".