If that\'s all you\'re using the .txt file for, it\'s useless. A simple variable would do the same thing.

on *:TEXT:*<Word-Or-Nick-Here>*:#: {
inc %word 1
}
on *:TEXT:.Counter:#: {
.msg $chan 11[<Word-Or-Nick-Here> Has Been Said: %word Times11]
}

\"Kick + Bans\" returns the same value as \"Bans\" even though it\'s possible to ban a user without kicking him too. You should change the \"Kick + Bans\" counter variable to %kb and remove both %b and %kc.

Rock, Paper, Scissors Game for Bot

Uptime

It\'s meant to be funny. But that aspect of it is often missed by critics like yourselves.

Lamer Script

...

The on TEXT event doesn\'t trigger for anything except !deop, !dehalfop, and !devoice. The rest of the protection is triggered by the OP,HALFOP,VIOCE/DEOP,DEHALFOP,DEVOICE events. Therefore, using only an on TEXT even would serve no purpose...

Rating..? Maybe? Please?

Yet another kicker using various \"fun\" attacks...

How many is it now?

Not too bad.

A couple pointers though.
1) You don\'t need the backslash \"/\" when the command is between the brackets.
2) You may want to change \"$active\" to \"$chan\" to ensure that it triggers on the correct channel.

And xtr... why don\'t you review the comment rules before posting anything again.

Seemed fairly easy to use and understand to me.

Nice job xDaeMon.

1) Every message said in a channel that is 20 characters or more is saved in quotes.#channel.txt. These messages are then randomly chosen and sent to the designated channel upon typing the command: !quote

2) I\'ll update it to using only one \"on TEXT\" event soon.

3) I\'m not sure how I could make the variables any cleaner than they are. heh.

Questions? Comments? Ratings..?

Quote System

comments?

Updated.

Now features a guessing game:
!cookie guess start - Starts game
!cookie guess stop - Stops game

The rest is explained in once the game starts.

Note: Repaste ENTIRE code into your remotes to ensure that it works.

Cookie Jar

on *:text:*:#: {
if ($strip($$1) == @ $+ new8) { .write 8.txt $2- }
if ($strip($$1) == @addk) { .write k.txt $2- }
if ($1 == @ $+ k) && ($nick isop $chan) { .kick $chan $2 $read(k.txt) }
if ($1 == @ $+ kb) && ($nick isop $chan) { .ban $chan $2 | .kick $chan $2 $read(k.txt) }
}

Haven\'t tested it but it looks like it would work fine.

Pointers:
-You don\'t need all the $+\'s in there. Pointless.
-May want to restrict the kick and kick/ban commands to certain users, like channel operators.

But all in all, not too bad.

In your \"Authors Notes\" you tell people to type !nt when in fact the command is @nt. Might want to edit that...

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

Odd how your script is very similar to the one above...

Also included a join statistic. You may want to repaste the whole script into your remotes for this to work.

Ignore the html tags... I thought the comments supported it too. lol

Updated again.

Upon typing <b>!chanstats</b>, if any of the variables are $null, it will set them with the appropriate information. This way, you only have to type <b>!reset chanstats</b> when you want to reset all of the info at once.

Actually, it resets each time you connect... heh.

Updated again. Feedback would be appreciated.

Removed some stuff... added some others.

Feedback anyone?