You miss the point.
I could have two similar wildcarded user groups, I only discovered this because I was writing a script that used user groups for someone else, and it didn't want to trigger, so I had to look at the addresses, at which point I realized that since two were for my address, only one of them would trigger.
ABC:one!two@*.four.com
DEF:*!*@*.four.com
*** Join: blah (seven@noobs.four.com)
on DEF:join:#:{}
will not trigger.
As I mentioned in my previous post, I already know I can use $ulist or hash tables, in case you missed it, I'll quote it:
Now, I know there is optional ways to do this, like using $ulist to check to see if there is a match in DEF, or use hash tables to hold the addresses, and then do whatever, but these aren't very optimal ways to do it.
In other words, it doesn't matter how I code the user groups, if someone uses my scripts (that make use of User Groups), if the person is using: on SOMETHING:join:#:{} it runs a risk of not triggering because of my user groups.
Again, I know ways around it, but this only applies for -me- the creator of the script. It doesn't apply to another person who uses user groups who wants to use my script as well.