Func nav blocker: Difference between revisions

Revision as of 11:02, 3 August 2023

Class hierarchy
CFuncNavBlocker ↳CBaseEntity
`nav_entities.cpp`

Template:Entity and also in . It blocks nav areas touching its AABB to restrict NPCs / Bots from crossing over it. Template:ModernBug Template:ModernNote Template:ModernWarning

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

Start Disabled (StartDisabled) <boolean> (not in ): If set to false nav areas will be blocked right after spawning.

@@ Line 1: / Line 1: @@
 {{lang|title=func_nav_blocker}}
+{{CD|CFuncNavBlocker|file1=nav_entities.cpp}}
 {{entity|func_nav_blocker|type=e2|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.
 {{ModernBug|In {{l4d2}}, If{{ent|prop_door_rotating}}, {{ent|func_physbox}}, {{ent|func_door}}, etc 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 edit: Bug is real, however fix appears to be ineffective}}