Duplicate of MCPE-236811
Duplicate of MCPE-236811
Duplicate of MCPE-236811
I can confirm that the crashes and other Add-On related bugs have been fixed in the 26.2 Update. Both Singleplayer & Realms are back up and running. Thanks for the fix!
Duplicate of MCPE-235929
I’m experiencing this as well however my issues started when my game updated to 26.1
This has affected both my singleplayer and Realm worlds.
Got my game fixed by doing another partial uninstall. Glad I didn’t have to change the file paths this time.
Remember to make regular backups of your com.mojang folder so you don’t lose everything!
Update: My Realm has now become unplayable (again)
Feels like the Realms Outage of 2024 all over again but with servers, personal worlds and multiplayer LAN games included.
For me, this issue first appeared in the 1.21.122 Hotfix and it’s only affecting my singleplayer worlds. (And in some cases, the ability to connect to servers)
Realm worlds are immune to this issue and are still accessible, likely because their files are stored in the Cloud. This is the case with the 2 player Realm which has my main world uploaded to it. I’m still able to access and play that world as if nothing ever happened.
At first, I thought the issue was being caused by a corrupted file inside one of my addons but when I went to create a new world with nothing applied to it, the game crashed in the same way it did with my existing worlds.
I was able to fix the crashing on 1.21.122 through a partial reinstall of the game followed by a bunch of tweaks to the files so the new install could read the data from the original com.mojang folder. This worked for an entire 3 days until 1.21.123 came out.
Now I have to do it all again (Unless I want to wait an unknown period of time for the next update to come out)
This is an issue that is rendering the game almost unplayable.
Invalid is not an acceptable answer
This issue is also present in older worlds like mine.
I tried to use the command and it said the closest chamber was in an area generated prior to the Caves & Cliffs updates meaning that when I dug down, there was nothing except a couple of caves and a Stronghold that was found ages ago.
Here's what I think is happening:
Instead of checking where the nearest Chamber is within the world's actual loaded chunks, it appeared to be getting coordinates straight from the world's seed data without checking what has already been generated in versions prior to the 1.20 Trails & Tales update.
Again, this a clear duplicate of MCPE-123448 so link it to that ticket
Also, stop asking for info I can't provide. The world is on a realm and the only seed I can find with any relation to this world is from 2012 when the world was first created with MCPE 0.5.0 Alpha
It's a clear duplicate of MCPE-123448 so link it to that ticket
Load a world in Peaceful Mode (Can be either Creative or Survival) and allow some time for mobs to spawn
Find a Wolf or Fox but do not interact with it in any way. Just be sure to stay within its spawn region
Wait for a Sheep or Chicken to spawn in the same area as the mobs mentioned above
When a Wolf sees a Sheep, its eyes will turn red as if it was attacked by the player then chase and jump on the Sheep until it dies
If a Fox sees a Chicken, the Fox will attack the Chicken until it dies then run away, taking the dropped piece of Raw Chicken with it
What should be seen is the opposite where Peaceful Mode is what it's meant to be, Peaceful with no hostility whatsoever
For me, this issue has been slowly worsening with larger areas of ghost chunks and lag spikes
Issue still exists on 1.21.44
This one may be the result of reusing a sign with NBT Data from the Overworld and editing it in the Nether
Just got the 1.21.41 update and can confirm that the Tuff Blocks are now where they belong. Thanks for fixing this and the copper doors as well.
Thanks for the reply. I was able to force an update by loading my realm on my iPad which is running 1.21.30 and now everything is working.
Although I didn't need to do it this time, I'll certainly be keeping your tip in mind for the future
This is a GENUNINE issue
Fix it now. We already had the August Realms Outage and don't need more
FIX IT!!!!!
This is what happens.
Even when I opened the game on 26.2 and the 26.3 update automatically installed, the same crash sequence happened.
CPU: Intel Core i7 10th Generation
GPU: Nvidia G-Force RTX
Also, I’m using the standalone version of Bedrock which doesn’t require the MC Launcher.
Forgot to put that in the original report so I’m adding it here.