Func nav blocker: Difference between revisions
Jump to navigation
Jump to search
Note:The entity will NOT start to block automatically: it must first be activated with the
Bug:
When you make the func_nav_blocker block the navigation squares touching it, you must send UnblockNav along with BlockNav if the func_nav_blocker resides on the same navigation square(s) as a prop_door_rotating or func_physbox and perhaps others entities. Failure to do so will create the console error "Area navsquare# already blocked by a different team id. May produce flow bugs" ( Which is does). The navigation square numbers can be seen in-game by pointing at the nav square with z_debug 1 and nav_edit 1. [todo tested in ?]
m (Added tf2 to available games list) |
(SAlso, yeah I see that todo about templates to display the games, but how would go on to do that in a tidy manner?) |
||
| Line 2: | Line 2: | ||
{{todo|Any other games?}} | {{todo|Any other games?}} | ||
{{todo|Use templates to display which games include this entity. (But how would we accomplish this?)}} | |||
{{todo|Use templates to display which games include this entity.}} | |||
{{note|The entity will NOT start to block automatically: it must first be activated with the <code>BlockNav</code> input.}} | {{note|The entity will NOT start to block automatically: it must first be activated with the <code>BlockNav</code> input.}} | ||
{{bug| | {{bug|{{l4d2}} When you make the func_nav_blocker block the navigation squares touching it, you must send UnblockNav along with BlockNav if the func_nav_blocker resides on the same navigation square(s) as a [[prop_door_rotating|prop_door_rotating]] or [[func_physbox|func_physbox]] and perhaps others entities. Failure to do so will create the console error "Area navsquare# already blocked by a different team id. May produce [[L4D_Level_Design/Nav_Flow|flow]] bugs" ( Which is does). The navigation square numbers can be seen in-game by pointing at the nav square with z_debug 1 and nav_edit 1. }} | ||
== Keyvalues == | == Keyvalues == | ||
{{KV | {{KV NavBlocker}} | ||
== Inputs == | == Inputs == | ||
{{I NavBlocker}} | |||
{{I | |||
== Outputs == | == Outputs == | ||
{{O | {{O BaseEntity}} | ||
Revision as of 11:25, 16 March 2021
Available in 
. It is a brush entity that can block nav areas touching its AABB used to restrict NPCs from crossing over nav areas.
Todo: Any other games?
Todo: Use templates to display which games include this entity. (But how would we accomplish this?)
Note:The entity will NOT start to block automatically: it must first be activated with the BlockNav input.Bug: When you make the func_nav_blocker block the navigation squares touching it, you must send UnblockNav along with BlockNav if the func_nav_blocker resides on the same navigation square(s) as a prop_door_rotating or func_physbox and perhaps others entities. Failure to do so will create the console error "Area navsquare# already blocked by a different team id. May produce flow bugs" ( Which is does). The navigation square numbers can be seen in-game by pointing at the nav square with z_debug 1 and nav_edit 1. [todo tested in ?]
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.