Is there a better (more efficient) way for a Taunt resist notify addon? It seems to me that parsing every single combat log event is a bit wasteful. Forgive me of my ignorance :(
TauntResist = AceLibrary("AceAddon-2.0"):new("AceEvent-2.0")
function TauntResist:OnEnable()
self:RegisterEvent("COMBAT_LOG_EVENT_UNFILTERED")
end
function TauntResist:COMBAT_LOG_EVENT_UNFILTERED(timestamp, event, sourceGUID, sourceName, sourceFlags, destGUID, destName, destFlags, ...)
if( event=="SPELL_MISSED" and sourceName==UnitName("player") ) then
local spellId, spellName, spellSchool, missType = select(1, ...)
if (spellName == "Taunt" or spellName == "Growl" or spellName == "Challenging Roar" or spellName == "Challenging Shout") then
if missType == "RESIST" then
-- Taunt resist on BrownBear.
SendChatMessage(spellName.." resist on "..destName..".", "YELL");
elseif missType == "EVADE" then
-- Taunt on BrownBear failed! Evading on John.
SendChatMessage(spellName.." on "..destName.." failed! Evading on "..UnitName("targettarget")..".", "YELL");
end
end
end
end
I am sure this has been requested before... Given that sRF are basically the best unit frames for debuff/health monitoring, is there anyway for them to be active when you are in a party (but not a raid)? So essentially I could use them as all purpose unitframes for anytime I am in a group?
Thank you very much for adding the ability for negative padding. I was going to switch to BT3!
You can enable CyCircled by changing line 69 of Bongos.lua in the plugins directory to:
table.insert(self.elements["Main"].elements, format("Bongos3ActionButton%d", i))
doing a grep through my addons directory for "49431" I get no results. I installed Parrot and its dependencies (with non-embedded libs) and I still get this error, strange... The header for my LibRockConfig is:
--[[
Name: LibRockConfig-1.0
Revision: $Rev: 50569 $
Developed by: ckknight (ckknight@gmail.com)
Credits: Nargiddley, inspiration and some code taken from Waterfall-1.0
Website: http://www.wowace.com/
Description: Library to allow for easy configuration.
Dependencies: LibRock-1.0
License: LGPL v2.1
]]
local MAJOR_VERSION = "LibRockConfig-1.0"
local MINOR_VERSION = tonumber(("$Revision: 50569 $"):match("(%d+)")) - 100000
So it looks like its taking the revision number and subtracting 100000 to get the " -49431 ".
I still get this error after I click on the FuBar icon or right click on Fubar itself. I updated all of my ace addons tonight. I have had this error for about 4 weeks now, making Rock-based addons unuseable.
[2007/10/03 01:45:26-2152-x1]: LibRockConfig-1.0--49431:1578: bad argument #1 to 'format' (string expected, got table)
LibRockConfig-1.0--49431:1578: in function <...s\FuBar\libs\LibRockConfig-1.0\LibRockConfig-1.0.lua:1386>
LibRockConfig-1.0--49431:2743: in function `Select'
LibRockConfig-1.0--49431:698: in function `OpenConfigMenu'
LibRockConfig-1.0--49431:6643: in function `OnFuBarClick'
LibFuBarPlugin-3.0-49429:1113: in function <...ockFu\libs\LibFuBarPlugin-3.0\LibFuBarPlugin-3.0.lua:1109>
What falls under the "Cast" filter? For some reason it is not firing for any of my spells, as a Druid. The only time it ever fires is when I cast "Cower" in cat form. For example, Wrath, Lifebloom, Healing touch, and Innervate are not triggering the event. Am I mistaken and these are not supposed to fire inside of a "Cast" filter?
[2007/07/12 19:10:32-2314-x1]: kEnergy\frame.lua:66: attempt to perform arithmetic on local 'x' (a table value)
AceAddon-2.0-42430 (Ace2):927: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:920>
<in C code>: ?
AceEvent-2.0-40601 (Ace2):232: in function `TriggerEvent'
AceEvent-2.0-40601 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
---
I installed the newest version, did a profile reset. Then exited WOW and logged back in. I got the above error. I am a druid.
I got the following errors after updating all my Ace addons with the update program:
[2007/06/16 11:52:25-2147-x1]: Chronometer-0.10\Core\Chronometer.lua:125: attempt to index global 'ParserLib' (a nil value)
AceAddon-2.0-39076 (Ace2):455: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:432>
<in C code>: ?
AceEvent-2.0-38824 (Ace2):320: in function `TriggerEvent'
AceEvent-2.0-38824 (Ace2):1019: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:1012>
[2007/06/16 11:52:52-2147-x1]: Chronometer-0.10\Core\Chronometer.lua:339: attempt to index field 'COLOR_MAP' (a nil value)
AceAddon-2.0-39076 (Ace2):663: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:656>
<in C code>: ?
AceEvent-2.0-38824 (Ace2):251: in function `TriggerEvent'
AceEvent-2.0-38824 (Ace2):1019: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:1012>
I have a Parser-3.0 library folder in my Addons directory.
would it be possible to set up a BucketEvent and watch CHAT_MSG_CHANNEL_JOIN so that when someone logs in and joins multiple channels, one doesn't get spammed with 3 messages (XXX joined channel. XXX joined channel.)
I know we are able to completely block these messages, but that is a bit too extreme.
would it be possible to set up a BucketEvent and watch CHAT_MSG_CHANNEL_JOIN so that when someone logs in and joins multiple channels, one doesn't get spammed with 3 messages (XXX joined channel. XXX joined channel.)
I know we are able to completely block these messages, but that is a bit too extreme.
0
0
Is there a better (more efficient) way for a Taunt resist notify addon? It seems to me that parsing every single combat log event is a bit wasteful. Forgive me of my ignorance :(
0
0
You can enable CyCircled by changing line 69 of Bongos.lua in the plugins directory to:
table.insert(self.elements["Main"].elements, format("Bongos3ActionButton%d", i))
0
Can you please not auto release if you have a soul stone:?
0
--[[
Name: LibRockConfig-1.0
Revision: $Rev: 50569 $
Developed by: ckknight (ckknight@gmail.com)
Credits: Nargiddley, inspiration and some code taken from Waterfall-1.0
Website: http://www.wowace.com/
Description: Library to allow for easy configuration.
Dependencies: LibRock-1.0
License: LGPL v2.1
]]
local MAJOR_VERSION = "LibRockConfig-1.0"
local MINOR_VERSION = tonumber(("$Revision: 50569 $"):match("(%d+)")) - 100000
So it looks like its taking the revision number and subtracting 100000 to get the " -49431 ".
0
[2007/10/03 01:45:26-2152-x1]: LibRockConfig-1.0--49431:1578: bad argument #1 to 'format' (string expected, got table)
LibRockConfig-1.0--49431:1578: in function <...s\FuBar\libs\LibRockConfig-1.0\LibRockConfig-1.0.lua:1386>
LibRockConfig-1.0--49431:2743: in function `Select'
LibRockConfig-1.0--49431:698: in function `OpenConfigMenu'
LibRockConfig-1.0--49431:6643: in function `OnFuBarClick'
LibFuBarPlugin-3.0-49429:1113: in function <...ockFu\libs\LibFuBarPlugin-3.0\LibFuBarPlugin-3.0.lua:1109>
---
0
0
0
AceAddon-2.0-42430 (Ace2):927: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:920>
<in C code>: ?
AceEvent-2.0-40601 (Ace2):232: in function `TriggerEvent'
AceEvent-2.0-40601 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
---
I installed the newest version, did a profile reset. Then exited WOW and logged back in. I got the above error. I am a druid.
0
0
[2007/06/16 11:52:25-2147-x1]: Chronometer-0.10\Core\Chronometer.lua:125: attempt to index global 'ParserLib' (a nil value)
AceAddon-2.0-39076 (Ace2):455: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:432>
<in C code>: ?
AceEvent-2.0-38824 (Ace2):320: in function `TriggerEvent'
AceEvent-2.0-38824 (Ace2):1019: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:1012>
[2007/06/16 11:52:52-2147-x1]: Chronometer-0.10\Core\Chronometer.lua:339: attempt to index field 'COLOR_MAP' (a nil value)
AceAddon-2.0-39076 (Ace2):663: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:656>
<in C code>: ?
AceEvent-2.0-38824 (Ace2):251: in function `TriggerEvent'
AceEvent-2.0-38824 (Ace2):1019: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:1012>
I have a Parser-3.0 library folder in my Addons directory.
0
I know we are able to completely block these messages, but that is a bit too extreme.
0
I know we are able to completely block these messages, but that is a bit too extreme.
0