Again, not quite useful. You could turn this one in a very useful snippet by dynamicaly creating a list of commands, based for example on a text file. You could read and parse through all loaded .mrc files and see what commands do people have access to, and where they are active. If you need any help with how to do this, use the forum\'s mirc scripting section and ask for help.
looks also matter. clean style of coding is prefered over the messy one. there are some problems with your snippet instead. have you ever tryed setting mode +A or +c? or any other mode you\'ve commented on? they will surley give you some trouble, as mirc will try to set all the modes after +. if you were looking for comments, drop them on a new line and prefix the whole text with \';\'.
another thing required would be a better description. only specifying \'just copy and past the code in ur script remotes\' is no good to anybody. you should post info about what the snippet does (for those who don\'t know MSL), for what network it was made and so on.
Basically this will transform seconds in human readable durations. The first parameter of the function represents the number of seconds to transform, while the second represents how detailed will the transformation be (in his examples, duration 6 returns years, months, weeks, days, minutes and seconds, while duration 4 returns only years, months, weeks and days).
the biggest value $max_periods should have is 7 (years, months, weeks, days, hours, minutes and seconds), but in some cases, the function will act as with $max_periods = 6 (when one of the time values is null).
I would vote this as a very useful snippet. good job
hah... nice try corax, but i don\'t think you could match Pariah when talking about mirc scripts.. he\'s been here way longer than you have and helped a lot of people meanwhile.
about the snippet now. it is utterly useless. as Pariah already pointed out, about all the info you echo to the active window is shown in the default whois, so you might as well make the whois show in the active window. regarding the brackets and groups problem, i don\'t know how it could work without properly closing brackets - ALWAY CLOSE AN OPEN BRACKET. you obviously have no clue on what groups are or do, so i suggest you catch up on this topic (/help groups).
another topic would be to mention what network you made this snippet for, as i can see that neither raw 308 nor 309 are common raws (as in i can\'t find them on networks like undernet or quakenet)
again this situation makes me think that a submission queue (like mirc.net\'s one) is a great solution to filter out bad and useless scripts/snippets/addons/etc.
don\'t use #channel, use either # or $chan. furthermore, you forgot to replace some channels (like #die or #LisanneChat).
why limit this to halfop ? check if the one who issued the command is at least halfop (that means including ops too).
using on 1:TEXT:!kick:* has some problems. for example, the trigger will set off if you recieve the text !kick either in prv or in a channel, regardless of it\'s possition or if there are any other chars appended to it. (this means it will set off for !kick, adsf!kickSDa and any other combinations with !kick inside -> this makes the use of $2 useless)
this snippet\'s poorly written.. you\'ve put \'#chatplaza\' where it should have been \'$chan\', and used a lot of on text events that are not that efficient.
for example, in the so-called \'anti-spamming part\', you check if \'www\' is the first part of a message, if the spammer starts with anything other than www (even a control char, such as bold, color etc), it won\'t set-off, hence rendering your \'anti-spam part\' useless. same thing for \'assault\'.
I myself would rather use level-based access to important commands
/help /auser
/help levels