CTCPpack packs a message into CTCP format.

CTCPpackString packs a message into CTCP format from strings.

CTCPunpack unpacks a CTCP message.

CTCPunpackString unpacks a CTCP message to strings.

Hostname returns the host of the host.

IsCTCP checks if the current byte string is a CTCP message.

IsCTCPString checks if the current string is a CTCP message.

NewEvent constructs a event object that has a timestamp.

NewNetworkInfo initializes a networkinfo struct.

Nick returns the nick of the host.

Split splits a host into it's fragments: nick, user, and hostname.

Username returns the username of the host.

Pseudo Events, these events are not real events defined by the irc protocol but the bot provides them to allow for additional events to be handled such as connect or disconnects which the irc protocol has no protocol defined for.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

Pseudo Events, these events are not real events defined by the irc protocol but the bot provides them to allow for additional events to be handled such as connect or disconnects which the irc protocol has no protocol defined for.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are healthy defaults for a NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

These constants are the mappings from the 004 and 005 events to their respective spots inside the NetworkInfo type.

IRC_MAX_LENGTH is the maximum length for an irc message.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

Pseudo Events, these events are not real events defined by the irc protocol but the bot provides them to allow for additional events to be handled such as connect or disconnects which the irc protocol has no protocol defined for.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

IRC Reply and Error Events.

SPLIT_BACKWARD is the maximum number of characters split will search backwards from IRC_MAX_LENGTH for a space when spliting message to long to fit on one line.

IRC Events, these events are 1-1 constant to string lookups for ease of use when registering handlers etc.

Event contains all the information about an irc event.

Helper fullfills the Writer's many interface requirements.

NetworkInfo is used to record the server capabilities, this later aids in parsing irc protocol.

Writer provides common write operations in IRC protocol fashion to an underlying io.Writer.

Host is a type that represents an irc hostname.

Mask is an irc hostmask that contains wildcard characters ? and *.