Space to advance. I remember that one time I was writing a description for one of my projects and it kept on setting off the bad word detector. Eventually I figured out what it might have been and it was just another every day word. Studio descriptions, too. One studio's description kept on being attacked by the bad word detector. Any time we made an edit, the red sign would appear at the top, and it was extremely annoying. This led to us having to rewrite the entire description, and to this day we still don't know what was setting of the false alarm.
Dear Scratch team, I am sorry to say this, but your "bad word detector" is annoying. We can never figure out what is setting it off, and it catches completely innocent writing while missing the actual cuss words. I believe that we'd be better off WITHOUT a bad word detector, and if one remains, it should at least be improved. If this is not possible, at least some sort of highlighting of what the issue is would be helpful, because the bad word detector rings an alarm even when there is no bad word, making it very annoying for us scratchers. Thank you for reading, and I hope the bad word detector will be fixed some time soon. Sincerely, CodeBit. In conclusion: the bad word detector is basically useless and very flawed, and it'd be great if it could be fixed.
