Authors CurseForge

I posted this bug to other topic by mistake. Here's a bug I guess

1 of 2:
Interface/Addons/Omen/Libs/Threat-2.0/ThreatUtils.lua:212 attempt to index local 'guid' (a number value)

2 of 2:
Interface/Addons/Omen/Libs/Threat-2.0/ThreatNPCModuleCore.lua:372 attempt to index field 'attacks' (a nil value)

Omen used to display a message in the middle of my screen warning me when I had passed 90% of the tank's threat (I set this to 90%). Unfortunately, I can't get this message to appear now, although I can get screen shakes, sounds, etc. How can I get the message to appear? Thanks.

I'm not getting any errors, but I'm still not seeing any bars on Omen. Not even test bars.

Quote from burakerenn »

I posted this bug to other topic by mistake. Here's a bug I guess

1 of 2:
Interface/Addons/Omen/Libs/Threat-2.0/ThreatUtils.lua:212 attempt to index local 'guid' (a number value)

2 of 2:
Interface/Addons/Omen/Libs/Threat-2.0/ThreatNPCModuleCore.lua:372 attempt to index field 'attacks' (a nil value)

Indeed, those errors are driving me nuts, popping up 20+ times in a single encounter of Vashj.

autocollapse is broken and getting a few errors, which replaces everyones name with <Name> >.>

here are some ss:

no autocollapse?



<Name> lol:


thanks

Getting this error in BT. Apparently Gurtogg is causing Omen to stop calculating threat during Fel Rage as intended, but isn't restarting once Fel Rage ends.

[2008/03/26 19:01:49-923-x1]: Threat-2.0\Threat-2.0\ThreatNPCModuleCore.lua:299: Last parameter to :RegisterSpellHandler must be a function
Threat-2.0\Threat-2.0\ThreatNPCModuleCore.lua:299: in function `RegisterSpellHandler'
...-2.0\Threat-2.0\NPCModules\BlackTemple\Bloodboil.lua:13: in function `Init':
Threat-2.0\Threat-2.0\ThreatNPCModuleCore.lua:270: in function `OnInitialize'
Threat-2.0\Threat-2.0\ThreatNPCModuleCore.lua:227: in function <...AddOns\Threat-2.0\Threat-2.0\ThreatNPCModuleCore.lua:213>
Threat-2.0\Threat-2.0\ThreatNPCModuleCore.lua:250: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
AceEvent-3.0\AceEvent-3.0.lua:70: in function <Interface\AddOns\Ace3\AceEvent-3.0\AceEvent-3.0.lua:69>

 ---

Hello, just like to say Omen was awesome before 2.4, it rocks even harder now

Having 2 problems thou and are probably super simple, but was unable to find any info so thought i'd ask here, (sorry for doing so in this thread)

1. Is it still possible to version check within Omen?
2. is there any type of clear threat command still in the new version?

Edit:

Just remembered a problem we had tonight, with revision 66077 (highest version at time of raid)...

In SSC tonight on Single Target Mode, threat was not cleared on Hydross on transition, or on Leotheras on changing forms and after a whirlwind...as it would have been pre 2.4 version. Didn't get errors for any of the issues.

Thought you would like to know, can upload a combat log if you need it.

Thanking you in advanced for your reply. Keep up the awesome work.

Reporting a bug

Date: 2008-03-26 20:23:02
ID: 53
Error occured in: Global
Count: 1
Message: ...\AddOns\Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua line 457:
  attempt to call method 'ScheduleTimer' (a nil value)
Debug:
  (tail call): ?
  ...\AddOns\Omen\Libs\Threat-2.0\ThreatNPCModuleCore.lua:457: ?()
  ...gos\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
   ...gos\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
  [string "safecall Dispatcher[1]"]:4:
   [string "safecall Dispatcher[1]"]:4
  [C]: ?
  [string "safecall Dispatcher[1]"]:13: ?()
  ...gos\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
  ...ace\AddOns\Bongos\libs\AceEvent-3.0\AceEvent-3.0.lua:70:
   ...ace\AddOns\Bongos\libs\AceEvent-3.0\AceEvent-3.0.lua:69

a plethora of errors during tonight's ssc extravaganza:

count: 2:

Threat-2.0\\Threat-2.0\\ThreatUtils.lua:212: attempt to index local 'guid' (a number value)\nThreat-2.0\\Threat-2.0\\ThreatNPCModuleCore.lua:214: in function <...AddOns\\Threat-2.0\\Threat-2.0\\ThreatNPCModuleCore.lua:213>\nThreat-2.0\\Threat-2.0\\ThreatNPCModuleCore.lua:244: in function `ActivateModule'\nThreat-2.0\\Threat-2.0.lua:443: in function `?'\nThreat-2.0\\Threat-2.0\\ThreatUtils.lua:184: in function `?'\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:146: in function <...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146>\n<string>:\"safecall Dispatcher[4]\":4: in function <[string \"safecall Dispatcher[4]\"]:4>\n<in C code>: ?\n<string>:\"safecall Dispatcher[4]\":13: in function `?'\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:91: in function `Fire'\nAceComm-3.0\\AceComm-3.0.lua:244: in function <Interface\\AddOns\\Ace3\\AceComm-3.0\\AceComm-3.0.lua:233>\n\n ---

count: 17:

Threat-2.0\\Threat-2.0\\ThreatNPCModuleCore.lua:457: attempt to call method 'ScheduleTimer' (a nil value)\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:146: in function <...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146>\n<string>:\"safecall Dispatcher[1]\":4: in function <[string \"safecall Dispatcher[1]\"]:4>\n<in C code>: ?\n<string>:\"safecall Dispatcher[1]\":13: in function `?'\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:91: in function `Fire'\nAceEvent-3.0\\AceEvent-3.0.lua:70: in function <Interface\\AddOns\\Ace3\\AceEvent-3.0\\AceEvent-3.0.lua:69>\n\n ---

count: 54:

Threat-2.0\\Threat-2.0\\ThreatNPCModuleCore.lua:372: attempt to index field 'Attacks' (a nil value)\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:146: in function <...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146>\n<string>:\"safecall Dispatcher[20]\":4: in function <[string \"safecall Dispatcher[20]\"]:4>\n<in C code>: ?\n<string>:\"safecall Dispatcher[20]\":13: in function `?'\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:91: in function `Fire'\nAceEvent-3.0\\AceEvent-3.0.lua:70: in function <Interface\\AddOns\\Ace3\\AceEvent-3.0\\AceEvent-3.0.lua:69>\n\n ---

count: 228:

Threat-2.0\\Threat-2.0\\ThreatNPCModuleCore.lua:372: attempt to index field 'Attacks' (a nil value)\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:146: in function <...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146>\n<string>:\"safecall Dispatcher[20]\":4: in function <[string \"safecall Dispatcher[20]\"]:4>\n<in C code>: ?\n<string>:\"safecall Dispatcher[20]\":13: in function `?'\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:91: in function `Fire'\nAceEvent-3.0\\AceEvent-3.0.lua:70: in function <Interface\\AddOns\\Ace3\\AceEvent-3.0\\AceEvent-3.0.lua:69>\n\n ---

count: 14:

Threat-2.0\\Threat-2.0\\ThreatUtils.lua:212: attempt to index local 'guid' (a number value)\nThreat-2.0\\Threat-2.0\\ThreatNPCModuleCore.lua:214: in function <...AddOns\\Threat-2.0\\Threat-2.0\\ThreatNPCModuleCore.lua:213>\nThreat-2.0\\Threat-2.0\\ThreatNPCModuleCore.lua:244: in function `ActivateModule'\nThreat-2.0\\Threat-2.0.lua:443: in function `?'\nThreat-2.0\\Threat-2.0\\ThreatUtils.lua:184: in function `?'\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:146: in function <...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146>\n<string>:\"safecall Dispatcher[4]\":4: in function <[string \"safecall Dispatcher[4]\"]:4>\n<in C code>: ?\n<string>:\"safecall Dispatcher[4]\":13: in function `?'\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:91: in function `Fire'\nAceComm-3.0\\AceComm-3.0.lua:244: in function <Interface\\AddOns\\Ace3\\AceComm-3.0\\AceComm-3.0.lua:233>\n\n ---

count: 23:

Threat-2.0\\Threat-2.0\\ThreatNPCModuleCore.lua:457: attempt to call method 'ScheduleTimer' (a nil value)\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:146: in function <...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146>\n<string>:\"safecall Dispatcher[1]\":4: in function <[string \"safecall Dispatcher[1]\"]:4>\n<in C code>: ?\n<string>:\"safecall Dispatcher[1]\":13: in function `?'\nCallbackHandler-1.0\\CallbackHandler-1.0.lua:91: in function `Fire'\nAceEvent-3.0\\AceEvent-3.0.lua:70: in function <Interface\\AddOns\\Ace3\\AceEvent-3.0\\AceEvent-3.0.lua:69>\n\n ---

Quote from Razumikhin »

Omen used to display a message in the middle of my screen warning me when I had passed 90% of the tank's threat (I set this to 90%). Unfortunately, I can't get this message to appear now, although I can get screen shakes, sounds, etc. How can I get the message to appear? Thanks.

You need to go to the Output section in the Omen settings and choose something like Parrot or SCT to use their Notification area.

Quote from Antiarc »

Regarding warnings: You should be able to turn them off from the modules -> single target -> warnings menu.

Sorry it's been such a rough transition. I didn't have nearly as much time as I'd have liked to polish it up. :/

Warnings: The flash screen totally ignores the settings. But, if I only enable FCT - I get no warnings. So there's something wrong with the warnings themselves to be honest. It seems only the sound/flash screen actually works.

And about rough transitions, it's understandable. Don't fret it. Chill, kick back...

Bugged threat meter



If I use the ovewrview setting, the display sometimes dont refresh properly and I wind up with multiple overlapping bars and names. I have ran AceUpdater recently and I still got this in a group so dunno why. For now I'm using single setting. It would be nice if this could be fixed before my guild goes to raid so it'd be easier to keep track of the top few aggro-ers.

EDIT: typos fixed

Not sure if this is a bug, and also not sure if I missed this being covered in the previous pages. If it was I apologize up front. One of the hottest new features of Omen2 was the Raid Icon feature for multiple mob threat measurement. I have found the options to toggle the icons, and they show on test bars, but during a raid or group, none of the icons show on the bars in any mode. Can anyone help or is this feature non-operational yet?

Dont know if this has been posted before, but I seem to be getting extremely frequent threat warnings even when im well below the set threshold for warnings.

Im not sure how, why, or what is causing it. I just know that there is something very different in the warning system compared to the old(pre 2.4) omen. As it is now, im often flooded with warnings for no apparent reason.

Please, please, please add back the ability to load profiles via command line (then "skin" option doesn't seem to carry over between characters/accounts). An awful lot of compilation authors include this addon, and being able to position every element of the UI for a given character with minimal text editing is key for a lot of us.

Give back alternate bar textures such as litestep etc..
Maybe I'm doing something wrong but I can't change it and it's really bugging me as the rest of my ui has the same texture allover.

Quote from piids »

Give back alternate bar textures such as litestep etc..
Maybe I'm doing something wrong but I can't change it and it's really bugging me as the rest of my ui has the same texture allover.

Works fine now, make sure you have LibSharedMedia-3.0

Quote from Saynt »

Works fine now, make sure you have LibSharedMedia-3.0

No, you should only need to have SharedMedia installed. It supports all the versions of LibSharedMedia that the various addons use.