Trains: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
m (removing abstract mapping header)
Line 21: Line 21:
* Trains must be constructed facing east (in the Top viewport of Hammer, this is facing right) otherwise they will be pointing the wrong direction in-game. They will turn themselves to face the correct direction.
* Trains must be constructed facing east (in the Top viewport of Hammer, this is facing right) otherwise they will be pointing the wrong direction in-game. They will turn themselves to face the correct direction.
* You don't need to create each {{ent|path_track}} by hand. Create the first one, then <code>Shift-drag</code> it to create another; the new one will be automatically linked from the previous one. This works even for inserting new {{ents|path_track|s}} between existing ones.
* You don't need to create each {{ent|path_track}} by hand. Create the first one, then <code>Shift-drag</code> it to create another; the new one will be automatically linked from the previous one. This works even for inserting new {{ents|path_track|s}} between existing ones.
* For Team Fortress 2 mappers: If you wish to duplicate the trains as seen in CP Well, it is necessary to parent a [[trigger_hurt]] to a func_tracktrain, as trains will not normally hurt on touch. To get the "killed by train" icon in the killbar, the damage type must be set to freeze.


== See Also ==
== See Also ==

Revision as of 09:35, 24 April 2009

This page is about Source train entities. Train entities move along a predetermined track, and can look represent anything that moves.

Entities

Main entities

Other entities

Entities not in the FGD

Notes

  • If you want a prop to behave as a train, parent it to an invisible func_tracktrain.
  • Trains must be constructed facing east (in the Top viewport of Hammer, this is facing right) otherwise they will be pointing the wrong direction in-game. They will turn themselves to face the correct direction.
  • You don't need to create each path_track by hand. Create the first one, then Shift-drag it to create another; the new one will be automatically linked from the previous one. This works even for inserting new path_tracks between existing ones.
  • For Team Fortress 2 mappers: If you wish to duplicate the trains as seen in CP Well, it is necessary to parent a trigger_hurt to a func_tracktrain, as trains will not normally hurt on touch. To get the "killed by train" icon in the killbar, the damage type must be set to freeze.

See Also