Skip to content

[TF2] Add convar to prevent voice commands being printed in chat#1869

Open
YourSourceBoiii wants to merge 2 commits intoValveSoftware:masterfrom
YourSourceBoiii:voicecommandscvar
Open

[TF2] Add convar to prevent voice commands being printed in chat#1869
YourSourceBoiii wants to merge 2 commits intoValveSoftware:masterfrom
YourSourceBoiii:voicecommandscvar

Conversation

@YourSourceBoiii
Copy link
Copy Markdown

ISSUE: On certain gamemodes and servers, it can be quite annoying to constantly get spammed with voice commands being subtitled in chat. (Voice) shitman gaming 123: Spy!, etc. being done by people on the other side of the map or as a joke. It would be nice to give players the ability to prevent these messages from being printed to their chat.

FIX: Add in a client side convar named cl_mute_voice_commands_text.
This convar is set to 0 by default, allowing new players and less technically inclined people to still see those voice command subtitles in the chat.
When cl_mute_voice_commands_text 1 is set, none of the voice command subtitles get printed into your chat, allowing you to experience more peace of mind.
When cl_mute_voice_commands_text 2 is set, only calls for a MEDIC will be printed to chat. A special case is made for these as medic calls are useful for medics to determine where somebody is on the map (seeing both their name in chat and seeing the balloon pop up on your screen)
disabling-voice-commands-in-text-chat-v0-ddzsn4x8ktw11

@naydef
Copy link
Copy Markdown

naydef commented Apr 1, 2026

It would be even better if there's in addition a server-side convar for this. (Not that there's a plugin blocking voice commands in chat already)

@dilbertron2
Copy link
Copy Markdown

In my opinion a nice addition would be to have Spy! calls also be a part of cl_mute_voice_commands_text 2 as Spy! and MEDIC! calls are similarly as important, in the heat of combat it can be easy to miss a Spy! callout if its not printed to chat.

@Gavitro
Copy link
Copy Markdown

Gavitro commented Apr 4, 2026

I think a more efficient solution would be an option to filter which specific voice commands are muted. I would argue "Sentry Ahead!", "Help!" and "Incoming!" are useful, but adding them all to cl_mute_voice_commands_text 2 might be cumbersome.

@YourSourceBoiii
Copy link
Copy Markdown
Author

I think a more efficient solution would be an option to filter which specific voice commands are muted. I would argue "Sentry Ahead!", "Help!" and "Incoming!" are useful, but adding them all to cl_mute_voice_commands_text 2 might be cumbersome.

What do you think would be a better solution then? I kinda wanted to keep it simple to increase the chances of Volvo merging this, but if you have a better idea I'm willing to add it in

@FlaminSarge
Copy link
Copy Markdown
Contributor

This should also be integrated with the chat "Filters" button as "Voice Commands" before being merged, as an additional entry alongside e.g. Team Changes/Achievement announcements. The cvar should be a part of cl_chatfilters instead of its own cvar.

See

CHAT_FILTER_ACHIEVEMENT = 0x000020,
and
new CHudChatFilterCheckButton( this, "achivement_button", "Sky is blue?", CHAT_FILTER_ACHIEVEMENT);
, should be simple enough to add.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants