Hey, I have a problem which I don't believe is that big if you know what you're doing lol. One simple question how can I make the bot identify itself everytime it gets connected to IRC ?
# The format is:
# server[:port[:password]]
#
# Both the port and password fields are optional; however, if you want to set a
# password you must also set a port. If a port isn't specified it will default to
# your default-port setting.
set servers {
network name{s}:port:password
}
@Callisto:
That would generally be for password-protected connections, not nickserv...
I guess there might be some nickserv-implementations that use the PASS irc command for authentication, although I'd find that non rfc1459-comliant...
Quite possibly but it seems to work on bahamut based IRCDs (dalnet etc) although I admit it doesnt always work after a netsplit if services also splits. Sorry to mislead anyone
On most networks running nickserv the serverpass is forwarded as nickserv password.
for handling netsplits you should consult the script archive, it holds a pretty amount of scripts dealing with nickserv. Some with more, some with less functionality and reliability.
I wonder why you send the password only when the nickserv comes online and not when you change the nick name, also I doubt the watch will do any good without beeing within the init-server proc... (unless you have a init-server bind which rehashs the bot )
De Kus wrote:I wonder why you send the password only when the nickserv comes online and not when you change the nick name, also I doubt the watch will do any good without beeing within the init-server proc... (unless you have a init-server bind which rehashs the bot )
Good grief!
Do you even know what 'watch' does?
Add [SOLVED] to the thread title if your issue has been. Search | FAQ | RTM