We require the following two features to be added in order to move our game over to TextChatService by the deadline:
Please add both (they are incredibly easy fixes that will take maybe an hour), otherwise we will be unable to switch
We require the following two features to be added in order to move our game over to TextChatService by the deadline:
Please add both (they are incredibly easy fixes that will take maybe an hour), otherwise we will be unable to switch
Honestly this is mostly confusing for me and I might just wait to see if I’m effected. I think this just effects direct messaging with other users?? But I don’t even know if I’m using legacy or the new chat? And why would it matter without any form of direct messaging besides just bubble chat?
Slightly confused, oh well!
My game uses a slightly custom chat system just to display the messages, but everything else is built in, so I guess I just hope I’m not effected? ???
I’m a little confused by these new rules, I currently have a game that has custom chat only for “admins” of the experience that works across different places. Right now the custom chat goes through the FilterStringForBroadCast, and then goes through MessagingService to be replicated to other places. If i update my custom chat to use TextChannel
s, can I still send the messages to other places through MessagingService?
People are confused about Fork Chats requirements, is this meant to be the following?
- Either:
a. Forked version of the legacy chat systemb. Custom chat that does not use legacy chat system or TextChatService as its backend|By January 30, 2025
Integrate TextChatService: CanUserDirectChatAsync API and check that Whisper and direct chats are gated by this method;OR
By April 30, 2025
Migrate to TextChatService
If not the case, are we actually required to fully use TextChatService on April 30, 2025?
i don’t understand why Chage something when its ok i use Roblox chat in my games i don’t use voice
A reminder that not all developers can even migrate over to this because cross-server communication, in-transit message editing and message history just don’t exist as features. This effectively kills off social-deduction games as many become easier to exploit. Cross-server messaging systems also just outright became a no-go. Please do re-consider this change in favour of a different API structure that doesn’t shoot down these use-cases.
Why wasn’t CanUsersChatAsync considered for this, it seems to have the exact same documented purpose? Is CanUsersChatAsync used for a different purpose?
is there a way Xbox can use chat to say hello on Roblox?
As I stated before and will say again, please dont moderate people who forked the chat in the past.
I dont know which games I forked it in.
I agree. Roblox should have grandfathering policies. E.g. Something like “Experiences created before [DATE] are exempted from this policy change.”
I can’t miss the opportunity to voice this:
Enabling the new TextChatService, in any capacity, will grind my experience to a laggy halt. There are significant performance issues when dealing with many players, StreamingEnabled, non-standard characters (particularly without a Head) and Persistent characters over long distances.
You’re leaving us in the dark on how to migrate!
Does Chatted
still work? Since I’ve heard posts talking about how it’s not very compatible friendly with TextChatService.
According to this, messages from admin commands don’t count as a “chat” so it doesn’t need to go through TextChatService. But it still has to be filtered.
It definitely isn’t friendly. I don’t know how can I check if player wants to directly message somebody, because there’s no variable that says so. Let me consider the fact I cant listen to specific TextSources speaking compared to Speaker API of L U AChatService.
It’s so limiting I swear.
Chatted
should still work, but you can’t tell if player is trying to whisper to someone else.
I would assume that by the time the migration deadline hits, TextChatService will be fully up to date with both the legacy chat and also have additional features that lets you do things like this
fortunately, people will not get moderated, and the game will not be taken down.
VERY UNFORTUNATELY the chat in all those games with forked systems will all have their chat disabled
then again… I cant think of any games that use legacy chat service anymore off the top of my head
JToH does i guess, but it can be ported over to the modern one quite easily
maybe murder mystery 2? i cant remember what that games chat looks like
it is what it is i guess, i dont really use chat features all that often though, i am more of a “make pseudo-science evolution simulation” guy, so i have never actually delved into any sort of game styles that include messing with the chat service or anything like that
Roblox has confirmed that there will be no moderation action unless there is evidence of creators deliberately bypassing the new chat system.
For games that have not been migrated by April, first they will attempt to auto-migrate, and if that doesn’t work, then they’ll disable the chat, and if that doesn’t work, then they’ll set the game to private until the creator has migrated it.
i don`t know how to use textchatservice
Surely Roblox wouldn’t announce an API twice without it being available either time right?
Ha… ha…
More seriously: I know that 650 is released but I cannot update Studio.
TLDR Do I need to change anything in any games that use the legacy chat or the new chat