Portals not placing the player at correct coordinates causing them to take suffocation damage

This might be more along the lines of the over world nether portal transporting the player to the wrong location. I entered an existing portal in the overworld at -608,65,-813 and my coordinates upon entering the nether were exactly the same.

Yup Richard is right, portal puts you out at the same co-ords instead of dividing/multiplying by 8.

Can confirm. For some reason the portal brings you to the exact coordinates of the original portal, completely bypassing the divide by 8 rule.

EDIT: Can also confirm for singleplayer.

Can confirm for an existing multiplayer world. Recreating the portal does not fix the problem.

However, I tried to reproduce it in singleplayer with a new world and there everything seemed to work as intended.
Edit: Newly created worlds are affected, too. See Daniel Melby's comment

I just ran into this bug in Singleplayer, and it seems to be doing this in survival, but not creative.

It's exactly the same for me Daniel Melby

same on multiplayer server, not only are nether portals gone, so is everything , it is like nether is reset, nether hubs, storage systems fortresses, all gone, rail lines, tunneled to correct coords as it portaled me to diff y coord, and nothing, like nether is reset

it is however same coords in nether as overworld, so could be in totaly different area

vanilla survival multiplayer server latest snap

as reported in MC-89952 (and I can confirm this for my multiplayer world), End portals are affected, too.

My experience on vanilla multiplayer 15w41b:
When you enter a nether portal (din't test end portals), you are initially teleprted to the correct location in the nether, in my case a linked portal. However, after the portal animation finished you are teleprted to the same coordinates as you entered, wthout any division/multiplication by 8, for example. This causes pretty much all nether portals to be unusable as the player will often spwan in a wall, above a high drop or above lava, and die. Similar problems exist when going back inot the overworld as the coordinates are not multiplied by 8.

Example:
Overworld portal at 800, 80, 800
Expected nether portal at about 100, 80, 100
Actual portal at exactly 800, 80, 800

You're probably right. I'll resolve it the other way since this ticket has gained a lot more attention.

@redstone helper... thanks, deleted that comment... here's the additional detail I was placing on that one:

I found this (w/ end portals) in 3 successive worlds... (and naturally generated end gateway detail below as well)

does not happen in creative, only in survival

in each, i created an end portal within ~ 10 blocks of spawn, went into survival and hopped in...
the first consistantly sent me to -457 70 522 (out in the middle of the void... )
the second consistantly sent me to --2 75 -18 (in the air around the starting end fountain/exit portal)
the third consistantly sent me to -100 49 0 (in the air above the obsidian platform... enough to take about half my hearts in fall damage)

I found if i went in creative first I'd start on the platform and be teleported to the above coords

I also found end gateways (the single block ones embedded in bedrock) are similarly bugged, upon retrun to the main island, the one i tested placed you inside the bedrock gateway, meaning you could only escape in creative... otherwise you'd take a tick of damage and be returned to the other end

Works OK in Game mode 1

Portals not working, exisiting or new Nether or End portals do not place the player in the correct place in the realm.

Effects all game modes that can tarverse the portal.

Server running Centos with 41b, Clients on Windows 7 & 10 and Mac effected.

As Ian above,

Windows & Mac clients, CentOs Server on 41b.

Both End and Nether Portals do not place correctly.

All game modes affected.

Confirmed in 41b, portals are borked. Seems division by 8 is broken, math has failed us again.

In old save portals in nether and overworld still exist where they were, but now send me to same XYZ as the realm I am leaving, rather than factor in for the smaller size of the nether.

Created a new world, and created a portal at X:0 - Z:0 in the over, and the portal was created in the nether at the same location as excepted, and I was teleported to it but on top of the portal.
Created a second portal in the overworld at X:1600 - Z:0, a portal was correctly created in the nether at X:200 - Z:0 but I was teleported to X:1600 - Z:0.
Also tested at overworld X:0 - Z:1600 creating a portal at nether X:0 - Z:200, and also at overworld X:1600 - Z:1600 creating a portal at nether X:200 - Z:200. both portals created in the correct location for portal spawning rules.

Seems that portal creation is still functioning correctly but is not changing the players XYZ as intended.

Running 41b

Please use the "view function" before saving an edit. There is 17 people watching this ticket, all of them getting emails for every small edit.

Updated the bug report for more clarify and fitting descriptions.

My greatest apologies for e-mail spams for all of you, I had no idea and my e-mail is pretty full as well ;_;

I'm so glad i haven't gone into my nether/end portal.

Can confirm, in my server you now spawn in air when going trough the portal, previously you'd spawn at a portal, located ~200 blocks from there

The wierdest thing for me is that when I was still inside the portal, before the nausea ended, I was at the nether hub and could see it. But after it tped me into netherrack a few hundred blocks away.

I think the issue is the new anti-cheating mechanism sees that the player has moved farther than it thinks they should have in such a short time and moves the player back to where it thinks they should be. I too have seen short glimpses of my nether hub before being teleported into the middle of nowhere, which happens to match my previous overworld coordinates.

I think I have more light to shed on the situation.

I believe the server IS correctly doing the division by eight, but then it immediately teleports you to the coordinates you had in the overworld. When I go through the portal I can see my nether hub for a split second before being teleported 1000 meters away over lava. I think this is a result of the new player position stuffs I've heard about. Could it be possible that packets are arriving out of order and the client is still getting overworld updates after switching dimensions?

How to reproduce: go through a portal from the overworld to the nether, if the distance is great enough you should see a few frames of the correct location flash before your eyes before being relocated. I can make a video if you can't reproduce it.

Tick 1
Player location: 8000, 70, 8000
(goes through portal)
Tick 2
1000, 70, 1000 (in nether)
Tick 3
Server sees player move thousands of blocks
And teleports them back to
8000, 70, 8000

That's what I think happens

I just confirmed that items and boats go through the portal and end up at the proper locations. Only players seem to be affected.

Just noticed the bug description was edited.. and I think it's going to lead them on a wild goose chase. Between us all I think we can all agree divide by eight works. A simple test of throwing blocks through a portal will show that they get to the other side. It's only players going through portals that have an issue, and it's not caused by miscalculation. Also, bob above is on to something with whats going on with the server.

I would change the description to, and i'm using bob's example:

A few ticks after entering or leaving the nether via a portal the player is yanked back to their previous dimensions coordinates while still in the new dimension. This leads to suffocation in walls or spawning in this air (over lava perhaps). Items and boats still arrive on the other side unaffected.

How to reproduce:
1) Enter a portal in the overworld (f3 shows 8000, 70, 8000)
2) After the nether loads for you, you will quickly see the correct location flash before you eyes (f3 shows 1000, 70, 1000 correctly divided by 8)
3) A couple ticks later you will be teleported to your previous location, but you're still in the nether (f3 shows 8000, 70, 8000 again)
4) Death.

*Step 2 may happen so fast that you will need to attempt this a few times to see it.

Possible causes:

• anti-cheat detection isn't checking dims and doesn't like the distance traveled

• player location packets are out of sync and suddenly the client catches up

Hope this helps and sorry for the edits, I just really want the nether hub back and I had the time to do some tests 🙂

I really hope they don't make us wait until next Wednesday to fix this... 😞

i made a portal too but in another snapshot it was okay but now when i enter it i make me teleport to a strange place far from the original portal (it teleported me to lave and i lost my diamond stuff 😞)

an interesting thing we found, that fraction of a second where ya see the real coords ya can jump out, timing critical to proper coords, rarely works but on opposite trying to make portals and exit also the milisecond where the ow coords in nether match the 1/8 so farther out in ow jump out and are far away, i am a million out so actually was able to come out in ow overworld at 8 mill lol set a bed and works lol no one is playing much as this is the glitchiest snap yet , must be related to the boats and wings as they are effected in all 3 worlds maybe? i have nether hub, not working, i also have a sky rail at 125 minecart glitches and freezes, so ok ill jump on a horse, wont move lol, im wearing out a lot of boots, they still work!

good news is everythins still in nether that was built just cant get to it easily but end is totaly broken, materialized in endstone, tunneled up was on an out island, bridged out 5400 found massive city and ship, got wings yay!, afraid to use em, flew once, over water worked great, vid on blockheads oneearwille facebook page multiserver vanilla survival we running snaps i dont envy the staff fixing all this stuff, they must be working overtime on 1.9 and we all apreaciate the effort it is taking and look forward to the final product

Confirmed. I just fell into a nether lava lake on my survival world.

Same here. Built the portal stepped in. Next (after the usual wait when you first enter the nether) thing I'm dropping into the lava. Strangely I didn't die. I moved to the next shore and got out. My health went up and down in a chaotic way, like I was taking damage and healing at the same time. I barely survived, but now I'm stuck in the nether.

With the help of unmined (map tool) I found the portal. So, the portal is generated just the teleport is totally wrong. Same on the port back, I got to a totaly different location. Luckily a place I had explored before. But I got out way in the air and took a hefty hit from fall damage.

So, as others have already said, it must be the conversion between normal and nether coordinates that's bugged.

Can confirm for all three dimensions.
In my LAN world with my friend, when we went to the nether we wound up stuck in a wall. (we cheated by teleporting to the nether portal's proper coordinates - we had them from playing before so we wouldn't get lost.)
When we returned to the overworld sometimes we spawned in a forest far from home, but because we also recorded our home's coordinates we could get back home.
When we went to the end we spawned over the void and died several times. More cheating was required to get the end platform's coordinates so we could go there and beat the ender dragon.
Oddly, sometimes it worked properly by putting us properly next to a nether portal or on the obsidian platform, but more often it put us somewhere else. The other thing I noticed was, with our nether portal in the overworld, located at about coordinates -75 64 200, whenever it put us in the wrong place in the nether it was the same coordinates, -75 64 200, but in the nether. Same thing with the end - our end portal's coordinates are about -800 32 550, and that was where we wound up whenever it teleported us over the void. So I guess there's a problem with the coordinate conversion, as it is said in the bug report.
This is a very serious bug that must be fixed!

I can confirm for my two survival worlds. Ended up suffocating both times.
One is a new world for the snapshot, the other is an old one where I had already used a portal.
-
Okay, I've tested in creative mode now, and it seems to only reproduce in survival. I entered the same portal twice; once in creative and once in survival. In creative, the portal worked fine and I was teleported properly. I left the nether, switched gamemode, and tried again in survival, and THAT time I was sent to the exact same co-ords as the overworld.

Er... what exactly is this a duplicate of? Or was this accidental?

...yes...what is this duplicating? There are two issues listed as related, but neither of them describe this issue at all.

I would assume a mod was closing lots of tickets as dupes of this one and accidentally resolved this one as a dupe of itself.

Using "F3" and switching between spectator mode/ creative so I survive, it looks like the "new" portal is placed correctly in a safe area, but the player is being teleported to the destination it starts the search for a safe place. For example, if I step through a portal in overworld at 0 58 0, the new portal gets created at 9 45 -1 (correctly in a "safe" spot, a decent enough air pocket) but the player is STILL teleported to 0 58 0 in the nether, suffocating to death if not in creative.

As a workaround, I'm going to make my own air pocket and build a gate to see if that works.

(EDIT) Work-around confirmed. Build a gate, step through in creative, switch to spectator mode and F3 to see your 'intended' destination even if you are in a wall. Find a "safe" spot to go back to creative, work your way to the 'intended' destination, MAKE the air pocket and "safe" destination, make the gate, and it works properly. Destroying the "expected" gate it won't teleport you to is optional, of course.

Sorry, was an accident.

Happened to me in survival mode. Tried it a second time and it happened again. Both times when I tried this, I used the "creative mode workaround".

you are being transported to the nether but ther is no portal so yo are in netherack , just have a pick ready and start swinging and you will not suffocate, same in the end. this doesnt solve the problem but will keep you alive

i recieved an email and accidently deleted it from mojang asking me to hit f3 and some other keys to crash the server and then send in a screen capture of the results, im on a multiplayer and dont really want to crash the server also lost the info on how, block lag is also bad if you pillar up say 20 blocks then try to come down at about 5 from ground you get sent back up, see nothing where ya broke the blocks drop with no damage and back up and repeat, stuck in endless loop, this happened when i got my wings, blocked up 64 to the ship and on going down this happened. i did not want to try to fly an lose my wings so put em in a echest. did bed and fell onto a platform we made at spawn area in the end, died. went back in and got all my stuff cept the dragon head 😞 end is so broken, no health bar on dragon, no perch, on killin it no gateway, when going thru portal to end ended up in endstone, used pick, made hole survived an dug up, i was on an island 1k out lol, just commenting as 5k other people haver reported these issues, just sharing the fun

I attempted to force crash whilst in the nether portal but the crash didn't work until I was dead from lava when teleported into the wrong place in nether.

As others have observed being in creative mode in single player doesn't affect the portals, only survival mode.

And yes, it is the divide/multiply by 8 that isn't working for nether, you spawn at the same coords in the new dimension that you were at in the dimension you left. An overworld portal at 0, 0 teleports you correctly since the coords are almost the same in the nether.

My sense of it, it does create the portal in a "safe" location, it just puts you at the location where it STARTS looking, but the 1 to 8 ratio is still correctly done to the fault it PUTS you at that, rather than the "safe" location where a gate was created for you.

1) Create gate at 0 0.
2) Step through in creative mode.
3) Notice you are in netherrack or lava, or otherwise "bad" location, but 'safe' in creative, and at 0 0 in the Nether.
4) Switch to spectator.
5) Look around and you'll likely spot a gate in a "safe" location.
6) Go to the gate in the "safe" location while spectator.
7) Switch to creative and use the gate.
8) Find yourself at the 8/1 distance away from 0 0, 8 blocks for every block distant the "safe" gate in the Nether was... but NOT where you put the original gate you placed at 0 0, as you should be.

So gates are being created, and at "safe" locations. You just are not being PUT at the safe location created, or at an existing gate.

There is quite a comprehensive discussion of causes higher up this comment section; however the bug description is still quite misleading.

Fixed in 15w42a, at least in SSP.

It also seems fixed for MP in 15w42a as well 🙂

This is mostly fixed, with one problem. In 15w42a a member of my server went through Nether Portals okay, but upon entering the End Portal the first two times the same bug from the description happened. He recorded a video of it happening the second time:

https://www.youtube.com/watch?v=dLNwAex0cc4

After two other players went through the End Portal, though, he was able to step through without falling into the void.

@unknown that's another bug, that's unrelated to this one, it already existed in 1.8 too, I saw it get reported (I think)

@unknown: I'll try to locate it and post my comment there

@unknown If you can't find it, just create a new ticket, the cords are correct, the chunks just don't load sometimes (rarely)

Actually, if you watch the video, the coords are incorrect. They are off quite a ways. The player spawned in the End at the same coordinates he was in the overworld. That's why I commented here, as that's the symptom of this ticket's description.

I can confirm that this bug is still present for me in SMP in 15w42a when using an end portal. The exact same overworld coordinates carry over, resulting in the player falling into the void.

This bug is still occurring in 15w42a SMP, occasionally. I find that when my connection is slower (when uploading/downloading something outside of MC) it happens.

Sounds more like boat changes causing this than cheat detection then.

Can confirm definitely fixed in:
Single player for 42a

@@unknown & @unknown : Can you recreate that issue in a fresh 15w42a world with new placed portals ?

@@unknown : I haven't been able to recreate it since yesterday actually. It seems that it only happens in certain circumstances which I've been trying to replicate with no success. It has definitely happened twice, on "old" Nether portals in a world generated in a previous 1.9 snapshot. Will update with more information if it happens again.

Still effects SMP in 15w42a, occasionally.

I'll try to recreate the issue on a server, but so far I can't recreate the issue in single player. I did discover that it only affects me when in survival mode, and never in creative.

Reopening.

@@unknown: In a fresh 15w42a world ? If so, please provide game mode , seed and coordinates.

@@unknown: I didn't test fresh worlds and have no interest in doing it, but it definitely affects old worlds in 15w42a. The affected world can be downloaded at http://api.wurstmineberg.de/v2/world/wurstmineberg/backup/latest.tar.gz
It occasionally happens while entering the end. It also happened to @unknown as described in the comments to MC-90605 while entering and exiting the nether.

As long as that issue doesn't happen in 15w42a or newer worlds, this can remain fixed.

Has anyone experienced this in a world created in 1.8 stable? I don't have the means to test this, but would personally advocate for the issue being left reopened if that were the case.

@@unknown: So you're saying it is fixed in 15w42a although I have this bug in 15w42a since our world wasn't created in 15w42a? That's a funny definition of fixed.

@unknown: It's possible something a previous snapshot broke is causing this. If newer snapshots no longer break things the issue is fixed. It is unrealistic to support every world corruption issue caused by every snapshot. If you can reproduce this in a world created in a release version and not opened in any snapshots but 15w42a (or in a world created and only opened in 15w42a), we know the issue still exists within 15w42a - otherwise, previous snapshots could have caused it.

@redstonehelper On my server, the world was created in 15w31a (1st snapshot). Nether portals work ok, although we sometimes get some suffocation damage from spawning into the obsidian frame. But going to the End is broken. It transports us to the same coords as the overworld portal.

Your comment suggests our world is now definitely broken, and our only solution is a map reset and a complete startover? I totally don't agree. If it totally breaks older worlds, I wouldn't call it "fixed". Reverting the server to 15w40b fixes the issue, so I wouldn't call our world corrupted either since it works perfectly fine. I understand it "could" be corrupted somehow as I don't know all the internal mechanics but still... my verdict is 15w42a is still broken when it comes to End portals.

End Gateways seem to work fine.

@unknown: Snapshots/development versions are unsupported, you use them on your own risk. If they corrupt your world - tough luck, make sure it's reported and move on. Yes, I don't know if this issue is world specific or if something else is the cause, but as long as we don't get *definite confirmation that it isn't* we will not reopen it since a developer specifically went and fixed this bug. Bugs are valid if they

• occur in either the latest release version or the latest snapshot, and

• affect worlds created in either of these two versions that's not newer than the version of the bug itself

I hope this explains our reasoning more. If you're still experiencing this issue on a world created in 1.8.8 or 15w42a, which has never been opened in any other version and has not been downgraded through versions (15w42a->1.8.8 is unsupported, for example), we can reopen this ticket.

Snapshots will break your worlds. Do not use them for any production server. Never.

@redstonehelper Understood. I'll try to do some further testing.

@Kumasasa You cannot say never! My production server is actually a snapshot server. I understand all the risks involved, and I do regular backups too. I'm not complaining here, just reporting an existing issue! 😃 If I cannot reproduce the problem using a fresh new world created in 1.8.8 and reopened in 14w42a, then I'll consider it fixed. I'll push the testing!

End portal issue reproduction world, created on a 15w42a SMP vanilla server.

I was able to reproduce this End portal issue both in SMP and single player using the world I just attached. World created fresh on a new 15w42a vanilla server and tested in 15w42a vanilla client. I've put in a couple command blocks for convenience that teleport the player above the end portal and above the exit portal. Happens intermittently, maybe once every 5-10 times entering the end portal.

If you'd prefer to do this yourself, seed is 93819220 and end portal is at 803 45 105.

According to MC-90785, the reporter made the world in 15w42a and still experiences this issue.

Reopened once more.

I tried the seed given above and got the same results. When I first went to the End, the portal correctly put me on the island with the Ender Dragon. After I killed the dragon and went back to the overworld, I tried going back through the portal. This time it put me at the same coordinates in the End as I was in the overworld, and I fell in the void and died.

Replicated on a multiplayer world with seed 625279412075742952. It seems to depend on how you enter the portal. If instead of jumping in you try to run along the edge it puts you at the overworld coordinates.

@@unknown: I have found that the manner in which you enter the portal doesn't matter. The test world I attached to this issue exclusively drops the player directly into the middle of the portal and the issue happens just as frequently as when walking along the edge or walking straight in.

I think I found the exact steps to reproduce the issue for the end portal (in 15w43c):
-make a new creative world (superflat is the fastest)
-execute the command /setblock ~ ~ ~ minecraft:end_portal
-execute the command /gamemode s
-jump into the void (/kill does not work)
-go into the portal again. You will spawn in the void.
-now execute the command /gamemode c to go in creative mode
-go into the portal again and notice you will not be taken into the void in creative mode
Maybe this should be added to the description?

Also confirmed for 15w44a

I seem to be getting this error in the server log when this nether portal glitch happens to me.

Oct 31, 2015 4:01:59 PM io.netty.channel.AbstractChannelHandlerContext invokeExceptionCaught
WARNING: An exception was thrown by a user handler's exceptionCaught() method while handling the following exception:
java.io.IOException: Error while writev(...): Broken pipe
at io.netty.channel.epoll.Native.writevAddresses(Native Method)
at io.netty.channel.epoll.EpollSocketChannel.writeBytesMultiple(EpollSocketChannel.java:184)
at io.netty.channel.epoll.EpollSocketChannel.doWriteMultiple(EpollSocketChannel.java:364)
at io.netty.channel.epoll.EpollSocketChannel.doWrite(EpollSocketChannel.java:317)
at io.netty.channel.AbstractChannel$AbstractUnsafe.flush0(AbstractChannel.java:707)
at io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.epollOutReady(AbstractEpollChannel.java:248)
at io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.epollOutReady(EpollSocketChannel.java:623)
at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:322)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:264)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:745)

@James Pinckney According to the title the nether should be fixed..?

The title is wrong. It still affects nether portals.

No that is MC-90605 since 42a since the bug is now different with the looping.

Confirmed for 15w45a

When we are teleported from the Nether to the Overwold, it seems to teleport us first to the coordinates of the overwold's portal into the Nether.

Can confirm for 15w45a with end portals.

Can confirm this bug is still happening for nether portals in multiplayer in 15w45a.

I have a few portals at y=5 in the nether, coming through from the overworld would sometimes set me on fire, even though the area around the portals was clear.
Today i got disconnected when going to nether and ended up at the "overworld coordinates", but in the nether, inside a lava lake. That lava was probably setting me on fire before the teleport to the correct portal applied. That teleport didn't happen because of the disconnect, leaving me at those coordinates.

Confirmed for 15w45a with both Nether and END portals.

Confirmed for 15w46a

Confirmed in 15w46a, if you time out at the exact right moment (after the portal takes you out of the overworld and when it says Downloading), you end up at the overworld coordinates when you log back in.

Some players on my server have reached the world border and managed to crash the server by trying to go beyond the world border using this technique.

Hmm, should this issue be made private then?

No, it's too well known and people will keep reporting it anyway.

I think it fits the criteria of a private issue because new players on SMP can crash the server with minimal time and resources, but its not an instant process.

I also don't think it will actually help prevent maliciousness so there's no real point in marking this issue private.

Only issues present in release versions will be set to private, but not snapshot issues.

Affects 15w47a.

Also affects 15w47c

The bug may also frequently cause burning or temporary suffocation when entering Nether portal in multiplayer. I guess that the coordinate translation happens after switching dimension, and the suffocation/burning/falling happens between these two stages.

I attempted to access the End in my old survival 1.8 world where I'd already beaten the dragon, but I fell to my death in the void. Fortunately, I had cheats turned on and I discovered that the portal was now teleporting me several hundred blocks away from the end island. I had to use cheats to make an ugly causeway out to where the end portal was dropping me.

This bug makes the game virtually unplayable on a server. There is no way to break the cycle if there is no one around to help, and in certain cases you are not even teleported back to the correct coordinates, causing you to die and lose your items.

@Krist Pregracke

Why not make spawning platforms in the End at the location players and up, and place a pressure plate with a command block under it (which teleports the player to the proper location)?

May not be the ideal solution, but for a workaround I guess this is viable.

Also affects 15w50a

Just backup before going to the end...
That's what I did and I loaded it when I lost all my stuff.

NEVER seen it happen with nether (except in the 15w41a snapshot [or whatever the snapshot the elytra came out]), but very often with End portals... (about 30%). However, a lot of my portals are not taking me to portals after leaving the nether but making new ones within 100 blocks. My base portal glitched me 100 meters away, but the original portal in the nether was created by the game and not by me. Not sure if it's related...

I wish Dinnerbone would make it so portals were tileEntities and you could use /blockdata to control the output coordinates/dimension.

In 15w50a I have a nether portal setup, which causes suffocation damage when i'm teleporting to it

That is MC-90605

Affects 15w51b.

For what it's worth: We have a 15w51b server where entering the end often trigger this bug. Whenever the bug is triggered, the server log outputs "<player name> moved wrongly!" If the bug isn't triggered, the log message is instead something like "<player name> moved too quickly! 471.8518178045263,9.945106652967922,972.740300396834". (Our end portal in overworld is at -371, 38, -972, and the correct destination is 100, 50, 0 in the end.)

For geeky guys and the developing group: We have managed to provide a (possible) fix on 15w51b and would welcome every one of you to test for us.

The fix mainly changed the server action when the client's action(moving packet) is out of sync(the "moved wrongly" warning): previously the server place the player to the last valid position, now the server will place the player to the current valid place without processing the rest "useless" codes.

After some tests I am pretty optimistic about this version: it never place you at bad coordinates when you enter the end portal, and it does not affect other functionalities.

Also, for debug purpose, the server now prints a lot more debug info than before... In case you have any feedback plz attach the relevant info.

Thank Fang Zhang for providing many comments on my work ;p

Finally the link: https://drive.google.com/file/d/0B-0F4Ex2w5muX2RGU0hzaHFHWDQ/view?usp=sharing

@JimmyZJX

For the very 1st time in 10 weeks, the end portal placed me on the right spot! Is your fix only for the End portals? Nether portals have that issue too, just less consistently.

Anyhow, very well done, thank you!

@Early Reflections
Thank you for the early feedback!
On our server we are quite lucky and have not observed any Nether portal failure. If you are lucky enough to experience that once more, please (if possible) shutdown all the clients and send me the last-minute log, we will try to find out the problem.

@JimmyZJX

You're welcome!

I've never experienced that issue with the nether portals myself. But a friend, who's ping is much higher, can't even use them. He's either placed at the last valid coords or keeps on playing ping pong between nether and overworld until he logs off. My ping is always around 80 to 90 ms. His can go from 100 to 250 ms.

I often take damage when exiting a portal too. As if, for a tick or two, the game places me at last valid coords (inside of blocks) then returns me to the valid coords inside the exit portal.

In any case, expect some feedback as soon as I see it happen. The next few days may not be too MC-focused though!

Happy holidays!

@JimmyZJX

Here's a log of the incident using your jar:
https://drive.google.com/file/d/0B-2DQ3g04GV0cExURThGLWZ5UXM/view?usp=sharing

For me the bug is extremely persistent—it's more rare that it doesn't happen.

EDIT: This is when I enter nether portals. This only seems to happen when I start in the nether and go from the nether to the overworld. It doesn't happen (or at least happens very rarely) when I enter the nether from the overworld.

Hi everyone! I have changed my modification. The newer version will not make the nether portal bugs more persistent, and keep you end portals working. Moreover, a dimension change packet hook is added, so the log will provide more information.

The link(minecraft_server.15w51b_b.jar): https://drive.google.com/file/d/0B-0F4Ex2w5mueWxPRXhCYmtTNTA/view?usp=sharing

Weird, I would think a major bug like this would have been squashed immediately, instead it has been allowed to fester for many, many snapshots. I haven't noticed the bug with the nether, but the end will still often spawn me in the void. I really hope this one is fixed ASAP as its very detrimental to the game.

@all: Please stop discussing here, this site is a bug tracker and not a discussion forum.
Any meta-discussion can be done at https://www.reddit.com/r/Mojira/

Affects 16w02a.

affects 16w02a cant even get the thing activated in a new gen world in its strong hold, tried in both creative and survival.

@MrJacen

What you describe is MC-95547.

Anybody able to reproduce in 16w03a?

@redstonehelper

Yes. My server's End portal still places me at the same coordinates as the overworld, right into the void.

Can't reproduce as it seems random but still happens in 16w03a.

Confirmed in 16w05b SMP

Affects 16w06a.

Confirmed for 06a for end portals but not for nether portals:
https://youtu.be/uMxmf5WnLi0
https://youtu.be/2goMs21Fm6k
Should I open a new ticket for the nether portal behaviour as it it no longer this OR MC-90605?

Should I open a new ticket for the nether portal behaviour as it it no longer this OR MC-90605?

What? You just confirmed this ticket.

Sorry watch the videos now that they have come through. Nether portals still deal one tick of suffocation/fire damage and cause a ton of server lag.

Actually, I'd warrant to say that MC-89928 is what was causing MC-90605 (that is now "fixed")... The fact that the game was teleporting you into the portal, then it teleports you to the location you were in the overworld again, and then back, was causing load time issues, and it also 'broke' the functionality that you couldn't teleport after you teleported into a portal frame (because technically you left it and came back).

This can be seen if you are standing on the otherside of the portal when someone teleports in. Say you are teleporting from 800 x 70 x 800 in the overworld to the Nether. At the nether portal at x=100 z = 100, they appear, disappear then reappear. If you are observing at 800 x 70 x 800 in the nether at the same time, you'll see the player appear and then disappear. This is also why people sometimes take suffocation or fire damage... if there is a block or lava at 800 x 70 x 800 in the nether, they'll take whatever damage from what blocks are in that location.

Yes, it is. In previous snapshots you could open F3 and see your coords change AFTER teleporting. This is shown in https://youtu.be/uMxmf5WnLi0 as when I remove the blocks around my overworld postion in the nether I do not take the 1 tick suffocation damage. However the end does not teleport the player back up onto the platform about 1/2 the time (https://youtu.be/2goMs21Fm6k) and I would guess this is because the player has started moving (falling) and this makes the cheat detection exit or something.

@bob The nether part of the problem should be fixed, but I couldn't reproduce the End problem. Do you have the map you used in the video ?

I've noticed on our server if you jump up into the end portal from below it places you at the wrong coordinates 95% of the time where if you jump from the top it's more like 50% Try jumping up from the bottom to recreate.

@ProfMobius: do you mean the nether issue "should be fixed in 16w07a" or "should be fixed in the next snapshot"? I definitely still take a tick of suffocation damage going through nether portals in 16w07a.

I also experience the fatal version of the problem every time I try to go to the End in my main world this snapshot. I could send my world if you want it, but it's over 600Mb so I'm not sure how helpful that is? I also took some screenshots if you want them, but I don't think they show anything that @bob's video doesn't cover better.

This is total wild speculation, but I wonder if it's a "happens on old/slow computers" issue? Loading a new dimension means the thread doing chunk loading is working really hard. Maybe if the computer is slow enough, the chunk loading is pulling so many resources that the threads that are supposed to be doing other things, like updating coordinates, don't run in time or get scheduled out of order. And that'd explain why it's hard for @ProfMobius to reproduce, since I'm sure Mojang developers don't do their coding on old slow laptops...

@ProfMobius

On my server, the problem is easily reproduced 100% of the times. I made a bedrock platform at the destination and a command block that teleports the player(s) to the right place. But my world is around 600 MB too. It would almost be easier for me to whitelist you on it if you wanna experience it.

@Martha
For me it's 100% of the times. But I always go through it from below.

@early reflections
You could use dinnerbones tool to find the region file and upload it. Just put the co-ords of the portal and it'll tell you which region file contains the block https://dinnerbone.com/minecraft/tools/coordinates/

@ProfMobius I still get the tick of suffocation damage going through a nether portal in 16w07b

@ProfMobius I think that the key factor is the server load: I could never reproduce this without another player present.

Uploaded as requested; not sure how useful this will be

I've not been able to get the End version of the bug to happen in 1.9-prerelease yet after trying several times, even though it was happening almost every time in 16w07a. Not sure if that means it's fixed or just that it depends on some other factor that's different.

On the other hand, the prerelease still consistently gives me the tick of suffocation damage going through the nether portal.

In the prerealease:
Nether: as before (1 tick damage & massive desync) going both ways.
End: Reproduced 1/about 10 times jumping from the top
Reprouced every time jumping up into the portal
Can confirm for both portals.
Edit: Reproduced without other players present on server
Edit 2: Also happens in singleplayer, along with EXTREME lag when changing dimensions. I put lava at the overworld coords of the portal in the nether, and died when going through.

As what @bob just stated above, you can reproduce the issue with the End portal by jumping UP into the portal from underneath it.

Portals are still very screwy and not ready for a full release yet.

In 06b on vanilla survival entering nether portal crashed server, in 07a and b it worked fine, in pre-release 1 it is crashing server again

I will have to go back to snap 07b untill resolved on our server

Using 06a, have same bug. Curiously, it's only affecting 1 out of 2 players on the server. The unaffected player is OP. Spawns player inside a solid hill. Upon hollowing out they appear midair and fall to their death.

This is on a survival multiplayer server running 1.9 pre-1 on Java 1.8 on Linux Ubuntu 15.10. I was able to reproduce the issue by logging on to the server and walking into the portal before the chunks generated entirely. The water stream in the end that I placed is always exactly where I spawn.

@Chris Chappell

Good news is the issue has been marked as "fixed in next upcoming snapshot (pre-release 2)".

Not fixed in pre-2, still taking damage.

Please test on a new world to be sure.

Tested on new world of course. This issue is definitely not fixed. Should I provide video proof or something?

not fixed in -pre2, just tried it

End portals now work as they should on my server. I still take damage going to the nether in some portals, but the world has been created using 15w31a.

@redstonehelper
If I take damage in a world created in any official release (1.8, 1.7, 1.6 etc.), is it still an issue, or will 1.9 only support worlds created in 1.9? I ask this because I think it doesn't really matter what version you were using when creating a world. The math involved will be the exact same no matter what version created that world.

I take as an example Etho's Let's Play series. He created his current world using Beta 1.9 Pre-release 2, four and a half years ago. His portals have been working flawlessly for that whole time, in every releases and snapshots. If his portals cause him damage in 1.9, he's doomed to live with it because his world has been created in a pre-release, even though they've been working fine all that time?

Only worlds that have never been opened in a development release are supported. Some bugs do depend on the world so sometimes we ask for reproduction on new worlds. This is probably not one of those bugs but I want to make sure before reopening it.

Well, to be clear, here is what I am seeing. I have not reliably witnessed the aforementioned behavior where the player starts out at 'overworld coordinates' in the nether before moving to 'portal coordinates' (divided by 8), and taking damage as a result of being at those wrong coordinates.

What I am still seeing is taking suffocation damage as a result of going thru a portal into the nether in multiplayer (both server and LAN). That might simply be a result of the more general latency bug where any time a player is teleported anywhere, the client sees them 'falling' until the chunks get loaded, and thus they end up glitching into the floor (and taking suffocation damage) as a result.

Since you seem to be able to reproduce this reliably: Please see if clearing out the area around the overworld coordinates in the nether stop you from taking that one tick of damage.

Interestingly, when reproing this on -pre2 on a LAN world, I take suffocation damage only when the second player is in the nether there to witness me arriving. When the second player is at spawn in the overworld, I don't take damage. And I never take damage returning to the overworld. This is very reliable. I'm going to upload a tiny test world in case it helps.

A small world I am using for LAN testing of taking damage going to the Nether. When one (creative) player is in the nether, and another (survival) player (LAN host) goes from overworld to nether, the survival player always takes suffocation damage on arrival in my tests.

@redstonehelper - yes, I tried clearing the overworld-coordinates area in the nether (as well as filling it with lava and obsidian) in an attempt to reproduce the not-yet-divided-by-8-or-change-coordinates-or-whatever issue, and was not able to reproduce that in -pre2 (which is to say, none of clear/lava/obsidian affected my results). (I have not tried to repro in earnest on earlier releases.)

This bug was actually covering 2 issues.

1 - Suffocation damage when teleporting to the Nether

2 - Getting way off target when teleporting to the End.

Can we confirm that 2 is fixed ?

@redstonehelper

That does make a lot of sense. Thanks!

@ProfMobius
For me, #2 is fixed. But I suggest waiting for confirmation from others too!

@ProfMobius

#2 does indeed seem to be fixed, not able to reproduce.
Jumping up into the portal from below which previously sent you into the void every time, now takes you to the platform as intended.

Thank You!

Working fine for us now with pre - 2 although I'd like to know if the full release will generate new structures like igloos and the 128 end portals without resetting the map if not how can we get around this without a full world map reset our server has been running for 2 years last 6 months on snapshots

Yes, but only in not yet generated chunks

They are all generated

So I'm looking at a total map reset?

All 3000000*3000000 blocks have been generated? If not, then there is no need

I can confirm that, as outlined by @unknown:

1. Suffocation damage is not fixed. I receive anywhere between no damage and 5 hearts each time I enter the Nether.

2. The position bug that up until 1.9-pre1 affected both Nether and End portals, which consistently caused fire damage with a specific Nether portal and occasionally misplaced players entering the End, appears to be fixed.

@FVbico

World border is at 30,000,000 from 0, 0. Thus the world size is 60,000,000 x 60,000,000! 😛

Oops, ug, I'm so stupid sometimes, missing a 0 and had to so times 2, ah still close for not looking it up

I tested all portals nether and the end extensively alone and with people on our multi-server no problems whatsoever now thank you so far pre2 is great for that issue

Yes we are at 30 million by 30 million and no not that far out they haven't but the 128 end portals will only go out to 25000 and that area has been heavily traveled in the last 2 years I did find a couple igloos and they had no basements

I wonder if there is a better place to discuss this, as it has nothing to do with the bug at hand. Some people get emailed each time a comment is made on this post and it can get annoying.

I can't reproduce #2 (wrong coordinates going to the End) in -pre2, but I couldn't reproduce it in -pre1 either, so take that with a grain of salt.

#1 (tick of suffocation damage going to the Nether) is still reliably happening in -pre2.

Someone please create a separate, new ticket for #2 and link it in the comments here. Please also try to keep discussion to a minimum. Thank you.

Done
MC-97523
(sorry if I'm too late)
Maybe link this issue above to help direct people with more information?

We opened a new bug report Grum. Do you want us to keep using this one then?

Is this still happening in pre release 2? For you? We had the same problem on the multiplayer server and in single worlds but was cleared up many snapshots ago

Yes

Attached are a series of six screenshots taken in 1.9-pre2. As you can see from the filenames, they were taken in quick succession. Based on this evidence I actually don't think this bug has anything to do with coordinates any more, because the nether screenshots have the correct nether coordinates immediately. But as you can see, I still take damage (between .39 and .41) while waiting for the chunk to load.

Summary:
If there is a wall or lava at the location of a nether portal, but in the other dimension, then the player takes at least one tick of suffocation/fire/lava contact damage, dpending on the block on the other side. This is accompanied by massive server lag / desync in MP and massive frame lag in SP.

e.g.
Overworld portal at (100,64,100)
Lava at (100, 64, 100) in nether
Corresponding nether portal at (12,64,12)
Stone at (12, 65, 12) in overworld (one higher: player head)

Overworld ==> Nether:
Contact lava/fire damage
Nether ==> Overworld:
Suffocation damage

Video (pre-2):
https://youtu.be/5yhF9-tWCPc

@Stuart Actually, if you have another person observing the location of the portal in the opposite dimension, you sometimes will see that person appear. This has not changed.

Here is a video in Pre-1, but these results are reproducable in Pre-2. My server just happens to be on Pre-1, and it was easier to setup my camera account on the server, and it outlines the following:

-Taking damage while inside of a block or lava is NOT the bug. This is the EFFECT of the bug.
-This bug is the CAUSE of all of the damage bugs.
-I go on to show live what happens when a person teleports while this is happening.

https://youtu.be/YwFuABAtcBI

Ultimately, this bug is the one that needs to be fixed.

@James Koon thanks for the footage, it explains a lot. I agree that tackling the cause of the bug might be a more effective strategy to fix it , but just confirming that the bug is there is also a help to the devs. Also this bug report is open.

@@unknown: Thanks for recording that video, I'm afraid it's of little use since you recorded it in 1.9-pre1 - the coordinates bug was fixed in 1.9-pre2.

Fair enough. I'll see if I can prove or disprove this tomorrow.

@redstonehelper: Hi, here is a new video proving the exact thing still happens in 1.9-pre2. The exact same procedure was implemented. If you want I can record in a fresh world, but I was having a problem with my camera account connecting for some odd reason on an Open to LAN session from the same computer.

https://youtu.be/n9hZgJDO9TA

@redstonehelper according to my understanding of these bugs, if this is tracking Bug 3, it should be resolved as it is non-existent.

We'll see how grum handles it on monday. Great video proof on the other ticket!

Bug is back

Bug never left.

Yes also have this. Take damage or get suffocated in a wall whenever I return from nether to overworld in my test world.

Can confirm for 1.9 pre-3 in a clean world in MP, going both directions. Mods: If you need video then say.

Not understanding how the dev's aren't understanding the issue here. Something about the anticheat movement measure is temporarily teleporting people back to their overworld coordinates when going to the nether, and vice-versa if going to the overworld. All of the other bug fixes have been fixing the effect, not the cause. Fixing this would have resolved the damage issue, looping issue and wrong coordinate issue, and probably any other issue with the portals in the game... Not trying to be mean here, but I don't understand how they're not getting the cause and why this wasn't fixed in 15w43+. Sorry, just getting frustrated here repeating myself over and over.

Stop marking this as fixed when it isn't fixed. At this point, don't change the status to "fixed" until the community feedback indicates your efforts have been successful, since it's very clear that efforts to fix the issue are not fundamentally addressing the problem at hand.

@unknown it just indicates they try to fix it, and over 99% of the times, it's actually fixed then

@FVbico Eh, I'd say more like 80%.

you do know what I'm saying, it'd be more work to close all as fixed, then to reopen unsuccesfull fixes

I don't think it's quite the same as this bug (which is why I reported it separately), but MC-97725 is similar to the End Portal version of this, in that it's another "travel through a portal, immediately drop into the void and die and lose all your stuff unrecoverably" scenario...

@FVbico If I counted correctly, this issue has been reopened at least five times.

If an issue is opened, fixed, and closed once, you're right--the odds are high that it's been fixed.

After reopening an issue 2-3 times, though, it should be obvious that the process is flawed; at that point, you simply have to admit, "We don't actually know if this is fixed or not; can you tell us?"

with only 2 attempts being a fix...

Updated the bug report with Pre-3, error is still occurring.

Ultimately, I do believe this bug is in fact being caused by the anti-cheat system saying you moved to fast. Subsequent bug fixes since 15w42a have only been bug fixing the effects of this bug, not the cause.

youtu.be/2GG7bk-Hnqo?a

Would love to be able to test this with a console open but alas I cannot at this time without running a server off of my computer... is "Player moved too fast" errors still occurring during nether transports?

That hasn't appeared since pre 2, but I'd guess they removed the debug message.

Confirmed for 1.9pre3, several times took suffocation damage when heading back to the overworld in multiplayer.

It seems as if they added invulnerability on dimension change in Pre4. This is a work around, and IMO just lazy & sloppy programming due to the following reasons:

1 - It will still generate chunks in the nether far from the origin of the map. For example: Teleporting at 4000 70 4000 in the overworld would load 500 70 500 in the nether without this bug. However, this bug effectively generates chunks that may never be visited in the nether, at 4000 70 4000.

2 - It increases server load. Using the previous example, the fact that when you teleport from 4000 70 4000 in the over world to 500 70 500 in the nether, the chunks at 4000 70 4000 as well as 500 70 500 must load in the nether due to this bug. One person doing this at a time isn't a big issue, but if you have numerous people going through the nether on a multiplayer server, it has the potential to increase overall load on the server quite significantly. If this is also happening in the end, it's even worse.

3 - You can still catch fire while invulnerable. You then proceed to take damage afterwards.

Here is the video I took of Single Player opened to LAN on Pre-4 (my server isn't updated yet). It shows clearly that you are still teleported to the overworld equivalent coordinates, due to the setup I used this time.

https://youtu.be/w0sv2ZvQJ_k

EDIT: I did additional testing by running a server. Each time you go through the portal, the console states "darthkoonstyle moved too quickly!"... assuming now that if the Anti-Cheat system were set to ignore dimension shifts, this bug might disappear entirely.

The Pre4 fix may just be a temporary workaround to avoid blocking the 1.9 release on Monday. That would give them more time to investigate and test a proper fix, as I imagine this is fairly complicated code. I'm guessing the intention here, but that's what I would do in their place.

@James Koon

This "player x moved too quickly" thing is definitely the anti-cheat system kicking in. In my base I have several Speed 2 beacons and I get this message in the console all the time, just by running around my base. I get lots of rubberbanding too, because of this. I also get it A LOT when riding a horse under Speed 2 (like every second). With the Elytra, it simply makes us stop moving. The anti-cheat system seems to be causing more harm than good at this point and I would strongly suggest disabling it altogether for the release, unless, of course, it's not too intertwined with the rest of the codebase, which it probably is!

@Matthew Barnes

I'm 99.9% sure it's a temporary workaround.

@Early Reflections @Matthew Barnes

Even if it is temporary, you're still able to catch fire, which can lead to death after the invulnerability ends.

Either way, I'm pretty sure that they tweaked something with the anti-cheat in 15w40-15w41 era, and that tweak is the culprit here. If they disabled the anti-cheat system, it would probably be a bad thing for release, as modded clients would allow for crazy speeds and teleporting for non-opped players.

If the invulnerablility has been added, this bug should be marked as resolved. Instead, a new bug should be opened detailing the various effects of the broken anti-cheat system (rubberbanding with speed, portals briefly loading wrong chunks, portals setting you on fire and so forth).

@unknown: Go ahead.

While I agree with the opening a new ticket, the invulnerability does not negate all damage... if you catch fire in the portal, you'll continue to take damage.

Although it might make sense to keep this issue open because you can still take damage, the issue has changed a lot and we now have a much better understanding of it. Grouping issues by cause rather than effect may make the bugs be fixed more quickly.

Edit: See MC-98153

Hello - This is having an issue in Version 1.9 full release, where the portals located at: 311 66 137 (Facing South) overworld will take you to: 25 98 34 (Facing East) - nether to return you to: 198 72 274 overworld. - (Facing West)

It can also place the nether portal in mid-air, or ontop (both) of trees (overworld)

Server: 1.9 Vanilla Server - Multiplayer

This is not about the placement of portals, but of players. Portals in the air are no bug.

@Eddie Bingham Also, beyond what Fabian mentioned, the behavior you indicated is not a bug. If you want to resolve your issue, make new portals at the correct coordinates. Portals attempt to place in the nether at x/8 y z/8, and from the nether to overworld x*8 y z*8, as long as that place is not obstructed.

311 66 137 (Over) to Nether is 38 66 17. If this area is obstructed by netherrack or lava, it attempts to place you close to land.

25 98 34 (Nether) to Overworld is 200 98 272, which is only a couple blocks off from your reported 198 72 274. (98 is adjusted to land level)

If you want your overworld portal to connect to the 38 66 17, go there, dig it out or place a platform, build a new portal and light it. It will link properly.

I'd like to see whether what just happened to me is a result of this bug. I went to the End for the first time since the 1.9 update, mostly to check on my End base and to see if I could start exploring outwards to find End cities. I've taken the trip dozens of times in 1.8 and had no issues. As soon as I go through the portal, I start suffocating, and within seconds I die from "falling off the world", taking all of my Mending-equipped diamond gear with it. Lovely. Well, I took the trip again, figuring the whole thing was bugged and I'd have to reset my End spawn point or something, but no, this time I teleported on top of the obsidian platform as expected.

Has anyone else experienced this problem with only the first trip to the End causing issues, and would it be related to this bug?

This bug also affects end portals, so yes, it is the same bug. One question though: Did you see the block you were suffocating in or was the screen just black? Because if it was just black then it might have been void damage, not suffocation.

Interesting. I thought this issue had been fixed. This is not in a fresh 1.9 world though (I'm not sure how that is important but the mods were adamant about this before).

Yeah, if the problem resides in how old the world is, that could likely be the cause of my issue. This is a bit of a franken-world that started out as a 1.7 multiplayer world, then was transferred to single player since 1.8. The seed was reset in the process, which I had to later go back in and edit, and delete the mismatching chunks as I was doing that. That said, I do have a Nether portal network with many linked portals traveling thousands of blocks, and that worked perfectly as soon as I tried it in 1.9. Not sure why the End portal gave me issues.

Technically I guess I would have been taking void damage, since I was literally dead within 2 seconds; I tried pulling out some ender pearls I had brought to throw myself back up to the mainland, but I didn't even see it (looking down I suppose). The damage was so quick, and it was also silent strangely, unless it was simply drowned out by the reintroduced "portal exit noise". I know the noises for void damage are working, since I was thrown off quite a few times later by Endermen while trying to bridge out to End cities.

You didn't see the mainland because you were teleported to the exact coords you entered the portal at in the overworld. We can say this bug is confirmed for 1.9.

While I don't typically use mapping applications and the like, thinking them to be a bit unfair for regular survival gameplay, I decided to investigate my save with Chunky to see if what you're talking about is what happened. In the Overworld, the End Portal that I use to go to the End is roughly located at around X = -1040 and Z = -60. When looking at the End, at around X = -1040 and Z = -60, there is a square of terrain perfectly generated around that area, showing that I have been there. However, it's not connected to the rest of the End that I have actually explored. I guess that does confirm that the bug is happening in release 1.9. I added a picture to show this. (You can also see my failed attempts to bridge out afterwards.) It seems to mostly match what the other commenters and pictures demonstrated, but it appears that this bug used to happen on every entrance into the End. It only happened to me on the first go.

That kind of makes me sad, knowing that there was a slim chance I could have survived it, had I fallen into some sort of cave in one of the islands or something. 😞

I haven't had this in any of the 1.9.3 pres; I have only seen MC-98153 so far. Is this now fixed with the removal of a lot of lag sources?

Is this still an issue in 1.9.3-pre2?

I thinks it's a direct result of MC-98153. Should be "blocked by", as I learned recently. 😉

Unable to reproduce in 1.8.3 pre-2, but have only used end portal once.

All the "catch fire when entering the nether" bugs are marked as dups of this one.

In 1.9.4 I still catch fire and take damage when entering the nether through unlucky portals.

Please see MC-98153

What are we awaiting the response to? This bug changed in the 1.9.x versions and is now different and covered in other reports.

You're right.

The bug is still present in 1.10.2

you may be able to recreate the bug by killing the minecraft instance while in the portal. i consistently experience the bug, if my instance crashes while in the portal.

Could not find more recent non-duplicate version of bug report.

Can confirm bug is still active in Bedrock edition, and can happen in Realms.  Recently entered a portal at -320, 70, -2  The corresponding exit in the nether is at -40, 70, 0.  However I found myself somewhere around -300, 45, 0.  I was on an island surrounded by lava, not suffocating in a wall.  I do not know exact location as I was surprised and walked around a bit before taking notes, I was eating some food while waiting for portal to activate.

After dying I reentered portal and ended up at correct location, so did confirm exit still existed and was also not able to reproduce.

@@unknown Bedrock issues go here: https://bugs.mojang.com/projects/MCPE