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
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.
0 voters
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.
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.
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.
That’s my question, maybe it was using something legacy or something? Not like I know the engineering process.
It felt kinda random IMO but that reason was very in-line with recent changes. All of the other questions lead to more questions.
Do they want to replace it? (then why not finish the replacement/make it a beta before removal?)
Do they want more people to use Guilded? (why not list it as an alternative?)
Yeah no idea. It’s pretty odd that they’d do this so suddenly without any other proper alternatives. Hopefully we get something better soon and quickly. For now, I’m literally using my own plugin lol.
Upon further inspection, I seem to be right. Which is AGAIN, stupid, because TEXTLABELS…
This likely means the plugin is against some sort of rule if it does not have the proper filtering/parental controls stuff.
"Team Chat is being removed from Studio on January 30th, 2025
In keeping with our effort to drive safe chat on the platform, we’re removing support for Team Chat from Studio by January 30th, 2025, as it does not integrate with parental controls. We believe that creator team communication within Studio will be better served by the ability to annotate and add comments directly within the workspace. (intrusive + textlabels) We plan to enable annotation and comments early next year.
Thank you, and let us know if you have any more questions."
But why doesn’t it integrate with parental controls is my question? Why not just update it? Pretty confusing I must say. Left in the dark to sit and wait for “better” Roblox Studio features. Not sure if they will be good or not, but you know what Roblox does sometimes.
I don’t think TextChatService
nor PolicyService
APIs can be called from a Plugin, as Plugins don’t run at runtime. So this rule can’t really be applied to Plugins.
Team Chat was removed due to it not being able to be integrated by Parental Controls. This is the stupidest decision I’ve ever seen here because like you’ve said… TextLabel
s. It’s not that hard to write anything you want on the Screen lol.
Yeah! I don’t know how to even add a gosh darn proper Roblox filter implementation into this plugin just because Roblox still hasn’t decided to fix that. Not saying they haven’t tried, but I hope they are.
Parental Controls are managed through PolicyService in experiences. And you can’t call PolicyService from a Plugin.
I think the filter can stay as it is, don’t think Roblox is going to take action against a plugin for including a custom filtering system.
So you think my plugin’s most likely safe from moderation? I mean I did try with a custom table filter lol. Best I can do for now.
No, I do not, but I think moderation is the villain, I wasn’t trying to put down your plugin as against the rules, I was warning you and telling you of what you can do to try and not get moderated. This is already a better implementation than the previous team chat from what I’ve seen.
Eh, I’m not a moderator, but I’ve seen many Plugins published here in a position similar to yours that never got deleted. You can DM a moderator or an admin to be sure. Or just let it roll.
Yeah that’s why I’m scared about such a great plugin being taken down just because it doesn’t have a proper Roblox filter.
I’ll check with a moderator soon. Thanks for the extra information though!