Hi! I own a game that relies heavily on the very specific aesthetic of early-to-mid 2010s Roblox, generic zombie apoclypse RP. For this game, using the new default chat system with its heavily modernized UI was simply not an option- but soon, the option to use the old Chat service for chat systems will no longer exist.
I tried taking a look at the original code to see if it would be easy to modify to use TextChatService. I gave up on that very quickly- there’s a lot.
So instead, I rewrote the legacy chat system back up to the point that it had everything I needed for my game. I thought I’d publish it for free use in case anyone else just needs a basic version of legacy chat they can quickly implement without having to worry about rescripting a bunch of things.
hey so uh, im confused on where exclactly I should place the “ungroup me on chat” because it doesnt seem to work? well I tried putting it in “TextChatService” so that might be wrong on me
This looks really awesome, though I have a few questions + an issue I encountered;
As for the questions, are you planning on adding DisplayName support? From what I can see, the chat doesn’t show display names, only usernames (except for the friend join messages). I also noticed that the ‘Roblox automatically translates chat messages’ message that appears with the default TextChatService is also appearing when I first join the server on PC (doesn’t happen on mobile), is there a way to disable that?
And as for the bug (i assume), in mobile, when trying to send a message, it just adds a newline instead of sending the message.
I did notice that this bug apparently also happens to me in other games that use the legacy chat service, so maybe it’s a Roblox thing? I’m just kinda confused abt that
Yeah, I can add support for display names! That should only take a minute or two.
The “Roblox automatically translates chat messages” message is a system message that Roblox automatically sends to the player as soon as they join. If you want to override it, you’ll have to manually add in an extra check for that message specifically.
The mobile bug I wasn’t able to replicate. I’m not sure what’s going on there, because I’m not doing anything particularly fancy with the TextBox there.
Chat tags should be fully functional already.
Here’s a code sample you can throw into a script in ServerScriptService if you need to test:
local ServerScriptService = game:GetService("ServerScriptService")
local Players = game:GetService("Players")
local SpeakerProperties = require(ServerScriptService:WaitForChild("ChatServiceRunner"):WaitForChild("SpeakerProperties"))
Players.PlayerAdded:Connect(function(player)
-- Adds a yellow tag named "Tag" with priority 3 to all players
SpeakerProperties.addTag(player, "Tag", Color3.new(1, 1, 0), 3)
end)
Hello! Thanks for the reply.
Is there any chance you would modify it to work with how you would used to make chat tags on Legacy Chat?
I could modify it myself to do it but to be honest I’m just wondering if you would be interested in doing it, as it might be useful for others.
fortunately i’ve actually already dealt with something similar to this. for some reason the text on these system messages is always that light gray color, and i wanted it to be black for my personal modifications to the system. the check i made for it can easily be modified to delete this message instead
just replace lines 205-210 of the “Message” script with
if sourceText ~= nil then
-- Add spacing for source text
messageLabel.Text = `<font transparency = "1"><stroke transparency="1">{sourceText}</stroke></font> {messageText}`
else
if string.sub(messageText,1,22) == [[<font color="#d4d4d4">]] and translationMessageRemoved == false then
translationMessageRemoved = true
return
end
messageLabel.Text = messageText
end
and create a “translationMessageRemoved” variable set to false before that Message.create function (around line 26)
i threw this version of it together pretty hastily so it will throw a few errors, but from the looks of it, it won’t actually disrupt anything. so you can add some stuff to the erroring scripts to clean it up, or just ignore it
edit: i found out how to remove the error it was pretty easy
just add
if frame == nil then return end
between lines 65 and 66 of the ChatChannel script that the Message script is parented to
if you want to additionally remove all system messages like that (such as the one for when you change teams) you can just remove any mention of translationMessageRemoved from that block of code and it’ll stop those too
again, not a perfect solution, but this is at least the route to go for if you want to detect these kinds of messages
I’ve been trying to work a bit on making this a bit more accurate, and I noticed that for some reason the size of the chat frame is different than the original legacy chat when playing ingame (i’m pretty sure it’s the correct size in studio when playtesting though?) for some reason
(The second image is the original Legacy Chat, while the first image is this rewrite)
The chat window is basically larger than normal
(the “You are now privately chatting with […]” is also missing, along with ‘cancelling’ the private message/switch back to the default channel by clicking on the other player’s name in the text box (where it says “[To PlayerName]”) — I tried to fix that part myself but I kinda got stuck on it so I was wondering if u could try to fix that when you have time)
No; it wouldn’t be very practical, because speaker objects don’t exist in this system, which means I’d just be forcing you to jump through an additional hoop for the sake of making the code look the same. I tried to keep the structure and usage as similar as possible without adding unnecessary complexity.
Ran a playtest recently with the GZARP playerbase and caught a handful of bugs, including:
Players are unable to type in the chat bar on mobile
Sending RichText symbols (<, >, etc.) shows up as the original escape forms in bubble chat (“<”, “>”, etc.)
The “w” in “/w” gets registered as a username search for “w”
Whispering to a player sometimes cuts off their username
Typing indicator is visible from way too far away
I’ve gotten the easy fixes out of the way and published an updated version, but I still need to do some more testing for mobile devices; they seem to be causing a lot of trouble.
If anyone else can figure out some of the mobile issues before I do, let me know and I’ll publish an updated version.
