path_corner Last edited 4 weeks ago2024-10-07 14:13:33 UTC

path_corner - Point Entity

Attributes

• Name (targetname) - Property used to identify entities.
• Pitch Yaw Roll (angles) - Sets the pitch (up / down), yaw (left / right) and roll (bank) respectively. The compass in Hammer corresponds to Yaw. Used by Apaches and Ospreys to orient themselves in flight. [A/O]
• Next stop target (target) - Name of the next path_corner in the path. [A/O/M/G/T]
• Fire On Pass (message) - Trigger this event when this path_corner is passed by a func_train using the path (blah!). [G/T]
• Wait here (wait) - Makes a func_train wait for this number of seconds before moving to next path_corner. [G/T]
• New Train Speed (speed) - Set new speed for the Osprey or func_train once it passes this path_corner. [O/T]

Flags

• Wait for retrigger (1) - func_train entity will wait and will only continue when triggered. [T]
• Teleport (2) - Makes a func_train entity teleport to the current path_corner. [T]
• Fire once (4) - The entity will only fire the path's "Fire On Pass" target once. [G/T]

Notes

• It's a good idea to establish a simple path_corner naming convention. E.g. mypath1_1, mypath1_2, mypath1_3...
• A better idea is to use the level editor's path tool if available. This greatly reduces the chore of manually naming every single entity and its targets. The generated entities follow the above advice as well.
• Only unnamed monsters would follow path_corners, and once they are interrupted, they would not proceed to the next path_corner anymore. It makes sense to think of path_corners as "patrol paths" for monsters, where anything that raises alert makes them stop their rounds. scripted_sequence offer more control and are more reliable.
• A trigger_changetarget can be used to make a func_guntarget or func_train move to a specific path_corner, regardless of which path_corner they're currently heading towards.