Return of Reckoning

Hi all,

So i was wandering if anyone could provide additional information regarding the 'Proc Abilities' of the 'T4 (Epic) Weapon Quest' rewards. (This question derives from my lack of knowledge regarding game mechanics so sorry in advance )

e.g.1:
'Annihilator' Quest rewards 1h weapon (chosen/dok) that has 5% chanse to genearate 45 AP 'on being hit'.
So 'on being hit' means that you take damage or that you could also block/evade/disrupt/parry?
Additionaly, 'on being hit' includes that attackes from all sources(e.g. players autoattack, players skill cast)?
When the weapon ability procs is there a CD for it to proc again (can't see any in the description but still i am curious)?

e.g.2:
'Time to Waagh' Quest rewards 2h weapon (chosen/BO/BG) that has 10% to taunt target 'on hit'.
So 'on hit' means that you do damage or that you could also be blocked/parried?
Additionaly, 'on hit' only relates to the weapon autoattack or the class skill (that require weapons) are included also?
When the weapon ability procs is there a CD and is the weapon 'Taunt' equivalent to the 'Taunt' Skill?

I understand that this questiong is more mechanic related but thanks in advance for any info you can provide.

P.S. I know that the SC and ORVR influence weapons are far better but till then carefull planing is required .

On being hit mean when you get hit whatever the source of damage (not guard and morales i assume).
Differently is on being attacked ( chance to proc even on block parry etc). Some proc have on attack some have on hit.
Chance to taunt effect only appy the 30 % damage but it does not interrupt

Since i am here which was the t4 epic quest that give the 2h that provode 10% to parry, dodge and disrupt?

Tesq wrote: Since i am here which was the t4 epic quest that give the 2h that provode 10% to parry, dodge and disrupt?

It was Empire - 'Annihilator' i think . If you get another Tank it will be cheesy-peasy to do with crossguard. No heal or dps required . Just be carefull of the Hero mob in the PQ area (can be avoided with ease).

I will have to find a way and test the 'on being attacked' option if it is equivalent to 'on being hit' .