TheVille

I was just looking at the script for it, Spanish.
It isn't one of our plugins (ie Stevo, MMX or me)

It actually doesn't use any regex at all, just a StrContains. Go figure.

Can we modify the comparator string or does that require a recompile (is this c++)?

Last night someone asked about getting rid of slot/class tokens and I replied, "Can't you just smash them back into metal?" and was rejected by the swear filter, twice. It probably is also removing whitespace beforehand but I still don't see the offending word.

As Carpe mentioned earlier this year, "Push It" is the one that always drives me crazy!




.

The Spanish Inquisition wrote:Can we modify the comparator string or does that require a recompile (is this c++)?

Last night someone asked about getting rid of slot/class tokens and I replied, "Can't you just smash them back into metal?" and was rejected by the swear filter, twice. It probably is also removing whitespace beforehand but I still don't see the offending word.

Before you said it as "Can't you just smash it back into metal".

"Smash it" is your problem. Remove the Sma.

To be honest, swear filters are hard to do, regex or not.
If is difficult to determine whether someone is trying to bypass the filters or not.

The alternate might be to configure the plugin to * out the offending letters.

I've been meaning to ask this questions and this thread seems like an appropriate place to do so.

What is The Ville's stance on player's who have used name or description tags to add "colorful" language to their weapons and hats? For example a few weeks ago I was killed by someone who had renamed their soldier's Black Box to the: "Big Black C***" I doubt there is a swear filter out there to catch things like that!



.

Take a screenshot.
Report it to the Helpdesk.

Will do if I see something like that again in the future.




.

Dog wrote:To be honest, swear filters are hard to do, regex or not.
If is difficult to determine whether someone is trying to bypass the filters or not.

The alternate might be to configure the plugin to * out the offending letters.

In my experience, people who are trying to bypass swear filters are also being annoying in other regards warranting their removal.

Getting rid of the line of code that removes the whitespace before the string compare would be an improvement.

Dog wrote: The alternate might be to configure the plugin to * out the offending letters.

I like this idea

The most annoying one I run into a lot is "Please do not circumnavigate the swear filter"