Mapping with Control Points - Revision history

Goober: /* Control Point Events */

2025-12-19T11:34:48Z

Control Point Events

← Older revision		Revision as of 11:34, 19 December 2025
Line 54:		Line 54:
	{{Infobox RF1Event		{{Infobox RF1Event
	\|eventname = Set_Capture_Point_Owner		\|eventname = Set_Capture_Point_Owner
	\|category = ~~AF_Gameplay~~		\|category = AF_General
	\|description = Forces linked control points to a specific ownership state. Must be run on the server, ignored when run on a client.		\|description = Forces linked control points to a specific ownership state. Must be run on the server, ignored when run on a client.
	\|on = Set all linked control points to the specified owner.		\|on = Set all linked control points to the specified owner.

Goober: /* Control Point Events */

2025-12-19T11:33:00Z

Control Point Events

← Older revision		Revision as of 11:33, 19 December 2025
Line 49:		Line 49:
	\|eventname = When_Captured		\|eventname = When_Captured
	\|category = AF_Catalysts		\|category = AF_Catalysts
	\|description = Fires ~~when~~ a linked control point is captured by either team.		\|description = Fires a message to all linked triggers, movers, and events whenever a linked control point is captured by either team.
	}}		}}

Goober: /* Advanced Mechanics */

2025-12-19T11:32:05Z

Advanced Mechanics

← Older revision		Revision as of 11:32, 19 December 2025
Line 43:		Line 43:
	* '''Escalation''': Linked respawn points are enabled when their control point is the current defense hill for that team. The teams assigned to each respawn point never changes, so you should set the red/blue checkboxes on each respawn point to match the intended defending/attacking team for that stage. For example, in a 5-point Escalation map, if red controls their own base, their own forward point, and the center point, while blue only controls their own forward point and their own base, only blue spawn points associated with the blue forward point will be enabled, because that's the point blue is defending; while only red spawn points associated with the center point will be enabled, because that's the point red is defending. The only exception to this rule is when the map first starts and the center point is neutral - in that case, both team's spawns associated with the center point will be enabled until the center point is captured by a team.		* '''Escalation''': Linked respawn points are enabled when their control point is the current defense hill for that team. The teams assigned to each respawn point never changes, so you should set the red/blue checkboxes on each respawn point to match the intended defending/attacking team for that stage. For example, in a 5-point Escalation map, if red controls their own base, their own forward point, and the center point, while blue only controls their own forward point and their own base, only blue spawn points associated with the blue forward point will be enabled, because that's the point blue is defending; while only red spawn points associated with the center point will be enabled, because that's the point red is defending. The only exception to this rule is when the map first starts and the center point is neutral - in that case, both team's spawns associated with the center point will be enabled until the center point is captured by a team.

	Additionally, the [[RED Event List#Respawn_Point_State\|Respawn_Point_State]] and [[RED Event List#Modify_Respawn_Point\|Modify_Respawn_Point]] events can be used to manually adjust the behaviour of respawn points in all ~~modes~~.		Additionally, the [[RED Event List#Respawn_Point_State\|Respawn_Point_State]] and [[RED Event List#Modify_Respawn_Point\|Modify_Respawn_Point]] events can be used to manually adjust the behaviour of respawn points in all gametypes.

	=== Control Point Events ===		=== Control Point Events ===

Goober at 11:30, 19 December 2025

2025-12-19T11:30:50Z

← Older revision		Revision as of 11:30, 19 December 2025
Line 36:		Line 36:
	== Advanced Mechanics ==		== Advanced Mechanics ==
	=== Linking to Respawn Points ===		=== Linking to Respawn Points ===
	~~You can link~~ the Capture_Point_Handler to [[RED_Objects#Multiplayer_Respawn_Point\|respawn points]].		Link the Capture_Point_Handler to [[RED_Objects#Multiplayer_Respawn_Point\|respawn points]] to let Alpine Faction automatically manage spawn activation and team assignment depending on the gametype.

	~~If you do this, the game will automatically update spawn points linked to from the Capture_Point_Handler when the ownership state of the control point changes. In~~ '''King of the Hill''' ~~and~~ '''Damage Control'''~~, only~~ the ~~team that currently owns~~ the point will be able to spawn at ~~linked~~ respawn points. ~~If no team currently owns~~ the point, the ~~linked~~ respawn ~~points are disabled~~. In '''~~Revolt~~''', the team assigned to ~~the~~ respawn point never changes as the ~~game progresses~~, ~~but both teams~~ will only be ~~able~~ to ~~spawn at linked respawn points while~~ the ~~specified stage~~ is ~~active~~.		==== Behaviour per Gametype ====
			* '''King of the Hill''' & '''Damage Control''': Linked respawn points are synced to the owner of the control point. Only that team will be able to spawn at those respawn points. Use of this in KOTH is generally not needed/recommended
			* '''Revolt''': Linked respawn points are enabled when their control point’s stage is active, and disabled when the game moves to the next stage. The teams assigned to each respawn point never changes, so you should set the red/blue checkboxes on each respawn point to match the intended defending/attacking team for that stage.
			* '''Escalation''': Linked respawn points are enabled when their control point is the current defense hill for that team. The teams assigned to each respawn point never changes, so you should set the red/blue checkboxes on each respawn point to match the intended defending/attacking team for that stage. For example, in a 5-point Escalation map, if red controls their own base, their own forward point, and the center point, while blue only controls their own forward point and their own base, only blue spawn points associated with the blue forward point will be enabled, because that's the point blue is defending; while only red spawn points associated with the center point will be enabled, because that's the point red is defending. The only exception to this rule is when the map first starts and the center point is neutral - in that case, both team's spawns associated with the center point will be enabled until the center point is captured by a team.

	* In '''King of the ~~Hill''', this is generally not recommended.~~		Additionally, the [[RED Event List#Respawn_Point_State\|Respawn_Point_State]] and [[RED Event List#Modify_Respawn_Point\|Modify_Respawn_Point]] events can be used to manually adjust the behaviour of respawn points in all modes.
	* In '''Damage Control''', this can be ~~a nice feature~~ to ~~reduce~~ the ~~chances~~ of ~~people spawning very close to~~ points ~~they do not own. However, especially given that it is possible for one team to own~~ all ~~control points on the map, it is highly recommended to have at least some number of respawn points that are ''not'' linked from a Capture_Point_Handler and are therefore active for the entire game.~~
	* In '''Revolt''', linked respawn points are effectively a requirement for game flow.

	=== Control Point Events ===		=== Control Point Events ===
	* ~~WIP~~		{{Infobox RF1Event
			\|eventname = When_Captured
			\|category = AF_Catalysts
			\|description = Fires when a linked control point is captured by either team.
			}}

			{{Infobox RF1Event
			\|eventname = Set_Capture_Point_Owner
			\|category = AF_Gameplay
			\|description = Forces linked control points to a specific ownership state. Must be run on the server, ignored when run on a client.
			\|on = Set all linked control points to the specified owner.
			\|params = * '''Owner:''' (int1) Desired owner.
			}}

			{{Infobox RF1Event
			\|eventname = Owner_Gate
			\|category = AF_Flow
			\|description = Tests whether a specific control point has a specified owner.
			\|params = * '''Handler UID:''' (int1) UID of the Capture_Point_Handler to test.
			* '''Required owner:''' (int2) Owner to check.
			}}

	[[Category: Red Faction]]		[[Category: Red Faction]]

Goober: /* Advanced Mechanics */

2025-11-20T21:03:04Z

Advanced Mechanics

← Older revision		Revision as of 21:03, 20 November 2025
Line 40:		Line 40:
	If you do this, the game will automatically update spawn points linked to from the Capture_Point_Handler when the ownership state of the control point changes. In '''King of the Hill''' and '''Damage Control''', only the team that currently owns the point will be able to spawn at linked respawn points. If no team currently owns the point, the linked respawn points are disabled. In '''Revolt''', the team assigned to the respawn point never changes as the game progresses, but both teams will only be able to spawn at linked respawn points while the specified stage is active.		If you do this, the game will automatically update spawn points linked to from the Capture_Point_Handler when the ownership state of the control point changes. In '''King of the Hill''' and '''Damage Control''', only the team that currently owns the point will be able to spawn at linked respawn points. If no team currently owns the point, the linked respawn points are disabled. In '''Revolt''', the team assigned to the respawn point never changes as the game progresses, but both teams will only be able to spawn at linked respawn points while the specified stage is active.

	* In '''King of the Hill''', this is generally not recommended, as it can overly constrain spawns around a single point.		* In '''King of the Hill''', this is generally not recommended.
	* In '''Damage Control''', this can be a nice feature to reduce the chances of people spawning very close to points they do not own. However, especially given that it is possible for one team to own all control points on the map, it is highly recommended to have at least some number of respawn points that are ''not'' linked from a Capture_Point_Handler and are therefore active for the entire game.		* In '''Damage Control''', this can be a nice feature to reduce the chances of people spawning very close to points they do not own. However, especially given that it is possible for one team to own all control points on the map, it is highly recommended to have at least some number of respawn points that are ''not'' linked from a Capture_Point_Handler and are therefore active for the entire game.
	* In '''Revolt''', linked respawn points are effectively a requirement for game flow.		* In '''Revolt''', linked respawn points are effectively a requirement for game flow.

Goober: /* Basic Setup */

2025-11-20T21:02:22Z

Basic Setup

← Older revision		Revision as of 21:02, 20 November 2025
Line 5:		Line 5:

	== Basic Setup ==		== Basic Setup ==
	# Create a [[RED Objects#Triggers\|trigger]]. This can be a box or a sphere. The only properties of the ~~triggerthat~~ matter for control points are the dimensions and the shape.		# Create a [[RED Objects#Triggers\|trigger]]. This can be a box or a sphere. The only properties of the trigger that matter for control points are the dimensions and the shape.
	# Create a [[RED Event List#Capture_Point_Handler\|Capture_Point_Handler]] event (under the '''AF_Gameplay''' category).		# Create a [[RED Event List#Capture_Point_Handler\|Capture_Point_Handler]] event (under the '''AF_Gameplay''' category).
	# Link the Capture_Point_Handler event to the trigger.		# Link the Capture_Point_Handler event to the trigger.

Goober at 21:01, 20 November 2025

2025-11-20T21:01:40Z

@@ Line 1: / Line 1: @@
 {{RF1Tutorial|Goober}}
-{{Under construction}}
+'''Control Points''' are used as objectives in the '''[[King of the Hill]]''', '''[[Damage Control]]''', and '''[[Revolt]]''' game types added in [[Alpine Faction|Alpine Faction]] v1.2.
-'''Control Points''' are used as objectives in the '''King of the Hill''', '''Damage Control''', and '''Revolt''' game types added in [https://alpinefaction.com Alpine Faction]
+The process to create these is very straightforward.
-The process to create these is very straightforward.
+If you do this, the game will automatically update spawn points linked to from the Capture_Point_Handler when the ownership state of the control point changes. In '''King of the Hill''' and '''Damage Control''', only the team that currently owns the point will be able to spawn at linked respawn points. If no team currently owns the point, the linked respawn points are disabled. In '''Revolt''', the team assigned to the respawn point never changes as the game progresses, but both teams will only be able to spawn at linked respawn points while the specified stage is active.
-==Tutorial Steps==
+* In '''King of the Hill''', this is generally **not recommended**, as it can overly constrain spawns around a single point.
-* Create a Trigger
+* In '''Damage Control''', this can be a nice feature to reduce the chances of people spawning very close to points they do not own. However, especially given that it is possible for one team to own all control points on the map, it is highly recommended to have at least some number of respawn points that are ''not'' linked from a Capture_Point_Handler and are therefore active for the entire game.
-* Create a Capture_Point_Handler event, link the event to the trigger
+* In '''Revolt''', linked respawn points are effectively a requirement for game flow.
 [[Category: Red Faction]]

Goober: Goober moved page Creating Control Points to Mapping with Control Points

2025-10-31T11:52:00Z

Goober moved page Creating Control Points to Mapping with Control Points

← Older revision	Revision as of 11:52, 31 October 2025
(No difference)

Goober: Created page with "{{RF1Tutorial|Goober}} {{Under construction}} '''Control Points''' are used as objectives in the '''King of the Hill''', '''Damage Control''', and '''Revolt''' game types added in [https://alpinefaction.com Alpine Faction] The process to create these is very straightforward. ==Tutorial Steps== * Create a Trigger * Create a Capture_Point_Handler event, link the event to the trigger Category: Red Faction Category: RF1 Editing Category: Tutorials Category..."

2025-10-31T02:43:43Z

Created page with "{{RF1Tutorial|Goober}} {{Under construction}} '''Control Points''' are used as objectives in the '''King of the Hill''', '''Damage Control''', and '''Revolt''' game types added in [https://alpinefaction.com Alpine Faction] The process to create these is very straightforward. ==Tutorial Steps== * Create a Trigger * Create a Capture_Point_Handler event, link the event to the trigger Category: Red Faction Category: RF1 Editing Category: Tutorials Category..."

New page

{{RF1Tutorial|Goober}}
{{Under construction}}

'''Control Points''' are used as objectives in the '''King of the Hill''', '''Damage Control''', and '''Revolt''' game types added in [https://alpinefaction.com Alpine Faction]

The process to create these is very straightforward.

==Tutorial Steps==
* Create a Trigger
* Create a Capture_Point_Handler event, link the event to the trigger

[[Category: Red Faction]]
[[Category: RF1 Editing]]
[[Category: Tutorials]]
[[Category: Alpine Faction]]