Omen - Ace Threat Meter - Page 75

denniz · 10/03/07, 12:29 PM

Originally Posted by Antiarc

KTM transmits only pet or player data, whichever is highest. It does not transmit both. In that case, KTM is "working as intended". Whether or not that's what you want is up to you. Even if you were running KTM, you would see the same thing that you are seeing in Omen.

If you want to see separate player and pet threat, then your groupmates will have to run Omen. KTM isn't capable of sending that information.

Thx for clearing that up to me! Then atleast I know it's not some kind of bug, although I do find it weird that KTM implemented it that way, ow welll we got Omen now, awsome addon

srobin001 · 10/03/07, 1:46 PM

Omen sounds fantastic and I've had an interest in using it for some time now. However, I have a couple of extremely noobish questions as I am a rather non technical person.

1. Is Omen and Threat pretty much plug and play at this point. Can I just install it and run it as I do KTM? I don't even know what an external is, nor do I know alot about adjusting addons once they've been installed.

2. My entire guild and raid group uses KTM. Will Omen be effective for me judging threat for myself and others if I'm the only one using it? Is there any dependency on CT RAID or other raid mods that will effect it?

3. Are they any known conflicts with other mods, such as X-perl, Deadly Boss Mods, Bartender3, Titan Panel, etc.

Thanks in advance for any help.

• Latito · 10/03/07, 1:59 PM

1. Yep, standard Ace2 mod - download latest version, install as per normal, enjoy. I wouldn't recommend running KTM and Omen at the same time (same person using both simultaneously).

2. Yes. Ideally everyone should have Omen in your raid as it will be a more accurate tracking of threat, however you can have the 2 mods co-existing in the raid. There are 2 settings to play with. One for showing KTM data - that is, you will see the threat of people using KTM. Another for exporting your threat to KTM so that other people see you. Both work reasonably well.

3. No problems I've heard of, except sometimes KTM.

Just a note.. Omen is updated a LOT. You don't need to update it that often, we generally have a range of several thousand revisions within the raid. As the addon improves and becomes more accurate however, you should keep your copy updated to utilize these improvements.

srobin001 · 10/03/07, 2:08 PM

Thank you very much for the detailed reply.

Rinced · 10/03/07, 2:47 PM

[2007/10/03 19:44:37-533-x9]: ...s\Threat-1.0\Threat-1.0\ThreatMobNameTranslation.lua:149: Conflicting translation for Vashj'ir Honor Guard in deDE: old is "Zertrümmerer des Echsenkessels", new is "Ehrenwache der Vashj'ir". Please report to Antiarc.:

Apate · 10/03/07, 3:50 PM

Originally Posted by srobin001

Thank you very much for the detailed reply.

Note that if you don't set master targets in KTM, you should.

Antiarc · 10/03/07, 8:39 PM

Originally Posted by Rinced

[2007/10/03 19:44:37-533-x9]: ...s\Threat-1.0\Threat-1.0\ThreatMobNameTranslation.lua:149: Conflicting translation for Vashj'ir Honor Guard in deDE: old is "Zertrümmerer des Echsenkessels", new is "Ehrenwache der Vashj'ir". Please report to Antiarc.:

Thanks. This bug seems to be rearing its head more and more often lately. I'll see if I can knock it out.

sp00n · 10/04/07, 5:09 AM

Originally Posted by Antiarc

Thanks. This bug seems to be rearing its head more and more often lately. I'll see if I can knock it out.

Bah, that's because the German localization team is changing names around like crazy.
One reason more to use the enGB language pack.

Mikari · 10/06/07, 2:53 PM

Had a pretty bad bug today, Omen for some reason stopped receiving data from KTM. I'm using the latest version of Omen from Wowace. The problem occurred about half way through a Karazhan raid, Omen was receiving data fine up till that point.

Ziraj · 10/06/07, 3:47 PM

Originally Posted by Mikari

Had a pretty bad bug today, Omen for some reason stopped receiving data from KTM. I'm using the latest version of Omen from Wowace. The problem occurred about half way through a Karazhan raid, Omen was receiving data fine up till that point.

Same thing happened to us last night. Omen wasn't receiving any KTM data. Was pretty rough for the dps, as the MT on that particular night was using KTM...

Bullshot · 10/06/07, 3:52 PM

Originally Posted by Mikari

Had a pretty bad bug today, Omen for some reason stopped receiving data from KTM. I'm using the latest version of Omen from Wowace. The problem occurred about half way through a Karazhan raid, Omen was receiving data fine up till that point.

Was a Master Target set through KTM and not reset? I have noticed this happening if a master target is set on a mob and not cleared; Omen stops receiving threat data from KTM for every subsequent mob since KTM is technically logging threat for a mob with a different name than what Omen is tracking.

Mikari · 10/06/07, 4:36 PM

Originally Posted by Bullshot

Was a Master Target set through KTM and not reset? I have noticed this happening if a master target is set on a mob and not cleared; Omen stops receiving threat data from KTM for every subsequent mob since KTM is technically logging threat for a mob with a different name than what Omen is tracking.

Yeah it started happening after a KTM master target was set. KTM auto clears the master target though usualy, I guess Omen isn't picking that up.

Bullshot · 10/07/07, 7:46 AM

Originally Posted by Mikari

Yeah it started happening after a KTM master target was set. KTM auto clears the master target though usualy, I guess Omen isn't picking that up.

It does? The last time I used KTM, I had to not target anything and type /ktm mastertarget or click the "Hunter's Mark" icon on the KTM window in order to reset the Master Target.

Mikari · 10/07/07, 8:00 AM

Originally Posted by Bullshot

It does? The last time I used KTM, I had to not target anything and type /ktm mastertarget or click the "Hunter's Mark" icon on the KTM window in order to reset the Master Target.

It wasn't a manually set master target. Newer versions of KTM have boss mods that will automatically set the master target to the boss, after the boss is killed the master target is automatically cleared. Omen doesn't seem to be picking up the fact it's cleared though.

Drunkmunky · 10/08/07, 9:00 PM

I have also noticed a few weird things with Omen/KTM, I've stopped raiding so this is only in 5mans. Sometimes I don't get info from people running KTM, sometimes I don't even get info from people running Omen, sometimes I get it from a mix, sometimes people tell me I'm not appearing in their Omen/KTM window, there is no exact point it doesn't work. I've even seen people using Omen being marked as KTM in the omen window, also when I have a mix of Omen & KTM the data is wildly different, this probably isn't a problem with Omen itself I don't know =\ (I'm referring to single targets with no main target set and no other mobs at all).

Another thing I noticed is that the aggro marker isn't accurate with my pet, is this the nature of hunters and their pets that the % required to draw aggro is different? I see many times that I'm nearly 1k under Omen's "aggro" marker and I still draw aggro. Being that it is only myself and my pet I assumed Omen's data would be 100% accurate.

I'm using the latest version of Omen/Threat I'm not using KTM alongside it, reporting to KTM and using KTM data is both ticked. I'm not really fussed about getting these "fixed" I just thought I would mention it. If you need screenshots I'll endevour to get them in the next few days.

RK · 10/09/07, 9:49 AM

Looking towards 2.3 and in particular the increased rate of Lightning Overload (and the fact that the procs are going to be threatless).

If they put in some sort of combat log note that LO has proc'd, no problems. If it remains as it currently is, however, this is going to be a problem.

Is it possible to put a toggle into Omen to let people ignore lightning bolt hits that do less than X damage, and lightning bolt crits that do less than 2X damage? While this will lead to some very slight underreporting due to 50% and 75% partial resists, it's better than nothing. People will need to account for trinketed bolts and stuff, of course. And the lightning capacitor could well screw it up (Omen would need to track the capacitor charges fading to differentiate? But travel time on bolts makes that a doozy).

Just trying to think ahead. Maybe a better way to deal with this would be to slip a note to Slouken asking him to get some sort of combat log marker put into the combat log for lightning overload to save the sanity of mod writers

Kirion · 10/09/07, 10:05 AM

Originally Posted by RK

Looking towards 2.3 and in particular the increased rate of Lightning Overload (and the fact that the procs are going to be threatless).

If they put in some sort of combat log note that LO has proc'd, no problems. If it remains as it currently is, however, this is going to be a problem.

Is it possible to put a toggle into Omen to let people ignore lightning bolt hits that do less than X damage, and lightning bolt crits that do less than 2X damage? While this will lead to some very slight underreporting due to 50% and 75% partial resists, it's better than nothing. People will need to account for trinketed bolts and stuff, of course. And the lightning capacitor could well screw it up (Omen would need to track the capacitor charges fading to differentiate? But travel time on bolts makes that a doozy).

Just trying to think ahead. Maybe a better way to deal with this would be to slip a note to Slouken asking him to get some sort of combat log marker put into the combat log for lightning overload to save the sanity of mod writers

I think i saw in change logs that Antiarc already added LO checks

Antiarc · 10/09/07, 1:35 PM

2.3 LO handling is already in, actually. I'm doing it by watching the time of casts, and if you cast LB or CL less than a certain amount of time after the previous cast, it's counted as an LO proc.

Unaz · 10/09/07, 4:24 PM

Originally Posted by Antiarc

2.3 LO handling is already in, actually. I'm doing it by watching the time of casts, and if you cast LB or CL less than a certain amount of time after the previous cast, it's counted as an LO proc.

Don't forget to check for Nature's Swiftness in between!

Antiarc · 10/10/07, 3:13 AM

Oh, damn, right. Thanks - I'll add that in. Good catch.

RK · 10/10/07, 3:25 AM

Is it taking Lightning Capacitor into account as well? Every elemental shaman who can get it will be using it, and the proc is just "lightning bolt" because Blizzard are lazy buggers sometime (probably the same reason they didn't put anything in the combatlog to help LO being tracked). A time-based approach might count a regular lightning bolt as an LO proc because it came too soon after a capacitor lightning bolt hit.

Jayde · 10/10/07, 9:03 AM

As far as I've been in the KTM code, auto-clears for bosses aren't done by setting a blank master target via me.mtevent, but instead relay a me.bossdeathevent which is then handled in a different function.

The me.bossdeath function in the KTM_MasterTarget.lua module handles the clearing of the local mastertarget after recieving this event.

There are also, as Mikari mentioned, a bit different handler for the automastertarget events also that is a little different than the normal mastertarget handler.

--[[
---------------------------------------------------------------------------------------------
					Relay Event Triggers
---------------------------------------------------------------------------------------------
]]

--[[
This is called when the RelayEvent <me.mtevent> activates, i.e. when a local or remote boss mod sets the master target.
<target> is the localised name of the mob.
]]
me.automastertarget = function(target)

	-- ignore if this is a dupe
	if me.mastertarget == target then
		return
	end

	me.mastertarget = target
	mod.raidtable.updateview()
	
	me.isworldboss = true
	me.lastmttime = GetTime()
	me.lastpollmessage = ""
	
	-- explain to user
	mod.printf(mod.string.get("print", "boss", "automt"), target)
	
end

--[[
This is called when the RelayEvent <me.bossdeathevent> activates, i.e. when a local or remote client reports the death of the master target.
]]
me.bossdeath = function()
	
	me.mastertarget = nil
	mod.raidtable.updateview()
	
	me.isworldboss = false
	me.lastmttime = GetTime()
	me.lastpollmessage = ""
	
end

Irise · 10/10/07, 11:46 AM

Does Omen receive Data from Recount and vice versa?

Apate · 10/10/07, 12:40 PM

Originally Posted by Irise

Does Omen receive Data from Recount and vice versa?

They share libraries.

RK - capacitor and Antiarc's approach to it has been mentioned a few times in this thread already

Beska · 10/11/07, 7:52 AM

I've updated to the most recent version (r51502) from WoWAce and the readme confirms this but the in-game /omen about screen is still showing the addon as version r50185. This is annoying because I have the "new version avaliable!" notice always showing.

What's the problem?