Originally Posted by Yhor
Yes Seerah, it wasn't the fault of Aloft (I should have said this already), it was a piece of my code (I'm a newby with code btw) not playing nice with Aloft.
|
whew... good news (at least from Aloft's perspective). there were a number of things that jumped out of WotLK, and i made a few typos trying to fix them, which did not help... it took a few releases for Aloft to stabilize.
but Aloft 2.4.6-315 (most recent version as of 2008/11/18) appears to be relatively stable (so far). and thanks as always to Seerah, i often come across threads in which the poster has already been steered to the latest/greatest version.
anyway, Aloft's current threat implementation would give you about what Omen would give you (group threat against your current target), plus the Blizzard aggro glow.
we have been discussing trying to do more with the threat subsystem, but it looks like it would be pretty resource-intensive to do. it does not look like Blizzard's threat event model covers anything to a useful degree except the current target (from the perspective of each player). so, to gather more information Aloft (or any other addon) would need to query additional targets and/or get into the business of exchanging data over the addon channel with other installations of itself.
i am still digging into this, but it is not too promising so far.