ns identify Help

Silence · Post by **Silence** » Sat Sep 30, 2006 6:37 pm

Hi, I'm having some trouble getting this to work for the bot. I have tried several tcl scripts, none however were succesfull. I have also tried:

Code: Select all

bind evnt - init-server evnt:init_server

proc evnt:init_server {type} {
  global nick
  putquick "MODE $botnick +iR-ws"
  putquick "privmsg nickserv :identify Pass."
}

However, I'm not sure if I placed the code in the correct location... I assume this was to be placed in the config? I placed it just below set servers {}

Any assistance will be greatly appreciated

- Regards.

Alchera · Post by **Alchera** » Sat Sep 30, 2006 7:11 pm

You have placed it in the correct location and the bot will identify to NickServ; on connect only!

Your bot is probably ignoring NickServ because of the notices services sent on connect. The solution is to add the hostmask of services to your bot as a (global) friend.

I did the following (for DALnet):

Code: Select all

Enfield HANDLE           PASS NOTES FLAGS           LAST
Enfield DALnet           no      0 f              13:39 (#dalnet)
Enfield   HOSTS: *!*@dal.net

List the ignores '.ignores *' and remove the one for the network your bot is on.

Post by **nml375** » Sat Sep 30, 2006 7:40 pm

@Silence:
You've made the variable "nick" global, but use the variable "botnick" as if it was global..
Change "global nick" into "global botnick" and it should work just fine...

Alchera · Post by **Alchera** » Sat Sep 30, 2006 8:07 pm

I missed that bit.

You can also simply use $::botnick.

Code: Select all

bind evnt - init-server evnt:init_server

proc evnt:init_server {type} {
  putquick "MODE $::botnick +iR-ws"
  putquick "privmsg nickserv :identify Pass."
}

My suggestion (above) re ignored services still applies.

Silence · Post by **Silence** » Sat Sep 30, 2006 8:09 pm

Hi, Thank you both for responding to assistance me.

Change "global nick" into "global botnick" and it should work just fine.

For some reason, when I use botnick the bot does not connect to the server successfully. Would this mean the setup for the bot is incorrect?

List the ignores '.ignores *' and remove the one for the network your bot is on.

I understand what you mean, however there currently are not any networks ignored. Could I possibly run the ns identify at a select time? For example, I press ctrl+i or something (send a command) and the bot runs the ns identify command?

Thanks again!

Azeem · Post by **Azeem** » Sat Sep 30, 2006 8:59 pm

For some reason, when I use botnick the bot does not connect to the server successfully. Would this mean the setup for the bot is incorrect?

this cannot happen.. i guess global botnick have nothing to do with connection.

Post by **nml375** » Sun Oct 01, 2006 7:24 am

@Silence:
Well, it means something odd is going on..
init-server bindings should'nt trigger until after your bot successfully connected to the server, so the contents of init-server script really should'nt matter unless it contains something like: putserv "QUIT" (I'm assuming it does'nt

Also, where you put it really does'nt matter, with the exception that you must put the binding after you've loaded the server-module.

Do you get any error-messages during startup?

Alchera · Post by **Alchera** » Sun Oct 01, 2006 8:49 am

Silence: eggdrop logs a lot of stuff. On your shell start your bot with the -n option and watch what is happening; CTRL + C terminates.

Silence · Post by **Silence** » Sun Oct 01, 2006 8:23 pm

Ahh thank you very much. I now have figured out that it is connecting, but just as you said it places the services under ignore and then reconnects.

Thank you very much for your help