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.
In the notification area, when loosing rep with a group (syndicate in hillsbrad is good for testing this), there is a repeated negation symbol. That is, it reads out "--100 rep, (syndicate)".
Upon poking at it, I found the error... on line 2800 of data\combatevents.lua, the line is currently
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"
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)
Multiple buffs with the same name are only seen once. By this I mean if you have a trigger for say mongoose, and duel wield mongoose, the trigger will only fire on the first buff gain, and will not fire again until the buff fades. This means if you get two procs (one mainhand one offhand) you only get one message.
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.
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
Interface\AddOns\Parrot\Code\CombatEvents.lua:2536: attempt to concatenate global 'itemName' (a nil value)
im getting this error when creating items using first aid and conjour water, anyone know why that might be? i thought it was ebb but now i am using sbf and still getting the error (even with sbf disabled).
I want to report that some triggers seem to have stopped working. At least the "riposte" trigger of my rogue which should trigger on every incoming parry. (I dont check for available skill since this always seemed to work unreliably)
I'm not sure if it stopped working with the release of 2.4.2 or maybe with the larger localization done in the last time. I'm playing on a german client.
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.
Yes do it please :)
And in same way could you please add something for buff-fading-soon (duration <5 sec)?
So, I found a way to catch Guardian (totem) combatlog events. I'll take me a few more days to completely implement the events.
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. In the meanwhile, for users, getting totem support in Parrot is just a matter of installing ParrotOnFire alongside Parrot.
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.
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.
You may want to take into consideration that under normal circumstances Shamans do not have pets. The exceptions are a few quests (can only think of one where the pet actually does damage). So basically, treating totem damage like pet damage is not going to be a problem for any sane people - I'd consider it extreme overkill to add a separate configuration category for them.
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?
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 »
Bug:
Wand damage is being colored as physical damage, rather than elemental damage.
It's on my TODO-list
edit:
totem-damage is in r74959
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I've following triggers:
Selfbuff gain <Mountname>
+ 1st condition No Selfbuff: Crusader Aura
Show: Switch on CRUSADER AURA!
and
Selfbuff fade <Mountname>
+ 1st condition Selfbuff: Crusader Aura
Show: Switch off CRUSADER AURA!
But they stopped working
In LibParser-4.0.lua around line 1220 find
local GOLD_MATCH = "(%d+) " .. _G.GOLD
local SILVER_MATCH = "(%d+) " .. _G.SILVER
local COPPER_MATCH = "(%d+) " .. _G.COPPER
Replace with:
local GOLD_MATCH = "(%d+) " .. string.gsub(_G.GOLD_AMOUNT, "%%d ", "")
local SILVER_MATCH = "(%d+) " .. string.gsub(_G.SILVER_AMOUNT, "%%d ", "")
local COPPER_MATCH = "(%d+) " .. string.gsub(_G.COPPER_AMOUNT, "%%d ", "")
and in Loot.lua around line 79 find:
local GOLD_ABBR = utf8trunc(_G.GOLD, 1)
local SILVER_ABBR = utf8trunc(_G.SILVER, 1)
local COPPER_ABBR = utf8trunc(_G.COPPER, 1)
Replace with:
local GOLD_ABBR = utf8trunc(string.gsub(_G.GOLD_AMOUNT, "%%d ", ""), 1)
local SILVER_ABBR = utf8trunc(string.gsub(_G.SILVER_AMOUNT, "%%d ", ""), 1)
local COPPER_ABBR = utf8trunc(string.gsub(_G.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.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumbuff-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"
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.
In the notification area, when loosing rep with a group (syndicate in hillsbrad is good for testing this), there is a repeated negation symbol. That is, it reads out "--100 rep, (syndicate)".
Upon poking at it, I found the error... on line 2800 of data\combatevents.lua, the line is currently and should be
New combat log probably gives the negative sign already?
Hope that helps! (and doesn't introduce new bugs ><)
Spy
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)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumMultiple buffs with the same name are only seen once. By this I mean if you have a trigger for say mongoose, and duel wield mongoose, the trigger will only fire on the first buff gain, and will not fire again until the buff fades. This means if you get two procs (one mainhand one offhand) you only get one message.
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.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWhile 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.
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
im getting this error when creating items using first aid and conjour water, anyone know why that might be? i thought it was ebb but now i am using sbf and still getting the error (even with sbf disabled).
Addons i'm using:
Bartender
ButtonFacade (+skins)
Cartographer (+mining and herbalism)
Chinchilla
Cowtip
Fubar (clockFu durabilityFu experienceFu)
MobInfo2
Omen
OmniCC, OmniCCoptions
Parrot
Pitbull
Prat
Quartz
Quest Helper
Satrinas buff frame (+sbf options)
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumfixed in r74499
thanks
I want to report that some triggers seem to have stopped working. At least the "riposte" trigger of my rogue which should trigger on every incoming parry. (I dont check for available skill since this always seemed to work unreliably)
I'm not sure if it stopped working with the release of 2.4.2 or maybe with the larger localization done in the last time. I'm playing on a german client.
Yes do it please :)
And in same way could you please add something for buff-fading-soon (duration <5 sec)?
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. In the meanwhile, for users, getting totem support in Parrot is just a matter of installing ParrotOnFire alongside Parrot.
Direct download: http://files.wowace.com/ParrotOnFire/ParrotOnFire.zip
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNice work.
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.
That's a great idea. That way, only the people that want the totemdamage displayed can have it displayed.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumfixed in r74808
Edit: Nevermind
You may want to take into consideration that under normal circumstances Shamans do not have pets. The exceptions are a few quests (can only think of one where the pet actually does damage). So basically, treating totem damage like pet damage is not going to be a problem for any sane people - I'd consider it extreme overkill to add a separate configuration category for them.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt's on my TODO-list
edit:
totem-damage is in r74959