Info landmark: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
1416006136 (talk | contribs) (use {{lang}}) |
||
| Line 1: | Line 1: | ||
{{ | {{lang|Info landmark|title={{MdCode|oneclick|background=transparent|info_landmark}}}} | ||
{{subpage|[[Level Transitions]]}} | {{subpage|[[Level Transitions]]}} | ||
__NOTOC__ | __NOTOC__ | ||
| Line 12: | Line 12: | ||
{{clr}}{{CD|CPointEntity|file1=subs.cpp}} | {{clr}}{{CD|CPointEntity|file1=subs.cpp}} | ||
{{clr}} | |||
==Keyvalues== | ==Keyvalues== | ||
Revision as of 08:52, 10 January 2023
| info_landmark | |
|---|---|
 | |
| Type | Point entity |
| Engine |  Source |
| Availability | In all games |
It acts as a landmark for Level Transitions. 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.
 Class hierarchy
|
|---|
| CPointEntity |
| subs.cpp
|
Keyvalues
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentnameortarget).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
See also
- Level Transitions
- info_landmark
- trigger_changelevel
- trigger_transition
- point_changelevel (only in
) - info_changelevel (only in
)