Difference between revisions of "TERRAIN"

Revision as of 07:54, 27 June 2010

This folder contains the information used for tiles in the battlescape view, both statistical and graphical.

These are divided up into "sets" made of three files: An MCD file, which defines the tiles for that set, and PCK file accompanied by a TAB file, which together define the image data that represents said tiles on-screen.

Each "set" stored here will have a corresponding set in the both the MAPS folder and the ROUTES folder.

Difference between revisions of "TERRAIN"

Revision as of 07:54, 27 June 2010

Contents

See Also

Navigation menu

Search

@@ Line 1: / Line 1: @@
-This folder contains the information used for tiles in the battlescape view, both statistical and graphical.<br>
+This folder contains the information used for tiles in the battlescape view, both statistical and graphical.
-<br>
-Each of the three files used for each tileset contains a variable amount of records. PCK files and their respective TAB files should always contain an equal amount of records.<br>
-=MCD=
-==General Information==
-*MCD stands for Map Control Data.
-*MCD files have a variable amount of records, each of 62 bytes.
-*Each record defines one of four possible terrain items (see [53]):
-**ground tile,
-**north wall,
-**west wall, or
-**object
-*For example, DESERT.MCD defines a number of desert terrain items such as sand (ground tiles), sand dunes, rocks, and cacti.
-*The PCK and TAB files work hand-in-hand with MCD records to define what each terrain item looks like.
-*These MCD terrain items are subsequently combined to make "3D" maplets in the MAPS\DESERT''nn''.MAP 10x10 or 20x20 [[module|tilesets]].
-*The MAP tilesets are then selected from, to make a "random" desert map when a new battlescape is created.
-*Sometimes more than one collection is used for a given map type; farms are made from the CULTIVAT (fields) and BARN (farmhouse) sets.
-*More complex terrain types, especially UFOs and bases, tend to have many more MCD records (terrain items) and/or more than one MCD set. The maximum total cannot excede 256 records.
-*Most MCD files are accompanied by respective [[Image_Formats#PCK|PCK & TAB]] files, and vice versa.
-==Structure==
+These are divided up into "sets" made of three files: An [[MCD]] file, which defines the tiles for that set, and [[Image_Formats#PCK|PCK file accompanied by a TAB file]], which together define the image data that represents said tiles on-screen.
-'''0-7 / 00-07:''' Animation of the tile.
-The eight bytes refer to images on the PCK files which are used in a sequence (from the first byte to the last) to animate tiles. This animation is used by several tiles on both games, such as doors (see [46]), bubbles on TFTD, blinking lifts, etc. If all eight frames are the same, it's a static tile.
+Each "set" stored here will have a corresponding set in the both the [[MAPS]] folder and the [[ROUTES]] folder.
-'''8-19 / 08-13:''' Line Of Fire Template (LOFT) for the tile. 12 values, each references into [[LOFTEMPS.DAT]] file.
+==Contents==
+''Directory listings for UFO/TFTD to go here; [[MCD]] page has a fairly good outline for now. To memory, TFTD doesn't actually use all the files it has...''
-Each LOFT record is a 16x16 grid; these are stacked one over the other, with mcd[8] being the bottom. Used to create a 3D map (16x16x12) of the tile, for LOS. For more info, see [[LOFTEMPS.DAT]].
+==See Also==
+* [[Game Files]]
-'''20-21 / 14-15:''' Reference into [[SCANG.DAT]] file. Two-byte integer ([20] + [21] * 256 + 35 = offset). 4x4 bmp images for the top-down map; see [[SCANG.DAT]].
+[[Category:Terrain]]
-'''22-23 / 16-17:''' Two-byte integer. Unknown. Always 4.
-'''24-25 / 18-19:''' Two-byte integer. Unknown. Breakdown of values listed below:
-<table {{StdCenterTable}} class="sortable">
-<tr {{StdDescTable_Heading}}><th width="60">Low</th><th width="70">High</th><th width="80">Value</th><th align="left">File(s)</th></tr>
-<tr><td>193</td><td>79</td><td>20417</td><td align="left">U_BITS</td></tr>
-<tr><td>45</td><td>88</td><td>22573</td><td align="left">MARS, BRAIN</td></tr>
-<tr><td>183</td><td>88</td><td>22711</td><td align="left">AVENGER, POLAR, ROADS, U_EXT02, U_OPER2, URBAN, DESERT, fires, FRNITURE, interc, LIGHTNIN, MOUNT, PLANE</td></tr>
-<tr><td>185</td><td>88</td><td>22713</td><td align="left">UFO1, URBITS, JUNGLE, BLANKS</td></tr>
-<tr><td>109</td><td>90</td><td>23149</td><td align="left">FOREST, JUNGLE, CULTIVAT, BARN</td></tr>
-<tr><td>153</td><td>106</td><td>27289</td><td align="left">U_DISEC2</td></tr>
-<tr><td>154</td><td>106</td><td>27290</td><td align="left">U_BASE, U-PODS, U_WALL02, XBASE1, XBASE2</td></tr></table>
-'''26-27 / 1A-1B:''' Two-byte integer. Unknown. Always 4.
-'''28-29 / 1C-1D:''' Two-byte integer. Unknown. Breakdown of values listed below:
-<table {{StdCenterTable}} class="sortable">
-<tr {{StdDescTable_Heading}}><th width="60">Low</th><th width="70">High</th><th width="80">Value</th><th align="left">File(s)</th></tr>
-<tr><td>195</td><td>79</td><td>20419</td><td align="left">U_BITS</td></tr>
-<tr><td>47</td><td>88</td><td>22575</td><td align="left">BRAIN</td></tr>
-<tr><td>50</td><td>88</td><td>22578</td><td align="left">MARS</td></tr>
-<tr><td>186</td><td>88</td><td>22714</td><td align="left">U_OPER2, UFO1, BLANKS</td></tr>
-<tr><td>187</td><td>88</td><td>22715</td><td align="left">ROADS, FRNITURE</td></tr>
-<tr><td>189</td><td>88</td><td>22717</td><td align="left">U_EXT02, DESERT, URBITS</td></tr>
-<tr><td>190</td><td>88</td><td>22718</td><td align="left">fires, LIGHTNIN, MOUNT</td></tr>
-<tr><td>191</td><td>88</td><td>22719</td><td align="left">AVENGER</td></tr>
-<tr><td>192</td><td>88</td><td>22720</td><td align="left">interc, PLANE</td></tr>
-<tr><td>196</td><td>88</td><td>22724</td><td align="left">JUNGLE</td></tr>
-<tr><td>198</td><td>88</td><td>22726</td><td align="left">URBAN</td></tr>
-<tr><td>199</td><td>88</td><td>22727</td><td align="left">POLAR</td></tr>
-<tr><td>113</td><td>90</td><td>23153</td><td align="left">BARN</td></tr>
-<tr><td>114</td><td>90</td><td>23154</td><td align="left">CULTIVAT</td></tr>
-<tr><td>117</td><td>90</td><td>23157</td><td align="left">FOREST</td></tr>
-<tr><td>156</td><td>106</td><td>27292</td><td align="left">U_DISEC2</td></tr>
-<tr><td>158</td><td>106</td><td>27294</td><td align="left">U_PODS</td></tr>
-<tr><td>163</td><td>106</td><td>27299</td><td align="left">U_WALL02, XBASE2</td></tr>
-<tr><td>164</td><td>106</td><td>27300</td><td align="left">U_BASE</td></tr>
-<tr><td>168</td><td>106</td><td>27304</td><td align="left">XBASE1</td></tr></table>
-'''30 / 1E:''' Boolean: Is sliding door? See [46]
-'''31 / 1F:''' Boolean: Can see through?
-= False = Can't see through tile <sup><b>*</b></sup>
-= True = Can see through tile <sup><b>*</b></sup>
-<small><b>* Note:</b> Daishiva's MapView program lists this incorrectly!</small>
-'''32 / 20:''' Boolean: Can't be stood on? For ground tiles: non-flying units fall through. ''Only two ground tiles have this set: BLANKS MCD id 0 and UFO1 MCD id 0''
-'''33 / 21:''' Boolean: Is Wall? Used for Objects intended to act as Walls; used to make UFO, Skyranger, and Avenger outer "walls" that aren't otherwise possible as "real" North or West walls. Used for a few other things, too. Called "BigWall" in MapView.
-'''34 / 22:''' Boolean: Is Grav lift? Up/Down of Lifts is determined by whether there is another one above or below in the .MAP.
-'''35 / 23:''' Boolean: Is hinged door? See [46]
-'''36 / 24:''' Boolean: Blocks fire?
-'''37 / 25:''' Boolean: Blocks smoke?
-'''38 / 26:''' Unknown - Always 3.
-'''39 / 27:''' Time units used to walk across the tile. (255 means unpassable)
-'''40 / 28:''' Time units used to slide across the tile. (255 means unpassable)
-'''41 / 29:''' Time units used to fly across the tile. (255 means unpassable)
-For [39] to [41], values range from 0 to 8, or are 255. There are only a few places where they are not all the same ([39]=[40]=[41]):
- <u>Walk</u> <u>Slide</u> <u>Fly</u> <u>File</u>    <u>Description</u>
-   0    2   Avenger Middle ramp object
-255   4   Arctic  Water pools in ice (18 ground MCDs)
-   2    0   U_Base  Death ''objects'' for large round containers in alien bases (four quadrants)...
-                        thus, their remnants don't ''add'' TUs for fliers
-   1    0   U_Base  Little green plant objects found on black "base garden" flooring
-   2    0   Urbits  Two death objects (splinters on ground) for city's tall green picket fence
-                        (one is a North-wall fence, the other is a West-wall fence)
-Which of the three movement types a given unit uses is determined by [[UNITREF.DAT|UnitRef[11]]]. Note that by default, ALL units are "walkers".
-'''42 / 2A:''' Armor of tile.
-*Tile must take this amount of damage to be destroyed, at which point it changes to mcd[44].
-*Terrain items do not "remember" damage (like units); terrain is either destroyed (if damage >= armor) or not.
-*Some things are set to 255 to mean "indestructible" but actually, anything >100 is indestructible in a non-hacked game, and anything >127 (for explosives, 255/2) or >191 (firearms, 255x.75) cannot be destroyed, even in a hacked game (see [[Damage]] re: Damage to terrain).
-*With explosions, all four terrain items in the tile are hit by the same strength, but firearm shots target only one of them.
-*For a loopy exception to explosions being equally applied (due to erroneous data), see [[Explosions#Mile-High Madness|Mountain Madness]].
-*''[[user:NKF|NKF]]:'' I suppose you could make a gate out of this by creating two tiles, each easily destroyed, which change to the other when hit. One could be walked across, the other could not.
-'''43 / 2B:''' [[Explosions#HE Block|HE Blockage]]
-'''44 / 2C:''' Tile becomes a tile of this type (i.e., this other MCD record in the same MCD file) when destroyed. Also known as the '''death tile'''. Also see [53].
-'''Note:''' If [44]=0, it means there is no death tile per se; it reverts to a "raw earth" (BLANKS[01]) tile if on ground, or nothing if in air. (It does not revert to the MCD id 0 record in the current collection.)
-'''45 / 2D:''' The higher this is, the less likely the tile will be set on fire.
-'''46 / 2E:''' If the tile is a door ([30] or [35]), the tile will become this tile number when opened. Animation [0] (see [0] to [7]) is shown until someone walks through the door, in which case it cycles through its animation stopping and holding Animation [7]. Then it will return to a closed door next turn.
-'''47 / 2F:''' Unknown - Always 0. [[TERRAIN#MCD Editor|MCDEdit]] calls this "Keycode".
-'''48 / 30:''' Signed value; add this to the graphical Y offset of units or objects on this tile. A.k.a. terrain level.
-'''49 / 31:''' Subtract this value from the graphical Y offset of the tile image (used for hills).
-'''50 / 32:''' Unknown - Always 0.
-'''51 / 33:''' From 0 to 10, amount of light blocked by tile.
-Blocks no light.
- ''... up to ...''
-Blocks all light.
-'''52 / 34:''' Footstep sound effect. Most likely an index to the .CAT file RAW wave ''-[http://www.strategycore.co.uk/forums/Map-Control-Data-MCD-long-Post-t1468.html BladeFireLight]
-Not used in XCOM (makes a metal sound if hacked); is used on TFTD for some objects ''-[[User:Hobbes|Hobbes]]''
-Metal
-Normal (Grass, Wood, Dirt)
-Three mountain ground tiles, and some city apt. furniture objects that can't be walked on?
-   (six furniture objects might've been - but they're death tiles that nothing points to)
-   Uses same sound as 6 in DOS version.
-Pool of water (Not used in XCOM)
-Sand (Desert)
-Martian ground (DOS version), snow (CE version)
-Snow (only DOS version, Not used in XCOM, Arctic terrain actually uses 2)
-'''53 / 35:''' Tile type:
-Floor
-West Wall
-North Wall
-Object
-In the map, there are four bytes per tile: One each for the floor, west wall, north wall and object. If one of those changes (eg Is destroyed, or in the case of a door, opened), it is removed from the map and a new object is placed instead. This byte is used to work out which of the four map bytes should recieve the new object.
-For example, in the mountains, if you destroy the ground tile you get an object (tree stump). The new tile gets written into the fourth byte of the map record, even though the original tile that was destroyed belonged in the first byte.
-As for the potential for change in tile type when becoming death tile ([44]): There are 22 instances of [[Explosions#Mile-High Madness|Mountain Madness]] (ground to object), 1 instance of North Wall becoming an object (XCOM1 northwall door becomes rubble), one MCD record with tile type of '''10''' (Barn 7 which looks like a North Wall and becomes northwall when killed; obviously a typo'd Tile Type), and 31 total instances on 18 different tilesets where objects become ground upon dying (probably to "scorched earth", but this was not checked).
-'''54 / 36:''' Explosive type; [55] must be >0:
-HE
-Smoke
-''Notes:''
-#To see explosive objects in XCOM, see [[Explosions#Explosive Map Objects]].
-#Type 0 (HE) explosions follow the usual rules for [[explosions]] (average damage to units decreases by 10 per tile outward, etc.).
-#Hackers: Type 0 (HE) terrain items with little or no armor ([42]=0) are obliterated before exploding (i.e., they won't explode, no matter how high [55] is). Probably also depends on, if it was a very big blast relative to the armor.
-#Chain reactions are exceedingly difficult to set up (per Hobbes). Most of the time when you see e.g. the four sections of the Navigator's table explode, it's because you used explosives that actually set off each one individually. It has to do with a balance of, among other things, not obliterating the object (see previous point).
-#Type 1 (Smoke) explosives are strange, and mainly only affect aliens - and very haphazardly at that. XCOM units are only very rarely affected; I could only get it to work if they were 1) unarmored, 2) on a diagonal, and 3) no other objects are "in the way" between the blast moving "over and up" or "up and over" to the diagonal (blast propagation never moves directly diagonally per se; see [[Explosions#Playing With Fire]]). ''-MTR''
-#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)''
-#There are no "naturally occuring" HE explosives tiles in UFO. All explosive objects are MCD[54]=1.
-#TFTD uses both values for [54], 0 (more common, like the barrels on Port) and 1 (the Synomium device on Grunge/Artifact Site).
-'''55 / 37:''' Strength of explosion when tile is destroyed.
-'''56 / 38:''' Smoke blockage. This is set to 0 for all UFO tiles!
-'''''Perhaps [36] is used only? A varying [56] might have been where the 2 un-used smoke sprites would have come in. --[[User:Danial|Danial]]'''''
-'''57 / 39:''' The amount of turns this tile will burn for.
-'''58 / 3A:''' Brightness of tile. Amount of light produced.
-MCDs produce light: 7 alien base objects (several pulsing fuel pods and several 4-part round "museum containers"), 2 XCOM base ground tiles, and 2 city objects (street lamp and large standing room lamp). See [[Night_Missions#Artificial_Lighting|Night Missions]] for pictures. Oddly, values range from 1 for the street lamp to 16 for the alien base museum containers, so lower values must be brighter. The [[Night Missions|distances]] of projected light have yet to be determined, but note that flares and personal lighting ignore vertical distance... at night, a soldier can see aliens on the ground exactly 9 tiles away, regardless of whether the soldier is at ground level or 4 levels high.
-''In practise, it seems if this is not zero then the tile will be fully illuminated regardless of the value. - [[User:Bomb Bloke|Bomb Bloke]] 06:48, 20 June 2008 (PDT)''
-'''59 / 3B:''' Special properties of tile. Determines what is salvaged at end of mission:
-''No Special Properties''
-Starting Point ''(place to Abort mission)''
-[[UFO Power Source]]
-[[UFO Navigation]]
-[[UFO Construction]]
-[[Alien Food]]
-[[Alien Reproduction]]
-[[Alien Entertainment]]
-[[Alien Surgery]]
-[[Examination Room]]
-[[Alien Alloys]]
-[[Alien Habitat]]
-Dead Tile
-End Point ''(from surface of Mars to base)''
-Alien Brain  ''(final mission victory condition)''
-'''60 / 3C:''' Set to 1 for most (but not all) non-death-tile XCOM base objects (TileType=3). All other MCD records set to 0. [[TERRAIN#MCD Editor|MCDEdit]] calls this "Victory Points" - so presumably you lose VPs based on how much of your base is destroyed?
-'''61 / 3D:''' 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?
-==List of MCD Files==
-Here are the MCD files in Enemy Unknown and Terror From The Deep along with a list of the number of records in each one:
-<table cellpadding="10">
-<tr><td valign="top">
-<table {{StdCenterTable}} class="sortable">
-<caption><b>X-COM MCD Files</b></caption>
-<tr {{StdDescTable_Heading}}><th width="100" align="left">File</th><th>Terrain</th><th>Records</th></tr>
-<tr><td align="left">avenger</td><td>Avenger</td><td>59</td></tr>
-<tr><td align="left">barn</td><td>Farm</td><td>29</td></tr>
-<tr><td align="left">blanks</td><td>All</td><td>2</td></tr>
-<tr><td align="left">brain</td><td>Alien Base</td><td>4</td></tr>
-<tr><td align="left">cultitav</td><td>Farm</td><td>37</td></tr>
-<tr><td align="left">desert</td><td>Desert</td><td>66</td></tr>
-<tr><td align="left">forest</td><td>Forest</td><td>83</td></tr>
-<tr><td align="left">frniture</td><td>City</td><td>26</td></tr>
-<tr><td align="left">jungle</td><td>Jungle</td><td>82</td></tr>
-<tr><td align="left">lightnin</td><td>Lightning</td><td>42</td></tr>
-<tr><td align="left">mars</td><td>Cydonia</td><td>36</td></tr>
-<tr><td align="left">mount</td><td>Mountain</td><td>78</td></tr>
-<tr><td align="left">plane</td><td>Skyranger</td><td>65</td></tr>
-<tr><td align="left">polar</td><td>Polar</td><td>81</td></tr>
-<tr><td align="left">roads</td><td>City</td><td>23</td></tr>
-<tr><td align="left">ufo1</td><td>Small Scout</td><td>20</td></tr>
-<tr><td align="left">urban</td><td>City</td><td>112</td></tr>
-<tr><td align="left">urbits</td><td>City</td><td>25</td></tr>
-<tr><td align="left">u_base</td><td>Alien Base</td><td>67</td></tr>
-<tr><td align="left">u_bits</td><td>UFOs</td><td>8</td></tr>
-<tr><td align="left">u_disec2</td><td>UFOs</td><td>17</td></tr>
-<tr><td align="left">u_ext02</td><td>UFOs</td><td>34</td></tr>
-<tr><td align="left">u_oper2</td><td>UFOs</td><td>15</td></tr>
-<tr><td align="left">u_pods</td><td>UFO/Alien Base</td><td>11</td></tr>
-<tr><td align="left">u_wall02</td><td>UFO/Alien Base/Cydonia</td><td>47</td></tr>
-<tr><td align="left">xbase1</td><td>X-COM Base</td><td>97</td></tr>
-<tr><td align="left">xbase2</td><td>X-COM Base</td><td>62</td></tr></table>
-</td>
-<td>
-<table {{StdCenterTable}} class="sortable">
-<caption><b>TFTD MCD Files</b></caption>
-<tr {{StdDescTable_Heading}}><th width="100" align="left">File</th><th>Terrain</th><th>Records</th></tr>
-<tr><td align="left">asunk</td><td>Sunken Galleon</td><td>50</td></tr>
-<tr><td align="left">atlantis</td><td>Atlantis</td><td>77</td></tr>
-<tr><td align="left">barracud</td><td>Barracuda</td><td>46</td></tr>
-<tr><td align="left">blanks</td><td>All</td><td>2</td></tr>
-<tr><td align="left">cargo1</td><td>Cargo Ship</td><td>103</td></tr>
-<tr><td align="left">cargo2</td><td>Cargo Ship</td><td>13</td></tr>
-<tr><td align="left">cargo3</td><td>Cargo Ship</td><td>6</td></tr>
-<tr><td align="left">coral</td><td>Coral</td><td>28</td></tr>
-<tr><td align="left">crypt1</td><td>Crypt</td><td>45</td></tr>
-<tr><td align="left">crypt2</td><td>Crypt</td><td>49</td></tr>
-<tr><td align="left">crypt3</td><td>Crypt</td><td>12</td></tr>
-<tr><td align="left">crypt4</td><td>Crypt</td><td>7</td></tr>
-<tr><td align="left">debris</td><td>Seabed</td><td>50</td></tr>
-<tr><td align="left">deckc</td><td>Liner Ship (Top)</td><td>18</td></tr>
-<tr><td align="left">entry</td><td>Entry</td><td>12</td></tr>
-<tr><td align="left">grunge1</td><td>Artifact Site</td><td>38</td></tr>
-<tr><td align="left">grunge2</td><td>Artifact Site</td><td>8</td></tr>
-<tr><td align="left">grunge3</td><td>Artifact Site</td><td>10</td></tr>
-<tr><td align="left">grunge4</td><td>Artifact Site</td><td>37</td></tr>
-<tr><td align="left">hammer</td><td>Hammerhead</td><td>44</td></tr>
-<tr><td align="left">island1</td><td>Island</td><td>50</td></tr>
-<tr><td align="left">island2</td><td>Island</td><td>50</td></tr>
-<tr><td align="left">island3</td><td>Island</td><td>35</td></tr>
-<tr><td align="left">leviath</td><td>Leviathan</td><td>47</td></tr>
-<tr><td align="left">linera</td><td>Liner Ship</td><td>99</td></tr>
-<tr><td align="left">linerb</td><td>Liner Ship</td><td>24</td></tr>
-<tr><td align="left">linerc</td><td>Liner Ship</td><td>40</td></tr>
-<tr><td align="left">linerd</td><td>Liner Ship</td><td>23</td></tr>
-<tr><td align="left">manta</td><td>Manta</td><td>44</td></tr>
-<tr><td align="left">msunk1</td><td>Sunken Ship</td><td>50</td></tr>
-<tr><td align="left">msunk2</td><td>Sunken Ship</td><td>29</td></tr>
-<tr><td align="left">mu</td><td>Mu</td><td>80</td></tr>
-<tr><td align="left">organic1</td><td>Alien Base/Level/Entry</td><td>96</td></tr>
-<tr><td align="left">organic2</td><td>Alien Base/Level</td><td>10</td></tr>
-<tr><td align="left">organic3</td><td>Alien Base/Level</td><td>4</td></tr>
-<tr><td align="left">pipes</td><td>Pipes</td><td>55</td></tr>
-<tr><td align="left">planes</td><td>Sunken Plane</td><td>79</td></tr>
-<tr><td align="left">port01</td><td>Port</td><td>95</td></tr>
-<tr><td align="left">port02</td><td>Port</td><td>78</td></tr>
-<tr><td align="left">psynom</td><td>Alien Base/Level</td><td>2</td></tr>
-<tr><td align="left">pyramid</td><td>Artifact</td><td>24</td></tr>
-<tr><td align="left">rocks</td><td>Artifact/Seabed/Galleon</td><td>15</td></tr>
-<tr><td align="left">sand</td><td>several</td><td>20</td></tr>
-<tr><td align="left">sea</td><td>several</td><td>18</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">uext2</td><td>USO/Entry</td><td>9</td></tr>
-<tr><td align="left">uext3</td><td>USO/Entry</td><td>25</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">uint2</td><td>USO</td><td>11</td></tr>
-<tr><td align="left">uint3</td><td>USO</td><td>14</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">xbases1</td><td>X-COM Base</td><td>87</td></tr>
-<tr><td align="left">xbases2</td><td>X-COM Base</td><td>42</td></tr>
-<tr><td align="left">xbases3</td><td>X-COM Base</td><td>37</td></tr>
-<tr><td align="left">xbases4</td><td>X-COM Base</td><td>43</td></tr>
-<tr><td align="left">xbases5</td><td>X-COM Base</td><td>42</td></tr>
-<tr><td align="left">xbits</td><td>Cargo Ship</td><td>39</td></tr></table>
-</td></tr></table>
-==Additional Information==
-===MikeTheRed's MCD Database===
-An Acccess 2000 copy of all MCD data is [[Media:XcomMCD.zip|here]]. It's from X-COM DOS 1.4, but AFAIK, all X-COM versions use the same data (even down to the buggy [[Explosions#Mile-High_Madness|Mile-High Madness]] MCD record). You will need to use this wiki page to understand it; I did not name the fields. They're just called by their offset address (see above). This Access database can be readily exported to Excel if you want. Or contact me. There are also a few files giving overall stats; the "Exclude" field for tblFileTypes only means, I excluded them for most counts I've made. There are also a few queries that might or might not be helpful.
-===BladeFireLight's MCD Info===
-Another in-depth look at MCD (and more) can be found on [http://www.strategycore.co.uk/forums/lofiversion/index.php?t1468.html this] message by BladeFireLight. His post also contains a [http://www.HexWorkshop.com HexWorkshop] template for viewing MCD files in a logical manner.
-===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!
-===MapView===
-DaiShiva has an excellent utility called [http://www.daishiva.com/phpBB2/generic.php?page=progLinks.shtml MapView] for viewing or editing maps. However, it does not allow editing of MCD terrain items per se, AFAIK; just moving/placement of them. Caution: You must install the extensive Microsoft .NET platform to use MapView; see DaiShiva's site.
-===BombBloke's Hacked Desert Terrain===
-[[User:Bomb Bloke|Bomb Bloke]] has a numerical (ground) tileset which makes weapon damage blast testing easy as pie. It also has a little applet that lets you edit MCD variables Armor [42], HE Block [43], and Explosion Strength [55] (but not type, [54]), and it includes all four types of terrain item. Find his hacked terrain
-[http://www.strategycore.co.uk/forums/index.php?showtopic=746&st=195&# here] or bundled with a savegame [http://www.xcomufo.com/forums/index.php?showtopic=8701&st=114&# here]. To see a screencap of the tiles in action, see [http://www.xcomufo.com/forums/index.php?showtopic=8701&st=112&# this] message.
-[[Category: Terrain]]
 [[Category:Game Files]]