Authors CurseForge

Quote from Hinalover

So basically your saying is that we will not be able to see what the main tank's threat is unless we throw something at the boss. So for example I'm looking at Gurtogg, MT pulls and I'm still seeing nothing on Omen3. However if I throw up an Ice Lance at Gurtogg, I'll see what the MT's Threat is?

Correct.

Quote from Hinalover

Also I understand the UserID's are client side, but is there a way to get the name of each of the users/pets in the raid? If that is the case, wouldn't that help to match who is NOT on the Threat meter and who is, and send the Threat information to the people who are not on the Threat meter?

The whole design idea of Omen3 is to avoid syncing, and also avoid parsing the combat log to be as minimal as possible.

If you looked at KTM's (wrath version) source code, it doesn't attempt to sync any data either. The framework for data syncing is still there, but its not actually used. Similarly, the framework for parsing the combat log is present, but its not being used either.

ok. Because right now, the main issue is the first 10 or so seconds when the MT pulls. How is the rest of the mod coming along then?

Quote from Hinalover

ok. Because right now, the main issue is the first 10 or so seconds when the MT pulls. How is the rest of the mod coming along then?

Right now, I am hoping that Blizzard lets us get threat values of mobs anyone in the party/raid is in combat with (within visible range), rather than only mobs you are in combat with.

If you have git installed, you may now pull a copy of Omen3 down to your computer from
git://git.wowace.com/wow/omen/wrath.git

Edit: You can now also download alpha packages from:
http://www.wowace.com/projects/omen-threat-meter/repositories/wrath/files/

Note: An existing bug with the packager is including CBH and Libstub in the nolib zips because apparently the packager treats externals that point at tags differently.

You were not kidding in that it was a bare-bones version. I didn't have any problems with it while soloing. The threat came in at a reasonable time frame so that should not be an issue. While soloing Dr. Boom threat was displayed in an easy to read format and gave exact numbers. I need to test this in a group setting so I would have to hold judgment until then but so far a good start.

Added a sizable amount of options to Omen3 today. "/omen config" to see them. Might do some right-click menu stuff, sharedmedia and sink stuff tomorrow.

Quote from Hinalover

... while soloing ...

Did you have a pet tanking? Or were you really really "solo"? :) (Worth checking out either circumstance.)

I'm curious about whether or not Blizzard are giving us pet threat. I doubt many hunters will be pulling from their tank pets, but this is something I've always had to watch carefully as a warlock.

Quote from jokeyrhyme

Did you have a pet tanking? Or were you really really "solo"? :) (Worth checking out either circumstance.)

I'm curious about whether or not Blizzard are giving us pet threat. I doubt many hunters will be pulling from their tank pets, but this is something I've always had to watch carefully as a warlock.

I was just doing it without any pets (though I could respec Frost and pull out my Water elemental and try it out with that)

edit:

Ok I just respeced and tested with my water elemental on Dr. Boom on the Beta (Boom was at 150k health when I did this so I killed him while doing this test). I initially pulled out my WE on Dr. Boom first and allowed him to attack Boom while I dealt with a bug pat that showed up. After killing the pat, I went on and; as expected; saw that my WE was not showing up on Omen since I hadn't tagged Boom yet. Once I did start attack, Omen DID show my WE's threat as well as mine. I eventually did surpase my WE's threat and shortly after that my WE went away. After a little bit I pulled out my WE again and had it continue attacking. Omen was able to pick up my WE after he started attacking so it does go both ways.

i was asking myself if omenn could now do what we had to do by hand earlier: find out all aggroresets and reducing effects of abilities and bosss in a threat-profilingfunction? ;)
or is this sth a standalone addon should do?

It isn't necessary to calculate threat at all, because Blizzard always gives the correct values. So even if a tank's threat gets halved, Blizzard's values will tell us, we don't have to calculate it.

The only reason to calculate threat is to do faster updates than Blizzard's 1-2 seconds interval based on combat log parsing, and this isn't really necessary at all.

Problem fixed by kaelten, the omen3 alpha zips is now at

http://www.wowace.com/projects/omen-threat-meter/repositories/wrath/files/

Check above post for a temporary zip straight from my addons folder.

woooooot :P

Xin, I have to give you props. I used Omen3 last night while attempted the "LEEEEEEEROY!!!!" Achievement, and the thing worked like a charm. The only request I have is if you can implement the AOE feature into Omen3. I rarely use that feature, but when I do use it, it's a godsend (IE Hyjal trash, Dragons in UBRS for the Jenkins title :p [which I did get last night :p])

I'm afraid the AOE feature is not possible to implement without scanning the combat log and doing manual threat calculations for every mob (and then syncing...). Remember you cannot obtain threat on a mob if someone isn't targetting it in your raid? If there are 50 whelps and only 6 of them are targetted by your raid, then the other 44's threat cannot be queried in any manner.

ah ok. I didn't realize people have to target the mobs in order to gather the info. My bad. Still i generally keep Omen2 set to Single target anyway, so it was not a big deal.