Info landmark: Difference between revisions
Jump to navigation
Jump to search
(Cleanup) |
mNo edit summary |
||
Line 1: | Line 1: | ||
{{base point|info_landmark|sprite=1}} It acts as a landmark for transitions to another level. There should be a corresponding '''info_landmark''' entity in the next map. Entities will be transitioned to the next level relative to the info_landmark entities. | |||
{{base point|info_landmark}} It acts as a landmark for transitions to another level. There should be a corresponding '''info_landmark''' entity in the next map. Entities will be transitioned to the next level relative to the info_landmark entities. | |||
{{in code|class=class_c_point_entity.html CPointEntity|file=subs_8cpp-source.html subs.cpp}} | {{in code|class=class_c_point_entity.html CPointEntity|file=subs_8cpp-source.html subs.cpp}} |
Revision as of 17:25, 30 July 2011
Template:Base point It acts as a landmark for transitions to another level. There should be a corresponding info_landmark entity in the next map. Entities will be transitioned to the next level relative to the info_landmark entities.
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