Alpine Level Design - Revision history

Goober: /* HUD Messages */

2026-01-14T03:57:36Z

HUD Messages

← Older revision		Revision as of 03:57, 14 January 2026
Line 126:		Line 126:

	==HUD Messages==		==HUD Messages==
	Magic words can be used in HUD message display (via the ''HUD_Message''' event, and any other reason HUD messages would be rendered) to display dynamic values to the player. The stock game supported the use of magic words in HUD messages for a subset of the controls in the stock game (used in the training mission), but Alpine Faction expands this capability substantially. To use these magic words, simply include their text exactly as written below in the string for your HUD message.		Magic words can be used in HUD message display (via the ''HUD_Message'' event, and any other reason HUD messages would be rendered) to display dynamic values to the player. The stock game supported the use of magic words in HUD messages for a subset of the controls in the stock game (used in the training mission), but Alpine Faction expands this capability substantially. To use these magic words, simply include their text exactly as written below in the string for your HUD message.

	The following is a list of magic words that are available for use by level designers and mod developers in Alpine Faction, as well as what they are translated to when displayed as a HUD message		The following is a list of magic words that are available for use by level designers and mod developers in Alpine Faction, as well as what they are translated to when displayed as a HUD message

Goober: /* Translating Movers */

2025-12-23T13:07:03Z

Translating Movers

← Older revision		Revision as of 13:07, 23 December 2025
Line 47:		Line 47:
	In the stock game, the way values were applied along the mover path was not always intuitive. In Alpine Faction, the travel, acceleration, and deceleration times for a movement segment are always as configured on the starting keyframe for that segment.		In the stock game, the way values were applied along the mover path was not always intuitive. In Alpine Faction, the travel, acceleration, and deceleration times for a movement segment are always as configured on the starting keyframe for that segment.
	* For example, if a mover is moving forward from Keyframe A -> B -> C, and is set to "Ping Pong Once":		* For example, if a mover is moving forward from Keyframe A -> B -> C, and is set to "Ping Pong Once":
	** Time values configured on Keyframe A are used for the movement from A -> B (moving forward)		** Time values configured on Keyframe A are used for the movement from A -> B (moving forward, uses "Departing Travel Time")
	** Time values configured on Keyframe B are used for the movement from B -> C (moving forward)		** Time values configured on Keyframe B are used for the movement from B -> C (moving forward, uses "Departing Travel Time")
	** The mover hits Keyframe C, and because it's set to "Ping Pong Once", it reverses direction and begins moving backwards		** The mover hits Keyframe C, and because it's set to "Ping Pong Once", it reverses direction and begins moving backwards
	** Time values configured on Keyframe C are used for the movement from C -> B (moving backward)		** Time values configured on Keyframe C are used for the movement from C -> B (moving backward, uses "Returning Travel Time")
	** Time values configured on Keyframe B are used for the movement from B -> A (moving backward)		** Time values configured on Keyframe B are used for the movement from B -> A (moving backward, uses "Returning Travel Time")
	** The mover hits Keyframe A, and because it's set to "Ping Pong Once" and has now reached its starting position, it stops. The next time it is activated, it begins moving forward from Keyframe A -> B again.		** The mover hits Keyframe A, and because it's set to "Ping Pong Once" and has now reached its starting position, it stops. The next time it is activated, it begins moving forward from Keyframe A -> B again.

Goober: /* Multiplayer Respawn Points */

2025-12-23T13:03:26Z

Multiplayer Respawn Points

← Older revision		Revision as of 13:03, 23 December 2025
Line 107:		Line 107:
	In the new KOTH, DC, REV, and ESC gametypes, Multiplayer Respawn Points can be associated with control points. This behaviour is further described in [[Mapping with Control Points#Advanced Mechanics\|Mapping with Control Points]].		In the new KOTH, DC, REV, and ESC gametypes, Multiplayer Respawn Points can be associated with control points. This behaviour is further described in [[Mapping with Control Points#Advanced Mechanics\|Mapping with Control Points]].

	Multiplayer Respawn Points can now be toggled on/off with [[RED Event List#~~Respawn_Point_State~~\|Respawn_Point_State]], and the associated team(s) changed with [[RED Event List#~~Modify_Respawn_Point~~\|Modify_Respawn_Point]].		Multiplayer Respawn Points can now be toggled on/off with [[RED Event List#AF_Utility\|Respawn_Point_State]], and the associated team(s) changed with [[RED Event List#AF_General\|Modify_Respawn_Point]].

	==Triggers==		==Triggers==

Goober: /* Multiplayer Respawn Points */

2025-12-23T13:02:11Z

Multiplayer Respawn Points

← Older revision		Revision as of 13:02, 23 December 2025
Line 105:		Line 105:
	The stock game recognized only the first 32 [[RED Objects#Multiplayer Respawn Point\|Multiplayer Respawn Points]] placed in a level. Alpine Faction recognizes the first 2048.		The stock game recognized only the first 32 [[RED Objects#Multiplayer Respawn Point\|Multiplayer Respawn Points]] placed in a level. Alpine Faction recognizes the first 2048.

	In the new KOTH, DC, REV, and ESC gametypes, Multiplayer Respawn Points can be associated with control points. This behaviour is further described in [[~~Mapping_with_Control_Points~~#~~Linking_to_Respawn_Points~~\|Mapping with Control Points]].		In the new KOTH, DC, REV, and ESC gametypes, Multiplayer Respawn Points can be associated with control points. This behaviour is further described in [[Mapping with Control Points#Advanced Mechanics\|Mapping with Control Points]].

	Multiplayer Respawn Points can now be toggled on/off with [[RED Event List#Respawn_Point_State\|Respawn_Point_State]], and the associated team(s) changed with [[RED Event List#Modify_Respawn_Point\|Modify_Respawn_Point]].		Multiplayer Respawn Points can now be toggled on/off with [[RED Event List#Respawn_Point_State\|Respawn_Point_State]], and the associated team(s) changed with [[RED Event List#Modify_Respawn_Point\|Modify_Respawn_Point]].

Goober at 13:01, 23 December 2025

2025-12-23T13:01:34Z

← Older revision		Revision as of 13:01, 23 December 2025
Line 101:		Line 101:

	Note: Relative position '''requires''' you specify a scale and an eye anchor (and of course a skyboox room UID). If you do not specify each of these, ticking the "use relative position" option will have no effect.		Note: Relative position '''requires''' you specify a scale and an eye anchor (and of course a skyboox room UID). If you do not specify each of these, ticking the "use relative position" option will have no effect.

			==Multiplayer Respawn Points==
			The stock game recognized only the first 32 [[RED Objects#Multiplayer Respawn Point\|Multiplayer Respawn Points]] placed in a level. Alpine Faction recognizes the first 2048.

			In the new KOTH, DC, REV, and ESC gametypes, Multiplayer Respawn Points can be associated with control points. This behaviour is further described in [[Mapping_with_Control_Points#Linking_to_Respawn_Points\|Mapping with Control Points]].

			Multiplayer Respawn Points can now be toggled on/off with [[RED Event List#Respawn_Point_State\|Respawn_Point_State]], and the associated team(s) changed with [[RED Event List#Modify_Respawn_Point\|Modify_Respawn_Point]].

	==Triggers==		==Triggers==

Goober: /* Movers */

2025-12-23T12:56:58Z

Movers

@@ Line 38: / Line 38: @@
 ==Movers==
-WIP
+Alpine Faction fixes several issues present in the stock game with movers, and adds some new functionality for mappers. All functionality described in this section is subject to the [[#Advanced options|Legacy movers]] option.
 ==Lighting==

Goober: /* Advanced options */

2025-12-23T12:25:10Z

Advanced options

← Older revision		Revision as of 12:25, 23 December 2025
Line 28:		Line 28:
	These options allow level designers to access new functionality available only in Alpine Faction. The default values for existing levels ensure functionality continues as it always has (legacy compatible), while the default values for new levels enable the new features. You can control them yourself in the Level Properties window.		These options allow level designers to access new functionality available only in Alpine Faction. The default values for existing levels ensure functionality continues as it always has (legacy compatible), while the default values for new levels enable the new features. You can control them yourself in the Level Properties window.
	* '''Legacy Cyclic_Timer events''' - Disable Cyclic_Timer fix, see [[#Fixed Cyclic_Timer\|Fixed Cyclic_Timer]] for more information. Defaults to true for existing levels, false for new levels.		* '''Legacy Cyclic_Timer events''' - Disable Cyclic_Timer fix, see [[#Fixed Cyclic_Timer\|Fixed Cyclic_Timer]] for more information. Defaults to true for existing levels, false for new levels.
	* '''Legacy movers''' - Disable new Alpine mover logic, see [[Movers]] for more information. Defaults to true for existing levels, false for new levels.		* '''Legacy movers''' - Disable new Alpine mover logic, see [[Alpine Level Design#Movers\|Movers]] for more information. Defaults to true for existing levels, false for new levels.
	* '''Player starts with headlamp''' - If true, players of this level can use their headlamp immediately when the level loads (SP only). If false, the player must first be given a headlamp with [[RED Event List#~~Cyclic_Timer~~\|Set_Gameplay_Rule]] before they can use their headlamp. Defaults to true for existing and new levels.		* '''Player starts with headlamp''' - If true, players of this level can use their headlamp immediately when the level loads (SP only). If false, the player must first be given a headlamp with [[RED Event List#Set_Gameplay_Rule\|Set_Gameplay_Rule]] before they can use their headlamp. Defaults to true for existing and new levels.
	* '''Override static mesh ambient light scale''' - If true, use the specified '''New scale value''' as scalar for ambient light applied to static meshes. If false, use the stock game's behaviour, which is a scale of 2.0 when loaded in SP and 3.2 when loaded in MP. Defaults to false for existing and new levels.		* '''Override static mesh ambient light scale''' - If true, use the specified '''New scale value''' as scalar for ambient light applied to static meshes. If false, use the stock game's behaviour, which is a scale of 2.0 when loaded in SP and 3.2 when loaded in MP. Defaults to false for existing and new levels.

Goober at 12:23, 23 December 2025

2025-12-23T12:23:43Z

← Older revision		Revision as of 12:23, 23 December 2025
Line 3:		Line 3:

	This page lists all major differences between normal Red Faction level design and level design for Alpine Levels, as featured in Alpine Faction.		This page lists all major differences between normal Red Faction level design and level design for Alpine Levels, as featured in Alpine Faction.

			*This page is current as of the release of Alpine Faction v1.2.

	==General==		==General==
Line 10:		Line 12:
	Due to features unavailable in those clients, Alpine Levels are '''not''' playable while using other client versions such as any version of Red Faction (official builds), Pure Faction, or Dash Faction.		Due to features unavailable in those clients, Alpine Levels are '''not''' playable while using other client versions such as any version of Red Faction (official builds), Pure Faction, or Dash Faction.

	===~~Testing~~===		===Troubleshooting===
	* '''Multiplayer playtesting''' - In addition to the '''Play''' and '''Play from Camera''' features that have always been available, the Alpine level editor adds a feature to allow you to playtest multiplayer maps in multiplayer. If you click the '''Play (multi)''' button on the top toolbar, the game will launch you into a listen (local) server running your level.
	* '''Troubleshooting goals''' - You can use the <tt>[ dbg_goal GOALNAME ]</tt> console command at any time to query a goal by name and print its current and initial values.		* '''Troubleshooting goals''' - You can use the <tt>[ dbg_goal GOALNAME ]</tt> console command at any time to query a goal by name and print its current and initial values.
	* '''Troubleshooting event and trigger links''' - You can use the <tt>[ debug trigger ]</tt> and <tt>[ debug event ]</tt> console commands at any time (SP only) to draw events and triggers and their links as arrows in the game world. Links from triggers are blue, links from events are purple.		* '''Troubleshooting event and trigger links''' - You can use the <tt>[ debug trigger ]</tt> and <tt>[ debug event ]</tt> console commands at any time (SP only) to draw events and triggers and their links as arrows in the game world. Links from triggers are blue, links from events are purple.

			===Workflow===
			* '''Multiplayer playtesting''' - In addition to the '''Play''' and '''Play from Camera''' features that have always been available, the Alpine level editor adds a feature to allow you to playtest multiplayer maps in multiplayer. If you click the '''Play in multi''' or '''Play in multi (camera)''' buttons on the top toolbar, the game will launch you into a listen (local) server running your level.
			* '''Hotkeys''' - The F9 hotkey now maps to '''Play in multi''' and F10 maps to '''Play in multi (camera)'''
			* '''Object links''' - You can now link to multiple objects at once. When you select multiple objects and press "K", the first object you selected will be linked to all other object you have selected.
			* '''Pixels/meter tiling''' - The maximum configurable value in Preference->Texture has been raised to 8192.

			===Level Properties===
			* '''RFL version''' - Is now displayed in the Level Properties window.
			* '''Fog''' - Default fog colour for newly created levels is now (0, 0, 0) full black instead of the stock game default of (40, 40, 40).
			====Advanced options====
			These options allow level designers to access new functionality available only in Alpine Faction. The default values for existing levels ensure functionality continues as it always has (legacy compatible), while the default values for new levels enable the new features. You can control them yourself in the Level Properties window.
			* '''Legacy Cyclic_Timer events''' - Disable Cyclic_Timer fix, see [[#Fixed Cyclic_Timer\|Fixed Cyclic_Timer]] for more information. Defaults to true for existing levels, false for new levels.
			* '''Legacy movers''' - Disable new Alpine mover logic, see [[Movers]] for more information. Defaults to true for existing levels, false for new levels.
			* '''Player starts with headlamp''' - If true, players of this level can use their headlamp immediately when the level loads (SP only). If false, the player must first be given a headlamp with [[RED Event List#Cyclic_Timer\|Set_Gameplay_Rule]] before they can use their headlamp. Defaults to true for existing and new levels.
			* '''Override static mesh ambient light scale''' - If true, use the specified '''New scale value''' as scalar for ambient light applied to static meshes. If false, use the stock game's behaviour, which is a scale of 2.0 when loaded in SP and 3.2 when loaded in MP. Defaults to false for existing and new levels.

	==Geometry==		==Geometry==
Line 19:		Line 36:

	Similarly, when adding brushes to moving groups during construction of non-Alpine levels, if those brushes have surfaces with textures that tile many times, the brush will be split. This also does not occur when constructing Alpine Levels - you can safely tile textures as much as you like on brushes that either are, or will eventually be, members of moving groups, without it resulting in additional unnecessary faces being added.		Similarly, when adding brushes to moving groups during construction of non-Alpine levels, if those brushes have surfaces with textures that tile many times, the brush will be split. This also does not occur when constructing Alpine Levels - you can safely tile textures as much as you like on brushes that either are, or will eventually be, members of moving groups, without it resulting in additional unnecessary faces being added.

			==Movers==
			WIP

	==Lighting==		==Lighting==
Line 33:		Line 53:
	In Alpine Levels, while you can still make static skyboxes as you always could before if you wish, through the ''Set_Skybox'' event (described below) you can enhance your skyboxes. The key differences are listed below.		In Alpine Levels, while you can still make static skyboxes as you always could before if you wish, through the ''Set_Skybox'' event (described below) you can enhance your skyboxes. The key differences are listed below.

	Note: When making an enhanced skybox, while you still do need to place a ''Room Effect'' in the room that is to be your sky room, you should '''not''' select the "Sky Room" type on the ''Room Effect'' - instead, leave "type" set to "None"~~, or set it to "Liquid Room" if you wish to have a liquid surface in your sky room~~. The UID of the ''Room Effect'' is the skybox room UID you will specify in the properties of the ''Set_Skybox'' event.		Note: When making an enhanced skybox, while you still do need to place a ''Room Effect'' in the room that is to be your sky room, you should '''not''' select the "Sky Room" type on the ''Room Effect'' - instead, leave "type" set to "None". The UID of the ''Room Effect'' is the skybox room UID you will specify in the properties of the ''Set_Skybox'' event.

			===Base Functionality===
			Enhanced skyboxes retain all functionality seen in normal skyboxes, but add:
			* '''Lighting''' - Lightmaps are rendered in surfaces in enhanced skyboxes (Direct3D 11 renderer only). If you do not want lightmaps on your skybox faces, you can set them to fullbright in texture properties.
			* '''Liquid''' - You can set the ''Room Effect'' that designates your enhanced skybox room to type "Liquid Room" if you wish to have a liquid surface in your sky room.

	===Eye Anchor===		===Eye Anchor===
	When setting an enhanced skybox via the ''Set_Skybox'' event, you can specify an "eye anchor" UID. This must be the UID of an ''Anchor_Marker'' event that is inside the skybox room you are using. If you specify a valid "eye anchor" UID, this will be the position from which the sky room will be visible when projected as your skybox. You can also place the ''Anchor_Marker'' in a moving group and move it with keyframes if you wish.		When setting an enhanced skybox via the ''Set_Skybox'' event, you can specify an "eye anchor" UID. This must be the UID of an ''Anchor_Marker'' event that is inside the skybox room you are using. If you specify a valid "eye anchor" UID, this will be the position from which the sky room will be visible when projected as your skybox. You can also place the ''Anchor_Marker'' in a moving group and move it with keyframes if you wish.
Line 84:		Line 110:

	==Events==		==Events==
	===~~Fixes~~===		===Fixed Delay Parameter===
	Outside of Alpine Levels, using the delay parameter with the following stock game events leads to that event breaking - the effect will never apply. In Alpine Levels, the delay parameter can be used on these events without issue - just like any other event.		Outside of Alpine Levels, using the delay parameter with the following stock game events leads to that event breaking - the effect will never apply. In Alpine Levels, the delay parameter can be used on these events without issue - just like any other event.
	* '''Play_Sound'''		* '''Play_Sound'''
Line 91:		Line 117:
	* '''Alarm_Siren'''		* '''Alarm_Siren'''
	* '''Unhide'''		* '''Unhide'''

			===Fixed Cyclic_Timer===
			Normally, the [[RED Event List#Cyclic_Timer\|Cyclic_Timer]] fires twice on its first activation. In Alpine levels, this is fixed so the first activation (like every other activation_ fires only once. (Subject to [[#Advanced options\|Legacy Cyclic_Timer events]] option)

	===Enhanced Functionality===		===Enhanced Functionality===

Goober at 14:09, 17 May 2025

2025-05-17T14:09:21Z

Show changes

Goober: /* AF_General */

2025-04-19T21:31:25Z

AF_General

← Older revision		Revision as of 21:31, 19 April 2025
Line 345:		Line 345:
	\|on = Set configured fog colour.		\|on = Set configured fog colour.
	\|params = * '''Fog color:''' (str1) Specify fog colour to set. Uses the same format as Level Properties - e.g. specifying "<255, 255, 255>" would result in pure white fog.		\|params = * '''Fog color:''' (str1) Specify fog colour to set. Uses the same format as Level Properties - e.g. specifying "<255, 255, 255>" would result in pure white fog.
			}}
			{{Infobox RF1Event
			\|eventname = Set_Light_Color
			\|category = AF_General
			\|description = Sets the colour of dynamic lights
			\|on = Set light colour.
			\|params = * '''Light color:''' (str1) Specify light colour to set. Uses the same format as Light properties - e.g. specifying "<255, 255, 255>" would result in pure white light.
			* '''Random color instead:''' (bool1) If true, generate a random color instead.
	}}		}}
	</div><div style="clear: both;"></div>		</div><div style="clear: both;"></div>

← Older revision		Revision as of 13:02, 23 December 2025
Line 105:		Line 105:
	The stock game recognized only the first 32 [[RED Objects#Multiplayer Respawn Point\|Multiplayer Respawn Points]] placed in a level. Alpine Faction recognizes the first 2048.		The stock game recognized only the first 32 [[RED Objects#Multiplayer Respawn Point\|Multiplayer Respawn Points]] placed in a level. Alpine Faction recognizes the first 2048.

	In the new KOTH, DC, REV, and ESC gametypes, Multiplayer Respawn Points can be associated with control points. This behaviour is further described in [[~~Mapping_with_Control_Points~~#~~Linking_to_Respawn_Points~~\|Mapping with Control Points]].		In the new KOTH, DC, REV, and ESC gametypes, Multiplayer Respawn Points can be associated with control points. This behaviour is further described in [[Mapping with Control Points#Advanced Mechanics\|Mapping with Control Points]].

	Multiplayer Respawn Points can now be toggled on/off with [[RED Event List#Respawn_Point_State\|Respawn_Point_State]], and the associated team(s) changed with [[RED Event List#Modify_Respawn_Point\|Modify_Respawn_Point]].		Multiplayer Respawn Points can now be toggled on/off with [[RED Event List#Respawn_Point_State\|Respawn_Point_State]], and the associated team(s) changed with [[RED Event List#Modify_Respawn_Point\|Modify_Respawn_Point]].