Guild Wars 2

I’ve posted this before and sent in numerous bug reports and it appears to be ignored, as I’ve been reporting this since BWE1. So… until it gets fixed I’ll keep posting, I guess and hope it gets fixed.

Within this post, you should be able to find EVERYTHING about WHY it’s happening and how it occurs and it seems like a simple fix coding-wise.

What happens:
1) You get downed.
2) You use Vengeance ( #3 Warrior Downed skill, kills you on expiration)
3) You lose ALL your health BEFORE Vengeance expires.
4) You die
5) Vengeance expires
6) You die, AGAIN

This results in an “Armour Break” happening TWICE in one death and if you use a way point, you will get there dead, UNLESS you WAIT for vengeance to expire post health-loss death, but you will still receive damaged armour.

Why this is happening:
I don’t know the exact code of the skill, but the mechanic and how the script functions is relatively obvious, so I’ll do my best.

Upon using Vengeance, the game runs a script that sets the player to “Alive” state, with a condition of something like “if Vengeance = true, player = alive” The vengeance runs on a timer of 15s and then should do a “if timer = 0, vengeance = false, script end”

This is not taking into account the Sweet Revenge trait, but that doesn’t appear to be the issue.

Now, this script is all well and good and functions fine, PROVIDING THE PLAYER DOES NOT DIE FROM HEALTH LOSS. This happens often in dungeons and should be expected, if you’re up with only, say… 15% health.

What SHOULD hapkitten (again, I don’t know how the code is written, so keep that in mind) that there is some form of “or” type statement or something, like

or if player = dead, script end.

This bug blocks progress. It costs money and time to repair armour and every extra repair is like 1.5s and that really starts to add up. The bug has probably cost me about 2g in total.

Again, my knowledge of coding is only very, very basic (I’m currently taking a course in Interactive Digital Media, it’s why I know anything at all) and I’ve probably got no clue what I’m talking about, but from the client end, it’s what appears to be happening and my (albeit, horrible) attempt and pseudo-code to explain it kind of gets the idea across.

I really hope this can be fixed with the next update and I hope that at some point someone can say “Yes, we’re aware of this”

Also, a note:

This is not player error. This is an actual bug and has been confirmed by at least 5 other warriors I’ve spoken to whilst grouping in Dungeons.

As an actual software developer, albeit obviously not working for ANet, I can assure you that your pseudocode is horrible, but you indeed explained the situation well.

As a general word of advice - when reporting bugs, there is rarely need to explain the behavior with snippets of code, pseudo or not, especially without an actual access to the original code in question, as it only unnecessarily clutters the flow of information and doesn’t add much to what already has been said (this based on many years of general practice).

Looking at your description, this is (even without access to the code) a pretty clear and simple oversight in either early timer termination, or respectively not checking for a death state upon calling a death procedure, so if they are not fixing it since BWE1, the most probable cause is that it’s just buried under a ton of other bugs classified with higher priority, and not that hey can’t find a solution for it.

Stumbled upon this bug today. Very annoying. Just want to confirm it is still not fixed.