Bryan F
- hatebeat
- hatebeat
- Europe/Stockholm
- Yes
- No
MCPE-55314cantloginminecraft.mp4
Following version 1.17.30, my long-standing realm world is experiencing corruption. Immediately after the patch, the world file size randomly jumped
600 mb (from about 1gb to 1.6gb) after a couple hours of play.(Note: My players have a world limit, so new exploration did not cause this. I’ve investigated the file using mcc tool chest, and no new chunks have been explored).
After the file size jump, the world began slowing down until the lag made moving or placing blocks impossible. After several more hours, the realm no longer allowed anyone to log on (stuck on loading world screen). The backup from this time cannot be entered in single player mode, either.
I replaced the world with a backup from before the file size jump, but from after the 1.17.30 update. After another day, the process repeated (the file size jump, the slow down, the inevitable inability to load the world).
My next troubleshooting step is to replace the world with another backup from prior to the update and see if the corruption occurs again. I have not yet done this, as I do not want to ask my players to keep working on projects that will likely be rolled back.
Some background info:
I’ve run this realm for over three years. We had a very similar problem happen immediately following the December 2019 Buzzy Bees update (1.14). It took me four months to get my world back online for my members; our spawn chunks had become corrupt somehow due to the update, and I had to do hours upon hours of very meticulous work to get our world functioning again. I still was not able to run the world on the realm until a hotfix on April 15th, 2020 (patch version 1.14.60). I’m not sure if somehow a similar bug that was addressed by that hotfix was introduced this time around as well, but the after-effect of this patch is very similar.
Thank you for taking the time to listen and look into this. If I can provide any further information or files, I’m happy to do so.
Following version 1.17.30, my long-standing realm world is experiencing corruption. Immediately after the patch, the world file size randomly jumped 700 mb (from about 1gb to 1.7 gb) after a couple hours of play.
(Note: My players have a world limit, so new exploration did not cause this. I’ve investigated the file using mcc tool chest, and no new chunks have been explored).
After the file size jump, the world began slowing down until the lag made moving or placing blocks impossible. After several more hours, the realm no longer allowed anyone to log on (stuck on loading world screen). The backup from this time cannot be entered in single player mode, either.
I replaced the world with a backup from before the file size jump, but from after the 1.17.30 update. After another day, the process repeated (the file size jump, the slow down, the inevitable inability to load the world).
My next troubleshooting step is to replace the world with another backup from prior to the update and see if the corruption occurs again. I have not yet done this, as I do not want to ask my players to keep working on projects that will likely be rolled back.
Some background info:
I’ve run this realm for over three years. We had a very similar problem happen immediately following the December 2019 Buzzy Bees update (1.14). It took me four months to get my world back online for my members; our spawn chunks had become corrupt somehow due to the update, and I had to do hours upon hours of very meticulous work to get our world functioning again. I still was not able to run the world on the realm until a hotfix on April 15th, 2020 (patch version 1.14.60). I’m not sure if somehow a similar bug that was addressed by that hotfix was introduced this time around as well, but the after-effect of this patch is very similar.
Thank you for taking the time to listen and look into this. If I can provide any further information or files, I’m happy to do so.
Following version 1.17.30, my long-standing realm world is experiencing corruption. Immediately after the patch, the world file size randomly jumped 700 mb (from about 1gb to 1.7 gb) after a couple hours of play.
(Note: My players have a world limit, so new exploration did not cause this. I’ve investigated the file using mcc tool chest, and no new chunks have been explored).
After the file size jump, the world began slowing down until the lag made moving or placing blocks impossible. After several more hours, the realm no longer allowed anyone to log on (stuck on loading world screen). The backup from this time cannot be entered in single player mode, either.
I replaced the world with a backup from before the file size jump, but from after the 1.17.30 update. After another day, the process repeated (the file size jump, the slow down, the inevitable inability to load the world).
My next troubleshooting step is to replace the world with another backup from prior to the update and see if the corruption occurs again. I have not yet done this, as I do not want to ask my players to keep working on projects that will likely be rolled back.
Some background info:
I’ve run this realm for over three years. We had a very similar problem happen immediately following the December 2019 Buzzy Bees update (1.14). It took me four months to get my world back online for my members; our spawn chunks had become corrupt somehow due to the update, and I had to do hours upon hours of very meticulous work to get our world functioning again. I still was not able to run the world on the realm until a hotfix on April 15th, 2020 (patch version 1.14.60). I’m not sure if somehow a similar bug that was addressed by that hotfix was introduced this time around as well, but the after-effect of this patch is very similar.
Thank you for taking the time to listen and look into this. If I can provide any further information or files, I’m happy to do so.Following version 1.17.30, my long-standing realm world is experiencing corruption. Immediately after the patch, the world file size randomly jumped 700 mb (from about 1gb to 1.7 gb) after a couple hours of play.
(Note: My players have a world limit, so new exploration did not cause this. I’ve investigated the file using mcc tool chest, and no new chunks have been explored).
After the file size jump, the world began slowing down until the lag made moving or placing blocks impossible. After several more hours, the realm no longer allowed anyone to log on (stuck on loading world screen). The backup from this time cannot be entered in single player mode, either.
I replaced the world with a backup from before the file size jump, but from after the 1.17.30 update. After another day, the process repeated (the file size jump, the slow down, the inevitable inability to load the world).
My next troubleshooting step is to replace the world with another backup from prior to the update and see if the corruption occurs again. I have not yet done this, as I do not want to ask my players to keep working on projects that will likely be rolled back.
Some background info:
I’ve run this realm for over three years. We had a very similar problem happen immediately following the December 2019 Buzzy Bees update (1.14). It took me four months to get my world back online for my members; our spawn chunks had become corrupt somehow due to the update, and I had to do hours upon hours of very meticulous work to get our world functioning again. I still was not able to run the world on the realm until a hotfix on April 15th, 2020 (patch version 1.14.60). I’m not sure if somehow a similar bug that was addressed by that hotfix was introduced this time around as well, but the after-effect of this patch is very similar.
Thank you for taking the time to listen and look into this. If I can provide any further information or files, I’m happy to do so.
Editing to add information:
Browsing reddit for others having this issue, and this seems to only be happening to worlds that are uploaded to realms, so this report should potentially be in the realms section instead.
Minecraft just updated to a new version (1.5.1) with a "hotfix". It says that this issue has been fixed. However, now when I click sign in, it says "connecting..." and then tells me "We tried signing you into your Microsoft account, but something went wrong." I still cannot login to my Microsoft account on my Switch.
I'm wondering if there is anything we (those of us affected by this issue) have in common. I'm assuming it has to be something to do with our Microsoft accounts...? We are all using the same hardware, and we all can still login with our Nintendo IDs, so the only other factor could be the account. In my case, I've never used Xbox live before signing into Minecraft with my Microsoft account, so maybe that has something to do with it? Also, I login using my phone number rather than a username. I don't know if these things can cause an issue, but I guess it doesn't hurt to brainstorm; since this bug seems to be affecting random users, it's probably hard to replicate, which means it's hard to fix.
Thanks for keeping us posted, Auldrick. In my case, my MS account (which uses my phone number as a login) was an existing account that I've had for several years; I believe I created it for Skype in the past, but I'm not 100% sure.
(edit: As others are now confirming that not using a phone number login is solving the issue, I'm still hoping this might be somehow resolved without having to delete my save data. I've put in 45 hours on my world in the meantime.)
I have been experiencing this issue on my survival realm and it's becoming a big issue (many players live far from one another and use the nether to travel). Only specific portals cause damage, and they only cause damage going one way (either into the nether or into the overworld). No blocks are obstructing these portals. I have rebuilt some of these portals and it did not have any effect. Some of the portals cause more damage than others; the one that goes to my base regularly will damage me 1.5 to 3 hearts, but one just built today is for some reason causing the game to hang in loading (the generating terrain screen upon entering the nether) for around 10 seconds or so, and doing quite a bit of damage as a result. I am playing on Switch; others in my realm are playing from Switch, PC, Xbox and mobile.
Has this been resolved for any of you? I am having the same issue as of this morning. Nobody can join from any platform. Realm name is "Koholint", owner gamertag is "tokaroonieroo".
I've had this problem since I started my realm in August. Certain words (the majority of them are player names, but there are some other random words like "paper") will cause a sign to be posted and then immediately delete the text. If you write the same word in a book, it will censor the word with ####s. To be clear, these words aren't profanity in any way, but player names such as "Hannah", "Bryan", or "Cody" most of the time. It happens with the same words consistently, but occasionally after a long time of not trying a specific word (think weeks to months), it will be typeable again.
I don't believe this was patched as David is suggesting above, because I am having this issue this morning still on the latest version.
This issue has affected two members of my realm this week that I know of. Both times they had slept in their respective beds at their respective bases. Both of them logged in and got a death message. In both instances, their belongings were scattered at the world spawn point even though neither of them were anywhere near spawn. One user was on Nintendo Switch and the other on PC, so this isn't limited to one platform.
Unfortunately this has not been resolved as Robert suggested above. In fact, the issue seems to be becoming more frequent. I cannot even type the word "west" in my realm, let alone half the other words I need to post navigational signs. About 7 times out of 10, a sign I place is censored. This is incredibly frustrating, as signs are very important in a multiplayer world with many members.
We had a couple members of our realm get stuck in end gateways prior to knowing about this glitch and ever since we have been having these "corrupt" chunks in the overworld as well as the end-- we have a town at spawn point and keep losing chunks with no way to restore them but to revert to a backup. It has also happened on another player's base outside of town. I assume this is related as it's only been happening since our players got stuck in the end gateways and also it seems to be the same rendering error that is affecting the end and causing people inside these chunks to not be able to log back in.
A few hours ago, I reset the end on our realm with mcctoolchest and we have not had any issues since doing so (I'm still keeping my members from re-entering the end for now), so this may be a solution for those who don't have any buildings or anything to lose in the end. I do have a copy of my world from before the fix though so I will see about uploading it somewhere. It's about 800mb so it could take a bit but I'll report back when I can.
I think this is somehow related to https://bugs.mojang.com/browse/MCPE-40538 . This started happening in my world at the same time as 40538. Whenever people entered the End, I would start losing chunks in our spawn town around 2-3 days later. This was fixed by downloading the world, resetting the End (meaining, I deleted all the End chunks with MCC tool chest), and re-uploading the world. I kept my members out of the End for a while and it didn't happen again... Until we had a new member start going into the End (unbeknownst to us) and we started losing chunks in town again. I then reset the End once again, made sure nobody entered, and it stopped happening.
40538 was said to be resolved (for newly created End portals) in the most recent update. I destroyed our existing End portals and created a new one for my members to use. For about a week, we were okay. We are now losing chunks again. I have found out I can reload the chunks by clicking the "close realm" button and then opening the realm again.
I'm not sure if this is directly caused by the same bug that is causing 40538, but there must be some kind of correlation, because this is NOT happening at all in my world when no End chunks exist.
One other thing to note is that this does not happen if the world is offline (which I guess is why closing and then reopening the realm resolves it). When I've had the issue and then downloaded my realm to reset the end, I logged on in single player mode and the chunks were just fine.
edit: I see that this report has been open since 2017, so this obviously can't have been CAUSED by 40538 specifically, but perhaps something that's causing 40538 might also be causing a resurgence in this issue as well.
edit: This is now causing chunks of our nether network to disappear almost every time anyone enters the nether (as described in
REALMS-1569, which is marked as resolved). I can reset my realm to "fix" this, but I'm at the point where I have to reset my realm every other hour to keep it running properly.Was there ever any solution for this? This has begun happening to my realm. Last week after I spent 3 hours building an event for my realm community, the world reverted to a save several hours earlier. Just last night it rolled back again for seemingly no reason. I have an established community that I've worked hard for, but people will certainly begin to leave if this remains an issue, and I can't blame them. The only instances I find of this happening to others are just like this one, with no comments attached.
My realm is no longer playable in any way. It went from crashing a couple times a week about two weeks ago to crashing a couple times a day last week, to crashing several times a day this week, to just being offline entirely yesterday (nobody was able to join the realm). Interestingly, I was able to bring it back online by closing and reopening the realm (under subscription) which has (temporarily) fixed some realms issues in the past. Once back online, though, a few of my members logged in and it crashed again in minutes.
This morning I'm able to log on again as nobody else is even trying to get online anymore, but the performance was very bad and stuttery. Within 5 minutes, objects such as chests and furnaces were no longer able to be interacted with, and chunks surrounding the area I'm in will not load, so I've obviously lost connection. After a few more minutes, I've disconnected. Every one of these disconnections leads to a rollback. This is an emergency issue at this point.
For others of you experiencing this issue, how old is the world you're playing on? I've had this issue increasingly over the past couple weeks to the point where, as of two days ago, I can no longer play on my realm at all (I can log on, but within 5 minutes, the game stops responding until it crashes, and then no progress is saved). My realm is almost a year and a half old. I know some members of my realms have other realms they play on occasionally and their other (newer) realms are all fine and not having this issue. We are wondering if it has to do with the age of our realm.
For those of us who have a realm stuck in an unplayable state, it seems as if this is tied to
MCPE-32501- meaning, our actual world file is a problem now whether it's uploaded to a realm or not. I'm not sure if this was caused by the continuous crashing or the update or what, but we are now getting the same error as people on 32501 which has been open without a fix for a year and a half.One interesting thing to note:
When I downloaded my broken realm world and opened it, I got two error messages in succession, both with the pink and black checkered background. First I was told something like "missing or corrupt skin!" and after that I was given the "you are out of storage space" message.
I did a little testing trying to create a new world with the same seed and files from my current world. Every time I would try to load up the new world, it would either just crash, or it would give me an error about missing skins or textures (and then crash). I'm wondering if something about the recent update somehow changed the way certain textures are accessed and it's resulting in a crash.
A second interesting thing to note:
My realm has been unplayable for about 3 days now. I was under the impression that backups are mainly created while people are playing. My realm is creating backups still even though nobody is able to play. Even more interesting, the backups are changing in size each time. They range from around 1770MB to 1793MB. So I'll have something like this
Backup 1: 1770 MB
Backup 2: 1776 MB
Backup 3: 1789 MB
Backup 4: 1770 MB
I'm not sure if this is normal, as I've never needed to monitor my backups so closely in the past, but it seems strange. Why would the file size fluctuate if nothing in the world is changing?
My year-and-a-half-old realm world is encountering this issue. If I download the current world, I can't log on at all-- this issue comes up during world loading. I've been trying to see if I could restore an older file, but backups as far back as August are giving this error (although in those, it will let me play for a few minutes before this error pops up). I have about 450 gb free on my hard drive, so I know that's not the issue, and anyway, it's keeping the world from working on my realm, where it also shouldn't be an issue.
Every time it closes with this error, there are also texture issues on the loading screen. The menu will not load properly; sometimes the buttons are tiny squares instead of rectangles, sometimes the whole menu interface is replaced by the pink and black checkers. Most of the time, the background image of the menu screen (currently the bees) will be replaced by a moving pink/black checkered screen.
After many other attempts at working around the issue, I attempted to reinstall the game, but that also had no affect.
I realise this issue has been open for quite some time, but it certainly seems as if it is becoming more of an issue for many people since 1.14.
In regard to the above suggestions that it happens at 700mb - my world did not have a problem until 1800 mb. Also, going through backups of my world over the past year, it is still occurring no matter what the size. My oldest backup of my world is about 350mb and, though it does take a bit longer to occur, the glitch still happens... So it seems something in the newer updates' code is not playing nice with another bit of code, I think.
I'm willing to wait for a fix if it is being worked on, but my main concern is that nobody is assigned to this bug on here, which certainly leads us to believe that nobody is looking into the matter.
Isn't this the same issue as
MCPE-32501?This is still present on Bedrock 1.14.60 (playing on PC). I and many others had assumed this was related to
MCPE-32501, but that was finally fixed in yesterday's update.Clicking into Realms Stories either from the game menu (before entering the world) or from the menu while the world is loaded crashes the game for me. This is even without resetting the world as initially suggested in this report.
This has been happening again ever since the Realms outage a few weeks ago.