simpleknight
Assigned
Reported
Comments
Honestly, I thought your team had closed the issue, the thread was a little confusing
Yes, the issue is resolved, the owner of the realm was finally able to update a few days later, which then updated the realm.
It would be good if users on other platforms were able to walk back recent updates to avoid these issues. I know on Java we can do that, but on consoles we can't, and even on Bedrock PC, there's no simple way if you haven't been playing in a while to load older versions. If users could have access to even just both the newest update as well as the previous one (in this case, 1.19.20 and 1.19.21) this would prevent being locked out of a Realm while waiting for the owner to update. Because of the creative nature of Minecraft, a lot of us put in many days of effort into what we build, getting locked out like that makes it a bit stressful.
Ok, that explains it, they were unable to update on both Switch and PC. Unfortunately, I was forced to update on PS4, so I don't have realms access.
Big bummer, because now I can't stream playing on that server.
Any ETA when these update issues will be fixed?
This is happening in 1.19.30, and is far more frequent and impactful than previously. In previous versions, it was happening from time to time where a mined block wouldn't get mined and instead would reappear. The resolution would be to save and exit, then upon re-entering, the issue would be gone for several hours or more.
However, on Sept 29, around 10p PT, four players in our Realm experienced an extreme version of this. We had been playing for over an hour when this glitch occurred. That ENTIRE hour of play was lost for all players in our Realm. This caused a lot of grief among the players, all of whom rage quit, and two of whom suggested they might stop playing altogether.
This is a more serious version of this issue, and I think requires more detailed review. It's also worth noting that the frequency of this issue in all forms has been far higher than in previous versions. This suggests a more fundamental problem regarding this issue in 1.19.30. We are hoping for a quick update to resolve both this issue and the slow redraw issue noted in another bug report.