Vanguard Curse of Weariness

[Rudra]

I make a point of not fighting Vanguard, so this may be normal operation, but checking City of Data, it shouldn't be. I was affected by a Vanguard Curse of Weariness, but cleared out the spawn. Not a problem, MM pets to the rescue. Anyway, I waited for the curse to wear off. And I waited. And I waited. 2 minutes later, I look up the power on City of Data to find out how long I was going to have to wait, and it said "until caster defeated". Well, the caster was defeated now more than 5 minutes ago as of me starting this thread and I am still affected. So is there an added duration City of Data is missing or is this a bug?

 

Edit: Update, it went away some time while I was typing this up.

 

Edited March 22 by Rudra

[merrypessimist]

Could be worse.  Used to be "Lasts until you use the cure bought with vanguard merits." 

[Honorbridge]

Gonna preface this by saying it’s been awhile so I could be wrong about this.

I believe the Curse of weariness is a temporary auto power given to you by the vanguard enemy, rather than a traditional debuff.  The City of Data blurb that mentions until caster defeated also mentions that it is self only.  The caster of the power is YOU, so that’s why it out lives the enemy.  The duration you keep the power for is 5 minutes.  

Edited March 22 by Honorbridge

[Rudra]

44 minutes ago, merrypessimist said:

Could be worse.  Used to be "Lasts until you use the cure bought with vanguard merits." 

I forgot about that. Thanks. Like I said, been a while.

 

31 minutes ago, Honorbridge said:

Gonna preface this by saying it’s been awhile so I could be wrong about this.

I believe the Curse of weariness is a temporary auto power given to you by the vanguard enemy, rather than a traditional debuff.  The City of Data blurb that mentions until caster defeated also mentions that it is self only.  The caster of the power is YOU, so that’s why it out lives the enemy.  The duration you keep the power for is 5 minutes.  

Thanks for the reminder. I forgot it worked that way. So yeah, not a bug, and I'm glad it went away on its own.