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.
- Team (TeamNum)
- Which team can currently capture. (Does not detect which team the activator is on.)
- 0: Any
- 2: Red
- 3: Blue
- Filter mode
- Inverts the filter, making the specified criteria fail and all others pass.
- Maintain the same initial offset to this entity. An attachment point can also be used if separated by a comma at the end. (
parentname [targetname],[attachment])Tip: Entities transition to the next map with their parentsTip:
phys_constraintcan be used as a workaround if parenting fails.
- Global Entity Name
- When the player transitions to a new map, entities in the new map with matching globalnames will have their previous map's states copied over to it.
- Origin (X Y Z)
- The position of this entity's center in the world. Rotating entities typically rotate around their origin.Note: Hammer does not move the entities accordingly only in the editor.
- Pitch Yaw Roll (X Y Z)
- This entity's orientation in the world. Pitch is rotation around the Y axis, yaw is the rotation around the Z axis, roll is the rotation around the X axis.Note: This works on brush entities, although Hammer doesn't show the new angles.
- Response Contexts
- Pre-defined response system contexts; Format is
[key]:[value],[key]:[value],...and so on.Tip: Can also be filtered for or against!
- Toggles exclusive features of an entity, its specific number is determined by the combination of flags added.
- Hammer ID
- The entity's unique Hammer ID that's auto-generated on map compiles. Mainly used by plugins or debugging commands (like the
ent_keyvaluecommand). Run-time spawned entities don't have a Hammer ID.
- Changes the entity's Team keyvalue.
- Tests the entity that called the input (the
!activator) against the filter, and fires either the
!activatorentity 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
OnEndTouchoutput of a trigger.
- Evaluates a keyvalue/output on this entity.
<output name> <targetname>:<inputname>:<parameter>:<delay>:<max times to fire, -1 means infinite>
- Removes this entity and any entities parented to it from the world.
- Functions the same as
Kill, although this entity and any entities parented to it are killed on the same frame, being marginally faster than
- Move with this entity. See Entity Hierarchy (parenting).
- Change this entity to attach to a specific attachment point on its parent. The entity will teleport so that the position of its root bone matches that of the attachment. Entities must be parented before being sent this input.
- As above, but without teleporting. The entity retains its position relative to the attachment at the time of the input being received.
- Removes this entity from the the movement hierarchy, leaving it free to move independently.
- Fire the
OnUseroutputs; see User Inputs and Outputs.
- Adds to the entity's list of response contexts. Format is
- Remove a context from this entity's list. The name should match the key of an existing context.
- Removes all contexts from this entity's list.
- Dispatches a special effect from the entity's origin.
- Dispatches a response to the entity. See Response and Concept.
- Same as a player invoking +use; may not do anything. Can also be invoked by creating an output that does not specify an input.
This input is not included in Valve's FGDs.
- One of these will fire when
TestActivatorinput is sent, depending on if the activator is allowed by the filter or not.
- These outputs each fire in response to the firing of the like-numbered
FireUser4Input; see User Inputs and Outputs.