Chatterbox is a successor to AnnoyRP; it detects events and responds to them by, for instance, saying witty things. You could "/party Ow." when you die. You could say various funny things when draining souls.
By default, Chatterbox uses a low chance (about 5%) of saying anything at all in response to events. Trust me! THIS IS A GOOD THING.
Chatterbox seems to be stable!
Feedback is welcome.
Upcoming features:
Some way to share events between characters.
0.14:
* Changed font so {} and [] can be told apart.
* "Interrupt" event type reworked: now watches for SPELL_INTERRUPT combat log event, instead of UNIT_SPELLCAST_INTERRUPTED unit event. This allows to pass interrupting spell, interrupting spell source, interrupted spell and interrupted target as ${ability}, ${source}, ${info} and ${target}. Old functionality is still available as "Interrupted" type. Please be cautious when using both "Interrupt" and "Interrupted", they may clash.
* Added new event type: "Summon". It corresponds to SPELL_SUMMON combat log event. Use ${ability} and ${target} to pass summoning spell name and summoned creature name. Examples:
I choose you, ${target}!
Yes, ${target}, it is in your contract!
Event is triggered by hunter pet summons, warlock demon summons, shaman totems etc. As usual, if you want to create an event for particular summon, write its ability or target in corresponding event field.
0.13:
* TOC for 4.0.
* Fixed for 4.0 API.
* Fixed editing of throttle value.
* Fixed displaying of options.
* Debug options now are saved between sessions.
* Added tooltips to "Fast" and "Pass" checkbuttons.
-------
Implemented /cbx say and /cbx psay (to say something from a chatter list either unconditionally or with a given percentage chance), fixed a few bugs. Sorry for the delay, folks.
Works with WotLK now (the tab interface and scroll interface both changed).
The 4.1 change in combat log format must have broken Chatterbox too. As I don't have active account, I can't log in and check the fix, but I hope this will work:
In Chatterbox.lua file, find
Code:
function CBox.Event_Combat(event, ...)
line and replace
Code:
local arg4 = select(4, ...)
local arg7 = select(7, ...)
local arg9, arg10 = select(9, ...)
local arg12 = select(12, ...)
local arg13 = select(13, ...)
local arg15 = select(15, ...)
local arg18 = select(18, ...)
with
Code:
local arg4 = select(5, ...)
local arg7 = select(8, ...)
local arg9, arg10 = select(10, ...)
local arg12 = select(13, ...)
local arg13 = select(14, ...)
local arg15 = select(16, ...)
local arg18 = select(19, ...)
With 4.3.3 I'm finding reasonable success with the following. Keep in mind that this was a quick hack. I haven't really gone back to be sure what I did was correct. But it's working pretty well for my uses - well enough to not overcome abject laziness. YMMV.
Code:
local arg4 = select(5, ...)
local arg7 = select(6, ...)
local arg9, arg10 = select(12, ...)
local arg12 = select(14, ...)
local arg13 = select(15, ...)
local arg15 = select(17, ...)
local arg18 = select(21, ...)
Again - there may be errors in this that I'm not seeing as I'm only looking for some specific events. But hey - at least you'll be less broken.
1. I would be happy to answer questions about Chatterbox source, but as noted, I'm not playing WoW (my accounts are perma-deleted, too, I have... issues with Activision), so I can't comment on the current API. I check my PMs here very occasionally, or you can email me.
2. The RIFT test shard has an addons button on character select. It is quite possible that Chatterbox will show up there.
It seems that Chatterbox is our own Defence Against Dark Arts position: first Seebs stopped playing WoW, then I stopped playing WoW three months after I started maintaining the addon.
The 4.1 change in combat log format must have broken Chatterbox too. As I don't have active account, I can't log in and check the fix, but I hope this will work:
In Chatterbox.lua file, find
Code:
function CBox.Event_Combat(event, ...)
line and replace
Code:
local arg4 = select(4, ...)
local arg7 = select(7, ...)
local arg9, arg10 = select(9, ...)
local arg12 = select(12, ...)
local arg13 = select(13, ...)
local arg15 = select(15, ...)
local arg18 = select(18, ...)
with
Code:
local arg4 = select(5, ...)
local arg7 = select(8, ...)
local arg9, arg10 = select(10, ...)
local arg12 = select(13, ...)
local arg13 = select(14, ...)
local arg15 = select(16, ...)
local arg18 = select(19, ...)
Based on the Real ID stuff, Chatterbox is hereby unmaintained. Anyone who wants to pick it up is welcome to, but I'm done.
(And yes, I know they sort of backed down, but comments since then, and the way Real ID appears to work in SC2, have pretty much confirmed this; I'm off playing City of Heroes now. Anyone who wants my old mods is welcome to mess with them.)
Originally posted by Jesamyn I am getting this error when adding an event:
Code:
[2009/02/15 11:33:25-1898-x1]: Chatterbox\Chatterbox.lua:937: bad argument #2 to 'sub' (number expected, got nil)
Chatterbox\Chatterbox.lua:937: in function `ExtractChatLists'
Chatterbox\Chatterbox.lua:904: in function `AddEvent'
Chatterbox\Chatterbox.lua:1595: in function <Interface\AddOns\Chatterbox\Chatterbox.lua:1572>
Weird thing is that after a reload, it does seem to have added it.
Huh! I haven't seen that, but I think I had another report like that.
I plan to have a look at this sometime soon and maybe clean some things up. Thanks for the report, I'll be looking into it.
Originally posted by Jesamyn I am getting this error when adding an event:
Code:
[2009/02/15 11:33:25-1898-x1]: Chatterbox\Chatterbox.lua:937: bad argument #2 to 'sub' (number expected, got nil)
Chatterbox\Chatterbox.lua:937: in function `ExtractChatLists'
Chatterbox\Chatterbox.lua:904: in function `AddEvent'
Chatterbox\Chatterbox.lua:1595: in function <Interface\AddOns\Chatterbox\Chatterbox.lua:1572>
Weird thing is that after a reload, it does seem to have added it.
Hmm. That's... odd. I'm not seeing it right now, but I'll have a look. This could happen if there were no characters other than spaces, or a comma followed by no characters other than spaces, I think. Hmm. I'll have to mess around with it.
[2009/02/15 11:33:25-1898-x1]: Chatterbox\Chatterbox.lua:937: bad argument #2 to 'sub' (number expected, got nil)
Chatterbox\Chatterbox.lua:937: in function `ExtractChatLists'
Chatterbox\Chatterbox.lua:904: in function `AddEvent'
Chatterbox\Chatterbox.lua:1595: in function <Interface\AddOns\Chatterbox\Chatterbox.lua:1572>
Weird thing is that after a reload, it does seem to have added it.
__________________
I'm not an idiot. I'm just harmlessly psychotic.
My question to you is - did I miss this documentation elsewhere on this site? Or do you just hide it so those of us who know nothing will never get the full functionality of this excellent addon? [/b]
In theory, it ought to give some kind of a brief message when it first loads which hints at how to invoke it. I think.
Sorry, been in crunch time at work and haven't had time to work on this.
This is by far my favorite addon despite the fact that I have no freakin' idea how to work it. I know next to nothing about addons and couldn't find any documentation on here about how to use it. I saw from the posts that there are tabs and such and, having never actually seen anything on my screen that looks like a Chatterbox controller, I had no idea how to access them.
Brilliant, addon-illiterate me finally thought to open the Chatterbox folder in my addons folder, where I found something cryptically called Docs that explains everything.
My question to you is - did I miss this documentation elsewhere on this site? Or do you just hide it so those of us who know nothing will never get the full functionality of this excellent addon?
Optimally I'd like to see an checkbox for each Event or best of all individual Chatters to turn it off out of combat. This would allow chatters for spells meant to be used out of combat to retain them for utility's sake, such as portals, res spells and buffs, but avert issues like the example I gave above without any fuss.
Thanks for your time. [/b]
I sort of like that -- maybe a combat flag and a non-combat flag, similar to the intent of the self/other flags (which I don't think work right now).