Uploaded image for project: 'Minecraft Realms'
  1. Minecraft Realms
  2. REALMS-7624

NETHER COORDS BEING MATCHED TO OVERWORLD COORDS

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.16.210 (Bedrock)
    • None
    • Bedrock Edition (Xbox One, Windows 10, MCPE)
    • Unconfirmed
    • Bedrock

      On my realm, I have a vast network of nether portals connected by railway to everyone's individual lands. Occasionally when going through a nether portal, either from the Overworld to the Nether or vice versa a couple different things tend to happen.

      Primarily, one member of the realm made a portal inside his base and then would enter the portal to go to the nether, come back and appeared underground 200 blocks away with a new portal.

      Secondly, myself and another member have experienced an issue where we will enter a nether portal in the Overworld and then appear in the nether at the matching coordinates rather than the 8:1 ratio seen in gameplay. For example, we have a portal near Overworld coordinates 2000, 70, 500 and when we go to the nether it would bring us to roughly 250, y, 63 but instead would bring us to the matching coordinates 2000, y, 500.

      Not only is this extremely aggravating but it is beyond frustrating that when this error occurs there is no portal nearby to re enter the Overworld. The only solution is to have coordinates written down and dig or fly yourself thousands of blocks.

      I believe this is a critical game function error and quite honestly a robbery of those who pay for a realm every month to have their friends play on a server without issues.

      I have no files to upload as a video would take longer than my devices allow me to record. It took about 5 minutes to load into the nether when this initial error occurred.

      Last date of issue was 3/23/2021 @ approx 7pm (MST)

            Unassigned Unassigned
            Darth Hobbes Dylan D Nave
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: