Migrate to TextChatService: Removing Support for Legacy Chat and Custom Chat Systems

I was planning on making something that heavily utilized cross-server communication but I guess I can’t anymore if literally all chats have to go through TextChannels now. There really needs to be a way to do cross-server messaging with TextChatService in the future.

1 Like

My biggest issue with TextChatService is the lack of what I like to call “bot speakers”. In the legacy chat system, its trivial to add new speakers as you just use AddSpeaker.

I get this behaviour can somewhat be emulated with the associated SetCore method, but this outputs the whole message as a single color, rather than an actual user sending the message.

The APIs for this dont appear to be in the new chat service, I assume this is due to issues with reporting a bot speaker, or people creating bot speakers to make themselves unreportable.

My usecase comes down to dialogs, as well as showing the dialog message as a bilboard GUI, I like to forward this message to the Chat so that the player can refer back to it in case the dialog option disappears.

3 Likes

I understand all the reasonings behind this change. However there will be some backlash if these actions are not performed.

  1. Allow for deep customization of chat UI.
  2. Allow for chat interactivity to be controlled by developers.
  3. Reinstate a “Version” of legacy in order to keep the creative freedom of chat reworks.

I promise you, ive seen roblox be stupid and its only gone downhill since then.

Dont be a failing and arrogant company relying on your shareholders to make YOUR decisions on YOUR premises.

Be a good company, and listen to your community for once ever since 2018.

Put. Chat. Customization. As. Your. Next. Priority.

:slight_smile:

3 Likes

TextChatService has a bug where the old bubble chat overlaps with the new one on npcs, will yall fix it?

1 Like

I’ve checked TextSource (equivelant of a speaker) instance and there are plans for non-user entries, but when’s that god knows when.

This is still a really bad time to announce all this because what we’re basically provided is half-baked migration which we have to WAIT for roblox to release new APIs and things for us to migrate with.

(can we also mention the fact there are some features from LuaChatService missing? e.g. run code when chat input has changed (which appears to be possible only through custom ui or the Lua chat itself)

I really don’t mind chat design, what I mind the most is amount of technical difficulties this change brings.

Why’s there so little damage control going on nowadays either???

1 Like
  • game: not being actively maintained at all
  • roblox: “hey can you rewrite some code in the game you havent touched in years so you can deal with one of our stupid coregui changes?”
6 Likes

Wouldn’t a simple unified API be a good solution? Instead of creating new ones for a new policy, wouldn’t one that accounts for almost every new possible policy be good for the long term and for the freedom of the developers? I still don’t think that Roblox taking the responsibility from us is still a good excuse to rip it all away together.

Sorry bro, but removing the Legacy Chat and then MODERATING our games for using it is not a solution, y’all FORCING us to use a ugly new chat system that came from Garbage and Wish that no one wants.

4 Likes

Thank you.


I’m pretty sure many old games exist that aren’t maintained whatsoever because their creators either quit Roblox permanently or are just - gone, are still being played.

In such event where migration is not possible because they may have a custom chat system in place, I guess your action is to private the place?

Well, that’d be bummers. But, okay.

3 Likes

Roblox stock went up due to two main reasons. Roblox saw an unexpected fairly sized earnings beat (although still not profitable), and a continued increase in user count.

I don’t doubt that Roblox has made chat a major priority now (after its been a problem for a decade) due to legal and parental pressure. However, Roblox stock tends to not shift based on individual feature releases. This unless the feature directly relates to money, such as buying games with USD rather than Robux.

P.s Its of course not impossible that this feature contributed to the stock price change. However it was certainly not a major contributing factor.

1 Like

I’m confused about CanUserDirectChatAsync, if I have TextChatService enabled and using a custom made chat UI with code that uses TextChatService, do I need this additional CanUserDirectChatAsync() implementation in my code or not?

i aint migrating it unless the thing where if your fps is low and you try to chat and then enter the algorithm breaks and then sends a message before its fully typed (unlike the classic chat)

2 Likes

Agreed, I won’t migrate too. The reason why I don’t want to migrate is because I do not want my games to use this ugly chat system.

3 Likes

“why are we doing this? idrk. everything will be modern ig lol” - roblox

3 Likes

Oh yeah, I’ve encountered this issue many times and it’s quite very annoying. I really hope that they fix it. It doesn’t happen on the Legacy chat as you’ve noted.

Yeah I’m not migrating to this. They’d have to remove legacy before that ever happens. Maybe they won’t go through with this if enough people don’t use it.

2 Likes

Exactly, I might bypass the upcoming change by just adding a modded legacy chat to my game (I refuse to call it experience cuz it sounds dumb and ugly).

4 Likes

That’s one way to get your game and maybe your account moderated. They said they will be moderating games and maybe accounts that attempt to bypass the change.

Screenshot_20241102_222716_Chrome

just adding on to this:
coregui changes on their own are fine, but having to force some (not all) creators to go stop what they’re doing (actually creating) and fix their games to work fine with these features is not ok (even if they have the span of a couple of months to do so)
i understand player safety features are important, but people have built complete custom chat systems and now you’re just telling them to rewrite most of it to use textchatservice apis or else? just let them implement the damn apis and keep their system their way

i can see why you guys ditched the whole ‘powering imagination’ thing

Reminds me of something… oh yeah! The new experience controls we have no control over. We can’t change the visibility, size, buttons, it’s so unfair.

(Replied to wrong person but whatever)