Bukkit

@TeamCobalt

I'm not making myself clear. I don't want an SB command that retrieves this information. I just want it written into the warnings file.

Here is an example:

Player 'MisterX' says "Your house is shitty" and the next day says "Your skin is bullshit." Since I have the string 'shit' in my config file, his chat text should be blocked, he should be zapped and warned by text, and lastly the warnings file should be updated to add MIsterX:

warns:
  MisterX: 2
    21-10-2012 09:11 "Your house is shitty"
    22-10-2012 13:52 "Your skin is bullshit"

That is kind of what I mean.

@joshwenke

Some of my users are on every day for hours and are quite chatty. I'm aware of how to search text in a document. What I was requesting was something to spare me from having to scan through gobs of chat text. Simply logging the offending text string in the warnings file would be very useful. At the very least, logging the exact date and time of the offending text would help in chat log searches.

@TeamCobalt

I'm sorry but I don't understand you. Ctrl-f? This is something I press or the swearing user presses? When I try both ctrl-f and the sign, nothing happens.

btw your update msg has a typo. It talks about a new version being 'avaible' when it should say 'available'.

If I get banned (I talk a different language and it recognises that language some stuff from it as swear words how long do I get banned)

@TeamCobalt

Thank you. For my next suggestion, could you write the offending line of text to the warnings file, perhaps beside the player name or stacked underneath if multiple entries? I have users claiming they didn't swear and I can't easily check without going through miles of chat logs.

@TeamCobalt

Awesome. I don't care which method is used as long as there are no false positives and I don't have to maintain a 10,000-word exception list ;)

Oh, don't forget to account for punctuation! A match for the whole word " ass " should trigger on " ass....", " ass," etc etc. Basically, strip all non [a-z|A-Z] characters.

Again, thanks for your efforts.

@TeamCobalt

Hi,

I'm saying that you might want to consider a modifier that determines whether the blocked string is a substring of the word or not. My comment from Oct 5 shows a workable system that handles whole words and substrings.

@TeamCobalt

I appreciate your efforts but I'm not sure a whitelist is the way to go. Now you would have to maintain a config with every exception, so the list for 'ass' would include, 'mass', 'crass', 'glass', 'pass', 'lass', 'bass', 'lassie', 'gassy' etc.