<dominikh>
we've been considering including a list of all IRC commands that make for valid events, but that'd be a rather long list, so still debating it
ayonix has quit [Remote host closed the connection]
ayonix has joined #cinch
ayonix has quit [Read error: Connection reset by peer]
ayonix has joined #cinch
ayonix has quit [Remote host closed the connection]
ayonix has joined #cinch
xeviox is now known as xeviox|afk
<dominikh>
Zackio: want to file a bug so I don't forget?
marahin has left #cinch ["Leaving..."]
onewheelskyward has joined #cinch
skybotalpha has joined #cinch
skybotalpha has quit [*.net *.split]
onewheelskyward has quit [*.net *.split]
onewheelskyward has joined #cinch
skybotalpha has joined #cinch
cadence has joined #cinch
hephaestus_rg has joined #cinch
hephaestus_rg has quit [Quit: hephaestus_rg]
hephaestus_rg has joined #cinch
xeviox|afk is now known as xeviox
<CM-Punk>
How do I get my bot to read quit messages. Also is there a way to rate limit things like greetings?
<catepillar>
there is a global bot rate limit
<catepillar>
anything more than that, you need to supply
<catepillar>
as far as not reading quit messages anymore, you can either unregister the handler responsible, or add a condition to exit the handler
<leftylink>
my general conception of how to read quit messages which I'm just throwing off the top of my head without looking at docs: listen to a :quit event, the handler method gets passed a Message object, you want Message#text of that
<leftylink>
or maybe it was Message#message
<leftylink>
something along those lines anyway
<dominikh>
Message#message – we like stutter in our APIs
<CM-Punk>
Okay
<CM-Punk>
Cool
<CM-Punk>
So there's no further way, or maybe a gem to do a limit on how many greets it sends...like in the event of a netsplit rejoin?
<catepillar>
that would be best implemented by you