Oh yeah, Russel, if you think you can make a better version, go ahead and try. No one's stopping you if you think mine is crappy. I just don't feel like bothering updating it, it's not worth my time.
Hmm..let's see. Because I said I'd base the idea of my script off yours, not the code? Yeah, I thought so. My code looks much different from yours and it's more feature rich, although the game does work the same way. If it ain't broke, why fix it, y'know? But I really don't see why I should give you credit just because I made a script of the same kind.
Like I said, this is out of date, for the best version, mirc.net.
And now for some real comments that will actually help people improve the script instead of patronizing them:
First off...it makes more sense to make on on dialog event and then use $devent and $did. For example:
On *:Dialog:design:*:*:{
if ($devent == init) {
if ($did == 0 {
}
}
}
Also, I don't see the point of the echo in the on join event. The dialog also could use some alignment, and could be easier to use. The one cool point of this is the topic styles. One last thing, your readme assumes that everyone uses C:\Program Files\mirc.
Try these suggestions and it'll be a lot better. You could also add more options, such as botserv and chanserv (for some networks) and make the topics customizable. This has potential.
It's my choice whether I upload it or not. If you must know what bothers me:
# There is a 1 megabyte limit on script submissions. Please do not include any executables with your script.
# Only upload .zip files, nothing else will be accepted.
# Script Updates need to use a different file name from the past.
Now please, for the new version, you must go to mirc.net. No exceptions, I'm not uploading it here.
I can't update it because it's a .rar archive, and I can't be assed to submit it here, especially when mirc.net has a fine version of it. That, and I don't like Hawkee's submission guidelines, no offense.
Is it just me or am I getting tired of hearing the reviewers say "This script isn't that good, but it's great for beginners". If a script sucks, it sucks, and we need to stop fluffing it up.
It's honestly really simple and not very good at what it does, the readme has NO contact info whatsoever, and does indeed show bias to Anope. the script is also broken up into two files, which is unnecessary, and they're text files. Not .mrc files.
You need to work on your spelling. Both Create and Type are wrong in places. Also, instead of using that long unset at the bottom, make all of your vars start with some prefix (ca., for example) and then have /unset %ca.*.
Why not make it so the user can set up a list of words he or she wants to block, instead of only blocking http, www, porn, and xxx. Besides, those are the best things in the world anyways. xD
It's very basic, and poorly coded. For example, you have && ($2 != $me) in On Text events. This makes no sense, because on text CANNOT BE TRIGGERED BY YOU. Also, there is NO multi-channel support: The bot will autovoice, or not autovoice in any channel. The same goes for autoop and other options. Lastly, there are also NO spaces in between identifiers and other text on some options, meaning the identifiers won't work.
Well, I like the idea. It even inspired me to make my game (not a ripoff from your though!!) and put it on my bot. One question though... what's the point of %meplays, really? The events are all On Text...you'd have to do an on input the exact same as the on text.
There should be some kind of limit on becoming the quote bot's owner, and the script could be cleaned up a bit both codewise and gramatically. However, it's still very good. :D
It's not bad. There should be some kind of limit on becoming the quote bot's owner, and the script could be cleaned up a bit both codewise and gramatically. However, it's still very good. :D