there\'s lots of ways to accomplish this, FLCL\'s methods are probably amongst the worst i\'ve seen (sorry, just seems like you\'ve copied techniques without understanding them at all :P), here\'s quite possibly the shortest method:
Nope. I fully understand this snippet. I guess it\'s just my habit to over complicate things with $regex. I am going to reduce the code a bit more right now. Hopefully it won\'t be as bad as it was before.
I\'ll probably go with something similar to $iif(2 // $1) as you pointed out jaytea.
I, because I am pretty lazy, use this to check users in my channel from the active browser. I use this in an on join event so it will tell me the current list of users in the channel It doesn\'t have to serve any particular use. I really don\'t understand the second half of your comment, but yeah. Whatever it serves the user for I guess.
Ah. Sorry about that. The properties are actually what the $scon properties are. Basically, properties of $scon $acon and /dcon can be any identifier, but that identifier has to be relative to the network. For example
$acon(network) would return the networks you are currently on.
$acon(server) returns each server you are on
$acon(away) would return any network that you are away on and display \'$true\'
$acon(awaymsg) if you were away, it would display the away message on the network that you are away on.
etc.
The same applies for /dcon (/dcon network for example)
Hope this helps.
This snippet, no offense to the author all though there will probably be some taken, isn\'t worth an 8.0. But it can deserve more if you make a few changes: One, why not set this to all chans? Or have specific channels added to the variable. This can be done through token identifiers. Two, you don\'t check if you are an op. You can receive an error. This can be done by either adding if ($me isop $chan) of an @ to the user levels in the on *:TEXT. Three, one thing you will hear is people saying remove the /\'s. The /\'s before commands aren\'t needed and tend to be removed. So I would remove them.
You could even take this snippet a bit further by adding a prohibited list or something of the sort. Just try to find a way to make this snippet unique.