Capture Missions - Revision history

Yarn: Corrected spelling and hyphenation

2016-03-16T08:01:37Z

Corrected spelling and hyphenation

← Older revision		Revision as of 08:01, 16 March 2016
Line 7:		Line 7:

	*The next major problem you will face is the FreeSpace AI. Just ordering them to disable and/or disarm a ship is not enough. You must then remind them that the vessel is now off limits as far as attacking is concerned. There are several ways to accomplish this:<br>		*The next major problem you will face is the FreeSpace AI. Just ordering them to disable and/or disarm a ship is not enough. You must then remind them that the vessel is now off limits as far as attacking is concerned. There are several ways to accomplish this:<br>
	**Adding Ignore - Ship AI to friendly fighters. This will work, but must be added to all ships in the field of battle to be effective.		**Adding Ignore Ship AI to friendly fighters - This will work, but must be added to all ships in the field of battle to be effective.
	**Protecting the disabled Ship - This has the same effect as the ignore AI directives, with much less intensive SEXPing.		**Protecting the disabled Ship - This has the same effect as the ignore AI directives, with much less intensive SEXPing.
	**Changing the IFF of the disabled ship - This will work, but is not ~~reccomended~~, as it implies that the ship has become friendly, rather than simply having been subdued. Moreover, this will cause any hostile fighters that may warp in to protect it to regard it as an enemy (though this may be beneficial if, for example, they would rather destroy the ship than see its crew fall into enemy hands). Volition used this method.		**Changing the IFF of the disabled ship - This will work, but is not recommended, as it implies that the ship has become friendly, rather than simply having been subdued. Moreover, this will cause any hostile fighters that may warp in to protect it to regard it as an enemy (though this may be beneficial if, for example, they would rather destroy the ship than see its crew fall into enemy hands). Volition used this method.
	*Just as your wingmen will continue attacking a disabled ship, so will that ship keep attacking your wingmen if you do not order it not to. If you're not changing its AI to friendly, remember to lock all the turrets and beams of a surrendering ship.		*Just as your wingmen will continue attacking a disabled ship, so will that ship keep attacking your wingmen if you do not order it not to. If you're not changing its AI to friendly, remember to lock all the turrets and beams of a surrendering ship.
	*Use the escort list wisely, and remember that any vessels doing the capturing should be placed on this list. Lack of escorted vessels is a classic sign of less than stellar mission, and should be avoided.		*Use the escort list wisely, and remember that any vessels doing the capturing should be placed on this list. Lack of escorted vessels is a classic sign of less than stellar mission, and should be avoided.

The Force: Undo revision 38738 by Hired (Talk)

2012-06-19T08:41:40Z

Undo revision 38738 by Hired (Talk)

← Older revision	Revision as of 08:41, 19 June 2012
(No difference)

Scourge of Ages: Added "disarmed" to last paragraph.

2012-03-31T06:48:06Z

Added "disarmed" to last paragraph.

← Older revision		Revision as of 06:48, 31 March 2012
Line 18:		Line 18:
	*Keep in mind the potential for multiple points of entry on disabled vessels. Many ships have multiple dockpoints which can now be accessed thanks to the Source Code Project's multidocking code, and larger vessels may be able to be infiltrated through their fighterbays.		*Keep in mind the potential for multiple points of entry on disabled vessels. Many ships have multiple dockpoints which can now be accessed thanks to the Source Code Project's multidocking code, and larger vessels may be able to be infiltrated through their fighterbays.
	*Keep in mind that a disabled vessel should not warp under its own power unless its engines are repaired, and while a docked vessel can warp out and take the captured vessel with it, this should, ideally, only occur between vessels of comparable size.		*Keep in mind that a disabled vessel should not warp under its own power unless its engines are repaired, and while a docked vessel can warp out and take the captured vessel with it, this should, ideally, only occur between vessels of comparable size.
	*'''Note that non-friendly ~~ships~~ that are part of a wing and that have been disabled will self-destruct after a short period of time.''' This is intentional behavior but can be surprising and frustrating for FREDders trying to create a capture mission for an enemy wingman. To avoid this behavior, set the ship to friendly after it is disabled, or remove it from the wing. Note that Arjuna 1 in [[Enter the Dragon]] was not part of a wing.		*'''Note that non-friendly fighters that are part of a wing and that have been disabled ''or'' disarmed will self-destruct after a short period of time.''' This is intentional behavior but can be surprising and frustrating for FREDders trying to create a capture mission for an enemy wingman. To avoid this behavior, set the ship to friendly after it is disabled, or remove it from the wing. Note that Arjuna 1 in [[Enter the Dragon]] was not part of a wing.

	[[Category:FRED Tips]]		[[Category:FRED Tips]]

Goober5000 at 03:47, 31 October 2011

2011-10-31T03:47:59Z

← Older revision		Revision as of 03:47, 31 October 2011
Line 18:		Line 18:
	*Keep in mind the potential for multiple points of entry on disabled vessels. Many ships have multiple dockpoints which can now be accessed thanks to the Source Code Project's multidocking code, and larger vessels may be able to be infiltrated through their fighterbays.		*Keep in mind the potential for multiple points of entry on disabled vessels. Many ships have multiple dockpoints which can now be accessed thanks to the Source Code Project's multidocking code, and larger vessels may be able to be infiltrated through their fighterbays.
	*Keep in mind that a disabled vessel should not warp under its own power unless its engines are repaired, and while a docked vessel can warp out and take the captured vessel with it, this should, ideally, only occur between vessels of comparable size.		*Keep in mind that a disabled vessel should not warp under its own power unless its engines are repaired, and while a docked vessel can warp out and take the captured vessel with it, this should, ideally, only occur between vessels of comparable size.
			*'''Note that non-friendly ships that are part of a wing and that have been disabled will self-destruct after a short period of time.''' This is intentional behavior but can be surprising and frustrating for FREDders trying to create a capture mission for an enemy wingman. To avoid this behavior, set the ship to friendly after it is disabled, or remove it from the wing. Note that Arjuna 1 in [[Enter the Dragon]] was not part of a wing.

	[[Category:FRED Tips]]		[[Category:FRED Tips]]

Mobius: Link to the Disarming ships article added. Also, "civvilian" ---> "civilian"

2009-06-07T10:12:37Z

Link to the Disarming ships article added. Also, "civvilian" ---> "civilian"

← Older revision		Revision as of 10:12, 7 June 2009
Line 4:		Line 4:

	Capture missions can be quite difficult to make and fully test, largely because of the design of the FreeSpace AI, which is geared towards destroying things, rather than simply damaging them enough to capture. Moreover, making a coherent and realistic plot for these missions is also potentially difficult. When FREDding, bear the following suggestions in mind: <br>		Capture missions can be quite difficult to make and fully test, largely because of the design of the FreeSpace AI, which is geared towards destroying things, rather than simply damaging them enough to capture. Moreover, making a coherent and realistic plot for these missions is also potentially difficult. When FREDding, bear the following suggestions in mind: <br>
	*Decide early on exactly how much resistance the vessel you are capturing will put up, and how much you want the player to do to make the area safe for any capturing vessels. [[Shivans\|Shivan]] ships, for example, will need to be entirely disabled and disarmed before they can be captured, whereas ~~civillian~~ ships may give up after simply losing their engines.		*Decide early on exactly how much resistance the vessel you are capturing will put up, and how much you want the player to do to make the area safe for any capturing vessels. [[Shivans\|Shivan]] ships, for example, will need to be entirely disabled and disarmed before they can be captured, whereas civilian ships may give up after simply losing their engines. Read [[Disarming ships\|this]] article for additional hints.

	*The next major problem you will face is the FreeSpace AI. Just ordering them to disable and/or disarm a ship is not enough. You must then remind them that the vessel is now off limits as far as attacking is concerned. There are several ways to accomplish this:<br>		*The next major problem you will face is the FreeSpace AI. Just ordering them to disable and/or disarm a ship is not enough. You must then remind them that the vessel is now off limits as far as attacking is concerned. There are several ways to accomplish this:<br>

TopAce: spelling, typos, capitals

2008-12-16T14:08:45Z

spelling, typos, capitals

Black Wolf: Major Rewrite - gave examples, and tried to make it flow better, more readable + added some tips of my own.

2008-12-16T12:56:23Z

Major Rewrite - gave examples, and tried to make it flow better, more readable + added some tips of my own.

← Older revision		Revision as of 12:56, 16 December 2008
Line 1:		Line 1:
	'''Capture missions''' ~~are probably~~ the ~~hardest~~ and ~~most nerve-consuming~~ to make and test. ~~Bear~~ the following suggestions in mind: <br>		Often, during the course of your campaign, it may become neccesary to capture, rather than destroy, an enemy vessel. Missions involving this tactic can be reffered to as '''Capture missions'''. Examples of this type of mission would be [[Enter the Dragon]] and [[First Strike]] in Freespace 1, with First Strike more typical of the way this mission type is often encountered in user made campaigns.
	*~~Given~~ the ~~fact~~ the ~~AI in FreeSpace 2 is not smart enough~~ to ~~take~~ the ~~goals into consideration~~, ~~they tend~~ to ~~attack~~ and ~~eventually destroy the ship~~ you will ~~have~~ to ~~capture~~. ~~To block~~ this, ~~use~~ the ~~change~~-~~iff SEXP and change~~ the ~~ship to friendly after it is disarmed and disabled~~.
	*~~Not putting~~ the ~~capture party's transport into~~ the ~~escort list might suggest two facts: <br>~~		==FREDding a Capture Mission==
	~~You did~~ not ~~place~~ it ~~into~~ the ~~escort list because~~ it ~~does not come under attack during~~ the ~~mission <br>~~
	~~You neglected~~ your ~~mission <br>~~		Capture missions can be quite difficult to make and fully test, largely because of the design of the Freespace AI, which is geared towards destroying things, rather than simply damaging them enough to capture. Moreover, making a coherent and realistic plot for these missions is also potentially difficult. When FREDding, bear the following suggestions in mind: <br>
	So, in a ~~word~~, ~~use~~ the ~~Escort~~ list ~~<br>~~		*Decide early on exactly how much resistance the vessel you are capturing will put up, and how much you want the player to do to make the area safe for any capturing vessels. Shivan ships, for example, will need to be entirely disabled and disarmed before they can be captured, whereas civillian ships may give up after simply losing their engines.
	*~~Order~~ the ~~player~~ to ~~destroy the Communication subsystem~~. ~~Otherwise, using the~~ intact ~~communication systems, the enemy can~~ call in for reinforcements. If the ~~player fails~~ to ~~disable the communications in time, have some more enemy forces arrive~~. If you ~~are evil enough, you will send in a force that is impossible to beat~~, ~~making~~ the ~~disablement of the communication system obligatory~~.
	*~~Make~~ the capture transport ~~send~~ messages often, keeping the pilots updated about the status of the capture operation.		*The next major problem you will face is the Freespace AI. Just ordering them to disable and/or disarm a ship is not enough. You must then remind them that the vessel is now off limits as far as attacking is concerned. There are several ways to accomplish this:<br>
	*~~If you think it is~~ a ~~good idea~~, ~~you can make the capture party fail~~ and ~~send in~~ a ~~new transport or order~~ the ~~pilots to leave~~, ~~considering~~ the mission a failure.		**Adding Ignore - Ship AI to friendly fighters. This will work, but must be added to all ships in the field of battle to be effective.
	*If you have used the change-iff to ~~make~~ the ~~capturable ship friendly~~, ~~do not forget that~~ the enemy ~~also considers~~ it ~~friendly~~. ~~Therefore~~, ~~they do~~ not ~~intend~~ to ~~destroy it until they see it is easier~~ to ~~destroy than to defend it~~.		**Protecting the disabled Ship - This has the same effect as the ignore AI directives, with much less intensive sexping.
	*~~The above hint should also work~~ in ~~reverse: If~~ the ~~friendly team considers~~ the ~~mission a failure~~, ~~they should attempt~~ to ~~destroy~~ that vessel~~. Do~~ this ~~if the capture transport is destroyed~~.		**Changing the IFF of the disabled ship - This will work, but is not reccomended, as it implies that the ship has become friendly, rather than simply having been subdued. Moreover, this will cause any hostile fighters that may warp in to protect it to regard it as an enemy (though this may be beneficial if, for example, they would rather destroy the ship than see its crew fall into enemy hands).

			*Just as your wingmen will continue attacking a disabled ship, so to will that ship keep attacking your wingmen in you do not order it not to. If you're not changing its AI to friendly, remember to lock all the turrets and beams of a surrendering ship.

			*Use the escort list wisely, and remember that any vessels doing the capturing should be placed on this list. Lack of escorted vessels is a classic sign of less than stellar mission, and should be avoided.
			*Weapons and engines are not the only subsystems of relevance to a captured ship. An intact communications subsystem may allow a vessel to call for reinforcements, while a destroyed navigation subsytem may prevent a ship from jumping to subspace even when its engines are still intact. Use these non-core subsystems in your missions, but be aware of the amount of damage you're doing to a ship. Smaller vessels may take considerable damage if you destroy multiple subsystems and turrets, potentially risking their unintentional destruction by the player.
			*Ensure the capture transport sends messages often, keeping the pilots updated about the status of the capture operation.
			*The capture transport will make a tempting target for hostile fighters, and its protection should be a goal for the player. Make sure that you have contingencies in place should this first attempt at capturing fail, whether that be sending more transports, or declaring the mission a failure. This may be grounds to trigger an order to destroy the disabled vessel, rather than allow the enemy to reclaim and repair it.
			*Be sensible in your choice of capture vessel. While a [[GTS Hygeia]] is perfectly appropriate for capturing a disabled enemy fighter, it almost certaily will not be able to deploy enough troops to subdue the crew of a destroyer.
			*Keep in mind the potential for multiple points of entry on disabled vessels. Many ships have multiple dockpoints which can now be accessed thanks to the Source Code Projects multidocking code, and larger vessels may be able to be infiltrated through their fighterbays.
			*Keep in mind that a disabled vessel should not warp under its own power unless its engines are repaired, and while a docked vessel can warp out and take the captured vessel with it, this should, ideally, only occur between vessels of comparable size.


	[[Category:FRED Tips]]		[[Category:FRED Tips]]

TopAce at 19:08, 26 June 2006

2006-06-26T19:08:53Z

← Older revision		Revision as of 19:08, 26 June 2006
Line 1:		Line 1:
	~~==Capture Missions==~~		'''Capture missions''' are probably the hardest and most nerve-consuming to make and test. Bear the following suggestions in mind: <br>

	Capture missions are probably the hardest and most nerve-consuming to make and test. Bear the following suggestions in mind: <br>
	*Given the fact the AI in FreeSpace 2 is not smart enough to take the goals into consideration, they tend to attack and eventually destroy the ship you will have to capture. To block this, use the change-iff SEXP and change the ship to friendly after it is disarmed and disabled.		*Given the fact the AI in FreeSpace 2 is not smart enough to take the goals into consideration, they tend to attack and eventually destroy the ship you will have to capture. To block this, use the change-iff SEXP and change the ship to friendly after it is disarmed and disabled.
	*Not putting the capture party's transport into the escort list might suggest two facts: <br>		*Not putting the capture party's transport into the escort list might suggest two facts: <br>

Shade: changed category

2006-04-13T23:31:20Z

changed category

← Older revision		Revision as of 23:31, 13 April 2006
Line 13:		Line 13:
	*The above hint should also work in reverse: If the friendly team considers the mission a failure, they should attempt to destroy that vessel. Do this if the capture transport is destroyed.		*The above hint should also work in reverse: If the friendly team considers the mission a failure, they should attempt to destroy that vessel. Do this if the capture transport is destroyed.

	[[Category:FRED]]		[[Category:FRED Tips]]

Wanderer: added category

2006-04-03T17:16:25Z

added category

← Older revision		Revision as of 17:16, 3 April 2006
Line 12:		Line 12:
	*If you have used the change-iff to make the capturable ship friendly, do not forget that the enemy also considers it friendly. Therefore, they do not intend to destroy it until they see it is easier to destroy than to defend it.		*If you have used the change-iff to make the capturable ship friendly, do not forget that the enemy also considers it friendly. Therefore, they do not intend to destroy it until they see it is easier to destroy than to defend it.
	*The above hint should also work in reverse: If the friendly team considers the mission a failure, they should attempt to destroy that vessel. Do this if the capture transport is destroyed.		*The above hint should also work in reverse: If the friendly team considers the mission a failure, they should attempt to destroy that vessel. Do this if the capture transport is destroyed.

			[[Category:FRED]]

← Older revision		Revision as of 14:08, 16 December 2008
Line 1:		Line 1:
	Often, during the course of your campaign, it may become neccesary to capture, rather than destroy, an enemy vessel. Missions involving this tactic can be ~~reffered~~ to as '''~~Capture~~ missions'''. Examples of this type of mission would be [[Enter the Dragon]] and [[First Strike]] in ~~Freespace~~ 1, with First Strike more typical of the way this mission type is often encountered in user made campaigns.		Often, during the course of your campaign, it may become neccesary to capture, rather than destroy, an enemy vessel. Missions involving this tactic can be referred to as '''capture missions'''. Examples of this type of mission would be [[Enter the Dragon]] and [[First Strike]] in FreeSpace 1, with First Strike more typical of the way this mission type is often encountered in user-made campaigns.

	==FREDding a Capture Mission==		==FREDding a Capture Mission==

	Capture missions can be quite difficult to make and fully test, largely because of the design of the ~~Freespace~~ AI, which is geared towards destroying things, rather than simply damaging them enough to capture. Moreover, making a coherent and realistic plot for these missions is also potentially difficult. When FREDding, bear the following suggestions in mind: <br>		Capture missions can be quite difficult to make and fully test, largely because of the design of the FreeSpace AI, which is geared towards destroying things, rather than simply damaging them enough to capture. Moreover, making a coherent and realistic plot for these missions is also potentially difficult. When FREDding, bear the following suggestions in mind: <br>
	*Decide early on exactly how much resistance the vessel you are capturing will put up, and how much you want the player to do to make the area safe for any capturing vessels. Shivan ships, for example, will need to be entirely disabled and disarmed before they can be captured, whereas civillian ships may give up after simply losing their engines.		*Decide early on exactly how much resistance the vessel you are capturing will put up, and how much you want the player to do to make the area safe for any capturing vessels. [[Shivans\|Shivan]] ships, for example, will need to be entirely disabled and disarmed before they can be captured, whereas civillian ships may give up after simply losing their engines.

	*The next major problem you will face is the ~~Freespace~~ AI. Just ordering them to disable and/or disarm a ship is not enough. You must then remind them that the vessel is now off limits as far as attacking is concerned. There are several ways to accomplish this:<br>		*The next major problem you will face is the FreeSpace AI. Just ordering them to disable and/or disarm a ship is not enough. You must then remind them that the vessel is now off limits as far as attacking is concerned. There are several ways to accomplish this:<br>
	**Adding Ignore - Ship AI to friendly fighters. This will work, but must be added to all ships in the field of battle to be effective.		**Adding Ignore - Ship AI to friendly fighters. This will work, but must be added to all ships in the field of battle to be effective.
	**Protecting the disabled Ship - This has the same effect as the ignore AI directives, with much less intensive ~~sexping~~.		**Protecting the disabled Ship - This has the same effect as the ignore AI directives, with much less intensive SEXPing.
	**Changing the IFF of the disabled ship - This will work, but is not reccomended, as it implies that the ship has become friendly, rather than simply having been subdued. Moreover, this will cause any hostile fighters that may warp in to protect it to regard it as an enemy (though this may be beneficial if, for example, they would rather destroy the ship than see its crew fall into enemy hands).		**Changing the IFF of the disabled ship - This will work, but is not reccomended, as it implies that the ship has become friendly, rather than simply having been subdued. Moreover, this will cause any hostile fighters that may warp in to protect it to regard it as an enemy (though this may be beneficial if, for example, they would rather destroy the ship than see its crew fall into enemy hands). Volition used this method.
			*Just as your wingmen will continue attacking a disabled ship, so will that ship keep attacking your wingmen if you do not order it not to. If you're not changing its AI to friendly, remember to lock all the turrets and beams of a surrendering ship.
	*Just as your wingmen will continue attacking a disabled ship, so to will that ship keep attacking your wingmen in you do not order it not to. If you're not changing its AI to friendly, remember to lock all the turrets and beams of a surrendering ship.

	*Use the escort list wisely, and remember that any vessels doing the capturing should be placed on this list. Lack of escorted vessels is a classic sign of less than stellar mission, and should be avoided.		*Use the escort list wisely, and remember that any vessels doing the capturing should be placed on this list. Lack of escorted vessels is a classic sign of less than stellar mission, and should be avoided.
	*Weapons and engines are not the only subsystems of relevance to a captured ship. An intact communications subsystem may allow a vessel to call for reinforcements, while a destroyed navigation subsytem may prevent a ship from jumping to subspace even when its engines are still intact. Use these non-core subsystems in your missions, but be aware of the amount of damage you're doing to a ship. Smaller vessels may take considerable damage if you destroy multiple subsystems and turrets, potentially risking their unintentional destruction by the player.		*Weapons and engines are not the only subsystems of relevance to a captured ship. An intact communications subsystem may allow a vessel to call for reinforcements, while a destroyed navigation subsytem may prevent a ship from jumping to subspace even when its engines are still intact. Use these non-core subsystems in your missions, but be aware of the amount of damage you're doing to a ship. Smaller vessels may take considerable damage if you destroy multiple subsystems and turrets, potentially risking their unintentional destruction by the player.
	*Ensure the capture transport sends messages often, keeping the pilots updated about the status of the capture operation.		*Ensure the capture transport sends messages often, keeping the pilots updated about the status of the capture operation.
	*The capture transport will make a tempting target for hostile fighters, and its protection should be a goal for the player. Make sure that you have contingencies in place should this first attempt at capturing fail, whether that be sending more transports, or declaring the mission a failure. This may be grounds to trigger an order to destroy the disabled vessel, rather than allow the enemy to reclaim and repair it.		*The capture transport will make a tempting target for hostile fighters, and its protection should be a goal for the player. Make sure that you have contingencies in place should this first attempt at capturing fail, whether that be sending more transports, or declaring the mission a failure. This may be grounds to trigger an order to destroy the disabled vessel, rather than allow the enemy to reclaim and repair it.
	*Be sensible in your choice of capture vessel. While a [[GTS Hygeia]] is perfectly appropriate for capturing a disabled enemy fighter, it almost ~~certaily~~ will not be able to deploy enough troops to subdue the crew of a destroyer.		*Be sensible in your choice of capture vessel. While a [[GTS Hygeia\|GTS ''Hygeia'']] is perfectly appropriate for capturing a disabled enemy fighter, it almost certainly will not be able to deploy enough troops to subdue the crew of a destroyer.
	*Keep in mind the potential for multiple points of entry on disabled vessels. Many ships have multiple dockpoints which can now be accessed thanks to the Source Code ~~Projects~~ multidocking code, and larger vessels may be able to be infiltrated through their fighterbays.		*Keep in mind the potential for multiple points of entry on disabled vessels. Many ships have multiple dockpoints which can now be accessed thanks to the Source Code Project's multidocking code, and larger vessels may be able to be infiltrated through their fighterbays.
	*Keep in mind that a disabled vessel should not warp under its own power unless its engines are repaired, and while a docked vessel can warp out and take the captured vessel with it, this should, ideally, only occur between vessels of comparable size.		*Keep in mind that a disabled vessel should not warp under its own power unless its engines are repaired, and while a docked vessel can warp out and take the captured vessel with it, this should, ideally, only occur between vessels of comparable size.


	[[Category:FRED Tips]]		[[Category:FRED Tips]]