filter_activator_tfteam
This article needs more links to other articles to help integrate it into the encyclopedia. Please help improve this article by adding links that are relevant to the context within the existing text.
January 2024
January 2024
Class hierarchy |
---|
CFilterTFTeam |
tf_filters.cpp
|
filter_activator_tfteam
is a point entity available in Team Fortress 2. It's a filter that filters by the team of the activator. (See Filter Applications) It will allow the winning team in addition to the set team during the humiliation period. The main difference between this entity and filter_activator_team
is that this filter can be associated with a control point.
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
- Associated Control Point
(controlpoint)
<targetname> - The team_control_point associated with this filter. The filter does NOT need an associated control point to function properly, but ownership of the control point will control the team number the filter uses (setup during each round start).
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 theOnPass
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 theOnEndTouch
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.