Red-alert - Revision history

Goober5000: update comment regarding bugs; add more red-alert information

2024-07-11T20:20:44Z

update comment regarding bugs; add more red-alert information

← Older revision		Revision as of 20:20, 11 July 2024
Line 8:		Line 8:
	Despite what the SEXP description says, red-alert has been tested with a simple branching campaign and it appears that you can branch off of a red-alert mission.		Despite what the SEXP description says, red-alert has been tested with a simple branching campaign and it appears that you can branch off of a red-alert mission.

	~~Regardless~~, red-alert ~~missions often cause errors in retail~~ and ~~SCP FreeSpace, so avoid them if it all possible~~. ~~This can be done using campaign~~-~~persistent~~ [[~~variables~~]] ~~to "remember" the status of various craft just before the player departs.~~		Despite occasional buggy behavior in the past, red-alert works pretty reliably as of FSO version 23.2. Alternatives to red-alert include saving and loading the mission state with scripts[https://github.com/FSO-Scripters/fso-scripts/tree/master/SaveLoad 1][https://github.com/FSO-Scripters/fso-scripts/tree/master/SaveLoadX 2]; as well as [[Tutorial_-_In-Mission_Jumps\|in-mission jumps]].
	~~While most of the bugs that caused these errors have been fixed in FSO version 3.6.10, there is still no absolute guarantee that this sexp will work each time, every time~~.

	==Usage==		==Usage==
Line 18:		Line 17:
	**The ships do not have to be the same type, but it is highly recommended that they are if the ships are not a player craft nor in one of the player's wings.		**The ships do not have to be the same type, but it is highly recommended that they are if the ships are not a player craft nor in one of the player's wings.
	** Trivia: Older versions of FSO (and FS2) only required the "red-alert-carry" flag be defined in the red-alert mission. Somewhere along the line, this code was refactored to require the flag be present in both the source mission and the red-alert mission.		** Trivia: Older versions of FSO (and FS2) only required the "red-alert-carry" flag be defined in the red-alert mission. Somewhere along the line, this code was refactored to require the flag be present in both the source mission and the red-alert mission.
			*By default, the carried ships in the second mission must be present at mission start. The [[Game_settings.tbl#.24Red-alert_applies_to_delayed_ships:\|$Red-alert applies to delayed ships:]] flag allows ships not present at mission start to also inherit red-alert data.
	[[Category:Retail SEXPs]]		[[Category:Retail SEXPs]]

Z64555: Added section on usage

2017-01-21T07:51:06Z

Added section on usage

← Older revision		Revision as of 07:51, 21 January 2017
Line 11:		Line 11:
	While most of the bugs that caused these errors have been fixed in FSO version 3.6.10, there is still no absolute guarantee that this sexp will work each time, every time.		While most of the bugs that caused these errors have been fixed in FSO version 3.6.10, there is still no absolute guarantee that this sexp will work each time, every time.

			==Usage==
	If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur once the ship has reached jumpout velocity (40 m/s) to give the red-alert a few seconds to go into effect.		If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur once the ship has reached jumpout velocity (40 m/s) to give the red-alert a few seconds to go into effect.

			*Ships that have the "red-alert-carry" flag will have their hull HP, shield HP, subsystems HP, and weapon ammo counts saved to an internal buffer which is then used to init the red-alert mission.
			*The carried ships '''''MUST''''' have the same name and the "red-alert-carry" flag set in '''''BOTH''''' the source mission and the red-alert mission in order for a successful red-alert mission to start.
			**The ships do not have to be the same type, but it is highly recommended that they are if the ships are not a player craft nor in one of the player's wings.
			** Trivia: Older versions of FSO (and FS2) only required the "red-alert-carry" flag be defined in the red-alert mission. Somewhere along the line, this code was refactored to require the flag be present in both the source mission and the red-alert mission.
	[[Category:Retail SEXPs]]		[[Category:Retail SEXPs]]

TopAce at 09:45, 17 April 2010

2010-04-17T09:45:53Z

← Older revision		Revision as of 09:45, 17 April 2010
Line 1:		Line 1:
	~~red-alert~~
	red-alert		red-alert
	Causes Red Alert status in a mission. This function ends the current mission, and moves to the next mission		Causes Red Alert status in a mission. This function ends the current mission, and moves to the next mission

The E: Adding a bit of updated info

2009-12-20T07:41:58Z

Adding a bit of updated info

← Older revision		Revision as of 07:41, 20 December 2009
Line 10:		Line 10:

	Regardless, red-alert missions often cause errors in retail and SCP FreeSpace, so avoid them if it all possible. This can be done using campaign-persistent [[variables]] to "remember" the status of various craft just before the player departs.		Regardless, red-alert missions often cause errors in retail and SCP FreeSpace, so avoid them if it all possible. This can be done using campaign-persistent [[variables]] to "remember" the status of various craft just before the player departs.
			While most of the bugs that caused these errors have been fixed in FSO version 3.6.10, there is still no absolute guarantee that this sexp will work each time, every time.

	If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur once the ship has reached jumpout velocity (40 m/s) to give the red-alert a few seconds to go into effect.		If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur once the ship has reached jumpout velocity (40 m/s) to give the red-alert a few seconds to go into effect.

	[[Category:Retail SEXPs]]		[[Category:Retail SEXPs]]

TopAce at 17:59, 24 September 2008

2008-09-24T17:59:16Z

← Older revision		Revision as of 17:59, 24 September 2008
Line 12:		Line 12:

	If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur once the ship has reached jumpout velocity (40 m/s) to give the red-alert a few seconds to go into effect.		If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur once the ship has reached jumpout velocity (40 m/s) to give the red-alert a few seconds to go into effect.

			[[Category:Retail SEXPs]]

Mustang19 at 20:28, 18 September 2007

2007-09-18T20:28:02Z

← Older revision		Revision as of 20:28, 18 September 2007
Line 11:		Line 11:
	Regardless, red-alert missions often cause errors in retail and SCP FreeSpace, so avoid them if it all possible. This can be done using campaign-persistent [[variables]] to "remember" the status of various craft just before the player departs.		Regardless, red-alert missions often cause errors in retail and SCP FreeSpace, so avoid them if it all possible. This can be done using campaign-persistent [[variables]] to "remember" the status of various craft just before the player departs.

	If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur ~~3-4 seconds after the keypress and when~~ the ship has reached jumpout velocity (40 m/s).		If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur once the ship has reached jumpout velocity (40 m/s) to give the red-alert a few seconds to go into effect.

Mustang19: added link to variables

2007-09-18T20:22:14Z

added link to variables

← Older revision		Revision as of 20:22, 18 September 2007
Line 9:		Line 9:
	Despite what the SEXP description says, red-alert has been tested with a simple branching campaign and it appears that you can branch off of a red-alert mission.		Despite what the SEXP description says, red-alert has been tested with a simple branching campaign and it appears that you can branch off of a red-alert mission.

	Regardless, red-alert missions often cause errors in retail and SCP FreeSpace, so avoid them if it all possible. This can be done using campaign-persistent variables to "remember" the status of various craft just before the player departs.		Regardless, red-alert missions often cause errors in retail and SCP FreeSpace, so avoid them if it all possible. This can be done using campaign-persistent [[variables]] to "remember" the status of various craft just before the player departs.

	If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur 3-4 seconds after the keypress and when the ship has reached jumpout velocity (40 m/s).		If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur 3-4 seconds after the keypress and when the ship has reached jumpout velocity (40 m/s).

Mustang19: deleted broken link

2007-09-13T20:21:19Z

deleted broken link

← Older revision		Revision as of 20:21, 13 September 2007
Line 11:		Line 11:
	Regardless, red-alert missions often cause errors in retail and SCP FreeSpace, so avoid them if it all possible. This can be done using campaign-persistent variables to "remember" the status of various craft just before the player departs.		Regardless, red-alert missions often cause errors in retail and SCP FreeSpace, so avoid them if it all possible. This can be done using campaign-persistent variables to "remember" the status of various craft just before the player departs.

	If you want to make a red-alert occur as the player jumps out, ~~consider [http://homepage.ntlworld~~.~~com/karajorma/freespace/FAQ~~-~~Images/Fred~~-~~Tips~~/~~RedAlert.jpg this] example~~.		If you want to make a red-alert occur as the player jumps out, create an event that waits for the player to hit ALT+J. Chain to it an event that causes the red-alert to occur 3-4 seconds after the keypress and when the ship has reached jumpout velocity (40 m/s).

Mustang19: New page: red-alert red-alert Causes Red Alert status in a mission. This function ends the current mission, and moves to the next mission in the campaign under red alert status. There sh...

2007-09-13T20:17:38Z

New page: red-alert red-alert Causes Red Alert status in a mission. This function ends the current mission, and moves to the next mission in the campaign under red alert status. There sh...

New page

red-alert
red-alert
Causes Red Alert status in a mission. This function ends the current mission, and moves to the next mission
in the campaign under red alert status. There should only be one branch from a mission that uses this expression.
Takes no arguments.

==Comments==

Despite what the SEXP description says, red-alert has been tested with a simple branching campaign and it appears that you can branch off of a red-alert mission.

Regardless, red-alert missions often cause errors in retail and SCP FreeSpace, so avoid them if it all possible. This can be done using campaign-persistent variables to "remember" the status of various craft just before the player departs.

If you want to make a red-alert occur as the player jumps out, consider [http://homepage.ntlworld.com/karajorma/freespace/FAQ-Images/Fred-Tips/RedAlert.jpg this] example.