mIRC Homepage
Posted By: DJ_Sol Network in a prefix or the event. - 07/05/11 04:21 PM
I'm sure this has been brought up in the past but I haven't seen it.

It would be nice to be able to have a network halt in a prefix.

Code:
Instead of:
on !@*:join:#:{
if ($network != NETWORK) return
}


Code:
Something like:
on network.name:!@*:join:#:{ }


Means the event will only trigger if network.name matches $network or $server if that seems better/safer.

Thank you.
Posted By: FroggieDaFrog Re: Network in a prefix or the event. - 08/05/11 04:41 AM
To do this would require an update to the parser itself, considering the event markup itself....
Posted By: landonsandor Re: Network in a prefix or the event. - 12/05/11 05:43 PM
I think it's safer to have it as an IF comparison myself. I think changing the way the scripting engine goes could lead to a floodgate of requests to change it around. That's just my $.02 USD
Posted By: FroggieDaFrog Re: Network in a prefix or the event. - 13/05/11 09:39 PM
Not to mention, How would you account for user levels with it as such?

something like this?
Code:
on userlevel:network:TEXT:matchtext:target: { }
??

Now image exactly how MANY scripts that would break. ALL OF THEM that depend on an on text event.....
Posted By: Wims Re: Network in a prefix or the event. - 13/05/11 10:35 PM
His example shows where the user level is.
Actually, the undocumented me prefix use the syntax he wants:
Quote:
on me:*:text:matchtext:location:
so it's not a parser problem, that me could be a network value, the problem is that the network value is not reliable, it could easily return 'me' or even $null
I agree with landonsandor anyway, it would be too ugly
Posted By: landonsandor Re: Network in a prefix or the event. - 15/05/11 07:06 PM
you know I completely forgot about the ME level as I rarely use mirc anymore, tho I used to be one of the biggest supporters of that level
Posted By: DJ_Sol Re: Network in a prefix or the event. - 17/05/11 03:30 PM
Originally Posted By: Wims
His example shows where the user level is.
Actually, the undocumented me prefix use the syntax he wants:
Quote:
on me:*:text:matchtext:location:
so it's not a parser problem, that me could be a network value, the problem is that the network value is not reliable, it could easily return 'me' or even $null
I agree with landonsandor anyway, it would be too ugly


Well thats why I said $network or $server, whichever is better. I figured Khaled's team could determine that. It's up to the scripter to make sure the value matches what they want it to. All mIRC would do is return the $network or $server value.
© mIRC Discussion Forums