Guild Wars 2

The Ranger’s Signet of Renewal is not passively removing conditions every 10 seconds (or ever).

I noticed this while dueling a thief using shortbow poison volley, and then asked that thief to help me test.

We tested this by using poison volley to load me up with poison. Got over a minute of poison applied and then waited. The poison ran it’s full course without ever being removed.

I think this may be going un-noticed by many Rangers because of other passive removal being used in most builds. (eg. Empathic Bond).

If anyone else could test this out and confirm that would be awesome.

The thread to confirm is posted in the Game Bugs forum:
https://forum-en.gw2archive.eu/forum/support/bugs/Signet-of-Renewal-passive-not-working/first#post2235189

Anyone able to test?

EHh, I just tested it like 3 days ago.. and it was working.. did they break it again?

One sec i’ll go test

K, tested it.. and it works fine

At least against mobs

Hmmm. Maybe it’s only poison not working, or maybe it’s only in pvp; I’ll try some other scenarios to narrow it down and do a little QA for them.

It worked against poison, cause that’s what I tested against it.

Been working fine for me today.

Ok found the actual bug.

The signets work, if they are showing in the UI.

For some reason the sigils can get disabled. You can re-enable by selecting a new signet and then going back to it.

Tracker.6483:

Ok found the actual bug.

The signets work, if they are showing in the UI.

For some reason the sigils can get disabled. You can re-enable by selecting a new signet and then going back to it.

Yeah, old bug that keeps reappearing from patch to patch. Highly annoying, don’t understand why they keep putting this old bug back into the game all the time…

OGDeadHead.8326:

Yeah, old bug that keeps reappearing from patch to patch. Highly annoying, don’t understand why they keep putting this old bug back into the game all the time…

They do it intentionally to keep us on our toes :P

Seriously though, these things happen in IT all the time. I know I’ve “accidentally re-introduced” a fixed bug before. They might need more regression testing to make sure it won’t happen again.