Func nav blocker: Difference between revisions
Jump to navigation
Jump to search
Bug:In 
, Ifprop_door_rotatingorfunc_physboxresides on the same areas, send an
Note:The entity won't block nav areas automatically on spawn (except in 
). It is best practice to have either
Note:This entity blocks navigation areas using its bounding box! Complex brush models will not work.
m (edit revert; edit rephrase; OnMultiNewRound (OnMapSpawn is only when the map first loads)) |
1416006136 (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
{{brush ent|since=Left 4 Dead}} and also in {{tf2}}. It blocks [[Navigation Meshes|nav areas]] touching its [[Bounding volume|AABB]] to restrict NPCs / Bots from crossing over it. | {{lang|Func nav blocker}} | ||
{{brush ent|func_nav_blocker|since=Left 4 Dead}} and also in {{tf2}}. It blocks [[Navigation Meshes|nav areas]] touching its [[Bounding volume|AABB]] to restrict NPCs / Bots from crossing over it. | |||
{{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}}}} | ||
{{note|The entity won't block nav areas automatically on spawn (except in {{csgo}}). It is best practice to have either<code>BlockNav</code>or<code>UnblockNav</code>inputs sent with<code>[[logic auto|OnMultiNewRound]]</code>.}} | {{note|The entity won't block nav areas automatically on spawn (except in {{csgo}}). It is best practice to have either<code>BlockNav</code>or<code>UnblockNav</code>inputs sent with<code>[[logic auto|OnMultiNewRound]]</code>.}} | ||
Revision as of 20:02, 19 September 2021
Template:Brush ent and also in 
. It blocks nav areas touching its AABB to restrict NPCs / Bots from crossing over it.
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 ?]Note:The entity won't block nav areas automatically on spawn (except in ). It is best practice to have eitherBlockNavorUnblockNavinputs sent withOnMultiNewRound.Note:This entity blocks navigation areas using its bounding box! Complex brush models will not work.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
- Start Disabled (StartDisabled) <boolean>
- Stay dormant until activated (with the
Enableinput).
Inputs
- BlockNav
- 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.
Outputs
See Also
- script_nav_blocker - VScript catered version of func_nav_blocker.