- Disconnecting.pod: Mention when it is appropriate to use C<< $irc->yield('shutdown') >>. - Connector.pm: Clear the reconnect timer when the plugin is deleted so that we can actually shut down the IRC component. - Depend on POE::Component::Pluggable 1.26 for irc_plugin_error
- CTCP.pm: Do "use POE::Component::IRC;" to avoid weird failures when this plugin is compiled by code which hasn't done the same.
Without this, dzil adds poco-server-irc stuff to BUILD_REQUIRES even though we have it in t/inc/
I was getting really odd failures because of this. The CTCP plugin uses $POE::Component::IRC::VERSION, and it compiles without the "use", but its absence prevented me from using POE::Component::IRC::State in the code which compiled the CTCP plugin.
[@Git] must come after [NextRelease] so the timestamp made by the latter will be committed.
Ill-configured dzil caused this step to be skipped
This makes it possible to have a bot which responds to commands as well as to messages (e.g. a configurable chatterbot).
Removed the undocumented behavior of concatenating multiple arguments. It only accepts one argument now, and newlines/CR in a message (and everything following them) will be stripped as with other commands.