Horses can suffocate when going through nether portals
Everytime I push a horse through a nether portal and it comes to the other dimension, it suffocate in obsidian or in surrounding blocks. Sometime, I can't get out of it an dies.
Note that this may actually be three bugs:
- Horses can suffocate from walls because they are partially teleported into them
- Players can push horses into the obsidian wall after portal teleport
- Horse size is not accounted for when placing horse inside the portal (
MC-121098)
This ticket only describes the first two bugs, which should be properly tested and split into two tickets at some point.
Linked Issues
is duplicated by6
MC-97868horses die when traveling through Nether PortalsDuplicateMC-116939Horse takes damage from nether portal frameDuplicateMC-166314Entities with big hitbox often die in portalsDuplicateMC-173224horses suffocate when going into nether portal DuplicateMC-214929Donkey with chest full of items traveled through portal, suffocated, died, left no itemsDuplicateMC-250230Horse suffocated when going through a nether portal MC-250228Duplicaterelates to5
MC-262114Block with complex collisions around an exit nether portal cause more lag than blocks with simple collisions when entities go through them
NormalMC-92729Horses spawn in blocks during world generation, causing them to suffocateAwaiting ResponseMC-121098Entering a tall portal that takes you to a short portal from the top causes you to take suffocation damageFixedMC-262115 Large hitbox mobs having inconsistent exit position and can suffocate in surrounding blocks depending on some factorsNormalMC-13734Horses - Killed With Nether PortalDuplicate
ImportantCreated Issue:
Horse suffocate when going through nether portals
Everytime I push a horse through a nether portal and it comes to the other dimension, it suffocate in obsidian or in surrounding blocks. Sometime, I can't get out of it an dies.
is duplicated by
is duplicated by
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Everytime I push a horse through a nether portal and it comes to the other dimension, it suffocate in obsidian or in surrounding blocks. Sometime, I can't get out of it an dies.
Note that this may actually be three bugs:
- Horses can suffocate from walls because they are partially teleported into them
- Players can push horses into the obsidian wall after portal teleport
- Horse size is not accounted for when placing horse inside the portal (
MC-121098)This ticket only describes the first two bugs, which should be properly tested and split into two tickets at some point.
relates to
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
Horses can suffocate when going through nether portals
is duplicated by
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
is duplicated by
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
BROKEN.jpg
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
is duplicated by
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
![[Mojang] MNilsson](../../../data/avatars/users/18951.svg){kind=small}
[Mojang] MNilsson![[Bot] Piston](../../../data/avatars/users/31202.png){kind=small}
relates to
Thank you for your report!
However, this issue has been closed as a Duplicate of MC-80032.
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-80032, 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
It seems to have been fixed with some portal changes in 20w28a, along with MC-80032.
Thank you for your report!
We're tracking this issue in MC-80032, 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
Thank you for your report!
MC-80032 is my issue. Fuond it.
Thank you for your report!
We're tracking this issue in MC-80032, 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.
When an entity goes through a nether portal, it checks blocks in a large radius around the exit position for collisions and offsets trying to avoid suffocation. This process of collision checking cause variable amount of lag depending on how complex the collision model of the blocks around the portal are. Blocks with complex collisions (like cauldron, hopper, closed fence gates, composters, etc), cause way more lag than simple blocks (like stone, glass, etc).
This complex collision checking was introduced in 22w45a seemingly a fix for MC-80032.
Steps to reproduce:
- Make a 3x3 portal in overworld
- Go through this portal and extend the nether portal on the nether side to a 3x3 instead of a 2x3
- Place a repeating command block to kill the non player entities
- kill @e[type=!player,distance=..16]
- Make a 6x6x6 cube using cauldrons sandwiching the portal (See nether screenshot)
- Go back to overworld and place a repeating command block under the portal with
- summon ravager ~ ~2 ~
- Activate the this command block.
- Profile the lag.
- Repeat the same with simple collision block (stone or glass) or blocks with no collision (open fence gates)
Observeration:
- Complex collision blocks cause far more lag than simple blocks
- All this lag is caused by the collision resolution part of code which was introduced in 22w45a
Large hitbox mobs having inconsistent exit position and can suffocate in surrounding blocks depending on entry portal size, exit portal size and blocks around exit portal.
Seemingly bug fix for MC-80032, the collision resolution code introduced in 22w45a to prevent entities from suffocating in walls has inconsistent behavior and mobs end up suffocating when they shouldn't.
Screenshots were taken in 2 different worlds exit portal in both of them in exact replica while entry portal varies. This causes horses, donkeys, ravagers to suffocate in one instance while not in the other one.
Horse survives in crimson forest nether but not in lava lake nether.
Related to MC-262114
When an entity arrives in a portal, there is a collision check to try to ensure that the entity doesn't collide with any blocks (to avoid issues like MC-80032). However, the collision check only accounts for blocks in adjacent chunks if those chunks are already loaded. As a result, entities with a larger-than-1x1 hitbox will sometimes clip into blocks when they arrive in a portal, if the portal happens to be located next to a chunk boundary.
To reproduce:
1. Construct a 3x3 nether portal in the overworld where the four corner portal blocks (the portal blocks themselves, not the obsidian) are at the following coordinates: (3200, 129, 3199), (3200, 129, 3201), (3200, 131, 3199) (3200, 131, 3201)
2. Construct a 2x3 nether portal in the nether where the four corner portal blocks are at the following coordinates: (400, 129, 400), (400, 129, 401), (400, 131, 400), (400, 131, 401)
3. Place 4 solid blocks surrounding the 3x3 nether portal in the overworld, at the following locations: (3199, 129, 3199), (3199, 129, 3201), (3201, 129, 3199), (3201, 129, 3201).
4. Go to the nether.
5. Throw a snowball through the portal. Then within 15 seconds, spawn a boat in the portal by running the following command:
/execute in minecraft:the_nether run summon minecraft:oak_chest_boat 401.68 129.00 400.69 {Rotation: [180.0f, 0.0f]}
6. Go back to the overworld. Note that the boat has appeared on top of the blocks, within the portal.
7. Break the boat. Return to the nether, and wait at least 15 seconds to ensure that the overworld chunks are unloaded.
8. Run the same command as before, but this time, don't throw a snowball through the portal first.
9. Go back to the overworld. Note that the boat is now at the bottom level of the portal, and its hitbox is overlapping with the blocks.
In other words, if the overworld chunks are already loaded when the boat arrives, then the boat will be correctly placed. If the overworld chunks aren't already loaded when the boat arrives, the boat will collide with the blocks around the portal.
Expected behavior: When the boat appears on the overworld side of the portal, it shouldn't collide with blocks if other places to spawn are available. Since the arriving entity itself loads the overworld chunks, it's surprising that the behavior would depend on whether those chunks were previously loaded before the entity arrived.
This seems similar to MC-262115, but the issue doesn't only affect mobs, and it also seems to be specifically dependent on chunkloading. It's possible that the chunkloading-specific behavior described here is actually the root cause of the "inconsistent" behavior in MC-262115.
I've had this happen to both horses and villagers. I keep the walls set far back from the portals now to prevent them landing inside those, but that doesn't help with glitching into the obsidian of the portal frame itself.
It seems to happen more often when transporting multiple through at once (pushing each other into the blocks?) and/or when the portal they enter through is wider than the one they arrive at. Trying those together might increase the odds of reproducing it.
I'm fairly sure it's because when the nether chunk is loading when you step through, your hitbox pushes the horse into the frame of the portal. This should be impossible - perhaps it's because the horse loads before the surrounding terrain or the horse gets shifted because the game tries to avoid two entities taking up the same location. In any case, it sucks.
I can confirm that this bug has been present in 1.9 Pre 1, 1.9 Pre 2, and 1.9 Pre 3.
Steps to recreate:
1. Tame any horse or donkey.
2. Ride into Nether Portal
3. Dismount (Horse will teleport through portal)
4. Enter portal
5. Horse will be suffocating or dead nearly 100% of the time with traditional 2 wide x 3 high portals.
They appear within frame of portal. Happens both in Overworld > Nether, and Nether > Overworld portals.
6. Horses may still end up within portal frame for larger portals.
Confirmed in Minecraft 1.9 Pre-Release 4
confirmed for the 1.9 as downloaded today (02Mar). horses going through portal receive suffocation damage from the portal frames for the most part. i had this problem in both overworld and nether.
Confirmed in Minecraft 1.9.1-pre2
Created new 1.9.1-pre2 world, tested issue in both directions (Overworld <-> Nether). Horse "materializes" within side frame of portal and suffocates / dies.
This happens 100% of the time with standard portals (the 2 wide x 3 high type.)
Confirmed in latest release (1.9.2). This happens both when 1) you lead the horse through the portal with a lead, or 2) you ride the horse into the portal and then dismount to initiate transport of the horse. As near as I can tell, the horse's head seems to enter the obsidian after I travel through the portal following the horse - it seems to occur as a result of my knocking the horse out of the portal itself and into the portal frame. In 1.8.9 this does not happen - I seem to be able to co-ccupy the same space as the horse until it walks out of the portal.
This is a major bug, severely limiting the utility of horses/mules. One of the main reasons I have mules is to enable rapid transport of myself and materials through the Nether to various remote regions of my world! Under the current version, I must either build all new (larger) portals, or place mules outside every Nether transport station (like taxis) to handle local transport needs. Ugh!
Please, please, please figure out how to enable players to ride horses through Nether portals while mounted! This seems like an obvious feature that should have been built into the game since introducing horses into the game in the first place!
Confirmed for me too. This is really infuriating and has never been a problem for me previously. I've had a couple of horses killed by this now when I'm a large distance (through the Nether and Overworld) from anywhere with new horses to be tamed. It's a massive inconvenience and I would agree would be best improved by enabling passage through portals while mounted.
the same happened to me in 1.9.4 vanilla with an iron golem in std 2x3 portal. when you follow your critter through the portal you probably push its hitbox into obsidian
Confirmed in Minecraft 1.10.2.
Just recently happened to me in my survival world.
Confirmed in Minecraft 1.10 and 1.10.2.
Widening portals to 3 or 4 blocks wide lessened the chance that it would happen, but did not eliminate the problem. I generally dismount my horse and then push it into the portal, but have the same problem that the horse spawns on the other side stuck in the obsidian frame potentially dying from suffocation damage if not quickly mounted and moved away. In a related phenomena, I have also had a horse die of suffocation damage while swimming (alone and unmounted) in a small lake. The lake had a dirt overhang in one part and the horse swam under it and got stuck inside the block and suffocated to death. So this seems to be a reoccurring issue with horses and suffocation damage in blocks. I have noticed that the horse seems more likely to get stuck in the obsidian frame of a portal if it is moving while it teleports to the other side. It seems as though the horse keeps moving during transit and walks into a location that is then occupied by the obsidian block when the world loads. Perhaps an error in the movement code for horses?
Possible solutions:
1. Allow player and horse to enter portal together while mounted (may or may not fix error, depending on cause).
2. Remove suffocation damage in solid blocks. Suffocation damage almost always happens as a glitch of some sort. Damage taken from gravel or sand falling onto a player's/entity's location makes sense, or from entering low clearances while on a minecart maybe. But there have been reoccurring issues since beta minecraft of entities dying from block suffocation getting stuck in walls, corners, fences, etc. Furthermore mechanics while riding a horse under low clearance are implemented poorly, especially in jagged terrain. Even just slightly walking over a chest in a room with only a 3 block height will result in this "head" damage, and in caves a player can easily become hopelessly stuck in a wall taking damage with a black screen. It is incurred far to frequently and easily, and furthermore makes little sense. The horse mounted player should be stopped from entering the space rather than magically phasing his head inside a solid rock and then being hurt by it (or, you know, maybe add a head ducking animation). One must ask, for the preponderance of glitches, accidental mob/player deaths, and poorly designed mechanics, what is the purpose for taking damage in this way? The game, in theory, should never allow you or any other entity to phase inside of a solid block in survival mode in the first place, so why punish players because the game made an error?
Horse taking damage inside Obsidian frame after travelling through portal (Survival Server, although I was temporarily in Creative mode to spawn in a horse to sacrafic.)
Second picture show there was open space around the portal (and the same issue has occurred with much larger open spaces than shown here). It is less common with wider portals (i.e. 3x3 in place of standard 2x3) but can still occur. With standard sized portals it seems to occur the majority of the time.
Occurring in 1.11 official release.
Occurrence, every time.
Happens by horse contact with portal and on lead.
Horse appears stuck in obsidian on the side of the portal, quickly right clicking the horse to mount and jumping frees the horse, only if you are fast.
Mode: Survival
Older versions 1.8 and previous were run with the same nether portal configuration and never hit this issue. There was a falling through the blocks beneath the portal into lava (not fun) in pre-1.8 but not this suffocating condition.
I can confirm this with 1.11.2.
it even happens if you widen the portals on both sides, or if you change the orientation of one/both of the portals.
this is an EXTREMELY annoying bug since good horses are so hard to find/breed and there's seemingly no way to prevent it happening.
please, at the very least, ensure that the hose is oriented so its head is sticking OUT of the portal, and not into the portal block.
If I make the portal opening both in the nether and in the real world 5 blocks wide (blocks you can stand on) / 7x7 including the obsidian, and I make sure I am in the middle block (block 3) when I dismount my horse, it does arrive safely in the other dimension, as long as the destination portal is that same size.
I have an elaborate nether world full of portals, changing to this configuration took more hours than I care to admit.
Adjusting the offset when spawning the entity in the portal accounting for that entity width would fix the issue. Currently if the portals have different widths exit portal position may cause AABB to intersect with the Obsidian frame. Still even if mobs are placed in the middle of the portal, player can still push them into the obsidian somehow, but that's another story.
Yes. The glitch seems to be caused by player pushing horse. It's intended for horse to bump against obsidian, but collision check doesn't work. Why is that?
Confirmed in 1.12.2.
This is happening consistently and repeatably for me. I've done some testing with another player - whether pushing the horse into the nether, pulling them in with a lead, or just waiting for them to wander in of their own free will, this will happen.
It is also unaffected by whether a player is there on the other side or not - every time we tested this, the horse spawned inside the portal walls on the other side, even if no player was nearby or followed the horse through (I was watching from a distance on the other side as my accomplice sent the horse through the portal).
Still happening in 1.12.1. I used to bring horses through the nether all the time in 1.8 and before. Spent some time away from Minecraft and now, my first attempt to bring horses home, and even after making the portals all wider, I've had 4 deaths and only 1 successful transport – and that one was a very near miss; I was able to push him out of the portal with half a heart of health remaining! This is VERY frustrating, given how far you often need to transport horses to bring them home in the first place.
Confirmed for 1.13.1.
This still happens in both 1.13.2 and in the 1.14 snapshots. Being such an old bug it baffles me that there's still no response from devs.
Still happening in 1.14.1. It's very frustrating!
Still in 1.14.2 - genocide for the entire horse and donkey population?
[EDIT]:
Following a hunch, I just had a look at the hitboxes of horses and donkeys – they're massive!
No other mobs I've ever seen (well, except ravagers, which are a little bit bigger, and bosses) have such incredibly huge hitboxes in comparison to their body size, especially considering the hitboxes of cows or even iron golems, that look almost tiny… – and the hitboxes of donkeys are only marginally smaller than those of horses, even when donkeys are a little bit smaller than cows(?!?)
– No wonder horses suffocate at each opportunity, even when their bodies aren't really next to a wall; the trouble with hitboxes that don't turn according to the viewpoint, when an animal's body length is considerably bigger than its body width….
This is the bug that killed PewDiePie's horse.
https://youtu.be/YuihlgsgNSo?t=7m19s
Rip Joergen
Affects 1.16, 1.16.1 and 20w27a
Minecraft 1.16.2 - Singleplayer 2020-09-02 18-00-00.mp4
Cannot reproduce in 1.16.2
This bug seems to have been fixed with some portal changes in 20w28a, along with
MC-121098.Not true, I almost lost my horse yesterday in a portal in 1.16.3.
I probably tested it improperly, then. (I rode a horse into the corner of a portal, got off, and teleported; the horse wasn't inside of the portal frame nor did it get pushed in by me. But there possibly are other ways it could happen; can you elaborate on what happened to your horse?)
The portal I pushed it through had a wall on one side, which it then got stuck in.
Playing on 1.16.1 and I had this issue as well
My Neither Portal was surrounded by walls on all sides except for a 2x3 corridor going up to it. Horse goes in, horse suffocates on the other side.