Forums Scripts & Popups whats causes this

hello

from time to time I view in my status the below:



what could cause this?

in my remote I have scripts such as:

Try this


It could be the order of the arguments for /ignore. This is untested.

Although it isn't stated anywhere that I can find, sometimes switches need or work best if used in a particular order.

Try using .ignore -pntidu10 $nick

as far as I've seen (tho this is not the official answer from Khaled - I dont think it says it in the help file either tho it's been ages since I've looked at it), the timed ignore switch MUST be last in the order otherwise it gets all funked up.

Although that would make sense just to be able to determine which parameter went with whichever value. Try it with /ban -ku10 and then /ban -u10k. Actually I will try it now and get back to you on the results.


EDIT: There is no difference between /ban -ku10 and /ban -u10k

Tested and proven.

While your test works with /ban, did you try it with /ignore, considering that's the command in question here.

It has the same effect on /ban as on /ignore, in my case. I am using v6.2 not 6.12 so there might be a difference

weird...I tested it under 6.2 & 6.21 (presuming that you meant 6.21 rather than 6.12) and got the same results...it didn't work unless the u switch was last.
Oh well.

unfortunately, I now get this in my status:





any ideas??

The only time I can see that coming up, is if the person ($nick) quits/disconnects from the network. I can't think of a way to double check this, however.

If $nick doesn't evaluate to something, then mIRC will complain about insufficient parameters, not the error he got.

My guess is a custom /ignore alias that tries to msg or notice $1, as it doesn't take -switches into account.

OP: type //echo -a $isalias(ignore) and if it returns $true, find and remove the custom ignore alias.

yes, it returns $true

I have various "custom ignore aliases"

which should I change?

Personally, I'd change them all, so that you don't get this problem again. However, using /!ignore in place of /ignore should use mIRC's ignore command, rather than one of your aliases.

thanks

you mean to make my script look like:



??

I have no idea if this will solve your problem. Regardless, this is probably good advice...

The ignore should come BEOFRE you close the window. Also, instead of using just $nick in the /ignore line use $fulladdress.



See if that helps...

I don't use query windows personally. I don't remember how they behaive. Though I thought if you halted the event a window would not open.

This is true for the ON OPEN event, not the ON TEXT event.

Yeah k, that's right. Looking at the help file I see how I could have made the mistake confusing the two. The OPEN event appears to have been originally inteded for incoming query (private) messages. Hence it has a <matchtext> paramater within the event definition.