Bees do not stop being angry after being angered.
Harvest hive with shears or bottle without having a fire underneath it.
Bees get mad.
Leaving area or hiding does not stop the bees from being angry, even after multiple full in-game days.
Game on default hard settings, no mods.
I’ve lost two generations of bees so far. Is this expected behavior on hard mode now?
Linked issues
duplicates 1
Comments 7
Thank you for your report!
We're tracking this issue in MC-305388, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
@ManosSef I did see that the other issue was marked as resolved. Which is why I made a new issue for it. Since it’s not a duplicate if it’s an issue of a previously fixed issue. That would be a new issue, not a duplicate.
When/If it continues to happen I’ll be making yet another issue for it since you’ve marked this issue as resolved. Issues that are still issues are not resolved issues.
The issue is actually resolved, but in the snapshots for 26.1. You are playing in 1.21.11, where obviously it won’t be fixed, since versions cannot be retroactively patched. If you had followed my advice from the previous comment:
Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
… this misunderstanding would not have happened.
How ironic. You think I’m having trouble reading when you didn’t read my comment saying I saw that.
Snapshot may fix it, but I still don’t see an update on my game. So no, the issue isn’t fixed. “We’ve got a patch coming out to fix it at an indeterminate point in the future” is different than “it’s fixed, here you go!”
I even downloaded an update not two days ago, after this alleged fix was marked resolved. I see the wiki and everyone else talking about the new version numbering for 2026 Minecraft updates and yet here we are. In March. With the release version still being not that.
The "Fixed" resolution on the bug tracker literally means "this issue has been fixed in a version of Minecraft that may or may not be released to the public yet, and may or may not be a release version." Unfortunately, there is nothing else that can be done about this issue since it has indeed been fixed, and the full update that fixes it will come out at some point near the end of the month (if last year's release pattern is to be continued).
I did, in fact, read your comments before replying. I didn't, however, think you would be under the impression that you should already have an update that fixes this issue, and I do admit that what the "Fixed" resolution means on the bug tracker is poorly documented anywhere. I didn't intend to start any arguments here; I was just trying to explain the situation, as from your previous comments it looked like you hadn't understood what version the fix is supposed to be coming in, but the actual misunderstanding was about what it means for a ticket on the bug tracker to be resolved as Fixed.
So, to clear this up: This issue will be fixed in 26.1. On this bug tracker (in the MC project only), Mojang resolves issues as Fixed before there is an actual public version fixing them. The "Fixed" resolution does not mean "it's fixed, here you go," it means that a snapshot and eventually a release that fixes an issue will be coming out in the future. It might be confusing sometimes, but sadly this is just how the system works here.
As far as version numbering is concerned, Java Edition is still on 1.21.11, which was released in 2025, before the new numbering system. This is not the place to talk about this topic, however.
Duplicate of MC-305388