You saved the script onto a text file and called it something.tcl ? placed it into your eggdrop/scripts directory and added source scripts/something.tcl to the bottom of your config?
The lifecycle of a noob is complex. Fledgling noobs gestate inside biometric pods. Once a budding noob has matured thru gestation they climb out of their pod, sit down at a PC, ask a bunch of questions that are clearly in the FAQ, The Noob is born
You saved the script onto a text file and called it something.tcl ? placed it into your eggdrop/scripts directory and added source scripts/something.tcl to the bottom of your config?
yes, I did all that.... I installed it as a normal TCL. but still does not work. The bot is klined, but does not return under a new vhost. :\
I don't understand...
yes, but I don't get it. so how can the script choose another vhost on disconnect and reconnect to that vhost?
sounds quite simple...
bot gets disconnected, it changed vhost and connects again...
is this posible?
In a nutshell, no! The ban is enforced before your bot can ever get the needed info to swap the host and once disconnected (which you are) it's impossible for the script to switch to another vhost; the default vhost is used always.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
Alchera wrote:In a nutshell, no! The ban is enforced before your bot can ever get the needed info to swap the host and once disconnected (which you are) it's impossible for the script to switch to another vhost; the default vhost is used always.
that is not correct... you get an ERROR ("Closing link" etc.) message from the server upon disconnect because of a K-line/G-line, so you can bind to it and do the vhost hopping
of course, this is not the case when you are D-lined - the server doesn't notify you and simply drops the connection
@ demond: Haven't got a "trick" to get past this stupid DALnet release command have you? It's been a thorn in not only my side for ages but awyeah's as well and neither of us seem to able to find a solution. lol
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
demond wrote:@Alchera: what's the problem with it? I presume you meant NickServ's RELEASE
Yup, the very one.. lol
Need the bot to switch from its normal main nick if the nick is being held to an alternative nick (as per conf) and then issue the release command so it can switch back to it's normal nick.I've tried a few approaches (and came close) but failed in all efforts.
BTW: Nice avatar.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
demond wrote:@Alchera: what's the problem with it? I presume you meant NickServ's RELEASE
Yup, the very one.. lol
Need the bot to switch from its normal main nick if the nick is being held to an alternative nick (as per conf) and then issue the release command so it can switch back to it's normal nick.I've tried a few approaches (and came close) but failed in all efforts.
BTW: Nice avatar.
why not do a USERHOST on the main nick and if the answer is something like enforcer@services, issue a RELEASE?
Tried something similar; instant disconnect to DALnet when a nick is held therefore making it (apparently) impossible to issue the command.
Switching to the alternate nick (when the error is received) to issue the command and then allowing the bot to recover it's main nick (as normal) seems to be the only way.
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM
@Alchera: you might want to try what I posted, setting ::nick instead of ::my-ip (and once connected, do the USERHOST and RELEASE stuff and then set ::nick back)
@Thunderdome: that code should work on any RFC1459 (IRC protocol standard spec) compliant network (I've never been to PTnet)