Comments

A similar loop is this:

GET and POST are only methods of requesting/sending data. Your regex is used when receiving it.

Jethro_, probably referring to the fact that you have to join each line together to form a pseudo-switch which is actually just a single command.

Won't that fail if you use any non-word character as your case criteria? (\w+)

That explains the old programming style.

Converting the text in the reverse order, you mean. Probably easier to understand that way.

/echo -q is an echo which doesn't show up if you put the . in front of your alias call.
/.msg hides the echo of your message.
If you created your own /noop alias which pointed to a silenced (e.g. /.noop2) alias then you could use echo -q but that'd be a pain anyway.
The other alternative, of course, is to just use a dud variable in its place.

You don't even need to "negotiate" to $10 - there is a valid discount for $10 still, which has been around for years. For the amount of time I've used it, it's worth the $10.
http://www.mirc.co.uk/register.php?coupon=MIRC-SWV0-MNKL

That's actually really easy up until the point where you decide how each website must be matched. All websites are arranged differently and sometimes the data comes through on more than one message, making that more difficult.
One solution which can't really fail is to always use a file and binvars, but that will make unnecessarily complicated scripts for most applications.

Jethro_ you /set %nicks once as well as /var %nicks twice. You should probably fix that up.

Using \w as your regex pattern by itself will match any word character after any word boundary. That means that "Jethro's" would become "Jethro'S"
For matching words alone you can use

If you still want to match words in other places like "[Hello]" then you need a more complex check if you want to do this accurately.

Oh, I realise that $highlight() seems to be the best solution, which is why I explicitly stated that I wasn't using my script in a regular fashion. People tend to get my names wrong and they aren't common words so I'm not concerned about whether it's in a word or not in my case.

I have never used $highlight() because I need more advanced matching for my highlight script, but yes, regex won't achieve what that can do and thinking that \b or \B is going to work is a common mistake leaving many people confused as to why their script won't match something they think it should.

Napa, did you check when someone uses a number? jaytea used $lf to get around that.

$me doesn't only contain letters, numbers and - meaning a \b will often not match correctly, eg "]," has no word boundary (neither character is a word character).

I don't know how $istokcs could have worked for you, Jethro_.
You're checking to see if ALL modes in a room match ONE mode.
+si does not match 's'.
$istokcs(s,si,32)

For clarification, Jethro_, since it retrieves the last token in a list with : between, if the server has no *:* bans it will still get the wildcard correctly. :)

I'm not actually sure what your response to me was supposed to mean, but there's no need to get defensive. It's just unused code.

Jethro_, he can't store it in the original sock mark because it doesn't exist until the sockread. He then executes the sockmark as a partial command, so I don't know where you expect him to use it again.

On another note, whether "$1." is enabled doesn't change a preference to "$1 $+ ." which is a format more often used by a real programming language without a syntax which must be guessed by the compiler.

The general hate for the goto command stems from the "goto is now bad programming" once structured programming techniques were developed, even though goto often makes faster, more logical code.

noop evaluates identifiers without performing a function.
The $findfile identifier returns a value you are not interested in, so you /noop it.
Using the method there you perform commands within it instead.

It won't match if they place a special ban like ~q: though, so for that you could use ($gettok($2,-1,58) iswm $ial($me))
I think a colon is 58, anyway. Not checking now.

Then you ask the question of why you don't just do that for all of them.
On another note, using | as the delimiter like that may end up with a user having a | with a space either side, which breaks the script. It's best to stick with something else they're not likely to use, such as ~ or @

Yeah, I've known him for quite a while.

I'd rather help anyone who happens to stumble across this snippet. At this rate of comments, that's highly likely.

Something tells me that people will give me a funny look if I type /slap Arch and it says
* Gummo giggle Arch

_Teen_ did say that, _Jethro, but in a confusing way. :P

I was just explaining the reason for the path not existing.

You fool! Assuming I only want to help him! ;)

_Teen_, it means they run it on a particular server and didn't think to change the message.

Anyway.. You might want to make this script work by IP address instead of nickname, as that's harder to change.
Another improvement could be the use of -eu switches on your /inc (see help file for info) because otherwise someone could be banned for spamming a few times over a week or months.

Be sure to change $chan here to #chan or people will modify your code instead of what they're supposed to change.