for some reason, twice now, my bot has stopped accepting my password, though through telnet my password is still accepted. I do not know why this is happening, but i am unable to dcc chat with the bot because even with the correct password, it still says "badpass" and cancels the connection. Also it stops recognizing me as a user- for example i lose control of the tcl as well b/c it does not recognize me or something - plz help - Jeff Thanks
This is because the hostmasks you have in your bot, is not matching you, it is matching some1 else.
When you DCC chat, all the bot asks you for is your password. It gets your username, by looking for the first person it finds that matches your IRC hostname.
EG, 2 users.
user1 hostmask of *!*@*.isp.com
user2 hostmask of *!*@*.area.isp.com
User2 wants to login to the bot, but the bot thinks he is user1, because that is the first person that matches the hostmask.
I sugest getting some1 to set a better hostmask for yourself, and the other person that your hostmask is clashing with.
Somthing like *!*ident@*.isp.com would be better.
Note, as you stated you could get on via telnet, this is because it does not use hostmasks to determine who you are. Remember it asked you for your handle, before the password.
You can still use your IRC client to connect with the bot. Use "/ctcp <botnick> CHAT" and it will reverse DCC chat with you.
NOTE: I sugest fixing this issue with the hostmasks urgently though, as it could be a security risk. EG, you have global +n flags (AKA global owner), and the other matching user has only channel +v (channel voice). This means your are only being matched as a channel voice user, and are not protected as a owner. Under certain circumstanses, the bot may aslo go on to think that the other user (channel +v) is a global +n, this means that if they are OP'ed by mistake, they can deop any1, and the bot wont flinch. They could also use any channel commands, that they notmaly would not have access too.
had a similar problem with 2 users some time ago, both have been using aol and I added them like *!ident@*.aol.com to the bots.
For some reason, I guess both used a indentical IRC Client with default settings, both had the same ident. After changing the ident the problem was fixed.