This is a forbidden words plugin for verlihub.
Designed by Bourne from the KOLI hub.
Made pluggable by Verliba.

Description:
* does not allow user sending any of a list of forbidden words that match by the specified regular expression
* limits the upcase letters in each post
* limits char repetitions

Configuration:
in the SetupList:

insert into SetupList (file, var, val) value ("pi_forbid", "max_upcase_percent", 100);
* replace the 100 by whatever you need.

insert into SetupList (file, var, val) value ("pi_forbid", "max_repeat_char", 10);
* replate the 10 by what you want
* do the setting before loading the plugin, or else default or old values are used.

Extra tables:
"pi_forbid" - contains the list of forbidden words

Chat commands:
!addforbidden <regex_pattern> [<check_mask>] [<max_affected_user_class>] [<kick reason which can contain _BAN_1period to make ban as well>]
!delforbidden <regex_pattern>
!getforbidden

<max_affected_user_class> : 1 - normal, 2 - vip, 3 - cheef, 4 - operator, 5 - admin, 10 - master
<check_mask> : 0 - check nothing ; 1 - check main chat ; 2 - check PM; 3 - check both
<regex_pattern> : a regular expression compatible with perl or it may be a simple word (containing no special chars)
<kick reason> : you can specify a resaon for every forbidden word, also you can use the _BAN_ for to make ban

To get more info on regular expressions see http://www.perldoc.com/perl5.8.0/pod/perlre.html
Very good regex tutorial site: http://www.regular-expressions.info
I suggest you reading that, so you get the most possible out of this plugin.
Note: in the commands the <regex_pattern> is to be written without the slashes "/" as you may see them in the above link

Dependencies:
nothing special

Install Verlihub first:
go to verlihub project, make it, and "make install", Note, you can profit of the ./configure --prefix /some/folder
which tells you where should be verlihub installed.
After making verlihub you'll find a file called verlihub_config in it's folder (which is not installed now .. to verify)
you can copy it anywhere into the reach of PATH, so that typing verlihub_config would execute it..
When it's done, you can run ./configure of this script

Using plugins in verlihub:
verlihub has two mechanisms for the plugins
1, the .verlihub/plugins folder (which you may wanna create)
2, !plugin !pluout !plugreload !pluglist all commands

the plugin can be found (after running 'make' or 'gmake') in the src/.libs folder

* if you wanna load plugin automaticaly on startup of verlihub, put a file called (in this case) "libstats_pi.so" 
which is the plugin itself. verlihub searches for files called .verlihub/plugins/*.so and tries to load them
you can just make a symlink to the plugin from .verlihub/plugins/ directory

!pluglist all
and you will see it there

!plugin relative/path/filename
!plugout PluginName1.0
!plugreload PluginName1.0
