You could at least tell us that it's going to change our VERSION reply and ignore people for requesting a version...
And please don't use $decode like that. There's no reason...
Also there's no reason to have any of this in more than one file, and if you want to include a reame (which in this case was somewhat pointless anyway) you should upload it as an addon in a zip file.
Not bad, but I must say I don't really see the point. /helpop ?opercmds will tell you all the commands if you don't know them so ... I'm going to say 7 because even so it is well coded and people may find it useful. :)
on *:HELPOP:#:{ I think you mean on *:HELP:#:{ and also doesn't that refer to a status given to an IRCop on oper-up that flags him as able to receive /helpop notices? I know that's what a helpop is but maybe mIRC is talking about something else...
You also can't tell me you're an IRCop on a network with a userbase larger than 5 that's allowed to use this, or that you expect such an IRCop to use it
If anyone has any idea as to how the editboxes with the answers change from read-only to disabled when you click Evaluate I'd be glad to know as I have looked through the code a thousand times and can't figure out why
Sending the !Vending_Machine command several times in succession will flood you off the server. Also the /'s before each instance of "describe" are not neccesary.
Just a note, the G-rater warn notice thing, typing /identd on <ident> will not immediately change your identd (you have to reconnect for it to take effect), and also may not work on other IRC clients. The /chgident <ident> is a server command and therefore will work on all clients and it immediately changes their identd.
Yeah, it's not neccessary to start a timer for everyone that joins. Maybe have a $rand, or maybe make the timer name not nick-unique, such as /timerVoiceall, check if the timer is active, and if not start it. Just a few suggestions though, the script works fairly well.
And please don't use $decode like that. There's no reason...