You and many others are making this a bigger deal than it has to be. This change is good so that any chat system can now be standardized through one API. You are still allowed to customize and whatnot. I doubt the investors were begging for this change. This is more about keeping players safe considering the largest audience is children.
Will you make the new TextChatService support more options like Legacy Chat System did? Because the reason why I haven’t switched is because I prefer the older system with more flexible options.
If you’re talking about having ChannelTabs, then yes, they said they will add support for that in TextChatService next week. Additionally they will also add support for UI gradients next week.
Now I can use the skull emoji in every game 
i feel like this is a massive update… as many people said, you’re telling us to migrate to a new api that does not have everything that legacy chat. plus, on top of that TCS is completely different from how LCS handles stuff. i’ll wait until you guys finish the tabs and whatever and then fork the chat window to get me a result acceptable for my game theme
will this break my pre existing scripting?
Or you could just make the legacy chat service include these things you are listing, but nooo. Because all you think about is the new stuff and not the old stuff, no wonder why I barely do stuff on this site, You keep dropping these updates specifically to get rid of legacy features, when literally you could just improve said legacy features with whatever needs to be improved, I’d rather not have to waste countless hours fixing my own forks of things that use the legacy chatting system, Not to mention how many scripts this would actually break.
3 Likes
Actually, the investors may have been indeed begging for this change. How is it possible that such a simple and logical parental control feature is being implemented only NOW in such a aggressive and destructive manner? Roblox had all the time in the world to implement this LOOONG ago in much softer ways but instead choose to ram this change onto us without any prior warning.
Roblox was called numerous times a pedophile hellhole with next to no parental control systems yet did not budge, they only budged when a company designed to tank the stocks of other corporations magically revealed pretty much nothing new about them to the public (only technically new thing would have been roblox specifically lying and inflating their own numbers). Only difference being is that bigger parties actually noticed and saw the stuff going down and likely spooked the roblox higher ups.
If this is the actual real story, i don’t know but i also dont doubt that im pretty close to the real deal. No company would try to shot themselves in the foot like this unless the alternative was a million times worse.
Also, check roblox stock. It magically went up not too long after they made this announcement. It’s very hard for me to believe that these changes weren’t specifically the doings of some angry investors when their stock magically shoots up by nearly 10 usd practically overnight while also trying to ram this new change onto us at full speed.
1 Like
Does it though? It is less buggy and has more features. That doesn’t seem like something that “sucks”
Well I guess TextChatService:DisplayBubble() would do the job?
some exciting stuff here, yay!
Call me a idiot or something but I 100% think you misread my comment, I mentioned nothing about games being deleted. You can still be moderated just for not using a specific API.
Well, there was a day when they removed bevels and filtering disabled option. Now it’s time for legacy chat. I guess I have to take a vacation to fix all the scripts until the deadline so roblox doesn’t delete my games and terminate my account 
1 Like
You have until April 2025 to fully migrate.
This is grasping for straws, lol. The stock could have changed for any number of reasons; you just want it to be because of this.
Why not just move the textchatservice ui into the playergui so it is way easier for developers to customise it
As soon as you remove the ExperienceChatMain performance hog, I’ll switch.
Thanks, I was also concerned about issues that I experienced with it, which is why I made two of those bug reports.
Cool I hope this won’t break anything on a massive scale 
That’s not entirely my point. I know there is some time but what i meant is that this is pretty much a thing we HAVE to do it regardless, aka they are focing this on us. I should have worded that better initially to be honest.
What could have been any other reason though? Big companies don’t magically get a jump in stock out of nowhere or because of some sort of unknown magical reason. And they especially don’t see any jump in stocks right after they announce something designed to fight back against the countless times they have been called a pedophile safe haven or whatever else terms.
It’s really hard for me to believe the jump in stock could have been caused by anything other than this announcement (not this SPECIFIC announcement to us but some sort similar announcement meant for share holders and other kinds of higher up parties derived specifically from this, or maybe vice-versa).
2 Likes
Hi Creators,
We appreciate everyone’s feedback. We recognize this is a major change, and wanted to follow up with some clarifications and changes that we’ve made based on your feedback. We’ve updated the body of the original post to reflect these changes.
Why are we doing this?
-
We want to reiterate, that the primary reason for this change is to ensure that all chat messages between users respect our upcoming parental controls which give more control to parents on who their children can speak with in experience.
-
We anticipate that in the future, we will have to make additional changes to the platform to support different safety or legal requirements, and migrating everyone to TextChatService, helps us ensure your experiences always follow these requirements and save you time for future updates.
Clarifying our policy on moderating non-compliant experiences: We will prioritize auto-migrating first, disabling chat second, and, only as a last resort, restricting access to experiences.
-
In addition to this post, we plan to reach out via multiple channels to affected creators to ensure that everyone is aware of this change.
-
We will attempt to automatically migrate creators to TextChatService as much as possible and provide more details in a little post.
-
Auto-migration may break custom functionality so we recommend migrating on your own if possible.
-
If we cannot auto-migrate an experience, we will attempt to disable the chat functionality.
-
As a last resort, in the case of custom chat implementations that do not use either legacy chat system or TextChatService, we may need to restrict access to your experience to only you and notify you that you will need to manually remove your chat integration and integrate TextChatService to restore your experience.
We anticipate that this situation will be very rare but we wanted to give you a heads up that this is a potential outcome if you don’t take any action. -
We’ve heard your feedback about inactive developers, and we will do our best to try to ensure their experiences are automatically onboarded to the TextChatService
-
Note: Private or archived experiences are not subject to moderation under this policy and there is no requirement for you to update them
-
We do not plan to enforce any moderation action on creators unless we see evidence of creators intentionally trying to bypass our chat systems.
-
We’ve updated the DevForum post copy to clarify this point.
TextChatService allows for custom UI:
- Clarifying that you need to use the TextChatService APIs but are welcome to design your custom UI and not use the default CoreUI for TextChatService.
- To disable the default TextChatService UI, set ChatWindowConfiguration.Enabled and ChatInputBarConfiguration.Enabled to false
- Additionally, some of the most requested features (ChannelTabs and UIGradients) will be launched next week.
Clarifying what is or isn’t a chat:
-
We’ve heard your feedback on Admin messages and those will not be considered chat. We’ve updated the post accordingly.
- We will update our guidelines to differentiate one-time broadcasts like these from equal back-and-forth chat.
- We will be clarifying in great detail what is and is not considered chat on our creator hub documentation at a later date.
-
We’ve added a section further explaining CanUserChatAsync and CanUserDirectChatAsync
More resources coming:
- We are working on more documentation and tutorials to help answer your questions about migration and more use cases using TextChatService. We apologize for not having those available yet but are working on those now and your feedback helps us figure out what to prioritize.
26 Likes