Talk:XcomUtil - Revision history

Mathalor: /* bladefirelight.com */ new section

2017-01-19T20:12:09Z

bladefirelight.com: new section

← Older revision		Revision as of 20:12, 19 January 2017
Line 606:		Line 606:
	* Upon returning to the geoscape, it is likely that the game "realizes" that interceptors are not supposed to carry crew or equipment, and promptly destroys the passengers and equipment that it is carrying.</blockquote>		* Upon returning to the geoscape, it is likely that the game "realizes" that interceptors are not supposed to carry crew or equipment, and promptly destroys the passengers and equipment that it is carrying.</blockquote>
	::I think that the reason for losing the crew and equipment actually is not due to the game waking up to the fact that interceptors cannot hold them. In fact even with the game modded to allow craft to transport said soldiers and material I would be willing to bet that you will still lose them if the battlescape fails due to there being no map for the ship. The reason is because when the mission is started it places those soldiers and equipment on the terrain, but for the craft which aren't normally capable of it the game doesn't know where to place them. Thus when the mission fails none of your soldiers or equipment were actually in the game map to be retrieved, resulting in their loss. In fact it is possible that even with the craft map and modifications to the exe, you may still lose all soldiers and equipment if you don't have XcomUtil to place them on the map built for that mission.[[User:Mannon\|Mannon]] 19:01, 3 April 2011 (EDT)		::I think that the reason for losing the crew and equipment actually is not due to the game waking up to the fact that interceptors cannot hold them. In fact even with the game modded to allow craft to transport said soldiers and material I would be willing to bet that you will still lose them if the battlescape fails due to there being no map for the ship. The reason is because when the mission is started it places those soldiers and equipment on the terrain, but for the craft which aren't normally capable of it the game doesn't know where to place them. Thus when the mission fails none of your soldiers or equipment were actually in the game map to be retrieved, resulting in their loss. In fact it is possible that even with the craft map and modifications to the exe, you may still lose all soldiers and equipment if you don't have XcomUtil to place them on the map built for that mission.[[User:Mannon\|Mannon]] 19:01, 3 April 2011 (EDT)

			== bladefirelight.com ==

			When I download the file, Superantivirus claims that it is infected with Trojan.Agent/Gen-SpyNet.

			Is this a false infection? Is anyone else noticing this?

			Is there a mirror for this download?

Sherlock: /* Using XcomUtil without installation */

2013-01-30T22:58:55Z

Using XcomUtil without installation

← Older revision		Revision as of 22:58, 30 January 2013
Line 557:		Line 557:

	Not the most important of features to expand on, but worth considering now that a lot more is known about the game since the command was introduced. -[[User:NKF\|NKF]] 02:06, 23 April 2010 (EDT)		Not the most important of features to expand on, but worth considering now that a lot more is known about the game since the command was introduced. -[[User:NKF\|NKF]] 02:06, 23 April 2010 (EDT)

			=== Using XcomUtil without installation ===

			XcomUtil needs installation in order to use it. Installation modifies some things, which the user may not want for some reason. But xcomutil.exe work well with an unmodified game. A good example is just listing things (LST or DIS) but in fact most (or even all) functions of the program do not depend on any changes made by XcomUtil installer - so in fact there is no need for installation. Despite of this, now, in order to use the program without any modification of the game, you must copy XcomUtil files, and next copy manually xcusetup.xcf from another installation to flags. An alternative method is to backup the original installation of the game, next to install XcomUtil, and next to copy back the original installation, with replacing all files.

			It would be much simpler just to copy xcomutil.exe, and to have a possibility to run it without all that installing procedure. Unfortunately, as for now it is impossible as xcomutil.exe checks if the package has been installed or not. And if it does not find the flag file, it ends working.

			[[User:Sherlock\|Sherlock]] 17:58, 30 January 2013 (EST)

	==See Also==		==See Also==

BladeFireLight: /* XcomUtil 9.7 */ No longer Beta

2012-04-08T13:07:38Z

XcomUtil 9.7: No longer Beta

← Older revision		Revision as of 13:07, 8 April 2012
Line 1:		Line 1:
	=XcomUtil 9.7=		=XcomUtil 9.7=

	9.7 ~~Beta~~ is available on www.bladefirelight.com		9.7 is available on www.bladefirelight.com

	==Release Notes==		==Release Notes==

BladeFireLight: /* XcomUtil 9.7 Beta */

2012-04-08T13:06:25Z

XcomUtil 9.7 Beta

← Older revision		Revision as of 13:06, 8 April 2012
Line 1:		Line 1:
	=XcomUtil 9.7 ~~Beta~~=		=XcomUtil 9.7=

	9.7 Beta is available on www.bladefirelight.com		9.7 Beta is available on www.bladefirelight.com

	==Release Notes==		==Release Notes==

	~~This is a Beta, so backup your files before using. And check back often for newer builds.~~

	New in this version.		New in this version.

	*Major ~~overhall~~ of the installer (XcuSetup) and the inclusion of 16/32bit exe's to support both DOSBox and Windows Vista/7 x64.		*Major overhaul of the installer (XcuSetup) and the inclusion of 16/32bit exe's to support both DOSBox and Windows Vista/7 x64.
	*New ~~subfolders~~ added to hold supporting files making the install cleaner		*New sub folders added to hold supporting files making the install cleaner
	*New XcuSetup command line arguments were added to XcuSetup allowing for silent install and uninstallation.		*New XcuSetup command line arguments were added to XcuSetup allowing for silent install and uninstallation.
	*New XcuSetup option for debugging the install (XcuSetup debug) creating XcomUtil\debug.txt.		*New XcuSetup option for debugging the install (XcuSetup debug) creating XcomUtil\debug.txt.
	*New command line argument "nobackup" skips backup only if it has been ran ~~atleast~~ once.		*New command line argument "nobackup" skips backup only if it has been ran at least once.
	*XcuSetup can now have minimal impact on the game.		*XcuSetup can now have minimal impact on the game.
	**Almost all options default to NO (Only Split Windows EXE set to Yes).		**Almost all options default to NO (Only Split Windows EXE set to Yes).
Line 33:		Line 31:
	*Support for the DOS/Window STEAM Install.		*Support for the DOS/Window STEAM Install.
	**Installer will detect STEAM and change steam launcher to start the XcomUtil Steam Menu (can be re-installed with XcomUtil\SteamSetup.bat		**Installer will detect STEAM and change steam launcher to start the XcomUtil Steam Menu (can be re-installed with XcomUtil\SteamSetup.bat
			**Force Split EXE on STEAM. Fixes issues with setup failing.
	*Out of the box support for UFO Extender. XcuSetup will detect it and ask if you want RunXcom to use it.		*Out of the box support for UFO Extender. XcuSetup will detect it and ask if you want RunXcom to use it.
	*XcuSetup ~~can~~ be run from windows and RunXcom run from DosBox		*RunXcom can detect if it's in DosBox. Allowing XcuSetup to be run from windows and RunXcom run from DosBox.
	*Hybrid Colors updated based on BombBloke's pallets.		*Hybrid Colors updated based on BombBloke's pallets.
	*EQL flag allowed any turn.		*EQL flag allowed any turn.
	*Add Xcom UFO Italian Support.		*Add Xcom UFO Italian Support.
	*Auto Combat will not run on second half of two part using first parts saved data.
	*Auto Combat will no longer run if combat was won.
	*MIA Recovery on won combat only.
	*MIA Recovery no longer recovering units that bleed to death.
	*Auto equip no longer triggers on second part of 2 stage missions.
	*Combine clips skiped if between stages of 2-3 part missions.
	*Updated f0dders ReadMe per his request. (XcomUtil\bugfix-readme.txt)		*Updated f0dders ReadMe per his request. (XcomUtil\bugfix-readme.txt)
	*Add-on support added. see XcomUtil\XcomUtil.txt and XcomUtil\Addon\Example.txt		*Add-on support added. see XcomUtil\XcomUtil.txt and XcomUtil\Addon\Example.txt
	*Prompted Terrain in BattleField Generator allows to abort or use of current setting.		*Prompted Terrain in BattleField Generator allows to abort and use of current setting.
	*~~Beta versions include~~		*"debug" command arugument createds XcomUtil\Debug.txt and adds debug info to XcomUtil\XcomUtil.log
	**XcomUtil\XcomUtil.log ~~includes lots of debug info~~		*Original Sound Effects from UFO were re-sampled to work with 1.4 and CE.
	**XcomUtil\Debug.~~txt created by default (Release will need "debug" command argument)~~

	Removed from this versions		Removed from this versions

	*New Desert and Urban terrain. (Will be added once I have a C++ version of the Java Terrain Edit.)		*New Desert and Urban terrain. (Will be added once I have a C++ version of the Java Terrain Edit.)
	*Expanded capacity Laviathan, Hammerhead and Avenger (maps ~~avalible~~ in XcomUtil\Patches)		*Expanded capacity Laviathan, Hammerhead and Avenger (maps available in XcomUtil\Patches)
			*Unit placement for Alien Bases

			Bugs fixed
	~~NOTE: If you use DosBox, this requires DosBox 0~~.~~72 (Does not work~~ on 0.~~73 due to buffer overflow setting ERRORLVEL)~~		*Auto Combat will no longer run if combat was won.
			*MIA Recovery on won combat only.
	~~===Build 435===~~		*MIA Recovery no longer recovering units that bleed to death.
			*Auto equip no longer triggers on second part of 2 stage missions.
	~~Original Sound Effects from UFO were re-sampled~~ to ~~work with 1~~.~~4 and CE~~.		*Combine clips skiped if between stages of 2-3 part missions.

	*~~Add Category to option headers~~.
	*Improve randomness by using current time instead of game date/time in srand()		*Improve randomness by using current time instead of game date/time in srand()
	*Added Option to keep Current terrain/UFO to BFG.
	*Original UFO 1.2 Sounds for Geoscape and Tactical added as an option for UFO 1.4 and CE.
	*Force Split EXE on STEAM. Fixes issues with setup failing.
	*Reset Laser/Gauss craft weapons stats to be default.
	*Example addon now uses different flag extension to avoid deletion by XcuSetup
	*fix issue with Lab Screen on DosBox always screening

	~~===Build 442===~~

	*Add Batch file for Java Terrain Editor as an example for thoes that want to use it.
	*Fix BFG placement of units in Alien Base Terrain.
	*Autocombat: All units with health <= fatal wounds dies before autocombat calculates win threshold.
	*Autocombat: Fixed MIA units on WIN.

	~~--[[User~~:~~BladeFireLight\|BladeFireLight]] 18:16~~, ~~26 March 2010~~ (~~EDT~~)		NOTE: If you use DosBox, this requires DosBox 0.74 (Does not work on 0.73 due to buffer overflow setting ERRORLVEL)

	==Beta Discussion==		==Beta Discussion==

Mannon: /* Read The Fine Manual */

2011-04-03T23:01:36Z

Read The Fine Manual

← Older revision		Revision as of 23:01, 3 April 2011
Line 618:		Line 618:
	* The tactical portion of the mission fails because no battlescape configurations or terrain exist for the interceptor, since it was never meant to hold crew.		* The tactical portion of the mission fails because no battlescape configurations or terrain exist for the interceptor, since it was never meant to hold crew.
	* Upon returning to the geoscape, it is likely that the game "realizes" that interceptors are not supposed to carry crew or equipment, and promptly destroys the passengers and equipment that it is carrying.</blockquote>		* Upon returning to the geoscape, it is likely that the game "realizes" that interceptors are not supposed to carry crew or equipment, and promptly destroys the passengers and equipment that it is carrying.</blockquote>
	:I think that the reason for losing the crew and equipment actually is not due to the game waking up to the fact that interceptors cannot hold them. In fact even with the game modded to allow craft to transport said soldiers and material I would be willing to bet that you will still lose them if the battlescape fails due to there being no map for the ship. The reason is because when the mission is started it places those soldiers and equipment on the terrain, but for the craft which aren't normally capable of it the game doesn't know where to place them. Thus when the mission fails none of your soldiers or equipment were actually in the game map to be retrieved, resulting in their loss. In fact it is possible that even with the craft map and modifications to the exe, you may still lose all soldiers and equipment if you don't have XcomUtil to place them on the map built for that mission.[[User:Mannon\|Mannon]] 19:01, 3 April 2011 (EDT)		::I think that the reason for losing the crew and equipment actually is not due to the game waking up to the fact that interceptors cannot hold them. In fact even with the game modded to allow craft to transport said soldiers and material I would be willing to bet that you will still lose them if the battlescape fails due to there being no map for the ship. The reason is because when the mission is started it places those soldiers and equipment on the terrain, but for the craft which aren't normally capable of it the game doesn't know where to place them. Thus when the mission fails none of your soldiers or equipment were actually in the game map to be retrieved, resulting in their loss. In fact it is possible that even with the craft map and modifications to the exe, you may still lose all soldiers and equipment if you don't have XcomUtil to place them on the map built for that mission.[[User:Mannon\|Mannon]] 19:01, 3 April 2011 (EDT)

Mannon: /* Read The Fine Manual */

2011-04-03T23:01:18Z

Read The Fine Manual

← Older revision		Revision as of 23:01, 3 April 2011
Line 618:		Line 618:
	* The tactical portion of the mission fails because no battlescape configurations or terrain exist for the interceptor, since it was never meant to hold crew.		* The tactical portion of the mission fails because no battlescape configurations or terrain exist for the interceptor, since it was never meant to hold crew.
	* Upon returning to the geoscape, it is likely that the game "realizes" that interceptors are not supposed to carry crew or equipment, and promptly destroys the passengers and equipment that it is carrying.</blockquote>		* Upon returning to the geoscape, it is likely that the game "realizes" that interceptors are not supposed to carry crew or equipment, and promptly destroys the passengers and equipment that it is carrying.</blockquote>
			:I think that the reason for losing the crew and equipment actually is not due to the game waking up to the fact that interceptors cannot hold them. In fact even with the game modded to allow craft to transport said soldiers and material I would be willing to bet that you will still lose them if the battlescape fails due to there being no map for the ship. The reason is because when the mission is started it places those soldiers and equipment on the terrain, but for the craft which aren't normally capable of it the game doesn't know where to place them. Thus when the mission fails none of your soldiers or equipment were actually in the game map to be retrieved, resulting in their loss. In fact it is possible that even with the craft map and modifications to the exe, you may still lose all soldiers and equipment if you don't have XcomUtil to place them on the map built for that mission.[[User:Mannon\|Mannon]] 19:01, 3 April 2011 (EDT)

Spike: /* XcomUtil 9.7 Beta */

2010-11-03T20:48:00Z

XcomUtil 9.7 Beta

← Older revision		Revision as of 20:48, 3 November 2010
Line 171:		Line 171:
	*Research Help from Captured Aliens awards research help without checking first if you have Alien Containment at the base of origin. Resulting in dead aliens helping you with your enquiries! Possibly only applies to AutoCombat? [[User:Spike\|Spike]] 21:05, 14 March 2010 (EDT)		*Research Help from Captured Aliens awards research help without checking first if you have Alien Containment at the base of origin. Resulting in dead aliens helping you with your enquiries! Possibly only applies to AutoCombat? [[User:Spike\|Spike]] 21:05, 14 March 2010 (EDT)
	:: Ideally it would not only check for containment but also have a research item for it and check on how many scientist days had been reduced since the last combat and use that as a value for how much you get form the aliens still in containment. But that could just be a pipe dream. Checking for containment for now is a good idea. --[[User:BladeFireLight\|BladeFireLight]] 15:35, 16 March 2010 (EDT)		:: Ideally it would not only check for containment but also have a research item for it and check on how many scientist days had been reduced since the last combat and use that as a value for how much you get form the aliens still in containment. But that could just be a pipe dream. Checking for containment for now is a good idea. --[[User:BladeFireLight\|BladeFireLight]] 15:35, 16 March 2010 (EDT)

	*Additional multi-level mission bugs. See [[Talk:Known Bugs (TFTD)#Multi-part map ammo loss]]. Is XcomUtil attempting to teleport uncarried items back to base at the end of each level by default? If so, maybe this should be an explicit option in XCUSetup. Also, this routine may need to be fixed to detect items which are carried or loaded into weapons, but are not marked as owned/carried by a Soldier/Aquanaut. Typically this means ammo that is pre-loaded into weapons in the equip phase. This can be fixed either by doing a check to see if the item is loaded into a weapon, or by doing a "full fix" and marking the ammo item as carried by the Soldier/Aquanaut (presumably this doesn't break anything since I think it's what happens if you manually load the ammo into the weapon). [[User:Spike\|Spike]] 17:03, 1 November 2010 (UTC)

	* (Build 442) Prompts for "Pistol" not "Dart Gun" mod in TFTD. Also "Psionics" not "M.C.". [[User:Spike\|Spike]] 21:53, 1 November 2010 (UTC)		* (Build 442) Prompts for "Pistol" not "Dart Gun" mod in TFTD. Also "Psionics" not "M.C.". [[User:Spike\|Spike]] 21:53, 1 November 2010 (UTC)
Line 203:		Line 201:
	* You can get X-COM MIA if you abort a mission, even if everyone is in the exit. Possibly a second stage bug only? See [[Image:X-COM_MIA.zip]]. Note that this only affects the report - after mission all the X-COM troops are still available.		* You can get X-COM MIA if you abort a mission, even if everyone is in the exit. Possibly a second stage bug only? See [[Image:X-COM_MIA.zip]]. Note that this only affects the report - after mission all the X-COM troops are still available.
	:*NOT Fixed: This happens even on vanilla TFTD with that save. Given it's TFTD it could be an issue with the mapfiles. --[[User:BladeFireLight\|BladeFireLight]] 00:23, 24 February 2010 (EST)		:*NOT Fixed: This happens even on vanilla TFTD with that save. Given it's TFTD it could be an issue with the mapfiles. --[[User:BladeFireLight\|BladeFireLight]] 00:23, 24 February 2010 (EST)
	*Various second stage bugs - ammo clip recovery, crashes after autocombat of first stage, etc. Mainly for TFTD, but possibly Cydonia in UFO is also affected.		*Various second stage bugs - ammo clip recovery, crashes after autocombat of first stage, etc. Mainly for TFTD, but possibly Cydonia in UFO is also affected.
	:*Fixed: Clip recovery no longer ran between parts of 2-3 part missions. Autocombat only crashes on two part if you are aborting the second stage and the save in slot 10 is from the first stage. Stage comparisons are now done to abort autocombat if you do this.		:*Fixed: Clip recovery no longer ran between parts of 2-3 part missions. Autocombat only crashes on two part if you are aborting the second stage and the save in slot 10 is from the first stage. Stage comparisons are now done to abort autocombat if you do this.
			:*Fixed: [[Talk:Known Bugs (TFTD)#Multi-part map ammo loss\|Multi-part map ammo loss]].
	*Removal of Small Scout map / Survey Ship map, making it impossible to do these Battlescape missions.		*Removal of Small Scout map / Survey Ship map, making it impossible to do these Battlescape missions.
	:*Fixed: 9.7 only removes the maps if you use the BFG. I hope to have 9.8 not remove them at all. --[[User:BladeFireLight\|BladeFireLight]] 22:34, 7 February 2010 (EST)		:*Fixed: 9.7 only removes the maps if you use the BFG. I hope to have 9.8 not remove them at all. --[[User:BladeFireLight\|BladeFireLight]] 22:34, 7 February 2010 (EST)

Spike: /* Open Bugs */ SteamSetup prompts

2010-11-03T20:18:49Z

Open Bugs: SteamSetup prompts

← Older revision		Revision as of 20:18, 3 November 2010
Line 176:		Line 176:
	* (Build 442) Prompts for "Pistol" not "Dart Gun" mod in TFTD. Also "Psionics" not "M.C.". [[User:Spike\|Spike]] 21:53, 1 November 2010 (UTC)		* (Build 442) Prompts for "Pistol" not "Dart Gun" mod in TFTD. Also "Psionics" not "M.C.". [[User:Spike\|Spike]] 21:53, 1 November 2010 (UTC)

	* (Build 442) Steam instructions are confusing - should I run XCUSetup.bat first, then run SteamSetup.bat, then run Steam? Probably not. I think I should run SteamSetup.bat, then Steam, which will run XCUSetup.bat. But it's not very clear. Although the instructions are pretty explicit, why doesn't XCUSetup.bat terminate when it detects Steam? That's what confused me I think. I didn't expect to have to hit Ctrl-C at that point. ~~Also~~, ~~need~~ to ~~state the path~~ to SteamSetup.bat (.~~\XCOMUTIL\)~~. [[User:Spike\|Spike]] 21:53, 1 November 2010 (UTC)		* (Build 442) Steam instructions are confusing - should I run XCUSetup.bat first, then run SteamSetup.bat, then run Steam? Probably not. I think I should run SteamSetup.bat, then Steam, which will run XCUSetup.bat (or then I will directly run XCUSetup.bat). But it's not very clear. Although the instructions are pretty explicit, why doesn't XCUSetup.bat terminate when it detects Steam? That's what confused me I think. I didn't expect to have to hit Ctrl-C at that point. [[User:Spike\|Spike]] 21:53, 1 November 2010 (UTC)
			**As a nice to have, tell me to hit Ctrl-C to abort XCUSetup (and run SteamSetup.bat) when Steam is detected
			**As a nice to have, ''don't'' tell me to abort and run SteamSetup.bat, if I've already run SteamSetup.bat. [[User:Spike\|Spike]] 20:18, 3 November 2010 (UTC)

	==Fixed Bugs==		==Fixed Bugs==

Spike: /* Open Bugs */ TFTD text, Steam setup instructions,

2010-11-01T21:53:01Z

Open Bugs: TFTD text, Steam setup instructions,

← Older revision		Revision as of 21:53, 1 November 2010
Line 173:		Line 173:

	*Additional multi-level mission bugs. See [[Talk:Known Bugs (TFTD)#Multi-part map ammo loss]]. Is XcomUtil attempting to teleport uncarried items back to base at the end of each level by default? If so, maybe this should be an explicit option in XCUSetup. Also, this routine may need to be fixed to detect items which are carried or loaded into weapons, but are not marked as owned/carried by a Soldier/Aquanaut. Typically this means ammo that is pre-loaded into weapons in the equip phase. This can be fixed either by doing a check to see if the item is loaded into a weapon, or by doing a "full fix" and marking the ammo item as carried by the Soldier/Aquanaut (presumably this doesn't break anything since I think it's what happens if you manually load the ammo into the weapon). [[User:Spike\|Spike]] 17:03, 1 November 2010 (UTC)		*Additional multi-level mission bugs. See [[Talk:Known Bugs (TFTD)#Multi-part map ammo loss]]. Is XcomUtil attempting to teleport uncarried items back to base at the end of each level by default? If so, maybe this should be an explicit option in XCUSetup. Also, this routine may need to be fixed to detect items which are carried or loaded into weapons, but are not marked as owned/carried by a Soldier/Aquanaut. Typically this means ammo that is pre-loaded into weapons in the equip phase. This can be fixed either by doing a check to see if the item is loaded into a weapon, or by doing a "full fix" and marking the ammo item as carried by the Soldier/Aquanaut (presumably this doesn't break anything since I think it's what happens if you manually load the ammo into the weapon). [[User:Spike\|Spike]] 17:03, 1 November 2010 (UTC)

			* (Build 442) Prompts for "Pistol" not "Dart Gun" mod in TFTD. Also "Psionics" not "M.C.". [[User:Spike\|Spike]] 21:53, 1 November 2010 (UTC)

			* (Build 442) Steam instructions are confusing - should I run XCUSetup.bat first, then run SteamSetup.bat, then run Steam? Probably not. I think I should run SteamSetup.bat, then Steam, which will run XCUSetup.bat. But it's not very clear. Although the instructions are pretty explicit, why doesn't XCUSetup.bat terminate when it detects Steam? That's what confused me I think. I didn't expect to have to hit Ctrl-C at that point. Also, need to state the path to SteamSetup.bat (.\XCOMUTIL\). [[User:Spike\|Spike]] 21:53, 1 November 2010 (UTC)

	==Fixed Bugs==		==Fixed Bugs==

Spike: /* Open Bugs */ multi part mission ammo bug

2010-11-01T17:03:13Z

Open Bugs: multi part mission ammo bug

← Older revision		Revision as of 17:03, 1 November 2010
Line 171:		Line 171:
	*Research Help from Captured Aliens awards research help without checking first if you have Alien Containment at the base of origin. Resulting in dead aliens helping you with your enquiries! Possibly only applies to AutoCombat? [[User:Spike\|Spike]] 21:05, 14 March 2010 (EDT)		*Research Help from Captured Aliens awards research help without checking first if you have Alien Containment at the base of origin. Resulting in dead aliens helping you with your enquiries! Possibly only applies to AutoCombat? [[User:Spike\|Spike]] 21:05, 14 March 2010 (EDT)
	:: Ideally it would not only check for containment but also have a research item for it and check on how many scientist days had been reduced since the last combat and use that as a value for how much you get form the aliens still in containment. But that could just be a pipe dream. Checking for containment for now is a good idea. --[[User:BladeFireLight\|BladeFireLight]] 15:35, 16 March 2010 (EDT)		:: Ideally it would not only check for containment but also have a research item for it and check on how many scientist days had been reduced since the last combat and use that as a value for how much you get form the aliens still in containment. But that could just be a pipe dream. Checking for containment for now is a good idea. --[[User:BladeFireLight\|BladeFireLight]] 15:35, 16 March 2010 (EDT)

			*Additional multi-level mission bugs. See [[Talk:Known Bugs (TFTD)#Multi-part map ammo loss]]. Is XcomUtil attempting to teleport uncarried items back to base at the end of each level by default? If so, maybe this should be an explicit option in XCUSetup. Also, this routine may need to be fixed to detect items which are carried or loaded into weapons, but are not marked as owned/carried by a Soldier/Aquanaut. Typically this means ammo that is pre-loaded into weapons in the equip phase. This can be fixed either by doing a check to see if the item is loaded into a weapon, or by doing a "full fix" and marking the ammo item as carried by the Soldier/Aquanaut (presumably this doesn't break anything since I think it's what happens if you manually load the ammo into the weapon). [[User:Spike\|Spike]] 17:03, 1 November 2010 (UTC)

	==Fixed Bugs==		==Fixed Bugs==