egghelp/eggheads community

No, you can't change the bots nick with the /nick command., but you CAN change it using 'botnick.tcl' found here on slennox's site. Install it and use .botnick newnick via the partyline. I also wonder how, if still possible, bots could be added to X on Undernet. I know it used to be possible BEFORE ...

Yes masskilla, you are correct, I misunderstood about the 'user file' thing. I was incorrect......BUT it DID say "eggdrop" and not "windrop". I took his last statement as "he HAS been running windrops, but now is trying EGGdrops and has never gotten this error message before...

While making the eggdrop when it came to the:
"make install DEST=~/botdir" part, did you rename the '/botdir' to something else and THEN type it as ".eggdrop -m <what-ever-you-changed-it-to>" ?

Not sure if you CAN shut off autoop of the owner when de-oped. My personal quetion is why the is owner is being de-opped? You may try making sure protect ops is off via party line, but I still don't think this will work for an owner.

Usually when I have trouble with a bot connecting to a server I can telnet or SSH connect to it and 'usually' it gives an error message there everytime it tries to connect to a server. i.e "dns lookup failed" or "too many connections from host" so on and so on. One ides would be ...

Either you can set the password by using in the party line:
.chpass username password
or they can set their own password with:
/msg botname PASS <password> (without the < >'s)

I always try to get the user when they set their own to make sure they do it on the hob bot if possuble.

My suggestion? Not to tell people how or how NOT to reply. You never know when that valuable piece of information that someone WOULD'VE replied to you with may have been the answer you were looking for.

Are you able to join the party line? And if so have you tried op-ing yourself WHILE on the party line to see if there is an error message there? Also hope your not typing just "/msg OP pass" as your topic points out

Well if the IP address is 'ident@255.255.255.255' that usually means a problem with the shell and/or the way the bot is running BECAUSE of something to do with the shell. Has to do with the DNS lookup "i believe". As long as that keeps doing it they probably will not be able to join a serv...

Hey, I'm just glad I could help. I, too, am learning all about eggdrops. Some of the more simple problems I can help out with but when it comes to the more complex problems, the true experts that are here have to help out.

Nope, sorry...maybe someone else on here can help you with that.

Like I stated previously. If you can connect either DCC or telnet tpye ".rehash" it will give you something like this: [05:09] <BotNick> [05:15] #DrTongue# rehash [05:09] <BotNick> Rehashing. [05:09] <BotNick> [05:15] Writing user file... [05:09] <BotNick> [05:15] Writing channel file ... ...

If you can now connect via the partyline do a .rehash and verify that all your .tcl's are not listed there. Is that how you checked to see if the are loaded or not?

Ok, have you been able to connect to the bot at ALL? Like for the first time when you set a password? If you haven't , did you edit the bind-'hello' part of the config and change it to something else unbind msg - hello *msg:hello bind msg - <my new word> *msg:hello If you changed it you'll have to m...

Well if all the scripts were loaded at start up they 'should' be running. It doesn't hurt to do .rehash on the party line, all the .tcl scripts that are loaded will be listed there.