NoSwearing

Config

 <<code html>>
 NoSwearing

 Show user upon login the onLoginMessage, params: true | false
showMessageOnLogin: true

 Don't censor ops
ignoreOps: true

 Check players inventory for items crafted with custom names. Remove caught item, params: true | false
inventoryCheck: true

 Queue messages to catch multiline swears, params: true | false
 Catches:
 f
 u
 c
 k
messageQueing: true
 
Mute Offenders for a number of seconds after having been warned
This will cancel player chat messages and tell them that they are muted.
0 disables this feature.
MuteOffendersTime: 0

 The number of messages to keep in the queue, params: integer
queStack: 10

 Ban first timers who swear within x number of minutes of their first login, params: integer, -1 disables
firstTimers: -1

 Run additional check that removes vowels from offending words to find words like "fck", params: true | false
 This could potentially cause false-positives depending on your word list. 
 For example: 'shit' would check additionally check as 'sht', and under advanced mode 'push them' would match unless 
 'shit' is in the word list with word boundries '/bshit'
removeVowels: false

 Allow users to flag words that need to be reviewed. 
allowReport: false

 Login message to show to player, params: String
onLoginMessage: This server is monitored for swearing.

 Show warning count on player login, params: true | false
showWarnings: true

 What to show player on a warning, params: String
onWarning: is not an allowed word. This is a warning!

 censor false will hide player message, censor true will mask restricted word params: true | false
censor: true

 When censoring, replace resticted word with censorString, params: String
 %name% will replace it with the persons name.
censorString: 
- flowers

 Detect words like @$$, f**k
 This will enable the allow list
 /ns allow <word>
 Allow list makes certain symbol combinations skip validiation (Ex: 0_0)
symbols: true

 Set the action for advanced checks. params: warn | none
 If censor is set to true, string will be censored
symbolsAction: warn

 Catch words like 's h i t'.
advanced: true

 Do you want to kick users as a warning? params: true | false
kick: true

 Warning number to kick, params: integer
kickOnWarning: 2

 Instead of kicking, use a custom command
overrideKick: false
 Command to use. %name% adds player name to command.
customCommand: /jail %name% jail

 Total number of warnings before final action, params: integer
warnings: 3

 Block 3 or more repeating characters (Ex: ahhhhhh), params: true | false
censorRepeating: false

 Final action, params: kick | ban | custom
onFinalWarning: kick

 Final message to show player, params: String
onFinalMessage: You have reached the maximum number of warnings.

 Words that are monitored

 /b can be used at the beginning or end of words to denote the border of the word.
 This prevents words like ass being detected in 'lass' if it is set as /bass. The /b
 is a regular expression that sets the check to look for words that only start at 'a'

 /i is used to make it so that the word is not included in removeVowel option.
 Words like 'hoe' and 'tit' should include the /i since they would result in common letter combinations.

 The ! command works for words like hello. 'hell!o' will find any word with hell but not o 
 at the end. I am sure you could use /b in this case as well. Its up to you.

 The words are in a hashmap so that they can be counted. This is so that you can know the 
 most used words that are being blocked. 


 Users that are exempt from warnings
 Text is still censored the wame as any other user.
noWarn: []

<</code>>

You must login to post a comment. Don't have an account? Register to get one!

  • 2 comments
  • Avatar of xavierarmadillo xavierarmadillo May 08, 2013 at 15:01 UTC - 0 likes

    @JAG100: Go

    That was an isolated issue with signs and has been fixed.

  • Avatar of JAG100 JAG100 Apr 11, 2013 at 04:13 UTC - 0 likes

    Anything you can do to turn off the case sensitivity as it relates to how the plugin interprets words on signs? Currently you need to include all case sensitive variations to get effective blocking.

  • 2 comments

Facts

Date created
Jan 16, 2013
Last updated
May 13, 2013