Add cvars to toggle (show/hide) chat messages from some plugins - #998
Open
altair-sossai wants to merge 1 commit into
Open
Add cvars to toggle (show/hide) chat messages from some plugins#998altair-sossai wants to merge 1 commit into
altair-sossai wants to merge 1 commit into
Conversation
…educe chat spam for players
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Several plugins send recurring chat messages that explain game mechanics which more experienced players are already very used to seeing, which ends up causing a bit of chat spam during matches. The goal of this PR is to let server owners turn these messages off through new cvars to avoid that spam. Every cvar defaults to
1(show), so behavior is unchanged unless an owner explicitly sets it to0.1.
checkpoint-rage-control.spcrc_announce(default1)0:Tank will still lose frustration while survivors are in saferoom.Tank will not lose frustration while survivors are in saferoom.2.
l4d2_slowdown_control.spl4d2_slowdown_announce(default1)0:Water Slowdown has been reduced while Tank is in play.Water Slowdown has been restored to normal.3.
l4d2_tankrage.spl4d2_tankrage_announce(default1)0:For every X% Survivors run back, the Tank will have their frustration frozen for Y seconds.4.
l4d_tank_rush.spl4d_no_tank_rush_announce(default1)0:Tank has spawned. Freezing distance points!Tank is dead. Unfreezing distance points!Survivors made it to the saferoom. Unfreezing distance points!l4d_no_tank_rush_spawn_sound) stays independent of the message toggle.5.
l4d2_tank_attack_control.spl4d2_tank_rock_selector_announce(default1)0: the "Tank Rock Selector" control tutorial shown to the Tank player on spawn —[Tank Rock Selector]Reload/!overhand = 2 Handed OverhandUse/!underhand = UnderhandM2/!overonehand = 1 Handed Overhand6.
spechud.sp(Hyper-V HUD Manager)Two independent cvars (the hints target different audiences — the Tank player vs. spectators):
spechud_tank_usage_hint(default1)0:<HUD> Type !tankhud into chat to toggle the Tank HUDspechud_spectator_usage_hint(default1)0:<HUD> Type !spechud into chat to toggle the Spectator HUD