Profanity filter changes #665
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add CensoredMessage property to ChatMessage and update references
Censor "Admin" in player name Add extra bad words Add summaries to ProfanityFilter
|
Nightly build for this pull request:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new profanity filter will filter l33tspeak variations of words, repeating characters, and basic bypass attempts. For example, these are all considered profane:
It's a regex based filter system. Hoping the comments make it easy to follow. On my somewhat dated laptop it can censor 10,000 medium sized strings in 200ms, and checking if a string is offensive will be quicker than that.
Censoring usernames isn't included in this PR. That's a different beast and will need more time.
The word "Admin" is now only considered profane when choosing your username.