karadine
Assigned
Reported
Comments
duplicates MCPE-125872
Well then if its happening in single player, it is far less common (and maybe we're talking about separate bugs). But to expand on my point, if developers are not SPECIFICALLY investigating this and are just doing a couple courtesy tests in single player, then they need to radically ramp up their investigation. Since it happens more on realms, then latency might be a factor, and since devs work locally and on high-end equipment typically, they probably cannot recreate it.
This bug is a pain point exactly because it happens on realms, where players often are guests. It destroys their armor instantly, which can represent a lot of work especially on a realm. What I'd like to be hearing is for devs to be asking players for specific realm names and times so they can crunch logs. Or set up a realm for people watching this bug to connect to. Load spawn with some diamond armor, enchant books, and a nether portal and they can watch it happen live.
This bug has only ever been happening on Realms. Prior comments make that crystal-clear.
NOT fixed in 1.4 . Why exactly is this bug marked as fixed EVERY new release, and yet it never is fixed. Is this just a method of closing bug reports without actually addressing them?
Pulling back your bow, then switching off it without firing seems to cause this bug.
You can correct it by going back to your bow and firing it, or relogging.
Pulling back your bow, then switching off it without firing seems to cause this bug.
You can correct it by going back to your bow and firing it, or relogging.
I was experiencing this in 1.2.9. I have two XBL accounts, and one of them was constantly crashing Minecraft. Specific actions which caused this crash:opening Store, opening chat/command line, alt-tabbing. Other account worked fine as always. I tried removing DLC, worlds, and also fully uninstalling. Those steps didn't resolve it.
On the account that was crashing, I noticed that my custom gamerpic had been removed from my profile. In the XBL app and web profile, my picture was a blank default icon. I changed by gamerpic to one of the standard ones. I confirmed the new pic was active in the XBL windows app, and web profile. After this, Minecraft worked fine.
I suspect that MS removed my gamerpic for some reason, and this cause a null-response from XBL to Minecraft when my gamerpic was requested. Minecraft was crashing on any screen where my gamerpic would be visible.
If you're crashing and try this, please reply either way if it works or doesn't work.
Still happens in 1.2.1. Died wearing full set of unenchanted iron armor with no potions.
https://bugs.mojang.com/browse/MCPE-19535 needs to be reopened. It was NOT resolved.
If it isn't intended behavior, then it should be. In the real world, if the observer is near the equator, they would see the moon's crescent as parallel to the horizon much like it is shown in-game. Its only at northern/southern latitudes that the moon appears angled against the horizon.
Since the game world is flat, and the sun's zenith is the midpoint directly above, then the moon would appear like at the equator.
A bigger inaccuracy would be related to the moon rising at the same time every single day, but It makes sense that players need a visual means of telling the time. As such, it should appear as a full moon every single night if it rises at the same time as sunset.
Confirmed. Happening on Windows 10 edition as well. New bug as of 1.1.x
Walking on any block adjacent to (same y-level as) lava sets the player on fire.
Example: Seed #1723257520. Bonus chest spawns at -189, 9, 35
Bug seen on Windows 10.