Healer Mode grow up does not work right. It's jumpy, sometimes it grows up but brings the bottom bar with it while trying to print bars where it things the bar area is, etc.
I am *extremely* frustrated by the fact that Omen2 is not letting me select my desired bar texture because I have enough bar textures registered in SharedMedia that the list is higher than my screen, and there's no way to scroll the list or show it in multiple columns :(
Also, the profile system seems to be nonfunctional, as it's not adjusting to look like it does on any of my other toons when I switch profiles.
if not mousescroll, maybe slidebar can be implemented?
I loaded in today and my Omen is not showing up on my screen neither is /omen working. I logged out and checked to make sure that everything is enabled, and it is, so its nothing on my side. I even tried disabling everything and leaving only omen on and it didn't work. Please help.
-Sami
I would like to propose a "small" new feature here.
Something like "Warn me if my next three Attacks will definitely draw Aggro if I don't stop doing damge right now"
Some will say, "well thats implemented, adjust the alertlevel", hm no, that is not what I want, the problem is. I set this to "warn me at 90%", and the Bossfight starts, I as a warlock cast a spell, it hits critical, and i see the Warning "over 90% aggro". so i stop dealing damage, soon as I am below 90% I cast again and crit again, resulting in drawing Aggro.
If I could be warned, that I will (if i crit) draw aggro, this would be much more efficient for me, because later in the Bossfight i can and will go up to 120% Aggro to maximize DPS. And beeing in the 120% Area I still have enough Aggro between myself and "130%" to cast right away.
This is the reason why I would like something like, the next three casts - assumed the hit critical, we'll end up with 30k Aggro, so to test it i wanted to set it to .. "warn me if I have only 20k Aggro left bevore i will draw aggro" , I had a glimpse in the code and did this:
[SingleTarget.lua:814]
if selfThreat+30000 > aggroThreat and not self.warned and aggroGUID and playerGUID ~= aggroGUID and aggroThreat > 5 then
-- if pct > WarningThreshold and not self.warned and aggroGUID and playerGUID ~= aggroGUID and aggroThreat > 5 then
Maybe this is a nice Idea for the masses ?
Comments ?
and yes I know I am just looking from a warlock p?erspective here (first) :-)
You're basically asking for a "wait for sunders" warning built-in...
How much more dumbing down is needed?
It's obvious that 40% (90%->130% assuming ranged class) of 5k tank threat at the very first seconds of the fight is roughly 2k,
a crit will pull aggro.. 90% warning means nothing at very start of fight.
Further in when the tank's threat is 50k.. 40% of that is 20k a much safer margin.
Do you really need the addon to tell people not to be complete morons and
wait a few seconds for initial threat build up?
You're basically asking for a "wait for sunders" warning built-in...
How much more dumbing down is needed?
you fail ... no I don't need an "wait for" addon, read my post again.
I want Omen to notify me when I only have "20k Aggro" bevore I will draw Aggro. This is needed when you doing Damage in the 120-130% Aggro Area in the Fight, not at the start when you can obviously wait befor doing damage.
So basically
- "notify me when I will draw Aggro in 5 sec if I keep doing Damage at my current APS"
can be easier implemented, by doing:
- "notify me when i Have only 20k Aggro left to draw Aggro"
Do you really need the addon to tell people not to be complete morons and
wait a few seconds for initial threat build up?
It wasn't directed at "you" I assumed you were requesting it for others due to that "nice idea for the masses" reference.
However after this
Quote from DownLord »
you fail ....
I should re-phrase and say that you don't have to be a moron.. you can wait at the start of fight
or take your eyes off the tps column and look at total aggro.
Edit: I think I'll quote the relevant parts for posterity (emphasis added by me)
Quote from DownLord »
<snip>I set this to "warn me at 90%", and the Bossfight starts, I as a warlock cast a spell, it hits critical, and i see the Warning "over 90% aggro". so i stop dealing damage, soon as I am below 90% I cast again and crit again, resulting in drawing Aggro.
Quote from DownLord »
<snip>...because later in the Bossfight i can and will go up to 120% Aggro to maximize DPS. And beeing in the 120% Area I still have enough Aggro between myself and "130%" to cast right away.
Now tell me again that what you describe is not the regular 2-button brainless dps pulling aggro at start of fights... and I fail.
People who can't do instant math off the top of their heads while also concentrating on many other things, are not morons. Everyone is wired different. Some have the math gift, some don't. Computers are good at this, so tools like Omen (developed in peoples free time!) are great, and I for one appreciate what it dose very much.
If there is some mathematical way to make the warning smarter rather than just an overall %, I wouldn't complain about it. :) Seems like a rather chaotic system though to be predicting such things as stealing aggro in 2 or 3 swings... I'm not one of the math gurus, so I can't say.
If there is some mathematical way to make the warning smarter rather than just an overall %, I wouldn't complain about it. :)
See this is exactly my Idea, why is something implemented that is "only useable" but "rough" and not "that final solution" .. my proposal here aims towards a better Warning Method, which works fine tbh, I can now safely deal Damage up to the critical Range of 130%-20k .. exellent. I would only wich to see this get implemented in the code, so I don't have to change each updated version by myself *gg*
Still having problems with Omen 2. I don't notice it, but my fellow raiders find me dropping off their Omen, even when I'm MTing the target and no-one is higher than me on the threat.
I'm a Feral Druid, so it's usually not a problem, but in aggro sensitive fights it can be when people don't know my aggro when I'm offtanking.
Any ideas why I would be dropping off Omen? Being a feral it's obviously not because of any aggro dumps.
While Downlord isn't being exactly polite, I can see the point he's trying to make.
In an extended normal-threat encounter (no weird threat resets), it's not terribly useful to know you're at 98% threat (or 108 or 128 if you like to ride the edge), because you'll still be a good distance off from pulling aggro. However, closer to the beginning of the fight, you'll want to stay under the safe value of 90%, just in case you get a lucky (or unlucky) string of crits.
It seems like having an option for an absolute value of threat indication would be helpful, so you can set it to 5k or 10k or 20k damage warning (some number greater than what you can generate between omen checks). This would have the advantage of automatically warning you to go slow towards the beginning or if the tank gets hit with a threat dump early, but it would allow a much closer 'riding-the-line' for crazy dps encounters like Brutallus.
One potential drawback I see with warnings based on absolute threat value is that these numbers are not all exact. They are pretty close to exact in most cases, but the small differences between "pretty close" and "exact" build up over large fights. When this happens more for some classes' abilities and less for others', percentages will also be affected.
Still having problems with Omen 2. I don't notice it, but my fellow raiders find me dropping off their Omen, even when I'm MTing the target and no-one is higher than me on the threat.
I'm a Feral Druid, so it's usually not a problem, but in aggro sensitive fights it can be when people don't know my aggro when I'm offtanking.
Any ideas why I would be dropping off Omen? Being a feral it's obviously not because of any aggro dumps.
Can you explain what "dropping off Omen" means? Does it mean your threat goes below other people but you remain holding aggro? Or you don't show up at all on their Omen, but everyone else does?
I fixed a bug some 2 weeks ago that was hiding people from being shown in Omen. Make sure they have the latest Omen version from http://files.wowace.com and NOT from curse gaming or wowinterface or some other website. Those websites have very very outdated versions.
Can you explain what "dropping off Omen" means? Does it mean your threat goes below other people but you remain holding aggro? Or you don't show up at all on their Omen, but everyone else does?
I fixed a bug some 2 weeks ago that was hiding people from being shown in Omen. Make sure they have the latest Omen version from http://files.wowace.com and NOT from curse gaming or wowinterface or some other website. Those websites have very very outdated versions.
When I say dropping off of omen, I mean my bar disappears on the other people's Omen. It seems to happen randomly, but often enough for people to be getting pissed off with me. I'm not losing aggro at all.
I'm currently using Wowace updater to keep them up to date - latest version I picked up the other night was 74199.
Is there any other Addons that could cause conflicts?
We were playing around in Naxxramas the other night. On Loatheb Omen was reporting incorrect threat amounts for the entire raid.
I believe the problem lies in ThreatClassModuleCore.lua. "Fungal Bloom" is in the BuffModifiers table when it should be in the DebuffModifiers table as it is a debuff upon the player, not a buff.
old raidinstances before bc are not supported yet ;)
onyxia and kelthuzad are in the works by dead_masters and myself.
so if you have information regarding threat on old bosses that dont work.
Tell me ;) and i see what i can do for you
btw.
Fungal Bloom - Critical-hit chance increased by 50%. Spell critical-hit chance increased by 60%.
this spell can be considered buff,and you cause no aggro, why is this a de.buff? it doesnt harm, it helps you :)
Do you have a combatlog for that fight and instance maybe? or a transcriptorlog? so we can get some information like the spellid from it ? :)
If you look in ThreatClassModuleCore.lua in Threat-2.0 lib you will see fungal bloom is already there(line 218), however it is in the wrong spot.
The spell is a debuff upon the player, yes it increases the player's crit chances and makes them generate no threat and as such may be considered a buff, but it is a debuff applied upon the player that can not be removed. As to why it is a debuff, my guess is that Blizzard did that on purpose in order to control the fight. Since it is not removable, a raid will most likely be wiped if the main tank receives this debuff. The debuff is obtained by killing a spawned spore during the fight, and it applies this debuff to the 5 nearest people. Controlling who receives this debuff is one major part of the fight.
Since the spell is a player debuff it should be in the DebuffModifiers table(starting line 258) not the BuffModifiers(starting line 196) table.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumA screenshot showing the problem will be useful.
if not mousescroll, maybe slidebar can be implemented?
-Sami
Something like "Warn me if my next three Attacks will definitely draw Aggro if I don't stop doing damge right now"
Some will say, "well thats implemented, adjust the alertlevel", hm no, that is not what I want, the problem is. I set this to "warn me at 90%", and the Bossfight starts, I as a warlock cast a spell, it hits critical, and i see the Warning "over 90% aggro". so i stop dealing damage, soon as I am below 90% I cast again and crit again, resulting in drawing Aggro.
If I could be warned, that I will (if i crit) draw aggro, this would be much more efficient for me, because later in the Bossfight i can and will go up to 120% Aggro to maximize DPS. And beeing in the 120% Area I still have enough Aggro between myself and "130%" to cast right away.
This is the reason why I would like something like, the next three casts - assumed the hit critical, we'll end up with 30k Aggro, so to test it i wanted to set it to .. "warn me if I have only 20k Aggro left bevore i will draw aggro" , I had a glimpse in the code and did this:
[SingleTarget.lua:814]
if selfThreat+30000 > aggroThreat and not self.warned and aggroGUID and playerGUID ~= aggroGUID and aggroThreat > 5 then
-- if pct > WarningThreshold and not self.warned and aggroGUID and playerGUID ~= aggroGUID and aggroThreat > 5 then
Maybe this is a nice Idea for the masses ?
Comments ?
and yes I know I am just looking from a warlock p?erspective here (first) :-)
How much more dumbing down is needed?
It's obvious that 40% (90%->130% assuming ranged class) of 5k tank threat at the very first seconds of the fight is roughly 2k,
a crit will pull aggro.. 90% warning means nothing at very start of fight.
Further in when the tank's threat is 50k.. 40% of that is 20k a much safer margin.
Do you really need the addon to tell people not to be complete morons and
wait a few seconds for initial threat build up?
you fail ... no I don't need an "wait for" addon, read my post again.
I want Omen to notify me when I only have "20k Aggro" bevore I will draw Aggro. This is needed when you doing Damage in the 120-130% Aggro Area in the Fight, not at the start when you can obviously wait befor doing damage.
So basically
- "notify me when I will draw Aggro in 5 sec if I keep doing Damage at my current APS"
can be easier implemented, by doing:
- "notify me when i Have only 20k Aggro left to draw Aggro"
and is superior to the current implementation:
- "notify me when i reach 90% of Tank's aggro"
It wasn't directed at "you" I assumed you were requesting it for others due to that "nice idea for the masses" reference.
However after this
I should re-phrase and say that you don't have to be a moron.. you can wait at the start of fight
or take your eyes off the tps column and look at total aggro.
Edit: I think I'll quote the relevant parts for posterity (emphasis added by me)
Now tell me again that what you describe is not the regular 2-button brainless dps pulling aggro at start of fights... and I fail.
If there is some mathematical way to make the warning smarter rather than just an overall %, I wouldn't complain about it. :) Seems like a rather chaotic system though to be predicting such things as stealing aggro in 2 or 3 swings... I'm not one of the math gurus, so I can't say.
Thanks for Omen!
See this is exactly my Idea, why is something implemented that is "only useable" but "rough" and not "that final solution" .. my proposal here aims towards a better Warning Method, which works fine tbh, I can now safely deal Damage up to the critical Range of 130%-20k .. exellent. I would only wich to see this get implemented in the code, so I don't have to change each updated version by myself *gg*
qft ^^
I'm a Feral Druid, so it's usually not a problem, but in aggro sensitive fights it can be when people don't know my aggro when I'm offtanking.
Any ideas why I would be dropping off Omen? Being a feral it's obviously not because of any aggro dumps.
In an extended normal-threat encounter (no weird threat resets), it's not terribly useful to know you're at 98% threat (or 108 or 128 if you like to ride the edge), because you'll still be a good distance off from pulling aggro. However, closer to the beginning of the fight, you'll want to stay under the safe value of 90%, just in case you get a lucky (or unlucky) string of crits.
It seems like having an option for an absolute value of threat indication would be helpful, so you can set it to 5k or 10k or 20k damage warning (some number greater than what you can generate between omen checks). This would have the advantage of automatically warning you to go slow towards the beginning or if the tank gets hit with a threat dump early, but it would allow a much closer 'riding-the-line' for crazy dps encounters like Brutallus.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumCan you explain what "dropping off Omen" means? Does it mean your threat goes below other people but you remain holding aggro? Or you don't show up at all on their Omen, but everyone else does?
I fixed a bug some 2 weeks ago that was hiding people from being shown in Omen. Make sure they have the latest Omen version from http://files.wowace.com and NOT from curse gaming or wowinterface or some other website. Those websites have very very outdated versions.
My first question would be what's the name of the character that drops off (as in disappears?) from the threat list.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhen I say dropping off of omen, I mean my bar disappears on the other people's Omen. It seems to happen randomly, but often enough for people to be getting pissed off with me. I'm not losing aggro at all.
I'm currently using Wowace updater to keep them up to date - latest version I picked up the other night was 74199.
Is there any other Addons that could cause conflicts?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWe were playing around in Naxxramas the other night. On Loatheb Omen was reporting incorrect threat amounts for the entire raid.
I believe the problem lies in ThreatClassModuleCore.lua. "Fungal Bloom" is in the BuffModifiers table when it should be in the DebuffModifiers table as it is a debuff upon the player, not a buff.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumonyxia and kelthuzad are in the works by dead_masters and myself.
so if you have information regarding threat on old bosses that dont work.
Tell me ;) and i see what i can do for you
btw.
this spell can be considered buff,and you cause no aggro, why is this a de.buff? it doesnt harm, it helps you :)
Do you have a combatlog for that fight and instance maybe? or a transcriptorlog? so we can get some information like the spellid from it ? :)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe spell is a debuff upon the player, yes it increases the player's crit chances and makes them generate no threat and as such may be considered a buff, but it is a debuff applied upon the player that can not be removed. As to why it is a debuff, my guess is that Blizzard did that on purpose in order to control the fight. Since it is not removable, a raid will most likely be wiped if the main tank receives this debuff. The debuff is obtained by killing a spawned spore during the fight, and it applies this debuff to the 5 nearest people. Controlling who receives this debuff is one major part of the fight.
Since the spell is a player debuff it should be in the DebuffModifiers table(starting line 258) not the BuffModifiers(starting line 196) table.