UFOpaedia - User contributions [en]

Talk:Tasoth

2016-04-01T08:00:36Z

Morgan525: /* Shipping Route missions in April/May? */ Confirm chart is correct.

==Nomenclature==

Like I said over in the Sectoid discussion page, I'm doing a personal project and wondering about the origins of the alien names. Most are self-explanatory, but I can't find anything about a 'Tasoth' that doesn't relate to TFTD. The suffix -oth seems to mean something in H.P. Lovecraft's fictional language ('a native of'), but I can't find anything about 'tas.' Maybe it just means they're the natives of a planet/realm/other called Tas?
[[User:Debesh Unnos|Debesh Unnos]] 21:09, 12 February 2013 (EST)

: I'm probably over-simplifying the answer, but apart from being made up to sound Lovecraft-ey, Tas may just refer to T'Leth. It would certainly be fitting. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 02:13, 4 May 2015 (EDT)

==Plural==

Is there any evidence either way about whether the plural of Tasoth is "Tasoth" or "Tasoths"? If not, what's the plural of Shoggoth in Lovecraft's work? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 21:15, 3 May 2015 (EDT)

: I know Wikipedia's not the be-all and end-all of knowledge, but http://en.wikipedia.org/wiki/Shoggoth does have Shoggoths as a plural.

: For Tasoth though, I am guessing the last line in the live entry seems to suggest ''Tasoth'' is the plural. We would normally add an s when we pluralize the rank. Tasoth Soldiers and Tasoth Squad Leaders for example. The only time you'd stick s on the end is with an apostrophe to indicate possession. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 01:54, 4 May 2015 (EDT)

The last two lines of the live entry are singular (why, I have no clue). "The Tasoth '''is''' a true alien and '''its''' behaviour and carnivorous nature unmatched on the planet. The Tasoth often form'''s''' the spearhead of an alien attack and never seem'''s''' to shrink from the fight even in the face of overwhelming odds." So it doesn't tell us the plural.

Shoggoths (and that is indeed the plural; just checked At the Mountains of Madness) are a servant race of the Old Ones, bred to perform manual labour. They share certain features with Tasoth(s), specifically their aquatic nature and mutable flesh. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 02:14, 4 May 2015 (EDT)

== Shipping Route missions in April/May? ==

This has had a {{Verify}} tag for several years. That they can't appear before April on such missions is an obvious consequence of the fact that Shipping Route missions themselves don't appear until April; however, does anyone know for sure whether the [[Alien Appearance Ratios]] table includes them in the April/May block on Shipping Routes? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 07:37, 1 April 2016 (UTC)
:The charts are correct. Shipping routes only use one entry on the alien selection table, despite the length of the game. Here is the raw data: 0x478D1C: 00 01 01 01 04 04 02 02 03 03 -[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 08:00, 1 April 2016 (UTC)

MISDATA.DAT

2016-03-23T08:40:23Z

Morgan525: /* Structure */

This 170 byte file (172 for TFTD) is only used by tactical saves, and much of it is made up of two-byte signed integers. It comes in three flavours: 

*MISSION.DAT 
Initially created by the GeoScape engine and stored in the [[Saved_Game_Files#Missdat_Files|MISSDAT]] folder. Contains info required for [[Battlescape Map Generation]]. 

*MISDATA.DAT 
Created along with a [[Saved_Game_Files#Battlescape_Files|battlescape save]], effectively a mirror of the original "MISSION.DAT". 

*MISSION2.DAT 
Appears in the MISSDAT folder at the end of combat. Contains debreifing data (such as who won, what was recovered and what points were scored). The relevant offsets for this file are unused by the previous two versions. 

Values are presented according to byte offset ([[#0|0]] to [[#169|169]]/[[#171|171]]) followed by the equivalent hex offset ([[#0x00|0x00]] to [[#0xA9|0xA9]]/[[#0xAB|0xAB]]) in '''bold'''. Let us know what else you can find!!

== Structure ==

{| class="wikitable"
|-
!Offset (Decimal)
!Offset (Hex)
!Usage
|-
|colspan="3"|The first 20 bytes are a count up of the various recoverable tile types in the map. These two-byte integers are only set if you actually won the mission by eliminating all enemy forces. These offsets + 100 index into the respective [[BASE.DAT]] values that they'll be added to.

See [[Equipment Recovery]] for more information.
|- valign="top"
!0-1
!0x00-0x01
|[[UFO Power Source]] ([[MCD#59|MCD[59]]] set to 02).
|- valign="top"
!2-3
!0x02-0x03
|[[UFO Navigation]] ([[MCD#59|MCD[59]]] set to 03, not counted for alien bases).
|- valign="top"
!4-5
!0x04-0x05
|[[UFO Construction]] ([[MCD#59|MCD[59]]] set to 04, no known tiles have this set).
|- valign="top"
!6-7
!0x06-0x07
|[[Alien Food]] ([[MCD#59|MCD[59]]] set to 05).
|- valign="top"
!8-9
!0x08-0x09
|[[Alien Reproduction]] ([[MCD#59|MCD[59]]] set to 06, no known tiles have this set).
|- valign="top"
!10-11
!0x0A-0x0B
|[[Alien Entertainment]] ([[MCD#59|MCD[59]]] set to 07).
|- valign="top"
!12-13
!0x0C-0x0D
|[[Alien Surgery]] ([[MCD#59|MCD[59]]] set to 08).
|- valign="top"
!14-15
!0x0E-0x0F
|[[Examination Room]] ([[MCD#59|MCD[59]]] set to 09).
|- valign="top"
!16-17
!0x10-0x11
|[[Alien Alloys]] ([[MCD#59|MCD[59]]] set to 10).

The total is divided by 2 for a UFO mission or 30 for an alien base. The value stored here is further divided by 5 to get the result you see on the debriefing screen.
|- valign="top"
!18-19
!0x12-0x13
|[[Alien Habitat]] ([[MCD#59|MCD[59]]] set to 11, no known tiles have this set).
|- valign="top"
!20-21
!0x14-0x15
|Mission descriptor. Possible values:
UFO TFTD
0: UFO Site 0: Alien Sub Site
1: Terror Site 1: Port/Island Attack
2: Base Defence (X-COM Base) 2: Base Defense (X-COM Base)
3: Base Offense (Alien Base) 3: Colony Stage 1
4: Mars Stage 1 4: T'leth Stage 1
5: Mars Stage 2 5: T'leth Stage 2
6: T'leth Stage 3
7: Artefact Site Stage 1
8: Artefact Site Stage 2
9: Passenger/Cargo Ship Stage 1
10: Passenger/Cargo Ship Stage 2
11: Colony Stage 2
|-
|colspan="3"|Values 22-73 (Hex: 16-49) primarily hold scoring information. As per the tile recovery indexes, these are only stored in the final "end-of-combat" MISSION2.DAT. For temporary storage mid-mission, some of these values are stored in [[WGLOB.DAT]].
|- valign="top"
!22-23
!0x16-0x17
|Aliens killed.
|- valign="top"
!24-25
!0x18-0x19
|Aliens killed score.
|- valign="top"
!26-27
!0x1A-0x1B
|Alien corpses.
|- valign="top"
!28-29
!0x1C-0x1D
|Corpse score.
|- valign="top"
!30-31
!0x1E-0x1F
|Live aliens captured.
|- valign="top"
!32-33
!0x20-0x21
|Live alien score.
|- valign="top"
!34-35
!0x22-0x23
|Artefacts (''unresearched'' alien items) recovered.
|- valign="top"
!36-37
!0x24-0x25
|Artefacts score.
|- valign="top"
!38-39
!0x26-0x27
|Alien base control destroyed. This flags if you win a [[Alien_Base_Assault|base offense mission]] by killing all enemy forces, or if you destroy all 16 nav modules in the command center. If not zero, the base you were attacking will be removed from the world map at the end of combat.
|- valign="top"
!40-41
!0x28-0x29
|Base control score.
|- valign="top"
!42-43
!0x2A-0x2B
|Civilians killed by aliens.
|- valign="top"
!44-45
!0x2C-0x2D
|Civilians killed by aliens score (typically negative).
|- valign="top"
!46-47
!0x2E-0x2F
|Civilians killed by X-COM.
|- valign="top"
!48-49
!0x30-0x31
|Civilians killed by X-COM score (typically negative).
|- valign="top"
!50-51
!0x32-0x33
|Civilians saved.
|- valign="top"
!52-53
!0x34-0x35
|Civilians saved score.
|- valign="top"
!54-55
!0x36-0x37
|X-COM troopers killed.
|- valign="top"
!56-57
!0x38-0x39
|X-COM troopers killed score (typically negative).
|- valign="top"
!58-59
!0x3A-0x3B
|X-COM troopers "retired through injury" (never actually flags).
|- valign="top"
!60-61
!0x3C-0x3D
|X-COM troopers "retired through injury" score (never actually flags).
|- valign="top"
!62-63
!0x3E-0x3F
|X-COM troopers MIA.
|- valign="top"
!64-65
!0x40-0x41
|X-COM troopers MIA score (typically negative).
|- valign="top"
!66-67
!0x42-0x43
|Tanks lost.
|- valign="top"
!68-69
!0x44-0x45
|Tanks lost score (typically negative).
|- valign="top"
!70-71
!0x46-0x47
|X-COM craft lost (GeoScape ignores this if you actually lose a craft, Tactical sets it regardless).
|- valign="top"
!72-73
!0x48-0x49
|X-COM craft lost score (GeoScape ignores this if you actually lose a craft, Tactical doesn't set it regardless).
|- valign="top"
!74-75
!0x4A-0x4B
|A value based on the time at the [[LOC.DAT]] location. References into a table stored in the executable in order to define the values in [[BGLOB.DAT]].
|- valign="top"
!76
!0x4C
|For a UFO site, this is the [[LOC.DAT]] reference corresponding to the crash site. This is plausibly true for every mission type (with the possible exception of the [[Cydonia|Mars assault]]). Used to determine whether the alien ship crashed or not (and therefore whether to randomly detonate the power supply units). ''I seem to remember that tweaking this byte could have an effect on [[BGLOB.DAT]], but I might've confused myself. - [[User:Bomb Bloke|Bomb Bloke]] 03:45, 23 June 2008 (PDT)''
|- valign="top"
!77
!0x4D
|Index into [[CRAFT.DAT]] pointing to the craft sent on this mission. In the case of base defence (see offset [[#79|[79]]]), it indexes to the [[LOC.DAT]] record for the base in concern.
|- valign="top"
!78
!0x4E
|Victory status.

0: Mission aborted with some units in exit areas.
1: Mission won.
2: Mission lost.
3: Mission aborted with no units in exit areas.
|- valign="top"
!79
!0x4F
|0 unless the mission is a UFO site, in which case it is 1. Determines use of [[#77|[77]]] but doesn't seem to affect [[#16-17|[16-17]]].
|- valign="top"
!80-151
!0x50-0x97
|A list of 36 two-byte integers, used during base defence missions. In order, they represent each module in your base, reading from left to right, top to bottom.

At the end of battle, the tactical game engine tallies up the amount of [[Base_Defence#Destruction_Of_Base_Facilities|"target" objects]] existing within each module, and stores the results in "MISSION2.DAT". If that figure is 0 for any given destructible [[Base_Facilities_(EU)|facility]], then the geoscape engine will remove it from your base (along with any ''other'' modules that relied on that section for passage to the [[Access Lift]]).

"Target objects" are tiles that have offset 60 set to 1 within their [[MCD]] record.
|-
|colspan="3"|Bytes '''152-167''' (Hex: '''0x98-0xA7''') allow you to use the following equipment only if they are set to 1. X-COM produced equipment can be used even if it hasn't been researched (however, in order to get it into combat, you must build it - and that requires research). The last three entries in the list are item slots that were never used in the game.
|'''TFTD'''
|- valign="top"
!152
!0x98
|Enables [[Heavy Plasma]] ([[OBDATA.DAT|ObData]][34])
|[[Vibro_Blade|Vibroblade]]
|- valign="top"
!153
!0x99
|Enables [[Heavy Plasma Clip]] ([[OBDATA.DAT|ObData]][35])
|[[Thermic_Lance|Thermic Lance]]
|- valign="top"
!154
!0x9A
|Enables [[Plasma Rifle]] ([[OBDATA.DAT|ObData]][36])
|[[Heavy_Thermic_Lance|Heavy Thermic Lance]]
|- valign="top"
!155
!0x9B
|Enables [[Plasma Rifle Clip]] ([[OBDATA.DAT|ObData]][37])
|[[Sonic_Cannon|Sonic Cannon]]
|- valign="top"
!156
!0x9C
|Enables [[Plasma Pistol]] ([[OBDATA.DAT|ObData]][38])
|Sonic Cannon Clip
|- valign="top"
!157
!0x9D
|Enables [[Plasma Pistol Clip]] ([[OBDATA.DAT|ObData]][39])
|[[Sonic-Blasta_Rifle|Sonic-Blasta Rifle]]
|- valign="top"
!158
!0x9E
|Enables [[Blaster Launcher]] ([[OBDATA.DAT|ObData]][40])
|Blasta Clip
|- valign="top"
!159
!0x9F
|Enables [[Blaster Bomb]] ([[OBDATA.DAT|ObData]][41])
|[[Sonic_Pistol|Sonic Pistol]]
|- valign="top"
!160
!0xA0
|Enables [[Small Launcher]] ([[OBDATA.DAT|ObData]][42])
|Sonic Pistol Clip
|- valign="top"
!161
!0xA1
|Enables [[Stun Bomb]] ([[OBDATA.DAT|ObData]][43])
|[[Disruptor_Pulse_Launcher|Disruptor Pulse Launcher]]
|- valign="top"
!162
!0xA2
|Enables [[Alien Grenade]] ([[OBDATA.DAT|ObData]][44])
|Disruptor Ammo
|- valign="top"
!163
!0xA3
|Enables [[Elerium-115]] ([[OBDATA.DAT|ObData]][45])
|[[Thermal_Shok_Launcher|Thermal Shok Launcher]]
|- valign="top"
!164
!0xA4
|Enables [[Mind Probe]] ([[OBDATA.DAT|ObData]][46])
|Thermal Shok Bomb
|- valign="top"
!165
!0xA5
|Enables "null>>UNDEFINED <<" ([[OBDATA.DAT|ObData]][47])
|[[Sonic_Pulser|Sonic Pulsar]]
|- valign="top"
!166
!0xA6
|Enables "null>> empty <<" ([[OBDATA.DAT|ObData]][48])
|null
|- valign="top"
!167
!0xA7
|Enables "null>> empty <<" ([[OBDATA.DAT|ObData]][49])
|[[M.C._Reader|M.C. Reader]]
|- valign="top"
!168-169
!0xA8-0xA9
|Determines the language in which the mission was initiated. If the game is saved and later loaded, this overrides whatever language was selected when the program started.

0 - English
1 - German
2 - French
|- valign="top"
!170-171
!0xAA-0xAB
|Only present for TFTD. Determines the depth level (that is, which [[PALETTES.DAT#TFTD Tactical Palettes|battlescape palette]] to use, whether to render air bubbles around units, and which background noise to play):

0 - Surface
1 - Shallow Water
2 - Medium Depths
3 - Deep Sea

Values above 3 use the surface palette, but otherwise act as though the mission were underwater.
|}

==See Also==
* [[Battlescape Map Generation]]
* [[Saved Game Files]]
* [[OBDATA.DAT]]
* [[MCD|MCD files]]
* [[WGLOB.DAT]]
* [[CRAFT.DAT]]
* [[BASE.DAT]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

RESEARCH.DAT (TFTD)

2016-03-23T08:11:22Z

Morgan525: switched decimal to hex

UNDER CONSTRUCTION

File dump created using Smart Dump 3.11

File: game_1\research.dat
<pre>
Object /
# Offset Base Research UfoPedia Score Don't Has No* Prereqs*
| Days Category Cat Obj | Repeat? Prereq? Met/Nil?
00 00000000: 0032 00 00 00 00 0B 00 0A 00 00000000 00000001 00000001 Gauss Tech
01 00000016: 00B4 00 00 18 00 02 17 14 00 00000000 00000001 00000001 Particle Disturbance Sensor
02 0000002C: 00D2 00 00 19 00 02 18 14 00 00000000 00000001 00000001 Medi-Kit
03 00000042: 01F4 00 00 1D 00 02 19 14 00 00000000 00000000 00000000 M.C. Disruptor
04 00000058: 0320 31 00 00 00 03 22 1E 00 00000000 00000001 00000001 Sonic Cannon
05 0000006E: 0190 32 00 00 00 03 23 07 00 00000000 00000001 00000001 Cannon Power Clip
06 00000084: 02BC 33 00 00 00 03 24 19 00 00000000 00000001 00000001 Blasta Rifle
07 0000009A: 0190 34 00 00 00 03 25 06 00 00000000 00000001 00000001 Blasta Clip
08 000000B0: 0258 35 00 00 00 03 26 14 00 00000000 00000001 00000001 Sonic Pistol
09 000000C6: 0190 36 00 00 00 03 27 05 00 00000000 00000001 00000001 Sonic Pistol Clip
0A 000000DC: 0384 37 00 00 00 03 28 28 00 00000000 00000000 00000000 Disruptor Pulse Launcher
0B 000000F2: 012C 38 00 00 00 03 29 0A 00 00000000 00000000 00000000 Disruptor Ammo
0C 00000108: 0226 39 00 00 00 03 2A 1E 00 00000000 00000001 00000001 Thermal Shock Launcher
0D 0000011E: 00B4 3A 00 00 00 03 2B 0A 00 00000000 00000001 00000001 Thermal Shock Bomb
0E 00000134: 00C8 3B 00 00 00 03 2C 14 00 00000000 00000001 00000001 Sonic Pulser
0F 0000014A: 01C2 3C 00 00 00 03 2D 28 00 00000000 00000001 00000001 Zrbite
10 00000160: 0258 3D 00 00 00 03 2E 19 00 00000000 00000000 00000000 M.C. Reader
11 00000176: 01C2 50 00 00 00 07 00 1E 00 00000000 00000001 00000001 Ion-Beam Accelerator
12 0000018C: 01C2 51 00 00 00 07 01 1E 00 00000000 00000001 00000001 Magnetic Navigation
13 000001A2: 01C2 52 00 14 00 07 02 1E 00 00000000 00000000 00000000 Alien Sub Construction
14 000001B8: 0096 53 00 00 00 07 03 1E 00 00000000 00000001 00000001 Alien Cryogenics
15 000001CE: 0096 54 00 00 00 07 04 1E 00 00000000 00000001 00000001 Alien Cloning
16 000001E4: 0096 55 00 00 00 07 05 1E 00 00000000 00000001 00000001 Alien Learning Arrays
17 000001FA: 0096 56 00 00 00 07 06 1E 00 00000000 00000001 00000001 Alien Implanter
18 00000210: 0096 57 00 00 00 07 07 1E 00 00000000 00000001 00000001 Examination Room
19 00000226: 0190 00 00 00 00 07 08 1E 00 00000000 00000000 00000000 Aqua Plastics
1A 0000023C: 0258 00 00 01 00 00 04 1E 00 00000000 00000000 00000000 Manta
1B 00000252: 02BC 00 00 02 00 00 01 1E 00 00000000 00000000 00000000 Hammerhead
1C 00000268: 0384 00 00 03 00 00 02 1E 00 00000000 00000000 00000000 Leviathan
1D 0000027E: 0064 00 00 04 00 02 10 0A 00 00000000 00000000 00000000 Gauss Pistol
1E 00000294: 012C 00 00 05 00 02 11 0A 00 00000000 00000000 00000000 Gauss Rifle
1F 000002AA: 01CC 00 00 06 00 02 12 0A 00 00000000 00000000 00000000 Heavy Gauss
20 000002C0: 01A4 00 00 07 00 00 09 0A 00 00000000 00000000 00000000 Craft Gauss Cannon (includes Gauss Cannon Ammo)
21 000002D6: 0294 00 00 08 00 00 0A 19 00 00000000 00000000 00000000 Sonic Oscillator
22 000002EC: 0370 00 00 09 00 00 08 19 00 00000000 00000000 00000000 PWT Cannon
23 00000302: 01FE 00 00 0A 00 04 09 0F 00 00000000 00000000 00000000 Gauss Defences
24 00000318: 026C 00 00 0B 00 04 0A 19 00 00000000 00000000 00000000 Sonic Defences
25 0000032E: 0320 00 00 0C 00 04 0B 19 00 00000000 00000000 00000000 PWT Defences
26 00000344: 03A2 00 00 0D 00 04 0C 19 00 00000000 00000000 00000000 Bombardment Shield
27 0000035A: 0168 00 00 0E 00 04 0D 19 00 00000000 00000000 00000000 MC Generator
28 00000370: 01A4 00 00 0F 00 04 0E 19 00 00000000 00000000 00000000 MC Lab
29 00000386: 029E 00 00 10 00 04 0F 19 00 00000000 00000000 00000000 Transmission Resolver
2A 0000039C: 00FA 00 00 11 00 01 02 0F 00 00000000 00000000 00000000 Coelacanth/Gauss
2B 000003B2: 01AE 00 00 12 00 01 03 19 00 00000000 00000000 00000000 Displacer/Sonic
2C 000003C8: 02B2 00 00 13 00 01 04 19 00 00000000 00000000 00000000 Displacer/PWT
2D 000003DE: 00B4 41 00 00 00 05 01 32 00 00000000 00000001 00000001 Aquatoid Corpse
2E 000003F4: 00B4 42 00 00 00 05 03 32 00 00000000 00000001 00000001 Gill Man Corpse
2F 0000040A: 00B4 43 00 00 00 05 05 32 00 00000000 00000001 00000001 Lobsterman Corpse
30 00000420: 00B4 44 00 00 00 05 07 32 00 00000000 00000001 00000001 Tasoth Corpse
31 00000436: 00B4 45 00 00 00 05 09 32 00 00000000 00000001 00000001 Calcinite Corpse
32 0000044C: 00B4 46 00 00 00 05 0B 32 00 00000000 00000001 00000001 Deep One Corpse
33 00000462: 00B4 47 00 00 00 05 0D 32 00 00000000 00000001 00000001 Biodrone Corpse
34 00000478: 00B4 48 00 00 00 05 0F 32 00 00000000 00000001 00000001 Tentaculat Corpse
35 0000048E: 00B4 49 00 00 00 05 11 32 00 00000000 00000001 00000001 Triscene Corpse
36 000004A4: 00B4 4A 00 00 00 05 13 32 00 00000000 00000001 00000001 Hallucinoid Corpse
37 000004BA: 00B4 4B 00 00 00 05 15 32 00 00000000 00000001 00000001 Xarquid Corpse
38 000004D0: 012C 00 00 15 00 06 64 3C 00 00000000 00000000 00000000 Alien Origins
39 000004E6: 01F4 00 00 16 00 06 65 3C 00 00000000 00000000 00000000 Ultimate Threat
3A 000004FC: 0258 00 00 17 00 06 66 3C 00 00000000 00000000 00000000 T'leth the alien city
3B 00000512: 00B4 00 00 1A 00 02 64 14 00 00000000 00000000 00000000 Plastic Aqua Armor
3C 00000528: 00CD 00 00 1B 00 02 65 14 00 00000000 00000000 00000000 Ion Armor
3D 0000053E: 014A 00 00 1C 00 02 66 14 00 00000000 00000000 00000000 Mag-Ion Armor
3E 00000554: 003C 00 00 1E 00 02 2F 05 00 00000000 00000000 00000000 Gauss Pistol Clip
3F 0000056A: 0096 00 00 1F 00 02 30 07 00 00000000 00000000 00000000 Gauss Rifle Clip
40 00000580: 00E6 00 00 20 00 02 31 0A 00 00000000 00000000 00000000 Heavy Gauss Clip
41 00000596: 0190 00 00 11 00 02 0D 0A 00 00000000 00000000 00000000 <<BAD REF>> (unused Gauss Cannon ammo??)
42 000005AC: 01F4 00 00 21 05 03 1C 14 00 00000000 00000000 00000000 Vibroblade
43 000005C2: 01F4 00 00 22 00 03 1D 19 00 00000000 00000000 00000000 Thermic Lance
44 000005D8: 0258 00 00 23 00 03 1E 1E 00 00000000 00000000 00000000 Heavy Thermic Lance
45 000005EE: 00C0 00 01 01 00 06 01 00 00 00000000 00000001 00000001 Live Aquatoid Soldier (r1)
46 00000604: 00C0 00 01 02 00 06 01 00 00 00000000 00000001 00000001 Live Aquatoid Squad Leader (r2)
47 0000061A: 00C0 00 01 03 00 06 01 00 00 00000000 00000001 00000001 Live Aquatoid Technician (r3)
48 00000630: 00C0 00 01 04 00 06 01 00 00 00000000 00000001 00000001 Live Aquatoid Medic (r4)
49 00000646: 00C0 00 01 05 00 06 01 00 00 00000000 00000001 00000001 Live Aquatoid Navigator (r5)
4A 0000065C: 00C0 00 01 06 00 06 01 00 00 00000000 00000001 00000001 Live Aquatoid Commander (r6)
4B 00000672: 00C0 00 02 01 00 06 02 00 00 00000000 00000001 00000001 Live Gillman Soldier (r1)
4C 00000688: 00C0 00 02 04 00 06 02 00 00 00000000 00000001 00000001 Live Gillman Squad Leader (r4)
4E 0000069E: 00C0 00 02 05 00 06 02 00 00 00000000 00000001 00000001 Live Gillman Technician (r5)
4F 000006B4: 00C0 00 02 06 00 06 02 00 00 00000000 00000001 00000001 Live Gillman Commander (r6)
50 000006CA: 00C0 00 03 01 00 06 03 00 00 00000000 00000001 00000001 Live Lobsterman Soldier (r1)
51 000006E0: 00C0 00 03 02 00 06 03 00 00 00000000 00000001 00000001 Live Lobsterman Squad Leader (r2)
52 000006F6: 00C0 00 03 04 00 06 03 00 00 00000000 00000001 00000001 Live Lobsterman Technician (r4)
53 0000070C: 00C0 00 03 05 00 06 03 00 00 00000000 00000001 00000001 Live Lobsterman Navigator (r5)
54 00000722: 00C0 00 03 06 00 06 03 00 00 00000000 00000001 00000001 Live Lobsterman Commander (r6)
55 00000738: 00C0 00 04 05 00 06 04 00 00 00000000 00000001 00000001 Live Tasoth Soldier (r5)
56 0000074E: 00C0 00 04 06 00 06 04 00 00 00000000 00000001 00000001 Live Tasoth Squad Leader (r6)
57 00000764: 00AA 00 05 07 00 06 05 00 00 00000000 00000001 00000001 **Live terror units from here onward**
58 0000077A: 00AA 00 06 07 00 06 06 00 00 00000000 00000001 00000001
59 00000790: 00AA 00 07 07 00 06 07 00 00 00000000 00000001 00000001
5A 000007A6: 00AA 00 08 07 00 06 08 00 00 00000000 00000001 00000001
5B 000007BC: 00AA 00 09 07 00 06 09 00 00 00000000 00000001 00000001
5C 000007D2: 00AA 00 0A 07 00 06 0A 00 00 00000000 00000001 00000001
5D 000007E8: 00AA 00 0B 07 00 06 0B 00 00 00000000 00000001 00000001
5E 000007FE: 0000 00 00 00 00 00 00 00 00 00000000 00000000 00000000 (Presumed End of File record)
</pre>
--[[User:BladeFireLight|BladeFireLight]] 21:45, 5 January 2010 (EST)

(Moved from [[Talk:Alien Research (TFTD)]])[[User:Spike|Spike]] 16:33, 16 September 2012 (EDT)

<nowiki>*</nowiki>Note: Prereqs referred to in the last two columns are ''in addition'' to the pre-req of possessing the researched object (columns 2-4 / bytes 0x02-0x4).

Column headings and interpretation above ''assumes'' the structure is identical to EU. See [[RESEARCH.DAT]] for more information.

[[Category:Game Files (TFTD)]]
[[Category:TFTD]]

MISDATA.DAT

2016-03-23T05:33:44Z

Morgan525: /* Structure */

This 170 byte file (172 for TFTD) is only used by tactical saves, and much of it is made up of two-byte signed integers. It comes in three flavours: 

*MISSION.DAT 
Initially created by the GeoScape engine and stored in the [[Saved_Game_Files#Missdat_Files|MISSDAT]] folder. Contains info required for [[Battlescape Map Generation]]. 

*MISDATA.DAT 
Created along with a [[Saved_Game_Files#Battlescape_Files|battlescape save]], effectively a mirror of the original "MISSION.DAT". 

*MISSION2.DAT 
Appears in the MISSDAT folder at the end of combat. Contains debreifing data (such as who won, what was recovered and what points were scored). The relevant offsets for this file are unused by the previous two versions. 

Values are presented according to byte offset ([[#0|0]] to [[#169|169]]/[[#171|171]]) followed by the equivalent hex offset ([[#0x00|0x00]] to [[#0xA9|0xA9]]/[[#0xAB|0xAB]]) in '''bold'''. Let us know what else you can find!!

== Structure ==

{| class="wikitable"
|-
!Offset (Decimal)
!Offset (Hex)
!Usage
|-
|colspan="3"|The first 20 bytes are a count up of the various recoverable tile types in the map. These two-byte integers are only set if you actually won the mission by eliminating all enemy forces. These offsets + 100 index into the respective [[BASE.DAT]] values that they'll be added to.

See [[Equipment Recovery]] for more information.
|- valign="top"
!0-1
!0x00-0x01
|[[UFO Power Source]] ([[MCD#59|MCD[59]]] set to 02).
|- valign="top"
!2-3
!0x02-0x03
|[[UFO Navigation]] ([[MCD#59|MCD[59]]] set to 03, not counted for alien bases).
|- valign="top"
!4-5
!0x04-0x05
|[[UFO Construction]] ([[MCD#59|MCD[59]]] set to 04, no known tiles have this set).
|- valign="top"
!6-7
!0x06-0x07
|[[Alien Food]] ([[MCD#59|MCD[59]]] set to 05).
|- valign="top"
!8-9
!0x08-0x09
|[[Alien Reproduction]] ([[MCD#59|MCD[59]]] set to 06, no known tiles have this set).
|- valign="top"
!10-11
!0x0A-0x0B
|[[Alien Entertainment]] ([[MCD#59|MCD[59]]] set to 07).
|- valign="top"
!12-13
!0x0C-0x0D
|[[Alien Surgery]] ([[MCD#59|MCD[59]]] set to 08).
|- valign="top"
!14-15
!0x0E-0x0F
|[[Examination Room]] ([[MCD#59|MCD[59]]] set to 09).
|- valign="top"
!16-17
!0x10-0x11
|[[Alien Alloys]] ([[MCD#59|MCD[59]]] set to 10).

The total is divided by 2 for a UFO mission or 30 for an alien base. The value stored here is further divided by 5 to get the result you see on the debriefing screen.
|- valign="top"
!18-19
!0x12-0x13
|[[Alien Habitat]] ([[MCD#59|MCD[59]]] set to 11, no known tiles have this set).
|- valign="top"
!20-21
!0x14-0x15
|Mission descriptor. Possible values:
UFO TFTD
0: UFO Site 0: Alien Sub Site
1: Terror Site 1: Port/Island Attack
2: Base Defence (X-COM Base) 2: Base Defense (X-COM Base)
3: Base Offense (Alien Base) 3: Colony Stage 1
4: Mars Stage 1 4: T'leth Stage 1
5: Mars Stage 2 5: T'leth Stage 2
6: T'leth Stage 3
7: Artefact Site Stage 1
8: Artefact Site Stage 2
9: Passenger/Cargo Ship Stage 1
10: Passenger/Cargo Ship Stage 2
11: Colony Stage 2
|-
|colspan="3"|Values 22-73 (Hex: 16-49) primarily hold scoring information. As per the tile recovery indexes, these are only stored in the final "end-of-combat" MISSION2.DAT. For temporary storage mid-mission, some of these values are stored in [[WGLOB.DAT]].
|- valign="top"
!22-23
!0x16-0x17
|Aliens killed.
|- valign="top"
!24-25
!0x18-0x19
|Aliens killed score.
|- valign="top"
!26-27
!0x1A-0x1B
|Alien corpses.
|- valign="top"
!28-29
!0x1C-0x1D
|Corpse score.
|- valign="top"
!30-31
!0x1E-0x1F
|Live aliens captured.
|- valign="top"
!32-33
!0x20-0x21
|Live alien score.
|- valign="top"
!34-35
!0x22-0x23
|Artefacts (''unresearched'' alien items) recovered.
|- valign="top"
!36-37
!0x24-0x25
|Artefacts score.
|- valign="top"
!38-39
!0x26-0x27
|Alien base control destroyed. This flags if you win a [[Alien_Base_Assault|base offense mission]] by killing all enemy forces, or if you destroy all 16 nav modules in the command center. If not zero, the base you were attacking will be removed from the world map at the end of combat.
|- valign="top"
!40-41
!0x28-0x29
|Base control score.
|- valign="top"
!42-43
!0x2A-0x2B
|Civilians killed by aliens.
|- valign="top"
!44-45
!0x2C-0x2D
|Civilians killed by aliens score (typically negative).
|- valign="top"
!46-47
!0x2E-0x2F
|Civilians killed by X-COM.
|- valign="top"
!48-49
!0x30-0x31
|Civilians killed by X-COM score (typically negative).
|- valign="top"
!50-51
!0x32-0x33
|Civilians saved.
|- valign="top"
!52-53
!0x34-0x35
|Civilians saved score.
|- valign="top"
!54-55
!0x36-0x37
|X-COM troopers killed.
|- valign="top"
!56-57
!0x38-0x39
|X-COM troopers killed score (typically negative).
|- valign="top"
!58-59
!0x3A-0x3B
|X-COM troopers "retired through injury" (never actually flags).
|- valign="top"
!60-61
!0x3C-0x3D
|X-COM troopers "retired through injury" score (never actually flags).
|- valign="top"
!62-63
!0x3E-0x3F
|X-COM troopers MIA.
|- valign="top"
!64-65
!0x40-0x41
|X-COM troopers MIA score (typically negative).
|- valign="top"
!66-67
!0x42-0x43
|Tanks lost.
|- valign="top"
!68-69
!0x44-0x45
|Tanks lost score (typically negative).
|- valign="top"
!70-71
!0x46-0x47
|X-COM craft lost (GeoScape ignores this if you actually lose a craft, Tactical sets it regardless).
|- valign="top"
!72-73
!0x48-0x49
|X-COM craft lost score (GeoScape ignores this if you actually lose a craft, Tactical doesn't set it regardless).
|- valign="top"
!74-75
!0x4A-0x4B
|A value based on the time at the [[LOC.DAT]] location. References into a table stored in the executable in order to define the values in [[BGLOB.DAT]].
|- valign="top"
!76
!0x4C
|For a UFO site, this is the [[LOC.DAT]] reference corresponding to the crash site. This is plausibly true for every mission type (with the possible exception of the [[Cydonia|Mars assault]]). Used to determine whether the alien ship crashed or not (and therefore whether to randomly detonate the power supply units). ''I seem to remember that tweaking this byte could have an effect on [[BGLOB.DAT]], but I might've confused myself. - [[User:Bomb Bloke|Bomb Bloke]] 03:45, 23 June 2008 (PDT)''
|- valign="top"
!77
!0x4D
|Index into [[CRAFT.DAT]] pointing to the craft sent on this mission. In the case of base defence (see offset [[#79|[79]]]), it indexes to the [[LOC.DAT]] record for the base in concern.
|- valign="top"
!78
!0x4E
|Victory status.

0: Mission aborted with some units in exit areas.
1: Mission won.
2: Mission lost.
3: Mission aborted with no units in exit areas.
|- valign="top"
!79
!0x4F
|0 unless the mission is a UFO site, in which case it is 1. Determines use of [[#77|[77]]] but doesn't seem to affect [[#16-17|[16-17]]].
|- valign="top"
!80-151
!0x50-0x97
|A list of 36 two-byte integers, used during base defence missions. In order, they represent each module in your base, reading from left to right, top to bottom.

At the end of battle, the tactical game engine tallies up the amount of [[Base_Defence#Destruction_Of_Base_Facilities|"target" objects]] existing within each module, and stores the results in "MISSION2.DAT". If that figure is 0 for any given destructible [[Base_Facilities_(EU)|facility]], then the geoscape engine will remove it from your base (along with any ''other'' modules that relied on that section for passage to the [[Access Lift]]).

"Target objects" are tiles that have offset 60 set to 1 within their [[MCD]] record.
|-
|colspan="3"|Bytes '''152-167''' (Hex: '''0x98-0xA7''') allow you to use the following equipment only if they are set to 1. X-COM produced equipment can be used even if it hasn't been researched (however, in order to get it into combat, you must build it - and that requires research). The last three entries in the list are item slots that were never used in the game.
|- valign="top"
!152
!0x98
|Enables [[Heavy Plasma]] ([[OBDATA.DAT|ObData]][34])
|- valign="top"
!153
!0x99
|Enables [[Heavy Plasma Clip]] ([[OBDATA.DAT|ObData]][35])
|- valign="top"
!154
!0x9A
|Enables [[Plasma Rifle]] ([[OBDATA.DAT|ObData]][36])
|- valign="top"
!155
!0x9B
|Enables [[Plasma Rifle Clip]] ([[OBDATA.DAT|ObData]][37])
|- valign="top"
!156
!0x9C
|Enables [[Plasma Pistol]] ([[OBDATA.DAT|ObData]][38])
|- valign="top"
!157
!0x9D
|Enables [[Plasma Pistol Clip]] ([[OBDATA.DAT|ObData]][39])
|- valign="top"
!158
!0x9E
|Enables [[Blaster Launcher]] ([[OBDATA.DAT|ObData]][40])
|- valign="top"
!159
!0x9F
|Enables [[Blaster Bomb]] ([[OBDATA.DAT|ObData]][41])
|- valign="top"
!160
!0xA0
|Enables [[Small Launcher]] ([[OBDATA.DAT|ObData]][42])
|- valign="top"
!161
!0xA1
|Enables [[Stun Bomb]] ([[OBDATA.DAT|ObData]][43])
|- valign="top"
!162
!0xA2
|Enables [[Alien Grenade]] ([[OBDATA.DAT|ObData]][44])
|- valign="top"
!163
!0xA3
|Enables [[Elerium-115]] ([[OBDATA.DAT|ObData]][45])
|- valign="top"
!164
!0xA4
|Enables [[Mind Probe]] ([[OBDATA.DAT|ObData]][46])
|- valign="top"
!165
!0xA5
|Enables "null>>UNDEFINED <<" ([[OBDATA.DAT|ObData]][47])
|- valign="top"
!166
!0xA6
|Enables "null>> empty <<" ([[OBDATA.DAT|ObData]][48])
|- valign="top"
!167
!0xA7
|Enables "null>> empty <<" ([[OBDATA.DAT|ObData]][49])
|- valign="top"
!168-169
!0xA8-0xA9
|Determines the language in which the mission was initiated. If the game is saved and later loaded, this overrides whatever language was selected when the program started.

0 - English
1 - German
2 - French
|- valign="top"
!170-171
!0xAA-0xAB
|Only present for TFTD. Determines the depth level (that is, which [[PALETTES.DAT#TFTD Tactical Palettes|battlescape palette]] to use, whether to render air bubbles around units, and which background noise to play):

0 - Surface
1 - Shallow Water
2 - Medium Depths
3 - Deep Sea

Values above 3 use the surface palette, but otherwise act as though the mission were underwater.
|}

==See Also==
* [[Battlescape Map Generation]]
* [[Saved Game Files]]
* [[OBDATA.DAT]]
* [[MCD|MCD files]]
* [[WGLOB.DAT]]
* [[CRAFT.DAT]]
* [[BASE.DAT]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

MISDATA.DAT

2016-03-23T05:32:59Z

Morgan525: /* Structure */

This 170 byte file (172 for TFTD) is only used by tactical saves, and much of it is made up of two-byte signed integers. It comes in three flavours: 

*MISSION.DAT 
Initially created by the GeoScape engine and stored in the [[Saved_Game_Files#Missdat_Files|MISSDAT]] folder. Contains info required for [[Battlescape Map Generation]]. 

*MISDATA.DAT 
Created along with a [[Saved_Game_Files#Battlescape_Files|battlescape save]], effectively a mirror of the original "MISSION.DAT". 

*MISSION2.DAT 
Appears in the MISSDAT folder at the end of combat. Contains debreifing data (such as who won, what was recovered and what points were scored). The relevant offsets for this file are unused by the previous two versions. 

Values are presented according to byte offset ([[#0|0]] to [[#169|169]]/[[#171|171]]) followed by the equivalent hex offset ([[#0x00|0x00]] to [[#0xA9|0xA9]]/[[#0xAB|0xAB]]) in '''bold'''. Let us know what else you can find!!

== Structure ==

{| class="wikitable"
|-
!Offset (Decimal)
!Offset (Hex)
!Usage
|-
|colspan="3"|The first 20 bytes are a count up of the various recoverable tile types in the map. These two-byte integers are only set if you actually won the mission by eliminating all enemy forces. These offsets + 100 index into the respective [[BASE.DAT]] values that they'll be added to.

See [[Equipment Recovery]] for more information.
|- valign="top"
!0-1
!0x00-0x01
|[[UFO Power Source]] ([[MCD#59|MCD[59]]] set to 02).
|- valign="top"
!2-3
!0x02-0x03
|[[UFO Navigation]] ([[MCD#59|MCD[59]]] set to 03, not counted for alien bases).
|- valign="top"
!4-5
!0x04-0x05
|[[UFO Construction]] ([[MCD#59|MCD[59]]] set to 04, no known tiles have this set).
|- valign="top"
!6-7
!0x06-0x07
|[[Alien Food]] ([[MCD#59|MCD[59]]] set to 05).
|- valign="top"
!8-9
!0x08-0x09
|[[Alien Reproduction]] ([[MCD#59|MCD[59]]] set to 06, no known tiles have this set).
|- valign="top"
!10-11
!0x0A-0x0B
|[[Alien Entertainment]] ([[MCD#59|MCD[59]]] set to 07).
|- valign="top"
!12-13
!0x0C-0x0D
|[[Alien Surgery]] ([[MCD#59|MCD[59]]] set to 08).
|- valign="top"
!14-15
!0x0E-0x0F
|[[Examination Room]] ([[MCD#59|MCD[59]]] set to 09).
|- valign="top"
!16-17
!0x10-0x11
|[[Alien Alloys]] ([[MCD#59|MCD[59]]] set to 10).

The total is divided by 2 for a UFO mission or 30 for an alien base. The value stored here is further divided by 5 to get the result you see on the debriefing screen.
|- valign="top"
!18-19
!0x12-0x13
|[[Alien Habitat]] ([[MCD#59|MCD[59]]] set to 11, no known tiles have this set).
|- valign="top"
!20-21
!0x14-0x15
|Mission descriptor. Possible values:
UFO TFTD
0: UFO Site 0: Alien Sub Site
1: Terror Site 1: Port/Island Attack
2: Base Defence (X-COM Base) 2: Base Defense (X-COM Base)
3: Base Offense (Alien Base) 3: Colony Stage 1
4: Mars Stage 1 4: T'leth Stage 1
5: Mars Stage 2 5: T'leth Stage 2
6: T'leth Stage 3
7: Artefact Site Stage 1
8: Artefact Site Stage 2
9: Passenger/Cargo Ship Stage 1
10: Passenger/Cargo Ship Stage 2
11: Colony Stage 2
|-
|colspan="3"|Values 22-73 (Hex: 16-49) primarily hold scoring information. As per the tile recovery indexes, these are only stored in the final "end-of-combat" MISSION2.DAT. For temporary storage mid-mission, some of these values are stored in [[WGLOB.DAT]].
|- valign="top"
!22-23
!0x16-0x17
|Aliens killed.
|- valign="top"
!24-25
!0x18-0x19
|Aliens killed score.
|- valign="top"
!26-27
!0x1A-0x1B
|Alien corpses.
|- valign="top"
!28-29
!0x1C-0x1D
|Corpse score.
|- valign="top"
!30-31
!0x1E-0x1F
|Live aliens captured.
|- valign="top"
!32-33
!0x20-0x21
|Live alien score.
|- valign="top"
!34-35
!0x22-0x23
|Artefacts (''unresearched'' alien items) recovered.
|- valign="top"
!36-37
!0x24-0x25
|Artefacts score.
|- valign="top"
!38-39
!0x26-0x27
|Alien base control destroyed. This flags if you win a [[Alien_Base_Assault|base offense mission]] by killing all enemy forces, or if you destroy all 16 nav modules in the command center. If not zero, the base you were attacking will be removed from the world map at the end of combat.
|- valign="top"
!40-41
!0x28-0x29
|Base control score.
|- valign="top"
!42-43
!0x2A-0x2B
|Civilians killed by aliens.
|- valign="top"
!44-45
!0x2C-0x2D
|Civilians killed by aliens score (typically negative).
|- valign="top"
!46-47
!0x2E-0x2F
|Civilians killed by X-COM.
|- valign="top"
!48-49
!0x30-0x31
|Civilians killed by X-COM score (typically negative).
|- valign="top"
!50-51
!0x32-0x33
|Civilians saved.
|- valign="top"
!52-53
!0x34-0x35
|Civilians saved score.
|- valign="top"
!54-55
!0x36-0x37
|X-COM troopers killed.
|- valign="top"
!56-57
!0x38-0x39
|X-COM troopers killed score (typically negative).
|- valign="top"
!58-59
!0x3A-0x3B
|X-COM troopers "retired through injury" (never actually flags).
|- valign="top"
!60-61
!0x3C-0x3D
|X-COM troopers "retired through injury" score (never actually flags).
|- valign="top"
!62-63
!0x3E-0x3F
|X-COM troopers MIA.
|- valign="top"
!64-65
!0x40-0x41
|X-COM troopers MIA score (typically negative).
|- valign="top"
!66-67
!0x42-0x43
|Tanks lost.
|- valign="top"
!68-69
!0x44-0x45
|Tanks lost score (typically negative).
|- valign="top"
!70-71
!0x46-0x47
|X-COM craft lost (GeoScape ignores this if you actually lose a craft, Tactical sets it regardless).
|- valign="top"
!72-73
!0x48-0x49
|X-COM craft lost score (GeoScape ignores this if you actually lose a craft, Tactical doesn't set it regardless).
|- valign="top"
!74-75
!0x4A-0x4B
|A value based on the time at the [[LOC.DAT]] location. References into a table stored in the executable in order to define the values in [[BGLOB.DAT]].
|- valign="top"
!76
!0x4C
|For a UFO site, this is the [[LOC.DAT]] reference corresponding to the crash site. This is plausibly true for every mission type (with the possible exception of the [[Cydonia|Mars assault]]). Used to determine whether the alien ship crashed or not (and therefore whether to randomly detonate the power supply units). ''I seem to remember that tweaking this byte could have an effect on [[BGLOB.DAT]], but I might've confused myself. - [[User:Bomb Bloke|Bomb Bloke]] 03:45, 23 June 2008 (PDT)''
|- valign="top"
!77
!0x4D
|Index into [[CRAFT.DAT]] pointing to the craft sent on this mission. In the case of base defence (see offset [[#79|[79]]]), it indexes to the [[LOC.DAT]] record for the base in concern.
|- valign="top"
!78
!0x4E
|Victory status.

0: Mission aborted with some units in exit areas.
1: Mission won.
2: Mission lost.
3: Mission aborted with no units in exit areas.
|- valign="top"
!79
!0x4F
|0 unless the mission is a UFO site, in which case it is 1. Determines use of [[#77|[77]]] but doesn't seem to affect [[#16-17|[16-17]]].
|- valign="top"
!80-151
!0x50-0x97
|A list of 36 two-byte integers, used during base defence missions. In order, they represent each module in your base, reading from left to right, top to bottom.

At the end of battle, the tactical game engine tallies up the amount of [[Base_Defence#Destruction_Of_Base_Facilities|"target" objects]] existing within each module, and stores the results in "MISSION2.DAT". If that figure is 0 for any given destructible [[Base_Facilities_(EU)|facility]], then the geoscape engine will remove it from your base (along with any ''other'' modules that relied on that section for passage to the [[Access Lift]]).

"Target objects" are tiles that have offset 60 set to 1 within their [[MCD]] record.
|-
|colspan="3"|Bytes '''152-167''' (Hex: '''0x98-0xA7''') allow you to use the following equipment only if they are set to 1. X-COM produced equipment can be used even if it hasn't been researched (however, in order to get it into combat, you must build it - and that requires research). The last three entries in the list are item slots that were never used in the game.
|- valign="top"
!152
!0x98
|Enables [[Heavy Plasma]] ([[OBDATA.DAT|ObData]][34])
|- valign="top"
!153
!0x99
|Enables [[Heavy Plasma Clip]] ([[OBDATA.DAT|ObData]][35])
|- valign="top"
!154
!0x9A
|Enables [[Plasma Rifle]] ([[OBDATA.DAT|ObData]][36])
|- valign="top"
!155
!0x9B
|Enables [[Plasma Rifle Clip]] ([[OBDATA.DAT|ObData]][37])
|- valign="top"
!156
!0x9C
|Enables [[Plasma Pistol]] ([[OBDATA.DAT|ObData]][38])
|- valign="top"
!157
!0x9D
|Enables [[Plasma Pistol Clip]] ([[OBDATA.DAT|ObData]][39])
|- valign="top"
!158
!0x9E
|Enables [[Blaster Launcher]] ([[OBDATA.DAT|ObData]][40])
|- valign="top"
!159
!0x9F
|Enables [[Blaster Bomb]] ([[OBDATA.DAT|ObData]][41])
|- valign="top"
!160
!0xA0
|Enables [[Small Launcher]] ([[OBDATA.DAT|ObData]][42])
|- valign="top"
!161
!0xA1
|Enables [[Stun Bomb]] ([[OBDATA.DAT|ObData]][43])
|- valign="top"
!162
!0xA2
|Enables [[Alien Grenade]] ([[OBDATA.DAT|ObData]][44])
|- valign="top"
!163
!0xA3
|Enables [[Elerium-115]] ([[OBDATA.DAT|ObData]][45])
|- valign="top"
!164
!0xA4
|Enables [[Mind Probe]] ([[OBDATA.DAT|ObData]][46])
|- valign="top"
!165
!0xA5
|Enables "null>>UNDEFINED <<" ([[OBDATA.DAT|ObData]][47])
|- valign="top"
!166
!0xA6
|Enables "null>> empty <<" ([[OBDATA.DAT|ObData]][48])
|- valign="top"
!167
!0xA7
|Enables "null>> empty <<" ([[OBDATA.DAT|ObData]][49])
|- valign="top"
!168-169
!0xA8-0xA9
|Determines the language in which the mission was initiated. If the game is saved and later loaded, this overrides whatever language was selected when the program started.

0 - English
1 - German
2 - French
|- valign="top"
!170-171
!0xAA-0xAB
|Only present for TFTD. Determines the depth level (that is, which [[PALETTES.DAT#TFTD Tactical Palettes|battlescape palette]] to use, whether to render air bubbles around units, and which background noise to play):

0 - Surface
1 - Shallow Water
2 - Medium Depths
3 - Deep Sea

Values above 3 use the surface palette, but otherwise act as though the mission were underwater.
}

==See Also==
* [[Battlescape Map Generation]]
* [[Saved Game Files]]
* [[OBDATA.DAT]]
* [[MCD|MCD files]]
* [[WGLOB.DAT]]
* [[CRAFT.DAT]]
* [[BASE.DAT]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

ASTORE.DAT

2016-03-21T14:34:19Z

Morgan525: added note that TFTD has 100 entries

ASTORE.DAT contains information pertinent to live aliens in confinement.

== Structure ==
ASTORE.DAT has a fixed size of 50 entries (100 for TFTD) of 12 bytes each for a total file size of 600 bytes. Information below is arranged by the byte's hex offset, in bold.

00: Alien race:
00 = Unused entry
01 = Sectoid
02 = Snakeman
03 = Etherial
04 = Muton
05 = Floater
06 = Cellatid
07 = Silacoid
08 = Chryssalid
09 = Reaper
0A = Sectopod
0B = Cyberdisk

Once an alien is researched, its entry is erased by setting its race to 00.

01: Rank:
01 = Commander
02 = Leader
03 = Engineer
04 = Medic
05 = Navigator
06 = Soldier
07 = Terrorist

02: Base at which the alien is imprisoned, using index values from [[LOC.DAT]], your original base is always 00.
A value of FF indicates that the alien is being transferred.

03-0B: It is unclear what, if anything, these values do. 0B gets set to 01 when an alien is in transit
(this is in addition to setting the Base byte to FF). There is an intermediate value of 02 when an alien is selected for transfer but the "TRANSFER" button has not been clicked yet. Otherwise, these bytes tend to remain 00.

== For TFTD ==

Note: TFTD v2 expanded ASTORE.DAT to 3600 bytes (300 entries of 12 bytes each), with the same format. Attempting to load a v2 or later saved game into the v1 version of TFTD will cause it to crash unless this file is truncated back to 600 bytes. Loading a v1 version of this file into a v2 or later version of the game will not cause any problems.

ASTORE.DAT
1st BYTE Alien type
01h Aquatoid
02h Gill Man
03h Lobster Man
04h Tasoth
05h Calcinite
06h Deep One
07h Bio-Drone
08h Tentaculat
09h Triscene
0Ah Hallucinoid
0Bh Xarquid

2nd BYTE Alien class
01h Commander
02h Navigator
03h Medic
04h Technician
05h Squad Leader
06h Soldier
07h Terrorist

These values define the alive aliens that we have in the base. The two values (one for the type and one for the class) must be entered in the first two bytes of the file. After the project has started or the aliens have been transferred to another base, the first byte will be 0. You can re-enter a new value to have other aliens.

==See Also==
* [[TRANSFER.DAT]] - Can contain information on Captured aliens in transit
* [[Saved Game Files]]
[[Category:Game Files]]
[[Category:Game Files (TFTD)]]
[[Category:Enemy Unknown/UFO Defense]]

PURCHASE.DAT (TFTD)

2016-03-21T14:31:20Z

Morgan525: /* Structure */

== Structure ==

'''0 (1 Byte):''' Item Category:
0 General Item...basically, anything not Personnel or Subs
1 X-Com Craft
2 Soldier
3 Scientist
4 Technician

'''1 (1 Byte):''' Index to an array of the amount of inventory space used, (see [[#Notes on Sorting|Notes on Sorting]] below). For General Items (Item Category=0), this value ''perhaps'' controls the sort order on the Base Information Stores screen (only General Items appear there). Or more likely, the Stores listing just shares a common index order with the array of inventory space used.
00-42 'Human' Items...all purchaseable equipment, all Craft weapons/ammo, all HWPs, Gauss,
Particle Distrubance Sensor, Medikit, etc.
43-45 Vibroblade, Thermic Lance, Heavy Thermic Lance
46-48 Unused
49-59 Alien Weapons/Ammo...Sonic Cannon through Sonic Pulsar
60-61 Zrbite & M.C.Reader ...Alien Non-Weapon items that can be picked up in Battlescape?
62-64 Gauss Cannon clip, Gauss Rifle clip, Gauss Pistol Clip
65-75 Alien Corpses
76-79 Not Used
80-89 Alien Items...Ion Beam Accelerator through Reanimation Zone
90-92 Armor...Plastic Aqua Armor, Ion Armor, Magnetic Ion Armor
93-96 HWP Ammo...SWS Harpoon Bolts, SWS Missiles, SWS PWT Torpedoes, SWS Gauss Ammo
97 Unused
For Personnel, this value is '0', while for subs, it indicates Sub Type:
0 Triton
1 Hammerhead
2 Levaithan
3 Barracuda
4 Manta

'''2-5 (4 Bytes):''' These four bytes are set to [E8 03 00 00] (=1000) for all entries except manufactured subs

'''6-9 (4 Bytes):''' Item Cost (buy price) if Purchaseable. Curiously, starting with entry 56 (Heavy Plasma Clip), set to [E8 03 00] (=1000) for the remainder of entries (none of which is normally purchaseable.)

'''0A-0D (4 Bytes):''' Item Selling Price.

'''0E (1 Byte):''' Transfer time for new purchases, in hours. All items have this value, even manufacture-only and alien items, and it is usually a multiple of 24 (=1 day):
96 for most Subs, HWPs, and Craft Cannon Rounds
72 for Triton and Personnel hires
48 for Craft Weapons and Ammo (ex. Gas Cannon Rounds), HWP Ammo, and non-Battlescape Alien Items
32 for Alien Corpses and X-Com Armor
24 for everything else

'''0F:''' Set to 00 (0) for all entries. Possible high bit for transfer time.

'''10:''' Usually set to 0, but seems to hold the quantity purchased last time (i.e. will be set to 5 on grenades if you just bought 5 of them). Unsure when this gets cleared, and unsure why it is saved. Probably because they just used the same structure as in the Purchase screen in saving this file.

'''11:''' Appears to always be set to 00. Possible high bit for offset 10.

'''12 (1 Byte):''' Purchase-ability flag: 1 for everything that you can buy on the Purchase/Recruit screen, 0 for everything else

'''13 (1 Byte):''' Set to [00] (0) for all entries

'''00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 Item Index Num'''
02 00 E8 03 00 00 40 9C 00 00 00 00 00 00 48 00 00 00 01 00 soldier 00
03 00 E8 03 00 00 60 EA 00 00 00 00 00 00 48 00 00 00 01 00 scientist 01
04 00 E8 03 00 00 50 C3 00 00 00 00 00 00 48 00 00 00 01 00 technician 02
01 00 E8 03 00 00 20 A1 07 00 00 00 00 00 48 00 00 00 01 00 Triton 03
01 01 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Hammerhead 04
01 02 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Levaithan 05
01 03 E8 03 00 00 C0 27 09 00 00 00 00 00 60 00 00 00 01 00 Barracuda 06
01 04 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Manta 07
00 00 E8 03 00 00 80 3E 00 00 E0 2E 00 00 30 00 00 00 01 00 Ajax launcher 08
00 01 E8 03 00 00 68 42 00 00 CE 31 00 00 30 00 00 00 01 00 DUP launcher 09
00 02 E8 03 00 00 30 75 00 00 E4 57 00 00 30 00 00 00 01 00 Craft Gas Cannon 0A
00 03 E8 03 00 00 00 00 00 00 0C 4A 04 00 30 00 00 00 00 00 PWT Cannon 0B
00 04 E8 03 00 00 00 00 00 00 38 38 03 00 30 00 00 00 00 00 Gauss Cannon 0C
00 05 E8 03 00 00 00 00 00 00 24 14 04 00 30 00 00 00 00 00 Sonic Osillator 0D
00 06 E8 03 00 00 B8 0B 00 00 60 09 00 00 30 00 00 00 01 00 Ajax torpedoes 0E
00 07 E8 03 00 00 28 23 00 00 20 1C 00 00 30 00 00 00 01 00 DUP torpedoes 0F
00 08 E8 03 00 00 D8 04 00 00 F4 03 00 00 60 00 00 00 01 00 Gas Rounds(x50) 10
00 09 E8 03 00 00 00 00 00 00 84 42 00 00 30 00 00 00 00 00 PWT ammo 11
00 61 E8 03 00 00 00 00 00 00 34 D0 00 00 30 00 00 00 00 00 Craft Gauss Ammo(unused) 12
00 0A E8 03 00 00 A0 68 06 00 20 30 05 00 60 00 00 00 01 00 Tank/harpoon 13
00 5D E8 03 00 00 C8 00 00 00 64 00 00 00 30 00 00 00 01 00 SWS harpoon 14
00 0B E8 03 00 00 00 53 07 00 40 7E 05 00 60 00 00 00 01 00 Tank/Torpedo 15
00 5E E8 03 00 00 B8 0B 00 00 CA 08 00 00 30 00 00 00 01 00 SWS torpedoes 16
00 0C E8 03 00 00 00 00 00 00 50 10 09 00 60 00 00 00 00 00 Tank/Gauss 17
00 60 E8 03 00 00 B8 0B 00 00 C8 00 00 00 30 00 00 00 00 00 SWS Gauss Ammo 18
00 0D E8 03 00 00 00 00 00 00 20 F4 0E 00 60 00 00 00 00 00 Displacer/sonic 19
00 0E E8 03 00 00 00 00 00 00 38 EA 0F 00 60 00 00 00 00 00 Displacer/PWT 1A
00 5F E8 03 00 00 00 00 00 00 D0 E8 00 00 30 00 00 00 00 00 SWS PWT ammo 1B
00 0F E8 03 00 00 20 03 00 00 58 02 00 00 18 00 00 00 01 00 dart gun 1C
00 10 E8 03 00 00 46 00 00 00 34 00 00 00 18 00 00 00 01 00 dart clip 1D
00 11 E8 03 00 00 B8 0B 00 00 CA 08 00 00 18 00 00 00 01 00 jet harpoon 1E
00 12 E8 03 00 00 C8 00 00 00 96 00 00 00 18 00 00 00 01 00 harpoon clip 1F
00 13 E8 03 00 00 00 19 00 00 C0 12 00 00 18 00 00 00 01 00 Gas Cannon 20
00 14 E8 03 00 00 2C 01 00 00 E1 00 00 00 18 00 00 00 01 00 GC-AP 21
00 15 E8 03 00 00 F4 01 00 00 13 01 00 00 18 00 00 00 01 00 GC-HE 22
00 16 E8 03 00 00 90 01 00 00 2C 01 00 00 18 00 00 00 01 00 GC-IN 23
00 17 E8 03 00 00 BC 34 00 00 8D 27 00 00 18 00 00 00 01 00 Hydro-Jet Cannon 24
00 18 E8 03 00 00 F4 01 00 00 90 01 00 00 18 00 00 00 01 00 HJ-AP 25
00 19 E8 03 00 00 BC 02 00 00 30 02 00 00 18 00 00 00 01 00 HJ-HE 26
00 1A E8 03 00 00 8A 02 00 00 08 02 00 00 18 00 00 00 01 00 HJ-IN 27
00 1B E8 03 00 00 A0 0F 00 00 B8 0B 00 00 18 00 00 00 01 00 Torpedo Launcher 28
00 1C E8 03 00 00 58 02 00 00 E0 01 00 00 18 00 00 00 01 00 Small Torpedo 29
00 1D E8 03 00 00 84 03 00 00 D0 02 00 00 18 00 00 00 01 00 Large Torpedo 2A
00 1E E8 03 00 00 B0 04 00 00 C0 03 00 00 18 00 00 00 01 00 IN Torpedo 2B
00 1F E8 03 00 00 00 00 00 00 20 4E 00 00 18 00 00 00 00 00 Gauss Pistol 2C
00 3E E8 03 00 00 00 00 00 00 1A 04 00 00 18 00 00 00 00 00 G.Pistol Clip 2D
00 20 E8 03 00 00 00 00 00 00 24 90 00 00 18 00 00 00 00 00 Gauss Rifle 2E
00 3F E8 03 00 00 00 00 00 00 9E 07 00 00 18 00 00 00 00 00 G.Rifle clip 2F
00 21 E8 03 00 00 00 00 00 00 48 EE 00 00 18 00 00 00 00 00 Gauss Cannon 30
00 40 E8 03 00 00 00 00 00 00 94 0C 00 00 18 00 00 00 00 00 G. Cannon clip 31
00 22 E8 03 00 00 2C 01 00 00 F0 00 00 00 18 00 00 00 01 00 Magna grenade 32
00 23 E8 03 00 00 96 00 00 00 78 00 00 00 18 00 00 00 01 00 Dye grenade 33
00 24 E8 03 00 00 F4 01 00 00 90 01 00 00 18 00 00 00 01 00 Particle D grenade 34
00 25 E8 03 00 00 DC 05 00 00 B0 04 00 00 18 00 00 00 01 00 Magna-Pak Explosive 35
00 26 E8 03 00 00 00 00 00 00 20 B2 00 00 18 00 00 00 00 00 Particle D sensor 36
00 27 E8 03 00 00 00 00 00 00 A4 B5 00 00 18 00 00 00 00 00 Medi-kit 37
00 28 E8 03 00 00 00 00 00 00 8C F8 02 00 18 00 00 00 00 00 MC-Disruptor 38
00 29 E8 03 00 00 EC 04 00 00 B1 03 00 00 18 00 00 00 01 00 Thermal Tazer 39
00 2A E8 03 00 00 3C 00 00 00 28 00 00 00 18 00 00 00 01 00 flare 3A
00 3C E8 03 00 00 00 00 00 00 88 13 00 00 18 00 00 00 00 00 Zrbite 3B
00 31 E8 03 00 00 00 00 00 00 50 9E 02 00 18 00 00 00 00 00 Sonic Cannon 3C
00 32 E8 03 00 00 E8 03 00 00 76 25 00 00 18 00 00 00 00 00 S.Cannon clip 3D
00 33 E8 03 00 00 E8 03 00 00 24 EE 01 00 18 00 00 00 00 00 Sonic rifle 3E
00 34 E8 03 00 00 E8 03 00 00 92 18 00 00 18 00 00 00 00 00 S.rifle clip 3F
00 35 E8 03 00 00 E8 03 00 00 20 48 01 00 18 00 00 00 00 00 Sonic Pistol 40
00 36 E8 03 00 00 E8 03 00 00 58 11 00 00 18 00 00 00 00 00 S.Pistol clip 41
00 37 E8 03 00 00 E8 03 00 00 80 32 02 00 18 00 00 00 00 00 Disruptor Pulse Launcher 42
00 38 E8 03 00 00 E8 03 00 00 A8 93 00 00 18 00 00 00 00 00 Disruptor ammo 43
00 39 E8 03 00 00 E8 03 00 00 C0 D4 01 00 18 00 00 00 00 00 Thermal Shock Launcher 44
00 3A E8 03 00 00 E8 03 00 00 60 3B 00 00 18 00 00 00 00 00 Thermal Shock Ammo 45
00 3B E8 03 00 00 E8 03 00 00 02 3A 00 00 18 00 00 00 00 00 Sonic Pulsar 46
00 3D E8 03 00 00 E8 03 00 00 80 A3 04 00 18 00 00 00 00 00 M.C.reader 47
00 2B E8 03 00 00 E8 03 00 00 DC 05 00 00 18 00 00 00 00 00 Vibro blade 48
00 2C E8 03 00 00 E8 03 00 00 08 07 00 00 18 00 00 00 00 00 Thermic Lance 49
00 2D E8 03 00 00 E8 03 00 00 D0 07 00 00 18 00 00 00 00 00 Heavy Lance 4A
00 41 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4B
00 42 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4C
00 43 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4D
00 44 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4E
00 45 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4F
00 46 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 50
00 47 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 51
00 48 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 52
00 49 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 53
00 4A E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 54
00 4B E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 55
00 50 E8 03 00 00 E8 03 00 00 90 D0 03 00 30 00 00 00 00 00 Ion-Beam Accelerator 56
00 51 E8 03 00 00 E8 03 00 00 80 38 01 00 30 00 00 00 00 00 Magnetic Navigation 57
00 52 E8 03 00 00 E8 03 00 00 20 4E 00 00 30 00 00 00 00 00 Sub Construction 58
00 53 E8 03 00 00 E8 03 00 00 88 13 00 00 30 00 00 00 00 00 Cryogenics 59
00 54 E8 03 00 00 E8 03 00 00 40 9C 00 00 30 00 00 00 00 00 cloning 5A
00 55 E8 03 00 00 E8 03 00 00 20 4E 00 00 30 00 00 00 00 00 learning arrays 5B
00 56 E8 03 00 00 E8 03 00 00 70 94 00 00 30 00 00 00 00 00 Implanter 5C
00 57 E8 03 00 00 E8 03 00 00 28 23 00 00 30 00 00 00 00 00 Examination Room 5D
00 58 E8 03 00 00 E8 03 00 00 64 19 00 00 30 00 00 00 00 00 Aqua Plastics 5E
00 59 E8 03 00 00 E8 03 00 00 64 00 00 00 30 00 00 00 00 00 Re-Animation zone 5F
00 5A E8 03 00 00 E8 03 00 00 F0 D2 00 00 20 00 00 00 00 00 Plastic Armor 60
00 5B E8 03 00 00 E8 03 00 00 08 4C 01 00 20 00 00 00 00 00 Ion Armor 61
00 5C E8 03 00 00 E8 03 00 00 38 C1 01 00 20 00 00 00 00 00 Mag. Ion Armor 62

PURCHASE.DAT (TFTD)

2016-03-21T14:30:30Z

Morgan525: /* Structure */ changed byte reference numbers to Hex

== Structure ==

'''0 (1 Byte):''' Item Category:
0 General Item...basically, anything not Personnel or Subs
1 X-Com Craft
2 Soldier
3 Scientist
4 Technician

'''1 (1 Byte):''' Index to an array of the amount of inventory space used, (see [[#Notes on Sorting|Notes on Sorting]] below). For General Items (Item Category=0), this value ''perhaps'' controls the sort order on the Base Information Stores screen (only General Items appear there). Or more likely, the Stores listing just shares a common index order with the array of inventory space used.
00-42 'Human' Items...all purchaseable equipment, all Craft weapons/ammo, all HWPs, Gauss,
Particle Distrubance Sensor, Medikit, etc.
43-45 Vibroblade, Thermic Lance, Heavy Thermic Lance
46-48 Unused
49-59 Alien Weapons/Ammo...Sonic Cannon through Sonic Pulsar
60-61 Zrbite & M.C.Reader ...Alien Non-Weapon items that can be picked up in Battlescape?
62-64 Gauss Cannon clip, Gauss Rifle clip, Gauss Pistol Clip
65-75 Alien Corpses
76-79 Not Used
80-89 Alien Items...Ion Beam Accelerator through Reanimation Zone
90-92 Armor...Plastic Aqua Armor, Ion Armor, Magnetic Ion Armor
93-96 HWP Ammo...SWS Harpoon Bolts, SWS Missiles, SWS PWT Torpedoes, SWS Gauss Ammo
97 Unused
For Personnel, this value is '0', while for subs, it indicates Sub Type:
0 Triton
1 Hammerhead
2 Levaithan
3 Barracuda
4 Manta

'''2-5 (4 Bytes):''' These four bytes are set to [E8 03 00 00] (=1000) for all entries except manufactured subs

'''6-9 (4 Bytes):''' Item Cost (buy price) if Purchaseable. Curiously, starting with entry 56 (Heavy Plasma Clip), set to [E8 03 00] (=1000) for the remainder of entries (none of which is normally purchaseable.)

'''0A-0D (4 Bytes):''' Item Selling Price.

'''0E (1 Byte):''' Transfer time for new purchases, in hours. All items have this value, even manufacture-only and alien items, and it is usually a multiple of 24 (=1 day):
96 for most Subs, HWPs, and Craft Cannon Rounds
72 for Triton and Personnel hires
48 for Craft Weapons and Ammo (ex. Gas Cannon Rounds), HWP Ammo, and non-Battlescape Alien Items
32 for Alien Corpses and X-Com Armor
24 for everything else

'''0F:''' Set to 00 (0) for all entries. Possible high bit for transfer time.

'''10:''' Usually set to 0, but seems to hold the quantity purchased last time (i.e. will be set to 5 on grenades if you just bought 5 of them). Unsure when this gets cleared, and unsure why it is saved. Probably because they just used the same structure as in the Purchase screen in saving this file.

'''11:''' Appears to always be set to 00. Possible high bit for offset 16.

'''12 (1 Byte):''' Purchase-ability flag: 1 for everything that you can buy on the Purchase/Recruit screen, 0 for everything else

'''13 (1 Byte):''' Set to [00] (0) for all entries

'''00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 Item Index Num'''
02 00 E8 03 00 00 40 9C 00 00 00 00 00 00 48 00 00 00 01 00 soldier 00
03 00 E8 03 00 00 60 EA 00 00 00 00 00 00 48 00 00 00 01 00 scientist 01
04 00 E8 03 00 00 50 C3 00 00 00 00 00 00 48 00 00 00 01 00 technician 02
01 00 E8 03 00 00 20 A1 07 00 00 00 00 00 48 00 00 00 01 00 Triton 03
01 01 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Hammerhead 04
01 02 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Levaithan 05
01 03 E8 03 00 00 C0 27 09 00 00 00 00 00 60 00 00 00 01 00 Barracuda 06
01 04 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Manta 07
00 00 E8 03 00 00 80 3E 00 00 E0 2E 00 00 30 00 00 00 01 00 Ajax launcher 08
00 01 E8 03 00 00 68 42 00 00 CE 31 00 00 30 00 00 00 01 00 DUP launcher 09
00 02 E8 03 00 00 30 75 00 00 E4 57 00 00 30 00 00 00 01 00 Craft Gas Cannon 0A
00 03 E8 03 00 00 00 00 00 00 0C 4A 04 00 30 00 00 00 00 00 PWT Cannon 0B
00 04 E8 03 00 00 00 00 00 00 38 38 03 00 30 00 00 00 00 00 Gauss Cannon 0C
00 05 E8 03 00 00 00 00 00 00 24 14 04 00 30 00 00 00 00 00 Sonic Osillator 0D
00 06 E8 03 00 00 B8 0B 00 00 60 09 00 00 30 00 00 00 01 00 Ajax torpedoes 0E
00 07 E8 03 00 00 28 23 00 00 20 1C 00 00 30 00 00 00 01 00 DUP torpedoes 0F
00 08 E8 03 00 00 D8 04 00 00 F4 03 00 00 60 00 00 00 01 00 Gas Rounds(x50) 10
00 09 E8 03 00 00 00 00 00 00 84 42 00 00 30 00 00 00 00 00 PWT ammo 11
00 61 E8 03 00 00 00 00 00 00 34 D0 00 00 30 00 00 00 00 00 Craft Gauss Ammo(unused) 12
00 0A E8 03 00 00 A0 68 06 00 20 30 05 00 60 00 00 00 01 00 Tank/harpoon 13
00 5D E8 03 00 00 C8 00 00 00 64 00 00 00 30 00 00 00 01 00 SWS harpoon 14
00 0B E8 03 00 00 00 53 07 00 40 7E 05 00 60 00 00 00 01 00 Tank/Torpedo 15
00 5E E8 03 00 00 B8 0B 00 00 CA 08 00 00 30 00 00 00 01 00 SWS torpedoes 16
00 0C E8 03 00 00 00 00 00 00 50 10 09 00 60 00 00 00 00 00 Tank/Gauss 17
00 60 E8 03 00 00 B8 0B 00 00 C8 00 00 00 30 00 00 00 00 00 SWS Gauss Ammo 18
00 0D E8 03 00 00 00 00 00 00 20 F4 0E 00 60 00 00 00 00 00 Displacer/sonic 19
00 0E E8 03 00 00 00 00 00 00 38 EA 0F 00 60 00 00 00 00 00 Displacer/PWT 1A
00 5F E8 03 00 00 00 00 00 00 D0 E8 00 00 30 00 00 00 00 00 SWS PWT ammo 1B
00 0F E8 03 00 00 20 03 00 00 58 02 00 00 18 00 00 00 01 00 dart gun 1C
00 10 E8 03 00 00 46 00 00 00 34 00 00 00 18 00 00 00 01 00 dart clip 1D
00 11 E8 03 00 00 B8 0B 00 00 CA 08 00 00 18 00 00 00 01 00 jet harpoon 1E
00 12 E8 03 00 00 C8 00 00 00 96 00 00 00 18 00 00 00 01 00 harpoon clip 1F
00 13 E8 03 00 00 00 19 00 00 C0 12 00 00 18 00 00 00 01 00 Gas Cannon 20
00 14 E8 03 00 00 2C 01 00 00 E1 00 00 00 18 00 00 00 01 00 GC-AP 21
00 15 E8 03 00 00 F4 01 00 00 13 01 00 00 18 00 00 00 01 00 GC-HE 22
00 16 E8 03 00 00 90 01 00 00 2C 01 00 00 18 00 00 00 01 00 GC-IN 23
00 17 E8 03 00 00 BC 34 00 00 8D 27 00 00 18 00 00 00 01 00 Hydro-Jet Cannon 24
00 18 E8 03 00 00 F4 01 00 00 90 01 00 00 18 00 00 00 01 00 HJ-AP 25
00 19 E8 03 00 00 BC 02 00 00 30 02 00 00 18 00 00 00 01 00 HJ-HE 26
00 1A E8 03 00 00 8A 02 00 00 08 02 00 00 18 00 00 00 01 00 HJ-IN 27
00 1B E8 03 00 00 A0 0F 00 00 B8 0B 00 00 18 00 00 00 01 00 Torpedo Launcher 28
00 1C E8 03 00 00 58 02 00 00 E0 01 00 00 18 00 00 00 01 00 Small Torpedo 29
00 1D E8 03 00 00 84 03 00 00 D0 02 00 00 18 00 00 00 01 00 Large Torpedo 2A
00 1E E8 03 00 00 B0 04 00 00 C0 03 00 00 18 00 00 00 01 00 IN Torpedo 2B
00 1F E8 03 00 00 00 00 00 00 20 4E 00 00 18 00 00 00 00 00 Gauss Pistol 2C
00 3E E8 03 00 00 00 00 00 00 1A 04 00 00 18 00 00 00 00 00 G.Pistol Clip 2D
00 20 E8 03 00 00 00 00 00 00 24 90 00 00 18 00 00 00 00 00 Gauss Rifle 2E
00 3F E8 03 00 00 00 00 00 00 9E 07 00 00 18 00 00 00 00 00 G.Rifle clip 2F
00 21 E8 03 00 00 00 00 00 00 48 EE 00 00 18 00 00 00 00 00 Gauss Cannon 30
00 40 E8 03 00 00 00 00 00 00 94 0C 00 00 18 00 00 00 00 00 G. Cannon clip 31
00 22 E8 03 00 00 2C 01 00 00 F0 00 00 00 18 00 00 00 01 00 Magna grenade 32
00 23 E8 03 00 00 96 00 00 00 78 00 00 00 18 00 00 00 01 00 Dye grenade 33
00 24 E8 03 00 00 F4 01 00 00 90 01 00 00 18 00 00 00 01 00 Particle D grenade 34
00 25 E8 03 00 00 DC 05 00 00 B0 04 00 00 18 00 00 00 01 00 Magna-Pak Explosive 35
00 26 E8 03 00 00 00 00 00 00 20 B2 00 00 18 00 00 00 00 00 Particle D sensor 36
00 27 E8 03 00 00 00 00 00 00 A4 B5 00 00 18 00 00 00 00 00 Medi-kit 37
00 28 E8 03 00 00 00 00 00 00 8C F8 02 00 18 00 00 00 00 00 MC-Disruptor 38
00 29 E8 03 00 00 EC 04 00 00 B1 03 00 00 18 00 00 00 01 00 Thermal Tazer 39
00 2A E8 03 00 00 3C 00 00 00 28 00 00 00 18 00 00 00 01 00 flare 3A
00 3C E8 03 00 00 00 00 00 00 88 13 00 00 18 00 00 00 00 00 Zrbite 3B
00 31 E8 03 00 00 00 00 00 00 50 9E 02 00 18 00 00 00 00 00 Sonic Cannon 3C
00 32 E8 03 00 00 E8 03 00 00 76 25 00 00 18 00 00 00 00 00 S.Cannon clip 3D
00 33 E8 03 00 00 E8 03 00 00 24 EE 01 00 18 00 00 00 00 00 Sonic rifle 3E
00 34 E8 03 00 00 E8 03 00 00 92 18 00 00 18 00 00 00 00 00 S.rifle clip 3F
00 35 E8 03 00 00 E8 03 00 00 20 48 01 00 18 00 00 00 00 00 Sonic Pistol 40
00 36 E8 03 00 00 E8 03 00 00 58 11 00 00 18 00 00 00 00 00 S.Pistol clip 41
00 37 E8 03 00 00 E8 03 00 00 80 32 02 00 18 00 00 00 00 00 Disruptor Pulse Launcher 42
00 38 E8 03 00 00 E8 03 00 00 A8 93 00 00 18 00 00 00 00 00 Disruptor ammo 43
00 39 E8 03 00 00 E8 03 00 00 C0 D4 01 00 18 00 00 00 00 00 Thermal Shock Launcher 44
00 3A E8 03 00 00 E8 03 00 00 60 3B 00 00 18 00 00 00 00 00 Thermal Shock Ammo 45
00 3B E8 03 00 00 E8 03 00 00 02 3A 00 00 18 00 00 00 00 00 Sonic Pulsar 46
00 3D E8 03 00 00 E8 03 00 00 80 A3 04 00 18 00 00 00 00 00 M.C.reader 47
00 2B E8 03 00 00 E8 03 00 00 DC 05 00 00 18 00 00 00 00 00 Vibro blade 48
00 2C E8 03 00 00 E8 03 00 00 08 07 00 00 18 00 00 00 00 00 Thermic Lance 49
00 2D E8 03 00 00 E8 03 00 00 D0 07 00 00 18 00 00 00 00 00 Heavy Lance 4A
00 41 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4B
00 42 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4C
00 43 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4D
00 44 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4E
00 45 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4F
00 46 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 50
00 47 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 51
00 48 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 52
00 49 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 53
00 4A E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 54
00 4B E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 55
00 50 E8 03 00 00 E8 03 00 00 90 D0 03 00 30 00 00 00 00 00 Ion-Beam Accelerator 56
00 51 E8 03 00 00 E8 03 00 00 80 38 01 00 30 00 00 00 00 00 Magnetic Navigation 57
00 52 E8 03 00 00 E8 03 00 00 20 4E 00 00 30 00 00 00 00 00 Sub Construction 58
00 53 E8 03 00 00 E8 03 00 00 88 13 00 00 30 00 00 00 00 00 Cryogenics 59
00 54 E8 03 00 00 E8 03 00 00 40 9C 00 00 30 00 00 00 00 00 cloning 5A
00 55 E8 03 00 00 E8 03 00 00 20 4E 00 00 30 00 00 00 00 00 learning arrays 5B
00 56 E8 03 00 00 E8 03 00 00 70 94 00 00 30 00 00 00 00 00 Implanter 5C
00 57 E8 03 00 00 E8 03 00 00 28 23 00 00 30 00 00 00 00 00 Examination Room 5D
00 58 E8 03 00 00 E8 03 00 00 64 19 00 00 30 00 00 00 00 00 Aqua Plastics 5E
00 59 E8 03 00 00 E8 03 00 00 64 00 00 00 30 00 00 00 00 00 Re-Animation zone 5F
00 5A E8 03 00 00 E8 03 00 00 F0 D2 00 00 20 00 00 00 00 00 Plastic Armor 60
00 5B E8 03 00 00 E8 03 00 00 08 4C 01 00 20 00 00 00 00 00 Ion Armor 61
00 5C E8 03 00 00 E8 03 00 00 38 C1 01 00 20 00 00 00 00 00 Mag. Ion Armor 62

PURCHASE.DAT (TFTD)

2016-03-21T14:28:17Z

Morgan525: added and updated structure information for TFTD

== Structure ==

'''0 (1 Byte):''' Item Category:
0 General Item...basically, anything not Personnel or Subs
1 X-Com Craft
2 Soldier
3 Scientist
4 Technician

'''1 (1 Byte):''' Index to an array of the amount of inventory space used, (see [[#Notes on Sorting|Notes on Sorting]] below). For General Items (Item Category=0), this value ''perhaps'' controls the sort order on the Base Information Stores screen (only General Items appear there). Or more likely, the Stores listing just shares a common index order with the array of inventory space used.
00-42 'Human' Items...all purchaseable equipment, all Craft weapons/ammo, all HWPs, Gauss,
Particle Distrubance Sensor, Medikit, etc.
43-45 Vibroblade, Thermic Lance, Heavy Thermic Lance
46-48 Unused
49-59 Alien Weapons/Ammo...Sonic Cannon through Sonic Pulsar
60-61 Zrbite & M.C.Reader ...Alien Non-Weapon items that can be picked up in Battlescape?
62-64 Gauss Cannon clip, Gauss Rifle clip, Gauss Pistol Clip
65-75 Alien Corpses
76-79 Not Used
80-89 Alien Items...Ion Beam Accelerator through Reanimation Zone
90-92 Armor...Plastic Aqua Armor, Ion Armor, Magnetic Ion Armor
93-96 HWP Ammo...SWS Harpoon Bolts, SWS Missiles, SWS PWT Torpedoes, SWS Gauss Ammo
97 Unused
For Personnel, this value is '0', while for subs, it indicates Sub Type:
0 Triton
1 Hammerhead
2 Levaithan
3 Barracuda
4 Manta

'''2-5 (4 Bytes):''' These four bytes are set to [E8 03 00 00] (=1000) for all entries except manufactured subs

'''6-9 (4 Bytes):''' Item Cost (buy price) if Purchaseable. Curiously, starting with entry 56 (Heavy Plasma Clip), set to [E8 03 00] (=1000) for the remainder of entries (none of which is normally purchaseable.)

'''10-13 (4 Bytes):''' Item Selling Price.

'''14 (1 Byte):''' Transfer time for new purchases, in hours. All items have this value, even manufacture-only and alien items, and it is usually a multiple of 24 (=1 day):
96 for most Subs, HWPs, and Craft Cannon Rounds
72 for Triton and Personnel hires
48 for Craft Weapons and Ammo (ex. Gas Cannon Rounds), HWP Ammo, and non-Battlescape Alien Items
32 for Alien Corpses and X-Com Armor
24 for everything else

'''15:''' Set to 00 (0) for all entries. Possible high bit for transfer time.

'''16:''' Usually set to 0, but seems to hold the quantity purchased last time (i.e. will be set to 5 on grenades if you just bought 5 of them). Unsure when this gets cleared, and unsure why it is saved. Probably because they just used the same structure as in the Purchase screen in saving this file.

'''17:''' Appears to always be set to 00. Possible high bit for offset 16.

'''18 (1 Byte):''' Purchase-ability flag: 1 for everything that you can buy on the Purchase/Recruit screen, 0 for everything else

'''19 (1 Byte):''' Set to [00] (0) for all entries

'''00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 Item Index Num'''
02 00 E8 03 00 00 40 9C 00 00 00 00 00 00 48 00 00 00 01 00 soldier 00
03 00 E8 03 00 00 60 EA 00 00 00 00 00 00 48 00 00 00 01 00 scientist 01
04 00 E8 03 00 00 50 C3 00 00 00 00 00 00 48 00 00 00 01 00 technician 02
01 00 E8 03 00 00 20 A1 07 00 00 00 00 00 48 00 00 00 01 00 Triton 03
01 01 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Hammerhead 04
01 02 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Levaithan 05
01 03 E8 03 00 00 C0 27 09 00 00 00 00 00 60 00 00 00 01 00 Barracuda 06
01 04 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Manta 07
00 00 E8 03 00 00 80 3E 00 00 E0 2E 00 00 30 00 00 00 01 00 Ajax launcher 08
00 01 E8 03 00 00 68 42 00 00 CE 31 00 00 30 00 00 00 01 00 DUP launcher 09
00 02 E8 03 00 00 30 75 00 00 E4 57 00 00 30 00 00 00 01 00 Craft Gas Cannon 0A
00 03 E8 03 00 00 00 00 00 00 0C 4A 04 00 30 00 00 00 00 00 PWT Cannon 0B
00 04 E8 03 00 00 00 00 00 00 38 38 03 00 30 00 00 00 00 00 Gauss Cannon 0C
00 05 E8 03 00 00 00 00 00 00 24 14 04 00 30 00 00 00 00 00 Sonic Osillator 0D
00 06 E8 03 00 00 B8 0B 00 00 60 09 00 00 30 00 00 00 01 00 Ajax torpedoes 0E
00 07 E8 03 00 00 28 23 00 00 20 1C 00 00 30 00 00 00 01 00 DUP torpedoes 0F
00 08 E8 03 00 00 D8 04 00 00 F4 03 00 00 60 00 00 00 01 00 Gas Rounds(x50) 10
00 09 E8 03 00 00 00 00 00 00 84 42 00 00 30 00 00 00 00 00 PWT ammo 11
00 61 E8 03 00 00 00 00 00 00 34 D0 00 00 30 00 00 00 00 00 Craft Gauss Ammo(unused) 12
00 0A E8 03 00 00 A0 68 06 00 20 30 05 00 60 00 00 00 01 00 Tank/harpoon 13
00 5D E8 03 00 00 C8 00 00 00 64 00 00 00 30 00 00 00 01 00 SWS harpoon 14
00 0B E8 03 00 00 00 53 07 00 40 7E 05 00 60 00 00 00 01 00 Tank/Torpedo 15
00 5E E8 03 00 00 B8 0B 00 00 CA 08 00 00 30 00 00 00 01 00 SWS torpedoes 16
00 0C E8 03 00 00 00 00 00 00 50 10 09 00 60 00 00 00 00 00 Tank/Gauss 17
00 60 E8 03 00 00 B8 0B 00 00 C8 00 00 00 30 00 00 00 00 00 SWS Gauss Ammo 18
00 0D E8 03 00 00 00 00 00 00 20 F4 0E 00 60 00 00 00 00 00 Displacer/sonic 19
00 0E E8 03 00 00 00 00 00 00 38 EA 0F 00 60 00 00 00 00 00 Displacer/PWT 1A
00 5F E8 03 00 00 00 00 00 00 D0 E8 00 00 30 00 00 00 00 00 SWS PWT ammo 1B
00 0F E8 03 00 00 20 03 00 00 58 02 00 00 18 00 00 00 01 00 dart gun 1C
00 10 E8 03 00 00 46 00 00 00 34 00 00 00 18 00 00 00 01 00 dart clip 1D
00 11 E8 03 00 00 B8 0B 00 00 CA 08 00 00 18 00 00 00 01 00 jet harpoon 1E
00 12 E8 03 00 00 C8 00 00 00 96 00 00 00 18 00 00 00 01 00 harpoon clip 1F
00 13 E8 03 00 00 00 19 00 00 C0 12 00 00 18 00 00 00 01 00 Gas Cannon 20
00 14 E8 03 00 00 2C 01 00 00 E1 00 00 00 18 00 00 00 01 00 GC-AP 21
00 15 E8 03 00 00 F4 01 00 00 13 01 00 00 18 00 00 00 01 00 GC-HE 22
00 16 E8 03 00 00 90 01 00 00 2C 01 00 00 18 00 00 00 01 00 GC-IN 23
00 17 E8 03 00 00 BC 34 00 00 8D 27 00 00 18 00 00 00 01 00 Hydro-Jet Cannon 24
00 18 E8 03 00 00 F4 01 00 00 90 01 00 00 18 00 00 00 01 00 HJ-AP 25
00 19 E8 03 00 00 BC 02 00 00 30 02 00 00 18 00 00 00 01 00 HJ-HE 26
00 1A E8 03 00 00 8A 02 00 00 08 02 00 00 18 00 00 00 01 00 HJ-IN 27
00 1B E8 03 00 00 A0 0F 00 00 B8 0B 00 00 18 00 00 00 01 00 Torpedo Launcher 28
00 1C E8 03 00 00 58 02 00 00 E0 01 00 00 18 00 00 00 01 00 Small Torpedo 29
00 1D E8 03 00 00 84 03 00 00 D0 02 00 00 18 00 00 00 01 00 Large Torpedo 2A
00 1E E8 03 00 00 B0 04 00 00 C0 03 00 00 18 00 00 00 01 00 IN Torpedo 2B
00 1F E8 03 00 00 00 00 00 00 20 4E 00 00 18 00 00 00 00 00 Gauss Pistol 2C
00 3E E8 03 00 00 00 00 00 00 1A 04 00 00 18 00 00 00 00 00 G.Pistol Clip 2D
00 20 E8 03 00 00 00 00 00 00 24 90 00 00 18 00 00 00 00 00 Gauss Rifle 2E
00 3F E8 03 00 00 00 00 00 00 9E 07 00 00 18 00 00 00 00 00 G.Rifle clip 2F
00 21 E8 03 00 00 00 00 00 00 48 EE 00 00 18 00 00 00 00 00 Gauss Cannon 30
00 40 E8 03 00 00 00 00 00 00 94 0C 00 00 18 00 00 00 00 00 G. Cannon clip 31
00 22 E8 03 00 00 2C 01 00 00 F0 00 00 00 18 00 00 00 01 00 Magna grenade 32
00 23 E8 03 00 00 96 00 00 00 78 00 00 00 18 00 00 00 01 00 Dye grenade 33
00 24 E8 03 00 00 F4 01 00 00 90 01 00 00 18 00 00 00 01 00 Particle D grenade 34
00 25 E8 03 00 00 DC 05 00 00 B0 04 00 00 18 00 00 00 01 00 Magna-Pak Explosive 35
00 26 E8 03 00 00 00 00 00 00 20 B2 00 00 18 00 00 00 00 00 Particle D sensor 36
00 27 E8 03 00 00 00 00 00 00 A4 B5 00 00 18 00 00 00 00 00 Medi-kit 37
00 28 E8 03 00 00 00 00 00 00 8C F8 02 00 18 00 00 00 00 00 MC-Disruptor 38
00 29 E8 03 00 00 EC 04 00 00 B1 03 00 00 18 00 00 00 01 00 Thermal Tazer 39
00 2A E8 03 00 00 3C 00 00 00 28 00 00 00 18 00 00 00 01 00 flare 3A
00 3C E8 03 00 00 00 00 00 00 88 13 00 00 18 00 00 00 00 00 Zrbite 3B
00 31 E8 03 00 00 00 00 00 00 50 9E 02 00 18 00 00 00 00 00 Sonic Cannon 3C
00 32 E8 03 00 00 E8 03 00 00 76 25 00 00 18 00 00 00 00 00 S.Cannon clip 3D
00 33 E8 03 00 00 E8 03 00 00 24 EE 01 00 18 00 00 00 00 00 Sonic rifle 3E
00 34 E8 03 00 00 E8 03 00 00 92 18 00 00 18 00 00 00 00 00 S.rifle clip 3F
00 35 E8 03 00 00 E8 03 00 00 20 48 01 00 18 00 00 00 00 00 Sonic Pistol 40
00 36 E8 03 00 00 E8 03 00 00 58 11 00 00 18 00 00 00 00 00 S.Pistol clip 41
00 37 E8 03 00 00 E8 03 00 00 80 32 02 00 18 00 00 00 00 00 Disruptor Pulse Launcher 42
00 38 E8 03 00 00 E8 03 00 00 A8 93 00 00 18 00 00 00 00 00 Disruptor ammo 43
00 39 E8 03 00 00 E8 03 00 00 C0 D4 01 00 18 00 00 00 00 00 Thermal Shock Launcher 44
00 3A E8 03 00 00 E8 03 00 00 60 3B 00 00 18 00 00 00 00 00 Thermal Shock Ammo 45
00 3B E8 03 00 00 E8 03 00 00 02 3A 00 00 18 00 00 00 00 00 Sonic Pulsar 46
00 3D E8 03 00 00 E8 03 00 00 80 A3 04 00 18 00 00 00 00 00 M.C.reader 47
00 2B E8 03 00 00 E8 03 00 00 DC 05 00 00 18 00 00 00 00 00 Vibro blade 48
00 2C E8 03 00 00 E8 03 00 00 08 07 00 00 18 00 00 00 00 00 Thermic Lance 49
00 2D E8 03 00 00 E8 03 00 00 D0 07 00 00 18 00 00 00 00 00 Heavy Lance 4A
00 41 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4B
00 42 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4C
00 43 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4D
00 44 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4E
00 45 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4F
00 46 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 50
00 47 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 51
00 48 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 52
00 49 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 53
00 4A E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 54
00 4B E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 55
00 50 E8 03 00 00 E8 03 00 00 90 D0 03 00 30 00 00 00 00 00 Ion-Beam Accelerator 56
00 51 E8 03 00 00 E8 03 00 00 80 38 01 00 30 00 00 00 00 00 Magnetic Navigation 57
00 52 E8 03 00 00 E8 03 00 00 20 4E 00 00 30 00 00 00 00 00 Sub Construction 58
00 53 E8 03 00 00 E8 03 00 00 88 13 00 00 30 00 00 00 00 00 Cryogenics 59
00 54 E8 03 00 00 E8 03 00 00 40 9C 00 00 30 00 00 00 00 00 cloning 5A
00 55 E8 03 00 00 E8 03 00 00 20 4E 00 00 30 00 00 00 00 00 learning arrays 5B
00 56 E8 03 00 00 E8 03 00 00 70 94 00 00 30 00 00 00 00 00 Implanter 5C
00 57 E8 03 00 00 E8 03 00 00 28 23 00 00 30 00 00 00 00 00 Examination Room 5D
00 58 E8 03 00 00 E8 03 00 00 64 19 00 00 30 00 00 00 00 00 Aqua Plastics 5E
00 59 E8 03 00 00 E8 03 00 00 64 00 00 00 30 00 00 00 00 00 Re-Animation zone 5F
00 5A E8 03 00 00 E8 03 00 00 F0 D2 00 00 20 00 00 00 00 00 Plastic Armor 60
00 5B E8 03 00 00 E8 03 00 00 08 4C 01 00 20 00 00 00 00 00 Ion Armor 61
00 5C E8 03 00 00 E8 03 00 00 38 C1 01 00 20 00 00 00 00 00 Mag. Ion Armor 62

Game Files

2016-03-21T14:06:08Z

Morgan525: /* Geoscape Files */

Not-for-profit, just-for-fun reverse engineering.

* General note re: [[HackerTools|Hex editing game files]]
:Contains a quick introduction to using a most unlikely program to edit your game files, and suggestions on other editors out there.
* A primer for the [[Command Prompt]] (aka the command console).
:Information on how to manage directories, files, plus other neat tricks that can be done through the command console that should not be forgotten in today's era of point and click madness.

[http://www.stonepool.com/xcom/hacking/index.html Hatfarm / Chris Voss] and [http://www.daishiva.com/phpBB2/generic.php?page=progLinks.shtml DaiShiva] (see [http://www.daishiva.com/programs/XCFormat.html file formats]) also have notes on a number of XCOM's file formats not yet detailed on this wiki.

= General File Information =
== Program Files ==

These are program files and static data files that are not part of the saved game files.

<table {{StdDescTable}}>
<th {{StdDescTable_Heading}}>File</th><th {{StdDescTable_Heading}}>Description</th>
<tr><td>[[GEODATA]]</td><td>Geoscape data. Includes localization strings, [[OBDATA.DAT]] for objects like weapons, [[WORLD.DAT]] for globe terrain.</td></tr>
<tr><td>[[GEOGRAPH]]</td><td>Graphics for [[UFOpaedia]] and research screen backgrounds.</td></tr>
<tr><td>[[MAPS]]</td><td>Pre-generated Battlescape terrain blocks (.MAP). These are filled in with terrain tiles. A few dozen blocks make up a battlescape.</td></tr>
<tr><td>[[Saved_Game_Files#Missdat_Files|MISSDAT]]</td><td>Holds the data from the previous mission. (Can be [[ExploitsA#Score_Points_For_Free|exploited]]).</td></tr>
<tr><td>[[ROUTES]]</td><td>Alien route maps (.RMP) for moving around the pre-generated Battlescape terrain blocks.</td></tr>
<tr><td>[[SOUND]]</td><td>1990-era sound drivers, or MIDI files for Windows version.</td></tr>
<tr><td>[[TERRAIN]]</td><td>Battlescape graphic tiles for buildings, ships, and terrain (.MCD, .PCK, and .TAB).</td></tr>
<tr><td>UFO2EXE\[[TACTICAL.EXE]]</td><td>The "Battlescape" program in DOS-release of UFO.</td></tr>
<tr><td>UFOEXE\[[GEOSCAPE.EXE]]</td><td>The "Geoscape" program that handles base management and aircraft.</td></tr>
<tr><td>UFOEXE\BLACK.EXE</td><td>The black screen UFO.BAT puts up when swapping between the above two programs.</td></tr>
<tr><td>[[UFOGRAPH]]</td><td>Misc graphics (.PCK) for soldier equipment screens, smoke, motion detector blobs.</td></tr>
<tr><td>[[UFOINTRO]]</td><td>Holds the introduction movie (.FLI) and the endgame pictures (.LBM).</td></tr>
<tr><td>[[UNITS]]</td><td>Battlescape graphics for soldiers, aliens, and the pixelated guns they hold. (.PCK and .TAB).</td></tr></table>

== Geoscape Files ==
These are savegame files used by the [[Geoscape]] portion of the game. This can be considered a 'standard' save.

<table {{StdDescTable}}>
<th {{StdDescTable_Heading}}>File</th><th {{StdDescTable_Heading}}>Description</th>
<tr><td>[[ACTS.DAT]]</td><td>Contains information which acts with which priority in respective zones aliens are going to try.</td></tr>
<tr><td>[[AKNOW.DAT]]</td><td></td></tr>
<tr><td>[[ALIEN.DAT]]</td><td>Contains Alien activity in Countries and areas, for graphs.</td></tr>
<tr><td>[[ASTORE.DAT]]</td><td>Has the info on aliens in [[Alien Containment]].</td></tr>
<tr><td>[[BASE.DAT]] [[BASE.DAT_(TFTD)|(TFTD)]]</td><td>Has all of the [[X-COM Bases|base]] layout and contents information, radar scanning abilities and other base information.</td></tr>
<tr><td>[[BPROD.DAT]] [[BPROD.DAT_(TFTD)|(TFTD)]]</td><td>List of [[Equipment (EU)|equipment]] being [[manufacturing|produced]].</td></tr>
<tr><td>[[CRAFT.DAT]] [[CRAFT.DAT_(TFTD)|(TFTD)]]</td><td>Has all the [[craft]] info, [[Craft Weapons|weapons]], fuel, damage and items onboard. Also stores UFO information, although information is handled differently from friendly aircraft.</td></tr>
<tr><td>[[DIPLOM.DAT]]</td><td>Diplomacy info, and current and historical [[Country Funding]].</td></tr>
<tr><td>[[DUM.BIN]]</td><td>Dummy file for keeping directory structure. Not used.</td></tr>
<tr><td>[[FACIL.DAT]]</td><td>Info on [[Base Facilities]] you can build.</td></tr>
<tr><td>[[IGLOB.DAT]]</td><td>Date and time.</td></tr>
<tr><td>[[INTER.DAT]]</td><td>Info on interception windows</td></tr>
<tr><td>[[LEASE.DAT]]</td><td></td></tr>
<tr><td>[[LIGLOB.DAT]]</td><td>Money! Also financial graph information.</td></tr>
<tr><td>[[LOC.DAT]]</td><td>Location of bases on the planet as well as other things like ships, waypoints and missions. Basically anything that is an icon on the Geoscape world view.</td></tr>
<tr><td>[[MISSIONS.DAT]]</td><td>Contains counters and race info on the ongoing alien acts.</td></tr>
<tr><td>[[PRODUCT.DAT]] [[PRODUCT.DAT_(TFTD)|(TFTD)]]</td><td>Info on things you can produce.</td></tr>
<tr><td>[[PROJECT.DAT]] [[PROJECT.DAT_(TFTD)|(TFTD)]]</td><td>These are things you are [[research]]ing.</td></tr>
<tr><td>[[PURCHASE.DAT]] [[PURCHASE.DAT_(TFTD)|(TFTD)]]</td><td>Info on stuff you can buy.</td></tr>
<tr><td>[[RESEARCH.DAT]] [[RESEARCH.DAT_(TFTD)|(TFTD)]]</td><td>Completed research.</td></tr>
<tr><td>[[SAVEINFO.DAT]]</td><td>Name of the saved game.</td></tr>
<tr><td>[[SITE.DAT]]</td><td>List of recent Terror Sites. (May be TFTD-only.)</td></tr>
<tr><td>[[SOLDIER.DAT]] [[SOLDIER.DAT (TFTD)|(TFTD)]]</td><td>Data about the [[soldiers]].</td></tr>
<tr><td>[[TRANSFER.DAT]]</td><td>Personnel and equipment being transferred.</td></tr>
<tr><td>[[UIGLOB.DAT]]</td><td>Holds the next numbers for [[UFOs]], Terror Sites, [[Interceptor]]s, etc. Also contains monthly scores for research.</td></tr>
<tr><td>[[UP.DAT]]</td><td>[[UFOpaedia]] info.</td></tr>
<tr><td>[[XBASES.DAT]]</td><td>Schedules [[Base Defence|attacks on X-COM bases]].</td></tr>
<tr><td>[[XCOM.DAT]]</td><td>Contains X-Com activity in Countries and areas, for graphs.</td></tr>
<tr><td>[[ZONAL.DAT]]</td><td>Information on which zones and with what priority aliens are going to attack.</td></tr></table>

(28 files. Note that if you find a geoscape save with additional files, this simply means a battlescape save was made in that slot at some prior point. UFO does not remove unused save files).

== Battlescape Files ==
These are savegame files created and used by the tactical portion of the game. They are only created if the game is saved while in the battlescape. [[Battlescape]] saves also contain all the files used in a standard save.

<table {{StdDescTable}}>
<th {{StdDescTable_Heading}}>File</th><th {{StdDescTable_Heading}}>Description</th>
<tr><td>[[BGLOB.DAT]]</td><td>Describes ambient light on map.</td></tr>
<tr><td>[[GEODATA.DAT]]</td><td>Details the map type and overall map structure.</td></tr>
<tr><td>[[MAP.DAT]]</td><td>Stores tile information for the whole map. Basically all static structures, such as trees, walls, floors and furniture.</td></tr>
<tr><td>[[MISDATA.DAT]]</td><td>Contains information on craft in use and which alien artefacts are available for use in combat.</td></tr>
<tr><td>[[OBPOS.DAT]]</td><td>Stores all the objects that your soldiers can pick up (guns, corpses, etc).</td></tr>
<tr><td>[[ROUTES.DAT]]</td><td>Stores nodes for soldier and alien spawn points, also acts as waypoints for AI pathfinding.</td></tr>
<tr><td>[[SEEMAP.DAT]]</td><td>Fog of war overlay.</td></tr>
<tr><td>[[SMOKBIT.DAT]]</td><td>Smoke particles and fire patches on the map.</td></tr>
<tr><td>[[SMOKREF.DAT]]</td><td>Smoke particles and fire patches on the map.</td></tr>
<tr><td>[[SOURCEMP.DAT]]</td><td>Light source overlays for mobile light sources (i.e. your soldiers).</td></tr>
<tr><td>[[TERMP.DAT]]</td><td>Light source overlays for ambient (or fixed) lighting.</td></tr>
<tr><td>[[UNITPOS.DAT]]</td><td>Controls ownership, visibility, whether the unit is under temporary mind control, etc. Works hand in hand with [[UNITREF.DAT]].</td></tr>
<tr><td>[[UNITREF.DAT]]</td><td>Contains the primary stats for all units in combat. X-Com owned soldiers in this file are ''virtual'' copies of the soldiers in soldier.dat. Works very closely with unitpos.dat.</td></tr>
<tr><td>[[WGLOB.DAT]]</td><td>Battlescape map global information such as map dimensions and the number of turns that have elapsed.</td></tr></table>

(14 unique files, plus all 28 standard save files, totaling 42).

== Missdat Files ==
These temporary files are used at run time, when a battlescape game is in progress. The missdat folder also contains all the files needed to create a standard Geoscape save for the game in progress.

When the tactical game engine starts, it first checks [[SAVEINFO.DAT]] to see if this is a new battle, or if you're loading a battlescape save game. In the case of the former, it generates a new map, based off these files:
*[[GEODATA.DAT]]
*[[MISSION.DAT]]
*[[OBPOSREF.DAT]]
*[[UNIPOS.DAT]]
*[[UNIREF.DAT]]

If you load a game, the tactical engine loads from the save slot directly, as according to [[DIRECT.DAT]] (which details the path to the slot in concern).

When combat ends, these files are created:
*[[CODE.DAT]]
*[[MISSION2.DAT]]
*[[OBPOS2.DAT]]
*[[OPTION.DAT]]
*[[UNIREF2.DAT]]
*[[UNITPOS.DAT_(MISSDAT)|UNITPOS.DAT]]

(12 unique files, plus 27 standard save files (does not use dum.bin), totaling 39).
-----

=File Format information=

==Graphics==

A list of specific image formats used by EU/TFTD.

<table {{StdDescTable}}>
<th {{StdDescTable_Heading}}>Extension</th><th
{{StdDescTable_Heading}}>Description</th>
<tr><td>[[Image Formats#PCK|PCK]]</td><td>A run-length-encoded image format for storing one or more images with a dimension of 32x40 pixels. Used for sprites, tiles and inventory images. Usually accompanied by a TAB file, serving as an index to the image archive.</td></tr>
<tr><td>[[Image Formats#SCR & DAT|SCR & DAT]]</td><td>Stores uncompressed image data for the full screen backgrounds and the inventory screen icons.</td></tr>
<tr><td>[[Image Formats#SPK|SPK]]</td><td>Paper doll and UFOpedia images, among other full screen pictures.</td></tr>
<tr><td>[[Image Formats#BDY|BDY]]</td><td>Often used by TFTD in place of SPK.</td></tr>
</table>

=Did You Know?=
* If your game crashes and you are returned to previous mission, the game is actually referring to the battlescape information in the MISSDAT directory. Also, if a tactical mission is abnormally aborted, the results are obtained from the MISSDAT folder as well. Because the game was not able to update the files that hold the results of the last mission, your current game will be updated with information from the ''previous'' mission that was able to end normally. Abnormal program termination simply means that the tactical game engine crashed or was forced to crash by the user. This [[ExploitsA#Score_Points_For_Free|can be abused]].

* Other exploits with gamefiles can be found [[ExploitsF|here]].

=See Also=

[[Game editors]]

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

PURCHASE.DAT (TFTD)

2016-03-21T14:04:30Z

Morgan525: Created page with " '''00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 Item Index Num''' 02 00 E8 03 00 00 40 9C 00 00 00 00 00 00 48 00 00 00 01 00 soldier ..."

'''00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 Item Index Num'''
02 00 E8 03 00 00 40 9C 00 00 00 00 00 00 48 00 00 00 01 00 soldier 00
03 00 E8 03 00 00 60 EA 00 00 00 00 00 00 48 00 00 00 01 00 scientist 01
04 00 E8 03 00 00 50 C3 00 00 00 00 00 00 48 00 00 00 01 00 technician 02
01 00 E8 03 00 00 20 A1 07 00 00 00 00 00 48 00 00 00 01 00 Triton 03
01 01 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Hammerhead 04
01 02 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Levaithan 05
01 03 E8 03 00 00 C0 27 09 00 00 00 00 00 60 00 00 00 01 00 Barracuda 06
01 04 00 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 00 00 Manta 07
00 00 E8 03 00 00 80 3E 00 00 E0 2E 00 00 30 00 00 00 01 00 Ajax launcher 08
00 01 E8 03 00 00 68 42 00 00 CE 31 00 00 30 00 00 00 01 00 DUP launcher 09
00 02 E8 03 00 00 30 75 00 00 E4 57 00 00 30 00 00 00 01 00 Craft Gas Cannon 0A
00 03 E8 03 00 00 00 00 00 00 0C 4A 04 00 30 00 00 00 00 00 PWT Cannon 0B
00 04 E8 03 00 00 00 00 00 00 38 38 03 00 30 00 00 00 00 00 Gauss Cannon 0C
00 05 E8 03 00 00 00 00 00 00 24 14 04 00 30 00 00 00 00 00 Sonic Osillator 0D
00 06 E8 03 00 00 B8 0B 00 00 60 09 00 00 30 00 00 00 01 00 Ajax torpedoes 0E
00 07 E8 03 00 00 28 23 00 00 20 1C 00 00 30 00 00 00 01 00 DUP torpedoes 0F
00 08 E8 03 00 00 D8 04 00 00 F4 03 00 00 60 00 00 00 01 00 Gas Rounds(x50) 10
00 09 E8 03 00 00 00 00 00 00 84 42 00 00 30 00 00 00 00 00 PWT ammo 11
00 61 E8 03 00 00 00 00 00 00 34 D0 00 00 30 00 00 00 00 00 Craft Gauss Ammo(unused) 12
00 0A E8 03 00 00 A0 68 06 00 20 30 05 00 60 00 00 00 01 00 Tank/harpoon 13
00 5D E8 03 00 00 C8 00 00 00 64 00 00 00 30 00 00 00 01 00 SWS harpoon 14
00 0B E8 03 00 00 00 53 07 00 40 7E 05 00 60 00 00 00 01 00 Tank/Torpedo 15
00 5E E8 03 00 00 B8 0B 00 00 CA 08 00 00 30 00 00 00 01 00 SWS torpedoes 16
00 0C E8 03 00 00 00 00 00 00 50 10 09 00 60 00 00 00 00 00 Tank/Gauss 17
00 60 E8 03 00 00 B8 0B 00 00 C8 00 00 00 30 00 00 00 00 00 SWS Gauss Ammo 18
00 0D E8 03 00 00 00 00 00 00 20 F4 0E 00 60 00 00 00 00 00 Displacer/sonic 19
00 0E E8 03 00 00 00 00 00 00 38 EA 0F 00 60 00 00 00 00 00 Displacer/PWT 1A
00 5F E8 03 00 00 00 00 00 00 D0 E8 00 00 30 00 00 00 00 00 SWS PWT ammo 1B
00 0F E8 03 00 00 20 03 00 00 58 02 00 00 18 00 00 00 01 00 dart gun 1C
00 10 E8 03 00 00 46 00 00 00 34 00 00 00 18 00 00 00 01 00 dart clip 1D
00 11 E8 03 00 00 B8 0B 00 00 CA 08 00 00 18 00 00 00 01 00 jet harpoon 1E
00 12 E8 03 00 00 C8 00 00 00 96 00 00 00 18 00 00 00 01 00 harpoon clip 1F
00 13 E8 03 00 00 00 19 00 00 C0 12 00 00 18 00 00 00 01 00 Gas Cannon 20
00 14 E8 03 00 00 2C 01 00 00 E1 00 00 00 18 00 00 00 01 00 GC-AP 21
00 15 E8 03 00 00 F4 01 00 00 13 01 00 00 18 00 00 00 01 00 GC-HE 22
00 16 E8 03 00 00 90 01 00 00 2C 01 00 00 18 00 00 00 01 00 GC-IN 23
00 17 E8 03 00 00 BC 34 00 00 8D 27 00 00 18 00 00 00 01 00 Hydro-Jet Cannon 24
00 18 E8 03 00 00 F4 01 00 00 90 01 00 00 18 00 00 00 01 00 HJ-AP 25
00 19 E8 03 00 00 BC 02 00 00 30 02 00 00 18 00 00 00 01 00 HJ-HE 26
00 1A E8 03 00 00 8A 02 00 00 08 02 00 00 18 00 00 00 01 00 HJ-IN 27
00 1B E8 03 00 00 A0 0F 00 00 B8 0B 00 00 18 00 00 00 01 00 Torpedo Launcher 28
00 1C E8 03 00 00 58 02 00 00 E0 01 00 00 18 00 00 00 01 00 Small Torpedo 29
00 1D E8 03 00 00 84 03 00 00 D0 02 00 00 18 00 00 00 01 00 Large Torpedo 2A
00 1E E8 03 00 00 B0 04 00 00 C0 03 00 00 18 00 00 00 01 00 IN Torpedo 2B
00 1F E8 03 00 00 00 00 00 00 20 4E 00 00 18 00 00 00 00 00 Gauss Pistol 2C
00 3E E8 03 00 00 00 00 00 00 1A 04 00 00 18 00 00 00 00 00 G.Pistol Clip 2D
00 20 E8 03 00 00 00 00 00 00 24 90 00 00 18 00 00 00 00 00 Gauss Rifle 2E
00 3F E8 03 00 00 00 00 00 00 9E 07 00 00 18 00 00 00 00 00 G.Rifle clip 2F
00 21 E8 03 00 00 00 00 00 00 48 EE 00 00 18 00 00 00 00 00 Gauss Cannon 30
00 40 E8 03 00 00 00 00 00 00 94 0C 00 00 18 00 00 00 00 00 G. Cannon clip 31
00 22 E8 03 00 00 2C 01 00 00 F0 00 00 00 18 00 00 00 01 00 Magna grenade 32
00 23 E8 03 00 00 96 00 00 00 78 00 00 00 18 00 00 00 01 00 Dye grenade 33
00 24 E8 03 00 00 F4 01 00 00 90 01 00 00 18 00 00 00 01 00 Particle D grenade 34
00 25 E8 03 00 00 DC 05 00 00 B0 04 00 00 18 00 00 00 01 00 Magna-Pak Explosive 35
00 26 E8 03 00 00 00 00 00 00 20 B2 00 00 18 00 00 00 00 00 Particle D sensor 36
00 27 E8 03 00 00 00 00 00 00 A4 B5 00 00 18 00 00 00 00 00 Medi-kit 37
00 28 E8 03 00 00 00 00 00 00 8C F8 02 00 18 00 00 00 00 00 MC-Disruptor 38
00 29 E8 03 00 00 EC 04 00 00 B1 03 00 00 18 00 00 00 01 00 Thermal Tazer 39
00 2A E8 03 00 00 3C 00 00 00 28 00 00 00 18 00 00 00 01 00 flare 3A
00 3C E8 03 00 00 00 00 00 00 88 13 00 00 18 00 00 00 00 00 ??Zrbite?? 3B
00 31 E8 03 00 00 00 00 00 00 50 9E 02 00 18 00 00 00 00 00 Sonic Cannon 3C
00 32 E8 03 00 00 E8 03 00 00 76 25 00 00 18 00 00 00 00 00 S.Cannon clip 3D
00 33 E8 03 00 00 E8 03 00 00 24 EE 01 00 18 00 00 00 00 00 Sonic rifle 3E
00 34 E8 03 00 00 E8 03 00 00 92 18 00 00 18 00 00 00 00 00 S.rifle clip 3F
00 35 E8 03 00 00 E8 03 00 00 20 48 01 00 18 00 00 00 00 00 Sonic Pistol 40
00 36 E8 03 00 00 E8 03 00 00 58 11 00 00 18 00 00 00 00 00 S.Pistol clip 41
00 37 E8 03 00 00 E8 03 00 00 80 32 02 00 18 00 00 00 00 00 Disruptor Pulse Launcher 42
00 38 E8 03 00 00 E8 03 00 00 A8 93 00 00 18 00 00 00 00 00 Disruptor ammo 43
00 39 E8 03 00 00 E8 03 00 00 C0 D4 01 00 18 00 00 00 00 00 Thermal Shock Launcher 44
00 3A E8 03 00 00 E8 03 00 00 60 3B 00 00 18 00 00 00 00 00 Thermal Shock Ammo 45
00 3B E8 03 00 00 E8 03 00 00 02 3A 00 00 18 00 00 00 00 00 Sonic Pulsar 46
00 3D E8 03 00 00 E8 03 00 00 80 A3 04 00 18 00 00 00 00 00 M.C.reader 47
00 2B E8 03 00 00 E8 03 00 00 DC 05 00 00 18 00 00 00 00 00 Vibro blade 48
00 2C E8 03 00 00 E8 03 00 00 08 07 00 00 18 00 00 00 00 00 Thermic Lance 49
00 2D E8 03 00 00 E8 03 00 00 D0 07 00 00 18 00 00 00 00 00 Heavy Lance 4A
00 41 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4B
00 42 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4C
00 43 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4D
00 44 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4E
00 45 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 4F
00 46 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 50
00 47 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 51
00 48 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 52
00 49 E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 53
00 4A E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 54
00 4B E8 03 00 00 E8 03 00 00 20 4E 00 00 20 00 00 00 00 00 corpse 55
00 50 E8 03 00 00 E8 03 00 00 90 D0 03 00 30 00 00 00 00 00 Ion-Beam Accelerator 56
00 51 E8 03 00 00 E8 03 00 00 80 38 01 00 30 00 00 00 00 00 Magnetic Navigation 57
00 52 E8 03 00 00 E8 03 00 00 20 4E 00 00 30 00 00 00 00 00 Sub Construction 58
00 53 E8 03 00 00 E8 03 00 00 88 13 00 00 30 00 00 00 00 00 Cryogenics 59
00 54 E8 03 00 00 E8 03 00 00 40 9C 00 00 30 00 00 00 00 00 cloning 5A
00 55 E8 03 00 00 E8 03 00 00 20 4E 00 00 30 00 00 00 00 00 learning arrays 5B
00 56 E8 03 00 00 E8 03 00 00 70 94 00 00 30 00 00 00 00 00 Implanter 5C
00 57 E8 03 00 00 E8 03 00 00 28 23 00 00 30 00 00 00 00 00 Examination Room 5D
00 58 E8 03 00 00 E8 03 00 00 64 19 00 00 30 00 00 00 00 00 Aqua Plastics 5E
00 59 E8 03 00 00 E8 03 00 00 64 00 00 00 30 00 00 00 00 00 Re-Animation zone 5F
00 5A E8 03 00 00 E8 03 00 00 F0 D2 00 00 20 00 00 00 00 00 Plastic Armor 60
00 5B E8 03 00 00 E8 03 00 00 08 4C 01 00 20 00 00 00 00 00 Ion Armor 61
00 5C E8 03 00 00 E8 03 00 00 38 C1 01 00 20 00 00 00 00 00 Mag. Ion Armor 62

Game Files

2016-03-21T13:43:31Z

Morgan525: /* Geoscape Files */

Not-for-profit, just-for-fun reverse engineering.

* General note re: [[HackerTools|Hex editing game files]]
:Contains a quick introduction to using a most unlikely program to edit your game files, and suggestions on other editors out there.
* A primer for the [[Command Prompt]] (aka the command console).
:Information on how to manage directories, files, plus other neat tricks that can be done through the command console that should not be forgotten in today's era of point and click madness.

[http://www.stonepool.com/xcom/hacking/index.html Hatfarm / Chris Voss] and [http://www.daishiva.com/phpBB2/generic.php?page=progLinks.shtml DaiShiva] (see [http://www.daishiva.com/programs/XCFormat.html file formats]) also have notes on a number of XCOM's file formats not yet detailed on this wiki.

= General File Information =
== Program Files ==

These are program files and static data files that are not part of the saved game files.

<table {{StdDescTable}}>
<th {{StdDescTable_Heading}}>File</th><th {{StdDescTable_Heading}}>Description</th>
<tr><td>[[GEODATA]]</td><td>Geoscape data. Includes localization strings, [[OBDATA.DAT]] for objects like weapons, [[WORLD.DAT]] for globe terrain.</td></tr>
<tr><td>[[GEOGRAPH]]</td><td>Graphics for [[UFOpaedia]] and research screen backgrounds.</td></tr>
<tr><td>[[MAPS]]</td><td>Pre-generated Battlescape terrain blocks (.MAP). These are filled in with terrain tiles. A few dozen blocks make up a battlescape.</td></tr>
<tr><td>[[Saved_Game_Files#Missdat_Files|MISSDAT]]</td><td>Holds the data from the previous mission. (Can be [[ExploitsA#Score_Points_For_Free|exploited]]).</td></tr>
<tr><td>[[ROUTES]]</td><td>Alien route maps (.RMP) for moving around the pre-generated Battlescape terrain blocks.</td></tr>
<tr><td>[[SOUND]]</td><td>1990-era sound drivers, or MIDI files for Windows version.</td></tr>
<tr><td>[[TERRAIN]]</td><td>Battlescape graphic tiles for buildings, ships, and terrain (.MCD, .PCK, and .TAB).</td></tr>
<tr><td>UFO2EXE\[[TACTICAL.EXE]]</td><td>The "Battlescape" program in DOS-release of UFO.</td></tr>
<tr><td>UFOEXE\[[GEOSCAPE.EXE]]</td><td>The "Geoscape" program that handles base management and aircraft.</td></tr>
<tr><td>UFOEXE\BLACK.EXE</td><td>The black screen UFO.BAT puts up when swapping between the above two programs.</td></tr>
<tr><td>[[UFOGRAPH]]</td><td>Misc graphics (.PCK) for soldier equipment screens, smoke, motion detector blobs.</td></tr>
<tr><td>[[UFOINTRO]]</td><td>Holds the introduction movie (.FLI) and the endgame pictures (.LBM).</td></tr>
<tr><td>[[UNITS]]</td><td>Battlescape graphics for soldiers, aliens, and the pixelated guns they hold. (.PCK and .TAB).</td></tr></table>

== Geoscape Files ==
These are savegame files used by the [[Geoscape]] portion of the game. This can be considered a 'standard' save.

<table {{StdDescTable}}>
<th {{StdDescTable_Heading}}>File</th><th {{StdDescTable_Heading}}>Description</th>
<tr><td>[[ACTS.DAT]]</td><td>Contains information which acts with which priority in respective zones aliens are going to try.</td></tr>
<tr><td>[[AKNOW.DAT]]</td><td></td></tr>
<tr><td>[[ALIEN.DAT]]</td><td>Contains Alien activity in Countries and areas, for graphs.</td></tr>
<tr><td>[[ASTORE.DAT]]</td><td>Has the info on aliens in [[Alien Containment]].</td></tr>
<tr><td>[[BASE.DAT]] [[BASE.DAT_(TFTD)|(TFTD)]]</td><td>Has all of the [[X-COM Bases|base]] layout and contents information, radar scanning abilities and other base information.</td></tr>
<tr><td>[[BPROD.DAT]] [[BPROD.DAT_(TFTD)|(TFTD)]]</td><td>List of [[Equipment (EU)|equipment]] being [[manufacturing|produced]].</td></tr>
<tr><td>[[CRAFT.DAT]] [[CRAFT.DAT_(TFTD)|(TFTD)]]</td><td>Has all the [[craft]] info, [[Craft Weapons|weapons]], fuel, damage and items onboard. Also stores UFO information, although information is handled differently from friendly aircraft.</td></tr>
<tr><td>[[DIPLOM.DAT]]</td><td>Diplomacy info, and current and historical [[Country Funding]].</td></tr>
<tr><td>[[DUM.BIN]]</td><td>Dummy file for keeping directory structure. Not used.</td></tr>
<tr><td>[[FACIL.DAT]]</td><td>Info on [[Base Facilities]] you can build.</td></tr>
<tr><td>[[IGLOB.DAT]]</td><td>Date and time.</td></tr>
<tr><td>[[INTER.DAT]]</td><td>Info on interception windows</td></tr>
<tr><td>[[LEASE.DAT]]</td><td></td></tr>
<tr><td>[[LIGLOB.DAT]]</td><td>Money! Also financial graph information.</td></tr>
<tr><td>[[LOC.DAT]]</td><td>Location of bases on the planet as well as other things like ships, waypoints and missions. Basically anything that is an icon on the Geoscape world view.</td></tr>
<tr><td>[[MISSIONS.DAT]]</td><td>Contains counters and race info on the ongoing alien acts.</td></tr>
<tr><td>[[PRODUCT.DAT]] [[PRODUCT.DAT_(TFTD)|(TFTD)]]</td><td>Info on things you can produce.</td></tr>
<tr><td>[[PROJECT.DAT]] [[PROJECT.DAT_(TFTD)|(TFTD)]]</td><td>These are things you are [[research]]ing.</td></tr>
<tr><td>[[PURCHASE.DAT]]</td><td>Info on stuff you can buy.</td></tr>
<tr><td>[[RESEARCH.DAT]] [[RESEARCH.DAT_(TFTD)|(TFTD)]]</td><td>Completed research.</td></tr> RESEARCH.DAT_(TFTD)
<tr><td>[[SAVEINFO.DAT]]</td><td>Name of the saved game.</td></tr>
<tr><td>[[SITE.DAT]]</td><td>List of recent Terror Sites. (May be TFTD-only.)</td></tr>
<tr><td>[[SOLDIER.DAT]] [[SOLDIER.DAT (TFTD)|(TFTD)]]</td><td>Data about the [[soldiers]].</td></tr>
<tr><td>[[TRANSFER.DAT]]</td><td>Personnel and equipment being transferred.</td></tr>
<tr><td>[[UIGLOB.DAT]]</td><td>Holds the next numbers for [[UFOs]], Terror Sites, [[Interceptor]]s, etc. Also contains monthly scores for research.</td></tr>
<tr><td>[[UP.DAT]]</td><td>[[UFOpaedia]] info.</td></tr>
<tr><td>[[XBASES.DAT]]</td><td>Schedules [[Base Defence|attacks on X-COM bases]].</td></tr>
<tr><td>[[XCOM.DAT]]</td><td>Contains X-Com activity in Countries and areas, for graphs.</td></tr>
<tr><td>[[ZONAL.DAT]]</td><td>Information on which zones and with what priority aliens are going to attack.</td></tr></table>

(28 files. Note that if you find a geoscape save with additional files, this simply means a battlescape save was made in that slot at some prior point. UFO does not remove unused save files).

== Battlescape Files ==
These are savegame files created and used by the tactical portion of the game. They are only created if the game is saved while in the battlescape. [[Battlescape]] saves also contain all the files used in a standard save.

<table {{StdDescTable}}>
<th {{StdDescTable_Heading}}>File</th><th {{StdDescTable_Heading}}>Description</th>
<tr><td>[[BGLOB.DAT]]</td><td>Describes ambient light on map.</td></tr>
<tr><td>[[GEODATA.DAT]]</td><td>Details the map type and overall map structure.</td></tr>
<tr><td>[[MAP.DAT]]</td><td>Stores tile information for the whole map. Basically all static structures, such as trees, walls, floors and furniture.</td></tr>
<tr><td>[[MISDATA.DAT]]</td><td>Contains information on craft in use and which alien artefacts are available for use in combat.</td></tr>
<tr><td>[[OBPOS.DAT]]</td><td>Stores all the objects that your soldiers can pick up (guns, corpses, etc).</td></tr>
<tr><td>[[ROUTES.DAT]]</td><td>Stores nodes for soldier and alien spawn points, also acts as waypoints for AI pathfinding.</td></tr>
<tr><td>[[SEEMAP.DAT]]</td><td>Fog of war overlay.</td></tr>
<tr><td>[[SMOKBIT.DAT]]</td><td>Smoke particles and fire patches on the map.</td></tr>
<tr><td>[[SMOKREF.DAT]]</td><td>Smoke particles and fire patches on the map.</td></tr>
<tr><td>[[SOURCEMP.DAT]]</td><td>Light source overlays for mobile light sources (i.e. your soldiers).</td></tr>
<tr><td>[[TERMP.DAT]]</td><td>Light source overlays for ambient (or fixed) lighting.</td></tr>
<tr><td>[[UNITPOS.DAT]]</td><td>Controls ownership, visibility, whether the unit is under temporary mind control, etc. Works hand in hand with [[UNITREF.DAT]].</td></tr>
<tr><td>[[UNITREF.DAT]]</td><td>Contains the primary stats for all units in combat. X-Com owned soldiers in this file are ''virtual'' copies of the soldiers in soldier.dat. Works very closely with unitpos.dat.</td></tr>
<tr><td>[[WGLOB.DAT]]</td><td>Battlescape map global information such as map dimensions and the number of turns that have elapsed.</td></tr></table>

(14 unique files, plus all 28 standard save files, totaling 42).

== Missdat Files ==
These temporary files are used at run time, when a battlescape game is in progress. The missdat folder also contains all the files needed to create a standard Geoscape save for the game in progress.

When the tactical game engine starts, it first checks [[SAVEINFO.DAT]] to see if this is a new battle, or if you're loading a battlescape save game. In the case of the former, it generates a new map, based off these files:
*[[GEODATA.DAT]]
*[[MISSION.DAT]]
*[[OBPOSREF.DAT]]
*[[UNIPOS.DAT]]
*[[UNIREF.DAT]]

If you load a game, the tactical engine loads from the save slot directly, as according to [[DIRECT.DAT]] (which details the path to the slot in concern).

When combat ends, these files are created:
*[[CODE.DAT]]
*[[MISSION2.DAT]]
*[[OBPOS2.DAT]]
*[[OPTION.DAT]]
*[[UNIREF2.DAT]]
*[[UNITPOS.DAT_(MISSDAT)|UNITPOS.DAT]]

(12 unique files, plus 27 standard save files (does not use dum.bin), totaling 39).
-----

=File Format information=

==Graphics==

A list of specific image formats used by EU/TFTD.

<table {{StdDescTable}}>
<th {{StdDescTable_Heading}}>Extension</th><th
{{StdDescTable_Heading}}>Description</th>
<tr><td>[[Image Formats#PCK|PCK]]</td><td>A run-length-encoded image format for storing one or more images with a dimension of 32x40 pixels. Used for sprites, tiles and inventory images. Usually accompanied by a TAB file, serving as an index to the image archive.</td></tr>
<tr><td>[[Image Formats#SCR & DAT|SCR & DAT]]</td><td>Stores uncompressed image data for the full screen backgrounds and the inventory screen icons.</td></tr>
<tr><td>[[Image Formats#SPK|SPK]]</td><td>Paper doll and UFOpedia images, among other full screen pictures.</td></tr>
<tr><td>[[Image Formats#BDY|BDY]]</td><td>Often used by TFTD in place of SPK.</td></tr>
</table>

=Did You Know?=
* If your game crashes and you are returned to previous mission, the game is actually referring to the battlescape information in the MISSDAT directory. Also, if a tactical mission is abnormally aborted, the results are obtained from the MISSDAT folder as well. Because the game was not able to update the files that hold the results of the last mission, your current game will be updated with information from the ''previous'' mission that was able to end normally. Abnormal program termination simply means that the tactical game engine crashed or was forced to crash by the user. This [[ExploitsA#Score_Points_For_Free|can be abused]].

* Other exploits with gamefiles can be found [[ExploitsF|here]].

=See Also=

[[Game editors]]

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

GEODATA

2016-03-19T08:54:39Z

Morgan525:

<table width="50%" {{StdDescTable}}>
<th {{StdDescTable_Heading}}>File</th><th {{StdDescTable_Heading}}>Description</th>
<tr><td>[[BACKPALS.DAT]]</td><td>Palettes used by some [[BACK01.SCR-BACK17.SCR|background images]].</td></tr>
<tr><td>[[BIGLETS.DAT]]</td><td>Font file. Large text.</td></tr>
<tr><td>[[COS.DAT]]</td><td>Pre-calculated cosine table.</td></tr>
<tr><td>[[ENGLISH.DAT]] [[ENGLISH.DAT_(TFTD)|(TFTD)]]</td><td>Geoscape English language text.</td></tr>
<tr><td>[[ENGLISH2.DAT]] [[ENGLISH2.DAT_(TFTD)|(TFTD)]]</td><td>Battlescape English language text.</td></tr>
<tr><td>[[FRENCH.DAT]]</td><td>Geoscape French language text.</td></tr>
<tr><td>[[FRENCH2.DAT]]</td><td>Battlescape French language text.</td></tr>
<tr><td>[[GERMAN.DAT]]</td><td>Geoscape German language text.</td></tr>
<tr><td>[[GERMAN2.DAT]]</td><td>Battlescape German language text.</td></tr>
<tr><td>[[INTERWIN.DAT]]</td><td>Intercept screen and control panel.</td></tr>
<tr><td>[[LANG1.DAT]]</td><td>French Geoscape control panel overlay.</td></tr>
<tr><td>[[LANG2.DAT]]</td><td>German Geoscape control panel overlay.</td></tr>
<tr><td>[[LOFTEMPS.DAT]]</td><td>3-D Info on Map Objects</td></tr>
<tr><td>[[OBDATA.DAT]] [[OBDATA.DAT_(TFTD)|(TFTD)]]</td><td>Object data.</td></tr>
<tr><td>[[PALETTES.DAT]]</td><td>Color information used in the game.</td></tr>
<tr><td>[[SCANG.DAT]]</td><td>Battlescape map graphics.</td></tr>
<tr><td>[[SINE.DAT]]</td><td>Pre-calculated sine table.</td></tr>
<tr><td>[[SMALLSET.DAT]]</td><td>Font file. Normal text.</td></tr>
<tr><td>[[WORLD.DAT]]</td><td>Global terrain/depth divisions.</td></tr></table>
[[Category:Game Files]]
[[Category:Game Folders]]
[[Category:Enemy Unknown/UFO Defense]]

GEODATA

2016-03-19T08:53:09Z

Morgan525:

<table width="50%" {{StdDescTable}}>
<th {{StdDescTable_Heading}}>File</th><th {{StdDescTable_Heading}}>Description</th>
<tr><td>[[BACKPALS.DAT]]</td><td>Palettes used by some [[BACK01.SCR-BACK17.SCR|background images]].</td></tr>
<tr><td>[[BIGLETS.DAT]]</td><td>Font file. Large text.</td></tr>
<tr><td>[[COS.DAT]]</td><td>Pre-calculated cosine table.</td></tr>
<tr><td>[[ENGLISH.DAT]] [[ENGLISH.DAT_(TFTD)|(TFTD)]]</td><td>Geoscape English language text.</td></tr>
<tr><td>[[ENGLISH2.DAT]]</td><td>Battlescape English language text.</td></tr>
<tr><td>[[FRENCH.DAT]]</td><td>Geoscape French language text.</td></tr>
<tr><td>[[FRENCH2.DAT]]</td><td>Battlescape French language text.</td></tr>
<tr><td>[[GERMAN.DAT]]</td><td>Geoscape German language text.</td></tr>
<tr><td>[[GERMAN2.DAT]]</td><td>Battlescape German language text.</td></tr>
<tr><td>[[INTERWIN.DAT]]</td><td>Intercept screen and control panel.</td></tr>
<tr><td>[[LANG1.DAT]]</td><td>French Geoscape control panel overlay.</td></tr>
<tr><td>[[LANG2.DAT]]</td><td>German Geoscape control panel overlay.</td></tr>
<tr><td>[[LOFTEMPS.DAT]]</td><td>3-D Info on Map Objects</td></tr>
<tr><td>[[OBDATA.DAT]] [[OBDATA.DAT_(TFTD)|(TFTD)]]</td><td>Object data.</td></tr>
<tr><td>[[PALETTES.DAT]]</td><td>Color information used in the game.</td></tr>
<tr><td>[[SCANG.DAT]]</td><td>Battlescape map graphics.</td></tr>
<tr><td>[[SINE.DAT]]</td><td>Pre-calculated sine table.</td></tr>
<tr><td>[[SMALLSET.DAT]]</td><td>Font file. Normal text.</td></tr>
<tr><td>[[WORLD.DAT]]</td><td>Global terrain/depth divisions.</td></tr></table>
[[Category:Game Files]]
[[Category:Game Folders]]
[[Category:Enemy Unknown/UFO Defense]]

Talk:Alien Appearance Ratios

2016-03-18T13:35:09Z

Morgan525: /* Snakemen in Jan */

Don't Alien Retaliations depend on who you shot down. So in August if you shoot down lots of Snakemen Ships they will retaliate not the Ethereals who have 40% chance to be the race on the Retalation?

: Retaliations are done in two ways. The aliens can be generated to appear on retaliation scouting missions, with the race determined by the probabilities in these tables. This means any race can start scouting for X-Com bases to attack even if you haven't shot down any UFOs of that particular race. They still have to find your base to attack it though.

: The other method is the instant base attack. Every time you shoot down a UFO, the game has a 2% chance to instantly retaliate against the interceptor's home base and will send a battleship straight to the base without having to scout for it. In this scenario, the race is determined by the crew of the UFO you shot down.

: I think it was determined that researching the Martian Solution (or was it Cydonia or Bust?) may generate a base attack as well. -[[User:NKF|NKF]] 17:21, 19 June 2012 (EDT)

:: I have never seen either of those ways in the Collector's Edition. The only way that works in the Collectors Edition (verified by examining MISSIONS.DAT) is to shoot down a UFO, which has a difficulty-level dependent probability of immediately generating a Retaliation scouting mission of the same race as the one you shot down.

:: Note that since DOS does not do an awesome job of default-initializing its files, that garbage data in XBASES.DAT can do strange things. For the Collector's Edition, correctly tweaking that file will convert the next mission by that race into a base attack, and cause the scheduled mission to be rescheduled for later. -[[User:Zaimoni|Zaimoni]] 17:21, 19 June 2012 (EDT)

:::I think the 2% probability I mentioned is part of what you're referring to. Having it adjusted by difficulty would make sense, as 2% on its own seems a bit low for superhuman. But now that I think about it, I might be getting confused with the terror mission mechanics. I'll have to run a practical test and check this out manually. Should be easy enough by setting all the races to one type and all the retaliation rows to some other race. -[[User:NKF|NKF]] 03:31, 20 June 2012 (EDT)

::::The retaliation rows aren't used. At all. -[[User:NKF|NKF]] 05:15, 20 June 2012 (EDT)

:::::Ran a few more tests just in case, and still nothing. So if it's unused data, why were they set in TFTD's rows as well? [[User:NKF|NKF]] 05:20, 21 June 2012 (EDT)

::::::Shouldn't we add this to the bullet points at the End? -[[User:Ditto51|Ditto51]] 19:20, 22 June 2012 (GMT)

:So, to clarify, are Alien Retaliation missions always the same race as the craft that was downed? If not, what does determine their race if it's not these tables? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 21:42, 8 May 2015 (EDT)

On another note, when an Iflitration mission is complete a base almost immediatly spawns in or around the Area of the contry being inflitrated, it is of the same race as the inflitration aliens so won't the Alien Base and the Alien Infiltration missions can have the same probably, just without the mission of an Alien Base. Meaning that Alien Base can still spawn even without the presensce of an Alien Base Missions, so it is just as common to have Muton Base as Etherial bases.

Just Saying we may need to add this to the Bullet points at the bottom. -[[User:Ditto51|Ditto51]] 19:20, 22 June 2012 (GMT)

: That's one of the possible outcomes of an infiltration mission. The probabilities here are more for the generation of the 'alien base' teams that look for the base site that eventually lead up to the base creation. Certainly this can be clarified in the notes. -[[User:NKF|NKF]] 19:27, 22 June 2012 (EDT)

==Snakemen in Jan==
Is it really true the Snakemen can do a Harvest mission in January 1999, or is that a typo? It's not a mission they normally do. --[[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 17:24, 3 July 2014 (EDT)
: Yes it is possible, I'm pretty sure the numbers were pulled from the game's coding so they would all be right. Its probably just so rare to the point that it doesn't happen. Or it does and you just don't detect the ships because bad luck or different continent.--[[User:Ditto51|Ditto51]] ([[User talk:Ditto51|talk]]) 13:34, 12 August 2014 (EDT)
All rows except Alien Research and Alien Terror are unused in January, since the non-terror mission for that month is hardcoded to be an Alien Research mission in the area containing X-Com's first base. So it seems there is a 10% chance of encountering Snakemen in the first month, but a Snakeman Harvest is impossible in the unmodded game. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 21:42, 8 May 2015 (EDT)
:However, now that I think about it, it's also possible the Alien Research mission is locked to Sectoids. I know I've seen both Sectoid and Floater Alien Terror missions in the first month, but I don't seem to recall getting Floater Alien Research, and I've never seen Snakemen in the first month. Anybody remember getting a non-Sectoid Research mission in the first month? Or has anyone done a code dig? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 23:56, 16 March 2016 (UTC)
Looking at the code for CE: The first research mission is hard set to be sectoids. The first terror mission of the game has a 30% chance to be sectoid, 70% chance to be floater. -[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 13:34, 18 March 2016 (UTC)

Talk:Alien Appearance Ratios

2016-03-18T13:34:17Z

Morgan525: /* Snakemen in Jan */

Don't Alien Retaliations depend on who you shot down. So in August if you shoot down lots of Snakemen Ships they will retaliate not the Ethereals who have 40% chance to be the race on the Retalation?

: Retaliations are done in two ways. The aliens can be generated to appear on retaliation scouting missions, with the race determined by the probabilities in these tables. This means any race can start scouting for X-Com bases to attack even if you haven't shot down any UFOs of that particular race. They still have to find your base to attack it though.

: The other method is the instant base attack. Every time you shoot down a UFO, the game has a 2% chance to instantly retaliate against the interceptor's home base and will send a battleship straight to the base without having to scout for it. In this scenario, the race is determined by the crew of the UFO you shot down.

: I think it was determined that researching the Martian Solution (or was it Cydonia or Bust?) may generate a base attack as well. -[[User:NKF|NKF]] 17:21, 19 June 2012 (EDT)

:: I have never seen either of those ways in the Collector's Edition. The only way that works in the Collectors Edition (verified by examining MISSIONS.DAT) is to shoot down a UFO, which has a difficulty-level dependent probability of immediately generating a Retaliation scouting mission of the same race as the one you shot down.

:: Note that since DOS does not do an awesome job of default-initializing its files, that garbage data in XBASES.DAT can do strange things. For the Collector's Edition, correctly tweaking that file will convert the next mission by that race into a base attack, and cause the scheduled mission to be rescheduled for later. -[[User:Zaimoni|Zaimoni]] 17:21, 19 June 2012 (EDT)

:::I think the 2% probability I mentioned is part of what you're referring to. Having it adjusted by difficulty would make sense, as 2% on its own seems a bit low for superhuman. But now that I think about it, I might be getting confused with the terror mission mechanics. I'll have to run a practical test and check this out manually. Should be easy enough by setting all the races to one type and all the retaliation rows to some other race. -[[User:NKF|NKF]] 03:31, 20 June 2012 (EDT)

::::The retaliation rows aren't used. At all. -[[User:NKF|NKF]] 05:15, 20 June 2012 (EDT)

:::::Ran a few more tests just in case, and still nothing. So if it's unused data, why were they set in TFTD's rows as well? [[User:NKF|NKF]] 05:20, 21 June 2012 (EDT)

::::::Shouldn't we add this to the bullet points at the End? -[[User:Ditto51|Ditto51]] 19:20, 22 June 2012 (GMT)

:So, to clarify, are Alien Retaliation missions always the same race as the craft that was downed? If not, what does determine their race if it's not these tables? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 21:42, 8 May 2015 (EDT)

On another note, when an Iflitration mission is complete a base almost immediatly spawns in or around the Area of the contry being inflitrated, it is of the same race as the inflitration aliens so won't the Alien Base and the Alien Infiltration missions can have the same probably, just without the mission of an Alien Base. Meaning that Alien Base can still spawn even without the presensce of an Alien Base Missions, so it is just as common to have Muton Base as Etherial bases.

Just Saying we may need to add this to the Bullet points at the bottom. -[[User:Ditto51|Ditto51]] 19:20, 22 June 2012 (GMT)

: That's one of the possible outcomes of an infiltration mission. The probabilities here are more for the generation of the 'alien base' teams that look for the base site that eventually lead up to the base creation. Certainly this can be clarified in the notes. -[[User:NKF|NKF]] 19:27, 22 June 2012 (EDT)

==Snakemen in Jan==
Is it really true the Snakemen can do a Harvest mission in January 1999, or is that a typo? It's not a mission they normally do. --[[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 17:24, 3 July 2014 (EDT)
: Yes it is possible, I'm pretty sure the numbers were pulled from the game's coding so they would all be right. Its probably just so rare to the point that it doesn't happen. Or it does and you just don't detect the ships because bad luck or different continent.--[[User:Ditto51|Ditto51]] ([[User talk:Ditto51|talk]]) 13:34, 12 August 2014 (EDT)
All rows except Alien Research and Alien Terror are unused in January, since the non-terror mission for that month is hardcoded to be an Alien Research mission in the area containing X-Com's first base. So it seems there is a 10% chance of encountering Snakemen in the first month, but a Snakeman Harvest is impossible in the unmodded game. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 21:42, 8 May 2015 (EDT)
:However, now that I think about it, it's also possible the Alien Research mission is locked to Sectoids. I know I've seen both Sectoid and Floater Alien Terror missions in the first month, but I don't seem to recall getting Floater Alien Research, and I've never seen Snakemen in the first month. Anybody remember getting a non-Sectoid Research mission in the first month? Or has anyone done a code dig? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 23:56, 16 March 2016 (UTC)
The first research mission is hard set to be sectoids. The first terror mission of the game has a 30% chance to be sectoid, 70% chance to be floater. -[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 13:34, 18 March 2016 (UTC)

Talk:TFTDextender

2016-03-18T07:03:18Z

Morgan525: /* Minor Bugs */

=Questions or Comments=
'''A place to provide feedback or ask questions:'''
:''Thanks to Kyrub, Spike, and numerous others who help to troubleshoot problems, provide feedback on releases, and innumerable other activities to help make TFTDextender and the game better! -'' [[User:Morgan525|Tycho]]

*The zip archive does not seem to include an .ini file. Where do I get the .ini file from?

:::''If the latest release is a patch, meaning there are no new additions to the INI file, only the patcher.dll file will be updated. In this way, those who already have the current release won't have their INI settings overwritten. You will need to download the last full version, extract the files from it, and then extract file from the latest patch. When I first release the Extender and lots of problems were being reported, I was releasing fixes almost on a weekly basis and so I still continue with this idea.'' [[User:Morgan525|Tycho]]

== Bug Reports ==
===Major Bugs===
*Battlescape Crash when HWP present in non-Base Defense missions
''An error in the code will cause the game to crash. This will be fixed in the next release. For now, it can be avoided by copying the line for 'No Freebies for Tanks' from the bugfix reference file into the [Bug Fix] section of the INI - [[User:Morgan525|Tycho]]''

*Battlescape Crash when alien (Old One) is in fire and "Fire Fix" bugfix is enabled.

:I've got a savegame which makes TFTDextender chocke on the "Fire Fix" bugfix - basically, during a terror map (Fiji, iirc), there's a Deep One on the third level in the house. I've just fired an incendiary round at it, and it's now standing in fire. I end the turn, and when all alien movement is done (presumably this is where the fire-check happens) the game crashes with the error message "TFTD crashed at 0x42E061 with error 0xC0000005 trying to access 0x0051C1C0". Those addresses are the same each crash, so it's a consistent bug.

:Disabling "Fire Fix" before starting TFTD and loading that savegame prevents the crash, and the Deep One dies.

:System is Windows 7 64 bit (up to date with patches and service packs), running on the Steam version of TFTD (but not through steam, obviously).

:I can provide the savegame (the entire GAME_8 folder as a zip) and the TFTDextender.ini in use, in the hopes this will aid in debugging. - [[User:MacGyver|MacGyver]]

::''Thanks MacGyver! It is nice when someone has troubleshot an issue to identify the cause. Just based on your initial report, I found the problem: The TFTD base code differed slightly from EU. I found the offending lines and modified them to fit the TFTD code. The problem was in the section to check if the unit catches fire. - [[User:Morgan525|Tycho]] 10:58, 2 May 2013 (EDT)''

*(a)Lobstermen don't use their guns and (b)their melee attack is weak.
:''The first part(a) is a problem in the fix for the code to determine a unit's abilities in the first step of the AI process. The latter problem (b) is a bug in the original program. If a unit has a ranged weapon, the damage is set to the value of the weapon's melee attack and not the strength of the lobsterman, as it is for all other units that have a natural melee attack.''

*Interception Crash
TFTD latest version (with the 7.2 patch) crashed in Geoscape on the 1st Intercept (subs vs Alien craft). I had already had a tactical combat against a landed craft, but this did not involve an interception. I did notice that the Geoscape Graphs looked strange (faulty) prior to the interception and crash.
Running windowed mode with most things switched on apart from the [ make defense missions harder ] mods. Geoscape and battlefield shortcuts switched [off].

:''If this happens again, please include any error message as well.'' -[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 09:37, 2 June 2015 (EDT)

Latest issue of TFTD full, with the 7.2 patch
I noticed in first tactical game that one of my aquanauts holding a gas cannon had it magically transformed into a sonic pistol (i think from the Deep One I was targetting at the time). Obviously I could not use it as it was my first mission. When I clicked away from the aquanaut and clicked back on him later, the sonic pistol was back to the gas cannon.
:''This sounds like the strangeness that using the '''More Reaction Fire''' mod can introduce. Try playing the game without that mod enabled for a while.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 01:45, 3 June 2015 (EDT)
I also note that even though I only expended 2 shots from each of my gas cannons carrying HE ammo, all my HE ammo was used up at the end of the mission.

TFTD needs the "collect ammo" feature that is used in UFO.
:''TFTD does have the collect ammo feature but it seems it needs more work.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 20:23, 2 June 2015 (EDT)

=== Minor Bugs ===
* I've got a feeling, though I can't check, that "Know Thy Enemy" currently doesn't register that autopsies have been performed - e.g. it shouldn't take 4 or 5 sonic-blasta shots to down a single Gill Man. When I disable "Know Thy Enemy", the game becomes significantly easier, also in missions with creatures on which autopsies have been performed. - [[User:MacGyver|MacGyver]]

''I found the problem and the code is working now. It will be out in the next version.''

* For some reason, the loader (newest version) opens TWO windows at startup. One is titled 'X-COM Terror From the Deep Gold Edition' and contains the game's video output, the other is titled 'Terror From The Deep.exe' and is completely blank (not even a blinking console prompt). Win7 auto-groups their buttons on the taskbar and closing either closes the other too. Is this normal behavior or am I missing something?--[[User:Amitakartok|amitakartok]] 11:47, 24 August 2013 (EDT)
<s>''To my knowledge, this has always been the case even with UFO Extender. The first 'blank' window is the loader which spawns the second 'game' window. Closing the Extender will abort the game and quitting the game automatically closes the Extender.''</s>
:: Well, UFOextender never did that for me, only TFTDextender. Maybe it's due to using an earlier build?--[[User:Amitakartok|amitakartok]] 11:43, 25 August 2013 (EDT)
<s>''It's doesn't happen with UFO. I checked earlier versions and this has been present since the beginning. The command to create the process for the game is different from UFO and the flags don't seem to allow the extender shell window to close. I've tried a few things but either they have no effect or they lock the game as it boots up. Since it is a cosmetic issue and doesn't impact the gameplay, I'm not too concerned with it for now.''</s>-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])

'''Fixed in version 1.07.3'''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 06:58, 18 March 2016 (UTC)

== Things that TFTDextender does not fix ==

Just more or less as a note to the reader, TFTDextender does not fix some of the following things that are sometimes thought of as needing fixing (and this is probably deliberate?):

* Does not fix the apparent swap of the ground map for the VERY SMALL Survey Ship (1 occupant) with the SMALL Escort (half-dozen or more occupants). So you get the VERY SMALL sub occupying about 25 squares of usable area on the Battlescape, and the supposedly larger SMALL sub occupying one square of usable area on the Battlescape, begging the question of how all those aliens got inside there in the first place. XcomUtil will fix this, as will the original patches that XcomUtil incorporates.
* Does not fix the incorrect pictures for the large USO in the interception window.
:''Both of the above issues have been corrected by Zombie, who swapped the USO map files and changed INTERCEPTION.DAT. You can get these updates from the StrategyCore file section.''[http://www.strategycore.co.uk/files/x-com-terror-from-the-deep/patches/]
* Does not fix the Dart Gun to make it any less utterly useless. Though you can do this yourself via the OBDATA.DAT section of TFTDextender. (Suggestion: don't fix it. The useless Dart Gun is all part of the "oh no we're all gonna die" experience of the beginning of TFTD.)
* Does not improve the armour and effectiveness of the basic Aqua-Jet and Gas Cannon Coelecanths (it does upgrade the Coelecanth/Gauss). (Again, suggestion: this is a good thing - XCOM should start the game hopelessly outclassed, and scramble to catch up).
:''The 'Ablative Armor' mod improves the endurance of the Gas Cannon and Aqua-Jet Coelecanths.''
* Does not allow you to mount weapons on Tritons, or use Barracudas as transport subs. XComUtil can help you cheat in this way.
* Does not allow you to have 360 degree vision out of your sub before exiting it. (What kind of coward would want that?). XComUtil does this.
:''Actually, XComUtil just sets the facing of your soldiers to each vector which gives you full view around the Skyranger. The same thing happens if you have a soldier on the front and back, right and left corners rotate in place 180 degrees on the first turn.''

==FYI==
*The game crashes when I start mission against a sub: "XCOM crashed at 0x7C82A5CD with error 0xC0000005 trying to access 0xFFE00B30."
:It's [[Known_Bugs_(TFTD)#Geoscape_Bugs|an already reported bug]]. What is happening is the Alien Sub is landing on land, and the Triton is also attempting to land on land. Probably the game crashes when it fails to generate the appropriate terrain type? So the GEOSCAPE map/terrain data must be corrupted. I've seen three examples of this. In a couple of cases the landing site is clearly inland, by hundreds of kilometres. In some cases it's right on the sea/land boundary and hard to tell. I have two save games that reproduce the bug now. From memory, the previous cases all happened around North Africa, like these present cases. [[User:Spike|Spike]] 08:31, 9 September 2012 (EDT)
*'''Trojan Horse?''' AVG Anti-Virus reports that TFTDExtender.exe contains a Trojan Horse (Generic30.MKG).
:AVG has been known to produce false positives before. I use AV software on my machine and have checked this by uploading/downloading from a site with its own AV check. In some sense Extender acts like a trojan, in that, it overwrites code in memory, just not in a malicious way.

=Resolved Reported Problems=
*<s>USOs not detected or Alien Missions not appearing with the Geoscape Clock mod enabled</s>
:'''Fixed in version 1.07'''
*<s> Changes to executable name under [loader] section of INI ignored by Extender </s>
:'''Fixed with version 1.061'''
*<s> Save Equipment not working</s>
:'''Fixed in 1.05p4'''
*<s> Weight Issues or "Weightless" Ammo Bug </s>
:'''All fixed in 1.05p4'''
*<s> Items on transport floor lost on Abort</s>
:'''Fixed in 1.05p4'''
*<s> Coelacanth/Gauss mutates into Coelacanth/G.C. after battle</s>
:'''Fixed in 1.05p4'''
*<s> Cannot build Leviathan </s>
:'''Fixed with 1.05p3.2'''
*<s>Mysterious artifacts recovered during aborted missions</s>
:'''Fixed in the 1.05p3.1-'''
*<s>Stunned MC'd Aquanauts MIA on Abort </s>
:'''Fixed in 1.05p2 -'''
**<s> Crewed Flying Sub Lost on Abort </s>
:'''Fixed in 105p4.'''
*<s> Materials deducted from wrong base </s>
:'''Fixed in 1.05p2'''
*<s> OBDATA changes in INI only working in Geoscape </s>
:'''Fixed in 1.05p2.'''
*<s>Displacer/Sonic damage incorrect</s>
*<s> Weight Display in Inventory not Localised </s>
*<s>Grenade Resistance in INI file </s>
*<s>Manufacturing Projects Minimum Production</s>
:In the unmodified game, if you have a manufacturing project underway, you can't reduce the quantity below the level that have been built or are in production now (the number that have been built, plus 1). With the autosell and autobuild features turned on, you need to be able to cursor down below zero, so the quantity cursor no longer stops when you reduce to this minimum. This may have some unintended effects, like changing a manufacturing project to produce less units than it has already reduced. On the other hand there may be no impact at all other than losing the built-in stop on the quantity cursor that reminds you how many units of that type you have already built or started to build. [[User:Spike|Spike]] 22:06, 21 September 2012 (EDT)
:''It would be interesting to experiment to see what the effects of doing this are, if any: What happens if you reduce the number desired for an item below what has already been produced? What happens if you create an order for a set number of items and later change it to auto-produce? [[User:Morgan525|Tycho]]''
:: OK I will take a look at this and report back. Unless some bugs/glitches are being introduced, the only loss of existing functionality is that you can currently use the down arrow keys in the unmodified version to in effect say "stop production after completion of the next unit", which avoids the wasted cost and effort of hitting the Stop Production button. [[User:Spike|Spike]] 04:45, 25 September 2012 (EDT)
:Tested - If I reduce the production quantity of a current production run to less than what as already been produced, the display completion time changes (incorrectly) to 'Indefinite', but production ends after completion of the next unit. So if I start by producing 10 units, wait until I have produced 2, then reduce the quantity to 2 (or probably 1), production stops after 3 units. Thies basically replicates the pre-existing behaviour when using the down arrow on the Quantity, so there has been no loss of functionality with your Mod. Also, Autosell and Autoproduce work normally when applied as changes to an existing production run. The only thing is I can't distinguish them on the Manufacturing display - both say 'unlimited' quantity and 'indefinite' period - is that intended? I suppose it makes sense, but it would be good to be able to tell which kind of production it is, *** Autoproduce or $$$ Autosell. [[User:Spike|Spike]] 08:57, 2 October 2012 (EDT)
:''Autosell should report 'unlimited $' like the pic on the information page. I could change this to '$unlimited$' - [[User:Morgan525|Tycho]]''
:: I think that extra '$' would be helpful. Also, maybe when production is reduced to equal-to or below the already-completed quantity, could you change the quantity display to 'halting' instead of 'indefinite'? [[User:Spike|Spike]] 09:46, 5 October 2012 (EDT)
:''' Changed the output to display "$unlimited$".'''[[User:Morgan525|Tycho]]
:''' Changed the output on duration to read "halting" when changing an order from unlimited to anything above zero. The order will terminate after the next unit is produced. This will be in version 1.08''' [[User:Morgan525|Tycho]]
*TFTD Extender and XComUtil/Error Messages with Bomb Bloke's ComboMod
: Getting TFTDextender to work with XcomUtil has to be handled by XcomUtil: XcomUtil needs to know the filename for TFTDextender.
: I put together a patch for XcomUtil that adds the support, but this was close-ish to the time when TFTDextender was still named TFTDLoader. Which means you still have to rename the extender executable, but it's buried away [http://www.strategycore.co.uk/forums/topic/9751-ufo-tftd-combo-mod-beta/ here] if anyone wants to take a look. I may update it shortly and send it off to Blade again.
: For whatever reason, kryub's fix for the splitter code STILL doesn't prevent an error on exiting the geoscape to the battlescape, but ''only'' if using TFTDextender, and not if you're quitting the game completely. I've been right through the ini and disabled everything I could find (cross checking against the ini ref file, but couldn't find a way to prevent this. Oddly enough it only seems to happen on my XP machine, not my Windows 7 laptop. The error is:
:'''TFTD crashed at 0x7C9102F6 with error 0xC0000005 trying to access 0x00000002'''
:-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 20:04, 24 January 2013 (EST)

::''After using your patch, I managed to get XComUtil to run with TFTD Extender. I'm using Windows XP Home. I get the above error when the program swaps from Geoscape to Battlescape and I get another error upon 'Quit to DOS' [TFTD crashed at 0x1 with error 0xC0000005 trying to access 0x00000001] with any version of TFTD Extender or even Xusalik's TFTDloader. --[[User:Morgan525|Tycho]] 20:26, 26 January 2013 (EST).

:::Note that disabling the debug code entirely is bad, because then the default Windows debugger takes over and that takes ages to load if it's not already in RAM (and of course that still gives you an error pop-up window)... You'd want the Extender to still catch crashes, but then just exit cleanly if it detects one. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 16:58, 29 January 2013 (EST)

::::''I put a new line under the [Loader] section call Debug Messages. If =1, crashes are reported to the player. If =0, debugging still occurs but the player doesn't get any notifications. This fixes both errors that occur with using the split executable when exiting from Geoscape and from the game. In the case of the error on exiting geoscape, Geoscape.exe actually terminates but the extra code that bridges the split executables forces Battlescape to load so it appear seamless. In other situations, I believe the game will break to the desktop or command prompt with no warning. - [[User:Morgan525|Tycho]] 23:36, 1 February 2013 (EST)''

=Feedback =

Please check the [[Known_Bugs_(TFTD)|TFTD Known Bugs]] or [[Known_Bugs|EU Known Bugs]](for bugs common to both games) and post bugs which are part of the original game in the appropriate section. Please post any general suggestions for the game here: [[Wish_List_(TFTD)]].
*Any errors that are a result of the Extender should be posted here.
*Use this section for suggestions and feedback on options currently available in the Extender or to discuss projects in Extender that are under development.

== alternate damage routines ==
:''1)For AP the armor works as it does currently: The armor value is applied as is and damage that is lower than the value is ignored but a hit that penetrates does a little damage to the armor.
:''2)Laser(Gauss) and Plasma(Sonic) attacks have to burn through the armor: The current armor value in the location hit is doubled and then damage is subtracted from this value. The remaining armor value (if any) is halved and saved. For these attack types, armor is stronger but quickly is gone. A soldier in power(ion) armor can take at least one seriously good hit from a heavy plasma(sonic) from the front without damage to the soldier. In testing, I've had a lot of occasions were a soldier in coveralls was able to survive a hit from a plasma pistol, although be seriously wounded. ''
:''3)HE works just like laser and plasma. ''
:''4)Stun damage depends on the weapons used: the stun rod works like an AP attack vs armor (normal game rules), but a stun bomb is applied against the modified armor value.
:''5)IN still works the same. Fire damage is unchanged.''

''Know thy Enemy: This will now affect the damage that is applied against the unit's health:
*''Headshot: full damage
*''Other: If autopsy on this unit type has been done: full damage. Otherwise half damage.

Would it also be worth adding some kind of bonus for Live Alien research? Maybe the negation of some kind of Morale penalty and/or Psi penalty? Fear of the unknown, know your enemy, that kind of thing?

:''I thought about that but the game doesn't record live aliens that have been researched. When you finish research on a live alien, it only follows the routine to unlock the appropriate UFOpaedia articles and then checks to see if the finished research can unlock other topics.'' [[User:Morgan525|Tycho]]

I had a further thought on this while trying to guess what your new pre-requisites are for the various armours. For now it's really cool to be guessing but once people have figured it out, well, it will be more logical but still will have 'replay fatigue'. Would it be possible to randomise the pre-requisites for a lot of the key research topics, from out of a plausible list of items (or even randomise pre-requisite topics)? That would make every game fresh in terms of the research sequence, and make the research aspect of the game more challenging and less dry & predictable. As ever, just a suggestion. :) Cheers, [[User:Spike|Spike]] 16:01, 19 October 2012 (EDT)

==General Tank Modding ==

I see you are interested in modding tanks (HWPs/SWPs) and that's partly what got you into updating UFO Extender. I made some suggestions for Tank Modding myself, including some of the mechanics required to make it work via a config file such as the UFO / TFD Extender config file. For example you could have cargo carrier / ambulance / casevac tanks, you could have demolition tanks, mine thrower tanks, and of course tanks with custom weapons including dual weapons. Could you have a look here: [[User:Spike#Tank_mods]] and see if any of that makes you feel like getting creative?

Thanks,
[[User:Spike|Spike]] 10:46, 3 September 2012 (EDT)

==Deep Colonies==

I am thinking of including an option to set all colonies to be Very Deep. Why would the aliens not do so? It would also delay the progress of the game in that the player would need the armor and subs necessary to get access to the appropriate commanders.

:I suppose so long as it isn't so deep as it requires a Leviathan (which does require a commander), it shouldn't be game-breaking? That would be my only concern with that sort of option. I would assume it would at the very least finally make X-COM require building the intermediate transport? I've never bothered with the Lightning or Hammerhead since they always offered LESS crew space than the default ship, and really didn't offer any major advantage beyond speed, and I was never bothered by having to wait a bit longer for the transport to arrive somewhere if it meant a better-equipped and manned team. They always seemed like such useless transitional craft. You already have the Manta/Firestorm by the time you get it, so you already have something much better for interception, and the smaller crew capacity seemed like shooting yourself in the foot before every mission. --[[User:StormhawkAPS|StormhawkAPS]] 09:07, 9 October 2013 (EDT)

''That's not a problem: Any transport, other than the Triton, can go very deep.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])

==D3D Window Position==

This option in the INI has what I can only describe as 'schizophrenic' behaviour, as, if the initial two numbers do not match (which would make the order of the numbers not matter), the program will interpret them in flip-order and overwrite them in kind every time it is run. To put simply, the window shifts between two locations with every launch. I suspect this may be due to the system or program somehow not respecting the intended number order and reading it backwards for whatever reason. I also notice two more numbers are added to the option line, seemingly to denote the far sides of the window as defined by the resolution dimensions listed in the subsequent lines.

Related to this, the wiki entry seems to not represent the current structure of the settings INI in regards to these particular options, and it might be wise to update it. --[[User:StormhawkAPS|StormhawkAPS]] 16:29, 9 October 2013 (EDT)

''If anyone wants to help update the entries, they can. Please, keep the information on the main page descriptive and save personal opinions for the discussion page.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])

Talk:TFTDextender

2016-03-18T06:58:30Z

Morgan525: /* Minor Bugs */

=Questions or Comments=
'''A place to provide feedback or ask questions:'''
:''Thanks to Kyrub, Spike, and numerous others who help to troubleshoot problems, provide feedback on releases, and innumerable other activities to help make TFTDextender and the game better! -'' [[User:Morgan525|Tycho]]

*The zip archive does not seem to include an .ini file. Where do I get the .ini file from?

:::''If the latest release is a patch, meaning there are no new additions to the INI file, only the patcher.dll file will be updated. In this way, those who already have the current release won't have their INI settings overwritten. You will need to download the last full version, extract the files from it, and then extract file from the latest patch. When I first release the Extender and lots of problems were being reported, I was releasing fixes almost on a weekly basis and so I still continue with this idea.'' [[User:Morgan525|Tycho]]

== Bug Reports ==
===Major Bugs===
*Battlescape Crash when HWP present in non-Base Defense missions
''An error in the code will cause the game to crash. This will be fixed in the next release. For now, it can be avoided by copying the line for 'No Freebies for Tanks' from the bugfix reference file into the [Bug Fix] section of the INI - [[User:Morgan525|Tycho]]''

*Battlescape Crash when alien (Old One) is in fire and "Fire Fix" bugfix is enabled.

:I've got a savegame which makes TFTDextender chocke on the "Fire Fix" bugfix - basically, during a terror map (Fiji, iirc), there's a Deep One on the third level in the house. I've just fired an incendiary round at it, and it's now standing in fire. I end the turn, and when all alien movement is done (presumably this is where the fire-check happens) the game crashes with the error message "TFTD crashed at 0x42E061 with error 0xC0000005 trying to access 0x0051C1C0". Those addresses are the same each crash, so it's a consistent bug.

:Disabling "Fire Fix" before starting TFTD and loading that savegame prevents the crash, and the Deep One dies.

:System is Windows 7 64 bit (up to date with patches and service packs), running on the Steam version of TFTD (but not through steam, obviously).

:I can provide the savegame (the entire GAME_8 folder as a zip) and the TFTDextender.ini in use, in the hopes this will aid in debugging. - [[User:MacGyver|MacGyver]]

::''Thanks MacGyver! It is nice when someone has troubleshot an issue to identify the cause. Just based on your initial report, I found the problem: The TFTD base code differed slightly from EU. I found the offending lines and modified them to fit the TFTD code. The problem was in the section to check if the unit catches fire. - [[User:Morgan525|Tycho]] 10:58, 2 May 2013 (EDT)''

*(a)Lobstermen don't use their guns and (b)their melee attack is weak.
:''The first part(a) is a problem in the fix for the code to determine a unit's abilities in the first step of the AI process. The latter problem (b) is a bug in the original program. If a unit has a ranged weapon, the damage is set to the value of the weapon's melee attack and not the strength of the lobsterman, as it is for all other units that have a natural melee attack.''

*Interception Crash
TFTD latest version (with the 7.2 patch) crashed in Geoscape on the 1st Intercept (subs vs Alien craft). I had already had a tactical combat against a landed craft, but this did not involve an interception. I did notice that the Geoscape Graphs looked strange (faulty) prior to the interception and crash.
Running windowed mode with most things switched on apart from the [ make defense missions harder ] mods. Geoscape and battlefield shortcuts switched [off].

:''If this happens again, please include any error message as well.'' -[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 09:37, 2 June 2015 (EDT)

Latest issue of TFTD full, with the 7.2 patch
I noticed in first tactical game that one of my aquanauts holding a gas cannon had it magically transformed into a sonic pistol (i think from the Deep One I was targetting at the time). Obviously I could not use it as it was my first mission. When I clicked away from the aquanaut and clicked back on him later, the sonic pistol was back to the gas cannon.
:''This sounds like the strangeness that using the '''More Reaction Fire''' mod can introduce. Try playing the game without that mod enabled for a while.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 01:45, 3 June 2015 (EDT)
I also note that even though I only expended 2 shots from each of my gas cannons carrying HE ammo, all my HE ammo was used up at the end of the mission.

TFTD needs the "collect ammo" feature that is used in UFO.
:''TFTD does have the collect ammo feature but it seems it needs more work.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 20:23, 2 June 2015 (EDT)

=== Minor Bugs ===
* I've got a feeling, though I can't check, that "Know Thy Enemy" currently doesn't register that autopsies have been performed - e.g. it shouldn't take 4 or 5 sonic-blasta shots to down a single Gill Man. When I disable "Know Thy Enemy", the game becomes significantly easier, also in missions with creatures on which autopsies have been performed. - [[User:MacGyver|MacGyver]]

''I found the problem and the code is working now. It will be out in the next version.''

* For some reason, the loader (newest version) opens TWO windows at startup. One is titled 'X-COM Terror From the Deep Gold Edition' and contains the game's video output, the other is titled 'Terror From The Deep.exe' and is completely blank (not even a blinking console prompt). Win7 auto-groups their buttons on the taskbar and closing either closes the other too. Is this normal behavior or am I missing something?--[[User:Amitakartok|amitakartok]] 11:47, 24 August 2013 (EDT)
''To my knowledge, this has always been the case even with UFO Extender. The first 'blank' window is the loader which spawns the second 'game' window. Closing the Extender will abort the game and quitting the game automatically closes the Extender.''
:: Well, UFOextender never did that for me, only TFTDextender. Maybe it's due to using an earlier build?--[[User:Amitakartok|amitakartok]] 11:43, 25 August 2013 (EDT)
''It's doesn't happen with UFO. I checked earlier versions and this has been present since the beginning. The command to create the process for the game is different from UFO and the flags don't seem to allow the extender shell window to close. I've tried a few things but either they have no effect or they lock the game as it boots up. Since it is a cosmetic issue and doesn't impact the gameplay, I'm not too concerned with it for now.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])

''I found the reason for the second window and have changed the code to prevent the second window from closing.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 06:58, 18 March 2016 (UTC)

== Things that TFTDextender does not fix ==

Just more or less as a note to the reader, TFTDextender does not fix some of the following things that are sometimes thought of as needing fixing (and this is probably deliberate?):

* Does not fix the apparent swap of the ground map for the VERY SMALL Survey Ship (1 occupant) with the SMALL Escort (half-dozen or more occupants). So you get the VERY SMALL sub occupying about 25 squares of usable area on the Battlescape, and the supposedly larger SMALL sub occupying one square of usable area on the Battlescape, begging the question of how all those aliens got inside there in the first place. XcomUtil will fix this, as will the original patches that XcomUtil incorporates.
* Does not fix the incorrect pictures for the large USO in the interception window.
:''Both of the above issues have been corrected by Zombie, who swapped the USO map files and changed INTERCEPTION.DAT. You can get these updates from the StrategyCore file section.''[http://www.strategycore.co.uk/files/x-com-terror-from-the-deep/patches/]
* Does not fix the Dart Gun to make it any less utterly useless. Though you can do this yourself via the OBDATA.DAT section of TFTDextender. (Suggestion: don't fix it. The useless Dart Gun is all part of the "oh no we're all gonna die" experience of the beginning of TFTD.)
* Does not improve the armour and effectiveness of the basic Aqua-Jet and Gas Cannon Coelecanths (it does upgrade the Coelecanth/Gauss). (Again, suggestion: this is a good thing - XCOM should start the game hopelessly outclassed, and scramble to catch up).
:''The 'Ablative Armor' mod improves the endurance of the Gas Cannon and Aqua-Jet Coelecanths.''
* Does not allow you to mount weapons on Tritons, or use Barracudas as transport subs. XComUtil can help you cheat in this way.
* Does not allow you to have 360 degree vision out of your sub before exiting it. (What kind of coward would want that?). XComUtil does this.
:''Actually, XComUtil just sets the facing of your soldiers to each vector which gives you full view around the Skyranger. The same thing happens if you have a soldier on the front and back, right and left corners rotate in place 180 degrees on the first turn.''

==FYI==
*The game crashes when I start mission against a sub: "XCOM crashed at 0x7C82A5CD with error 0xC0000005 trying to access 0xFFE00B30."
:It's [[Known_Bugs_(TFTD)#Geoscape_Bugs|an already reported bug]]. What is happening is the Alien Sub is landing on land, and the Triton is also attempting to land on land. Probably the game crashes when it fails to generate the appropriate terrain type? So the GEOSCAPE map/terrain data must be corrupted. I've seen three examples of this. In a couple of cases the landing site is clearly inland, by hundreds of kilometres. In some cases it's right on the sea/land boundary and hard to tell. I have two save games that reproduce the bug now. From memory, the previous cases all happened around North Africa, like these present cases. [[User:Spike|Spike]] 08:31, 9 September 2012 (EDT)
*'''Trojan Horse?''' AVG Anti-Virus reports that TFTDExtender.exe contains a Trojan Horse (Generic30.MKG).
:AVG has been known to produce false positives before. I use AV software on my machine and have checked this by uploading/downloading from a site with its own AV check. In some sense Extender acts like a trojan, in that, it overwrites code in memory, just not in a malicious way.

=Resolved Reported Problems=
*<s>USOs not detected or Alien Missions not appearing with the Geoscape Clock mod enabled</s>
:'''Fixed in version 1.07'''
*<s> Changes to executable name under [loader] section of INI ignored by Extender </s>
:'''Fixed with version 1.061'''
*<s> Save Equipment not working</s>
:'''Fixed in 1.05p4'''
*<s> Weight Issues or "Weightless" Ammo Bug </s>
:'''All fixed in 1.05p4'''
*<s> Items on transport floor lost on Abort</s>
:'''Fixed in 1.05p4'''
*<s> Coelacanth/Gauss mutates into Coelacanth/G.C. after battle</s>
:'''Fixed in 1.05p4'''
*<s> Cannot build Leviathan </s>
:'''Fixed with 1.05p3.2'''
*<s>Mysterious artifacts recovered during aborted missions</s>
:'''Fixed in the 1.05p3.1-'''
*<s>Stunned MC'd Aquanauts MIA on Abort </s>
:'''Fixed in 1.05p2 -'''
**<s> Crewed Flying Sub Lost on Abort </s>
:'''Fixed in 105p4.'''
*<s> Materials deducted from wrong base </s>
:'''Fixed in 1.05p2'''
*<s> OBDATA changes in INI only working in Geoscape </s>
:'''Fixed in 1.05p2.'''
*<s>Displacer/Sonic damage incorrect</s>
*<s> Weight Display in Inventory not Localised </s>
*<s>Grenade Resistance in INI file </s>
*<s>Manufacturing Projects Minimum Production</s>
:In the unmodified game, if you have a manufacturing project underway, you can't reduce the quantity below the level that have been built or are in production now (the number that have been built, plus 1). With the autosell and autobuild features turned on, you need to be able to cursor down below zero, so the quantity cursor no longer stops when you reduce to this minimum. This may have some unintended effects, like changing a manufacturing project to produce less units than it has already reduced. On the other hand there may be no impact at all other than losing the built-in stop on the quantity cursor that reminds you how many units of that type you have already built or started to build. [[User:Spike|Spike]] 22:06, 21 September 2012 (EDT)
:''It would be interesting to experiment to see what the effects of doing this are, if any: What happens if you reduce the number desired for an item below what has already been produced? What happens if you create an order for a set number of items and later change it to auto-produce? [[User:Morgan525|Tycho]]''
:: OK I will take a look at this and report back. Unless some bugs/glitches are being introduced, the only loss of existing functionality is that you can currently use the down arrow keys in the unmodified version to in effect say "stop production after completion of the next unit", which avoids the wasted cost and effort of hitting the Stop Production button. [[User:Spike|Spike]] 04:45, 25 September 2012 (EDT)
:Tested - If I reduce the production quantity of a current production run to less than what as already been produced, the display completion time changes (incorrectly) to 'Indefinite', but production ends after completion of the next unit. So if I start by producing 10 units, wait until I have produced 2, then reduce the quantity to 2 (or probably 1), production stops after 3 units. Thies basically replicates the pre-existing behaviour when using the down arrow on the Quantity, so there has been no loss of functionality with your Mod. Also, Autosell and Autoproduce work normally when applied as changes to an existing production run. The only thing is I can't distinguish them on the Manufacturing display - both say 'unlimited' quantity and 'indefinite' period - is that intended? I suppose it makes sense, but it would be good to be able to tell which kind of production it is, *** Autoproduce or $$$ Autosell. [[User:Spike|Spike]] 08:57, 2 October 2012 (EDT)
:''Autosell should report 'unlimited $' like the pic on the information page. I could change this to '$unlimited$' - [[User:Morgan525|Tycho]]''
:: I think that extra '$' would be helpful. Also, maybe when production is reduced to equal-to or below the already-completed quantity, could you change the quantity display to 'halting' instead of 'indefinite'? [[User:Spike|Spike]] 09:46, 5 October 2012 (EDT)
:''' Changed the output to display "$unlimited$".'''[[User:Morgan525|Tycho]]
:''' Changed the output on duration to read "halting" when changing an order from unlimited to anything above zero. The order will terminate after the next unit is produced. This will be in version 1.08''' [[User:Morgan525|Tycho]]
*TFTD Extender and XComUtil/Error Messages with Bomb Bloke's ComboMod
: Getting TFTDextender to work with XcomUtil has to be handled by XcomUtil: XcomUtil needs to know the filename for TFTDextender.
: I put together a patch for XcomUtil that adds the support, but this was close-ish to the time when TFTDextender was still named TFTDLoader. Which means you still have to rename the extender executable, but it's buried away [http://www.strategycore.co.uk/forums/topic/9751-ufo-tftd-combo-mod-beta/ here] if anyone wants to take a look. I may update it shortly and send it off to Blade again.
: For whatever reason, kryub's fix for the splitter code STILL doesn't prevent an error on exiting the geoscape to the battlescape, but ''only'' if using TFTDextender, and not if you're quitting the game completely. I've been right through the ini and disabled everything I could find (cross checking against the ini ref file, but couldn't find a way to prevent this. Oddly enough it only seems to happen on my XP machine, not my Windows 7 laptop. The error is:
:'''TFTD crashed at 0x7C9102F6 with error 0xC0000005 trying to access 0x00000002'''
:-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 20:04, 24 January 2013 (EST)

::''After using your patch, I managed to get XComUtil to run with TFTD Extender. I'm using Windows XP Home. I get the above error when the program swaps from Geoscape to Battlescape and I get another error upon 'Quit to DOS' [TFTD crashed at 0x1 with error 0xC0000005 trying to access 0x00000001] with any version of TFTD Extender or even Xusalik's TFTDloader. --[[User:Morgan525|Tycho]] 20:26, 26 January 2013 (EST).

:::Note that disabling the debug code entirely is bad, because then the default Windows debugger takes over and that takes ages to load if it's not already in RAM (and of course that still gives you an error pop-up window)... You'd want the Extender to still catch crashes, but then just exit cleanly if it detects one. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 16:58, 29 January 2013 (EST)

::::''I put a new line under the [Loader] section call Debug Messages. If =1, crashes are reported to the player. If =0, debugging still occurs but the player doesn't get any notifications. This fixes both errors that occur with using the split executable when exiting from Geoscape and from the game. In the case of the error on exiting geoscape, Geoscape.exe actually terminates but the extra code that bridges the split executables forces Battlescape to load so it appear seamless. In other situations, I believe the game will break to the desktop or command prompt with no warning. - [[User:Morgan525|Tycho]] 23:36, 1 February 2013 (EST)''

=Feedback =

Please check the [[Known_Bugs_(TFTD)|TFTD Known Bugs]] or [[Known_Bugs|EU Known Bugs]](for bugs common to both games) and post bugs which are part of the original game in the appropriate section. Please post any general suggestions for the game here: [[Wish_List_(TFTD)]].
*Any errors that are a result of the Extender should be posted here.
*Use this section for suggestions and feedback on options currently available in the Extender or to discuss projects in Extender that are under development.

== alternate damage routines ==
:''1)For AP the armor works as it does currently: The armor value is applied as is and damage that is lower than the value is ignored but a hit that penetrates does a little damage to the armor.
:''2)Laser(Gauss) and Plasma(Sonic) attacks have to burn through the armor: The current armor value in the location hit is doubled and then damage is subtracted from this value. The remaining armor value (if any) is halved and saved. For these attack types, armor is stronger but quickly is gone. A soldier in power(ion) armor can take at least one seriously good hit from a heavy plasma(sonic) from the front without damage to the soldier. In testing, I've had a lot of occasions were a soldier in coveralls was able to survive a hit from a plasma pistol, although be seriously wounded. ''
:''3)HE works just like laser and plasma. ''
:''4)Stun damage depends on the weapons used: the stun rod works like an AP attack vs armor (normal game rules), but a stun bomb is applied against the modified armor value.
:''5)IN still works the same. Fire damage is unchanged.''

''Know thy Enemy: This will now affect the damage that is applied against the unit's health:
*''Headshot: full damage
*''Other: If autopsy on this unit type has been done: full damage. Otherwise half damage.

Would it also be worth adding some kind of bonus for Live Alien research? Maybe the negation of some kind of Morale penalty and/or Psi penalty? Fear of the unknown, know your enemy, that kind of thing?

:''I thought about that but the game doesn't record live aliens that have been researched. When you finish research on a live alien, it only follows the routine to unlock the appropriate UFOpaedia articles and then checks to see if the finished research can unlock other topics.'' [[User:Morgan525|Tycho]]

I had a further thought on this while trying to guess what your new pre-requisites are for the various armours. For now it's really cool to be guessing but once people have figured it out, well, it will be more logical but still will have 'replay fatigue'. Would it be possible to randomise the pre-requisites for a lot of the key research topics, from out of a plausible list of items (or even randomise pre-requisite topics)? That would make every game fresh in terms of the research sequence, and make the research aspect of the game more challenging and less dry & predictable. As ever, just a suggestion. :) Cheers, [[User:Spike|Spike]] 16:01, 19 October 2012 (EDT)

==General Tank Modding ==

I see you are interested in modding tanks (HWPs/SWPs) and that's partly what got you into updating UFO Extender. I made some suggestions for Tank Modding myself, including some of the mechanics required to make it work via a config file such as the UFO / TFD Extender config file. For example you could have cargo carrier / ambulance / casevac tanks, you could have demolition tanks, mine thrower tanks, and of course tanks with custom weapons including dual weapons. Could you have a look here: [[User:Spike#Tank_mods]] and see if any of that makes you feel like getting creative?

Thanks,
[[User:Spike|Spike]] 10:46, 3 September 2012 (EDT)

==Deep Colonies==

I am thinking of including an option to set all colonies to be Very Deep. Why would the aliens not do so? It would also delay the progress of the game in that the player would need the armor and subs necessary to get access to the appropriate commanders.

:I suppose so long as it isn't so deep as it requires a Leviathan (which does require a commander), it shouldn't be game-breaking? That would be my only concern with that sort of option. I would assume it would at the very least finally make X-COM require building the intermediate transport? I've never bothered with the Lightning or Hammerhead since they always offered LESS crew space than the default ship, and really didn't offer any major advantage beyond speed, and I was never bothered by having to wait a bit longer for the transport to arrive somewhere if it meant a better-equipped and manned team. They always seemed like such useless transitional craft. You already have the Manta/Firestorm by the time you get it, so you already have something much better for interception, and the smaller crew capacity seemed like shooting yourself in the foot before every mission. --[[User:StormhawkAPS|StormhawkAPS]] 09:07, 9 October 2013 (EDT)

''That's not a problem: Any transport, other than the Triton, can go very deep.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])

==D3D Window Position==

This option in the INI has what I can only describe as 'schizophrenic' behaviour, as, if the initial two numbers do not match (which would make the order of the numbers not matter), the program will interpret them in flip-order and overwrite them in kind every time it is run. To put simply, the window shifts between two locations with every launch. I suspect this may be due to the system or program somehow not respecting the intended number order and reading it backwards for whatever reason. I also notice two more numbers are added to the option line, seemingly to denote the far sides of the window as defined by the resolution dimensions listed in the subsequent lines.

Related to this, the wiki entry seems to not represent the current structure of the settings INI in regards to these particular options, and it might be wise to update it. --[[User:StormhawkAPS|StormhawkAPS]] 16:29, 9 October 2013 (EDT)

''If anyone wants to help update the entries, they can. Please, keep the information on the main page descriptive and save personal opinions for the discussion page.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])

Talk:TFTDextender

2016-03-18T06:58:13Z

Morgan525: /* Minor Bugs */

=Questions or Comments=
'''A place to provide feedback or ask questions:'''
:''Thanks to Kyrub, Spike, and numerous others who help to troubleshoot problems, provide feedback on releases, and innumerable other activities to help make TFTDextender and the game better! -'' [[User:Morgan525|Tycho]]

*The zip archive does not seem to include an .ini file. Where do I get the .ini file from?

:::''If the latest release is a patch, meaning there are no new additions to the INI file, only the patcher.dll file will be updated. In this way, those who already have the current release won't have their INI settings overwritten. You will need to download the last full version, extract the files from it, and then extract file from the latest patch. When I first release the Extender and lots of problems were being reported, I was releasing fixes almost on a weekly basis and so I still continue with this idea.'' [[User:Morgan525|Tycho]]

== Bug Reports ==
===Major Bugs===
*Battlescape Crash when HWP present in non-Base Defense missions
''An error in the code will cause the game to crash. This will be fixed in the next release. For now, it can be avoided by copying the line for 'No Freebies for Tanks' from the bugfix reference file into the [Bug Fix] section of the INI - [[User:Morgan525|Tycho]]''

*Battlescape Crash when alien (Old One) is in fire and "Fire Fix" bugfix is enabled.

:I've got a savegame which makes TFTDextender chocke on the "Fire Fix" bugfix - basically, during a terror map (Fiji, iirc), there's a Deep One on the third level in the house. I've just fired an incendiary round at it, and it's now standing in fire. I end the turn, and when all alien movement is done (presumably this is where the fire-check happens) the game crashes with the error message "TFTD crashed at 0x42E061 with error 0xC0000005 trying to access 0x0051C1C0". Those addresses are the same each crash, so it's a consistent bug.

:Disabling "Fire Fix" before starting TFTD and loading that savegame prevents the crash, and the Deep One dies.

:System is Windows 7 64 bit (up to date with patches and service packs), running on the Steam version of TFTD (but not through steam, obviously).

:I can provide the savegame (the entire GAME_8 folder as a zip) and the TFTDextender.ini in use, in the hopes this will aid in debugging. - [[User:MacGyver|MacGyver]]

::''Thanks MacGyver! It is nice when someone has troubleshot an issue to identify the cause. Just based on your initial report, I found the problem: The TFTD base code differed slightly from EU. I found the offending lines and modified them to fit the TFTD code. The problem was in the section to check if the unit catches fire. - [[User:Morgan525|Tycho]] 10:58, 2 May 2013 (EDT)''

*(a)Lobstermen don't use their guns and (b)their melee attack is weak.
:''The first part(a) is a problem in the fix for the code to determine a unit's abilities in the first step of the AI process. The latter problem (b) is a bug in the original program. If a unit has a ranged weapon, the damage is set to the value of the weapon's melee attack and not the strength of the lobsterman, as it is for all other units that have a natural melee attack.''

*Interception Crash
TFTD latest version (with the 7.2 patch) crashed in Geoscape on the 1st Intercept (subs vs Alien craft). I had already had a tactical combat against a landed craft, but this did not involve an interception. I did notice that the Geoscape Graphs looked strange (faulty) prior to the interception and crash.
Running windowed mode with most things switched on apart from the [ make defense missions harder ] mods. Geoscape and battlefield shortcuts switched [off].

:''If this happens again, please include any error message as well.'' -[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 09:37, 2 June 2015 (EDT)

Latest issue of TFTD full, with the 7.2 patch
I noticed in first tactical game that one of my aquanauts holding a gas cannon had it magically transformed into a sonic pistol (i think from the Deep One I was targetting at the time). Obviously I could not use it as it was my first mission. When I clicked away from the aquanaut and clicked back on him later, the sonic pistol was back to the gas cannon.
:''This sounds like the strangeness that using the '''More Reaction Fire''' mod can introduce. Try playing the game without that mod enabled for a while.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 01:45, 3 June 2015 (EDT)
I also note that even though I only expended 2 shots from each of my gas cannons carrying HE ammo, all my HE ammo was used up at the end of the mission.

TFTD needs the "collect ammo" feature that is used in UFO.
:''TFTD does have the collect ammo feature but it seems it needs more work.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 20:23, 2 June 2015 (EDT)

=== Minor Bugs ===
* I've got a feeling, though I can't check, that "Know Thy Enemy" currently doesn't register that autopsies have been performed - e.g. it shouldn't take 4 or 5 sonic-blasta shots to down a single Gill Man. When I disable "Know Thy Enemy", the game becomes significantly easier, also in missions with creatures on which autopsies have been performed. - [[User:MacGyver|MacGyver]]

''I found the problem and the code is working now. It will be out in the next version.''

* For some reason, the loader (newest version) opens TWO windows at startup. One is titled 'X-COM Terror From the Deep Gold Edition' and contains the game's video output, the other is titled 'Terror From The Deep.exe' and is completely blank (not even a blinking console prompt). Win7 auto-groups their buttons on the taskbar and closing either closes the other too. Is this normal behavior or am I missing something?--[[User:Amitakartok|amitakartok]] 11:47, 24 August 2013 (EDT)
''To my knowledge, this has always been the case even with UFO Extender. The first 'blank' window is the loader which spawns the second 'game' window. Closing the Extender will abort the game and quitting the game automatically closes the Extender.''
:: Well, UFOextender never did that for me, only TFTDextender. Maybe it's due to using an earlier build?--[[User:Amitakartok|amitakartok]] 11:43, 25 August 2013 (EDT)
''It's doesn't happen with UFO. I checked earlier versions and this has been present since the beginning. The command to create the process for the game is different from UFO and the flags don't seem to allow the extender shell window to close. I've tried a few things but either they have no effect or they lock the game as it boots up. Since it is a cosmetic issue and doesn't impact the gameplay, I'm not too concerned with it for now.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])
''I found the reason for the second window and have changed the code to prevent the second window from closing.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 06:58, 18 March 2016 (UTC)

== Things that TFTDextender does not fix ==

Just more or less as a note to the reader, TFTDextender does not fix some of the following things that are sometimes thought of as needing fixing (and this is probably deliberate?):

* Does not fix the apparent swap of the ground map for the VERY SMALL Survey Ship (1 occupant) with the SMALL Escort (half-dozen or more occupants). So you get the VERY SMALL sub occupying about 25 squares of usable area on the Battlescape, and the supposedly larger SMALL sub occupying one square of usable area on the Battlescape, begging the question of how all those aliens got inside there in the first place. XcomUtil will fix this, as will the original patches that XcomUtil incorporates.
* Does not fix the incorrect pictures for the large USO in the interception window.
:''Both of the above issues have been corrected by Zombie, who swapped the USO map files and changed INTERCEPTION.DAT. You can get these updates from the StrategyCore file section.''[http://www.strategycore.co.uk/files/x-com-terror-from-the-deep/patches/]
* Does not fix the Dart Gun to make it any less utterly useless. Though you can do this yourself via the OBDATA.DAT section of TFTDextender. (Suggestion: don't fix it. The useless Dart Gun is all part of the "oh no we're all gonna die" experience of the beginning of TFTD.)
* Does not improve the armour and effectiveness of the basic Aqua-Jet and Gas Cannon Coelecanths (it does upgrade the Coelecanth/Gauss). (Again, suggestion: this is a good thing - XCOM should start the game hopelessly outclassed, and scramble to catch up).
:''The 'Ablative Armor' mod improves the endurance of the Gas Cannon and Aqua-Jet Coelecanths.''
* Does not allow you to mount weapons on Tritons, or use Barracudas as transport subs. XComUtil can help you cheat in this way.
* Does not allow you to have 360 degree vision out of your sub before exiting it. (What kind of coward would want that?). XComUtil does this.
:''Actually, XComUtil just sets the facing of your soldiers to each vector which gives you full view around the Skyranger. The same thing happens if you have a soldier on the front and back, right and left corners rotate in place 180 degrees on the first turn.''

==FYI==
*The game crashes when I start mission against a sub: "XCOM crashed at 0x7C82A5CD with error 0xC0000005 trying to access 0xFFE00B30."
:It's [[Known_Bugs_(TFTD)#Geoscape_Bugs|an already reported bug]]. What is happening is the Alien Sub is landing on land, and the Triton is also attempting to land on land. Probably the game crashes when it fails to generate the appropriate terrain type? So the GEOSCAPE map/terrain data must be corrupted. I've seen three examples of this. In a couple of cases the landing site is clearly inland, by hundreds of kilometres. In some cases it's right on the sea/land boundary and hard to tell. I have two save games that reproduce the bug now. From memory, the previous cases all happened around North Africa, like these present cases. [[User:Spike|Spike]] 08:31, 9 September 2012 (EDT)
*'''Trojan Horse?''' AVG Anti-Virus reports that TFTDExtender.exe contains a Trojan Horse (Generic30.MKG).
:AVG has been known to produce false positives before. I use AV software on my machine and have checked this by uploading/downloading from a site with its own AV check. In some sense Extender acts like a trojan, in that, it overwrites code in memory, just not in a malicious way.

=Resolved Reported Problems=
*<s>USOs not detected or Alien Missions not appearing with the Geoscape Clock mod enabled</s>
:'''Fixed in version 1.07'''
*<s> Changes to executable name under [loader] section of INI ignored by Extender </s>
:'''Fixed with version 1.061'''
*<s> Save Equipment not working</s>
:'''Fixed in 1.05p4'''
*<s> Weight Issues or "Weightless" Ammo Bug </s>
:'''All fixed in 1.05p4'''
*<s> Items on transport floor lost on Abort</s>
:'''Fixed in 1.05p4'''
*<s> Coelacanth/Gauss mutates into Coelacanth/G.C. after battle</s>
:'''Fixed in 1.05p4'''
*<s> Cannot build Leviathan </s>
:'''Fixed with 1.05p3.2'''
*<s>Mysterious artifacts recovered during aborted missions</s>
:'''Fixed in the 1.05p3.1-'''
*<s>Stunned MC'd Aquanauts MIA on Abort </s>
:'''Fixed in 1.05p2 -'''
**<s> Crewed Flying Sub Lost on Abort </s>
:'''Fixed in 105p4.'''
*<s> Materials deducted from wrong base </s>
:'''Fixed in 1.05p2'''
*<s> OBDATA changes in INI only working in Geoscape </s>
:'''Fixed in 1.05p2.'''
*<s>Displacer/Sonic damage incorrect</s>
*<s> Weight Display in Inventory not Localised </s>
*<s>Grenade Resistance in INI file </s>
*<s>Manufacturing Projects Minimum Production</s>
:In the unmodified game, if you have a manufacturing project underway, you can't reduce the quantity below the level that have been built or are in production now (the number that have been built, plus 1). With the autosell and autobuild features turned on, you need to be able to cursor down below zero, so the quantity cursor no longer stops when you reduce to this minimum. This may have some unintended effects, like changing a manufacturing project to produce less units than it has already reduced. On the other hand there may be no impact at all other than losing the built-in stop on the quantity cursor that reminds you how many units of that type you have already built or started to build. [[User:Spike|Spike]] 22:06, 21 September 2012 (EDT)
:''It would be interesting to experiment to see what the effects of doing this are, if any: What happens if you reduce the number desired for an item below what has already been produced? What happens if you create an order for a set number of items and later change it to auto-produce? [[User:Morgan525|Tycho]]''
:: OK I will take a look at this and report back. Unless some bugs/glitches are being introduced, the only loss of existing functionality is that you can currently use the down arrow keys in the unmodified version to in effect say "stop production after completion of the next unit", which avoids the wasted cost and effort of hitting the Stop Production button. [[User:Spike|Spike]] 04:45, 25 September 2012 (EDT)
:Tested - If I reduce the production quantity of a current production run to less than what as already been produced, the display completion time changes (incorrectly) to 'Indefinite', but production ends after completion of the next unit. So if I start by producing 10 units, wait until I have produced 2, then reduce the quantity to 2 (or probably 1), production stops after 3 units. Thies basically replicates the pre-existing behaviour when using the down arrow on the Quantity, so there has been no loss of functionality with your Mod. Also, Autosell and Autoproduce work normally when applied as changes to an existing production run. The only thing is I can't distinguish them on the Manufacturing display - both say 'unlimited' quantity and 'indefinite' period - is that intended? I suppose it makes sense, but it would be good to be able to tell which kind of production it is, *** Autoproduce or $$$ Autosell. [[User:Spike|Spike]] 08:57, 2 October 2012 (EDT)
:''Autosell should report 'unlimited $' like the pic on the information page. I could change this to '$unlimited$' - [[User:Morgan525|Tycho]]''
:: I think that extra '$' would be helpful. Also, maybe when production is reduced to equal-to or below the already-completed quantity, could you change the quantity display to 'halting' instead of 'indefinite'? [[User:Spike|Spike]] 09:46, 5 October 2012 (EDT)
:''' Changed the output to display "$unlimited$".'''[[User:Morgan525|Tycho]]
:''' Changed the output on duration to read "halting" when changing an order from unlimited to anything above zero. The order will terminate after the next unit is produced. This will be in version 1.08''' [[User:Morgan525|Tycho]]
*TFTD Extender and XComUtil/Error Messages with Bomb Bloke's ComboMod
: Getting TFTDextender to work with XcomUtil has to be handled by XcomUtil: XcomUtil needs to know the filename for TFTDextender.
: I put together a patch for XcomUtil that adds the support, but this was close-ish to the time when TFTDextender was still named TFTDLoader. Which means you still have to rename the extender executable, but it's buried away [http://www.strategycore.co.uk/forums/topic/9751-ufo-tftd-combo-mod-beta/ here] if anyone wants to take a look. I may update it shortly and send it off to Blade again.
: For whatever reason, kryub's fix for the splitter code STILL doesn't prevent an error on exiting the geoscape to the battlescape, but ''only'' if using TFTDextender, and not if you're quitting the game completely. I've been right through the ini and disabled everything I could find (cross checking against the ini ref file, but couldn't find a way to prevent this. Oddly enough it only seems to happen on my XP machine, not my Windows 7 laptop. The error is:
:'''TFTD crashed at 0x7C9102F6 with error 0xC0000005 trying to access 0x00000002'''
:-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 20:04, 24 January 2013 (EST)

::''After using your patch, I managed to get XComUtil to run with TFTD Extender. I'm using Windows XP Home. I get the above error when the program swaps from Geoscape to Battlescape and I get another error upon 'Quit to DOS' [TFTD crashed at 0x1 with error 0xC0000005 trying to access 0x00000001] with any version of TFTD Extender or even Xusalik's TFTDloader. --[[User:Morgan525|Tycho]] 20:26, 26 January 2013 (EST).

:::Note that disabling the debug code entirely is bad, because then the default Windows debugger takes over and that takes ages to load if it's not already in RAM (and of course that still gives you an error pop-up window)... You'd want the Extender to still catch crashes, but then just exit cleanly if it detects one. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 16:58, 29 January 2013 (EST)

::::''I put a new line under the [Loader] section call Debug Messages. If =1, crashes are reported to the player. If =0, debugging still occurs but the player doesn't get any notifications. This fixes both errors that occur with using the split executable when exiting from Geoscape and from the game. In the case of the error on exiting geoscape, Geoscape.exe actually terminates but the extra code that bridges the split executables forces Battlescape to load so it appear seamless. In other situations, I believe the game will break to the desktop or command prompt with no warning. - [[User:Morgan525|Tycho]] 23:36, 1 February 2013 (EST)''

=Feedback =

Please check the [[Known_Bugs_(TFTD)|TFTD Known Bugs]] or [[Known_Bugs|EU Known Bugs]](for bugs common to both games) and post bugs which are part of the original game in the appropriate section. Please post any general suggestions for the game here: [[Wish_List_(TFTD)]].
*Any errors that are a result of the Extender should be posted here.
*Use this section for suggestions and feedback on options currently available in the Extender or to discuss projects in Extender that are under development.

== alternate damage routines ==
:''1)For AP the armor works as it does currently: The armor value is applied as is and damage that is lower than the value is ignored but a hit that penetrates does a little damage to the armor.
:''2)Laser(Gauss) and Plasma(Sonic) attacks have to burn through the armor: The current armor value in the location hit is doubled and then damage is subtracted from this value. The remaining armor value (if any) is halved and saved. For these attack types, armor is stronger but quickly is gone. A soldier in power(ion) armor can take at least one seriously good hit from a heavy plasma(sonic) from the front without damage to the soldier. In testing, I've had a lot of occasions were a soldier in coveralls was able to survive a hit from a plasma pistol, although be seriously wounded. ''
:''3)HE works just like laser and plasma. ''
:''4)Stun damage depends on the weapons used: the stun rod works like an AP attack vs armor (normal game rules), but a stun bomb is applied against the modified armor value.
:''5)IN still works the same. Fire damage is unchanged.''

''Know thy Enemy: This will now affect the damage that is applied against the unit's health:
*''Headshot: full damage
*''Other: If autopsy on this unit type has been done: full damage. Otherwise half damage.

Would it also be worth adding some kind of bonus for Live Alien research? Maybe the negation of some kind of Morale penalty and/or Psi penalty? Fear of the unknown, know your enemy, that kind of thing?

:''I thought about that but the game doesn't record live aliens that have been researched. When you finish research on a live alien, it only follows the routine to unlock the appropriate UFOpaedia articles and then checks to see if the finished research can unlock other topics.'' [[User:Morgan525|Tycho]]

I had a further thought on this while trying to guess what your new pre-requisites are for the various armours. For now it's really cool to be guessing but once people have figured it out, well, it will be more logical but still will have 'replay fatigue'. Would it be possible to randomise the pre-requisites for a lot of the key research topics, from out of a plausible list of items (or even randomise pre-requisite topics)? That would make every game fresh in terms of the research sequence, and make the research aspect of the game more challenging and less dry & predictable. As ever, just a suggestion. :) Cheers, [[User:Spike|Spike]] 16:01, 19 October 2012 (EDT)

==General Tank Modding ==

I see you are interested in modding tanks (HWPs/SWPs) and that's partly what got you into updating UFO Extender. I made some suggestions for Tank Modding myself, including some of the mechanics required to make it work via a config file such as the UFO / TFD Extender config file. For example you could have cargo carrier / ambulance / casevac tanks, you could have demolition tanks, mine thrower tanks, and of course tanks with custom weapons including dual weapons. Could you have a look here: [[User:Spike#Tank_mods]] and see if any of that makes you feel like getting creative?

Thanks,
[[User:Spike|Spike]] 10:46, 3 September 2012 (EDT)

==Deep Colonies==

I am thinking of including an option to set all colonies to be Very Deep. Why would the aliens not do so? It would also delay the progress of the game in that the player would need the armor and subs necessary to get access to the appropriate commanders.

:I suppose so long as it isn't so deep as it requires a Leviathan (which does require a commander), it shouldn't be game-breaking? That would be my only concern with that sort of option. I would assume it would at the very least finally make X-COM require building the intermediate transport? I've never bothered with the Lightning or Hammerhead since they always offered LESS crew space than the default ship, and really didn't offer any major advantage beyond speed, and I was never bothered by having to wait a bit longer for the transport to arrive somewhere if it meant a better-equipped and manned team. They always seemed like such useless transitional craft. You already have the Manta/Firestorm by the time you get it, so you already have something much better for interception, and the smaller crew capacity seemed like shooting yourself in the foot before every mission. --[[User:StormhawkAPS|StormhawkAPS]] 09:07, 9 October 2013 (EDT)

''That's not a problem: Any transport, other than the Triton, can go very deep.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])

==D3D Window Position==

This option in the INI has what I can only describe as 'schizophrenic' behaviour, as, if the initial two numbers do not match (which would make the order of the numbers not matter), the program will interpret them in flip-order and overwrite them in kind every time it is run. To put simply, the window shifts between two locations with every launch. I suspect this may be due to the system or program somehow not respecting the intended number order and reading it backwards for whatever reason. I also notice two more numbers are added to the option line, seemingly to denote the far sides of the window as defined by the resolution dimensions listed in the subsequent lines.

Related to this, the wiki entry seems to not represent the current structure of the settings INI in regards to these particular options, and it might be wise to update it. --[[User:StormhawkAPS|StormhawkAPS]] 16:29, 9 October 2013 (EDT)

''If anyone wants to help update the entries, they can. Please, keep the information on the main page descriptive and save personal opinions for the discussion page.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])

Talk:GEOSCAPE.EXE

2016-02-27T05:55:25Z

Morgan525: /* HWP weapons data */ added TFTD info

= X-COM Complete Packages =

This entry is only a stub for the moment. We grognards on the wiki ask anyone who has bought one of the new packages to tell us things like:
#Who did you get it from - GamersGate, Steam, or elsewhere? (If it is found that they're both selling the exact same package, we'll say so here.)
#What version of X-COM UFO Defense is included? Probably the Win CE version (below), yes?
#Any trouble installing, or other considerations to keep in mind?
#Any problems versus what you expect from X-COM? (if you played it before, or have been reading this wiki, or whatever)
Et cetera. This info is intended to help those who might buy the packages in the future, and is also intended to tell us old hands what's in the package.

Once we get 3-5 mini-reviews, we'll remove these italicized comments, and collapse reviews into a more "wiki-like" overview. (We'll include a link to the time/version when you posted individual reviews.) So, newcomers who bought the Complete Package, please make a new "Review #(next #)" section below, with a summary review. And see the new [[Talk:GEOSCAPE.EXE#New Bundles]] section for more in-depth Q&A and comments.

If any of you have the ability to make comments on Steam or GamersGate that are tacked onto the new X-COM bundles, please post a comment letting people know about this wiki. '''www.UFOpaedia.org''', loud and proud. It's 1999. We're here to save Earth.

''Thanks, and welcome!''

'''wfames, elliotw2, or other new Complete Package folks - please put your comments under a heading like the one below - thanks!''' -[[User:MikeTheRed|MikeTheRed]] 03:51, 19 January 2009 (CST)

==Review #1 by wfames==

Everything seems fine except for psionics. Soldiers in both original X-Com and TFTD do not seem to gain any Psi Skill for either successful or unsuccessful mind control attempts. MC also never seems to work more than once in any given battle. Makes psionics practically useless. It's still a great game, even with that frustration, though.

==Review #2 by Draco Cracona==

Had MC in TFTD work multiple times in one battle with the steam version and seemed like MC-Str was going up faster with those using it (can check tomorrow night) - they definately got some TUs from just MCing; will try to check out some of the TFTD research bugs soon, although the magnetic navigation is available as soon as ion armour is done iirc, although I do remember needing a lobsterman nav for something, I didn't spend much time going from ion to magnetic ion and I saw no Tasoth Commanders. Seems like UFO still has the very annoying difficulty bug; will try it with Xcomutil soon and see if theres a difference. Not played apocalypse yet. Tried many times with decent MC-skill to MC terror units; never managed it - no idea if this happens in the original too though.

==Review #3 by Muton commander==

I've had the Steam version package for a while, but I've mostly played Apoc or UFO Defense, not TFTD. In Apoc, I've yet to see anything wrong with it so far, and in UFO Defense, It appears to be the original DOS version, as the Blaster Launcher can fire normally, with no Up Waypoint Bug (accidently tested to my dismay and the death of half of my squad). I'm going to go test TFTD more, as it is really what needs or seems to need to most attention on the Wiki.

==Review #4 by Diegoba==

I've just downloaded the package from Direct2Disk.
* Ufo Defense. Version 1.2 running under DOSBox. The installer takes care of all configuration and creates an icon for the game. I noticed some changes in the sounds. The intro seems to have been modified to include sounds from the game (weapons fire, doors opening). Sectoids don't make the high-pitched scream when killed, they sound more like Mutons. Maybe V1.2 is like this and I've never played it before? More on this as I keep playing.

==Review #5 by niffiwan==

I purchased the complete package from GamersGate. As Diegoba said above, the installer took care of everything. The "default" version (i.e. the one that the created icon launches) seems to be DOS 1.4 (running inside Dosbox 0.72) which doesn't seem to match with what elliotw2 found. I say 1.4 because the filesize of geoscape.exe is 382,957 bytes. The readme.txt included in the base XCOM dir says version 1.2?

Anyway, they have also included the Win CE version as they have the following two executables as well, 'UFO Defense.exe' and 'UFO Defense_Patched.exe'. The 1st doesn't seem to work properly on my PC with the intro & menu graphics being garbled but the 2nd seems to work OK (but I haven't tested further than checking that the 'load game' window displays correctly).

'UFO Defense_Patched.exe' is 6,144 bytes & I'd guess that it's just some sort of wrapper for 'UFO Defense.exe'.

I've played a fair bit of the way through a "superhuman" game (which given the version I've now found is really "beginner") and it all seems to work as expected. No hassles with the install or configuration. Everything seems to match what the wiki says. Unlike wfames the Psi skill seems to be increasing normally for the soldiers in my game. --[[User:Niffiwan|Niffiwan]] 06:06, 15 February 2010 (EST)

===Note on x_patched.exe===

The patched EXE found in many of the packages is f0ders XCLoader.exe. This is a wrapper that patches in memory the way the games interact with Direct X. This resolves corrupt graphics. --[[User:BladeFireLight|BladeFireLight]] 18:05, 15 February 2010 (EST)

==Review #6 by ciago==

Bought the game from Gamestop Now. It installed using DOSBox v.72 and works great. Seem slightly more difficult than I expected, but I'm sure that's just newbie inexperience. However, it installed the game under 2K Games/X-COM UFO Defense and I cannot find a way to get the XCOMHack at http://www.stonepool.com/xcom/ to work. It tells me to find the save game directory but no matter where I select it won't accept it. If anyone knows how to fix this, let me know. If you don't need to mess with the save games, Gamestop Now works great! [[User:Ciago92|Ciago92]] 18:16, 4 September 2012 (EDT)

:XcomHack is an old application that probably does not understand long path names, including path names with spaces in them. Try installing and running XcomHack in the actual XCOM directory, then you can specify the path to save game files as '''.\GAME_1''' etc (don't forget the initial dot). If that fails, copy the save game directory you want to work on to C:\TEMP\game_1 (etc) and then copy it back. Or use XcomUtil, which does most of the same things (not all), and more. Enjoy! [[User:Spike|Spike]] 20:16, 4 September 2012 (EDT)

::If it will only let you browse for the directory, you may be in trouble. Otherwise, try what Spike says. Another trick is that long file and directory names also have hidden short names... "C:\Documents and Settings" is also "C:\DOCUME~1". You can see them in a DOS command box (/Start /Run COMMAND[Enter], then type "DIR /X"). You can see where the savegames are, right? -[[User:MikeTheRed|MikeTheRed]] 23:21, 4 September 2012 (EDT)

I just remembered something: Some bitmaps are stored in the executable. I think one such bitmap belongs to the Geoscape side bar. If the offsets for this can be located in the executable, you should be able to sign it off as an irrelevant section if you're hunting for particular variables in the executable.

But that's the hard part. Where do you look? And what image width are we looking at?

I once tried creating a program that took in an offset number, a line width number and how many bytes you want displayed from then on as the parameters. It would then open up one of the executables and draw the bytes on the screen as a bitmap of sorts. Kind of never got off the ground - I got distracted and now a year has passed and all my programming knowledge has gone into a vegetative state. I wonder if a program like this would be useful in locating tables or images in the file?

- [[User:NKF|NKF]]

----

The Geoscape side bar? Isn't that in [[GEOBORD.SCR]]?

Regardless, something to mask out known offsets in the file would certainly come in handy.

- [[User:Bomb Bloke|Bomb Bloke]] 22:41, 21 October 2006 (PDT)

== Offsets ==

This page is going to get rather long if we explain in detail all of the offsets here. I don't know if we should merge the Alien stats to the [[Alien Stats]] page or make a new page for it?

Also technically the Weapon stats are stored in Tactical so probably should be put on that page.

I've found some other offsets and if I keep digging I'm sure I'll find more. See my talk page for a mock-up of what I'm thinking for the format. [[User:Pi Masta|Pi Masta]] 15:21, 12 March 2007 (PDT)

:Well, in terms of length, it is (or is going to be) much like other game files: lots and lots of offsets, and their descriptions. It's not a page a casual player is going to reference.--[[User:Ethereal Cereal|Ethereal Cereal]] 15:56, 12 March 2007 (PDT)

Added the Detection Range offsets that Seb76 found. By the way fwiw my view is that only technically minded people will be looking at the wiki entry for a game save file so it's ok to fill this page with a lot of offsets. [[User:Spike|Spike]] 16:13, 9 March 2008 (PDT)
----
Well then, if you don't mind about huge posts, I guess it is a good place to put some stuff I discovered with static dissassembly of the executable [before my hard drive burns down ;)], some info may already be known (gold edition, sorry about the crude format...):

===Damage modifiers===
.data:0046DE74 Incendiary 64h,64h,50h, 0,28h,46h,46h,64h, 0,50h,AAh,64h,64h,64h; 0
.data:0046DE90 HiEx 64h,64h,64h,64h,4Bh,64h,64h,64h,82h,64h,64h,50h,3Ch,50h; 0
.data:0046DEAC Laser 64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,96h,64h,46h; 0
.data:0046DEC8 Plasma 64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,50h,64h,46h; 0
.data:0046DEE4 Stun 64h,64h,5Ah,50h,64h,64h,50h,64h,64h,5Ah,64h,64h,64h, 0; 0
.data:0046DF00 Melee 64h,78h,64h,64h,5Ah,64h,64h,64h,64h,64h,64h,64h,64h,64h; 0
.data:0046DF1C Acid 64h,A0h,6Eh,64h,28h,64h,64h,64h,64h,64h,64h,64h,64h,64h; 0

===HWP weapons data===
00 02 04 06 08 0A 0C 0E 10 12 TFTD Equivalent
.data:0046D57C tank cannon 0, 4, 3Ch, 3Ch, 21h, 0, 0, 5Ah, 50h, 0 Tank/harpoon
.data:0046D tank rocket 2, Ch, 55h, 37h, 2Dh, 0, 0, 73h, 4Bh, 0 Tank/Torpedo
.data:0046D tank laser 3, 11h, 6Eh, 32h, 21h, 0, 0, 55h, 4Bh, 0 Tank/Gauss
.data:0046D tank plasma 4, 24h, 6Eh, 56h, 1Eh, 0, 0, 64h, 3Ch, 0 Triscene/BioDrone/Displacer
.data:0046D blaster bomb 2, 28h, 8Ch, 0, 0, 0, 0, 78h, 50h, 1 Displacer/PWT
.data:0046D acid spit 7, 26h, 8Ch, 4Bh, 1Eh, 0, 0, 6Eh, 3Ch, 0
.data:0046D cyberdisk 4, 22h, 82h, 4Bh, 1Eh, 0, 0, 6Eh, 3Ch, 0 Xarquid
.data:0046D sectopod 3, 22h, 64h, 4Bh, 1Eh, 32h, 23h, 6Eh, 3Ch, 0 Deep One

The structure is:
00 damage type 0A autoshot accuracy
02 ammo type 0C autoshot TU
04 damage 0E aimshot accuracy
06 snapshot accuracy 10 aimshot TU
08 snapshot TU 12 guided weapon

----------
People were asking about the location where the ammo amount is passed to TACTICAL.
For the Tank/Cannon:
44ED20 74 11 66 85 C0 75 06 C6 45 76 1E EB 0A C6 45 76
the Rocket launcher and FBL:
44ED30 08 EB 04 C6 45 76 FF 33 FF C7 44 24 28 04 00 00

There are several other places that must be altered to adjust base inventory properly.
-[[User:Morgan525|Tycho]]

===Funding countries borders polylines===
.data:00474AD4 GeoBordersData dw 0FFFFh ; DATA XREF: GeoDrawBorders+3�r
.data:00474AD4 ; GeoDrawBorders+C�o
.data:00474AD6 dw 221h
.data:00474AD8 dw 0FF43h
.data:00474ADA dw 238h
.data:00474ADC dw 0FF3Dh
.data:00474ADE dw 22Ch
.data:00474AE0 dw 0FF28h
.data:00474AE2 dw 233h
.data:00474AE4 dw 0FF1Fh
.data:00474AE6 dw 236h
...
TFDT-CE(CRC32:C2F6C035): 0x0008AE00..0x0008B00F. 
use: rivers instead of country borders. 
data: lon,lat,lon,lat.. streams, Flags: lon = -1(NewLine), lon = -2(EndOfSection).

===Funding countries names coordinates===
.data:00474DF8 GeoCountryNamesData dw 280h ; DATA XREF: GeoDrawCountryNames+6�o
.data:00474DFA dw 0FF40h
.data:00474DFC dw 263h
.data:00474DFE dw 0B30h
.data:00474E00 dw 0FE53h
.data:00474E02 dw 25Ch
.data:00474E04 dw 0B2Ch
.data:00474E06 dw 0FEABh
.data:00474E08 dw 260h
.data:00474E0A dw 14h
.data:00474E0C dw 0FE8Ch
...
TFDT-CE(CRC32:C2F6C035): 0x0008B010..0x0008B06F. ((16*2)*3:lon,lat,Nid)

===Craft type data===
Craft type known fields: (14 x 2-byte dwords per record)
00000000 structCraftData struc ; (sizeof=0x1C)
00000000 nameIdx reference to the ENGLISH.DAT entry
00000002 scoreDestroyed ; base 10
00000004 weaponPods ''always 2 for UFOs. is this used for UFOs? how?''
00000006 maxSpeed ''in knots'' ; base 10
00000008 acceleration
0000000A fuelCapacity ; base 10
0000000C damageCapacity ; base 10
0000000E ufoSize ''5 - Very Small / 4 - Small (inc. XCom) / 3 - Medium / 2 - Large / 1 - Very Large -spike''
00000010 ufoReload ''UFO only. Firing interval (rand(x-(diff*2))+(x-(diff*2)).
Values: 56=S/MSct 48=LSct/Abd 32=Harv 24=Suppl/Terr/BS. -spike''
00000012 ufoEscapeTime ''100~200% = time before UFO attempts escape (on Beginner) - Volutar.
Values: SS=200 MS=250 LS=300 A=500 H=500 TS=2000 BS=4000 SS=3000 -spike''
00000014 ufoPower ''alien weapon distance in km*8 -kyrub/spike''
00000016 ufoRange ''alien weapon damage (0%-100%) -Morgan525/Tycho''
00000018 TroopSpace ''Troop capacity ''
0000001A HWPSpace ''HWP capacity ''
0000001C structCraftData ends

While the 9th [dword] could be UFO weapon Accuracy or even rate of fire, it seems unlikely. All the values are a multiple of 8 just like distance, so it may be related to that. That's my guess. I'm sure someone like Seb would know more. --[[User:Zombie|Zombie]] 23:56, 4 July 2009 (EDT)

:Sorry I didn't sign those theory guesses, I will do so now. Actually, evidence is building up that the byte at 0x10 within structCraftData is an inverse co-factor - i.e. a divisor - of the net total damage output of UFO attacks. In other words, it could well be a firing interval value such as is seen for XCom craft weapons. I have done 3-4 sets of ten tests so far (XCom craft survival-time tests, deducing UFO damage output). 1 set was for Medium Scout vs Interceptor, 2 sets were for Terror Ship vs Avenger. (I also did multiple attacker sets but those are harder to compare directly to this scenario). So far all 3 test sets are a reasonably good fit for this formula:

UFO net damage output =
<big>(</big>Weapon power x 75% ''(avg of randomisation)'' x 2/3 ''(accuracy)'' <big>)</big>
x <big>(</big> time ''(in game seconds)'' / 0x10 offset ''(firing interval)'' <big>)</big>

: What I want to do next is take one or both of those test scenarios, hack the 0x10 offset up or down, and see if the observed damage output varies inversely. If so, I think that will be pretty strong evidence. Even in my data, there is definitely still also some variation going on that is not fully accounted for in the formula above. As you say it is interesting the 0x10 values are all multiples of 8, suggesting distances. I will keep testing and see what I come up with! Cheers, [[User:Spike|Spike]] 06:39, 5 July 2009 (EDT)

I'm enclined to agree with the rate of fire theory. A countdown is stored in [[CRAFT.DAT]] at offset 0x26 and when it hits 0, the UFO fires. It is reset for the next shot with this formula:
tmp = offset10-2*difficultyLevel
nextShot = RAND(0,tmp)+tmp

Edit: Although the attack type does not appear here, I suspect that while a missile is "traveling", the countdown is not changed. As a result, closer ranges means higher rates of fire. [[User:Seb76|Seb76]] 07:36, 5 July 2009 (EDT)

:Excellent timing Seb! I was just about to start my tests. I could've coped with the random element, since I'm only measuring averages over time, but the presence of a 2nd factor (difficultyLevel), I was not expecting. It would have completely thrown my numbers. Also I might've crashed the game since I'd set offset10 to 0x08 on difficulty level Superhuman (=5?), creating a negative rate of fire! For simplicity I might do my tests on Beginner from now on, and repeat the earlier tests on Beginner.

:It's interesting that you don't see any reference to Attack Mode. So the changing rate of fire could indeed be a "Space Invaders Effect" as you say. Perhaps the reason this is not seen for cannon fire is that cannon fire is resolved instantly, whereas missiles are plotted as objects on the map? Is there any indication that missiles and cannon are handled differently by these routines?

:My test scenarios are probably too simplistic at the moment. But, I am sure I am seeing different rates of fire for missiles at the same range, dependent on whether they are in Standard or Cautious attack mode. I will recheck this. [[User:Spike|Spike]] 08:07, 5 July 2009 (EDT)

:Seb, I realise your formula above for variable firing intervals, from 100%-200% of the base value, explains the 2/3 factor I found which I thought might be UFO Accuracy. The average of a 100-200% range is 1.5, and the inverse of this is 2/3. So perhaps there is no accuracy factor in UFO weapon damage at all. Possibly you just have a base damage and a base firing interval, plus a 50%-100% variation on the base damage and a 100%-200% variation on the firing interval. This would certainly match the data I have so far.
[UFOs have a 60% accuracy with no variation depending upon difficulty level. Damage is 0-100%.--[[User:Morgan525|Tycho]] 00:07, 16 April 2012 (EDT)]

:I have done a couple of tests of varying this offset 0x10 value and they show the right "sign": increasing this value decreases UFO damage output over time, and decreasing this value increases UFO damage output. The effect is strong, and approximately linear, i.e. halving the value roughly doubles the damage, etc (testing on Superhuman). To quantify it more exactly I need to go back and control for Difficulty Level which I did not expect to be a variable. I'm also going to control for the time taken for the UFO to close into firing range - by increasing the UFO weapon range in the tests to 70 or 75km.

:One thing that is worrying me though is that the firing interval is random. Since I'm using the firing interval of a cannon as my "timer" to measure the duration of all other events, it means I'm measuring with a yardstick that randomly changes size. I have to hope that my sample sizes are large enough that the averages will dominate over the fluctuations.

:More worrying is the idea that rate of fire varies with range (as opposed to with Attack Mode). That would be an elastic yardstick, worse than a random one. I thought I had disproved this but I need to go back and do it again, more carefully. I need to test the same weapon at the same range with different attack modes, again. I may well be guilty of building my hypothesis into my test scenario as an assumption! I will also double check the assumption that hacking the firing interval values for XCom weapons has no effect. I'm pretty sure that, even if the absolute firing interval changes with range, the relative ratios of firing interval when comparing different weapons, does not change. But I'll double check.

:In the code, do you see any evidence of cannon-type weapons being treated differenly from missile weapons? For example, do cannon rounds not "travel"? Also, do you see the same '''rnd (0,tmp) + tmp''' function being applied to the firing interval of XCom air attacks? Regards, [[User:Spike|Spike]] 14:30, 5 July 2009 (EDT)
[Interestingly, cannon rounds are treated just like missiles: They have a speed delta that is added to the speed delta of the Xcraft. Since the range of a cannon is so small it is almost an instant hit. Laser Cannon and Plasma cannon fire hits are resolved instantly once the fire delay timer reaches zero.--[[User:Morgan525|Tycho]] 00:07, 16 April 2012 (EDT)]

::Canon-type and missile weapons treated absolutely the same way. There are array of 26 launched projectiles for the left and 26 for the right craft weapons. Thus only 52 missiles can be in-the-fly mode. Cannon weapon uses this "burst mode" at maximum potential, others - not. Though, you can patch built-in xcom craft weapon characteristics with reload time set to minimum delay, and see how it go.--[[User:Volutar|Volutar]] 06:24, 3 October 2011 (EDT)
----
Builtin craft field 0x12 (ufoUnknown) actually works as craft parameter of how much time before alien craft tries to escape from pursue.
The formula of this time is
UfoCraft->EscapeTimer_Field_28 = craftbuiltin->ufoManeuverability_Field_12
+ RAND(0,craftbuiltin->ufoManeuverability_Field_12) - 30*difficulty_level;
--[[User:Volutar|Volutar]] 02:45, 14 April 2011 (EDT)

===Base components data===
.data:00470640 baseElements baseComponentStruct <249h, 300, 1, 4, 0, 0, 5>; 0
.data:00470640 ; DATA XREF: BaseEditDrawSideBar_sub_432EF0+12D�r
.data:00470640 ; BuildFacilities+74�o ...
.data:00470640 baseComponentStruct <24Ah, 400, 16, 10, 1Eh, 0, 4>; 1
.data:00470640 baseComponentStruct <24Bh, 750, 26, 30, 0Ah, 0, 4>; 2
.data:00470640 baseComponentStruct <24Ch, 800, 32, 35, 32h, 0, 4>; 3
.data:00470640 baseComponentStruct <24Dh, 500, 12, 10, 0, 0, 5>; 4
.data:00470640 baseComponentStruct <24Eh, 800, 25, 15, 0, 0, 4>; 5
.data:00470640 baseComponentStruct <24Fh, 200, 16, 5, 0, 3201F4h, 5>; 6
.data:00470640 baseComponentStruct <250h, 150, 10, 5, 0FAh, 0, 4>; 7
.data:00470640 baseComponentStruct <251h, 400, 18, 15, 0Ah, 0, 4>; 8
.data:00470640 baseComponentStruct <252h, 400, 24, 10, 0, 3C0258h, 0Ah>; 9
.data:00470640 baseComponentStruct <253h, 600, 34, 12, 0, 460384h, 0Ah>; 10
.data:00470640 baseComponentStruct <254h, 800, 34, 14, 0, 5004B0h, 0Ah>; 11
.data:00470640 baseComponentStruct <255h, 1200, 38, 15, 0, 0, 9>; 12
.data:00470640 baseComponentStruct <256h, 1300, 33, 5, 0, 0, 9>; 13
.data:00470640 baseComponentStruct <257h, 750, 24, 16, 0Ah, 0, 8>; 14
.data:00470640 baseComponentStruct <258h, 1400, 26, 30, 0, 0, 9>; 15
.data:00470640 baseComponentStruct <259h, 200, 25, 25, 1, 0, 4>; 16
fields:
00000000 baseComponentStruct struc ; (sizeof=0x10)
00000000 stringId dw ?
00000002 cost dw ? ; base 10
00000004 constructionTime db ? ; base 10
00000005 maintenance db ? ; base 10
00000006 anonymous_4 dw ?
00000008 anonymous_5 dd ?
0000000C anonymous_8 dd ?
00000010 baseComponentStruct ends

===Alien missions data===
(I made another post for this one in missions.dat):
.data:00470E70 alienMissionData structAlienMission <5, 1, 0, 12Ch> ; 0
.data:00470E70 ; DATA XREF: SpawnAlienShip+10D�r
.data:00470E70 ; UpdateAlienMissions+78�r ...
.data:00470E70 structAlienMission <6, 1, 2, 104h> ; 1 ;
.data:00470E70 structAlienMission <7, 2, 4, 12Ch> ; 2 ;
.data:00470E70 structAlienMission 5 dup(<0FFFFh, 0FFFFh, 0FFFFh, 0FFFFh>); 3
...
fields:
00000000 structAlienMission struc ; (sizeof=0x8)
00000000 ufoType dw ?
00000002 numUfoToSpawn dw ?
00000004 unknown dw ?
00000006 timeCounter dw ?
00000008 structAlienMission ends

===Ground patches===
(used to spawn locations on continents):
.data:00471278 randPlaces structArea <640h, 0FDF8h, 0A0h, 28h> ; 0
.data:00471278 ; DATA XREF: GetRandomPositionOnContinent+2D�r
.data:00471278 ; GetRandomPositionOnContinent+46�r ...
.data:00471278 structArea <730h, 0FDF8h, 0F0h, 50h> ; 1
.data:00471278 structArea <8C0h, 0FE70h, 50h, 50h> ; 2
.data:00471278 structArea <730h, 0FE70h, 0A0h, 50h> ; 3
.data:00471278 structArea <820h, 0FE70h, 0A0h, 50h> ; 4
.data:00471278 structArea <730h, 0FEC0h, 0A0h, 50h> ; 5
.data:00471278 structArea <7D0h, 0FEC0h, 0B0h, 60h> ; 6
.data:00471278 structArea <870h, 0FEB0h, 0A0h, 88h> ; 7

00000000 structArea struc ; (sizeof=0x8)
00000000 xstart dw ?
00000002 ystart dw ?
00000004 width dw ?
00000006 height dw ?
00000008 structArea ends

-------

Some expansion on Seb's data above - thanks to kyrub for explaining this structure to me, it's been very nearly a year since so it's probably about time I documented it somewhere. ;)

This area of the executable, starting at 0x71278 for EU/CE or 0x7BA70 for TFTD/CE, defines the comings and goings of alien ships. It's divided up into 720 records of four two-byte signed integers each (5,760 bytes for the entire table).

The records are first divided up into groups of sixty, one for each of the first twelve regions in each game:

{| class="wikitable"
|-
!
!UFO:EU
!TFTD
|- valign="top"
!0
|North America
|North Atlantic
|- valign="top"
!1
|Arctic
|South Atlantic
|- valign="top"
!2
|Antarctica
|North Pacific
|- valign="top"
!3
|South America
|South Pacific
|- valign="top"
!4
|Europe
|Mediterranean
|- valign="top"
!5
|North Africa
|South China Sea
|- valign="top"
!6
|Southern Africa
|Indian Ocean
|- valign="top"
!7
|Central Asia
|Sea of Japan
|- valign="top"
!8
|South East Asia
|North Sea
|- valign="top"
!9
|Siberia
|Caribbean
|- valign="top"
!10
|Australasia
|Antarctic
|- valign="top"
!11
|Pacific
|Arctic
|- valign="top"
!12
!North Atlantic
!Eurasia
|- valign="top"
!13
!South Atlantic
!North America
|- valign="top"
!14
!Indian Ocean
!Africa
|-
|}

The last three regions (12 to 14) aren't covered by this table. Nor are they handled by [[ZONAL.DAT]], which tracks where aliens will concentrate their attacks each month, nor in [[XBASES.DAT]], which tracks within which regions they have discovered your bases. Suggesting that planting bases in those last three areas may somehow make you immune from attack. They're pictured [[User:Mvgulik|here]] should anyone wish to test this out.

Anyway, the groups of sixty are further divided up into groups of ten, according to the type of alien activity intended to take place there:

{| class="wikitable"
|-
!
!Purpose
|- valign="top"
!0
|After spawning on the map in an area from 5, most UFOs will fly to an area in this set, then turn and head to their actual destination. After landing, the UFO will usually leave the map through an area in set 5, but some instead return here then go to another landing zone first. Base supply missions don't go here, they go straight to the base they intend to supply. Retaliation missions may or may not go here, they seem to randomly bounce between areas from sets 0-4 before leaving through set 5 (possible pattern of 1-2-3-4-0-5?).
|- valign="top"
!1
|Landing zones for most alien mission types. UFOs usually either land in one of these areas, or one from set 2.
|- valign="top"
!2
|Landing zones for most alien mission types. UFOs usually either land in one of these areas, or one from set 1.
|- valign="top"
!3
|Vast majority of areas defined here are cities (width/height of zero). Infiltration ships occasionally land here. Not all terror ships land on cities, some opt to land/fly around sets 1/2, but actual terror mission where you fight in a city only happen here.
|- valign="top"
!4
|Alien base building areas, and rarely, infiltration landing zones (these are mostly in remote areas).
|- valign="top"
!5
|This defines where UFOs may enter/exit the map. After spawning, most UFOs (except supply/retaliation ships) head to an area from set 0.
|-
|}

So once the UFO has picked a region and a mission type, it then randomly chooses one of the ten records available, and this is used to work out where it'll land. Each record defines a small rectangular area on the world map, and the UFO simply chooses a random destination somewhere within that space. The vast majority of terror mission targets have an area width/height of 0, meaning that the alien ship will always end up landing on the exact same point.

{| class="wikitable"
|-
!Offset
!Use
|- valign="top"
!0-1
|X co-ord of the top left corner. If this value is 0xFFFF, then the record is ignored (unused).
|- valign="top"
!2-3
|Y co-ord of the top left corner. A negative number if north of the equator.
|- valign="top"
!4-5
|Width of the rectangular area.
|- valign="top"
!6-7
|Height of the rectangular area.
|-
|}

The width of the world map is 2880 points. The height ranges from -720 to 720 (1440 points, half the width). ''Lots'' of records are unused. UFO:EU has great big areas plonked down (leading to a lot of diversity in terms of where UFOs might land), TFTD has tiny little ones (meaning USOs tend to land close to where all the other USOs landed).

-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 05:07, 10 April 2012 (EDT)

===Zones sectors===
(used to get the zone number for a world coordinate):
.data:00474F38 geo_globe_zones structGlobeZone <618h, 987h, 0FDD0h, 0FE47h, 0>; 0
.data:00474F38 ; DATA XREF: GetWorldZoneFromPos+10�o
.data:00474F38 structGlobeZone <730h, 987h, 0FE48h, 0FF0Fh, 0>; 1
.data:00474F38 structGlobeZone <780h, 95Fh, 0FF10h, 0FFAFh, 0>; 2
.data:00474F38 structGlobeZone <0, 0B3Fh, 0FD30h, 0FDCFh, 1>; 3
.data:00474F38 structGlobeZone <0, 0B3Fh, 1E0h, 2D0h, 2>; 4
.data:00474F38 structGlobeZone <870h, 9D7h, 0FFB0h, 0FFFFh, 3>; 5
.data:00474F38 structGlobeZone <898h, 0A4Fh, 0, 77h, 3>; 6
.data:00474F38 structGlobeZone <898h, 0A27h, 78h, 1DFh, 3>; 7
.data:00474F38 structGlobeZone <0A78h, 1DFh, 0FDD0h, 0FEE7h, 4>; 8
.data:00474F38 structGlobeZone <0A78h, 13Fh, 0FEE8h, 0FF87h, 5>; 9
.data:00474F38 structGlobeZone <0A78h, 1B7h, 0FF88h, 0FFFFh, 5>; 10
.data:00474F38 structGlobeZone <28h, 1B7h, 0, 13Fh, 6> ; 11
.data:00474F38 structGlobeZone <140h, 22Fh, 0FEE8h, 0FF87h, 7>; 12
.data:00474F38 structGlobeZone <1E0h, 2CFh, 0FE70h, 0FEE7h, 7>; 13
.data:00474F38 structGlobeZone <230h, 2CFh, 0FEE8h, 0FFD7h, 7>; 14
.data:00474F38 structGlobeZone <2D0h, 347h, 0FE70h, 4Fh, 8>; 15
.data:00474F38 structGlobeZone <348h, 4AFh, 0FE70h, 0FFD7h, 8>; 16
.data:00474F38 structGlobeZone <1E0h, 59Fh, 0FDD0h, 0FE6Fh, 9>; 17
.data:00474F38 structGlobeZone <348h, 59Fh, 0FFD8h, 18Fh, 0Ah>; 18
.data:00474F38 structGlobeZone <5A0h, 617h, 0FDD0h, 0FE47h, 0Bh>; 19
.data:00474F38 structGlobeZone <5A0h, 72Fh, 0FE48h, 0FF0Fh, 0Bh>; 20
.data:00474F38 structGlobeZone <5A0h, 77Fh, 0FF10h, 0FFAFh, 0Bh>; 21
.data:00474F38 structGlobeZone <5A0h, 86Fh, 0FFB0h, 0FFFFh, 0Bh>; 22
.data:00474F38 structGlobeZone <5A0h, 897h, 0, 1DFh, 0Bh>; 23
.data:00474F38 structGlobeZone <4B0h, 59Fh, 0FE70h, 0FFD7h, 0Bh>; 24
.data:00474F38 structGlobeZone <988h, 0A77h, 0FDD0h, 0FF0Fh, 0Ch>; 25
.data:00474F38 structGlobeZone <960h, 0A77h, 0FF10h, 0FFAFh, 0Ch>; 26
.data:00474F38 structGlobeZone <9D8h, 0A77h, 0FFB0h, 0FFFFh, 0Ch>; 27
.data:00474F38 structGlobeZone <0A50h, 27h, 0, 77h, 0Dh>; 28
.data:00474F38 structGlobeZone <0A28h, 27h, 78h, 1DFh, 0Dh>; 29
.data:00474F38 structGlobeZone <28h, 1B8h, 140h, 1DFh, 0Dh>; 30
.data:00474F38 structGlobeZone <1B8h, 22Fh, 0FF88h, 4Fh, 0Eh>; 31
.data:00474F38 structGlobeZone <230h, 2CFh, 0FFD8h, 4Fh, 0Eh>; 32
.data:00474F38 structGlobeZone <1B8h, 347h, 50h, 1DFh, 0Eh>; 33

Same for country zones:
.data:00475090 geo_glob_country_zones structGlobeZone <758h, 7F8h, 0FE78h, 0FF00h, 0>; 0
.data:00475090 ; DATA XREF: GetCountryFromPos+11�o
.data:00475090 structGlobeZone <7F8h, 8ACh, 0FE78h, 0FF18h, 0>; 1
.data:00475090 structGlobeZone <820h, 848h, 0FF18h, 0FF30h, 0>; 2
.data:00475090 structGlobeZone <8A8h, 8C0h, 0FF00h, 0FF38h, 0>; 3
.data:00475090 structGlobeZone <8ACh, 8F0h, 0FEA0h, 0FF00h, 0>; 4
.data:00475090 structGlobeZone <8F0h, 924h, 0FE94h, 0FEC0h, 0>; 5
.data:00475090 structGlobeZone <0F0h, 190h, 0FDD0h, 0FE98h, 1>; 6
.data:00475090 structGlobeZone <0C0h, 0F0h, 0FE20h, 0FEB0h, 1>; 7
.data:00475090 structGlobeZone <190h, 258h, 0FD98h, 0FEC0h, 1>; 8
.data:00475090 structGlobeZone <258h, 528h, 0FD80h, 0FE70h, 1>; 9
.data:00475090 structGlobeZone <528h, 550h, 0FDD0h, 0FE28h, 1>; 10
.data:00475090 structGlobeZone <0B00h, 10h, 0FE20h, 0FE70h, 2>; 11
.data:00475090 structGlobeZone <0B18h, 38h, 0FE70h, 0FEA8h, 3>; 12
.data:00475090 structGlobeZone <30h, 78h, 0FE48h, 0FE84h, 4>; 13
.data:00475090 structGlobeZone <38h, 78h, 0FE8Ch, 0FEA8h, 5>; 14
.data:00475090 structGlobeZone <58h, 90h, 0FEA8h, 0FED8h, 5>; 15
...

===Dot color data for LOC.DAT entries===
shawn on world map (can't think of a better name...):
.data:00475202 locationColor dw 0, 0Dh, 0Bh, 9, 1, 5, 7, 3 ; 0
.data:00475202 ; DATA XREF: geoDrawLocations+ED�r

Just after that are data describing the mask for drawing the location (I don't remember the format, but it shouldn't be something too complicated to decypher)

===Flare pattern===
(tactical mode):
flarePattern db 16,16,16,16,16,16,16,16,16,16,16,16,15,15,15,15,15,15,15,16,16,16,16,16,16,16,16,16,16,16,16; 0
db 16,16,16,16,16,16,16,16,16,15,15,15,14,14,14,14,14,14,14,15,15,15,16,16,16,16,16,16,16,16,16; 31
db 16,16,16,16,16,16,16,15,15,14,14,14,13,13,13,13,13,13,13,14,14,14,15,15,16,16,16,16,16,16,16; 62
db 16,16,16,16,16,16,15,15,14,14,13,13,12,12,12,12,12,12,12,13,13,14,14,15,15,16,16,16,16,16,16; 93
db 16,16,16,16,16,15,15,14,13,13,12,12,12,11,11,11,11,11,12,12,12,13,13,14,15,15,16,16,16,16,16; 124
db 16,16,16,16,15,15,14,13,12,12,11,11,11,10,10,10,10,10,11,11,11,12,12,13,14,15,15,16,16,16,16; 155
db 16,16,16,15,15,14,13,12,12,11,10,10,10, 9, 9, 9, 9, 9,10,10,10,11,12,12,13,14,15,15,16,16,16; 186
db 16,16,15,15,14,13,12,12,11,10,10, 9, 9, 8, 8, 8, 8, 8, 9, 9,10,10,11,12,12,13,14,15,15,16,16; 217
db 16,16,15,14,13,12,12,11,10, 9, 9, 8, 8, 7, 7, 7, 7, 7, 8, 8, 9, 9,10,11,12,12,13,14,15,16,16; 248
db 16,15,14,14,13,12,11,10, 9, 9, 8, 7, 7, 6, 6, 6, 6, 6, 7, 7, 8, 9, 9,10,11,12,13,14,14,15,16; 279
db 16,15,14,13,12,11,10,10, 9, 8, 7, 6, 6, 6, 5, 5, 5, 6, 6, 6, 7, 8, 9,10,10,11,12,13,14,15,16; 310
db 16,15,14,13,12,11,10, 9, 8, 7, 6, 6, 5, 5, 4, 4, 4, 5, 5, 6, 6, 7, 8, 9,10,11,12,13,14,15,16; 341
db 15,14,13,12,12,11,10, 9, 8, 7, 6, 5, 4, 4, 3, 3, 3, 4, 4, 5, 6, 7, 8, 9,10,11,12,12,13,14,15; 372
db 15,14,13,12,11,10, 9, 8, 7, 6, 6, 5, 4, 3, 2, 2, 2, 3, 4, 5, 6, 6, 7, 8, 9,10,11,12,13,14,15; 403
db 15,14,13,12,11,10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 1, 1, 2, 3, 4, 5, 6, 7, 8, 9,10,11,12,13,14,15; 434
db 15,14,13,12,11,10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9,10,11,12,13,14,15; 465
db 15,14,13,12,11,10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 1, 1, 2, 3, 4, 5, 6, 7, 8, 9,10,11,12,13,14,15; 496
db 15,14,13,12,11,10, 9, 8, 7, 6, 6, 5, 4, 3, 2, 2, 2, 3, 4, 5, 6, 6, 7, 8, 9,10,11,12,13,14,15; 527
db 15,14,13,12,12,11,10, 9, 8, 7, 6, 5, 4, 4, 3, 3, 3, 4, 4, 5, 6, 7, 8, 9,10,11,12,12,13,14,15; 558
db 16,15,14,13,12,11,10, 9, 8, 7, 6, 6, 5, 5, 4, 4, 4, 5, 5, 6, 6, 7, 8, 9,10,11,12,13,14,15,16; 589
db 16,15,14,13,12,11,10,10, 9, 8, 7, 6, 6, 6, 5, 5, 5, 6, 6, 6, 7, 8, 9,10,10,11,12,13,14,15,16; 620
db 16,15,14,14,13,12,11,10, 9, 9, 8, 7, 7, 6, 6, 6, 6, 6, 7, 7, 8, 9, 9,10,11,12,13,14,14,15,16; 651
db 16,16,15,14,13,12,12,11,10, 9, 9, 8, 8, 7, 7, 7, 7, 7, 8, 8, 9, 9,10,11,12,12,13,14,15,16,16; 682
db 16,16,15,15,14,13,12,12,11,10,10, 9, 9, 8, 8, 8, 8, 8, 9, 9,10,10,11,12,12,13,14,15,15,16,16; 713
db 16,16,16,15,15,14,13,12,12,11,10,10,10, 9, 9, 9, 9, 9,10,10,10,11,12,12,13,14,15,15,16,16,16; 744
db 16,16,16,16,15,15,14,13,12,12,11,11,11,10,10,10,10,10,11,11,11,12,12,13,14,15,15,16,16,16,16; 775
db 16,16,16,16,16,15,15,14,13,13,12,12,12,11,11,11,11,11,12,12,12,13,13,14,15,15,16,16,16,16,16; 806
db 16,16,16,16,16,16,15,15,14,14,13,13,12,12,12,12,12,12,12,13,13,14,14,15,15,16,16,16,16,16,16; 837
db 16,16,16,16,16,16,16,15,15,14,14,14,13,13,13,13,13,13,13,14,14,14,15,15,16,16,16,16,16,16,16; 868
db 16,16,16,16,16,16,16,16,16,15,15,15,14,14,14,14,14,14,14,15,15,15,16,16,16,16,16,16,16,16,16; 899
db 16,16,16,16,16,16,16,16,16,16,16,16,15,15,15,15,15,15,15,16,16,16,16,16,16,16,16,16,16,16,16; 930

Sorry for the big post and the raw format... [[User:Seb76|Seb76]] 13:59, 10 March 2008 (PDT)

Construction costs for access lifts:
.data:0046E69C basePrice dd 800000, 950000, 900000, 600000, 1000000, 650000, 550000, 500000, 750000; 0
.data:0046E69C dd 800000, 750000, 600000, 3 dup(500000); 9
[[User:Seb76|Seb76]] 11:01, 16 March 2008 (PDT)

=== Craft weapon stats ===

I guess the craft weapon stats could be in here too?
as far I can see these are at 353378 (plain 1.4), 18 bytes, 9x2 byte: 
index/range/acc/dmg/??/time/no of ammo/??/ammo 
--[[User:Emphyrio|Emphyrio]] 15:25, 1 March 2009 (CST)

----

In the WinCE version (unpatched) the craft weapon stats start at offset 0x6fb18. Or search for this signature:

40 02 1e 00 46 00 46 00 01 00 0f 00 06 00 01 00 06 00

Fields are:
Index - Range (km) - Hit% - Damage - ?X? - reload time - ammo cap - ?Y? - ammo type

Weapon X Y
Stingray 1 1
Avalanche 3 1
Cannon 8 100
FBL 5 1
Laser C 10 50
Plasma C 12 50

I would speculate that value "Y" is the re-arming rate on the ground. I think this data differs slighly from what is stated at [[Rearming]] so it might be worth double checking that.

Value "X" could be a bitmask, an index to a sound effect, or just about anything. It's possible the lowest bit is a flag that is set for a missile weapon, unset for a cannon-type weapon.

[[User:Spike|Spike]] 19:43, 5 July 2009 (EDT)

The "reload time" value (as it is called in the in-game UFOPaedia) does not seem to be used by the executable. Instead, hard coded values are used. See [[UFO Interception#Observed Rates of Fire|Observed Rates of Fire]]. [[User:Spike|Spike]] 20:31, 13 July 2009 (EDT)

I checked and the rearming rates in the wiki article are correct, i.e. 100 rds per hour for all Cannon types. Maybe this "Y" data was intended as the rearming rate but is unused? The next step would be to hack the "Y" values and look for any effect. It would also be interesting to hack the low bit of the "X" value and see if that has any effect, such as controlling the missile weapon firing interval behaviour (RoF changes based on attack mode), or sound effect.

Here is X as a bitmask

Weapon X Bitmask
Stingray 1 00000001
Avalanche 3 00000011
FBL 5 00000101
Cannon 8 00001000
Laser C 10 00001010
Plasma C 12 00001100

[[User:Spike|Spike]] 18:18, 16 February 2010 (EST)

Actually it looks like the low order 3 bits are just a sequence/ID number (ascending damage?). The next higher bit is launched (0) vs cannon (1).

Weapon X Bitmask Seq Cannon?
Cannon 8 00001000 0 1
Stingray 1 00000001 1 0
Laser C 10 00001010 2 1
Avalanche 3 00000011 3 0
Plasma C 12 00001100 4 1
FBL 5 00000101 5 0

[[User:Spike|Spike]] 19:49, 14 March 2010 (EDT)

---
.data:0046FB18 a_GS_CraftWeapon_Builtin
.data:0046FB18 strucCraftWeaponBuiltin <576, 30, 70, 70, 1, 15, 6, 1, 6>; stingray
.data:0046FB18 strucCraftWeaponBuiltin <577, 60, 80, 100, 3, 20, 3, 1, 7>; avalanche
.data:0046FB18 strucCraftWeaponBuiltin <578, 10, 25, 10, 8, 2, 200, 100, 8>; cannon
.data:0046FB18 strucCraftWeaponBuiltin <579, 65, 100, 230, 5, 25, 2, 1, 9>; fusion ball
.data:0046FB18 strucCraftWeaponBuiltin <580, 21, 35, 70, 10, 4, 0, 50, 0>; laser cannon
.data:0046FB18 strucCraftWeaponBuiltin <581, 52, 50, 140, 12, 6, 0, 50, 0>; plasma beam

00000000 Weapon_NameIdx dw ?
00000002 Range dw ?
00000004 CraftWepAccuracy dw ?; chances=random(100)< Accuracy * (1+3/(5-ufosize))/2 => Accuracy * (0.8|0.875|1|1.25|2)
00000006 CraftWepDamage dw ? ; damage=(WeaponDamage+random(WeaponDamage))/2 [50-100%]
00000008 reload_time_field_8 dw ? ;???? probably not used
0000000A UP_Reload_time__ dw ? ; ufopaedia fire rate value
0000000C MaxAmmoCount dw ?
0000000E CraftWep_RearmingRate dw ?
00000010 Ammo_Ref dw ? ;ammo blob ref, 0=ray

Fire delay for different attack modes of different craft weapon:
.data:00473FB8 a_Craft_Weapon_Reload_Time
.data:00473FB8 dw 64, 48, 32 ; stingray
.data:00473FB8 dw 96, 72, 48 ; avalanche
.data:00473FB8 dw 4, 4, 4 ; cannon
.data:00473FB8 dw 64, 48, 32 ; fusion ball
.data:00473FB8 dw 24, 24, 24 ; laser cannon
.data:00473FB8 dw 24, 24, 24 ; plasma beam

--[[User:Volutar|Volutar]] 14:13, 12 October 2011 (EDT)

==== TFTD Sub weapon stats ====

In the Steam (DOS, XcomUtil patched) version of TFTD, GEOSCAPE.EXE offset 0x665e0 is the start of the AJAX Torpedo record, the first sub weapon. Signature:

4002 2000 4600 3c00 0100 1100 0600 0100 0600

: Hacking the re-arm rate works, you see faster reloading when the sub is back at base, for Ajax at least. I didn't think this worked when I tried it before in XCOM:EU. Maybe I was mistaken, or maybe it depends on the version of XCOM:EU. Or maybe it works for launched weapons, but is overridden to 100 for cannon weapons, in both games. Need to test. [[User:Spike|Spike]] 14:58, 12 October 2010 (EDT)

=== Manufacturing stats? ===

Has someone worked out the manufacturing stats at offset <s>355596</s> 355600 (vanilla 1.4)??
As far as I can see it looks like 35 records of 18 bytes 
 
:See the [[PRODUCT.DAT]] page. --[[User:Zombie|Zombie]] 16:25, 24 February 2009 (CST)
:: ok, this is actually is a useful bit of information, I <s>would</s> have put it in the article.. --[[User:Emphyrio|Emphyrio]] 07:06, 25 February 2009 (CST)
:Good deal. I also added a note to the top of [[PRODUCT.DAT]] (and linked the [[Manufacturing_Profitability]] to PRODUCT.DAT - that should've been there, too). -[[User:MikeTheRed|MikeTheRed]] 11:17, 25 February 2009 (CST)

==New Bundles==

The "Complete Package" and such versions of X-Com from Steam, interestingly enough, include both versions of the game, at least .exe wise. The one that runs when you just launch from the Steam menu is the original European version, 1.2, so I wonder exactly why they included the other version. -[[User:Elliotw2|Elliotw2]] 2009-01-15 18:01:37

:Hiya Elliotw2! I wasn't watching this page's Talk page before, but I am now.
:As for the various versions, I dusted off some 10 y.o. DOS floppies a few years ago. They still worked, and I ran with it (U.S. DOS v. 1.4). Although I've read a lot about the other versions on this wiki, I'll let the other vets here address what you just said (smile). I personally would have chosen the U.S. version... Vets, why would they have both versions in the bundle, but make the default be the European version?
:Elliotw2, please leave a mini-review (or repeat what you just said) at [[GEOSCAPE.EXE#X-COM_Complete_Packages]] (see my new "mini-review" format request there). Sorry for the mess, newcomers - especially having this tucked away under GEOSCAPE, but it makes sense to us grognards. As always, we will change and grow as needed, and "us" easily includes "you". For now, we're just trying to make sure that newcomers can find what they need here, and that there's a place for info on the Complete Packages to be voiced.
:-[[User:MikeTheRed|MikeTheRed]] 03:49, 19 January 2009 (CST)

Just bought the Complete Package on Steam. Can test later today. What should I look at first? Oh, and hi all, I'm new here :) --[[User:Kpobococ|kpobococ]] 06:17, 25 March 2011 (EDT)

:Hiya. :)

:Steam contains DOS and CE executables - the CE one is primarily there for anyone who can use it, as it's a bit faster and stabler then the DOS release, however, DOSBox is the easiest option for most people with "modern" computers.

::DOSBox is also configured to use filter (known in DOSBox config as scaler) to enhance low resolution mode. --[[User:Kpobococ|kpobococ]] 07:58, 25 March 2011 (EDT)

:The DOS install should be 1.4, but release notes for 1.2 do exist in the package as well. I suppose if you'd like to confirm that, you could try checking the executable filesizes to determine which DOS version is in there - you can find the patches [http://www.strategycore.co.uk/files/index.php?cid=40 here] should you wish to compare some files. Filesizes and checksums for all the different EXEs of all the different releases would be great to have documented! -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 07:37, 25 March 2011 (EDT)

::I'll get back to you with filesizes and probably checksums too, if you can tell my which utility to use for the checksums --[[User:Kpobococ|kpobococ]] 07:58, 25 March 2011 (EDT)

::Steam version's GEOSCAPE.EXE filesize is 382,957b (md5: 33ea0819e6888f0450f9a1e5e19dc98b; sha1: 832d78f3c9a9c50960f10473592ae2c48dc7b6a7). Also, I've checked all the versions from strategycore, here are their sizes and checksums: v1.2: 415,271b (md5: be98b94f3f477181e186a5191a8bf36a; sha1: 29dd0f48b86f6ff3f68caa3c22303295753c240f); v1.3: 419,367b (md5: 42b5be21e24dd5b2b8088cb1f4e70aee; sha1: 54cd69cd3b9222a723eb269a7d63b7965b74b3ea); v1.4: 382,957b (md5: 33ea0819e6888f0450f9a1e5e19dc98b; sha1: 832d78f3c9a9c50960f10473592ae2c48dc7b6a7). So, the Steam version is definitely version 1.4. --[[User:Kpobococ|kpobococ]] 17:38, 25 March 2011 (EDT)

== Difficulty patch information wrong? ==

It appears that the information for patching the difficulty is wrong on this page.

I have what I believe is the US version of XCOM 1.4, and I patched the file as per the data given for 1.4, and yet it still created a 60-byte IGLOB.DAT file. Further, DOSBOX complained of illegal memory accesses after the patch (which it did not do before).

33ea0819e6888f0450f9a1e5e19dc98b *GEOSCAPE.EXE (binary MD5SUM -- file is 382,957 bytes, created 1995-02-28 @ 10:24 PM)

There actually was a 60 byte (0x3c) at the location given, but I have a feeling it was something other than the size_t in question.

:If you search for:
<pre>3C 00 00 00 57 2B C9 49</pre>
:you will fined the iglob.dat length for all versions of UFO. --[[User:BladeFireLight|BladeFireLight]] 19:45, 16 February 2010 (EST)

Yeah, that was my fault, I just put the same value as was in 1.0. It's corrected now.
[[User:Hatfarm|Hatfarm]] 18:45, 5 June 2010 (EDT)

I tried that out, it seems to work perfectly. Thank you both! FYI; the above is the XCOM package available from <s>GOG.com</s> Direct2Drive. [[User:Renegrade|Renegrade]] 20:23, 17 July 2010 (EDT)

:Is there a patched Geoscape.exe floating around anywhere, so I could fix the bug without using a hex editor? This bug is the reason I haven't played UFO for years. [[User:Magic9mushroom|Magic9mushroom]] 06:10, 6 February 2012 (EST)

== Wacky TFTD Zone ==

I shot a sub down near Easter Island in the South Pacific, assaulted it, and the XCOM Activity score was credited to Egyptian Cartel. I was nowhere near Egypt, all month long. Is that a weird Zone polygon, or is it just a bug? [[User:Spike|Spike]] 19:03, 7 October 2010 (EDT)

== Alien equipment tables ==

Dos Geoscape.exe at 0x599A5
MS-Edit @100 columns: Line: 3671 col: 14

CE executable at 0x72D68
MS-Edit @100 columns: Line: 4704 col: 77

TFTD CE version starts at 0x7DAB8
TFTD Dos at 0x69E84 (Approx)

55 rows of 21 byte structures.

A short digest from [[Alien Weapon Loadouts]]

:'''00''': Mission type (starts from 05 = Small Scout; goes to 15 (x0F) for Mars 2)
:'''01''': Alien rank
:'''02''': Base number of aliens on Beginner / Experienced
:'''03''': Base number of aliens on Superhuman (Veteran / Genius is the average of these two)
:'''04''': A random number from 0 to this number will be added to the above number of aliens
:'''05''': chance for this unit to be a "scout" and get spawned on a civ/scout node.
:'''06-10''' (x06-x0A): Early game loadout
:'''11-15''' (x0B-x0F): Mid game loadout
:'''16-20''' (x10-x14): Late game loadout

The three sets are randomly selected for the aliens as they are individually generated. Set selection is likely weighted by other factors such as difficulty level. Time or score may also influence this. Aliens races without corresponding ranks will still get created at that rank and granted the corresponding equipment set, then get demoted later.

- [[User:NKF|NKF]] 03:47, 19 May 2012 (EDT)

File:UFOLoader.zip

2016-02-22T15:01:41Z

Morgan525:

=CHOOSE A VERSION FROM THE LIST AT THE BOTTOM OF THIS PAGE=
THE FILE ON THE MAIN LINK ABOVE IS AN EMPTY ZIP FILE. I've done this because, when you click the link, your browser may report the file is malicious (malware or a trojan). This has nothing to do with the contents of the file: The Extender does not contain a digital signature from a recognize authority and is available on an open site so Chrome and other AV software automatically flag it as bad.

This is the loader for the 1994 X-COM:Enemy Unknown (UFO Defense).

See the [[UFOextender|UFO Extender information page]] for details about options in the INI.

= New Information=
*Check that the file you are downloading is a full version or a patch!
*Details on each version can be found in the Discussion Section.

User:Morgan525

2016-02-22T15:00:00Z

Morgan525: /* UFO Extender */

I'm also known as "Tycho" on StrategyCore forums. I've been studying disassembly and C++ coding since December of 2011. This all started because I wanted to mod the tank/cannon of '94 Enemy Unknown into a tank/chaingun for my own games. I started playing the DOS version but eventually switched to the CE version. At first, I focused on the sound problems which is when I started to experiment with Seb76's UFOloader.

==[[UFOextender|UFO Extender]]==
This is the original program created by [[user:seb76|Seb76]] for use with ''Enemy Unknown''. Check out the [[UFOextender|UFO Extender's Information Page]]. You can download the latest version and patches here: [[:file:UFOLoader.zip|UFO Extender]].

If you're interested in the source code, it is available. Be warned you'll need to decompile the executable and be familiar with disassembly terminology to understand a lot of what the Extender does, since it inserts new lines into preexisting code. The source files for the Extender are here: [[Image:UFOExtender-src.zip]].

==[[TFTDextender|TFTD Extender]]==
It adds a lot of functionality and fixes to the Collector's Edition (MS Windows version) of ''Terror from the Deep''. Click on the title to get to the information page.

For those interested, here is the [[:File:TFTDextender-src.zip| source code]] for the Extender.

==Other information==

Talk:Base Defence Systems

2016-02-20T22:43:13Z

Morgan525: /* Penetration Math */

I added some info about TFTD to the article since it talks about TFTD too. I noticed though that some of the info conflicts with [[Base_Defense (TFTD)]] article. e.g. here it says the item limit has been raised to 110, there it says the limit is still 80. Anyhow, I can verify there's a sorting algorithm from my experience, but not much further. I wonder if it may end up preferring unresearched guns for example.. [[User:Cesium|Cesium]] 20:02, 30 December 2009 (EST)
:Hadn't realized that there was a page for TFTD. I just corrected it to 110 (this number is actually from the Unofficial Strategy Guide but from what I recall it is correct). About the sorting algorithm I can't confirm it. [[User:Hobbes|Hobbes]] 20:40, 30 December 2009 (EST)
::I just ordered a lot of Jet Harpoons, Dart Guns and Chemical Flares to a base and let the aliens find it. The equipment available in the load screen was mainly Sonic Rifles and Sonic Cannons. The Darts, Jets and Flares were not available. Something has to account for the quartermaster being sane, and we do know some attention was given to base defense (since the item limit was raised). I guess only way to be sure is for someone to disassemble the executable and examine the code.... [[User:Cesium|Cesium]] 09:35, 31 December 2009 (EST)
:::Well the quartermaster is mostly sane. However it does not check if you have researched the clip before it packs the shiny new Sonics. So be sure to move them out if you have not or you might end up with lots of guns without ammo. If you want Medikits be sure to reduce the number of spare weapons--[[User:Tauon|Tauon]] 19:32, 16 October 2010 (EDT)
Not sure the 110 number for TFTD is technically correct. When I try to load more than 80 items on a craft I still get a warning. --[[User:Zombie|Zombie]] 22:31, 30 December 2009 (EST)
:The limit for weapons being carried in craft is still 80 but for the base defense missions the game allows for 110 items. [[User:Hobbes|Hobbes]] 22:56, 30 December 2009 (EST)

== Penetration Math ==

"...Missile/Torpedo Defences are the most cost-effective of the defensive base facilities. The odds of penetrating 12 such modules and a Grav/Bombardment Shield are 30 to 1. On average, 30 attack ships will be destroyed before one gets through. Such a system costs $3.7 million. For the same price, 3 Fusion Ball/P.W.T. Defences with a Grav/Bombardment Shield will offer only 9 to 1 protection..."

Huh? Where is this math coming from? From the way I understand it, it's a simple binomial distribution (at least for exclusively one type of base defense module).

In order to bring down a battleship (3200 hits) you need to connect 7 rounds from a missile defense (500 damage). With 12 missile defenses and a grav shield, you have 24 bernoulli trials with a 50% probability of success. The probability of 6 successes or fewer out of 24 trials at 50% I believe is ~0.01133, or 1 out of about 88 ships getting through your defenses. I calculated this in excel via =BINOM.DIST(6,24,0.5,TRUE) so I am confident it is correct.

In the fusion ball case, I believe it is 2 or fewer successes out of 6 trials with 80% probability, =BINOM.DIST(2,6,0.8,TRUE), 0.01696, or 1 out of about 59 ships getting through.

While the original point still stands with my math (missile is more cost effective than fusion), the odds of penetrating either setup are greatly reduced, as is the difference between the performance of the two. Perhaps I do not properly understand the mechanics of base defense modules, or screwed up my thinking or math somewhere along the way.

--[[User:Jewcifer|Jewcifer]] 12:57, 16 March 2012 (EDT)

:I'm not sure if the page mentions it (I've only got time for a quick skim right now), but to further complicate matters the amount of damage the defences do per-shot is randomised. I think it goes from about 50% to 150% of their rated power, can't remember if I was ever able to confirm an exact range. Seven shots from a missile defence may not be enough to down a battleship. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 17:39, 16 March 2012 (EDT)

::Hmmm, I have seen no mention of variable damage either in-game or anywhere on this wiki (I've been reading through it quite extensively for months before finally getting around to signing up a couple days ago). I think that information should be determined and put somewhere (this article is probably as good a place as any for it). I'm not likely to do that myself (would probably require either extensive simulation or disassembling and hunting through the executable code to determine the range?), but if anyone else does I will run the different calculations appropriately. If the range is 50%-150% it should be only slightly more likely for ships to penetrate in these cases (but not nearly enough to account for the discrepancy), but perhaps if the range is more like 50%-100% (like craft weapons) they would match up with what's in the article. --[[User:Jewcifer|Jewcifer]] 12:24, 21 March 2012 (EDT)
:::I am 100% sure that damage to UFOs from base defences is variable. I have seen Battleships both die and not die from 2 hits with a Fusion Ball Defence while I was using the Battleship Farming exploit. [[User:Magic9mushroom|Magic9mushroom]] 18:19, 21 March 2012 (EDT)

:::Indeed, a defense module may deal more then 100% of its rated damage. I've seen two fusion ball shots take out a battleship, and I've seen some require four - the vast majority drop after three. This "proves" a minimum range of 66%-133% (the damage averages required to achieve 2-4 hit take-downs), which strongly suggests the actual range is 50%-150%.

:::Much of the information on this wiki is written off the top of someone's head, especially articles like this one that deal less in hard statistics and more on handing out strategies and tactics (it doesn't even mention how much damage needs to be done to shoot down a battleship!). Many such errors are only corrected when newcomers come along and spot them. There are plenty there, though, so don't be afraid to question anything you see or correct anything you are certain to be wrong. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 04:42, 22 March 2012 (EDT)

::::Thanks guys. Initially I tried to work out a mathematical approach using the probability density function of an irwin–hall distribution, but dealing with variable n due to the accuracy aspect made it way too complicated and confusing for me to handle. Yikes.
::::So I did what any sensible programmer would do and wrote a quick script to run monte carlo simulations of x-com base defense. I ran 1,500,000 simulations of both of the above scenarios for damage ranges of 100%-100%, 50%-100%, 50%-150%, and 0%-200% (using a discrete uniform distribution within the range). The output is the damage range formula used, the base defense setup (i.e. number of shots, damage, and accuracy), and the average number of attacking ships needed for one to get through:
100%-100%
24 shots, 500 damage, 50% accuracy:
89.46 ships
6 shots, 1200 damage, 80% accuracy:
59.12 ships

50%-100%
24 shots, 500 damage, 50% accuracy:
11.63 ships
6 shots, 1200 damage, 80% accuracy:
07.88 ships

50%-150%
24 shots, 500 damage, 50% accuracy:
67.75 ships
6 shots, 1200 damage, 80% accuracy:
25.19 ships

0%-200%
24 shots, 500 damage, 50% accuracy:
31.32 ships
6 shots, 1200 damage, 80% accuracy:
10.86 ships
::::Nicely enough, the 100%-100% numbers (fixed damage) match my earlier calculations reasonably well, and it seems the 0%-200% numbers are very close to what is in the article! So I think unless someone verifies or is already quite confident the damage range is something other than 0 to double, or maybe has some non-uniform distribution, I'll leave it alone.
::::I do think this article should mention somewhere that the damage is a variable range. Perhaps go ahead and say 0%-200%, with a note that this maybe should be verified?
::::Thanks again for the replies!
::::--[[User:Jewcifer|Jewcifer]] 11:36, 29 March 2012 (EDT)
Monte Carlo method should be able to find the damage range, actually. Given a save with a Battleship inbound on a base with 10 Fusion Ball Defences + Grav Shield, one would save-scum (or just keep playing while leaving the Battleship swarms alone) and record the number of Fusion Ball hits needed to down the Battleship on each attempt. If it's 50%-150% (as I suspect it is), then the chance in Collector's Edition (3000 Battleship health) should be 1/8 (12.50%) to down it in two hits, 5/6 (83.33%) to down it in three hits or less, and 383/384 (99.74%) to down it in four hits or less (five hits gives certainty). In DOS (3200 Battleship health) it should be 1/18 (5.56%) to down it in two hits, 241/243 (99.18%) to down it in four hits or less and 933119/933120 (99.9999%) to down it in five hits or less (six hits gives certainty; three hits is more complicated and I CBF doing it right now). If it's 0%-200% then the chance to down it in two hits should be 9/32 (28.12%) in CE and 2/9 (22.22%) in DOS, the chance to down it in three hits or less should be under 5/6 (83%), the chance to down it in four hits should be under 23/24 (96%) and the chance to down it in five hits should be under 119/120 (99.2%) (in all cases by a decent margin, since that's actually the chance of doing under 2400 damage). My recollections don't match that latter set of numbers (I've ''never'' seen four hits fail to down a Battleship in CE, and two-hit kills are fairly rare) but I could be wrong. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 02:22, 18 February 2016 (EST)

:After analyzing the CE code, it seems the damage range is 50-150%. - [[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 03:52, 20 February 2016 (EST)

Talk:Base Defence Systems

2016-02-20T08:52:28Z

Morgan525: /* Penetration Math */

I added some info about TFTD to the article since it talks about TFTD too. I noticed though that some of the info conflicts with [[Base_Defense (TFTD)]] article. e.g. here it says the item limit has been raised to 110, there it says the limit is still 80. Anyhow, I can verify there's a sorting algorithm from my experience, but not much further. I wonder if it may end up preferring unresearched guns for example.. [[User:Cesium|Cesium]] 20:02, 30 December 2009 (EST)
:Hadn't realized that there was a page for TFTD. I just corrected it to 110 (this number is actually from the Unofficial Strategy Guide but from what I recall it is correct). About the sorting algorithm I can't confirm it. [[User:Hobbes|Hobbes]] 20:40, 30 December 2009 (EST)
::I just ordered a lot of Jet Harpoons, Dart Guns and Chemical Flares to a base and let the aliens find it. The equipment available in the load screen was mainly Sonic Rifles and Sonic Cannons. The Darts, Jets and Flares were not available. Something has to account for the quartermaster being sane, and we do know some attention was given to base defense (since the item limit was raised). I guess only way to be sure is for someone to disassemble the executable and examine the code.... [[User:Cesium|Cesium]] 09:35, 31 December 2009 (EST)
:::Well the quartermaster is mostly sane. However it does not check if you have researched the clip before it packs the shiny new Sonics. So be sure to move them out if you have not or you might end up with lots of guns without ammo. If you want Medikits be sure to reduce the number of spare weapons--[[User:Tauon|Tauon]] 19:32, 16 October 2010 (EDT)
Not sure the 110 number for TFTD is technically correct. When I try to load more than 80 items on a craft I still get a warning. --[[User:Zombie|Zombie]] 22:31, 30 December 2009 (EST)
:The limit for weapons being carried in craft is still 80 but for the base defense missions the game allows for 110 items. [[User:Hobbes|Hobbes]] 22:56, 30 December 2009 (EST)

== Penetration Math ==

"...Missile/Torpedo Defences are the most cost-effective of the defensive base facilities. The odds of penetrating 12 such modules and a Grav/Bombardment Shield are 30 to 1. On average, 30 attack ships will be destroyed before one gets through. Such a system costs $3.7 million. For the same price, 3 Fusion Ball/P.W.T. Defences with a Grav/Bombardment Shield will offer only 9 to 1 protection..."

Huh? Where is this math coming from? From the way I understand it, it's a simple binomial distribution (at least for exclusively one type of base defense module).

In order to bring down a battleship (3200 hits) you need to connect 7 rounds from a missile defense (500 damage). With 12 missile defenses and a grav shield, you have 24 bernoulli trials with a 50% probability of success. The probability of 6 successes or fewer out of 24 trials at 50% I believe is ~0.01133, or 1 out of about 88 ships getting through your defenses. I calculated this in excel via =BINOM.DIST(6,24,0.5,TRUE) so I am confident it is correct.

In the fusion ball case, I believe it is 2 or fewer successes out of 6 trials with 80% probability, =BINOM.DIST(2,6,0.8,TRUE), 0.01696, or 1 out of about 59 ships getting through.

While the original point still stands with my math (missile is more cost effective than fusion), the odds of penetrating either setup are greatly reduced, as is the difference between the performance of the two. Perhaps I do not properly understand the mechanics of base defense modules, or screwed up my thinking or math somewhere along the way.

--[[User:Jewcifer|Jewcifer]] 12:57, 16 March 2012 (EDT)

:I'm not sure if the page mentions it (I've only got time for a quick skim right now), but to further complicate matters the amount of damage the defences do per-shot is randomised. I think it goes from about 50% to 150% of their rated power, can't remember if I was ever able to confirm an exact range. Seven shots from a missile defence may not be enough to down a battleship. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 17:39, 16 March 2012 (EDT)

::Hmmm, I have seen no mention of variable damage either in-game or anywhere on this wiki (I've been reading through it quite extensively for months before finally getting around to signing up a couple days ago). I think that information should be determined and put somewhere (this article is probably as good a place as any for it). I'm not likely to do that myself (would probably require either extensive simulation or disassembling and hunting through the executable code to determine the range?), but if anyone else does I will run the different calculations appropriately. If the range is 50%-150% it should be only slightly more likely for ships to penetrate in these cases (but not nearly enough to account for the discrepancy), but perhaps if the range is more like 50%-100% (like craft weapons) they would match up with what's in the article. --[[User:Jewcifer|Jewcifer]] 12:24, 21 March 2012 (EDT)
:::I am 100% sure that damage to UFOs from base defences is variable. I have seen Battleships both die and not die from 2 hits with a Fusion Ball Defence while I was using the Battleship Farming exploit. [[User:Magic9mushroom|Magic9mushroom]] 18:19, 21 March 2012 (EDT)

:::Indeed, a defense module may deal more then 100% of its rated damage. I've seen two fusion ball shots take out a battleship, and I've seen some require four - the vast majority drop after three. This "proves" a minimum range of 66%-133% (the damage averages required to achieve 2-4 hit take-downs), which strongly suggests the actual range is 50%-150%.

:::Much of the information on this wiki is written off the top of someone's head, especially articles like this one that deal less in hard statistics and more on handing out strategies and tactics (it doesn't even mention how much damage needs to be done to shoot down a battleship!). Many such errors are only corrected when newcomers come along and spot them. There are plenty there, though, so don't be afraid to question anything you see or correct anything you are certain to be wrong. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 04:42, 22 March 2012 (EDT)

::::Thanks guys. Initially I tried to work out a mathematical approach using the probability density function of an irwin–hall distribution, but dealing with variable n due to the accuracy aspect made it way too complicated and confusing for me to handle. Yikes.
::::So I did what any sensible programmer would do and wrote a quick script to run monte carlo simulations of x-com base defense. I ran 1,500,000 simulations of both of the above scenarios for damage ranges of 100%-100%, 50%-100%, 50%-150%, and 0%-200% (using a discrete uniform distribution within the range). The output is the damage range formula used, the base defense setup (i.e. number of shots, damage, and accuracy), and the average number of attacking ships needed for one to get through:
100%-100%
24 shots, 500 damage, 50% accuracy:
89.46 ships
6 shots, 1200 damage, 80% accuracy:
59.12 ships

50%-100%
24 shots, 500 damage, 50% accuracy:
11.63 ships
6 shots, 1200 damage, 80% accuracy:
07.88 ships

50%-150%
24 shots, 500 damage, 50% accuracy:
67.75 ships
6 shots, 1200 damage, 80% accuracy:
25.19 ships

0%-200%
24 shots, 500 damage, 50% accuracy:
31.32 ships
6 shots, 1200 damage, 80% accuracy:
10.86 ships
::::Nicely enough, the 100%-100% numbers (fixed damage) match my earlier calculations reasonably well, and it seems the 0%-200% numbers are very close to what is in the article! So I think unless someone verifies or is already quite confident the damage range is something other than 0 to double, or maybe has some non-uniform distribution, I'll leave it alone.
::::I do think this article should mention somewhere that the damage is a variable range. Perhaps go ahead and say 0%-200%, with a note that this maybe should be verified?
::::Thanks again for the replies!
::::--[[User:Jewcifer|Jewcifer]] 11:36, 29 March 2012 (EDT)
Monte Carlo method should be able to find the damage range, actually. Given a save with a Battleship inbound on a base with 10 Fusion Ball Defences + Grav Shield, one would save-scum (or just keep playing while leaving the Battleship swarms alone) and record the number of Fusion Ball hits needed to down the Battleship on each attempt. If it's 50%-150% (as I suspect it is), then the chance in Collector's Edition (3000 Battleship health) should be 1/8 (12.50%) to down it in two hits, 5/6 (83.33%) to down it in three hits or less, and 383/384 (99.74%) to down it in four hits or less (five hits gives certainty). In DOS (3200 Battleship health) it should be 1/18 (5.56%) to down it in two hits, 241/243 (99.18%) to down it in four hits or less and 933119/933120 (99.9999%) to down it in five hits or less (six hits gives certainty; three hits is more complicated and I CBF doing it right now). If it's 0%-200% then the chance to down it in two hits should be 9/32 (28.12%) in CE and 2/9 (22.22%) in DOS, the chance to down it in three hits or less should be under 5/6 (83%), the chance to down it in four hits should be under 23/24 (96%) and the chance to down it in five hits should be under 119/120 (99.2%) (in all cases by a decent margin, since that's actually the chance of doing under 2400 damage). My recollections don't match that latter set of numbers (I've ''never'' seen four hits fail to down a Battleship in CE, and two-hit kills are fairly rare) but I could be wrong. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 02:22, 18 February 2016 (EST)

:From looking at the CE code the damage range is 50-150%. - [[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 03:52, 20 February 2016 (EST)

File:UFOLoader.zip

2016-02-20T08:11:38Z

Morgan525:

=CHOOSE A VERSION FROM THE LIST AT THE BOTTOM OF THIS PAGE=
THE FILE ON THE MAIN LINK ABOVE IS AN EMPTY ZIP FILE. I've done this because, when you click the link, your browser may report the file is malicious (malware or a trojan). This has nothing to do with the contents of the file: The Extender does not contain a digital signature from a recognize authority and is available on an open site so Google automatically flags it as bad.

This is the loader for the 1994 X-COM:Enemy Unknown (UFO Defense).

See the [[UFOextender|UFO Extender information page]] for details about options in the INI.

= New Information=
*Check that the file you are downloading is a full version or a patch!
*Details on each version can be found in the Discussion Section.

File:UFOLoader.zip

2016-02-20T08:10:26Z

Morgan525:

=CHOOSE A VERSION FROM THE LIST AT THE BOTTOM OF THIS PAGE=

This is the loader for the 1994 X-COM:Enemy Unknown (UFO Defense).

See the [[UFOextender|UFO Extender information page]] for details about options in the INI.

*Check that the file you are downloading is a full version or a patch!
*Details on each version can be found in the Discussion Section.

= New Information=

THE FILE ON THE MAIN LINK ABOVE IS AN EMPTY ZIP FILE. I've done this because, when you click the link, your browser may report the file is malicious (malware or a trojan). This has nothing to do with the contents of the file: The Extender does not contain a digital signature from a recognize authority and is available on an open site so Google automatically flags it as bad.

File:UFOLoader.zip

2016-02-20T01:33:51Z

Morgan525:

This is the loader for the 1994 X-COM:Enemy Unknown (UFO Defense)

See the [[UFOextender|UFO Extender information page]] for details about options in the INI.

=CHOOSE A VERSION FROM THE LIST AT THE BOTTOM OF THIS PAGE=

*Check that the file you are downloading is a full version or a patch!
*Details on each version can be found in the Discussion Section.

= New Information=

THE FILE ON THE MAIN LINK ABOVE IS AN EMPTY ZIP FILE. I've done this because, when you click the link, your browser may report the file is malicious (malware or a trojan). This has nothing to do with the contents of the file: The Extender does not contain a digital signature from a recognize authority and is available on an open site. Choose the latest version from the list below. You'll need a full version and latest patch if this is your first time to try the Extender.

File:UFOLoader.zip

2016-02-19T09:17:17Z

Morgan525: Morgan525 uploaded a new version of "File:UFOLoader.zip"

User:Morgan525

2016-02-18T11:53:54Z

Morgan525:

I'm also known as "Tycho" on StrategyCore forums. I've been studying disassembly and C++ coding since December of 2011. This all started because I wanted to mod the tank/cannon of '94 Enemy Unknown into a tank/chaingun for my own games. I started playing the DOS version but eventually switched to the CE version. At first, I focused on the sound problems which is when I started to experiment with Seb76's UFOloader.

==[[UFOextender|UFO Extender]]==
This is the original program created by [[user:seb76|Seb76]] for use with ''Enemy Unknown''. Check out the [[UFOextender|UFO Extender's Information Page]]. You can download the latest version and patches here: [[:file:UFOextender1.33.zip|UFO Extender]].

Here is the archive page for older versions: [[:file:UFOLoader.zip|UFOextender]].

If you're interested in the source code, it is available. Be warned you'll need to decompile the executable and be familiar with disassembly terminology to understand a lot of what the Extender does, since it inserts new lines into preexisting code. The source files for the Extender are here: [[Image:UFOExtender-src.zip]].

==[[TFTDextender|TFTD Extender]]==
It adds a lot of functionality and fixes to the Collector's Edition (MS Windows version) of ''Terror from the Deep''. Click on the title to get to the information page.

For those interested, here is the [[:File:TFTDextender-src.zip| source code]] for the Extender.

==Other information==

UFOextender

2016-02-18T11:46:22Z

Morgan525:

This is the loader for Enemy Unknown, created by [[user:seb76|Seb76]] and further developed by [[User:Morgan525|Tycho]], which adds fixes, more features, and improvements to the Collector's Edition (a.k.a. CE or Gold Edition) of the game.
[[File:X-com1994cover.jpg|480px|right|]]
== General Information ==

The loader patches the program in memory, it does '''not''' modify the executable. The advantage is that it doesn't change the file on disk so there is little risk of destroying your game installation (still, it is wise to do a backup of your game folder before using this).
Of course, if your computer starts pestering you to play "Global Thermonuclear War", I don't take any responsibility...

This program only works with the Windows version '''and will not work through DOSbox'''. There will not be a DOS-compatible version.

Do not hesitate to report any problem you encounter with it, I'll try to help you fix it.--[[User:Morgan525|Tycho]]

===Installation===

#Download the version you want and/or patches. [http://ufopaedia.org/index.php?title=File:UFOextender1.33.zip '''UFO Extender Download Page''']
#Extract these files into the game folder containing the UFO Defense.exe (or whatever the windows version of Enemy Unknown executable is on your machine.)
#Using a simple text editor (like Windows notepad), open the '''UFOextender.INI''' file and enable the options you wish to use.
#*For most options, you enable it by changing the value from zero to one. Some options do have more settings. Refer to this page or the README file for more information on each one.
#Run ''UFOloader.exe'' instead of UFO Defense.exe.

*You need a program that can extract zip files.
*You need the Microsoft VC++2008 redistributable package to run this program. If you don't already have it installed, you can get it [http://www.microsoft.com/downloads/details.aspx?FamilyID=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en here].
*The extender looks for the file ''UFO Defense.exe'' but this can be changed under the [Loader] section of the INI.
*For enhanced music, you will need to create a folder called MP3 in the same folder as your UFO Defense executable. Copy the music files to this folder.
** You need to have Windows Media Player installed for versions before 1.30, if you wish to use the enhanced music.

=== FAQs ===
*Does it fix the difficulty bug?
::The infamous difficulty bug only applies to the DOS version of the game. It was never an issue with the Windows version.
*MP3 music crashes the game or doesn't work
::Prior to version 1.30, the loader played the enhanced music through the OS. Audio codecs installed by other programs can interfere with the playback. This causes no music or an error which will force the game to exit. Some people have experienced this after upgrading their OS even though no other changes were made and music played prior to the upgrade. ''Someone has developed a good method to help isolate and maybe resolve these conflicts. See [[TFTDextender#FAQs| TFTDextender FAQs]]. Otherwise, the only solution is to uninstall whatever audio/video programs you have loaded to determine the source and solution to the problem.''
::'''Starting with version 1.30, the Extender plays enhanced music utilizing the BASS audio library and sound system[http://www.un4seen.com]'''.
* Can I change the music/SFX volume || The music is louder than the DOS version.
::The original game only selects the effect/music to be played and then sends data to the OS sound layer.The Windows version uses MIDI for music since, prior to Windows Vista, there were separate volume controls for WAV and MIDI. An entire new routine to create new buffers for each sound sample would be required as well as routines to allow volume controls in-game.
::'''Version 1.33 plays all sounds through the BASS audio system and provides separate volume controls for music and SFX.'''
*"X-COM crashed at 0x45E6A5 with error ..."
::Usually this occurs when playing with a mod program that splits the executable in order to run. A part that gets altered during the split conflicts with the Extender's option to "skip the intro". Disabling this option in the Extender will stop the error.
*"X-COM crashed at 0x7------- with error ..." (when quitting the game or starting combat)
::This will occur after the player has viewed one of the aircraft pages in the in-game Ufopaedia. When the game loads the various graphic files of the in-game UFOpaedia, it uses a designated memory block to store the graphic information and swaps the data in this section as needed (to conserve memory usage, I suppose: It was a DOS game originally.) The file TAC00.SCR is used as the template for this region. Unfortunately, the SPK files for each aircraft are several bytes larger than TAC00.SCR, so the memory region's "header"(?) is partially overwritten. When GEOSCAPE or BATTLESCAPE closes and starts to free the memory regions, the memory deallocate function crashes when it attempts to read the corrupted information. I expanded TAC00.SCR to compensate for the larger SPK files. [[:file:TAC00.zip|Download it here.]] Extract the file into the UFOGRAPH folder and overwrite the current one.
*The zip only contains a single file called ''patcher.dll''. Where is the rest of the loader?
::The minor versions (aka patches) only include an update to this file. For the other files you need to download the most recent major version. If you look at the page for the zip file, you will see a link to the most current release at the top of the page, information on the release, and then beneath that you will see a table that has links to all the previous releases, with the version number listed in the comments field. This is intentional so patches can be downloaded and installed easily without fear of overwriting a custom INI file by mistake.
*Using Extender in Steam (seamlessly) [aka attempting to run Extender directly from the Steam interface]
::I suggest seeking help on the Steam forums. For most digital downloads, the Windows version can be run independently and that is the only method for which I am able to help. You might also try [[XcomUtil#XcomUtil_.2B_UFO_Extender| the UFOpaedia XCOMutil page]] where some information is available.
*I don't recover clips in missions. // I am losing ammo in every mission.
:: This usually occurs with people playing Extender and XcomUtil. Each has a different way to fix the partial-clips-lost issue and are incompatible.
*The text in the mission debriefing that is associated with the 'Wreck Analysis' mod is incomprehensible.
:: An altered version of the ENGLISH.DAT file that came with some early versions of the Extender has an error. Restoring this file to its original should fix this.
*My anti-virus software reports that the Extender is a trojan or malicious software.
:: Anti-virus companies are extremely sensitive to malicious software which means that software from private individuals can be falsely reported as a problem and be removed or quarantined. The Extender works by loading the game and then altering the game code that resides in memory. This behavior is similar to those of malicious software so AV programs may identify the Extender as such. When they do this, you'll need to locate the appropriate section in the AV software and reinstate the Extender. Even if your AV software is working fine with the Extender currently, it is recommended that you add an exception for the extender in your anti-virus settings (or add it to a "safe" list for some software versions.) The terminology and methods for each AV software are different so please consult the help section of your particular AV program.

=== Some Disclaimers===
:'''Extender and XcomUtil''': When Seb76 stopped development on the Extender, both programs were fairly compatible. Since the Extender has been developed further but XcomUtil has not, there are more areas of incompatibility now. If errors arise, it is advised to try to recreate those issues without using XcomUtil before reporting them. Even splitting the executable, as is done by XComUtil, has caused problems.
:'''Extender and other modified game executables''': [such as ET_2005] These may work together but there is no guarentees. ET_2005 heavily modifies the binary and trying to patch on top of it will produce unexpected data corruption or crash the game.
:'''DAT file mod requests''': DAT files modifications are not done because there are already lots of them and various data editors available to do them for yourself. This rule allows all data mods to keep working with the loader (that is why some xcomutil features should still work, as long as they are those only based on resource modifications). [prior to version 1.32]''Any bug fix that requires a change to some resource data in order to compensate for the fix, will have an option to exclude the data change so that any player changes will not be overwritten.'' [version 1.32+] ''The data changes that were implemented in 1.32 will override any changes made by players for the same data block. These data changes in the Extender are applied starting at "Veteran" difficulty. Players can choose "experienced" difficulty and chose the "Maximize Aliens" mod to play closer to the original game with harder battles.''

<tabber>
Version 1.0~1.32=The game is fully customizable: One can play a "pure vanilla" game with only the video fixes enabled or with as many of the modifications as you want. Everything can be enabled or disabled in the loader's INI file.
|-|
Version 1.32+=These versions a very different from all prior versions. The goal for these versions is to provide balance to the strategy layer and increase the aggressiveness of the aliens with the difficulty level. The difficulty one chooses at the main menu will be the default difficulty for both the strategy layer (Geoscape) and battles. Battle difficulty can be set independently in the INI for version 1.33. At lower difficulties, one will find the game not very different from the original and the methods that most players normally employ will work with no problems.

Many of the imbalanced aspects of the strategic layer have been corrected and the difficulty level affects the options the aliens can take in response to X-COM's interference in their agenda. Many things have been balanced by comparing each element to other elements in the game, if possible: UFO plasmas have standard ranges and power. The human plasma cannon is comparable to the aliens. The laser cannon is more powerful than the cannon and more suited to dealing with small ~ medium range threats while the plasma cannon is better against large craft.

Various aspects of the economy has been revised and balanced: All alien artifacts have had their production and selling prices altered, based on a relation to laser weapons. The selling price of alien artifacts is affected by the status of the member nations. The country bonuses to monthly income for good performance have been increased in 1.33.

In previous versions, each bug fix and mod could be independently enabled or disabled by the player. In version 1.32, this is changed so that most bug fixes are enabled by a single option and the difficulty level determines what other elements are active. Players choose which elements to play by selecting the appropriate difficulty level.

=Difficulty Settings=
Here is a breakdown of features for each level of difficulty. Most of these options stack upon the ones of the previous difficulty:

Beginner
*All Bug Fixes enabled.
*Alien unit hp and stats reduced in combat. (vanilla game setting)
*Retaliation ships vary depending upon game time.
*Alien Containment is now limited to 10 aliens per facility, as per the description (the maximum is still 50 for all bases.)
*When a UFO is destroyed during the anti-aircraft portion of base defense, the interval until the next UFO arrives is longer.
*Game ends if all nations sign pacts.

Experienced
*Alien units have full stats in combat. (vanilla game setting)
*<s>Living Quarters and Laboratory use the capacities as defined in FACIL.DAT. (30 for living quarters and 10 for laboratories.)</s>

Veteran
*Craft/UFO data and craft/UFO weapons stats balanced. [moved here in 1.32.2]
*Economic model balanced. ''Values may need to be tweaked depending on play testing and feedback.'' [moved here in 1.32.2]
*The selling price of alien items drops as nations sign pacts.
*Score for civilians higher in Terror missions. [moved here in 1.32.2]
*Soldier can only MC one unit per turn.
*UFOs take more damage before crashing.
*Alien Base daily penalty increases the longer the base is active.
*Zombies will hatch into chryssalids after several turns if fire not used against them.
*Alien AI in interceptions.
*Random elerium recovered per ball.
*Battleships bomb the access lift when attempting to invade an X-COM base. [moved here in 1.32.2]
*An additional alien mission at game start. {1.32.8}
*Changes to the mission routines to make harvester and abductor UFOs appear more frequently. {1.32.8}
*Alien leaders will only appear on "capital" ships and commanders will only be in bases. {1.32.8}
*Only alien soldiers and terror units are present in terror missions. {1.32.8}
*When a UFO is destroyed during the anti-aircraft portion of base defense, the interval until the next UFO arrives is shorter than Beginner/Experienced. {1.33}

Genius
*Terror Site will expire even if there is an inbound dropship.
*Battleships can perform terror missions.
*<s>Alien will use base busters after failed attempts to assault an X-COM base. {1.32 only} </s>
*Two additional alien missions at game start.
*Game ends if too many nations sign pacts.
*UFOs take more damage to crash than previous level.
*The effect of nations signing pacts on prices for alien items is higher.
*Alien ships attack base defenses.
*A Missile Defense will spend money when attacking
* <s>A Fusion ball defense requires 4 blaster bombs in base stores to activate.</s> {1.32.8}Fusion Ball Defense requires 4 Fusion Bombs in base stores to activate.
*{1.32.8}Game will not end due to two consecutive months of extremely low scores but rather from getting high scores. The threshold value is determined by game difficulty.
*{1.33}When a UFO is destroyed during the anti-aircraft portion of base defense, the interval until the next UFO arrives is shorter than Veteran.
*{1.33}Plasma Defense requires 8 units of elerium to activate.
*{1.33}Aliens will performing strafing or bombardment of a base after they fail to invade it:
**Battleships will launch bombs against random facilities.
**Other UFOs will attack only a limited choice of facilities.

Superhuman
*<s>Aliens use base busters quicker. {1.32 only} </s>
*UFOs take even more damage to crash.
*Three additional alien missions at game start.
*Aliens will conduct more terror missions as game progresses.
*Average amount of elerium recovered is lower.
*The effect of nations signing pacts on prices is severe. {1.32.8}
*<s>A Fusion Ball defense requires 6 blaster bombs in base stores to activate. {1.32}</s>
:--------------New in version 1.33-----------------------
*When a UFO is destroyed during the anti-aircraft portion of base defense, the interval until the next UFO arrives is shorter than Genius. (but still longer than the original setting.)
*After the first failed attempt to invade '''any''' base, the aliens will not attempt to invade a base again and only perform strafing or bombardment on any bases discovered.

=Interception stances=
*Standoff: No changes from vanilla.
*Cautious: Aircraft closes to longest weapon range. {"True Cautious Mode enabled: With two similar weapons only one will fire until ammo is depleted before attacking with the second weapon. Cannon/beam weapons fire slower. Imparts a -15% to UFO accuracy.} Clicking on the status button again will toggle the right weapon on/off {1.33}.
*Standard: Aircraft will close to weapon range for both weapons and both similar weapons will fire. Cannon/beam weapons fire at a standard rate.
*Aggressive: Aircraft move as close a possible to the UFO. Cannon/beam weapons fire faster. UFOs receive a 10% bonus to hit.
*Abort: When alien interception AI is active, aircraft that are slower than UFO cannot automatically escape unless another craft is intercepting (or UFO gives up.) Imparts a -30% to UFO accuracy.
:''Missiles fire rates are the same in all stances.''
</tabber>

==Extender INI references==

===Video===

* '''Video Pitch''': fixes garbled video output due to pitch error similar to f0dder's loader.
* '''D3D''': replace DirectDraw calls to Direct3D9. It sets the monitor to its default resolution and uses D3D to stretch the image on screen. It may also fix the speed issues if your video driver is configured properly.
* '''HQ4x''': raise the resolution of the game and apply some filtering. It is quite CPU intensive though...
* '''Linear Filter''': Enables bilinear filtering. Set to 2 to prescale the game (makes game less blurry in full screen mode).
* '''D3D Fullscreen Width''': Set the width (pixels) for fullscreen.
* '''D3D Fullscreen Height''': Set the height (pixels) for fullscreen.
* '''D3D Windowed''': run the game in a window.
* '''D3D Window Position''': set the initial position of the window in X Y cooordinates.
:=0 0 will have the windows placed in the upper right corner of your display.
:''These numbers will be updated automatically if the window is moved later.''
* '''D3D Window Width''': set the width (pixels) of the game window. ''This is the actual playable area. Borders will add extra pixels to the entire window.''
* '''D3D Window Height''':set the height (pixels) of the window. ''The title bar and border will add to the height.''
* '''Screen Ratio''': add black bars to keep aspect ratio on non 16:10 monitors (based on patch from mikawo) for full screen mode only. '''''Use common display resolution terminology to specify the aspect ratio: 16:10, 16:9, 4:3, etc [version 1.31.5 or later.]'''''
:''In prior versions, this setting was based on a formula with the idea that a value of 1 specified 16:10. Players needed to calculate what this value should be depending on their monitor: For example, the formula to get a 4:3 ratio is: 4/3x = 16/10, which equals 1.2 (or 0.83333 depending on where one wishes the black bars to be on the display.) ''
* '''Always On Top''': force the window to be in the foreground.
* '''Clip Cursor''': prevents the cursor from going outside the window.
* '''Scale Mouse''': attempt to fix the cursor running off screen when using HQ4x and/or D3D in full screen mode.
* '''Slow Geoscape Clock''': [Two Modes: =1 or =2]
:=1: The speed buttons reflect how fast time passes for each second of real time. ''Time will pass faster at the lowest rate. This option does not produces the step effect that other speed mods do. A small side effect is that the globe doesn't rotate as fast when the time frame is at a lower rate.''
:=2: Similar to Mok's Clock mod. The buttons reflect the rate of time at which the clock will change. ''This option produced a jumping effect at higher time rates.''
* '''Interception Delay''': This will slow animations and the passage of time in interception windows. The player specifies the amount of time in milliseconds [version 1.32 or later.] ''Only up to 2 or 3 milliseconds should be necessary.''
* '''Battlescape Delay''': All animations and scroll speed will be slowed. The player chooses the amount time in milliseconds. The value should be any number over 4. The higher the number the greater the effect. ''Too high and the player will experience lag. The player can further fine tune the movement speeds and shot animations from the options menu buttons.''
* '''Force Language''': Tired of selecting your language every time the start the game? This is for you. Options are 1,2,or 3.
* '''Skip intro''': Skip the movie when you start the program.
* '''CPU Mask''': force the process on a specific processor (1 is processor 0, 2 is processor 1, 4 is processor 2, etc).
* '''High Priority''': run XCOM with "above normal" priority
* '''Max FPS''': limit the framerate for the ones that cannot get vsync working. Not as smooth as vsync limited, but better than nothing (only works with D3D or Video Pitch enabled). ''Use this as an option in conjuction with, or as an alternative to, the Geoscape Clock and Battlescape Delay mods if your still having animation speed issues or the other mods cause any lag with the mouse cursor. Use this if using Video Pitch and shot speed is too fast in battles, even with Battlescape Delay set.''

=== Mods ===

* '''Doubleclick Movement''': change the requirement for moving a unit in the battlescape from clicking a tile once, to doubleclicking it (within 500ms). Failing to doubleclick will result in no action being taken. This allows for a considerable safety margin with movement, as the default movement controls are easy to accidentally trigger on the wrong tiles.
* '''TFTD Doors''': open a facing door by right-clicking. The time cost is 4 TUs.
* '''De-equip crafts''': provides an option to remove a weapon from an aircraft slot.
[[Image:Deequip.png|center]]
* '''Reorder soldiers in craft''': Move soldiers up or down via a simple interface. If you hold the mouse button for more than 200ms when clicking, the soldier will be moved to the top/bottom of the list. You can check the soldiers' stats by clicking on their names.
[[Image:SoldiersPosition.png|center]]

* '''Save Reserve Mode''': keeps the chosen TU reserve mod between turns.
* '''Keep Base Navigation Modules''': keeps the navigation controls that are in the base control center after a successful base assault.
* '''More Chryssalid Sound Effects''': victims will howl during zombification and newly emerged Chryssalids scream.
* '''Alien Inventory''': get direct access to an alien's inventory when it is mind controlled.
* '''Alien Bleeding''': most aliens will suffer from fatal wounds.
* '''More Reaction Fire''': Units turning in place will provoke reaction fire from enemy units that can see them. ''In scenarios where a quick exchange of multiple reaction fire occurs, the weapon fire may remain what the previous reaction shot was. Alien units with grenades may toss them in a wrong direction.''
* '''Hot grenades''': <s>They do explode even when held.</s> Grenades do not have a timer and explode after they are thrown. Only high explosives have a timer.
* '''Stunned Units KIA''': Usually, unconscious units just disappear when they blow up. Now you score the kill when you blast stunned units with explosives (with the experience, morale and all the stuff that goes with it).
::::::::[[Image:Blasted1.png]] [[Image:Blasted2.png]]
:In case of XCom units destroyed that way, they'll no longer go MIA but KIA

* '''No Blaster Bomb Drift''': disable the randomness applied to blaster bomb trajectories between waypoints. It'll solve drifting issues experimented with the blaster launcher, but also make aliens even more deadly with that weapon since the hard coded accuracy of 55% they have won't affect their shots anymore.
* '''More Smoke''': set the limit of smoking tiles to 2048 (up from 400). I don't expect this to work perfectly on the first try; smoke is referenced on lots of places and I'm not sure I patched everywhere needed. Report what works and what fails. ''You won't be able to load a saved game that used this option when this option is not enabled.''
* '''Heavy laser''': This adds 2 firing modes to the heavy laser. <s>Firing the weapon will cost 50 energy.</s> ''version 1.31+: Each mode has a recharge time cost.''
::'''Burst mode''': you select 3 target points, and the soldier will shoot a 5 shots burst (on each and between points). Recharge time: 2 turns.
::[[Image:burst1.png]] [[Image:burst2.png]] [[Image:burst3.png]]

::'''Full auto''': you select 2 points, the soldier will spray the area inbetween with 8 shots. Recharge time: 3 turns.
::[[Image:fullauto1.png]] [[Image:fullauto2.png]] [[Image:fullauto3.png]]

* '''Stun Fest''': Add the "Stun" command in the menu for most weapons. The TU/Damage is based on the weapon's class:
:::::::::<table {{StdCenterTable}}>
:::::::::<tr {{StdDescTable_Heading}}><th align="left" width="150">Weapon Class</th><th width="90">Stun Damage</th><th width="75">TU %s</th></tr>
:::::::::<tr><th align="left">Pistols</th><td>20</td><td>15</td></tr>
:::::::::<tr><th align="left">Rifles and small launcher</th><td>50</td><td>40</td></tr>
:::::::::<tr><th align="left">"Heavy" weapons and auto-cannon</th><td>65</td><td>50</td></tr>
:::::::::<tr><th align="left">Launchers</th><td>80</td><td>80</td></tr>
:::::::::<tr><th align="left">Stun Rod (unchanged)</th><td>65</td><td>30</td></tr>
:::::::::</table>

* '''No Auto Wake Up''': stunned unit still have their stun level decrease, but they won't wake up on there own
* '''No Alien Freak Out Messages''': don't show "Alien Commander has panicked" and the like messages. ''With CE, you'll only see this message if the alien is visible to the player.''
* '''Auto Sell''': allows the player to activate an automatic production and automatic selling mode in manufacturing. By pressing the down arrow button to reduce the quantity of desired items below zero, the mode will switch to the autosell mode, represented by three dollar signs ("$$$"). In this mode, production will never cease unless resources become unavailable, and all produced items will be immediately sold. By pressing the down arrow a second time, it will switch to autoproduce mode, represented by three asterisks ("***"). This functions in the same way as autosell, but the results will not be sold, merely stockpiled forever; caution should be used with this mode, as it can drain resources quickly
* '''Start With All Missiles''': Craft cannons and ammo will be sold and an equivalent price of Avalanche launchers and missiles will be bought. Crafts will be automatically equipped with the new items.
* '''Assign All Personnel''': Set the maximum amout of scientists/engineers on a project quickly by using the down arrow when the quantity is at zero (à la ET)
* '''General Store Capacity''': change the capacity of general stores (default is 50). Capped at 187 to prevent integer overflows. ''This is the value that the base stores will have. Any value below below 51 is ignored and the default value is used.''
* '''Rank In Inventory''': The icon for the character's rank will be displayed on the inventory screen.
* '''Show Money''': shrink the clock in the date/time panel on the main geoscape screen, and adds a funds display above it. It is useful for examining remaining funds during manufacturing projects, while waiting for time to pass.
* '''Base Build Stacking''': You can place base stuctures in advance. The construction will start when possible:

:::::::[[Image:Queue1.png]] [[Image:Queue2.png]]

:Funds are credited when you place an element. No refund is possible. There might be some issues with 2x2 structures, report any problem you encounter.
* '''Fast Base Defenses''': remove the wait periods during base defense sequence. The need to press the button can be removed too
* '''Improved Laser Tank''': The tank stats are improved but it requires Alien Alloys to produce. ''In-game UFOpaedia will display the updated information on the new tank.''
* '''Know Thy Enemy''': Damage is reduced against targets until an autopsy has been preformed. There is a small chance that a "lucky" shot will do full damage. Explosives and Fire are not affected. ''The reduction only affects the damage that is applied against a unit's health not armor.''
* '''Ablative Armor''': No changes for AP weapons but armor is more effective against HE, laser, and plasma. However, these attacks quickly reduce the armor in the location hit. In regards to the armor value used to determine stun damage applied to a target, the stun rod is treated as an AP attack but the Stun Bomb is treated like HE. ''Neither stun attack damages the armor.''
* '''Alternate Weapon Loadouts''': reduces ammo carried by the aliens. ''This balances the game after implementing the Recover Clip Fix. Players will recover more clips than originally expected.''
* '''EU2012 Item Rules''': Alien weapons have a high chance to self-destruct: A unit dying to direct damage has a high chance of destroying the weapon. Explosions leave no items behind. Panicked units don't drop items. Fire is bad for high tech items.
* '''Weak Sectoids''':Sectoids will have heavy plasmas replaced with rifles or pistols depending on rank. Only sectoid engineers will carry blaster launchers.
* '''Zombies Will Hatch''': Zombies will automatically convert to Chryssalids after a few turns. The resulting "mature" Chryssalid will have stats based on game difficulty. Killing a zombie will result in an "immature" Chryssalid emerging. Fire is still the only means to kill a Chryssalid in a zombie. Fire damage slows the hatching process. ''Any amount of fire damage will delay the Chryssalid's hatching.''
* '''Human Limits''': Engineers and Scientists will work in 12 hours shifts. The project screen will assign two people per click but only one space will be used between them. Research and production times are adjusted accordingly.
* '''Alternate Research Tree''':
**=1
***Laser cannon requires research into E-115 and UFO power to produce and E-115 is a production material.
***Plasma weapons and Blaster Bombs require "help" from various alien engineers to obtain the knowledge to produce.
***Hyperwave may require multiple species navigators to be interrogated in order to be finally unlocked. (depending on game difficulty)
***Only a Etheral can give the required technology to unlock Psionics. Sectoids provide other options.
***Improved detectors after the correct technologies have been researched or can be produced.
***Quicker access to Mind Shield with the right research and Psionic testing.
**=2 ''Alternate progression for laser weapons''
***The first breakthrough allows the production of Heavy Lasers but damage is minimal.
***Each new level researched allows a new item to be made and increases the damage for the prevous stage(s) items.
* '''Difficulty Level of Interception''': adjusts the difficulty of hitting UFOs. [values from 1-5]
* '''Manual Interception Fire Mode''': craft will no longer fall back when the last shot is expended or when damage is taken
* '''True Cautious Mode''': craft with two similar weapons will only fire one-at-a-time and the stance gives a penalty for UFO's accuracy (-10%).
* '''Crafts Always Ready''': change when craft are available after returning to base.
::=1 allow crafts to take off even when not 100% refueled/rearmed/repaired.
::=2 only damaged craft are grounded.
* '''Retaliate Against Ground Assault''': Aliens do not seem to care if you assault a landed UFO. You can now have them retaliate as if their ship was shot down. ''Note that this was not extensively tested so feel free to report any odd thing that may happen when this patch is activated!!-Seb76''
* '''No Funkers''': only guys that went on the last mission are checked for promotion.
* '''Bloodthirst''': compute the "promotion score" based on killing stats only
* '''Disable Base Defenses''': disable the base defence mechanism. Useful if you want to use some defence modules for tactical purposes. ''This is unnecessary if the Base Retaliation Loop Fix is enabled, since it allows right-clicking to disable defenses.''
* '''Surrender Defense Missions''': [[Making_the_Game_Harder#Base_Defense | Surrender Defence Missions]]
* '''Initial Alien Bases''': [[Aliens_Own_Earth | Initial Alien Bases]]
* '''Funding Council Income Only''': [[Making_the_Game_Harder#Funding_Council_Income_Only | Funding Council Income Only]]
* '''Limited Military''': [[ Making_the_Game_Harder#Limited_Military | Limited Military ]]
* '''Max Aliens''': Setting this will make the game treat all combat as if the game was on Superhuman difficulty despite the actual difficulty of the game. This will affect the number of aliens created and those stats which are affected by the normal rules for the difficulty setting. [''Version 1.32 only'']

=== Bug Fixes ===
''These fixes are '''not''' enabled by default.''
::* '''Tactical Scroll''': Enable/disable the fix that reduces the scroll speed in tactical mode
::* '''Animations Speed''': reduce the speed of in-game animations (cursors, fire, smoke...) [''moved to video in version 1.32'']
:::: ''Both of these and other battlescape speed issues are addressed by the Battlescape Delay feature.''
::* '''Intro Sounds''': restore the sound effects during the intro
::* '''Music Change Freeze''': try to prevent the freeze that happens ingame when the MIDI music changes (experimental)

'' The following fixes are enabled by default. There is no listing for each one in the INI and no other actions are required by the player to use them. Any can be disabled by copying the appropriate line(s) from the bug reference file, which is included with the Extender, to this section in the INI.''

* [[Known_Bugs#Radar_Stacking | Radar stacking ]] enabled. Credits go to [[User:Spike#Base_Fixer | Spike]] for I used something close to his formula.
* [[Known_Bugs#Funky_Fire | Funky fire]] fix: Fire/stun damage applied at the end of each X-Com and Alien turn. ''Units standing on a tile with fire will be damaged as well as those units that are immolated.''
* [[Known_Bugs#Collectors_Edition_Blaster_Bomb_Bug | Vertical waypoints blaster bomb bug]]
* [[Known_Bugs#Door_jam | Door jam]] fixed.
* '''Personnel Overflow''': [[ExploitsA#Robotic Factories|Robotic Factories]] / [[ExploitsA#Cybernetic Laboratories|Cybernetic Laboratories]]. You cannot get more than 255 engineers/scientists, buying more will just result in them being lost during transfer.
* [[Why civilians go rogue | Hostile Civilians]] fix. All units under mind control will have their proper faction restored after recovering thier wits.
* '''Crash On First Move''': Fix occasional crash when moving your first unit out of the craft.
* '''Tactical Sounds Fix''': fixes problems with snakeman, celatid, and zombie movement and the mind probe and stun rod sound effects.
* '''Craft Weapon UFOpaedia Fix''': Accuracy is correct, Re-load time is obtained from correct dataset, and flavor text added. UFO weapon range is now in KM and all numbers positioned better.
* '''UFOs Respond to Interception''': UFOs will close to weapons range when attacked. Craft that are slower than their attacker cannot abort* but the stance does give a strong defensive bonus. Also fixes the last shot missing. [*version 1.32: slow craft with a wingman present can abort.]
* [[Known_Bugs#Paying_For_Dirt | Pay for dirt]] removed.
* [[Known_Bugs#Phantom_Radar | Phantom radar bug]] fixed. Radar coverage is updated when facilities are removed.
* [[Known_Bugs#Base_Disjoint_Bug | Base disjoint bug]] fixed. [[Image:Disjoint.png|center]]
* [[Known_Bugs#Base_Facility_Dismantle-Construction_Crash | Base Facility Dismantle-Construction Crash]]
* [[Known_Bugs#The_trouble_with_Mines_in_General | Armed state issues]] with proximity grenades when reloading a game. Should also fix [[Known_Bugs#What_just_exploded.3F | "What just exploded?"]]
* [[Known_Bugs#The_trouble_with_Mines_in_General | Experience issue]] with proximity grenades. The thrower now gets the experience, not the poor alien that blows up...
* [[Known_Bugs#Fuel_dump_on_transfer | Refueling issue]] when transfered crafts arrive (enabled by default if you use the "Crafts Always Ready" mod)
* [[Known_Bugs#Elerium-fueled_Craft_Bug | Elerium fueled crafts bug]] fixed.
* [[Base_Facilities#Displayed_Base_Maintenance_Cost_Bug | Displayed Base Maintenance Cost Bug]] fixed.
* '''Unconscious Unit MC fix''': A unit under mind control will have the effect removed and its proper faction restored when knocked unconscious.
* '''EOB fix''': Units under Mind Control are not lost if battle is won, or if they are in the xcraft when mission aborted.
* '''Tank/Cannon Ammo Storage Fix''': The tank/cannon ammo will not take up room in storage similar to Craft Cannon ammo.
* '''Clip Weight Fix''': Clip weight in weapons is correctly assigned to the unit and removed when the weapon leaves the unit's possession.
* '''Large Unit MC Fix''': All sections of a large unit will be correctly controlled on a successful mind control attack.
* '''Large Unit Explosion Fix''':Explosions will now only affect a large unit once and not per section.
* '''Large Unit Deaths''':Certain large units will not be "killed" multiple times at the end of the turn after dying from the initial attack. [version 1.32]
* '''Alien Weapon Selection Crash Fix''': fixes the crash after an alien throws a grenade and does not have another weapon available.
* '''Alien Attacks Base Location Fix''':An alien that attempts to attack one of the base's areas will not crash the game.
* '''Weapon Loadout Fix''': Corrects the weapon loadout on the small scout pilot and on the abductor's leaders.
* '''Change Sectopod Laser Modifer''': Removes the vulnerability to laser damage when 'Ablative Armor' mod is active since the armor rating is directly reduced by laser damage and the unit takes damage to its accuracy rating, which is closer to the description in the ufopaedia.
* '''Armor Modifer Fix''':Personal Armor is now assigned the correct category of damage modifiers.
* '''Zombie Fix''': Fixes the exploit where an MCed zombie that dies will give the player permanent control of the resulting Chryssalid. Also makes zombies to drop their weapons.
* '''No Freebies for Tanks''': Available tanks during Base Defense missions will get their ammo from what is available in the base stores.
* '''Recover Clips Fix''': Each ammo type on the battlefield is tallied and placed into a clip. Thus, only any leftover ammo that cannot make a full clip will be discarded.
* '''Tank Death Penalty Fix''': The penalty for losing a tank is fixed at 20 points, not based on the rank of the first unit in SOLDIER.DAT
* '''Slow Death Screams on Alien Turn''': puts a small delay after a death scream on the alien turn. Useful in Terror Missions for civilain deaths.
* '''Bezerk Unit Crash Fix''': Tanks will not suffer moral loss, and large units or units with in-built range weapons will not go Bezerk.
* '''Explosion Fix''': All explosions now behave the same for all walls. (if the proper byte for the tile is set in the MCD records.)
* '''Smoke&Fire Propagate Fix''': Fire and smoke will not spread through solid walls. (with the same provisions as above.)
:''The MCD records for Xcom Bases don't have the proper bit set for smoke and fire. A corrected set of files is [[:File:XBASEx.zip | here]].''
* '''Terror Mission Score Fix''': The score for each civilian in a terror mission is now [base score / number of civilian]. [version 1.32: the total score for civilians is determined by the difficulty rating, starting with veteran difficulty. The base score is {252*difficulty rating}. If the mission is aborted the base score gets set to 1008.] ''Removes the land-and-abort exploit to reduce the penalty of a terror mission.''
* '''Research Medic Crash Fix''': Researching an alien medic will no longer crash the game which happens under certain circumstances.
* '''Base Retaliation Loop Fix''': UFOs fire on base defenses and the aliens respond more logically at failed attempts to assault a base. Missile Defenses will spend money when activated. Fusion Ball Defenses require blaster bombs in base stores to work: 4 bombs required per unit on Genius difficulty, 6 for Superhuman.
* '''Grenade Throw Test Fix''': Removes the problem where units with high strength can't throw items when indoors or under something. ''Hypothetical: please report any issues! - [[User:Morgan525|Tycho]]''
* '''Alien Base Exploit Fix''': The aliens' monthly score for a base increases with game difficulty and the longer the base stays in operation.
* '''Base Defense Prep''': Players are taken to the base editor screen before starting a base defense mission.
* '''BB Exploit Fix''': Production materials are in the correct order and Sell Price adjusted.
* '''Staff Transfer Exploit Fix''': Engineers and Scientists being transferred at the end of a month still get paid.
* '''Alien Psi Attack Fix''': Aliens will only remember the location of an unseen target for 1 turn. ''Of course, a successful Psionic Attack may renew this memory.'' [version 1.32: aliens randomly target known units and will give preference to those units in line of sight. Aliens are more likely to only panic units not in line of sight.]

=== Tactical AI ===
*'''Apply''': Aliens are less indecisive and more aggressive.
*'''Autofire Distance''': The number of squares that if a target is within, an alien will try to use autofire against it.
*'''Snap Distance''': The number of squares that an alien will use a snap shot against a target. Otherwise, alien will try to use an aimed shot.

=== Equipment Screen ===
This patch changes the equipment screen. It effectively renders [[Statstrings|statstrings]] obsolete ;-)
*Before battle, it changes the screen like this (the psi stats are only shown when the soldier has been trained):

[[Image:Equip.png|center]]

*During a mission, it looks like this:

[[Image:Ingame.png|center]]

*You can also have the rank shown:

[[Image:Rank.png|center]]

*Show Grenade State: if you select a primed grenade, it'll be indicated in the description
*Save Equipment: automatically reequip your team with their last weapon layout ('''HIGHLY EXPERIMENTAL'''). New recruits will be given a gun and some ammo but nothing outstanding. Don't forget to properly equip them
*Auto Flares: automatically equip flares (if available in the craft) during night missions (only works with Save Equipment)

=== Range Based Accuracy ===
This modifies the accuracy based on the distance from the target. The accuracy decreases linearly (2% per tile) when shooting beyond the limit of the firing mode:
* auto shot: 7 tiles
* snap shot: 15 tiles
* aimed shot: no penalty
These values should be considered as a first draft; they are configurable in the ini file so feel free to test other settings and report back if you find good ones.

[[Image:Acc0000.png]] [[Image:Acc0001.png]] [[Image:Acc0002.png]]

''Advanced options''
*Add these lines to your INI in the [Range Based Accuracy] section

::Aimed Penalty Distance=200
::Auto Accuracy Dropoff=2
::Snap Accuracy Dropoff=2
::Aimed Accuracy Dropoff=3

:''Change the numbers to your own personal preferences. Remember that the distance number is twice the number of hexes on the battlescape.''

=== Line Of Fire Check ===
A soldier will need a line of fire toward the targeted alien to use psionic device. It is configurable for each ability:

*Mind Control
*Panic
*Mind Probe

=== Music ===
==== PSX CD ====
If you have the PSX version of the game, you can enjoy the CD music with this patch. The tracks are mapped like that:
* 1,2,3,4: geoscape music
* 5: gmdefend
* 6: gmenbase
* 7: gmmars
* 8: gminter
* 9: gmstory
* 10,11: battlescape music
* 12: gmnewmar

gmwin and gmlose are not available. Because of similarity, gmlose is replaced with gmstory and gmwin with gminter.

==== MP3 music ====
If you have mp3 music files available for the game, you can use them instead of the default MIDI ones (see default ini file as an example). Note that the intro music will still use the original files.

:Battlescape=*tactical*.mp3
:Start Menu=*Final Briefing*.mp3
:Bad Ending=*Final Briefing*.mp3
:Good Ending=*intercept*.mp3
:Geoscape=*Geoscape*.mp3
:Dogfight=*intercept*.mp3
:Mission Debriefing=*Debriefing*.mp3
:UFO Assault=*Briefing1.mp3
:Base Defense=*Briefing2.mp3
:Base Attack=*Briefing1.mp3
:Mars=*Debriefing*.mp3
:Terror Mission=*Briefing2.mp3

''Note that the above files are only an example. You can change the music played during any event by changing the file name. All files must be in a folder named MP3 which should be in the same list as the SOUND folder.''

=== Initial Base ===
Change the layout of your starting base.
Possible modules:
*AccessLift
*LivingQuarters
*Laboratory
*Workshop
*SmallRadar
*LargeRadar
*MissileDefense
*GeneralStores
*AlienContainment
*LaserDefense
*PlasmaDefense
*FusionBallDefense
*GravShield
*MindShield
*PsionicLaboratory
*HyperWaveDecoder
*HangarTL
*HangarTR
*HangarBL
*HangarBR
*Empty

=== Wreck Analysis ===
Until the construction of hyper-wave decoders, it is impossible to know what missions aliens are performing. Even after recovering an alien ship, XCOM intelligence is unable to determine what was its purpose. This is no longer true. Salvaged navigation modules can now be analysed and may reveal what evil intentions the aliens had:

::::::::[[Image:Wreck_analysis.png]]

The probability of retrieving the information is based on the difficulty and on the number of UFO navigation items recovered from the mission. UFO mission and geographical zone can be discovered individually too.

=== Craft Ready Message ===
A message will notify the player when a craft is ready.
::::::::[[Image:CraftReady.png]]

=== Roswell mod ===
Make scout ships possibly crash during their missions:

::::::::[[Image:Roswell.png]]

It can happen to all scouts, either detected or not. Crashed UFOs will be made visible so that you can initiate recovery missions.

=== Shortcuts ===
Enable keyboard shortcuts. The keymap is qwerty.

==== Default key mapping in geoscape ====
*UpArrow: Rotate Up
*DownArrow: Rotate Down
*LeftArrow: Rotate Left
*RighArrow: Rotate Right
*MouseWheelUp: Zoom In
*MouseWheelDown: Zoom Out
*1: Geo Speed1
*2: Geo Speed2
*3: Geo Speed3
*4: Geo Speed4
*5: Geo Speed5
*6: Geo Speed6
*MouseMiddle: Intercept
*B: Bases
*G: Graphs
*U: Ufopaedia
*Escape: Options
*F: Fundings

==== Default key mapping in battlescape ====
*UpArrow: unit goes up
*DownArrow: unit goes down
*LeftArrow: left menu
*RightArrow: right menu
*Return: end of turn
*Escape: options menu
*BackSpace: go to next unit, remove current from the queue
*Tab: go to next unit
*Space: go to inventory
*PageUp: view goes up one level
*PageDown: view goes down one level
*1: reserve mode off
*2: reserve mode snap
*3: reserve mode auto
*4: reserve mode aimed

==== Key names ====
Standard keys (A, 2, etc) are indicated as-is, the following "special" keynames are available (case insensitive):
{|
|
*Back
*BackSpace
*Back Space
*Tab
*Clear
*Return
*Enter
*Shift
*Control
*Menu
|
*Pause
*Escape
*Space
*Prior
*PageUp
*Next
*PageDown
*End
*Home
*Left
|
*Up
*Right
*Down
*Print
*Insert
*Delete
*Num0
*Numpad0
*Num1
*Numpad1
|
*Num2
*Numpad2
*Num3
*Numpad3
*Num4
*Numpad4
*Num5
*Numpad5
*Num6
*Numpad6
|
*Num7
*Numpad7
*Num8
*Numpad8
*Num9
*Numpad9
*Multiply
*Add
*Separator
*Subtract
|
*Decimal
*Divide
*F1
*F2
*F3
*F4
*F5
*F6
*F7
*F8
|
*F9
*F10
*F11
*F12
*MouseMiddle
*MouseWheelUp
*MouseWheelDown
*MouseWheelLeft
*MouseWheelRight
|}

If you need a key not listed here and you know its VK_* code, you can specify it with it's hex value (e.g. 0x90 for num lock)

The implementation is rather messy, expect side effects and report them...

=== Caps ===

: This sections sets the highest number for each stat to which it can be raised by in-game methods. See [[Experience#Regarding_Caps | experience caps]].

=== OBDATA.DAT patching ===
Change the value of some OBDATA.DAT settings on the fly.
To change a value, add a line "itemname setting=value" (without the quotes). For example:

High Explosive Damage=200

Available settings:
*Damage
*Resistance (to explosions)
*Weight
*Damage Type
*Auto accuracy
*Snap accuracy
*Aimed accuracy
*Auto TUs
*Snap TUs
*Aimed TUs
*Size (clip size)
*get

Item names are case insensitive and available at [[OBDATA.DAT]].

=== Text ===
''This section contains almost all of the strings that are used in the Extender. Useful for multiple languages. To change one, modify the text after the equal sign. Others may require that you copy the appropriate line to the [Text] section of the INI.''
*equipment screen texts
::Weight=Weight>
::Accuracy=Accur>
::Reaction=React>
::Psi Strength=P.Str>
::Psi Skill=P.Skill>
::Primed=primed

*Roswell mod texts
:{Terrain names}
::Jungle=Jungle
::Farm=Farm
::Mountain=Mountain
::Desert=Desert
::Polar=Polar
:{Dialog strings}
::RoswellTitle=UFO Incident
::Roswellinfo=Crash reported
::Location=LOCATION
::Type=TYPE
::Terrain=TERRAIN

*Wreck Analysis
::Zone Discovered=Intel found out that the %s UFO was raiding %s
::Mission Discovered=Inspection showed that the %s UFO was on an %s mission
::Both Discovered=Ship investigation revealed that the %s UFO was on an %s mission in %s

*Craft Ready
::CraftReadyTitle=Aircraft ready
::CraftReadyInfo=A craft has been refitted

*Other
::research needed=research needed
::to produce=in order to produce
::full auto=Full Auto
::burst shot=Burst Shot
::laser rifle=The laser rifle is lighter and more accurate than the older design.
::plasma cannon=This is a devastatingly powerful weapon based on accelerating particles from within a minute anti-gravity field.
::base strike=
::ship crash=
::lift hit=
::detector=
::gravshield=
::avalanche=This heavy air-to-air missile is designed to attack bombers and large craft. It is less useful against smaller, more agile targets.
::fusionball=This launcher fires missiles propelled by an anti-gravity system. A massive anti-matter explosion is created when the weapon reaches its target.
::rental=Craft Maintenance
::firestorm=An experimental unmanned craft that replicates the classic saucer design. Faster and more maneuverable than any other conventional aircraft.
::base control=ALIEN BASE CONTROL
::production time=Days/Hours Left To Next Unit
::MeleeText=Hit

''To make the text appear for another language setting add _1 or _2 to the end of the last word before the = sign. For example, if the first language button is English and the second is Spanish:''
MeleeText_1=golpear
''Would make "gopear" be listed for the "hit" option on stun weapons or melee attacks if Spanish was the chosen language.''
----
<blockquote>
'''Hacks '''

:''This section is not part of the normal INI but are available. These hacks heavily alter the gameplay and should only be used for testing purpose. Those options with a <s>strike-through</s> are not available in release versions. [currently in 1.31, no hacks are available.]''

* <s>Prevent game over when score is really bad at the end of the month </s>
* Big brother: follow all units in combat.
* Alien pets: Alien turn handed over to the human player
* <s>Show All Locations: displays all active locations, detected or not.</s>
* FPS: show an FPS counter in the geoscape. Mostly used for debugging D3D.
* <s>Directly Use Alien Weapons: After all a gun's a gun, you just pull the trigger. When activated, you can use all alien items you recovered. Of course you still do need to research items before you're able to manufacture them!</s>
* <s>No Alien Psi: no more psi trouble when fighting sectoids/ethereals</s>
</blockquote>

[[Category:Enemy Unknown/UFO Defense]]

ROUTES.DAT

2016-01-09T03:42:39Z

Morgan525: /* Structure */

This file is only used by tactical saves.

It is a collection of all nodes on the map, and uses much the same format as the .RMP files in the [[ROUTES|routes]] folder. Aliens and civilians are placed randomly amongst these nodes when combat begins, and (prior to spotting your units) patrol between them.

If a unit cannot be placed because you've run out of appropriate nodes, it'll use a non-appropriate node instead. This means that sometimes alien leaders won't be inside their ships.

X-Com units don't spawn according to these nodes if you use an Avenger. Need to test the other craft, and base offense/defense missions. - BB

After a new tactical map has been generated from the small map sections, the records are read from the corresponding .RMP files in order of left to right, top to bottom. However the X-Com and Alien craft nodes are always saved until last, and so appear at the end of the file.

Each record is 24 bytes, so the total file size is equal to that times the amount of records in the entire map. Decimal/Hex offsets:

== Structure ==
0/00 - X position of node.

1/01 - Y position of node.

2/02 - Z position of node.

3/03 - Map section counter. All nodes from the first map segment will have this flagged as 0, the nodes from the next map segment as 1, the next segment 2, and so on.

4/04 - 18/12 - Each node can connect to multiple other nodes. These 15 bytes contain 5 records of 3 bytes each, detailing those connections:
*0 - The record number of the connected node. 255/FF if unused. When the game engine pieces the small map segments together, if an external node can't be connected, the spare connection record will be disabled. A common example is a connection that would make a unit walk off the playing field. For external node connections this number is FE:North, FD:East, FC:South, FB:West.
*1 - The distance to the connected node. If the connected node was not originally in the same .RMP file, this is calculated by adding the two connection distances together.
*2 - The type of unit that can travel along this connection.
0 = Any
1 = Flying
2 = Flying Large
3 = Large
4 = Small
<blockquote>Check the discussion page for these values, because they are probably wrong</blockquote>

19/13 - The type of unit that can spawn at this node.
0 = Any
1 = Flying Small
2 = Small
3 = Flying Large
4 = Large

<blockquote>Check the discussion page for these values, because they are probably wrong</blockquote>
<blockquote>At least, modulo 8. The above is exhaustive only for reference data in the routes folder, and non-UFO nodes in Battlescape saves.

Bit 3 (value 8) Spawn point used flag. Set so another unit can't spawn here at the start.

Bit 4 (value 16) may be set for nodes sourced from UFO reference data...and furthermore is sometimes changed by processing during the alien turn for these nodes. Presumed (needs more testing): in patrol mode nodes sourced from UFO reference data, the AI explicitly prefers (but is not guaranteed to) to stop moving on nodes with bit 4 set.

Bits 5-7 are uniformly 0 for medium scouts. Other UFO types have not been verified yet. Neither have terror sites or alien bases.</blockquote>

20/14 - The rank, or the team, of unit that can spawn at this node. (Misc1 is only used on TFTD, Misc2 appears on both games)

0 = Civilian / "Scout"
1 = X-Com
2 = Alien Soldier
3 = Alien Navigator
4 = Alien Leader / Commander
5 = Alien Engineer
6 = "Misc1"
7 = Alien Medic
8 = "Misc2"

21/15 - Ranges from 0 to 8, Daishiva calls this the "flags" byte. Governs whether an alien will attempt to destroy a base module. Apparently, the higher the number, the greater the chance the aliens will start shooting. So far, this has only been tested on an X-COM base defense mission but seems to hold. No other maps or modules have been tried.

An alternative explanation is that the number indicates the 'importance' of the node when the aliens are conducting their patrols. Using Bomb Bloke's graphics I've superimposed on the Battleship map the values for this flag on all the nodes:

[[File:Ufo_160_0_flags.gif]]
[[File:Ufo_160_1_flags.gif]]
[[File:Ufo_160_2_flags.gif]]

According to this theory the aliens will choose a node with the higher value 'flag' when their AI is set for patroling/guarding, unless it is already occupied. The Battleship schematics above show some proof of this, specially on the bridge area (the aliens that start on the bridge room usually never come out except to have a look outside the door). Now look at the plants for the Supply Ship:

[[File:Ufo_170_0_flag.gif]]
[[File:Ufo_170_1_flag.gif]]
[[File:Ufo_170_2_flag.gif]]

The ground and first level almost contains nodes with a 1 value, with a single exception - the 3 and 2 of the engine room. This should explain the aliens' behaviour of only using 1 of the UFO's 2 doors - when an alien moves into the node outside the door, it chooses instead to go to the node with the 3 value, and then to the 2 value, diverting the aliens from the 2nd outside door.

[[File:Ufo_140_0_flag.gif]]
[[File:Ufo_140_1_flag.gif]]

Next one is the Abductor. Usually the aliens don't come out much and you find a large number of them on the main chamber on the ground, due to the concentration of 3/4s that acts as a bottleneck.

Finally here's the remaining medium/large UFOs. Usually the higher value of this byte also corresponds to a high value on 23/17 (which makes sense due to the importance of the node to increase the probability of units spawned there - [[User:Hobbes|Hobbes]] 19:05, 27 January 2012 (EST))

[[File:Ufo_120_0_flag.gif]]
[[File:Ufo_150_0_flag.gif]]
[[File:Ufo_150_1_flag.gif]]

[[File:Ufo_130_0_flag.gif]]
[[File:Ufo_130_1_flag.gif]]
[[File:Ufo_130_2_flag.gif]]

22/16 - Always seems to be set to 0.
(the exception is also seen in TFTD, with a few maps having different values)
(there are also maps on UFO that contain this flag, such as 2 nodes on the Skyranger map that have a value of 10, 1 node on the Battleships that has a 1 value, etc. - some of those look more like coding errors though)

23/17 - Ranges from 0 to 10, Daishiva calls this the "spawn" byte. A value of 0 makes it impossible for a unit to spawn there.

==See Also==
* [[ROUTES|Routes Folder]]
* [[Alien_movement_patterns|Alien Movement Patterns]]
* [[Saved_Game_Files#Battlescape_Files|Battlescape Files]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

Talk:ROUTES.DAT

2016-01-09T02:37:27Z

Morgan525: cleaned up the grammar

Regarding offset 23, Zombie, were you attempting to "clarify" or "correct" it?

Previously it stated that 0-value nodes CAN spawn units, but only if all other nodes are taken...

- [[User:Bomb Bloke|Bomb Bloke]] 21:07, 26 August 2008 (PDT)

----
"Correct" it. In any case, 0-value "spawn" nodes can never have units placed there period. They are only used for alien pathfinding. If all the spawn points with values of 1 or greater get filled and there are still alien units waiting to be placed on the map yet, they don't. This follows the same basic premise as an auto-win base defense mission. --[[User:Zombie|Zombie]] 22:11, 27 August 2008 (PDT)
----
Some wild guesses about the "flags" byte on non-base missions: Aliens patrol around using the spawn points, but sometimes they "guard" a certain point. A theory is that the chance the next state is just guarding this spawnpoint is higher when the "flags" byte is higher. So they save TUs, thus making a strong defense(reaction shots). When the flags is zero, they will not stand still on the point and continue patrolling. You will notice that inside UFO's the values are higher, this makes that aliens inside UFOs have a higher defensive advantage.
So this byte can actually be called the "offensive (x-com base)/defensive (others)" decision score. --[[User:Daiky|Daiky]] 07:26, 21 July 2011 (EDT)

----

== Offset 19 (0x13) ==

According my observation this is a bit field
bit0 (1) = this node is only for flying units (mobility bit, used for '''spawning''').
bit1 (2) = this node is only for small units (used for '''spawning''').
bit2 (4) = this node is only for flying units (movement type).
bit3 (8) = this node was used for NPC placement (runtime bit).
bit4 (16) = this node is only for civilians (runtime bit, cleared when aliens nowhere else to go).
bit5 (32) = cannot be used as patrol point.
so
0 = Any (small walk, large walk, small flying, large flying)
1 = Flying (small flying, large fly)
2 = Small (small flying, small walk)
3 = Flying Small (flying small)
--[[User:Volutar|Volutar]] 05:29, 23 September 2011 (EDT)

From what I've made of the code concerning bit4, its used to keep units in patrol mode moving to new areas: It's set after it was selected as a destination and the unit reaches it. Once set, the AI will skip these nodes for patrol units when determining future destinations. -- [[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])

== Offset 20 ==
Actually it's not a "rank", it's more abstract version of "rank" which is used by many ranks (if there's no other appropriate spawnpoints left). At the end of priority list are points with value 0. Same value 0 used for spawning "scout" units, which are mainly spawned outside of UFO, and just hanging around (their AI have quite different route priorities). If there is no free spawn points found - unit marked as "dead" instead of spawning.

Scout 0
Commander 4 > 3 > 5 > 8 > 7 > 2 > 0
Leader 4 > 3 > 5 > 8 > 7 > 2 > 0
Engineer 5 > 4 > 3 > 2 > 7 > 8 > 0
Medic 7 > 6 > 2 > 8 > 3 > 4 > 0
Navigator 3 > 4 > 5 > 2 > 7 > 8 > 0
Soldier 2 > 5 > 3 > 4 > 6 > 8 > 0
Terrorist 2 > 5 > 3 > 4 > 6 > 8 > 0
XCom 1 > 0 > 2

So, 1st priority spawn points confirmed to be as they listed on main page. But almost any of these spawn point can be used by number of alien ranks, not only by those you assigned to.

0 = Scout/Any rank
1 = X-Com
2 = Soldier/Terrorist, Medic, Engineer/Navigator, Commander/Leader
3 = Navigator, Commander/Leader, Engineer/Soldier/Terrorist, Medic
4 = Commander/Leader, Engineer/Navigator, Soldier/Terrorist, Medic
5 = Engineer, Commander/Leader/Navigator
6 = ..., Medic, Soldier/Terrorist
7 = Medic, Commander/Leader/Engineer/Navigator
8 = ..., Commander/Leader/Medic, Engineer/Navigator/Soldier/Terrorist
--[[User:Volutar|Volutar]] 03:21, 26 September 2011 (EDT)

little note: "scout" is also a civilian spawn node, they also only spawn at 0 --[[User:Daiky|Daiky]] 15:30, 30 December 2011 (EST)

== Node link offset 2 (travel unit type) ==

This is a bitfield with values as mask for kind of units.

bit0 (1) = this node is only for units in fly mode (mobility bit).
bit1 (2) = this node is only for small units.
bit2 (4) = this node is only for flying units (movement type).
*bit3 (8) = this link was already processed for path estimation (runtime bit).

so
0= any units
1= units of any size in fly mode
2= small units flying or not
3= small units in fly mode
4= any size of flyers
5= any size of flyers in fly mode
6= small flyers
7= small flying flyers

Actually I dont know why there are TWO bits (0 and 2) which stand for flying... AFAIR every flying alien unit unable to walk, so they always have movement type "Fly" and mobility bit "fly mode" (like floaters, who are unable to use steps). Probably some of walking alien units was planned to have flying abilities, but abandoned for some reason.
--[[User:Volutar|Volutar]] 01:51, 27 September 2011 (EDT)

== Offsets 0x15 (21) & 0x16 (22) ==

They seems to be used for AI patrol route distortion for BaseDefence mission type.
Before (and including) 30th turn of battle Aliens seems to be attracted by route nodes having one of these (or both) flags set (as boolean field). It's more like a target points, and they seems to be not interested in others at all. But after 30th turn of battle Aliens seems to be wandering all over the place without paying attention on these flags.

It can be confirmed by clearing all these flags from XCOM base module maps, and setting them only for "lift" module nodes. Apparently they will be swarming around lift area, without trying to get somwehere else. But after 30 turn they must scatter.
--[[User:Volutar|Volutar]] 00:05, 28 September 2011 (EDT)
Yes, this was confirmed. Though if Alien spots your unit, it will pursue (in Snipe mode), no matter what routes and flags are
--[[User:Volutar|Volutar]] 00:51, 28 September 2011 (EDT)

I wonder why there are so-called targetpoints (flags 5 in base defense) in the small rooms around the hangar?
Also, on terror sites there are flags 1 (and I found a flags 2 on a roof). They seem to be somewhat random, however on maps with buildings, the nodes with flags 1 are mostly inside. An explanation may be that aliens are attracted to these flags 1 nodes as targetpoints, making aliens targetting the inside of buildings to terrorise civilians.
On larger UFOs, the flags seems to have the same value as priority? Which might be an error in the data? Or maybe the flags values are not used in UFOs at all. There is a theory that until a certain turn aliens will prefer to stay inside and around the UFO before spreading to the outside, this might be controlled by this flags.
On other terrain once and a while there is a flags 1 value, the rest is 0. It could be aliens walk around and stand still and look around on the nodes with flags 1.
--[[User:Daiky|Daiky]] 15:45, 5 January 2012 (EST)
:Regarding the small rooms I've seen aliens hiding on those, I can't remember if their are spawn points also though. I've made quite a few attempts are figuring out what the values meant on terrain modes I've created, usually based on the assumption that the higher the number on the flag the more the AI would 'choose' to go to that point. Can't really say that it worked all the time.
:I've always disregarded the theory that aliens leave their craft after turn 8. While it may seem that way, a more easy explanation is simply that the more aliens you have on a confined space, the longer it will take for them to reach the outside because they will block each other's movement (unless they spot a hostile unit, their scouting mode seems to be to go from one waypoint to the other unless they are blocked). Again most of this can't be exactly trusted because without some sort of proof, which I dont have other than observation. [[User:Hobbes|Hobbes]] 19:20, 5 January 2012 (EST)
::"the higher the number on the flag the more the AI would 'choose' to go to that point."; I also think this is a "weight" value when evaluating the next target node, but it's possible there is still some randomness on top of that, otherwise alien behaviour could become too predictable.
::Note that offset 0x2B (43) on unitref.dat also has something to do with pathfinding...
::--[[User:Daiky|Daiky]] 05:45, 6 January 2012 (EST)
:::I got no clue about 'offset 0x2B (43) on unitref.dat' means :) I'm not used to code, just using software that others created to mod things :) [[User:Hobbes|Hobbes]] 18:10, 8 January 2012 (EST)
Just read an old chat I had with BladeFireLight a while ago. This is what I wrote:
'I tried it three times.....on the first I randomly attributed higher values to nodes in upper levels, on the second I attributed high values to specific nodes located on top of stairs and so forth, on the third I increased the value of the highest nodes and put high values on specific nodes to make sure that the aliens would choose them.............I ran each test about some 20 times using
VIS and on the last one the (aliens definitly kept themselves to the higher levels' (VIS is an XComUtil flag that reveals the entire battlefield).
'I think it's more a matter of probability....if you have a node with links to three others with the same value and one of them is in a higher level, there's one third of a chance that he'll go upstairs' [[User:Hobbes|Hobbes]] 18:30, 8 January 2012 (EST)
:Started going over the .RMP files to create the routes for my terrain replacement mod for UFO. The theory of 'the higher the number on this flag, the most likely it will influence the AI' seems to stick by looking at the distribution of the values, specially regarding UFOs. The bridges and engine areas of the larger UFOs usually have much higher values (>5) in clusters, most likely to force the aliens to stay on those areas, as usually seen during (it can also be inferred that they are used to create 'ambushes'). The question still to be answered is what the AI does exactly - there are 2 main hypothesis at this point - a) that they are used by aliens on patrol/guard when choosing the next node that they will travel to (higher values are preferred over the lower ones) or b) that the number determines the time that the alien will spend on that node (which would be useful to set up snipers and ambushes. I will test for b) later. [[User:Hobbes|Hobbes]] 10:31, 26 January 2012 (EST)

ROUTES.DAT

2016-01-08T16:22:18Z

Morgan525: /* Structure */ X and Y were reversed

This file is only used by tactical saves.

It is a collection of all nodes on the map, and uses much the same format as the .RMP files in the [[ROUTES|routes]] folder. Aliens and civilians are placed randomly amongst these nodes when combat begins, and (prior to spotting your units) patrol between them.

If a unit cannot be placed because you've run out of appropriate nodes, it'll use a non-appropriate node instead. This means that sometimes alien leaders won't be inside their ships.

X-Com units don't spawn according to these nodes if you use an Avenger. Need to test the other craft, and base offense/defense missions. - BB

After a new tactical map has been generated from the small map sections, the records are read from the corresponding .RMP files in order of left to right, top to bottom. However the X-Com and Alien craft nodes are always saved until last, and so appear at the end of the file.

Each record is 24 bytes, so the total file size is equal to that times the amount of records in the entire map. Decimal/Hex offsets:

== Structure ==
0/00 - X position of node.

1/01 - Y position of node.

2/02 - Z position of node.

3/03 - Map section counter. All nodes from the first map segment will have this flagged as 0, the nodes from the next map segment as 1, the next segment 2, and so on.

4/04 - 18/12 - Each node can connect to multiple other nodes. These 15 bytes contain 5 records of 3 bytes each, detailing those connections:
*0 - The record number of the connected node. 255/FF if unused. When the game engine pieces the small map segments together, if an external node can't be connected, the spare connection record will be disabled. A common example is a connection that would make a unit walk off the playing field. For external node connections this number is FE:North, FD:East, FC:South, FB:West.
*1 - The distance to the connected node. If the connected node was not originally in the same .RMP file, this is calculated by adding the two connection distances together.
*2 - The type of unit that can travel along this connection.
0 = Any
1 = Flying
2 = Flying Large
3 = Large
4 = Small
<blockquote>Check the discussion page for these values, because they are probably wrong</blockquote>

19/13 - The type of unit that can spawn at this node.
0 = Any
1 = Flying Small
2 = Small
3 = Flying Large
4 = Large

<blockquote>Check the discussion page for these values, because they are probably wrong</blockquote>
<blockquote>At least, modulo 8. The above is exhaustive only for reference data in the routes folder, and non-UFO nodes in Battlescape saves.

Bit 3 (value 8) is set for nodes where an alien starts. Whether the alien is alive, or dead from power plant explosion, is irrelevant.

Bit 4 (value 16) may be set for nodes sourced from UFO reference data...and furthermore is sometimes changed by processing during the alien turn for these nodes. Presumed (needs more testing): in patrol mode nodes sourced from UFO reference data, the AI explicitly prefers (but is not guaranteed to) to stop moving on nodes with bit 4 set.

Bits 5-7 are uniformly 0 for medium scouts. Other UFO types have not been verified yet. Neither have terror sites or alien bases.</blockquote>

20/14 - The rank, or the team, of unit that can spawn at this node. (Misc1 is only used on TFTD, Misc2 appears on both games)

0 = Civilian / "Scout"
1 = X-Com
2 = Alien Soldier
3 = Alien Navigator
4 = Alien Leader / Commander
5 = Alien Engineer
6 = "Misc1"
7 = Alien Medic
8 = "Misc2"

21/15 - Ranges from 0 to 8, Daishiva calls this the "flags" byte. Governs whether an alien will attempt to destroy a base module. Apparently, the higher the number, the greater the chance the aliens will start shooting. So far, this has only been tested on an X-COM base defense mission but seems to hold. No other maps or modules have been tried.

An alternative explanation is that the number indicates the 'importance' of the node when the aliens are conducting their patrols. Using Bomb Bloke's graphics I've superimposed on the Battleship map the values for this flag on all the nodes:

[[File:Ufo_160_0_flags.gif]]
[[File:Ufo_160_1_flags.gif]]
[[File:Ufo_160_2_flags.gif]]

According to this theory the aliens will choose a node with the higher value 'flag' when their AI is set for patroling/guarding, unless it is already occupied. The Battleship schematics above show some proof of this, specially on the bridge area (the aliens that start on the bridge room usually never come out except to have a look outside the door). Now look at the plants for the Supply Ship:

[[File:Ufo_170_0_flag.gif]]
[[File:Ufo_170_1_flag.gif]]
[[File:Ufo_170_2_flag.gif]]

The ground and first level almost contains nodes with a 1 value, with a single exception - the 3 and 2 of the engine room. This should explain the aliens' behaviour of only using 1 of the UFO's 2 doors - when an alien moves into the node outside the door, it chooses instead to go to the node with the 3 value, and then to the 2 value, diverting the aliens from the 2nd outside door.

[[File:Ufo_140_0_flag.gif]]
[[File:Ufo_140_1_flag.gif]]

Next one is the Abductor. Usually the aliens don't come out much and you find a large number of them on the main chamber on the ground, due to the concentration of 3/4s that acts as a bottleneck.

Finally here's the remaining medium/large UFOs. Usually the higher value of this byte also corresponds to a high value on 23/17 (which makes sense due to the importance of the node to increase the probability of units spawned there - [[User:Hobbes|Hobbes]] 19:05, 27 January 2012 (EST))

[[File:Ufo_120_0_flag.gif]]
[[File:Ufo_150_0_flag.gif]]
[[File:Ufo_150_1_flag.gif]]

[[File:Ufo_130_0_flag.gif]]
[[File:Ufo_130_1_flag.gif]]
[[File:Ufo_130_2_flag.gif]]

22/16 - Always seems to be set to 0.
(the exception is also seen in TFTD, with a few maps having different values)
(there are also maps on UFO that contain this flag, such as 2 nodes on the Skyranger map that have a value of 10, 1 node on the Battleships that has a 1 value, etc. - some of those look more like coding errors though)

23/17 - Ranges from 0 to 10, Daishiva calls this the "spawn" byte. A value of 0 makes it impossible for a unit to spawn there.

==See Also==
* [[ROUTES|Routes Folder]]
* [[Alien_movement_patterns|Alien Movement Patterns]]
* [[Saved_Game_Files#Battlescape_Files|Battlescape Files]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

Talk:ROUTES.DAT

2016-01-08T13:23:54Z

Morgan525: /* Offset 19 (0x13) */ observation on byte 13h

Regarding offset 23, Zombie, were you attempting to "clarify" or "correct" it?

Previously it stated that 0-value nodes CAN spawn units, but only if all other nodes are taken...

- [[User:Bomb Bloke|Bomb Bloke]] 21:07, 26 August 2008 (PDT)

----
"Correct" it. In any case, 0-value "spawn" nodes can never have units placed there period. They are only used for alien pathfinding. If all the spawn points with values of 1 or greater get filled and there are still alien units waiting to be placed on the map yet, they don't. This follows the same basic premise as an auto-win base defense mission. --[[User:Zombie|Zombie]] 22:11, 27 August 2008 (PDT)
----
Some wild guesses about the "flags" byte on non-base missions: Aliens patrol around using the spawn points, but sometimes they "guard" a certain point. A theory is that the chance the next state is just guarding this spawnpoint is higher when the "flags" byte is higher. So they save TUs, thus making a strong defense(reaction shots). When the flags is zero, they will not stand still on the point and continue patrolling. You will notice that inside UFO's the values are higher, this makes that aliens inside UFOs have a higher defensive advantage.
So this byte can actually be called the "offensive (x-com base)/defensive (others)" decision score. --[[User:Daiky|Daiky]] 07:26, 21 July 2011 (EDT)

----

== Offset 19 (0x13) ==

According my observation this is a bit field
bit0 (1) = this node is only for flying units (mobility bit, used for '''spawning''').
bit1 (2) = this node is only for small units (used for '''spawning''').
bit2 (4) = this node is only for flying units (movement type).
bit3 (8) = this node was used for NPC placement (runtime bit).
bit4 (16) = this node is only for civilians (runtime bit, cleared when aliens nowhere else to go).
bit5 (32) = cannot be used as patrol point.
so
0 = Any (small walk, large walk, small flying, large flying)
1 = Flying (small flying, large fly)
2 = Small (small flying, small walk)
3 = Flying Small (flying small)
--[[User:Volutar|Volutar]] 05:29, 23 September 2011 (EDT)

From what I've made of the bit4, it's set unit a unit in patrol mode reaches it as a destination. Once set, the AI for patrol mode units will skip this node for a destination. It seems to ensure that patrol units always move to new areas.--[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 08:23, 8 January 2016 (EST)

== Offset 20 ==
Actually it's not a "rank", it's more abstract version of "rank" which is used by many ranks (if there's no other appropriate spawnpoints left). At the end of priority list are points with value 0. Same value 0 used for spawning "scout" units, which are mainly spawned outside of UFO, and just hanging around (their AI have quite different route priorities). If there is no free spawn points found - unit marked as "dead" instead of spawning.

Scout 0
Commander 4 > 3 > 5 > 8 > 7 > 2 > 0
Leader 4 > 3 > 5 > 8 > 7 > 2 > 0
Engineer 5 > 4 > 3 > 2 > 7 > 8 > 0
Medic 7 > 6 > 2 > 8 > 3 > 4 > 0
Navigator 3 > 4 > 5 > 2 > 7 > 8 > 0
Soldier 2 > 5 > 3 > 4 > 6 > 8 > 0
Terrorist 2 > 5 > 3 > 4 > 6 > 8 > 0
XCom 1 > 0 > 2

So, 1st priority spawn points confirmed to be as they listed on main page. But almost any of these spawn point can be used by number of alien ranks, not only by those you assigned to.

0 = Scout/Any rank
1 = X-Com
2 = Soldier/Terrorist, Medic, Engineer/Navigator, Commander/Leader
3 = Navigator, Commander/Leader, Engineer/Soldier/Terrorist, Medic
4 = Commander/Leader, Engineer/Navigator, Soldier/Terrorist, Medic
5 = Engineer, Commander/Leader/Navigator
6 = ..., Medic, Soldier/Terrorist
7 = Medic, Commander/Leader/Engineer/Navigator
8 = ..., Commander/Leader/Medic, Engineer/Navigator/Soldier/Terrorist
--[[User:Volutar|Volutar]] 03:21, 26 September 2011 (EDT)

little note: "scout" is also a civilian spawn node, they also only spawn at 0 --[[User:Daiky|Daiky]] 15:30, 30 December 2011 (EST)

== Node link offset 2 (travel unit type) ==

This is a bitfield with values as mask for kind of units.

bit0 (1) = this node is only for units in fly mode (mobility bit).
bit1 (2) = this node is only for small units.
bit2 (4) = this node is only for flying units (movement type).
*bit3 (8) = this link was already processed for path estimation (runtime bit).

so
0= any units
1= units of any size in fly mode
2= small units flying or not
3= small units in fly mode
4= any size of flyers
5= any size of flyers in fly mode
6= small flyers
7= small flying flyers

Actually I dont know why there are TWO bits (0 and 2) which stand for flying... AFAIR every flying alien unit unable to walk, so they always have movement type "Fly" and mobility bit "fly mode" (like floaters, who are unable to use steps). Probably some of walking alien units was planned to have flying abilities, but abandoned for some reason.
--[[User:Volutar|Volutar]] 01:51, 27 September 2011 (EDT)

== Offsets 0x15 (21) & 0x16 (22) ==

They seems to be used for AI patrol route distortion for BaseDefence mission type.
Before (and including) 30th turn of battle Aliens seems to be attracted by route nodes having one of these (or both) flags set (as boolean field). It's more like a target points, and they seems to be not interested in others at all. But after 30th turn of battle Aliens seems to be wandering all over the place without paying attention on these flags.

It can be confirmed by clearing all these flags from XCOM base module maps, and setting them only for "lift" module nodes. Apparently they will be swarming around lift area, without trying to get somwehere else. But after 30 turn they must scatter.
--[[User:Volutar|Volutar]] 00:05, 28 September 2011 (EDT)
Yes, this was confirmed. Though if Alien spots your unit, it will pursue (in Snipe mode), no matter what routes and flags are
--[[User:Volutar|Volutar]] 00:51, 28 September 2011 (EDT)

I wonder why there are so-called targetpoints (flags 5 in base defense) in the small rooms around the hangar?
Also, on terror sites there are flags 1 (and I found a flags 2 on a roof). They seem to be somewhat random, however on maps with buildings, the nodes with flags 1 are mostly inside. An explanation may be that aliens are attracted to these flags 1 nodes as targetpoints, making aliens targetting the inside of buildings to terrorise civilians.
On larger UFOs, the flags seems to have the same value as priority? Which might be an error in the data? Or maybe the flags values are not used in UFOs at all. There is a theory that until a certain turn aliens will prefer to stay inside and around the UFO before spreading to the outside, this might be controlled by this flags.
On other terrain once and a while there is a flags 1 value, the rest is 0. It could be aliens walk around and stand still and look around on the nodes with flags 1.
--[[User:Daiky|Daiky]] 15:45, 5 January 2012 (EST)
:Regarding the small rooms I've seen aliens hiding on those, I can't remember if their are spawn points also though. I've made quite a few attempts are figuring out what the values meant on terrain modes I've created, usually based on the assumption that the higher the number on the flag the more the AI would 'choose' to go to that point. Can't really say that it worked all the time.
:I've always disregarded the theory that aliens leave their craft after turn 8. While it may seem that way, a more easy explanation is simply that the more aliens you have on a confined space, the longer it will take for them to reach the outside because they will block each other's movement (unless they spot a hostile unit, their scouting mode seems to be to go from one waypoint to the other unless they are blocked). Again most of this can't be exactly trusted because without some sort of proof, which I dont have other than observation. [[User:Hobbes|Hobbes]] 19:20, 5 January 2012 (EST)
::"the higher the number on the flag the more the AI would 'choose' to go to that point."; I also think this is a "weight" value when evaluating the next target node, but it's possible there is still some randomness on top of that, otherwise alien behaviour could become too predictable.
::Note that offset 0x2B (43) on unitref.dat also has something to do with pathfinding...
::--[[User:Daiky|Daiky]] 05:45, 6 January 2012 (EST)
:::I got no clue about 'offset 0x2B (43) on unitref.dat' means :) I'm not used to code, just using software that others created to mod things :) [[User:Hobbes|Hobbes]] 18:10, 8 January 2012 (EST)
Just read an old chat I had with BladeFireLight a while ago. This is what I wrote:
'I tried it three times.....on the first I randomly attributed higher values to nodes in upper levels, on the second I attributed high values to specific nodes located on top of stairs and so forth, on the third I increased the value of the highest nodes and put high values on specific nodes to make sure that the aliens would choose them.............I ran each test about some 20 times using
VIS and on the last one the (aliens definitly kept themselves to the higher levels' (VIS is an XComUtil flag that reveals the entire battlefield).
'I think it's more a matter of probability....if you have a node with links to three others with the same value and one of them is in a higher level, there's one third of a chance that he'll go upstairs' [[User:Hobbes|Hobbes]] 18:30, 8 January 2012 (EST)
:Started going over the .RMP files to create the routes for my terrain replacement mod for UFO. The theory of 'the higher the number on this flag, the most likely it will influence the AI' seems to stick by looking at the distribution of the values, specially regarding UFOs. The bridges and engine areas of the larger UFOs usually have much higher values (>5) in clusters, most likely to force the aliens to stay on those areas, as usually seen during (it can also be inferred that they are used to create 'ambushes'). The question still to be answered is what the AI does exactly - there are 2 main hypothesis at this point - a) that they are used by aliens on patrol/guard when choosing the next node that they will travel to (higher values are preferred over the lower ones) or b) that the number determines the time that the alien will spend on that node (which would be useful to set up snipers and ambushes. I will test for b) later. [[User:Hobbes|Hobbes]] 10:31, 26 January 2012 (EST)

MISDATA.DAT

2015-12-31T11:40:53Z

Morgan525: /* Structure */ changed wording on mission abort status

This 170 byte file (172 for TFTD) is only used by tactical saves, and much of it is made up of two-byte signed integers. It comes in three flavours: 

*MISSION.DAT 
Initially created by the GeoScape engine and stored in the [[Saved_Game_Files#Missdat_Files|MISSDAT]] folder. Contains info required for [[Battlescape Map Generation]]. 

*MISDATA.DAT 
Created along with a [[Saved_Game_Files#Battlescape_Files|battlescape save]], effectively a mirror of the original "MISSION.DAT". 

*MISSION2.DAT 
Appears in the MISSDAT folder at the end of combat. Contains debreifing data (such as who won, what was recovered and what points were scored). The relevant offsets for this file are unused by the previous two versions. 

Values are presented according to byte offset ([[#0|0]] to [[#169|169]]/[[#171|171]]) followed by the equivalent hex offset ([[#0x00|0x00]] to [[#0xA9|0xA9]]/[[#0xAB|0xAB]]) in '''bold'''. Let us know what else you can find!!

== Structure ==

{| class="wikitable"
|-
!Offset (Decimal)
!Offset (Hex)
!Usage
|-
|colspan="3"|The first 20 bytes are a count up of the various recoverable tile types in the map. These two-byte integers are only set if you actually won the mission by eliminating all enemy forces. These offsets + 100 index into the respective [[BASE.DAT]] values that they'll be added to.

See [[Equipment Recovery]] for more information.
|- valign="top"
!0-1
!0x00-0x01
|[[UFO Power Source]] ([[MCD#59|MCD[59]]] set to 02).
|- valign="top"
!2-3
!0x02-0x03
|[[UFO Navigation]] ([[MCD#59|MCD[59]]] set to 03, not counted for alien bases).
|- valign="top"
!4-5
!0x04-0x05
|[[UFO Construction]] ([[MCD#59|MCD[59]]] set to 04, no known tiles have this set).
|- valign="top"
!6-7
!0x06-0x07
|[[Alien Food]] ([[MCD#59|MCD[59]]] set to 05).
|- valign="top"
!8-9
!0x08-0x09
|[[Alien Reproduction]] ([[MCD#59|MCD[59]]] set to 06, no known tiles have this set).
|- valign="top"
!10-11
!0x0A-0x0B
|[[Alien Entertainment]] ([[MCD#59|MCD[59]]] set to 07).
|- valign="top"
!12-13
!0x0C-0x0D
|[[Alien Surgery]] ([[MCD#59|MCD[59]]] set to 08).
|- valign="top"
!14-15
!0x0E-0x0F
|[[Examination Room]] ([[MCD#59|MCD[59]]] set to 09).
|- valign="top"
!16-17
!0x10-0x11
|[[Alien Alloys]] ([[MCD#59|MCD[59]]] set to 10).

The total is divided by 2 for a UFO mission or 30 for an alien base. The value stored here is further divided by 5 to get the result you see on the debriefing screen.
|- valign="top"
!18-19
!0x12-0x13
|[[Alien Habitat]] ([[MCD#59|MCD[59]]] set to 11, no known tiles have this set).
|- valign="top"
!20-21
!0x14-0x15
|Mission descriptor. Possible values:
UFO TFTD
0: UFO Site 0: USO Site
1: Terror Site 1: Port/Island Attack
2: Base Defence (X-COM Base) 2: Base Defense (X-COM Base)
3: Base Offense (Alien Base) 3: Colony Stage 1
4: Mars Stage 1 4: T'leth Stage 1
5: Mars Stage 2 5: T'leth Stage 2
6: T'leth Stage 3
7: Artefact Site Stage 1
8: Artefact Site Stage 2
9: Passenger/Cargo Ship Stage 1
10: Passenger/Cargo Ship Stage 2
11: Colony Stage 2
|-
|colspan="3"|Values 22-73 (Hex: 16-49) primarily hold scoring information. As per the tile recovery indexes, these are only stored in the final "end-of-combat" MISSION2.DAT. For temporary storage mid-mission, some of these values are stored in [[WGLOB.DAT]].
|- valign="top"
!22-23
!0x16-0x17
|Aliens killed.
|- valign="top"
!24-25
!0x18-0x19
|Aliens killed score.
|- valign="top"
!26-27
!0x1A-0x1B
|Alien corpses.
|- valign="top"
!28-29
!0x1C-0x1D
|Corpse score.
|- valign="top"
!30-31
!0x1E-0x1F
|Live aliens captured.
|- valign="top"
!32-33
!0x20-0x21
|Live alien score.
|- valign="top"
!34-35
!0x22-0x23
|Artefacts (''unresearched'' alien items) recovered.
|- valign="top"
!36-37
!0x24-0x25
|Artefacts score.
|- valign="top"
!38-39
!0x26-0x27
|Alien base control destroyed. This flags if you win a [[Alien_Base_Assault|base offense mission]] by killing all enemy forces, or if you destroy all 16 nav modules in the command center. If not zero, the base you were attacking will be removed from the world map at the end of combat.
|- valign="top"
!40-41
!0x28-0x29
|Base control score.
|- valign="top"
!42-43
!0x2A-0x2B
|Civilians killed by aliens.
|- valign="top"
!44-45
!0x2C-0x2D
|Civilians killed by aliens score (typically negative).
|- valign="top"
!46-47
!0x2E-0x2F
|Civilians killed by X-COM.
|- valign="top"
!48-49
!0x30-0x31
|Civilians killed by X-COM score (typically negative).
|- valign="top"
!50-51
!0x32-0x33
|Civilians saved.
|- valign="top"
!52-53
!0x34-0x35
|Civilians saved score.
|- valign="top"
!54-55
!0x36-0x37
|X-COM troopers killed.
|- valign="top"
!56-57
!0x38-0x39
|X-COM troopers killed score (typically negative).
|- valign="top"
!58-59
!0x3A-0x3B
|X-COM troopers "retired through injury" (never actually flags).
|- valign="top"
!60-61
!0x3C-0x3D
|X-COM troopers "retired through injury" score (never actually flags).
|- valign="top"
!62-63
!0x3E-0x3F
|X-COM troopers MIA.
|- valign="top"
!64-65
!0x40-0x41
|X-COM troopers MIA score (typically negative).
|- valign="top"
!66-67
!0x42-0x43
|Tanks lost.
|- valign="top"
!68-69
!0x44-0x45
|Tanks lost score (typically negative).
|- valign="top"
!70-71
!0x46-0x47
|X-COM craft lost (GeoScape ignores this if you actually lose a craft, Tactical sets it regardless).
|- valign="top"
!72-73
!0x48-0x49
|X-COM craft lost score (GeoScape ignores this if you actually lose a craft, Tactical doesn't set it regardless).
|- valign="top"
!74-75
!0x4A-0x4B
|A value based on the time at the [[LOC.DAT]] location. References into a table stored in the executable in order to define the values in [[BGLOB.DAT]].
|- valign="top"
!76
!0x4C
|For a UFO site, this is the [[LOC.DAT]] reference corresponding to the crash site. This is plausibly true for every mission type (with the possible exception of the [[Cydonia|Mars assault]]). Used to determine whether the alien ship crashed or not (and therefore whether to randomly detonate the power supply units). ''I seem to remember that tweaking this byte could have an effect on [[BGLOB.DAT]], but I might've confused myself. - [[User:Bomb Bloke|Bomb Bloke]] 03:45, 23 June 2008 (PDT)''
|- valign="top"
!77
!0x4D
|Index into [[CRAFT.DAT]] pointing to the craft sent on this mission. In the case of base defence (see offset [[#79|[79]]]), it indexes to the [[LOC.DAT]] record for the base in concern.
|- valign="top"
!78
!0x4E
|Victory status.

0: Mission aborted with some units in exit areas.
1: Mission won.
2: Mission lost.
3: Mission aborted with no units in exit areas.
|- valign="top"
!79
!0x4F
|0 unless the mission is a UFO site, in which case it is 1. Determines use of [[#77|[77]]] but doesn't seem to affect [[#16-17|[16-17]]].
|- valign="top"
!80-151
!0x50-0x97
|A list of 36 two-byte integers, used during base defence missions. In order, they represent each module in your base, reading from left to right, top to bottom.

At the end of battle, the tactical game engine tallies up the amount of [[Base_Defence#Destruction_Of_Base_Facilities|"target" objects]] existing within each module, and stores the results in "MISSION2.DAT". If that figure is 0 for any given destructible [[Base_Facilities_(EU)|facility]], then the geoscape engine will remove it from your base (along with any ''other'' modules that relied on that section for passage to the [[Access Lift]]).

"Target objects" are tiles that have offset 60 set to 1 within their [[MCD]] record.
|-
|colspan="3"|Bytes '''152-167''' (Hex: '''0x98-0xA7''') allow you to use the following equipment only if they are set to 1. X-COM produced equipment can be used even if it hasn't been researched (however, in order to get it into combat, you must build it - and that requires research). The last three entries in the list are item slots that were never used in the game.
|- valign="top"
!152
!0x98
|Enables [[Heavy Plasma]] ([[OBDATA.DAT|ObData]][34])
|- valign="top"
!153
!0x99
|Enables [[Heavy Plasma Clip]] ([[OBDATA.DAT|ObData]][35])
|- valign="top"
!154
!0x9A
|Enables [[Plasma Rifle]] ([[OBDATA.DAT|ObData]][36])
|- valign="top"
!155
!0x9B
|Enables [[Plasma Rifle Clip]] ([[OBDATA.DAT|ObData]][37])
|- valign="top"
!156
!0x9C
|Enables [[Plasma Pistol]] ([[OBDATA.DAT|ObData]][38])
|- valign="top"
!157
!0x9D
|Enables [[Plasma Pistol Clip]] ([[OBDATA.DAT|ObData]][39])
|- valign="top"
!158
!0x9E
|Enables [[Blaster Launcher]] ([[OBDATA.DAT|ObData]][40])
|- valign="top"
!159
!0x9F
|Enables [[Blaster Bomb]] ([[OBDATA.DAT|ObData]][41])
|- valign="top"
!160
!0xA0
|Enables [[Small Launcher]] ([[OBDATA.DAT|ObData]][42])
|- valign="top"
!161
!0xA1
|Enables [[Stun Bomb]] ([[OBDATA.DAT|ObData]][43])
|- valign="top"
!162
!0xA2
|Enables [[Alien Grenade]] ([[OBDATA.DAT|ObData]][44])
|- valign="top"
!163
!0xA3
|Enables [[Elerium-115]] ([[OBDATA.DAT|ObData]][45])
|- valign="top"
!164
!0xA4
|Enables [[Mind Probe]] ([[OBDATA.DAT|ObData]][46])
|- valign="top"
!165
!0xA5
|Enables "null>>UNDEFINED <<" ([[OBDATA.DAT|ObData]][47])
|- valign="top"
!166
!0xA6
|Enables "null>> empty <<" ([[OBDATA.DAT|ObData]][48])
|- valign="top"
!167
!0xA7
|Enables "null>> empty <<" ([[OBDATA.DAT|ObData]][49])
|- valign="top"
!168-169
!0xA8-0xA9
|Determines the language in which the mission was initiated. If the game is saved and later loaded, this overrides whatever language was selected when the program started.

0 - English
1 - German
2 - French
|- valign="top"
!170
!0xAA
|Only present for TFTD. Determines the depth level (that is, which [[PALETTES.DAT#TFTD Tactical Palettes|battlescape palette]] to use, whether to render air bubbles around units, and which background noise to play):

0 - Surface
1 - Shallow Water
2 - Medium Depths
3 - Deep Sea

Values above 3 use the surface palette, but otherwise act as though the mission were underwater.
|- valign="top"
!171
!0xAB
|Only present for TFTD. Unknown, never seen it flag. Not a part of the above value.
|-
|}

==See Also==
* [[Battlescape Map Generation]]
* [[Saved Game Files]]
* [[OBDATA.DAT]]
* [[MCD|MCD files]]
* [[WGLOB.DAT]]
* [[CRAFT.DAT]]
* [[BASE.DAT]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

UNITREF.DAT

2015-12-26T02:13:21Z

Morgan525: /* Structure */

A [[Saved Game Files|save game file]] that has a record size of 124 bytes for UFO, or 132 for TFTD. Values are unsigned unless otherwise stated. Some bytes represent bitfields. There are 80 records (not all of them necessarily used) for a fixed file size of 9,920 bytes (or 10,560 for TFTD). It goes hand in hand with [[UNITPOS.DAT]].

Comes in three flavours: 

*UNIREF.DAT 
Initially created by the GeoScape engine before tactical battles. Stored in the [[Saved_Game_Files#Missdat_Files|MISSDAT]] folder and contains info on all units that will be present in the coming mission (in an alive state - the deaths of aliens killed by exploding UFO power units isn't determined until [[Battlescape_Map_Generation#KABOOM.21.21|later]]). Unlike the other two versions, this only contains the bare minimum number of records required to store the units it details. 

*UNITREF.DAT 
Created along with a [[Saved_Game_Files#Battlescape_Files|battlescape save]], contains the mid-mission state of the unit table. 

*UNIREF2.DAT 
Appears in the [[Saved_Game_Files#Missdat_Files|MISSDAT]] folder at the end of combat. Used to determine which troopers/tanks survived, statistic gains via [[experience]], and which aliens need to be hauled off to the [[Alien Containment]] unit. 

Values are presented according to byte offset ([[#0|0]] to [[#123|123]] (or [[#131|131]] for TFTD)) followed by the equivalent hex offset ([[#0x00|0x00]] to [[#0x7B|0x7B]] (or [[#0x83|0x83]] for TFTD)). Notes apply to both UFO and TFTD unless otherwise stated. Let us know what else you can find - refer to the [[#Notes|bottom of the page]] for those values that're unknown, or to the [[Talk:UNITREF.DAT|talk page]] for further ideas as to what they could be.

== Structure ==

{| class="wikitable"
|-
!Offset (Decimal)
!Offset (Hex)
!Usage
|- valign="top"
!0
!0x00
|Type of unit. Unit scream and movement sound effects are based on this and gender. Gender and flying abilities affect the sprites as well. Not turrets. Specifically: [[#53|[53]]] & [[#54|[54]]] (weapons in hands), [[#115|[115]]] (gender) and [[#120|[120]]] (other flags) affect the final screen image. If the unit is a large unit, this will also determine the appearance of the last three quarters of the unit. This does NOT affect: the flying ability of the unit, the soldier image in the inventory screen, or the special abilities for certain aliens.
UFO TFTD
0: Male/female unarmored X-COM soldier 0: Male/female unarmored X-COM diver
1: Male/female personal armor soldier 1: Male/female plastic armor diver
2: Power/flying suit soldier 2: Power/flying suit diver
3: Tank 3: Tank
4: Sectoid 4: Aquatoid
5: Snakeman 5: Gillman
6: Ethereal 6: Lobster Man
7: Muton 7: Tasoth
8: Floater 8: Calcinite
9: Celatid 9: Deep One
10: Silacoid 0A: BioDrone
11: Chryssalid 0B: Tentaculat
12: Reaper 0C: Triscene
13: Sectopod 0D: Hallucinoid
14: Cyberdisc 0E: Xarquid
15: Male civilian 0F: Male civilians
16: Female civilian 10: Female civilians
17: Zombie 11: Zombie
255: Unused 255: Unused

<blockquote>If the corresponding [[UNITPOS.DAT]] record is unused, then the record is unused.</blockquote>
|- valign="top"
!1
!0x01
|Inventory paper doll image. File "UFOGRAPH\MAN_"+(char)(value + 48)+".SPK" will be used as the inventory sprite, unless the value is 0 or 1. In those cases, [[#115|[115]]] and [[#116|[116]]] are used to determine the picture.
0: No armor.
1: Personal armour.
2: Power suit.
3: Flying suit.
|- valign="top"
!2-5
!0x02-0x05
|Four byte value pointing to RAM location of the [[Image_Formats#PCK|PCK set]] used by the unit. Re-determined when the save game is loaded.
|- valign="top"
!6-9
!0x06-0x09
|Four byte value pointing to RAM location of the [[Image_Formats#PCK|TAB index for the PCK data]] used by the unit. Re-determined when the save game is loaded.
|- valign="top"
!10
!0x0A
|Unit facing. Does NOT control HWP turret direction; see [[#24|[24]]].
0: North (up right)
1: Northeast (right)
2: East (down right)
3: Southeast (down)
4: South (down left)
5: Southwest (left)
6: West (up left)
7: Northwest (up)
|- valign="top"
!11
!0x0B
|Movement type. When entering a given map location, each tile is checked to see the TU requirements accordingly. [[MCD]][39+[[#11|UnitRef[11]]]] is the offset used. Note: By default, this is 0 for ALL unit types.
0: Walking
1: Sliding
2: Flying
|- valign="top"
!12
!0x0C
|Current TUs.
|- valign="top"
!13
!0x0D
|Current Health. Health of 0 = Dead. Compare [[#42|[42]]], [[#120|[120]]].

''For my [[Talk:Bravery|Bravery experience point testing]], I killed 15 of 16 aliens by setting this to zero, and my soldiers to 0 Morale. When I loaded the savegame, the aliens were still "alive" (i.e., up), then all died when I ended this turn. So death is probably only checked when injury happens, and at end of turn... to truly kill them dead on the ground through savegame editing must take more. And arg - when they all died, my soldiers all went to 100 Morale! So I edited them back to 0 Morale. But guess what... then all the aliens died '''again''' at the end of '''next''' turn, even though they were all on the ground (I heard screams, and all soldiers' Morale went to 100 again). What the heck? The aliens stayed down after that, though. --[[User:MikeTheRed|MikeTheRed]] 16:01, 3 November 2006 (PST)''

''Update: [[UNITPOS.DAT]] offset 10 bit 2 should be used to kill a unit entirely dead. Thanks, NKF & BB - MTR''

: ''While the game kills characters when Health<=Fatal Wounds (__ dies message), XComUtil will recover them based if their health is greater than 0. Haven't tested an unmodified game. --[[User:Zaimoni|Zaimoni]] 11:52, 14 April 2007 (CDT)''
|- valign="top"
!14
!0x0E
|Current Stun level ''how much falloff of paralysis every turn? What determines it?''
|- valign="top"
!15
!0x0F
|Current Energy
|- valign="top"
!16
!0x10
|Current Reactions ''NKF: affected by health percentage''
|- valign="top"
!17
!0x11
|Strength
|- valign="top"
!18
!0x12
|Current Front Armour
|- valign="top"
!19
!0x13
|Current Left Armour
|- valign="top"
!20
!0x14
|Current Right Armour
|- valign="top"
!21
!0x15
|Current Rear Armour
|- valign="top"
!22
!0x16
|Current Under Armour
|- valign="top"
|colspan="3"|"Base" means the original (total) value (as carried forward from geoscape) - Also see Note 1 re: Base soldier stat values.
|- valign="top"
!23
!0x17
|Base Firing accuracy. Current value = this * [[#13|[13]]]/[[#26|[26]]] (percent health)
|- valign="top"
!24
!0x18
|Base Throwing accuracy. Current value = this * [[#13|[13]]]/[[#26|[26]]] (percent health)

Note: Tanks (turreted units?) always have 0 throwing accuracy. They use this for turret facing, relative to unit facing. 0 means it's facing forwards. Additional values are clockwise increments; see [[#10|[10]]].
|- valign="top"
!25
!0x19
|Base TUs
|- valign="top"
!26
!0x1A
|Base Health
|- valign="top"
!27
!0x1B
|Base Energy
|- valign="top"
!28
!0x1C
|Base Reactions
|- valign="top"
|colspan="3"|''These Base Armour values are used to show the starting armor value in the Attributes screen (so you can readily see if it's been damaged''
|- valign="top"
!29
!0x1D
|Base Front Armour
|- valign="top"
!30
!0x1E
|Base Left Armour
|- valign="top"
!31
!0x1F
|Base Right Armour
|- valign="top"
!32
!0x20
|Base Rear Armour
|- valign="top"
!33
!0x21
|Base Under Armour
|- valign="top"
!34
!0x22
|Supposedly this was going to be Health Recharge which would function like the Energy Recharge. Always 0 and ignored by game.
|- valign="top"
!35
!0x23
|Energy to recharge each turn. Equals '''recruit initial''' TUs/3 ([[SOLDIER.DAT]][43], '''not''' total base TUs). This is a signed byte. See [[Time Units]] and [[Energy#Usage|Energy Usage]]; also see [[#45|[45]]] (energy usage when walking/turning). ''BombBloke: Is this affected by damage?''
|- valign="top"
!36
!0x24
|Supposedly this was going to be Armor Recharge which would function like the Energy Recharge. Always 0 and probably unused, but needs testing.
|- valign="top"
!37
!0x25
|Psi skill. Psi stats not displayed/usable until this is greater then 0.
|- valign="top"
!38
!0x26
|Item to create when unit is unconscious/dead (index into obdata.dat).

NKF: If you set this value to that of a usable item, the item that is created in place of the unconscious or dead soldier can be used like the ordinary item. Elerium pods, for example, can be recovered for 50 elerium each after the battle. Weapons can be used as you normally use them, etc.

For unconscious 'units', the item will be treated as the unconscious body - it will retain the name of the unconscious unit when looked at via the inventory screen. Picking up and using the 'item' will work, but when the unit wakes up, the 'item' image in the soldier's hands is not cleared, even though the item no longer 'exists' in the soldier's hands. Using this 'item' will just crash the battlescape.

Actually, I do not even want to think about what would happen if you 'prime' a grenade/stunned body.
|- valign="top"
!39
!0x27
|"Soldier value" a.k.a. victory points. You gain (or lose, as the case may be) score at the end of combat according to this value when the unit dies.
*For X-COM units: A soldier with 42 will be worth -42 points if killed. Note this doesn't seem to apply if the soldier is killed when unconscious. The soldier just vanishes.
*For aliens: A commander with 35 will give you +35 points if killed.
*This value is the same as [[SOLDIER.DAT]] bytes 15-16 (a Word) and equals:
20 + Missions + Rank Bonus

with [[Rank]] Bonus as follows: SGT +1, CPT +3, COL +6, CDR +10
Note that although this equation holds true, the value is not actually computed per se. Instead, 1 is added directly to it each mission, as is a rank-bonus delta if you advance (e.g. COL to CDR, delta +4). In other words, hacking the Missions or Rank fields does not affect this value.
|- valign="top"
!40
!0x28
|Index into [[SOLDIER.DAT]], so game knows what to update. 255 = does not belong to anyone (i.e., it's not a soldier). ''NKF: This byte is critical for player controlled units. If this doesn't refer to anything, the unit ceases to exist at the end of the game. If it points to a valid soldier entry in soldier.dat, the soldier.dat entry will be updated.''
|- valign="top"
!41
!0x29
|Animation frame counter for the unit. Used by eg [[Celatid]]s and [[Silacoid]]s.
|- valign="top"
!42
!0x2A
|Rank. Affects morale loss and interface icon (hull for tanks). Only X-COM troopers display rank icons.
X-COM
0: Rookie ''Civvies are 0 too''
1: Squaddie
2: Sergeant
3: Captain
4: Colonel
5: Commander
255: Dead/unused

Aliens
1: Commander
2: Leader
3: Engineer
4: Medic
5: Navigator
6: Soldier
7: Terrorist
255: Dead/unused

Hull shape for X-COM tanks:
0: Treaded
1: Hover
''I don't see 255 set for three dead mutons in a current game... [[#13|[13]]] (Health=0) seems to be the only reliable death indicator for them. Compare [[#120|[120]]]. -[[User:MikeTheRed|MikeTheRed]]''
|- valign="top"
!43
!0x2B
|Called "deployment" with values of 0 or 1 (0=normal, 1=special).
0: Only those locations specified for units of the appropriate rank, size, and flying ability are used.
1: Civilian spawn points are used, ignoring a unit's rank, but still selected by the unit's size and flying ability.
As result - Commanders/leaders can occasionally be spawned outside of the UFO craft (and ramble around the UFO) and not in the "control room", which has an exclusive commander spawn node.
|- valign="top"
!44
!0x2C
|Alien aggression. The higher it is, the less likely an alien will take cover. Maximum of 2. 0=Cautious,1=Normal,2=Aggressive ''MTR: This is true for aliens in Hobbes game, but soldiers have values from 4 to 254. Garbage? Delete this comment if so.'' This determines the amount of the unit's TUs that are devoted to shooting: 0=50%,1=60%,2=66%.
|- valign="top"
!45
!0x2D
|Used to calculate energy loss when walking or turning as: INT( TUs / 2[45] ). See [[Energy#Usage]]; compare [[#35|[35]]] (energy recharge per turn). Set this byte to 4 to ensure no energy use whatsoever (maximum map [[Time Units#Time_Unit_Walking_Usage_Tables|tile TU cost]] is 12). ''In Hobbes game, many aliens are 0 and all soldiers are 1, but a dozen aliens have higher values ranging all the way up to 112! Garbage and/or the game doesn't care if they are garbage?''
|- valign="top"
!46
!0x2E
|HWP turret image. Only used (and only appears) if unit type [[#0|[0]]]=3 (X-COM tanks):
0: Cannon
1: Rocket
2: Laser
3: Plasma
4: Blaster
5,6: ? Blanks
'''Note:''' For non-tanks, this controls the inventory layout. ''Only'' 0 and 1 are valid. 0 is the standard layout seen on all soldiers. 1 is an alternate layout that may have been intended for custom tank equipment. Larger values only crash the game due to missing files. Also see [[#113|[113]]] and [[#117|[117]]].
|- valign="top"
!47
!0x2F
|This is a direct copy of offset[48] from the [[MCD]] record of the tile the unit is standing on. A signed byte.
|- valign="top"
!48
!0x30
|Values for this byte always equal [[#52|[52]]] and are:
2 (3x3 square; legacy 5 pixels): Sectoid
3 (5x5 square, corners removed; legacy 7 pixels): Celatid, Chryssalid, Civvie,
Ethereal, Floater, Muton, Snake, '''Soldier'''
4 (7x7 octagon; legacy 9 pixels): Cyberdisc, Hovertank, Reaper, Sectopod, Tank
5 (9x9 square, Ls with 3-pixel legs removed; legacy 11 pixels): Silacoid
Based on copious research by [[User:Bomb_Bloke|Bomb_Bloke]], [[User:Seb76|Seb76]], [[user:Zombie|Zombie]], and others, this has been found to be a LOF Template look-up for the shape of targets; Loftemps 2 to 5 define the "3D" shape of units relative to Line Of Fire as a cylinder, where 2 (Sectoid) is a thin cylinder and 5 (Silacoid) is very wide. The pixel width of each "silhoutte" that [[LOFTEMPS.DAT]] corresponds to has been added to the list above (see LOFTemps images 2-5). Tiles are 16 pixels wide in the X or Y direction (that's what this byte is about), and 24 pixels high (compare [[#49|[49]]]).

This cylindrical shape is used in conjunction with height [[#49|[49]]] to define the silhouette that targets present to a shooter. Combine the pixel-width cross-section from Loftemps with height to find the cross-sectional area presented to shooters (sorted on increasing cross-section):

LOF LOF Cross Percent
Lookup Width Height Section of 384 Float 4x?
Type ''UR[48] Pixels UR[[#49|[49]]] Pxls X Ht (16x24) UR[[#51|[51]]]''
---- ------ ------ ------ --------- ------- ------ ---
Sectoid 2 5 16 80 20.8% - -
Celatid 3 7 12 84 21.9% 6 -
Soldier (Kneeling) 3 7 14 98 25.5% - -
Hovertank 4 9 12 108 28.1% 6 Yes
Silacoid 5 11 10 110 28.6% - -
Snakeman 3 7 18 126 32.8% - -
Zombie 3 7 18 126 32.8% - -
Ethereal 3 7 20 140 36.5% - -
Cyberdisc 4 9 15 135 35.2% 2 Yes
Chryssalid 3 7 21 147 38.3% - -
Civilian 3 7 21 147 38.3% 2 -
Floater 3 7 21 147 38.3% 2 -
Muton 3 7 21 147 38.3% - -
Tank 4 9 16 144 37.5% - Yes
Soldier 3 7 22 154 40.1% - -
Reaper 4 9 23 207 53.9% - Yes
Sectopod 4 9 23 207 53.9% - Yes
Units take up an amount of the whole tile (as seen in cross-section by a shooter) as shown in the "Percent of 384" column. In reality, though, the [[Firing Accuracy|accuracy]] of shots makes this a more complex topic than the percents suggest. Also, dividing by 384 is an oversimplification, since it implies a directly rectangular shot (shooting right down the X or Y axis). While it's useful to see, keep in mind that this column only shows relative numbers.

: [[User:Zaimoni|Zaimoni]]: actual cross section depends on shot facing. The table is close to correct for pure diagonal shots, so leaving alone for now.

The unit Float number ([[#51|[51]]], below) is shown simply for convenience. It does not enter into the cross-sectional computations. "4x" units actually consist of four units grouped in tight 2x2 formation (making their cross section effectively much larger then the percentage stated).

Note that causing an X-Com soldier to kneel causes their cross section to fall by 36.36~% of that of when they are standing.
|- valign="top"
!49
!0x31
|[[height|Standing height]].
|- valign="top"
!50
!0x32
|[[height|Kneeling height]].
|- valign="top"
!51
!0x33
|Floating [[height]]. A unit 'floats' this high above the ground, thus allowing shots to fly underneath. The highest point of a unit can be found by adding this to the units height stat. Does this have an effect on explosive damage?
|- valign="top"
!52
!0x34
|"Radius" of LOF Template. Always the same as [[#48|[48]]] in all known saved games. More info can be found at [[Talk:UNITREF.DAT#Offsets_0x30_.26_0x34|Talk:UNITREF.DAT#Offsets_0x30_&_0x34]] ([48] and [52]).
|- valign="top"
!53
!0x35
|Image index for item in left hand. 255 for none. Indexes into [[OBDATA.DAT]], not [[OBPOS.DAT]].
|- valign="top"
!54
!0x36
|Image index for item in right hand. 255 for none. Indexes into [[OBDATA.DAT]], not [[OBPOS.DAT]].
|- valign="top"
|colspan="3"|''NKF:'' If there is no item in the unit's hands, but one of the above two bytes are set, the 'image' that represents the item will still be displayed in the battlescape. If these phantom items are clicked on, the game crashes. If the image is not the right type for the real item in hand, the ammo count doesn't get displayed. Otherwise, it'll work as normal.
|- valign="top"
!55
!0x37
|[[Damage#Susceptible_to...|Damage Modifier]] Category

This field is simply a look-up table, or more directly, a way to categorize the units into similar groups. The actual modifiers are listed in the executable. A value of 1 indicates the first DM category, a value of 4 indicates the 4th, etc. The values of 2 and 3 are not seen in the alien stats as they refer to X-COM soldier armor info. I'm not sure about 13 as the Zombie's stats haven't been found yet, but I think there is a category in the DM's for it.

'''Value''' '''Unit Type(s)'''
'''0''' Terrain and Items
'''1''' Civilian, Sectoid, Celatid, Floater
'''2''' Personal Armor
'''3''' Power Suit, Flying Suit
'''4''' Tanks, Hovertanks
'''5''' Snakemen
'''6''' Ethereal
'''7''' Muton
'''8''' Silacoid
'''9''' Chryssalid
'''10''' Reaper
'''11''' Sectopod
'''12''' Cyberdisc
'''13''' Zombie
|- valign="top"
!56
!0x38
|[[Melee Accuracy]] ([[SOLDIER.DAT]] bytes 50 (initial) & 60 (increase) added together)
|- valign="top"
!57
!0x39
|[[Psionic Strength]]
|- valign="top"
!58
!0x3A
|Current [[Morale]]. Base morale is hardcoded to 100.
|- valign="top"
!59
!0x3B
|[[Bravery]] = 110 - (10 * ''this value'')
|- valign="top"
!60
!0x3C
|Panic mode. This takes effect at the start of the unit's next turn. Since it is cleared at that point, you'll never see it at anything other then 0 in the save files. You can manually change it to other values to force a specific panic attack on the next turn.
0: None
1: Freeze
2: Running
3: Berserk
|- valign="top"
!61
!0x3D
|[[#62|[62]]] will increment by this amount whenever the unit moves.
3: Sectiod ''- Hobbes''
4: Soldiers, civs, and all other aliens (but Hobbes had no Large aliens)
30: Tank/Laser
|- valign="top"
!62
!0x3E
|Visibility via motion scanner. The bigger it is, the bigger the blip. Test this one out for values.
|- valign="top"
!63
!0x3F
|Number of [[Fatal Wounds]] to head.
|- valign="top"
!64
!0x40
|Number of fatal wounds to torso.
|- valign="top"
!65
!0x41
|Number of fatal wounds to right arm.
|- valign="top"
!66
!0x42
|Number of fatal wounds to left arm.
|- valign="top"
!67
!0x43
|Number of fatal wounds to right leg.
|- valign="top"
!68
!0x44
|Number of fatal wounds to left leg.
|- valign="top"
!69-70
!0x45-0x46
|Indexes into [[ROUTES.DAT]]. To start with, aliens will be located at the same position as the node indicated by byte 69.
:For patrol AI (no X-COM units sighted in turn 1, either X-COM or alien):
::Byte 69 is the index of the node of the start of the planned move.
::Byte 70 is the index of the node of the end of the planned move.
:Note that the move may be multi-turn, and byte 69 is not guaranteed to update during a multi-turn move. I think it will if the alien ends its move on a node, however. -- Zaimoni
:For AI mode 2:
::Byte 70 is the UNITPOS reference number for this unit's target. - Tycho
|- valign="top"
!71
!0x47
|Unit lighting: always 16 for XCom units, 0 for most aliens but 1 for cyberdisc. If greater than 1, it is set to 1 when unit inactive - see the [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page.
|- valign="top"
!72
!0x48
|The amount of [[Morale]] that has been restored using the [[Medi-Kit (EU)|Medkit's]] painkillers. The amount that ''can'' be restored is equal to the maximum health of the unit (index 26) minus their current health (index 13) further minus this.
|- valign="top"
!73
!0x49
|Intelligence. Rated from 2 - 8. Indicates for how many turns the alien will know the location of spotted soldiers. ''Hey - why do humans have zero intelligence? :(''
|- valign="top"
!74
!0x4A
|AI Mode. Zaimoni found [http://www.strategycore.co.uk/forums/UFO-AI-patch-t8908.html&st=20&start=20 Here] that the values are
:::0:PATROL
:::1:SNIPER
:::2:ATTACKING
:::3:ESCAPING
:::4:GUARD
:::5:Returning to UFO.
:255 (-1): Makes the program recalculate the AI mode.
|- valign="top"
!75
!0x4B
|Unknown. With that said, the only item remaining on my list is called "lightdirect" or direction of light for a unit (0=all around, 1=direction unit facing). Unused by game code and always 0. Maybe it was for a hand-held light source, or a armor-mounted flashlight?
|- valign="top"
!76-77
!0x4C-0x4D
|Mission count. Signed integer (low byte, high byte) also found in [[SOLDIER.DAT]] ''MTR: Wonder why they bothered to put this in Unitref since this will never change '''during''' a mission; compare how soldier stats are actually read from SOLDIER (not UNITREF) on return to geoscape. Is Missions shown anywhere on the combatscape?
|- valign="top"
!78-79
!0x4E-0x4F
|Kill count. Signed integer (low byte, high byte) also found in [[SOLDIER.DAT]]. Number of kills this unit has made for ALL missions, not just this one. This one '''can''' vary "unpredictably" and thus is the only byte known to directly carry forward into the geoscape / Soldier.Dat!
|- valign="top"
!80
!0x50
|[[Reactions]] experience counter, for number of reaction shots. It doesn't matter if they hit the target; reactions still count. See Note 2 re: Experience counters. (Also note: Aliens do not use experience counters.)

''NKF:'' Where does death by fire (overexposure rather than incendiary shell impact) fit into the experience counters? It becomes a non-assigned kill, I guess, like death by wounds, or death by a grenade that hasn't got an owner?
|- valign="top"
!81
!0x51
|[[Firing Accuracy]] experience counter, for number of hits on an enemy (lethal or not, grenades or bullets). Each Autoshot hit counts as 1, so you can get 3 hits from one Autoshot burst. Likewise, grenades and blaster bombs can hit multiple targets with one explosion. Also, if you miss the intended target but hit a different alien, it still counts. Finally, if your shot actually has zero [[Damage]], it does still count as a hit. (Not due to armor blockage; a pure roll of 0 coming out of the gun.)
|- valign="top"
!82
!0x52
|[[Melee Accuracy]] experience counter, for number of times stun rod has been used (not stun bombs).
|- valign="top"
!83
!0x53
|[[Throwing Accuracy]] experience counter, for number of times unit has thrown any object.
|- valign="top"
!84
!0x54
|<div id="Psi_Skill_Experience_Counter"></div>[[Psionic Skill]] experience counter, for number of psi attacks performed. 1 is added if attempt was unsuccessful, 3 if it was successful. Note: if this value goes over 255, all psi experience is lost. That's 85 successful psis (255/3). So be careful of marathon psi'ing (a minimum of 43 turns at 2 psis/turn, 29 turns at 3/turn).
|- valign="top"
!85
!0x55
|[[Bravery]] experience counter, for number of times unit has ''resisted'' panicking, despite Morale < 50. Being mind-controlled, panicking, or going berserk does ''not'' increase this stat -- although Panic Unit attacks will reduce Morale to the point where panic checks will be performed by the game.
|- valign="top"
!86-110
!0x56-0x6E
|Unit's Name. Standard string ended by null byte. The rest can hold garbage.
|- valign="top"
!111
!0x6F
|Called "BigFire". If true (value of 1) then the unit is currently firing a weapon. It reverts back to 0 afterwards - determines whether to render the gun and firing arm in the "pointing weapon" position, or whether the weapon is being held against the chest. If manually set to a value above 0, the unit will hold its weapon out until such time as it actually uses it.

Note that this value is only used by units holding two-handed weapons. A unit holding for eg a pistol will ''always'' point the weapon, and uses a different arm sprite for the purposes of doing so (regardless of whether or not the weapon is being fired).
|- valign="top"
!112
!0x70
|Called "Finished". If true (value of 1) signifies that the unit finished AI actions for current turn.
|- valign="top"
!113
!0x71
|If 1, then you can't use the inventory button and the unit will be immune to stun. Used for tanks. Mind controlled units don't use this but their button disables anyway.

''BombBloke:'' This is the only way to access tank inventories.
*Tank/Cannon has a normal inventory and uses man_1m0.spk.
*Tank/Rocket Launcher has a different layout and uses man_1m0.spk.
*Tank/Laser Cannon uses man_œ.spk, which doesn't exist normally. Providing this file still crashes.
*Hovertank/Plasma simply crashes.
*Hovertank/Launcher simply crashes.

[[#1|[1]]] actually determines the inventory screen used, might be worth playing with that. [[#46|[46]]] determines the layout.
|- valign="top"
!114
!0x72
|If not 0, then unit is on fire, and will burn for this amount of turns.
|- valign="top"
!115
!0x73
|Gender: 0 = male, 1 = female.
|- valign="top"
!116
!0x74
|Hair/skin colour (for inventory; all other units = 0):
0: Blond caucasian
1: Brunette caucasian
2: Asian
3: Black
|- valign="top"
!117
!0x75
|Turret weapon. Over-rides hand held weapon. Turret images are not centered; that would be impossible because they aren't all 'objects' (e.g. Celatid). ''(Mix of notes by BB and NKF)''
F.A. TUs F.A. TUs
0: HWP cannon (bigobs[40])....................Aimed 90% 80% Snap 60% 33%
1: HWP rocket (bigobs[42])....................Aimed 115% 75% Snap 55% 45%
2: HWP laser (bigobs[54]).....................Aimed 85% 75% Snap 50% 33%
3: HWP plasma cannon (bigobs[43]).............Aimed 100% 60% Snap 86% 30%
4: HWP blaster (bigobs[43]) (looks like ordinary cannon?)......Aimed 120% 80%
5: Celatid plasma cannon (bigobs[38]).........Aimed 110% 60% Snap 75% 30%
6: Cyberdisc plasma cannon (bigobs[34]).......Aimed 110% 60% Snap 75% 30%
7: Sectopod Laser* cannon (bigobs[34])as cyberdisk, above, plus Auto 50% 35%
22: Invalid - Incredibly powerful armour piercing shell. Overpowering.
255: Unused
Note: This item will take precendence over any item carried in the hand slots. It can be installed on non-tanks, but then the unit won't be able to use any carried weapons or items. This weapon is NOT affected by the kneeling modifier, but it is affected by the current unit's accuracy stat. Also note, this byte does NOT determine the turret image for HWPs in the battlescape.

[*]The damage type for the Sectopod is indeed set to (3)laser in the executable! Graphical/sound effects of a turret weapon is set there as well, via a reference to a weapon in OBDATA.DAT (HWP Cannon=4=Heavy Cannon, Sectopod=34=Heavy Plasma) ''When I changed HWP Cannon to 2, it looked/sounded like rifle fire - Crus8r''

Also see [[#46|[46]]], [[#113|[113]]], and [[#118|[118]]].
|- valign="top"
!118
!0x76
|Ammo for [[#117|[117]]] turret weapon
|- valign="top"
!119
!0x77
|[Garbage unused by game] Movement related? Large unit related? Possible bitfield.
''MTR:''
00000000 0 Chryssalid(2), Civilian(9), Ethereal(2), Floater(2), Muton,
00000001 1 Muton, PA Soldier(2) Sectoid(2), Silacoid(2),
00000011 3 PA Soldier PA Soldier(2), Tank/Laser
00000101 5 Snakeman
00001010 10 Celatid ''- Hobbes game - could have some garbage''
00001101 13 Muton, PA Soldier '' (parens) is count, if more than 1 unit''
00010011 19 Snakeman
00100110 38 PA Soldier
00101010 42 Muton(3)
00110001 49 Muton
00110010 50 PA Soldier
00110101 53 Silacoid(2)
00111011 59 Celatid
00111111 63 Silacoid
01001110 78 PA Soldier
01100111 103 PA Soldier
01111111 127 Muton
10010000 144 Muton
11000000 192 Celatid
11111110 254 Muton
|- valign="top"
!120-123
!0x78-0x7B
|Unit bit flags (32bit), mainly re: mobility. They do NOT affect the soldier in inventory screen: ''(Mix of notes by BB and NKF)''
( 1) 1: 1 = Unit moving.
( 2) 2: 1 = Unit can fly.
( 4) 3: 1 = Unit is flying. (Toggles leg sprites for power armour.)
( 8) 4: 1 = Has been to this unit in next unit loop. Or to put it another way, has the unit been selected this turn.
( 16) 5: 1 = Unit has been disabled for selection.
(Stops the unit tab button from selecting this soldier.)
( 32) 6: 0 = Unit has left hand object selected, 1 = right hand object selected.
( 64) 7: 1 = Unit is kneeling.
(128) 8: 1 = Unit is wearing power/flying suit. (Can't be stunned by smoke flag?
Seems to work for fire, too.)
If a unit is carrying something in either hand, it is impossible to get him to appear as if he is carrying nothing - in the game, at least. If he is carrying nothing, bit 6 can flag (as though the unit was using it's right hand item). But maybe it's just the order of dropped items affecting this?

Note: A unit is only considered as flying if it is not on the ground. For example, a hover tank is not always considered as flying.

What if a hovertank is half on the ground, half in the air? What about a treaded tank, or large alien unit? What about units in lifts?
|- valign="top"
!124-125
!0x7C-0x7D
|TFTD ONLY - Bubble animation count for soldiers. Can be 0 to 16 (0x0F).
|- valign="top"
!126-127
!0x7E-0x7F
|TFTD ONLY - Bubble animation delay, skips this amount of frames.
|- valign="top"
!128-129
!0x80-0x81
|TFTD ONLY - Bubble animation enable. (0=disable, 1=enable) - [unused by game - taken from "underwater" flag]
|- valign="top"
!130-131
!0x82-0x83
|TFTD ONLY - Called "floorabove" flag. Is there a floor above unit? (0=no, 1=yes) [unused by game - calculated on-fly]
|-
|}

== Notes ==
1) The original/base values for soldier stats (offsets [[#23|[23]]]-[[#28|[28]]], etc.) correspond to the initial+increase bytes from [[SOLDIER.DAT|Soldier.Dat]] (bytes 43-62). Changes to these Unitref bytes are lost when the mission ends; instead, XCOM re-reads them from Soldier at that time. This makes sense because base soldier stats don't change during a mission per se (although they might increase when the mission ends); in this way, the programmers didn't have to bother with separately storing and/or adding initial+increase during combat. (It's also why you don't see the initial+increase in the soldier stat display during combat, that you can see back at base.) On a practical note, if you are testing soldier stat increases versus experience counters, change the experience counters in Unitref, but change the soldier stats in Soldier. (IOW, it doesn't matter what the soldier stats are in the combat mission.)

The Kill count (offset [[#78-79|[78-79]]]) is the only Unitref value I know of that is directly carried forward into the geoscape and Soldier.dat. However, some others do indirectly carry forward, for example: experience (offsets [[#80|[80]]]-[[#85|[85]]]) causes stat and rank increases, and decreased health (offset [[#26|[26]]] - offset [[#13|[13]]]) means hospital time. And, of course, death is permanent. Heh.

2) Experience counters (offsets [[#80|[80]]]-[[#85|[85]]]) determine the likelihood of soldier stat increases at the end of the combat mission, according to the formula for Primary Stats shown [[Experience#How_Experience_Points_Are_Applied|here]]. The Bravery counter (offset [[#85|[85]]]) affects Bravery as shown [[Bravery|here]].

Also, if at least one of the experience counters (except Throws) has a count, your secondary stats will increase, as discussed [[Experience#Secondary_Stats|here]]. All you need is at least a 1 in offsets [[#80|[80]]]-[[#82|[82]]] or [[#84|[84]]]-[[#85|[85]]]; more than 1 and/or multiple counters has no additional effect.

3) BombBloke's additional "To be Done" notes - can we cross some of these off yet?

Need to research:
Stun recovery rate, does it exist?
Hand to hand attacks
<strike>Offset of weapon from unit image?</strike>
''Based on unit height and nothing else. There may be values to determine what arm sprites to use,''
''but I doubt it.''
Firing sprite offset?
''Probably just based on unit height and some hardcoded values in the executable.''
<strike>Inventory lockout?</strike> ''All mind controlled units are locked out.''
Kneel lockout?
''Probably the same as above, I seem to remember that using XcomUtil to "swap sides" would make it''
''possible to kneel small alien units.''
<strike>Aliens seen?</strike> ''Not used in unitref.dat, only in unitpos.dat. -[[User:Zombie|Zombie]] 23:48, 29 September 2006 (PDT)''
<strike>Whether a unit slides/floats/hovers/rolls/walks (movement noise)?</strike> ''Set according to unit type.''
What else? The more to look for, the easier it is...

Know 119 values.
Unknown values (5 in total):
[[#75|[075 / 0x4B]]] - Always 0?
[[#119|[119 / 0x77]]] - No idea, possible bitfield, could be anything.
[[#121|[121 / 0x79]]] - Second unit gets a value of 16. Everyone else gets 0. No obvious purpose.
[[#122|[122 / 0x7A]]] - Always 0?
[[#123|[123 / 0x7B]]] - Always 0?

4) Hobbes posted a savegame with a TON of different aliens in it [http://www.xcomufo.com/forums/index.php?showtopic=8591 here] (message 6). Interesting for testing. But note it was made with XCOMUTIL and there may(?) be concerns over vailidity of unit info - see [[Talk:UNITREF.DAT]].

5) A [[HackerTools|Hex Workshop]] Structure Library for UNITREF.DAT created by Danial is [[UNITREF_DAT_HSL|here]].

== For More Information ==
*[[SOLDIER.DAT]]
*[[Soldiers|Soldier Stats]]
*[[Experience]]
*[[HackerTools|Hex editing]]

Return to [[Saved_Game_Files|Saved Game Files]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

UNITREF.DAT

2015-12-26T02:02:13Z

Morgan525: /* Structure */ more information on Byte 70.

A [[Saved Game Files|save game file]] that has a record size of 124 bytes for UFO, or 132 for TFTD. Values are unsigned unless otherwise stated. Some bytes represent bitfields. There are 80 records (not all of them necessarily used) for a fixed file size of 9,920 bytes (or 10,560 for TFTD). It goes hand in hand with [[UNITPOS.DAT]].

Comes in three flavours: 

*UNIREF.DAT 
Initially created by the GeoScape engine before tactical battles. Stored in the [[Saved_Game_Files#Missdat_Files|MISSDAT]] folder and contains info on all units that will be present in the coming mission (in an alive state - the deaths of aliens killed by exploding UFO power units isn't determined until [[Battlescape_Map_Generation#KABOOM.21.21|later]]). Unlike the other two versions, this only contains the bare minimum number of records required to store the units it details. 

*UNITREF.DAT 
Created along with a [[Saved_Game_Files#Battlescape_Files|battlescape save]], contains the mid-mission state of the unit table. 

*UNIREF2.DAT 
Appears in the [[Saved_Game_Files#Missdat_Files|MISSDAT]] folder at the end of combat. Used to determine which troopers/tanks survived, statistic gains via [[experience]], and which aliens need to be hauled off to the [[Alien Containment]] unit. 

Values are presented according to byte offset ([[#0|0]] to [[#123|123]] (or [[#131|131]] for TFTD)) followed by the equivalent hex offset ([[#0x00|0x00]] to [[#0x7B|0x7B]] (or [[#0x83|0x83]] for TFTD)). Notes apply to both UFO and TFTD unless otherwise stated. Let us know what else you can find - refer to the [[#Notes|bottom of the page]] for those values that're unknown, or to the [[Talk:UNITREF.DAT|talk page]] for further ideas as to what they could be.

== Structure ==

{| class="wikitable"
|-
!Offset (Decimal)
!Offset (Hex)
!Usage
|- valign="top"
!0
!0x00
|Type of unit. Unit scream and movement sound effects are based on this and gender. Gender and flying abilities affect the sprites as well. Not turrets. Specifically: [[#53|[53]]] & [[#54|[54]]] (weapons in hands), [[#115|[115]]] (gender) and [[#120|[120]]] (other flags) affect the final screen image. If the unit is a large unit, this will also determine the appearance of the last three quarters of the unit. This does NOT affect: the flying ability of the unit, the soldier image in the inventory screen, or the special abilities for certain aliens.
UFO TFTD
0: Male/female unarmored X-COM soldier 0: Male/female unarmored X-COM diver
1: Male/female personal armor soldier 1: Male/female plastic armor diver
2: Power/flying suit soldier 2: Power/flying suit diver
3: Tank 3: Tank
4: Sectoid 4: Aquatoid
5: Snakeman 5: Gillman
6: Ethereal 6: Lobster Man
7: Muton 7: Tasoth
8: Floater 8: Calcinite
9: Celatid 9: Deep One
10: Silacoid 0A: BioDrone
11: Chryssalid 0B: Tentaculat
12: Reaper 0C: Triscene
13: Sectopod 0D: Hallucinoid
14: Cyberdisc 0E: Xarquid
15: Male civilian 0F: Male civilians
16: Female civilian 10: Female civilians
17: Zombie 11: Zombie
255: Unused 255: Unused

<blockquote>If the corresponding [[UNITPOS.DAT]] record is unused, then the record is unused.</blockquote>
|- valign="top"
!1
!0x01
|Inventory paper doll image. File "UFOGRAPH\MAN_"+(char)(value + 48)+".SPK" will be used as the inventory sprite, unless the value is 0 or 1. In those cases, [[#115|[115]]] and [[#116|[116]]] are used to determine the picture.
0: No armor.
1: Personal armour.
2: Power suit.
3: Flying suit.
|- valign="top"
!2-5
!0x02-0x05
|Four byte value pointing to RAM location of the [[Image_Formats#PCK|PCK set]] used by the unit. Re-determined when the save game is loaded.
|- valign="top"
!6-9
!0x06-0x09
|Four byte value pointing to RAM location of the [[Image_Formats#PCK|TAB index for the PCK data]] used by the unit. Re-determined when the save game is loaded.
|- valign="top"
!10
!0x0A
|Unit facing. Does NOT control HWP turret direction; see [[#24|[24]]].
0: North (up right)
1: Northeast (right)
2: East (down right)
3: Southeast (down)
4: South (down left)
5: Southwest (left)
6: West (up left)
7: Northwest (up)
|- valign="top"
!11
!0x0B
|Movement type. When entering a given map location, each tile is checked to see the TU requirements accordingly. [[MCD]][39+[[#11|UnitRef[11]]]] is the offset used. Note: By default, this is 0 for ALL unit types.
0: Walking
1: Sliding
2: Flying
|- valign="top"
!12
!0x0C
|Current TUs.
|- valign="top"
!13
!0x0D
|Current Health. Health of 0 = Dead. Compare [[#42|[42]]], [[#120|[120]]].

''For my [[Talk:Bravery|Bravery experience point testing]], I killed 15 of 16 aliens by setting this to zero, and my soldiers to 0 Morale. When I loaded the savegame, the aliens were still "alive" (i.e., up), then all died when I ended this turn. So death is probably only checked when injury happens, and at end of turn... to truly kill them dead on the ground through savegame editing must take more. And arg - when they all died, my soldiers all went to 100 Morale! So I edited them back to 0 Morale. But guess what... then all the aliens died '''again''' at the end of '''next''' turn, even though they were all on the ground (I heard screams, and all soldiers' Morale went to 100 again). What the heck? The aliens stayed down after that, though. --[[User:MikeTheRed|MikeTheRed]] 16:01, 3 November 2006 (PST)''

''Update: [[UNITPOS.DAT]] offset 10 bit 2 should be used to kill a unit entirely dead. Thanks, NKF & BB - MTR''

: ''While the game kills characters when Health<=Fatal Wounds (__ dies message), XComUtil will recover them based if their health is greater than 0. Haven't tested an unmodified game. --[[User:Zaimoni|Zaimoni]] 11:52, 14 April 2007 (CDT)''
|- valign="top"
!14
!0x0E
|Current Stun level ''how much falloff of paralysis every turn? What determines it?''
|- valign="top"
!15
!0x0F
|Current Energy
|- valign="top"
!16
!0x10
|Current Reactions ''NKF: affected by health percentage''
|- valign="top"
!17
!0x11
|Strength
|- valign="top"
!18
!0x12
|Current Front Armour
|- valign="top"
!19
!0x13
|Current Left Armour
|- valign="top"
!20
!0x14
|Current Right Armour
|- valign="top"
!21
!0x15
|Current Rear Armour
|- valign="top"
!22
!0x16
|Current Under Armour
|- valign="top"
|colspan="3"|"Base" means the original (total) value (as carried forward from geoscape) - Also see Note 1 re: Base soldier stat values.
|- valign="top"
!23
!0x17
|Base Firing accuracy. Current value = this * [[#13|[13]]]/[[#26|[26]]] (percent health)
|- valign="top"
!24
!0x18
|Base Throwing accuracy. Current value = this * [[#13|[13]]]/[[#26|[26]]] (percent health)

Note: Tanks (turreted units?) always have 0 throwing accuracy. They use this for turret facing, relative to unit facing. 0 means it's facing forwards. Additional values are clockwise increments; see [[#10|[10]]].
|- valign="top"
!25
!0x19
|Base TUs
|- valign="top"
!26
!0x1A
|Base Health
|- valign="top"
!27
!0x1B
|Base Energy
|- valign="top"
!28
!0x1C
|Base Reactions
|- valign="top"
|colspan="3"|''These Base Armour values are used to show the starting armor value in the Attributes screen (so you can readily see if it's been damaged''
|- valign="top"
!29
!0x1D
|Base Front Armour
|- valign="top"
!30
!0x1E
|Base Left Armour
|- valign="top"
!31
!0x1F
|Base Right Armour
|- valign="top"
!32
!0x20
|Base Rear Armour
|- valign="top"
!33
!0x21
|Base Under Armour
|- valign="top"
!34
!0x22
|Supposedly this was going to be Health Recharge which would function like the Energy Recharge. Always 0 and ignored by game.
|- valign="top"
!35
!0x23
|Energy to recharge each turn. Equals '''recruit initial''' TUs/3 ([[SOLDIER.DAT]][43], '''not''' total base TUs). This is a signed byte. See [[Time Units]] and [[Energy#Usage|Energy Usage]]; also see [[#45|[45]]] (energy usage when walking/turning). ''BombBloke: Is this affected by damage?''
|- valign="top"
!36
!0x24
|Supposedly this was going to be Armor Recharge which would function like the Energy Recharge. Always 0 and probably unused, but needs testing.
|- valign="top"
!37
!0x25
|Psi skill. Psi stats not displayed/usable until this is greater then 0.
|- valign="top"
!38
!0x26
|Item to create when unit is unconscious/dead (index into obdata.dat).

NKF: If you set this value to that of a usable item, the item that is created in place of the unconscious or dead soldier can be used like the ordinary item. Elerium pods, for example, can be recovered for 50 elerium each after the battle. Weapons can be used as you normally use them, etc.

For unconscious 'units', the item will be treated as the unconscious body - it will retain the name of the unconscious unit when looked at via the inventory screen. Picking up and using the 'item' will work, but when the unit wakes up, the 'item' image in the soldier's hands is not cleared, even though the item no longer 'exists' in the soldier's hands. Using this 'item' will just crash the battlescape.

Actually, I do not even want to think about what would happen if you 'prime' a grenade/stunned body.
|- valign="top"
!39
!0x27
|"Soldier value" a.k.a. victory points. You gain (or lose, as the case may be) score at the end of combat according to this value when the unit dies.
*For X-COM units: A soldier with 42 will be worth -42 points if killed. Note this doesn't seem to apply if the soldier is killed when unconscious. The soldier just vanishes.
*For aliens: A commander with 35 will give you +35 points if killed.
*This value is the same as [[SOLDIER.DAT]] bytes 15-16 (a Word) and equals:
20 + Missions + Rank Bonus

with [[Rank]] Bonus as follows: SGT +1, CPT +3, COL +6, CDR +10
Note that although this equation holds true, the value is not actually computed per se. Instead, 1 is added directly to it each mission, as is a rank-bonus delta if you advance (e.g. COL to CDR, delta +4). In other words, hacking the Missions or Rank fields does not affect this value.
|- valign="top"
!40
!0x28
|Index into [[SOLDIER.DAT]], so game knows what to update. 255 = does not belong to anyone (i.e., it's not a soldier). ''NKF: This byte is critical for player controlled units. If this doesn't refer to anything, the unit ceases to exist at the end of the game. If it points to a valid soldier entry in soldier.dat, the soldier.dat entry will be updated.''
|- valign="top"
!41
!0x29
|Animation frame counter for the unit. Used by eg [[Celatid]]s and [[Silacoid]]s.
|- valign="top"
!42
!0x2A
|Rank. Affects morale loss and interface icon (hull for tanks). Only X-COM troopers display rank icons.
X-COM
0: Rookie ''Civvies are 0 too''
1: Squaddie
2: Sergeant
3: Captain
4: Colonel
5: Commander
255: Dead/unused

Aliens
1: Commander
2: Leader
3: Engineer
4: Medic
5: Navigator
6: Soldier
7: Terrorist
255: Dead/unused

Hull shape for X-COM tanks:
0: Treaded
1: Hover
''I don't see 255 set for three dead mutons in a current game... [[#13|[13]]] (Health=0) seems to be the only reliable death indicator for them. Compare [[#120|[120]]]. -[[User:MikeTheRed|MikeTheRed]]''
|- valign="top"
!43
!0x2B
|Called "deployment" with values of 0 or 1 (0=normal, 1=special).
0: Only those locations specified for units of the appropriate rank, size, and flying ability are used.
1: Civilian spawn points are used, ignoring a unit's rank, but still selected by the unit's size and flying ability.
As result - Commanders/leaders can occasionally be spawned outside of the UFO craft (and ramble around the UFO) and not in the "control room", which has an exclusive commander spawn node.
|- valign="top"
!44
!0x2C
|Alien aggression. The higher it is, the less likely an alien will take cover. Maximum of 2. 0=Cautious,1=Normal,2=Aggressive ''MTR: This is true for aliens in Hobbes game, but soldiers have values from 4 to 254. Garbage? Delete this comment if so.'' This determines the amount of the unit's TUs that are devoted to shooting: 0=50%,1=60%,2=66%.
|- valign="top"
!45
!0x2D
|Used to calculate energy loss when walking or turning as: INT( TUs / 2[45] ). See [[Energy#Usage]]; compare [[#35|[35]]] (energy recharge per turn). Set this byte to 4 to ensure no energy use whatsoever (maximum map [[Time Units#Time_Unit_Walking_Usage_Tables|tile TU cost]] is 12). ''In Hobbes game, many aliens are 0 and all soldiers are 1, but a dozen aliens have higher values ranging all the way up to 112! Garbage and/or the game doesn't care if they are garbage?''
|- valign="top"
!46
!0x2E
|HWP turret image. Only used (and only appears) if unit type [[#0|[0]]]=3 (X-COM tanks):
0: Cannon
1: Rocket
2: Laser
3: Plasma
4: Blaster
5,6: ? Blanks
'''Note:''' For non-tanks, this controls the inventory layout. ''Only'' 0 and 1 are valid. 0 is the standard layout seen on all soldiers. 1 is an alternate layout that may have been intended for custom tank equipment. Larger values only crash the game due to missing files. Also see [[#113|[113]]] and [[#117|[117]]].
|- valign="top"
!47
!0x2F
|This is a direct copy of offset[48] from the [[MCD]] record of the tile the unit is standing on. A signed byte.
|- valign="top"
!48
!0x30
|Values for this byte always equal [[#52|[52]]] and are:
2 (3x3 square; legacy 5 pixels): Sectoid
3 (5x5 square, corners removed; legacy 7 pixels): Celatid, Chryssalid, Civvie,
Ethereal, Floater, Muton, Snake, '''Soldier'''
4 (7x7 octagon; legacy 9 pixels): Cyberdisc, Hovertank, Reaper, Sectopod, Tank
5 (9x9 square, Ls with 3-pixel legs removed; legacy 11 pixels): Silacoid
Based on copious research by [[User:Bomb_Bloke|Bomb_Bloke]], [[User:Seb76|Seb76]], [[user:Zombie|Zombie]], and others, this has been found to be a LOF Template look-up for the shape of targets; Loftemps 2 to 5 define the "3D" shape of units relative to Line Of Fire as a cylinder, where 2 (Sectoid) is a thin cylinder and 5 (Silacoid) is very wide. The pixel width of each "silhoutte" that [[LOFTEMPS.DAT]] corresponds to has been added to the list above (see LOFTemps images 2-5). Tiles are 16 pixels wide in the X or Y direction (that's what this byte is about), and 24 pixels high (compare [[#49|[49]]]).

This cylindrical shape is used in conjunction with height [[#49|[49]]] to define the silhouette that targets present to a shooter. Combine the pixel-width cross-section from Loftemps with height to find the cross-sectional area presented to shooters (sorted on increasing cross-section):

LOF LOF Cross Percent
Lookup Width Height Section of 384 Float 4x?
Type ''UR[48] Pixels UR[[#49|[49]]] Pxls X Ht (16x24) UR[[#51|[51]]]''
---- ------ ------ ------ --------- ------- ------ ---
Sectoid 2 5 16 80 20.8% - -
Celatid 3 7 12 84 21.9% 6 -
Soldier (Kneeling) 3 7 14 98 25.5% - -
Hovertank 4 9 12 108 28.1% 6 Yes
Silacoid 5 11 10 110 28.6% - -
Snakeman 3 7 18 126 32.8% - -
Zombie 3 7 18 126 32.8% - -
Ethereal 3 7 20 140 36.5% - -
Cyberdisc 4 9 15 135 35.2% 2 Yes
Chryssalid 3 7 21 147 38.3% - -
Civilian 3 7 21 147 38.3% 2 -
Floater 3 7 21 147 38.3% 2 -
Muton 3 7 21 147 38.3% - -
Tank 4 9 16 144 37.5% - Yes
Soldier 3 7 22 154 40.1% - -
Reaper 4 9 23 207 53.9% - Yes
Sectopod 4 9 23 207 53.9% - Yes
Units take up an amount of the whole tile (as seen in cross-section by a shooter) as shown in the "Percent of 384" column. In reality, though, the [[Firing Accuracy|accuracy]] of shots makes this a more complex topic than the percents suggest. Also, dividing by 384 is an oversimplification, since it implies a directly rectangular shot (shooting right down the X or Y axis). While it's useful to see, keep in mind that this column only shows relative numbers.

: [[User:Zaimoni|Zaimoni]]: actual cross section depends on shot facing. The table is close to correct for pure diagonal shots, so leaving alone for now.

The unit Float number ([[#51|[51]]], below) is shown simply for convenience. It does not enter into the cross-sectional computations. "4x" units actually consist of four units grouped in tight 2x2 formation (making their cross section effectively much larger then the percentage stated).

Note that causing an X-Com soldier to kneel causes their cross section to fall by 36.36~% of that of when they are standing.
|- valign="top"
!49
!0x31
|[[height|Standing height]].
|- valign="top"
!50
!0x32
|[[height|Kneeling height]].
|- valign="top"
!51
!0x33
|Floating [[height]]. A unit 'floats' this high above the ground, thus allowing shots to fly underneath. The highest point of a unit can be found by adding this to the units height stat. Does this have an effect on explosive damage?
|- valign="top"
!52
!0x34
|"Radius" of LOF Template. Always the same as [[#48|[48]]] in all known saved games. More info can be found at [[Talk:UNITREF.DAT#Offsets_0x30_.26_0x34|Talk:UNITREF.DAT#Offsets_0x30_&_0x34]] ([48] and [52]).
|- valign="top"
!53
!0x35
|Image index for item in left hand. 255 for none. Indexes into [[OBDATA.DAT]], not [[OBPOS.DAT]].
|- valign="top"
!54
!0x36
|Image index for item in right hand. 255 for none. Indexes into [[OBDATA.DAT]], not [[OBPOS.DAT]].
|- valign="top"
|colspan="3"|''NKF:'' If there is no item in the unit's hands, but one of the above two bytes are set, the 'image' that represents the item will still be displayed in the battlescape. If these phantom items are clicked on, the game crashes. If the image is not the right type for the real item in hand, the ammo count doesn't get displayed. Otherwise, it'll work as normal.
|- valign="top"
!55
!0x37
|[[Damage#Susceptible_to...|Damage Modifier]] Category

This field is simply a look-up table, or more directly, a way to categorize the units into similar groups. The actual modifiers are listed in the executable. A value of 1 indicates the first DM category, a value of 4 indicates the 4th, etc. The values of 2 and 3 are not seen in the alien stats as they refer to X-COM soldier armor info. I'm not sure about 13 as the Zombie's stats haven't been found yet, but I think there is a category in the DM's for it.

'''Value''' '''Unit Type(s)'''
'''0''' Terrain and Items
'''1''' Civilian, Sectoid, Celatid, Floater
'''2''' Personal Armor
'''3''' Power Suit, Flying Suit
'''4''' Tanks, Hovertanks
'''5''' Snakemen
'''6''' Ethereal
'''7''' Muton
'''8''' Silacoid
'''9''' Chryssalid
'''10''' Reaper
'''11''' Sectopod
'''12''' Cyberdisc
'''13''' Zombie
|- valign="top"
!56
!0x38
|[[Melee Accuracy]] ([[SOLDIER.DAT]] bytes 50 (initial) & 60 (increase) added together)
|- valign="top"
!57
!0x39
|[[Psionic Strength]]
|- valign="top"
!58
!0x3A
|Current [[Morale]]. Base morale is hardcoded to 100.
|- valign="top"
!59
!0x3B
|[[Bravery]] = 110 - (10 * ''this value'')
|- valign="top"
!60
!0x3C
|Panic mode. This takes effect at the start of the unit's next turn. Since it is cleared at that point, you'll never see it at anything other then 0 in the save files. You can manually change it to other values to force a specific panic attack on the next turn.
0: None
1: Freeze
2: Running
3: Berserk
|- valign="top"
!61
!0x3D
|[[#62|[62]]] will increment by this amount whenever the unit moves.
3: Sectiod ''- Hobbes''
4: Soldiers, civs, and all other aliens (but Hobbes had no Large aliens)
30: Tank/Laser
|- valign="top"
!62
!0x3E
|Visibility via motion scanner. The bigger it is, the bigger the blip. Test this one out for values.
|- valign="top"
!63
!0x3F
|Number of [[Fatal Wounds]] to head.
|- valign="top"
!64
!0x40
|Number of fatal wounds to torso.
|- valign="top"
!65
!0x41
|Number of fatal wounds to right arm.
|- valign="top"
!66
!0x42
|Number of fatal wounds to left arm.
|- valign="top"
!67
!0x43
|Number of fatal wounds to right leg.
|- valign="top"
!68
!0x44
|Number of fatal wounds to left leg.
|- valign="top"
!69-70
!0x45-0x46
|Indexes into [[ROUTES.DAT]]. To start with, aliens will be located at the same position as the node indicated by byte 69.
:For patrol AI (no X-COM units sighted in turn 1, either X-COM or alien):
::Byte 69 is the index of the node of the start of the planned move.
::Byte 70 is the index of the node of the end of the planned move.
:Note that the move may be multi-turn, and byte 69 is not guaranteed to update during a multi-turn move. I think it will if the alien ends its move on a node, however. -- Zaimoni
:For AI mode 2:
::Byte 70 is the UNITPOS reference number for this unit's target. - Tycho
|- valign="top"
!71
!0x47
|Unit lighting: always 16 for XCom units, 0 for most aliens but 1 for cyberdisc. If greater than 1, it is set to 1 when unit inactive - see the [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page.
|- valign="top"
!72
!0x48
|The amount of [[Morale]] that has been restored using the [[Medi-Kit (EU)|Medkit's]] painkillers. The amount that ''can'' be restored is equal to the maximum health of the unit (index 26) minus their current health (index 13) further minus this.
|- valign="top"
!73
!0x49
|Intelligence. Rated from 2 - 8. Indicates for how many turns the alien will know the location of spotted soldiers. ''Hey - why do humans have zero intelligence? :(''
|- valign="top"
!74
!0x4A
|AI Mode. Zaimoni found [http://www.strategycore.co.uk/forums/UFO-AI-patch-t8908.html&st=20&start=20 Here] that the values are 0:PATROL, 1:SNIPER, 2:ATTACKING, 3:ESCAPING, 4:GUARD, 5:Returning to UFO. 255 (-1) is also possible. Zaimoni tripped this by wounding a Floater in SNIPER mode; it returned fire, then was taken down by another soldier. Snap guess is that this is a "recalculate" marker.
|- valign="top"
!75
!0x4B
|Unknown. With that said, the only item remaining on my list is called "lightdirect" or direction of light for a unit (0=all around, 1=direction unit facing). Unused by game code and always 0. Maybe it was for a hand-held light source, or a armor-mounted flashlight?
|- valign="top"
!76-77
!0x4C-0x4D
|Mission count. Signed integer (low byte, high byte) also found in [[SOLDIER.DAT]] ''MTR: Wonder why they bothered to put this in Unitref since this will never change '''during''' a mission; compare how soldier stats are actually read from SOLDIER (not UNITREF) on return to geoscape. Is Missions shown anywhere on the combatscape?
|- valign="top"
!78-79
!0x4E-0x4F
|Kill count. Signed integer (low byte, high byte) also found in [[SOLDIER.DAT]]. Number of kills this unit has made for ALL missions, not just this one. This one '''can''' vary "unpredictably" and thus is the only byte known to directly carry forward into the geoscape / Soldier.Dat!
|- valign="top"
!80
!0x50
|[[Reactions]] experience counter, for number of reaction shots. It doesn't matter if they hit the target; reactions still count. See Note 2 re: Experience counters. (Also note: Aliens do not use experience counters.)

''NKF:'' Where does death by fire (overexposure rather than incendiary shell impact) fit into the experience counters? It becomes a non-assigned kill, I guess, like death by wounds, or death by a grenade that hasn't got an owner?
|- valign="top"
!81
!0x51
|[[Firing Accuracy]] experience counter, for number of hits on an enemy (lethal or not, grenades or bullets). Each Autoshot hit counts as 1, so you can get 3 hits from one Autoshot burst. Likewise, grenades and blaster bombs can hit multiple targets with one explosion. Also, if you miss the intended target but hit a different alien, it still counts. Finally, if your shot actually has zero [[Damage]], it does still count as a hit. (Not due to armor blockage; a pure roll of 0 coming out of the gun.)
|- valign="top"
!82
!0x52
|[[Melee Accuracy]] experience counter, for number of times stun rod has been used (not stun bombs).
|- valign="top"
!83
!0x53
|[[Throwing Accuracy]] experience counter, for number of times unit has thrown any object.
|- valign="top"
!84
!0x54
|<div id="Psi_Skill_Experience_Counter"></div>[[Psionic Skill]] experience counter, for number of psi attacks performed. 1 is added if attempt was unsuccessful, 3 if it was successful. Note: if this value goes over 255, all psi experience is lost. That's 85 successful psis (255/3). So be careful of marathon psi'ing (a minimum of 43 turns at 2 psis/turn, 29 turns at 3/turn).
|- valign="top"
!85
!0x55
|[[Bravery]] experience counter, for number of times unit has ''resisted'' panicking, despite Morale < 50. Being mind-controlled, panicking, or going berserk does ''not'' increase this stat -- although Panic Unit attacks will reduce Morale to the point where panic checks will be performed by the game.
|- valign="top"
!86-110
!0x56-0x6E
|Unit's Name. Standard string ended by null byte. The rest can hold garbage.
|- valign="top"
!111
!0x6F
|Called "BigFire". If true (value of 1) then the unit is currently firing a weapon. It reverts back to 0 afterwards - determines whether to render the gun and firing arm in the "pointing weapon" position, or whether the weapon is being held against the chest. If manually set to a value above 0, the unit will hold its weapon out until such time as it actually uses it.

Note that this value is only used by units holding two-handed weapons. A unit holding for eg a pistol will ''always'' point the weapon, and uses a different arm sprite for the purposes of doing so (regardless of whether or not the weapon is being fired).
|- valign="top"
!112
!0x70
|Called "Finished". If true (value of 1) signifies that the unit finished AI actions for current turn.
|- valign="top"
!113
!0x71
|If 1, then you can't use the inventory button and the unit will be immune to stun. Used for tanks. Mind controlled units don't use this but their button disables anyway.

''BombBloke:'' This is the only way to access tank inventories.
*Tank/Cannon has a normal inventory and uses man_1m0.spk.
*Tank/Rocket Launcher has a different layout and uses man_1m0.spk.
*Tank/Laser Cannon uses man_œ.spk, which doesn't exist normally. Providing this file still crashes.
*Hovertank/Plasma simply crashes.
*Hovertank/Launcher simply crashes.

[[#1|[1]]] actually determines the inventory screen used, might be worth playing with that. [[#46|[46]]] determines the layout.
|- valign="top"
!114
!0x72
|If not 0, then unit is on fire, and will burn for this amount of turns.
|- valign="top"
!115
!0x73
|Gender: 0 = male, 1 = female.
|- valign="top"
!116
!0x74
|Hair/skin colour (for inventory; all other units = 0):
0: Blond caucasian
1: Brunette caucasian
2: Asian
3: Black
|- valign="top"
!117
!0x75
|Turret weapon. Over-rides hand held weapon. Turret images are not centered; that would be impossible because they aren't all 'objects' (e.g. Celatid). ''(Mix of notes by BB and NKF)''
F.A. TUs F.A. TUs
0: HWP cannon (bigobs[40])....................Aimed 90% 80% Snap 60% 33%
1: HWP rocket (bigobs[42])....................Aimed 115% 75% Snap 55% 45%
2: HWP laser (bigobs[54]).....................Aimed 85% 75% Snap 50% 33%
3: HWP plasma cannon (bigobs[43]).............Aimed 100% 60% Snap 86% 30%
4: HWP blaster (bigobs[43]) (looks like ordinary cannon?)......Aimed 120% 80%
5: Celatid plasma cannon (bigobs[38]).........Aimed 110% 60% Snap 75% 30%
6: Cyberdisc plasma cannon (bigobs[34]).......Aimed 110% 60% Snap 75% 30%
7: Sectopod Laser* cannon (bigobs[34])as cyberdisk, above, plus Auto 50% 35%
22: Invalid - Incredibly powerful armour piercing shell. Overpowering.
255: Unused
Note: This item will take precendence over any item carried in the hand slots. It can be installed on non-tanks, but then the unit won't be able to use any carried weapons or items. This weapon is NOT affected by the kneeling modifier, but it is affected by the current unit's accuracy stat. Also note, this byte does NOT determine the turret image for HWPs in the battlescape.

[*]The damage type for the Sectopod is indeed set to (3)laser in the executable! Graphical/sound effects of a turret weapon is set there as well, via a reference to a weapon in OBDATA.DAT (HWP Cannon=4=Heavy Cannon, Sectopod=34=Heavy Plasma) ''When I changed HWP Cannon to 2, it looked/sounded like rifle fire - Crus8r''

Also see [[#46|[46]]], [[#113|[113]]], and [[#118|[118]]].
|- valign="top"
!118
!0x76
|Ammo for [[#117|[117]]] turret weapon
|- valign="top"
!119
!0x77
|[Garbage unused by game] Movement related? Large unit related? Possible bitfield.
''MTR:''
00000000 0 Chryssalid(2), Civilian(9), Ethereal(2), Floater(2), Muton,
00000001 1 Muton, PA Soldier(2) Sectoid(2), Silacoid(2),
00000011 3 PA Soldier PA Soldier(2), Tank/Laser
00000101 5 Snakeman
00001010 10 Celatid ''- Hobbes game - could have some garbage''
00001101 13 Muton, PA Soldier '' (parens) is count, if more than 1 unit''
00010011 19 Snakeman
00100110 38 PA Soldier
00101010 42 Muton(3)
00110001 49 Muton
00110010 50 PA Soldier
00110101 53 Silacoid(2)
00111011 59 Celatid
00111111 63 Silacoid
01001110 78 PA Soldier
01100111 103 PA Soldier
01111111 127 Muton
10010000 144 Muton
11000000 192 Celatid
11111110 254 Muton
|- valign="top"
!120-123
!0x78-0x7B
|Unit bit flags (32bit), mainly re: mobility. They do NOT affect the soldier in inventory screen: ''(Mix of notes by BB and NKF)''
( 1) 1: 1 = Unit moving.
( 2) 2: 1 = Unit can fly.
( 4) 3: 1 = Unit is flying. (Toggles leg sprites for power armour.)
( 8) 4: 1 = Has been to this unit in next unit loop. Or to put it another way, has the unit been selected this turn.
( 16) 5: 1 = Unit has been disabled for selection.
(Stops the unit tab button from selecting this soldier.)
( 32) 6: 0 = Unit has left hand object selected, 1 = right hand object selected.
( 64) 7: 1 = Unit is kneeling.
(128) 8: 1 = Unit is wearing power/flying suit. (Can't be stunned by smoke flag?
Seems to work for fire, too.)
If a unit is carrying something in either hand, it is impossible to get him to appear as if he is carrying nothing - in the game, at least. If he is carrying nothing, bit 6 can flag (as though the unit was using it's right hand item). But maybe it's just the order of dropped items affecting this?

Note: A unit is only considered as flying if it is not on the ground. For example, a hover tank is not always considered as flying.

What if a hovertank is half on the ground, half in the air? What about a treaded tank, or large alien unit? What about units in lifts?
|- valign="top"
!124-125
!0x7C-0x7D
|TFTD ONLY - Bubble animation count for soldiers. Can be 0 to 16 (0x0F).
|- valign="top"
!126-127
!0x7E-0x7F
|TFTD ONLY - Bubble animation delay, skips this amount of frames.
|- valign="top"
!128-129
!0x80-0x81
|TFTD ONLY - Bubble animation enable. (0=disable, 1=enable) - [unused by game - taken from "underwater" flag]
|- valign="top"
!130-131
!0x82-0x83
|TFTD ONLY - Called "floorabove" flag. Is there a floor above unit? (0=no, 1=yes) [unused by game - calculated on-fly]
|-
|}

== Notes ==
1) The original/base values for soldier stats (offsets [[#23|[23]]]-[[#28|[28]]], etc.) correspond to the initial+increase bytes from [[SOLDIER.DAT|Soldier.Dat]] (bytes 43-62). Changes to these Unitref bytes are lost when the mission ends; instead, XCOM re-reads them from Soldier at that time. This makes sense because base soldier stats don't change during a mission per se (although they might increase when the mission ends); in this way, the programmers didn't have to bother with separately storing and/or adding initial+increase during combat. (It's also why you don't see the initial+increase in the soldier stat display during combat, that you can see back at base.) On a practical note, if you are testing soldier stat increases versus experience counters, change the experience counters in Unitref, but change the soldier stats in Soldier. (IOW, it doesn't matter what the soldier stats are in the combat mission.)

The Kill count (offset [[#78-79|[78-79]]]) is the only Unitref value I know of that is directly carried forward into the geoscape and Soldier.dat. However, some others do indirectly carry forward, for example: experience (offsets [[#80|[80]]]-[[#85|[85]]]) causes stat and rank increases, and decreased health (offset [[#26|[26]]] - offset [[#13|[13]]]) means hospital time. And, of course, death is permanent. Heh.

2) Experience counters (offsets [[#80|[80]]]-[[#85|[85]]]) determine the likelihood of soldier stat increases at the end of the combat mission, according to the formula for Primary Stats shown [[Experience#How_Experience_Points_Are_Applied|here]]. The Bravery counter (offset [[#85|[85]]]) affects Bravery as shown [[Bravery|here]].

Also, if at least one of the experience counters (except Throws) has a count, your secondary stats will increase, as discussed [[Experience#Secondary_Stats|here]]. All you need is at least a 1 in offsets [[#80|[80]]]-[[#82|[82]]] or [[#84|[84]]]-[[#85|[85]]]; more than 1 and/or multiple counters has no additional effect.

3) BombBloke's additional "To be Done" notes - can we cross some of these off yet?

Need to research:
Stun recovery rate, does it exist?
Hand to hand attacks
<strike>Offset of weapon from unit image?</strike>
''Based on unit height and nothing else. There may be values to determine what arm sprites to use,''
''but I doubt it.''
Firing sprite offset?
''Probably just based on unit height and some hardcoded values in the executable.''
<strike>Inventory lockout?</strike> ''All mind controlled units are locked out.''
Kneel lockout?
''Probably the same as above, I seem to remember that using XcomUtil to "swap sides" would make it''
''possible to kneel small alien units.''
<strike>Aliens seen?</strike> ''Not used in unitref.dat, only in unitpos.dat. -[[User:Zombie|Zombie]] 23:48, 29 September 2006 (PDT)''
<strike>Whether a unit slides/floats/hovers/rolls/walks (movement noise)?</strike> ''Set according to unit type.''
What else? The more to look for, the easier it is...

Know 119 values.
Unknown values (5 in total):
[[#75|[075 / 0x4B]]] - Always 0?
[[#119|[119 / 0x77]]] - No idea, possible bitfield, could be anything.
[[#121|[121 / 0x79]]] - Second unit gets a value of 16. Everyone else gets 0. No obvious purpose.
[[#122|[122 / 0x7A]]] - Always 0?
[[#123|[123 / 0x7B]]] - Always 0?

4) Hobbes posted a savegame with a TON of different aliens in it [http://www.xcomufo.com/forums/index.php?showtopic=8591 here] (message 6). Interesting for testing. But note it was made with XCOMUTIL and there may(?) be concerns over vailidity of unit info - see [[Talk:UNITREF.DAT]].

5) A [[HackerTools|Hex Workshop]] Structure Library for UNITREF.DAT created by Danial is [[UNITREF_DAT_HSL|here]].

== For More Information ==
*[[SOLDIER.DAT]]
*[[Soldiers|Soldier Stats]]
*[[Experience]]
*[[HackerTools|Hex editing]]

Return to [[Saved_Game_Files|Saved Game Files]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

GEOSCAPE.EXE

2015-11-21T07:07:20Z

Morgan525: /* Craft type data */

The "Geoscape" program that handles base management and aircraft, a.k.a. XCOM outside of tactical combat. [[TACTICAL.EXE]] handles combat.

'''NOTE:''' In the WinCE version, GEOSCAPE and TACTICAL are one executable, "UFO Defense.exe". Due to this confusion (what wiki pages place things on, when they're practically identical), currently GEOSCAPE, TACTICAL, and UFO Defense information appear here. (Unless and until someone wants to break everything up... then again, having highly related stuff in one place is a good thing.)

Also see [[Versions]].

= XCOM: UFO Defense (U.S. DOS) version 1.4 =
*Is 382,957 bytes long for the virgin 1.4 executable
*Has [[Alien_Stats|alien statistics]] starting at (non-offset) byte 379,729. There are 33 records of 39 bytes each. No alien names, though.
*If you have installed [[XcomUtil]], it may alter the length of GEOSCAPE. ''Does anybody have a modified version, so we can put the length here? --[[User:MikeTheRed|MikeTheRed]]''
** My XCOM Util GEOSCAPE size is 415,271 --[[User:Pi Masta|Pi Masta]]
** My XCOM Util GEOSCAPE size is still 382,957, Pi Masta I think is using 1.2, because that is the size of that file normally --[[User:hatfarm|hatfarm]]
** XcomUtil Does not alter the length of the EXE's only data sections of the code are overwrite (Only splitting the exe adds code but uses padding in the EXE. --[[User:BladeFireLight|BladeFireLight]] 01:16, 5 January 2010 (EST)

= XCOM Windows Collector's Edition =
*Variously called the '''Win CE''' or '''Gold''' version on the wiki
*Is 495,616 bytes long
*Starting at byte 648, reads:
XCOM: UFO Defense Gold Edition
This awesome game was compiled on Sep 8 1999 at 08:57:11
Copyright - 1999 Hasbro Interactive/MicroProse Software
Party on dude.
*If you install XcomUtil, it separates your ''UFO Defense.exe'' into GEOSCAPE and TACTICAL executables. They are almost identical copies of ''UFO Defense.exe'', however they start at the right place when run. This allows the game to closely mimick the Dos version by having its main loop run in a batch file.
*Has [[Alien_Stats|alien statistics]] starting at (non-offset) byte 480,145 (75391x). There are 33 records of 39 bytes each. No alien names, though.
*Has tank & inbuilt alien weapon stats at byte 447,868 (6D57Cx, see below).
*Has the copy protection codes written in the manual starting at byte 475,176 (74028x) (despite the fact that the game stopped asking for these prior to the Windows port!).

= File Templates =
There appears to be 'templates' of some of the [[Saved Game Files|game files]] stored within this executable. Makes sense as initially no saved game files are present when installed. Here is a list of known positions and the corresponding file. Offsets are from DOS Version of the game patched with XComUtil
{| {{StdDescTable}}
|- {{StdDescTable_Heading}}
! Offset (Hex) !! Offset (Dec) !! Length (Bytes) !! File
|-
| 5AB28 || 371496 || 2112|| [[RESEARCH.DAT]]
|-
| 5B5E0 || 374240 || 272|| [[FACIL.DAT]]
|-
| 5B6F0 || 374512 || 1820|| [[PURCHASE.DAT]]
|-
| 5D894 || 383124 || 576 || [[DIPLOM.DAT]]
|-
| 5E48C || 386188 || 1392|| [[UP.DAT]]
|-
| 5EB90 || 387984 || 84|| [[ACTS.DAT]]
|-
| 5FAC0 || 391872 || 2336|| [[BASE.DAT]]
|-
| 5FBB8 || 392120 || 5200|| [[CRAFT.DAT]]
|}

Possibly these are in-game data structures used to hold the current in-memory state, between game saves?

= Craft type data =

At offset 353,020 in X-COM 1.4 (DOS), the aircraft statistics begin. In WinCE this starts at hex offset 0x6F9A8 and Alien craft start at 0x6fa34.

.data:0046F9A8
00 02 04 06 08 0A 0C 0E 18 1A
<23Ah, -200, 0, 760, 2, 1500, 150, 4, 0, 0, 0, 0, 0E, 03, 0> ; 0 ''Skyranger''
<23Bh, -300, 1, 3100, 8, 30, 800, 4, 0, 0, 0, 0, 0C, 00, 0> ; 1 ''Lightning''
<23Ch, -400, 2, 5400, Ah, 60, 1200, 4, 0, 0, 0, 0, 1A, 04, 0> ; 2 ''Avenger''
<23Dh, -250, 2, 2100, 3, 1000, 100, 4, 0, 0, 0, 0, 0, 00, 0> ; 3 ''Interceptor''
<23Eh, -250, 2, 4200, 9, 20, 500, 4, 0, 0, 0, 0, 0, 00, 0> ; 4 ''Firestorm''

.data:0046FA34
00 02 04 06 08 0A 0C 0E 10 12 14 16
<2B2h, 100, 2, 2200, Ch, 0, 50, 5, 38h, C8h, 0, 0, 0, 0, 0> ; 5 ''Small Scout (VS)''
<2B3h, 150, 2, 2400, 9, 0, 200, 4, 38h, FAh, 78h, 14, 0, 0, 0> ; 6 ''Medium Scout (S)''
<2B4h, 250, 2, 2700, 9, 0, 250, 4, 30h, 12Ch, 110h, 14, 0, 0, 0> ; 7 ''Large Scout (S)''
<2B5h, 500, 2, 4000, 8, 0, 500, 3, 30h, 1F4h, B0h, 28, 0, 0, 0> ; 8 ''Abductor (M)''
<2B6h, 500, 2, 4300, 8, 0, 500, 3, 20h, 1F4h, A0h, 28, 0, 0, 0> ; 9 ''Harvester (M)''
<2B7h, 1000, 2, 4800, 6, 0, 1200, 2, 18h, 7D0h, 150h, 78, 0, 0, 0> ; 10 ''Terror Ship (L)''
<2B8h, 1400, 2, 5000, 6, 0, 3000, 1, 18h, FA0h, 208h, 8C, 0, 0, 0> ; 11 ''Battleship (VL'')
<2B9h, 800, 2, 3200, 6, 0, 2200, 2, 18h, BB8h, 120h, 3C, 0, 0, 0> ; 12 ''Supply Ship (L)''

known fields (14 x 2-byte dwords per record)
00 nameIdx reference to the ENGLISH.DAT entry
02 score Destroyed ; base 10
04 weapon Pods ''Xcraft only''
06 max Speed ''in knots'' ; base 10
08 acceleration
0A fuel Capacity ; base 10
0C damage Capacity ; base 10
0E ufo Size ''5 - Very Small / 4 - Small (inc. XCom) / 3 - Medium / 2 - Large / 1 - Very Large -spike''
10 ufo Reload time ''Firing interval (rand(x-(diff*2))+(x-(diff*2)).
Values: 56=S/MSct 48=LSct/Abd 32=Harv 24=Suppl/Terr/BS.''
12 ufo Escape Time ''100~200% = time before UFO attempts escape (on Beginner).
Values: SS=200 MS=250 LS=300 A=500 H=500 TS=2000 BS=4000 SS=3000''
14 weapon range ''distance in km*8''
16 weapon damage ''(0%-100%)''
18 Troop Space ''Troop capacity (Xcraft only)''
1A HWP Space ''HWP capacity (Xcraft only)''
1C structCraftData ends

Here is the hex signature of all craft:

3A 02 38 FF 00 00 F8 02 02 00 DC 05 96 00 04 00 00 00 00 00 00 00 00 00 0E 00 03 00
3B 02 D4 FE 01 00 1C 0C 08 00 1E 00 20 03 04 00 00 00 00 00 00 00 00 00 0C 00 00 00
3C 02 70 FE 02 00 18 15 0A 00 3C 00 B0 04 04 00 00 00 00 00 00 00 00 00 1A 00 04 00
3D 02 06 FF 02 00 34 08 03 00 E8 03 64 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00
3E 02 06 FF 02 00 68 10 09 00 14 00 F4 01 04 00 00 00 00 00 00 00 00 00 00 00 00 00
B2 02 64 00 02 00 98 08 0C 00 00 00 32 00 05 00 38 00 C8 00 00 00 00 00 00 00 00 00
B3 02 96 00 02 00 60 09 09 00 00 00 C8 00 04 00 38 00 FA 00 78 00 14 00 00 00 00 00
B4 02 FA 00 02 00 8C 0A 09 00 00 00 FA 00 04 00 30 00 2C 01 10 01 14 00 00 00 00 00
B5 02 F4 01 02 00 A0 0F 08 00 00 00 F4 01 03 00 30 00 F4 01 B0 00 28 00 00 00 00 00
B6 02 F4 01 02 00 CC 10 08 00 00 00 F4 01 03 00 20 00 F4 01 A0 00 28 00 00 00 00 00
B7 02 E8 03 02 00 C0 12 06 00 00 00 B0 04 02 00 18 00 D0 07 50 01 78 00 00 00 00 00
B8 02 78 05 02 00 88 13 06 00 00 00 B8 0B 01 00 18 00 A0 0F 08 02 8C 00 00 00 00 00
B9 02 20 03 02 00 80 0C 06 00 00 00 98 08 02 00 18 00 B8 0B 20 01 3C 00 00 00 00 00

= X-COM craft weapon data =

00 02 04 06 08 0A 0C 0E 10 Fire Intevals
.data:0046FB18 <240h, 1Eh, 46h, 46h, 1, 0Fh, 6, 1, 6 >; stingray .data:00473FB8 64, 48, 32 stingray
.data:0046FB2A <241h, 3Ch, 50h, 64h, 3, 14h, 3, 1, 7 >; avalanche 96, 72, 48 avalanche
.data:0046FB3C <242h, 0Ah, 19h, 0Ah, 8, 2, C8h, 64h, 8 >; cannon 4, 4, 4 cannon
.data:0046FB4E <243h, 41h, 64h, E6h, 5, 19h, 2, 1, 9 >; fusion ball 64, 48, 32 fusion ball
.data:0046FB60 <244h, 15h, 23h, 46h, 0A, 4, *0,*32h, 0 >; laser cannon 24, 24, 24 laser cannon
.data:0046FB72 <245h, 34h, 32h, 140, 0C, 6, *0,*32h, 0 >; plasma beam 24, 24, 24 plasma beam

00 Weapon_NameIdx
02 Range
04 CraftWepAccuracy ''chances=random(100)< Accuracy * (1+3/(5-ufosize))/2 => Accuracy * (0.8|0.875|1|1.25|2)''
06 CraftWepDamage ''damage=(WeaponDamage+random(WeaponDamage))/2 [50-100%]''
08 Weapon ID ''not used: bit0 = 1->weapon is missile. bit3 = 1-> weapon is direct fire.''
0A Reload time ''Value given for in-game ufopaedia fire rate. See table for correct fire rate''
0C ammunition max
0E Base rearm rate ''Amount added to the weapons ammo value in CRAFT.DAT every hour.''
10 Ammo_Ref ''reference to the proper entry in BASE.DAT to check for ammo. (0 = ray)''

* The code which rearms aircraft ignores these settings and always gives 100 units of ammo to beam weapons.

-- Fire intervals for different attack modes of craft weapon --

Attack modes in order: Cautious / Standard / Aggressive

Hex signature of all weapons:
40 02 1E 00 46 00 46 00 01 00 0F 00 06 00 01 00 06 00
41 02 3C 00 50 00 64 00 03 00 14 00 03 00 01 00 07 00
42 02 0A 00 19 00 0A 00 08 00 02 00 C8 00 64 00 08 00
43 02 41 00 64 00 E6 00 05 00 19 00 02 00 01 00 09 00
44 02 15 00 23 00 46 00 0A 00 04 00 00 00 32 00 00 00
45 02 34 00 32 00 8C 00 0C 00 06 00 00 00 32 00 00 00

== TFTD USO Stats ==

Here is a hex signature to help find the first alien sub record (Survey Ship):

b2 02 64 00 02 00 d0 07 0c 00 00 00 3c 00

In the Steam release of TFTD (a DOS version, modified by XcomUtil) this starts at offset 419072 decimal, 0x66500, in GEOSCAPE.EXE

TFTD appears to have the same 14 x 2-byte record structure, and the same or similar meaning, based on comparing a few records to the table in [[USOs]].

= HWP Stats =

At offset 380,668 the Tank Statistics begin.

= Armor Stats =

At offset 369,898 in the DOS version; the personal armor statistics begin.

The Statistics are in two byte format and go in the following order:

Front Armor 
Left Armor 
Right Armor 
Rear Armor 
Under Armor 

To help you find it in UGE, here are the various armor stats in UGE format:

Unarmored X-COM Personnel: 12 - 0 - 8 - 0 - 8 - 0 - 5 - 0 - 2 - 0 
Personal Armor: 50 - 0 - 40 - 0 - 40 - 0 - 30- 0 - 30 - 0 

So on, etc.

= Alien Stats =

This section is for the structure of the alien stats, as found in GEOSCAPE. For actual data and additional information, see the [[Alien_Stats|alien statistics]] page. Also see Zombie's excellent alien stats page at [http://www.strategycore.co.uk/xcom/pg/ufoalienstats StrategyCore].

Alien stats are found as 33 records of 39 bytes each, in all versions of X-COM. They are identical in all versions. This data actually represents the "core" alien stats; modifiers are used to determine the final stats relative to game difficulty level. (In most, but not all, cases, the core stats are the same as the Beginner level stats.)

Alien stats start in each version of X-COM at the following location. This is a byte ''count'', not an offset; with counts, the first byte in the file is byte 1:
Version Location
DOS 1.4 379,729 (GEOSCAPE.EXE)
WinCE Gold 480,145 (UFO Defense.exe)
Playstation 501,212
TFTD 486,930

Alien names are not actually found in Geoscape; it just has 33 strings of data... the alien each string applies to has been inferred by matching against aliens in the game.

The 39 bytes correspond to the following values. For the below, statements also apply to TFTD, since it's relevant to understanding the bytes:

'''0:''' Race - Corresponds to Unitref[000]

'''1:''' Rank - Corresponds to Unitref[042]

'''2:''' ''Unknown - Always 0'' - Corresponds to Unitref[011]

'''3:''' Can Fly - No Corresponding Unitref offset

'''4:''' TUs - Corresponds to Unitref[025]

'''5:''' Health - Corresponds to Unitref[026]

'''6:''' Energy - Corresponds to Unitref[027]

'''7:''' Reactions - Corresponds to Unitref[028]

'''8:''' Strength - Corresponds to Unitref[017]

'''9:''' Firing Accuracy - Corresponds to Unitref[023]

'''10:''' Throwing Accuracy - Corresponds to Unitref[024]

'''11:''' Melee Accuracy - Corresponds to Unitref[056]

'''12:''' Front Armor - Corresponds to Unitref[029]

'''13:''' Left Armor - Corresponds to Unitref[030]

'''14:''' Right Armor - Corresponds to Unitref[031]

'''15:''' Rear Armor - Corresponds to Unitref[032]

'''16:''' Under Armor - Corresponds to Unitref[033]

'''17:''' ''Unknown - Always 0'' - Corresponds to Unitref[034]

'''18:''' Energy Recharge - Corresponds to Unitref[035]

'''19:''' ''Unknown - Always 0'' - Corresponds to Unitref[036]

'''20:''' ''Unknown - Always 1'' No Corresponding Unitref offset

'''21:''' ''Unknown - Always 0'' - Corresponds to Unitref[046]

'''22:''' ''Unknown'' - Corresponds to Unitref[048] (see below)

'''23:''' ''Unknown'' - Corresponds to Unitref[052] (see below)

''NOTE: For additional important info on the last two bytes, see [[Talk:UNITREF.DAT]]. My notes below do not take that info into account. For the moment though I'm leaving it as is. I sure wish we could figure the bytes out, and get rid of all the conjecture! - [[User:MikeTheRed|MikeTheRed]] 08:05, 6 November 2006 (PST)''

These Unitref bytes ([48] and [52]) and now Geoscape Core values have long stumped us hardcore X-Commies. The two bytes always equal the same value for a given alien, including all aliens of the same race (the N's below). And, they're the same between Geoscape and Unitref. Clearly it must be important (or a goof!), but exactly what it is, who knows. Although this page is for X-COM, I've included TFTD in the hopes it helps folks - but it's been so long since I've played TFTD, I can't remember those units at all.

How's this for a thought?...
Dimension Byte(s)

X 22

Y 23

Z 24 (top when standing)
25 (top when kneeling)
26 (bottom)

Maybe they represent the "size in profile" ("width"), affecting likelihood to hit. A game could be tried with a target 20 squares away, set 22 and 23 alternately to 5 or 2 (or 1 or 0?), and see if it affects the successful shots percentage. 0 or even 1 might break the game, though.

Also, how do these values (2 to 5) correlate with the "pixel drawings" of units? I can't seem to find that info at the moment... aren't units and tiles defined as something like 16x16x[[Height|28]]? If so, then perhaps the values (2 to 5) are multiplied by 3 or something to get their final "width" for bullet interception?? --[[User:MikeTheRed|MikeTheRed]] 05:20, 17 September 2006 (PDT)

:I finally got the OSG (w00t!), and noticed the following: The section on weapon accuracy says (p. 221) that target size affects the chance to hit, and "the 'size' of each alien is listed along with all other alien statistics in Chapter 9". But the alien stats tables (p. 250 ff.) only lists Height as a possible 'size' stat, and the text write-ups don't otherwise address "target size" with any precision. This discrepancy - that Chapter 8 talks about '''size''', but Chapter 9 only has '''height''' - might (might!) mean there are more variables that determine target area size, but somehow they didn't make it to the alien stats tables.

:The description for Height (p. 249) does say, "Taller creatures are easier to hit than short ones are. An alien with a height of 40, for example, is twice as easy to hit as an alien with a height of 20." (Note: The tallest [[Height]] is actually 23. And also notice, Float is never mentioned.) This ''might'' mean only height affects this, or it could be read in a general way; other dimensions (X and Y in addition to Z) might also affect it.

:Somebody should do some firing accuracy tests while hacking these potential X & Y bytes! But I still don't know how the values for [22] & [23] compare to what X-COM considers tile width... we know the Height byte accurately reflects the full range of possible values (0 to 23), but I doubt 5 is the full (pixel?) width of a tile. This might mean it's not width, then (or maybe [22] & [23] are added, or they are individually multiplied by 3 or something??) If anyone who knows about tile width could say something, I'd appreciate it. --[[User:MikeTheRed|MikeTheRed]] 11:24, 1 October 2006 (PDT)

In any event, here's a summary of bytes [22] and [23], in the hopes we can figure it out. They're always identical for a given race, and [22] always equals [23].

'''X-COM TFTD'''

Value Alien N Value Alien N

2 Sectoid 6 2 Aquatoid 6
Bio-Drone 1
3 Celatid 1 Tentaculat 1
Chryssalid 1
Civilian 2 3 Calcinite 1
Ethereal 3 Civilian 2
Floater 6 Deep_One 1
Muton 3 Gill_Man 4
Snakeman 5 Tasoth 2

4 Cyberdisc 1 4 Coelacant 1
Hovertank 1 Displacer 1
Reaper 1 Hallucinoid 1
Sectopod 1 Lobster_Man 5
Tank 1 Triscene 1
Xarquid 1
5 Silacoid 1

'''24:''' Standing Height - Corresponds to Unitref[049]

'''25:''' Kneeling Height - Corresponds to Unitref[050]

'''26:''' Floating Height - Corresponds to Unitref[051]

'''27:''' [[Damage#Susceptible_to...|Damage Modifier]] Category - Corresponds to Unitref[055]

This field is simply a look-up table, or more directly, a way to categorize the units into similar groups. The actual modifiers are listed elsewhere in the executable. A value of 1 indicates the second DM category, a value of 4 indicates the 5th, etc. The values of 2 and 3 are not seen in the alien stats as they refer to X-COM soldier armor info. I'm not sure about 13 as the Zombie's stats haven't been found yet, but there is a category in the DM's for it.

'''Category''' '''Unit Type(s)'''
'''0''' Not for units, but is used for Terrain and Items
'''1''' Civilian, Sectoid, Celatid, Floater
'''2''' Personal Armor
'''3''' Power Suit, Flying Suit
'''4''' Tanks, Hovertanks
'''5''' Snakemen
'''6''' Ethereal
'''7''' Muton
'''8''' Silacoid
'''9''' Chryssalid
'''10''' Reaper
'''11''' Sectopod
'''12''' Cyberdisc
'''13''' Zombie

'''28:''' Psi Skill - Corresponds to Unitref[037]

'''29:''' Psi Strength - Corresponds to Unitref[057]

'''30:''' Bravery (encoded) - Corresponds to Unitref[059]

'''31:''' Motion scanner size - Corresponds to Unitref[061]

'''32:''' ''1 for Cyberdisc, 0 for all others including TFTD... isn't "Explodes"; the TFTD Bio-Drone also explodes...'' - Corresponds to Unitref[071]

I edited the Cyberdisc's field to 0 and checked to see if it exploded. It still did. Obviously this field is for something else. I'll work on this some more. --[[User:Zombie|Zombie]] 20:15, 15 September 2006 (PDT)

:I have a theory. I vaguely remember something about Cyberdiscs cannot be stunned. Even if you poke it with a Stun Rod and bypass it's self-destruct, it still counts as a kill. Maybe this has something to do with it (as I also remember that none of the other aliens exhibit this behavior)?--[[User:Amitakartok|amitakartok]] 12:55, 23 June 2009 (EDT)

::Good thinking. But the [[Stun]] page shows that Cyberdiscs can be stunned. Checking [[Unitref.Dat]] byte 71 (hex 0x47) shows that, after Zombie posted his statement, there's been a lot of on its [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page about this byte. -[[User:MikeTheRed|MikeTheRed]] 20:07, 2 July 2009 (EDT)

'''33:''' ''Unknown - Always 0'' No Corresponding Unitref offset

'''34:''' Corpse type - Corresponds to Unitref[038]

'''35:''' Big unit (2x2) No Corresponding Unitref offset

'''36:''' Victory point score - Corresponds to Unitref[039]

'''37:''' Aggression - Corresponds to Unitref[044]

'''38:''' Intelligence - Corresponds to Unitref[073]

''This data was just put together working heavily with Zombie and his great SC [http://www.strategycore.co.uk/xcom/pg/ufoalienstats alien stats] page.

= Country Labels =
Starting at offset 396480 (hex: 0x60CC0) are the records that contain the location of the labels for the country names on the world. In order they are X, Y, and English.dat index all signed short integers (6 bytes for each record). X should never be negative but between 0 and 2880, Y should be between -720 and 720 (See [[WORLD.DAT]]). The English.dat file, despite all other array indexes appears to start at 1 and not 0, thus a value of 611 in here represents index 610 in a zero based English.dat array. (It stands to reason that these work for the other language files as well)

= Detection Ranges =

Detection ranges are hard coded into the executable at the following locations (Win CE / Gold edition):

{| cellspacing="0" border="1"
!Platform
!Address
!Data bytes
!Hex
!Range
!nm
|-
|Aircraft||591EA||C8 00||x00C8||200||600
|-
|Hyperwave||59237||20 03||x0328||800||2400
|-
|Lg Radar||5926D||EE 02||x02EE||750||2250
|-
|Sm Radar||59278||F4 01||x01F4||500||1500
|}

Patching "88 13" to these locations = x1388 = 5000 range units = 15,000 nm pretty much gives that platform visibility over the whole world. Of course Small Radar still only has a 10% detection chance per half hour.

= Battlescape Terrain List =

In the UFO CE executable, offset 476156 (743FCx) marks the beginning of the [[WORLD.DAT]] terrain to battlescape terrain conversion list. 13 double byte values.

02 00 01 00 01 00 01 00 01 00 07 00 02 00 06 00 06 00 08 00 00 00 02 00 08 00

For example, a mission initiated in a GeoScape polygon of type 5 will be performed in battlescape terrain type 7 (mountains).

Note that jungle (type 00) missions in the north will end up as forest missions, and forest (type 02) missions in the south will end up as jungle missions. See offset 10 in [[GEODATA.DAT]] for the full battlescape terrain list.

= Manufacturing stats =

The original data for the product manufacturing information in [[PRODUCT.DAT]] is contained in the geoscape executable, at offset 355600 (for plain 1.4 version).
:And at 459720 in Steam's UFO Defense.exe. [[User:Off the Rails|Off the Rails]] 17:49, 2 February 2011 (EST)

= XCOM: UFO Defense DOS Versions, difficulty setting bug =
In the DOS versions of the game there was a problem when saving the [[IGLOB.DAT]] file, that would cut off the last four bytes. When the saved game was loaded or at the end of a mission, the game would then be set to beginner, never to return again. There is a single byte that can be adjusted to fix this problem, you change the value from 60 (0x3C) to 64 (0x40). Below are the offsets so you can fix them in your game. 
 
<table {{StdDescTable}}>
<tr>
<th {{StdDescTable_Heading}}>'''Offset dec (hex)'''</th><th {{StdDescTable_Heading}}>'''Game Version'''</th>
</tr>
<tr><td>97228 (0x17BCC)</td><td>DOS Version 1.0</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.2</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.3</td></tr>
<tr><td>95676 (0x175BC)</td><td>DOS Version 1.4</td></tr>
</table>
 
You can read more about the bug at the [[Known_Bugs#Difficulty_Bug|known bugs]] area.

= See Also =
* [[TACTICAL.EXE]] - Sister executable used for Turn based strategy (merged with geoscape.exe in WinCE edition)
* [[UNITREF.DAT]] - Stats on current units (both XCOM and Alien) in play
* [[Talk:GEOSCAPE.EXE]] - More offsets and investigations are on the Discussion page.
* [[Saved Game Files]]

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

Talk:Soldiers

2015-10-02T15:58:26Z

Morgan525: /* Missing in Action */

TODO: Insert links for other attributes and conditions used only in combat, such as "current reaction level", amongst other things that a player will want to know.

==Intro==
Ideas for opening blurb:

Welcome to the XCOM Personell Department. Here we maintain the records of extensive aptitude testing and training regimes.

From the sharpshooter with their rifle to the weakling with their smoke grenade, everyone on the assault team has a part to play.

XCOM is an Equal Opportunities Exploiter. Both men and women from any XCOM-funding country are welcome to apply.

-[[User:JellyfishGreen|JellyfishGreen]]

----

We make no distinctions regarding gender or ethnicity (neither do plasma beams). Regardless of how you look you will be turned into blondes the moment the transport lands? -[[User:Hobbes|Hobbes]] 06:12, 17 February 2006 (PST)

----

If your last name sounds English, French, German, Russian, or Japanese, please apply. If not, get lost. -[[User:MikeTheRed|MikeTheRed]]

== Managing squads ==

I'd suggest that all useful soldiers are renamed so you can identify them easily. It can even add a bit of fun. I also add a rating for their key stats by appending letters at the end, an R for 50 reactions or S for 35 strength, say. This lets me arm and move soldiers appropriately without knowing everything about them.

When picking a squad for a mission you probably need some expandable scouts, a leader, and some people to carry heavy weapons. It's useful if the front people in the skyranger are expendable as any accidents tend to happen to them. Once you've picked your scouts, hopefully before you've even set off, you should make sure that none of the other soldiers get shot during the mission. I would use low bravery soldiers as expendable scouts. You won't miss people who can go beserk at the first sign of trouble and intentional bravery training is typically an exploit. Soldiers can generally perform all roles except Psi offense, even if some are better skilled than others. - [[User:Egor|Egor]]

== Stats vs Attributes ==
I would call them stats, but a consensus would be nice. I'm pretty sure they mean the same thing. When it is decided, note it on the main talk page.

: I'd go with stats too, but there's no point splitting hairs. In the context they are used, they are interchangeable. - [[User:NKF|NKF]]

== Missing in Action ==

Soldiers that go MIA sometimes re-appear on alien UFO's or even alien bases. It's also mentioned in the briefing for UFO crash/landing sites. I haven't seen it anywhere mentioned on UFOPaedia yet though. Also mind crontrol seems to be a bit different then, as for the first few turns the soldier will automatically be on the aliens side and THEN start to regain control over their body. Does anyone know though if the same applies to TFTD? [[User:Zac x Me|Zac x Me]] ([[User talk:Zac x Me|talk]]) 00:55, 1 October 2015 (EDT)

:I have no idea what you are talking about, unfortunately. Though that may have something to do with the fact that I never let soldiers go MIA in the first place. Could you upload a screenshot of a briefing mentioning it? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 04:07, 2 October 2015 (EDT)

:: I can somewhat understand the second part as they would technically still be under the same state they were when the last mission ended. The first part however is a bit difficult to work out. I take it these missing soldiers will sometimes reappear on the mission immediately after the one where they went MIA? The only way I can possibly rationalize this is if the MIA soldier's slot did not get filled up at the time the next mission starts, so the game would have ghost data from the last mission. However this shouldn't happen, as the game would have compacted or filled in all the gaps by the time the new mission was generated. Do Do you recall any of the conditions that may lead up to this? Also was it in the Windows or Dos version of the game? I'd certainly like to try and replicate this. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 04:32, 2 October 2015 (EDT)

:I think he may be referring to the phrase in the UFO recovery mission briefing: "There may be operatives in the UFO or around the crash site." I've always taken that to mean operatives are the alien units. In the windows version, MIA or KIA soldiers have their entries in SOLDIER.DAT disabled as part of the post-battle routine. UNITREF and UNITPOS dat files have all entries disabled before new entries are created when the GEOSCAPE prepares for the next battle. -[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 11:58, 2 October 2015 (EDT)

User talk:NKF

2015-08-27T01:43:56Z

Morgan525: /* Sunken plane? */

= NKF:Talk =

Welcome to NKF Talk. Pardon the mess.

==The NKF-Centric TO-DO-List of Doom==

* "[[NKF's X-Com Apocalypse: Starter's Guide|X-Com Apocalypse Starter's Guide]]" - kind of there. Kind of not there. Perpetually.

== UFO Base Kit ==

The UBK is a transclusion template I created so that you could plug base layouts into your articles and discussions. Go see the template and its documentation at [[Template:UBK]] to see how to use it.

== Test of Gallery markup ==

<gallery>
File:Ufobadge.gif
File:Ufobadge.gif | Yes, this is a caption
File:TFTDBadge.gif
File:Ufobadge.gif
File:ApocBadge.gif
File:Ufobadge.gif
</gallery>

----
Now with adjustments

<gallery caption = "Icons" widths = "50" heights = "50" perrow = "3">
File:Ufobadge.gif
File:Ufobadge.gif | Oo-fow
File:TFTDBadge.gif | Tee-eff-tee-dee
File:Ufobadge.gif
File:Ufobadge.gif
File:ApocBadge.gif | Ah-pock
File:Ufobadge.gif | Yoo-eff-ow
File:TFTDBadge.gif | Tiftid
File:Ufobadge.gif
File:ApocBadge.gif | Ay-pock

</gallery>

Note to self: The new wiki software is really case sensitive these days! A good thing in one respect.

== Smoke Grenades ==

IMO they're only useful turn 1. And even that goes out the window if you have a tank. A tank is worth it in the early game, if only because it draws alien Plasma Pistol fire away from your squishy unarmoured dudes. Later on, though, when you have armour and the aliens switch to Heavy Plasma, tanks become less useful and you can bring out the Smoke Grenades. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 00:02, 22 August 2014 (EDT)

: Like the tank (or 4 rookies, for the budget conscious), the smoke grenade is just another tool at your disposal that you can use depending on how you like to play. The smoke grenade is certainly most useful for the initial deployment, but that's not so say that is the only time you can take advantage of it. I know I've had many occasions where I managed to save a bunch of soldiers that were stuck out in the open in full view of some aliens by throwing a smoke grenade between them. The [[Smoke Grenade]] page has some scenarios listed. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 03:26, 22 August 2014 (EDT)

::Four rookies die to four plasma pistol shots or one alien grenade. A tank can take either and keep trucking. It's also faster.

::I guess Smoke Grenades are okay if they're pre-primed and kept on the shoulder straps. Otherwise there's too big a TU cost to use opportunistically. Turn 1, on the other hand, you're not doing anything anyway because of all the full-TU aliens.

::At least we can agree that Dye Grenades are terrible! [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 05:59, 22 August 2014 (EDT)

:::I'd take the tank myself as it has plenty of merits, and the later Plasma Hovertank/Sonic Displacer are superb. However those that prefer 4 rookies do argue that they are cheaper, can spread out, carry more weaponry and still take the 4 (or more) shots to dispose of. Those that live through can go onto greater things. The tank just needs one bad roll of the die and it ends up a very expensive afterthought. Bit of a RTS peon pumper meat grinder mentality going on here methinks.

:::Grenades are in the same boat as the smoke grenade and do cost a lot to use. That's probably why they are best relegated to the support units that back up those on the front. Then again, front-line units carrying pre-armed grenades are handy for ninja-style retreats. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 16:21, 22 August 2014 (EDT)

Well, like I said, the main advantage of the tank is against aliens with Plasma Pistols at the very start of the game. A tank's front plate is guaranteed to survive at least 7 Plasma Pistol shots even if they all roll absolute max (which they won't), so you can park it on the opposite side of a UFO hatch to your firing line, close in, and draw fire from the aliens coming out until they use too many TUs and get reaction-fired to death (since on Superhuman, alien Reactions are usually high enough for them to avoid taking reaction-fire from stepping out of the hatch alone). In addition, you don't lose a huge amount of firepower by going with a tank right at the start since its cannon does twice the damage of Rifles. Once you've got lasers, the tank starts to hurt your firepower significantly, and once you've got decent armour and the aliens start using heavier weapons the defensive qualities of the tracked tanks go down the drain.

HWPs do have something of a renaissance later on when you get Avengers and are running into the 80-item limit, since a hovertank, while not reaching anywhere near the firepower of four Heavy-Plasma-equipped soldiers, does have more firepower than four soldiers without guns. Hovertanks/Launcher also don't count their ammo against said limit.

In TFTD it's a whole different kettle of fish thanks to the existence of Tentaculats and the lower fire rate of Sonic weaponry. Displacers/Sonic are absolutely essential due to their ability to lure Tentaculats - taking Artefact Sites without them is almost impossible thanks to That Goddamned Room. There's also the lower clip sizes making the 80-item limit an even bigger problem.

A pre-loaded Small Launcher does a lot of the same stuff a pre-armed Grenade does, and has the upside of taking the "suicide" out of "suicide bomb". There are a lot of ways to use those things. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 21:49, 22 August 2014 (EDT)

: Small Launchers are certainly quite handy beyond just capturing key aliens, and the Thermal Shok Launcher in TFTD is scary indeed. But they have their own share of drawbacks as well. Deciding which to use to get the best result for the task at hand is all part of the fun I guess. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 03:18, 25 August 2014 (EDT)

== Geocities site? ==

Hi. I suppose there's a good chance you might be the "nkfarma" who at one time had a page i found linked on the strategycore forums -- specifically http://www.geocities.com/nkfarma/temporary/lsc_lure.html . Did you ever manage to get those geocities pages moved to a different host? -- [[User:Jokes_Free4Me|Jokes_Free4Me]] ([[User_talk:Jokes_Free4Me|talk]]) 11:47, 9 April 2015 (EDT)

: The same. It has been a while, but I did manage to save some of the content. After reviewing it though, it was mostly trivial stuff. My most important work that was on the old Geocities page, the [[TRTBAG|TFTD Research Tree Bug Avoidance Guide]], survives in its current form on this wiki. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 02:53, 10 April 2015 (EDT)

:: Okay, i trust your judgement on this, even though my curiosity still makes me want to read through all that other "trivial stuff"...

:: As for the [[User_talk:Jokes_Free4Me#Rolling_back_NKF|revert issue]], your first paragraph about it is just as sensible as i presumed any admin would be. Contacting Spike just for this is not worthwhile IMO, since he's been inactive since August and this really is quite "trivial stuff" too. It's not too big a deal if the sections stays or goes... I reverted merely because i'm an [[wikipedia:Wikipedia:Inclusionism|inclusionist]] (as you might have guessed) and favour preserving all information, even if obsolete. As the saying goes, "Those who cannot remember the past are [more likely] to repeat it." -- [[User:Jokes_Free4Me|Jokes_Free4Me]] ([[User_talk:Jokes_Free4Me|talk]]) 07:25, 10 April 2015 (EDT)

:::The files I recovered were mostly the media files. Some .gif and .jpgs. Mainly game screenshots and a few fan-art scribbles I did on the back of some envelopes. Two zip files containing UFO save files, one being my "Solo Floater Base Assault Challenge" and one labelled scratch.zip. A no-base start file. I still use the challenge save on occasion to relearn how to play after long periods between games. There is a html file called The Deep One Dilemma - which was the basis for research tree bug avoidance guide. Also a grenade guide I had started but only ever got round to writing up the grenade relay. That's about it. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 23:15, 10 April 2015 (EDT)

==Pile of calcs==

So I did [[User:Magic9mushroom#TFTD_weapon_effectiveness_calculations|a thing]] and I think it's fairly important, but I'm not really sure where to put it or what to link to it. I'm thinking call it Weapon Effectiveness (TFTD) and stick a link to it in Weapon Analysis; is there anywhere else you think it should go? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 19:32, 27 April 2015 (EDT)

: I did give this some thought as you were compiling the data. It can certainly be included on the Weapon Analysis page. However, I'm also thinking that the information is quite relevant to TFTD so could also take a place on the main TFTD menu. For example, if you look at the UFO section's technical section under data tables, there's a [[Kill Modelling]] subheading that follows slightly similar lines. I am however starting to wonder if that fits the data table category. Perhaps a sub heading under Analysis might be best? [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 01:57, 28 April 2015 (EDT)

Well, the difference between this and all the data tables currently there is that this is a set of calculations rather than raw game data. And it's less like the weapon analyses we have than part of the framework on which they're based. I think I'll stick a "See also" in the TFTD section of [[Weapon Analysis]] and link it on the main TFTD menu. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 06:14, 28 April 2015 (EDT)

: Sorry, I was thinking aloud at the end there and forgot to put the context. I was wondering about where Kill Modelling fits in. Like your table, it's not raw game data as such. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 01:46, 29 April 2015 (EDT)

== VIGILO CONFIDO ==

You say on the main page that you found VIGILO CONFIDO hidden somewhere on the Advent page. I would appreciate you specifying where those words are hidden so people can check themselves. [[User:PizzaMan|PizzaMan]] ([[User talk:PizzaMan|talk]]) 04:17, 30 May 2015 (EDT)

: To be honest, I usually steer clear of promotional pre-hype until the games are finally out, so have been avoiding it. Hobbes, who added that item to the news, may know more about it. However I had a quick look anyway, and one of the links the site points to https://downloads.2kgames.com/adventfuture/images/en/ADVENT_LIES.html has part of the clue. It's just a bit of treasure hunt. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 04:50, 30 May 2015 (EDT)
: [http://i.imgur.com/ZaaiO3D.png] [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 19:19, 30 May 2015 (EDT)

==Sunken plane?==

I noticed you added a TFTD bug about "sunken plane missions". What in blazes is a "sunken plane mission", and why do they have different versions of their right wings? I have no clue what you're on about. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 06:58, 25 August 2015 (EDT)

: I'm referencing the mission where you are recovering or assaulting an alien sub while fighting around the wreck of a sunken cargo plane. If you haven't seen it before, try looking for it. It's quite neat. There are a couple different versions of its wings.

: See, when the Geoscape.exe portion of the game generates this map, it creates a 5x5 grid that forms the map outline. Each grid location is a 10x10 map chunk. Tactical.exe uses this outline to create the actual map you end up playing on.

: When populating the map outline, the game first marks off the area of the map where the X-Com sub and alien sub will go. Then it attempts to install the left and right wings of the plane into the map, followed by the various parts of the fuselage and finally fills in all the holes with random 10x10 map blocks in the terrain set.

: Each wing is a 20x20 map block. If it is not able to install the wing, say one of the subs is in the way, it will then try to use the small 10x10 version of the wing. If there is no space in the location it wants to place the small wing, then nothing is placed.

: The installation of the left wing of the plane works fine. However, when it gets around to installing the right wing and it fails to place the big wing and tries to place the small wing, instead of checking the exact destination to see if it the area is free, it checks the completely wrong part of the map. The block at 1,1 (which I have incorrectly stated as 0,1 in the article). This means that the small right wing could potentially overwrite anything that may be in that spot.

: Most of the time you probably will not even notice the difference even if the bug had occurred. But if the small right wing overwrote the landing area for your Triton for example, you'll start the map with odd bits of the wing around the Triton. Luckily the game places the Triton after the wing, otherwise I imagine you'd start the mission with floating Triton bits and your Aquanauts standing on the wing. At it is, it ends up looking like the Triton's forced its way into the wing.

:Again, players might not notice this as a bug, considering the chaos of debris around the map. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 02:07, 26 August 2015 (EDT)

Ah, now I get you. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 21:20, 26 August 2015 (EDT)

::Do you have a hex address where this error occurs? -[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 21:43, 26 August 2015 (EDT)

User talk:Warboy1982

2015-08-08T12:28:50Z

Morgan525:

I know that the forum profile link works fine for you, but in order to avoid more headscratching like "wtf? this is my profile!" when clicking it, you may want to use this one: http://openxcom.org/forum/index.php?action=profile;u=969

Warboy,
Does OpenXcom use the same coordinate system for the globe as the original game or did you all remap it in order to make navigation plotting easier? -[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 23:20, 6 August 2015 (EDT)

we converted them in most cases from xcom units into degrees, the in-game coordinate values are actually the same as the ones used on google maps, which makes it pretty easy to locate cities/etc. and add them in to the rulesets.--[[User:Warboy1982|Warboy1982]] ([[User talk:Warboy1982|talk]]) 05:32, 8 August 2015 (EDT)

:Thanks for the info. For a while, I was investigating the navigation code to eventually fix the Great Circle issue in the original game. I got a working formula but the output for the degrees of heading were never as expected. I looked at what formula OpenXCOM used but it seemed fundamentally the same, so I wondered if you all were using your own map data. -[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 08:28, 8 August 2015 (EDT)

Known Bugs (TFTD)

2015-08-07T07:53:58Z

Morgan525: /* Alien Glitches */

''Note: Since TFTD shares its game engine with X-Com Enemy Unknown, there are many problems that are common to both games. Please track any shared/common bugs under the XCOM-EU list of Known Bugs (link at the bottom of this page). This page is just for TFTD-Specific bugs. ''

= List of TFTD-Specific Bugs =
==Artifact Site Glitches==
There is a rarely occurring glitch when winning Artifact Sight missions by killing all aliens. Instead of a normal end screen,the screen will turn black and then resume on one of your soldiers, but with an unmovable cursor. Reloading saves may put you on the geoscape where the game can be played normally apart from when entering Artifact Sites, where you either cannot move your cursor in the equipment screen or the ending screen from the mission when the glitch occurred is shown but the cursor can't be moved. This means you must ignore all Artifact Site missions to continue the game, but as ignoring them results in an immediate -2000 point penalty, you will eventually lose due to being shut down or running out of funds.

== Research Tree bugs ==

See the [[TRTBAG|Research Bug Avoidance Guide]] for full discussion. *

==Alien Glitches==

* Aliens can't use carried melee weapons (Vibroblades and both types of Thermic Lances), even when they are equipped with them. (This is a game engine bug is present in UFO:EU as well, but it is not relevant to UFO:EU, since in UFO:EU aliens never get equipped with any carried melee weapons.) *
* The [[Bio-Drone]]'s melee attack almost always has no effect, even on unarmoured troops. ([[User:Zombie|Zombie]] has determined the weapon has a base accuracy of 0%, presumably a programming error). This is a serious flaw in the Bio-Drone, as it always uses this attack when Aquanauts are adjacent - especially given that one of the best ways to deal with Bio-Drones is by melee combat. *
* <s>The [[Hallucinoid]]'s ranged attack only works on land, but the Hallucinoid rarely/never appears on land. Presumably this is a programming error and was meant to be the other way round (only works underwater)</s>. The [[Hallucinoid]] is not given a ranged attack of any kind although the in-game description states that it has one. Its melee attack deals normal (lethal) damage although the in-game description says that it is icy, leading the player to believe that it should stun. ''This has been verified by several reliable sources. It does not appear on land unless the game code or data files have been modified.''
* The Deep One attack looks like the Celatid spit / mortar (holdover from UFO). *
* The Bio-Drone leaves a burning trail (holdover from the Silacoid in UFO?). *

== Mind Control Bugs==
*[[Large units#Large units in TFTD|Large units in TFTD]] suffer from even more bizarre behaviour than in UFO, due to an attempt to fix the old UFO bug.

== Craft Bugs==
*The floor maps & schematic pictures of the Survey Ship and Escort are swapped with each other in the Battlescape, the Interception window and the UFOPaedia. There is a (partial?) fix for this in [[XcomUtil]]. [[User:Zombie|Zombie]] has provided a [http://www.strategycore.co.uk/files/index.php?dlid=620 fix] that also fixes the routes as well as the maps.

*The schematic pictures of the Battle Ship and the Fleet Supply Cruiser are also swapped in the UFOPaedia and Intercept window. The floorplan maps on the Battlescape are not affected.
*Troop transports like the [[Triton]] can be blown up quite badly in land maps (rather than being invulnerable as it should be). This somehow doesn't prevent X-COM from flying back using it.
* '''TFTD V1.0''' There is a unit positioning bug when placing 26 men in a Leviathan. This bug is fixed by [[XcomUtil]] (and presumably in later versions of TFTD).

== X-COM Equipment Glitches ==
* Underwater-only weapons (HydroJet Cannon, Torpedo Launcher, and Disruptor Pulse Launcher, plus the Coelecanth/AquaJet & Displacer/PWT SWS weapons) are able to fire on land during XCOM's reaction-fire phase. This should not be allowed. *
* Coelacanth/Gauss Cannon ammo arming bug(s): The Coelacanth/Gauss does NOT return any remaining ammo to your stores at the end of a mission. In addition, when you assign a Coelacanth/Gauss to a troop transport, 50 Gauss Cannon rounds (used by both Craft and SWS Gauss Cannon) will be immediately deducted. These rounds cannot be refunded by any means. If you change your mind about assigning it, deassign it, and then reassign it, the premium will be deducted yet again from your stores. *

== Geoscape Bugs ==
* There is a really annoying "Cannot intercept over land" message that repeatedly pops up (often more than once a second) during some pursuits along coastlines. This is probably because the pursuing aircraft is moving rapidly from land areas to sea areas and back again as it flies along a coastline. *

* When intercepting an Alien Sub that is too deep for an XCom Flying Sub's operating depth, the Sub will report "Mission too deep" and return to base, rather than tracking the Alien Sub until such time as the Alien Sub rises to a depth at which the Sub can intercept. This forces you to take control of the Sub and get it to follow the Alien Sub manually, using Geoscape waypoints. *

* Alien Subs will sometimes Touch Down on land (e.g. several hundred nm south of the North African coastline). If you respond to these missions with an Assault, they are fought at Shallow depth rather than on land. Geoscape map/terrain data bug maybe? ''Even worse, assaulting these subs may cause your game to crash when it tries to start the battle.''

* [[Known Bugs#Manufacturing Rate Limit Bug (TFTD)|Manufacturing Rate Limit Bug/Quirk (TFTD)]] - The manufacturing windows allows you to assign more technicians than the limit allowed and provides a quicker estimated time to complete the project than actually occurs. *

* Craft Gauss Cannon rearm rate. The Craft Gauss Cannon reloads at only 10 rounds per hour. This compares to 99 or 100 rounds per hour for all other cannon weapons in TFTD and EU. This is believed to be a data entry bug when changing the reload rate of the Laser Cannon (99) for the TFTD equivalent Gauss Cannon. The result is that fully reloading a single Gauss Cannon takes 5+1= 6 hours and dual Gauss Cannon 5x2+1= 11 hours. This is slower rearming than any other weapon system apart from AJAX/Stingray (which itself probably represents a design oversight on its rearming rate). *

== Battlescape Bugs ==
* Strange MCD records (aka the 3d shapes that form the various walls and objects in the game). Due to some strange shapes, there are some locations with various line of sight errors and clipping errors such as a bullet hitting something in mid air when it shouldn't. There are even some cases where walking into a tile is much more tiring than it should be. This is not TFTD specific, but is much more apparent.

* On ship missions, there are some metal panels on walls. These tend to remain floating in the air even if the wall is destroyed. This is only a visual bug.

* Multi-stage mission bugs
**Strange effects occur to Aquanauts who were unconscious and/or under Molecular Control at the end of the previous stage of a multi-stage mission. These effects include: the Aquanauts becoming invisible, or becoming 'wraiths' in the next mission stage. (Does this also affect XCOM-EU, e.g. the 2-stage Cydonia mission?) *
** Any Captured aliens that are carried will die when they reach phase two. The actual working logic behind this is that since the new map is generated with a new set of enemies, the 'stats' that make up the stunned alien aren't retained, but only the physical object that represents the alien is carried over. This makes capturing aliens on the first part pointless unless you intend to abort the first part after physically hauling the stunned alien back to the transport.
** '''TFTD V1.0''' any equipment that is left on the ground on the first part of a two parter mission are not collected when you abort or complete the second part. This includes everything in the troop transport, which is lost forever. The V2.0 patch fixes this bug and returns everything on the first map.

* [[Dye Grenade]]s are to all intents and purposes, useless. Arguably not a bug, but it should not have survived basic playtesting. Weak weapons (eg [[Dart Gun]]) are one thing, but Dye Grenades are pointless because they never generate enough of a screen to block visibility. The best they would do is reduce alien visual range from 20 to 17. There would be a strong case to fix the strength of the Dye 'explosion' upward from 10 to 60 (like the [[Smoke Grenade]]) or at least 30-40. *
* Stunned Aquanaut bugs. (These might not be specific to TFTD, the situations are rare enough).
** In some cases, when moving a stunned body elsewhere, and it is subsequently killed by an explosion, the corpse may appear back at its original location. *
** Stunned Aquanauts in the Triton are not reported as either inside or outside the transport sub when you abort a terror mission. *
*** Stunned aquanauts that are carried by other aquanauts are listed as MIA if mission is aborted even if the carrier is aboard the Triton.
**It is possible to abort a mission even if all Aquanauts are stunned. Not sure if this should be possible?
**If the Triton is lost (aborting with no survivors), the stunned Aquanauts are shown as assigned to "Weapon-1", not their Triton, and they become inaccessible, basically lost/gone. *
** The animation for stunning a Civilian falling down shows them being violently killed.

* Zrbite spawns in locations unrelated to the Ion Accelerators. This is a result that the developers either 1) set the location of zrbite and later the ship maps were changed or 2) the developers confused the x and y coordinates in the database which specifies the specific location in the USO. ''In the game, Zrbite spawns when the alien items are created. Each Zrbite's OBPOS coordinates are established based on the USO position then reading the additional x, y, and z coordinates from a database, referenced to each USO.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 05:56, 3 April 2015 (EDT)

* In the CE version, clips that are loaded into weapons dropped on the battlefield will be given to the player at the time of an abort, even if the weapon in question was left on the battlefield. This is very apparent on USO recovery missions if the player immediately aborts when the battle starts and several aliens have died prior to the start of battle.*

==Manufacturing Rate Limit Bug(TFTD)*==

In UFO Enemy Unknown, the Manufacturing Rate Limit is just an irritant: The game prevents you from allocating more Engineers than the PRODUCT.DAT files says are needed to complete the item in one hour. This result in a minimum of one hour per item being necessary for the whole order. In an attempt to overcome this, the programmers eliminated this cap on the manufacture screen but failed to alter the code that actually determines what is produced every hour. Any extra technicians assigned over the number shown when you start an order produce nothing and their hours are wasted.

== Ufopedia Discrepancies ==

* [[Deep One]]s are portrayed carrying a weapon, in fact it appears to be carrying an X-com issue [[P.W.T. Cannon|P.W.T. Cannon]] craft weapon, instead of being unarmed other than its built in attack. *
* The [[Tasoth]] species is described as more resembling some sort of foot soldier in Ufopedia. It seems highly likely that the Tasoth were supposed to be one of the grunt races, and planning issues caused there to only be 4 main races in TFTD, making Tasoth the default Psionic (MC using) race.
* The [[Tentaculat]] description states that ([[Zombie]]s) cause death by touch even through armor. That's very wrong. The resulting zombies have a rather weak melee attack, especially compared to the Tentaculats. Also, the description says nothing about Zombies turning into Tentaculats upon death.
* The Ufopedia shows the damage of a [[Displacer/Sonic]] cannon as 130, but the coded value is 110. *
* See also the Craft Bugs where the map layout, interception picture and the Ufopedia picture are inconsistent with each other.
* The Ufopedia describes the [[Dart Gun]] as having a ten round magazine, when in fact it has a twelve round magazine.

== Questionable logic==
* Aquanauts and SWSs are unable to move vertically in water without the use of alien technology. Apparently no one has heard of ballast belts, propellers, or flippers.
** Actually, most of the aliens are unable to move vertically in water, despite most of them being aquatic creatures!
* Thrown objects behave underwater with identical physics as on land - impossible.
* Explosions behave underwater with identical physics as on land - impossible. (See [http://science.howstuffworks.com/explosion-land-water1.htm this link])
* Projectile weapons behave underwater with identical physics as on land - extremely unlikely.
* Vehicles behave the same underwater as in the air, fuel, acceleration, speed, etc. - impossible
* Alien "Molecular Control" is said to work via MC implants on the subject, but works on human Aquanauts (and civilians), regardless of whether the humans have MC implants. (They should've just called this Psionics like in Enemy Unknown.)
* X-com craft mounted Gas Cannon has an effective range of 8km. A gas reservoir capable of launching a solid bolt 8km underwater? - ridiculous.
* Underwater missions will at most take place in the light during the day and in the dark during the night. This is impossible. Sunlight won't penetrate deep in the water and most of the seabed is permanently dark.

== [[XcomUtil]] Bugs ==

These bugs relating to XComutil may be outdated.

* Gillmen are reported as Snakemen in some pop up messages, when using XcomUtil.

*Sometimes at the start of the 2nd level of a mission, all items, not loaded onto Aquanauts in the equip phase, appear to be lost. And some/all weapons have an ammo count of zero / no clips (possibly when the ammo was loaded automatically in the equip phase). (Believed to be related to XcomUtil teleporting 'spare' equipment back to base at the end of a level. See Talk page and [[Talk:XcomUtil#Open Bugs]])

==TFTD Extender ==
Items marked with an asterisk (*) have been fixed with the Extender.

= TFTD-Specific Exploits =

== Massively Profitable Alternate Craft Gauss Ammo ==

(Possibly should be defined as 'Light Modding' rather than an exploit, in the language of the Enemy Unknown [[Exploits]] pages.)

There is an alternate Craft Gauss Ammo type (in [[BASE.DAT (TFTD)]] at offset 0xD2). There appears to be no research path to unlock this ammo type. It looks like a late design decision was taken to have both the [[Coelacanth/Gauss]]'s cannon and the Craft [[Gauss Cannon]] use the same ammo type (in BASE.DAT (TFTD) at offset D0), unlocked by Gauss Cannon research, and unusually (uniquely?) without its own ammo Research topic. This is just as well, since the 0xD2 ammo type is incredibly expensive to manufacture and uses a huge amount of storage space. The production start cost is $10,000, and each unit uses 0.6 base storage. Perhaps this was intended to be a 50-round ammo pack, like the Craft [[Gas Cannon]] (and Enemy Unknown's [[Cannon]]), in which case the cost would not have been unreasonable.
Probably due to a typing / data entry error, the sell price of the 0xD2 ammo is set to $53,300, which is the sell price of Craft P.W.T. Ammo (and the Fusion Ball in Enemy Unknown). The extremely favourable spread between the build price and the sell price makes this item more than 5 times more profitable to manufacture than Gauss Cannon, far and away the most profitable item in the game.
If it is true that there is no Research path to unlock this 0xD2 ammo, then unlocking it requires game file manipulation, so this is arguably a Game File exploit, and of course if one is manipulating Game Files, it's easier just to hack ridiculously large amounts of money. For those who are not inclined to edit a binary file themselves, the XcomUtil TEC:ALL option will unlock this ammo type. Possibly XcomHack could also be used. The clear profit with two full Workshops is $22.866 million per month - after all expenses including Technician salaries.

= See Also =

*[[Known Bugs|Known Bugs (Enemy Unknown and generic)]]
*[[Exploits|Exploits (Enemy Unknown and generic)]]

[[Category: Oddities and bugs]]
[[Category:TFTD]]

Known Bugs (TFTD)

2015-08-07T07:51:41Z

Morgan525: /* Alien Glitches */ updated information on the Hallucinoid

''Note: Since TFTD shares its game engine with X-Com Enemy Unknown, there are many problems that are common to both games. Please track any shared/common bugs under the XCOM-EU list of Known Bugs (link at the bottom of this page). This page is just for TFTD-Specific bugs. ''

= List of TFTD-Specific Bugs =
==Artifact Site Glitches==
There is a rarely occurring glitch when winning Artifact Sight missions by killing all aliens. Instead of a normal end screen,the screen will turn black and then resume on one of your soldiers, but with an unmovable cursor. Reloading saves may put you on the geoscape where the game can be played normally apart from when entering Artifact Sites, where you either cannot move your cursor in the equipment screen or the ending screen from the mission when the glitch occurred is shown but the cursor can't be moved. This means you must ignore all Artifact Site missions to continue the game, but as ignoring them results in an immediate -2000 point penalty, you will eventually lose due to being shut down or running out of funds.

== Research Tree bugs ==

See the [[TRTBAG|Research Bug Avoidance Guide]] for full discussion. *

==Alien Glitches==

* Aliens can't use carried melee weapons (Vibroblades and both types of Thermic Lances), even when they are equipped with them. (This is a game engine bug is present in UFO:EU as well, but it is not relevant to UFO:EU, since in UFO:EU aliens never get equipped with any carried melee weapons.) *
* The [[Bio-Drone]]'s melee attack almost always has no effect, even on unarmoured troops. ([[User:Zombie|Zombie]] has determined the weapon has a base accuracy of 0%, presumably a programming error). This is a serious flaw in the Bio-Drone, as it always uses this attack when Aquanauts are adjacent - especially given that one of the best ways to deal with Bio-Drones is by melee combat. *
* <s>The [[Hallucinoid]]'s ranged attack only works on land, but the Hallucinoid rarely/never appears on land. Presumably this is a programming error and was meant to be the other way round (only works underwater)</s>. The [[Hallucinoid]] is not given a ranged attack of any kind although the in-game description states that it should have one. It has a melee attack but it deals normal, lethal damage even though its in-game description says that it is icy, leading the player to believe that it should be stun damage. ''This has been verified by several reliable sources and the unit does not appear on land unless the game code or data files have been modified.''
* The Deep One attack looks like the Celatid spit / mortar (holdover from UFO). *
* The Bio-Drone leaves a burning trail (holdover from the Silacoid in UFO?). *

== Mind Control Bugs==
*[[Large units#Large units in TFTD|Large units in TFTD]] suffer from even more bizarre behaviour than in UFO, due to an attempt to fix the old UFO bug.

== Craft Bugs==
*The floor maps & schematic pictures of the Survey Ship and Escort are swapped with each other in the Battlescape, the Interception window and the UFOPaedia. There is a (partial?) fix for this in [[XcomUtil]]. [[User:Zombie|Zombie]] has provided a [http://www.strategycore.co.uk/files/index.php?dlid=620 fix] that also fixes the routes as well as the maps.

*The schematic pictures of the Battle Ship and the Fleet Supply Cruiser are also swapped in the UFOPaedia and Intercept window. The floorplan maps on the Battlescape are not affected.
*Troop transports like the [[Triton]] can be blown up quite badly in land maps (rather than being invulnerable as it should be). This somehow doesn't prevent X-COM from flying back using it.
* '''TFTD V1.0''' There is a unit positioning bug when placing 26 men in a Leviathan. This bug is fixed by [[XcomUtil]] (and presumably in later versions of TFTD).

== X-COM Equipment Glitches ==
* Underwater-only weapons (HydroJet Cannon, Torpedo Launcher, and Disruptor Pulse Launcher, plus the Coelecanth/AquaJet & Displacer/PWT SWS weapons) are able to fire on land during XCOM's reaction-fire phase. This should not be allowed. *
* Coelacanth/Gauss Cannon ammo arming bug(s): The Coelacanth/Gauss does NOT return any remaining ammo to your stores at the end of a mission. In addition, when you assign a Coelacanth/Gauss to a troop transport, 50 Gauss Cannon rounds (used by both Craft and SWS Gauss Cannon) will be immediately deducted. These rounds cannot be refunded by any means. If you change your mind about assigning it, deassign it, and then reassign it, the premium will be deducted yet again from your stores. *

== Geoscape Bugs ==
* There is a really annoying "Cannot intercept over land" message that repeatedly pops up (often more than once a second) during some pursuits along coastlines. This is probably because the pursuing aircraft is moving rapidly from land areas to sea areas and back again as it flies along a coastline. *

* When intercepting an Alien Sub that is too deep for an XCom Flying Sub's operating depth, the Sub will report "Mission too deep" and return to base, rather than tracking the Alien Sub until such time as the Alien Sub rises to a depth at which the Sub can intercept. This forces you to take control of the Sub and get it to follow the Alien Sub manually, using Geoscape waypoints. *

* Alien Subs will sometimes Touch Down on land (e.g. several hundred nm south of the North African coastline). If you respond to these missions with an Assault, they are fought at Shallow depth rather than on land. Geoscape map/terrain data bug maybe? ''Even worse, assaulting these subs may cause your game to crash when it tries to start the battle.''

* [[Known Bugs#Manufacturing Rate Limit Bug (TFTD)|Manufacturing Rate Limit Bug/Quirk (TFTD)]] - The manufacturing windows allows you to assign more technicians than the limit allowed and provides a quicker estimated time to complete the project than actually occurs. *

* Craft Gauss Cannon rearm rate. The Craft Gauss Cannon reloads at only 10 rounds per hour. This compares to 99 or 100 rounds per hour for all other cannon weapons in TFTD and EU. This is believed to be a data entry bug when changing the reload rate of the Laser Cannon (99) for the TFTD equivalent Gauss Cannon. The result is that fully reloading a single Gauss Cannon takes 5+1= 6 hours and dual Gauss Cannon 5x2+1= 11 hours. This is slower rearming than any other weapon system apart from AJAX/Stingray (which itself probably represents a design oversight on its rearming rate). *

== Battlescape Bugs ==
* Strange MCD records (aka the 3d shapes that form the various walls and objects in the game). Due to some strange shapes, there are some locations with various line of sight errors and clipping errors such as a bullet hitting something in mid air when it shouldn't. There are even some cases where walking into a tile is much more tiring than it should be. This is not TFTD specific, but is much more apparent.

* On ship missions, there are some metal panels on walls. These tend to remain floating in the air even if the wall is destroyed. This is only a visual bug.

* Multi-stage mission bugs
**Strange effects occur to Aquanauts who were unconscious and/or under Molecular Control at the end of the previous stage of a multi-stage mission. These effects include: the Aquanauts becoming invisible, or becoming 'wraiths' in the next mission stage. (Does this also affect XCOM-EU, e.g. the 2-stage Cydonia mission?) *
** Any Captured aliens that are carried will die when they reach phase two. The actual working logic behind this is that since the new map is generated with a new set of enemies, the 'stats' that make up the stunned alien aren't retained, but only the physical object that represents the alien is carried over. This makes capturing aliens on the first part pointless unless you intend to abort the first part after physically hauling the stunned alien back to the transport.
** '''TFTD V1.0''' any equipment that is left on the ground on the first part of a two parter mission are not collected when you abort or complete the second part. This includes everything in the troop transport, which is lost forever. The V2.0 patch fixes this bug and returns everything on the first map.

* [[Dye Grenade]]s are to all intents and purposes, useless. Arguably not a bug, but it should not have survived basic playtesting. Weak weapons (eg [[Dart Gun]]) are one thing, but Dye Grenades are pointless because they never generate enough of a screen to block visibility. The best they would do is reduce alien visual range from 20 to 17. There would be a strong case to fix the strength of the Dye 'explosion' upward from 10 to 60 (like the [[Smoke Grenade]]) or at least 30-40. *
* Stunned Aquanaut bugs. (These might not be specific to TFTD, the situations are rare enough).
** In some cases, when moving a stunned body elsewhere, and it is subsequently killed by an explosion, the corpse may appear back at its original location. *
** Stunned Aquanauts in the Triton are not reported as either inside or outside the transport sub when you abort a terror mission. *
*** Stunned aquanauts that are carried by other aquanauts are listed as MIA if mission is aborted even if the carrier is aboard the Triton.
**It is possible to abort a mission even if all Aquanauts are stunned. Not sure if this should be possible?
**If the Triton is lost (aborting with no survivors), the stunned Aquanauts are shown as assigned to "Weapon-1", not their Triton, and they become inaccessible, basically lost/gone. *
** The animation for stunning a Civilian falling down shows them being violently killed.

* Zrbite spawns in locations unrelated to the Ion Accelerators. This is a result that the developers either 1) set the location of zrbite and later the ship maps were changed or 2) the developers confused the x and y coordinates in the database which specifies the specific location in the USO. ''In the game, Zrbite spawns when the alien items are created. Each Zrbite's OBPOS coordinates are established based on the USO position then reading the additional x, y, and z coordinates from a database, referenced to each USO.''-[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 05:56, 3 April 2015 (EDT)

* In the CE version, clips that are loaded into weapons dropped on the battlefield will be given to the player at the time of an abort, even if the weapon in question was left on the battlefield. This is very apparent on USO recovery missions if the player immediately aborts when the battle starts and several aliens have died prior to the start of battle.*

==Manufacturing Rate Limit Bug(TFTD)*==

In UFO Enemy Unknown, the Manufacturing Rate Limit is just an irritant: The game prevents you from allocating more Engineers than the PRODUCT.DAT files says are needed to complete the item in one hour. This result in a minimum of one hour per item being necessary for the whole order. In an attempt to overcome this, the programmers eliminated this cap on the manufacture screen but failed to alter the code that actually determines what is produced every hour. Any extra technicians assigned over the number shown when you start an order produce nothing and their hours are wasted.

== Ufopedia Discrepancies ==

* [[Deep One]]s are portrayed carrying a weapon, in fact it appears to be carrying an X-com issue [[P.W.T. Cannon|P.W.T. Cannon]] craft weapon, instead of being unarmed other than its built in attack. *
* The [[Tasoth]] species is described as more resembling some sort of foot soldier in Ufopedia. It seems highly likely that the Tasoth were supposed to be one of the grunt races, and planning issues caused there to only be 4 main races in TFTD, making Tasoth the default Psionic (MC using) race.
* The [[Tentaculat]] description states that ([[Zombie]]s) cause death by touch even through armor. That's very wrong. The resulting zombies have a rather weak melee attack, especially compared to the Tentaculats. Also, the description says nothing about Zombies turning into Tentaculats upon death.
* The Ufopedia shows the damage of a [[Displacer/Sonic]] cannon as 130, but the coded value is 110. *
* See also the Craft Bugs where the map layout, interception picture and the Ufopedia picture are inconsistent with each other.
* The Ufopedia describes the [[Dart Gun]] as having a ten round magazine, when in fact it has a twelve round magazine.

== Questionable logic==
* Aquanauts and SWSs are unable to move vertically in water without the use of alien technology. Apparently no one has heard of ballast belts, propellers, or flippers.
** Actually, most of the aliens are unable to move vertically in water, despite most of them being aquatic creatures!
* Thrown objects behave underwater with identical physics as on land - impossible.
* Explosions behave underwater with identical physics as on land - impossible. (See [http://science.howstuffworks.com/explosion-land-water1.htm this link])
* Projectile weapons behave underwater with identical physics as on land - extremely unlikely.
* Vehicles behave the same underwater as in the air, fuel, acceleration, speed, etc. - impossible
* Alien "Molecular Control" is said to work via MC implants on the subject, but works on human Aquanauts (and civilians), regardless of whether the humans have MC implants. (They should've just called this Psionics like in Enemy Unknown.)
* X-com craft mounted Gas Cannon has an effective range of 8km. A gas reservoir capable of launching a solid bolt 8km underwater? - ridiculous.
* Underwater missions will at most take place in the light during the day and in the dark during the night. This is impossible. Sunlight won't penetrate deep in the water and most of the seabed is permanently dark.

== [[XcomUtil]] Bugs ==

These bugs relating to XComutil may be outdated.

* Gillmen are reported as Snakemen in some pop up messages, when using XcomUtil.

*Sometimes at the start of the 2nd level of a mission, all items, not loaded onto Aquanauts in the equip phase, appear to be lost. And some/all weapons have an ammo count of zero / no clips (possibly when the ammo was loaded automatically in the equip phase). (Believed to be related to XcomUtil teleporting 'spare' equipment back to base at the end of a level. See Talk page and [[Talk:XcomUtil#Open Bugs]])

==TFTD Extender ==
Items marked with an asterisk (*) have been fixed with the Extender.

= TFTD-Specific Exploits =

== Massively Profitable Alternate Craft Gauss Ammo ==

(Possibly should be defined as 'Light Modding' rather than an exploit, in the language of the Enemy Unknown [[Exploits]] pages.)

There is an alternate Craft Gauss Ammo type (in [[BASE.DAT (TFTD)]] at offset 0xD2). There appears to be no research path to unlock this ammo type. It looks like a late design decision was taken to have both the [[Coelacanth/Gauss]]'s cannon and the Craft [[Gauss Cannon]] use the same ammo type (in BASE.DAT (TFTD) at offset D0), unlocked by Gauss Cannon research, and unusually (uniquely?) without its own ammo Research topic. This is just as well, since the 0xD2 ammo type is incredibly expensive to manufacture and uses a huge amount of storage space. The production start cost is $10,000, and each unit uses 0.6 base storage. Perhaps this was intended to be a 50-round ammo pack, like the Craft [[Gas Cannon]] (and Enemy Unknown's [[Cannon]]), in which case the cost would not have been unreasonable.
Probably due to a typing / data entry error, the sell price of the 0xD2 ammo is set to $53,300, which is the sell price of Craft P.W.T. Ammo (and the Fusion Ball in Enemy Unknown). The extremely favourable spread between the build price and the sell price makes this item more than 5 times more profitable to manufacture than Gauss Cannon, far and away the most profitable item in the game.
If it is true that there is no Research path to unlock this 0xD2 ammo, then unlocking it requires game file manipulation, so this is arguably a Game File exploit, and of course if one is manipulating Game Files, it's easier just to hack ridiculously large amounts of money. For those who are not inclined to edit a binary file themselves, the XcomUtil TEC:ALL option will unlock this ammo type. Possibly XcomHack could also be used. The clear profit with two full Workshops is $22.866 million per month - after all expenses including Technician salaries.

= See Also =

*[[Known Bugs|Known Bugs (Enemy Unknown and generic)]]
*[[Exploits|Exploits (Enemy Unknown and generic)]]

[[Category: Oddities and bugs]]
[[Category:TFTD]]

Overviews of Aliens (TFTD)

2015-08-07T07:16:37Z

Morgan525: /* Hallucinoid - Terror Unit */ Removed all misinformation about its range attack. It cannot appear on land unless game code or data is manipulated.

All aliens are not, of course, equal. While a novice may be overwhelmed at any manifestation of Alien presence, he will soon learn to cope, and discern the abilities of his enemy. For those who aren't yet well-versed in such things, here's a rundown on how mean each of these creatures can be in a fight. For more details, look at aliens' specific pages or [[Alien Stats (TFTD)|the stats page]].

==Low Threat==
===Gill Man - Armed Combatant===
[[Image:Gillman.png|How does I betray planet?]]

These guys are the worst. Not only are they bad soldiers but they're pathetic traitors to boot.

They have marginally better health and armour than the [[Aquatoid]]s (though worse at actually shooting) but have no M.C. ability whatsoever with the sole exception of the [[Commander]] rank, who isn't especially good at it anyway.

Gillmen have no redeeming features whatsoever from a military standpoint, and we can only assume the aliens use them as cannon fodder by testament of their frequent appearance on the battlefield.

They have all ranks except for the Medic and Navigator.

Methods of Disposal: Pretty much anything. Note however that Hydro-Jet Cannons, Gauss Pistols and especially Jet Harpoons will usually not kill them in one hit.

You will need to have examined a dead Gillman in order to unlock the [[Thermic Lance]]. Their [[#Deep One - Terror Unit|associates]] are perhaps of more interest.
 
See also: [[Gillman]] | [[Overviews of Aliens (TFTD)#Xarquid - Terror Unit|Medium Threat: Xarquid - Terror Unit]] | [[Overviews of Aliens (TFTD)#Deep One - Terror Unit|Medium Threat: Deep One - Terror Unit]]

===Calcinite - Terror Unit===
[[Image:Calc.PNG|I am a civilian you cannot see me, oh wait...]]

Melee only units with powerful claws. These guys can take a bit of a beating due to their high level of health and are pretty fast, but they don't have any special resistance to any weapons so sustained fire of any kind will drop them. Eventually.

Calcinites have no ranks and are found in the company of [[Aquatoid]]s and [[Mixed Crew]] on land missions.

Methods of Disposal: Gauss or Sonic preferred, but Explosives and [[Gas Cannon]]s can be useful.

A dead Calcinite is required to unlock all the melee weapons, starting with the [[Vibroblade]].

 
See also: [[Calcinite]] | [[Overviews of Aliens (TFTD)#Aquatoid - Armed Combatant |Medium Threat: Aquatoid - Armed Combatant]]

===[[Hallucinoid]] - Terror Unit===
[[Image:Hallucinoid.png|Jelly baby!]]

The Hallucinoid is a large floating terror unit that primarily attacks with a lethal "cold-based" melee attack. It is supposed to have a ranged attack, but due to a [[Known Bugs (TFTD)|bug]], it does not.

Hallucinoids have no ranks and are found in the company of [[Aquatoid]]s and [[Mixed Crew]] on underwater missions.

Notes: Its "cold-based" melee attack does normal damage rather than Stun damage.

Methods of Disposal: Explosives are recommended due to the increased damage dealt to large size. For non-explosive attacks, the higher the damage the better. Low damage weapons don't have sufficient power to breach the moderately heavy armor. Phosphor is claimed to be effective, but in reality, even given their increased susceptibility, incendiary damage is likely too weak to kill Hallucinoids. This may be more a reference to the use of the unusual [[incendiary]] damage exploit.

Hallucinoids are able to alter their depth (i.e. "fly"). This can make it harder to hit them thrown explosives or melee weapons. On the other hand, it makes misses with ranged area-effect rounds much safer.

 
See also: [[Hallucinoid]] | [[Overviews of Aliens (TFTD)#Aquatoid - Armed Combatant |Medium Threat: Aquatoid - Armed Combatant]]

===Zombie - Fallen Aquanaut===

[[File:TFTD ZOMBIE24.PNG|200px]]

The unfortunate result of human entanglement with a [[Tentaculat]].

Zombies are slow and armed only with a (strong) melee attack. This makes them easy to evade, run away from and kill. They are completely immune to stun weapons and leave a nasty surprise for you upon their death: A newly emerged Tentaculat with full TUs and a hunger for tasty X-COM flesh. Note that this will be a Tentaculat at base stat levels that have not been adjusted by difficulty level. This is a reprieve on Superhuman difficulty, but a curse on Beginner difficulty.

Zombies have no ranks and can only be found where there are already Tentaculats which (thankfully) means at least you don't have to worry about [[Civilian]]s feeding these things.

Methods of disposal: Ranged weapons preferred over melee weapons due to the danger of being too close, though melee weapons are probably the most effective if you are willing to risk being next to a dead Zombie when the Tentaculat emerges. HE is good, Sonic and Gauss are fine, AP is weak. Just as long as you can take care of the resulting Tentaculat 'surprise' as well; if you can't, flee and let the zombie waddle after you (it's safer!). If all else fails, try to strike the killing blow with a phosphorous attack. This prevents the embryo from hatching.

There is no in-game UFOPedia entry for this creature, as they can not be stunned, captured or researched - not even corpses can be recovered. The grainy image above is from XCom tactical video footage.

==Medium Threat==
===Aquatoid - Armed Combatant===
[[Image:Aquatoid.png|Beware: Aquatards!]]

Distant relations to the [[Sectoid]]s, these guys have much the same strengths and weaknesses.

They make at best average soldiers having pitifully low health, so why are they 'medium threat' you ask? Aquatoid Technicians, Navigators and Commanders have [[Molecular Control]] abilities, and the higher ranks can be pretty good at it (the Commander has the most powerful MC you'll ever face).

Aquatoids can be of any rank (they are the only race to have Medics).

Methods of Disposal: Anything, Staring, Harsh Language - they really are that weak.

 
See also: [[Aquatoid]] | [[Overviews of Aliens (TFTD)#Hallucinoid - Terror Unit|Low Threat: Hallucinoid - Terror Unit]] | [[Overviews of Aliens (TFTD)#Calcinite - Terror Unit|Low Threat: Calcinite - Terror Unit]]

===Deep One - Terror Unit===
[[Image:DeepOne.png|Cthulu says: Die plz.]]

Probably the biggest mistake the aliens made was creating the Deep One as they are the basis from which X-COM goes about unlocking the most important secrets: Armour and Advanced craft.

Although they're pretty resistant to the basic 'bought' weapons, they're simply fodder for anything else. While the in-game illustration shows them holding something that looks like a PWT cannon, they are actually armed with what appears to be an electrical mortar of some kind which is unaffected by armour and does not require a direct line-of-sight to its target, thankfully it is woefully inaccurate. This weapon is geared towards dealing maximum damage to human foes, and does less damage to other aliens. Note that this weapon cannot be recovered by X-com.

Deep Ones have no ranks and are found in the company of [[Gillman|Gillmen]] and some [[Mixed Crew]] on land missions. They can be found in water during the second and third levels of T'leth, as well as on one type of Mixed Crew Dreadnaught.

Methods of Disposal: Pretty much anything really.

It cannot be overstated how vitally important these creatures are to your research, you will require dead examples to unlock research into [[Aqua Plastics]] and [[Plastic Aqua Armor|Plastic Aqua Armour]], and '''afterwards''' live specimens to unlock [[Ion Armor|Ion Armour]], advanced Submarines and advanced [[SWS]] models.

 
See also: [[Deep One]] | [[Overviews of Aliens (TFTD)#Gill Man - Armed Combatant|Low Threat: Gill Man - Armed Combatant]]

===Xarquid - Terror Unit===
[[Image:Xarquid.png|Japanese Delicacy]]

Probably the rarest of all the TFTD units. They resemble a giant nautilus that move backwards, with their tentacles facing the front.

They have fairly decent stats they don't seem to move around much, preferring instead to 'camp' a particular location and use their good reflexes to tag intruders with their particle cannon, which seems to be roughly equivalent to the [[SWS]] [[Gauss Cannon]] making it fairly decent at cracking X-COM armour.

Amongst the aliens, the Xarquid feature some of the higher end external armour, making low powered weapons ineffective. Being a 2x2 unit it is however very vulnerable to explosives or stun damage.

Xarquids are found in the company of [[Gillman|Gillmen]] and some [[Mixed Crew]]s on underwater missions.

Methods of Disposal: Explosives, [[Weapons_(TFTD)#Armor-Piercing|Armor-Piercing]] weapons (especially mid to high powered drills).

 
See also: [[Xarquid]] | [[Overviews of Aliens (TFTD)#Gill Man - Armed Combatant|Low Threat: Gill Man - Armed Combatant]]

===Triscene - Terror Unit===
[[Image:Triscene.png|Jurassic Farce]]

Another pretty rare unit, the Triscene is on first appearances a formidable foe with its twin [[Sonic Cannon]]s and melee attack along with lots of [[Time Units]] and health. Note that the side cannons on it do resemble the X-COM Craft PWT cannons - but are only for show.

While a dangerous foe, its biggest weakness is its non-existent underside armour which means it can be even be felled with a [[Magna-Blast Grenade]].

Triscene have no ranks and are found in the company of Tasoths and some Mixed Crews on land missions.

Methods of Disposal: Explosives.

 
See also: [[Triscene]] | [[Overviews of Aliens (TFTD)#Tasoth - Armed Combatant|High Threat: Tasoth - Armed Combatant]]

==High Threat==
===Lobster Man - Armed Combatant===
[[Image:Lobsterman.png|Foe or Food?]]

These orange instruments of doom are the [[Muton]] of TFTD. Big and tough, but not really the sharpest knife in the alien drawer. Despite this they are very flexible opponents as they can fight with standard weapons or their built-in claw attacks, which can give even the most well protected aquanaut a major pounding.

They lack external armour, but have insanely formidable resistances that allow them to shrug off between 50% and 80% (!) of most damage types. Combined with plenty of health, this allows them to sustain unreal amounts of damage before dropping dead. Thankfully this is balanced by Lobstermen taking more damage from stun or drill type weapons.

Lobster Men have all ranks except for Medic, and none of them have any M.C. ability at all.

Methods of Disposal: Thermal Shok Bombs (or Tazers if you're feeling brave), drills, lots of explosives, Sonic weapons and lots of clips.

A live Lobster Man Commander is required to research the [[Leviathan]] Assault Sub and "T'Leth, the Alien's City", both of which are required to finish the game. Earlier versions of the game required a Lobsterman Navigator for Magnetic Navigation.

 
See also: [[Lobsterman]] | [[Overviews of Aliens (TFTD)#Tentaculat - Terror Unit|High Threat: Tentaculat - Terror Unit]] | [[Overviews of Aliens (TFTD)#Bio Drone - Terror Unit|High Threat: Bio Drone - Terror Unit]]

===Tasoth - Armed Combatant===
[[Image:Tasoth.png|Rag-dolly-lizard, all liquid inside...]]

Fast and agile, these guys can be quite a nuisance as they have plenty of TUs to run around and lots of health to soak up damage, although they don't really have any special resistance to any weaponry.

Tasoth come in two flavours: Soldier and Squad Leader. Both ranks are more or less the same except for the leaders having slightly better stats. and more importantly [[Molecular Control]] ability.

Methods of Disposal: Sonic weapons are preferred, but ''strong'' explosives and melee weapons will also do the trick. Gauss weapons can work in an emergency, but bring lots of ammo (4-5 Rifle hits are required per Tasoth).

A live Tasoth of either rank is required to research the [[M.C. Disruptor]].

 
See also: [[Tasoth]] | [[Overviews of Aliens (TFTD)#Triscene - Terror Unit|Medium Threat: Triscene - Terror Unit]] | [[Overviews of Aliens (TFTD)#Bio Drone - Terror Unit|High Threat: Bio Drone - Terror Unit]] | [[Overviews of Aliens (TFTD)#Tentaculat - Terror Unit|High Threat: Tentaculat - Terror Unit]]

===Bio Drone - Terror Unit===
[[Image:BioDrone.png|Screaming you to death since 2045.]]

Like miniature [[Cyberdisc]]s with high TUs, very high health, and a sonic weapon with the best accuracy in the game.

These things are a menace that can not only cut your men down in their own turn, but take a considerable amount of punishment before falling, and when they do fall they explode.

There are however three quirks of this beast to take advantage of:
* Firstly they don't self-destruct if they are killed by melee weapons (this includes the [[Thermal Tazer]]).
*Second, they have a secondary melee attack which they prefer to use in close quarters - but it is INCREDIBLY inaccurate (0%, probably a bug), so if you stand next to it you probably will survive.
*And last, they leave a trail wherever they go. If you see a burned path in the ground, you can often guess their locations. This is even more effective for parts of the map that have already been sighted, as you'll be able to visually see the burnt path being created after each turn.

Bio Drones are found on [[Lobsterman|Lobstermen]], [[Tasoth]] and [[Mixed Crew]] land missions.

Methods of Disposal: Gauss, Sonic and Explosives from as far away as possible; or Melee as close as possible.

 
See also: [[Bio-Drone]] | [[Overviews of Aliens (TFTD)#Tasoth - Armed Combatant|High Threat: Tasoth - Armed Combatant]] | [[Overviews of Aliens (TFTD)#Lobster Man - Armed Combatant|High Threat: Lobster Man - Armed Combatant]]

===Tentaculat - Terror Unit===
[[Image:Tentaculat.PNG|Death From Above!]]

Tentaculats are very similar to a [[Chryssalid]]. These big brain creatures have the same ability to proliferate by ''zombify''ing their targets into mindless walking incubators for their young. They are only found in water and are generally found guarding Dreadnaughts, Battleships or alien structures. Tentaculats are able to raise or lower their elevation in the water with impunity. In short: Underwater flying [[Chryssalid]]s. The one saving grace is that no civilians are ever encountered on the same map as tentaculats.

Tentacults have a high distribution of front armour, but their rear and sides are weaker. If encountered early with weaker weapons, try to hit them from the flanks or rear as much as you can. Liberal use of explosives generally does the trick.

Tentaculats have no ranks and are found on [[Lobsterman]], [[Tasoth]] or [[Mixed Crew]] underwater missions.

Methods of Disposal : Sonic weapons, explosives and a healthy dose of luck.

 
See Also [[Chryssalid]] | [[Zombie]] | [[Tentaculat]] | [[Overviews of Aliens (TFTD)#Lobster Man - Armed Combatant|High Threat: Lobster Man - Armed Combatant]] | [[Overviews of Aliens (TFTD)#Tasoth - Armed Combatant|High Threat: Tasoth - Armed Combatant]]

==See Also==
*[[Alien Stats (TFTD)]]
*[[Damage Modifiers (TFTD)]]
*[[Overviews of Aliens|Overviews of Aliens (UFO Defense)]]

[[Category:TFTD]]

Talk:Hallucinoid

2015-08-07T06:22:13Z