Block entities store additional information about certain blocks, with the type of information varying by block. In some cases, this information is used to create a more complex model, such as the book on an enchanting table. In other cases, it is used to store contents of an object. Blocks with block entities can be moved by pistons in Bedrock Edition, but not in Java Edition.
List of block entities
These are the current blocks that hold block entities.
|To store bees.|
|To store written text.|
|To store the patterns.|
|To store their contents.
|To store the pyramid level, active effects, and contents. Also uses the block's position for the beacon beam.|
|To store the note to be played.|
|To store the offset of block, and blocks that it should move or break.|
|To store the offset of block[Java Edition only], direction of movement[Java Edition only], and ID (and data value, if applicable) of the moving block.|
|To play music discs, if any are inside.|
|For the floating book.|
|For the particle field effect.|
|For the type of the head[Bedrock Edition only], rotation when placed on top of a block[Bedrock Edition only], and (if applicable) data of the player represented.|
|For the command text, its output strength, and the output text.|
|For the teleport location and also whether to render the beam.|
|To store information about the structure.|
|To store the structure pool and the block this jigsaw block becomes.|
|To store whether the reaction started and the time remaining in the reaction.|
|To force the daylight sensor to update its output signal strength.|
|To store the ID and the data value of the block displayed inside of it.|
|To store its output strength.|
|To store color[Bedrock Edition only] and for rendering the block.|
|To store details about liquid content. Cauldrons containing dyed water store water color. Cauldrons containing potions store the potion's ID and a tag of whether it is a splash potion or not.|
|To check its activation area for valid activation blocks and calculate its effective range. Also used for rendering the block in its active and inactive states.|
|For the render of the swaying animation of the bell.|
|To link with compass.|
|To store written text.|
|To store the items in lab table and the process of lab experiment.|
Block entities and their render limits
Some block entities, or their effects, stop being rendered beyond a hard-coded block limit which is modeled after the radius of a sphere. This limit is not affected by the Render Distance nor the Entity Distance scale in the Video Settings.
Block entities that stop rendering beyond 64 blocks include:
Some effects related to block entities stop rendering beyond a number of blocks:
- The beacon and end gateway beams stop rendering beyond 256 blocks or when the end gateway is out of frame.
- The contents of a campfire stop rendering beyond 64 blocks.
- The book on a lectern stops rendering beyond 64 blocks.
- The mob inside a spawner stops spinning beyond the RequiredPlayerRange, which is 16 blocks by default, and stops rendering beyond 64 blocks.
- The note particles emitted by a note block stop rendering beyond 32 blocks.
- Pistons stop animating beyond 64 blocks.
- The book on an enchanting table stops rendering beyond 64 blocks.
- The outlines created by a structure block stop rendering beyond 96 blocks.
- The bell part of the model of a bell, but not the frame, stops rendering beyond 64 blocks.
- Chunk format § Block entity format – describes the save format for block entities
- Entities, which are all the dynamic, moving objects throughout the Minecraft world, plus several non-moving objects that resemble blocks.
- Block states, which are, like block entities, extra pieces of data that further define a block.