I agree that the scoring system needs a total overhaul. I think for some just the definitions of the numbers is the problem, as they are quite vague.

As for the script, yeah it could be a bit neater, but this one was done on the fly, and I have never been one to really like using multistep variable definitions because it is easier to get lost that way.

Surely I could have done something like:

%a = $rand(0,9), %b = $str(%a,4), %c = $calc($int($asin($rand(1,%b))))
and so on and so on....

But, it does not take into account the fact that your computer computes $rand based on its current state. With the speed of calculations that it can do, $rand is not truly random.

(7+4+5+5+7)/5=5.6

Simple random Number

This one: if ($version <= 6.16) should be changed to if ($version < 6.16) otherwise, everyone will get both messages. Also, you need to halt the script in the instance of under 6.16.

Try to condense it all down to a singular on 1:text:*:#: event. Like

on 1:Text:*:<specific channel>: {
if ($1- <operator> <word> ) { <cmds> }
else if ($1- <operator> <word>) { <cmds> }

and so on. This will prevent locking up mIRC, because in the way that you have it set-up, it has to go through all the on:Text events one by one.

Basically you determine the length of a password that you want, from 4-25 characters, and it randomly outputs one for you to use for whatever.

Just for comparison sake, there are other IRCOp snippets:

http://www.hawkee.com/snippet.php?snippet_id=1097

This is quite a dangerous script without protections built in. A level system could be overcome fairly easily. I would add a check system that only allows certain areas of a specific folder for increased safety.

Yeah, what Corne said.

Forgot it was for a bot when I did the on Text and such. This is what happens when you are doing chaos math and replying here :)

It is already set to kick voices and normals. I excluded ops and halfops from being kicked.

For a bot:

on @*:TEXT:!idler*:?: {
.check.idle $1
}

Just message the bot with the room name and if it has ops, it will perform the check.

!idler #roomname

RusselB:

http://scriptsdb.org/files.php?type=theme

http://www.mircscripts.org/mts.php

Really nice code.

Just curious, have you ever tried using MTS themes? They give you the same freedom for this code as a dialog, but they are much easier to work with.

Idle kicker

Ooops, meant .mode # -o $$1

1. Why op someone then deop them right away?
2. With 3 commands going off at once, there is the potential to be flooded off of the server.
3. Why not just do:

Revenge: {
.mode # $$1
.kick # $$1 Revenge is Sweet
}

I would add on:kick and on:ban to it. Otherwise, looks pretty good.

You forgot to define this variable:

if (%autoflooded >= 2)

*Updated*

Nothing special on the update, just cleaned up some of the code. Forgot I posted this one :)~

Aren\'t all Ops and HalfOps automatically voiced?

Thanks Corne! I knew that something did not look right when I posted it, but I could not see it.

*Updated*

Away System

Auto Kill for Admin use

What I meant was, if you have 2 or more scripts that use the on:input statement, that is where the danger lies. Because 1 keystroke (input) is detected, mIRC will not know which on:input to use.

Ummm you just C&P\'d this one from DarkEngine DLL

Ugh, sorry that I missed this comment.

Ok, for everyone else that views this: different servers display this message in their own unique way. You may have to play around with the $8 ($7, $10, $2). Basically you count along the message until you find the $nick.

You should probably close the on:text event with a group (#awaylog), otherwise it will highlight every mention of your nick.

Be sure to note that you can only have 1 on:Input script. More than 1 at best will confuse your mirc, at worst, will crash. So if you are using more than 1, you will need to string them all together, which in itself is a bit delicate.

on !1:JOIN:#:

If you just use on @!1:JOIN:#: , you can eliminate the need to check if you have ops.

Actually, changing the version is a bit more complicated than that. Pretty much, you have to halt all ctcp processes are redefine them.

Fairly likely to get you booted for flooding...