Guild Wars 2

If you enter combat from gaining a condition, it won’t remove that one condition… Unless stacked again.
-Other than that, enjoy the replacement to water line.-

That is not a bug, its a feature.

Working as intended (only remove condition after getting hit).

It’s not a bug. It’s a feature.

We gotta stop posting about DS and move on. It’s a dead useless trait. Karl not gonna change it. He doesn’t even read/post in this Ele forums.

No its a bug where DS is only working in combat and when it dose this its not dealing with conditions from before getting into combat. Its not working as intended.

It is not a bug, nethier feature. It is deception.
In preview, they said it removes condi every sec not every hit with 1 sec cd.

Everyone thought that the preview would be the final stuff. We couldnt imagine it could be worse.

And yet here it is!

Jski.6180:

No its a bug where DS is only working in combat and when it dose this its not dealing with conditions from before getting into combat. Its not working as intended.

The first tick doesn’t count. You need to get struck again for DS to remove the first condition. If your 2nd struck gives 2 conditions, tough love. It’s not a bug, it’s a feature. It’s not a great feature though.

Sunshine.5014:

Jski.6180:

No its a bug where DS is only working in combat and when it dose this its not dealing with conditions from before getting into combat. Its not working as intended.

The first tick doesn’t count. You need to get struck again for DS to remove the first condition. If your 2nd struck gives 2 conditions, tough love. It’s not a bug, it’s a feature. It’s not a great feature though.

Is that how the 10 sec conditions remove effects work too?

Jski.6180:

Sunshine.5014:

Jski.6180:

No its a bug where DS is only working in combat and when it dose this its not dealing with conditions from before getting into combat. Its not working as intended.

The first tick doesn’t count. You need to get struck again for DS to remove the first condition. If your 2nd struck gives 2 conditions, tough love. It’s not a bug, it’s a feature. It’s not a great feature though.

Is that how the 10 sec conditions remove effects work too?

No because they don’t have the having to be struck rule. The others, e.g., ranger only has the time component to the rule, so every 10 sec.

Diamond Skin has 3 rules:

- time component (1 sec);
- when struck – so you had to have a condi before getting struck; and
- health threshold – I don’t know this one for sure, but I imagine you need to be at 75% or more of health before getting the hit and not after the damage of the hit is applied.

So what OP described as a bug is a feature and working as intended.

Jski.6180:

Sunshine.5014:

Jski.6180:

No its a bug where DS is only working in combat and when it dose this its not dealing with conditions from before getting into combat. Its not working as intended.

The first tick doesn’t count. You need to get struck again for DS to remove the first condition. If your 2nd struck gives 2 conditions, tough love. It’s not a bug, it’s a feature. It’s not a great feature though.

Is that how the 10 sec conditions remove effects work too?

I’m sorry I don’t understand what you meant with that.

Azel.4786:

Jski.6180:

Sunshine.5014:

Jski.6180:

No its a bug where DS is only working in combat and when it dose this its not dealing with conditions from before getting into combat. Its not working as intended.

The first tick doesn’t count. You need to get struck again for DS to remove the first condition. If your 2nd struck gives 2 conditions, tough love. It’s not a bug, it’s a feature. It’s not a great feature though.

Is that how the 10 sec conditions remove effects work too?

No because they don’t have the having to be struck rule. The others, e.g., ranger only has the time component to the rule, so every 10 sec.

Diamond Skin has 3 rules:

- time component (1 sec);
- when struck – so you had to have a condi before getting struck; and
- health threshold – I don’t know this one for sure, but I imagine you need to be at 75% or more of health before getting the hit and not after the damage of the hit is applied.

So what OP described as a bug is a feature and working as intended.

I do hope they changes that it takes a lot of what DS should be doing away.

The fact that it dose not remove the first conduction that is applied to you even though you are in combat seems more like a bug even if you would have to wait 1 sec. So it seems the skill is saying you do not have a condition on you becuse it was not on at the time of the condition i think IS a bug.

Waiting for 1 sec to start up seems ok though.

Jski.6180:

Azel.4786:

Jski.6180:

Sunshine.5014:

Jski.6180:

No its a bug where DS is only working in combat and when it dose this its not dealing with conditions from before getting into combat. Its not working as intended.

The first tick doesn’t count. You need to get struck again for DS to remove the first condition. If your 2nd struck gives 2 conditions, tough love. It’s not a bug, it’s a feature. It’s not a great feature though.

Is that how the 10 sec conditions remove effects work too?

No because they don’t have the having to be struck rule. The others, e.g., ranger only has the time component to the rule, so every 10 sec.

Diamond Skin has 3 rules:

- time component (1 sec);
- when struck – so you had to have a condi before getting struck; and
- health threshold – I don’t know this one for sure, but I imagine you need to be at 75% or more of health before getting the hit and not after the damage of the hit is applied.

So what OP described as a bug is a feature and working as intended.

I do hope they changes that it takes a lot of what DS should be doing away.

The fact that it dose not remove the first conduction that is applied to you even though you are in combat seems more like a bug even if you would have to wait 1 sec. So it seems the skill is saying you do not have a condition on you becuse it was not on at the time of the condition i think IS a bug.

Waiting for 1 sec to start up seems ok though.

Again, it is not a bug.

You feel it is bad because it is horrible.

It has no relation with being in combat.

You need to understand it is not remove a condition per second.

The wording is – remove a condition when struck with a 1 sec internal cool down.

So once you are hit, if you have a condi, it removes 1. The trait then has a 1 sec cool down and if you are hit again after the cool down and you have a condi, it will remove a condi.

The above works only if you are above the health threshold.

So in a grotesque example, if you have 10 stacks of burning that last 5 sec and you don’t take any hits, you will suffer the condi for the entire duration because you weren’t hit (trigger to remove condi).

Thus it is not a bug.

If you want to argue it is a kitten tier trait, that is another issue. But the trait works as presented.

Next patch: Diamond skin – updated the tooltip for clarification: it now describes the trait as following: “bad choice, you are screwed”

Wow so messed up but I love it

I ran diamond skin on my ele.. but it’s so funny to watch how dependent you guys were on a broken skill.

Ele has a ton of condi removal and better master traits for removing them. I am sorry you have to actually think about your build now.

Lies.. I am not sorry.. this is hilarious.

It’s not that we can’t play without it, it’s just that it is badly redesigned. Can’t we complain about having one more useless trait, at least?

Correct me if I’m worng.
From what I think when I used Signet of Water its count 10s since its was equipped and then remove 1condition when 10th second since equipping hits. Am I so confused or its works like that. That its proc its condi remove when 10th second hits since equipp.

So maybe that second hit in reality time when exatly next second in server time hits/or since equipping it/or even since entering to instance to proc its condi removal ability? That means it doesn’t have cd. But rather pulse remove on every 1s of server time/since being equipped with additional requirement which is hp treshold and and being struck / maybe its even take amount of hits from late second / programming that trait could go in very very ways.

So maybe its have bug in way it was programmed.

I would also call it a bug, cuz they didn’t give more viable build and destroyed trait, that compared to other was significant, but on us somehow it worked, that I woudn’t dare call it op. Maybe tweak to not prevent application of conditions, but to give massive resistance, but with assume that chill is exception and it can be prevented from being applicated cuz of devastation that it does to that proffesion.

I think it triggers on the first application of a condition, and starts its icd thereafter.

MyPuppy.8970:

Everyone thought that the preview would be the final stuff. We couldnt imagine it could be worse.

Arenanet slogan:

Expect nothing. Still get disappointed.

….so elementalists are masochists now?

TheLastNobody.8319:

….so elementalists are masochists now?

All auras give effect if you come up with idea to bait enemies with your hp, just to trigger effects.

SchmendrickTheMagician.8247:

MyPuppy.8970:

Everyone thought that the preview would be the final stuff. We couldnt imagine it could be worse.

Arenanet slogan:

Expect nothing. Still get disappointed.

Or “expect the less, it’s gonna be worse”.

Honestly, one shouldn’t bother anymore and just adapt. That’s all I do. Of course we care for our favorite profession, but posting, suggesting and feedbacking here feels like talking to the wailing wall.