Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make banned words configurable #222

Open
sean-gilliam opened this issue Oct 21, 2023 · 1 comment
Open

Make banned words configurable #222

sean-gilliam opened this issue Oct 21, 2023 · 1 comment

Comments

@sean-gilliam
Copy link
Collaborator

The below function has a set of hard-coded banned words (slurs, sexual, reserved words, etc). These should be placed in either a database table or a config file for easier maintenance.

bool check_ooc(CHAR_DATA *ch, char *argument, char *type)

@rezalas
Copy link
Owner

rezalas commented Oct 21, 2023

Not only do we need to make it configurable, but the name isn't clear on the functionality. I don't know why it returns true, or why it returns false. If nothing is detected or something is detected it returns false, but if an immortal or NPC said something the return is true. We can pull the list from SQL on startup and probably do a better transformer using tokenization for identification rather than the current design, which may improve detections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants