I don't know if this has already been reported (I did check) but in snapshot 15w31b, spawning a wither with no AI and hitting it with any weapon will damage it but its health bar will look as though it hasn't been hit. Note that it did go down before 1.9 snapshots.
How to reproduce:
1. Spawn a Wither with no AI
2. Hit it with a diamond sword a few times
3. Watch its health bar stay untouched
Related issues
is duplicated by
Attachments
Comments


cannot confirm

I have updated. And please do not add files against the issue. They are invalid

what do you mean they are invalid, it's stated nowhere that it's not allowed/invalid, I have used your exact steps, and I cannot reproduce this issue

Read how to reproduce

confirmed with no AI wither, which you didn't mention before

Confirmed for
15w44b

WAI, NoAI is always WAI.

It used to go down. And it isn't modded. It could affect gameplay and servers using NoAi withers

It doesn't affect vanilla survival gameplay, servers can fix it themselves. NoAI is WAI.

It still affects vanilla gameplay. Nothing rules it out.

NoAI is WAI.

How is it? It's vanilla minecraft

The NoAI state is an internal state that you can use through commands. But it remains an internal state. If it changes, so be it, but it will not be supported.

/summon WitherBoss ~ ~1 ~ {NoAI:1b,Invulnerable:1b,CustomName:"boss name",Silent:1b,Health:1}
The summoned wither will have 1 health, and can be punched to death, has the wither armor, but shows full health.
/entitydata @e[type=WitherBoss] {NoAI:0}
do this, and the health will drop down quickly.

@unknown This is not going to be fixed,
The NoAI state is an internal state that you can use through commands. But it remains an internal state. If it changes, so be it, but it will not be supported.

FVbico, tell me why not? It must be fixed.

Again:
The NoAI state is an internal state that you can use through commands. But it remains an internal state. If it changes, so be it, but it will not be supported.

Why it shoudln´t be supported? It is bug , it is critical to many people , and it doesn´t seem to be fixed.

So because it is internal state , it shouldn´t be fixed? Really? Bugs should be fixed. And this is bug. Doesn´t matter if it is some internal state or not.

If it changes, so be it, but it will not be supported.

Bug or not, this should be fixed for all the map makers and minigame makers. And I've made a few minigames in my time. Having the bossbar has a timer to tell the player that, maybe they need to survival a horde of hostile mobs until the bossbar is depleted. (the witherboss could of the wither EFFECT lowering the bar) This will be tricky to do if a user can't set the witherboss's NoAI tag to 1. Because if it won't go down, the player won't know when to use their last healing potion of not.

Don't give the wither noai, put it in a bedrock box and make it silent then, or spam it between ai and no ai.

Already tryed that. The sounds it makes with it's wither skulls are quite noisey. I tryed "/kill" the skull before they hit the bedrock but didn't work.

This bug has affected more people than 90% of the other bugs on this site. If anything this should be one of number 1 priorities.

Still not fixed. Seriously , Mojang?

Read previous comments:
NoAI=WAI
The NoAI state is an internal state that you can use through commands. But it remains an internal state. If it changes, so be it, but it will not be supported.
It won't be fixed.

"It wont be fixed." can a developer get lazier than not fixing bugs? probably not...

Wow. It's been almost 6 years since I reported this and nothing's changed. Summoning a wither boss in 1.16.5 yields the same result. Even if it's technically not a bug, withers without AI should still have accurate boss bars, otherwise what's the point of a static health bar rendering on-screen?
Having reread the discussions, it's kinda weird to see Dhranios defend the "working as intended" argument so passionately. To be blunt, it sounds like it's being labeled that way as an excuse to leave this unpatched.

Just ran into this issue 7 years later. Why has it been a thing for so long? How is it WAI? If this WAI then you might as well just remove the boss bar entirely.
If it's intended to work this way, then it should might as well work a different way
Huh? 😛
Anyone dealing with this issue, just use /bossbar
. It's not 1.4 anymore! 😃