Possibly every point that Admins and Engineers have pointed out has already been debunked and proven false, they’re just doing it to convince people to migrate, cute, honestly.
When the main point isn’t even the service itself, but rather, our freedom of choice.
Compared to before, I think I’m much more willing to accept TextChatService now. However, I still do not have full feature equivalence, which makes reimplementing some of my desired features absolutely impossible rather than just more difficult. I’m hoping Roblox can address this.
4 Likes
Agreed with this one, some people prefer old chat. Not everyone uses new one.
2 Likes
In that case you’ll have to rely on hard coding some delays to know when the chat “fades out” and keeping track of player inputs like the input box being focused or the mouse entering the chatbox window to know when it fades in. I did that with my chat so I have the flexibility to change the background etc. Its not the most elegant solution but all I could think of after toying around for so long.
Heres an example of what I was able to do. The real TextChatService background (green) fades out earlier than I want it to, so a window (red) comes in after a bit. This example isn’t perfect because the solution I implemented has a little more trickery going on, but it illustrates what is possible. For this example I’ve gone and copied ExperienceChat from CoreGUI and am automatically resizing/positioning it based on the values in TextChatService.ChatWindowConfiguration.
4 Likes
kinda liked the old chat better
2 Likes
It would be nice if there were easier direct ways to customize the chat window. I would like to make it as wide as the Legacy chat’s was, but there seems to be a UISizeConstraint preventing me from doing so and the provided HeightScale and WidthScale properties do not let me exceed it
1 Like
Yeah that’s pretty what my clump of a script is just wish they’d introduce an actual event for it similar to how they’ve got for if your focused on the chatbox.
1 Like
Great I think this is good.
Also NO ONE CARES. What about the home recommendations? Are there not 200 devs waiting for a responses ont he post “limiting low quality experiences” maybe a DETAILED SUMMARY OF CHANGES? Instead of this useless “innovation” that is 1000% not needed.
That’s going to break any game that tries to use StarterGui Chat Function, I would recommend fixing the new chat service to work better with the old startergui scripts that utilize chat messages.
does that mean that i can not make a custom chat system even if i use CanUserDirectChatAsync ?
You can make a custom chat system, as long as you use TextChannel:SendAsync()
2 Likes
but this is not a custom chat this is just the default chat
i like the old chat’s look way more, mostly because of its simpler look and actually being able to read messages
cant there just be an option for using the older look but also using the new system? idk, maybe im completely wrong here but since you can customize the look of the chat, cant roblox just provide us with the old look for us to use?
this is why you make your own custom chat
if you don’t like the default it’s not anyone else’s problem, you need to solve it
Fix the interaction with the new chat system, I jump and click / to chat and I keep jumping, sometimes I just keep moving when not pressing the movement keys after interacting with the chat. The audacity to force us to change while you have these crazy bugs is insane.
1 Like
Making a custom chat after this update will be very difficult if you’re not a coder and this is not beginner friendly. Roblox caused this problem for a lot of people so don’t make it sound like it’s just this one person having this issue.
3 Likes
There will probably some module scripts for custom chat in resources category that could help. If not keep checking up on that category as the migration progresses. I bet at least one person will make a custom chat thing for this.
But gui wise you may have to make it yourself …I believe the chat screen gui is in the player gui when you click play. So copy and paste that.
I do hope they consider this or making it easy to change chat.
1 Like
I can understand this for people who prefers the default UI of the Legacy Chat System for nostalgic purposes, but what about for people who are genuinely concerned about the downgrade of the default TextChatService UI? I am one of these people. I personally prefer the look and feel of the default TextChatService UI, however it’s literally full of bugs and the UI for ChannelTabs is a downgrade to be honest compared to the UI on the Legacy Chat System. It becomes everyone’s problem when the default UI is the most used one and it’s just not feasible for every developer to create their own UI for the chat just because Roblox couldn’t create something good when they can and should.
2 Likes
Can we have any updates on this issue? There’s been some “performance fixes” and yet nothing have changed, same stuff over and over, and this just discourages me to use TextChatService when it causes lots of trouble in terms of performance. More than a year has passed and nothing has changed.
There IS a reason to worry when TextChatService needs about 3-7ms to process LITERALLY ANY INTERACTION YOU DO WITH IT. We’re getting forced to move onto TextChatService, yet there are problems that just aren’t solved due to negligence.
Microprofiler graph, first two are 5ms reference, last is 10ms reference
This is when i keep hovering on the text chat
typing anything
sending and receiving message to myself.
Some people have worse outcomes, but for me its the worst one ive seen so far.
LUAChatService is ironically faster than what we have right now.
Again, no clear issue, because this is core script and there’s no way to properily debug it.
Sorry for looping back to this, there’s been messages that the performance problems are being investigated. It’s been a year, nothing changed. I don’t know why. It shouldn’t be that awfully hard for it to take so much time, unless for some reason the entire backend is being redone from scratch.
UPDATE: upon further exploration of debugging features, I’ve figured out that it’s React-Lua that is the cause of all the performance issues. The big question I have to this is that: how did we come to this point where React UI is awfully unoptimized?
2 Likes
A large issue that needs to be addressed is LocalPlayer.Chatted no longer firing on the client. Piggy has over 100 skins with Animate local scripts that rely on .Chatted for using emotes. The find & replace all doesnt support more than one line of code making it impossible to switch easily.
3 Likes