filter_tf_player_can_cap
Jump to navigation
Jump to search
Class hierarchy |
---|
CFilterTFCanCap |
tf_filters.cpp |
filter_tf_player_can_cap
is a point entity available in Team Fortress 2. It's a filter that filters detects which players are allowed to capture objectives. This is not required for a standard objective, and also is not limited to use on them.
Note:Players are not allowed to capture objectives if they are disguised, cloaked, or invulnerable.
Keyvalues
- Name (targetname) <string>
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentname
ortarget
).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
TeamNum:
- Initial Team (TeamNum) <choices>
- Which Team the entity belongs / is assigned to on spawn
- 0: None
- 1: Spectator/Halloween Souls
- 2: RED
- 3: BLU/Robots
- 5: Halloween Bosses (only in ) !FGD
BaseFilter:
- Filter mode (Negated) <boolean>
- Inverts the filter, making the specified criteria fail and all others pass.
Inputs
TFTeam:
- SetTeam <integer>
- Changes the entity's Team keyvalue.
BaseFilter:
- TestActivator
- Tests the entity that called the input (the !activator) against the filter, and fires either the
OnPass
orOnFail
output. - Bug:Calling this input will cause the server to crash if the !activator entity no longer exists. Do not use this input to test any entities which may be asynchronously deleted, such as players or projectiles, or in an i/o chain which might be initiated by entity deletion, such as the
OnEndTouch
output of a trigger.
Outputs
BaseFilter:
- OnPass
- OnFail
- One of these will fire when
TestActivator
input is sent, depending on if the activator is allowed by the filter or not.