UFOpaedia - User contributions [en]

OBDATA.DAT

2008-03-19T19:13:09Z

Sirgalahadwizard: /* Structure */

'''OBDATA.DAT''' is found in GEODATA and contains general information on objects found in the game, such as their accuracy and weight. It also contains template information regarding clip size; to hack dynamic [[Battlescape]] info on the number of rounds left in a particular item in play (or it's location etc), see [[OBPOS.DAT]].

There are 80 records, each of which are 54 bytes long (a total of 4,320 bytes).

There are 33 entries for corpses (or otherwise destroyed robots and vehicles), four per large unit, one per small unit. Furthermore there are 41 "object" entries (weapons etc) and 6 obsolete/unused entries (mostly unusable, and without valid name pointers in the executable).

Values are presented in bold, according to the offsets in each record (0 to 53).

Note: If you hack OBDATA, you can have the game reload the data by entering or exiting the battlescape mode. This is true for the DOS version of X-Com (which switches between executables at these points), but the WinCE version may need to be entirely restarted.

== Structure ==

0-19: Name of object. Delimited by a null character. These are internal names... they all make sense, but are not the standardized names displayed in the game. Names and IDs (reference lookup numbers, including within OBDATA - see e.g. [26] to [28]):

{| {{StdDescTable}}
|- {{StdDescTable_Heading}}
! Index !! Object !! Index !! Object !! Index !! Object
|-
| 00/x00 || PISTOL || 27/x1B || Flare || 54/x36 || Floater Corpse
|-
| 01/x01 || PISTOL CLIP || 28/x1C || empty || 55/x37 || Celatid Corpse
|-
| 02/x02 || RIFLE || 29/x1D || empty || 56/x38 || Silacoid Corpse
|-
| 03/x03 || RIFLE CLIP || 30/x1E || empty || 57/x39 || Chryssalid Corpse
|-
| 04/x04 || HEAVY CANNON || 31/x1F || CORPSE || 58/x3A || reaper corpse 1
|-
| 05/x05 || CANNON AP-AMMO || 32/x20 || CORPSE & ARMOUR || 59/x3B || reaper corpse 2
|-
| 06/x06 || CANNON HE-AMMO || 33/x21 || CORPSE & POWER SUIT || 60/x3C || reaper corpse 3
|-
| 07/x07 || CANNON I-AMMO || 34/x22 || Heavy Plasma || 61/x3D || reaper corpse 4
|-
| 08/x08 || AUTO-CANNON || 35/x23 || Heavy Plasma Clip || 62/x3E || cyber 1
|-
| 09/x09 || AUTO-CANNON AP-AMMO || 36/x24 || Plasma Rifle || 63/x3F || cyber 2
|-
| 10/x0A || AUTO-CANNON HE-AMMO || 37/x25 || Plasma Rifle Clip || 64/x40 || cyber 3
|-
| 11/x0B || AUTO-CANNON I-AMMO || 38/x26 || Plasma Pistol || 65/x41 || cyber 4
|-
| 12/x0C || ROCKET LAUNCHER || 39/x27 || Plasma Pistol Clip || 66/x42 || secto 1
|-
| 13/x0D || SMALL ROCKET || 40/x28 || BLASTER LAUNCHER || 67/x43 || secto 2
|-
| 14/x0E || LARGE ROCKET || 41/x29 || BLASTER BOMB || 68/x44 || secto 3
|-
| 15/x0F || INCENDIARY ROCKET || 42/x2A || SMALL LAUNCHER || 69/x45 || secto 4
|-
| 16/x10 || LASER PISTOL || 43/x2B || STUN MISSILE || 70/x46 || hover 1
|-
| 17/x11 || LASER GUN || 44/x2C || ALIEN GRENADE || 71/x47 || hover 2
|-
| 18/x12 || HEAVY LASER || 45/x2D || ELERIUM-115 || 72/x48 || hover 3
|-
| 19/x13 || GRENADE || 46/x2E || MIND PROBE || 73/x49 || hover 4
|-
| 20/x14 || SMOKE GRENADE || 47/x2F || >>UNDEFINED << || 74/x4A || TANK1
|-
| 21/x15 || PROXIMITY GRENADE || 48/x30 || >> empty << || 75/x4B || TANK 2
|-
| 22/x16 || HIGH EXPLOSIVE || 49/x31 || >> empty << || 76/x4C || TANK 3
|-
| 23/x17 || MOTION SCANNER || 50/x32 || Sectoid Corpse || 77/x4D || TANK 4
|-
| 24/x18 || MEDI-KIT || 51/x33 || Snakeman Corpse || 78/x4E || CIVM
|-
| 25/x19 || PSI-AMP || 52/x34 || Ethereal Corpse || 79/x4F || CIVF
|-
| 26/x1A || STUN ROD || 53/x35 || Muton Corpse || ||
|}

The names as displayed in battle are stored in [[ENGLISH2.DAT]], [[FRENCH2.DAT]] and [[GERMAN2.DAT]], hence allowing them to appear in multiple languages. The exact pointers as to which item has which name are stored in [[TACTICAL.EXE]].

'''20:''' [[BIGOBS.PCK]] reference (pointer to graphic for inventory)

'''21:''' [[FLOOROB.PCK]] reference (pointer to graphic for item on ground)

'''22:''' Average Weapon Strength (Same as seen in [[UFOpaedia]]). For clip based weapons, this applies to the clip and ''not'' the weapon itself. Also note that if set to 0 the weapon will still "shoot" and the shot can still "hit", registering with the hit counter at [[UNITREF.DAT]][81] and making an easy way to avoid any damage while testing (if so desired).

Note that a (non-explosive) weapon will hit for between 0 and this*2 damage with each shot. For example, if you set it to 100, the weapon will deal between 0 and 200 points each time it is fired.

For information on hacking explosives vs. their blast diameters and strength, see [[Explosions#Playing_With_Fire|this]]. It includes what happens if you change the Stun Bomb to HE.

'''23:''' Display priority for when items are in a stack. The highest value here determines which will be rendered in the battlescape. In the case of a tie, the lowest ObPos record number wins.

'''24:''' Inventory X Size (width)

'''25:''' Inventory Y Size (height)

'''26-28:''' Look-up within OBDATA for ammo this weapon uses. Up to three types possible; 255 for no (more) ammo. Note that ammo always directly follows its weapon in this file.

'''29:''' Unknown. Apparently comparable to offset 30 on occasion.

'''30:''' [[HANDOB.PCK]] reference (pointer to graphic for battlescape).

'''31:''' Ammo Damage Type
0 AP
1 IN
2 HE
3 Laser
4 Plasma
5 Stun
6 Melee
7 Acid Spit (from [[Celatid]])
255 ''Not Ammo''

'''32:''' Accuracy, Auto

'''33:''' Accuracy, Snap

'''34:''' Accuracy, Aimed

''Percent TUs are rounded down (truncated). In an extreme case, if you hack [[UNITREF.DAT]][25] (Base TUs) to 199 and Percent TUs to 1, you will need 1 TU to fire the weapon (and can make 199 shots per turn). Or to really make things interesting, set Base TUs to 99 and Percent TUs to 1 - now it takes '''zero''' TUs! Also, it relies on Base TUs, not current TUs, so if you e.g. put Base TUs at 99, Percent TUs at 1 (0 TUs per shot), and Current TUs at 255, you still get 255 TUs, with 0 TUs per shot, for the turn you load that savegame - excellent if you plan on reloading it for each round of testing.''

''Don't set Percent TUs to 0. If you do, the object is no longer considered a weapon, and can only be thrown.''

'''35:''' Percent TUs Used, Auto

'''36:''' Percent TUs Used, Snap

'''37:''' Percent TUs Used, Aimed

'''38:''' Primary use: Clip Size (for ammo; see [49]). Secondary use: Melee weapon strength, as follows:

0 All Corpses/Electroflare/Mind probe
8 Pistol
65 Stun Rod
10 ''Everything else...''
Tertiary use: Timer for "grenade", if Grenade ([44]) is true. Only works if item is ammo ([49]). If it is then e.g. since Blaster has a 1 here (1 bomb per blaster "clip"), it will explode at end of turn 1 (if not being held in inventory).

'''39:''' Possibly Melee-related Stat??
0 All Corpses
0 Plasma Pistol Clip
5 Stun Rod
9 Pistol and Pistol Clip
8 ''Everything else...''

''SGW:'' Melee damage type?
0 AP
1 IN
2 HE
3 Laser or Gauss
4 Plasma or Sonic
5 Stun
6 TFTD vibroblade damage (does not appear to be used in UFO)
7 TFTD Electric damage (Bio Drone?)

'''40:''' Possibly Melee Accuracy?? Zombie [http://www.strategycore.co.uk/forums/index.php?showtopic=746&st=178# found] that changing this does not change the Stun Rod's 100% accuracy (nor does changing soldier Melee Accuracy). Thus the Stun Rod appears to be hard-wired to 100%. Has anyone tried editing this value with hacked melee weapons?
0 All Corpses
0 Electroflare
0 Plasma Weapon Clips
100 ''Everything else...''

''SGW:'' This '''is''' Melee Weapon Accuracy. For UFO Stun Rod the amount may be hard wired for 100%, but in TFTD this variable is valid and effective (though I don't know what kind of accuracy it uses - Aiming/Throwing?)

'''41:''' TU% when attacking as a melee weapon: (courtesy of NKF)
50 Most objects
30 Stun rod
40 TFTD thermal tazer
10 Vibroblade
15 Thermal lance
20 Heavy thermal Lance
0 All Corpses
0 Electroflare
0 Plasma Weapon Clips

So a summary of 39 to 41 looks like this:

39 40 41 Objects
0 0 0 All Corpses/Plasma Pistol Clip
5 100 30 Stun Rod
8 0 0 Plasma Rifle Clip/Heavy Plasma Clip/Electroflare
9 100 50 Pistol/Pistol Clip

8 100 50 ''Everything else...'' (34 objects)

'''42:''' Explosive strength needed to [[Explosions#Object_Destruction|destroy object]].

'''43:''' [[Item Weight]], used for both throwing and encumberance purposes.

'''44:''' Grenade Type
1 Grenade, Alien Grenade, High Explosive
2 Proximity Grenade
3 Smoke Grenade

'''45:''' Maybe an abandoned bit field, all except the Elerium tick?:

0 All corpses and many human objects, including weapons and ammo
1 All alien weapons and ammo but also several common human ammos and the pistol
4 Elerium

'''46:''' Boolean: Is Weapon That Shoots?

'''47:''' Boolean: Is Weapon?

'''48:''' Boolean: Is Non-Waypoint Weapon?

'''49:''' Boolean: Is Ammo?

'''50:''' Boolean: Is Two-Handed Weapon?

'''51:''' Boolean: Is Blaster Launcher?

'''52:''' Boolean: Is Alien?

'''53:''' [[Scoring]] points (except for Elerium which works per 50 units).

==Extra Notes==
Certain weapons have "unique" features, such as the motion scanner (which can, well, bring up the motion scanner display) and the stun rod (which is the only item in the game which you can actually use as a melee weapon).

These properties are not configured in this file, but are instead defined by the game executable. Copying the stun rod ObData info to a different record number results in an item which can't be used to zap things.

One way around this limitation is to stack two or more items in your soldiers hands (via hacking) - The action menu will then display a combination of both items abilities. This allows you to bludgeon things with a plasma rifle (for example).

Laser weapons use no clips, but can still be fired. To give similar properties to other weapons you must remove their ammo type indexes (set offsets [26]-[28] to 255), give them a valid damage type (set offset [31] to a value from 0-7), and give them a power rating (set offset [22] to the average you want the weapon to deal).

==See Also==
* [[OBPOS.DAT]] - Stores positions of objects in a battlescape
* [[PRODUCT.DAT]] - Stores information on manufactuable items (Hours, Cost, etc.)
* [[PURCHASE.DAT]] - Stores buying and selling Information about most of these items
* [[UP.DAT]] - References items in this file for the UFOpaedia
* [[GEODATA]] - Parent Folder for file
* [[Saved Game Files]]
[[Category:Game Files]]

Item Destruction Table (TFTD)

2008-03-19T18:53:31Z

Sirgalahadwizard:

This page lists the damage that must be done by an explosive weapon to destroy a given object. Listed from most fragile objects to most durable and indestructible.

Note: The Sonic Pulser, Magna-Pack Explosive, Particle Disturbance Grenade, and Magna-Blast Grenade have negative values for the amount of power needed to destroy them, making them effectively indestructible.

{| border="1" cellspacing="0"
!Item
!Damage needed to destroy
|-
|X-Com Corpses
|0(any explosion)
|-
|Civilian Male Corpse
|12
|-
|All items not listed
|20
|-
|Small alien corpses
|26
|-
|Hydro Jet Cannon clips
|40
|-
|Chemical Flare
|40
|-
|Phosphorous Torpedo
|40
|-
|Disrupter Pulse Launcher
|40
|-
|Sonic Pistol
|45
|-
|Gas Cannon clips
|50
|-
|All Sonic weaponry and clips EXCEPT Sonic Pistol
|50
|-
|Small and Large torpedoes
|50
|-
|Thermal Shok Bomb
|60
|-
|Disrupter Pulse Torpedo
|60
|-
|Gauss weapon clips
|70
|-
|Dye Grenade
|110
|-
|Magna-Blast Grenade
|150
|-
|Particle Grenade
|150
|-
|Sonic Pulser
|150
|-
|Magna-Pack Explosive
|150

|}

[[Explosions#Explosive Damage to Walls and Objects|Explosive weapons]] do 50% of average damage to items on the ground (adjusted for distance from ground zero). In addition, objects can only be destroyed by explosions with strength greater than the values in the table. These are the damage values versus objects for various weapons at ground zero:

*[[Gas Cannon#Ammo Statistics|Gas Cannon HE rounds]]: 32.5
*[[Hydro-Jet Cannon#Ammo Statistics|Hydro-Jet Cannon HE rounds]]: 25
*[[Torpedo Launcher#Ammo Statistics|Small HE Torpedoes]]: 40
*Large HE Torpedoes: 45
*[[Magna-Blast Grenade]]: 25
*[[Magna-Pack Explosive]]: 50
*[[Particle Disturbance Grenade]]: 35
*[[Sonic Pulser]]: 60
*[[Disrupter Pulse Launcher]]: 100

*[[Coelacanth/Aqua_Jet|Coelacanth Torpedoes]]: 45
*[[Displacer/PWT|Displace Pulse Wave Torpedoes]]: 70

[[Category:data tables]]

GEOSCAPE.EXE

2008-03-11T15:56:23Z

Sirgalahadwizard: /* Alien Stats */

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]]

= 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!).

= 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]. ''(Have YOU made your StratCore and [http://www.xcomufo.com XCOMUFO] accounts yet?)''

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)

'''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)

= 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?

= 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.

= 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
* [[Saved Game Files]]

[[Category:Game Files]]

GEOSCAPE.EXE

2008-03-11T15:50:30Z

Sirgalahadwizard: /* Alien Stats */

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]]

= 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!).

= 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]. ''(Have YOU made your StratCore and [http://www.xcomufo.com XCOMUFO] accounts yet?)''

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)

'''24:''' ''Damage Modifier'' - Corresponds to which set of damage modifiers the creature uses (0-13) (see Damage Modifiers)

'''33:''' ''Points'' - How many mission points are received for killing the alien (note, does not affect points for capture, for killing civilians, or killing Tanks/SWS's)

''NOTE: For additional important info on bytes 22-23, 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)

'''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)

= 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?

= 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.

= 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
* [[Saved Game Files]]

[[Category:Game Files]]

HackerTools

2008-03-11T15:39:37Z

Sirgalahadwizard:

Windows comes with the simple but effective EDIT hex editor. To use it:

* /Start /Run then enter EDIT
* Point to the game file of interest. This DOS tool has some old conventions such as: clicking on the two periods (..) at the top of the Directory list moves you up one directory level. Use Help (F1) for more info. Once you've highlighted the file of interest,
* Checkmark "Open Binary"
* If you know the record length for your file of interest, enter it on "Line Width". For example, SOLDIER.DAT has record lengths of 68. This causes file entries to "line up" and makes patterns obvious.
* If you're new to hacking, checkmark "Open Read-Only". This prevents you from making changes.

Editing:
* The "Col" and "Value" info along the bottom bar show you the current byte column you're in, and its value. Use this when comparing your file against e.g. the [[SOLDIER.DAT]] and [[UNITREF.DAT]] wiki entries.
* Many folks talk about byte positions using offsets (starts at 0, and is indicated by [square brackets]) whereas EDIT does not (starts with column 1). If the values don't seem to be jiving, try looking one column to the right (or left!).
* WARNING: When you first start to edit, hit the Insert key once to get the big block cursor. This puts you in Overwrite mode instead of Insert mode (the small underline cursor). Be VERY CAREFUL about hitting the Insert key again. Insert mode is a Very Bad Thing(tm) for binary files. Inserting a byte moves every subsequent byte over by one, thus nuking position-based files (i.e., most XCOM files). If your game has gone south and you're SOL though, you might give it a shot... you never know what might happen!
* Likewise, be VERY CAREFUL about hitting keys like Delete, Backspace, or Enter. All these (and more!) mess with positionality. If you ever see that records aren't lining up, Close without saving!!
* To enter numeric values into a byte:
** Hold down an Alt key (either one)
** Using the NUMERIC KEYPAD (the numbers on right side of keyboard, not the ones along the top of keyboard), type in the number you want to enter. It doesn't matter if Numlock is on or off.
** Let go of the Alt key. In the case where your computer doesn't have a numeric keypad such as a laptop, you must press the function (Fn) key along with ALT in order to enter these values.
** The number will now be entered. However, for values less than 28, you have to go through special gyrations (these were "control characters" for DOS). First, hit Control-P (^P). Then:
*** For 0, hit ^2 (don't ask why)
*** For 1-26, hit ^A to ^Z. For example, ^A is 1, ^M is 13, ^Z is 26.
*** For 27, hit ^[
* A handy lookup table for numbers versus characters can be found as a .GIF [[Media:DOS_Chars_In_MsEdit.gif|here]] or the same thing in a .PDF [[Media:DOS_Chars_In_MsEdit.pdf|here]]
* If you see that your number makes a "regular" character (e.g. 65=A), you can also simply type in that character. However, the space character (number 32) looks just like a null character (number 0); don't use a space to mean zero!
* Make a copy of the file if you're unsure of what you're doing. EDIT prompts you about making a .BAK backup file when you save edits, which is a nice convenience.

Also:
* Some savegame files store 'rubbish' in a field that's not being used. For example, not all soldier and alien names are 25 characters long (26 including the null byte, value 00, that shows where it ends). You'll usually find rubbish stored in the columns past the name end. It can be the remains of old (longer) names, or might even be e.g. random Windows crap that was in that position in RAM when the file was last in memory. Garbage characters may also show up in e.g. fields that an alien doesn't use (but soldiers do). Don't worry about them... if there's no reason for the game to use them, they're meaningless.
* If you have a file open in EDIT, it is not locked by the system. You can keep the file open indefinitely even when the game is running and nothing strange will happen. Just make sure to save your changes so that they show up. In the case if the executable, it is always best to save and restart.

Another hex editor that some folks use is Hex Workshop by [http://www.bpsoft.com www.BPSoft.com]. Hex Workshop has the nice feature that you can make a 'structure library' with the meaning (field name) of each byte, turning the file into a little database. You will see some of these definitions (.HSLs) in the game file wikis. Hex Workshop is free for 30 days and then costs $50 if you want to keep using it. While it has a number of nice features, it does have some drawbacks. Examples: 1) Its display field can't be more than 64 characters wide (unlike EDIT), so you can't do a "one row equals one record" display for e.g. SOLDIER.DAT (reclength 68) or UNITREF.DAT (reclength 124). Related to this, 2) although it's a "modern" Windows app, you can't e.g. go to some tiny font and see a lot more in your data display window (even though you probably have 1600x1200 screen rez as a L33T gamer).

If you're on a budget, EDIT is a fine little tool. I, for one, once used Hex Workshop, but now exclusively use EDIT.

'''NOTE:''' To make screen captures, see [[Info#Screenshots|this]].

----

Another VERY useful hex editing program is the Universal Game Editor (UGE). It is a hex editor which displays numbers in digits instead of hex codes. It uses templates that can store variables found in the game files, so that they can be easily edited (including variables with 1, 2, or 4 bytes, or text entries).

It can be found from a variety of locations using a search engine. The program is only about 400kb and is free to use (shareware with full capabilities, but has a reminder screen).

----

Return to [[Game_Files]]

Damage

2008-03-11T15:31:22Z

Sirgalahadwizard: /* Formula */

= Overview =

'''Damage''' in XCOM comes in two major ways, and then there are some oddballs:

*[[Weapons|Weapon]] (a.k.a. firearm or gun) damage, and
*[[Explosions|Explosive]] damage.

Technically, explosives are weapons. But on this wiki, "weapons" usually means firearms, as separate from explosives - but use your judgement when reading any particular page. Still, on this Damage page and on the [[Explosions]] page, "weapons" always means firearms as opposed to explosives, unless otherwise stated.

Past these two types of damage, there are two important target classes: Units and Terrain. (A third target class is [[Explosions#Object_Destruction|objects on the ground]].) The application of force to these two targets types is different. A 2 x 2 table follows. Percents mean, '''percent of weapon strength as shown in UFOpaedia''' (an important point):

Firearms Explosives
Units 0%-200% 50%-150%
Terrain 25%- 75% 50%

Rules:
* For '''units''', armor always reduces calculated damage, before any damage is applied. Units take damage that exceeds their armor and "remember" it, by having their health damaged.
* But '''terrain''' is unaffected unless damage is equal to or greater than its health rating, at which point it is simply destroyed. (This is sometimes called terrain's "armor" value, but for terrain, "armor" does not equate to the XCOM soldier sense of armor.) If terrain has ''not'' been outright killed by a particular shot or explosion, it stays at perfect health, unless and until some future damage exceeds its rating. Thus, terrain is either obliterated or in perfect health. Just the same, the XCOM programmers designed the game so that if terrain objects are "killed", they usually turn into a "damaged" object. Here's where "melted walls" or "burnt corn fields" come into play. Still, even these latter are terrain objects which, in turn, can be destroyed if damage exceeds their rating. Once the "regular" and "dead" tile have both been killed, once sees raw earth at ground level, or nothing, at higher levels.
* As you can see from the table above, it's important to realize that the UFOpaedia shows ''average'' weapon strength versus units. And conversely, both weapons and explosives only impart ''half'' their UFOpaedia strength versus terrain. This is a fixed half, for explosives, and half on average, for firearms.

Some units also have modifiers versus particular weapon classes, as shown below.

The less common (but no less fun!) forms of damage are:

* Stun damage, provided by the [[Stun Rod]] and [[Small Launcher|Stun Bomb]] and even [[Smoke Grenade|smoke]]. Oddly, the Stun Rod is the lone melee weapon in XCOM, and the [[Small Launcher|Small Launcher's]] stun bomb follows the rules of [[explosions|explosives]] for its blast pattern and tile "explosive" strength, but gives 0-200% stun damage at a given tile; see [[Small Launcher]] for more clarification.
* [[Incendiary]] damage is a complex but ultimately fairly weak type of damage.
* Objects dropped on the ground can only be destroyed by explosive damage, at particular fixed strengths as shown [[Explosions#Object Destruction|here]] .

Wise X-COM commanders are mainly concerned about '''unit''' damage from '''weapons''' - explained in detail below. But see [[Explosions]] for more about explosions and terrain.

= Formula =

''' Damage to Unit = (Weapon Damage × Damage Modifier) - Armour '''

If the bullet does negative or zero damage, then the bullet is ignored (for damage purposes, but you still get [[Firing Accuracy]] [[experience]] if it did hit). If the bullet does damage, then there's a chance that the armour plate that it struck will deteriorate by a few points, as shown [[Damage#Armor_vs._Health_Damage|below]].

That's the basic idea. Let's expand on the variables a bit:

; Weapon Damage : Weapon damage will be a random number between 0 and two times the damage level of the weapon listed in the UFOpaedia. In reality, all of the damages listed in the UFOpaedia are the averages for the weapons. Note that the doubling of the damage is done before the modifiers are applied.

(edit: In TFTD, the listed weapon damage in the UFOpaedia is still the average damage caused, but the difference from UFO is that random weapon damage is rolled twice and averaged, which produces values which are more often closer to the average)

; Damage Modifier : All units in the game will have various modifier levels for all the ammo types in the game. The modifier is simply a percentage multiplier that changes the weapon damage, for better or for worse. For more information, see the next section for specifics.

; Armour : The armour section the bullet hit. This can be the front, rear or the left or right side armour for ballistic projectiles. Under armour can only be hit when the target is at or standing right next to the very [[Explosions#Distance_from_Ground_Zero|centre]] of an explosion from an area-effect weapon, otherwise it's treated as directional damage. To put it bluntly, armour is pure damage reduction.

= Damage Modifiers =

{{:Damage Modifiers}}

For another way to view the same info above, see [[Kill_Modelling#Modifiers|this]].

See also: [[Damage Modifiers (TFTD)|TFTD Damage Modifiers]]

= Example =

''Adapted from [http://www.xcomufo.com/forums/index.php?act=ST&f=280&t=8701&st=37# Zombie's] kindly example:

'''Scenario:''' Beginner level Muton mission. Your soldier is carrying a normal Pistol and you want to know what is the chance that a Muton Soldier's front armor will absorb a direct hit without lowering health.

'''Vitals:'''
Muton Soldier front armor = 10
Muton Soldier health = 125
Muton susceptibility to Armor Piercing ammo = 60%
Pistol listed power = 26 (average)

'''Calculation:'''

Max damage for a Pistol against a Muton is lowered due to susceptibility:

'''Modified max damage''' = INT(26 * 2 * 60 / 100)
= INT(52 * 60 / 100)
= INT(3120 / 100)
= INT(31.2)
= 31

where 2 is the max modifier (200% of UFOpaedia listed power) and 60/100 is the damage modifier (60%)

The range of values the Pistol can deal is 0 to 31 points of damage (or a range of 32 different values). The equation's steps are shown because XCOM's math sometimes leads to slightly unexpected values in [http://www.strategycore.co.uk/forums/index.php?showtopic=746&view=findpost&p=41445 subsequent] steps.

The Muton Soldier has a front armor rating of 10. It will absorb up to this much damage without changing health. In other words, it will negate the first 10 points of damage a Pistol can dish out (0-10; 11 possible values). Since the Pistol has a range of 32 possible values, the probability that a direct hit will be blocked by Muton armor is simply 11 / 32 = '''34.4%'''.

Okay, say you want to know the probability of doing damage to a Muton's health. The pistol still has 32 values, but instead of absorption we want penetration. 10 points of damage is absorbed, so we need at least 11 to penetrate. 32 - 11 = 21 values which will breach. 21 / 32 = '''65.6%'''.

21 is also the maximum number of damage points which might be deducted from the Muton's health. Assuming the Muton was initially uninjured, in the worst case (for him!) he will have an ending health of 125 - 21 = '''104'''.

On average, there will be 15.5 damage dealt (0-31). Then armor (10) reduces this to an actual (penetrating) average damage of '''7.22'''. (It's not simply 15.5-10=5.5 because initial damage that's less than ten becomes zero penetrating damage, not negative penetrating damage. The removal of these negative values causes the expected average to rise, as it were.)

If you need precision while testing, note that the game applies truncation ''after'' making its damage roll. It does not first determine the maximum (including damage modifiers), and then roll randomly/evenly from 0 up to the maximum, per se. To wit: if you hack a pistol to an average damage strength of 1, there would not be an overall roll of 0 to a maximum of 1 (with average damage of '''''0.5''''') as might be implied from the Muton-versus-AP example above. Instead, there is a roll of 0, 1, or 2, to which the .6 modifier is applied. Only a roll of 2 results in non-zero damage (INT(2x60/100)= INT(1.2)= 1), and the Muton only takes an average of '''''0.33''''' damage, not 0.5. Usually this effect is insignificant relative to the large damage values found in the game, but it could matter in testing situations involving very low damage strengths. It also means you need to take into account all possible values versus individual truncation effects, if you want an ultra-precise listing of e.g. how often armor is breached.

= Armor vs. Health Damage =

When there is '''penetrating''' damage (i.e., damage is >0 and not all blocked by armor), Health and Armor Damage have a very simple relationship:

'''Health Damage''' = 10 * Armor Damage, minus 1 to 10

Or the other way around:

'''Armor Damage''' = INT( Health Damage / 10 ) + 1

In table form:

Armor Health Damage
Damage Min Max
0 0 0
1 1 9
2 10 19
3 20 29
4 30 39
5 40 49
6 50 59
7 60 69
8 70 79
9 80 89
etc.

Of course, this assumes armor is not zeroed out by the hit. Also note that you will always have armor damage if you have health damage and vice-versa, if there was damage penetration. Stated another way, you will never have armor damage if you don't have health damage (i.e., when there is insufficient damage to breach the armor).

You will see this health/armor relationship if you watch damage from individual hits. However, the relationship is muddied if you only look at a unit after a number of hits (or, of course, if armor is broken through). The most extreme example would be if a unit were hit with e.g. five hits of 1 penetrating damage point each. The unit would have 5 health damage and 5 armor damage, which would appear contrary to the above table.

This relationship has been been tested for a wide variety of explosions and some light weapons vs. Mutons, and some hits on soldiers. It has not otherwise been widely tested, but is presumed true unless/until found otherwise.

As stated, the above is for damage that '''penetrates'''. It is possible for hits (guns or explosions) to do zero damage. This happens on the rare occasion that a weapon damage roll is actually zero, or, much more commonly, when armor has blocked all the damage. You still get an experience point toward [[Firing Accuracy]] if damage fails to penetrate. You only have to hit the target(s) to get Firing experience; there doesn't have to be damage.

For Health Damage versus Fatal Wounds, see [[Fatal_Wounds#Probability_of_Fatal_Wounds]].

= See Also =

*[[Weapons]]
*[[Explosions]]
*[[Firing Accuracy]]
*[[Health]]
*[[Medi-Kit]]
*[[Experience]]

[[Category: data tables]]

Damage Modifiers (TFTD)

2008-03-11T15:22:14Z

Sirgalahadwizard: /* '''Susceptible to...''' */

= Damage Modifiers =

=== '''Vulnerable to...''' ===

'''Phosphor/Fire'''
Hallucinoid 170%

'''High Explosive'''
Tentaculat 150%

'''Sonic'''
Tasoth 120%
Deep One 110%
Gill Man 110%
Calcinite 110%
Tentaculat 110%

'''Stun(Freeze)'''
Tasoth 110%
Tentaculat 110%

'''Drill'''
Lobsterman 200%
Unarmored Soldier 160%
Civilian 160%
Aquatoid 160%
Xarquid 145%
Deep One 120%
Gill Man 120%
Plastic Aqua Armor 120%
Ion Armor 110%
Magnetic Ion Armor 110%
Tentaculat 110%
Triscene 110%

'''Electric Shock'''
Unarmored Soldier 150%
Civilian 150%
Bio-Drone 120%
Plastic Aqua Armor 110%

=== '''Resistant to...''' ===

'''Armor Piercing'''
Bio-Drone 95%
Deep One 90%
Triscene 90%
Plastic Aqua Armor 90%
Ion Armor 80%
Magnetic Ion Armor 80%
Tasoth 80%
Tentaculat 80%
Hallucinoid 60%
Lobsterman 20%

'''Phosphor/Fire'''
Triscene 90%
Deep One 90%
Calcinite 90%
Plastic Aqua Armor 80%
Xarquid 60%
Bio-Drone 40%
Tasoth 40%
Lobsterman 30%
Ion Armor 0%
Magnetic Ion Armor 0%

'''High Explosive'''
Triscene 90%
Tasoth 90%
Ion Armor 80%
Magnetic Ion Armor 80%
Bio-Drone 80%
Deep One 80%
Hallucinoid 70%
Xarquid 60%
Lobsterman 30%

'''Gauss'''
Deep One 90%
Calcinite 90%
Tentaculat 90%
Plastic Aqua Armor 80%
Hallucinoid 80%
Triscene 80%
Ion Armor 70%
Magnetic Ion Armor 70%
Tasoth 70%
Xarquid 70%
Bio-Drone 60%
Lobsterman 30%

'''Sonic'''
Ion Armor 90%
Magnetic Ion Armor 90%
Xarquid 90%
Triscene 90%
Lobsterman 50%

'''Stun(Freeze)'''
Xarquid 90%
Triscene 90%

'''Drill'''
Tasoth 90%
Bio-Drone 80%
Calcinite 80%
Hallucinoid 60%

'''Electric Shock'''
Deep One 0%
Gill Man 0%
Tasoth 0%
Calcinite 0%
Tentaculat 0%
Lobsterman 0%
Xarquid 0%
Hallucinoid 0%
Triscene 0%

=== '''Susceptible to...''' ===

<table width="80%" {{StdCenterTable}}>
<tr {{StdDescTable_Heading}}><th rowspan="2">Ammo Type</th>
<th colspan="14">Damage Modifier Category</th></tr>
<tr{{StdDescTable_Heading}}><th>0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4</th>
<th>5</th>
<th>6</th>
<th>7</th>
<th>8</th>
<th>9</th>
<th>10</th>
<th>11</th>
<th>12</th>
<th>13</th>
<tr><th align="left" {{StdDescTable_Heading}}>Armour Piercing</th><td>100</td><td>100</td><td>90</td><td>80</td><td>95</td><td>90</td><td>100</td><td>80</td><td>100</td><td>80</td><td>20</td><td>100</td><td>60</td><td>90</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Incendiary</th><td>100</td><td>100</td><td>80</td><td>0</td><td>40</td><td>90</td><td>100</td><td>40</td><td>90</td><td>100</td><td>30</td><td>60</td><td>170</td><td>90</tr>
<tr><th align="left" {{StdDescTable_Heading}}>High-Explosive</th><td>100</td><td>100</td><td>100</td><td>80</td><td>80</td><td>80</td><td>100</td><td>90</td><td>100</td><td>150</td><td>30</td><td>60</td><td>70</td><td>90</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Gauss</th><td>100</td><td>100</td><td>80</td><td>70</td><td>60</td><td>90</td><td>100</td><td>70</td><td>90</td><td>90</td><td>30</td><td>70</td><td>80</td><td>80</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Sonic</th><td>100</td><td>100</td><td>100</td><td>90</td><td>100</td><td>110</td><td>110</td><td>120</td><td>110</td><td>110</td><td>50</td><td>90</td><td>100</td><td>90</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Stun(Freeze)</th><td>100</td><td>100</td><td>100</td><td>100</td><td>100</td><td>100</td><td>100</td><td>110</td><td>100</td><td>110</td><td>110</td><td>90</td><td>100</td><td>90</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Drill</th><td>100</td><td>160</td><td>120</td><td>110</td><td>80</td><td>120</td><td>120</td><td>90</td><td>80</td><td>110</td><td>200</td><td>145</td><td>60</td><td>110</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Electric Shock</th><td>100</td><td>150</td><td>110</td><td>100</td><td>120</td><td>0</td><td>0</td><td>0</td><td>0</td><td>0</td><td>0</td><td>0</td><td>0</td><td>0 </tr></table>
Please note that these are the actual numbers taken directly from the executable, which the game uses. The numbers from the Official Strategy Guide are incorrect.

(For those interested in changing/hacking the creature damage modifiers, they are located in the Tactical.exe near the end of the file, preceded directly by the decimal variable "26". They are listed in left to right order, using the table above as a reference - in groups of 14 variables for each ammo type. Each variable is separated by a "0", which may indicate they are actually 2-byte variables.)

The Numbers listed below are a reference to the damage chart above (there are 14 sets of damage modifiers, numbered 0-13). The creature entries listed in the Geoscape.exe have a variable which points to which set of damage modifiers the creature uses.
{| {{StdDescTable}}
|- {{StdDescTable_Heading}}
! Column !! Unit Type(s)
|-
| '''0''' || Terrain.
|-
| '''1''' || Unarmored Soldiers, Civilians, Aquatoids, Zombies.
|-
| '''2''' || Plastic Aqua Armor.
|-
| '''3''' || Ion Armor and Magnetic Ion Armor.
|-
| '''4''' || SWS's and Displacers.
|-
| '''5''' || Deep One.
|-
| '''6''' || Gill Man.
|-
| '''7''' || Tasoth.
|-
| '''8''' || Calcinite.
|-
| '''9''' || Tentaculat.
|-
| '''10''' || Lobsterman.
|-
| '''11''' || Xarquid and Bio-Drone.
|-
| '''12''' || Hallucinoid.
|-
| '''13''' || Triscene.
|}

Note: SWS and Displacer damage modifiers are not shown in the Official Strategy Guide.

[[Category:data tables]]

Damage Modifiers (TFTD)

2008-03-11T15:17:40Z

Sirgalahadwizard: /* '''Susceptible to...''' */

= Damage Modifiers =

=== '''Vulnerable to...''' ===

'''Phosphor/Fire'''
Hallucinoid 170%

'''High Explosive'''
Tentaculat 150%

'''Sonic'''
Tasoth 120%
Deep One 110%
Gill Man 110%
Calcinite 110%
Tentaculat 110%

'''Stun(Freeze)'''
Tasoth 110%
Tentaculat 110%

'''Drill'''
Lobsterman 200%
Unarmored Soldier 160%
Civilian 160%
Aquatoid 160%
Xarquid 145%
Deep One 120%
Gill Man 120%
Plastic Aqua Armor 120%
Ion Armor 110%
Magnetic Ion Armor 110%
Tentaculat 110%
Triscene 110%

'''Electric Shock'''
Unarmored Soldier 150%
Civilian 150%
Bio-Drone 120%
Plastic Aqua Armor 110%

=== '''Resistant to...''' ===

'''Armor Piercing'''
Bio-Drone 95%
Deep One 90%
Triscene 90%
Plastic Aqua Armor 90%
Ion Armor 80%
Magnetic Ion Armor 80%
Tasoth 80%
Tentaculat 80%
Hallucinoid 60%
Lobsterman 20%

'''Phosphor/Fire'''
Triscene 90%
Deep One 90%
Calcinite 90%
Plastic Aqua Armor 80%
Xarquid 60%
Bio-Drone 40%
Tasoth 40%
Lobsterman 30%
Ion Armor 0%
Magnetic Ion Armor 0%

'''High Explosive'''
Triscene 90%
Tasoth 90%
Ion Armor 80%
Magnetic Ion Armor 80%
Bio-Drone 80%
Deep One 80%
Hallucinoid 70%
Xarquid 60%
Lobsterman 30%

'''Gauss'''
Deep One 90%
Calcinite 90%
Tentaculat 90%
Plastic Aqua Armor 80%
Hallucinoid 80%
Triscene 80%
Ion Armor 70%
Magnetic Ion Armor 70%
Tasoth 70%
Xarquid 70%
Bio-Drone 60%
Lobsterman 30%

'''Sonic'''
Ion Armor 90%
Magnetic Ion Armor 90%
Xarquid 90%
Triscene 90%
Lobsterman 50%

'''Stun(Freeze)'''
Xarquid 90%
Triscene 90%

'''Drill'''
Tasoth 90%
Bio-Drone 80%
Calcinite 80%
Hallucinoid 60%

'''Electric Shock'''
Deep One 0%
Gill Man 0%
Tasoth 0%
Calcinite 0%
Tentaculat 0%
Lobsterman 0%
Xarquid 0%
Hallucinoid 0%
Triscene 0%

=== '''Susceptible to...''' ===

<table width="80%" {{StdCenterTable}}>
<tr {{StdDescTable_Heading}}><th rowspan="2">Ammo Type</th>
<th colspan="14">Damage Modifier Category</th></tr>
<tr{{StdDescTable_Heading}}><th>0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4</th>
<th>5</th>
<th>6</th>
<th>7</th>
<th>8</th>
<th>9</th>
<th>10</th>
<th>11</th>
<th>12</th>
<th>13</th>
<tr><th align="left" {{StdDescTable_Heading}}>Armour Piercing</th><td>100</td><td>100</td><td>90</td><td>80</td><td>95</td><td>90</td><td>100</td><td>80</td><td>100</td><td>80</td><td>20</td><td>100</td><td>60</td><td>90</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Incendiary</th><td>100</td><td>100</td><td>80</td><td>0</td><td>40</td><td>90</td><td>100</td><td>40</td><td>90</td><td>100</td><td>30</td><td>60</td><td>170</td><td>90</tr>
<tr><th align="left" {{StdDescTable_Heading}}>High-Explosive</th><td>100</td><td>100</td><td>100</td><td>80</td><td>80</td><td>80</td><td>100</td><td>90</td><td>100</td><td>150</td><td>30</td><td>60</td><td>70</td><td>90</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Gauss</th><td>100</td><td>100</td><td>80</td><td>70</td><td>60</td><td>90</td><td>100</td><td>70</td><td>90</td><td>90</td><td>30</td><td>70</td><td>80</td><td>80</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Sonic</th><td>100</td><td>100</td><td>100</td><td>90</td><td>100</td><td>110</td><td>110</td><td>120</td><td>110</td><td>110</td><td>50</td><td>90</td><td>100</td><td>90</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Stun(Freeze)</th><td>100</td><td>100</td><td>100</td><td>100</td><td>100</td><td>100</td><td>100</td><td>110</td><td>100</td><td>110</td><td>110</td><td>90</td><td>100</td><td>90</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Drill</th><td>100</td><td>160</td><td>120</td><td>110</td><td>80</td><td>120</td><td>120</td><td>90</td><td>80</td><td>110</td><td>200</td><td>145</td><td>60</td><td>110</tr>
<tr><th align="left" {{StdDescTable_Heading}}>Electric Shock</th><td>100</td><td>150</td><td>110</td><td>100</td><td>120</td><td>0</td><td>0</td><td>0</td><td>0</td><td>0</td><td>0</td><td>0</td><td>0</td><td>0 </tr></table>
Please note that these are the actual numbers taken directly from the executable, which the game uses. The numbers from the Official Strategy Guide are incorrect. For those interested in changing/hacking the creature damage modifiers, they are located in the Tactical.exe near the end of the file.

The Numbers listed below are a reference to the damage chart above (there are 14 sets of damage modifiers, numbered 0-13). The creature entries listed in the Geoscape.exe have a variable which points to which set of damage modifiers the creature uses.
{| {{StdDescTable}}
|- {{StdDescTable_Heading}}
! Column !! Unit Type(s)
|-
| '''0''' || Terrain.
|-
| '''1''' || Unarmored Soldiers, Civilians, Aquatoids, Zombies.
|-
| '''2''' || Plastic Aqua Armor.
|-
| '''3''' || Ion Armor and Magnetic Ion Armor.
|-
| '''4''' || SWS's and Displacers.
|-
| '''5''' || Deep One.
|-
| '''6''' || Gill Man.
|-
| '''7''' || Tasoth.
|-
| '''8''' || Calcinite.
|-
| '''9''' || Tentaculat.
|-
| '''10''' || Lobsterman.
|-
| '''11''' || Xarquid and Bio-Drone.
|-
| '''12''' || Hallucinoid.
|-
| '''13''' || Triscene.
|}

Note: SWS and Displacer damage modifiers are not shown in the Official Strategy Guide.

[[Category:data tables]]