Difference between revisions of "Filter activator tfteam"
(Fix some typos, add note about differences between filter_team nad filter_tfteam) |
m (filter_activator_team that is) |
||
Line 7: | Line 7: | ||
It will allow the winning team in addition to the set team during the humiliation period. | It will allow the winning team in addition to the set team during the humiliation period. | ||
− | The main difference between this entity and | + | The main difference between this entity and filter_activator_team is that this filter can be associated with a control point. |
{{clr}} | {{clr}} | ||
Revision as of 08:06, 19 November 2013
filter_activator_tfteam
is a point entity available in Team Fortress 2.
Entity description

A filter that filters by the team of the activator. The team number to filter by. If the filter mode is Allow, only entities whose team number matches the given team will pass the filter. If the filter mode is Disallow, all entities except those whose team number matches the given team will pass the filter.
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
- Associated Control Point
<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).
TFTeam:
- Team (TeamNum)
<choices>
- Team
- 0: Any
- 2: Red
- 3: Blue
BaseFilter:
- Filter mode (Negated)
<boolean>
- Inverts the filter, making the specified criteria fail and all others pass.
Flags
TFTeam:
SetTeam
<integer>
- Changes the entity's Team keyvalue.
Inputs
BaseFilter:
TestActivator
- Tests the entity that called the input (the
!activator
) against the filter, and fires either theOnPass
orOnFail
output.

!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.