Confusing Legacy Chat Warning Despite Using TextChatService

Bug Reports Studio Bugs
,
#1

I am receiving a warning in Roblox Studio stating:
image

However, my game does not use the legacy chat system. Instead, I am using TextChatService
image

with using the new API, including CanUsersDirectChatAsync.
image

My chat system is custom design but fully powered by TextChatService, which is stated to be allowed as seen here:

image
image737×76 13.9 KB

{7685B629-A8AB-4452-9B04-4C2BDD2B13D9}

:hammer_and_wrench: Repro Steps

:one: Open Roblox Studio.
:two: Ensure ChatVersion is set to TextChatService (as shown in the attached screenshot).
:three: Possibly adding a custom chat design that still uses TextChatService
:four: Run the game and observe the warning message appearing despite using the correct chat system.

:white_check_mark: Expected Behavior

The warning should not appear if the game is already using TextChatService and is using CanUsersDirectChatAsync.

:x: Actual Behavior

The warning incorrectly appears even though the game does not use legacy chat, which is very confusing.

A private message is associated with this bug report

#2

The prompt is appearing because you have children parented directly to the old Chat service. This configuration is a bit odd. Out of curiosity, what is the benefit of parenting these scripts to Chat service?

#3

the purpose of them being there is that
it’s my custom chat design

I’ve attached a private message to staff with the files to see it and test

#4

Would your design work just the same if you parented it to TextChatService or ReplicatedStorage?

Edit: It sounds like the benefit of using Chat service is that Legacy LocalScripts and Legacy Scripts will run in the container?

You could replicate this behavior by setting Script’s RunContext to Client and Server respectively

Likewise you can ignore this prompt if you believe you are already using TextChatService. We can look into silencing this modal for this configuration.

#5

looks like that was the problem, hah thanks!

#6

Maybe you can make the message state the problem it found