![[Mojang] Alexander Torstling](../../../data/avatars/users/27191.png)
[Mojang] Alexander Torstling
- atorstling
- atorstling
- Europe/Stockholm
- Yes
- No
[Mojang] Alexander Torstlingis duplicated by
is duplicated by
is duplicated by
REALMS-1250
is duplicated by
is duplicated by
[Mojang] Alexander Torstling:Hey everyone! I'm sorry for the inconvenience this has caused. We're now at a stage that we believe most people should have gotten unstuck. If not, please re-add yourself to https://codeshare.io/GLypMV, I'm restarting that list after this fix.
For everyone who was impacted, please start a support case so we get a chance to compensate you.
We will continue to closely monitor the issue in the upcoming days.
How to open a support caseSend an email to Mojang with your Transaction ID, Mojang account email, and any other relevant information, through this form: https://help.mojang.com/customer/portal/emails/new
Refer to this page for wait times on replies.The problem only appears when I log into Realms
C [lwjgl_opengl.dll+0xe92d] Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) J 6303 org.lwjgl.opengl.GL11.glBindTexture(II)V (0 bytes) @ 0x0000000003899c84 [0x0000000003899c40+0x44] J 6478 C2 dde.h()V (10 bytes) @ 0x0000000002f0332c [0x0000000002f03280+0xac] j chw.a(Lchx;)Lchy;+29 j chv.a(Lchx;)Lchy;+31 j chv.b(C)Lcia;+61 J 6337 C2 chv.a(C)Lcia; (76 bytes) @ 0x000000000317eff8 [0x000000000317ee60+0x198] J 6274 C1 cfz.a(C)F (27 bytes) @ 0x0000000003366c24 [0x0000000003366b60+0xc4] j cfz.e(Ljava/lang/String;I)I+161 j cfz.d(Ljava/lang/String;I)Ljava/lang/String;+14 j cfz.c(Ljava/lang/String;I)Ljava/util/List;+3 j cio.a(Ljava/lang/String;I)Ljava/util/List;+6 j net.minecraft.realms.RealmsScreen.fontSplit(Ljava/lang/String;I)Ljava/util/List;+6 j net.minecraft.realms.DisconnectedRealmsScreen.init()V+25 j cio.c()V+4 j cjs.a(Lcfi;II)V+50 j cio.a(Lcfi;II)V+14 j cfi.a(Lcjs;)V+129 j net.minecraft.realms.Realms.setScreen(Lnet/minecraft/realms/RealmsScreen;)V+7 j net.minecraft.realms.RealmsConnect$1.run()V+374 v ~StubRoutines::call_stubName AMD Radeon R9 200 Series Win32_VideoController DriverVersion = 24.20.11016.4 Win32_VideoController DriverDate = 05/16/2018[Mojang] Alexander Torstling:Hey everyone! I'm sorry for the inconvenience this has caused. We're now at a stage that we believe most people should have gotten unstuck. If not, please re-add yourself to I'm restarting that list after this fix.
For everyone who was impacted, please start a support case so we get a chance to compensate you.
We will continue to closely monitor the issue in the upcoming days.
How to open a support caseSend an email to Mojang with your Transaction ID, Mojang account email, and any other relevant information, through this form: https://help.mojang.com/customer/portal/emails/new
Refer to this page for wait times on replies.The problem only appears when I log into Realms
C [lwjgl_opengl.dll+0xe92d] Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) J 6303 org.lwjgl.opengl.GL11.glBindTexture(II)V (0 bytes) @ 0x0000000003899c84 [0x0000000003899c40+0x44] J 6478 C2 dde.h()V (10 bytes) @ 0x0000000002f0332c [0x0000000002f03280+0xac] j chw.a(Lchx;)Lchy;+29 j chv.a(Lchx;)Lchy;+31 j chv.b(C)Lcia;+61 J 6337 C2 chv.a(C)Lcia; (76 bytes) @ 0x000000000317eff8 [0x000000000317ee60+0x198] J 6274 C1 cfz.a(C)F (27 bytes) @ 0x0000000003366c24 [0x0000000003366b60+0xc4] j cfz.e(Ljava/lang/String;I)I+161 j cfz.d(Ljava/lang/String;I)Ljava/lang/String;+14 j cfz.c(Ljava/lang/String;I)Ljava/util/List;+3 j cio.a(Ljava/lang/String;I)Ljava/util/List;+6 j net.minecraft.realms.RealmsScreen.fontSplit(Ljava/lang/String;I)Ljava/util/List;+6 j net.minecraft.realms.DisconnectedRealmsScreen.init()V+25 j cio.c()V+4 j cjs.a(Lcfi;II)V+50 j cio.a(Lcfi;II)V+14 j cfi.a(Lcjs;)V+129 j net.minecraft.realms.Realms.setScreen(Lnet/minecraft/realms/RealmsScreen;)V+7 j net.minecraft.realms.RealmsConnect$1.run()V+374 v ~StubRoutines::call_stubName AMD Radeon R9 200 Series Win32_VideoController DriverVersion = 24.20.11016.4 Win32_VideoController DriverDate = 05/16/2018
[Mojang] Alexander Torstling:Hey everyone! I'm sorry for the inconvenience this has caused. We're now at a stage that we believe most people should have gotten unstuck.
If not, please re-add yourself to I'm restarting that list after this fix.For everyone who was impacted, please start a support case so we get a chance to compensate you.
We will continue to closely monitor the issue in the upcoming days.
How to open a support caseSend an email to Mojang with your Transaction ID, Mojang account email, and any other relevant information, through this form: https://help.mojang.com/customer/portal/emails/new
Refer to this page for wait times on replies.The problem only appears when I log into Realms
C [lwjgl_opengl.dll+0xe92d] Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) J 6303 org.lwjgl.opengl.GL11.glBindTexture(II)V (0 bytes) @ 0x0000000003899c84 [0x0000000003899c40+0x44] J 6478 C2 dde.h()V (10 bytes) @ 0x0000000002f0332c [0x0000000002f03280+0xac] j chw.a(Lchx;)Lchy;+29 j chv.a(Lchx;)Lchy;+31 j chv.b(C)Lcia;+61 J 6337 C2 chv.a(C)Lcia; (76 bytes) @ 0x000000000317eff8 [0x000000000317ee60+0x198] J 6274 C1 cfz.a(C)F (27 bytes) @ 0x0000000003366c24 [0x0000000003366b60+0xc4] j cfz.e(Ljava/lang/String;I)I+161 j cfz.d(Ljava/lang/String;I)Ljava/lang/String;+14 j cfz.c(Ljava/lang/String;I)Ljava/util/List;+3 j cio.a(Ljava/lang/String;I)Ljava/util/List;+6 j net.minecraft.realms.RealmsScreen.fontSplit(Ljava/lang/String;I)Ljava/util/List;+6 j net.minecraft.realms.DisconnectedRealmsScreen.init()V+25 j cio.c()V+4 j cjs.a(Lcfi;II)V+50 j cio.a(Lcfi;II)V+14 j cfi.a(Lcjs;)V+129 j net.minecraft.realms.Realms.setScreen(Lnet/minecraft/realms/RealmsScreen;)V+7 j net.minecraft.realms.RealmsConnect$1.run()V+374 v ~StubRoutines::call_stubName AMD Radeon R9 200 Series Win32_VideoController DriverVersion = 24.20.11016.4 Win32_VideoController DriverDate = 05/16/2018[Mojang] Alexander Torstling:Hey everyone! I'm sorry for the inconvenience this has caused. We're now at a stage that we believe most people should have gotten unstuck.
For everyone who was impacted, please start a support case so we get a chance to compensate you.
We will continue to closely monitor the issue in the upcoming days.
How to open a support caseSend an email to Mojang with your Transaction ID, Mojang account email, and any other relevant information, through this form: https://help.mojang.com/customer/portal/emails/new
Refer to this page for wait times on replies.The problem only appears when I log into Realms
C [lwjgl_opengl.dll+0xe92d] Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) J 6303 org.lwjgl.opengl.GL11.glBindTexture(II)V (0 bytes) @ 0x0000000003899c84 [0x0000000003899c40+0x44] J 6478 C2 dde.h()V (10 bytes) @ 0x0000000002f0332c [0x0000000002f03280+0xac] j chw.a(Lchx;)Lchy;+29 j chv.a(Lchx;)Lchy;+31 j chv.b(C)Lcia;+61 J 6337 C2 chv.a(C)Lcia; (76 bytes) @ 0x000000000317eff8 [0x000000000317ee60+0x198] J 6274 C1 cfz.a(C)F (27 bytes) @ 0x0000000003366c24 [0x0000000003366b60+0xc4] j cfz.e(Ljava/lang/String;I)I+161 j cfz.d(Ljava/lang/String;I)Ljava/lang/String;+14 j cfz.c(Ljava/lang/String;I)Ljava/util/List;+3 j cio.a(Ljava/lang/String;I)Ljava/util/List;+6 j net.minecraft.realms.RealmsScreen.fontSplit(Ljava/lang/String;I)Ljava/util/List;+6 j net.minecraft.realms.DisconnectedRealmsScreen.init()V+25 j cio.c()V+4 j cjs.a(Lcfi;II)V+50 j cio.a(Lcfi;II)V+14 j cfi.a(Lcjs;)V+129 j net.minecraft.realms.Realms.setScreen(Lnet/minecraft/realms/RealmsScreen;)V+7 j net.minecraft.realms.RealmsConnect$1.run()V+374 v ~StubRoutines::call_stubName AMD Radeon R9 200 Series Win32_VideoController DriverVersion = 24.20.11016.4 Win32_VideoController DriverDate = 05/16/2018
is duplicated by
is duplicated by
duplicates
duplicates
[Mojang] Alexander Torstlingduplicates
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
MCPE-19535is duplicated by
duplicates
duplicates
duplicates
duplicates
[Mojang] Alexander Torstling[Mojang] Alexander Torstlingduplicates
duplicates
duplicates
is duplicated by
is duplicated by
duplicates
[Mojang] Alexander Torstlingduplicates
duplicates
is duplicated by
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
is duplicated by
Hey everyone. If you have this problem, please file a support ticket at https://help.mojang.com/customer/portal/emails/new so that we can investigate your realm specifically. We've been unable to reproduce this issue so far.
duplicates
is duplicated by
duplicates
duplicates
duplicates
is duplicated by
is duplicated by
is duplicated by
duplicates
is duplicated by
is duplicated by
is duplicated by
duplicates
duplicates
duplicates
duplicates
is duplicated by
WEB-1188
Normalduplicates
Error message after downloading world from realmWrong Version of Downloaded World
On second thought, you reported this as an issue on PC. Is this correct?
is duplicated by
duplicates
What I expected to happen was:
When I downloaded a world on my Switch from Minecraft realms (uploaded from windows 10 version), to be able to play it.What actually happened was:
Instead, after it downloaded, it goes to a screen saying "A newer version of the game has saved this level. It cannot be loaded", and "unable to connect to world". It won't let me play the downloaded world, even though it lets me connect to the world if I play in the realm and not download it.Steps to Reproduce:
1. Create a Minecraft world in the Windows 10 version of Minecraft on 1.9, exit and save that world.
2. Upload that same world to Realms.
3. Go onto Minecraft for the Nintendo Switch version 1.9 and go to realms. Go to options and select download the realm.4. Select the world you just downloaded from the realm and play it. This is when I'm met with the screen saying "A newer version of the game has saved this level. It cannot be loaded", and "unable to connect to world".What I expected to happen was:
When I downloaded a world on my Switch from Minecraft realms (uploaded from windows 10 version), to be able to play it.What actually happened was:
Instead, after it downloaded, it goes to a screen saying "A newer version of the game has saved this level. It cannot be loaded", and "unable to connect to world". It won't let me play the downloaded world, even though it lets me connect to the world if I play in the realm and not download it.Steps to Reproduce:
1. Create a Minecraft world in the Windows 10 version of Minecraft on 1.9, exit and save that world.
2. Upload that same world to Realms.
3. Go onto Minecraft for the Nintendo Switch version 1.9 and go to realms. Go to options and select download the realm.
4. Select the world you just downloaded from the realm and play it. This is when I'm met with the screen saying "A newer version of the game has saved this level. It cannot be loaded", and "unable to connect to world".
[Mojang] Alexander Torstlingis duplicated by
[Mojang] Alexander Torstling[Mojang] Alexander Torstlingduplicates
REALMS-1706 → 
MC-149600REALMS-1725 → MC-149602duplicates
is duplicated by
[Mojang] Alexander Torstlingis duplicated by
duplicates
[Mojang] Alexander TorstlingFix went out in R18U3, ADO 713672. Looks like the changelog might have gotten lost on the way out, there's a changelog in the PR.
Are you using team prefixes/suffixes or any other username-changing formatting?
Thank you for the crash report, very useful for us.
Judging from the stacktraces you provided, this crash seemingly happens when you are having network problems. When Realms cannot lookup the hostname for the server, it crashes like this. So if this happens, try to verify that your network is working properly. No network problems -> no crash, as far as I can tell from your reports.
Of course, the crash shouldn't happen, and the fix is scheduled for 1.13.1, so hang in there.
@John Do you have the same stack trace? I'm focusing on the crash which mentions "DisconnectedRealmsScreen". This crash is due to DNS resolve issues or other network issues when you try to join a Realm server. I could reproduce this while joining. What are your reproduction steps?
Also, this crash unfortunately cannot be reliably fixed without updating the client. Of course we want to ensure that you are able to play on your realm, so if this is turns out to be a real showstopper we will prioritise it accordingly.
It is also entirely possible that people are having DNS issues, and that this crash is masking those problems. DNS issues can be anywhere on the network, so if anyone who is having this problem with the skills to trace the DNS resolves, please post if you find anything.
The crash in "Minecraft Crash.txt" is identical to the one reported in
REALMS-1116, but I'm not sure how the other file is related. Could you explain?@Jesse Kint I was simply trying to agree with @John that my analysis might not be 100% correct, that DNS issues might be the underlying issue, and that any info on DNS issues from the client side would help. I was not trying to imply that DNS issues are the fault of the users.
I understand your frustration, but let's keep it civil. Surprise, you guys probably know more about this issue than I do, since I haven't experienced it first hand. I'm simply trying to interact with you people to get more information. Given the info you provide in your post (disregarding some portions of it), I realize this might also happen when the server is stuck (edited). So that's good. We'll investigate further. But as far as this crashing bug goes, the specific crash will be addressed in 1.13.1 .
@PappaDavid If the crash report contains the `DisconnectedRealmsScreen` I think we have enough. But I would love to hear if you noticed the server crashing just before this started happening, or anything else which happened up until the point of the problem starting to appear.
@PappaDavid: Thank you. That's valuable information. The fact that the server is stuck thinking that one player is online will prevent Realms from shutting down that server, leaving it open until the next maintenence shutdown. We've seen this problem on occational servers lately. Also the fact that it affects multiple platforms equally is useful.
@deadfish12 your log is also very useful, thank you. Here we can see that it's actually a gameserver connect issue, not a DNS issue.
@Jonas Gamby thanks. I will try to get in contact with one of you who has their realm stuck in this way (one ghost player remaining), so we can have a look at exactly what is going on.
Hey everyone. We're still working on the issue, with some progress. If you are still experiencing this problem, please contact support so we can check your realm specifically. Since the crash happens with in any type of connection problems, we could be dealing with different types of problems here. So please ping support and we'll take it from there.
We had a bug relating to team prefixes, where Realms wouldn't be able to validate the logged in players, causing frequent shutdowns. This has been fixed. Try again and reopen if it still persists please.
Guessing duplicate here, let us know if that's not the case.
Do you have team prefixes configured? If so, did this issue resolve itself lately?
Could you translate the russian message to english please?
Ah, bummer. Sorry about that. Well, if you're comfortable sharing your realm name publically, you may add your realm name here and I'll se what we can do (no promises): https://codeshare.io/GLypMV
Hi! Do you have the same issue if you download the world and play in singleplayer?
Crashing clients on join is
REALMS-1116. Lag and perf in 1.13 is an issue which we are actively trying to solve. Unfortunately the issues are not experienced by everyone, so it's a matter of diagnosing, identifying the perf issues, patch them and release them. 1.13.1 will contain several of them.Since this is not a forum for discussions, as per https://bugs.mojang.com/projects/MC/summary, I'm going to close this bug as duplicate of
REALMS-1116. But thank you for sharing, and rest assured we are working on these issues.Hi! 'FIXING' means that we've temporarily disabled your realm and scheduled it for migration, normally as a consequence of a detected fault in our infrastructure. This should normally resolve in a timely manner. Lost progress is normally not expected in this case. I'm closing the 'FIXING' problem as known, but please open a support case and we can look into your case more closely, especially with regards to the lost progress.
Hi! Please file a support issue for this, so we can investigate further.
Hey everyone! I'm sorry for the inconvenience this has caused. We're now at a stage that we believe most people should have gotten unstuck. If not, please re-add yourself to https://codeshare.io/GLypMV, I'm restarting that list after this fix.
For everyone who was impacted, please start a support case so we get a chance to compensate you.
We will continue to closely monitor the issue in the upcoming days.
Thank for reporting back!
Hello! The crash is fixed now. And most hangs as well. If you are still experiencing getting stuck in FIXING or constant crashing, start a support case or look through the other bugs. Thanks!
Hi Evita! Thanks for reporting, this has been fixed as you can see in the linked issue.
Hej Albin!
Thank you for reporting this. It's been fixed now, checked the linked issue.
Hello! We're trying to fix these issues as we speak. Are you on 1.13 or 1.13.1? Also, please open a support case so we can collect your details and investigate individually.
Please start a support case for this, so we can investigate.
@Vatroslav that shouldn't happen. Start a support case please so we can investigate.
Cannot reproduce on 1.13.1 on PC-1.13.6. I tried with Buried_Treasure and got results. Can you be more specific?
Hey everyone. Each time you restore from backup, a restore point is created. That is why you see an extra entry in the backup list. You should be able to restore from backup, if not contact support and we'll try to help you.
Yes, go to backups. Reopen or file a new bug if you're unable to please.
Hi Melinda. Check the backups pane, that should have backups for your world. If that doesn't work, support is your next option.
Hey Kumasasa! Sorry, I got a bit overzealous there. It's a valid bug, and it was fixed for 1.13.6. Thanks for the report.
Hey! I just want to say it's our top prio right now to fix this for everyone. We don't want people to be kicked because of perf issues, and we're trying to pin those down and nail them. What you say @young chung is interesting, are you suggesting that your realms world is laggy both on realms and after you download it, as opposed to a world which you generate in singleplayer?
@Christopher McElroy Are you able to fly elytra in singleplayer?
@Jansen any more detail? Can you start a support case, then we can jump in and see what's going on...
Where are you located? We're tuning the system and fixing perf issues right now, so please let us know when/if this clears up.
@young chung thank you! Could you start a support case so we can get your details and if you don't mind download the world and try to analyze what is going on? Just mention this ticket and we can pick it up from there.
Please start support cases so we can get your details and work with you to fix this.
Hey Amanda! We've had some problems lately, and the realm might have been affected. Please ask the realm owner to contact us through support to fix, or reset through backups. Thank you.
By the way, can you post the client log? Do you have a customized world?
Hi Zac. I totally understand that it's not just you. But it would help if we could get your realm name and gamertag to investigate. The easiest way for that is through support.
Hello! We've fixed some issues related to FIXING worlds now. Have things improved?
Also, if your world gets borked, you should be able to restore from backups. Have you tried that?
We've found some issues which we fixed now. Are things better?
Hello Elliott! Has this cleared up? If not, please start a support case.
Hi Arlene! I'm sorry about this bad experience. We will address it as part of the fix for
REALMS-339.Confirmed. Thank you for your bug report.
Start a support ticket please.
Hey James!
You are right, this one fell through the cracks a bit. Sorry about that. Can you start a support case so we can get your details and then login to your realm and try to repro if that's OK with you? Thank you.
The 1.13.3 refers to realms version. Minecraft Java is still on 1.13.1. A bit confusing, I know
Hi James,
I mean filling out the form at https://help.mojang.com/customer/portal/emails/new . This bugtracker is public, so its not great for exchanging personal details like usernames and the like. This site it's more for tracking the general problem than for investigating purposes.
Hi Robert!
Thanks for the report. ImI sorry to say that we've had issues with crashing realms the last days, and what you are seeing might be the unfortunate side-effects. Are you able to restore from backup?
Thank you for the update kiddailey. I think we're out of the woods now, but we'll keep tuning the systems and try to fix the tick-lag, which we have also seen sporadically.
Let us know if you run into problems again, and we'll have a look.
Good to hear Amanda! Thanks for updating. IllI close the issue.
Hey Mark. You should have backups on the backup pane, can you check there?
We've had some crashes and lag the last few days. It looks like you suffered the negative consequences of that and I apologize. Right now the majority of those problems should be fixed and numbers are looking up on our side.
If you still have lag, please fill out https://help.mojang.com/customer/portal/emails/new so we can investigate your realm individually. It would help us understand what is going on. Thank you.
This sounds like
REALMS-1100. Are you still having this issue with Realms >= 1.13.4?Are you only seeing this on realms? Can you try downloading the world to singleplayer and test there?
I can close it.
Hello! We certainly care. But we're unable to handle individual cases here, so please fill out a support case so we can look at your problem first hand. We're investigating these issues as we speak.
I'll close it for you
Fixed for Java.
This affected large worlds, and the symptoms were that the restore went through eventually, but you got a timeout message in the client telling you it failed.
This has now been fixed for Java clients.
Bedrock client fixes will be rolled out with the normal release cadance.
Before the Bedrock fixes are out: If you are on Bedrock and get the failed message, click restore of the same vesion again, and the client should resume waiting for the result.
Another temporary workaround is to close the realm before you restore, this will make the restore process a lot quicker and prevent these errors from appearing.
If you can't get it to work, or suspect that your restore is failing for some other reason, don't hesitate to contact support at https://help.mojang.com/customer/portal/emails/new , and we'll be happy to assist.
Resolved September 19.
Hello!
We did have some issues around the time period you describe. We believe this to be resolved now.
If you are still having problems, please contact support (https://help.mojang.com/customer/portal/emails/new) so we can have a look at your realms specifically.
We've had some issues lately with lag and worlds getting stuck like you describe. We believe this to be fixed now. Are you still experiencing this?
Backup restore issues are at least partially fixed by https://bugs.mojang.com/browse/REALMS-1328
Fixed for Java.
This affected large worlds, and the symptoms were that the restore went through eventually, but you got a timeout message in the client telling you it failed.
This has now been fixed for Java clients.
Bedrock client fixes will be rolled out with the normal release cadance.
Before the Bedrock fixes are out: If you are on Bedrock and get the failed message, click restore of the same vesion again, and the client should resume waiting for the result.
Another temporary workaround is to close the realm before you restore, this will make the restore process a lot quicker and prevent these errors from appearing.
If you can't get it to work, or suspect that your restore is failing for some other reason, don't hesitate to contact support at https://help.mojang.com/customer/portal/emails/new , and we'll be happy to assist. We're unable to handle any individual cases here in the bug tracker.
Can you check if this is reproducable in the standalone Java server please?
Hello! The way Realms work, is that we take a backup everytime the server stops, including crashes. So this means that the backups might be an effect, and not the cause.
Crashes can have multiple causes, so please contact support (https://help.mojang.com/customer/portal/emails/new ) , so that we can have a look at your realm specifically.
Marked this one as a duplicate, even though this one was earlier than the issue it duplicates. This since the other issue was the first one we got in the Realms project.
Hi Suzanne. I've marked this one as a duplicate with regards to the difficulty setting not biting. Are you still experiencing the crash?
Thank you Scott for doing that. We'll investigate.
Hello Jon-Jacob! The crash log you posted looks like https://bugs.mojang.com/browse/REALMS-1116, which a lot of people had for a while. But the chunk-related crash sound like a different issue. Do you still have that corrupted world? If so, can you reproduce the issue in singleplayer? That would most lineli give you a more detailed crash report.
"The uploading bug" - which uploading bug?
Hey Carl. Thanks for checking back in. We're trying to nail these issues down, but unfortunately 1.13 changed the perf profile significantly, and we're not quite there yet. Chunk loading, flying fast and entering areas with mobs produces some high-latency ticks, which are more noticable on Realms, we're aware of that. We might have to wait until the next game release until we get it completely solved, but we still have a couple of tricks up our sleeves that we're going to try in the near future.
Hey Bryan! Did they fall? Could it be https://bugs.mojang.com/browse/MCPE-38374 ?
Hey. I'm sorry about that. Is it working for you now? We had some issues during this time that you are reporting.
Hello everyone. We're actively working on this problem and the fix is in testing at the moment. We will try to get it out as soon as possible.
Hey everyone. This problem currently happens when launches happen at different times on different platforms due to different store procedures and such. We have a better and more permanent solution in the pipeline, which will stop this from happening altogether. But that fix will earliest be out next update. In the meantime, we are trying to keep these out-of-synch problem to a minimum. So expect this to happen for a couple of days around updates until the long-term fix is in. We realise that this is a major inconvenience and are working on fixing this ASAP.
Is this resolved now? There are backups available in the backups tab of the game client. Have you tried those? Upload will be blocked when the Realm is in "FIXING", but this should resolve itself within the hour. After that, you should be able to upload manually or by using the backups built into Realms.
@Shawn Royal This works if the disk format is compatible between releases. Feel free to try it if you make a backup. But it might break if the format has actually changed. That doesn't usually happen with minor updates, but it might.
What we are doing in the permanent solution is to version the disk format separately. That would allow different versions of the game to load the same disk data as long as the disk format is compatible.
Hey @orlacien . This can be a sign of world corruption and some other failure states. Could you start a support case please? Then we can have a look at what is happening in detail.
Could you start a support case please? Then we can have a look at your realms specifically.
Please start a support case so that we can have a look at your specific case. https://help.mojang.com/customer/portal/emails/new
Unfortunately there is an active gameplay bug which can mess up spawning in certain scenarios. I recommend using the backups functionality built into realms to restore to previous states if this happens. https://bugs.mojang.com/browse/MCPE-38374
Could you please start support cases so we can investigate this more thoroughly?
Hi Marla. Please start a support case here so we can investigate further.
Backups are not kept for a year, they are kept for three months. Unfortunately, the backup list is not updated until you interact with the Realm, so it happens that you see old entries which are in fact already effectively gone.
Hi everyone. We have seen this happen to a few worlds which got corrupted during a system failure. If you have this issue, please file a support ticket here so that we can investigate further. If you want to try, please try to restore to an earlier backup and / or just try a fresh world and see if that resolves the issue.
This is most probably due to the world using a "customized world" generator, which stopped being supported by the main game in 1.13 . You can download the world to singleplayer and run the conversion there, and then upload the world again. The conversion is somewhat lossy, but works OK.
If you want support, please file a ticket here and you can get personal responses.
I can tell from the screenshot that this clearly isn't Realms we're talking about /s. On a serious note, please file a support ticket here so that we can take a look. What happens if you dowload the world and try it in singleplayer? Same problem?
We're investigating. There is a timeout of 10s which should prevent ghost users from locking you out. In this case it seems as if this has failed. As a workaround, the owner can close and re-open the realm. This resets the user list.
Come to think of it, did you verify that you didn't have the old app running in the background still?
Which version of the game are you playing? PC-1.14 isn't released yet, and isn't supported on realms.
Hi everyone. We did a major perf overhaul during the fall, and we believe that it's a lot better now. Have any of you noticed improvements?
Hi John, yes that's the one. https://help.mojang.com/customer/portal/emails/new
Hi @orlacien, please use the form here: https://help.mojang.com/customer/portal/emails/new
@Gan thanks for troubleshooting it a bit. @Anders This might happen when the server starts, but fails to accept connections. We're working on detecting this type of failure better and correcting it. Is this error reproducible for a given resource pack? It would be interesting to see if we can reproduce it and find the root cause.
On second thought, if you're not using datapacks, this should definitely not be happening. We did have issues with the uploading functionality on PC beteen december 11 and 14. Is it working for you now?
Please start a support case here: https://help.mojang.com/customer/portal/emails/new
I forgot to ask: is this still happening for you? On Dec 11-13 we had some uploader issues, but in November I have no registered issues.
We have scheduled work for improving downloading of large worlds. Right now, some Bedrock clients can't handle more than ~1.4 GB before crashing. Our ambition is of course to support arbitrarily large worlds, and we'll make sure to fix this. In the mean time, if you can't get a hold of your large world, please start a support case at https://help.mojang.com/customer/portal/emails/new and we can assist you.
Great! @Foxy No-Tail : can we close this issue then?
We couldn't reproduce. Please contact the support as Mega_Spud suggest so we can get more info on this specific case.
Update: We investigated some support tickets (thanks for reporting!) and we found a bug which resetted some worlds, if the world had originally be created from a map (an adventure, experience, inspiration or a world template). We're sorry about that. This has now been fixed. Please restore from backup if this has happened to you.
:thumbsup:
If this happens to you, remember that Realms automatically takes a backup every 30 mins of play. So even though this is a very annoying bug, you can at least restore to a recent backup.
Please contact support here: https://help.mojang.com/customer/portal/emails/new
Please contact support here: https://help.mojang.com/customer/portal/emails/new
Confirmed. Thank you for the bug report. It's been added to our backlog.
We believe that we have fixed the general performance issues related to the update aquatic, so if you are still having these issues please file a support ticket at https://help.mojang.com/customer/portal/emails/new so that we can have a look at your realm specifically.
Closing this ticket. Please re-open if you disagree.
Our testers couldn't reproduce this bug with exploratory testing. So if you can reproduce this, please write here what the repro steps are.
Hey everyone. As far as we are aware this bug has been resolved. If you find any resource packs which aren't working properly, please list them here. I'm keeping the bug open until we've been able to verify the packs you guyls are using.
Ok cool. To add some context, we have noticed that our parsing of the resource packs is stricter than the parsing done by the game itself in some cases. This is by necessity. We are however planning to add better error messages for that, and will make sure to double-check that official packs are compliant. So if anyone finds a pack not working, please let us know.
Hey @GTARPS. We tried your refrigerator example and managed to upload it just fine. We also tested various custom packs from sites around the net and all the ones we tried were successful.
There is one caveat, however. If you have uploaded a custom pack previously, you need to bump the version or change the uuid for the changes to be visible in Realms. This is true across all realms globally, so if you re-upload the same version, any changes will be ignored. Could this be what you were hitting?
I will close this bug for now, and urge anyone with a similar problem to check the versioning and the format of your manifest. If you still have a problem, please register a ticket at https://help.mojang.com/customer/portal/emails/new and we can investigate on a per-realm basis.
Confirmed. Added to backlog. Thank you for the bug report.
We have been able to reproduce this problem and are looking into it. Stay tuned.
Oh, and if you have this problem, please hold on to a pre-1.9.0 version of the world. We're yet to figure out whether this bug is destructive or not.
This should not be possible (TM). We did have a glitch in the menu system so that you could click item 2 and connect to item 1. This should be fixed in 1.14.13. Are you still seeing this behavior? If so, please file a support ticket so we can investigate your specific case: https://help.mojang.com/customer/portal/emails/new
Hi David. I'm sorry to hear that. Could you contact support at https://help.mojang.com/customer/portal/emails/new and provide your details there? This way we can investigate your issue directly.
Thanks for diagnosing this error. We'll take a look at this. BTW, does the log contain more info than the 500 screen?
Are you still seeing this? We had a service disruption during the timeframe that you mention, which should have been resolved now. I apologize for the inconvenience.
Re-assigning to MC since gameplay-related.
Reassigning to MC since gameplay-related
Do you mean that the narration is interrupted even though nothing else is being narrated instead? Can you give me an example?
Are you on Windows? 1.11.0 looks a bit old, is it Minecraft 1.14?
I'm sorry to hear that Ronald. Can you please verify that you are using realms 1.14.13 by looking in the log?
If this is the case, this popup depends a lot on your account status. Things like if you have purchased realms, a realms trial or neither, if you have your own realms created or they are yet to be created, if you are invited to other realms and so forth.
Screenshots and/or relevant details would help.
If you would prefer, please create a support ticket at https://help.mojang.com/customer/portal/emails/new and we can continue the discussion in person.
Assuming duplicate, please reopen if this is not the case.
You should be able to invite players although the feed is disabled. If you cannot, can you please clarify why?
Hi Dave. Sorry to hear about your issues. The easiest way to proceed is it you contact support at https://help.mojang.com/customer/portal/emails/new . This way we can verify your ownership and proceed to check logs and interact with your world to figure out the problem.
Hi Dave. Everyone gets one of those auto-responses. You should hear back soon enough if you follow the instructions at the bottom.
Assuming duplicate, please reopen if this turns out to not be the case.
Do you have an example world with datapacks to test?
Thank you, could repro. Will schedule.
Hi Dave, please fill out the support form at https://help.mojang.com/customer/portal/emails/new so we can have a look at this.
A fix is on the way. Another temporary workaround is to modify the world zip by re-zipping any datapack zips inside it which have become folders.
Serverside fix, live as of now.
Serverside fix, live as of now
Hi Levi. Since this is a generic error, it's very hard to tell what is wrong without having access to the world which is causing this problem. Could you please create a support ticket at https://help.mojang.com/customer/portal/emails/new so we can verify ownership and check you realm specifically?
FYI this feature is in preview for blocks starting with version 1.21.0.21