Team control point master: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
m (Updated old entity format to {{this is a}}. This action was perfomed by a bot.)
Line 1: Line 1:
{{tf2 point|team_control_point_master}}
{{this is a|e0|game=tf2|name=team_control_point_master}}


==Entity description==
==Entity description==

Revision as of 08:50, 7 January 2024

team_control_point_master is an e0 available in Team Fortress 2 Team Fortress 2.

Warning.pngWarning:
  • The {{{game}}} parameter is inconsistent with the name defined by the {{tf2}} template. This can most likely be fixed by setting the value of the {{{game}}} parameter to Team Fortress 2.
    If a parameter is consistent but you're still seeing this warning, it may be an issue with the template itself. Please discuss it on the template's talk page.

Entity description

This entity controls all the control points in a map. It is responsible for the layout of the hud icons as well as some round specific settings. team_control_point_round entities will override settings if they are used.

Keyvalues

Name (targetname) <string>[ Edit ]
The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g. parentname or target).
Also displayed in Hammer's 2D views and Entity Report.
See also:  Generic Keyvalues, Inputs and Outputs available to all entities

Start Disabled (StartDisabled) <boolean>
Stay dormant until activated (with theEnableinput).
Material for the RED Base icon (team_base_icon_2) <material>
The default material used for HUD icons for control points owned by RED
Material for the BLUE Base icon (team_base_icon_3) <material>
The default material used for HUD icons for control points owned by BLU
Cap Layout (caplayout) <string>
A string that tells the HUD how to lay out the cap points. It should be a string with indexes of cap points separated by commas to denote a new line. So 2,0 1 would create a pyramid, with cap point 2 on the top and cap points 0 & 1 on the bottom.
Custom cap position X (custom_position_x) <float>
Set the cap layout custom X position [0,1]
Custom cap position Y (custom_position_y) <float>
Set the cap layout custom Y position [0,1]
Restrict team from winning (cpm_restrict_team_cap_win) <choices>
Prevent this team from winning by capping all the points. This field is ignored if you're using control_point_rounds in your map (set the corresponding field inside the rounds).
  • 0 : Neither
  • 1 : Both
  • 2 : Red
  • 3 : Blue
Switch teams on map win? (switch_teams) <boolean>
Switch the teams when one team has won the map and the game is going to be reset.
Scoring style (score_style) <choices>
Sets the style of scoring used for capture point maps.
  • 0 : Add team score for each round won
  • 1 : Add team score for each captured point
Play all rounds before changelevel (play_all_rounds) <choices>
Determines whether the server may changelevel when mp_timelimit is up before all mini-rounds have been completed (for maps like Dustbowl).
  • 0 : Changelevel normally
  • 1 : Only changelevel after all mini-rounds have been played to completion
Partial cap rate (partial_cap_points_rate) <float>
Rate at which to give partial cap points for area captures.

Inputs

EnableDisable:

Enable / Disable
Enable/disable this entity from performing its task. It might also disappear from view.
SetWinner <integerRedirectInput/integer>
Set the winner of the round to this team (0 for a stalemate).
Icon-Bug.pngBug:Firing this Input when a point capture is in progress will not cancel the capture, resulting in an Overtime condition.  [todo tested in ?]
SetWinnerAndForceCaps <integerRedirectInput/integer>
Set the winner of the round to this team and give them ownership of all points.
Icon-Bug.pngBug:Firing this Input when a point capture is in progress will not cancel the capture, resulting in an Overtime condition.  [todo tested in ?]
SetCapLayout <stringRedirectInput/string>
Set the cap layout string.
Icon-Bug.pngBug:The layout will not work correctly if the team_control_point indeces are not consecutive starting from 0. Eg. indeces 0, 1, 3 will not work correctly.  [todo tested in ?]

Outputs

OnWonByTeam1
Sent when RED wins the game.
OnWonByTeam2
Sent when BLUE wins the game.

See also