info_node_climb
...
info_node_climb
is a point entity available in all Source games.
Entity description
A nodegraph and hint node entity, used only by Climbing NPCs. Climb nodes work similarly to func_useableladder, in that there is a bottom point and a top point. Unlike ladders, you instead place two climb nodes to determine the position of these two points. One node at the bottom and another vertically above the bottom one.
Note:In , the top node must be named and it's name must start with
climb_up
or just be named that. Otherwise the node will fail to connect with the bottom node regardless if it's connected with info_node_link or it's counterparts.Keyvalues
Targetname:
- Name
(targetname)
<string> - The targetname that other entities refer to this entity by.
Angles:
- Pitch Yaw Roll (Y Z X)
(angles)
<angle> - This entity's orientation in the world. Pitch is rotation around the Y axis, yaw is the rotation around the Z axis, roll is the rotation around the X axis.
- Hint
(hinttype)
<choices> - Hint type
- 0 : None
- 2 : World: Window
- 12 : World: Act Busy Hint
- 13 : World: Visually Interesting
- 14 : World: Visually Interesting (Don't aim at)
- 15 : World: Inhibit Combine Mines within 15 feet
- 16 : World: Visually Interesting (Stealth mode)
- 100 : Crouch Cover Medium
- 101 : Crouch Cover Low
- 102 : Waste Scanner Spawn
- 103 : Entrance / Exit Pinch
- 105 : Enemy Disadvantage Point
- 106 : Health Kit
- 400 : Antlion: Burrow Point
- 401 : Antlion: Thumper Flee Point
- 450 : Headcrab: Burrow Point
- 451 : Headcrab: Exit Pod Point
- 500 : Roller: Patrol Point
- 501 : Roller: Cleanup Spot
- 700 : Crow: Fly to point
- 701 : Crow: Perch point
- 900 : Follower: Wait point
- 901 : Override jump permission
- 902 : Player squad transition point
- 903 : NPC exit point
- 904 : Strider node
- 950 : Player Ally: Push away destination
- 951 : PLayer Ally: Fear withdrawal destination
- 1000 : HL1 World: Machinery
- 1001 : HL1 World: Blinking Light
- 1002 : HL1 World: Human Blood
- 1003 : HL1 World: Alien Blood
- Hint Activity
(hintactivity)
<string> - Activity associated with this hint node. Various parts of the NPC AI play this activity at times. i.e. Actbusy nodes will play this activity when an NPC acts busy on the node.
- Node FOV
(nodeFOV)
<choices> - Imagine this node requires that an NPC be in the node's field of view in order to use this hint.
- 45 : 45 Degrees
- 90 : 90 Degrees
- 180 : 180 Degrees
- 360 : 360 Degrees
- Start Hint Disabled
(StartHintDisabled)
<boolean> - Spawn the hint disabled.
- Hint Group
(Group)
<string> - If specified, gives the hint a specific group name. Useful for hint nodes that need to be logically grouped together. NPCs may also refuse to use hint nodes that don't match their hint group.
- Target node
(TargetNode)
<node_dest> - The node ID of an associated target node, if any.
- Ignore Facing
(IgnoreFacing)
<choices> - Don't pay attention to the facing of the node. May not apply to a given hint type.
- 0 : No
- 1 : Yes
- 2 : Default
- Radius
(???)
<integer> - Allows hints to only be usable in a pre-defined radius(in all games since )(also in )
- Weight
(???)
<integer> - Allows NPCs to prefer certain hints over others (only in )
- Minimum State
(MinimumState)
<choices> - Require an NPC have a minimum state to use the hint.
- 1 : Idle
- 2 : Alert
- 3 : Combat
- Maximum State
(MaximumState)
<choices> - Require an NPC have a maximum state to use the hint.
- 1 : Idle
- 2 : Alert
- 3 : Combat
- Node ID
(nodeid)
<integer> - Read-only internal Hammer value.
Flags
- [
65536
] : Allow jump up
Inputs
Base:
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"
|
ClearContext
- Removes all contexts from this entity's list.
ClearParent
- Removes this entity from the the movement hierarchy, leaving it free to move independently.
FireUser1
toFireUser4
- Fires the respective
OnUser
outputs; see User Inputs and Outputs.
Kill
- Removes this entity and any entities parented to it from the world.
KillHierarchy
- Functions the same as
Kill
, although this entity and any entities parented to it are killed on the same frame, being marginally faster thanKill
input.
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.
DispatchResponse
<string> !FGD- Dispatches a response to the entity. See Response and Concept.
DispatchEffect
<string> (removed since ) !FGD- Dispatches a special effect from the entity's origin; See also List of Client Effects. Replaced by the particle system since .
RunScriptFile
<script> (in all games since ) (also in )- 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 ) (also in )- 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. Bug:In Hammer, using string arguments will corrupt the VMF file's structure, making the file unviewable for the next Hammer session.Fix:Remove the string argument manually with a text editor.
CallScriptFunction
<string> (in all games since ) (also in ) !FGD- Calls a VScript function defined in the scope of the receiving entity.
TerminateScriptScope
(only in ) !FGD- Destroys the script scope of the receving entity.
SetLocalOrigin
<coordinates> (in all games since ) !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.
HintNode:
EnableHint
- Enable hint.
DisableHint
- Disable hint.
Outputs
Targetname:
OnUser1
toOnUser4
- These outputs each fire in response to the firing of the like-numbered
FireUser1
toFireUser4
Input; see User Inputs and Outputs.