Why Do CC's Stand in AoE?

[tjwow2011]

Was wondering why every CC I've tried stands in AOE Dmg effects instead of moving out of them?

Have noticed this with Fps hunter, rogue, paladin. Ensemble's priest, paladin. Shamwow. Simple DK. Default warrior and warlock....

Was just wondering what has to be done to get the toons to step out of aoe stuff on there own?

 

[supersurfer]

pretty self explaining. you have to code that in the CC or make a plugin.

 

[CodenameG]

even if it was programmed what about places like in battle grounds where you have 10 aoe effects going on at the same time? your little paladin would be spamming around instead killing what the hell is making it. theres too many downsides and not enough upsides for programming it in.

 

[tjwow2011]

BG I understand is pretty much impossible, but was actually reffering to the various AOE affects in Instances and Raids. Those are very specific and IMHO controlable. DBM does a great job letting players know what and when and where to avoid such things, was just wondering why it couldn't be included into either the CC's, or IB so that when afk botting instances, your char doesn't stand in aoe's and die instead of taking a step or two out, then continuing to cast/attack/heal.

 

[Impala]

Those are not implemented because the cata instances are not programmed in InstanceBuddy (said by raphus himself). All HB does is act like combat bot providing either heal/dps and following the tank in the unsupported instances. Deal with it until it gets programmed.

 

[neodite]

even if it was programmed what about places like in battle grounds where you have 10 aoe effects going on at the same time? your little paladin would be spamming around instead killing what the hell is making it. theres too many downsides and not enough upsides for programming it in.

Which is why there should be 2 CC's

1 for PVP
1 for PVE

PVP to have combat logic movment (moving around targets)
PVE to move out of AOE/Move towards tank if you get agro