Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Minecraft:Block offset

From SAS Gaming Wiki

Template:Partially conjecture

File:5x5 Grid of Poppies.png
A completely filled in 5 by 5 grid of poppies, where each flower is subject to a block offset

Certain non-solid blocks, such as short grass, pointed dripstone, and some Minecraft:flowers do not have their textures or hitboxes centered on blocks they are placed on, and are instead staggered in a

  1. REDIRECT Template:Wikipedia

Template:Redr manner. The offset of a block depends solely on its X and Z coordinates, and not the world seed. This means that, for example, a row of flowers at the same coordinates will always be staggered the same way between worlds, and this will not be changed by a player breaking or replacing them.

All blocks with an offset have their hitbox and/or texture translated in the X and Z axis. Some blocks such as short grass or the Minecraft:fern additionally have an offset in the Y axis for their textures only. The base X, Y, and Z offsets of a block are consistent between all blocks at a certain coordinate. However, some blocks (such as Minecraft:bambooTemplate:Only or pointed dripstoneTemplate:Only) may use the base offset slightly differently than most blocks for block placement.

List of blocks subject to offset

The following is a list of blocks subject to an offset in game. Most blocks have their hitbox offset to match their texture being offset, but some do not.

Blocks subject to offset
Block Hitbox XZ offset Texture XZ offset Hitbox Y offset Texture Y offset
  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr||

  1. REDIRECT Template:Table choice

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr||

  1. REDIRECT Template:Table choice

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr||

  1. REDIRECT Template:Table choice

Template:Redr

  1. redirect Template:blockLink

Template:Redr

  1. redirect Template:blockLink

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr<ref group="note">Template:Bug</ref> ||

  1. REDIRECT Template:Table choice

Template:Redr||

  1. REDIRECT Template:Table choice

Template:Redr

  1. redirect Template:blockLink

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr

  1. redirect Template:blockLink

Template:Redr||

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr

  1. REDIRECT Template:Table choice

Template:Redr ||

  1. REDIRECT Template:Table choice

Template:Redr

Effects of block offset on textures and hitboxes

Template:Message boxTemplate:Article other In Java Edition, X and Z offsets are added to the coordinates of the center of the block to determine the new center of the texture or hitbox. In Bedrock Edition, X and Z offsets are used differently depending on the block. On both versions, the Y offset is directly added to the Y coordinate of the block to determine what Y level a texture will start. A Y offset will always be negative or zero, meaning a block's texture or hitbox may be translated downwards but never upwards.

Calculation of block offset

X and Z offset

The following algorithm is used to calculate X and Z offsets of blocks (except for pointed dripstone in Java Edition, given a block's X and Z coordinates.<ref name="offsetAlgorithm">From {{#VARDEFINE:class name|BlockBehaviour}}Template:Tooltip#offsetType({{#VARDEFINE:class name|OffsetType}}Template:Tooltip)</ref> Note that

  1. REDIRECT Template:Wikipedia

Template:Redr while treating all integers as signed 64 bit numbers must be used for correct results.<ref group="note">This corresponds to standard arithmetic operations involving the long datatype in

  1. REDIRECT Template:Wikipedia

Template:Redr.</ref> <syntaxhighlight lang="c"> temp1 = (0x2FC20F * x) XOR (0x6EBFFF5 * z) temp2 = (0x285B825 * temp1 * temp1) + (0x000B * temp1) x_offset = ((temp2 AND 0x00F0000) / 15.0 - 0.5) * 0.5 z_offset = ((temp2 AND 0xF000000) / 15.0 - 0.5) * 0.5 </syntaxhighlight>

On Java Edition, the X and Z offsets of pointed dripstone are given by calculating x_offset and z_offset above, and

  1. REDIRECT Template:Wikipedia

Template:Redr the values between -0.125 and 0.125. All other blocks have their X and Z offsets clamped between -0.25 and 0.25.<ref group="note">The y_offset however is not clamped</ref>

Y offset

The Y offset depends solely on the X and Z coordinates of a block and the block type. For all blocks with a Y offset besides small dripleaf, the Y offset is given by (using the variable temp2 from above):<ref name="offsetAlgorithm"/> <syntaxhighlight lang="c"> y_offset = ((temp2 AND 0x0F00000) / 15.0 - 1.0) * 0.2 </syntaxhighlight> On Java Edition, the Y offset for small dripleaf is half as much as the Y offset for other blocks at the same coordinates.

Notes

Template:Notelist