Upgrading campaigns - Revision history

Goober5000: better category

2023-12-13T20:28:00Z

better category

← Older revision		Revision as of 20:28, 13 December 2023
Line 281:		Line 281:
	**[http://www.hard-light.net/forums/index.php/board,146.0.html Public board \| Hard Light Productions.net]		**[http://www.hard-light.net/forums/index.php/board,146.0.html Public board \| Hard Light Productions.net]

	[[Category: ~~FRED Tips~~]]		[[Category: Campaign Design]]
	[[Category: Articles that need proofreading]]		[[Category: Articles that need proofreading]]

SypheDMar: Fixed most grammar issues.

2011-05-11T23:50:47Z

Fixed most grammar issues.

← Older revision		Revision as of 23:50, 11 May 2011
Line 1:		Line 1:
	~~{{grammar}}~~

	'''Upgrading a campaign''' means editing someone else's work. This means that the changes a FREDder can make are somewhat restricted.		'''Upgrading a campaign''' means editing someone else's work. This means that the changes a FREDder can make are somewhat restricted.

Line 117:		Line 115:
	If you decide to create a background from scratch, it would be a nice idea to post it to the Background Emporium. Both alternate versions of existing system backgrounds and background for exclusive systems are accepted and should be made public.		If you decide to create a background from scratch, it would be a nice idea to post it to the Background Emporium. Both alternate versions of existing system backgrounds and background for exclusive systems are accepted and should be made public.

	====~~Number of stars~~====		====Stars====
	Older campaigns were tested using FRED Retail. Back then, no starfield skyboxes were available, so the only ways to improve a background were to add nebulae and set the number of stars to the max value, 2,000.		Older campaigns were tested using FRED Retail. Back then, no starfield skyboxes were available, so the only ways to improve a background were to add nebulae and set the number of stars to the max value, 2,000.

Line 124:		Line 122:
	''Editors'' ---> ''Background'' ---> ''Misc'' ---> ''Number of stars'' ---> Set the value to ''0''.		''Editors'' ---> ''Background'' ---> ''Misc'' ---> ''Number of stars'' ---> Set the value to ''0''.

	====Skybox ~~models~~====		====Skybox====
	Skyboxes are graphical enhancements introduced by the [[FreeSpace Upgrade Project]]. Needless to say, as fan-made effects, skyboxes are missing from old campaigns.		Skyboxes are graphical enhancements introduced by the [[FreeSpace Upgrade Project]]. Needless to say, as fan-made effects, skyboxes are missing from old campaigns.

Line 196:		Line 194:
	Because renaming a wing in FRED resets that wing's orders and also leads to event/cue conflicts, not to mention the possibility of altering the contents of messages, the easiest way to change wing names is using Notepad. Use the program to open the mission and scroll down the file until you find the list of wings. Take note of the repetitive and/or misspelled names and then decide which names you're going to use instead. Use the search function of Notepad to ensure that no ships/messages have the name you're willing to add (read below for more info about this possible conflict) and then use the same function to find each reference to the wing name that is in dire need of changes. The search function should point you to: each ship of the wing, the wing's entry in the list of wings, eventual directives related to the wing, eventual arrival cues/event conditions that are related to the wing, message names and the content of some messages. Changing the name via Notepad will effectively do the job. Be careful when editing a mission via Notepad, though - any errors could result in certain mission corruption.		Because renaming a wing in FRED resets that wing's orders and also leads to event/cue conflicts, not to mention the possibility of altering the contents of messages, the easiest way to change wing names is using Notepad. Use the program to open the mission and scroll down the file until you find the list of wings. Take note of the repetitive and/or misspelled names and then decide which names you're going to use instead. Use the search function of Notepad to ensure that no ships/messages have the name you're willing to add (read below for more info about this possible conflict) and then use the same function to find each reference to the wing name that is in dire need of changes. The search function should point you to: each ship of the wing, the wing's entry in the list of wings, eventual directives related to the wing, eventual arrival cues/event conditions that are related to the wing, message names and the content of some messages. Changing the name via Notepad will effectively do the job. Be careful when editing a mission via Notepad, though - any errors could result in certain mission corruption.

	Please note how it's not that hard to have individual ships with names that match perfectly those used for wings. It's the case of transports and freighters, which usually have conventional names like ''Capricorn 1'' or ''Iota 2'' without being part of any wings. For this reason, before replacing a wing's name with another, it's extremely important to use the search function of Notepad to verify ~~wheter~~ or not that name is used for another ship - FRED won't tolerate both a combat spacecraft and a transport/freighter with the same name like ''Capricorn 1''.		Please note how it's not that hard to have individual ships with names that match perfectly those used for wings. It's the case of transports and freighters, which usually have conventional names like ''Capricorn 1'' or ''Iota 2'' without being part of any wings. For this reason, before replacing a wing's name with another, it's extremely important to use the search function of Notepad to verify whether or not that name is used for another ship - FRED won't tolerate both a combat spacecraft and a transport/freighter with the same name like ''Capricorn 1''.

	====Random protection====		====Random protection====
Line 274:		Line 272:
	===Weapons management===		===Weapons management===

	====~~Implementation of~~ Shivan weapons====		====Shivan weapons====
	With [[MediaVP\|Media VPs]], the Shivans now have a large variety of specific weapons. They're the same as the weapons used by the player, but their mesh and their color fits for Shivan use.		With [[MediaVP\|Media VPs]], the Shivans now have a large variety of specific weapons. They're the same as the weapons used by the player, but their mesh and their color fits for Shivan use.

SypheDMar at 23:48, 11 May 2011

2011-05-11T23:48:10Z

Show changes

SypheDMar: /* The purpose of the upgrade */

2010-01-19T23:04:44Z

The purpose of the upgrade

← Older revision		Revision as of 23:04, 19 January 2010
Line 10:		Line 10:
	The upgrade is to make an old campaign compatible with [[FreeSpace Open\|FSO]] or, if it was already compatible with FSO, to make it compatible with recent builds developed by the SCP.		The upgrade is to make an old campaign compatible with [[FreeSpace Open\|FSO]] or, if it was already compatible with FSO, to make it compatible with recent builds developed by the SCP.

	This means that the [[FreeSpace Campaign Restoration Project\|FSCRP's]] upgrades are not intended to be compatible with Retail FreeSpace. ~~More in general~~, upgrades are not intended to fully replace the original versions - the original releases are the only official ones in existence and therefore should remain available. It's worth noting that people who don't make use of FSO have all the right to play old ~~Retail~~ campaigns.		This means that the [[FreeSpace Campaign Restoration Project\|FSCRP's]] upgrades are not intended to be compatible with Retail FreeSpace. Generally, upgrades are not intended to fully replace the original versions - the original releases are the only official ones in existence and therefore should remain available. It's worth noting that people who don't make use of FSO have all the right to play old retail campaigns.

	====Working as a team====		====Working as a team====

SypheDMar at 22:43, 19 January 2010

2010-01-19T22:43:25Z

← Older revision		Revision as of 22:43, 19 January 2010
Line 13:		Line 13:

	====Working as a team====		====Working as a team====
	~~Without considering~~ a few exceptions, upgrading a campaign is the result of the work of many members who decide to use their free time in a useful way. For this reason, it'd be polite to keep a reasonable behavior and respect the other members of the upgrade team.		With a few exceptions, upgrading a campaign is the result of the work of many members who decide to use their free time in a useful way. For this reason, it'd be polite to keep a reasonable behavior and respect for the other members of the upgrade team.

	No one ~~is to~~ be ashamed ~~for~~ mistakes, so ~~flaming is all but out of context~~.		No one should be ashamed of making mistakes, so don't flame.

	====Contacts====		====Contacts====
	~~Effective contacts are~~ a ~~vital parameter~~ in upgrades. Although instant messaging programs, personal messages, e-mails and any other form of communication are ~~reliable and effective~~, using private forums is surely the best option.		The ability to contact is a necessity in upgrades. Although instant messaging programs, personal messages, e-mails and any other form of communication are possible, using private forums is surely the best option.

	As evidenced [http://www.hard-light.net/forums/index.php/topic,62475.0.html here,] coordinating work of notable complexity requires a private forum which can be easily used to post questions, proposals, reports, etc. etc.		As evidenced [http://www.hard-light.net/forums/index.php/topic,62475.0.html here,] coordinating work of notable complexity requires a private forum which can be easily used to post questions, proposals, reports, etc. etc.
Line 30:		Line 30:
	Although most of the bug-hunting job is up to testers, FREDders are also encouraged to playtest campaigns in need of upgrades at least once.		Although most of the bug-hunting job is up to testers, FREDders are also encouraged to playtest campaigns in need of upgrades at least once.

	There are several benefits: first of all, it's very important to get acquainted with the original campaign creator's FREDding style so that the upcoming changes can fit with the previous work. It's also extremely important when trying to supplement a tester's work and propose significant changes - testers with poor or nonexistent FREDding experience are focused on mission bugs and balancing while a FREDder may also analyze the campaign and decide ~~wheter~~ or not cutscenes and/or other special effects should be added.		There are several benefits: first of all, it's very important to get acquainted with the original campaign creator's FREDding style so that the upcoming changes can fit with the previous work. It's also extremely important when trying to supplement a tester's work and propose significant changes - testers with poor or nonexistent FREDding experience are focused on mission bugs and balancing while a FREDder may also analyze the campaign and decide whether or not cutscenes and/or other special effects should be added.

	====Proper naming conventions====		====Proper naming conventions====
Line 41:		Line 41:
	In this example, the event has been created by [[User:Mobius\|Mobius]] and it's intended to show up a specific directive: "Destroy Transports".		In this example, the event has been created by [[User:Mobius\|Mobius]] and it's intended to show up a specific directive: "Destroy Transports".

	====~~Change logs~~====		====Changelogs====
	~~Change logs~~ are necessary to track edits and undo them should problems arise. Each upgrader working on a project is supposed to attach a .txt file with the changes he made. The document needs to be ~~exhaustive~~.		Changelogs are necessary to track edits and undo them should problems arise. Each upgrader working on a project is supposed to attach a .txt file with the changes he made. The document needs to be extensive.

	It's also recommended to post the contents of the ~~change logs~~ in the forums. Do not attach the .txt to a post, since attachments are deleted at regular intervals.		It's also recommended to post the contents of the changelogs in the forums. Do not attach the .txt to a post, since attachments are deleted at regular intervals.

	===Testers===		===Testers===
Line 50:		Line 50:

	====Compiling initial reports====		====Compiling initial reports====
	Initial reports mark the beginning of an upgrade. During this phase~~, in facts~~, the most noticeable bugs and problems are found and discussed with the rest of the upgrade team.		Initial reports mark the beginning of an upgrade. During this phase, the most noticeable bugs and problems are found and discussed with the rest of the upgrade team.

	Problems are various and aren't all ~~supposed to be~~ FREDding-related~~; certain~~ campaigns are, in fact, old enough to give problems with recent builds of [[FreeSpace Open]] (or worse, with FreeSpace Open in general) so immediate edits are needed to test the campaign in a proper way.		Problems are various and aren't all FREDding-related. Certain campaigns are, in fact, old enough to give problems with recent builds of [[FreeSpace Open]] (or worse, with FreeSpace Open in general) so immediate edits are needed to test the campaign in a proper way.

	The basic formula to create a report is the following:		The basic formula to create a report is the following:
Line 102:		Line 102:

	====Sanity check====		====Sanity check====
	Sanity check is the last phase of the upgrade. It consists in one or more playthroughs whose objective is testing additional changes and making sure that the campaign is in ~~very~~ good conditions. Sanity checks shouldn't be underestimated simply because most of the job is already done - that's why there should be a coherent approach during this phase.		Sanity check is the last phase of the upgrade. It consists in one or more playthroughs whose objective is testing additional changes and making sure that the campaign is in good conditions. Sanity checks shouldn't be underestimated simply because most of the job is already done - that's why there should be a coherent approach during this phase.

	==Basic edits==		==Basic edits==
Line 109:		Line 109:
	:''See also:'' [[Background Emporium\|''Background Emporium'']]		:''See also:'' [[Background Emporium\|''Background Emporium'']]

	A considerable number of custom-made missions lack backgrounds and many, many others feature minimal backgrounds. Most, if not all, campaign upgrades also involved the radical improvement of backgrounds. It's actually possible to create several backgrounds from scratch, but the ~~existance~~ of several shortcuts makes thing easier.		A considerable number of custom-made missions lack backgrounds and many, many others feature minimal backgrounds. Most, if not all, campaign upgrades also involved the radical improvement of backgrounds. It's actually possible to create several backgrounds from scratch, but the existence of several shortcuts makes thing easier.

	Thanks to the efforts of several FREDders, most canon systems have their specific backgrounds. If a mission takes place in a given system, it's possible to copy and paste that background via Notepad. The operation is not hard at all, but eventual errors could result in certain mission corruption. Be careful when using Notepad to alter mission files, and don't forget to open the modified mission in FRED to verify if the new background is properly set and/or to check if your Notepad edits somewhat compromised critical mission lines.		Thanks to the efforts of several FREDders, most canon systems have their specific backgrounds. If a mission takes place in a given system, it's possible to copy and paste that background via Notepad. The operation is not hard at all, but eventual errors could result in certain mission corruption. Be careful when using Notepad to alter mission files, and don't forget to open the modified mission in FRED to verify if the new background is properly set and/or to check if your Notepad edits somewhat compromised critical mission lines.
Line 120:		Line 120:
	Older campaigns were tested using FRED Retail. Back then, no starfield skyboxes were available, (the SCP added them) so the only ways to improve a background were to add nebulae and set the number of stars to the max value, 2,000.		Older campaigns were tested using FRED Retail. Back then, no starfield skyboxes were available, (the SCP added them) so the only ways to improve a background were to add nebulae and set the number of stars to the max value, 2,000.

	Many fans complain about the presence of those stars because their usage results in certain render oddities, like the "distortion effect". A recent change to the code has made sure that the skybox overwrites auto-generated stars, but it's always a safer to the number of stars to 0:		Many fans complain about the presence of those stars because their usage results in certain render oddities, like the "distortion effect". A recent change to the code has made sure that the skybox overwrites auto-generated stars, but it's always a safer to change the number of stars to 0:

	''Editors'' ---> ''Background'' ---> ''Misc'' ---> ''Number of stars'' ---> Set the value to ''0''.		''Editors'' ---> ''Background'' ---> ''Misc'' ---> ''Number of stars'' ---> Set the value to ''0''.

	====Skybox models====		====Skybox models====
	Skyboxes are among the best graphical enhancements introduced by the [[FreeSpace Upgrade Project]]. Needless to say, as fan-made effects, skyboxes are ~~totally~~ missing from old campaigns.		Skyboxes are among the best graphical enhancements introduced by the [[FreeSpace Upgrade Project]]. Needless to say, as fan-made effects, skyboxes are missing from old campaigns.

	Adding them is a must during the upgrade—they're the easiest and most effective way to show a good background even without any nebula. The standard skybox model released with the [[Media VP\|Media VPs]] is called "starfield". Adding it is easy:		Adding them is a must during the upgrade—they're the easiest and most effective way to show a good background even without any nebula. The standard skybox model released with the [[Media VP\|Media VPs]] is called "starfield". Adding it is easy:
Line 136:		Line 136:

	====Weird warship battles====		====Weird warship battles====
	Often, FREDders order ships to engage each other in a fight by simply ordering them to attack each other. This is known to cause oddities~~, mostly under an eyecandy point of view~~—ships engaged in some sort of "dance" and/or involved in multiple collisions aren't worth watching. Obviously, this edit isn't necessary if all warships involved in the battle are supposed to remain immobile.		Often, FREDders order ships to engage each other in a fight by simply ordering them to attack each other. This is known to cause oddities—ships engaged in some sort of "dance" and/or involved in multiple collisions aren't worth watching. Obviously, this edit isn't necessary if all warships involved in the battle are supposed to remain immobile.

	The best idea is to create waypoints the warships will then be supposed to fly through. If the warships are too fast and/or their starting distance is too short, it may be a good idea to reduce their speed. All of this can be easily done:		The best idea is to create waypoints the warships will then be supposed to fly through. If the warships are too fast and/or their starting distance is too short, it may be a good idea to reduce their speed. All of this can be easily done:
Line 175:		Line 175:
	Unless it is clearly specified that the player is supposed to issue orders to such ships, it's very important to make sure that those ships will do only what they're supposed to:		Unless it is clearly specified that the player is supposed to issue orders to such ships, it's very important to make sure that those ships will do only what they're supposed to:

	''Editors'' ---> ''Ships'' ---> ''Player Orders'' ---> Unmark all orders that the player can issue. The white ~~squares~~ need to be ~~empty~~.		''Editors'' ---> ''Ships'' ---> ''Player Orders'' ---> Unmark all orders that the player can issue. The white boxes need to be unchecked.

	====Spacecraft====		====Spacecraft====

General Battuta at 18:29, 30 June 2009

2009-06-30T18:29:44Z

← Older revision		Revision as of 18:29, 30 June 2009
Line 271:		Line 271:
	'''Delay between waves:''' <br>		'''Delay between waves:''' <br>
	''Editors'' ---> ''Wings'' ---> ''Arrival'' ---> ''Delay between waves'' ---> Edit the ''Min'' and/or ''Max'' value.		''Editors'' ---> ''Wings'' ---> ''Arrival'' ---> ''Delay between waves'' ---> Edit the ''Min'' and/or ''Max'' value.

			===Weapons management===

			====Implementation of Shivan weapons====
			Thanks to the new [[MediaVP\|Media VPs]], the Shivans now have a large variety of specific and more realistic weapons. They're more or less the same as the weapons used by the player, but their mesh and their color fits for Shivan use.

			In order to add those weapons, the [[FreeSpace Upgrade Project\|FSU Team]] has modified the default table entries of Shivan craft. This kind of change, although entirely appropriate, has its drawbacks: it has no effect on weapon configurations which have been modified manually in FRED. Because getting an idea of the difference is hard during the game, it's highly suggested to. Doing this is very important if, for example, missions feature the [[SB Nephilim]]: the bomber's default configuration, in fact, has no heavy weaponry - it's very likely that the mission designer changed the configuration manually, meaning that during the mission the Nephilims will not make use of new Shivan weapons.

	==Related Links==		==Related Links==

Mobius: "Random protection" subsection added

2009-06-28T17:19:39Z

"Random protection" subsection added

← Older revision		Revision as of 17:19, 28 June 2009
Line 197:		Line 197:

	Please note how it's not that hard to have individual ships with names that match perfectly those used for wings. It's the case of transports and freighters, which usually have conventional names like ''Capricorn 1'' or ''Iota 2'' without being part of any wings. For this reason, before replacing a wing's name with another, it's extremely important to use the search function of Notepad to verify wheter or not that name is used for another ship - FRED surely won't tolerate both a combat spacecraft and a transport/freighter with the same name, like ''Capricorn 1''.		Please note how it's not that hard to have individual ships with names that match perfectly those used for wings. It's the case of transports and freighters, which usually have conventional names like ''Capricorn 1'' or ''Iota 2'' without being part of any wings. For this reason, before replacing a wing's name with another, it's extremely important to use the search function of Notepad to verify wheter or not that name is used for another ship - FRED surely won't tolerate both a combat spacecraft and a transport/freighter with the same name, like ''Capricorn 1''.

			====Random protection====
			For pure balance issues, the upgrade might involve additional changes to allied wings' survivability. Thanks to random protection, it's possible to make sure that a friendly wing will not be completely destroyed during the mission.

			In order to represent the effect, create an event for the wing you want the random protection to have effect on. In this event, use [[percent-ships-destroyed]] with any reasonable value (like 50) and [[ship-guardian-threshold]] (with [[rand]]) for every spacecraft of the wing. [[ship-guardian]] would work, but it won't randomize anything (the minimum value will be 1% for every spacecraft). Additionally, it's strongly suggested to use [[ship-subsys-guardian-threshold]] to prevent the spacecraft from being disabled. Here's an example:

			Condition that will trigger the event (with [[when]]):

			''percent-ships-destroyed''
			''50''
			''Epsilon

			To protect the hull:

			''ship-guardian-threshold''
			''rand''
			''5''
			''15''
			''Epsilon 1''

			[...]

			''ship-guardian-threshold''
			''rand''
			''5''
			''15''
			''Epsilon 4''

			To protect the engines:

			''ship-subsys-guardian-threshold''
			''rand''
			''20''
			''40''
			''Epsilon 1''
			''engine/engines/<<all engines>>''

			[...]

			''ship-subsys-guardian-threshold''
			''rand''
			''20''
			''40''
			''Epsilon 4''
			''engine/engines/<<all engines>>''

			Finally, it's also possible to AI-protect the spacecraft. It's not highly recommended, but it's a valid option:

			''protect-ship''
			''Epsilon 1''

			[...]

			''protect-ship''
			''Epsilon 4''

			Depending on the contest, it's also possible to protect the spacecraft from beams:

			''beam-protect-ship''
			''Epsilon 1''

			[...]

			''beam-protect-ship''
			''Epsilon 4''

	====Waves-related problems====		====Waves-related problems====

Mobius: Section "The purpose of the upgrade" created following a discussion on FSCRP internal (HLP)

2009-06-18T19:43:58Z

Section "The purpose of the upgrade" created following a discussion on FSCRP internal (HLP)

← Older revision		Revision as of 19:43, 18 June 2009
Line 7:		Line 7:
	==Guidelines==		==Guidelines==
	===Generic===		===Generic===
			====The purpose of the upgrade====
			The upgrade is to make an old campaign compatible with [[FreeSpace Open\|FSO]] or, if it was already compatible with FSO, to make it compatible with recent builds developed by the SCP.

			This means that the [[FreeSpace Campaign Restoration Project\|FSCRP's]] upgrades are not intended to be compatible with Retail FreeSpace. More in general, upgrades are not intended to fully replace the original versions - the original releases are the only official ones in existence and therefore should remain available. It's worth noting that people who don't make use of FSO have all the right to play old Retail campaigns.

	====Working as a team====		====Working as a team====
	Without considering a few exceptions, upgrading a campaign is the result of the work of many members who decide to use their free time in a useful way. For this reason, it'd be polite to keep a reasonable behavior and respect the other members of the upgrade team.		Without considering a few exceptions, upgrading a campaign is the result of the work of many members who decide to use their free time in a useful way. For this reason, it'd be polite to keep a reasonable behavior and respect the other members of the upgrade team.

Mobius: Order-related issues section divided in two subsections (Ships and Spacecraft). "Number of stars" and "Skybox models" are part of the "Backgrounds" section now. New section added: "Adding backgrounds"

2009-06-14T11:11:18Z

Order-related issues section divided in two subsections (Ships and Spacecraft). "Number of stars" and "Skybox models" are part of the "Backgrounds" section now. New section added: "Adding backgrounds"

Show changes

Mobius: Improvement of the Wings management section. The edit is based on my recent experience with the upgrade of Deep Blood, when I had to come out with new ideas to solve issues related to wing names

2009-06-11T16:42:00Z

Improvement of the Wings management section. The edit is based on my recent experience with the upgrade of Deep Blood, when I had to come out with new ideas to solve issues related to wing names

← Older revision		Revision as of 16:42, 11 June 2009
Line 103:		Line 103:
	To be filled in later.		To be filled in later.

	===~~Hostile wings~~ management===		===Wings management===
	Although waved wings are rare in main campaigns, their use in custom campaigns is notable. For several reasons, an upgrader may have to change the number of waves and/or the delay between waves according to the reports compiled by testers:		Although waved wings are rare in main campaigns, their use in custom campaigns is notable. For several reasons, an upgrader may have to change the number of waves and/or the delay between waves according to the reports compiled by testers.

			====Names-related problems====
			:''See also:'' [[Friendly wing names\|''Friendly wing names'']], [[Enemy wing names\|''Enemy wing names'']]

			It's not rare to deal with misspelled or repetitive wing names. Although it's normal to have an ''Alpha'' wing in virtually every single mission, it's not possible to say the same thing if every mission of a campaign features a ''Cancer'' and/or ''Aries'' wing. Misspelled names, like ''Beema'' (Bheema) or ''Sagitarious'' (Sagittarius), are also unacceptable.

			Because renaming a wing in FRED resets that wing's orders and also leads to event/cue conflicts, not to mention the possibility of altering the contents of messages, the easiest way to change wing names is using Notepad. Use the program to open the mission and scroll down the file until you find the list of wings. Take note of the repetitive and/or misspelled names and then decide which names you're going to use instead. Use the search function of Notepad to ensure that no ships/messages have the name you're willing to add (read below for more info about this possible conflict) and then use the same function to find each reference to the wing name that is in dire need of changes. The search function should point you to: each ship of the wing, the wing's entry in the list of wings, eventual directives related to the wing, eventual arrival cues/event conditions that are related to the wing, message names and the content of some messages. Changing the name via Notepad will effectively do the job. Be careful when editing a mission via Notepad, though - any errors would result in certain mission corruption.

			Please note how it's not that hard to have individual ships with names that match perfectly those used for wings. It's the case of transports and freighters, which usually have conventional names like ''Capricorn 1'' or ''Iota 2'' without being part of any wings. For this reason, before replacing a wing's name with another, it's extremely important to use the search function of Notepad to verify wheter or not that name is used for another ship - FRED surely won't tolerate both a combat spacecraft and a transport/freighter with the same name, like ''Capricorn 1''.

			====Waves-related problems====
			A bad management of waves oftentimes results in serious balance problems. One of the most common things testers notice is how some enemy wings respawn too quickly and/or their number of waves is exaggerated. Thanks to simple and effective edits, those issues can be solved. One of the main advantages is the fact that, unlike many other changes, this has minimal to nonexistent effects on storytelling.

	'''Number of waves:''' <br>		'''Number of waves:''' <br>