events condition based on number of channel users

events condition based on number of channel users

the default options for events should include one that can be chosen for "large" channels, also, definable by the mIRC user.

i.e.: you could automatically hide join/parts for big channels by default

this is precisely why we have a scripts editor in the client

Just an example to hide JOIN PART and MODE's for channels with atleast 100 users. Am sure you could look in the helpfile for more info

Code:

alias largechannel return 100
on ^*:JOIN:#:{ if ($Nick($chan,0) >= $largechannel) { halt } }
on ^*:PART:#:{ if ($nick($chan,0) >= $largechannel) { halt } }
on ^*:RAWMODE:#:{ if ($nick($chan,0) >= $largechannel) { halt } }

I think you'll need HALTDEF on those.

Originally Posted By: Riamus2

I think you'll need HALTDEF on those.

No, halt works.

I've seen halt and haltdef used interchangeably for custom events. They both seem to be acceptable.

Though according to the help file:

Quote:

If you only want to halt the default text without /halting the entire script, you can use the /haltdef command.

Both /halt and /haltdef stop the default output, while /halt also stops the script execution. /halt implies /haltdef.

Yeah. I've been in the habit of using HALTDEF to halt default text because most of the time, I have something else happening and HALT would not work. It's more of a personal preference, I guess. I'd rather use HALTDEF so that I don't forget and put a HALT where it shouldn't be. It's the same reason I use RETURN instead of HALT in places where either could be used. There are times when you can't interchange them. Of course, as long as you know when they can be interchanged, you can use either and you'll be fine. I just haven't used HALT to halt default text in awhile and forgot that they could be changed in this specific case.

normally I use HALTDEF and RETURN aswell, but that was a quick example I threw together out of laziness