I put in a feature request on this BETA, and wondering is it filed internally and what’s the timeline on it because this feature could be really used in all types of games not just mine.
We’re currently aligning on finalizing UI/UX for channel tabs and also parallelizing some higher priority, frequently requested support on other developer requested features such as increased bubble chat customization, cleaner NPC text support, and various small quality of life requests mentioned in this and other posts.
Using game:GetService(“Chat”):Chat() for NPCs is a similar issue to the point before. The chat bubbles fail to appear sometimes. Some players can see their chats and other players can’t.
These are the main issues I’ve had with the chat which have been ongoing issues for a while now.
In the legacy LUA chat system, I had the ability to restrict commands to specific channels so only those players who were in those channels could execute them. This is in addition to what permissions the player has. So an admin or moderator could /kick a player, but only from the admin channel. It also provided a private channel for moderators and admins to talk to each other. Now it’s just strictly player permissions, which I guess is ok.
Another feature that I would like to see (others have requested this as well), is a flag in the command definition instance to make the command case-insensitive. So /cOmmAND is the same as /command which is also the same as /COMMAND.
Beyond that, I’m going to have to do a rethink on how my command architecture is setup.
If you look at the code to my game, I am using non-player speakers for server generated announcements. The announcements alert players to when someone was killed, who killed them, with what weapon, etc… It also alerts the players when someone enters the game, if a player gets an arm or leg taken off, falls to their death, or dies due to some environmental factor (like trying to swim in lava). So until that actually gets added, I cannot migrate over to the new system.
As for the system messages, I’m working on that. But what @SubtleShuttle mentioned below is an issue:
The problem with that example is that we are not allowed to know the age of the player. Because of this, we cannot make that distinction. Is this going to change in the future? Will there be a new parameter for us to indicate an age range so Roblox can maintain user privacy? System messages and system messages and are important for a reason. The indicate important status changes in the server. Therefore they should be broadcast to all players on the server regardless of their age. Having it on a per-client basis is asinine. I can see a per-client basis of having messages from a a non-player speaker, but not system messages.
I’ve noticed that bright violet color doesn’t match up in the new system, can you please provide the new colors or is there a function to get the color for a players name.
Any updates on customizable bubble chat for specific chat channels? I am specifically asking for this level of customization on individual team chats and whispers. For example, I would want the green team to have their team chat bubble color to be light green. Blue team should have their team bubble chat color be light blue and so on.
Is there a way to get a sending clients message before it reach’s the server and sink it? The new command system could be handy but it’d prefer not to be forced to use it. Especially with the fact that it is case sensitive and it forces me to replicate commands the client isn’t permitted to use.
Hello. Regarding TextChatService. Whenever I join a game using this module and try to use the chat, my message either doesn’t appear or appears for a millisecond. Is there a reason for this? Or perhaps a fix? It occurs both in my games and other ROBLOX game
Bug with TextBoxFocused firing after losing focus or pressing enter. I was trying to update a script that shows a little bubble above a player when they’re typing and realized that TextBoxFocused only fired after losing focus/pressing enter.
I put this in a local script under starter player scripts and testing showed that it does in fact fire at the same time as textboxfocusreleased. This was done on a new default template and on a live server.
local ui = game:GetService("UserInputService")
ui.TextBoxFocused:Connect(function()
print("test1")
end)
ui.TextBoxFocusReleased:Connect(function()
print("test2")
end)
Pressing slash or clicking on the chat bar does not fire the focused event, pressing enter or losing focus fires both.
It’s possible to send system messages and customize them using Rich Text.
I wrote a tutorial for how to convert usage of the old game.StarterGui:SetCore("ChatMakeSystemMessage") function (which no longer works with the new TextChatService) over to the new API
The tutorial shows how you can display system messages with custom color, font, etc.:
I think that given the limited ability which developers have to edit this new chat’s functionality, Roblox should try to cram as much configurable functionality into it as possible. This is one I would like to see