[MC-73034] Nether Portals don't connect to newly constructed portals until World Reload

While testing the fix of MC-3, I found this bug. I then tested it back in 1.8 and it was still there, so I don't know how long it's been around or even if there is a ticket for it already (I tried to look it up but couldn't come up with anything).

Anyways, when you travel to the Nether, generating a new portal, and build a new portal, even just a couple blocks away, and destroy the old one, the overworld portal doesn't adjust your destination coords in the Nether, placing you where the old one was.

To reproduce, build a new Portal in the overworld and travel through, generating a new portal in the Nether. Now build a second portal in the Nether a few blocks away and destroy the first. Now if you travel through the new portal to the overworld and then back again, it will place you where the old portal was, even if it was destroyed. The game also neglects to generate a new portal in that location, so you just spawn in with no portal blocks touching you.

Related issues

discovered while testing

MC-3 Player facing changes when passing through nether portals in certain cases

is duplicated by

MC-72224 Nether Portals not generating correctly

MC-73041 No nether

MC-74963 Nether portal not working as intended

Comments

galaxy_2alex 2014-10-15T15:44:01Z

Technically a duplicate of MC-72224, but this is more detailed.

migrated 2014-10-15T16:12:00Z

I would add that it doesn't seem it work for more than a few blocks away but It is definitely present in 1.8.1 Pre-1.

Edit: Seems to only work some of the time.

Edit 2: This bug (feature?) is based on what Sol Toder said below. If you wait 60 seconds this doesn't occur. This may be working as intended.

AjaxGb 2014-10-15T16:15:21Z

According to the wiki, nether portals remember the destination from the last time they were used for 60 seconds. So this is less of a bug, and more of a poorly thought out feature.

migrated 2014-10-15T16:20:30Z

Well if a [Mod] or member of Mojang wants to come mark this poorly thought out "Feature" as "Works as intended", then they can go right ahead. I just think it should be adjusted so it doesn't feel so buggy (spawning in a location without portal blocks touching you). At the very least, they could make a new portal generate where the old one was if it's no longer there.

Nathan Adams 2014-10-16T09:29:13Z

WAI for now. Right now we remember portal destinations for 30 seconds after they're last used, because it's really expensive to do otherwise.

migrated 2014-10-16T09:40:33Z

Excuse my ignorance, why can't you "forget" portal destinations when a portal is built or destroyed?

migrated 2014-10-16T12:00:51Z

Scanning for them is resource-intensive.