IRC bot.
A single bot can be connected to multiple networks. The bot's username and real name are shared across all networks, but the nick name can differ.
Bot configuration.
All fields are required.
All fields are required.
All fields are required.
All fields are required.
Create a new bot with the given configuration.
If eventLoop is passed, connections by this bot will be handled by the given event loop. Otherwise, the bot shares a default event loop with all other bots created in the same thread.
Boolean whether or not command invocations are allowed in private messages.
The event loop handling connections for this bot.
The command prefix used to invoke bot commands through chat messages.
The username of this bot.
The real name of this bot.
InputRange of all networks the bot is connected to, where each network is represented by its IrcClient connection.
InputRange of all command sets (diggler.command.ICommandSet) registered with the bot.
Request a new nick name for the bot on all networks.
The bot may have different nick names on different networks. Use the nick property on the clients in Bot.clients to get the current nick names.
Connect the bot to a network described in the IRC URL url.
The new connection is automatically added to the event loop used by this bot.
Register a command set with the bot.
ICommandSet cmdSet | command set to register |
Give bot administrator rights to all the users in accountNames, by account name.
The account name is the name of the account the user has registered
with the network's authentication services, such as AuthServ or NickServ.
Authenticated bot administrators can run commands with the @admin
command attribute.
Convenience method to start an event loop for a bot.
Same as executing bot.eventLoop.run().