Forums Feature Suggestions Server Identifiers & Pre-Connect Event

I'd like to see some identifiers and commands added that would set/return more data in the server and messages options, e.g., group, server, port, quit message, finger message, etc. Along with these would be a pre-connect event that would run a script before mIRC started connecting to the server. This would allow a connection script to see which server/network is being connected to and set nicknames, alternates, quit messages, passwords, and so on, based on the server or network.

Also, a few identifiers for the current status of the Notify window would be nice (on/off, visible/hidden). My connection script does a /whois on NickServ before sending the password so I turn off Notify to keep its automatic /whois from confusing the connection script, then turn on Notify after the script is finished. Unfortunately, if I distribute this script that's going to turn on Notify for people who normally don't use it.

Thanks for a great IRC client. I've been a dedicated user for over ten years.

Until such time as Khaled adds your pre-connect event (presuming that he does), you might be able to use the ON START event, which runs when mIRC is started, whether it's connected or not.

As to the rest, I'll reserve comment on them until I've had a chance to read them when I'm not half-a-sleep.

About the pre-connect event, check out ON LOGON in the help file.

This event might be what I was looking for. In fact, it may even obviate the need for the ON CONNECT event since ON CONNECT may or may not be triggered before Services requests my password. This guessing game has been complicating my scripts for far too long.

Thanks!

isnt LOGON after connect ?

depends how its used

This confused me for a bit until I played with it. If you use the ^ at the beginning of the event it will trigger before mIRC registers onto the server. If you leave the ^ out of the event it will trigger after mIRC registers onto the server. Both ON LOGON events trigger before the ON CONNECT event triggers.

If you use the /halt command in the ^ event you'll have to supply the server with your registration data like so:

on ^*:LOGON:*: {
pass ServerPassword
user $emailaddr *.* $server $fullname
nick $mnick
}

The password line is optional for servers that don't require a password. You can find more information here.