Quote:
Originally Posted by Criimson
So for instance priorities are basically in the code. If a shaman and an enchanter are grouped: Enchanter hastes - shaman slows unless the MoB is DR resistant. That code is in there.
|
I just wanted to add this for my reference more than anything. Since I do raid with bots and take on tough mobs with sometimes just one group, I don't have a problem with both enchanters and shaman slowing (or beastlords, or any of the specialty slows), and here's why: Oftentimes, the difference between winning and losing is how quickly a slow lands. Shaman have Malo, Enchanters have tash, which sometimes is almost required before a slow will land. I know the logic could be tweaked from what it was, but it allowed the Shaman to cast the debuff, and the enchanter could cast the slow. (The enchanter could tash as well, but you get the point) If a slow was resisted, you would have to wait until the Shaman was finished casting, then cast again. I don't care who gets the slow first, just as long as the mob is slowed. I would even take a beastlord slow to help get the mob under control. The AI could also allow the slow to be overwritten if a bot has a better slow than what's currently on the mob (I assume this is how things work on live- I don't believe the second slow doesn't land because there's already a slow on.)
A possible example of healing/nuking presets: A cleric on Normal Nuking would only nuke when mana > 50%, Aggressive when mana > 25%, passive when mana > 75%. Hybrid healing: normal- heal when bot/player HP <25%, passive self heals only, aggressive- HP < 50%. (I would rather my hybrids heal than nuke- almost all hybrid nukes except those with stuns are horrible and terribly inefficient...).
Threaded Mode
