egghelp/eggheads community

Server says bot's nick is invalid

2006-03-13T17:18:49-04:00

Minor fix to the above script; the author left out the 'passwordbot' setting:
Change:

Code:

set aslinick $nickset needrelease 0

to:

Code:

set aslinick $nickset needrelease 0set passwordbot "PutYourBotPassHere"

... replacing 'PutYourBotPassHere' with your actual botnick password.

Statistics: Posted by Alchera — Mon Mar 13, 2006 5:18 pm

Server says bot's nick is invalid

2006-02-01T10:11:33-04:00

This script could be of great assistance to those on DALnet using eggdrop.

Statistics: Posted by Alchera — Wed Feb 01, 2006 10:11 am

script nickrelease.tcl

2006-01-31T21:15:08-04:00

i create this script after i know raw 432
thanks

Code:

set aslinick $nickset needrelease 0bind raw - 432 release_nickproc release_nick {from key text} {global botnick nick altnick needreleaseif {[string match "*Services*RELEASE*nickname*please wait patiently and try again later*" " $text "]} {set keep-nick 0set needrelease 1set nick "$altnick"putlog "Change nick to $altnick and then jump."jump}}bind notc - "*Do not share your password with anyone*" releasenick2proc releasenick2 {n uhost hand text dest} {        global nickbot passwordbot needrelease aslinick        set nickserv "nickserv"if {$needrelease == 1} {        if {[string match [string tolower $n] [string tolower $nickserv]]} {                putlog "Release to NickServ for $aslinick."                putserv "PRIVMSG NickServ@services.dal.net :release $aslinick $passwordbot"        }}}bind notc - "The nickname * has been released." success_releaseproc success_release {n uhost hand text dest} {        global nickbot passwordbot needrelease aslinick        set nickserv "nickserv"if {$needrelease == 1} {        if {[string match [string tolower $n] [string tolower $nickserv]]} {                putlog "Success Release."putserv "NICK $aslinick"set keep-nick 1set needrelease 0set nick "$aslinick"putlog "Change nick to $aslinick"        }}}bind notc - "*is currently being held by a Services Enforcer. If you are the nicks owner, use *msg NickServ@services.dal.net RELEASE*" notc_nick_releaseproc notc_nick_release {n uhost hand text dest} {        global nickbot passwordbot needrelease aslinick        set nickserv "nickserv"if {$needrelease == 0} {        if {[string match [string tolower $n] [string tolower $nickserv]]} {putlog "Release to NickServ for $aslinick."putserv "PRIVMSG NickServ@services.dal.net :release $aslinick $passwordbot"set keep-nick 0set needrelease 1set nick "$altnick"putlog "Change nick to $altnick"putserv "NICK $altnick"        }}}putlog "nick release v 0.1"

Statistics: Posted by cachak — Tue Jan 31, 2006 9:15 pm

Server says bot's nick is invalid

2004-10-04T07:07:12-04:00

Read the posts above and utilize the scripts posted by some users and myself. Some ought to work!

Statistics: Posted by awyeah — Mon Oct 04, 2004 7:07 am

Server says bot's nick is invalid

2004-10-04T06:53:43-04:00

awyeah: i have a problem same with you, all my bot can't get in to dalnet. i really hate this way that dalnet threat this way.

is that code really works? how about setup in conf file using
putserv "privmsg nickserv@services.dal.net :release "

hehe that's a manual for me.

regards,
qwek

Statistics: Posted by qwek — Mon Oct 04, 2004 6:53 am

Server says bot's nick is invalid

2004-09-25T09:25:51-04:00

This is not tested, though.
Replace the nick password with $nickpass.

You don't have to set $botnick as will be read as the bots current nick which is being used on irc either it will be $nick or $altnick or any other nick. As for $nick it will be the bots main nick set in the configuration file and $altnick will be the alternate nick (will be used if main nick, $nick is in use) which is also defined in the configuration file.

Statistics: Posted by awyeah — Sat Sep 25, 2004 9:25 am

Server says bot's nick is invalid

2004-09-24T18:21:29-04:00

What you can do here is directly bind to the raw number as you have done, 432 if its correct or string match the $arg or $text var.
This is the raw and not 'Server say nick is invalid.' You will need to match for the following text:

The nick asskicker is currently being held by a Services Enforcer. If you are the nicks owner, use /msg NickServ@services.dal.net RELEASE asskicker password to release the nickname. If the nickname recently expired, please wait patiently and try again later. [asskicker]
Code:
bind raw - 432 nickserv:release proc nickserv:release {from keyword arg} { global botnick nickpass nick altnick  putquick "NICK $altnick" -next  #putquick "NICK $nick[rand 10][rand 10]" #for alternative nick  puthelp "PRIVMSG NickServ@services.dal.net :RELEASE $nick $nickpass"  return 0} orbind raw - * nickserv:release proc nickserv:release {from keyword arg} { global botnick nickpass nick altnick if {([string match "*The nick * is currently being held by a Services Enforcer. If you are the nicks owner*" $arg])} {  putquick "NICK $altnick" -next  #putquick "NICK $nick[rand 10][rand 10]" #for alternative nick  puthelp "PRIVMSG NickServ@services.dal.net :RELEASE $nick $nickpass"  return 0  } } 
Note: I used puthelp for the delay in releasing the nick after you are connected and putquick -next for the nick change when you are connecting, which might solve it, if possible.

The thing is, mostly it doesn't let you kill the enforcer or release the nick when it gives you the raw message. You have to switch to an alternative nick, then bind init-server or something then go ahead and release that nick after you have connected to the server, not while you are connecting to it or when it is giving you that error message.

You cannot release the nick enforcer when it gives you that error message, and that is really crappy I say, the coders should atleast let people release it when they get the error while connecting.

The thing is that you are not fully connected to the client server, hence you cannot message nickserv to release your nick while you get that message. Untill you are fully connected then only you can.

where put the nick of the eggdrop and the passwd of the eggdrop ?¿

Statistics: Posted by devilsoulblack — Fri Sep 24, 2004 6:21 pm

Server says bot's nick is invalid

2004-09-23T20:39:33-04:00

Given the second scenario would ghosting the nick be an easier solution?

I guesss so. But that would always be handy if someone is using the bot's nick at anytime, not only when it has an enforcer or when it is held.

Statistics: Posted by awyeah — Thu Sep 23, 2004 8:39 pm

Server says bot's nick is invalid

2004-09-23T01:42:58-04:00

Given the second scenario would ghosting the nick be an easier solution?

Statistics: Posted by Alchera — Thu Sep 23, 2004 1:42 am

Server says bot's nick is invalid

2004-09-22T23:04:49-04:00

I know that but there must be a solution around it. Setting enforce off, would hold the bots nick if some one is using it, suppose some one was using it before I loaded the bot, or some one got it through a netsplit and a collison occured or the bot was lagging and didn't identify to it, or the bot couldnt change its nick because it was not opped on an +R, +M chan. There are so many cases!

I would have to make a tcl script for that too, if some one else is using the bot's nick and $botname does not match the bots user@host, and if it is not an enforcer, then use the nickserv ghost command to ghost the nick to make it regain its nick back, $nick.

Statistics: Posted by awyeah — Wed Sep 22, 2004 11:04 pm

Server says bot's nick is invalid

2004-09-22T22:25:32-04:00

hi Awyeah !

well just set off the enforced option for your bot nick (asskicker), manually release the nick by using

/nickserv release nick password
and set the enforced option off

and then try it will work , it worked for me too

BYE

ALI

Statistics: Posted by Bingooss — Wed Sep 22, 2004 10:25 pm

Server says bot's nick is invalid

2004-09-22T21:16:16-04:00

What you can do here is directly bind to the raw number as you have done, 432 if its correct or string match the $arg or $text var.

This is the raw and not 'Server say nick is invalid.' You will need to match for the following text:

The nick asskicker is currently being held by a Services Enforcer. If you are the nicks owner, use /msg NickServ@services.dal.net RELEASE asskicker password to release the nickname. If the nickname recently expired, please wait patiently and try again later. [asskicker]

Code:

bind raw - 432 nickserv:release proc nickserv:release {from keyword arg} { global botnick nickpass nick altnick  putquick "NICK $altnick" -next  #putquick "NICK $nick[rand 10][rand 10]" #for alternative nick  puthelp "PRIVMSG NickServ@services.dal.net :RELEASE $nick $nickpass"  return 0} orbind raw - * nickserv:release proc nickserv:release {from keyword arg} { global botnick nickpass nick altnick if {([string match "*The nick * is currently being held by a Services Enforcer. If you are the nicks owner*" $arg])} {  putquick "NICK $altnick" -next  #putquick "NICK $nick[rand 10][rand 10]" #for alternative nick  puthelp "PRIVMSG NickServ@services.dal.net :RELEASE $nick $nickpass"  return 0  } }

Note: I used puthelp for the delay in releasing the nick after you are connected and putquick -next for the nick change when you are connecting, which might solve it, if possible.

The thing is, mostly it doesn't let you kill the enforcer or release the nick when it gives you the raw message. You have to switch to an alternative nick, then bind init-server or something then go ahead and release that nick after you have connected to the server, not while you are connecting to it or when it is giving you that error message.

You cannot release the nick enforcer when it gives you that error message, and that is really crappy I say, the coders should atleast let people release it when they get the error while connecting.

The thing is that you are not fully connected to the client server, hence you cannot message nickserv to release your nick while you get that message. Untill you are fully connected then only you can.

Statistics: Posted by awyeah — Wed Sep 22, 2004 9:16 pm

Server says bot's nick is invalid

2004-09-22T11:04:29-04:00

ok, i am having the same problem,
what i need is the bind for
" Server says my nickname is invalid."

then i can work from there.

i made this and it worked once,
but now it is not working, the server
will not allow the bot to get on dalnet
to execute the script:

Code:

bind raw -|- 432 Nserv:need:releaseproc Nserv:need:release {from keyword text} {  global botnick iNickServ i_nick i_pass i_gost_timer i_timer  if {[string match -nocase "*$iNickServ*" "$text"]} {    if {[string match -nocase "*$i_nick*" "$text"]} {      putserv "PRIVMSG NickServ@services.dal.net :RELEASE $i_nick $i_pass"    }  }}

so, if i can get the bind for
" Server says my nickname is invalid."
i will write the code.

hmmm,

Statistics: Posted by Dedan — Wed Sep 22, 2004 11:04 am

Server says bot's nick is invalid

2004-09-13T22:47:11-04:00

Have fun with the coders. LOL

Allah Hafiz

Statistics: Posted by Alchera — Mon Sep 13, 2004 10:47 pm

Server says bot's nick is invalid

2004-09-13T21:39:51-04:00

Yeah this is really crap. I and a few other users are atleast trying to convince the coders to add a command to release the with nickserv maybe when it says that the nick is on enforcer.

This will atleast get bots to release their nicks via scripts and owners wouldn't have to do it manually, by their clients. My bot aswell didn't change to its altnick, instead it got the message for enforcer and got disconnected and it couldn't connect, I telnetted to it and found this out.

Statistics: Posted by awyeah — Mon Sep 13, 2004 9:39 pm