By January 30th, 2025 we need chats to comply with settings thus you can either incorporate the new TextChatService:CanUserDirectChatAsync API into your legacy or custom chat implementation OR migrate to TextChatService where we will take care of settings if you are using default channels.
By April 30th, 2025 we will still require all experiences to migrate to TextChatService.
I’m making a classic game, and the legacy chat bubble is one of the core parts of making it feel classic.
And I mean identical.
Considering the new report button in the chat window, are we expected to have all communications route through the chat window or are we allowed to use the TextChatService APIs but with a custom UI?
Specifically, we have a custom chat window when you’re in the middle of a trade, and I wanted to know if we can still use that visual design but use the TextChatService APIs (TextChannels, not the interim APIs).
-- The new CanUsersDirectChatAsync literally works cross server, they should have done any amount of research before making that announcement.
External Media-- This feels more like a classic Roblox fan trying to get people mad at any changes this site makes for the millionth time, even though I shouldn’t even have to argue why the “don’t DM minors” update is an incredibly good changes for Roblox.
-- Yes, very easily. The legacy chat is made using regular GUI components, you can even see them if you go into your PlayerGui while playtesting in Studio. You just have to make sure that under the hood that it’s using TextChatService, but as long as you’re doing that everything should be all good!
I was worried about the Custom Chat implementation, this clears up that it may be used still. Thank you.
Great question, it’s not supposed to return an array in that shape! We have a flag we need to flip on for Studio to address this. We’ll do it first thing tomorrow.
Okay, that’s fair enough actually. As long as the look such as the font are all the same, then I see no issue with this update.
Update – studio has been updated and now the behavior of this method should act as expected
I havent tried this out yet, but I found this the other day: Old Chat System - LegacyChatSystem converted to TextChatService API
Will we ever be able to modify the TextChatService like LegacyChatService? Most of us have an autofill system using LegacyChatService and this will hurt the game when it is migrated.
Will there be support to resize and reposition the chat as well as being to save and load those settings for the player?
And what about custom chat systems that have custom emojis & custom animated emojis, will this be supported before April 30th as well?
Oh wow, that’s useful!
Thank you so much for showing me this.
How forked do we have to fork the LegacyChatService for it to be considered forked?
Anything that doesn’t update with Roblox’s chat (ex. placing all of the scripts in Chat in studio so roblox cant load its own)
Will games that aren’t open to be played but haven’t enabled this feature be taken down? I don’t really want to have to go through all old games for this…
I wasn’t calling it a bad change, I was suggesting something they could add to it.
Also, the message system I was referring to works with an inbox system, not a real-time chat. Does this service support that?
My game doesn’t use Chat, but is there a way to entirely disable roblox’s Chat Systems completely, such as deleting ChatService?
Also, TextChatService is VERY easy to bypass, practically anyone can do it (see: a literal baseplate.)
Not to mention when I chat at low fps it sorta just kills itself when you press enter, legacy will wait for everything to type then send the message.
so basically no more custom "retro"ish chats (and pretty much any other custom chat) for games like retrostudio, never let roblox cook again