CPU: AMD Ryzen 7 5700G with Radeon Graphics Amount of Ram: 16GB Device: Windows GPU: AMD Radeon™ Graphics
In our game we use Custom Chat Channels instead of the Roblox’s default channels. For some reason, players are experiencing that the custom channel chats randomly disappear without warning and only come back when the reclick on the channel tab. No scripts are setting the TargetTextChannel or kicking the player out of the channel so nothing should be causing this to happen. See the video below of the bug.
I’ve noticed that it also always happen when account display names, faction names, and faction tags are clicked into on the chat on your game. In addition to that, it also happens when text is cleared by the backspace keyboard button.
This issue is still occuring and it is making chatting really hard on the game War Tycoon. Can this issue please be looked at and addressed? This game is a pretty popular game and have a lot of CCUs (it’s at ~13k right now) and the bug is being complained about almost everyday on the game’s Discord server so I don’t see why it’s not being given priority if it affects so many players.
It’s been more than 5 months since this bug has been reported and it is still impacting the game “War Tycoon”. I am really disappointed on Roblox’s failure to provide proper communication on this bug report and their negligence to provide a solution to it. It’s ridiculous how Roblox doesn’t care about a bug that affects a very popular game with 2 digit CCUs on a critical feature being the chat. This is pure incompetence. Sorry for the rant however it’s most likely necessary for this bug report to have attention.
I have this issue too, exactly the same symptoms and I have no clue how to fix it. Logs show no error messages, I don’t see a config option to make the window not clickable or anything.
@thirdtakeonit Is there an update? Pretty poor response from Roblox regarding this issue so far.
local ChatBar = TextChatService:WaitForChild("ChatInputBarConfiguration")
local currentChannel = ChatBar.TargetTextChannel
ChatBar:GetPropertyChangedSignal("TargetTextChannel"):Connect(function()
if ChatBar.TargetTextChannel == nil and currentChannel ~= nil then
-- Set this back to what it should be
ChatBar.TargetTextChannel = currentChannel
elseif ChatBar.TargetTextChannel ~= nil then
currentChannel = ChatBar.TargetTextChannel
end
end)
If the user loses the target channel, it will immediately restore it back again without losing messages - if currentChannel is already nil and it loses the channel, i’m not entirely sure what this would mean since the bug only seems to occur when you’re already focused in on a channel - essentially this shouldn’t have a pitfall. Try it and let me know,
Thanks for taking the time to look at this and coming up with potential solution. We will be trying this out and I will let you know if this fixes this issue.
We’ve identified a few issues with the chat window and have a few changes in flight to address them.
One thing you can do to alleviate the issue for now is to rename your “General” channel to “RBXGeneral”
The issue in the current moment is a result of not having a TextChannel named RBXGeneral. We are addressing this root issue, but renaming an existing TextChannel to RBXGeneral may resolve things in the interim.
I would try renaming the General channel to RBXGeneral only.
The reason being is that the default UI assumes there’s a “fallback” channel during certain interactions. RBXGeneral is currently a magic-case to be the assigned default fallback. If there is no fallback, you’ll have your TargetTextChannel assigned to nil. Since ChannelTabs render the messages based on the current state of TargetTextChannel, this causes them to disappear.
While we are working on making changes to:
Prevent assigning TagetTextChannel to nil if possible
Allowing developers to assign their own default TargetTextChannel without using magic “RBXGeneral” naming
simply naming one of the TextChannels to RBXGeneral may be a quick remedy.
Hey! Did you manage to integrate it and test if it works out for you? I am not a fan of the renaming solution provided, it’s more robust to properly monitor if your channel focus is lost… it’s dynamic.