Just having the debuff on you doesn't break cloak. It is the application/refreshing of the debuff, that breaks it. So if you have a DoT on somebody with the riposte set, the cloak will immediately break (especially when using the Shadowy Disguise morph). However cloaking without damaging the wizard's riposte user usually works (unless something else breaks it), even if i already have the debuff on me. It can be still super annoying and should be fixed of course.
As Rianai's comment makes clear, this isn't a problem with Wizard's Riposte, it's a problem with the way cloak works: things other than direct actions taken by the cloaking player will pull you out of cloak.
What proc sets are you referring to?The same problem occurs with numerous other proc sets.
Comfortably_Buzzed wrote: »As Rianai's comment makes clear, this isn't a problem with Wizard's Riposte, it's a problem with the way cloak works: things other than direct actions taken by the cloaking player will pull you out of cloak.
It's a problem with cloak caused by Wizard's Riposte. DOTs cause Wizard's to reapply (which is fine) but it's the reapplication breaks cloak, not the DOT tick. It's unlikely this was intended.What proc sets are you referring to?The same problem occurs with numerous other proc sets.
DeadlyRecluse wrote: »The updated Fasalla's set breaks stealth on minor defile application, too.
Want to know what's even better? It applies the minor defile even if the wearer is dead. Yeah.
I think we're just arguing over semantics. You're right, Riposte is making this happen and I agree that it shouldn't. I was referring to sets like Vicecanon, Fasalla's, etc. that pull you out of cloak. In my view, it's better to call for Cloak to be fixed than for Riposte to be fixed, since it's Cloak that's functioning incorrectly (breaking when it shouldn't), but it's two sides of the same coin.