nickserv problem

[martpen69]

Ok im prolly gonna get ignore for this but hey. I have read loads of posts regarding identifying the bot with nickserv. I have tried tcl scripts and tried the code inside the eggdrop conf file itself. The bot starts fine but no matter what i do with tcl scripts or with the config The only way my bot will identify is by me dcc chat with the bot and typing .msg nickserv identify password. I wouldnt have posted this as normally I would have found the answer just be searching. This isnt a major issue as my bots uptime is good but when the channel list grows this will cause my a huge headache. I hope you guys can help me. Thanks in advance for not flameing me or whatever the correct term is. :)

[demond]

debug it

set console +rvd and see whats actually happening when your bot needs identifying with NS (given that you run some NS identify script)

+r logs server's raw output, +v logs your bot's raw output, +d logs pretty much anything involving events triggering binds

[martpen69]

sorry for being a noob but i dont understand i unloaded all the tcl scripts i was trying to use and just thought it would be an easy task to add something to the config file of the eggdrop. If you have the time could you explain please. Thanks

[demond]

load your NS identify script, and on the partyline type .console +rvd

then see what happens when the bot gets on IRC and/or needs ops from CS (that is, needs to identify with NS first)

[YooHoo]

this topic has been repeated like 10,000 times, and the answer is almost always the same, and no extra tcl is needed : set init-server

Code: Select all

# This is a Tcl script to be run immediately after 
# connecting to a server. 
bind evnt - init-server evnt:init_server 

proc evnt:init_server {type} { 
  global botnick 
  putserv "MODE $botnick +i-ws" 
  putserv "privmsg chanserv :identify #chan <pass>" 
  putserv "privmsg nickserv :identify <pass>" 
}

i believe the default conf file uses putquick commands, which seems sufficient for most, but not all, IRC servers. I suggest altering this command to putserv instead, so the eggdrop doesn't flood &/or throttle your networks chan services.
Hope this is helpful....

[De Kus]

there are many reasons to include a sensible nickserv script such as to prevent your bot from fighting the guest nick fight against nickserv after a netsplit.

[martpen69]

Now maybe im just thick or maybe my ircd has a problem. But i have read that answer and you are correct the same question is all over the forum and I have read most if not all. I would not have posted if i found the answer allready. I have tried what you put and restarted the bot and still the only way for the bot to identify to nickserv is to dcc chat and type .msg nickserv idetify pass. I also tried the the debug mode which I cannot get to work. Maybe the I had errors while compiling the bot I dont know I will check these things out. But I have tried everything I hae found both on and off this site/forum. But thanks anyway.

[Alchera]

Some Networks (for security of users) now require that the FULL address of the service be used to private message. In the case of DALnet (for instance) it's .msg nickserv@services.dal.net (via DCC) etc.

What YooHoo posted (above) will work on connection but not if services go down and return which is where a decent auto identify script would help; another little trick is to use NickServ's access lists for the bot which goes a long way to prevent the bot becoming a guest.

[demond]

much ado about nothing

all nick services I know of (DALnet's or otherwise) send a nick identify request via NOTICE, so simply set your bot's registered nick to require identify at all times and use the minimal, yet most efficient NS identify script:

Code: Select all

bind notc - * foo
proc foo {n u h t d} {
   if {$n == "NickServ" && [string match "*owned by someone else*" $t]} {
      putserv "nickserv :identify $::password"
   }
}

[YooHoo]

much ado about nothing

/me agrees