TextChatService forced on

TextChatService was forced on our game, despite the Enum still being set to LegacyChat.

Attempting to publish the game or toggle the Enum has no effect. This is affecting all places under the game.

22 Likes

LegacyChatService is getting depracated and Roblox is trying to slowly make the Devs implement TextChatService to the games, they also mentioned that there will be auto-migrations in February 2025. I’m not sure if that was an auto-migration but you probably would want to switch to TextChatService already.

Announcement of removal:

Update Announcement:

It also may be caused by other stuff that I’m not aware of but this is the most likely answer in my opinion.

1 Like

They mentioned migrations for any places not running custom chats.

1 Like

Is it TextChatService while testing in Studio too?

yeah that’s kind of been indicated with that little popup you see every single time you open studio. Its been there for a few months now.

Except that popup stated that the migration would take place on April 30th, not March 24th.

2 Likes

7 Likes

Correct, however - they released it before the pre-planned date on the migration timeline. The roadmap details that we had until ~April (we use a lot of custom chat systems, which the popup explicitly mentioned would be migrated April 30th)

I noticed this happened when I entered Studio for my game that uses legacy chat too, despite pressing “Remind me Later”. It would be nice to know if this was intentional or not. It’s poor UX, as you’d think pressing “Remind me later” wouldn’t force any changes @be_nj