Info landmark: Difference between revisions
Jump to navigation
Jump to search
In code, it is represented by the
mNo edit summary |
(Added Lang template. Added back button. Added links. Code links were 404.) |
||
| Line 1: | Line 1: | ||
{{base point|info_landmark|sprite=1}} It acts as a landmark for | {{lang|info_landmark}} | ||
{{toc-right}} | |||
{{back|Level Transitions}} | |||
{{base point|info_landmark|sprite=1}} | |||
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. | |||
{{ | {{code class|CPointEntity|subs.cpp}} | ||
==Keyvalues== | ==Keyvalues== | ||
| Line 15: | Line 17: | ||
== See also == | == See also == | ||
* [[Level Transitions]] | |||
* [[info_landmark]] | |||
* [[trigger_changelevel]] | * [[trigger_changelevel]] | ||
* [[trigger_transition]] | |||
* [[point_changelevel]] {{only|{{portal2}}}} | |||
* [[info_changelevel]] {{only|{{l4ds}}}} | |||
Revision as of 20:38, 16 October 2021
Template:Base point 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.
In code, it is represented by theCPointEntityclass, defined in thesubs.cppfile.
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
Inputs
Outputs
See also
- Level Transitions
- info_landmark
- trigger_changelevel
- trigger_transition
- point_changelevel (only in
) - info_changelevel (only in
)