this is just a terrible idea that will break hundreds of experiences
unfortunately it seems like these changes are due to legal issues, o well
What about games from inactive users, will they be content deleted for good? Are you seriously ruining preservation of your classic games like this?
I hope that until April 2025, they’ll have fixed all the bugs related to the New Experience Chat that are not present in the old one, otherwise it’s going to be dramatic for a few games.
This is a really needed feature as a lot of games rely on that for easy communication between multiple teams. Pinewood Computer Core for example
There should also be a command to easily switch between the channel you are currently sending messages to just like the legacy chat did.
Hey, I understand why this update happens, but could you NOT moderate people for not switching over? Just ban the game and give a warning or something?? OR atleast send us emails with games whose chat could not be changed?
I understand this is a necessary change for roblox, however, it’s quite unfair if people get banned because they don’t switch. I have atleast 500 roblox places on my profile, some of which nobody even plays because they’re closed. It would be a very big pain for me to change the chat in all of these places, so please consider NOT giving bans for these games!
I beg you not ban people for not changing. A warning or inbox message with these games should be enough.
We’re going to be adding ChannelTabs to TextChatService next week
They are gonna moderate experiences that use Legacy Chat? What the heck Roblox?!
why ban every game the had the old chat system?
Will you guys fix bugs that were not present in the old chat system?
It is a really accurate description that should address the exact location of what may causes this issue.
Another thing that isn’t present in the old chat system, is to join a game and see previous chat messages.
Will you allow us to have more chat width ranges, & disable rounded corners to at least it HAVE the new chat look similar to the original one? The current chat design won’t fit every game.
I really hope the performance issues with the new chat will be solved before the old chat is entirely removed
What about games where the developer has quit the platform completely or has no access to their account with legacy games?
Not all LegacyChatService APIs have even been given TextChatService replacements yet. Please make sure that developers can actually migrate everything before LegacyChatService is removed!
Here’s an example I brought up over a year ago, I’m sure there are plenty more.
Just to clarify, we are not planning to moderate users unless we see users intentionally trying to create new chat experiences that don’t comply with our new guidelines. We only plan to take action on the experience itself.
I hate this change
The new chat lacks a lot of features compared to legacy, and I find it REALLY ugly and impractical. Lol.
edit: why cant we just have functions and events that allows us to make our own chats? a SendMessage function and a ReceiveMessage event… ugh
edit: i misread the post, this is actually a decent update LOOL
I welcome this change and I think it is in the best interest of Roblox to move away from the current “two-chat” system they have created by allowing people to choose between LegacyChatService and TextChatService. The old chat system’s code is really bad and it’s about time more experiences started adopting the new chat.
But what engineers often fail to acknowledge is that there’s a reason why people haven’t migrated to TextChatService. In fact, there are several:
- Objectively worse performance (backed up by several DevForum bug report posts)
- UI takes up more space and covers UI on the side that the previous chat box did not
- No way to allow users to customize the size of the window
- No channel bar to allow users to switch between text channels easily
- Although it has been announced in this post that this is being added soon, so this will soon no longer be a reason not to migrate
- RichText formatting issues
- RichText interference with other APIs such as
Player.Chatted
- No automated way to migrate things like chat tags from LegacyChatService to TextChatService
- Some widely-used legacy APIs are completely missing from TextChatService
Roblox needs to address these issues before expecting people to migrate, let alone forcing them to. These are issues developers have been talking about since the release of TextChatService in 2021, with several unresolved bug reports about most of the issues. It’s time to start prioritizing the things that are putting people off migration in the first place. I have no doubt that Roblox will do so over the next few months, and their commitment is promising.
One of the biggest concerns is how this can potentially break old games, especially those created by developers who have either left the platform or even passed away. If Roblox is going to force migration to TextChatService, how do they plan to rectify the issues that many games will face in scripts awaiting the ChatServiceRunner
? This module doesn’t exist with TextChatService and scripts will require manual edits to migrate away from it. Will these games just be left in the dust?
The majority of experiences using legacy chat are using the standard version of legacy chat and will have until April 30. 2025 to migrate to TextChatService. As mentioned in the post, we’re exploring ways to auto-migrate old inactive experiences but may not be able to do this for all experiences.
are games that are private still gonna be affected, by moderation or otherwise?
Oh, alright! Thanks for the clarification, I was worried I might get moderated for experiences that I haven’t been developing on for years. Thanks for letting me know