as often said before, anti changed the libs protocol so the other people have to update as well, otherwise you wont see them and they wont see you. All this happens to reduce traffic. and its not completed yet, so exspect it to break it again,after the weekend ;)
i also have WAU without externals and inside omen folder is a threat2 folder, so that would mean that is should work right?
Just a little request : could it be possible to reintroduce the sound "link" in the alarm sounds ? I used to be used to that one and now, I had to change and sometimes when I hear it, I don't have the reflex to FD (hunter inside).
1: i can't hide the icon. It's either in fubar, or on the minimap. but i can't hide it completely.
Should be addressed.
2: Scaling issue, when i logged in my alts, i found that the omen window was screwed up. After some experimenting i found that when i clicked the resize tag it snapped back to normal size.
Still tracking this one down.
3: No way to save profiles. As with version 1, you still have to do all settings for each character individually it seems.
Should be fixed now.
4: Class colors? Can't seem to customize these on a per-player basis anymore.
Chis will be coming back.
5: Bar color styles seem nice, but making these selectable will be a cool feature.
Elaborate?
6: You still get warnings, even if you disable warnings. Only when you actually disable the individual warnings do the warnings stop.
Should be fixed.
Quote from fr0ggy »
1' in older version i could get the agro bar from omen, wich represent my agro vs tank, and put somewhere in the screen, and close omen, cause i dint care to much about the others.
i canot seems to do it now.
This isn't in yet, and will be coming back.
2' i miss the ... "ching" or "ding" sound. a melodious beep, canot really tell you how it sounds.
i dint find any sound in the curent list good for my ears :(
That sound probably came from SharedMedia. Install and that you should hopefully have it back.
Quote from Rantoul »
I would also like an "Omen Classic" The look of Omen2 just doesn't seem to fit right.
/omen skin load classic
Quote from Koriani »
Also I miss where we USE to be able to set at what percentage we wanted our threat notification to pop (I just used a text message, no shaking or red blinky). Can we get that back??
Modules -> Single Target -> Warnings
I'd also like to just be able to display threat percentage - I don't need four colums of informational numbers (that I have no FRICK CLUE what the heck they are telling me anyway). Other than my rank "near the top" with the graphs, I had no idea what to look at and what numbers were telling me how far my threat was from the tanks vs. all the other numbers.
You can toggle columns off under Modules -> Single Target -> Columns
I agree to have the option where myself is labeled in RED to make ME easier to find (I'm not a raid leader, I only care about ME! :)).
This is coming back.
Quote from ManniAT »
either it does no longer exist - or I can't find it.
In GOOD OLD OMEN (compact and great) I made a rightclick to choose thing like "Send Data to KTM / Display KTM Data".
Nothing happens with right click - and in the config I can't find such options.
Both KTM and Omen's data formats have changed, and there hasn't been an adapter developed yet.
Assumeing the Healer / AOE and so on mode will work - I have to bring up that nasty big button bar to switch mode or go through Fu-Bar / Config and then bring up the bar - choose mode / remove the bar.....
Rightclick - select mode - done - would be great.
We don't have a good dropdown menu library for Ace3 yet. I'm working on one, but in the meantime, I've provided keybindings to let you cycle through modes. Find them under "Omen" in the Blizzard keybindings menu.
I find no longer options to pull out bars also.
They're not in yet, and will be coming back.
1: AOE mode and Healer mode are crashing and/or lagging people significantly. I myself had my computer come to a near halt when I went to AOE mode (I play a mage and as such was looking foward to that feature.)
The lagging/crashing should be fixed.
3: Not so much of a glitch, the lack of your own agro being singled out as a red bar did make tracking ones own threat more difficult.
This'll be coming back.
4: When I enabled the auto collapse so it would shrink to occupy less space between fights and/or targets, it very often would go back to its default size and "hang up" until a new target was selected for it to track.
Yes, this is a known bug and needs to be addressed.
Quote from yoshimo »
omen&threat were coded to be efficient, so i highly doubt that most of this blames are true. Prove me wrong here :)
I appreciate the vote of confidence, but there are some outstanding performance issues to be resolved yet. Threat is running very efficiently according to my tests, but Omen needs some work yet.
Quote from Chasgil »
uhm where is the option to show which people in the raid have omen2 installed? need it for tomorrow.
This is in now under "Version Checks"
Quote from triton5 »
The option to choose bar textures only seems to list "Blizzard" as an option.
Install SharedMedia
Would be nice to be able to put the modules bar at the top too.
Flexibility's coming. I ran out of time to produce the configuration polish I wanted, but I'll be adding it in as I have time.
Sorry for this post arriving with a bit of delay, haven't played much since the release of 2.4.
I dunno where the problem is, but the "feel" is confusing. It's the same for my whole guild.
I don't feel it lacks something... maybe it's kinda the opposite, it has too much and I have no way to understand what every function does, there are way too many options! Which may be good from a certain point of view, but not when you don't know how to configure them.
Where can I find a detailed guide? Omen1... you just installed it and it worked. Now I have these problems, many of these are probably related to the fact I don't know how to configure it.
1) I don't see some people in the list (nobody does). They only have the version of 2 days ago, not a very old one!
2) I cannot understand how to make it work "the old way". Single target? But sometimes the bars disappear
3) There is an option to select the Tank. One is from oRA2, one is from within blizzard UI, but I can't see the option anymore (in blizzard UI) where it used to be, what do I have to do?
I don't wanna bash the work the omen team did to produce this new threat meter, who has to read a completely different battle log. It's just that it feels different, it feels like I'm using a totally different addon that I have no clue how to use. Please allow me to understand, allow me to correctly use, and allow me to apreciate all the sleepless nights you spent to program it!
I mean no disrespect toward your work. I just want to understand how to use it.
Threat 2.0 version 66309. Got some bug for threat display at bloodboil fight in BT. After first P2. Threat stop update.
I need the text of the error, if possible.
Quote from Lindalas »
I like a lot of what I see in Omen2. Being able to change modes in the FuBar menu (and hide that in the window would be awesome. Another request I have is to go back to the old % display (from 0 to 130%) and, while at it... dump the decimal. I like to minimize clutter and "-34.7%" is a lot bigger than "75%".
This option is in under Modules -> Single Target now.
Quote from sam.freak »
I'm seeing libdropdown-1.0 under optdeps, but can't find a DL link anywhere (and it doesn't seem to be includedanywhere.
It's in branches and isn't finished. Don't worry about it.
Quote from gades »
Actually Omen is pretty bugged when using the druid growl, it gives me something like millions of threat (it started with 45690......) and basically it screw up the threat since all other bars collapse to left being to small compared to my super threat, is it going to be fixed soon?
This is fixed.
Quote from BBR »
Omen2 is pretty heavy on the addonspamfu meter.
It's TL2 right?
Yes. I'm working on cutting the traffic down. It grew due to GUID usage, and I opted out of any optimization of it up front in order to be a good programmer. I've made one protocol change to lighten it a bit, and will be making another Monday.
Quote from silvermoons »
I think that Omen2 has so many bugs and is so hard to even to get to work that im having my whole guild change away from it. A Rewrite HAS to be done to fix this!!!!!!!!
It's not quite finished. I didn't get the scale of testing I was hoping for on the PTR, so the live push becomes my PTR. Not much that can be done about it. The best you can do is continue to report bugs and I'll get them fixed up ASAP. Beyond that...well, I'm doing my best, and if it's not what you want, you always have the option of writing your own.
Quote from Maddhawk »
2: Omen2 not seeing the agro reset on Zul'Jin every 20%.
This was a problem with the NPC module framework. It's fixed now.
Quote from bimmian »
How does Omen2 handle feign death since it doesn't create an event in the combatlog?
Same way as it did before - looks for the cast event, waits a little looking for a resist, and clears threat if it doesn't find one.
Quote from Shades228 »
Threat2.0-LUA:653 attempt to call global 'IsGroupOfficer'(a nil value) happening everytime Leo changes forms.
One thing I do want to make you aware of, although I don't know if it's been fixed in one of the builds of the last horus: Soulshatter and Invisibility both don't show on the threat. Our locks and mages got scared shitless when they used their threat dumps and they were still top on Omen (and yes, they're absolutely HORRIBLE on managing threat :P).
Treat the player's bar differently from other bars. It would be great to be able to configure your own threat bar differently from other player's bars. Since I trim my UI for high contrast and zero unnecessary data and as a warlock mostly play with the single-target mode, it would be great if my own bar would be customizable on its own. You already allow us to customize the aggro threshold bar differently.
The features for your own bar could be the same as for the aggro bar. (height, color, alpha, texts visibility, maybe even a different TPS calculation frequency)
This will be coming.
Quote from Neo »
Not sure if this has been requested yet but is it possible to get a raid/party version report. We seem to have people that aren't updating Omen and it would be nice to see the raid version per person.
This should be in now.
2. Omen doesn't want to stay hidden: I join a team it pops up, I enter an instance it pops up, I dismount, my pet spawns and it pops up, etc. I want it to stay hidden until I hit the button.
This is an outstanding issue and needs to be fixed.
The moment we get the Insignificance debuff in phase 2, TPS stops. However, it doesn't seem to restart for everyone when the debuff fades. Not sure if this is an Omen thing or a Threat thing though.
Do you get any errors with this?
Sorry if this has already been reported, but it doesn't appear that Omen is being reset on Leotheras the Blind whenever he changes forms or Whirlwinds.
This should be fixed.
Please return the option to NOT display when solo with a pet.
I'll put this back in.
The one and most important option I miss is the ability to drag the tank aggro bar out to the screen and close the omen window all together. This allowed me just to see the percent & time til aggro gain on the target it was in, without it taking up so much room. I would put it next to my other raid windows and one bar worked so well.
In the new version this option isn't there yet that I can find. Is this going to be worked back in on omen2?
Yes, this is coming back eventually.
When accessing omen2 options from the main interface screen by hitting escape then picking interface. Then click addons, then omen. Some of the omen options get clipped because there isn't enough room for them.
I don't know if there's a fix I can make for this, but I'll bring it up to the Ace3 guys.
I updated to the latest build of Omen 2 and now it's only showing my threat in groups on my omen, and on other ppl in my group omen its not showing me at all.
I tried clicking the, 'show self' option, as well as turning off the all of the other classes and pets except warriors / druids. But I still cannot recreate the way the threat bars. Even with, 'always show self' option clicked, Omen doesn't show my threat in the threat meter.
This should be fixed.
Just a little request : could it be possible to reintroduce the sound "link" in the alarm sounds ? I used to be used to that one and now, I had to change and sometimes when I hear it, I don't have the reflex to FD (hunter inside).
I think that one was being injected into SharedMedia by another mod. It's not a part of Omen, just selectable by it if it's available.
1) I don't see some people in the list (nobody does). They only have the version of 2 days ago, not a very old one!
On the contrary, that's probably a good 3 dozen commits old by now. People will need to update very regularly right now due to the fact that I'm working bugs out of the new version.
2) I cannot understand how to make it work "the old way". Single target? But sometimes the bars disappear
Single Target is the old-style meter. If the bars are disappearing, it's a bug. However, I've fixed a number of those. Please let me know if it still happens when all group members are using the latest version.
3) There is an option to select the Tank. One is from oRA2, one is from within blizzard UI, but I can't see the option anymore (in blizzard UI) where it used to be, what do I have to do?
In the blizzard raid UI, right click a raid member and select "Promote to Main Tank".
Single Target is the old-style meter. If the bars are disappearing, it's a bug. However, I've fixed a number of those. Please let me know if it still happens when all group members are using the latest version.
What I've noticed so far (3 members have the old version tho) is that nothing appears (usually) if no target is selected. If I select a monster, or someone, usually that someone's target appears in place of "Omen2" and bars work more or less right.
Sometimes they get "stuck" after a few mobs get killed. But if I unselect the target, and select it again, it starts working once more.
Sorry, didn't have the chance to do thoroughful tests.
In the blizzard raid UI, right click a raid member and select "Promote to Main Tank".
That's where it was, but I couldn't find it tonight! I'll check again.
Ok been having loads of problems with Omen2 and threat2.0 tonight was most the cause of my raids issues tonight from people DCing massive lag spike at Illidan when He does the blue fire(Flame Burst) in demon form comes the whole raid was complaining of freezing.
In Hyjal it was eating my fps and causing others to lag as well as my self it seems to be using a hell of a lot of memory Omen2 16Meg Threat2.0 3.03Meg threat was using more at some points
The Nightbane module seems buggy again. There are no threat resets right now... my hunters just got wtfpwned. Using r66721 (not sure if thats a Threat or Omen revision, but thats what the title bar says.)
omen2 has worked fine for me since 2.4 in groups etc. but tonight i updated before a raid and it didn't work at all. almost everyone in the raid had a different version which, i assume, is less than ideal. i could see my own threat and occasionally one of our healers would pop up but never for long.
is this the kind of problem which would be solved by making sure the whole raid its using the latest version?
Would it be possible to add an option to enforce a full threatlib clear? It seems that sometimes Omen keeps the aggro between wipes when it should not.
this has been driving me nuts but every time I relog Omen reverts to "grow up" even though the option is not checked. This along with the not properly collapsing thing. Once I unlock omen and drag it back where it's supposed to be all works fine other than not fully collapsing........until I relog again. Something got fixed partially though because it used to be out of position upon logging in. Now it starts out in the right place it just grows up and then has to be repositioned. Checking/unchecking the "grow up" option by itself does not stop it from growing up, you have to unlock omen as well. Err more appropriately you just have to unlock it and possibly move it, the grow up checkbox doesn't see to have any effect on fixing the problem.
Version r66755. Several others in my raid have the same version. I can only see my own bar - nothing else. I have the omen window expanded almost 2/3rds the height of my screen, and locked at that size. I still only see my own threatbar.
Tried completely deleting the omen folder and reinstalling again - same problem. Others say they have it working, but were not able (dur?) to tell me what version(s) they were using.
when I use the check versions options, I get nothing reported from anyone.
I received the following two errors tonight while using version 66755.
This first one happens whenever someone uses an aggro drop/reduction skill such as Soulshatter or Vanish.
[2008/03/28 22:57:17-1369-x7]: Omen-Omen r66676 / Threat-2.0 r66721\Libs\Threat-2.0\ThreatClassModuleCore.lua:1160: attempt to concatenate field 'target' (a nil value)
Omen-Omen r66676 / Threat-2.0 r66721\Libs\Threat-2.0\ThreatClassModuleCore.lua:1181: in function <...ddOns\Omen\Libs\Threat-2.0\ThreatClassModuleCore.lua:1175>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0\AceTimer-3.0.lua:140: in function <Interface\AddOns\Ace3\AceTimer-3.0\AceTimer-3.0.lua:114>
This second errors was during the Zul'Jin fight in ZA.
[2008/03/29 01:18:19-1369-x1]: ...s\Omen\Libs\Threat-2.0\NPCModules\ZulAman\Zuljin.lua:66: attempt to index global 'BB' (a nil value):
Omen-Omen r66676 / Threat-2.0 r66721\Libs\Threat-2.0\ThreatNPCModuleCore.lua:273: in function <...\AddOns\Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:264>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0\AceAddon-3.0.lua:316: in function `InitializeAddon'
AceAddon-3.0\AceAddon-3.0.lua:404: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:397>
<in C code>: ?
<in C code>: in function `LoadAddOn'
AddonLoader-1.0\Conditions.lua:30: in function `Trigger'
AddonLoader-1.0\Conditions.lua:146: in function <Interface\AddOns\AddonLoader\Conditions.lua:145>
<in C code>: ?
AceEvent-2.0-66043 (Ace2):298: in function `TriggerEvent'
AceEvent-2.0-66043 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
<in C code>: in function `TurnOrActionStop'
<string>:"TURNORACTION":4: in function <[string "TURNORACTION"]:1>
Nope, but everyone had the same threat value seen. The TPS would occasionally tick over, but usually it just slowed to 0 and stopped mid fight after the insignificance buff, but didn't restart.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
i also have WAU without externals and inside omen folder is a threat2 folder, so that would mean that is should work right?
Just a little request : could it be possible to reintroduce the sound "link" in the alarm sounds ? I used to be used to that one and now, I had to change and sometimes when I hear it, I don't have the reflex to FD (hunter inside).
Thanks a lot, and anyway good work !
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumShould be addressed.
Still tracking this one down.
Should be fixed now.
Chis will be coming back.
Elaborate?
Should be fixed.
This isn't in yet, and will be coming back.
That sound probably came from SharedMedia. Install and that you should hopefully have it back.
/omen skin load classic
Modules -> Single Target -> Warnings
You can toggle columns off under Modules -> Single Target -> Columns
This is coming back.
Both KTM and Omen's data formats have changed, and there hasn't been an adapter developed yet.
We don't have a good dropdown menu library for Ace3 yet. I'm working on one, but in the meantime, I've provided keybindings to let you cycle through modes. Find them under "Omen" in the Blizzard keybindings menu.
They're not in yet, and will be coming back.
The lagging/crashing should be fixed.
This'll be coming back.
Yes, this is a known bug and needs to be addressed.
I appreciate the vote of confidence, but there are some outstanding performance issues to be resolved yet. Threat is running very efficiently according to my tests, but Omen needs some work yet.
This is in now under "Version Checks"
Install SharedMedia
I'll be adding this.
That's it for page 2. On to page 3!
Sorry for this post arriving with a bit of delay, haven't played much since the release of 2.4.
I dunno where the problem is, but the "feel" is confusing. It's the same for my whole guild.
I don't feel it lacks something... maybe it's kinda the opposite, it has too much and I have no way to understand what every function does, there are way too many options! Which may be good from a certain point of view, but not when you don't know how to configure them.
Where can I find a detailed guide? Omen1... you just installed it and it worked. Now I have these problems, many of these are probably related to the fact I don't know how to configure it.
1) I don't see some people in the list (nobody does). They only have the version of 2 days ago, not a very old one!
2) I cannot understand how to make it work "the old way". Single target? But sometimes the bars disappear
3) There is an option to select the Tank. One is from oRA2, one is from within blizzard UI, but I can't see the option anymore (in blizzard UI) where it used to be, what do I have to do?
I don't wanna bash the work the omen team did to produce this new threat meter, who has to read a completely different battle log. It's just that it feels different, it feels like I'm using a totally different addon that I have no clue how to use. Please allow me to understand, allow me to correctly use, and allow me to apreciate all the sleepless nights you spent to program it!
I mean no disrespect toward your work. I just want to understand how to use it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI need the text of the error, if possible.
This option is in under Modules -> Single Target now.
It's in branches and isn't finished. Don't worry about it.
This is fixed.
Yes. I'm working on cutting the traffic down. It grew due to GUID usage, and I opted out of any optimization of it up front in order to be a good programmer. I've made one protocol change to lighten it a bit, and will be making another Monday.
It's not quite finished. I didn't get the scale of testing I was hoping for on the PTR, so the live push becomes my PTR. Not much that can be done about it. The best you can do is continue to report bugs and I'll get them fixed up ASAP. Beyond that...well, I'm doing my best, and if it's not what you want, you always have the option of writing your own.
This was a problem with the NPC module framework. It's fixed now.
Same way as it did before - looks for the cast event, waits a little looking for a resist, and clears threat if it doesn't find one.
Should be fixed.
Page 4 done! Replies to page 5 incoming.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis should be fixed. If it isn't, please file a Jira bug report at http://jira.wowace.com/browse/OMEN
This will be coming.
This should be in now.
This is an outstanding issue and needs to be fixed.
Do you get any errors with this?
This should be fixed.
I'll put this back in.
Yes, this is coming back eventually.
I don't know if there's a fix I can make for this, but I'll bring it up to the Ace3 guys.
This should be fixed.
I think that one was being injected into SharedMedia by another mod. It's not a part of Omen, just selectable by it if it's available.
On the contrary, that's probably a good 3 dozen commits old by now. People will need to update very regularly right now due to the fact that I'm working bugs out of the new version.
Single Target is the old-style meter. If the bars are disappearing, it's a bug. However, I've fixed a number of those. Please let me know if it still happens when all group members are using the latest version.
In the blizzard raid UI, right click a raid member and select "Promote to Main Tank".
What I've noticed so far (3 members have the old version tho) is that nothing appears (usually) if no target is selected. If I select a monster, or someone, usually that someone's target appears in place of "Omen2" and bars work more or less right.
Sometimes they get "stuck" after a few mobs get killed. But if I unselect the target, and select it again, it starts working once more.
Sorry, didn't have the chance to do thoroughful tests.
That's where it was, but I couldn't find it tonight! I'll check again.
In Hyjal it was eating my fps and causing others to lag as well as my self it seems to be using a hell of a lot of memory Omen2 16Meg Threat2.0 3.03Meg threat was using more at some points
Does this mean another back-compat break? I totally respect the necessity, but knowing will help us plan accordingly ;)
Misdirection - Showing as hunter threat rather than the player who has been misdirected
Void reaver - Not adjusting for tank knockback threat therefore giving inaccurate results
also it's now seems to be incompatible with KTM threat meters and its new complexity is causing quite a disruption in our raids.
If you could get the new features as optionals and the choice to have a classic simple omen that worked with ktm etc that would be awsome :)
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumomen2 has worked fine for me since 2.4 in groups etc. but tonight i updated before a raid and it didn't work at all. almost everyone in the raid had a different version which, i assume, is less than ideal. i could see my own threat and occasionally one of our healers would pop up but never for long.
is this the kind of problem which would be solved by making sure the whole raid its using the latest version?
Tried completely deleting the omen folder and reinstalling again - same problem. Others say they have it working, but were not able (dur?) to tell me what version(s) they were using.
when I use the check versions options, I get nothing reported from anyone.
This is all I keep getting. I can't get Omen to work at all, and I've updated it a few times today.
This first one happens whenever someone uses an aggro drop/reduction skill such as Soulshatter or Vanish.
[2008/03/28 22:57:17-1369-x7]: Omen-Omen r66676 / Threat-2.0 r66721\Libs\Threat-2.0\ThreatClassModuleCore.lua:1160: attempt to concatenate field 'target' (a nil value)
Omen-Omen r66676 / Threat-2.0 r66721\Libs\Threat-2.0\ThreatClassModuleCore.lua:1181: in function <...ddOns\Omen\Libs\Threat-2.0\ThreatClassModuleCore.lua:1175>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0\AceTimer-3.0.lua:140: in function <Interface\AddOns\Ace3\AceTimer-3.0\AceTimer-3.0.lua:114>
This second errors was during the Zul'Jin fight in ZA.
[2008/03/29 01:18:19-1369-x1]: ...s\Omen\Libs\Threat-2.0\NPCModules\ZulAman\Zuljin.lua:66: attempt to index global 'BB' (a nil value):
Omen-Omen r66676 / Threat-2.0 r66721\Libs\Threat-2.0\ThreatNPCModuleCore.lua:273: in function <...\AddOns\Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:264>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0\AceAddon-3.0.lua:316: in function `InitializeAddon'
AceAddon-3.0\AceAddon-3.0.lua:404: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:397>
<in C code>: ?
<in C code>: in function `LoadAddOn'
AddonLoader-1.0\Conditions.lua:30: in function `Trigger'
AddonLoader-1.0\Conditions.lua:146: in function <Interface\AddOns\AddonLoader\Conditions.lua:145>
<in C code>: ?
AceEvent-2.0-66043 (Ace2):298: in function `TriggerEvent'
AceEvent-2.0-66043 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
<in C code>: in function `TurnOrActionStop'
<string>:"TURNORACTION":4: in function <[string "TURNORACTION"]:1>
---
Hope these help. Great job on a great mod.
Nope, but everyone had the same threat value seen. The TPS would occasionally tick over, but usually it just slowed to 0 and stopped mid fight after the insignificance buff, but didn't restart.