Antiarc

BIG IMPORTANT NOTE: This isn't ready for production use yet. It's still in development, and please don't expect it to compete with KTM right at this moment. It works in many cases, but it is broken in others. I am hoping to have a full-fledged KTM competitor inside of a week, but it is not ready right now, so please tell anyone that uses it/is using it as much. Watch WoWAceUpdater for updates.

Well, it looks like the cat's out of the bag. I was gonna wait till it was a bit more complete to post it here, but whatever

It's not ready for primetime yet, but I hope to have it there soon. I checked in pet module framework code earlier today, and hyperactiveChipmunk checked in the pet module itself. I've begun work on the NPC abilities framework (threat wipes, reductions, etc), but that's got a ways to go yet. I am not going to rely on BigWigs for the boss events - they're relatively rare enough that we can keep them native in the mod easily enough without incurring another dependency.

Healing threat assumes one enemy target, so it'll show what your max healing threat could be. This will often times be higher than what healing threat actually is, but since there is no good way to find out how many enemies there are in combat, it's better to overestimate than to make a wrong guess.

Questions are welcome, and I would really value the EJ community's feedback, testing, and expertise as I develop this. It is a community project, and I couldn't have gotten this far without some massive help already (see credits.txt!), and will need help as we move into the future.

The Sanity framework has a few issues right now, but memory is not one of them. SanityBags is lean and mean.

The mod can't tell how many mobs you're in combat with, but it doesn't need to in order to provide good-enough threat lists per-mob.