[Urbana]

Description

• Filters chat and player names based off regular expressions read from config file

Feature List

• Blocks chat messages that match regex and notifies admins via chat
• Logs all chat blocks to logs/cf.log file
• Blocks players from connecting if their name matches regex

ConVars

• cf_filter_chat - Filter chat messages? 1 - Yes, 0 - No. (Default: 1)
• cf_filter_name - Filter player names? 1 - Yes, 0 - No. (Default: 1)
• cf_notify_admins - Notify admins upon chat block? 1 - Yes, 0 - No. (Default: 1)

Change Log

12-31-2018

• Initial release

Installation

1. Download chat-filter.zip file
2. Move everything in the plugins folder to your own addons/sourcemod/plugins folder
3. Move everything in the configs folder inside your addons/sourcemod/configs folder
4. You're done!

Configuring Config Files

• In the expressions.cfg file, each regular expression should be on a new line
• In the whitelist.cfg file each whitelisted word should be on a new line (note: these are words and phrases, not regex expressions)

For Developers (Include file)

/**
 * Retrieves the client index of the warden
 * 
 * @param	source	string to macth regex patterns to
 * @param	buffer  optional buffer to store matched pattern in source
 * @param	maxlen	optional length of buffer 
 * @param	notify	if true, will notify admins and player of matched regex
 * @param	client  client to notify if notify is true
 * @return	True if source matched to existing regex patterns.
 */
native bool CF_CheckString(const char[] source, char[] buffer = "", int maxlen = 0, bool notify = false, int client = 0);

[vERKE]

Does this work with letters like: á, é, ű, ú, ő, ó, ü, ö, í?

[Urbana]

Originally Posted by vERKE Does this work with letters like: á, é, ű, ú, ő, ó, ü, ö, í?

You will need to include any characters you want to block inside the regex config file. At the moment it doesn't know of all of the different alternate characters you can replace unless you specify them. This is meant as more of a front line defense against stuff and admins are meant to catch people attempting to get around the filter in special ways.

[vERKE]

Originally Posted by Urbana You will need to include any characters you want to block inside the regex config file. At the moment it doesn't know of all of the different alternate characters you can replace unless you specify them. This is meant as more of a front line defense against stuff and admins are meant to catch people attempting to get around the filter in special ways.

It works with characters like that, I tested it, but I found one bug with the plugin. It doesn’t filter out the word if it has any upper case in it.

So if I write apple in the cfg file, it would filter out apple, but it wouldn’t filter out Apple or appLe. Can you fix this?

[Mitchell]

Retrieves the client index of the warden

hmm

[einsfuhrer]

Doesn't work for me, used to work but when i reintalled my server and added this plugin it doesn't work.

I type one of the words, it only gets removed, not sended. I'm using the .smx from this thread and don't warn or anything.

What to do?