Closed TehGimp closed 10 years ago
Though the actual error isn't printed, I'm going to imagine it's an index out of bounds as the indices are not checked inside the LINQ statement.
This is exactly as gimp suspected, adding ',crash' (or anything after the comma without a : mark) to the end of the filter will cause the server to fully crash in the WashMouthWithSoap method.
We probably should validate the filter and reset it to the default if it's mangled, with an appropriate warning displayed.
EDIT: Or ignore bad entries, but still give a warning.
Hmm strange that it doesn't invoke the try catch
I'm thinking it's a differed execution issue. Going to change the LINQ a bit.
Reported via email:
Most likely a malformed profanity filter setting that's responsible.