This article's documentation is for anything that uses the Source engine. Click here for more information.


From Valve Developer Community
Jump to: navigation, search
English (en)
... Icon-Important.png

info_node_link is a point entity available in all Source Source games. It is a manually defined, dynamic connection between two navigation nodes. This could be used to create or destroy a connection in the nodegraph because of some event in your map (a bridge being created/destroyed, etc).


Start node ID (StartNode) <node_dest>
The node ID of one end of the node connection.
End node ID (EndNode) <node_dest>
The node ID of one end of the node connection.
Initial State (initialstate) <choices>
Makes this connection is available the moment the map loads. If there is something blocking the NPC's path while this is on, the NPC may appear to walk straight into that object/hole.
  • 0 : Off
  • 1 : On
Type of Connection (linktype) <choices>
How NPCs can use this node. Not all NPCs can do all types.
  • 1 : Ground
  • 2 : Jump
  • 4 : Fly
  • 8 : Climb
Allow Pass When Off (AllowUse) <string>
Entity or class to allow passage even when node is off

{{KV|Invert exclusion rules|intn=InvertAllow|boolean|Allowed entity is the only entity NOT allowed when this is set to 'yes'

Icon-Bug.pngBug:Non-functional. Use info_node_link_controller instead if this keyvalue is needed.
Name (targetname) <string>
The targetname that other entities refer to this entity by.


See: NPC Hull.

  • 1 : Force human connect
  • 2 : Force small_centered connect
  • 4 : Force wide_human connect
  • 8 : Force tiny connect
  • 16 : Force wide_short connect
  • 32 : Force medium connect
  • 64 : Force tiny_centered connect
  • 128 : Force large connect
  • 256 : Force large_centered connect
  • 512 : Force medium_tall connect


Turn the link on.
Turn the link off.

AddContext <string>
Adds to the entity's list of response contexts. See Context.
AddOutput <string>
Assigns a new keyvalue/output on this entity. For keyvalues, some rely on extra necessary code to be ran and won't work if its simply just changed through this input. There is a strict format that must be followed:
// Format of changing KeyValues: "AddOutput [key] [value]"
//// Raw text:
"OnUser1" "!self,AddOutput,targetname new_name"

// Format of adding an Output: "AddOutput {targetname}:{inputname}:{parameter}:{delay}:{max times to fire, -1 means infinite}"
//// Raw text:
"OnUser1" "!self,AddOutput,OnUser1:SetParent:!activator:0.0:-1"
// Arguments can be left blank, but the empty blank should still be contained.
//// Raw text:
"OnUser1" "!self,AddOutput,OnUser1:ClearParent::0.0:-1"
Removes all contexts from this entity's list.
Removes this entity from the the movement hierarchy, leaving it free to move independently.
FireUser1 to FireUser4
Fires the respectiveOnUseroutputs; see User Inputs and Outputs.
Removes this entity and any entities parented to it from the world.
Functions the same as Kill, although this entity and any entities parented to it are killed on the same frame, being marginally faster thanKillinput.
RemoveContext <string>
Remove a context from this entity's list. The name should match the key of an existing context.
SetParent <string>
Move with this entity. See Entity Hierarchy (parenting).
SetParentAttachment <string>
Change this entity to attach to a specific attachment point on its parent. The entity will teleport so that the position of its root bone matches that of the attachment. Entities must be parented before being sent this input.
SetParentAttachmentMaintainOffset <string>
As above, but without teleporting. The entity retains its position relative to the attachment at the time of the input being received.
Use  !FGD
Same as a player invoking +use; no effect in most cases.
DispatchResponse <string> !FGD
Dispatches a response to the entity. See Response and Concept.
DispatchEffect <string> (removed since Left 4 Dead) !FGD
Dispatches a special effect from the entity's origin; See also List of Client Effects. Replaced by the particle system since Left 4 Dead.
RunScriptFile <script> (in all games since Left 4 Dead 2) (also in Team Fortress 2)
Execute a VScript file from disk, without file extension. The script contents are merged with the script scope of the receiving entity.
RunScriptCode <string> (in all games since Left 4 Dead 2) (also in Team Fortress 2)
Execute a string of VScript source code in the scope of the entity receiving the input. String quotation may be needed when fired via console.
Icon-Bug.pngBug:In Hammer, using string arguments will corrupt the VMF file's structure, making the file unviewable for the next Hammer session.
Note.pngFix:Remove the string argument manually with a text editor.
Note.pngNote:Team Fortress 2 Backtick characters ` are replaced with quotation marks at runtime, allowing quotation marks to be used when normally not possible.
CallScriptFunction <string> (in all games since Left 4 Dead 2) (also in Team Fortress 2) !FGD
Calls a VScript function defined in the scope of the receiving entity.
TerminateScriptScope  (only in Team Fortress 2) !FGD
Destroys the script scope of the receving entity.
SetLocalOrigin <coordinates> (in all games since Alien Swarm) !FGD
Send this entity to a spot in the map. If the entity is parented to something, it will be offset from the parent by this amount.
SetLocalAngles <angles> (in all games since Alien Swarm) !FGD
Set this entity's angles.


OnUser1 to OnUser4
These outputs each fire in response to the firing of the like-numbered FireUser1 to FireUser4 Input; see User Inputs and Outputs.
OnKilled  (only in Left 4 Dead)
This output fires when the entity is killed and removed from the game.

See also

  • info_node_link_controller - manages all connections between nodes that intersect the controller's volume. This allows for mass enabling/disabling of all node connections.