Func nav attribute region: Difference between revisions
Jump to navigation
Jump to search
Tip:In
, Attributes are automatically applied after this entity spawns in, which is also every new round.
Note:Attributes set will persists when a round ends!
mNo edit summary |
(-rearange, notoc) |
||
Line 1: | Line 1: | ||
__NOTOC__ | |||
{{Lang|title=func_nav_attribute_region}} | {{Lang|title=func_nav_attribute_region}} | ||
{{CD|CFuncNavAttributeRegion}} | {{CD|CFuncNavAttributeRegion}} | ||
Line 7: | Line 8: | ||
==Keyvalues== | ==Keyvalues== | ||
{{KV Targetname}} | |||
{{KV NavAttributeRegion}} | {{KV NavAttributeRegion}} | ||
{{ | |||
==Inputs== | |||
{{I NavAttributeRegion}} | |||
==Flags== | ==Flags== | ||
{{Fl NavAttributeRegion}} | {{Fl NavAttributeRegion}} | ||
==See Also== | ==See Also== |
Revision as of 07:56, 19 August 2023
![]() |
---|
CFuncNavAttributeRegion |
Template:Entity It holds nav attributes to be applied on regions of overlapping nav areas when a navigation mesh has finished generating with nav_generate
/nav_generate_incremental
. Great for attributes necessitated by large regions of nav areas; e.g. TheFINALE
attribute.



Keyvalues
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentname
ortarget
).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities