No. That applies to games using a custom chat that does not use TextChatService.
The standard implementation consists of RemoteEvents and TextService to filter out messages, that’s all.
But again, this message seems… poorly redacted.
Yeah, the threat of moderation action against games that aren’t migrated is what really confuses me
Wait, did no one talk about this?
Ah well, not like I care. Never used it.
1 Like
dont understand why people are angry about this, legacy chat has tons of security issues and it’s not like your game will be deleted if you don’t migrate 
1 Like
They literally threatened moderating games that still use legacy (or custom idk) chat by the deadline
2 Likes
Your experience will be moderated if you don’t migrate.
Sorry, Roblox can’t communicate
keyword bypass, nobody reads and checks for updates apparently
some of this stuff is legal matters, so it’s super important that these comply with laws and regulations which is ultimately why the old chat is being deleted
some people say that “roblox failed to communicate” meanwhile your answer is within the post; you just didn’t read
It seems as if this will still impact any new chat integrations which is still a valid concern to have.
And using any implementation of LEgacy Chat would be a bypass once they disable the older chat filtering APIs as they mention.
It is, but they could also just add new APIs for us developers to comply with those laws.
Chat Service ≠ UI used for chat, see this:
bypass means that you switch back to a custom chat without using new API after migration
The TextChatService in-transit API is still very uncustomisable; there is no way to edit messages in-transit or send message across different servers.
1 Like
They were specifically talking about chat visual design and customizability, I just didn’t quote the whole thing.
If this worked like Reddit, I’d spend my money to award you a medal.
Now, let me give my takes.
I have a friend who uses a real Portuguese keyboard. Ever since Roblox has pushed this update, some Roblox games have decided to use this for no apparent benefit at all. The outcome is horrendous; with the new TextChatService, she had to use the ~ key instead of LegacyChatService which allowed her to use /, a common keybind for opening the chat among many games.
Most of the time, s*** doesn’t even go well for me. With the new TextChatService, I couldn’t even use the Enter key because it was so GOD DAMN BUGGY and I had to click the send button which was inconvenient.
Thanks.
1 Like
the point is that on different keyboards the key in the same space is used for an ergonomics stand point
enter is having no issue for anyone else, seems like an issue with your device or keyboard
Custom chat solutions would presumably break once TextFilterResult:GetChatForUserAsync and Chat:FilterStringAsync are changed to return blank strings though; so any implementation of legacy chat will need to bypass Roblox by editing their implementation.
sooo what is that implementation then
not filtering? if so that case is already accounted for
Yes there’s still an impact but that there is more to the story, it is worth pulling out that staff members comment to note that details.
If the post is too hard to read, it is a failure to communicate. A lot of details was missed because Roblox could not be bothered to use something as simple as a collapsible to skip the bits that don’t matter.
If a lot of people have clearly missed something, it’s not a single person’s fault.
2 Likes
“Well, it’s worked on my device, so it’s fine.”
2 Likes
it’s probably true, i don’t recall anyone having an issue with that specifically