Persistent Variables - Revision history

SpaceFreak: Fixed double redirect

2010-04-16T09:19:49Z

Fixed double redirect

← Older revision		Revision as of 09:19, 16 April 2010
Line 1:		Line 1:
	#REDIRECT [[~~Variables~~]]		#REDIRECT [[Variable]]

Mustang19: contents of page have been moved to "variables"

2008-01-31T20:50:37Z

contents of page have been moved to "variables"

← Older revision		Revision as of 20:50, 31 January 2008
Line 1:		Line 1:
	Variables have been a part of FRED since the Retail version, but are limited by only being available in the mission where they are defined. Persistent variables differ in this, as they are stored for later use instead of being lost for good when the mission ends. This allows mission designers to carry over specific information between missions and even campaigns.		#REDIRECT [[Variables]]

	~~There are two types of persistent variables:~~

	~~===Player-persistent===~~
	This type of persistent variable is stored in the pilot file. Further, they are stored immediately when they are created/changed from within a mission. This means that any change is going to be there regardless of the later outcome of the mission. Player-persistent variables can be accessed and changed from any campaign played with the same pilot.

	~~===Campaign-persistent===~~
	These persistent variables are stored in the campaign file, and are only stored when a campaign progresses to a new mission. So if the player is killed or quits during a mission, and changes made to a campaign-persistent variable are not stored.
	[[~~Category:FRED~~]]

Shade: Brought into line with goober's spelling to avoid persecution

2006-05-07T11:07:54Z

Brought into line with goober's spelling to avoid persecution

← Older revision		Revision as of 11:07, 7 May 2006
Line 1:		Line 1:
	Variables have been a part of FRED since the Retail version, but are limited by only being available in the mission where they are defined. ~~Persistant~~ variables differ in this, as they are stored for later use instead of being lost for good when the mission ends. This allows mission designers to carry over specific information between missions and even campaigns.		Variables have been a part of FRED since the Retail version, but are limited by only being available in the mission where they are defined. Persistent variables differ in this, as they are stored for later use instead of being lost for good when the mission ends. This allows mission designers to carry over specific information between missions and even campaigns.

	There are two types of ~~persistant~~ variables:		There are two types of persistent variables:

	===Player-~~persistant~~===		===Player-persistent===
	This type of ~~persistant~~ variable is stored in the pilot file. Further, they are stored immediately when they are created/changed from within a mission. This means that any change is going to be there regardless of the later outcome of the mission. Player-~~persistant~~ variables can be accessed and changed from any campaign played with the same pilot.		This type of persistent variable is stored in the pilot file. Further, they are stored immediately when they are created/changed from within a mission. This means that any change is going to be there regardless of the later outcome of the mission. Player-persistent variables can be accessed and changed from any campaign played with the same pilot.

	===Campaign-~~persistant~~===		===Campaign-persistent===
	These ~~persistant~~ variables are stored in the campaign file, and are only stored when a campaign progresses to a new mission. So if the player is killed or quits during a mission, and changes made to a campaign-~~persistant~~ variable are not stored.		These persistent variables are stored in the campaign file, and are only stored when a campaign progresses to a new mission. So if the player is killed or quits during a mission, and changes made to a campaign-persistent variable are not stored.
	[[Category:FRED]]		[[Category:FRED]]

Goober5000: Persistant Variables moved to Persistent Variables: spelling

2006-05-07T05:59:28Z

Persistant Variables moved to Persistent Variables: spelling

← Older revision	Revision as of 05:59, 7 May 2006
(No difference)

Shade: new page

2006-05-06T15:15:29Z

new page

New page

Variables have been a part of FRED since the Retail version, but are limited by only being available in the mission where they are defined. Persistant variables differ in this, as they are stored for later use instead of being lost for good when the mission ends. This allows mission designers to carry over specific information between missions and even campaigns.

There are two types of persistant variables:

===Player-persistant===
This type of persistant variable is stored in the pilot file. Further, they are stored immediately when they are created/changed from within a mission. This means that any change is going to be there regardless of the later outcome of the mission. Player-persistant variables can be accessed and changed from any campaign played with the same pilot.

===Campaign-persistant===
These persistant variables are stored in the campaign file, and are only stored when a campaign progresses to a new mission. So if the player is killed or quits during a mission, and changes made to a campaign-persistant variable are not stored.
[[Category:FRED]]