Quote from: Plague on May 30, 2008, 11:05:09 am
Is there a way to put the dmg for totems together? Like you can do it for Dots
Not yet. That's a bug.
Are you working on that bug? Hate to see all that messages with my Magma Totem
You should try loading Parrot without any other addons. Currently at least LibStub and AceLibrary are missing because some of the other libraries included depend on them. There may me more libraries missing.
Right. LSM-3.0 depends on LibStub, Deformat-2.0 depends on AceLibrary, will be fixed soon
Noticing a bug in the current version where wand damage isn't being coloured according to its damage type (currently have an Arcane damage wand but Parrot colours it as physical). Anyone else seeing this?
Quote from Marroc »
Wand damage is being colored as physical damage, rather than elemental damage.
I decided to implement a plugin for Parrot that adds totem damage to the outgoing area, as I've really missed that feature, and it seems you're plenty tied up with this thing already. The result is the addon "ParrotOnFire", which is now in trunk.
It uses the LibTotemTracker-1.0 library (in branches) that I made for the purpose (and another purpose). Feel free to port any of the code into Parrot as you please, but keep in mind that the library is in branches because the API has not been settled completely yet. I recommend extracting the stuff you need from LibTotemTracker-1.0 directly, as you only need the damage events, not tracking of individual totems.
I actually have implemented guardian-damage (including totems) in a branch (a quite buggy branch I know, didn't test it much).
The Problem is, that imho totem-damage needs to be seperated from pet and player damage. As everybody can notice, there are a lot of "Pet ..." events in the events-options. There would be the same number of "guardian ..." options.
The options became too many, and were too confusing (imho) so I wanted to seperate them into different options-tables, but that's more work than I expected, so I decided to focus on other issues for the time being.
Quote from xbeeps »
In the meanwhile, for users, getting totem support in Parrot is just a matter of installing ParrotOnFire alongside Parrot.
That's a great idea. That way, only the people that want the totemdamage displayed can have it displayed.
Thanks but it worked some days ago. So I don't think that it is a Blizzard combat-log bug. Or did they change it in 2.4.2? If yes could you please add an mounted/dismounted condition (as "on mount" and "on dismount"; not as "mount active")? (should be possible technically because ClosetGnome/ItemRack etc. handle mounting/dismounting)
While adapting Parrot for 2.4.2 LibSpecialEvents-Aura was removed. It reported Mounting as buff-gains by periodically checking the buff-list. I can do it this way again.
Quote from Marroc »
Buff refreshes are not being counted as 'gains' This means if you have a trigger for mongoose and the buff refreshes itself before it wears off you will not get a new message.
actually that's intended, because I got a report that this option creates too much spam. I'll try to make it configurable.
Or I could just make the trigger fire, without showing a notification for now
buff-triggers in general work, BUT the Blizzard-combat-log doesn't report mounting as buff-gain.
Try changing the Trigger, to "Check for XX seconds" and secondary "Buff active" <Mountname> + "Buff inactive" "Crusader Aura"
Quote from Whynona »
To fix the issue for myself, I've changed a bit the code saw here:
In LibParser-4.0.lua around line 1220:
local GOLD_MATCH = "(%d+) " .. string.gsub(GOLD_AMOUNT, "%%d ", "")
local SILVER_MATCH = "(%d+) " .. string.gsub(SILVER_AMOUNT, "%%d ", "")
local COPPER_MATCH = "(%d+) " .. string.gsub(COPPER_AMOUNT, "%%d ", "")
and in Loot.lua around line 79:
local GOLD_ABBR = utf8trunc(string.gsub(GOLD_AMOUNT, "%%d ", ""), 1)
local SILVER_ABBR = utf8trunc(string.gsub(SILVER_AMOUNT, "%%d ", ""), 1)
local COPPER_ABBR = utf8trunc(string.gsub(COPPER_AMOUNT, "%%d ", ""), 1)
With this small fix you'll be able to use your old parrot version, until the new version is completely released.
DO NOT do this!
the LibParser-4.0 has been removed because it's deprecated.
The version on http://files.wowace.com/Parrot is working (except that small mistake yesterday).
All the Events that were previously reported by LibParser are now captured by Parrot itself.
If some event is missing, just post it here and I'll try to implement it.