Using /damage to force a Guardian or Elder Guardian to attack another of the same entity type crashes the game instantly. This bug has been present since at least 1.21.90 and remains unfixed in 26.3.
Steps to reproduce:
1. Create a new world with cheats enabled
2. Summon two Guardians/Elder Guardians
3. Use name tags to rename them "a" and "b" (or any distinct names)
4. Execute the damage command:
/damage @e[name=a] 1 contact entity @e[name=b]
5. Game crashes immediately
Expected result:
The Guardian named "a" should either:
Not attack the target (if the target is considered invalid), or Perform the attack without causing a crash
Affected Versions:
1.21.90 (2025-07)
1.21.94
26.1
26.3(now)
Platform: iOS18 and iOS26, Android 14, Minecraft Bedrock Edition
Linked issues
Comments 2
We're tracking this issue at MCPE-224298, so I will resolve and link this report as a duplicate.
If you have new information to share, please leave a comment on the linked report. If not, add a vote to the report to show that you are affected.
If you haven't already, please make sure to search before creating a report to see if the issue has already been reported. See the Bug Tracker Guidelines for tips on searching for issues.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Correction on multiplayer impact:
In standard "Join Friends" multiplayer sessions:
If the host (or an op player) executes the /damage command under the described conditions:
The host's game crashes immediately
All other players lose connection because the host session terminates
While this is not an "any player" vulnerability, it remains a critical stability issue:
A host can accidentally crash their own session
An op player (intentionally or accidentally) can crash the entire session
The crash is host-side, affecting all players simultaneously