mojira.dev

All_Out_Savage

Assigned

No issues.

Reported

MCPE-167595 Pistons can not be broken fast with a pickaxe like in Java Edition. Duplicate MCPE-158591 All worlds report "there was a problem loading this world". Duplicate

Comments

Thank you for checking that. Just out of curiosity, what do you think made it stop working? I looked at the source files for 1.0.0 and 1.1.5 and can't see much of a difference. Most likely client side desync but im unsure 

Like the person below me said. this was working in older versions of the game before it just stopped one day. It seems like this could be caused the same way it was in java, just desync between the client side camera and the server side calculation that tells the camera the x y z of the attacking mob/player

This issue is fixed as of the release of 1.20 yesterday 

Confirmed in beta 1.20.0.23

It has come to my attention that mojang could add this to the game by manipulating the "setCameraShake" attribute with the posistion of the player and the attacker. It can determine if the attacker was north or north west of you and apply a shake to the player's  camera in the opposite direction.  I kinda don't know what I'm talking about though. I made a data pack to show this off. I have also attached new videos 

Beta 1.20.0.21 also shows no signs of this issue 

 This would be so nice for accessibility reasons. Imagine if they also added vibrations on controllers that would vibrate one side more than the other depending on where the damage is coming from. Also this is still present as of the 1.20.0.21 beta

Affects 1.19.70 and 1.19.71

Can confirm on ps4/5 and windows

This also effects minecraft on my pc and phone. The outline of the inventory slot overlaps the stack number. It seems something made the numbers shift down and to the left by two pixels 

These 6 steps restored my world so I thought I would share the fix

 

 

 

1.If your world is on console you will need to buy a realm and download the world on a computer 

 

 

 

2to to C/Users/(you're username)/app data/local/Packages/Microsoft.minecraftUWP/localstate/games/Com.mojang/minecraft worlds/

 

 

 

3.Find your corrupted world, open it and find the db folder

 

 

 

4.Locate the MANIFEST-xxxxxx file and copy the name (not the file)

 

 

 

5.Open the CURRENT file with a text editor such as Notepad++

 

 

 

6.Delete everything in the file (not the file itself) and paste in MANIFEST-xxxxxx

This issue is not as bad as it was 2 months ago. I can load most of my worlds now. However after I exit the world, it can only be loaded one more time. The (There was a problem loading this world) message appears again. To counteract this I must make a backup of the world on a USB drive and re-download it on my console. I have to repeat this process every time I save and quit or the world is lost. This doesn't always work so I keep some backups on my computer 

1.19.10 has made this issue change. I am now able to load smaller worlds (under 500 mb) it seems  the issue that effected playstation in 1.18/1.18.1 has come back the exact same way it was in https://bugs.mojang.com/browse/MCPE-149193 I have attached new screenshots 

the release of 1.19 has not solved this issue for me. It actually seems to have made it worse. I can enter the nether just fine. I just can't leave unless I jump in lava. Once I respawn in the overworld everything is fine for about 30 minutes until the game crashes and the file is unable to be loaded.