If you set the NoAI tag for a guardian that is charging his beam to 1, the beam of the guardian will be in a much longer range, will not disappear, will not damage the player and the guardian's body will still track the player (But won't move, just look at the direction of the player). The guardian's beam will also track the player in creative mode and spectator mode. The guardian's beam can also track the player even if there's a wall in between them.
What I expected to happen was...
The beam of the guardian would disappear and the guardian's body would stay still.
What actually happened was...
The beam of the guardian stayed and the guardian's body faced the direction of the player.
Steps to reproduce:
1. Summon a guardian.
2. Go into survival mode.
3. While the guardian is charging his beam at you, enter this command: /entitydata @e[type=Guardian,c=1] {NoAI:1}
A video of the issue occurring: https://youtu.be/4yF1WCvOYNI
Attachments
Comments 19
Please reopen. This issue is not invalid. There were bugs in the past that were fixed that were related to NBT tags, there is no reason for this issue to be invalid.
Because manually changing NoAI during it's lifetime isn't supported, all results are to be intended/invalid/won't fix
Yes, many maps use it, but still all bugs regarding behaviour with no ai are still invalid, as fixing them requires mojang to completely rewrite the ai system, this will eventually be fixed later, when they are going to rewrite it, but not now
First off, it's only guardian's AI. Second, it's only the beam part of the guardian's AI. Third, it's just a change in the AI of a certain mob, they did that in 15w40a.
The beam isn't part of the ai, attacking is, changing nbt during lifetime ISN'T SUPPORTED and lastly it will still require to make the guardian use a new ai system, so it still has to be rewritten
Whatever you say, this will not be reopened until mojang has started redoing the ai system
Since this issue is getting so much attention, why don't you look at issues that are quite old and important but don't get views, like MC-89567?
The NoAI tag has a very specific purpose: it disables AI updates for that entity. Many entity behaviors were implemented before the AI system was added to Minecraft, and it only covers some basic, common behaviors, so many mob-specific behaviors are still implemented in the mob code, and are thus unaffected by the NoAI tag. Ideally, the AI system would be expanded to cover all of these behaviors, and that code moved out of the mob code. However, that would be a major task, and Mojang still has many other major code cleanup tasks to do which are higher priority. Still, they have slowly been making improvements to the AI system, and some NoAI "bugs" will be fixed over time as they expand the AI system to give it the necessary functionality.
MC-67437 was not about the behavior of entities that had the NoAI tag, it was about the lightning transformation code not copying the NoAI tag across. The involvement of the NoAI tag doesn't automatically make an issue invalid. There are specific types of issues involving it that we've been instructed to mark as invalid or won't fix.
In this case, it's not even the NoAI tag itself that makes this issue invalid. It's the fact that you're changing the tag during the lifetime of the entity, which can have unexpected results. By setting the NoAI tag, you've stopped the AI from updating – but that doesn't mean that the entity will just stop doing what it's already doing. In this case, it means that it will continue targeting the player, because that's the state it was set to by the last AI update it received. For it to change to another state, perform another behavior, or even stop its current behavior would require another AI update. That's simply how the system works, and is intended to work. This isn't a bug, no matter how much you'd rather it behave differently.
Any issues regarding changing nbt during an entity's lifetime are not going to be fixed, any issues that occure are considered invalid