Migrate to TextChatService: Removing Support for Legacy Chat and Custom Chat Systems

[vojtasuper2 (Bubu)]

That’s what I’m saying.
I hope Roblox will not remove games that will not use that new chat…

[0bBinary (Binary)]

The issue is that we are using it to capture the attention of the players.

A single chat message is not enough to do so, especially in a game that you need to focus on other parts rather than the chat. (In fact, chat would be the last thing you’d look at there).

[azuderp (Azulie)]

why do you have to kill off custom chat solutions? that is so unnecessary

[unix_system]

Yeah, you don’t have to use the TextChatService UI (the new BubbleChat / Text Input Bars) to display messages in TextChatService. You can use TextChannel.MessageReceived to display the messages however you’d like.

[LvieReal (Lvie)]

Please make a fix to text chat scroll bar, it cuts off text

VerticalScrollBarInset = Enum.ScrollBarInset.ScrollBar

[ItsNicoshi (Nicoshi)]

would be intentional but roblox decided to take another worst move at all stakes
but thing is, if it’s a modified version of legacy chat, it should be alright

[TheRealANDRO (ANDRO)]

The problem is, that the new system is restricting in certain ways that developers like me want to implement things in. Most importantly, when I open MicroProfiler with TextChatService, I’m met with a very large ExperienceChatMain process that reduces performance. I do not want that.

[0bBinary (Binary)]

What do you find more effective?

[PeZsmistic]

Pay mind to this note, they’re looking into that as a solution.

@Roblox

Roblox is committed to preserving these legacy experiences. For transparency, one avenue we are researching is the impact of having methods that custom chats rely on such as TextFilterResult:GetChatForUserAsync return an empty result. Most custom chats at this time are likely using either TextFilterResult:GetChatForUserAsync or Chat:FilterStringAsync and the validity of the use cases these APIs provided will have diminished after April 30th, 2025.

We aim to make additional changes that prevent the Legacy Chat System from functioning, keeping these experiences compliant with the new policy. We plan to do this in a way that protects both the experience and the experience owners. We will have another announcement in the near future with more details on what to expect.

[ImmortalRemnant (Remnant)]

@Roblox

• Announcements from “Admin Commands”

So, how would we get important information out to users who have their parental controls set?

[Reditect]

Very comprehensive, good work here. As I read, I had questions such as what Roblox is doing for old games. Each question I had was answered. I appreciate the actual transparency of why this is happening, in addition to the multiple ways Roblox is tackling this.

I also am not impacted by any changes here though. So, take my feedback lightly in comparison to others who depend on these systems.

[Ayletheris (DevAyleth)]

Blasphemous. Are we in the so far behind in the middle age as to force all developers to bend the knee to something so painfully underdelivering such as TextChatService?

It has its flaws which the many here have clearly enumerated and many more that have gone unfixed for months. Design-wise, in my opinion, is honestly incredibly bland. Hell, it’s not even feature-complete enough to compare with LegacyChatService, and that one is older!

To be forced to use this when the old chat has worked so well, all under the pretext of “Oh, but it’s for the kids! We’re doing this, think about the kids! Of course!”

How could I forget the kids. Do better.

[unix_system]

TextChatService is separate from the CoreGUI Experience Chat, like ExperienceChatMain.
I’ve personally had to fork ExperienceChatMain and fix the performance issues myself, so I know your pain - but it’s not either / or here.

[unix_system]

As I’ve said, you can use whatever user interface you want to display announcements; either of those options are possible with TextChatService.

[AskForHeaven (Heaven)]

TextChannels are a miserable system to use and it seems unbelievably silly to keep track of a channel for every possible pair of users just to use my custom chat system. Just give me a function that tells me whether Player1 and Player2 can chat with each other and stop making me run in circles trying to comply with some policy you’re vaguely threatening to take down my games for.

[FriendlyBiscuit (Eric)]

You guys absolutely need to fix the frame time and network performance issues of the current chat implementation before you force this change onto developers. Anything less is objectively a downgrade - full stop.

Looking forward to the improvements you mentioned are in the works.

EDIT: I am aware that ExperienceChatMain ~= TextChatService. I still think it applies however as it is the default core UI implementation that is forced onto all experiences that use TextChatService. One could also argue that it seems silly to force these changes without fixing the related components first.

[vojtasuper2 (Bubu)]

i think when the moderators will find out they may terminate the game

[StEel_AtOmic (Steel)]

THIS IS ACTUALLY PEAK THANK YOU LORD ROBLOXIANS RAHHHHHH

[uglyburger0]

@Roblox

until April 30th, 2025, when you must migrate to TextChatService.

Please change the wording of this! A lot of developers are going to interpret this as “NO CUSTOM UI, YOU MUST USE OUR NEW SERVICE.”

@Roblox

Roblox’s policy is that all messages are sent and delivered through TextChatService’s TextChannels. Developers have the option and freedom to render those messages as long as they comply with our Community Standards.

Genuinely was getting worked up before I read this part of the post.
My only concerns ahead are gonna have to be just games that aren’t being maintained, and TextChatService’s performance concerns. Cool.

[TheRealANDRO (ANDRO)]

Doesn’t really matter since TextChatService brings ExperienceChatMain into function.