Warrior still ignoring his campradius in Tank mode. While not an issue in some camps, It is a huge concern in others. Are we going to just have to manually play the warrior in those situations? I know I have brought this up earlier and got shot down for it. I am not sure how I am supposed to approach this subject without ridicule. Bottom line is I need to know my Tank is going to behave the way I have the perimeters set up for. If there is something going on outside of campradius ( And I mean way outside ). Then I will handle whatever is causing this anomaly from one of the other programs ( KA ) that is causing this in the first place. ( Like bard casting dots on NPC's that he/she is supposed to be mezzing ). Or pet classes sending swarm pets out when they shouldn't. Again KA issue. But if I have no control over my tank, that just adds to the other problems.
Another problem with Mq2war is the Taunt logic. You can't wakamole your taunt buttons! If you already have aggro war still pushes every button needlessly that he has for taunt? As I am fully aware of limitations in automation - combined with the daunting task of trying to take into consideration every scenario that one may encounter. And actually understanding and having played the class to know how best to approach different scenarios. This taunt thing leaves me no room for correcting issues that may arise which require a manual takeover to correct. Warlords's Grasp should never be used as a taunt button to smash just for taunt. I need warlords grasp to bring NPC's into position as needed only. Unyielding Attention is an 18s taunt that when it is over doesn't keep you on top of the hate list. Shouldn't be used just cuz you can. And Area taunt should be fully controllable. It still fires off when i have AOE turned off ( UseAOE=false )? I know that Taunt logic in the game isn't fully understood by most people. I play war as my Raid main ( Top 10 server ). Point is to try to get higher on mobs hate list. Taunt button only puts you 1 point ahead of who ever is on top of that list. Smashing it doesn't improve anything it actually hurts. In group content warriors don't need to do much to get on top of hate list and stay there. ( designed that way ). So if there is any way to curb this excessive taunt logic it would help tremendously.
And I read ( posted by another user ) about issues with warrior letting other members in the group to get beat on while warrior is staying on his first target. He got shot down also ( not sure why ). This is also a big problem. If CC cant get CC because they are getting beat on or NPC is resisting mezz the first try ( or whatever the reason ) It is the Tanks job to grab aggro!! If healer is getting beat on because of CC toon getting beat on cant get a mezz off, or whatever the reason, then it is the Tanks job to establish control of situation! Tank needs to switch target sometimes to get control ...... not start wakamole taunt buttons. If all your taunt options have already been used when not needed then there isn't anything left to push when you need to reestablish your self on top of the hate list for all mobs in camp ( or just one pesky mob in the crowd that refuses to cooperate )! Once again switch target is always the fastest and most reliable way in some situations to gain control back.
I could go into further details of Taunt mechanics for a warrior if needed, but I guess you see the problem here. Sometimes targeting the offending mob and casting one of the warriors appropriate taunt abilities is all that is needed to re establish control of the situation ( which is aggro on all mobs ). Sometimes all you have to do is go hit the NPC on the head a few times and taunt once. I fully understand the repercussions of switching target mid fight! But still, it is the only way to get control back in a lot of situations!
I have always had trouble with certain personality types in trying to ask for things without coming across to strong in their minds. This isn't a jab. This is just me asking for help. I don't know any other way ................. sorry.
