Starting 2027 all chats must happen through the heavy and bloated React CoreGUI chat and all external TCS APIs will start silently failing or returning blank. A complete recreation of this chat with the new styling tools would be needed for this to work. Someone will probably do it but that person will not be me.
What
This was a port of the pre-LuaChat Chat CoreGUI (circa 2016) to TextChatService’s API. It lightly modified the CoreScript so it ran at the lower permission level and then added a shim to register the legacy SetCore stuff and for the 2016-2020 bubblechat to work using the same TCS handler.
Why
In 2023 when this was made TCS had an amazing API but a god-awful React CoreGUI interface. The interface was much worse then than it is today and would do things like drop keystrokes when even a few FPS below 60 or cause massive lag spikes. This replacement became even more relevant when Roblox announced they were forcing the terrible interface upon everyone.
How
The chat window used modified versions of the scripts and replaced all instances of PlayersService.Chatted, PlayersService:Chat, and all non-chat related CoreScript permission functions with equivalents that work in LocalScripts. Bubble chat just needed the line height fix (worked fine in 2023 but messes up aesthetics now, as seen in the top message) and to use tcs.OnIncomingMessage. Because of how OnIncomingMessage worked, both Chat and BubbleChat were turned into ModuleScripts to work around the one incoming message handler limit.
Old chat system? I used the old chat system once. But then they replaced it. They replaced it with a new chat system. And the new chat system makes me miss the
Yooo this is awesome i hope theres a finished version of this because it looks really good!
(also that it doesnt cut off NPC dialogue like legacychatsystem does for some reason)
The NPC dialogue part is a core script and it would be hard to make a one-size-fits-all solution for that, it just hasnt been updated in 8 years so the bug in an engine update that made bubble chat need patched broke that too
Forgive me for not testing this myself before posting this, I just don’t have the means to test it right now.
The legacy chat system had issues on mobile (for me, anyways. With a relatively old phone), one of which being an issue with text wrapping. Sometimes when the final word or two of a message landed outside the right-side edge of the chatbox, instead of text wrapping to the next line, those words were cut off completely.
I don’t remember off the top of my head if this has been an issue with the new TextChatService system, I don’t think it has. But would it be safe to assume your resource won’t reinstate those old legacy issues? Or at the very least, the text wrapping issue? Is this mainly for visuals or legacy functionality too? i.e. no emoji list, command previews, etc.
(Bubble chat would still show the entirety of the message, it’s just an annoying bug regardless. Especially when the person you’re trying to read messages from isn’t nearby and their message is cut short.)
This is quite literally just the backend being changes slightly so it probably has those issues if it didnt start before 2016/2017 (and wasnt caused by lua updates with no chat fixes)
if you give me an accurate reproduction instructions thing I can try and fix it if it exists as I did no know of the bug
Reproducing the issue using Legacy chat is pretty easy. You can test it with various NPCs with different length names (although name length shouldn’t matter, it still helps tests), have them send a message in chat that’s a random length (aiming for messages that would typically be close to the point of dropping to a new line), and if it happens to land in that bug’s sweet spot, it should occur and cut off the ending of their message in the chatbox.
If it doesn’t, then I’d say it’s safe to assume it won’t happen with your resource (at least until someone gets it and reports it). I’ll give it a test whenever I can get the time. But if you also get the time, it’d probably be worth testing it out yourself as well.
Edit: Here’s a thread from 2019 that addressed the bug I’m referring to. Has a prime example screenshot and helpful information on the bug.
if someone need just the old bubble chat then here is the script for this
local tcs = game:GetService("TextChatService")
local uis = game:GetService("UserInputService")
local players = game:GetService("Players")
local player = players.LocalPlayer
--tcs:WaitForChild("ChatWindowConfiguration").Enabled = false
--tcs:WaitForChild("ChatInputBarConfiguration").Enabled = false
if tcs:CanUserChatAsync(player.UserId) then
local bubblechat = require(script:WaitForChild("BubbleChat"))
tcs:WaitForChild('BubbleChatConfiguration').Changed:Connect(function(prop)
if prop == "Enabled" then
script:SetAttribute("BubbleChat", tcs.BubbleChatConfiguration.Enabled)
end
end)
script:GetAttributeChangedSignal("BubbleChat"):Connect(function()
tcs.BubbleChatConfiguration.Enabled = script:GetAttribute("BubbleChat")
end)
local function isUDim2Value(value)
return typeof(value) == "UDim2" and value or nil
end
local function isBubbleChatOn()
return not script:GetAttribute("ClassicChat") and script:GetAttribute("BubbleChat")
end
tcs.OnIncomingMessage = function(msg)
bubblechat(msg)
end
else
game.StarterGui:SetCoreGuiEnabled(Enum.CoreGuiType.Chat, false)
end