ConVars: Difference between revisions

From Fortress Blast
Jump to navigationJump to search
(Created page with "ConVars can only be executed manually in the server console or automatically through .cfg files. Override the default values in <code>tf/cfg/server.cfg</code>, and insert map-...")
 
(Added Gift Hunt convars)
Line 20: Line 20:
|-
|-
| <code>sm_fortressblast_drop_team <1-3></code> || Sets the teams that will drop powerups on death. If set to 1, both teams will drop powerups. If set to 2, only RED players will drop powerups. If set to 3, only BLU players will drop powerups. Requires <code>sm_fortressblast_drop</code> be set to 1 or 2. || 1
| <code>sm_fortressblast_drop_team <1-3></code> || Sets the teams that will drop powerups on death. If set to 1, both teams will drop powerups. If set to 2, only RED players will drop powerups. If set to 3, only BLU players will drop powerups. Requires <code>sm_fortressblast_drop</code> be set to 1 or 2. || 1
|-
| <code>sm_fortressblast_gifthunt_goal <#></code> || Sets the Gift Hunt gift goal for the first player group, such as when there is only one player on the server. || 125
|-
| <code>sm_fortressblast_gifthunt_increment <#></code> || Sets how much the Gift Hunt gift goal should increase by for each player group besides the first. Requires <code>sm_fortressblast_gifthunt_players</code> be set to a value between 1 and 31. || 25
|-
| <code>sm_fortressblast_gifthunt_players <0-32></code> || Sets how large each player group is when determining the new Gift Hunt gift goal. If a group is full and there are more players left, those players will be put into a new group, and so on. || 4
|-
| <code>sm_fortressblast_gifthunt_rate <0-100></code> || Sets the chance that each info_target named <code>fb_giftspawn</code> on a Gift Hunt map will spawn a gift when there are no gifts left, out of 100. || 20
|-
|-
| <code>sm_fortressblast_mannpower <0-2></code> || Sets whether Mannpower powerups are replaced with Fortress Blast powerups, only on maps with a <code>tf_logic_mannpower</code> entity. If set to 0, Mannpower powerups are never replaced. If set to 1, replacing will only occur if the current map does not have an associated .json file. If set to 2, replacing will always occur. || 2
| <code>sm_fortressblast_mannpower <0-2></code> || Sets whether Mannpower powerups are replaced with Fortress Blast powerups, only on maps with a <code>tf_logic_mannpower</code> entity. If set to 0, Mannpower powerups are never replaced. If set to 1, replacing will only occur if the current map does not have an associated .json file. If set to 2, replacing will always occur. || 2

Revision as of 15:03, 22 November 2019

ConVars can only be executed manually in the server console or automatically through .cfg files. Override the default values in tf/cfg/server.cfg, and insert map-specific values in tf/cfg/<map name here>.cfg.

ConVar Description Default
sm_fortressblast_action_use <string> Sets the input to watch for when a player wants to use a powerup. The following values are accepted: jump, duck, forward, back, use, cancel, left, right, moveleft, moveright, attack2, run, reload, alt1, alt2, score, speed, walk, zoom, weapon1, weapon2, bullrush, grenade1, grenade2 and attack3. attack3
sm_fortressblast_bot <0-1> Disables or enables bots using powerups within a random amount of time. 1
sm_fortressblast_bot_min <#> Sets the minimum time after which bots will use a powerup. Requires sm_fortressblast_bot be set to 1. 2
sm_fortressblast_bot_max <#> Sets the maximum time before which bots must use a powerup. Requires sm_fortressblast_bot be set to 1. 15
sm_fortressblast_debug <0-1> Disables or enables debug mode, which displays debug messages in chat and lets all players on the server use the command sm_setpowerup. 0
sm_fortressblast_drop <0-2> Sets how the plugin should handle players dropping powerups on death. Note that dropped powerups do not obey gravity. If set to 0, players will never drop powerups. If set to 1, drops will only occur if the current map does not have an associated .json file. If set to 2, drops will always occur. 1
sm_fortressblast_drop_rate <0-100> Sets the chance that a player will drop a powerup on death, out of 100. Requires sm_fortressblast_drop be set to 1 or 2. 10
sm_fortressblast_drop_team <1-3> Sets the teams that will drop powerups on death. If set to 1, both teams will drop powerups. If set to 2, only RED players will drop powerups. If set to 3, only BLU players will drop powerups. Requires sm_fortressblast_drop be set to 1 or 2. 1
sm_fortressblast_gifthunt_goal <#> Sets the Gift Hunt gift goal for the first player group, such as when there is only one player on the server. 125
sm_fortressblast_gifthunt_increment <#> Sets how much the Gift Hunt gift goal should increase by for each player group besides the first. Requires sm_fortressblast_gifthunt_players be set to a value between 1 and 31. 25
sm_fortressblast_gifthunt_players <0-32> Sets how large each player group is when determining the new Gift Hunt gift goal. If a group is full and there are more players left, those players will be put into a new group, and so on. 4
sm_fortressblast_gifthunt_rate <0-100> Sets the chance that each info_target named fb_giftspawn on a Gift Hunt map will spawn a gift when there are no gifts left, out of 100. 20
sm_fortressblast_mannpower <0-2> Sets whether Mannpower powerups are replaced with Fortress Blast powerups, only on maps with a tf_logic_mannpower entity. If set to 0, Mannpower powerups are never replaced. If set to 1, replacing will only occur if the current map does not have an associated .json file. If set to 2, replacing will always occur. 2
sm_fortressblast_powerups <#> A bitfield that denotes which powerups are enabled. A value outside of the range (or a value that only enables Mystery) will forcefully enable all powerups. Add the bits of your preferred powerups together to find the value you want. -1