Nether portals link back to the original overworld nether portal. I have traveled beyond 128 blocks, 500 blocks, and 750 blocks away from original portal to create an additional portal attempting to find a nether fortress. Regardless of distance traveled portal always links to the original portal created in the nether.
I searched bugs and couldn't find this pertaining to Xbox One Minecraft:Bedrock "Better Together Update".
Comments 13
I found a monument far enough away in the overworld; more than 1024 blocks; so I will try it out. Hopefully, I just miscalculated since it has been awhile since I created a nether hub. I also found a fortress that more than meets the requirements that you stated for the nether to create a new overworld portal. I have been known to be brain dead from time to time; so thanks.
Luis is correct. Since the 1.2.0 update, portals have not followed the rules. before the update, if you go 1000 blocks or more away from original a new portal is generated. after the merge. I have created a portal over 2000 blocks away, one facing North/south the other facing East/West. They still sync to the same nether portal. this world was created using the 1.2.0 update. My old world from version 14. still works correctly. which is a little strange.
I just tested yesterday with a newly created portal and had issues. The world was created with the latest Bedrock update and linking definitely has issues. In this newly created world the overworld portal was created about 75 blocks from spawn at one block above sea level. When entering the portal from the nether counter part created a new overworld portal approximately 100 blocks away from the original portal built by myself; approximately 175 blocks from world spawn in total. I wondered whether or not this was just a glitch so I destroyed the portal that was created from entering from the nether and ran back to my originally built portal and retried. Upon exiting from the nether yet another portal was created mere blocks from the portal I destroyed (approximately 4-5 blocks).
There is really an issue with portal mechanics that needs to be identified.
Another update after further testing......
I created yet another world in version 1.2.3.3 with cheats enabled. I created a portal in creative at or just outside spawn and it functioned correctly. I, therefore, using coordinates traveled 148 blocks away from the portal in the nether and created another portal. The portal created the correlating overworld portal as expected which functioned correctly as well.
There is something amiss that I can not place my finger on. The two previous worlds had issues to say the least. The first was created at launch so the version 1.2.0.0 in survival, no cheats. Therein may be the issue with nether portal linking in this case I am willing to concede. The second was created in 1.2.3.3 in survival, no cheats, and was very erratic and nonfunctional portal mechanics to say the least with the only changes being seed, cheats (for coordinates), and the portal being created in survival verses creative on the latest trial.
When I get some more time I can try and create the latest world with no cheats and recreate the portals strictly in survival to see what occurs. If it functions properly I'll recreate the worlds under the same prerequisites to see if it is world related and possibly a generation issue. My wife created a world on her Xbox and the same error that I described occurred for her as well utilizing the survival, no cheats world creation settings in version 1.2.3.3. I hope this isn't a hit and miss issue but something that can be recreated with consistency. I will try and identify if it is seed or settings related.
I have now requested help. Could you please verify that the procedure in your last comment still causes the problem in 1.2.3?
This works as intended.
The problem in this case was that the original Overworld portal location corresponded to a Nether location that was buried within a netherrack mountain. Usually in such cases the game looks for a place to generate the Nether portal as close as possible horizontally by searching vertically for a suitable location. However, this mountain ran all the way from the lava ocean to the Nether ceiling, so the game was forced to search horizontally. The closest place it could find was 21 blocks (Euclidian) away. 21 blocks in the Nether is equivalent to 168 blocks in the Overworld, which is outside the 128 block range for finding the Overworld portal when you returned. In short, your original Overworld portal was simply in an unfortunate location that can't be reached from anywhere in the Nether, because the entire part of the Nether that would link to it was either in lava, in netherrack, or in mid-air. However, you could have dug a 4x3x4 hole in the mountain near the destination coordinates and built a portal there, and it would have linked up the way you wanted.
Thank you for the explanation; at least now I understand why this is occurring. I guess I just have extremely poor luck when choosing portal locations.
It also makes it far more difficult to resolve issues when they have made coordinates a cheat. Maybe they will see the error in this thinking. I could understand if this was limited to hardcore mode or allowing coordinates to locator maps.
The explanation given was more than sufficient as to my bad luck in portal locations chosen. I fully expected this issue to be closed; I would have done this myself but couldn't figure out how.
This is not a bug; 1 block in the Nether is 8 blocks in the Overworld, which means if you want to create a portal in the Overworld that links to a new portal in the Nether you have to travel far enough in the Overworld to get 128+ blocks away in the Nether. 128 blocks in the Nether is 128*8 = 1024 blocks in the Overworld.
Your 128, 500, and 750 block tests only got you 16, ~62, and ~93 blocks away.