I had a look through the search and nothing really covered this. I got my bot to connect to the server and set the password. However when I tried to run:
/ctcp <botname> CHAT
I got the message:
Michelle ERROR reply: no telnet port
I am unable to DCC chat with the bot either as it says its wating for achnoledgement and never goes any futher. So I went into the config file and changed the port a few times then went back to Telnet and ran:
./eggdrop Michelle.conf
So that it would use the new config file with the new port (although the bot remained on the server during this time I think due to the idle time never restarting) However I still get the same problem so I dont think its to do with the port that the bot is listening on.
# If you would like the bot to listen for users and bots in separate ports,
# use the following format:
#
# listen 3333 bots
# listen 4444 users
#
# If you wish to use only one port, use this format:
#
# listen 3333 all
#
# You need to un-comment this line and change the port number in order to open
# the listen port. You should not keep this set to 3333.
listen 3333 all
I think thats the one being used as it says its listening at that port when I start the eggdrop from telnet.
If you do see (when starting it) something like: "listening on port xxx" then telnet to it's ip and xxx port or try again the ctcp chat on irc, see if that helps.
Once the game is over, the king and the pawn go back in the same box.
I tried connecting to the redbox.copaseticnet.com where I have it hosted with the port number but nothing happens then I get a connection timed out . The same thing happens when I use the IP address for it.
You may have to set the my-ip line. Some shells with multiple addresses (especially with local network addresses) don't let you open connections on some interfaces - such as the default interface if they have a decent number of them on that box. Whatever host the bot is going on irc from try using for my-ip (resolve it to the address first of course) and if that fails try using the ip address you connect to the shell with.
Search the forums for the words my-ip for a bit more detail on it if you can't locate it in your conf file (its usually towards the top).
Edit: On re-reading it seems you didnt .die the bot before running it again. (couldnt chat it to do so) Type 'ps x' and kill -9 any bots running. (kill -9 <process number>)Make sure there are none running at all, then start the bot again with your edited config file. Eggdrop SHOULD check for the pid file to see if its already running, but maybe something's borked on the shell..?
. The same thing happens when I use the IP address for it.
.