identify script

[zaida]

i am editing the config and doing everything okay
my bot name is
zaida
i am on dalnet
nickserv
but still not working

[demond]

a bot should not need to identify unless it needs ops; therefore, you don't need a real script at all:

Code: Select all

.chanset #chan need-op putserv "nickserv identify $nspass"; putserv "chanserv op #chan $botnick"

[zaida]

so what do i have to do,
my bot is aop on channels

thanks

[demond]

so what do i have to do,
my bot is aop on channels

thanks

you have to consider carefully each of the solutions you were given, and make YOUR choice

[ayie]

Try this:

Code: Select all

# Set this variable to the registered nick that you are going to use.
set nsnick ""

# Set this variable to the password of the registered nick you are using.
set nickpass ""

# Set this variable to the name of the nickserv bot on your network.
set nsname ""

# Set this variable to the command used to identify yourself with nickserv.
set identcomm ""


bind evnt - init-server my:procedure 

proc my:procedure {type} { 
 global nsnick nickpass nsname identcomm
  putserv "PRIVMSG $nsname :$identcomm $nsnick $nickpass"   
}
putlog "Perform loaded"
return "Perform loaded"

i use this scripts and working for my bot ....
i also i use this command to use it

Code: Select all

.chanset #chan need-op putserv "nickserv identify $nspass"; putserv "chanserv op #chan $botnick" 

the problem is .... my bot always identify to nickserv ...

Code: Select all

<MaXis> [08:12] CTCP PING: 1124262720 from MaXis 
<MaXis> [08:12] CTCP reply PING: 1124262720 from MaXis  to MaXis
<MaXis> [08:13] -NickServ - You are already identified.
<MaXis> [08:14] -NickServ You are already identified.
<MaXis> [08:14] CTCP PING: 1124262840 from MaXis 
<MaXis> [08:14] CTCP reply PING: 1124262840 from MaXis  to MaXis
<MaXis> [08:15] -NickServ You are already identified.
<MaXis> [08:16] !Log! AuTO ReSETING & IDeNTIFY
<MaXis> [08:16] -NickServ You are already identified.
<MaXis> [08:16] CTCP PING: 1124262960 from MaXis 
<MaXis> [08:16] CTCP reply PING: 1124262960 from MaXis to MaXis

how to make my bot identify once only .....

[demond]

by making sure it gets ops?

[awyeah]

I recommend not to use this:

Code: Select all

.chanset #chan need-op putserv "nickserv identify $nspass"; putserv "chanserv op #chan $botnick" 

Just set it as:

Code: Select all

.chanset #chan need-op { }

Because, my bot has gotten akilled alot of times for flooding services when it was mistakenly deoped. Also had gotten it's nick frozen for SAbuse later onwards, so I wouldn't recommend using any of those need-* functions, especially need-op and need-unban.

The only wise thing is to detect a nickserv notice, and then only identify once to it. After identification notice is received you can then go ahead and make the bot reop itself on all channels by using a 2-3 line simple procedure.

The script I gave above should work fine, just use that.

[Alchera]

a bot should not need to identify unless it needs ops;

On DALnet it does. Op or no Op

Try auto_ident.tcl (for DALnet) and see if that simplifies things i.e. takes into account splits/services going down and returning.

[demond]

my point was that there's no real need to register bot's nick, unless you plan to give it AOP, in which case it needs to identify on need-op only

[Alchera]

my point was that there's no real need to register bot's nick, unless you plan to give it AOP, in which case it needs to identify on need-op only

No one on DALnet doesn't register a nick for their bot or themselves. Most are actually opped in one channel or another though.

[demond]

my point was that there's no real need to register bot's nick, unless you plan to give it AOP, in which case it needs to identify on need-op only

No one on DALnet doesn't register a nick for their bot or themselves. Most are actually opped in one channel or another though.

you are wrong

I didn't register a nick for my bot, and registered an alternative nick for myself only to keep my channel from expiring (after my nick and my bot's nick got stolen on the malaysian server, mecra, tecra, or whatever its name was, probably with the participation of corrupt "staff", but that's another story)

anyway, registering a nick of an entity which is supposed to be 24/7 on IRC (i.e. bot) for the sake of registering itself is lame (hello? you are *always* on IRC already!)

[awyeah]

LOL @ poor demond. He always seems to get unlucky somewhere.

[demond]

au contraire, I was actually lucky my channel password was different from my nick password (or rather cautious), and I haven't identified with it on that corrupt server

[Alchera]

and registered an alternative nick for myself only to keep my channel from expiring (after my nick and my bot's nick got stolen on the malaysian server

It was mesra.* and stupidity (a majority of the time) usually results in nicks being stolen.

anyway, registering a nick of an entity which is supposed to be 24/7 on IRC (i.e. bot) for the sake of registering itself is lame (hello? you are *always* on IRC already!)

Users register their nicks. It does not matter one iota if they are online 24/7 or not or whether it's a bot or not. There's not one mIRC/XChat user that does not use an autoidentify script of one sort or another and there's not one eggdrop owner that doesn't want the same ability for their bot, especially if they have the advantage of services on their network.

[awyeah]

If you are talking about mesra.* sponsored by jaring.my, one of DALnet's oldest Server Administrators handles the ircd on that box, i.e. Raskah a canadian guy.

They all think they know everything anyone can compile an ircd, because ircd source codes are freely available on the web, edit the config.h and maybe give another recompile and edit ircd.conf in the end and load the process into the background. I mean people think there way smarter than others, as goes with the DALnet ircd/services coding team as well.

By the way IRCd's are the worst most vulnerable form of network security.