Func tanktrain: Difference between revisions
Jump to navigation
Jump to search
Note:Other
(-added class hierarchy, cleanup) |
mNo edit summary |
||
Line 1: | Line 1: | ||
{{distinguish|func_tracktrain}} | {{distinguish|func_tracktrain}} | ||
{{ | {{CD|CFuncTankTrain|file1=1}} | ||
{{this is a|brush entity|name=func_tanktrain}} It was meant to be a train that follows a target entity (such as the player). It was never finished and doesn't work correctly. | {{this is a|brush entity|name=func_tanktrain}} It was meant to be a train that follows a target entity (such as the player). It was never finished and doesn't work correctly. | ||
Revision as of 13:05, 2 September 2024
Not to be confused with func_tracktrain.
![]() |
---|
CFuncTankTrain |
![]() |
func_tanktrain
is a brush entity available in all Source games. It was meant to be a train that follows a target entity (such as the player). It was never finished and doesn't work correctly.
It was meant to be used in combination with a tanktrain_ai entity.
Keyvalues
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentname
ortarget
).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
- Health (health) <integer>
- Health of the tank.
Outputs
- OnDeath
- Fired when the tank is killed.
Bug:This entity can never die without code modification. (See talk page) [todo tested in ?]

Keyvalues / Inputs / Outputs
are same as func_tracktrain.