Env player blocker: Difference between revisions
Jump to navigation
Jump to search
Note:Examples of its use can be found in L4D1 Authoring Tools SDK content, such as the l4d_airport03_garage.vmf crescendo event.
ThaiGrocer (talk | contribs) mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{ | {{l4d series point|env_player_blocker}} It blocks any PC/NPC from entering of the specified type. | ||
{{note|Examples of its use can be found in L4D1 Authoring Tools SDK content, such as the l4d_airport03_garage.vmf crescendo event.}} | {{note|Examples of its use can be found in L4D1 Authoring Tools SDK content, such as the l4d_airport03_garage.vmf crescendo event.}} | ||
Revision as of 00:42, 2 November 2019
Template:L4d series point It blocks any PC/NPC from entering of the specified type.
Note:Examples of its use can be found in L4D1 Authoring Tools SDK content, such as the l4d_airport03_garage.vmf crescendo event.Keyvalues
An outlined box is displayed in Hammer when Mins/Maxs are specified.
- Initial State ([todo internal name (i)]) <choices>
- Initial state of the blocker
- 0 : Disabled
- 1 : Enabled
- Blocks ([todo internal name (i)]) <choices>
- What should be blocked
- 0 : Everyone
- 1 : Survivors
- 2 : Player Infected
- 3 : All Special Infected (Player and AI)
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentnameortarget).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
Inputs
- Enable
- Enables the Blocker
- Disable
- Disables the Blocker