Func nav blocker: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(added warning about diagonal nav blockage)
m (So.... a bounding box)
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 will NOT start to block automatically: it must first be activated with the <code>BlockNav</code> input.}}
{{note|The entity won't block nav areas automatically, it must be given the<code>BlockNav</code>input.}}
{{bug|{{l4d2}} For navigation squares touching your Nav Blocker, if [[prop_door_rotating|prop_door_rotating]], [[func_physbox|func_physbox]], etc. resides on the same squares, UnblockNav along with BlockNav inputs.<br>
{{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}}}}
Otherwise, the console errors "Area navsquare#[ID] already blocked by a different team id. May produce [[L4D_Level_Design/Nav_Flow|flow]] bugs" (Which it does). You can quickly access the faulty nav square by using<code>nav_mark [ID]</code>followed by <code>nav_warp_to_mark</code>. }}
{{warning|This entity blocks navigation areas using its [[bounding box]].}}
{{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 ==
== Keyvalues ==

Revision as of 12:05, 16 July 2021

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

Note.pngNote:The entity won't block nav areas automatically, it must be given theBlockNavinput.
Icon-Bug.pngBug:In Left 4 Dead 2, 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.pngWarning:This entity blocks navigation areas using its bounding box.

Keyvalues

Team(s) to block (teamToBlock) <choices>
Team this entity should block.
  • -1 : Everyone
    Warning.pngWarning:Team Fortress 2 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 Team Fortress 2, Survivors Left 4 Dead seriesLeft 4 Dead series, Terrorists Counter-Strike: Source Counter-Strike: Global Offensive
  • 3 : Blue Team Fortress 2, Infected Left 4 Dead seriesLeft 4 Dead series, Counter-Terrorists Counter-Strike: Source Counter-Strike: Global Offensive
Note.pngNote:Counter-Strike: Global Offensive teamToBlock non-functional, always blocks either for both teams or for no team.
Affects Flow? (affectsFlow) <boolean> (only in Left 4 Dead 2)
Does this Nav Blocker block flow in the level? Only Nav Blocker with this enabled will cause flow recomputation on blocking/unblocking.
Icon-Important.pngImportant: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

Retrieved from "https://developer.valvesoftware.com/w/index.php?title=Func_nav_blocker&oldid=243869"