Language Enforcer [1.0.3.0] (Apr 11.)

[ImportBot]

Originally Posted by dyn*:

 

Just wonderful!

 

I had been searching for something just like this and it looks like it will really help keep the obvious idiots at bay... Thanks Packman & SDS! Going to go ahead and add them now to Language Enforcer, sit back, and revel each time some kid tries to get around the list.

 

Our servers are in the United States and it seems that these two derogatory words are the most widely used. Some will just constantly spam them over and over again. Being able to quickly identify the immature individuals and then remove them if they continue on will be extremely beneficial. I'm willing to bet our case is not unique, perhaps linking to post #90 in the OP would also help new installs with a quick setup?

 

Did look in the OP and saw mention of a donate button being added. Hopefully you decide to do that.

 

Thanks again!!

[ImportBot]

Originally Posted by PacmanTRT*:

 

The current version of the Enforcer actually does contain a donate button, but I didn't want it to look blatant. So I placed it on the very bottom of the plugin description after the "Special Thanks" section.

This button exists since the 14th July and does not have its own Version number.

 

Now off to the original post to edit in some useful stuff! :-D

[ImportBot]

Originally Posted by dyn*:

 

Ah - Thought I saw one previously just couldn't find it when I went back to look.

 

On this laptop Internet Explorer is set to connect through a VPN. Procon must be taking the connection details from IE which is currently a non-connected IP address that points to my VPN. Thus no donate button is being downloaded and displayed.

 

Plugin developers like you enable us common folk to run better servers with less time spent dealing on problem users and server issues. When the money man comes online I will see if he's able to send over a donation via that link. Thanks again.

[ImportBot]

Originally Posted by IAF-SDS*:

 

Pacman (and dyn),

 

The regex in post #90 above isn't the latest version.

 

This is the latest version 8d regex:

 

Code:

[b]### v.8d REGEX ###
### "Nigger" written with spaces ###[/b]
\b((n)|([il1]\\[il1!]))+(\W*[1ilj!])+(\W*[gq&])+(\W*[e3])*(\W*r)+\b(_<!niger)# nigger
(\|\\\|)+(\W*[1ilj!])*(\W*[gq&])+(\W*[e3])*(\W*r)+\b# |\|igger
\b((n)|([il1]\\[il1!]))+(\W*[1ilj!])+(\W*[gq&])+(\W*[a4yi])*\b# nigga / niggy
(\|\\\|)+(\W*[1ilj!])+(\W*[gq&])+(\W*[a4yi])*\b# |\|igga
\b((n)|([il1]\\[il1!]))+(\W*[1ilj!])+(\W*[gq&])+(\W*[li1!])+(\W*[3e])*(\W*[dt])+\b# Niglet
(\|\\\|)+(\W*[1ilj!])+(\W*[gq&])+(\W*[li1!])+(\W*[3e])*(\W*[dt])+\b# |\|iglet
\b((n)|([il1]\\[il1!]))+(\W*[e3])+(\W*[gq&])+(\W*r)+(\W*[o0qc])+(\W*[1ilj])*(\W*[dt])*\b# negro
(\|\\\|)+(\W*[e3])*(\W*[gq&])+(\W*r)+(\W*[o0qc])+(\W*[1ilj!])*(\W*[dt])*\b# |\|egro
\b((n)|([il1]\\[il1!]))+(\W*[e3])+(\W*[gq&])+(\W*[e3])*(\W*r)+\b# neger
(\|\\\|)+(\W*[e3])*(\W*[gq&])+(\W*[e3])*(\W*r)+\b# |\|eger
\b((n)|([il1]\\[il1!]))+(\W*[e3])+(\W*[1ilj!])+(\W*[gq&])+(\W*[a4])+r+\b# neigar
(\|\\\|)+(\W*[e3])+(\W*[1ilj!])+(\W*[gq&])+(\W*[a4])+r+\b# |\|eigar

[b]### "Nigger" contained in a word ###[/b]
((n)|([il1!\|]\\[il1!\|])|(\|\\\|))+[1ilj!]*[gq&]{2,}[e3]*r(_<!pingger)# nigger
((n)|([il1!\|]\\[il1!\|])|(\|\\\|))+[1ilj!]+[gq&]{2,}[ayi]# nigga
((n)|([il1!\|]\\[il1!\|])|(\|\\\|))+[1ilj!]+[gq&]+[li1!]+[e3]*[dt]# niglet
((n)|([il1!\|]\\[il1!\|])|(\|\\\|))+[e3]+[gq&]+r+[o0qc]+# negro

[b]### "Jigger" written with spaces ###[/b]
\bj+(\W*[1ilj])+(\W*[gq&])+(\W*[e3a4])*(\W*r)+((\W*+(\W*[ocq])+)*(\W*[sz])*\b# jigger / jiggaboo

[b]### "Jigger" contained in a word ###[/b]
(_!jig+(l|s|ery|ing))j+[1i]+[gq&]+[e3a4]*r*(b+[ocq]+)*[sz]*# jigger / jiggaboo

I've been using it for over a month with no false positives.

[ImportBot]

Originally Posted by PacmanTRT*:

 

Copied Regex for "fag" and variations from post #90:

Code:

f[a4]+[gq&]# contained in a word
\bf\W*([a4]\W*)+[gq&]\b# written with spaces
\bf[a4e3]*g+[a4o0ile3]*t(_<!fget)\b# variations like "fgt" or "fegit"

 

I'm glad to see you guys are happy with what I've done :-)

 

EDIT: modified last entry to ignore "fget" which can be used as an abbreviation for "forget"

[ImportBot]

Originally Posted by dyn*:

 

The current version of the Enforcer actually does contain a donate button, but I didn't want it to look blatant. So I placed it on the very bottom of the plugin description after the "Special Thanks" section.

We were not able to click the 'donate' button inside the plugin... had to view source and copy the information out of it. Hopefully you received the donation. To note we were able to click the 'donate' button inside UMM so it seems there is an issue with just that button? Can anyone else confirm that they can NOT click the donate button inside Language Enforcer?

 

Thanks again for your plugin!

[ImportBot]

Originally Posted by PacmanTRT*:

 

I have indeed recieved your generous donation ^^

Thanks!

 

There will be a minor update somewhat soon.

None of the commands for the Enforcer work if you use uppercase letters.

This has become really annoying by now.

 

It doesn't seem like you people give Feedback very often, but I think of it as positive feedback.

There currently are 198 servers running my Enforcer. (according to this page this page)

That means there are a lot of people out there who are at least not unhappy with what I've done :-D

 

So I really hope I can put more time into development of the Enforcer soon.

[ImportBot]

Originally Posted by dyn*:

 

I have indeed recieved your generous donation ^^

It doesn't seem like you people give Feedback very often, but I think of it as positive feedback.

There currently are 198 servers running my Enforcer. (according to this page this page)

That means there are a lot of people out there who are at least not unhappy with what I've done :-D

Usually you will not see much feedback unless something is broken or unless a feature is requested (as is my case). If it's working as it's advertised, do not expect a ton of responses. Now just wait until something in the code for BF4 changes and we have 198 server operators showing up here wondering why something doesn't work. heh.

 

As for the commands in game, I haven't even tested that with other admins (all of whom would NOT be on the procon list)... in game language enforcer commands are not used currently.

[ImportBot]

Originally Posted by PacmanTRT*:

 

As promised I have made a few bugfixes

 

1.0.1.0 --> 1.0.1.1

• Fixed Bug where measure overrides were not saved
• Fixed Bug to ignore character casing of commands.
• Made PayPal Donate button work properly

You can download it

[ImportBot]

Originally Posted by SmackDown*:

 

As promised I have made a few bugfixes

 

1.0.1.0 --> 1.0.1.1

• Fixed Bug where measure overrides were not saved
• Fixed Bug to ignore character casing of commands.
• Made PayPal Donate button work properly

You can download it

I'm not sure if I'm doing something wrong or not, but I believe this download link is wrong. When I click on this link and install the file on my layer and restart it, it still shows the old version of 1.0.1.0.

 

I think your link is still downloading the older version.

[ImportBot]

Originally Posted by PacmanTRT*:

 

My fault, sorry! :-/

It now works

[ImportBot]

Originally Posted by earls_towing*:

 

Hello, I currently use this on my server and it works great. Is there a way to change the method in which it bans someone? It currently uses the players EA GUID. I am trying to unban someone and they cannot find their EA GUID and in my banlist it doesn't show the players name. Is there a way to either ban from their PB GUID or add the player name to the banlist?

[ImportBot]

Originally Posted by PacmanTRT*:

 

You can find an EA GUID by entering his player name here: http://www.247fairplay.com/CheatDetector/

 

Using PB GUIDs doesn't seem to be as easy and I see no advantage there.

Introducing a Setting to disable GUID bans is by far easier for me. I will implement that in the next release.

I can send you instructions on how to disable it via code editing if you want.

 

You can also add %player% to the ban reason. This is how I configured it on my server.

More of these variables are listed in the plugin description (nearly at the end)

[ImportBot]

Originally Posted by earls_towing*:

 

Great, thank you very much. I will look to add the player name on the ban reason which should solve my problem.

[ImportBot]

Originally Posted by wishmaster2002uk*:

 

great plugin any idea why its detecting non bad words as bad and giving the warnings

I have checked bad word list and some of the words being detected as bad do not exist.

[ImportBot]

Originally Posted by PacmanTRT*:

 

the plugin shlould write down what it recognized.

There is a setting under "1 - General" name "Log to". This is where you can read what the enforcer does.

 

Might be the source of the problem:

Please note that the normal badwords are detected by a simple contains function.

This means you can't make "nob" a badword, because it will also recognize "nobody".

You would have to use the regex badwords for that instead.

(in this case "\bnob\b"; the \b indicates the beginning or end of a word for regex)

[ImportBot]

Originally Posted by dyn*:

 

Trying to figure out the best way to add a bunch of players who should have access to the !langp command, but are not actually admins as seen by procon? Would it be possible to add this functionality?

 

Right now these admin-like players are kicking and banning players instead of adding another 'point' to the offender's total. While this works to remove the problem user, I would really like to see less bans as usually the idiot spamming chat just needs a little encouragement to stop what they're doing.

 

If this is not possible to implement, what are the minimum admin settings we would need to setup for a player to be considered an 'admin' by your plugin? Like if we put them in the admin player list for procon, what are the minimum permissions required for !langp to work?

[ImportBot]

Originally Posted by fcmun*:

 

Hey, I have installed your plugin and I edited the RegexBadwords.txt and the Badwords.txt for my needs. Put some new words in it and removed some and saved both files.

But the plugin is still working with the data I got before editing. What do I have to do that the plugin refers to the edited files?

[ImportBot]

Originally Posted by PacmanTRT*:

 

@dyn: I am terribly sorry. I read the email about the new post in this thread and forgot it when I got home.

Admins are players who have kill permission (can use !kill command of ingame admin plugin). If you need to edit this: There is a "IsAdmin" function that can easily be modified.

 

@fcmun: You can copy the stuff to the settings in procon or you have to delete the according settings in the config files (look for a config folder on your FTP besides the plugin folder).

The 2 text files are meant to act as initial values or as failsafe values.

It also may try to load the text files on disable then enable plugin or procon server restart (I've implemented this too long ago to tell without looking).

[ImportBot]

Originally Posted by iraqiboy90*:

 

Since watchdogs actions isnt being picked up by adkats, im considering moving to this plugin, but the question is;

Will this plugin's action get picked up by Adkats? Otherwise, I'm comfortable with watchdogs

[ImportBot]

Originally Posted by PacmanTRT*:

 

Not yet.

But AdKats support is planned and is very likely implemented around Christmas.

 

EDIT:

I hope I don't annoy anyone, but we need some people to play on our new server.

http://battlelog.battlefield.com/bf4...-768cb54eff46/

 

Our regular players ignored the messages that we needed to move the server to another hoster and now noone joins it.

This also is the server where development versions of the Enforcer are tested :-D

[ImportBot]

Originally Posted by superman50*:

 

I would like to ask, I am a server administrator, I come from china. This plugin can be broadcast by Chinese? Is the admin say (Yell) in Chinese, not in English play.

[ImportBot]

Originally Posted by PacmanTRT*:

 

I'm sorry. The Battlefield RCON interface does not support non-ascii characters.

This means that Procon and therefore the Language Enforcer cannot send or recieve Chinese or Russian characters.

 

If you want this fixed (like many others aswell) you'll have to write a letter to DICE

[ImportBot]

Originally Posted by PacmanTRT*:

 

AdKats support is about to be released.

Sadly I haven't seen a possibility to set the Severity of an AdKats punish.

 

Also if you want to use the Enforcer's punishment hierarchy with AdKats you will have to wait until the next version of AdKats (greater than version 6.0.0.0) is released to enable TBan functionality.

 

I am currently testing a few things with the help of DarkZerO_AT*. Thanks for that!

But if you really need AdKats support right now: You can download the current Release Candidate here (Version number will be changed to 1.0.2.0 so you will get an update notification when the real release is done)

[ImportBot]

Originally Posted by ColColonCleaner*:

 

AdKats support is about to be released.

Sadly I haven't seen a possibility to set the Severity of an AdKats punish.

 

Also if you want to use the Enforcer's punishment hierarchy with AdKats you will have to wait until the next version of AdKats (greater than version 6.0.0.0) is released to enable TBan functionality.

 

I am currently testing a few things with the help of DarkZerO_AT*. Thanks for that!

But if you really need AdKats support right now: You can download the current Release Candidate here (Version number will be changed to 1.0.2.0 so you will get an update notification when the real release is done)

If you are using the AdKats punish then it has its own internal hierarchy that will advance for each punish.

[ImportBot]

Originally Posted by PacmanTRT*:

 

I sent you a PM explaining that I am used to modifying the punishment for specific words. This seems to be either not possible or possible with many limitations at the moment.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

I sent you a PM explaining that I am used to modifying the punishment for specific words. This seems to be either not possible or possible with many limitations at the moment.

Oh that's what you mean, not severity based on infraction count, severity based on incident type. Correct, that cannot be done at the moment through the AdKats punish system. It's currently either punish or not, nothing in between.

[ImportBot]

Originally Posted by PacmanTRT*:

 

New Version Released

 

1.0.1.1 --> 1.0.2.0

• AdKats support (Get admins from Adkats and AdKats punish or Ban/Kick/Kill via AdKats)
• Measure overrides can now decide not to use AdKats punish and use e.g. AdKats ban instead.
• New Measure: Custom, which executes a Command on the Procon Commandline. (Code stolen from ProconRulz )
• New Measure: Show Rules
• All in-game messages can now be more than one line.
• Made PayPal Donate button smaller and moved it to the top

Please note that AdKats TempBans are not working properly as of AdKats Version 6.0.0.0 and lower!

You can send me a PM for instructions on how to fix this.

[ImportBot]

Originally Posted by westyjoe*:

 

Do you think this will work with BFH in it's current version? Thanks

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Do you think this will work with BFH in it's current version? Thanks

It should, it bases its actions off of chat, which have not changed in a while. Provide feedback after you test it.