Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
my guild and i have been updating this as often as possible, tonight we are on bloodboil, and still omen2 is so buggy its boarding on useless to us. I have some experience with mods and have done everything i can to get it working but im out of ideas.
the entire raid is on r67186
-only one tank is showing up at a time (many bosses require multiple tanks)
-most peoples TPS is showing at less than 500...waaaay off
-bloodboil in particular does a debuff which cause no threat to be generated by anyone for 20 seconds, this breaks omen2 for the duration of the fight
-most players cant see their own threat bar
-healer and aoe mode seem to be throughly broken
-overview mod shows players, but the data is incorrect, and is constantly "overwritten" by other bars, making it unreadable
-often times will not reset after a wipe.
all players are using the ost up to date ace and threatlib available to us.
don't get me wrong antriac, im a huge fan of omen, and i really like the idea of omen2...just atm...its not working = /
Our guild had exactly the same problem tonight on exactly the same boss, at the time we all had different versions running, we all updated and had the same version 67322, but still had strange aggro problems... hope you finda fix soon cause atm on some agro sensitive fights are pretty much impossible to attempt atm
Is there a Technical reason why older versions (as in versions since 2.4) are incompatible with each other? Even if the older persons threat is not 100% right its better to atleast get an idea then not to have anyone show up at all. Esp since omen is updated about once every hour now (or every 5 min, like tonight.....) and between the hour it seems to break compatiblity.
2: I use it alone mostly as I'm a hunter and like to track my threat vs. my pets so that I don't have to waste mana always feigning death. The old version did this pretty well. I know it's probably at the bottom of the list of things to get done, but it doesn't seem to track threat from the pet right now. I've reached 240% threat and still not pulled something off of my pet.
Do a little research. Blizzard completely changed the combatlog in 2.4, old versions of Omen are 100% broken. Antiarc is doing an amazing job getting it working again in next to no time, so sit tight.
Did you know that once upon a time people played without threat meters of any kind?
Yes I am aware that the combat system changed and that will have impacted on Omen. I am also aware that the Omen I was using prior to updating it seemed to be working. I agree, Antiarc is doing an amazing job with thios mod and I have never brought that into question. What I was asking for was (and only if possible?) A link to the most stable version so that Antiarc isn't bombarded by Bug posts.
I was one of those people who used to play without a Threat Meter, but as they mods evolved, so did peoples playstyles and the game itself to the point where Threat Meters are almost a must. Very few people would comfortably go back to pre-threat meter days by choice.
What's curious though, is why 2.4 is the exact time to do a full rewrite.
Wouldn't it have been faster to just make Omen1 compatible with 2.4, and then start development on a seperate Omen2 as replacement?
Obviously the author understands we appreciate the effort he puts into the project, but the way the conversion is handled is obviously causing a lot of problems.
I'm currently having a problem with Omen. I only use the Single Target feature. Within that I have set it up to always show my threat. This feature is currently not working, at least for me.
Also with 2.4 Omen has not been showing up in the Rock menu. Is this intentional?
I hate the warning sound. It decreases my enjoyment of playing wow a hundred fold. Can I delete the soundfile? Tips for editing the lua not to make the sound?
I recommend using a different sound, no one in my guild likes it at all.
Failing that, I recommend making the audible warning optional, or not existent.
I hate the warning sound. It decreases my enjoyment of playing wow a hundred fold. Can I delete the soundfile? Tips for editing the lua not to make the sound?
I recommend using a different sound, no one in my guild likes it at all.
Failing that, I recommend making the audible warning optional, or not existent.
Just go into Modules -> Single target -> Warnings (if iirc)
There you will find that u can adjust the lvl of threat where u want the warning and if u want a warning sound when passing that lvl of threat.
Will there be an official Omen2 thread, btw? I noticed that people post on 2 threads now, this one (unofficial Omen 2) and the old, official Omen thread...
Will there be an official Omen2 thread, btw? I noticed that people post on 2 threads now, this one (unofficial Omen 2) and the old, official Omen thread...
Better to create a new one IMO, where Antiarc controls the first post. *shrug* Or just rename the old one, so that people know that they should post there.
something i noticed with the latest omen 67544 is that whenever someone has gotten the "insignificance" debuff from Bloodboil (BT) his threat nolonger updates when the debuff runs out. Rather important bug imo.
Who liked the original Omen? I for one liked it. There were so many reasons why I used it, why I switch from KLM, and why I desire that functionality in Omen2. I find myself in the majority it seems in this wish, yet I seem to have a deeper understanding of the situation then the childish posts attacking its functionality. Blizzard changed the Combatlog. for the better I think. Omen uses the combat log. I have not coded Omen so I have no clue how much of a rewrite is involved in changing it to still work in the 2.4 patch. Since it is not working, for me yet, I must assume that the changes are larger that any one of us would have liked. The additional changes proposed in Omen2 have my mouth watering to try them once they work. I wish the coder all the best in making them work in a time frame that I hope is short and soon. To all other who are crying about it not working..... well what can I say. make your own threat meter :-) I would love to comment on its glowing success and rapid turn around when Blizzard changeds the rules.
It seems like the wiping of threat during a fight, like on Hydros or Leotheras isn't working. Maybe I'm way off here (I have never written any addons) and I have not tested this in any way, but...
in the function ThreatLib.OnCommReceive:RAID_MOB_THREAT_WIPE this line exists:
"if (cooldownTimes[mob_guid] or 0) > 15 then"
I think however it should look something like:
"if GetTime() - (cooldownTimes[mobName] or 0) > 15 then"
otherwise cooldownTimes[mobName] will not get a value and hence the function will never reset the raid aggro on the mob.
in 1600x1200 resolution i cannot access the Profile settings for Omen.
It's is located in the new Interface Options Addons Tab but Omen has it's own "Outline" style menu tree that takes up half of the right pane. This leaves a very small column for the actual options.
In my case, the right side of all the profile drop boxes are cut off behind the scroll bar, so I can't actually change any of the profile options.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Our guild had exactly the same problem tonight on exactly the same boss, at the time we all had different versions running, we all updated and had the same version 67322, but still had strange aggro problems... hope you finda fix soon cause atm on some agro sensitive fights are pretty much impossible to attempt atm
AddOn: Omen
File: Threat-2.0.lua
Line: 143
Count: 1
All raid members show as unknown (as do version numbers from version check) and the following lua error.
Date: 2008-04-01 02:02:53
ID: 48
Error occured in: Global
Count: 19
Message: ...nterface\AddOns\Threat-2.0\Threat-2.0\Threat-2.0.lua line 143:
bad argument #8 to 'format' (number expected, got no value)
Debug:
(tail call): ?
[C]: format()
...nterface\AddOns\Threat-2.0\Threat-2.0\Threat-2.0.lua:143:
...nterface\AddOns\Threat-2.0\Threat-2.0\Threat-2.0.lua:140
...nterface\AddOns\Threat-2.0\Threat-2.0\Threat-2.0.lua:369: ?()
...terface\AddOns\Threat-2.0\Threat-2.0\ThreatUtils.lua:190: ?()
...edia-3.0\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
...edia-3.0\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
[string "safecall Dispatcher[4]"]:4:
[string "safecall Dispatcher[4]"]:4
[C]: ?
[string "safecall Dispatcher[4]"]:13: ?()
...edia-3.0\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
Ace3\AceComm-3.0\AceComm-3.0.lua:246:
Ace3\AceComm-3.0\AceComm-3.0.lua:235
AddOn: Omen
File: ThreatUtils.lua
Line: 212
Count: Infinite
--------------------------------------------------
Error: bad argument #8 to 'format' (number expected, got no value)
AddOn: Omen
File: Threat-2.0.lua
Line: 143
Count: 20
2: I use it alone mostly as I'm a hunter and like to track my threat vs. my pets so that I don't have to waste mana always feigning death. The old version did this pretty well. I know it's probably at the bottom of the list of things to get done, but it doesn't seem to track threat from the pet right now. I've reached 240% threat and still not pulled something off of my pet.
Yes I am aware that the combat system changed and that will have impacted on Omen. I am also aware that the Omen I was using prior to updating it seemed to be working. I agree, Antiarc is doing an amazing job with thios mod and I have never brought that into question. What I was asking for was (and only if possible?) A link to the most stable version so that Antiarc isn't bombarded by Bug posts.
I was one of those people who used to play without a Threat Meter, but as they mods evolved, so did peoples playstyles and the game itself to the point where Threat Meters are almost a must. Very few people would comfortably go back to pre-threat meter days by choice.
Thanks for the comments though....
http://forums.worldofwarcraft.com/thread.html?topicId=5640666467&postId=56401791872&sid=1#6
What's curious though, is why 2.4 is the exact time to do a full rewrite.
Wouldn't it have been faster to just make Omen1 compatible with 2.4, and then start development on a seperate Omen2 as replacement?
Obviously the author understands we appreciate the effort he puts into the project, but the way the conversion is handled is obviously causing a lot of problems.
Date: 2008-04-01 18:33:04
ID: 52
Error occured in: Global
Count: 1
Message: ...terface\AddOns\Threat-2.0\Threat-2.0\ThreatUtils.lua line 185:
attempt to call field '?' (a nil value)
Debug:
(tail call): ?
...terface\AddOns\Threat-2.0\Threat-2.0\ThreatUtils.lua:185: ?()
...edia-3.0\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
...edia-3.0\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
[string "safecall Dispatcher[4]"]:4:
[string "safecall Dispatcher[4]"]:4
[C]: ?
[string "safecall Dispatcher[4]"]:13: ?()
...edia-3.0\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
Ace3\AceComm-3.0\AceComm-3.0.lua:246:
Ace3\AceComm-3.0\AceComm-3.0.lua:235
AddOns:
AtlasLoot, vAtlasLoot Enhanced v4.04.00
AucAdvanced, v5.0.PRE.2887
AucFilterBasic, v5.0.PRE.2887 (BillyGoat)
AucStatClassic, v5.0.PRE.2887 (BillyGoat)
AucStatPurchased, v5.0.PRE.2887 (BillyGoat)
AucStatSimple, v5.0.PRE.2887 (BillyGoat)
AucStatStdDev, v5.0.PRE.2887 (BillyGoat)
Bartender3, v3.1.2 r65221
BeanCounter, v5.0.PRE.2887 (BillyGoat)
BigWigsExtras, v2.0
BigWigsPlugins, v2.0
BigWigs, v2.0 r66723
BigWigsTimers, v1
BigWigsCommonAuras, v1
BotWhisperer, v0.1
Capping, v2.4.001
Cartographer, vr67263
CartographerCleanup, v1.0
CartographerHerbalism, v1.0
CartographerMailboxes, v1.0
CartographerMining, v1.0
CartographerTrainers, v1.0
CartographerVendors, v1.0
CartographerBattlegrounds, v2.0
CartographerCoordinates, v2.0
CartographerFoglight, v2.0
CartographerGroupColors, v2.0
CartographerGuildPositions, v2.0
CartographerInstanceLoot, v2.0
CartographerInstanceMaps, v2.0
CartographerInstanceNotes, v2.0
CartographerLookNFeel, v2.0
CartographerNotes, v2.0
CartographerPOI, v2.0
CartographerProfessions, v2.0
CartographerWaypoints, v2.0
CartographerZoneInfo, v2.0
CartographerImport, v1.0
CartographerNoteshare, v1.0
CartographerQuestObjectives, v0.9b
CartographerQuests, v0.2
CartographerQuicknotes, v0.1
CartographerStats, v1.0
ClassTimer, v1.0
Clique
ClosetGnomeBanker, v1
ClosetGnomeBigWigs, v1
ClosetGnomeGatherer, v1
ClosetGnomeMount, v1
ClosetGnomeOhNoes, v2
ClosetGnomeSwitcher, v1.0.66102
ClosetGnomeZone, v1
ClosetGnome, v1.0.65177
DMWho, v1.0
ElkBuffBars, v2.1
Enchantrix, v5.0.PRE.2887
EnchantrixBarker, v5.0.PRE.2887 (BillyGoat)
EnhTooltip, v5.0.PRE.2887
EQCompare, v1.4
GFWLinkerator, v2.4
FuBarAlchemyFu
FuBarDurabilityFu, v2.0
FuBarExperienceFu, v1.1 $Revision: 65606 $
FuBarFactionsFu, v2.2
FuBarGarbageFu, v2.0.$Revision: 55484 $
FuBarMiniClockFu, v1.0
FuBarMiniPerfsFu, v1.0
FuBarMoneyFu, v20000-1
FuBarQuestsFu, v2.0
FuBarRaidBuffFu, v1.0
FuBarReagentFu, v2.0.10
FuBarRegenFu, v2.1.0
FuBarTopScoreFu, v2.0
FuBarVolumeFu, v2.0.$Revision: 55081 $
FuBarWhisperFu, v2.0
FuBar, v60201
GhostCDP, v1.07
Informant, v5.0.PRE.2887
KLHThreatMeter, v21.11
AbacusLib
Ace2
Ace3
BabbleBoss22, v2.2.$Revision: 57540 $
BabbleClass22, v2.2.$Revision: 54514 $
BabbleFaction22, v2.2.$Revision: 54514 $
BabbleHerbs22, v2.2.$Revision: 54514 $
BabbleInventory22, v2.2.$Revision: 54514 $
BabbleOre22, v2.2.$Revision: 54514 $
BabbleSpell22, v2.2.$Revision: 54514 $
BabbleTradeskill22, v2.2.$Revision: 54514 $
BabbleTrainer22, v2.2.$Revision: 54514 $
BabbleVendor22, v2.2.$Revision: 54514 $
BabbleZone22, v2.2.$Revision: 54514 $
Babble22, v2.2.$Revision: 66632 $
LibBabbleBoss30
LibBabbleClass30
LibBabbleSpell30
LibBabbleZone30
LibBanzai20, v2.0
CandyBar
CrayonLib
Deformat, v1.0 $Revision: 3817 $
DewdropLib
FuBarPlugin20, v2.0 $Revision: 66634 $
GratuityLib, vr$Revision: 66041 $
LibHealComm30
OneStorage, v2.0.$Revision: 55087 $
PaintChipsLib
Parser30, v3.0
LibPeriodicTable31, v3.1
LibPeriodicTable31Consumable, v3.1
LibPeriodicTable31Misc, v3.1
LibPeriodicTable31Tradeskill, v3.1
Quixote
RosterLib, v2.1
LibSharedMedia20
LibSharedMedia30, v3.0
SinkLib
LibSink20
SpecialEventsEmbed
SpecialEventsAura20
SpecialEventsLoot10
SpecialEventsMount20
TabletLib
LibTalentQuery10, v$Rev: 66356 $
Talismonger30
Threat20
TouristLib
LibTourist30
Waterfall10
WindowLib
LibAbacus30
LibCrayon30
LibDogTag30, v1.0
LibDogTagUnit30, v1.0
LibDruidMana10, v1.0
LibGUIDRegistry01
LibJostle30
LibMobHealth40, v1.0
LibRock10
LibRockComm10
LibRockConfig10
LibRockConsole10
LibRockDB10
LibRockEvent10
LibRockHook10
LibRockLocale10
LibRockModuleCore10
LibRockTimer10
LibRollCall20, v2.0
LitheTooltipDoctor, v1.0.19463
LittleWigsMagistersTerrace, v2.0
LittleWigs
MobHealth, v3.2
Necrosis, v2.0
OgriLazy, v1.0.7
Omen, vOmen r67269 / Threat-2.0 r67277
OneBag, v2.0.67228
OneRing, v2.0.55081
OneView, v2.0.55081
oRA2, v2.0.$Revision: 66672 $
PerfectRaid
PitBull, vr67180
PitBullAura, v2.0
PitBullBanzai, v1.0
PitBullBarFader, v0.1
PitBullCastBar, v2.0
PitBullCombatIcon, v2.0
PitBullCombatText, v2.0
PitBullComboPoints, v2.0
PitBullExperienceBar, v2.0
PitBullHealthBar, v2.0
PitBullHideBlizzard, v2.0
PitBullHighlight, v2.0
PitBullLeaderIcon, v2.0
PitBullMasterLooterIcon, v2.0
PitBullPowerBar, v2.0
PitBullPrat, v2.0
PitBullPvPIcon, v2.0
PitBullRaidTargetIcon, v2.0
PitBullRangeCheck, v0.1
PitBullReadyCheckIcon, v2.0
PitBullReputationBar, v2.0
PitBullRestIcon, v2.0
PitBullSpark, v2.0
PitBullThreatBar, v2.0
PitBullVisualHeal, v2.0
PitBullVoiceIcon, v2.0
Prat, v2.0 67125
PratAutoLoD
PratFuBar
PratModules
PratWaterfall
Quartz, v0.1.0
QuartzFlight, v1.0
QuartzFocus, v1.0
QuartzGCD, v1.0
QuartzInterrupt, v1.0
QuartzLatency, v1.0
QuartzMirror, v1.0
QuartzPet, v1.0
QuartzPlayer, v1.0
QuartzRange, v1.0
QuartzTarget, v1.0
QuartzTimer, v1.0
QuartzTradeskill, v1.0
sct, v6.01
SeriousBuffTimers, v1.0
Squeenix
Stubby, v52
SWStats, v2.2.b1
SWUniLog, v2.1.4
Swatter, v5.0.PRE.2887
XRS, v2.1 r63691
Also with 2.4 Omen has not been showing up in the Rock menu. Is this intentional?
I recommend using a different sound, no one in my guild likes it at all.
Failing that, I recommend making the audible warning optional, or not existent.
Just go into Modules -> Single target -> Warnings (if iirc)
There you will find that u can adjust the lvl of threat where u want the warning and if u want a warning sound when passing that lvl of threat.
better to lock Omen1 thread
in the function ThreatLib.OnCommReceive:RAID_MOB_THREAT_WIPE this line exists:
"if (cooldownTimes[mob_guid] or 0) > 15 then"
I think however it should look something like:
"if GetTime() - (cooldownTimes[mobName] or 0) > 15 then"
otherwise cooldownTimes[mobName] will not get a value and hence the function will never reset the raid aggro on the mob.
or I'm completely wrong.
It's is located in the new Interface Options Addons Tab but Omen has it's own "Outline" style menu tree that takes up half of the right pane. This leaves a very small column for the actual options.
In my case, the right side of all the profile drop boxes are cut off behind the scroll bar, so I can't actually change any of the profile options.