Time for another meme post that summarizes the change Roblox has implemented on us.
12 Likes
I think removing Legacy is actually a good thing because you can easily disable chat filter in Legacy because it’s corescripts are public but TextChatService’s isn’t.
Well TextChatService corescripts are also public since they got decompiled but you can’t edit them during live unlike Legacy.
I can’t even rewrite my custom chat script to use TextChatService, it originally uses TextService and trying to change it just messes it up entirely. This update is terrible.
You can also disable filter and display unfiltered results in TextChatService lmao.
Not really that’s on studio only unless you’re talking about the callbacks then I don’t think that’s possible
The right choice here ROBLOX is to throw your hands up, put out an announcement that goes something along the lines of “We have heard your feedback and will be postponing this for later until we have a better plan of how to do this again!”
… then forget it, sweep it under the rug and go on. Just like
another very controversial update where many developers rioted. Those who remember, remember. That announcement from months ago was definitely buried. ( Experiences using Marketplace Items - Policy update - Updates / Announcements - Developer Forum | Roblox)
3 Likes
It is possible, I’ve made it many times before. You can even use commands to do it.
1 Like
They’re so vague on this, my game uses a custom chat script based on the late 2014 chat, and trying to change it to use TextChatService just does NOT work, i really hope they add things like being able to place the input bar somewhere else at the screen.
1 Like
TextChatService singleton and related instances ~= ExperienceChatMain core script that was written by some intern.
So many people in this thread are not understanding that. They should have worded the OP more carefully.
I don’t exactly trust Roblox moderation with going about this change, to be blunt, nor am I particularly fond that this is occurring in the first place when I still find TextChatService to be terribly more annoying to work with than the legacy chat system.
TextChatService just doesn’t have the same level of feature parity out of the box as the Lua Chat System. Accomplishing the same things you could do relatively easily with the legacy system requires more work. The biggest problem is the default interface being locked to the CoreGUI, meaning that you cannot modify it in any way. If you want to have anything close to the original system, you have to create your own GUI entirely, which can be a headache for many developers.
And then there are the other issues, highlighted by many a reply in this thread.
It’s like every year Roblox decides to attempt a change that rug-pulls developers and forces them to scramble and change their code, and it’s really, really exhausting.
I’m not surprised, but I’m still disappointed, honestly.
2 Likes
My game Poser relies on a fork of the legacy chat system. I don’t want to be forced to switch over to TextChatService, if I can find a way to do it. I understand depreciating it, and I understand deprecating it. But to force us through platform policy? This is a very distasteful move.
4 Likes
This would only be an issue if the developer uses a forked version fo legacy chat for each experience: it will be automatically migrated if using vanilla legacy chat as seen here:
keep team create chat i use it alot
This is not true. Many developers utilize the changing the chat window’s position with SetCore. Now we’re limited to the basic four corners without any utility to atleast offset from a corner.
For anyone who, just like me, is negatively impacted by this update, I just wish to state that I created a feature-request, hoping for this to be changed to support more use cases. Feel free to contribute any of your own personal pain points in there; including if a solution similar to my suggestion would be helpful or not.
1 Like
this is one of the most stupidest updates you guys have ever done
you are REQUIRED to remove custom chat and migrate with the roblox intergrated chat system??? and if not you would get moderated??? what???
dude, allot of my games use the legacy chat system and needed for related stuff like that, what did you think before rolling this out
just a fyi: this will ruin allot of roblox games using it, atp you are killing your own platform
1 Like
Will this update also effect the use of the “Chat” service for non-chat related functions such as filtering user-generated text? I have a highway sign system that uses Chat:FilterStringAsync() in order to filter player-inputed text as per original rules. I used that because it is simply to integrate, simply call the function with the text you need to filter and you get a simple string straight back with the filtered message. Unlike the TextService equivalent that returns an entirely seperate instance that needs further processing to extract the filtered string from for display.
No. You are simply required to modify your custom chat in a way in which all messages are sent and delivered through TextChatService. This can be quite annoying unfortunately.
This explains it well:
1 Like
In my opinion, forcing this change and moderating not only the places but the creators’ accounts is too far. I’d rather have the legacy chat completely removed and for non-compliant experiences to be unavailable to certain audiences until changes are made. At least improve the performance of TextChatService, since for fast paced non cash grab games, every bit of performance matters.
What?
Also does this just mean I have to comply with new API? My games text chat is entirely custom, so do I just have to change message sending/receiving to go through TextChatService? The wording of this announcement is all over the place. “You can use custom chat, but also you can’t!”
4 Likes