Originally Posted by Crepusculu
This probably would be the first "exploit" that would not care for a fix, despite never having used it. If you let people out of combat, its your own fault.
|
Uh, you are aware that on an average 2v2/3v3 match, espescially if a Mage or Warlock or Druid is involved, I will drop combat anywhere from 7-15 times depending how often I am cc'd? Every polymorph is a potential 1000+ mana gained due to dropping combat after 6s with sithack, or at the least 1-2 ticks if you sip without sithack. Every cyclone is a GUARANTEED drink, if your partners aren't in any danger of dying, you can drink and /sithack after EVERY cc (blind, poly, cyclone, fear if the pet isn't on you.)
This adds up to alot of mana. As much as I hate CC and the classes associated with it - espescially druids, you shouldn't be punishing them for using CC. Normal drinking is fine, sipping here and there I can understand. But when an affliction or SL/SL lock is trying to prevent you from sithack, what can they do really? Waste DC? recast fear? You still got at least 2 ticks off.
Originally Posted by Kaber
Killing the pet is a pretty easy way to avoid having to use any "exploits" to get around dealing with it. Not to mention it neuters BM hunters pretty well, and even MM hunters are going to have a tough time without their pet.
|
Or if you have a survivable partner (i.e warrior) and the hunter or warlock is hamstrung, more often or not you can just run off and actually despawn the pet. Either way you force the pet owner to recall the pet or have it possibly be desummoned. In 2's/3's we try to force the fight in their starting area, just so we can utilize this. This needs to be fixed, at least for arena - they only have to increase the range by like 10 or 15 yards.