some requests (as usual :) ):
- and to make less that 5 secs in "fading" ?
- also to hide the frame or to make it opacity 100%, so we can only see messages
Both those options are already available. Explore the menu that pops up when you right click the EavesDrop titlebar.
Not sure if this has been brought up or not, I may have missed as I scrolled through the pages quickly..
I'm noticing that in both SCTD and EavesDrop my totem damage is not being displayed. I have Pet Damage tunred on in both mods. I used the event debugger to be sure the totems were firing off as pet damage and it does look like that's the events in WoW. Anyone else play a Shammy and have this problem, or am I missing something?
Villainelle, I doubt I'll be adding crit colors or custom formatting anytime soon. They just really aren't the in the direction I want to take this. Its not supposed to be a 100% combat log replacement, though I don't use one anymore. Spell icons would have to updated in BabbleSpell, I'm not going to maintain a seperate list =)
uaxli, changing the width is coming.
hubutz, you can see who healed you if you turn on mouse over details. I'm trying to keep it as clean as possible in what is displayed, so feel that showing healer names there isn't as important as say in SCT. I guess I could make it a toggable options easy enough, we'll see.
Decoder01, Totems are not considered pets by wow. The chat message for them may be displayed for that event, but's there's no way for a parser to know that a totem is your pet. Its not considered a pet as far as unit names go. Same thing with summoned creatures from items, trinkets, etc...
You can add it as a custom event in SCT, its just that it would dispaly anyones totem that does damage, not just yours. That's the only reason its not shown by default.
hubutz, you can see who healed you if you turn on mouse over details. I'm trying to keep it as clean as possible in what is displayed, so feel that showing healer names there isn't as important as say in SCT. I guess I could make it a toggable options easy enough, we'll see.
I for one appreciate your resolve to keep it as simple as possible. EavesDrop has already replaced my combatlog as a Hunter, and I adore the aesthetic value of it. I do have one aesthetic suggestion if you'd consider it: Perhaps a toggleable feature that simply displays player / target a la BattleChat at the top of each column respectively?
Its purely a "look" request and not something thats neccessary by any means.
On my EavesDrop, the gradient textures at the top and bottom extend beyond the width of the frame by a handful of pixels on both sides. I'm using the smallest line size... Doesn't seem to be an issue if you're using larger line sizes.
EavesDrop 0.10 (10079 Beta) just displays "Buff" instead of the actual name of the buff. Also brings up an error frame mentioning close to all included libraries and painting the output frame white (screenshot later).
This gets fixed when i use/load the latest agUnitframes tho so i guess it has to do with the included libraries.
About the totem damages, I didn't went through a complete test, but is there any situation where a non-pet attacking message can get fired from PET events? If no, when the messages are fired from CHAT_MSG_XXX_PET_DAMAGE events, I think you can safely assume that it comes from your pet.
ParserLib will not try to determine that the name is a pet, friendly or hostile player, since it might not accurate, but may be an addon can try to make use of the event names to decide something. That's why ParserLib-1-1 is passing the original event name to client event handlers too.
For example by checking event is XX_FRIENDLY_DEATH or XX_HOSTILE_DEATH, you can know it's a friendly death or hostile death. This can be inaccurate though, I think friendly NPC deaths are being fired from HOSTILE_DEATH events.
Just commited another change that adds labels to top of frame. Sets its color alpha to zero to hide the labels.
Rophy, I'll have to test to see. I seem to remember all pet damage (not just yours) coming through on that chat event, but maybe not. Been a long time since I messed with it.
I'm guessing you didn't install it correctly. As you can see in the zip and the TOC, AceLocale-2.1 is there. Unless it has some problem with enGB, not sure what else it could be.
The "Buff" change is on purpose. The icon or the tooltip tell you what the actual buff is.
Which is a shame as I liked knowing what the debuff I got was (assuming the qoute above applies to the debuffs as well, it seems too). The icons for debuffs don't always make sense if I don't know that class well enough (some duplicates with other skills).
Also I noted debuffs that I cast on others weren't being picked up in Eavesdrop? (random examples as a warrior: thunderclap or deepwounds. Would show the damage but not the debuff affect).
Just mouse over it =) Buffs and Debuffs were never meant to be a fundamental part of this, just something added in. Too many buffs and debuffs have huge names to effectively keep the size small. I might add an option to toggle short/long names, but I'm really trying to keep this small in nature.
And no, there is no support for debuffs cast on others, as WoW does not currently say who casts a debuff on someone, it just says "bob is afflicted by debuff".
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Both those options are already available. Explore the menu that pops up when you right click the EavesDrop titlebar.
I'm noticing that in both SCTD and EavesDrop my totem damage is not being displayed. I have Pet Damage tunred on in both mods. I used the event debugger to be sure the totems were firing off as pet damage and it does look like that's the events in WoW. Anyone else play a Shammy and have this problem, or am I missing something?
Thanks!
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumuaxli, changing the width is coming.
hubutz, you can see who healed you if you turn on mouse over details. I'm trying to keep it as clean as possible in what is displayed, so feel that showing healer names there isn't as important as say in SCT. I guess I could make it a toggable options easy enough, we'll see.
Decoder01, Totems are not considered pets by wow. The chat message for them may be displayed for that event, but's there's no way for a parser to know that a totem is your pet. Its not considered a pet as far as unit names go. Same thing with summoned creatures from items, trinkets, etc...
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI for one appreciate your resolve to keep it as simple as possible. EavesDrop has already replaced my combatlog as a Hunter, and I adore the aesthetic value of it. I do have one aesthetic suggestion if you'd consider it: Perhaps a toggleable feature that simply displays player / target a la BattleChat at the top of each column respectively?
Its purely a "look" request and not something thats neccessary by any means.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis gets fixed when i use/load the latest agUnitframes tho so i guess it has to do with the included libraries.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThe included libraries are automatically all the latest. Can't tell what going on without an actual error message.
ParserLib will not try to determine that the name is a pet, friendly or hostile player, since it might not accurate, but may be an addon can try to make use of the event names to decide something. That's why ParserLib-1-1 is passing the original event name to client event handlers too.
For example by checking event is XX_FRIENDLY_DEATH or XX_HOSTILE_DEATH, you can know it's a friendly death or hostile death. This can be inaccurate though, I think friendly NPC deaths are being fired from HOSTILE_DEATH events.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumRophy, I'll have to test to see. I seem to remember all pet damage (not just yours) coming through on that chat event, but maybe not. Been a long time since I messed with it.
And yes, i checked out all the externals as well.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhich is a shame as I liked knowing what the debuff I got was (assuming the qoute above applies to the debuffs as well, it seems too). The icons for debuffs don't always make sense if I don't know that class well enough (some duplicates with other skills).
Also I noted debuffs that I cast on others weren't being picked up in Eavesdrop? (random examples as a warrior: thunderclap or deepwounds. Would show the damage but not the debuff affect).
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAnd no, there is no support for debuffs cast on others, as WoW does not currently say who casts a debuff on someone, it just says "bob is afflicted by debuff".