You probably already have fixed the script by now, but people reading the thread in archives may find this useful.

You can create _default handler that can dump events that were not handled any other way. This short function will let you know which events you are getting. For example, some servers don't send an 001 message, so your irc_001 handler may never be triggered.

sub _default { my ( $state, $event, $args, $heap ) = @_[ STATE, ARG0, ARG1, HEAP +]; $args ||= []; # Prevents uninitialized-value warnings. print "default: $state = $event (@$args)\n"; return 0; }

POE's cookbook contains a few recipes about IRC bots, including the _default debugging trick.

-- Rocco Caputo - rcaputo@pobox.com - poe.perl.org


In reply to Re: POE::IRC Not joining Channel by rcaputo
in thread POE::IRC Not joining Channel by kosh

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.