Threat Priority Effects vs. Threat Effects (bugged?)

[ThramFalc]

<DIV>Many of our taunts list something like "increase threat priority of the <STRONG>Target </STRONG>By X positions", while most of our stuff just says "increase threat by X."</DIV> <DIV> </DIV> <DIV>My questions is what does the former mean?  Rescue adds one to position which seems to make sense but Taunting Challenge, Vengeful Strike, and Slate Invigorating Threat add 300-400 positions so my perceived definition based on rescue is thrown out the window.  And why does it say position of the target? Shouldn't it say caster?  i.e. raises my threat position with the mob...</DIV> <DIV> </DIV> <DIV>For now I have been assuming<STRONG> no threat position components work properly</STRONG>, which means Slates, TC and VS are all but useless for agro and are only good for their -5% to DPS effects.  Notice that Rescue also has a 400+ Threat increase so the few times rescue works is probably from that and not the position increase.</DIV> <DIV> </DIV> <DIV>Let me know what you all have learned regarding the priority effects.</DIV>

[TunaBoo]

Yah I am assuming rescue threat position really is position, and like taunt blow threat position really is threat priority. That is what it seems anyway.. you don't get 300 threat POSITIONS with taunting blow it it would nbe instant 100% aggro./here is to hoping for typo

[knightinplaid]

Moorguard posted the following yesterday in response to charms displaying a 0%-1% success rate. Sounds like there were a good number of errors and typos getting it out so fast. Probably the best thing would be for us to point out problems in the spells and abilites forum where they'll get more attn.<BR> <BLOCKQUOTE> <HR> <DIV>There will be some funky output on the spell descriptions every once in a while. By all means, keep pointing them out so we can get them fixed.</DIV> <DIV> </DIV> <DIV>There may be cases where we're pointing to the wrong data, in which case we need to fix the examine window. There may be other cases where a spell has an incorrect description, and we want to know about those too.</DIV> <DIV> </DIV> <DIV>We realized that the system wouldn't be perfect right off the bat, but we chose to err on the side of giving you more information rather than holding it back.</DIV><BR> <HR> </BLOCKQUOTE><BR>