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.
24 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.
3 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)
1 Like
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
1 Like
Hello!
Sorry to hear you are having issues. Last year we shared with the community in forum posts and emails that experiences will be required to start a migration to our new TCS service in 2025. You can find information about this here: https://devforum.roblox.com/t/migrate-to-textchatservice-removing-support-for-legacy-chat-and-custom-chat-systems/3237100
If your in-experience chat is built using a modified version of legacy chat or a custom chat system not powered by TextChatService then you were required to integrate with CanUserDirectChatAsync API by January 30th, 2025. Legacy chat methods such as TextFilterResult:GetChatForUserAsync or Chat:FilterStringAsync won’t work any more, and are not in compliance with our updated policy.
What happens if I did not adopt one of the APIs by January 30, 2025?
If your experience falls into one of the categories above and you did not integrate the above API or migrate to TCS by January 30th, we will attempt to auto-migrate your experience to TextChatService API and any custom chat integrations you’ve created (for instance with TextFilterResult:GetChatForUserAsync or Chat:FilterStringAsync ) will no longer work, since it violates our Roblox Community Standards. Refer to the Experience Communication Guidelines 49 to understand best practices for implementing TextChatService.
If I implement this API will I still have to migrate to TextChatService by April 30, 2025?
Yes. We’re providing this API and a migration timeline to provide an interim solution for creators needing more time to migrate to TextChatService.
You can make your experience compliant by following the instructions found in our DevForum post below:
Thanks again for bringing this up and we hope this helps.
Hello! The pop up received in Studio for Legacy and/or custom chat systems doesn’t trigger any game changes. As mentioned above, auto-migration may occur in experiences that are not compliant with the necessary API now that the January 30, 2025 deadline has passed.
1 Like
First of all, thank you for taking the time to reply. Please bear in mind everything I’m about to state is not something I blame you for personally.
When the announcement was first made, we implemented the APIs it requested well before the due date. Everything in said announcement stated that we had until April 30th to complete the other migration.
As far as I’m concerned, that commitment was not honored. If for any reason we miss-implemented anything, or Roblox’s detection failed and flagged us anyways — no notification was given. Not only that, even after the fact, we’ve had no confirmation of whether we were force-migrated or if this is a bug.
We lost players. We lost revenue. Above all, my team lost sleep, since without hope of a Roblox reply, everyone stayed up porting the game (in a broken, glitchy, and rushed manner) to TextChatService. (Which is still full of issues we cannot resolve due to lack of Roblox controls).
Our feedback regarding the new TextChatService has not been replied to, from which I can only assume it has not been heard. Needless to say, none of the bugs or requests we’ve made have been fixed or implemented.
8 Likes
Hey, hate to bother, but I would like to just tag on that this automatic migration appears to have still occurred for games that implemented :CanUsersDirectChatAsync() if they had custom chat when the recent auto-migration rollout occurred this March even if :CanUsersDirectChatAsync() was added to the custom chat and other respective places. Is there any process we can go through to get the “No-opt” flag that be_nj mentioned removed from/reviewed on our game after we switch to TextChatService? I have tried going through support but they have not been helpful so far, and my game relies highly on :FilterStringAsync() for player-to-player message filters. At the time of the automigration rollout in my case we used deprecated ChatService API calls, but I have now switched it to TextService, if that makes a difference in automigration.