There should be a way already, though not intuitive IMO. (pressing R1 from in the Roblox/gamepad menu)
A user should be able to resize the chat window. I hope they add that.
Finally, now I won’t see people not responding to chat msgs because half of them are console users!
1 Like
While those events are present (and while I now have some other plans for BubbleDisplayed since I never knew that existed, thank you!), MessageReceived only works on the client, in which I’d assume BubbleDisplayed would be the same way (and also wouldn’t be what I’m looking for in case someone wants to hide their message with /e)
I’m specifically asking for something serverside for something like admin scripts. I’d really want to avoid making a system that makes the client send over messages by a remote to the server to validate and act on commands, in which that same remote could be abused by anyone who finds out about said remote.
Not to mention, while there are TextCommands, I have my heavy doubts on it running hundreds, maybe thousands of commands without a hitch and with a proper way to detect if someone is allowed to run it. Not to mention the setup and tie-ins, but I guess that’s a project to undertake should a proper .Chatted replacement not exist.
Amen. Entirely.
I think this is a consequence of Studio using the new Experience Controls but not Consoles, and I would guess that it’ll work once the team working on it launches it for consoles. I would suggest filing a bug report
3 Likes
and on the 6,767th day, we were granted console chat
3 Likes
I thought you just said R1 which doesn’t make sense because you use that to switch tools. But now I see what you mean because I just played today and discovered it.
1 Like
this is a really cool update! i was talking to someone from my Xbox!
amazing! gonna test when i get home, but does it get a cooldown like normal chatting if you spam it too quickly? on other roblox quick chat systems they usually bypass the spam cooldown
1 Like
Not yet, but I’ll work on it right after lunch. I assume stopping the bypass would mean the checking spam is all on the server. If you have any other suggestions, I’d love to hear them!
1 Like
seems to work now, maybe it was just a studio thing
1 Like
Nice but why did we have to remove legacy chat? Most useless removal EVER
3 Likes
Exactly, I really wish and hope for them to stop ignoring our concerns and actually do something to address them.
It’s ridiculous that many of the frontend and some backend bugs related to TextChatService have been reported for a very long time and most still remain to be unaddressed and ignored.
Additionally, the performance issues has been reported back as far as March 2023 and they still remain to be unaddressed after ~2 years.
This is all without the fact that a lot of features and use cases are missing from TextChatService and which would affect a fair amount of games when TextChatService gets completely removed next month.
1 Like
@KingJesseDev it took longer than I thought -I restructured the server script and my power & wifi went out temporarily-, but it’s done. 
1 Like
it looked old, the code was old, it couldnt support new features
I hear this all the time, and I do not want to hear it again LegacyChat ported to TextChatService
From modifying the LegacyChat, I can tell you the code is high quality, and the amount of deprecated things is quite limited. Making the chat look more modern was also very easy to do
And roblox THEMSELVES implemented chat translation into the legacy chat, they just never told anyone. Literally overwriting a FFlag and adding a bool value was enough to enable it
The worst part of LegacyChat is it’s complexity, which mostly stems from the customizability modules. On the client especially, messages go through a lot of modules and functions, making it hard to track what is happening
It’s not because the chat is 10 years old that it’s bad. Because it is so old also means it had time to get refined into a very solid peice of code
1 Like
Will you guys eventually be working on essentially “upgrading” the console version of Roblox, to utilise next-gen console features & performance? e.g. support 120 fps, allm, vrr, etc?
thats not really what i meant by the code is old. i didnt make it seem like its from 2006 or something, its just old code, that deserved to be rewritten
also dont seem like im mad at you, i used your legacy chat port 
im ngl i forgot about this, why does roblox not support this stuff?
I don’t understand what you mean then, 2006 or 2015, I don’t understand what distinction you are making
And code shouldn’t be rewritten simply because it’s old, it should be rewritten because either the code is bad, or the company is moving to a different code structure, … (and perhaps this is one of the reasons for roblox as they are making all their new stuff in react-lua)