/entitydata NoAI on Ender Dragon causes it to rapidly vibrate
To reproduce:
1) Summon an Ender Dragon.
2) Type
/entitydata @e[type=EnderDragon,c=1] {NoAI:1}
A very glitchy, rapidly vibrating Ender Dragon should result. This is likely caused by the way that the Ender Dragon turns. Relogging fixes the issue, but the Ender Dragon will be completely straight and always face North.
This does not occur with any other mob.
This seems to be closely related to my other report, MC-74114, since once this issue is fixed by relogging, the dragon no longer takes damage.
Linked Issues
Created Issue:
/entitydata NoAI on Ender Dragon causes it to rapidly vibrate
To reproduce:
1) Summon an Ender Dragon.
2) Type/entitydata @e[type=EnderDragon,c=1] {NoAI:1}A very glitchy, rapidly vibrating Ender Dragon should result. This is likely caused by the way that the Ender Dragon turns. Relogging fixes the issue, but the Ender Dragon will be completely straight.
This does not occur with any other mob.Environment
Should be irrelevant
To reproduce:
1) Summon an Ender Dragon.
2) Type/entitydata @e[type=EnderDragon,c=1] {NoAI:1}A very glitchy, rapidly vibrating Ender Dragon should result. This is likely caused by the way that the Ender Dragon turns. Relogging fixes the issue, but the Ender Dragon will be completely straight.
This does not occur with any other mob.To reproduce:
1) Summon an Ender Dragon.
2) Type/entitydata @e[type=EnderDragon,c=1] {NoAI:1}A very glitchy, rapidly vibrating Ender Dragon should result. This is likely caused by the way that the Ender Dragon turns. Logging out and back in fixes the issue, but the Ender Dragon will be completely straight.
This does not occur with any other mob.
To reproduce:
1) Summon an Ender Dragon.
2) Type/entitydata @e[type=EnderDragon,c=1] {NoAI:1}A very glitchy, rapidly vibrating Ender Dragon should result. This is likely caused by the way that the Ender Dragon turns.
Loggingout and back infixes the issue, but the Ender Dragon will be completely straight.This does not occur with any other mob.
To reproduce:
1) Summon an Ender Dragon.
2) Type/entitydata @e[type=EnderDragon,c=1] {NoAI:1}A very glitchy, rapidly vibrating Ender Dragon should result. This is likely caused by the way that the Ender Dragon turns. Relogging fixes the issue, but the Ender Dragon will be completely straight.
This does not occur with any other mob.
This seems to be closely related to my other report,
MC-74114, since once this issue is fixed, the dragon no longer takes damage.
To reproduce:
1) Summon an Ender Dragon.
2) Type/entitydata @e[type=EnderDragon,c=1] {NoAI:1}A very glitchy, rapidly vibrating Ender Dragon should result. This is likely caused by the way that the Ender Dragon turns. Relogging fixes the issue, but the Ender Dragon will be completely straight and always face North.
This does not occur with any other mob.
This seems to be closely related to my other report,
MC-74114, since once this issue is fixed, the dragon no longer takes damage.
To reproduce:
1) Summon an Ender Dragon.
2) Type/entitydata @e[type=EnderDragon,c=1] {NoAI:1}A very glitchy, rapidly vibrating Ender Dragon should result. This is likely caused by the way that the Ender Dragon turns. Relogging fixes the issue, but the Ender Dragon will be completely straight and always face North.
This does not occur with any other mob.
This seems to be closely related to my other report,
MC-74114, since once this issue is fixed by relogging, the dragon no longer takes damage.
relates to
discovered while testing
Should be irrelevant
/summon EnderDragon ~ ~ ~ {NoAI:1}
summons an Ender Dragon that does not take any damage, melee or ranged (projectiles simply pass through it as if it weren't even there).
Compare this to using
/entitydata @e[type=EnderDragon,c=1] {NoAI:1}
which causes it to glitch (MC-74113), but it is able to take damage (until you fix that issue by relogging).
Confirmed for pre-4. Including a video demo. Seems to only affect Dragons that are not level when the command is issued.
https://www.youtube.com/watch?v=RcwsW6QDAGM
would be 'could not be fixed'
Also this was discovered while testing MC-73719
.
this is fixed in 15w31b, on my side at least
Still an issue in 15w36c (sorry haven't tested it lately).
This has never been fixed. Confirmed for 15w38b
Still an issue as of 15w47c.
Reopened.
....aaaand resolved: