why not change that up a bit? people have done it before
Are you able to add more configurations for the chat window? Like transparency, font, textstroke settings, etc like the old chat?
because I might not gonna change up a bit and the new chat system may have some issue I won’t do it until the new chat system have the same features as the legacy did
As I’ve used this chat more with my games, there are many bugs that make me want to move back to the legacy chat service, here are some I’ve come across:
Chat History Bug:
One of the most annoying bugs out of them all is that after a server has been running for a while, there is a chance that the chat history will stop updating.
Scrolling Bug:
When disabling the chat utilising “setCoreEnabled”, upon re-enabling the chat, it will have scrolled to the top. This makes the player have to scroll down, which becomes tedious as it occurs frequently.
User Input Bug:
When you are holding one of your keys and press “/” to open the chat, even after you let go of that key, it will still think you are holding it. This is very annoying because players often open the chat while holding the “W” key - as a result, they are stuck in movement until they close the chat and click the “W” key again to override it.
Character Limit Reached Functionality:
When you have reached the character limit in this chat, it does not stop you from typing. Instead, it allows you to send the message and will only after notify you that your message is too long. As you can tell, this is extremely annoying when you’ve typed out a long message and it is instantly gone.
Chat Opening:
When joining the game, the chat is already open, however, the button to open the chat does not display this (it assumes the chat is closed). This means that you actually have to click the button twice in order to close the chat for the first time.
Idle Bug:
Sometimes even when you aren’t idle and the chat box is still open with you typing in it, it will fade out. Additionally, sometimes the chat box doesn’t fade out when you’re idle but the text does.
These are the bugs I’ve experienced so far, I will edit this post if I find any more.
I finally decided to try out the new in-experience text chat and was kind of dissapointed to find how hard it is to make tiny adjustments to the default UI. I personally love the new design but dislike the black text stroke around the text. After looking into the documentation for a while I could not find any ways to customize this without having to fork a copy of the Gui.
Is there ever going to be ways to do this, or did I just miss something?
Edit: It was the latter. This is technically covered in the documentation but I still think the name for “prefix” is confusing especially when used in the context of the VIP tag tutorial.
Still unfortunate that you can not modify the colon’s text stroke but this will have to do for now.
Simply set TextChatService’s ChatVersion from TextChatService back to to LegacyChatService!
We are investigating supporting additional configuration via ChatWindowConfiguration and ChatInputBarConfiguration!
Hi, for visibility and tracking purposes please submit bug reports instead (if you edit an old post there’s a high chance we’d miss any edits and we’re getting lots of feedback to track), thank you!
The new chat appears to have some type of connection leak, as after testing by myself for a few minutes, all keystrokes were causing massive stutters visible in the MicroProfiler.
I imagine this is related to how many chat messages have been processed and I expect it to be worse in actual servers.
There’s also a very annoying issue where pressing the chat key has a delay for when it actually focuses the chat bar. I’m assuming this is to avoid the chat bar picking up the same keystroke that activated it, but the old chat worked around this just fine.
I Cannot wait!
Changing the chat position is an absolute MUST! great work again as always
Is there a way to set a cooldown between sending messages, so that people can’t spam?
This is very annoying, I’m actually missing letters because of this
To sum up, the new chat is so far one big bug and a mess, not to mention usage of various ugly hacks and weird input handling.
While bugs are expected and acceptable for such a new thing, ugly hacks and weird behaviours are not. I thought updating stuff should mean getting rid of these, but apparently that’s not the case with Roblox.
And it’s not even the first time. Example: 2020 update of Core GUI, topbar and the playerlist. The “more menu” doesn’t handle user input correctly at all. The playerlist still does not handle longer names properly. And there’s much more.
Why, Roblox, why can’t you just update well-made components instead of throwing them in the trash and putting crappy, rushed replacements in their place, and making changes that no one asked for?
Hi! Sorry to hear that you had such a poor experience!
We’re taking feedback and rapidly iterating to offer the best in-experience chat system we can offer. We’d appreciate if you could possibly elaborate on the “usage of various ugly hacks and weird input handling” you mentioned (perhaps a bullet point list, or if some of these have been already mentioned in above posts, links/references to them) so that we can identify the issues and resolve them.
Thank you for your patience and cooperation!
I’ve come across some unintentional behavior with the new chat system when used with the new bubble chat system. Each time Chat.BubbleChatEnabled
is disabled and reenabled, chatting with the new chat system creates extra duplicate bubbles. This issue does not occur with the old chat system. Here’s a video of the issue, comparing both chat systems:
First of all I’d like to apologize that my previous post was perhaps a little bit too emotional, I was expressing my frustration with the overall poor quality of Roblox’s frontend (because there’s no other place to express it and Roblox barely ever wants to listen to user feedback but that’s another story).
Anyway, going back on track, by “ugly hacks and weird behaviours” I meant behaviours that clearly indicate that something somewhere is not done how it should be, such as:
This behaviour is not present with standard TextBox
es or the old Lua chat system.
This one is weird and also annoying (and also falls under the ugly hacks category if the reason why the delay exists is correct). Not present with previous chat systems either.
You can use TextChannel:DisplaySystemMessage("msg")
within the PlayerAdded
and PlayerRemoving
events to do this.
It’s pretty nice and I would love to use it, however my originial chat commands do not work with the new chat (and I’m too lazy to change it) since it relies on Player.Chatted event, which doesn’t fire with the new chat.
It would be pretty nice if that event could fire with the new chat or have an alternative to that gives the unfiltered message when a player chatted