This method instantiates a bot object that's potentially ready to start running. The following are the main or primary available methods from this class. (See Daemon::Device for more details.) MAIN METHODS You can control their number along with setting locations for things like PID file, log files, and so on. When the bot is started, the parent process will fork or spawn a given number of children workers. (See Daemon::Control for more details.) Pre-Forking Device Command-line commands include: start, stop, restart, reload, status, help, and so on. Let's say you place the above code into a "bot.pl" file.
This won't actually do much apart from connecting to the server and responding to pings, but it's useful to understand how this works. You can have a running IRC bot with as little as: use Bot::IRC I also wanted to keep the direct dependencies and core bot minimalistic, allowing as much functionality as possible to be defined as optional plugins. Why? There are so many good bots and bot frameworks to select from, but I wanted a bot framework that worked like a Unix service out-of-the-box, operated in a pre-fork way to serve multiple concurrent requests, and has a dirt-simple and highly extendable plugin mechanism. Send_user_nick => 'on_parent', # or 'on_connect' or 'on_reply' # illustrative example of most settings and various ways to get at them # minimal bot instance that does basically nothing except join a channel
0 kommentar(er)
