There was this bug in 1.6, and is still extremely problematic, and hard to correct for a player, since you have to either 1) die 2) take damage so that your "actual" amount of HP is extremely low, so that you can regen it accordingly (if you drop to 5%, you'll be able to regen up to 95%).
Needless to say how dangerous that bug is.
When this happens in Cyro (not IC), I jump from the top of a keep, then adjust a second jump to bring my health very low. Of course, it'd be fine without having to do it...
Did you get healed by the Templar healing Ultimate while taking damage before this happened to your health bar?
dwemer_paleologist wrote: »i have had the same problem, eventually it went away but it is still annoying.
Did you get healed by the Templar healing Ultimate while taking damage before this happened to your health bar?
dwemer_paleologist wrote: »i have had the same problem, eventually it went away but it is still annoying.
weird. Did it go away after a patch? or was it just completely random
dwemer_paleologist wrote: »also, note:
i have since the imperial city patch seen this happen to mobbs, wierd as it sounds, yeah, happened to mobbs.
random, and never know what cause it ...
likewow777 wrote: »I've seen it prior to the patch as well, but back then the entire group could also see the incorrect HP values. I guess it's an "upgrade" to only see it on one's self. Still, it's quite panic inducing when HP looks like it's at 2%, and you heal over and over to no effect.
Needless to say, we used the almighty power of a full group wipe to fix it. I have not experienced it personally since the update.
JaneCandyCane wrote: »I've experienced this often, too. I'm a templar and when I'm healing groups in Cyrodiil I see this all the time. Group members usually see my health bar as full, but not always.
I think it happens when I'm taking hits while healing. Especially while using the healing ultimate.
Has this bug been officially addressed yet? Experienced it on PC tonight-- extremely problematic for obvious reasons.
Please fix this bug...................