Entity hitbox in vehicle does not become shortened
When any entity (including a player) rides a vehicle, its hitbox has still the same size. This is mostly problematic for boats and minecarts as there you would be able to attack a player from underneath a boot or as seen here a player could get "for no reason" damage.
Linked Issues
is duplicated by12
relates to15
- Unresolved
Marcono1234- 42
- 14
- Confirmed
Normal
- Platform
- Entities Hitboxes
- hitbox rider vehicle
1.8.6 - 1.21.4
1.8.6 15w42a 16w04a 16w07b 1.9 1.10.2 16w35a 16w42a 16w43a 1.11.2 17w17b 1.12.1 1.12.2 17w45b 18w03b 1.13 18w30b 18w31a 1.13.1 1.13.2 19w05a 19w06a 19w07a 1.14.4 19w37a 19w45b 1.16-pre3 1.16.3 1.16.4 20w45a 20w46a 20w51a 21w03a 1.16.5 21w05a 21w05b 21w06a 21w07a 21w13a 21w15a 21w17a 21w18a 1.17 1.17.1 1.18 1.18.1-rc1 1.18.1 1.18.2 1.19 1.19.1-pre2 1.19.2 22w42a 1.19.3 23w06a 1.20 1.20.1-rc1 1.20.1 23w31a 1.20.3-rc1 1.20.4 24w05b 24w07a 1.20.6 1.21-pre1 1.21 1.21.1 1.21.4
Created Issue:
Entity hitbox in vehicle does not become shortened
relates to
is duplicated by
relates to
relates to
is duplicated by
relates to
relates to
is duplicated by
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
relates to
relates to
is duplicated by
is duplicated by
MC-272682
relates to
Damaging is hitbox based and very likely MC-80877
Duplicate of MC-80877. Please use the search function next time.
Might be caused by MC-80877
Thank you for your report!
We're actually already tracking this issue in MC-80877, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-80877, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Relates to MC-80877
There is a video linked on this bug MC-80877. Does it or the ticket describe your issue?
Relates to MC-80877
Duplicate of MC-80877.
Please search next time before creating a ticket
Testing the fix to MC-207258
Relates to MC-80877 MC-208597
If you ride a minecart on a rail over wool the sculk sensor is not able to detect it.
If you place a minecart on a rail over wool the sculk sensor is able to detect it.
If you ride a minecart on a rail not over wool the sculk sensor is able to detect it.
If you place a minecart on a rail not over wool the sculk sensor is able to detect it.
Entities which walk over wool, in this case drive, are not supposed to be detected. Although there is a rail between the minecart and the wool. The different results in each case suggest one of the first two scenarios is not correct.
This report is a duplicate of MC-80877.
This is caused by your hitbox not being shortened whilst riding a mount, therefore making this a duplicate of MC-80877.
Thank you for your report!
We're tracking this issue in MC-80877, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Potentially a duplicate of MC-80877.
Thank you for your report!
We're tracking this issue in MC-80877, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Would it be okay to request a review of this ticket since similar reports regarding how entity hitboxes don't correctly correspond with their models are considered issues? (MC-142848, MC-195133, MC-212565, MC-208015, MC-198242, MC-148559, MC-119372, MC-80877, etc...) It does seem rather strange that the wither's shoulder heads aren't included within their hitboxes and since similar behavior with other entities is considered to be valid problems, maybe this should be reconsidered? ![]()
I can confirm this behavior in 1.18.2 and 1.19 Pre-release 4. It's important to note that this issue can be seen with any ageable mob and isn't just exclusive to villagers. Here's a code analysis regarding this issue.
Code Analysis:
The following is based on a decompiled version of Minecraft 1.19 Pre-release 4 using Mojang mappings.
public class SpawnEggItem extends Item { ... public Optional<Mob> spawnOffspringFromSpawnEgg(Player player, Mob mob, EntityType<? extends Mob> entityType, ServerLevel serverLevel, Vec3 vec3, ItemStack itemStack) { ... Mob mob2 = mob instanceof AgeableMob ? ((AgeableMob)mob).getBreedOffspring(serverLevel, (AgeableMob)mob) : entityType.create(serverLevel); ... mob2.setBaby(true); ... mob2.moveTo(vec3.x(), vec3.y(), vec3.z(), 0.0f, 0.0f); ...
If we look at the above class, we can see that when a spawn egg is used on an ageable mob, the new baby entity is spawned at the parent's location. This is evident through the following line of code:
mob2.moveTo(vec3.x(), vec3.y(), vec3.z(), 0.0f, 0.0f);
When a given entity is in a boat, its hitbox isn't shortened (MC-80877) and because of this, it penetrates the bottom of the boat. Since an entity's position in the world is determined by the bottom center of its hitbox, this results in the newly summoned baby entity being placed at its parent's position (which is too low down when they're inside boats) resulting in them sinking through and suffocating in the ground when summoned.
This ticket is a duplicate of MC-80877. The zombie's hitbox should become shortened when riding an entity, but it doesn't, therefore resulting in it overlapping the allay's hitbox.
Thank you for your report!
We're tracking this issue in MC-80877, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Maybe fixing MC-80877 would partly fix this problem?
Confirmed. I think pufferfish are intentionally designed to attack a given entity that is within a certain distance of them, however, I don't call the shots on what is or isn't intentional though; that's Mojang's decision.
This can also be reproduced with normal boats and isn't just exclusive to chest boats so I've updated this ticket accordingly. This may also be a product of MC-80877.
Duplicate of MC-80877.
Thank you for your report!
We're tracking this issue in MC-80877, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
This issue now very much relates to/is caused by MC-80877.
Thank you for your report!
We're tracking this issue in MC-80877, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
I suppose this may be caused by MC-80877.
Dupe of MC-80877.


Confirmed for 16w07b
Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.
This is an automated comment on any open or reopened issue with out-of-date affected versions.
Can confirm for MC 1.12.1.
Can confirm for 18w30b.
Affects 18w31a. Better steps to reproduce: Sit in a Minecart, press F3+B, then F5 and teleport the minecart up: "/tp @e[type=minecraft:minecart] ~ ~20 ~"
The Player Hitbox changes when flying or swimming, so this Issue should be attended too.
Confirmed for 1.13.1.
Confirmed for 19w37a.
Confirmed for 1.16 pre-release 3
In 1.16.4 and 20w46a
Can confirm in 21w03a.
Can confirm in 21w05a.
Can confirm in 21w05b.
Can confirm in 21w06a.
Can confirm in 21w07a. Video attached.
Can confirm in 21w11a.
Can confirm in 21w13a.
Can confirm in 21w15a.
Can confirm in 21w18a.
Affects 1.17
Can confirm in 1.17.1.
Can confirm in 1.18.
Can confirm in 1.18.1.
Can confirm in 1.18.2.
Can confirm in 1.19.
Can confirm in 1.19.2.
Can confirm in 22w42a
1.19.3.
Affects 1.20.1 Release Candidate 1