AndrewGaming587
- ImNotSus117
- JIRAUSER726262
- America/New_York
- Yes
- No
MC-253896![[Mojang] etanaratsastaja](../../../data/avatars/users/10122.svg){kind=small}
99% sure this is intentional.
When you attack a neutral mob, it's supposed to fight back. However, under certain, strange, cases, they won't. It seems to happen whenever a command with a target selector containing nbt={any-nbt-data-here} is run on the same tick as a neutral mob being attacked.
Steps to reproduce:
- Place a repeating command block and add any command that contains a target selector with the 'nbt=' field in it, and power it.
- Spawn any neutral mob.
- Make sure you aren't in peaceful difficulty.
- In survival, attack the neutral mob.
- Observe that it doesn't attack back.
- Unpower the command block
- Attack the mob again.
- Observe that it attacks you back as intended again.
Notes:
- If you attack a neutral mob that will cause other mobs of the same species to attack you as well, while having a method to produce the bug active, the other nearby mobs of the same species do attack you (although they don't change to their attacking pose and/or texture), but the attacked mob doesn't attack.
- Other methods of angering neutral mobs without attacking them, such as looking an enderman in the eyes or going near a spider in a dark area, still work as intended.
Video:
2025-01-15 18-15-40.mkvFound this bug while using datapacks, as functions can also produce the bug.
Likely happens with older versions too, but it's a recent bug because it worked fine in 1.21.1 and I don't know when it started, but I believe it likely either started in 25w02a or 25w03a because I don't think I had this issue either in 1.21.4.
When you attack a neutral mob, it's supposed to fight back. However, under certain, strange, cases, they won't. It seems to happen whenever a command with a target selector containing nbt={any-nbt-data-here} is run on the same tick as a neutral mob being attacked.
Steps to reproduce:
- Place a repeating command block and add any command that contains a target selector with the 'nbt=' field in it, and power it.
- Spawn any neutral mob.
- Make sure you aren't in peaceful difficulty.
- In survival, attack the neutral mob.
- Observe that it doesn't attack back.
- Unpower the command block
- Attack the mob again.
- Observe that it attacks you back as intended again.
Notes:
- If you attack a neutral mob that will cause other mobs of the same species to attack you as well, while having a method to produce the bug active, the other nearby mobs of the same species do attack you (although they don't change to their attacking pose and/or texture), but the attacked mob doesn't attack.
- Other methods of angering neutral mobs without attacking them, such as looking an enderman in the eyes or going near a spider in a dark area, still work as intended.
Video: 2025-01-15 18-15-40.mkv You'll need to download it because onedrive won't play mkv videos for some reason
Found this bug while using datapacks, as functions can also produce the bug.
Likely happens with older versions too, but it's a recent bug because it worked fine in 1.21.1 and I don't know when it started, but I believe it likely either started in 25w02a or 25w03a because I don't think I had this issue either in 1.21.4.
Relates to
MC-279556.When you attack a neutral mob, it's supposed to fight back. However, under certain, strange, cases, they won't. It seems to happen whenever a command with a target selector containing nbt={any-nbt-data-here} is run on the same tick as a neutral mob being attacked.
Steps to reproduce:
- Place a repeating command block and add any command that contains a target selector with the 'nbt=' field in it, and power it.
- Spawn any neutral mob.
- Make sure you aren't in peaceful difficulty.
- In survival, attack the neutral mob.
- Observe that it doesn't attack back.
- Unpower the command block
- Attack the mob again.
- Observe that it attacks you back as intended again.
Notes:
- If you attack a neutral mob that will cause other mobs of the same species to attack you as well, while having a method to produce the bug active, the other nearby mobs of the same species do attack you (although they don't change to their attacking pose and/or texture), but the attacked mob doesn't attack.
- Other methods of angering neutral mobs without attacking them, such as looking an enderman in the eyes or going near a spider in a dark area, still work as intended.
Video: 2025-01-15 18-15-40.mkv You'll need to download it because onedrive won't play mkv videos for some reason
Found this bug while using datapacks, as functions can also produce the bug.
Likely happens with older versions too, but it's a recent bug because it worked fine in 1.21.1 and I don't know when it started, but I believe it likely either started in 25w02a or 25w03a because I don't think I had this issue either in 1.21.4.
When you attack a neutral mob, it's supposed to fight back. However, under certain, strange, cases, they won't. It seems to happen whenever a command with a target selector containing nbt={any-nbt-data-here} is run on the same tick as a neutral mob being attacked.
Steps to reproduce:
- Place a repeating command block and add any command that contains a target selector with the 'nbt=' field in it, and power it.
- Spawn any neutral mob.
- Make sure you aren't in peaceful difficulty.
- In survival, attack the neutral mob.
- Observe that it doesn't attack back.
- Unpower the command block
- Attack the mob again.
- Observe that it attacks you back as intended again.
Notes:
- If you attack a neutral mob that will cause other mobs of the same species to attack you as well, while having a method to produce the bug active, the other nearby mobs of the same species do attack you (although they don't change to their attacking pose and/or texture), but the attacked mob doesn't attack.
- Other methods of angering neutral mobs without attacking them, such as looking an enderman in the eyes or going near a spider in a dark area, still work as intended.
Video: 2025-01-15 18-15-40.mkv You'll need to download it because onedrive won't play mkv videos for some reason
Found this bug while using datapacks, as functions can also produce the bug.
Likely happens with older versions too, but it's a recent bug because it worked fine in 1.21.1 and I don't know when it started, but I believe it likely either started in 25w02a or 25w03a because I don't think I had this issue either in 1.21.4.
When you attack a neutral mob, it's supposed to fight back. However, under certain, strange, cases, they won't. It seems to happen whenever a command with a target selector containing nbt={any-nbt-data-here} is run on the same tick as a neutral mob being attacked.
Steps to reproduce:
- Place a repeating command block and add any command that contains a target selector with the 'nbt=' field in it, and power it.
- Spawn any neutral mob.
- Make sure you aren't in peaceful difficulty.
- In survival, attack the neutral mob.
- Observe that it doesn't attack back.
- Unpower the command block
- Attack the mob again.
- Observe that it attacks you back as intended again.
Notes:
- If you attack a neutral mob that will cause other mobs of the same species to attack you as well, while having a method to produce the bug active, the other nearby mobs of the same species do attack you (although they don't change to their attacking pose and/or texture), but the attacked mob doesn't attack.
- Other methods of angering neutral mobs without attacking them, such as looking an enderman in the eyes or going near a spider in a dark area, still work as intended.
Video: 2025-01-15 18-15-40.mkv You'll need to download it because onedrive won't play mkv videos for some reason
Found this bug while using datapacks, as functions can also produce the bug.
Bug started in 25w02a.
Relates to
MC-279556.When you attack a neutral mob, it's supposed to fight back. However, under certain, strange, cases, they won't. It seems to happen whenever a command with a target selector containing nbt={any-nbt-data-here} is run on the same tick as a neutral mob being attacked.
Steps to reproduce:
- Place a repeating command block and add any command that contains a target selector with the 'nbt=' field in it, and power it.
- Spawn any neutral mob.
- Make sure you aren't in peaceful difficulty.
- In survival, attack the neutral mob.
- Observe that it doesn't attack back.
- Unpower the command block
- Attack the mob again.
- Observe that it attacks you back as intended again.
Notes:
- If you attack a neutral mob that will cause other mobs of the same species to attack you as well, while having a method to produce the bug active, the other nearby mobs of the same species do attack you (although they don't change to their attacking pose and/or texture), but the attacked mob doesn't attack.
- Other methods of angering neutral mobs without attacking them, such as looking an enderman in the eyes or going near a spider in a dark area, still work as intended.
Video: 2025-01-15 18-15-40.mkv You'll need to download it because onedrive won't play mkv videos for some reason
Found this bug while using datapacks, as functions can also produce the bug.
Bug started in 25w02a.
99% sure this is intentional.
can confirm, applies to nearly every sound made by warden
Can confirm, happens on the latest version of preview at the time of writing this comment.
I think this is intentional, but I'm not fully sure.
It actually does work, but under VERY specific conditions that I do not know, as I ran the command near spawn, and I got the end spike to spawn, but only in that one specific spot did it work. I don't know why that specific spot worked and not any other that I tried.
EDIT: I figured out the conditions, the spikes only place if you try to place them in the ring where they would spawn in the end. Probably has been a bug since 1.9 if you use a mod to attempt to place a spike elsewhere before /placefeature was added
can confirm, also happens with targets selected by a target selector with the nbt= parameter. Also affects 25w04a. Relates to
MC-279543, a similar (but not duplicate) bug that I reported myself.This should really be fixed, it's breaking a lot of tellraw usages in my datapacks (not that they weren't already broken because of hoverEvent being changed to hover_event and clickEvent being changed to click_event) because of \n and removing all of the \n usages makes them look very ugly in-game, especially hover text.