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

Realm crash autochanged gamemode from s to c

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • None
    • 1.19.22 (Bedrock)
    • None
    • PlayStation split screen
    • Unconfirmed
    • Bedrock

      Playing on mcbe on a realm on ps4 in local splitscreen. As i go to change difficulty from normal to hard, i get kicked out from the realm. So i go back into it, just to find out that my realm just went from survival to creative, all on its own. So i try to load a backup from the realm settings, from a few minutes prior, and it is also in creative. Needless to say i never ever set this world to creative. Going back to select an even early backup from the settings i notice that the world name changed from what it was, to what the world on the second realm slot is called, the world on the second realm slot, which, guess what, is my creative world. So, tech ignorant speaking here, somehow the first realm slot picked something from the second slot and switched my first slot world from survival to the second slot world which is in creative. i don't ever make bug reports but i recorded two clips using the ps4 system, in the first one is the bug taking place, me getting kicked out and getting back in to find out that the gamemode is changed, and in the second clip is me going through the backups and seeing the world name changed ( i don't have proof that it was different before but trust me it was) to the second slot world name. I can't attach clips here and it's pointless to take screenshots of the bug so here are two youtube links for the clips             Bug happening: https://www.youtube.com/watch?v=q_XiAO1bXqY         Followup:         https://youtu.be/Z-aFwrP4Rr4        

            Unassigned Unassigned
            Mojo35 Steve Mazzocca
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: