Ok, after weeks of Omen not working for no apparent reason, and giving no bugs, I decided to see if it was another one of my addons that was messing it up. After extensive enabling and disabling of addons, I discovered that tekMapEnhancer was the culprit. Why this addon causes Omen to cease sending and receiving threat, I have no idea.
I'm having a bit of a problem, although I believe it's caused by Threat-1.0 and not Omen. I have the same versions as the rest of my raid, but nobody else can see my threat and I can't see anybody else's threat. No errors or anything, it's just like it's not communicating with anyone else. I tried wiping my Omen SVs, but that didn't help. Any idea what might be causing it? :S
Great little add-on but it will only work if you're using those layouts for the respective raid types.
Personnally I prefer a complete profile change (I don't display a 40-members raid in the same way I display a 10-members raid).
Note : instead of registering / unregistering the REGEN_ENABLED event you could use the ScheduleLeaveCombatAction(GridLayout, "ReloadLayout") method :)
I think I tried that and it didn't work for some reason. Guess I could try again... is there anything particularly bad about registering and unregistering an event?
I made this tiny little addon a couple weeks ago, it seems to work well. It will basically adjust the Grid layout so you can always see everyone in the raid (it does it by what groups people are in, not how many there are.)
I have a problem with EavesDrop where if I disable the addon, reload my UI, re-enable it and then reload again, it forgets it's position and appears in the center of the screen. Has anyone else experienced this?
Are you taking into account that the "Fire vulnerability" debuff can be resisted but the scorch not?
Actually, I'm 98% sure that this is no longer the case. They changed it so that if the scorch lands, the Fire Vulnerability debuff does as well. It used to be able to resist seperately, but not anymore.
Rabbit, I'd love to use closetgnome but it's so much more strict than itemrack!
for instance, if i'm in my "Tank" outfit and equip a 2h sword (not part of the Tank set) then mount up and ride to where im going...then dismount, my Tank outfit is reapplied and i have to re-equip my 2h sword!
with itemrack, if i make a manual change "on the fly" like that, it is remembered. the only time it goes back to "Tank" is when I tell it to!
To get around this I just made a "Dismount" set that it switches back to when I dismount. It's not perfect, but it's much better than what you described, especially if you only use one trinket for your mount set.
I'd just like to point out to everyone that this addon is < a week old and the author has been spending almost all that time working on the back end, Threat-1.0. Give him at least a little time to work with it before expecting too much :P
2. The spam gotten when you do a Syncing Report is large, I was wondering if you could think of another way to show this data besides printing it to chat.
How else would you report data from a mod to someone who isn't running the mod? You can select where the spam goes and how many lines it shows, which should be good enough.
At first I thought the same thing, but looking at what he said again I believe he meant the report on who Violation is syncing with, like in the bottom of your screenshot. That does look quite spammy, although the only other thing I could think of would be another tablet, like in BigWigs.
Here's my understanding of how Threat-1.0 is working, and keep in mind I don't know much about coding or whatever, so if this is wrong please try and explain it better for me >.>
Threat-1.0 is calculating your own threat (using Parser-3.0 to parse the combat log) and then using AceComm to broadcast your threat and pick up other people's threat. As in, it's the addon doing the conveying.
Then Violation/Omen just display the data Threat-1.0 has collected, from yourself and others. So any KTM compatibility is probably going in Threat-1.0, not Omen. I might be wrong on that though; Antiarc would have to clarify how he plans to have it work.
0
Here's the entire code of tekMapEnhancer:
UIPanelWindows["WorldMapFrame"] = {area = "center", pushable = 9} hooksecurefunc(WorldMapFrame, "Show", function(self) self:SetScale(0.75) self:EnableKeyboard(false) BlackoutWorld:Hide() end) MiniMapBattlefieldFrame.status = "active"Is there something in there that would affect Omen or Threat-1.0 in any way? :/
0
This might be a stupid question, but where exactly is that file? >.>
0
0
0
0
I think I tried that and it didn't work for some reason. Guess I could try again... is there anything particularly bad about registering and unregistering an event?
0
0
0
Any chance you could upload that texture somewhere, or link to somewhere I can find it? :P
0
Looks great. What's the mod in the lower right corner with the clock? I've seen a lot of people using it but I'm not sure what it's called.
0
Actually, I'm 98% sure that this is no longer the case. They changed it so that if the scorch lands, the Fire Vulnerability debuff does as well. It used to be able to resist seperately, but not anymore.
0
To get around this I just made a "Dismount" set that it switches back to when I dismount. It's not perfect, but it's much better than what you described, especially if you only use one trinket for your mount set.
0
0
At first I thought the same thing, but looking at what he said again I believe he meant the report on who Violation is syncing with, like in the bottom of your screenshot. That does look quite spammy, although the only other thing I could think of would be another tablet, like in BigWigs.
0
Threat-1.0 is calculating your own threat (using Parser-3.0 to parse the combat log) and then using AceComm to broadcast your threat and pick up other people's threat. As in, it's the addon doing the conveying.
Then Violation/Omen just display the data Threat-1.0 has collected, from yourself and others. So any KTM compatibility is probably going in Threat-1.0, not Omen. I might be wrong on that though; Antiarc would have to clarify how he plans to have it work.