Func nav blocker

Template:Brush ent Also in . It blocks nav areas touching its AABB to restrict NPCs / Bots from crossing over it.

Note:The entity will NOT start to block automatically: it must first be activated with the BlockNav input.

Bug: For navigation squares touching your Nav Blocker, if prop_door_rotating, func_physbox, etc. resides on the same squares, UnblockNav along with BlockNav inputs.
Otherwise, the console errors "Area navsquare#[ID] already blocked by a different team id. May produce flow bugs" (Which it does). You can quickly access the faulty nav square by usingnav_mark [ID]followed by nav_warp_to_mark.   [todo tested in ?]

Warning:Diagonal navigation mesh blockage with one large brush will not work. It artificially creates a box around the entire diagonal brush and turns that area into a Func_nav_blocker! To block paths diagonally, create multiple smaller Func_nav_blocker squares in a diagonal line so that each little brush blocks only the nav squares it stands on.

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

Note: teamToBlock non-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.

See Also

• script_nav_blocker - VScript catered version of func_nav_blocker.