Jethro_, contrary to what you may think, my comment was quite self-explanatory. The code snippet would just be holding someone's hand through the coding process that obviously already knows a little bit about what they're doing. As for a constructive comment- it's better to explain one's thoughts/ideas out thoroughly, instead of using terms that don't appeal to the masses.
If you find the need to continue this senseless game of comment-tag, just send me a private message. Thanks
Jethro_, because if i simply said "Use dynamic variables" it would defeat the purpose of posting constructive comments, especially if not all users understand the concept. Thanks for the concern though. :)
I'd suggest looking into making the (%flood.#chan (and/or %flood.nick)) variable(s) server-specific, instead of just channel/user specific. This will prevent problems if, for example, you're on the channel #Help on two different servers or there's a user on each server with the same nick.
Pass
commented on a Snippet, Blacklist - Dec 15, 2010
Aside from the various other suggestions/comments, there's a missing bracket at the very end
Looking like a troll is the least of my concern (although, you should definitely read up on the definition of 'troll'), as I was pointing out incorrect information that users could, and most likely would have mistaken for legit knowledge.
RusselB, excuse the spam, and I enjoyed the snippet. Worked well.
Cheiron, you're missing the point. In actuality, hash tables are more efficient for older PCs, not newer ones because mIRC does NOT use a lot of RAM, no matter the size of the table. Stop with this 'hash tables require modern pcs' propaganda. You're spreading false information for others to believe.
Cheiron, that's ridiculous. Using hash tables does not require any significant amount of RAM. I've a little over 700mb and can run hundreds(/thousands, if you count broken loops while creating tables) together. If anything, INI files would require more up-to-date systems to run smoother due to the constant writing to the hard drive disk.
Actually, only the newer mIRC versions, with the updated script editor crash with wine. I've never really experienced problems with prior versions, only few minor irritating bugs (regarding the script editor).
Actually Scakk, the current order for $haddtok supports multiple words. The words are separated by commas, not spaces, so there's no need to change the order (it's as close as i could get to $addtok's syntax).
Yes, i left it out because i did not see the need for creating a table when the user would be trying to ADD data to a pre-existing table item (although, it would work). I feel as if it is personal preference, really.
Could use some minor tweaking to make it a bit more functional
Code
That will check to see if the user being kicked is chanserv, while i'm assuming you wanted it to check if the user kicking is chanserv. So, you'd probably want to change $nick to $knick. Also, add a space between the parentheses and brackets.
Not all servers/services have the aliases "/ns, /cs, and /ms" so you might want to use the full "/msg *serv <blah>"
And you might want to check you're (H)Op as well, as to prevent any error messages. The "{ halt }" at the end doesn't need the brackets, either.