you’re not very smart… and this question wasn’t for you so you can keep it pushing
What I mean’t was, instead of having the LegacyChat UI can we instead use the new chat UI with the ported stuff? Like it would retain it’s functionality but also have the LegacyChat features as well
I agree, it would be cool to see some of the new features available through the port, e.g. the gradienting of chat message authors and more.
1 Like
I’ve tested it to give a proper answer and it does work with some huge caveats.
To get it to work is to set the Chat ScreenGui Enable property (from the lua chat system) to false, and you need to enable ChatWindowConfiguration, ChatInputBarConfiguration, and ChannelsTabConfiguration (which are objects inside of TextChatService)
However, this has the major caveat of completely bypassing the server side processing of messages, as the default ui calls :SendAsync() directly, rather than the remote event from the Lua Chat System. The client side processing is also rendered useless, as it can no longer detect when messages are initially sent, and only detects the reception of the filtered message (which it then promptly ignores, as the message is lacking the ID necessary to associated the filtered message to the original message that went through the lua chat system)
So TL;DR, it doesn’t work. Any other chat system that provides features on top of the TextChatService api also wont work with the default UI, as these features are built on top of the TextChatService api, requiring a custom message sending process
The TextChatService api provides basically no customization or processing capability on the server, which is very annoying
Pretty much anything is possible with the lua chat system, some things are just much harder to achieve, or at least require good knowledge of how the lua chat system is structured
What I’ve done, is, in this module
I’ve modified the :AddNameButtonToBaseMessage() function to add a gradient to the player’s name
function methods:AddNameButtonToBaseMessage(BaseMessage, nameColor, formatName, playerName)
local speakerNameSize = self:GetStringTextBounds(formatName, BaseMessage.FontFace, BaseMessage.TextSize)
local NameButton = self:GetFromObjectPool("TextButton")
NameButton.Selectable = false
NameButton.Size = UDim2.new(0, speakerNameSize.X, 0, speakerNameSize.Y)
NameButton.Position = UDim2.new(0, 0, 0, 0)
NameButton.BackgroundTransparency = 1
NameButton.FontFace = BaseMessage.FontFace
NameButton.TextSize = BaseMessage.TextSize
NameButton.TextXAlignment = BaseMessage.TextXAlignment
NameButton.TextYAlignment = BaseMessage.TextYAlignment
NameButton.TextTransparency = BaseMessage.TextTransparency
NameButton.TextStrokeTransparency = BaseMessage.TextStrokeTransparency
NameButton.TextColor3 = nameColor
NameButton.Text = formatName
NameButton.Visible = true
local IsActive = true -- Variable I added to handle when the Text is deleted
do -- Player gradient
-- Function that returns a triangle waveform from a time t
-- There are 1 triangle per second, with slopes 2 and -2
-- If you have a cyclic color sequence, you might not need a triangle waveform, but rather just a floored (x % 1) function
local function TriangleFunction(t)
return t % 1 < 1/2 and (t % (1/2))*2 or 1 - (t % (1/2))*2
end
local UIGradient = Instance.new("UIGradient")
UIGradient.Color = ColorSequence.new({
ColorSequenceKeypoint.new(0, Color3.fromRGB(183, 1, 255)),
ColorSequenceKeypoint.new(1, Color3.fromRGB(255, 11, 117))
})
UIGradient.Parent = NameButton
NameButton.TextColor3 = Color3.new(1,1,1) -- Set the player's color to white so the gradient isn't affected by it
task.defer(function()
while IsActive do
UIGradient.Offset = Vector2.one*(TriangleFunction(os.clock()/3)*2 - 1) -- Oscillates between -1 and 1
task.wait()
end
end)
end
NameButton.Parent = BaseMessage
local clickedConn = NameButton.MouseButton1Click:connect(function()
self:NameButtonClicked(NameButton, playerName)
end)
local changedConn = nil
changedConn = NameButton.Changed:connect(function(prop)
if prop == "Parent" then
IsActive = false
clickedConn:Disconnect()
changedConn:Disconnect()
end
end)
return NameButton
end
I also made the gradient move over time, for a cool effect
Something that would be useful would be to have the messageData.ExtraData available to those functions (something I might add to this port), as that would allow for much more in depth customizability that can be specified when creating/sending the messages (messageData.ExtraData can be accessed by callback functions when a message is sent, making it ideal for adding tags or changing various things about a message)
This is something I really like with the lua chat system, everything is possible if you’re able to make it. The way it was built allowed for these features without forking the whole thing (which is good and bad, as the roblox team were limited in the changes they could do). From the customization system alone the lua chat system is very feature rich, but if you allow yourself to fork it, then the possibilities are endless
Of course, the downside is that these aren’t accessible to less advanced scripters, without a youtube tutorial or something, unlike TextChatService’s default ui which is more limited but much more beginner friendly
1 Like
Something I wanted to ask: are all the settings currently present in the “ChatSettings” Module compliant with Roblox’s restrictions, as I seem to recall in an area(s) of the module when I last checked, a bit of an unsurety when it came to some of the settings being compliant with Roblox’s ToS. I might be making this up, I’m not sure, however I just want to be safe with what I’m planning for implementing this system.
There were a few things I was planning to do with the system, such as handling RichText support, which would involve me having to develop a TextMarkdown module for handling the display of things such as bolding text via surrounding a selection with two asterisks, for example, and for managing other things such as a typing indicator.
I’m probably overthinking things as I usually do, but I just want to be on the safe side.
1 Like
Could you pin point which settings you are unsure about. None of them are of concern to me
For legal reasons, I am not a lawyer and am not responsible if your game is moderated because of my port of the chat. I should probably add a MIT licence to my port
The only setting that you might be concerned about is this one
-- Shows _ before the message gets filtered. The placeholder message is displayed before it is sent to TextChatService
-- Set to false if using TextChatService's api (ie TextChatCommands, ShouldDeliverCallback, OnIncomingMessage, ...)
module.ShowUnfilteredMessagePlaceholder = true
But this one all it does is either make the message look like “_____” or if set to false, it just wont be shown until the filtered version is received
The only one I know wont be allowed is this one, from the FFlag module
-- /!\ Don't think this is allowed past april 30th (as it is probably considered a "chat"). It uses the usual filtering function,
-- and not TextChannels, as TextChannels (or TextChatService in general) doesn't have anything for storing previously sent messages and displaying them to new users
FFlags.HistoryLogEnabled = false
The module does have access to the unfiltered version of messages from other players on the client (passed to the custom Players.Chatted), but I think that’s fine