MC-74203Nether apoun second enter pushes100k + maybe more distance
basically if you create a portal enter it everything is fine
go back through and enter again , the location changes when you enter portal to go back your then pushed like 200k in overworld.
I dont understand how it works but i screenshot the process for you all to see
if you notice the cords you will see what i mean
this is also happening to everyone on server atm.
Environment
linux ubuntu 14, java 64 bit version 8
Created Issue:
Nether apoun second enter pushes100k + maybe more distance
basically if you create a portal enter it everything is fine
go back through and enter again , the location changes when you enter portal to go back your then pushed like 200k in overworld.I dont understand how it works but i screenshot the process for you all to see
if you notice the cords you will see what i meanthis is also happening to everyone on server atm.
Environment
linux ubuntu 14, java 64 bit version 8
Attachments6
@rodney cheney
Edit: I think you might want to add that you aren't creating the second portal, the game does this for you if I'm reading the bug correctly. I misread it the first time through.
So the bug is that the game spawns in the second portal in the wrong location in the nether.
WAI, try finding a guide on how to link your portals properly.
i do not think you understand correctly what is going on here
create portal x=-150110 y=63 z =-81045
enter portal nether cords are x=-18773 y=15 z=-10141
go back in everything is good
head back to nether
cords change to x=-2338 y=51 z=-1279 [WOW that is a big change]
enter portal to go back to over world
your cords are now
x=-18693 y=63 z=-10147
as you can see the issue is not linking my portals no nether portal should work like this 1 block = 8 not 8000
so really its not WAI please look at pictures and see what is happing before you say soem thing is WAI
is this still reproduceable?
I believe this was fixed in one of the 1.8.x updates. Is this still happening?
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.