Isak Osman
- iska
- iska
- Europe/Stockholm
- Yes
- No
I have not been able to reproduce this, but earlier I was fighting a skeleton by hitting it with a gold sword, it approached me, I hit it again and my gold sword ran out. Instead of the skeleton taking damage, it started firing arrows at me like a machine gun. I'm talking about 5 arrows a second.
Obviously I died, and I couldn't reproduce it. Could someone please look into this?
The world also no longer shows in the world selection menu, so I'd assume it went corrupt when I quit.
I have come across a serious crash issue with Minecraft Pocket Edition's new update/s (0.6.0/0.6.1).
I believe this is an issue with performance, although my phone actually mostly performs better than Minecraft: Pocket Edition on my tablet, on which the game never crashes.
When I load up large worlds (E.g. Isak_01, a city world, structures take up about 90% of the world), whether I am on Fancy Graphics or Low Graphics Quality, after playing in the world for a few seconds (with a VERY low framerate), my phone freezes. The phone does not respond again unless I take out the battery and put it back in again.
NOTE: This is a common crash. Only reproduce-able in large worlds.
Please respond, someone, and please fix this problem for the next update.
[Android 2.3.6 GINGERBREAD] Serious Crash on HTC Google Nexus One
I have tried this too - it has the potential to link with world issues (whether THEY have been modded or they are corrupt. I have an idea of what this is now, but Aron and Johan, you guys are the devs. Try it, it happens when you have more than one saved world for me. (ONE of the worlds do not have a name)
No, Sabin, the issue here is the fact you'd NEED to do that in the first place. Johan has fixed it, anyway.
Maybe this is entirely a framerate/performance issue?
I do say! This is a familiar bug! You'll find this bug has been present since the first version (0.1.0) of Pocket Edition!
I've experienced this bug before. I run Android 2.3.6 GINGERBREAD on both my Samsung Galaxy Tab P1010 and on my HTC Google Nexus One and I can confirm that this bug is uncommon however not biased. Great report, M.J!
They should normally come with the feature :/