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

My apologies. I did not see your message earlier.

5 Likes

So basically, having a custom chat system is now grounds to get your game banned?

Insane.

At least let the developers keep custom chat systems in place if they’re actively trying to filter the chat correctly.

The “admin command announcements” part is absolute insanity. We are generally using it to announce right before we have a maintenance/scheduled update upcoming, and now it’s going to turn into something that will get the games banned too? That is not something I expected at all.

9 Likes

yeah its all fine!
But it was 2 messages above, anyways…

3 Likes

EXCUSE ME???
YOU INTEND TO TELL ME THAT ROBLOX GAMES THAT SIMPLY DON’T USE A CERTAIN API ARE GONNA GET MODERATED???

What about historical games? Are we just expected to change the text chat API on games we may not be able to access anymore because Roblox decides randomly one day that the chat API needs to be unified because “eh why not” and then have the AUDACITY to ban those who resist the change?

HAS THE WORLD GONE MAD???

I get that I might be overreacting but threatening moderation action over this is insane.

22 Likes

The original post goes over how to do custom chats. You just need to be setting it up using TextChatService.

3 Likes

This. This post amazingly explains how this update is one of the worst updates to ever come to the platform. I cannot even fathom how you guys would actually approve such an update like this. Not only is this limiting for developers, but it is also worse for old experiences that use custom or already existing legacy chat systems.

I DO NOT WANT TO USE TEXTCHATSERVICE. It sucks. It performs worse, I want to implement my own features, and overall, have freedom over the experience that I made myself. Roblox is actively encouraging developers to create bypasses or workarounds with every recent update that they have been making that limits developers in one way or another.

43 Likes

I think you’ve misunderstood the announcement a bit (although it is somewhat confusing to parse) - these features will all still be possible, but need to be done within the TextChannel / TextChatService system. For example, you could have a TextChannel called AdminMessages and send / receive admin messages from that.

1 Like

The new chat UI is far too bloated and has many bugs.

One of the most important features of the legacy chat is the ability to see chat messages from users still in-game from before the time you joined, which is crucial to allowing recently-joined players to quickly join in with a conversation, especially in communication-heavy games.

There should be NO DEADLINE until every single possible functionality with the legacy chat system has been replicated with the new one. This is a basic design principle Roblox, you don’t make deadlines for a transition when the thing to be transitioned to is not complete.

16 Likes

yeah no i’m not even going to bother with this, i’m just gonna close all my games
i do not have the time nor the motivation to fully redo everything i’ve already done with the old system

7 Likes

no thank you

9 Likes

I’d prefer it if my old experiences had the chat stop working than have the place moderated.

16 Likes

That’s what I’m saying.
I hope Roblox will not remove games that will not use that new chat…

3 Likes

The issue is that we are using it to capture the attention of the players.

A single chat message is not enough to do so, especially in a game that you need to focus on other parts rather than the chat. (In fact, chat would be the last thing you’d look at there).

2 Likes

why do you have to kill off custom chat solutions? that is so unnecessary

15 Likes

Yeah, you don’t have to use the TextChatService UI (the new BubbleChat / Text Input Bars) to display messages in TextChatService. You can use TextChannel.MessageReceived to display the messages however you’d like.

2 Likes

Please make a fix to text chat scroll bar, it cuts off text

VerticalScrollBarInset = Enum.ScrollBarInset.ScrollBar

2 Likes

would be intentional but roblox decided to take another worst move at all stakes
but thing is, if it’s a modified version of legacy chat, it should be alright

2 Likes

The problem is, that the new system is restricting in certain ways that developers like me want to implement things in. Most importantly, when I open MicroProfiler with TextChatService, I’m met with a very large ExperienceChatMain process that reduces performance. I do not want that.

2 Likes


What do you find more effective?

Pay mind to this note, they’re looking into that as a solution.