This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

identify more nick every 2 day

Requests for complete scripts or modifications/fixes for scripts you didn't write. Response not guaranteed, and no thread bumping!
Post Reply
User avatar
Kerbau
Voice
Posts: 12
Joined: Sat May 22, 2021 6:48 am
Location: mundok

identify more nick every 2 day

Post by Kerbau »

hello there

i had more nickname and i want it sidentify with every 2 day by changing 1 by 1 nick.

thanx
Cross the line, Don`t cross your friends.
User avatar
CrazyCat
Revered One
Posts: 1261
Joined: Sun Jan 13, 2002 8:00 pm
Location: France
Contact:

Re: identify more nick every 2 day

Post by CrazyCat »

Not sure to understand...
You want the eggdrop to change its nick each 2 days and identify, according to a nicklist you set, to keep them alive ?

If the network you're on has services (like anope), using group nick may help.
If you can't use this feature, we've to know how much nicks you need to keep alive, and if they have separate password or if they share the same one.
User avatar
Kerbau
Voice
Posts: 12
Joined: Sat May 22, 2021 6:48 am
Location: mundok

Re: identify more nick every 2 day

Post by Kerbau »

i can't use that feature,
i had 17 nick and have separate password.
Cross the line, Don`t cross your friends.
User avatar
CrazyCat
Revered One
Posts: 1261
Joined: Sun Jan 13, 2002 8:00 pm
Location: France
Contact:

Re: identify more nick every 2 day

Post by CrazyCat »

Here is the simplest script:
# Fill np with nicks and password
set np {
   "nick1" "pass1" \
   "nick2" "pass2" \
   ... \
   "nick17" "pass17"
}

set cnp 0

proc identnick {min hour day month wod} {
   putserv "NICK [lindex $::np $::cnp]"
   incr ::cnp
   putserv "PRIVMSG NickServ :identify [lindex $::np $::cnp]"
   #change previous command to the one used on your server
   if {$::cnp >= [llength $::np]} {
      set ::cnp 0
   } else {
      incr ::cnp
   }
   putserv "NICK $::botnick"
}
bind cron - 14 3 */2 * * identnick
It can be more complex whith controls that the nickserv ask for identification or validate it before sending the pass or regain the original botnick.
And notice that if you rehash the eggdrop (or restart it), it will restart the cycle from the first entry in $np.
Post Reply