Hi so I'm part of a decently sized SMP and the owner of the realm put out a bug report around a month ago. The bug has been flagged as resolved when it clearly hasn't, it's only gotten worse. Since I'm not the one running things on the server, I wanted people who take care of bugs, to actually do their job and fix this. Nobody has been able to play on the realm for a month and a half, and it being summer break and all, it's extremely frustrating when we're just being ignored by support and have to take matters into our own hands.
Here's a summary of the issue. A day before the 1.17 update, our realm started having extremely bad chunk errors. Builds were being ruined and a lot of people lost entire houses. The owner of the SMP has tried multiple times to reload a backup, but nothing has worked. The original realm before the update was a file size of 3.4gb. After the new update, it increased to 4gb. There were addons being used but they were turned off while reloading a backup. It's gotten to the point where every time an attempt to backup the realm is made, their entire computer crashes. They've tried deleting the realm and reloading a new one with the same world, nothing works. At this point, they're just wasting money on a company doesn't even care.
We need the realm back up. We can't just give up and lose months of hard work and memories go to waste. If anyone is reading this who works at Microsoft and actually cares, we need you to help us.
Expect more reports similar to this, we are a group of individuals who will not give up until we get our realm back up.
Related issues
Attachments
Comments
migrated
[Mod] Umija5895M
What bug report was submitted by the realm owner that was "resolved"? Also note that "resolved" does not necessarily mean "fixed". If the report was a duplicate then the original report will take precedence and additional duplicates will be resolved as such.
The issue with chunks resetting or being voided is tracked as MCPE-98789.
Crashes are automatically reported by the realm servers and are not kept on the bug tracker unless there is a specific repeatable list of steps that someone else can follow to reproduce a crash.
If you are still not able to access your purchased realm please contact Minecraft Support for help. It would be best though if the realm owner did this so they can provide credentials if needed.
If you (or the realm owner) can download a copy of the realm, can it be opened locally and do the same issues occur? In that case, it might be helpful to provide a copy of the world for analysis.
You (or your group) might want to read the Bug Tracker Guidelines to understand how this system works. In addition, please limit your reports to information specifically related to describing and reproducing the issue.
This ticket has been temporarily closed as Awaiting Response. It will automatically reopen when you comment with new information. Please be sure to provide all requested information in a comment (not by editing the Description) so that the responses can be followed. Tickets that do not contain enough information may be closed as Incomplete.
migrated
REALMS-8282 this is the report
[media][media]
[media]
[media]
[media]
and here's some pictures of the world after the update.
Something else is that I have multiple realms and I've tried this with all the realms. The world itself, which is a backup of the messed up world which isn't in itself messed up, is fine and we can all play in it as a single world not in a realm. It's only when I try to put it into a realm that my computer breaks.
Auldrick
The damage to this world, as shown in the screenshots, is very severe. The corruption looks like the kind that might result from using a third-party world editor, though I'm not saying that you did that. But it's quite strange that corrupted chunks would be regenerated with such different heights, as if those chunks belonged somewhere else in the world. The only situation I can think of where that would be expected is if the corruption occurred a long time ago, before updates that made major changes to world generation, like the Update Aquatic and the Nether Update. Also Caves & Cliffs, except that you had this problem before it was released.
Or did you? Is it possible that this world was originally uploaded from one that was being played in a Caves & Cliffs Beta release? Mojang doesn't explicitly prohibit uploading Beta worlds to Realms, but they do warn you that Beta worlds cannot be guaranteed to be compatible with later full releases, which is what Realms uses.
At any rate, this copy of the world isn't repairable except by hard manual work. Since you were able to download this from your Realm and it's not at risk of being lost, it's safe for you to try restoring an earlier backup copy. If the damage happened recently, despite my thoughts above, you should be able to find an undamaged backup. Have you tried that yet?
Your original ticket was closed as a duplicate, which was correct because the problem it describes was reported previously. (As the other mod said, resolving a ticket doesn't mean the bug was fixed, it means we're no longer using the ticket to track activity for the issue it reports.) In your case, that was because we were already tracking activity via MCPE-98789.
With respect to this report, it was filed in the mistaken belief that your original ticket was incorrectly resolved. Since it essentially reports the same problem yet again, I will close it as another duplicate. I will, however, continue to watch this ticket for new comments in case you decide to try restoring a backup.