From Eggdrop Wiki

Revision as of 20:08, 25 November 2011 by SKy (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search



The partyline is very useful to find out why you bot won't come to irc or to see if scripts are working properly and so on. There are a lot common problems in order to join the partyline.

There are different methods to get on the partyline.

/dcc chat <botnick>
/ctcp chat <botnick>
telnet <ipadress> <listen-port>

dcc chat

  • dcc chat will only work if the bot is already on IRC
  • needs server port on your local computer
  • The local computer from where you want to establish a dcc connection needs to be able to open a server port. This means it needs to be reachable from outside. This is a major problem these days as most routers have NAT enabled by default. If you want to learn that, it's not really eggdrop related. Consult your routers manual for port forwarding or search the web.
  • in this case it does not matter if the bot is running firewalled shell
  • for many clients (mIRC, xchat, ...) type:
/dcc chat <botnick>

ctcp chat

  • ctcp chat will only work if the bot is already on IRC
  • in this case it does not matter if your local computer is firewalled
  • the shell where the eggdrop may not run a firewall or must forward the listen port
  • you need to set the listen port in your eggdrop configuration file, consult eggdrop example configuration file for details
listen <listen-port> all
listen 55555 all
  • for many clients (mIRC, xchat, ...) type:
/ctcp chat <botnick>


  • most operating systems have a telnet client preinstalled (Windows 7 has not, google 'Windows 7 telnet client' how to install it)
  • when you eggdrop is running on a shell you can login into your shell and type for example
telnet <listen-port>
telnet 55555

the advantage of this method is that no firewall can be in the way

  • After you made sure that this is working you do not need to login into your shell. You can telnet from your local computer.
telnet <shell-ip> <listen-port>
source "scripts/telnetclient.tcl"
  • After being on your sBNC type
/sbnc addtelnet <session-name> <shell-ip> <listen-port>

If sBNC installed on the same shell you can also use 127.0.0.l as IP-adress and of course there will be also no firewall problems.

/sbnc addtelnet lamestbot 127.0.0.l 55555
Retrieved from ""
Personal tools