Func nav blocker: Difference between revisions
Jump to navigation
Jump to search
Note:The entity will NOT start to block automatically: it must first be activated with the
Note: In l4d2, func_nav_blocker behaves slightly different then in L4D1. To block a nav area, you must use a logic_relay triggered by a logic_auto on map spawn and send an unblocknav input to all func_nav_blockers, then selectively send an input again .5 seconds or so after and block the ones needed. Failure to unblock them before blocking them will produce the error in the console that says "Area # already blocked by a different team id". In l4d2 func_nav_blocker may also ignore your "team(s) to block", and will block both teams if the func_nav_blocker brush resides in a prop_door_rotating , func_physbox and perhaps others entites which may break your flow if you have it set to "Affects Flow: Yes."
Warning:Enabled/disabled state does not block or unblock NAV areas. Use
Warning:Enabled/disabled state does not block or unblock NAV areas.
m (Added some info about l4d2 I had figured out by trail and error.) |
(Reformat) |
||
| Line 4: | Line 4: | ||
{{note| In l4d2, func_nav_blocker behaves slightly different then in L4D1. To block a nav area, you must use a [[logic_relay|logic_relay]] triggered by a [[logic_auto|logic_auto]] on map spawn and send an ''unblocknav'' input to all func_nav_blockers, then selectively send an input again .5 seconds or so after and block the ones needed. Failure to unblock them before blocking them will produce the error in the console that says "Area # already blocked by a different team id". In l4d2 func_nav_blocker may also ignore your "team(s) to block", and will block both teams if the func_nav_blocker brush resides in a [[prop_door_rotating|prop_door_rotating]] , [[func_physbox|func_physbox]] and perhaps others entites which may break your flow if you have it set to "Affects Flow: Yes."}} | {{note| In l4d2, func_nav_blocker behaves slightly different then in L4D1. To block a nav area, you must use a [[logic_relay|logic_relay]] triggered by a [[logic_auto|logic_auto]] on map spawn and send an ''unblocknav'' input to all func_nav_blockers, then selectively send an input again .5 seconds or so after and block the ones needed. Failure to unblock them before blocking them will produce the error in the console that says "Area # already blocked by a different team id". In l4d2 func_nav_blocker may also ignore your "team(s) to block", and will block both teams if the func_nav_blocker brush resides in a [[prop_door_rotating|prop_door_rotating]] , [[func_physbox|func_physbox]] and perhaps others entites which may break your flow if you have it set to "Affects Flow: Yes."}} | ||
==Keyvalues== | == Keyvalues == | ||
{{KV|Team(s) to block|choices|Team(s) this entity should block}} | |||
:* -1 : Everyone | |||
:* 2 : Survivors | |||
:* 3 : Infected | |||
{{KV|Affects Flow?|boolean|Does this func_nav_blocker block flow in the level? Only func_nav_blockers with this enabled will cause flow recomputation on blocking/unblocking.}} | |||
{{KV Targetname}} | {{KV Targetname}} | ||
{{KV EnableDisable}} | {{KV EnableDisable}} | ||
{{warning|Enabled/disabled state does ''not'' block or unblock NAV areas. Use <code>BlockNav</code>/<code>UnblockNav</code>}} | {{warning|Enabled/disabled state does ''not'' block or unblock NAV areas. Use <code>BlockNav</code>/<code>UnblockNav</code>}} | ||
== Inputs == | |||
==Inputs== | {{IO|BlockNav|Starts blocking nav areas.|param=string}} | ||
{{IO|UnblockNav|Stops blocking nav areas.}} | |||
{{I Targetname}} | {{I Targetname}} | ||
{{I EnableDisable}} | |||
{{I EnableDisable}} | |||
{{warning|Enabled/disabled state does ''not'' block or unblock NAV areas.}} | {{warning|Enabled/disabled state does ''not'' block or unblock NAV areas.}} | ||
==Outputs== | == Outputs == | ||
{{O Targetname}} | {{O Targetname}} | ||
Revision as of 04:17, 12 August 2011
Template:L4d series brush It is a brush entity that can block nav areas touching its AABB used to restrict NPCs from crossing over nav areas.
Note:The entity will NOT start to block automatically: it must first be activated with the BlockNav input.Note: In l4d2, func_nav_blocker behaves slightly different then in L4D1. To block a nav area, you must use a logic_relay triggered by a logic_auto on map spawn and send an unblocknav input to all func_nav_blockers, then selectively send an input again .5 seconds or so after and block the ones needed. Failure to unblock them before blocking them will produce the error in the console that says "Area # already blocked by a different team id". In l4d2 func_nav_blocker may also ignore your "team(s) to block", and will block both teams if the func_nav_blocker brush resides in a prop_door_rotating , func_physbox and perhaps others entites which may break your flow if you have it set to "Affects Flow: Yes."Keyvalues
- Team(s) to block ([todo internal name (i)]) <choices>
- Team(s) this entity should block
- -1 : Everyone
- 2 : Survivors
- 3 : Infected
- Affects Flow? ([todo internal name (i)]) <boolean>
- Does this func_nav_blocker block flow in the level? Only func_nav_blockers with this enabled will cause flow recomputation on blocking/unblocking.
- 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
- Start Disabled (StartDisabled) <boolean>
- Stay dormant until activated (with the
Enableinput).
Warning:Enabled/disabled state does not block or unblock NAV areas. Use BlockNav/UnblockNavInputs
- BlockNav <string>
- Starts blocking nav areas.
- UnblockNav
- Stops blocking nav areas.
EnableDisable:
- Enable / Disable
- Enable/disable this entity from performing its task. It might also disappear from view.
Warning:Enabled/disabled state does not block or unblock NAV areas.