Tested; I'm still seeing an animation when I pick up an item, but it is very quick and the animation stops before its completed. I'm not experiencing this at all with XP orbs.
Overwatch C-17: "confirmed" in comments means that that person has experienced that bug in an updated release. "Confirmed" as as a status on the bug itself (up there at the top, with "assigned to," and all the other bug info), I'm guessing is that someone in the Mojang team has duplicated the bug successfully as part of their workflow and will get around to assigning its fix eventually. Not that I think 400 bug testers need to each leave a "Confirmed for v123" comment, but you'll see it on any bug that's been around for more than one version.
If you're quick about it, the world is recoverable if it is reopened after a crash, the game is immediately paused and the difficulty is changed to Peaceful. crash-2018-12-15_21.30.30-server.txt
I've had it happen, so far, with villagers, iron golems, tame cats, illagers, llamas, horses, pigs and sheep. It results in the game being unplayable for a while until (if) they reappear. Just don't go killing them when they pop back up if they're villagers, not unless you want crap reputation.
New village, trading as usual and over time, all villagers were similarly affected with no negative actions toward them. Out of curiosity, went looking in villages.dat and it looks like the player settings (reputation, UUID) have disappeared. Occasionally, it will reappear but I've not been able to figure out when this happens and when it doesn't.
To clarify what I said above regarding player data inside villages.dat:
I was inside an active village when I checked villages.dat, in a world that I'd created in 19w05a about two hours before, and I'd not left the village since entering it. I'd not visited any other villages and have not traveled outside of this village's chunks. I'd successfully traded with villagers as normal (without trades being immediately disabled at first attempt) earlier in the day, and had not done anything to negatively affect reputation. I'd had this issue in my main world (combined with a different bug; entities become invisible), so when I noticed it happening again in this new world I checked villages.dat. There was no player data (i.e., 0 players, so no UUID, no S). I have a habit of rebuilding villages so I spawn new villagers periodically to test trades; when I noticed trades functioning normally again I checked villages.dat again and it had an entry for Players (1 entry, UUID = mine, S = a positive #). All villagers that I trade with when this happens are affected, and those affected villagers remain locked. I don't know if this is a separate bug or not, but it does seem to have some relation at least in my experience.
I couldn't begin to come up with a use case though because it doesn't seem like I'm doing anything reproducible when this happens.
Kutzee, that's true. That isn't the main issue of this bug, though; fences and various other blocks can be waterlogged when placed in water or when a water bucket is used on them. Barriers and some other blocks that should be cannot be (for example, anvils should be able to be waterlogged. I don't particularly agree that all blocks should be able to be waterlogged, but some definitely should be.
I haven't seen this happen in a game-crashing sense for about a year now. Still happens occasionally but not on that scale and not enough for it to feel like a bug.
@camden solved this. Anyone having this issue, try what they suggested: On the login prompt in the java launcher, go back. You'll see the mojang account you had been signing into - ignore it, and add a new account to the launcher. Using the email address associated with the microsoft account you just migrated to, sign in with the email address and password of your microsoft account. It's not an elegant migration on the UX side of things, but it does work.
I am experiencing this on Windows version 2.3.211. The update downloaded, but the update message persists. The last time this happened, the issue resolved on its own with the next update.
Win10 Pro, 21H1, OS build 19043.1706, experience pack 120.2212.4170.0, though I'll be updating to the next tonight.
Have tried restarting the launcher; loading an installation, quitting and loading again; disabling hardware acceleration, restarting the launcher, re-enabling hardware acceleration, restarting the launcher; and rebooting. I then disabled the beta version, restarted the launcher, re-enabled beta (which brought the message back immediately), restarted the launcher (which downloaded the beta file again), and the message will not go away after that. The game's still playable just fine. The only (very) minor annoyance is having to close it to get out of What's New.
neewom
MC-67468
Tested; I'm still seeing an animation when I pick up an item, but it is very quick and the animation stops before its completed. I'm not experiencing this at all with XP orbs.
Confirmed. Breaking any double-tall plant (i.e., double-tall grass, peony, rose bush, lilac, large fern) briefly shows the image of a sunflower.
Doesn't apply to cactus, and only happens when block is broken by punching the lower half.
Oops. Searched for everything but "bryce," it seems. Thanks!
Overwatch C-17: "confirmed" in comments means that that person has experienced that bug in an updated release. "Confirmed" as as a status on the bug itself (up there at the top, with "assigned to," and all the other bug info), I'm guessing is that someone in the Mojang team has duplicated the bug successfully as part of their workflow and will get around to assigning its fix eventually. Not that I think 400 bug testers need to each leave a "Confirmed for v123" comment, but you'll see it on any bug that's been around for more than one version.
No and, in addition to that, increased the load with various visual settings and everything seems fine.
Thanks!
If you're quick about it, the world is recoverable if it is reopened after a crash, the game is immediately paused and the difficulty is changed to Peaceful. crash-2018-12-15_21.30.30-server.txt
I've had it happen, so far, with villagers, iron golems, tame cats, illagers, llamas, horses, pigs and sheep. It results in the game being unplayable for a while until (if) they reappear. Just don't go killing them when they pop back up if they're villagers, not unless you want crap reputation.
New village, trading as usual and over time, all villagers were similarly affected with no negative actions toward them. Out of curiosity, went looking in villages.dat and it looks like the player settings (reputation, UUID) have disappeared. Occasionally, it will reappear but I've not been able to figure out when this happens and when it doesn't.
I'm on 19w05a.
To clarify what I said above regarding player data inside villages.dat:
I was inside an active village when I checked villages.dat, in a world that I'd created in 19w05a about two hours before, and I'd not left the village since entering it. I'd not visited any other villages and have not traveled outside of this village's chunks. I'd successfully traded with villagers as normal (without trades being immediately disabled at first attempt) earlier in the day, and had not done anything to negatively affect reputation. I'd had this issue in my main world (combined with a different bug; entities become invisible), so when I noticed it happening again in this new world I checked villages.dat. There was no player data (i.e., 0 players, so no UUID, no S). I have a habit of rebuilding villages so I spawn new villagers periodically to test trades; when I noticed trades functioning normally again I checked villages.dat again and it had an entry for Players (1 entry, UUID = mine, S = a positive #). All villagers that I trade with when this happens are affected, and those affected villagers remain locked. I don't know if this is a separate bug or not, but it does seem to have some relation at least in my experience.
I couldn't begin to come up with a use case though because it doesn't seem like I'm doing anything reproducible when this happens.
Kutzee, that's true. That isn't the main issue of this bug, though; fences and various other blocks can be waterlogged when placed in water or when a water bucket is used on them. Barriers and some other blocks that should be cannot be (for example, anvils should be able to be waterlogged. I don't particularly agree that all blocks should be able to be waterlogged, but some definitely should be.
I haven't seen this happen in a game-crashing sense for about a year now. Still happens occasionally but not on that scale and not enough for it to feel like a bug.
@camden solved this. Anyone having this issue, try what they suggested: On the login prompt in the java launcher, go back. You'll see the mojang account you had been signing into - ignore it, and add a new account to the launcher. Using the email address associated with the microsoft account you just migrated to, sign in with the email address and password of your microsoft account. It's not an elegant migration on the UX side of things, but it does work.
I am experiencing this on Windows version 2.3.211. The update downloaded, but the update message persists. The last time this happened, the issue resolved on its own with the next update.
Win10 Pro, 21H1, OS build 19043.1706, experience pack 120.2212.4170.0, though I'll be updating to the next tonight.
Have tried restarting the launcher; loading an installation, quitting and loading again; disabling hardware acceleration, restarting the launcher, re-enabling hardware acceleration, restarting the launcher; and rebooting. I then disabled the beta version, restarted the launcher, re-enabled beta (which brought the message back immediately), restarted the launcher (which downloaded the beta file again), and the message will not go away after that. The game's still playable just fine. The only (very) minor annoyance is having to close it to get out of What's New.