path_corner

GoldSrc

Source Engine

This entity is not in the FGD by default.
See below for instructions on making it available.

path_corner is a point entity available in all Source games.

Class hierarchy
CPathCorner ↳CPointEntity ↳CBaseEntity
pathcorner.cpp

Clarify: path_track vs path_corner

Entity description

Notes

• A path_corner is a corner in a path, either for a func_train or an NPC. path_corners can be chained together to form complex routes. To create a path_corner chain simply shift+drag an existing path_corner. The values will automatically be filled in. To manually make a chain (or link one up in a circle), edit the Next stop target property.
• A path_corner_crash is identical to a path_corner, but can be enabled and disabled for a crash point; when an NPC is searching for a crash point, it will not search for generic path_corners

NPCs

A path_corner can be a destination for an NPC. When told to, NPCs will stop other movement and walk steadily towards a path_corner. It is entirely scripted behavior. Note that the Train Speed and wait values do not affect NPCs.

To make an NPC move to a path_corner edit the Target Path Corner keyvalue, either in Hammer or through the I/O system. Alternatively, an NPC can be made to follow a path_corner chain by using the aiscripted_schedule or scripted_sequence entities.

• See also Assaults for an alternative way to create NPC routes without using path_corner.

Limitations and bugs

• A path_corner (or the first path_corner on a chain) must be within 576 units for NPCs to find it.
• It is either difficult or impossible to tell an NPC which direction to face once they've reached a path corner. If this is important, you may want to consider using Assaults instead.

Examples

• See the apc_on_path and the npc_scanner_on_path prefabs for examples on usage.
• Download Example (VMF)

Note that the example map does not have any info_nodes. They are not needed to have an NPC follow a path.

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

Next stop target (target) <string>

Wait here (secs) (wait) <float>

New train speed (speed) <float>

Leave at zero to leave path follower's speed the same

Flags

Wait for retrigger : [1]

Teleport to THIS path_corner : [2]

Inputs

SetNextPathCorner <targetnameRedirectInput/string>

Set target path_corner

InPass  !FGD

Called internally by game

Outputs

OnPass

!activator = activator of the InPass input, usually the train
!caller = caller of the InPass input, usually the train
Fires when a path follower passes this point.

FGD Code

The path_corner entity is not in defined the base.fgd that all games share. It only exists in the halflife2.fgd.
You may copy the FGD entry from the expand box below to the bottom of your base.fgd to make it appear in Hammer.

FGD entry from halflife2.fgd 

@PointClass base(Targetname, Angles) size(16 16 16) line(255 255 255, targetname, target) color(247 181 82) = path_corner : "Generic path point"
[
	spawnflags(Flags) =
	[
		1: "Wait for retrigger" : 0
		2: "Teleport to THIS path_corner" : 0
	]
	target(target_destination) : "Next stop target"
	wait(integer) : "Wait here (secs)" : 0
	speed(integer) : "New Train Speed" : 0
	yaw_speed(integer) : "New Train rot. Speed" : 0

	// Inputs 
	input SetNextPathCorner(string) : "Sets next pathcorner"

	// Outputs
	output OnPass(void) : "Fires when a path follower passes this point"
]

See also

• path_track