Guild Wars 2

I seem to remember an old post about getting to 1.75 seconds was enough to get two ticks. There’s an old Reddit post here that talks about that.
http://www.reddit.com/r/Guildwars2/comments/1d00x1/how_condition_duration_works_a_psa/

When I was testing my condi build, it seemed like the timer for burning started independently for that condition when it was applied. And the first damage happened at the 1 second point. So it seems like getting to only 1.75 seconds will not get two ticks. (I was testing by recording and watching the floaters. For sure, there may be errors with this – I saw one floater appear showing fire damage when burning was NOT on the target).

Has anyone done much testing with this recently? Thx!

I was testing a staff/ s/s condition build a while ago and did notice that Burn was very sporadic about when it did and did not want to tick. This may have been due to the duration stacking from myself and my clones (causing it to tick twice rapidly or only Once before falling away).

Without extensive testing i wouldn’t really have a clear answer and atm the laptop i’m being forced to use doesn’t allow me to play at Max FPS with 0 latency in game to time such exact spurts.

I did some testing with it awhile back – what seemed to be the case is that, with 76% condi duration and burning as the ONLY condition, you would get one tick. With the same condi duration and multiple conditions, burning would tick twice.

Dhampyr.2104:

I did some testing with it awhile back – what seemed to be the case is that, with 76% condi duration and burning as the ONLY condition, you would get one tick. With the same condi duration and multiple conditions, burning would tick twice.

Yes, I seem to recall something incredibly odd like that as well.

The information in the reddit post is correct. When a damaging condition is afflicted, a timer starts, ticking at 1s intervals. As long as damaging conditions are on the target, they will tick every second. This is why, when viewing an enemy health bar, it seems to drop in chunks rather than a continuous draining effect when the enemy is loaded with conditions.

I have tested this and found it to be true with Winds of Chaos, The Prestige, and Siren’s Call and I have no reason to believe it doesn’t apply to all conditions. I tested it at various condition benchmarks which did not result in whole additional second, recording video and watching it in slow-motion to see if extra ticks occurred.

It is a common misconception that whole-second duration increases are all that result in extra ticks. I don’t know why such a misconception exists, but it does.

The ultimate result of this information is that condition duration, regardless of the amount, increases dps. For further info, see:

https://forum-en.gw2archive.eu/forum/professions/mesmer/question-on-condition-duration/

https://forum-en.gw2archive.eu/forum/professions/mesmer/Video-MSS-GreatSword-Mesmer-10-Dec/first#post2358299

Thanks – that’s helpful. How do you think Torment fits in here?

The wiki says “inflicts damage twice per second if the victim is moving”. Do you think this means that Torment gets its own timer when it gets applied? (Or at least gets it’s own secondary timer?)

They should realy make burn tick every .5 or even .25 seconds rather then every 1 second- hardbreakpoints on a condition that tends to have very short durations are a bad things- they make the damage random an unreliable.

eldenbri.1059:

Thanks – that’s helpful. How do you think Torment fits in here?

The wiki says “inflicts damage twice per second if the victim is moving”. Do you think this means that Torment gets its own timer when it gets applied? (Or at least gets it’s own secondary timer?)

I believe torment still ticks on a 1s interval, but it simply ticks for twice as much. I haven’t tested it, but I would assume it follows the rules of the other conditions.

zest.4192:

They should realy make burn tick every .5 or even .25 seconds rather then every 1 second- hardbreakpoints on a condition that tends to have very short durations are a bad things- they make the damage random an unreliable.

I agree that the mechanism they have in place is kinda weird, but I think it works. Sure, there’s a chance, based on your condition duration, for conditions to get an extra tick, but over the course of a fight there are so many conditions that they should average out to reflect the condition duration accurately.