How is this is a W update. They’re literally removing something thousands rely on. There’s no major adds or new features it’s literally bad news.
1 Like
How is this peak, did you not read because now you’re just celebrating over bad news.
1 Like
The migration is not required immediately so people have time to update. Yes they are removing legacy chat but the new system is in its place. I’ve read the many issues with TextChatService and I am sure it may be prioritized since it is becoming the new standard. You can still customize the rendering of chats to your liking you must now just use the new APIs. This is better for the future of Roblox in terms of safety.
1 Like
I have several questions, One with reason many agree with
-
Can Legacy games be migrated to new chat instead of prompting moderation to users over old games? This seems destructive
-
Will there be an alternative barebones mode without all the extra options and just only the game chat?
-
Will the bugs regarding the slow performance of the new chat be fixed?
-
Will there ever be any UI-UX Customizations to fit the theme of the game?
-
Will we please EVER be able to move around the HUD for customization reasons?
-
Will the current chat system be overall better than the original Legacy chat, If not then your ignoring why 90% of the community uses legacy chat
-
Will most Legacy chat features be migrated to current chat?
i did not read the full forum, thank you !!!
Great, yet another “update” which erases history from Roblox. That’s exactly what we needed. First compatibility and now this??
this is the worst update made in 2024 ever
many custom chats will break, games gonna get deleted including KAT, etc which wasn’t being updated.
PLEASE roblox, if you’re going to release a single API feature, don’t remove legacy chat system, just update it, even if it’s legacy and deprecated.
2 Likes
please hope this didn’t end up like the 2023 marketplace items in experiences policy update
as for moderating experiences that didn’t follow the new policies, please have a better solution stated by people in this thread, I don’t want my accounts to be banned, or worse, terminated
2 Likes
Call me a idiot or something but I 100% think you misread this announcement, games that are still using the legacy chat will be forced to migrate to use the new chat system and NOT GETTING THEIR ENTIRE GAME DELETED.
Obviously old games will be broken but at the same time, the new chat system is honestly way better in my opinion.
Personally for the games I work on I don’t mind this since we had to migrate over to TextChatService to better accommodate our international audience anyway, as previously the roleplays were always kept in English, and adopting this system has since opened up possibilities for some of our non native English speaking players to interact with other players in our games (though not all, we’re still eagerly awaiting more languages to be supported).
I will say that we were massive fans of the level of customization Legacy Chat had to offer, so much so that when I was looking into whether or not to migrate over to TextChatService, I definitely would have elected to avoid doing so had chat translations been implemented into the Legacy Chat system. Since we decided to migrate, the migration of older systems over to TextChatService wasn’t as easy as we’d hoped. Its customization options didn’t/still don’t rival the Legacy Chat, it’s still quite buggy (though I cannot comment on performance, I haven’t looked into that), and at the time we moved over there was very little good documentation from Roblox to the point we were endlessly hunting around for clues as to how to customize the new system in a way that felt right for our games.
I think as long as long as Roblox have taken the above points into careful consideration and (or have already) take action upon each of them before this deadline then the forced migration should go a lot smoother for other developers than it went for us.
I will admit I was quite angry when first reading this — but I now believe this is just a case of the team at Roblox having very poor communication skills.
In practice, what they actually meant to say, and please correct me if I’m wrong here @Photoguy82, is that “all chat must be delivered through the TextChatService API by April 30th”, such as TextChannels.
5 Likes
Most experiences today on Roblox that want to migrate to TextChatService will still use the classic Montserrat font and text sizes… Will experiences that have not been migrated and those that use the legacy version too use that font?
Because current experiences use Builder sans, and for consistency it should be considered to ensure the experiences the the new settings…
Wow serious problem here?
I don’t use the old tchat, I don’t use very specifics chat things but as I see, the community have more one Serious reason to make you cancel that update.
You are gonna broke a lot of game and moderate dev for not using the new tchat? Are you crazy? Imagine you have an open public place you don’t remember, and get moderated because it use the old tchat?
Stop right now, a RE-THINK this update.
This is like public sound V.2, serious mistake, breaking a lot of game!
3 Likes
Ridiculous as always, thanks roblox! No one needed this, great job
2 Likes
Love this! I definitely didn’t spend 8 months creating a custom chat system for it to end like this.
11 Likes
Good change, the old chat system sucks. For the people complaining: 99.9% of games with the old chat don’t have any custom functionality. It will just be migrated to the new UI and won’t break anything. I also HIGHLY DOUBT that they will “moderate” small games with no players for misusing the old API, it sounds like fear-mongering. It’s unlikely they’ll spend resources to police tiny, inactive games with minimal impact.
1 Like
maybe a bit much?
especially for inactive devs
but oh well
Beginning to force a migration to the new TextChatService when it currently isn’t on par with the legacy chat system in the first place is absurd. Others in this thread have provided a few examples of that.
I would hope these issues are fully resolved before the new TextChatService becomes mandatory.
Additionally, from the look of the timeline, it seems that even custom chat systems that comply with the new API will eventually be outlawed by April 30th, 2025 in favor of the new TextChatService for everyone. If this is correct, this is once again absurd. Why cannot people have their own custom, compliant chat systems?
(edited to fix typo)
4 Likes
It seems pretty explicit that workarounds like this aren’t allowed for any type of chat. Even though GetNonChatStringForBroadcastAsync provides the strictest level of filtering.
But that aside having the chat filter results be like this isn’t ideal, as I would assume using the lesser strict chat filter for things like comments in games would be ideal. Given comments might be like a player giving feedback to another player, ect where comments act as a form of chat.
I would see using the chat filter for comments being useful in games like ClipIt or RecIt.
2 Likes
So simply put, I dont see TextChatService being a end all be all for any user chat-like message filtering. I get why roblox wants this, but it ends up heavily restricting communication in experiences that want to do more with chat. Such as comments, cross-server chat for games that want to have huge servers.
As having 1000 player servers is cool and all as a plan, but itd be much cooler if I could have several 1000 player servers “linked” and have a cross-server proximity chat in a giant survival world for example.
1 Like