MCD - Revision history

Warboy1982: removed hypothetical context for unused variables

2025-05-25T23:50:22Z

removed hypothetical context for unused variables

← Older revision		Revision as of 23:50, 25 May 2025
Line 176:		Line 176:
	!<span id="0x33"></span>0x33		!<span id="0x33"></span>0x33
	\|?????? OpenXCom and MCDEditor call this 'light block'. Note that the actual game seems to ignore this value.		\|?????? OpenXCom and MCDEditor call this 'light block'. Note that the actual game seems to ignore this value.
	~~0 Blocks no light?.~~
	~~''... up to ...''~~
	~~10 Blocks all light?.~~
	~~Is apparently percentage based: 1=10%, 10=100%.~~
	\|- valign="top"		\|- valign="top"
	!<span id="52"></span>52		!<span id="52"></span>52
Line 233:		Line 229:
	!<span id="0x38"></span>0x38		!<span id="0x38"></span>0x38
	\|?????? This is set to 0 for all UFO tiles!		\|?????? This is set to 0 for all UFO tiles!
	Called "gasblock" by OpenXCom and SmokeBlock by MCDEditor. ~~Supposedly it would block~~ the ~~gas/smoke from spreading. Needs testing~~.		Called "gasblock" by OpenXCom and SmokeBlock by MCDEditor. Note that the actual game seems to ignore this value.
	\|- valign="top"		\|- valign="top"
	!<span id="57"></span>57		!<span id="57"></span>57

Hobbes at 13:31, 25 May 2025

2025-05-25T13:31:32Z

← Older revision		Revision as of 13:31, 25 May 2025
Line 175:		Line 175:
	!<span id="51"></span>51		!<span id="51"></span>51
	!<span id="0x33"></span>0x33		!<span id="0x33"></span>0x33
	\|OpenXCom and MCDEditor call this 'light block'. Note that the actual game seems to ignore this value.		\|?????? OpenXCom and MCDEditor call this 'light block'. Note that the actual game seems to ignore this value.
	0 Blocks no light?.		0 Blocks no light?.
	''... up to ...''		''... up to ...''

Hobbes: clarifying the origin of some names used to describe the MCD fields

2025-05-25T13:28:30Z

clarifying the origin of some names used to describe the MCD fields

← Older revision		Revision as of 13:28, 25 May 2025
Line 175:		Line 175:
	!<span id="51"></span>51		!<span id="51"></span>51
	!<span id="0x33"></span>0x33		!<span id="0x33"></span>0x33
	\|~~Lightblock~~. Note that the actual game seems to ignore this value.		\|OpenXCom and MCDEditor call this 'light block'. Note that the actual game seems to ignore this value.
	0 Blocks no light.		0 Blocks no light?.
	''... up to ...''		''... up to ...''
	10 Blocks all light.		10 Blocks all light?.
	Is apparently percentage based: 1=10%, 10=100%.		Is apparently percentage based: 1=10%, 10=100%.
	\|- valign="top"		\|- valign="top"
Line 232:		Line 232:
	!<span id="56"></span>56		!<span id="56"></span>56
	!<span id="0x38"></span>0x38		!<span id="0x38"></span>0x38
	\|~~Smoke blockage.~~ This is set to 0 for all UFO tiles!		\|?????? This is set to 0 for all UFO tiles!
	~~Technically called~~ "gasblock" by ~~the game~~. Supposedly it would block the gas ~~type~~ from spreading~~. Not sure if this is intended to be just smoke, gas or a combination of the two~~. Needs testing.		Called "gasblock" by OpenXCom and SmokeBlock by MCDEditor. Supposedly it would block the gas/smoke from spreading. Needs testing.
	\|- valign="top"		\|- valign="top"
	!<span id="57"></span>57		!<span id="57"></span>57

Magic9mushroom: Continuing to remove USO instances I missed when I did this the first time.

2016-01-10T06:37:55Z

Continuing to remove USO instances I missed when I did this the first time.

← Older revision		Revision as of 06:37, 10 January 2016
Line 269:		Line 269:

	Notes:		Notes:
	* The images in the TFTD in-game UFOpedia do NOT match the tile-types you'll recover from the battlescape. For example, the [[Dreadnought]] has tiles which match the UFOpedia entries for the [[Magnetic Navigation]] systems - but they're really [[Alien Sub Construction]] units, or so your ~~USO~~ recovery team will tell you! Daishiva's [[MapView]] presents tiles according to the UFOpedia, hence the additional column.		* The images in the TFTD in-game UFOpedia do NOT match the tile-types you'll recover from the battlescape. For example, the [[Dreadnought]] has tiles which match the UFOpedia entries for the [[Magnetic Navigation]] systems - but they're really [[Alien Sub Construction]] units, or so your Alien Sub recovery team will tell you! Daishiva's [[MapView]] presents tiles according to the UFOpedia, hence the additional column.
	* The "entry points" are where your troopers spawn at the start of the map. If you wish to safely abort, your solders must return to those tiles first.		* The "entry points" are where your troopers spawn at the start of the map. If you wish to safely abort, your solders must return to those tiles first.
	* The "exit points" are where soldiers must be if you wish to proceed to the next stage of a [[Two Part Missions\|two-part mission]] without killing all aliens (by aborting instead).		* The "exit points" are where soldiers must be if you wish to proceed to the next stage of a [[Two Part Missions\|two-part mission]] without killing all aliens (by aborting instead).
Line 373:		Line 373:
	<tr><td align="left">triton</td><td>Triton</td><td>46</td></tr>		<tr><td align="left">triton</td><td>Triton</td><td>46</td></tr>
	<tr><td align="left">uext1</td><td>?</td><td>4</td></tr>		<tr><td align="left">uext1</td><td>?</td><td>4</td></tr>
	<tr><td align="left">uext2</td><td>~~USO~~/Entry</td><td>9</td></tr>		<tr><td align="left">uext2</td><td>Alien Sub/Entry</td><td>9</td></tr>
	<tr><td align="left">uext3</td><td>~~USO~~/Entry</td><td>25</td></tr>		<tr><td align="left">uext3</td><td>Alien Sub/Entry</td><td>25</td></tr>
	<tr><td align="left">ufobits</td><td>several</td><td>5</td></tr>		<tr><td align="left">ufobits</td><td>several</td><td>5</td></tr>
	<tr><td align="left">uint1</td><td>~~USO~~</td><td>41</td></tr>		<tr><td align="left">uint1</td><td>Alien Sub</td><td>41</td></tr>
	<tr><td align="left">uint2</td><td>~~USO~~</td><td>11</td></tr>		<tr><td align="left">uint2</td><td>Alien Sub</td><td>11</td></tr>
	<tr><td align="left">uint3</td><td>~~USO~~</td><td>14</td></tr>		<tr><td align="left">uint3</td><td>Alien Sub</td><td>14</td></tr>
	<tr><td align="left">volc</td><td>Volcanic</td><td>80</td></tr>		<tr><td align="left">volc</td><td>Volcanic</td><td>80</td></tr>
	<tr><td align="left">weeds</td><td>Artifact/Coral/Seabed</td><td>10</td></tr>		<tr><td align="left">weeds</td><td>Artifact/Coral/Seabed</td><td>10</td></tr>

Volutar: clarification

2015-06-21T16:07:05Z

clarification

← Older revision		Revision as of 16:07, 21 June 2015
Line 92:		Line 92:
	!<span id="38"></span>38		!<span id="38"></span>38
	!<span id="0x26"></span>0x26		!<span id="0x26"></span>0x26
	\|Always 3. Defined as "printype"; 3=whole, 2=right side, 1=left side. Since this is always 3 the game prints the entire object, while the assumption is that values of 2 or 1 are possibly used for the map designer.		\|Always 3. Defined as "printype"; 3=whole, 2=right side, 1=left side. Since this is always 3 the game prints the entire object, while the assumption is that values of 2 or 1 are possibly used for the map designer. But the actual game totally ignores this value.
	\|- valign="top"		\|- valign="top"
	!<span id="39"></span>39		!<span id="39"></span>39
Line 284:		Line 284:
	!<span id="61"></span>61		!<span id="61"></span>61
	!<span id="0x3D"></span>0x3D		!<span id="0x3D"></span>0x3D
	\|Unused. Almost half (560 of 1317) MCD records have widely varying values here, from 1 to 255 with no apparent pattern or preferred value. The remaining MCD records are 0. Called "VPs" by the game, this was supposed to be a victory point value for recovery/destruction. ~~Doubt it~~'s actually used~~, but needs to be tested~~.		\|Unused. Almost half (560 of 1317) MCD records have widely varying values here, from 1 to 255 with no apparent pattern or preferred value. The remaining MCD records are 0. Called "VPs" by the game, this was supposed to be a victory point value for recovery/destruction. It's not actually used.
	\|-		\|-
	\|}		\|}

Zombie: /* Structure */ New info, one spelling issue.

2015-06-18T04:25:16Z

Structure: New info, one spelling issue.

← Older revision		Revision as of 04:25, 18 June 2015
Line 60:		Line 60:
	!<span id="31"></span>31		!<span id="31"></span>31
	!<span id="0x1F"></span>0x1F		!<span id="0x1F"></span>0x1F
	\|Boolean: Blocks visibility of terrain?		\|Boolean: Blocks visibility of terrain? AKA LOS (Line Of Sight)
	0 = False = Doesn't block visibility.		0 = False = Doesn't block visibility.
	1 = True = Blocks visibility.		1 = True = Blocks visibility.
Line 88:		Line 88:
	!<span id="37"></span>37		!<span id="37"></span>37
	!<span id="0x25"></span>0x25		!<span id="0x25"></span>0x25
	\|Boolean: Tile blocks smoke. Used in smoke propagation routine.		\|Boolean: Tile blocks smoke (or a "gas" type which was never implemented) from spreading. Used in smoke propagation routine.
	\|- valign="top"		\|- valign="top"
	!<span id="38"></span>38		!<span id="38"></span>38
	!<span id="0x26"></span>0x26		!<span id="0x26"></span>0x26
	\|~~Unused~~. ~~Always~~ 3.		\|Always 3. Defined as "printype"; 3=whole, 2=right side, 1=left side. Since this is always 3 the game prints the entire object, while the assumption is that values of 2 or 1 are possibly used for the map designer.
	\|- valign="top"		\|- valign="top"
	!<span id="39"></span>39		!<span id="39"></span>39
Line 147:		Line 147:
	!<span id="45"></span>45		!<span id="45"></span>45
	!<span id="0x2D"></span>0x2D		!<span id="0x2D"></span>0x2D
	\|~~The~~ higher this is, the less likely the tile will be set on fire.		\|Flammability - the higher this is, the less likely the tile will be set on fire.
	\|- valign="top"		\|- valign="top"
	!<span id="46"></span>46		!<span id="46"></span>46
Line 175:		Line 175:
	!<span id="51"></span>51		!<span id="51"></span>51
	!<span id="0x33"></span>0x33		!<span id="0x33"></span>0x33
	\|~~From 0 to 10, amount of light blocked by tile~~. Note that the actual game seems to ignore this value.		\|Lightblock. Note that the actual game seems to ignore this value.
	0 Blocks no light.		0 Blocks no light.
	''... up to ...''		''... up to ...''
	10 Blocks all light.		10 Blocks all light.
			Is apparently percentage based: 1=10%, 10=100%.
	\|- valign="top"		\|- valign="top"
	!<span id="52"></span>52		!<span id="52"></span>52
Line 221:		Line 222:
	#Chain reactions are not possible with Type 1 (Smoke) explosive objects.		#Chain reactions are not possible with Type 1 (Smoke) explosive objects.
	#Also, when dealing with smoke damage, remember that if there is already tons of smoke on the map (filling up the smoke table) such that no new smoke can appear, you might get unexpected results (or no effect). ''[[user:Hobbes\|Hobbes]]:'' One strange thing that can happen when there's already too much smoke on the map and an object with [54]=1 explodes is that the alien dies and in the dying animation there's smoke on that square. ''Just in the dying animation, not after he's down? -MTR'' - ''I can't remember right now if the smoke remains afterward. Next time it happens I will check it [[User:Hobbes\|Hobbes]] 12:00, 18 Nov 2005 (PST)''		#Also, when dealing with smoke damage, remember that if there is already tons of smoke on the map (filling up the smoke table) such that no new smoke can appear, you might get unexpected results (or no effect). ''[[user:Hobbes\|Hobbes]]:'' One strange thing that can happen when there's already too much smoke on the map and an object with [54]=1 explodes is that the alien dies and in the dying animation there's smoke on that square. ''Just in the dying animation, not after he's down? -MTR'' - ''I can't remember right now if the smoke remains afterward. Next time it happens I will check it [[User:Hobbes\|Hobbes]] 12:00, 18 Nov 2005 (PST)''
	#There are no "naturally ~~occuring~~" HE explosives tiles in UFO. All explosive objects are MCD[54]=1.		#There are no "naturally occurring" HE explosives tiles in UFO. All explosive objects are MCD[54]=1.
			#The game show values of 0=not explosive, 1=normal (which I assume is HE), 2=gas (again, unused feature).
	#TFTD uses both values for [54], 0 (more common, like the barrels on Port) and 1 (the Synomium device on Grunge/Artifact Site).		#TFTD uses both values for [54], 0 (more common, like the barrels on Port) and 1 (the Synomium device on Grunge/Artifact Site).
	\|- valign="top"		\|- valign="top"
Line 231:		Line 233:
	!<span id="0x38"></span>0x38		!<span id="0x38"></span>0x38
	\|Smoke blockage. This is set to 0 for all UFO tiles!		\|Smoke blockage. This is set to 0 for all UFO tiles!
			Technically called "gasblock" by the game. Supposedly it would block the gas type from spreading. Not sure if this is intended to be just smoke, gas or a combination of the two. Needs testing.
	~~'''''Perhaps [[#36\|[36]]]~~ is ~~used only? A varying [56] might have been where~~ the ~~2 un-used smoke sprites would have come in~~. ~~--[[User:Danial\|Danial]]'''''~~
	\|- valign="top"		\|- valign="top"
	!<span id="57"></span>57		!<span id="57"></span>57
	!<span id="0x39"></span>0x39		!<span id="0x39"></span>0x39
	\|The amount of turns this tile will burn for.		\|Fuel. The amount of turns this tile will burn for.
	\|- valign="top"		\|- valign="top"
	!<span id="58"></span>58		!<span id="58"></span>58
Line 283:		Line 284:
	!<span id="61"></span>61		!<span id="61"></span>61
	!<span id="0x3D"></span>0x3D		!<span id="0x3D"></span>0x3D
	\|Unused. Almost half (560 of 1317) MCD records have widely varying values here, from 1 to 255 with no apparent pattern or preferred value. The remaining MCD records are 0. ~~Memory garbage~~.		\|Unused. Almost half (560 of 1317) MCD records have widely varying values here, from 1 to 255 with no apparent pattern or preferred value. The remaining MCD records are 0. Called "VPs" by the game, this was supposed to be a victory point value for recovery/destruction. Doubt it's actually used, but needs to be tested.
	\|-		\|-
	\|}		\|}

Magic9mushroom at 10:00, 1 May 2015

2015-05-01T10:00:29Z

← Older revision		Revision as of 10:00, 1 May 2015
Line 277:		Line 277:
	!<span id="60"></span>60		!<span id="60"></span>60
	!<span id="0x3C"></span>0x3C		!<span id="0x3C"></span>0x3C
	\|Set to 1 for [[~~Base_Defense~~#Destruction_Of_Base_Facilities\|some]] X-COM base tiles, 0 otherwise. At the end of the battle, the game tallies up the amount of these existing within each "module" of the base (the results are stored in [[MISSION2.DAT]], offsets 80-151) - if the end result for any given module is 0, [[~~Base_Defense~~#Destruction_Of_Base_Facilities\|it may be destroyed]].		\|Set to 1 for [[Base_Defence#Destruction_Of_Base_Facilities\|some]] X-COM base tiles, 0 otherwise. At the end of the battle, the game tallies up the amount of these existing within each "module" of the base (the results are stored in [[MISSION2.DAT]], offsets 80-151) - if the end result for any given module is 0, [[Base_Defence#Destruction_Of_Base_Facilities\|it may be destroyed]].

	If an alien patrols to a route node which has [[ROUTES.DAT#21\|offset [21]]] flagged as anything other then 0, it will intentionally shoot at any tiles with ''this'' offset likewise flagged. If you're playing a CE version of UFO/TFTD the game will then crash immediately afterwards... either way, best not to let them go up the stairs to where these objects can be found. ;)		If an alien patrols to a route node which has [[ROUTES.DAT#21\|offset [21]]] flagged as anything other then 0, it will intentionally shoot at any tiles with ''this'' offset likewise flagged. If you're playing a CE version of UFO/TFTD the game will then crash immediately afterwards... either way, best not to let them go up the stairs to where these objects can be found. ;)

Volutar: unused values 0x26 & 0x3D

2014-11-14T06:35:31Z

unused values 0x26 & 0x3D

← Older revision		Revision as of 06:35, 14 November 2014
Line 92:		Line 92:
	!<span id="38"></span>38		!<span id="38"></span>38
	!<span id="0x26"></span>0x26		!<span id="0x26"></span>0x26
	\|~~Unknown -~~ Always 3.		\|Unused. Always 3.
	\|- valign="top"		\|- valign="top"
	!<span id="39"></span>39		!<span id="39"></span>39
Line 283:		Line 283:
	!<span id="61"></span>61		!<span id="61"></span>61
	!<span id="0x3D"></span>0x3D		!<span id="0x3D"></span>0x3D
	\|Almost half (560 of 1317) MCD records have widely varying values here, from 1 to 255 with no apparent pattern or preferred value. The remaining MCD records are 0. ~~Some kind of pointer?~~		\|Unused. Almost half (560 of 1317) MCD records have widely varying values here, from 1 to 255 with no apparent pattern or preferred value. The remaining MCD records are 0. Memory garbage.
	\|-		\|-
	\|}		\|}

Volutar: /* MCD Editor */

2014-07-29T03:29:04Z

MCD Editor

← Older revision		Revision as of 03:29, 29 July 2014
Line 398:		Line 398:
	===MCD Editor===		===MCD Editor===
	Koralt's MCDEdit can view or modify MCD files. Find it here: [http://mypage.bluewin.ch/xcom/mcdedit.zip mcdedit.zip]. To see a screencap, scroll to the very bottom of BladeFireLight's MCD posting (above). MCDEdit needs [http://mypage.bluewin.ch/xcom/vbrun200.zip vbrun200] to run!		Koralt's MCDEdit can view or modify MCD files. Find it here: [http://mypage.bluewin.ch/xcom/mcdedit.zip mcdedit.zip]. To see a screencap, scroll to the very bottom of BladeFireLight's MCD posting (above). MCDEdit needs [http://mypage.bluewin.ch/xcom/vbrun200.zip vbrun200] to run!

			There's also [[MCDEdit\|MCDEdit made by volutar]]. It doesn't need of any extra library and works in windows x64.

	===MapView===		===MapView===

Hobbes: /* BombBloke's Hacked Desert Terrain */

2013-07-23T04:46:59Z

BombBloke's Hacked Desert Terrain

← Older revision		Revision as of 04:46, 23 July 2013
Line 407:		Line 407:

	[[Category:Game Files]]		[[Category:Game Files]]
			[[Category:Enemy Unknown/UFO Defense]]
			[[Category:TFTD]]