• Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.21.50
    • None
    • Creative
    • Unconfirmed
    • Windows

      MCPE - Bedrock Edition
      World Seed - 866 513 395

      Unable to teleport to back to world spawn point in Creative Mode for Windows. (MCPE)
      I began and finished all my builds at the world starting point, coordinates 1424 63 10.
      Recently I ventured off and got super lost just to explore, but tried using the "/tp" feature to teleport back to the XYZ coordinates, but end up inside a mountain in the ground in a different region of the world.

      Steps to Reproduce:
      open up Primary save file "phenoms world"
      notice you are next to a mountain with falling water
      type "T" for the chat - type in "/tp @s 1424 63 10"
      hit ENTER

      Observed Results:
      game will teleport you back inside the ground just under the foot of the mountain
      (which is the area I am super lost in, away from world spawn/starting point)

      Expected Results:
      Supposed to be teleported back to the original world spawn point, which has jack-o-lanterns surrounding you. All other builds are also present in immediate surrounding area, including a nearby church with bells on the roof and stained glass windows. This church is NOT in the back up save file in my start up menu after I hit "Play".

      Screenshots/Videos attached

      Notes:
      Pay close attention to the screen shot file names that pertain to which save file they come from, as well as the XYZ coordinates that somehow match in the "lost area" and the backup save file where the spawn point really is.

        1. 01 primary save file.jpg
          93 kB
          Justin Greathouse
        2. backup world spawn point.jpg
          294 kB
          Justin Greathouse
        3. primary save file mountain base.jpg
          256 kB
          Justin Greathouse

            phenom_1986 Justin Greathouse
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: