Info node: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
m (Found the example .vmf in an old DVD of mine and added it back as a downloadable file.)
m (→‎top: clean up, replaced: {{Language subpage → {{langsp)
Line 1: Line 1:
{{Language subpage|title=info_node}}{{infotable
{{langsp|title=info_node}}{{infotable
|Info node
|Info node
|img=[[Image:info_node.png|256px]]
|img=[[Image:info_node.png|256px]]

Revision as of 01:11, 4 January 2024

English (en)Translate (Translate)
Info node
Info node.png
TypePoint entity
EngineSource Source
AvailabilityIn all games
 

Template:Entity

Entity description

It is a ground navigation node for ground moving NPCs. Navigation nodes are baked into the nodegraph so that NPCs can move to them.

  • Ground nodes fall to the ground when they spawn, so you can place them up to 128 units above any solid world geometry, which excludes func_brush, and they will still work.
  • When placing nodes on displacements, place them slightly above the terrain to ensure connections are properly made. Use the Transform tool (Ctrl+M) to move many nodes quickly.
  • Nodes have a maximum connection distance of 720 units apart

Usage

Create an interesting map, place some enemies in it, and run it. Don't kill them straight away but turn on mat_wireframe and watch their actions as you move around. You'll see them, more or less, run straight at you and shoot. This is because they have no bearings in the world other than your position.

Leave the game and lay down info_node entities across the map, preferably at each point where the AI would have to choose what to do, or anywhere the AI might want to go - basically, any important place for the AI. Then recompile and do the same as last time. You should now see them group and attack together if they need to, seek cover, throw grenades at far more suitable times, try to get around you and more - all because you added a few nodes.

This alone has fully set up your AI for a map.

Note.pngNote:If, for some reason, your NPCs are not moving to the nodes or are simply not moving at all despite the existence of nodes, the first thing you want to try is to add a few hint nodes with contextual information like Crouch Cover Low. If they are not moving to those nodes either, then the game did not build or rebuild the node graph data. In order to get them to build automatically at every new compile you make, create an autoexec.cfg in your cfg folder and add ai_norebuildgraph 0. You may also use the command map_edit right after compiling your map, as this command will force the nodes to rebuild when you edit, add or remove nodes while in-game. Check the nodegraph page for a full explanation on nodegraph usage.

Keyvalues

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

Node ID (nodeid) <integer>
Read-only internal Hammer value.

Flags

Inputs

Outputs

See also

Download Example (VMF)