Minecraft:Hitbox - Revision history

SyncBot: Sync: updated from Minecraft

2026-10-15T11:09:03Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:09, 15 October 2026
Line 17:		Line 17:
	When the bounding boxes between two entities overlap, a small force is applied to each entity proportional to the distance between them to push them away from each other horizontally. Because there is no vertical collision, it is possible to put multiple entities in the same block by dropping them in from above.		When the bounding boxes between two entities overlap, a small force is applied to each entity proportional to the distance between them to push them away from each other horizontally. Because there is no vertical collision, it is possible to put multiple entities in the same block by dropping them in from above.

	An entity's bounding box can transform into different shapes depending on certain situations, typically unique to the entity itself. For instance, a [[Minecraft:pufferfish]] when approached by players gradually expands its shape, from unpuffed, to semi-puffed, then to fully puffed. It instantly shrinks its shape back to normal once it cools down. Players can also change their bounding box by [[Minecraft:sneaking]], [[Minecraft:~~crawl~~]]~~ing~~, [[Minecraft:~~swim~~]]~~ming~~, [[Minecraft:gliding]], or any other means.		An entity's bounding box can transform into different shapes depending on certain situations, typically unique to the entity itself. For instance, a [[Minecraft:pufferfish]] when approached by players gradually expands its shape, from unpuffed, to semi-puffed, then to fully puffed. It instantly shrinks its shape back to normal once it cools down. Players can also change their bounding box by [[Minecraft:sneaking]], [[Minecraft:crawling]], [[Minecraft:swimming]], [[Minecraft:gliding]], or any other means.

	Bounding boxes can be scaled by {{attr\|minecraft:scale}} attribute, or for specific entities, like [[Minecraft:interaction]], it can be changed by modifying [[Minecraft:Interaction#Entity data\|their entity data]].		Bounding boxes can be scaled by {{attr\|minecraft:scale}} attribute, or for specific entities, like [[Minecraft:interaction]], it can be changed by modifying [[Minecraft:Interaction#Entity data\|their entity data]].
Line 232:		Line 232:
	\|		\|
	\|-		\|-
	\|{{BlockLink\|Honey Block}} \|\| ~~15×15×15~~		\|{{BlockLink\|Honey Block}} \|\| 14×15×14
	\|Full block (16×16×16)		\|Full block (16×16×16)
	\|		\|
Line 388:		Line 388:
	}}		}}
	[[File:Barrier_Outline_Box_(held).png\|thumb\|200px\|A [[barrier]] block's interaction box is shown when hovered by the [[Minecraft:crosshair]].]]		[[File:Barrier_Outline_Box_(held).png\|thumb\|200px\|A [[barrier]] block's interaction box is shown when hovered by the [[Minecraft:crosshair]].]]
	The interaction box manages block interactions with [[Minecraft:~~players~~]], such as block placement, destruction, {{control\|use}} actions, etc. When looking at the given block, the interaction box is shown as a black outline around the block's edges; this is especially visible in the [[Minecraft:barrier]] block. The interaction box appears only if the block the player is looking at is inside of the [[Minecraft:interaction range]].		The interaction box manages block interactions with [[Minecraft:player]]s, such as block placement, destruction, {{control\|use}} actions, etc. When looking at the given block, the interaction box is shown as a black outline around the block's edges; this is especially visible in the [[Minecraft:barrier]] block. The interaction box appears only if the block the player is looking at is inside of the [[Minecraft:interaction range]].

	A block's interaction box is usually contained within its own 1×1×1 cube space. However, some blocks, such as the ones reported below, are capable of extending outside of this space.		A block's interaction box is usually contained within its own 1×1×1 cube space. However, some blocks, such as the ones reported below, are capable of extending outside of this space.

SyncBot: Sync: updated from Minecraft

2026-09-20T11:09:51Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:09, 20 September 2026
Line 1:		Line 1:
	{{Missing information\|List of interaction boxes for the blocks.}}<!--Perhaps this list could be made on another page; in any case, it would be important to at least have the link to this list here.-->		{{Missing information\|List of interaction boxes for the blocks.}}<!--Perhaps this list could be made on another page; in any case, it would be important to at least have the link to this list here.-->

	[[File:Zombie chasing villager with hitboxes.png\|thumb\|right\|A [[zombie]] chasing a [[Minecraft:villager]] with their hitboxes visible by using the "entity_hitboxes" [[Minecraft:debug renderer]].]]		[[File:Zombie chasing villager with hitboxes.png\|thumb\|right\|A [[zombie]] chasing a [[Minecraft:villager]] with their hitboxes visible by using the "entity_hitboxes" [[Minecraft:debug renderer]]]]

	A '''hitbox''' defines the physical boundary (or an approximation thereof) of a [[Minecraft:block]] or [[Minecraft:entity]]. Hitboxes are used in the calculations of collisions and targeting.		A '''hitbox''' defines the physical boundary (or an approximation thereof) of a [[Minecraft:block]] or [[Minecraft:entity]]. Hitboxes are used in the calculations of collisions and targeting.
Line 674:		Line 674:
	=== Screenshots ===		=== Screenshots ===
	<gallery>		<gallery>
	Ender dragon green hitboxes.png\|[[Minecraft:~~Ender~~ dragon]] has nine distinct hitboxes.		Ender dragon green hitboxes.png\|The [[Minecraft:ender dragon]] has nine distinct hitboxes.
	Wither hitbox.png\|Wither heads don't have a hitbox of their own.		Wither hitbox.png\|Wither heads don't have a hitbox of their own.
	Player hitbox while gliding using elytra.png\|[[Minecraft:Player]]s' small hitbox while [[Minecraft:gliding]] using an elytra.		Player hitbox while gliding using elytra.png\|[[Minecraft:Player]]s' small hitbox while [[Minecraft:gliding]] using an elytra
	Sheep upside down hitbox.png\|Sheep ~~has~~ the same hitboxes despite being [[Minecraft:Name_Tag#Easter_eggs\|upside down]].		Sheep upside down hitbox.png\|Sheep have the same hitboxes despite being [[Minecraft:Name_Tag#Easter_eggs\|upside down]].
	Items having entity hitboxes.png\|Items also have entity hitboxes.		Items having entity hitboxes.png\|Items also have entity hitboxes.
	Item frames and painting having entity hitboxes.png\|Pseudo-blocks like item frame and painting have entity hitboxes.		Item frames and painting having entity hitboxes.png\|Pseudo-blocks like the item frame and painting have entity hitboxes.
	</gallery>		</gallery>

SyncBot: Sync: updated from Minecraft

2026-08-10T11:16:23Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:16, 10 August 2026
Line 36:		Line 36:
	== Block hitboxes ==		== Block hitboxes ==
	=== Collision box ===		=== Collision box ===
			{{info needed section\|Do entities (boats, shulkers, happy ghasts) also have collision boxes?}}
	{{Anchor\|Block collision}}		{{Anchor\|Block collision}}
	{{FakeImage\|<nowiki/>		{{FakeImage\|<nowiki/>

SyncBot: Sync: updated from Minecraft

2026-07-27T11:05:54Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:05, 27 July 2026
Line 43:		Line 43:
	\|class=nomobile}}		\|class=nomobile}}
	<div class="mobileonly">[[File:Fences_hitboxes_height.png\|thumb\|[[Fence]]s have a one block tall interaction box, but with 1.5 blocks tall collision box.]]</div>		<div class="mobileonly">[[File:Fences_hitboxes_height.png\|thumb\|[[Fence]]s have a one block tall interaction box, but with 1.5 blocks tall collision box.]]</div>
	The collision box manages a block's collision with entities~~. They are usually shaped in cubes~~, ~~but some may have different shapes~~, ~~like~~ [[Minecraft:~~slab~~]]s, [[Minecraft:~~lectern~~]]s, [[Minecraft:~~lily pad~~]]s, [[Minecraft:~~fence~~]]s, [[Minecraft:~~wall~~]]s, and [[Minecraft:~~stair~~]]s.		The collision box manages a block's collision with entities, blocked movements and other various effects, such as blocking line of sight in [[Minecraft:mob AI]].

			A collision box may not be present for all blocks; for example [[Minecraft:grass]], [[Minecraft:sign]], [[Minecraft:button]], [[Minecraft:lever]], and [[Minecraft:torch]] have no collision box.

	A collision box may not be present for all blocks; [[Minecraft:non-solid block]]s such as [[Minecraft:grass]], [[Minecraft:sign]], [[Minecraft:button]], [[Minecraft:lever]], and [[Minecraft:torch]] have no collision box.
	~~{{Collapse~~
	~~\|title=~~
	The list below shows all blocks defined as {{cd\|noCollision}} {{in\|JE}}{{Note\|This is not exactly a list of all blocks without collision. It's possible for a block to have no collision because it has an empty interaction box (e.g., [[Minecraft:light (block)\|light]]). It is also possible that blocks in the list have a collision box, in case the collision box was created later (e.g., [[Minecraft:scaffolding]] and [[Minecraft:Hanging Signs\|wall hanging signs]]). In the [[Minecraft:Tutorial:See Minecraft's code\|game's code]], these blocks are defined in the {{jcp\|net.minecraft.world.level.block.Blocks}} class.}}:		The list below shows all blocks defined as {{cd\|noCollision}} {{in\|JE}}{{Note\|This is not exactly a list of all blocks without collision. It's possible for a block to have no collision because it has an empty interaction box (e.g., [[Minecraft:light (block)\|light]]). It is also possible that blocks in the list have a collision box, in case the collision box was created later (e.g., [[Minecraft:scaffolding]] and [[Minecraft:Hanging Signs\|wall hanging signs]]). In the [[Minecraft:Tutorial:See Minecraft's code\|game's code]], these blocks are defined in the {{jcp\|net.minecraft.world.level.block.Blocks}} class.}}:
	\|~~content~~=~~{{flatlist~~\|		{{-}}
			{{columns-list\|colwidth=16em\|
	*{{BlockLink\|Activator Rail}}		*{{BlockLink\|Activator Rail}}
	*{{BlockLink\|Air}}		*{{BlockLink\|Air}}
Line 165:		Line 165:
	*{{BlockLink\|Wither Rose}}		*{{BlockLink\|Wither Rose}}
	}}		}}
	}}

	~~While most blocks have their~~ collision box ~~identical~~ to ~~their~~ interaction box{{Note\|~~The interaction box is considered with an empty context.~~ Thus, for example, [[Minecraft:light (block)\|light]] will always have an empty collision box, even when the entity is holding the light item. However, ~~[[Minecraft:~~block states]] are still considered}} or an empty ~~collision box if it is a non-solid block~~, some may have a different collision box compared to their interaction box counterpart. For instance, a [[Minecraft:lectern]]'s collision box does not extend into the upper part of their interaction box, and a [[Minecraft:fence]]'s collision box is a bit taller than their interaction box. The table below shows all the exceptions {{in\|JE}}:{{note\|In the table, trios like 1×2×3 represent a box in the shape of a cuboid with 1 pixel in X, 2 pixels in Y, and 3 pixels in Z. If the note column is empty, the center of XZ-plane is the same as the center of the block and starts at the base. For example, 16×16×16 is a full block.}}		The collision box of a block can vary depending on the [[Minecraft:block states]], [[Minecraft:block entity]], or context. By default, the collision box is equal to the interaction box with an empty context{{Note\|Thus, for example, [[Minecraft:light (block)\|light]] will always have an empty collision box, even when the entity is holding the light item. However, block states and entity are still considered}}, or empty for the blocks mentioned above, however some blocks may have a different collision box compared to their interaction box counterpart.

			The table below shows all the exceptions {{in\|JE}}:{{note\|In the table, trios like 1×2×3 represent a box in the shape of a cuboid with 1 pixel in X, 2 pixels in Y, and 3 pixels in Z. If the note column is empty, the center of XZ-plane is the same as the center of the block and starts at the base. For example, 16×16×16 is a full block.}}
	{{Clear}}		{{Clear}}
	{\| class="wikitable sortable ~~collapsed~~ collapsible"		{\| class="wikitable sortable collapsible"
	!Block !! Collision box		!Block !! Collision box
	!Interaction box		!Interaction box
Line 381:		Line 382:
	=== Interaction box ===		=== Interaction box ===
	<!-- [[Minecraft:Interaction box]] redirects here. -->		<!-- [[Minecraft:Interaction box]] redirects here. -->
			{{info needed section\|
			* Adding information using the interaction box can change depending on the context. For example, light and scaffolding
			<!-- These two are the only ones that change when holding the item. But maybe there are more that change in other contexts; there are more than 100 classes that define the shape ('interaction box'). Save mistake, I saw them all a while ago and there weren't any left, but I'm not sure - Aloi4-->
			}}
	[[File:Barrier_Outline_Box_(held).png\|thumb\|200px\|A [[barrier]] block's interaction box is shown when hovered by the [[Minecraft:crosshair]].]]		[[File:Barrier_Outline_Box_(held).png\|thumb\|200px\|A [[barrier]] block's interaction box is shown when hovered by the [[Minecraft:crosshair]].]]
	The interaction box manages block interactions with [[Minecraft:players]], such as block placement, destruction, {{control\|use}} actions, etc. When looking at the given block, the interaction box is shown as a black outline around the block's edges; this is especially visible in the [[Minecraft:barrier]] block. The interaction box appears only if the block the player is looking at is inside of the [[Minecraft:interaction range]].		The interaction box manages block interactions with [[Minecraft:players]], such as block placement, destruction, {{control\|use}} actions, etc. When looking at the given block, the interaction box is shown as a black outline around the block's edges; this is especially visible in the [[Minecraft:barrier]] block. The interaction box appears only if the block the player is looking at is inside of the [[Minecraft:interaction range]].
Line 400:		Line 405:
	Incorrect. It could collide with the glass!		Incorrect. It could collide with the glass!
	-->		-->
	{{Missing information\|section=1\|section\|Mechanics {{In\|BE}}, this section was based on {{JE}} code.}}		{{Missing information\|section=1\|section\|
			* Mechanics {{In\|BE}}, this section was based on {{JE}} code.
			* Describe how lily pads, frogspawn and spawn eggs work when targeting water - it doesn't seem to be an interaction box based thing, so there could be a valuable distinction to make here}}
	=== Auxiliary interaction box ===		=== Auxiliary interaction box ===

Line 461:		Line 468:
	When an interaction occurs inside an interaction box or an auxiliary interaction box, the position and direction of the interaction are no longer calculated according to the first point encountered. Instead, the direction is considered dependent on the angle of the player's vision, and the position depends on the initial position of the interaction (the player's eye). Specifically, an interaction is considered inside a box if a point 0.001×{{cd\|[[Minecraft:interaction_range\|block_interaction_range]]}} blocks in the direction of the interaction is inside the box, the interaction position is also that point. However, the auxiliary interaction box in these cases still does not define the final interaction position (this is still defined by the interaction box). That is, interacting with a block inside an auxiliary interaction box, the direction will be calculated by the angle, but the position will still depend on the interaction box.		When an interaction occurs inside an interaction box or an auxiliary interaction box, the position and direction of the interaction are no longer calculated according to the first point encountered. Instead, the direction is considered dependent on the angle of the player's vision, and the position depends on the initial position of the interaction (the player's eye). Specifically, an interaction is considered inside a box if a point 0.001×{{cd\|[[Minecraft:interaction_range\|block_interaction_range]]}} blocks in the direction of the interaction is inside the box, the interaction position is also that point. However, the auxiliary interaction box in these cases still does not define the final interaction position (this is still defined by the interaction box). That is, interacting with a block inside an auxiliary interaction box, the direction will be calculated by the angle, but the position will still depend on the interaction box.

	=== ~~Blocks~~ visual box ===		=== Block visual box ===

	In most instances where ''Minecraft'' uses [[Minecraft:w:line_clipping\|line clipping]] for detection, it utilizes the collision box or the interaction box of the blocks. For example, when a player tries to interact with a block, the game draws a line from it to the [[Minecraft:interaction range]] and looks for the first block whose interaction box the line intersects with. In the case of movement, the game draws a line in the direction of movement to find the first collision box to limit movement instead of crossing it.		In most instances where ''Minecraft'' uses [[Minecraft:w:line_clipping\|line clipping]] for detection, it utilizes the collision box or the interaction box of the blocks. For example, when a player tries to interact with a block, the game draws a line from it to the [[Minecraft:interaction range]] and looks for the first block whose interaction box the line intersects with. In the case of movement, the game draws a line in the direction of movement to find the first collision box to limit movement instead of crossing it.
Line 608:		Line 615:
	\|{{HistoryLine\|\|1.2\|The hitbox of cakes at far distances became greater than a full block.}}		\|{{HistoryLine\|\|1.2\|The hitbox of cakes at far distances became greater than a full block.}}
	\|{{HistoryLine\|java}}		\|{{HistoryLine\|java}}
	\|{{HistoryLine\|\|?\|[[Minecraft:Stairs]] cannot be targeted at angles where the crosshair does not point at a solid feature of the block. However, the wireframe outline still displays as a full cube regardless.}}
	~~\|{{HistoryLine\|\|?\|The hitboxes for randomly misaligned blocks such as tall grass are now themselves randomly offset as well to accommodate them.}}~~
	\|{{HistoryLine\|\|1.0.0\|dev=Beta 1.9 Prerelease 2\|[[Minecraft:Fence]]s no longer have a full block hitbox on the xz plane, and instead more closely match their shape.}}		\|{{HistoryLine\|\|1.0.0\|dev=Beta 1.9 Prerelease 2\|[[Minecraft:Fence]]s no longer have a full block hitbox on the xz plane, and instead more closely match their shape.}}
	\|{{HistoryLine\|\|1.1\|dev=12w01a\|The [[Minecraft:fence gate]] hitbox has changed to match the changes made to fence hitboxes.}}		\|{{HistoryLine\|\|1.1\|dev=12w01a\|The [[Minecraft:fence gate]] hitbox has changed to match the changes made to fence hitboxes.}}
			\|{{HistoryLine\|\|1.3.1\|dev=12w23a\|[[Minecraft:Stairs]] cannot be targeted at angles where the crosshair does not point at a solid feature of the block. However, the wireframe outline still displays as a full cube regardless.}}
	\|{{HistoryLine\|\|1.4.4\|dev=1.4.3\|[[Minecraft:Wall]]s now have their own collision box size - previously they shared their size with fences.<ref>{{bug\|MC-1332\|\|\|Fixed}}</ref>		\|{{HistoryLine\|\|1.4.4\|dev=1.4.3\|[[Minecraft:Wall]]s now have their own collision box size - previously they shared their size with fences.<ref>{{bug\|MC-1332\|\|\|Fixed}}</ref>
	\|The above change also fixed [[Minecraft:Java Edition distance effects#Fences, fence gates and walls\|a bug causing their hitboxes to distort and stop working correctly at far distances from the world origin]].}}		\|The above change also fixed [[Minecraft:Java Edition distance effects#Fences, fence gates and walls\|a bug causing their hitboxes to distort and stop working correctly at far distances from the world origin]].}}
Line 622:		Line 628:
	\|{{HistoryLine\|\|\|dev=15w49b\|The hitbox height of the [[Minecraft:end portal block]] has been increased from {{frac\|1\|16}} of a block to {{frac\|3\|4}} of a block.}}		\|{{HistoryLine\|\|\|dev=15w49b\|The hitbox height of the [[Minecraft:end portal block]] has been increased from {{frac\|1\|16}} of a block to {{frac\|3\|4}} of a block.}}
	\|{{HistoryLine\|\|1.11\|dev=16w35a\|Cake's hitbox now appears at the right position again.<ref>{{bug\|MC-106300\|\|\|Fixed}}</ref>}}		\|{{HistoryLine\|\|1.11\|dev=16w35a\|Cake's hitbox now appears at the right position again.<ref>{{bug\|MC-106300\|\|\|Fixed}}</ref>}}
			\|{{HistoryLine\|\|\|dev=16w36a\|The hitboxes for randomly misaligned blocks such as flowers are now themselves randomly offset as well to accommodate them.}}
	\|{{HistoryLine\|\|1.13\|dev=17w47a\|The hitbox of [[Minecraft:brewing stand]]s now takes into account the central rod as well.<ref>{{bug\|MC-4504\|\|\|Fixed}}</ref>{{verify\|is this actually an entity collision thing?}}		\|{{HistoryLine\|\|1.13\|dev=17w47a\|The hitbox of [[Minecraft:brewing stand]]s now takes into account the central rod as well.<ref>{{bug\|MC-4504\|\|\|Fixed}}</ref>{{verify\|is this actually an entity collision thing?}}
	\|The collision box of [[Minecraft:wall]]s has been made to be correctly concave.<ref>{{bug\|MC-2666\|\|\|Fixed}}</ref>{{verify\|is this also an entity collision thing?}}\|The outline boxes of [[Minecraft:anvil]]s and [[Minecraft:hopper]]s now much more closely fit the model shape of these blocks.		\|The collision box of [[Minecraft:wall]]s has been made to be correctly concave.<ref>{{bug\|MC-2666\|\|\|Fixed}}</ref>{{verify\|is this also an entity collision thing?}}\|The outline boxes of [[Minecraft:anvil]]s and [[Minecraft:hopper]]s now much more closely fit the model shape of these blocks.

SyncBot: Sync: updated from Minecraft

2026-07-22T11:14:40Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:14, 22 July 2026
Line 212:		Line 212:
	\|-		\|-
	\|{{BlockLink\|Fence Gates}}		\|{{BlockLink\|Fence Gates}}
	\|\|		\|\|
	~~Closed~~: Empty		Open: Empty

	~~Open~~, facing is {{cd\|east}}/{{cd\|west}}: 16×24×4		Closed, facing is {{cd\|east}}/{{cd\|west}}: 16×24×4

	~~Open~~, facing is {{cd\|north}}/{{cd\|south}}: 4×24×16		Closed, facing is {{cd\|north}}/{{cd\|south}}: 4×24×16

	\|		\|

SyncBot: Sync: updated from Minecraft

2026-07-17T11:07:22Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:07, 17 July 2026
Line 415:		Line 415:
	{\| class="wikitable sortable collapsed <!--collapsible-->"		{\| class="wikitable sortable collapsed <!--collapsible-->"
	!Block		!Block
	!Auxiliary ~~nteraction~~ box		!Auxiliary interaction box
	!Notes		!Notes
	\|-		\|-

SyncBot: Sync: updated from Minecraft

2026-07-14T11:09:07Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:09, 14 July 2026
Line 1:		Line 1:
	{{Missing information\|List of interaction boxes for the blocks.}}<!--Perhaps this list could be made on another page; in any case, it would be important to at least have the link to this list here.-->		{{Missing information\|List of interaction boxes for the blocks.}}<!--Perhaps this list could be made on another page; in any case, it would be important to at least have the link to this list here.-->

	[[File:Zombie chasing villager with hitboxes.png\|thumb\|right\|A [[zombie]] chasing a [[Minecraft:villager]] with their hitboxes visible by using ~~{{Keys\|F3 + B}}~~ debug ~~hotkey~~.]]		[[File:Zombie chasing villager with hitboxes.png\|thumb\|right\|A [[zombie]] chasing a [[Minecraft:villager]] with their hitboxes visible by using the "entity_hitboxes" [[Minecraft:debug renderer]].]]

	A '''hitbox''' defines the physical boundary (or an approximation) of a [[Minecraft:block]] or [[Minecraft:entity]]. Hitboxes are used in the calculations of collisions and targeting.		A '''hitbox''' defines the physical boundary (or an approximation thereof) of a [[Minecraft:block]] or [[Minecraft:entity]]. Hitboxes are used in the calculations of collisions and targeting.

	Unlike with block models, all hitboxes' sizes are hard-coded and cannot be changed independently without modification.		Unlike with block models, all hitboxes' sizes are hard-coded and cannot be changed independently without modification.
Line 372:		Line 372:

	{{IN\|JE}}, it is possible to visualize the collision boxes by enabling {{cd\|[[Minecraft:Debug_renderer#visualize_collision_boxes\|visualize_collision_boxes]]}} in the debug renderer. It is also possible to see when the [[Minecraft:debug property]] {{cd\|SHAPES}} is enabled, indicated by a dark gray outline.		{{IN\|JE}}, it is possible to visualize the collision boxes by enabling {{cd\|[[Minecraft:Debug_renderer#visualize_collision_boxes\|visualize_collision_boxes]]}} in the debug renderer. It is also possible to see when the [[Minecraft:debug property]] {{cd\|SHAPES}} is enabled, indicated by a dark gray outline.

			{{IN\|BE}}, some entities attempt to resolve collisions when a solid collision box intersects their collision box. The procedure is as follows for each block that is found intersecting the entity's collision box.
			#The entity chooses to move along a cardinal axis by the shortest amount necessary to resolve the collision with the current block only.
			#The entity checks if its new position is free of additional solid collision boxes.
			#If the space is free, the entity moves to the new position. If the entity is a falling block, it will always move to the new position. Else, the entity aborts the movement.
			#If the space is occupied, the entity will no longer be affected by this mechanic for the remainder of its lifetime.

	=== Interaction box ===		=== Interaction box ===
Line 401:		Line 407:
	However, some blocks have an auxiliary interaction box. This auxiliary box is not used to actually interact with the block, but rather to calculate the direction of the interaction.		However, some blocks have an auxiliary interaction box. This auxiliary box is not used to actually interact with the block, but rather to calculate the direction of the interaction.

	For example, if the first face encountered of some element in a block's interaction box is the ~~top~~ face, but before that the ~~top~~ face of an auxiliary interaction box was encountered, it considers that the clicked face was the ~~top~~ face. However, if the interaction occurs with the auxiliary interaction box, but not with the block's interaction box, it is considered that no interaction took place.		For example, if the first face encountered of some element in a block's interaction box is not the up face, but before that the up face of an auxiliary interaction box was encountered, it considers that the clicked face was the up face. However, if the interaction occurs with the auxiliary interaction box, but not with the block's interaction box, it is considered that no interaction took place.

	The auxiliary interaction box only changes the direction of the interaction, not its position.		The auxiliary interaction box only changes the direction of the interaction, not its position.
Line 584:		Line 590:
	=== ''Java Edition'' ===		=== ''Java Edition'' ===
	==== Block hitboxes ====		==== Block hitboxes ====
	{{info needed section\|{{bug\|MC-1635}}, {{bug\|MC-73302}}, {{bug\|MC-1720}}, and b1.9pre2: did the wireframe also change?}}		{{info needed section\|
			* {{bug\|MC-1635}}, {{bug\|MC-73302}}, {{bug\|MC-1720}}, and b1.9pre2: did the wireframe also change?
			* when did auxillary hitboxes become a thing?}}

	{{HistoryTable		{{HistoryTable

SyncBot: Sync: updated from Minecraft

2026-07-12T11:10:12Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:10, 12 July 2026
Line 453:		Line 453:
	{{IN\|JE}}, it is possible to see the auxiliary interaction box when the [[Minecraft:debug property]] {{cd\|SHAPES}} is enabled, indicated by a blue outline.		{{IN\|JE}}, it is possible to see the auxiliary interaction box when the [[Minecraft:debug property]] {{cd\|SHAPES}} is enabled, indicated by a blue outline.

	When an interaction occurs inside an interaction box or an auxiliary interaction box, the position and direction of the interaction are no longer calculated according to the first point encountered. Instead, the direction is considered dependent on the angle of the player's vision, and the position depends on the initial position of the interaction (the player's eye). Specifically, an interaction is considered inside a box if a point 0.001×{{cd\|[[Minecraft:interaction_range\|block_interaction_range]]}} blocks in the direction of the interaction is inside the box. However, the auxiliary interaction box in these cases still does not define the final position (this is still defined by the interaction box). That is, interacting with a block inside an auxiliary interaction box, the direction will be calculated by the angle, but the position will still depend on the interaction box.		When an interaction occurs inside an interaction box or an auxiliary interaction box, the position and direction of the interaction are no longer calculated according to the first point encountered. Instead, the direction is considered dependent on the angle of the player's vision, and the position depends on the initial position of the interaction (the player's eye). Specifically, an interaction is considered inside a box if a point 0.001×{{cd\|[[Minecraft:interaction_range\|block_interaction_range]]}} blocks in the direction of the interaction is inside the box, the interaction position is also that point. However, the auxiliary interaction box in these cases still does not define the final interaction position (this is still defined by the interaction box). That is, interacting with a block inside an auxiliary interaction box, the direction will be calculated by the angle, but the position will still depend on the interaction box.

	=== Blocks visual box ===		=== Blocks visual box ===

SyncBot: Sync: updated from Minecraft

2026-07-11T11:06:25Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:06, 11 July 2026
Line 1:		Line 1:
			{{Missing information\|List of interaction boxes for the blocks.}}<!--Perhaps this list could be made on another page; in any case, it would be important to at least have the link to this list here.-->

	[[File:Zombie chasing villager with hitboxes.png\|thumb\|right\|A [[zombie]] chasing a [[Minecraft:villager]] with their hitboxes visible by using {{Keys\|F3 + B}} debug hotkey.]]		[[File:Zombie chasing villager with hitboxes.png\|thumb\|right\|A [[zombie]] chasing a [[Minecraft:villager]] with their hitboxes visible by using {{Keys\|F3 + B}} debug hotkey.]]

Line 400:		Line 402:

	For example, if the first face encountered of some element in a block's interaction box is the top face, but before that the top face of an auxiliary interaction box was encountered, it considers that the clicked face was the top face. However, if the interaction occurs with the auxiliary interaction box, but not with the block's interaction box, it is considered that no interaction took place.		For example, if the first face encountered of some element in a block's interaction box is the top face, but before that the top face of an auxiliary interaction box was encountered, it considers that the clicked face was the top face. However, if the interaction occurs with the auxiliary interaction box, but not with the block's interaction box, it is considered that no interaction took place.

			The auxiliary interaction box only changes the direction of the interaction, not its position.

	{{IN\|JE}}, there are 7 blocks with auxiliary interaction box:		{{IN\|JE}}, there are 7 blocks with auxiliary interaction box:
Line 448:		Line 452:

	{{IN\|JE}}, it is possible to see the auxiliary interaction box when the [[Minecraft:debug property]] {{cd\|SHAPES}} is enabled, indicated by a blue outline.		{{IN\|JE}}, it is possible to see the auxiliary interaction box when the [[Minecraft:debug property]] {{cd\|SHAPES}} is enabled, indicated by a blue outline.

			When an interaction occurs inside an interaction box or an auxiliary interaction box, the position and direction of the interaction are no longer calculated according to the first point encountered. Instead, the direction is considered dependent on the angle of the player's vision, and the position depends on the initial position of the interaction (the player's eye). Specifically, an interaction is considered inside a box if a point 0.001×{{cd\|[[Minecraft:interaction_range\|block_interaction_range]]}} blocks in the direction of the interaction is inside the box. However, the auxiliary interaction box in these cases still does not define the final position (this is still defined by the interaction box). That is, interacting with a block inside an auxiliary interaction box, the direction will be calculated by the angle, but the position will still depend on the interaction box.

	=== Blocks visual box ===		=== Blocks visual box ===

SyncBot: Sync: updated from Minecraft

2026-07-08T11:09:23Z

Sync: updated from Minecraft

@@ Line 392: / Line 392: @@
 Incorrect. It could collide with the glass!
 -->
 === Blocks visual box ===

← Older revision		Revision as of 11:09, 20 September 2026
Line 1:		Line 1:
	{{Missing information\|List of interaction boxes for the blocks.}}<!--Perhaps this list could be made on another page; in any case, it would be important to at least have the link to this list here.-->		{{Missing information\|List of interaction boxes for the blocks.}}<!--Perhaps this list could be made on another page; in any case, it would be important to at least have the link to this list here.-->

	[[File:Zombie chasing villager with hitboxes.png\|thumb\|right\|A [[zombie]] chasing a [[Minecraft:villager]] with their hitboxes visible by using the "entity_hitboxes" [[Minecraft:debug renderer]].]]		[[File:Zombie chasing villager with hitboxes.png\|thumb\|right\|A [[zombie]] chasing a [[Minecraft:villager]] with their hitboxes visible by using the "entity_hitboxes" [[Minecraft:debug renderer]]]]

	A '''hitbox''' defines the physical boundary (or an approximation thereof) of a [[Minecraft:block]] or [[Minecraft:entity]]. Hitboxes are used in the calculations of collisions and targeting.		A '''hitbox''' defines the physical boundary (or an approximation thereof) of a [[Minecraft:block]] or [[Minecraft:entity]]. Hitboxes are used in the calculations of collisions and targeting.
Line 674:		Line 674:
	=== Screenshots ===		=== Screenshots ===
	<gallery>		<gallery>
	Ender dragon green hitboxes.png\|[[Minecraft:~~Ender~~ dragon]] has nine distinct hitboxes.		Ender dragon green hitboxes.png\|The [[Minecraft:ender dragon]] has nine distinct hitboxes.
	Wither hitbox.png\|Wither heads don't have a hitbox of their own.		Wither hitbox.png\|Wither heads don't have a hitbox of their own.
	Player hitbox while gliding using elytra.png\|[[Minecraft:Player]]s' small hitbox while [[Minecraft:gliding]] using an elytra.		Player hitbox while gliding using elytra.png\|[[Minecraft:Player]]s' small hitbox while [[Minecraft:gliding]] using an elytra
	Sheep upside down hitbox.png\|Sheep ~~has~~ the same hitboxes despite being [[Minecraft:Name_Tag#Easter_eggs\|upside down]].		Sheep upside down hitbox.png\|Sheep have the same hitboxes despite being [[Minecraft:Name_Tag#Easter_eggs\|upside down]].
	Items having entity hitboxes.png\|Items also have entity hitboxes.		Items having entity hitboxes.png\|Items also have entity hitboxes.
	Item frames and painting having entity hitboxes.png\|Pseudo-blocks like item frame and painting have entity hitboxes.		Item frames and painting having entity hitboxes.png\|Pseudo-blocks like the item frame and painting have entity hitboxes.
	</gallery>		</gallery>

← Older revision		Revision as of 11:05, 27 July 2026
Line 43:		Line 43:
	\|class=nomobile}}		\|class=nomobile}}
	<div class="mobileonly">[[File:Fences_hitboxes_height.png\|thumb\|[[Fence]]s have a one block tall interaction box, but with 1.5 blocks tall collision box.]]</div>		<div class="mobileonly">[[File:Fences_hitboxes_height.png\|thumb\|[[Fence]]s have a one block tall interaction box, but with 1.5 blocks tall collision box.]]</div>
	The collision box manages a block's collision with entities~~. They are usually shaped in cubes~~, ~~but some may have different shapes~~, ~~like~~ [[Minecraft:~~slab~~]]s, [[Minecraft:~~lectern~~]]s, [[Minecraft:~~lily pad~~]]s, [[Minecraft:~~fence~~]]s, [[Minecraft:~~wall~~]]s, and [[Minecraft:~~stair~~]]s.		The collision box manages a block's collision with entities, blocked movements and other various effects, such as blocking line of sight in [[Minecraft:mob AI]].

			A collision box may not be present for all blocks; for example [[Minecraft:grass]], [[Minecraft:sign]], [[Minecraft:button]], [[Minecraft:lever]], and [[Minecraft:torch]] have no collision box.

	A collision box may not be present for all blocks; [[Minecraft:non-solid block]]s such as [[Minecraft:grass]], [[Minecraft:sign]], [[Minecraft:button]], [[Minecraft:lever]], and [[Minecraft:torch]] have no collision box.
	~~{{Collapse~~
	~~\|title=~~
	The list below shows all blocks defined as {{cd\|noCollision}} {{in\|JE}}{{Note\|This is not exactly a list of all blocks without collision. It's possible for a block to have no collision because it has an empty interaction box (e.g., [[Minecraft:light (block)\|light]]). It is also possible that blocks in the list have a collision box, in case the collision box was created later (e.g., [[Minecraft:scaffolding]] and [[Minecraft:Hanging Signs\|wall hanging signs]]). In the [[Minecraft:Tutorial:See Minecraft's code\|game's code]], these blocks are defined in the {{jcp\|net.minecraft.world.level.block.Blocks}} class.}}:		The list below shows all blocks defined as {{cd\|noCollision}} {{in\|JE}}{{Note\|This is not exactly a list of all blocks without collision. It's possible for a block to have no collision because it has an empty interaction box (e.g., [[Minecraft:light (block)\|light]]). It is also possible that blocks in the list have a collision box, in case the collision box was created later (e.g., [[Minecraft:scaffolding]] and [[Minecraft:Hanging Signs\|wall hanging signs]]). In the [[Minecraft:Tutorial:See Minecraft's code\|game's code]], these blocks are defined in the {{jcp\|net.minecraft.world.level.block.Blocks}} class.}}:
	\|~~content~~=~~{{flatlist~~\|		{{-}}
			{{columns-list\|colwidth=16em\|
	*{{BlockLink\|Activator Rail}}		*{{BlockLink\|Activator Rail}}
	*{{BlockLink\|Air}}		*{{BlockLink\|Air}}
Line 165:		Line 165:
	*{{BlockLink\|Wither Rose}}		*{{BlockLink\|Wither Rose}}
	}}		}}
	}}

	~~While most blocks have their~~ collision box ~~identical~~ to ~~their~~ interaction box{{Note\|~~The interaction box is considered with an empty context.~~ Thus, for example, [[Minecraft:light (block)\|light]] will always have an empty collision box, even when the entity is holding the light item. However, ~~[[Minecraft:~~block states]] are still considered}} or an empty ~~collision box if it is a non-solid block~~, some may have a different collision box compared to their interaction box counterpart. For instance, a [[Minecraft:lectern]]'s collision box does not extend into the upper part of their interaction box, and a [[Minecraft:fence]]'s collision box is a bit taller than their interaction box. The table below shows all the exceptions {{in\|JE}}:{{note\|In the table, trios like 1×2×3 represent a box in the shape of a cuboid with 1 pixel in X, 2 pixels in Y, and 3 pixels in Z. If the note column is empty, the center of XZ-plane is the same as the center of the block and starts at the base. For example, 16×16×16 is a full block.}}		The collision box of a block can vary depending on the [[Minecraft:block states]], [[Minecraft:block entity]], or context. By default, the collision box is equal to the interaction box with an empty context{{Note\|Thus, for example, [[Minecraft:light (block)\|light]] will always have an empty collision box, even when the entity is holding the light item. However, block states and entity are still considered}}, or empty for the blocks mentioned above, however some blocks may have a different collision box compared to their interaction box counterpart.

			The table below shows all the exceptions {{in\|JE}}:{{note\|In the table, trios like 1×2×3 represent a box in the shape of a cuboid with 1 pixel in X, 2 pixels in Y, and 3 pixels in Z. If the note column is empty, the center of XZ-plane is the same as the center of the block and starts at the base. For example, 16×16×16 is a full block.}}
	{{Clear}}		{{Clear}}
	{\| class="wikitable sortable ~~collapsed~~ collapsible"		{\| class="wikitable sortable collapsible"
	!Block !! Collision box		!Block !! Collision box
	!Interaction box		!Interaction box
Line 381:		Line 382:
	=== Interaction box ===		=== Interaction box ===
	<!-- [[Minecraft:Interaction box]] redirects here. -->		<!-- [[Minecraft:Interaction box]] redirects here. -->
			{{info needed section\|
			* Adding information using the interaction box can change depending on the context. For example, light and scaffolding
			<!-- These two are the only ones that change when holding the item. But maybe there are more that change in other contexts; there are more than 100 classes that define the shape ('interaction box'). Save mistake, I saw them all a while ago and there weren't any left, but I'm not sure - Aloi4-->
			}}
	[[File:Barrier_Outline_Box_(held).png\|thumb\|200px\|A [[barrier]] block's interaction box is shown when hovered by the [[Minecraft:crosshair]].]]		[[File:Barrier_Outline_Box_(held).png\|thumb\|200px\|A [[barrier]] block's interaction box is shown when hovered by the [[Minecraft:crosshair]].]]
	The interaction box manages block interactions with [[Minecraft:players]], such as block placement, destruction, {{control\|use}} actions, etc. When looking at the given block, the interaction box is shown as a black outline around the block's edges; this is especially visible in the [[Minecraft:barrier]] block. The interaction box appears only if the block the player is looking at is inside of the [[Minecraft:interaction range]].		The interaction box manages block interactions with [[Minecraft:players]], such as block placement, destruction, {{control\|use}} actions, etc. When looking at the given block, the interaction box is shown as a black outline around the block's edges; this is especially visible in the [[Minecraft:barrier]] block. The interaction box appears only if the block the player is looking at is inside of the [[Minecraft:interaction range]].
Line 400:		Line 405:
	Incorrect. It could collide with the glass!		Incorrect. It could collide with the glass!
	-->		-->
	{{Missing information\|section=1\|section\|Mechanics {{In\|BE}}, this section was based on {{JE}} code.}}		{{Missing information\|section=1\|section\|
			* Mechanics {{In\|BE}}, this section was based on {{JE}} code.
			* Describe how lily pads, frogspawn and spawn eggs work when targeting water - it doesn't seem to be an interaction box based thing, so there could be a valuable distinction to make here}}
	=== Auxiliary interaction box ===		=== Auxiliary interaction box ===

Line 461:		Line 468:
	When an interaction occurs inside an interaction box or an auxiliary interaction box, the position and direction of the interaction are no longer calculated according to the first point encountered. Instead, the direction is considered dependent on the angle of the player's vision, and the position depends on the initial position of the interaction (the player's eye). Specifically, an interaction is considered inside a box if a point 0.001×{{cd\|[[Minecraft:interaction_range\|block_interaction_range]]}} blocks in the direction of the interaction is inside the box, the interaction position is also that point. However, the auxiliary interaction box in these cases still does not define the final interaction position (this is still defined by the interaction box). That is, interacting with a block inside an auxiliary interaction box, the direction will be calculated by the angle, but the position will still depend on the interaction box.		When an interaction occurs inside an interaction box or an auxiliary interaction box, the position and direction of the interaction are no longer calculated according to the first point encountered. Instead, the direction is considered dependent on the angle of the player's vision, and the position depends on the initial position of the interaction (the player's eye). Specifically, an interaction is considered inside a box if a point 0.001×{{cd\|[[Minecraft:interaction_range\|block_interaction_range]]}} blocks in the direction of the interaction is inside the box, the interaction position is also that point. However, the auxiliary interaction box in these cases still does not define the final interaction position (this is still defined by the interaction box). That is, interacting with a block inside an auxiliary interaction box, the direction will be calculated by the angle, but the position will still depend on the interaction box.

	=== ~~Blocks~~ visual box ===		=== Block visual box ===

	In most instances where ''Minecraft'' uses [[Minecraft:w:line_clipping\|line clipping]] for detection, it utilizes the collision box or the interaction box of the blocks. For example, when a player tries to interact with a block, the game draws a line from it to the [[Minecraft:interaction range]] and looks for the first block whose interaction box the line intersects with. In the case of movement, the game draws a line in the direction of movement to find the first collision box to limit movement instead of crossing it.		In most instances where ''Minecraft'' uses [[Minecraft:w:line_clipping\|line clipping]] for detection, it utilizes the collision box or the interaction box of the blocks. For example, when a player tries to interact with a block, the game draws a line from it to the [[Minecraft:interaction range]] and looks for the first block whose interaction box the line intersects with. In the case of movement, the game draws a line in the direction of movement to find the first collision box to limit movement instead of crossing it.
Line 608:		Line 615:
	\|{{HistoryLine\|\|1.2\|The hitbox of cakes at far distances became greater than a full block.}}		\|{{HistoryLine\|\|1.2\|The hitbox of cakes at far distances became greater than a full block.}}
	\|{{HistoryLine\|java}}		\|{{HistoryLine\|java}}
	\|{{HistoryLine\|\|?\|[[Minecraft:Stairs]] cannot be targeted at angles where the crosshair does not point at a solid feature of the block. However, the wireframe outline still displays as a full cube regardless.}}
	~~\|{{HistoryLine\|\|?\|The hitboxes for randomly misaligned blocks such as tall grass are now themselves randomly offset as well to accommodate them.}}~~
	\|{{HistoryLine\|\|1.0.0\|dev=Beta 1.9 Prerelease 2\|[[Minecraft:Fence]]s no longer have a full block hitbox on the xz plane, and instead more closely match their shape.}}		\|{{HistoryLine\|\|1.0.0\|dev=Beta 1.9 Prerelease 2\|[[Minecraft:Fence]]s no longer have a full block hitbox on the xz plane, and instead more closely match their shape.}}
	\|{{HistoryLine\|\|1.1\|dev=12w01a\|The [[Minecraft:fence gate]] hitbox has changed to match the changes made to fence hitboxes.}}		\|{{HistoryLine\|\|1.1\|dev=12w01a\|The [[Minecraft:fence gate]] hitbox has changed to match the changes made to fence hitboxes.}}
			\|{{HistoryLine\|\|1.3.1\|dev=12w23a\|[[Minecraft:Stairs]] cannot be targeted at angles where the crosshair does not point at a solid feature of the block. However, the wireframe outline still displays as a full cube regardless.}}
	\|{{HistoryLine\|\|1.4.4\|dev=1.4.3\|[[Minecraft:Wall]]s now have their own collision box size - previously they shared their size with fences.<ref>{{bug\|MC-1332\|\|\|Fixed}}</ref>		\|{{HistoryLine\|\|1.4.4\|dev=1.4.3\|[[Minecraft:Wall]]s now have their own collision box size - previously they shared their size with fences.<ref>{{bug\|MC-1332\|\|\|Fixed}}</ref>
	\|The above change also fixed [[Minecraft:Java Edition distance effects#Fences, fence gates and walls\|a bug causing their hitboxes to distort and stop working correctly at far distances from the world origin]].}}		\|The above change also fixed [[Minecraft:Java Edition distance effects#Fences, fence gates and walls\|a bug causing their hitboxes to distort and stop working correctly at far distances from the world origin]].}}
Line 622:		Line 628:
	\|{{HistoryLine\|\|\|dev=15w49b\|The hitbox height of the [[Minecraft:end portal block]] has been increased from {{frac\|1\|16}} of a block to {{frac\|3\|4}} of a block.}}		\|{{HistoryLine\|\|\|dev=15w49b\|The hitbox height of the [[Minecraft:end portal block]] has been increased from {{frac\|1\|16}} of a block to {{frac\|3\|4}} of a block.}}
	\|{{HistoryLine\|\|1.11\|dev=16w35a\|Cake's hitbox now appears at the right position again.<ref>{{bug\|MC-106300\|\|\|Fixed}}</ref>}}		\|{{HistoryLine\|\|1.11\|dev=16w35a\|Cake's hitbox now appears at the right position again.<ref>{{bug\|MC-106300\|\|\|Fixed}}</ref>}}
			\|{{HistoryLine\|\|\|dev=16w36a\|The hitboxes for randomly misaligned blocks such as flowers are now themselves randomly offset as well to accommodate them.}}
	\|{{HistoryLine\|\|1.13\|dev=17w47a\|The hitbox of [[Minecraft:brewing stand]]s now takes into account the central rod as well.<ref>{{bug\|MC-4504\|\|\|Fixed}}</ref>{{verify\|is this actually an entity collision thing?}}		\|{{HistoryLine\|\|1.13\|dev=17w47a\|The hitbox of [[Minecraft:brewing stand]]s now takes into account the central rod as well.<ref>{{bug\|MC-4504\|\|\|Fixed}}</ref>{{verify\|is this actually an entity collision thing?}}
	\|The collision box of [[Minecraft:wall]]s has been made to be correctly concave.<ref>{{bug\|MC-2666\|\|\|Fixed}}</ref>{{verify\|is this also an entity collision thing?}}\|The outline boxes of [[Minecraft:anvil]]s and [[Minecraft:hopper]]s now much more closely fit the model shape of these blocks.		\|The collision box of [[Minecraft:wall]]s has been made to be correctly concave.<ref>{{bug\|MC-2666\|\|\|Fixed}}</ref>{{verify\|is this also an entity collision thing?}}\|The outline boxes of [[Minecraft:anvil]]s and [[Minecraft:hopper]]s now much more closely fit the model shape of these blocks.