Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-169488

Realm Crashing and Rolling Back

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • 1.15.1
    • None
    • iOS 13
    • Unconfirmed

      I'm an admin on a realm, and one day I think of making this one kit that people can get. It's decent, all the commands work, and when I test run it, everything is perfect. And then 30 seconds later the realm crashes. It takes about 5 mins for the realm to reconnect, and when I come back on, I am at the spot I was right before I started making the kit, and sure enough, the kit itself was gone. At first, I thought it was the kit, so I decided I'd remake it to see what happened. This time, the realm crashed just a couple minutes BEFORE I finished the kit. This is incredibly frustrating, because this means the realm crashing and rolling back (which basically means revert to the most recent auto save, which unfortunately for me was before I made the kit) has absolutely no rhyme or reason to it. At the time of making this report, the realm has done this at least 5 or 6 times now, and with every crash it becomes more frustrating. Everyone on the realm is furious, including me, and it is taking everything I have not to scribble down some crazy hate letter to you. This hasn't just been happening on this one realm, by the way. I've been on 3 or 4 realms in the past week and this has happened at least once on every single one of them. There is no avoiding the truth, Mojang: 1.14 realms are glitchy as heck, to the point where they are unplayable (you can't make any progress on anything because the realm will roll back and you'll lose the progress), and they need fixing immediately. I am not just speaking for myself, I am speaking for basically every single Bedrock Edition player who plays on realms.

            Unassigned Unassigned
            Xorkent 2 Bart Simpson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: