Q:
Choas armor?
A:
I made a thread on this a while back and a video of me testing it….
My findings were that the blind does seem bugged along with the protection aspect of the spell. I’m guessing that the protection aspect may just be shoddy tooltip text misleading people on how it is meant to work.
With the blind though the graphic does not seem to show but if you trait for Blinding Befuddlement (confusion on blind) you will tend to find you get more stacks of confusion leading me to believe it does trigger.
You probably just don’t see it applying because your target is attacking quickly so its probably applied and used up b4 you notice.
You probably just don’t see it applying because your target is attacking quickly so its probably applied and used up b4 you notice.
even if it the debuff doesnt appear.
Your character should show a “miss” a few times. I think I agree with samski and its a little bugged
I can confirm with samski that contrary to what the tooltip implies, you won’t get Protection as a random boon on Staff #4 (and it will never appear through field combos). You only get it as an immediate, guaranteed boon on hitting Staff #4, never when struck.
Chaos Armor appears if you use the power or if you have a null field or any type of pre exsisting field out when you summon a clone on that field a chaos armor appears
Chaos Armor appears if you use the power or if you have a null field or any type of pre exsisting field out when you summon a clone on that field a chaos armor appears
1. The question was not how to get Chaos Armor.
2. Your answer isn’t entirely correct. You can get Chaos Armor from Staff 4. You can also get it through leap or blast finishers in ethereal combo fields. The leap finishers of a Mesmer are Staff 2 and Sword 3; the only blast finisher we have is Torch 4 (however, you may also be affected from blast finishers of other people). Our ethereal combo fields are Chaos Storm (Staff 5), Feedback, Null Field and Time Warp. What you are saying is, that you get Chaos Armor from any clone summon on any combo field, which is (at least partly) wrong.