Func nav blocker: Difference between revisions
Jump to navigation
Jump to search
Note:The entity won't block nav areas automatically (except in 
), it must be given the
Bug:In 
, Ifprop_door_rotatingorfunc_physboxresides on the same areas, send an
Warning:This entity blocks navigation areas using its bounding box.
m (So.... a bounding box) |
(CS:GO: Does block initially on round start. Best practice: Fire either BlockNav or UnBlockNav OnMapSpawn.) |
||
| Line 1: | Line 1: | ||
{{brush ent|since=Left 4 Dead}} Also in {{tf2}}. It blocks [[NAV|nav]] areas touching its [[Bounding volume|AABB]] to restrict NPCs / Bots from crossing over it. | {{brush ent|since=Left 4 Dead}} Also in {{tf2}}. It blocks [[NAV|nav]] areas touching its [[Bounding volume|AABB]] to restrict NPCs / Bots from crossing over it. | ||
{{note|The entity won't block nav areas automatically, it must be given the<code>BlockNav</code>input.}} | {{note|The entity won't block nav areas automatically (except in {{csgo}}), it must be given the<code>BlockNav</code>input. It is best practice to have either <code>BlockNav</code> or <code>UnblockNav</code> fired <code>[[logic auto|OnMapSpawn]]</code>.}} | ||
{{bug|In {{l4d2}}, If{{ent|prop_door_rotating}}or{{ent|func_physbox}}resides on the same areas, send an<code>UnblockNav</code>input along a<code>BlockNav</code>input. Else the console reports "Area navsquare#[ID] already blocked by a different team ID.{{confirm}}}} | {{bug|In {{l4d2}}, If{{ent|prop_door_rotating}}or{{ent|func_physbox}}resides on the same areas, send an<code>UnblockNav</code>input along a<code>BlockNav</code>input. Else the console reports "Area navsquare#[ID] already blocked by a different team ID.{{confirm}}}} | ||
{{warning|This entity blocks navigation areas using its [[bounding box]].}} | {{warning|This entity blocks navigation areas using its [[bounding box]].}} | ||
Revision as of 08:08, 25 August 2021
Template:Brush ent Also in 
. It blocks nav areas touching its AABB to restrict NPCs / Bots from crossing over it.
Note:The entity won't block nav areas automatically (except in ), it must be given theBlockNavinput. It is best practice to have either BlockNav or UnblockNav fired OnMapSpawn.Bug:In , Ifprop_door_rotatingorfunc_physboxresides on the same areas, send anUnblockNavinput along aBlockNavinput. Else the console reports "Area navsquare#[ID] already blocked by a different team ID.[confirm] [todo tested in ?]Warning:This entity blocks navigation areas using its bounding box.Keyvalues
- Team(s) to block (teamToBlock) <choices>
- Team this entity should block.
- -1 : Everyone Warning: for everyone either edit FGD and use value -2 or turn off smart edit and set that, -1 is not valid and the nav blocker will not work
- 2 : Red , Survivors
, Terrorists 
- 3 : Blue , Infected , Counter-Terrorists
- -1 : Everyone
- Note:
teamToBlocknon-functional, always blocks either for both teams or for no team.
- Affects Flow? (affectsFlow) <boolean> (only in )
- Does this Nav Blocker block flow in the level? Only Nav Blocker with this enabled will cause flow recomputation on blocking/unblocking.
Important:When this is true don't block the only path to the level's goal with it or the flow won't be computed properly
Inputs
- BlockNav
- Starts blocking nav areas.
- UnblockNav
- Stops blocking nav areas.
Outputs
See Also
- script_nav_blocker - VScript catered version of func_nav_blocker.