Agent Allspice
Assigned
Reported
Comments
I really wish somebody from Mojang would pipe up with a comment about impact of this error on various platforms. It looks like private server Bedrock players can not play at all. What is the work around for that user base?
For Minecraft PE players on their device's local worlds seeing this error, what is the impact? I can launch the Minecraft IOS app. I can open a saved local world but I see this error while the world loads. Appears I can interact in the saved world after it opens. Can a world be permanently corrupted by this error if played?
While I'm seeing possible workarounds for Bedrock, I see nothing suggested for PocketEdition for IOS or Android.
How to do a reinstall of the app without deleting previously created worlds for IOS / Android?
While IOS users (at least this user) is seeing this error, the error does not crash the application like it seems to be doing for Bedrock private servers. If I play on my saved worlds, what risk does this error pose for the future stability and playability in these saved worlds? I have not been playing any world where I've invested any time and effort because I don't want to lose all the work I put in.
Any suggestions? Can I play on my old worlds without risk? Is there an IOS manual back up and restoration process for saved worlds so that I can attempt a reinstall?
Issue persists on iOS hotfix version 1.20.72
Edit: should say that issue persists in both new worlds and previously generated worlds dating back before the v1.20 releases.
The following settings changes restores, partially, old D Pad behavior. This does not solve smoothness of game play using the UP / DOWN / LEFT / RIGHT buttons, but does return screen interaction to optimize for touch over a joystick optimized block interaction
Go to Settings, then select Touch, then configure as follows:
Control Mode: D Pad and Tap to interact selected
Customize Controls (Experimental): 0
Camera Sensitivity: 60
Spyglass Damping: 50
Auto Jump: 1
Mobile menu size: 50%
Vibrate When Break Blocks: 1
Vibrate When Splitting Items: 1
Delayed Block Breaking (Creative Only): 1
Invert Y-Axis: 0
Split Controls: 0
Swap Jump and Sneak: 0
Touch only affects hotbar: 0
One other source of frustration is that the demo video in Settings > Touch for the D Pad shows the type of controls desired, but the delivered controls with the D Pad setting selection are different from what is shown on offer.
I can't play the game as is. Definitely not able to fight / swim and struggle to control block placement and destruction.
Screen shot of preferred D Pad controls from settings demo vid.
[media]This isn't an issue only in new worlds, I'm seeing this issue when opening a long established world. Abandoned Village seed.
This is happening to me on Minecraft PE v 1.19.63, on iPhone 13, iOS 16.3.1.
Steps for me:
My generated world, on my local iPhone, Survival mode, Difficulty Normal, based on seed -1968188527
Have long established Portal
I try entering portal
I see "generating terrain"
Before the nether resolves, I hear sounds of taking hit damage
I die in the Portal, my stuff is scattered on the lip of the portal in the overworld
My multiplayer guests also experience the same behavior.
Hi, since the major Caves and Cliffs update, I have not experienced this issue.
Finally captured an error message, see pic.
Currently on MC PE version 1.16.201
That response from Mojang support provided by DeadlyPark is troubling. I'm experiencing this issue on a vanilla iPhone 13, device not jailbroken, latest version of iOS v17.4.1. User profile set to English on the US app store. No private server. No linux. The worlds where I see this issue are local to on my device and saved to iCloud per the usual application installation and backup for an Apple user. You can't get any more straightforward than my set up for an Apple user. These days, I'm not even playing multiplayer, although those worlds have had other MC players in them a long while ago.