…why? If this affects games that use the old in-chat announcements, this will completely break those scripts. Roblox, stop making these useless updates. First Compatibility lighting, now the chat we had for over 6, maybe 7 and a half years? This is saddening.
1 Like
Is it really worth getting rid of all custom chat systems just because you’re adding new parental controls? It seems like there would be a way better way of doing this. For example one consolidated API that can approve or deny a message from user X to user(s) Y for any number of reasons.
Then on the customization side of things I wouldn’t really trust Roblox to make anything fully customizable like what you can do with a custom chat. And even if they did make it fully customizable it would take them years. I liked being able to add and display custom message metadata and have a customizable and extendable command system (similar to Cmdr) (which can also show the command that was run) in my custom chat. And that’s just the examples I can think of which I’m fairly certain TextChatService can’t do and my custom chat system can.
1 Like
They aren’t getting rid of custom chat systems, they are requiring all chat systems, including custom ones, to go through TextChatService.
I don’t mind this update much since I’ve happily moved on to TextChatService so I can customise the colour and font without having to make a custom system, but the fact they imply they’re going to moderate old games is bloody stupid.
I have about 200 archived games, all of them use legacy chat. How is that gonna work out when the time comes?
The answer I really want to know is, are they really gonna try to moderate archived games that still use the old chat, or will those just be automatically migrated.
I mean, indirectly that’s what they’re doing. Many features will probably stop working or have to be re-implemented because of the backend requiring TextChatService. Most developers will have to re-write their entire systems in order to support the new system.
The old one dies no matter what lol.
The old one only dies if nobody decides to make a modified version of it that goes through TextChatService, so that’s not a “no matter what” situation.
Yeah I know but my point about some of the custom features I made is still valid unless you do some like really hacky workarounds (with the possible exception of the parsing of commands)
1 Like
Taking action on experience = Moderating game = moderating owner of game, if game is moderated to much…
1 Like
I don’t mind that Roblox is imposing these changes but the performance issues with TextChatService has been a huge turn off for me. My experiences only use Bubble Chat, and so the rest of the offered advantages isn’t really applicable for my use cases. Are there any intentions to optimize so that performance is on par with Legacy Chat before the migration is fully imposed on all experiences?
1 Like
oh great just as i start working on a massive update for my game that will take 6+ months, i have to remake my game’s entire chat system and remove in-game messaging and push updates to the live game or have it be taken down. Sick.
11 Likes
Heh, I was just thinking of your game Arcane Odyssey and how you would do something about this.
Best of luck to you though.
1 Like
I have a solution to fix it all:
Keep both chat services, and add an option to not allow parent controlled devices/users. But if you allow it you must migrate
Mic drop.
6 Likes
My game’s custom legacy chat only shows messages from users whose characters are within certain stud distance of each other, and otherwise you have to send an in-game message to communicate with someone.
Since in-game messaging has to be removed since I assume it’s a form of “custom chat”, and I don’t think there’s a way to block messages in TextChatService from appearing based on distance, I think I would rather completely disable my experience’s chatting than do this.
Limited range chatting is great for making a game’s map feel like its actual size, and makes sense because obviously if a player is a 5 minute journey away from you, you shouldn’t be able to hear their chats, and instead have to message that player like you do in my game.
This is a terrible thing to force on developers and really restricts creativity on how players can chat with each other, I really hope some middle ground can be reached regarding this
13 Likes
no its not as flexible as legacy chat and what if i want to make it look like the legacy chat, i liked the older look, or the way it worked too if you wrote something in the box and then pressed esc it would automatically remove the text for you
3 Likes
i hope you’re ironic about this
same, i have been using legacy chat on purpose i dont know why im being forced to not use it
The documentation for TextChatService has an example precisely for proximity chat: In-Experience Text Chat System | Documentation - Roblox Creator Hub
2 Likes
Anyway in my opinion i think this is aweful change
and you guys could have just worked with both systems but i guess i can see some reason on why you wanna force all developers to use the new textchatservice, id suggest making the customization more flexible cause some people liked the older look of the chat box and we should be able to modify things such as UI corners as well
But i can’t say i’m not surprised cause there has been so many announcements like this in the past that it’s really not impressive to see Roblox falling off, i tend to notice that bad announcements are also published by the Roblox account and not a administrator
1 Like
i completely agree with this by the way, i planned to work on a distance-base chat for my game but since legacychat is being taken down it seems i cant do that anymore
1 Like