mIRC Home    About    Download    Register    News    Help

Active Threads | Unanswered Past 24 hours | Past 48 hours | Past Week | Past Month | Past Year
Scripts & Popups Jump to new posts
Re: Check Stored Hosts on JOIN Simo Yesterday at 06:34 PM
thanks lire i will work with that and go from there.
3 375 Read More
Scripts & Popups Jump to new posts
Re: login conect script Iire Yesterday at 11:55 AM
Hello,
I'm noticing two things in your on NOTICE event, (and one minor thing in your /prelogin alias):

For the /prelogin alias, ($network) will be treated as plain text, rather than as the identifier $network surrounded by parentheses. In order to get the network name wrapped in parentheses, you will need to use a $+ concatenator (preferably the infix version) between each "(" and ")" parenthesis and the $network identifier:
( $+ $network $+ )

As for the on NOTICE event issues...

The first thing I see there is that you have an extra event parameter:
on *:NOTICE:*You are now identified*:*:NickServ:{

If you remove the part underlined in red, the event should trigger correctly and will no longer attempt to execute "/NickServ:{" as a command whenever anybody sends you a notice containing the text "You are now identified".

The second, which I'm assuming is a typo, is that you're checking if the value of $server is irc.misiochat.net, without a g...
if ($server == irc.misiochat.net) {
...rather than irc.gmisiochat.net, with a g.

Other than those two things, your script should work fine. However, you should also be aware that timers will evaluate identifiers and variables used in their command parameter twice: once when the /timer command itself is encountered and the timer is created, and then again when that timer is actually executed and runs the command you've passed to it.

Although this is unlikely to be an issue for your particular case, you should get into the habit of wrapping any identifiers or variables that you use within a timer's command parameter inside the $unsafe() identifier in order to prevent mIRC from attempting to evaluate them twice. (Imagine, for instance, what might happen if any of your passwords began with a $ or % character.)

So
.timerNickServ 1 3 msg NickServ IDENTIFY $ns_pass
...would become:
.timerNickServ 1 3 msg NickServ IDENTIFY $unsafe( $ns_pass )

And
.timerOper 1 1 OPER $oper_user $oper_pass
...would become:
.timerOper 1 1 OPER $unsafe( $oper_user $oper_pass )

Hope this helps. smile
1 144 Read More
Scripts & Popups Jump to new posts
Re: Ban on specified time RoCk 19/05/25 03:56 PM
Looks good to me.
1 200 Read More
Bug Reports Jump to new posts
Re: InspIRCd numeric 650 and "Services Message". Khaled 18/05/25 01:43 PM
Thanks for your bug report. As far as I can tell, this is behaving as expected.

mIRC added support for DALnet's numerics 650 and 651 in 2002.

When mIRC sees numeric 650, it assumes that one or more service messages will follow, so it plays a single notice event sound, displays the message "Services Message" in reverse (as requested by users at the time), and then displays a list of incoming services messages. When it receives numeric 651, this indicates the end of the group of related services messages.

That said, it looks like InspIRCd does not send numeric 651, which means that mIRC cannot tell when the services messages group has ended.

I am going to change the implementation of this to be less dependent on receiving numeric 651. This change should be in the next beta.
1 231 Read More
Scripts & Popups Jump to new posts
Re: Scheduled PM? Fernet 18/05/25 08:23 AM
Why don't You send a memo? Maybe is more easy
1 196 Read More