By DangerOfFate on Sep 02, 2008First (actual) mirc script....alt+r
on *:load:{
if (!%n) { set %n $$?="Nick"
if (!%p) { set %p $$?*="Password"
}
}
}
on *:connect:{
if ($nick == %n) {
.timer 1 2 msg nickserv identify %p
}
}
on *:nick:{
if (guest isin $1-) && ($newnick == $me) {
.timer 1 3 msg nickserv sidentify %n %p
}
}
Hmm Zmodem Had alot to throw out but i aggree with him
/me doesnt know what his rating is yet
Zmodem pm me that link that you said my charectar looked like
would ya
Thanks
Anyways.....
First off you wouldnt need
on *:nick:{
Because if you connected your nick would be the same as before and ill the script would have to do is Identify you
So This Would Work
on *:load:{
if (!%p) { set %p $$?*="Password"
}
}
}
on *:connect:{
if ($nick == %n) {
.timer 1 2 msg nickserv identify %p
}
if (Guest* isin $1-) && ($newnick == $me) {
.timer 1 3 ns sidentify %p
}
Correct Zmodem
First, let me tell you that this is a mess of a code structure, with numerous bracket errors that destroy the code from executing right from the start. You've also used $nick in the ON CONNECT event in order to figure out if your own nickname is %n. The correct identifier, and the most proper, is $me; however, since the connect event triggers the $nick identifier, for one reason or another, to default to $me in this case, I will overlook that small logic-error.
Second, this timer, for the ON CONNECT event, is hardly necessary. For one, if a user doesn't have the IdentD either port-forwarded or enabled, it will take more than some 2 seconds to rectify a connection establishment. Your best bet, in this case, would be to get rid of the ON CONNECT event altogether and go with a less reprehensible event, such as the RAW numeric pertaining to the MOTD. It is more reliable than a timer, but bear in mind, also, that not all servers have the MOTD, either. In any case, you can replace your ON CONNECT event with this:
raw 322:*:if ($nick == %n) { msg nickserv identify %p }
Voila, you are done! By the way, the raw numeric 322 pertains to the end of the /MOTD display, usually sent by most servers once a full connection has been established. This will allow you to forgo your timer.
Next up, I've no idea what to say about your ON LOAD event, nor your ON NICK event. Both are a bit sloppy and both have serious issues. Let's address all of this by cleaning up the code:
ON *:LOAD:{
if (!%n) { set %n $$?="Nick" }
if (!%p) { set %p $$?*="Password" }
}
raw 322:*:if ($nick == %n) { msg nickserv identify %p }
on *:nick:if (($newnick == $me) && ($me == %n)) { msg nickserv identify %n p }
Later on, you might consider adding the ON LOAD event as an alias, so the user can change the auto-id on the fly when they want. For instance, here is another variant of code:
ON *:LOAD:if (!%n) { new.autoid }
alias new.autoid {
set %n $$?="Nick"
set %p $$?*="Password"
}
raw 322:*:if ($nick == %n) { msg nickserv identify %p }
on *:nick:if (($newnick == $me) && ($me == %n)) { msg nickserv identify %n p }
You wouldn't need to check the (!%p) event, because if there is no %n then %p is useless. On top of all of this, there are more suggestions:
Try asking if a user is sure they want to overwrite their old user/pass entries.
Check and make sure valid data is entered when the new.autoid command is done.
Well, sorry to go ballistic on it all, but I hope this helps point you in a better direction. Good luck!
