Disabling Certain TextChatService Default TextChatCommands doesn't actually disable them

[Real_Ser3rm (Ser3rm)]

Certain TextChatCommands appear to be fully hard coded into the TextChatService’s Default Chat, even when disabling the “Enabled” property.

It should be noted that even after deleting the command instance itself they are still enabled.

Commands I know are Hardcoded:

• RBXWhisperCommand
• RBXTeamCommand

From what I’ve tested, disabling the Whisper and Team commands is completely impossible without making an entirely custom TextChatService chat handler, but doing that isn’t viable since it comes with different issues that have already been reported.

Experience where “CreateDefaultCommands” is turned off, but certain commands (RBXWhisperCommand and RBXTeamCommand) still work
it should be noted that to test the whisper command you must be in the actual game since it will not work in team test due to this bug

BugReportPlace.rbxl (56.2 KB)

Expected Behavior:
Disabling CreateDefaultCommands, disabling a TextChatCommand’s Enabled Property or removing TextChatCommand instances should fully disable a command.

Actual Behavior:
RBXWhisperCommand and RBXTeamCommand still function despite being deleted and/or Disabled.

A private message is associated with this bug report

[Partcline (ricolantern)]

We’re running into the exact same issue.

Our game’s player communication heavily revolves around proximity chat, yet somehow there’s players who are able to bypass this entirely by using commands and channels that we’ve explicitly disabled through the studio interface.
We’re using the default chat interface.

CreateDefaultCommands is turned off -- this does not disable whispers.

Hacky attempt at a workaround: Delete any whisper channel the moment its created -- players can still whisper.

Strangely, no one in our team seems to be able to bypass the disabling of these commands themselves, so it’s apparently limited to a specific group of players??
In any case, it seems like it’s completely out of our hands.

• Is this an exploit?
• Is this a feature from some third-party client?

[AliceLostInWonder]

Hello, thank you for your report. We are currently looking into this issue and will let you know when we have an update. A temporary workaround that might help in the meantime would be to disable TextChatService.CreateDefaultTextChannels. When the default text channels aren’t enabled team and whisper channels won’t be automatically created and the /w and /t commands won’t execute.

[AliceLostInWonder]

Hello, thank you for your patience. A fix for this issue has been released. Both the RBXWhisper and RBXTeam commands will now follow disabling logic. Please let me know if you experience any other issues related to this bug.