Sends a line to the other end of the connection.

Called with creation date information about the server, usually at logon.

Parameters

when

A string describing when the server was created, probably. (type: str )

Called with daemon information about the server, usually at logon.

Parameters	info	(type: str )
	when	A string describing what software the server is running, probably.

Called with information about the server, usually at logon.

Parameters	servername	The hostname of this server. (type: str )
	version	A description of what software this server runs. (type: str )
	umodes	All the available user modes. (type: str )
	cmodes	All the available channel modes. (type: str )

Called with information about the number of connections, usually at logon.

Parameters

info

A description of the number of clients and servers connected to the network, probably. (type: str )

Called with information about where the client should reconnect.

Parameters

info

A plaintext description of the address that should be connected to. (type: str )

Called with various information about what the server supports.

Parameters

options

Descriptions of features or limits of the server, possibly in the form "NAME=VALUE". (type: list of str )

Called with the number of channels existant on the server.

Parameters

channels

(type: int )

Called with the number of ops logged on to the server.

Parameters

ops

(type: int )

Called with information about the server connected to.

Parameters

info

A plaintext string describing the number of users and servers connected to this server. (type: str )

Called when I have a message from a user to me or a channel.

Called when I finish joining a channel.

channel has the starting character (# or &) intact.

Called when I have left a channel.

channel has the starting character (# or &) intact.

Called when I have a notice from a user to me or a channel.

By default, this is equivalent to IRCClient.privmsg, but if your client makes any automated replies, you must override this! From the RFC:

   The difference between NOTICE and PRIVMSG is that
   automatic replies MUST NEVER be sent in response to a
   NOTICE message. [...] The object of this rule is to avoid
   loops between clients automatically sending something in
   response to something it received.

Called when a channel's modes are changed

Parameters	user	The user and hostmask which instigated this change. (type: str )
	channel	The channel for which the modes are changing. (type: str )
	set	true if the mode is being added, false if it is being removed. (type: bool or int )
	modes	The mode or modes which are being changed. (type: str )
	args	Any additional information required for the mode change. (type: tuple )

Called with the results of a CTCP PING query.

Called after sucessfully signing on to the server.

Called when I am kicked from a channel.

Called when my nick has been changed.

Called when I see another user joining a channel.

Called when I see another user leaving a channel.

Called when I see another user disconnect from the network.

Called when I observe someone else being kicked from a channel.

Called when I see a user perform an ACTION on a channel.

In channel, user changed the topic to newTopic.

Also called when first joining a channel.

A user changed their name from oldname to newname.

I received a message-of-the-day banner from the server.

motd is a list of strings, where each string was sent as a seperate message from the server. To display, you might want to use:

   string.join(motd, '\n')

to get a nicely formatted string.

Attempt to set the topic of the given channel, or ask what it is.

If topic is None, then I sent a topic query instead of trying to set the topic. The server should respond with a TOPIC message containing the current topic of the given channel.

Change the modes on a user or channel.

Send a message to a user or channel.

Parameters	user	The username or channel name to which to direct the message. (type: str )
	message	The text to send (type: str )
	length	The maximum number of octets to send at a time. This has the effect of turning a single call to msg() into multiple commands to the server. This is useful when long messages may be sent that would otherwise cause the server to kick us off or silently truncate the text we are sending. If None is passed, the entire message is always send in one command. (type: int )

Strike a pose.

Measure round-trip delay to another IRC client.

Send a DCC RESUME request to another user.

Send a DCC ACCEPT response to clients who have requested a resume.

Kicked? Who? Not me, I hope.

Someone in the channel set the topic.

I just joined the channel, and the server is telling me the current topic.

Dispatch method for any CTCP queries received.

A master index of what CTCP tags this client knows.

If no arguments are provided, respond with a list of known tags. If an argument is provided, provide human-readable help on the usage of that tag.

Initiate a Direct Client Connection

Called when I receive a DCC SEND offer from a client.

By default, I do nothing here.

Called when a client is trying to resume an offered file via DCC send. It should be either replied to with a DCC ACCEPT or ignored (default).

Called when a client has verified and accepted a DCC resume request made by us. By default it will do nothing.

Send one or more extended messages as a CTCP reply.

Parameters

messages

(type: a list of extended messages. An extended message is a (tag, data) tuple, where 'data' may be None. )

Send one or more extended messages as a CTCP query.

Parameters

messages

(type: a list of extended messages. An extended message is a (tag, data) tuple, where 'data' may be None. )

Dispatch method for any CTCP replies received.

Called when a fitting ctcpReply_ method is not found.

XXX: If the client makes arbitrary CTCP queries, this method should probably show the responses to them instead of treating them as anomolies.

When I get a message that's so broken I can't use it.

This is called when I receive a message which is peculiar, but not wholly indecipherable.

Called when a connection is made.

This may be considered the initializer of the protocol, because it is called when the connection is completed. For clients, this is called once the connection to the server has been established; for servers, this is called after an accept() call stops blocking and a socket has been received. If you need to send any greeting or initial message, do it here.

Called whenever data is received.

Use this method to translate to a higher-level message. Usually, some callback will be made upon the receipt of each complete protocol message.

Parameters

data

a string of indeterminate length. Please keep in mind that you will probably need to buffer some data, as partial (or multiple) protocol messages may be received! I recommend that unit tests for protocols call through to this method with differing chunk sizes, down to one byte at a time.

Override this for when each line is received.

Determine the function to call for the given command and call it with the given arguments.