Extremely similar to MC-98153. However in my instance when taking a portal from the overworld at coords -5/120/34 I end up in the Nether at or near -3/-3/-2 (The coordinates I'm sent to are just about directly below our actual portal in the Nether which is at -2/52/-2. I easily could have moved a tiny bit from X=-2 and I know I start falling immediately so I expect I'm actually arriving at -2/0/-2.). Upon arriving there's a sky of solid Bedrock above that the player begins falling away from at once, suffocating soon after. If the gamemode is set to Creative the player can punch through the Bedrock and if they fly directly upwards they are in the normal Nether chunk they expected to be at in the first place. In the server console I see the text "<player name> moved too quickly!" and right after the death message for that player is "<player name> fell out of the world."
Seed is -2466281547766755436. This world was created at version 1.9. This problem seems to have started somewhere around 1.9.4, potentially earlier. The only plugin in use on this server is PermissionsEx although the server itself is Spigot.
I checked per notes in MC-98153 and if I go in the Nether to the coordinates precisely corresponding to the Overworld coordinates of the starting nether portal there's nothing there but solid netherrack. However I do think it's significant that the player arrives at the same X and Z coordinates as their Nether Portal in the Nether but the Y value is far enough down that the player is basically outside of the game world.
This problem is rather severe as it basically renders all our existing Nether portals unusable.
Comments


Good question. I'm at work now and will give that a shot during lunch. I'll try and post back in a few hours when I can give it a go.

Invalid, modded server.

So as it happens I ran my server using the vanilla JAR. What happened is that while the problem with Nether Portals did not reproduce I also noted that my Nether world loads completely empty - none of the work that's been done in there was present.

That's just a difference in world saving between Spigot and vanilla JARs.

Gotcha. Well this looks to be something going on with Spigot, then, given that I can't reproduce it with the default JAR. I'll open a ticket with them. Thanks for the help!

FYI updating to the most recent release of Spigot 1.10 resolved this issue for me.
I guess the bug is different because you are running Spigot. Have you been able to reproduce with a vanilla server?