Isn’t this an in-studio plugin???
This is forced because of a different reason, I thought?
Are you sure?
It updates game assets. I could add a datastore, but once again, that’s for later due to different systems that can be made for the future. Most likely cause for the script injection request I assume! Not everyone wants to have a datastore.

This method of filtering chat is most definitely against TOS since it’s just a table with words you cannot say.
No, you’re allowed to make a custom chat system, but not a custom chat filter. I said that poorly, I meant you cannot create a custom chat system AND a custom chat filter.
Well I’m not too sure what I’m supposed to do here. I’m pretty confused why you can’t use a custom chat system, and a custom filtering system. I cannot add the Roblox filter because plugin issues.
When you tested with Roblox’s filter, were you in team create? Just wondering. You could take inspiration from how Collaborative Notes filters things.
I tested in a private session. As far as I can remember, apparently I wasn’t allowed to speak with another person in that session, even though I was the only one. So I just gave up from there, and moved on.
Well, like I said, you could take a look at how Collaborative Notes filters things. When looking at it’s code, it appears to only filter messages in Team Create.
Well I’ll see what I can do. In the meantime, we’re stuck with this custom system. Thanks for the feedback!
You can filter it using a HTTP request to PurgoMalum which filters many swears out. If it errors, do not send the message.
The table thing shouldn’t be against the rules though…
Alright! I’ll be waiting around for that edit then!
I wont be able to add this as it defeats the purpose of a quick messaging system. It would take way too long to reply to something after someone else speaks. So I wont be able to really add an official Roblox filter right now. This is the best I can do for now.
Update v0.2.2 - RichText Support
That’s right! You can use RichText formatting now. Go ahead and bold every single message now, and give it a fancy font! You wont be able to scale messages however due to how the UI was designed to properly scale without text going off the screen.
Do you all like my extremely frequent updates? This poll will be used for absolutely nothing by the way. I’m just updating what I can every single day.
- Yes, I like extreme updates.
- No, you’re too fast.
0 voters
Update Bugfix v0.2.3 - Filtering System
The filtering system was filtering out words that didn’t need to be tagged out. If it contained a bad word somewhere in the message, that would get filtered out. That has been resolved, and the filter has been strengthened to detect even more bypass attempts.
Update v0.2.5 - Chat Tab Navigator Unread Indicators
When someone sends a message, and you’re one another tab, there will be a little dot on the left of the text on the navigator buttons above. Now you shouldn’t miss out on messages if your Team Chat: Revived plugin is open.
New Update Incoming!
I’m working on a pretty big update called “Custom Chat Tabs”. Take a look at the creation wizard! I’m almost done, it may be released tomorrow.
Can you quote/link the ToS section that highlights this? And does it mention “Studio” exactly? In-experience systems must use FilterService, but I don’t think ToS says anything about Plugins.
You’re correct, they don’t say anything specifically about plugins or studio. It could technically fall under bypassing the filter (this can be done with textlabels, so if it IS enforced it is a very stupid rule for this to be in studio.)
I’m just warning that I’ve seen it somewhere that you cannot replace Roblox’s chat filter with your own.
Unrelated rule, but I believe this still applies to plugins as it allows users to directly (and privately?) chat with eachother. (which again, stupid, cause textlabel)
Conspiracy territory, but I believe a huge part of the reason that team chat was removed was to prevent <13 users from using it. (again again, textlabel) Perhaps it wasn’t compatible with parental controls, or some other reason. It wouldn’t make any sense for them to remove it entirely just because it was bad.
That or it was just that bad and I’m overthinking it, but it would be in line with the changes they were making to prevent <13 users from chatting.
Why not add a detection for <13 users utilizing team chat? Maybe it’s something else conflicting that had led to its full on deletion and deprecation.