Guild Wars 2

Sadly I don’t have any screenshots, but I encountered this bug on Gandara Server (EU) a couple days ago, while the server was fighting Taidha after a world reset due to patch (pretty much the only time she spawns seems the blocker that appears after fighting her once is ridiculous :P, and you have to do it three times to get her events to start again, but that’s besides the point).

Recently, a 15-minute timer got introduced to defeat Taidha when she spawns, that’s all well and good, but we encountered this problem when we defeated her AS the timer ended.

Basically, we defeated her with about 2 or 3 seconds to spare, but because of the death speech she gives, which lasts longer than a few seconds, the event failed (perhaps her timer should be increased to 16minutes to compensate for this? Off the point again, but anyway). Eventually, we did still get our Champ Bag Loot from her (no world chest or bonus rare chest of course seems the event itself failed even if she was defeated).

The nature of this pairing of Taidha dying but the event failing seemed to cause a problem though. While Taidha gives her speech, she is invulnerable – but as she died and was defeated before the timer ended, and was in her death speech at the time the event failed, once she finished the death speech she didn’t die.

Instead, she remained in the world, and re-engaged combat with the zerg, despite having zero health – she also retained the invulnerability buff she gets when giving her speech, which meant it was impossible to finish her off. Que annihilated zerg in a few seconds lol.

She persisted around the keep for a few minutes afterwards, among the undead that appear after her defeat, but eventually she despawned, leaving her champ bag.

So basically, in a nutshell;
TLDR; If you kill Taida with only a few seconds to spare, you don’t get the event reward due to her death speech. Moreover, she doesn’t die and remains in the world after her speech as a hostile but invulnerable enemy NPC, and takes a while to despawn. Pretty sure this isn’t intentional, so I thought I’d bring the bug to your attention on here.