UFOpaedia - User contributions [en]

Talk:MISSIONS.DAT

2018-07-31T04:11:54Z

Zombie: /* Alien missions data discovered in geoscape.exe [finally ;-)] */

Some questions [Zaimoni: now answered empirically]:
* What is going on with the start time for 0/0 on Research missions? The Jan 1999 one is always 2.5h, but I recently saw an Antarctica Research mission at 3d for 0/0.
* How consistently does the time to the next UFO react to a successful Battlescape game? (I just saw a Retaliation 1/1 go from 7Eh to 136h upon successful completion.)

--[[User:Zaimoni|Zaimoni]], 6:50 Sept 21 2006 CDT

I couldn't understand much of your research but it made me wonder about one question: is it possible to determine the amount of UFO missions and their types that you will see during a month (and also the areas?). Or are those set in a total random fashion?

If so this could be considered as spoilers but it could also be used for an article describing alien strategy on the field manual.

--[[User:Hobbes|Hobbes]] 18:39, 21 September 2006 (PDT)

MISSIONS.DAT is a spoiler, definitely. It stores the time (in 30-minute increments) for all non-Supply scheduled UFOs that have not arrived yet. While it won't tell you all of the UFOs arriving in the month, it will positively ID arrival time, mission, physical type, and race of each one in the queue. I'm in the middle of redocumenting it.

My current conjecture is that the 0..3 sequence indexes the "size" of the UFO. The legacy content just listing ufo-c coordinates is misleading (it seems to be enumerating the visible sequence of ufos), but I want to positively observe the entire sequence of ufo-c/ufo-sub-c pairs before updating.

At all times, the current mission types and areas are in MISSIONS.DAT...except for supply missions. You really want a Hyperwave Decoder covering each alien base you're harvesting. So far, Beginner and Superhuman schedule the same at the beginning of the months after Jan 1999: 1 Terror mission, one non-terror mission. I don't know the criteria for scheduling Retaliation missions. (I've never seen them show up except immediately after Battlescape missions, but that obviously isn't exhaustive.]

Particularly interesting: Battlescape messes with the arrival time of the next mission after the one you're cleaning up on. This needs more careful analysis (e.g., is it just mission completion?)

--[[User:Zaimoni|Zaimoni]], 22:35 Sept 21 2006 CDT

The increase in time to next UFO occurs either (or both) at shootdown, or at the start of the Battlescape mission. Since I used XCOMUtil interceptor with six soldiers for this test, I can't tell which one. No change between the beginning and the end of the Battlescape mission. [But a genuine Terrorship will happen soon enough...that gets a no-crew Interceptor and a full Skyranger.]

--[[User:Zaimoni|Zaimoni]], 23:51 Sept 21 2006 CDT
:After a shootdown, the next UFO for that mission is delayed between 1 and ~9 days ( the formula is 48+RAND()*400 half hours ). A retaliation mission will be scheduled if RAND()*100 < 4*(24-difficultyLevel).
:If RAND()*100 < (50-6*difficultyLevel), the retaliation mission will use the same zone as the shot UFO, else it'll be the zone containing the base the craft in coming from. The first UFO is scheduled in 100 half-hours (the value is taken from the table I speak of later at the bottom of this page).
:[[User:Seb76|Seb76]] 18:56, 12 July 2008 (PDT)
<hr>

I don't think I'll be continuing this savegame, but I just had a Feb 1999 that only generated a new Terror Mission. The other mission...not visible. [I may have messed it up — I did edit the Jan 1999 Terror mission from Europe to Southern Africa.]

--[[User:Zaimoni|Zaimoni]], 10:38 Dec 30 2006 CDT

== Retaliation ==

Zaimoni, I've been thinking about the comment about HWD's activating retaliation missions from the start. Are you able to check the mission types of the first couple of UFOs through mission.dat without editing the HWD stats onto the base? I'm not entirely convinced that retaliation missions are instigated by having a hyperwave decoder (stats or the module).

- [[User:NKF|NKF]]

: Yes, I can check (and have checked) that by hex editor. [It's a moderately different game with total information on arrival times and mission types...much easier to resume after a month or so hiatus.] I haven't tested with a game whose Hyperwave detection was edited.

: I normally save immediately after starting a new game to apply my custom soldier editor to the game. While I'm at it, I check MISSIONS.DAT. I have always gotten two missions: a Research mission in the same region as my starting base, and a terror mission with a decidedly non-uniform random distribution of location that I haven't bothered to try to analyze.

: I'm not sure whether there's a random component to getting a Retalation series scheduled by shooting down the first Research UFO, or whether it's just hypersensitive to some sort of detail. If the series is not significantly interfered with, the base defense mission would happen 2-3 weeks in.

: --[[User:Zaimoni|Zaimoni]], 3:23 Mar 20 2007 CDT

Just ran some quick checks, nothing too intensive.
* Editing hyperwave detection in a hex editor: no obvious effect, but would have to tweak the initial MISSIONS.DAT (move the Terror Act to within range) to be absolutely sure. The game does not transmogrify Research UFOs in real-time; I need to test Terror UFOs.
* Start a new game after abandoning one: race information is not cleared in MISSIONS.DAT, but other information is cleared. In particular, both ufo-c and subufo-c are overwritten to their defaults.

--[[User:Zaimoni|Zaimoni]], 23:11 Apr 11 2007 CDT

'''so''', the question which should be asked:

Is it too difficult to make an editor which changes the sequences? I dunno anything with hex-editors, programming, high level mathematics, etc. It would be interesting to have an opportunity to spawn multiple UFO everyday and not be able to shoot them all down as which is the case for the current mode of EU (and TFTD). The only thing that comes close to something of this current scenario is an inflitration mission where you have 5+ alien ships all at once and not having the capability to deal with them all. I dunno... i just wish having more tweaks to make it harder would be a good thing as opposite to just using editors to dull the technology of xcom to increase difficulty.

Six terror sites at once??? hell yeah! [[User:EsTeR|EsTeR]]

: It should be safe to create Retaliation acts and Terror acts by directly editing MISSIONS.DAT, there will be no internal consistency issues with other files. Editing existing entries in MISSIONS.DAT to other valid entries should be safe (note that not all mission types have been authoritatively mapped). Editing duration should be safe, but problems could happen with invalid races or UFO c/sub-c pairs. Creating other mission types will require counter-editing ACTS.DAT. I haven't specifically checked the behavior of ZONAL.DAT when spawning new acts.

: The ufo-c/ufo-sub-c pair 0/0 is always valid, at least.

: Research, Base, Terror, and Retaliation have fully documented ufo-c/ufo-sub-c pairs. I haven't done any verification at all for Abduction or Infiltration.

: Changing the relative durations between UFOs, time delays incurred when shooting down UFOs, or number of missions spawned per month, requires finding that information first. --[[User:Zaimoni|Zaimoni]], 10:16 Oct 17 2007 CDT

Just a note to add to this section lest I forget, and as late follow up to the notes that re on the page: back when I first got the idea that the first UFO was on a retaliation mission, I did not know that there was a 2% chance for every UFO to generate a retaliation mission. Armed with this knowledge, this is probably the sequence of events that happened to me at the time: I shot down the first UFO, recovered it and then got my base attacked. The 2% might've triggered then. This would very well the impression I had that UFOs could start on retaliation missions. They don't, but they can generate an attack. -[[User:NKF|NKF]] 03:10, 3 June 2010 (EDT)

== Alien missions data discovered in geoscape.exe [finally ;-)] ==

OK guys, here's a big one: alien missions data is located in the executable at offset 0x70E70 (gold edition) ; it starts with these values (all 16bit words):

.data:00470E70 structAlienMission <5, 1, 0, 12Ch>
.data:00470E70 structAlienMission <6, 1, 2, 104h>
.data:00470E70 structAlienMission <7, 2, 4, 12Ch>
.data:00470E70 structAlienMission 5 dup(<0FFFFh, 0FFFFh, 0FFFFh, 0FFFFh>)
...
It goes on for 64x4x2 bytes (7 mission types and possible data for additional 'supply' type mission).

Every mission type has 8 entries consisting of 4 words.
First word is the ship type, second is the number of ship of this type to spawn successively (each uses the same time counter), and 4th correspond to the time counter in [[MISSIONS.DAT]]. 3rd one is unknown for now.

The example below is for research mission: one small scout (type 5), then one medium scout (type 6) and finally 2 large scouts (type 7).
The time counter is calculated like this: time*RAND()+time/2.
Anyone care to hack the binaries to confirm this? [[User:Seb76|Seb76]] 10:58, 9 March 2008 (PDT)

: Time calculation looks good for those UFOs with randomized time (there are a few known exceptions). -- [[User:Zaimoni|Zaimoni]] 10:16 10 March 2008 (CDT)

: It would be very good to locate what controls fixed vs randomized times for the normal missions. -- [[User:Zaimoni|Zaimoni]] 10:59 13 July 2008 (CDT)

The 3rd word of missions is UFO_trajectory_type. It refers into table at address .data:00471070. So there are 10 types of trajectories possible, with maximum 8 waypoints.
.data:00471070 ufo_10_types_52___ dw 5 ; UFO_Waypoint_count
.data:00471070 dw 5, 0, 0, 1, 5, -1, -1, -1; UFO_Waypoint_Site
.data:00471070 dw 4, 3, 1, 1, 2, 0, 0, 0; UFO_Waypoint_Altitude
.data:00471070 dw 100, 74, 28, 47,100, 0, 0, 0; UFO_Waypoint_Speed
.data:00471070 dw 3000 ; Ground_Timer
--[[User:Volutar|Volutar]] 05:59, 14 April 2011 (EDT)

The 3rd "word" is called a ''Mission Plan'' in the dev notes I have. As Volutar mentioned, there are 10 types, and I'll list the internal descriptions here

Plan Description
0 Low level reconnaissance
1 Intense low level reconnaissance
2 Occasional landings
3 Occasional abductions
4 Systematic abductions
5 Reconnaissance for base
6 Establishing base
7 Visit major cities
8 Destroy <nowiki>[X-COM]</nowiki> base
9 Base Supply

--[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 06:10, 31 July 2018 (CEST)

==Clarification pls==

- So all these missions, once started, will continue in the precise sequence no matter what?

:: Yes; only most of these tables have been verified by inspection of the savegame files in a hex editor, however. Infiltration has not. Matching the savegame file behavior against the in-game data Seb76 has located is tricky. -- [[User:Zaimoni|Zaimoni]]

- What about the whole thing with whether it's found the site or not (e.g. Terror Ships finding/not finding a city to raid, Battleships finding/not finding your base)? Does this apply to all missions?

:: The base assault battleships are not on the Retaliation Act sequence, they're controlled by [[XBASES.DAT]]. Reverse-engineering how the Retaliation Act ships find bases hasn't been precisely done yet (don't let the UFOs get too close to the base), mind shielding reduces the range at which a UFO can spot a base.

::: So the two battleships that don't ever spot your base are unrelated to the battleships that come if you're spotted? [[User:magic9mushroom]]

:::: Correct. I've had entire Retaliation Acts cycle without scheduling a base attack battleship, but this was with [[XBASES.DAT]] never flagging a base for retaliation.

:: As for Terror Ships: whether a UFO lands or not, appears to be controlled by its ufo-c/ufo-sub-c indexing. If they have orders to land, they won't have problems finding an appropriate site. -- [[User:Zaimoni|Zaimoni]]

::: So that means that of the two Terror Ship indexes you have listed, only one occurs in any given mission? [[User:magic9mushroom]]

:::: For all act types, the indexes are incremented in strictly increasing order (with all ufo-sub-c indexes run through before the ufo-c index is incremented). It may take more than one hour for a ufo to reach hyperwave detection with incomplete hyperwave coverage. -- [[User:Zaimoni|Zaimoni]]

:::::So are there two Terror Ships per mission or not?

:::::: The separation between Terror Ship 2/0 and Terror Ship 3/0 is a few days, so it's conceptually two missions with one Terror Ship each with the Terror Act. Empirical research into ufo behavior suggests that if they are not shot down, Terror Ship 2/0 never lands, while Terror Ship 3/0 always lands (and gives you a terror site). -- [[User:Zaimoni|Zaimoni]]

- With the infiltration, what does the "it starts again" mean? Does that mean that once an infiltration mission has started in a zone, endless infiltrations will run there until all countries there are infiltrated?

:: Infiltration is the only mission type that loops. It will continue even after all countries in the zone have been infiltrated. Russia is empirically immune to infiltration in all versions higher than DOS 1.0. -- [[User:Zaimoni|Zaimoni]]

::: So what happens at the conclusion of an Infiltration mission after all countries in the zone are infiltrated? Does a country outside the zone get infiltrated? Does no country get infiltrated? [[User:magic9mushroom]]

::::Nothing happens. Was rather fortunate to experience this a few times - and when I ran a no-funding-country scenario where I edited the save and flagged all the countries as withdrawn. Rather amusing to see them infiltrate an already infiltrated country and yield no results. In this case, the only real impact is the area activity points, which the neighbours will notice. -[[User:NKF|NKF]] 05:30, 10 August 2009 (EDT)

- It says the order for infiltrations is Terror ship -> Battleship -> Supply ship -> Battleship, but my own experience contradicts this - I shot down each UFO in an infiltration run, and the sequence was Terror ship -> Supply ship -> Battleship -> Battleship.

:: While Infiltration has not been verified by me in-game yet, the tables all assume that all UFOs in the sequence are detected. This is more interesting if this was with the Hyperwave Decoder. -- [[User:Zaimoni|Zaimoni]], 8:42, 9 August 2009 (CDT)

::: It was with a Hyper-Wave Decoder and I shot down each before the next appeared. [[User:Magic9mushroom|Magic9mushroom]] 04:07, 10 August 2009 (EDT)

:::: All eight are in the executable, in the order specified in MISSIONS.DAT. However, the four mentioned are pretty much "in a row": the sixth should arrive exactly one hour later after the fifth, and so on. That is, you have one hour to shoot down the Terror Ship to delay the three others by ~2 weeks. -- [[User:Zaimoni|Zaimoni]], 9:37, 10 August 2009 (CDT)

::::: Well, it was days between detecting each one. They definitely arrived in the order Terror Ship, Supply Ship, Battleship, Battleship.

:::::: See it in the executable, fixing that now. (Mapping duration from executable to empirical is tricky, as is estimating turning points and landing counts.) -- [[User:Zaimoni|Zaimoni]], 9:37, 10 August 2009 (CDT)

Thanks in advance. [[User:Magic9mushroom|Magic9mushroom]] 04:14, 9 August 2009 (EDT)

I understood what mean third entry in section Alien Data Missions at executable file.
As I said in forum Seeing speeds of USO sub we can determine the mission of this USO sub even without transmission resolver - even in january 2040
Every USO sub in every missions (interdiction, colony, probe and other) have unique speeds and we can determine mission of USO on their speed
And we can determine what amount of times a sub touch down on his mission - because every mission has unique rule for touch down USO subs
And we can determine what amount of time USO Sub will touch down on their mission - because every Sub in every mission has unique and ALWAYS equal amoun of time to touch down (p.s. this time we can see in file Loc.dat)

And third entry - it's index of speeds of sub.

I have table of speeds of all USO subs. Where can locate it?

== Non-scheduled Terror Missions ==

What is it known on terror missions which are NOT in MISSIONS.DAT? At least in TFTD, such missions are, as a rule, on the 1st of each month, 1:00 (are they always ship route attacks?). Saving the game before the attack but after the midnight (1st, 0:00), and next loading and continuing it, always leads to a mission in the same (exact) location, on the same type of the ship, and with the same alien race (or Mixed Crew). Only numbers of particular creatures of a given race can change. So, the mission properties must be stored somewhere between the midnight and 1:00 (when the attack occurs). The game must store this information somewhere, and it is not MISSION.DAT for sure.

Such a first-o'clock alien terror mission does not influence the normal, scheduled alien missions (so, it is even possible to have another terror mission just few hours after the first one, if only the other mission had been scheduled). Where is it stored?

Does a similar phenomenon occur in UFO:EU as well?

[[File:Nstm.zip]] - a set of savegames for tests, the explanation inside.

[[User:Sherlock|Sherlock]] 20:24, 30 January 2013 (EST)

:It's in [[LOC.DAT]]. As in, the terror site already existed before it became visible to you, so you actually saved AFTER the attack started. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 02:02, 31 January 2013 (EST)

== Addresses ==

I'm not great at this sort of thing so I'd like to know if the following is correct. Zaimoni's example, ''"E.g. infiltration(3) in Europe(4) would have the offset 3*8+4*(7*8)=0xF8"'' means the entries are ordered by missiontype*8 + region*56 (respectively from [[ACTS.DAT]] and [[ZONAL.DAT]]) ???

Running that logic through excel I generated the addresses below. I guess they make sense; it could look like what's going on in-game though I don't have any saves where I am dead-certain what missions are running... which is what brought me to this page... :)

{| class="wikitable" style="font-size:90%;"
|-
! Adr.Hex !! Mission
|-
| 0 || Research in North America
|-
| 8 || Harvest in North America
|-
| 10 || Abduction in North America
|-
| 18 || Infiltration in North America
|-
| 20 || Base in North America
|-
| 28 || Terror in North America
|-
| 30 || Retaliation in North America
|-
| 38 || Research in Arctic
|-
| 40 || Harvest in Arctic
|-
| 48 || Abduction in Arctic
|-
| 50 || Infiltration in Arctic
|-
| 58 || Base in Arctic
|-
| 60 || Terror in Arctic
|-
| 68 || Retaliation in Arctic
|-
| 70 || Research in Antarctic
|-
| 78 || Harvest in Antarctic
|-
| 80 || Abduction in Antarctic
|-
| 88 || Infiltration in Antarctic
|-
| 90 || Base in Antarctic
|-
| 98 || Terror in Antarctic
|-
| A0 || Retaliation in Antarctic
|-
| A8 || Research in South America
|-
| B0 || Harvest in South America
|-
| B8 || Abduction in South America
|-
| C0 || Infiltration in South America
|-
| C8 || Base in South America
|-
| D0 || Terror in South America
|-
| D8 || Retaliation in South America
|-
| E0 || Research in Europe
|-
| E8 || Harvest in Europe
|-
| F0 || Abduction in Europe
|-
| F8 || Infiltration in Europe
|-
| 100 || Base in Europe
|-
| 108 || Terror in Europe
|-
| 110 || Retaliation in Europe
|-
| 118 || Research in North Africa
|-
| 120 || Harvest in North Africa
|-
| 128 || Abduction in North Africa
|-
| 130 || Infiltration in North Africa
|-
| 138 || Base in North Africa
|-
| 140 || Terror in North Africa
|-
| 148 || Retaliation in North Africa
|-
| 150 || Research in South Africa
|-
| 158 || Harvest in South Africa
|-
| 160 || Abduction in South Africa
|-
| 168 || Infiltration in South Africa
|-
| 170 || Base in South Africa
|-
| 178 || Terror in South Africa
|-
| 180 || Retaliation in South Africa
|-
| 188 || Research in Central Asia
|-
| 190 || Harvest in Central Asia
|-
| 198 || Abduction in Central Asia
|-
| 1A0 || Infiltration in Central Asia
|-
| 1A8 || Base in Central Asia
|-
| 1B0 || Terror in Central Asia
|-
| 1B8 || Retaliation in Central Asia
|-
| 1C0 || Research in Southeast Asia
|-
| 1C8 || Harvest in Southeast Asia
|-
| 1D0 || Abduction in Southeast Asia
|-
| 1D8 || Infiltration in Southeast Asia
|-
| 1E0 || Base in Southeast Asia
|-
| 1E8 || Terror in Southeast Asia
|-
| 1F0 || Retaliation in Southeast Asia
|-
| 1F8 || Research in Siberia
|-
| 200 || Harvest in Siberia
|-
| 208 || Abduction in Siberia
|-
| 210 || Infiltration in Siberia
|-
| 218 || Base in Siberia
|-
| 220 || Terror in Siberia
|-
| 228 || Retaliation in Siberia
|-
| 230 || Research in Australasia
|-
| 238 || Harvest in Australasia
|-
| 240 || Abduction in Australasia
|-
| 248 || Infiltration in Australasia
|-
| 250 || Base in Australasia
|-
| 258 || Terror in Australasia
|-
| 260 || Retaliation in Australasia
|-
| 268 || Research in Wilderness
|-
| 270 || Harvest in Wilderness
|-
| 278 || Abduction in Wilderness
|-
| 280 || Infiltration in Wilderness
|-
| 288 || Base in Wilderness
|-
| 290 || Terror in Wilderness
|-
| 298 || Retaliation in Wilderness
|}

--[[User:Tlist|Tlist]] ([[User talk:Tlist|talk]]) 13:46, 25 May 2014 (EDT)

Talk:MISSIONS.DAT

2018-07-31T04:10:37Z

Zombie: /* Alien missions data discovered in geoscape.exe [finally ;-)] */

Some questions [Zaimoni: now answered empirically]:
* What is going on with the start time for 0/0 on Research missions? The Jan 1999 one is always 2.5h, but I recently saw an Antarctica Research mission at 3d for 0/0.
* How consistently does the time to the next UFO react to a successful Battlescape game? (I just saw a Retaliation 1/1 go from 7Eh to 136h upon successful completion.)

--[[User:Zaimoni|Zaimoni]], 6:50 Sept 21 2006 CDT

I couldn't understand much of your research but it made me wonder about one question: is it possible to determine the amount of UFO missions and their types that you will see during a month (and also the areas?). Or are those set in a total random fashion?

If so this could be considered as spoilers but it could also be used for an article describing alien strategy on the field manual.

--[[User:Hobbes|Hobbes]] 18:39, 21 September 2006 (PDT)

MISSIONS.DAT is a spoiler, definitely. It stores the time (in 30-minute increments) for all non-Supply scheduled UFOs that have not arrived yet. While it won't tell you all of the UFOs arriving in the month, it will positively ID arrival time, mission, physical type, and race of each one in the queue. I'm in the middle of redocumenting it.

My current conjecture is that the 0..3 sequence indexes the "size" of the UFO. The legacy content just listing ufo-c coordinates is misleading (it seems to be enumerating the visible sequence of ufos), but I want to positively observe the entire sequence of ufo-c/ufo-sub-c pairs before updating.

At all times, the current mission types and areas are in MISSIONS.DAT...except for supply missions. You really want a Hyperwave Decoder covering each alien base you're harvesting. So far, Beginner and Superhuman schedule the same at the beginning of the months after Jan 1999: 1 Terror mission, one non-terror mission. I don't know the criteria for scheduling Retaliation missions. (I've never seen them show up except immediately after Battlescape missions, but that obviously isn't exhaustive.]

Particularly interesting: Battlescape messes with the arrival time of the next mission after the one you're cleaning up on. This needs more careful analysis (e.g., is it just mission completion?)

--[[User:Zaimoni|Zaimoni]], 22:35 Sept 21 2006 CDT

The increase in time to next UFO occurs either (or both) at shootdown, or at the start of the Battlescape mission. Since I used XCOMUtil interceptor with six soldiers for this test, I can't tell which one. No change between the beginning and the end of the Battlescape mission. [But a genuine Terrorship will happen soon enough...that gets a no-crew Interceptor and a full Skyranger.]

--[[User:Zaimoni|Zaimoni]], 23:51 Sept 21 2006 CDT
:After a shootdown, the next UFO for that mission is delayed between 1 and ~9 days ( the formula is 48+RAND()*400 half hours ). A retaliation mission will be scheduled if RAND()*100 < 4*(24-difficultyLevel).
:If RAND()*100 < (50-6*difficultyLevel), the retaliation mission will use the same zone as the shot UFO, else it'll be the zone containing the base the craft in coming from. The first UFO is scheduled in 100 half-hours (the value is taken from the table I speak of later at the bottom of this page).
:[[User:Seb76|Seb76]] 18:56, 12 July 2008 (PDT)
<hr>

I don't think I'll be continuing this savegame, but I just had a Feb 1999 that only generated a new Terror Mission. The other mission...not visible. [I may have messed it up — I did edit the Jan 1999 Terror mission from Europe to Southern Africa.]

--[[User:Zaimoni|Zaimoni]], 10:38 Dec 30 2006 CDT

== Retaliation ==

Zaimoni, I've been thinking about the comment about HWD's activating retaliation missions from the start. Are you able to check the mission types of the first couple of UFOs through mission.dat without editing the HWD stats onto the base? I'm not entirely convinced that retaliation missions are instigated by having a hyperwave decoder (stats or the module).

- [[User:NKF|NKF]]

: Yes, I can check (and have checked) that by hex editor. [It's a moderately different game with total information on arrival times and mission types...much easier to resume after a month or so hiatus.] I haven't tested with a game whose Hyperwave detection was edited.

: I normally save immediately after starting a new game to apply my custom soldier editor to the game. While I'm at it, I check MISSIONS.DAT. I have always gotten two missions: a Research mission in the same region as my starting base, and a terror mission with a decidedly non-uniform random distribution of location that I haven't bothered to try to analyze.

: I'm not sure whether there's a random component to getting a Retalation series scheduled by shooting down the first Research UFO, or whether it's just hypersensitive to some sort of detail. If the series is not significantly interfered with, the base defense mission would happen 2-3 weeks in.

: --[[User:Zaimoni|Zaimoni]], 3:23 Mar 20 2007 CDT

Just ran some quick checks, nothing too intensive.
* Editing hyperwave detection in a hex editor: no obvious effect, but would have to tweak the initial MISSIONS.DAT (move the Terror Act to within range) to be absolutely sure. The game does not transmogrify Research UFOs in real-time; I need to test Terror UFOs.
* Start a new game after abandoning one: race information is not cleared in MISSIONS.DAT, but other information is cleared. In particular, both ufo-c and subufo-c are overwritten to their defaults.

--[[User:Zaimoni|Zaimoni]], 23:11 Apr 11 2007 CDT

'''so''', the question which should be asked:

Is it too difficult to make an editor which changes the sequences? I dunno anything with hex-editors, programming, high level mathematics, etc. It would be interesting to have an opportunity to spawn multiple UFO everyday and not be able to shoot them all down as which is the case for the current mode of EU (and TFTD). The only thing that comes close to something of this current scenario is an inflitration mission where you have 5+ alien ships all at once and not having the capability to deal with them all. I dunno... i just wish having more tweaks to make it harder would be a good thing as opposite to just using editors to dull the technology of xcom to increase difficulty.

Six terror sites at once??? hell yeah! [[User:EsTeR|EsTeR]]

: It should be safe to create Retaliation acts and Terror acts by directly editing MISSIONS.DAT, there will be no internal consistency issues with other files. Editing existing entries in MISSIONS.DAT to other valid entries should be safe (note that not all mission types have been authoritatively mapped). Editing duration should be safe, but problems could happen with invalid races or UFO c/sub-c pairs. Creating other mission types will require counter-editing ACTS.DAT. I haven't specifically checked the behavior of ZONAL.DAT when spawning new acts.

: The ufo-c/ufo-sub-c pair 0/0 is always valid, at least.

: Research, Base, Terror, and Retaliation have fully documented ufo-c/ufo-sub-c pairs. I haven't done any verification at all for Abduction or Infiltration.

: Changing the relative durations between UFOs, time delays incurred when shooting down UFOs, or number of missions spawned per month, requires finding that information first. --[[User:Zaimoni|Zaimoni]], 10:16 Oct 17 2007 CDT

Just a note to add to this section lest I forget, and as late follow up to the notes that re on the page: back when I first got the idea that the first UFO was on a retaliation mission, I did not know that there was a 2% chance for every UFO to generate a retaliation mission. Armed with this knowledge, this is probably the sequence of events that happened to me at the time: I shot down the first UFO, recovered it and then got my base attacked. The 2% might've triggered then. This would very well the impression I had that UFOs could start on retaliation missions. They don't, but they can generate an attack. -[[User:NKF|NKF]] 03:10, 3 June 2010 (EDT)

== Alien missions data discovered in geoscape.exe [finally ;-)] ==

OK guys, here's a big one: alien missions data is located in the executable at offset 0x70E70 (gold edition) ; it starts with these values (all 16bit words):

.data:00470E70 structAlienMission <5, 1, 0, 12Ch>
.data:00470E70 structAlienMission <6, 1, 2, 104h>
.data:00470E70 structAlienMission <7, 2, 4, 12Ch>
.data:00470E70 structAlienMission 5 dup(<0FFFFh, 0FFFFh, 0FFFFh, 0FFFFh>)
...
It goes on for 64x4x2 bytes (7 mission types and possible data for additional 'supply' type mission).

Every mission type has 8 entries consisting of 4 words.
First word is the ship type, second is the number of ship of this type to spawn successively (each uses the same time counter), and 4th correspond to the time counter in [[MISSIONS.DAT]]. 3rd one is unknown for now.

The example below is for research mission: one small scout (type 5), then one medium scout (type 6) and finally 2 large scouts (type 7).
The time counter is calculated like this: time*RAND()+time/2.
Anyone care to hack the binaries to confirm this? [[User:Seb76|Seb76]] 10:58, 9 March 2008 (PDT)

: Time calculation looks good for those UFOs with randomized time (there are a few known exceptions). -- [[User:Zaimoni|Zaimoni]] 10:16 10 March 2008 (CDT)

: It would be very good to locate what controls fixed vs randomized times for the normal missions. -- [[User:Zaimoni|Zaimoni]] 10:59 13 July 2008 (CDT)

The 3rd word of missions is UFO_trajectory_type. It refers into table at address .data:00471070. So there are 10 types of trajectories possible, with maximum 8 waypoints.
.data:00471070 ufo_10_types_52___ dw 5 ; UFO_Waypoint_count
.data:00471070 dw 5, 0, 0, 1, 5, -1, -1, -1; UFO_Waypoint_Site
.data:00471070 dw 4, 3, 1, 1, 2, 0, 0, 0; UFO_Waypoint_Altitude
.data:00471070 dw 100, 74, 28, 47,100, 0, 0, 0; UFO_Waypoint_Speed
.data:00471070 dw 3000 ; Ground_Timer
--[[User:Volutar|Volutar]] 05:59, 14 April 2011 (EDT)

The 3rd "word" is called a ''Mission Plan'' in the dev notes I have. As Volutar mentioned, there are 10 types, and I'll list the internal descriptions here

Plan Description
0 Low level reconnaissance
1 Intense low level reconnaissance
2 Occasional landings
3 Occasional abductions
4 Systematic abductions
5 Reconnaissance for base
6 Establishing base
7 Visit major cities
8 Destroy <nowiki>[X-COM]</nowiki> base
9 Base Supply
--[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 06:10, 31 July 2018 (CEST)

==Clarification pls==

- So all these missions, once started, will continue in the precise sequence no matter what?

:: Yes; only most of these tables have been verified by inspection of the savegame files in a hex editor, however. Infiltration has not. Matching the savegame file behavior against the in-game data Seb76 has located is tricky. -- [[User:Zaimoni|Zaimoni]]

- What about the whole thing with whether it's found the site or not (e.g. Terror Ships finding/not finding a city to raid, Battleships finding/not finding your base)? Does this apply to all missions?

:: The base assault battleships are not on the Retaliation Act sequence, they're controlled by [[XBASES.DAT]]. Reverse-engineering how the Retaliation Act ships find bases hasn't been precisely done yet (don't let the UFOs get too close to the base), mind shielding reduces the range at which a UFO can spot a base.

::: So the two battleships that don't ever spot your base are unrelated to the battleships that come if you're spotted? [[User:magic9mushroom]]

:::: Correct. I've had entire Retaliation Acts cycle without scheduling a base attack battleship, but this was with [[XBASES.DAT]] never flagging a base for retaliation.

:: As for Terror Ships: whether a UFO lands or not, appears to be controlled by its ufo-c/ufo-sub-c indexing. If they have orders to land, they won't have problems finding an appropriate site. -- [[User:Zaimoni|Zaimoni]]

::: So that means that of the two Terror Ship indexes you have listed, only one occurs in any given mission? [[User:magic9mushroom]]

:::: For all act types, the indexes are incremented in strictly increasing order (with all ufo-sub-c indexes run through before the ufo-c index is incremented). It may take more than one hour for a ufo to reach hyperwave detection with incomplete hyperwave coverage. -- [[User:Zaimoni|Zaimoni]]

:::::So are there two Terror Ships per mission or not?

:::::: The separation between Terror Ship 2/0 and Terror Ship 3/0 is a few days, so it's conceptually two missions with one Terror Ship each with the Terror Act. Empirical research into ufo behavior suggests that if they are not shot down, Terror Ship 2/0 never lands, while Terror Ship 3/0 always lands (and gives you a terror site). -- [[User:Zaimoni|Zaimoni]]

- With the infiltration, what does the "it starts again" mean? Does that mean that once an infiltration mission has started in a zone, endless infiltrations will run there until all countries there are infiltrated?

:: Infiltration is the only mission type that loops. It will continue even after all countries in the zone have been infiltrated. Russia is empirically immune to infiltration in all versions higher than DOS 1.0. -- [[User:Zaimoni|Zaimoni]]

::: So what happens at the conclusion of an Infiltration mission after all countries in the zone are infiltrated? Does a country outside the zone get infiltrated? Does no country get infiltrated? [[User:magic9mushroom]]

::::Nothing happens. Was rather fortunate to experience this a few times - and when I ran a no-funding-country scenario where I edited the save and flagged all the countries as withdrawn. Rather amusing to see them infiltrate an already infiltrated country and yield no results. In this case, the only real impact is the area activity points, which the neighbours will notice. -[[User:NKF|NKF]] 05:30, 10 August 2009 (EDT)

- It says the order for infiltrations is Terror ship -> Battleship -> Supply ship -> Battleship, but my own experience contradicts this - I shot down each UFO in an infiltration run, and the sequence was Terror ship -> Supply ship -> Battleship -> Battleship.

:: While Infiltration has not been verified by me in-game yet, the tables all assume that all UFOs in the sequence are detected. This is more interesting if this was with the Hyperwave Decoder. -- [[User:Zaimoni|Zaimoni]], 8:42, 9 August 2009 (CDT)

::: It was with a Hyper-Wave Decoder and I shot down each before the next appeared. [[User:Magic9mushroom|Magic9mushroom]] 04:07, 10 August 2009 (EDT)

:::: All eight are in the executable, in the order specified in MISSIONS.DAT. However, the four mentioned are pretty much "in a row": the sixth should arrive exactly one hour later after the fifth, and so on. That is, you have one hour to shoot down the Terror Ship to delay the three others by ~2 weeks. -- [[User:Zaimoni|Zaimoni]], 9:37, 10 August 2009 (CDT)

::::: Well, it was days between detecting each one. They definitely arrived in the order Terror Ship, Supply Ship, Battleship, Battleship.

:::::: See it in the executable, fixing that now. (Mapping duration from executable to empirical is tricky, as is estimating turning points and landing counts.) -- [[User:Zaimoni|Zaimoni]], 9:37, 10 August 2009 (CDT)

Thanks in advance. [[User:Magic9mushroom|Magic9mushroom]] 04:14, 9 August 2009 (EDT)

I understood what mean third entry in section Alien Data Missions at executable file.
As I said in forum Seeing speeds of USO sub we can determine the mission of this USO sub even without transmission resolver - even in january 2040
Every USO sub in every missions (interdiction, colony, probe and other) have unique speeds and we can determine mission of USO on their speed
And we can determine what amount of times a sub touch down on his mission - because every mission has unique rule for touch down USO subs
And we can determine what amount of time USO Sub will touch down on their mission - because every Sub in every mission has unique and ALWAYS equal amoun of time to touch down (p.s. this time we can see in file Loc.dat)

And third entry - it's index of speeds of sub.

I have table of speeds of all USO subs. Where can locate it?

== Non-scheduled Terror Missions ==

What is it known on terror missions which are NOT in MISSIONS.DAT? At least in TFTD, such missions are, as a rule, on the 1st of each month, 1:00 (are they always ship route attacks?). Saving the game before the attack but after the midnight (1st, 0:00), and next loading and continuing it, always leads to a mission in the same (exact) location, on the same type of the ship, and with the same alien race (or Mixed Crew). Only numbers of particular creatures of a given race can change. So, the mission properties must be stored somewhere between the midnight and 1:00 (when the attack occurs). The game must store this information somewhere, and it is not MISSION.DAT for sure.

Such a first-o'clock alien terror mission does not influence the normal, scheduled alien missions (so, it is even possible to have another terror mission just few hours after the first one, if only the other mission had been scheduled). Where is it stored?

Does a similar phenomenon occur in UFO:EU as well?

[[File:Nstm.zip]] - a set of savegames for tests, the explanation inside.

[[User:Sherlock|Sherlock]] 20:24, 30 January 2013 (EST)

:It's in [[LOC.DAT]]. As in, the terror site already existed before it became visible to you, so you actually saved AFTER the attack started. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 02:02, 31 January 2013 (EST)

== Addresses ==

I'm not great at this sort of thing so I'd like to know if the following is correct. Zaimoni's example, ''"E.g. infiltration(3) in Europe(4) would have the offset 3*8+4*(7*8)=0xF8"'' means the entries are ordered by missiontype*8 + region*56 (respectively from [[ACTS.DAT]] and [[ZONAL.DAT]]) ???

Running that logic through excel I generated the addresses below. I guess they make sense; it could look like what's going on in-game though I don't have any saves where I am dead-certain what missions are running... which is what brought me to this page... :)

{| class="wikitable" style="font-size:90%;"
|-
! Adr.Hex !! Mission
|-
| 0 || Research in North America
|-
| 8 || Harvest in North America
|-
| 10 || Abduction in North America
|-
| 18 || Infiltration in North America
|-
| 20 || Base in North America
|-
| 28 || Terror in North America
|-
| 30 || Retaliation in North America
|-
| 38 || Research in Arctic
|-
| 40 || Harvest in Arctic
|-
| 48 || Abduction in Arctic
|-
| 50 || Infiltration in Arctic
|-
| 58 || Base in Arctic
|-
| 60 || Terror in Arctic
|-
| 68 || Retaliation in Arctic
|-
| 70 || Research in Antarctic
|-
| 78 || Harvest in Antarctic
|-
| 80 || Abduction in Antarctic
|-
| 88 || Infiltration in Antarctic
|-
| 90 || Base in Antarctic
|-
| 98 || Terror in Antarctic
|-
| A0 || Retaliation in Antarctic
|-
| A8 || Research in South America
|-
| B0 || Harvest in South America
|-
| B8 || Abduction in South America
|-
| C0 || Infiltration in South America
|-
| C8 || Base in South America
|-
| D0 || Terror in South America
|-
| D8 || Retaliation in South America
|-
| E0 || Research in Europe
|-
| E8 || Harvest in Europe
|-
| F0 || Abduction in Europe
|-
| F8 || Infiltration in Europe
|-
| 100 || Base in Europe
|-
| 108 || Terror in Europe
|-
| 110 || Retaliation in Europe
|-
| 118 || Research in North Africa
|-
| 120 || Harvest in North Africa
|-
| 128 || Abduction in North Africa
|-
| 130 || Infiltration in North Africa
|-
| 138 || Base in North Africa
|-
| 140 || Terror in North Africa
|-
| 148 || Retaliation in North Africa
|-
| 150 || Research in South Africa
|-
| 158 || Harvest in South Africa
|-
| 160 || Abduction in South Africa
|-
| 168 || Infiltration in South Africa
|-
| 170 || Base in South Africa
|-
| 178 || Terror in South Africa
|-
| 180 || Retaliation in South Africa
|-
| 188 || Research in Central Asia
|-
| 190 || Harvest in Central Asia
|-
| 198 || Abduction in Central Asia
|-
| 1A0 || Infiltration in Central Asia
|-
| 1A8 || Base in Central Asia
|-
| 1B0 || Terror in Central Asia
|-
| 1B8 || Retaliation in Central Asia
|-
| 1C0 || Research in Southeast Asia
|-
| 1C8 || Harvest in Southeast Asia
|-
| 1D0 || Abduction in Southeast Asia
|-
| 1D8 || Infiltration in Southeast Asia
|-
| 1E0 || Base in Southeast Asia
|-
| 1E8 || Terror in Southeast Asia
|-
| 1F0 || Retaliation in Southeast Asia
|-
| 1F8 || Research in Siberia
|-
| 200 || Harvest in Siberia
|-
| 208 || Abduction in Siberia
|-
| 210 || Infiltration in Siberia
|-
| 218 || Base in Siberia
|-
| 220 || Terror in Siberia
|-
| 228 || Retaliation in Siberia
|-
| 230 || Research in Australasia
|-
| 238 || Harvest in Australasia
|-
| 240 || Abduction in Australasia
|-
| 248 || Infiltration in Australasia
|-
| 250 || Base in Australasia
|-
| 258 || Terror in Australasia
|-
| 260 || Retaliation in Australasia
|-
| 268 || Research in Wilderness
|-
| 270 || Harvest in Wilderness
|-
| 278 || Abduction in Wilderness
|-
| 280 || Infiltration in Wilderness
|-
| 288 || Base in Wilderness
|-
| 290 || Terror in Wilderness
|-
| 298 || Retaliation in Wilderness
|}

--[[User:Tlist|Tlist]] ([[User talk:Tlist|talk]]) 13:46, 25 May 2014 (EDT)

Alien Supply

2018-07-31T04:10:26Z

Zombie: Added info about how long a supply ships stays landed.

[[Image:Alien Supply.png|thumb|right|Alien Supply mission type.]]
Once an Alien base is constructed, it is resupplied on a regular basis (approximately every 4 days + 4 hours - or 100 hours) by special [[Supply ship|supply vessels]]. If one of these vessels is detected while landing then it is certain that an Alien base is nearby. Once landed, Supply Ships remain on the ground for 33⅓ hours or 1 day, 9 hours and 20 minutes.

Aliens do not directly [[Scoring#Alien_Scoring|score]] for this mission.

Note that supply ships on supply missions are always at a speed that makes them impossible to shoot down by [[Interceptor]]s, even shortly before landing or after taking off. This means they can only be attacked on the ground unless new aircraft are researched and built. But because supply ships always land, it would be a waste of [[Elerium]] to shoot them down. Your new aircraft will need some for the interception, yet the Elerium in the supply ship [[UFO_Crash_Recovery#Supply_Ship|is usually destroyed]] by shooting it down.

Piracy time. You may want to let the Alien base exist, just for millions of dollars plundered from the Supply "Blimps". Arrrrrr, avast ye Space-Lubbers!

==See Also==
[[Base Farming]]
{{Alien Missions Navbar}}
[[Category:Research (EU)]]
[[Category:Enemy Unknown/UFO Defense]]

MISSIONS.DAT

2018-07-31T03:27:19Z

Zombie: /* Retaliation */ From what I can gather, all the ufo times are 100x30min=3000min=50hr. Need to double check against executable yet.

contains counters and race info on the ongoing acts. At the start of the game (beginner level) research in your home zone and terror in a random zone is initiated. After that each new month you will get two new missions, one of which is a terror mission (beginner level).

==Structure of a mission entry==

Each mission has 4 words. With 7 acts on 12 zones these are 672 bytes. E.g. infiltration(3) in Europe(4) would have the offset 3*8+4*(7*8)=0xF8.

offset meaning
0 ufo-counter on the ufos within the mission (FFFF, the mission is not active)
2 sub-ufo-counter used for some missions
4 time-counter, 30 minutes to next ufo
6 alien race of mission

The race number can be looked up in [[ENGLISH.DAT]] / [[ENGLISH.DAT (TFTD)|(TFTD)]], entries 466-476:
EU TFTD
0 Sectoid Aquatoid
1 Snakeman Gill Man
2 Ethereal Lobster Man
3 Muton Tasoth
4 Floater Calcinite
5 Celatid Deep One
6 Silacoid Bio-Drone
7 Chryssalid Tentaculat
8 Reaper Triscene
9 Sectopod Hallucinoid
10 Cyberdisc Xarquid

==Timetable of a mission==

When a mission starts, the ufo-counter is set to 0 and the time-counter to some act-depending time. The time-count is reduced every 30 minutes. When 0, an ufo will appear, the ufo-counter (or the sub-counter on some mission) will be increased and a new random time-counter for the new ufo will be set.

===Note on the timing===

Battlescape missions do not affect the scheduling of future UFOs.

UFO appearances are established with a base time period to which a random amount of time derived from the base time is added. The effect is that a UFO arrival will be scheduled 50-150% of the base time. When the mission is created, the first UFO in the mission is spawned when the timer reaches zero. Then the mission entry details are set for the next the next UFO in line and the timer begins counting down again.

Shooting down a UFO will immediately add 24~224 hours (1~9 days) to the timer for the next UFO in that mission.

A time followed by * denotes an exact non-randomized time of arrival.

===Research===

ufo-c time-c ufo-type
0/0 150h s.Scout (start of game Research mission is 2.5h*. This is for later ones)
1/0 130h m.Scout
2/0 150h l.Scout
2/1 150h l.Scout

===Harvest===
ufo-c time-c ufo-type
0/0 130h s.Scout
1/0 130h s.Scout
2/0 100h m.Scout
3/0 130h l.Scout
4/0 150h l.Scout
5/0 50h Harvester
6/0 12.5h Harvester
7/0 25h Battleship

===Abduction===
ufo-c time-c ufo-type
0/0 250h s.Scout
1/0 300h m.Scout
2/0 150h l.Scout
3/0 150h Abductor
4/0 1h Abductor
4/1 1h Abductor

===Infiltration===
ufo-c time-c ufo-type
0/0 275h s.Scout
1/0 250h m.Scout
2/0 230h m.Scout
3/0 150h l.Scout
4/0 1h l.Scout
5/0 1h Terrorship
6/0 1h Supply
7/0 1h Battleship
7/1 1h Battleship

===Base===
ufo-c time-c ufo-type
0/0 225h s.Scout
1/0 250h m.Scout
2/0 1h l.Scout
3/0 1h Supply
3/1 1h Supply
4/0 1h Battleship

===Terror===
ufo-c time-c ufo-type
0 250h m.Scout
1 160h l.Scout
2 200h Terrorship
3 150h Terrorship

Landing sites of Terrorships are terror missions, not ground assault missions. Your radars don't want to track a Terrorship after it drops off its cargo.

sub-ufo-c is empirically always 0 for Terror acts.

===Retaliation===
ufo-c time-c ufo-type
0/0 50h s.Scout
1/0 50h m.Scout
1/1 50h* m.Scout (add 146.5h* if 1/0 shot down at first turning point)
2/0 50h* l.Scout (add 3d if 1/1 shot down at first turning point)
2/1 50h l.Scout
2/2 50h l.Scout (Not always...finally confirmed it could happen, no idea what factors control this one's existence.)
3/0 50h Battleship
3/1 50h Battleship

This mission only relates to the aliens attempting to find an unknown XCOM base in a zone. Once the location of a base is known to the aliens, a special routine in the daily activities section generates the battleship that will attack the base.

A retaliation mission is possibly generated after a successful interception. The zone the mission is set will be either the location of the interception or the zone of the base from which the interceptor was launched. The random chance of a mission being generated and the chance of which zone is selected is affected by the difficulty level of the game.

After a certain point in research or after about 9 months of game time, retaliation missions are automatically generated for each zone that contains an XCOM base at the beginning of each game month.

==See Also==
* [[ACTS.DAT]] - Contains actions the Aliens will embark on
* [[ALIEN.DAT]] - Contains alien activity for graphs
* [[ZONAL.DAT]] - Contains priorities for alien activities
* [[UFO Flight Patterns]]
* [[Game Files]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

MISSIONS.DAT

2018-07-31T03:15:34Z

Zombie: /* Base */ Some changes to times. Need to check against executable yet.

contains counters and race info on the ongoing acts. At the start of the game (beginner level) research in your home zone and terror in a random zone is initiated. After that each new month you will get two new missions, one of which is a terror mission (beginner level).

==Structure of a mission entry==

Each mission has 4 words. With 7 acts on 12 zones these are 672 bytes. E.g. infiltration(3) in Europe(4) would have the offset 3*8+4*(7*8)=0xF8.

offset meaning
0 ufo-counter on the ufos within the mission (FFFF, the mission is not active)
2 sub-ufo-counter used for some missions
4 time-counter, 30 minutes to next ufo
6 alien race of mission

The race number can be looked up in [[ENGLISH.DAT]] / [[ENGLISH.DAT (TFTD)|(TFTD)]], entries 466-476:
EU TFTD
0 Sectoid Aquatoid
1 Snakeman Gill Man
2 Ethereal Lobster Man
3 Muton Tasoth
4 Floater Calcinite
5 Celatid Deep One
6 Silacoid Bio-Drone
7 Chryssalid Tentaculat
8 Reaper Triscene
9 Sectopod Hallucinoid
10 Cyberdisc Xarquid

==Timetable of a mission==

When a mission starts, the ufo-counter is set to 0 and the time-counter to some act-depending time. The time-count is reduced every 30 minutes. When 0, an ufo will appear, the ufo-counter (or the sub-counter on some mission) will be increased and a new random time-counter for the new ufo will be set.

===Note on the timing===

Battlescape missions do not affect the scheduling of future UFOs.

UFO appearances are established with a base time period to which a random amount of time derived from the base time is added. The effect is that a UFO arrival will be scheduled 50-150% of the base time. When the mission is created, the first UFO in the mission is spawned when the timer reaches zero. Then the mission entry details are set for the next the next UFO in line and the timer begins counting down again.

Shooting down a UFO will immediately add 24~224 hours (1~9 days) to the timer for the next UFO in that mission.

A time followed by * denotes an exact non-randomized time of arrival.

===Research===

ufo-c time-c ufo-type
0/0 150h s.Scout (start of game Research mission is 2.5h*. This is for later ones)
1/0 130h m.Scout
2/0 150h l.Scout
2/1 150h l.Scout

===Harvest===
ufo-c time-c ufo-type
0/0 130h s.Scout
1/0 130h s.Scout
2/0 100h m.Scout
3/0 130h l.Scout
4/0 150h l.Scout
5/0 50h Harvester
6/0 12.5h Harvester
7/0 25h Battleship

===Abduction===
ufo-c time-c ufo-type
0/0 250h s.Scout
1/0 300h m.Scout
2/0 150h l.Scout
3/0 150h Abductor
4/0 1h Abductor
4/1 1h Abductor

===Infiltration===
ufo-c time-c ufo-type
0/0 275h s.Scout
1/0 250h m.Scout
2/0 230h m.Scout
3/0 150h l.Scout
4/0 1h l.Scout
5/0 1h Terrorship
6/0 1h Supply
7/0 1h Battleship
7/1 1h Battleship

===Base===
ufo-c time-c ufo-type
0/0 225h s.Scout
1/0 250h m.Scout
2/0 1h l.Scout
3/0 1h Supply
3/1 1h Supply
4/0 1h Battleship

===Terror===
ufo-c time-c ufo-type
0 250h m.Scout
1 160h l.Scout
2 200h Terrorship
3 150h Terrorship

Landing sites of Terrorships are terror missions, not ground assault missions. Your radars don't want to track a Terrorship after it drops off its cargo.

sub-ufo-c is empirically always 0 for Terror acts.

===Retaliation===
ufo-c time-c ufo-type
0/0 50h* s.Scout
1/0 ? m.Scout
1/1 32h* m.Scout (add 146.5h* if 1/0 shot down at first turning point)
2/0 52h* l.Scout (add 3d if 1/1 shot down at first turning point)
2/1 ? l.Scout
2/2 3d l.Scout (Not always...finally confirmed it could happen, no idea what factors control this one's existence.)
3/0 2d Battleship
3/1 2d Battleship

This mission only relates to the aliens attempting to find an unknown XCOM base in a zone. Once the location of a base is known to the aliens, a special routine in the daily activities section generates the battleship that will attack the base.

A retaliation mission is possibly generated after a successful interception. The zone the mission is set will be either the location of the interception or the zone of the base from which the interceptor was launched. The random chance of a mission being generated and the chance of which zone is selected is affected by the difficulty level of the game.

After a certain point in research or after about 9 months of game time, retaliation missions are automatically generated for each zone that contains an XCOM base at the beginning of each game month.

==See Also==
* [[ACTS.DAT]] - Contains actions the Aliens will embark on
* [[ALIEN.DAT]] - Contains alien activity for graphs
* [[ZONAL.DAT]] - Contains priorities for alien activities
* [[UFO Flight Patterns]]
* [[Game Files]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

MISSIONS.DAT

2018-07-31T02:50:02Z

Zombie: /* Terror */ Added more exact times. Hope these are correct, need to double check against executable yet.

contains counters and race info on the ongoing acts. At the start of the game (beginner level) research in your home zone and terror in a random zone is initiated. After that each new month you will get two new missions, one of which is a terror mission (beginner level).

==Structure of a mission entry==

Each mission has 4 words. With 7 acts on 12 zones these are 672 bytes. E.g. infiltration(3) in Europe(4) would have the offset 3*8+4*(7*8)=0xF8.

offset meaning
0 ufo-counter on the ufos within the mission (FFFF, the mission is not active)
2 sub-ufo-counter used for some missions
4 time-counter, 30 minutes to next ufo
6 alien race of mission

The race number can be looked up in [[ENGLISH.DAT]] / [[ENGLISH.DAT (TFTD)|(TFTD)]], entries 466-476:
EU TFTD
0 Sectoid Aquatoid
1 Snakeman Gill Man
2 Ethereal Lobster Man
3 Muton Tasoth
4 Floater Calcinite
5 Celatid Deep One
6 Silacoid Bio-Drone
7 Chryssalid Tentaculat
8 Reaper Triscene
9 Sectopod Hallucinoid
10 Cyberdisc Xarquid

==Timetable of a mission==

When a mission starts, the ufo-counter is set to 0 and the time-counter to some act-depending time. The time-count is reduced every 30 minutes. When 0, an ufo will appear, the ufo-counter (or the sub-counter on some mission) will be increased and a new random time-counter for the new ufo will be set.

===Note on the timing===

Battlescape missions do not affect the scheduling of future UFOs.

UFO appearances are established with a base time period to which a random amount of time derived from the base time is added. The effect is that a UFO arrival will be scheduled 50-150% of the base time. When the mission is created, the first UFO in the mission is spawned when the timer reaches zero. Then the mission entry details are set for the next the next UFO in line and the timer begins counting down again.

Shooting down a UFO will immediately add 24~224 hours (1~9 days) to the timer for the next UFO in that mission.

A time followed by * denotes an exact non-randomized time of arrival.

===Research===

ufo-c time-c ufo-type
0/0 150h s.Scout (start of game Research mission is 2.5h*. This is for later ones)
1/0 130h m.Scout
2/0 150h l.Scout
2/1 150h l.Scout

===Harvest===
ufo-c time-c ufo-type
0/0 130h s.Scout
1/0 130h s.Scout
2/0 100h m.Scout
3/0 130h l.Scout
4/0 150h l.Scout
5/0 50h Harvester
6/0 12.5h Harvester
7/0 25h Battleship

===Abduction===
ufo-c time-c ufo-type
0/0 250h s.Scout
1/0 300h m.Scout
2/0 150h l.Scout
3/0 150h Abductor
4/0 1h Abductor
4/1 1h Abductor

===Infiltration===
ufo-c time-c ufo-type
0/0 275h s.Scout
1/0 250h m.Scout
2/0 230h m.Scout
3/0 150h l.Scout
4/0 1h l.Scout
5/0 1h Terrorship
6/0 1h Supply
7/0 1h Battleship
7/1 1h Battleship

===Base===
ufo-c time-c ufo-type
0/0 1w s.Scout
1/0 1w m.Scout
2/0 1w l.Scout
3/0 1.5h* Supply
3/1 1.5h* Supply
4/0 0.5h* Battleship

===Terror===
ufo-c time-c ufo-type
0 250h m.Scout
1 160h l.Scout
2 200h Terrorship
3 150h Terrorship

Landing sites of Terrorships are terror missions, not ground assault missions. Your radars don't want to track a Terrorship after it drops off its cargo.

sub-ufo-c is empirically always 0 for Terror acts.

===Retaliation===
ufo-c time-c ufo-type
0/0 50h* s.Scout
1/0 ? m.Scout
1/1 32h* m.Scout (add 146.5h* if 1/0 shot down at first turning point)
2/0 52h* l.Scout (add 3d if 1/1 shot down at first turning point)
2/1 ? l.Scout
2/2 3d l.Scout (Not always...finally confirmed it could happen, no idea what factors control this one's existence.)
3/0 2d Battleship
3/1 2d Battleship

This mission only relates to the aliens attempting to find an unknown XCOM base in a zone. Once the location of a base is known to the aliens, a special routine in the daily activities section generates the battleship that will attack the base.

A retaliation mission is possibly generated after a successful interception. The zone the mission is set will be either the location of the interception or the zone of the base from which the interceptor was launched. The random chance of a mission being generated and the chance of which zone is selected is affected by the difficulty level of the game.

After a certain point in research or after about 9 months of game time, retaliation missions are automatically generated for each zone that contains an XCOM base at the beginning of each game month.

==See Also==
* [[ACTS.DAT]] - Contains actions the Aliens will embark on
* [[ALIEN.DAT]] - Contains alien activity for graphs
* [[ZONAL.DAT]] - Contains priorities for alien activities
* [[UFO Flight Patterns]]
* [[Game Files]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

Alien Supply

2018-07-31T02:18:10Z

Zombie: Formatting.

[[Image:Alien Supply.png|thumb|right|Alien Supply mission type.]]
Once an Alien base is constructed, it is resupplied on a regular basis (approximately every 4 days + 4 hours - or 100 hours) by special [[Supply ship|supply vessels]]. If one of these vessels is detected while landing then it is certain that an Alien base is nearby.

Aliens do not directly [[Scoring#Alien_Scoring|score]] for this mission.

Note that supply ships on supply missions are always at a speed that makes them impossible to shoot down by [[Interceptor]]s, even shortly before landing or after taking off. This means they can only be attacked on the ground unless new aircraft are researched and built. But because supply ships always land, it would be a waste of [[Elerium]] to shoot them down. Your new aircraft will need some for the interception, yet the Elerium in the supply ship [[UFO_Crash_Recovery#Supply_Ship|is usually destroyed]] by shooting it down.

Piracy time. You may want to let the Alien base exist, just for millions of dollars plundered from the Supply "Blimps". Arrrrrr, avast ye Space-Lubbers!

==See Also==
[[Base Farming]]
{{Alien Missions Navbar}}
[[Category:Research (EU)]]
[[Category:Enemy Unknown/UFO Defense]]

Alien Supply

2018-07-31T02:17:27Z

Zombie: Added some info on duration between supply ship missions.

[[Image:Alien Supply.png|thumb|right|Alien Supply mission type.]]
Once an Alien base is constructed, it is resupplied on a regular basis (approximately every 4days, 4 hours - or 100 hours) by special [[Supply ship|supply vessels]]. If one of these vessels is detected while landing then it is certain that an Alien base is nearby.

Aliens do not directly [[Scoring#Alien_Scoring|score]] for this mission.

Note that supply ships on supply missions are always at a speed that makes them impossible to shoot down by [[Interceptor]]s, even shortly before landing or after taking off. This means they can only be attacked on the ground unless new aircraft are researched and built. But because supply ships always land, it would be a waste of [[Elerium]] to shoot them down. Your new aircraft will need some for the interception, yet the Elerium in the supply ship [[UFO_Crash_Recovery#Supply_Ship|is usually destroyed]] by shooting it down.

Piracy time. You may want to let the Alien base exist, just for millions of dollars plundered from the Supply "Blimps". Arrrrrr, avast ye Space-Lubbers!

==See Also==
[[Base Farming]]
{{Alien Missions Navbar}}
[[Category:Research (EU)]]
[[Category:Enemy Unknown/UFO Defense]]

MediaWiki:Sidebar

2018-02-22T06:39:04Z

Zombie: Updated link

Incendiary

2017-12-10T20:36:43Z

Zombie: /* Light */ Obstacles can hide in dark corners of a map? ;)

[[Image:Fire_ground.gif|Ground Fire Animation]] [[Image:Fire_unit.gif|Unit Fire Animation]]

'''[[Incendiary]]''' (IN) ammunition creates a large area of '''fire''' on the [[battlescape]] equal to its [[#Blast Diameter|blast diameter]]. Incendiary rounds will burn for two turns on non-flammable terrain. Flammable terrain will burn for longer, and the fire is likely to spread to any adjacent flammable tiles. Aliens and unarmored X-COM agents can catch fire as well.

Incendiary rounds do very little direct damage -- between 0 and 10 points per hit -- but continue to do damage every turn that a unit is in fire or on fire. Due to the "[[Known_Bugs#Funky_Fire|funky fire]]" bug, units in or on fire will also take damage every time an incendiary round goes of ''anywhere'' on the Battlescape.

== Source ==
Incendiary rounds are available for the following weapons:

*[[Auto-Cannon]]
*[[Heavy Cannon]]
*[[Rocket Launcher]]

Some tiles may already be on fire at the start of the mission if the [[UFO Crash Recovery|UFO crashed]].

== Blast Diameter ==

*Auto-Cannon incendiary rounds have a blast diameter of 5 tiles; note that the southern tip of the "diamond" will always be missing.
*Heavy Cannon incendiary rounds have a blast diameter of 7 tiles.
*Incendiary rockets have a blast diameter of 9 tiles.

X
X XXXXXXX
X XXXXX XXXXXXX
XXX XXXXX XXXXXXX
XXXXX XXXXXXX XXXXXXXXX
XXX XXXXX XXXXXXX
X XXXXX XXXXXXX
X XXXXXXX
X

AC-IN HC-IN RL-IN

==Smoke==
[[Image:Smoke1.gif]] [[Image:Smoke2.gif]] [[Image:Smoke3.gif]]
A burning fire can also be used as an impromptu smoke screen. No smoke appears immediately, but smoke will appear outside the edges of the fire, as the fire slowly spreads in subsequent turns. The smoke begins on the first turn after the turn the incendiary round is fired. The smoke will spread vertically (upwards) as well as laterally. Smoke can block [[Line_of_sight|line of sight]].

==Light==
[[File:FlarePattern.png|thumb|right|A single square of fire will illuminate the area within the grey line.]]
Fire not only damages obstacles and aliens hiding in dark corners of the map, but also illuminates the area for several turns. This is especially useful during [[Night Missions]].

Any tile on fire will provide illumination within a 9 tile radius. A large patch of fire will illuminate everything within 9 tiles of the outer edge of the fire. Curiously, aliens on fire do not provide illumination. Maybe they're [http://firecritic.com/2010/12/firefighters-guide-to-invisible-fire-otherwise-known-as-ethanol-fires/ made of ethanol] or something.

==Damage==
<div style="color:red;">Incendiary damage mechanics are not fully understood and are being re-investigated by [[User:Zombie|Zombie]]. The information below is part of the picture but not the completely accurate picture. Treat with caution! More discussion is on the [[Talk:Incendiary|Talk page]].</div>

* Brush and wood on fire will eventually be consumed, leaving a flat scorched-earth [[MCD|tile]].

* If a [[Zombie]] is killed by the explosive impact of any form of Incendiary munitions, the [[Chryssalid]] larva will be burnt up instead of hatching. However, Zombies have high [[Alien Stats|hit points]] and will have to be near death to be killed by an IN round, per se.

* UFO interiors and dropped items are fireproof, even if their owners aren't. Silverblade recommends combining this fact with the diagonal wall bug and an incendiary rocket to roast them in the shell.

* Damage caused by fire does not alter [[Morale]] level.

* '''All''' forms of manufactured X-COM armor will completely block the effects of fire -- including direct hits from incendiary rounds. Soldiers not wearing armor take [[Health]] damage.

* '''Soldiers wearing armour, if wounded, can die from spreading fire.''' Apparently if the damage the fire would inflict exceeds the soldier's remaining [[health]], the soldier will die. If the damage is not enough to kill the soldier that turn, no damage will be inflicted. This bug only applies to ''spreading'' fire, and will not affect a wounded soldier already standing in fire.

* Certain creatures take increased or decreased [[Damage#Damage_Modifiers|damage]] from incendiary rounds:
**More Vulnerable:
***170% - [[Reaper]]
**Less Vulnerable:
***80% - Chryssalid
***70% - [[Ethereal]], [[Snakeman]]
***40% - [[Heavy Weapons Platforms|Tanks/Hovertanks]]
*** 0% - [[Silacoid]] (rocks don't burn!)

* Initial "impact" damage from incendiary ammunition is either for no points (unit does not catch fire), or between 5-10 points (unit catches fire). Since the distribution is randomly chosen from the set [ 0, 5, 6, 7, 8, 9, 10 ] (seven values), the probability of remaining unharmed is 14% (1/7), while there is an 86% chance (6/7) a unit will take some damage. The average damage is 6.4.

* Units standing in a blaze (as opposed to being on fire themselves) will receive between 1-12 damage points, most likely determined by the flammability rating of their tile ([[MCD]] offset 45). The chance of catching fire is determined by an if-then statement: IF Random(100)<40*Damage Modifier/100 THEN Catch Fire. So for example, a normal unarmored soldier (with a damage modifier to IN=100) has a probability of catching fire of: Random(100)<40*100/100 = Random(100)<40 which means that rookie will catch fire 40% of the time. From a previous 6000+ trial conducted by [[User:Zombie|Zombie]] soldiers have a 33% chance of catching fire. It's unknown why these numbers don't match, but it's possible the sample size was still too small.

* Once lit, units burn for a slightly random amount of time, taking 5-10 damage points each turn. (If units fall unconscious, they do not continue to burn.) Thus the average total damage is 21.5 points (3 x 7.5), but could be as high as 50. Compare that [[Alien Stats|alien health values]] range from 30 to 120... it can kill or seriously damage Sectoids, Floaters (if on ground!), and maybe Snakemen, but barely warms up [[Muton|Mutons]]. [[Terror Units|Terrorists]] are hardly touched (but now you might have their attention). Unsurprisingly, the equation used to determine how long a unit will remain on fire depends on the damage modifier of the unit in question: MaxTime=5*Damage Modifier/100, Duration=Random(MaxTime). So for example, if a tank (damage modifier to IN=40) catches fire it will remain lit for MaxTime=5*40/100=2; Duration=Random(2) or 1-2 turns.

* Smoke does not snuff out units on fire.

* Ultimately, in comparison with other ammo types, incendiary ammo is both weak and slow. Most of the time you will want to use it for other purposes (light, blocking LOS, clearing areas) and consider any damage a plus. However, it can be particularly effective against Sectoids - so have plenty of IN for your early-game missions. Barbecue spits are optional.

==Spreading==
Fires can spread one tile in every direction, in ideal conditions (such as wheat fields and haylofts). However, since [[Battlescape_Map_Generation|no map]] is a pure wheat field and many tile types are unlikely to burn, they eventually go out.

Unarmored soldiers can walk through fire unscathed, but don't be left standing on '''''or next to''''' a burning tile at the end of the turn. That's when the fire-spreading code runs. Incendiaries also restrict alien movement; they, too, try to avoid fire.

Explosives (any weapon with [[damage]] type [[Explosives|HE]]) can start fires, particularly in mountains (due to a [[Explosives#Mile-High_Madness|bug]]). Copious use of explosives on thick cover can flush out the enemy - but you have an [[Managing_the_Item_Limit|80-item limit]].

Explosives will not put out fires, per se. You can directly destroy tile flammability via [[Explosives#Tile_Characteristics|explosives]] so that areas can't burn (or stop burning), but it's tricky. (How accurate is your [[Throwing_Accuracy|throwing]]?) In theory, it's possible for your team to corral or even direct flames, but how many folks have tried this? Please put any good war stories along these lines on this page's Discussion.

==Quirks, Tips, And Tricks==
XCOM makes a brave attempt to model fire. However, there are some quirks:

*If a unit (alien or friendly) is on fire or standing in flames, an incendiary explosion ''anywhere else on the map'' will damage it, even if you just shoot an IN round at a random patch of ground.

*Friendly units standing in '''smoke''' will take '''STUN''' damage every time an incendiary round explodes, '''even if armored.''' Alien units are not affected (needs further testing).

*Aliens not facing you will not respond with reaction fire when hit (directly or indirectly) by an incendiary round (see [[Reaction fire triggers]]).

* Smoke and flames do not mix. Only one type may exist on a particular tile on a particular turn. To quickly smother a blaze simply drop a primed [[Smoke Grenade]] in the center. This is a fairly useful trick for unarmored soldiers who want to safely cross a blaze without waiting for it to burn out by itself. But remember, you can cross a blaze safely - just don't stop in or next to one.

*There is an upper limit to how many squares can be on fire or in smoke (400 squares total for both). Once you have a good sized blaze going (forest fire, anyone?) further incendiary rounds will seem to fizzle, because no more fire can be created. Impact damage will still be dealt and units can still be set on fire. Still, existing smoke-covered tiles can be turned into fire instead of smoke, and vice versa.

*The damage values listed in the [[UFOpaedia]] do not determine how powerful an incendiary round deals damage; it only determines how wide an area will be blanketed with flames. Fire is unlike other damage; it works at initial blast and then over time, as described above.

*Shots made with IN rounds never count as "hitting" for the purposes of firing accuracy [[experience]], but reaction shots are counted and can go towards better reaction stats.

*Incendiary rounds (and other forms of fire) do not damage valuable equipment/loot; even corpses will not burn.

[[Category:Enemy Unknown/UFO Defense]]

Talk:Heavy Thermic Lance

2017-04-13T03:47:03Z

Zombie: Question about usage notes.

NKF, you win. Your description made me laugh twice. [[User:Arrow Quivershaft|Arrow Quivershaft]] 11:38, 13 September 2007 (PDT)

: Technically I'm borrowing ideas I've read elsewhere - or think I've read. Still, I almost couldn't complete it. I was laughing my own head off while writing it... -[[User:NKF|NKF]]

Hey Spike, you might want to place a warning about weight on the drill articles. It got me screwed more times than I can remember. [[User:Muton commander|Muton commander]] 22:08, 2 October 2008 (CDT)

Initial research on the operational use of the Heavy Thermic Lance hit a standstill. It was a problem that baffled even the boffins. No one could get it to operate. Of course, with some excruciatingly painful torture procedures helpful guidance from a representative of the [[Gillman]] race (that shall remain anonymous), this stumbling block with the triggering mechanism was removed. Who was to know they mis-assembled the trigger so that you had to push it the other way?

On a lesser note, funding for an under-slung butter and salt dispenser and utensil storage was declined. The loss in profit from not being able to sell prime lobster meat to the highest bidders was just too high to justify a free gourmet after-battle meal for the ground troops.

: Guys, you sure about this? All the guides say you can just research Heavy Thermic Lance right after you research thermic lance, you sure you need to interrogate a Live Gillman to get this? [[User:Jasonred|Jasonred]] 08:00, 12 March 2009 (CDT)

This could have been confusion with the Thermic Lance. You need a Calcinite corpse for the Vibro Blade, then a Gillman corpse for the Thermic Lance. After this I never needed anything else to get the HTL. --[[User:Zombie|Zombie]] 08:35, 12 March 2009 (CDT)

:I'll edit the main article to reflect this then... [[User:Jasonred|Jasonred]] 11:12, 12 March 2009 (CDT)

::What's wrong with a bit of flavor text? I always liked that line, and what's to say they didn't get the info from the same Gillman? :) [[User:Arrow Quivershaft|Arrow Quivershaft]] 17:41, 12 March 2009 (CDT)

:::I dunno, I like flavour text but people keep editting it out telling me the UFOpedia should be serious. In any case, that line is misleading. It implies that you must research a live gillmen before you can research Heavy Thermic Lance. TFTD already has a very messed up research tree, with more than 1 version of it IIRC, so that line confused even me... I thought my memory was playing tricks on me or something. [[User:Jasonred|Jasonred]] 03:47, 13 March 2009 (CDT)

:: Funny's funny, but we do have to maintain accuracy too - which we've been trying to do lately. Adding to the canon on the other hand is Field Manual territory.

:: My recollection on how the drills became available beyond the Vibroblade is a little different, so I'll need to run a few different test scenarios to be sure. Such as having a gill-man or gill-man corpse researched before the drills. Gill man/gill man corpse after the Vibroblade when there aren't any Thermic lances in storage, then getting some in. Thermic lance when there aren't any Heavy Thermic lances in storage. Etc. -[[User:NKF|NKF]] 04:43, 13 March 2009 (CDT)

== Usage notes a bit misleading ==

Using the Least Common Multiple (or LCM) is indeed a way to compare the three drills as the 60% TU cost of each are divisible, but it's also a little bit misleading. When I think of how much damage each drill can muster, I think of it in terms of a full round, not 60% of it. True, the Thermic Lance's 15% TU cost isn't a multiple of 100 (a full turn), but that extra 2/3 of a use is a realistic thing to drop. What does everyone think? --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 03:47, 13 April 2017 (UTC)

BIGOBS.PCK

2017-02-19T22:07:30Z

Zombie: /* Details */ A little more info.

==General Information==
Contains all the large Battlescape graphics for what is held in each hand. They have size 32x48.

==Details==
Contains 57 (0-56) objects.

[[File:BIGOBS.png|thumb|All BIGOBS in one picture|300px|right]]
{| {{StdDescTable}}
|- {{StdDescTable_Heading}}
! Index !! Object !! Index !! Object !! Index !! Object
|-
| 00/x00 || Laser Rifle || 19/x13 || Grenade || 38/x26 || Stun Bomb
|-
| 01/x01 || Rifle || 20/x14 || Smoke Grenade || 39/x27 || Alien Grenade
|-
| 02/x02 || Rifle Clip || 21/x15 || Proximity Grenade || 40/x28 || Hovertank Turret
|-
| 03/x03 || Pistol || 22/x16 || High Explosive || 41/x29 || Plasma Rifle Clip
|-
| 04/x04 || Pistol Clip || 23/x17 || Motion Scanner || 42/x2A || Tank/Rocket Launcher Turret
|-
| 05/x05 || Laser Pistol || 24/x18 || Medi-Kit || 43/x2B || Tank/Cannon Turret
|-
| 06/x06 || Heavy Laser || 25/x19 || Heavy Plasma Clip || 44/x2C || Power/Flying-Suited Corpse
|-
| 07/x07 || Auto-Cannon || 26/x1A || Stun Rod || 45/x2D || Soldier Corpse
|-
| 08/x08 || Auto-Cannon AP-Ammo || 27/x1B || ''Un-used Grenade''* || 46/x2E || Sectoid Corpse
|-
| 09/x09 || Auto-Cannon HE-Ammo || 28/x1C || Personal-Armoured Corpse || 47/x2F || Celatid Corpse
|-
| 10/x0A || Auto-Cannon I-Ammo || 29/x1D || Mind Probe || 48/x30 || Muton Corpse
|-
| 11/x0B || Heavy Cannon || 30/x1E || Heavy Plasma || 49/x31 || Ethereal Corpse
|-
| 12/x0C || Heavy Cannon AP-Ammo || 31/x1F || Plasma Rifle || 50/x32 || Snakeman Corpse
|-
| 13/x0D || Heavy Cannon HE-Ammo || 32/x20 || Plasma Pistol || 51/x33 || Silacoid Corpse
|-
| 14/x0E || Heavy Cannon I-Ammo || 33/x21 || Psi-Amp || 52/x34 || Floater Corpse
|-
| 15/x0F || Rocket Launcher || 34/x22 || Plasma Pistol Clip || 53/x35 || Chryssalid Corpse
|-
| 16/x10 || Small Rocket || 35/x23 || Blaster Launcher || 54/x36 || Tank/Laser Turret
|-
| 17/x11 || Large Rocket || 36/x24 || Blaster Bomb || 55/x37 || Electroflare
|-
| 18/x12 || Incendiary Rocket || 37/x25 || Small Launcher || 56/x38 || Elerium-115
|}

<nowiki>*</nowiki> This was supposedly a Stun Grenade of some sort which was never fully implemented. Called ''GAS GRENADE'' in the dev comments.

== Images ==
<table style="border:1px gray solid;">
<tr style="border:1px gray solid;"><td style="border:1px gray solid;">[[Image:BIGOBS00.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS01.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS02.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS03.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS04.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS05.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS06.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS07.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS08.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS09.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS10.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS11.GIF]]</td></tr>
<tr style="border:1px gray solid;"><td style="border:1px gray solid;">[[Image:BIGOBS12.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS13.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS14.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS15.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS16.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS17.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS18.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS19.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS20.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS21.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS22.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS23.GIF]]</td></tr>
<tr style="border:1px gray solid;"><td style="border:1px gray solid;">[[Image:BIGOBS24.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS25.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS26.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS27.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS28.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS29.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS30.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS31.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS32.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS33.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS34.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS35.GIF]]</td></tr>
<tr style="border:1px gray solid;"><td style="border:1px gray solid;">[[Image:BIGOBS36.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS37.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS38.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS39.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS40.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS41.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS42.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS43.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS44.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS45.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS46.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS47.GIF]]</td></tr>
<tr style="border:1px gray solid;"><td style="border:1px gray solid;">[[Image:BIGOBS48.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS49.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS50.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS51.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS52.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS53.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS54.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS55.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS56.GIF]]</td></tr>
</table>

==See Also==
* [[OBDATA.DAT]]
* [[UNITS]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

BIGOBS.PCK

2017-02-19T21:00:46Z

Zombie: /* Details */ For some reason this tag wasn't closed. Fixed now!

==General Information==
Contains all the large Battlescape graphics for what is held in each hand. They have size 32x48.

==Details==
Contains 57 (0-56) objects.

[[File:BIGOBS.png|thumb|All BIGOBS in one picture|300px|right]]
{| {{StdDescTable}}
|- {{StdDescTable_Heading}}
! Index !! Object !! Index !! Object !! Index !! Object
|-
| 00/x00 || Laser Rifle || 19/x13 || Grenade || 38/x26 || Stun Bomb
|-
| 01/x01 || Rifle || 20/x14 || Smoke Grenade || 39/x27 || Alien Grenade
|-
| 02/x02 || Rifle Clip || 21/x15 || Proximity Grenade || 40/x28 || Hovertank Turret
|-
| 03/x03 || Pistol || 22/x16 || High Explosive || 41/x29 || Plasma Rifle Clip
|-
| 04/x04 || Pistol Clip || 23/x17 || Motion Scanner || 42/x2A || Tank/Rocket Launcher Turret
|-
| 05/x05 || Laser Pistol || 24/x18 || Medi-Kit || 43/x2B || Tank/Cannon Turret
|-
| 06/x06 || Heavy Laser || 25/x19 || Heavy Plasma Clip || 44/x2C || Power/Flying-Suited Corpse
|-
| 07/x07 || Auto-Cannon || 26/x1A || Stun Rod || 45/x2D || Soldier Corpse
|-
| 08/x08 || Auto-Cannon AP-Ammo || 27/x1B || ''Un-used Grenade''* || 46/x2E || Sectoid Corpse
|-
| 09/x09 || Auto-Cannon HE-Ammo || 28/x1C || Personal-Armoured Corpse || 47/x2F || Celatid Corpse
|-
| 10/x0A || Auto-Cannon I-Ammo || 29/x1D || Mind Probe || 48/x30 || Muton Corpse
|-
| 11/x0B || Heavy Cannon || 30/x1E || Heavy Plasma || 49/x31 || Ethereal Corpse
|-
| 12/x0C || Heavy Cannon AP-Ammo || 31/x1F || Plasma Rifle || 50/x32 || Snakeman Corpse
|-
| 13/x0D || Heavy Cannon HE-Ammo || 32/x20 || Plasma Pistol || 51/x33 || Silacoid Corpse
|-
| 14/x0E || Heavy Cannon I-Ammo || 33/x21 || Psi-Amp || 52/x34 || Floater Corpse
|-
| 15/x0F || Rocket Launcher || 34/x22 || Plasma Pistol Clip || 53/x35 || Chryssalid Corpse
|-
| 16/x10 || Small Rocket || 35/x23 || Blaster Launcher || 54/x36 || Tank/Laser Turret
|-
| 17/x11 || Large Rocket || 36/x24 || Blaster Bomb || 55/x37 || Electroflare
|-
| 18/x12 || Incendiary Rocket || 37/x25 || Small Launcher || 56/x38 || Elerium-115
|}

<nowiki>*</nowiki> This was supposedly a Stun Grenade of some sort which was never fully implemented.

== Images ==
<table style="border:1px gray solid;">
<tr style="border:1px gray solid;"><td style="border:1px gray solid;">[[Image:BIGOBS00.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS01.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS02.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS03.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS04.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS05.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS06.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS07.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS08.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS09.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS10.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS11.GIF]]</td></tr>
<tr style="border:1px gray solid;"><td style="border:1px gray solid;">[[Image:BIGOBS12.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS13.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS14.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS15.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS16.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS17.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS18.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS19.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS20.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS21.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS22.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS23.GIF]]</td></tr>
<tr style="border:1px gray solid;"><td style="border:1px gray solid;">[[Image:BIGOBS24.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS25.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS26.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS27.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS28.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS29.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS30.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS31.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS32.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS33.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS34.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS35.GIF]]</td></tr>
<tr style="border:1px gray solid;"><td style="border:1px gray solid;">[[Image:BIGOBS36.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS37.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS38.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS39.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS40.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS41.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS42.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS43.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS44.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS45.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS46.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS47.GIF]]</td></tr>
<tr style="border:1px gray solid;"><td style="border:1px gray solid;">[[Image:BIGOBS48.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS49.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS50.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS51.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS52.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS53.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS54.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS55.GIF]]</td><td style="border:1px gray solid;">[[Image:BIGOBS56.GIF]]</td></tr>
</table>

==See Also==
* [[OBDATA.DAT]]
* [[UNITS]]
[[Category:Game Files]]
[[Category:Enemy Unknown/UFO Defense]]

Hiring/firing

2016-10-21T05:51:16Z

Zombie: /* Aircraft */ Minor rewording.

==General Information==
*You can only have a maximum of 250 soldiers. This includes new recruits (not yet shown up) and soldiers in transit between bases.
*New soldiers cost $40,000, while their monthly salary is half that price, or $20,000. If you have the full 250 soldiers, they're costing you $5M/month.
*Sacking a soldier costs nothing. To do so, make sure the soldiers name is listed in the Sell/Sack screen. If it is not there, the soldier is probably loaded on a transport ship.
*It takes 72 hours (3 days) for new recruits to show up. Once at a base, it takes anywhere from 6 to 16 hours to transfer between bases, dependent entirely on distance. The minimum transfer time is guaranteed even if both of your bases are stacked right on top of each other. The cost to transfer soldiers is free, regardless if they are wearing armor.
*Statistics and names of new recruits are always randomly generated. See [[Raw recruit statistical likelihood|recruit statistics]] for more info, including the probability of getting the perfect soldier.
*A soldier's armor stays with them, including if they are transferred or fired. So it is LOST if you fire them when they have on armor. This is the only item that stays with a soldier. Armor can be seen/changed on the Soldier tab, or under Equip Craft.
*Only 100 items can be in transit (transferred between bases) in total at any given time. "Items" here means line items; one transfer of 200 Elerium counts as one line item. Soldiers (including new recruits) each count as one item. So, in the endgame, if you want to hire a ton of new recruits for high-psi screening at the beginning of a month, you can only have 100 on the way at a time. This leads to a theoretical max of 1,000 soldiers per month if you're doing high-volume screening (3 days for 100 soldiers; 30 days per month). Do routine inter-base transfers before hiring huge batches, because they will hog your transfer queue for 3 days.
==Scientist Costs==

Scientist cost $60K each in the first month to hire, plus $30K/month thereafter in salary. They also need Laboratories to work in and Living Quarters to live in. Assuming you have Scientists on-staff in blocks of 50, including Lab rental and Living Quarters rental, each Scientist costs $1.54M/50 per month. As a good approximation, a full Lab costs $50K per day to run. In other words, every research day costs about $1K. As most of the cost (97%) is per-Scientist salaries, it's a good approximation even if your Labs are far from fully utilised.

In addition, the up-front cost of hiring an extra 50 scientists, building the Lab and the Living Quarters, is $4.15 million. The first Lab-full is a little cheaper as 10 Scientists are already hired, the Lab is already built, and there are (some, but not enough) Living Quarters available. $2.8 million is a reasonable approximation for the up-front costs of the first full Lab. Generally more than 3 Labs is not considered useful. However even in the limiting case (infinite/maximum Labs), the up-front cost amounts to about $83K per Scientist - not a huge amount more than the $30K hiring each Scientist will cost you in the first month.

'''Labs Up-front (/Scientist) Daily (/Scientist)'''
x1 $ 2.80M $ 56K $ 50K $1K
x2 $ 6.95M $ 70K $100K $1K
x3 $11.10M $ 74K $150K $1K
..
xN $ 4.15MxN $ 83K $ 50KxN $1K

==Aircraft==

===Craft Weapons===
When you sack/remove any craft you also lose the craft weapons (and ammo) it is armed with, so it is usually prudent to remove the weapons before sacking the aircraft. This is most often an issue when upgrading your [[Interceptor]]s, but also if you are getting rid of [[Firestorm]]s or [[Lightning]]s that you no longer require.

Unfortunately you are unable to totally remove weapons - you have to switch (rearm) to another weapon type. Therefore, before you sack an aircraft, make sure you have 2 spare cheap weapons in that base. Switch to the cheap weapons that you would rather lose, and keep your Plasma Beams or whatever was on the aircraft. Also, if you sell the aircraft right away after you have begun to rearm, there will be little or no ammunition lost when it flies back home to the leasing company.

In theory the cheapest sacrificial weapon is the Stingray Launcher at $16K each. In practice an Avalanche Launcher at $17K each, is a much more useful thing to have laying around spare. So far from being 'free' to sack an aircraft (with the exception of the [[Skyranger]]), it is likely to cost you $16K-$34K to sack it, even if you are careful. If you are careless it could cost you half a million dollars cash, plus lost manufacturing time.

When you do decide to rid yourself an aircraft, the general practice is to arm the cheap weapons onto it and then sack it immediately. If, due to various circumstances, you had the throwaway weapons on the ship long enough for it to proceed to its rearming phase, don't forget to unload the ammo before sacking the ship so that you don't lose the ammunition as well. To empty the ammo, re-arm the same weapon onto the ship. This will empty its magazine. Obviously this is not a necessary step if you do not have any of that weapon's ammo in storage, but one you should take if you are still actively using them.

[[User:Seb76|Seb76]]'s UFOLoader has a fix for this problem, allowing you to remove all weaponry from an aircraft.

===Soldiers, HWPs and Equipment===
When you sack an aircraft the soldiers and equipment get off first, so you don't need to worry about removing them first. They will still be retained even if there is no more storage capacity left for them, but this will mean that you won't be able to purchase new gear until free space is once again available.

==Costs==
<table {{StdCenterTable}} class="sortable">
<tr {{StdDescTable_Heading}}><th align="left" width="170">Personnel/Craft</th><th width="100">Recruit</th><th width="90">Salary</th></tr>
<tr><th align="left">Soldier</th><td>$40,000</td><td>$20,000</td></tr>
<tr><th align="left">Engineer</th><td>$50,000</td><td>$25,000</td></tr>
<tr><th align="left">Scientist</th><td>$60,000</td><td>$30,000</td></tr>
<tr><th align="left">Interceptor</th><td>$600,000</td><td>$600,000</td></tr>
<tr><th align="left">Skyranger</th><td>$500,000</td><td>$500,000</td></tr>
</table> 

== See Also ==
*[[Buying/Selling/Transferring]]
*[[Raw_recruit_statistical_likelihood|Recruit statistics]]
*[[Soldier Name Stats|Soldier Names]]
*[[Known_Bugs#Transfer_Limit_cash_eater|Transfer-limit cash-eating glitch]]

[[Category:Enemy Unknown/UFO Defense]]

Incendiary

2016-09-18T18:43:17Z

Zombie: /* Damage */ Linking mostly.

[[Image:Fire_ground.gif|Ground Fire Animation]] [[Image:Fire_unit.gif|Unit Fire Animation]]

'''[[Incendiary]]''' (IN) ammunition creates a large area of '''fire''' on the [[battlescape]] equal to its [[#Blast Diameter|blast diameter]]. Incendiary rounds will burn for two turns on non-flammable terrain. Flammable terrain will burn for longer, and the fire is likely to spread to any adjacent flammable tiles. Aliens and unarmored X-COM agents can catch fire as well.

Incendiary rounds do very little direct damage -- between 0 and 10 points per hit -- but continue to do damage every turn that a unit is in fire or on fire. Due to the "[[Known_Bugs#Funky_Fire|funky fire]]" bug, units in or on fire will also take damage every time an incendiary round goes of ''anywhere'' on the Battlescape.

== Source ==
Incendiary rounds are available for the following weapons:

*[[Auto-Cannon]]
*[[Heavy Cannon]]
*[[Rocket Launcher]]

Some tiles may already be on fire at the start of the mission if the [[UFO Crash Recovery|UFO crashed]].

== Blast Diameter ==

*Auto-Cannon incendiary rounds have a blast diameter of 5 tiles; note that the southern tip of the "diamond" will always be missing.
*Heavy Cannon incendiary rounds have a blast diameter of 7 tiles.
*Incendiary rockets have a blast diameter of 9 tiles.

X
X XXXXXXX
X XXXXX XXXXXXX
XXX XXXXX XXXXXXX
XXXXX XXXXXXX XXXXXXXXX
XXX XXXXX XXXXXXX
X XXXXX XXXXXXX
X XXXXXXX
X

AC-IN HC-IN RL-IN

==Smoke==
[[Image:Smoke1.gif]] [[Image:Smoke2.gif]] [[Image:Smoke3.gif]]
A burning fire can also be used as an impromptu smoke screen. No smoke appears immediately, but smoke will appear outside the edges of the fire, as the fire slowly spreads in subsequent turns. The smoke begins on the first turn after the turn the incendiary round is fired. The smoke will spread vertically (upwards) as well as laterally. Smoke can block [[Line_of_sight|line of sight]].

==Light==
[[File:FlarePattern.png|thumb|right|A single square of fire will illuminate the area within the grey line.]]
Fire not only damages aliens and obstacles hiding in dark corners of the map, but also illuminates the area for several turns. This is especially useful during [[Night Missions]].

Any tile on fire will provide illumination within a 9 tile radius. A large patch of fire will illuminate everything within 9 tiles of the outer edge of the fire. Curiously, aliens on fire do not provide illumination. Maybe they're [http://firecritic.com/2010/12/firefighters-guide-to-invisible-fire-otherwise-known-as-ethanol-fires/ made of ethanol] or something.

==Damage==
<div style="color:red;">Incendiary damage mechanics are not fully understood and are being re-investigated by [[User:Zombie|Zombie]]. The information below is part of the picture but not the completely accurate picture. Treat with caution! More discussion is on the [[Talk:Incendiary|Talk page]].</div>

* Brush and wood on fire will eventually be consumed, leaving a flat scorched-earth [[MCD|tile]].

* If a [[Zombie]] is killed by the explosive impact of any form of Incendiary munitions, the [[Chryssalid]] larva will be burnt up instead of hatching. However, Zombies have high [[Alien Stats|hit points]] and will have to be near death to be killed by an IN round, per se.

* UFO interiors and dropped items are fireproof, even if their owners aren't. Silverblade recommends combining this fact with the diagonal wall bug and an incendiary rocket to roast them in the shell.

* Damage caused by fire does not alter [[Morale]] level.

* '''All''' forms of manufactured X-COM armor will completely block the effects of fire -- including direct hits from incendiary rounds. Soldiers not wearing armor take [[Health]] damage.

* '''Soldiers wearing armour, if wounded, can die from spreading fire.''' Apparently if the damage the fire would inflict exceeds the soldier's remaining [[health]], the soldier will die. If the damage is not enough to kill the soldier that turn, no damage will be inflicted. This bug only applies to ''spreading'' fire, and will not affect a wounded soldier already standing in fire.

* Certain creatures take increased or decreased [[Damage#Damage_Modifiers|damage]] from incendiary rounds:
**More Vulnerable:
***170% - [[Reaper]]
**Less Vulnerable:
***80% - Chryssalid
***70% - [[Ethereal]], [[Snakeman]]
***40% - [[Heavy Weapons Platforms|Tanks/Hovertanks]]
*** 0% - [[Silacoid]] (rocks don't burn!)

* Initial "impact" damage from incendiary ammunition is either for no points (unit does not catch fire), or between 5-10 points (unit catches fire). Since the distribution is randomly chosen from the set [ 0, 5, 6, 7, 8, 9, 10 ] (seven values), the probability of remaining unharmed is 14% (1/7), while there is an 86% chance (6/7) a unit will take some damage. The average damage is 6.4.

* Units standing in a blaze (as opposed to being on fire themselves) will receive between 1-12 damage points, most likely determined by the flammability rating of their tile ([[MCD]] offset 45). The chance of catching fire is determined by an if-then statement: IF Random(100)<40*Damage Modifier/100 THEN Catch Fire. So for example, a normal unarmored soldier (with a damage modifier to IN=100) has a probability of catching fire of: Random(100)<40*100/100 = Random(100)<40 which means that rookie will catch fire 40% of the time. From a previous 6000+ trial conducted by [[User:Zombie|Zombie]] soldiers have a 33% chance of catching fire. It's unknown why these numbers don't match, but it's possible the sample size was still too small.

* Once lit, units burn for a slightly random amount of time, taking 5-10 damage points each turn. (If units fall unconscious, they do not continue to burn.) Thus the average total damage is 21.5 points (3 x 7.5), but could be as high as 50. Compare that [[Alien Stats|alien health values]] range from 30 to 120... it can kill or seriously damage Sectoids, Floaters (if on ground!), and maybe Snakemen, but barely warms up [[Muton|Mutons]]. [[Terror Units|Terrorists]] are hardly touched (but now you might have their attention). Unsurprisingly, the equation used to determine how long a unit will remain on fire depends on the damage modifier of the unit in question: MaxTime=5*Damage Modifier/100, Duration=Random(MaxTime). So for example, if a tank (damage modifier to IN=40) catches fire it will remain lit for MaxTime=5*40/100=2; Duration=Random(2) or 1-2 turns.

* Smoke does not snuff out units on fire.

* Ultimately, in comparison with other ammo types, incendiary ammo is both weak and slow. Most of the time you will want to use it for other purposes (light, blocking LOS, clearing areas) and consider any damage a plus. However, it can be particularly effective against Sectoids - so have plenty of IN for your early-game missions. Barbecue spits are optional.

==Spreading==
Fires can spread one tile in every direction, in ideal conditions (such as wheat fields and haylofts). However, since [[Battlescape_Map_Generation|no map]] is a pure wheat field and many tile types are unlikely to burn, they eventually go out.

Unarmored soldiers can walk through fire unscathed, but don't be left standing on '''''or next to''''' a burning tile at the end of the turn. That's when the fire-spreading code runs. Incendiaries also restrict alien movement; they, too, try to avoid fire.

Explosives (any weapon with [[damage]] type [[Explosives|HE]]) can start fires, particularly in mountains (due to a [[Explosives#Mile-High_Madness|bug]]). Copious use of explosives on thick cover can flush out the enemy - but you have an [[Managing_the_Item_Limit|80-item limit]].

Explosives will not put out fires, per se. You can directly destroy tile flammability via [[Explosives#Tile_Characteristics|explosives]] so that areas can't burn (or stop burning), but it's tricky. (How accurate is your [[Throwing_Accuracy|throwing]]?) In theory, it's possible for your team to corral or even direct flames, but how many folks have tried this? Please put any good war stories along these lines on this page's Discussion.

==Quirks, Tips, And Tricks==
XCOM makes a brave attempt to model fire. However, there are some quirks:

*If a unit (alien or friendly) is on fire or standing in flames, an incendiary explosion ''anywhere else on the map'' will damage it, even if you just shoot an IN round at a random patch of ground.

*Friendly units standing in '''smoke''' will take '''STUN''' damage every time an incendiary round explodes, '''even if armored.''' Alien units are not affected (needs further testing).

*Aliens not facing you will not respond with reaction fire when hit (directly or indirectly) by an incendiary round (see [[Reaction fire triggers]]).

* Smoke and flames do not mix. Only one type may exist on a particular tile on a particular turn. To quickly smother a blaze simply drop a primed [[Smoke Grenade]] in the center. This is a fairly useful trick for unarmored soldiers who want to safely cross a blaze without waiting for it to burn out by itself. But remember, you can cross a blaze safely - just don't stop in or next to one.

*There is an upper limit to how many squares can be on fire or in smoke (400 squares total for both). Once you have a good sized blaze going (forest fire, anyone?) further incendiary rounds will seem to fizzle, because no more fire can be created. Impact damage will still be dealt and units can still be set on fire. Still, existing smoke-covered tiles can be turned into fire instead of smoke, and vice versa.

*The damage values listed in the [[UFOpaedia]] do not determine how powerful an incendiary round deals damage; it only determines how wide an area will be blanketed with flames. Fire is unlike other damage; it works at initial blast and then over time, as described above.

*Shots made with IN rounds never count as "hitting" for the purposes of firing accuracy [[experience]], but reaction shots are counted and can go towards better reaction stats.

*Incendiary rounds (and other forms of fire) do not damage valuable equipment/loot; even corpses will not burn.

[[Category:Enemy Unknown/UFO Defense]]

UNITREF.DAT

2016-08-04T04:52:32Z

Zombie: /* Structure */ Indeed, Zombies have their own DM category, also linking to the preferred DM page.

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

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

Melee Accuracy

2016-07-05T03:18:10Z

Zombie: /* Soldier Usage */ Direct linked to the post instead of the page.

In theory, Melee Accuracy affects a soldier's ability to hit their target with a close combat, or melee, attack.
*This statistic is not shown in any displays, but is still tracked by the game. It can be seen to rise (like other skills) when the Stun Rod is used. BUT,
*Hacking this field has NO effect on Stun Rod accuracy; the Stun Rod seems hard-wired to 100% accuracy. Therefore, Melee Accuracy is an entirely useless/vestigial value, with the possible remote exception of somebody playing with hacked melee weapons (which might or might not also be hard-wired to 100% accuracy).
*Some players call this skill Melee Accuracy and some call it Close Combat Accuracy (CCA). The OSG talks about a CCA, but since it didn't wind up being shown anywhere in the game and it's not 100% clear that the OSG meant this skill as opposed to e.g. HTH, the shorter term is also used.
*It's not hard to abuse the Item Stacking Bug so as to make "new" [[Item Stacking Bug#Effects of stacked items in hand slots|melee weapons]].

Even though it appears to be an entirely irrelevant field, we've still managed to pin down some of its functionality (smile).

==Starting Values==
New recruits always begin with a value from 20 to 40.

==Improvement==
Melee Accuracy will ''only'' increase by the use of the [[Stun Rod]] in the original XCOM. In Terror From The Deep (TFTD), [[Vibro Blade]]s, [[Thermic Lance]]s, and [[Heavy Thermic Lance]]s will also increase it.

You are awarded an average of 2 skill points (range 1-3) per combat mission if you melee at least 3 times, and an average of 4 points (range 2-6) for 11+ uses. These points do not depend on your current skill level, only on the number of stun-rod/melee uses. For more particulars on skill-point increases, see [[Experience#How_Experience_Points_Are_Applied|Experience]].

==Maximum Caps==
An X-COM soldier's Melee Accuracy is capped at 120. However, because you can get a +6 roll when at 119, a soldier can have up to 125 Melee Accuracy (if they're really lucky!). For more info, see [[Experience#Regarding_Caps|Regarding Caps]].

==Hidden Value==
Melee or Close Combat Accuracy is not shown in any display, but it clearly increases when you use the Stun Rod. Possibly the XCOM programmers once hoped to emphasize melee much more in general, but then downplayed it to focus on other things. In any event, here are technical details for anyone interested. These specifics are for the original XCOM.

Like other [[Experience#Primary Stats|primary stats]], Melee Accuracy:
*Has an initial [50] and an increase [61] byte in [[SOLDIER.DAT]], in line with other primaries there
*Has an experience byte in [[UNITREF.DAT]] (offset 82), in line with other primary counters
*Also has its value pasted from geoscape into Unitref (offset 56), as do other primaries
*Has a cap of 120 (composed of an initial and increase), the same as firing and throwing accuracy
*Has the same rule as other primaries for [[Experience#Primary_Stats|skill point increases]]
*Triggers secondary stats to increase, just like other primaries
So it's quite functional relative to gaining experience.

But Melee Accuracy DOESN'T MATTER, because the Stun Rod appears to be hard-wired to 100% accuracy. (Hacking your melee accuracy to 0 or to 255 has absolutely no effect on Stun Rod accuracy.)

The only way you can see your Melee Accuracy value is by [[HackerTools|hex editing]] [[SOLDIER.DAT]] (bytes [50] and [61] added together) or [[UNITREF.DAT]] (offset [56]).

==Soldier Usage==
Melee accuracy is entirely irrelevant in a regular game of X-COM. The only melee weapon is hard-wired to 100% accuracy, period.

If someone wants to build melee accuracy just for the fun of it, the following was written before Zombie [http://www.strategycore.co.uk/forums/topic/746-damage-modifiers-for-aliens/page__st__160#entry70596 showed] that the Stun Rod is hard-wired:

Unless someone wants to have [[Stun_Rod#Activating_Melee_Attacks_For_Other_Items|fun with close combat]], melee isn't a particularly viable skill in XCOM. (It might be in TFTD, though.) In XCOM, if you were thinking of stunning aliens and then reviving them (so you can stun them again and/or shoot them to death - the pathetic slobs), note that the stun-rod can deliver up to 130 stun points (2x65). But the [[Medi-Kit]] stimulant only reduces stun level by 4 points (time 10 equals 40 points of stun per Medi-Kit). Aliens can become so [[unconscious]] that you use up all your [[Medi-Kit]]s trying to revive them (plus it's a real hassle). Most players would much rather increase their [[Firing Accuracy]] and [[Reactions]] skills than Melee.

Of course, the stun rod remains vital for capturing some aliens and unlocking research, even if you don't develop its accuracy.

Note: You can try to exploit the use of other items as melee weapons in the original XCOM if you're feeling adventurous - see [[Stun_Rod#Activating_Melee_Attacks_For_Other_Items|NKF's notes]]. If you do, then melee accuracy might matter... or it might not. The jury's still out.

In case anyone was confused: The [[Small Launcher]] does not use Melee Accuracy. Firing this ranged Stun bomb weapon counts as "hits" toward your Firing Accuracy stat (and Reaction too, if applicable).

==Alien Usage==
Because Aliens have no Stun Rod equivalent, the only species to utilise Melee Accuracy are the [[Silacoid]], [[Chryssalid]], [[Reaper]], and [[Zombie]], each of which have an accuracy of 80%. The melee attack's damage is equal to the unit's [[Strength|strength]].

==Influencing Factors==
Melee Accuracy ''might'' be affected by the same factors as [[Firing_Accuracy|firing]] and [[Throwing_Accuracy|throwing]] accuracies:

* +15% when kneeling.
* -20% when holding a two-handed weapon with one hand.
* -10% per wound to the head or hitting arm.
* -25% x (max health-current health)/max health)

... but probably not, because the Stun Rod seems to be hard-wired.

==See Also==
*[[Stun Rod]]
*[[Experience#How_Experience_Points_Are_Applied|Experience]]
*[[Raw_recruit_statistical_likelihood|Recruit Statistics]]

{{Unit Stats Navbar}}
[[Category:Soldiers]]
[[Category:Enemy Unknown/UFO Defense]]

Terror Mission (TFTD)

2016-06-04T05:21:27Z

Zombie: Added a bunch of internal links.

While the aliens are usually very passive in their dealings with the human populace in general, continual interference by X-COM will lead them to attack a populated area in order to provoke X-COM to action, or preferably inaction in an effort to make them look bad in the eyes of the Council of Funding Nations, thus reduce their standing and hopefully force countries to withdraw their funding.

Traditionally, the aliens in the first alien war attacked small country towns with a low population. In the second alien war, the scope has broadened. As the new alien threat are nautical in nature, so are their targets. Terror sites now occur in [[Port_Attack|small ports]], [[Island_Attack|island resorts]] and [[Shipping_Lane_Mission|ships]].

All of these are conducted on land. Though this eliminates the ability of the aliens to use their devastating torpedoes, they bring deadly [[Terror_Units_(TFTD)|terror units]] into battle to compensate.

There is also the [[Artefact_Site|Artefact Sites]], where the aliens are activating synonium devices in old temples on the sea bed. Though not strictly terror missions as no [[Civilian|civilians]] are involved, they have the same urgency as terror sites due to the short time frame available to you to attend to them. If they are not dealt with before the devices are restored, the blow to X-COM's standing with the Council of Funding Nations can be just as if not more disastrous than failing to attend to a terror site.

Artefact sites and ship missions are classified as two-parter missions. You must go through two maps in succession in order to clear the site. They are lengthy missions so you will need to plan your ammunition supplies accordingly.

Port and island missions are the closest to a traditional terror site that you can get and you only need to clear the infestation of aliens on the map.

For more information on the different terror mission types, refer to their respective articles.

==Timing==
Terror missions almost always occur on the first of the month, so make sure your troops are prepared for action at that time. Also, they appear during the dead of night in whichever location they have chosen and will disappear before dawn, seemingly guaranteeing that you will have to endure the additional hardship of a night mission.

However, there does seem to be a trick to get around this. Terror sites will not disappear as long as they are targeted by an X-Com craft. A couple hours before dawn approaches the terror site, send your craft in the opposite direction from the site. As dawn approaches, reroute the craft towards the terror site. The extra distance the craft needs to cover will make it so that you arrive during daylight hours, making what is normally a difficult and grueling mission a little bit easier.

==See Also==
{{Mission Types Navbar (TFTD)}}
[[Category: TFTD]]

Talk:Artefact Site

2016-06-04T05:19:02Z

Zombie: /* Synonium? */ new section

==Locked Hallucinoid?==
Hi everybody, I'm new here - and here's my new question.
I have recently completed two Artefact Site missions on Superhuman difficulty. In both of these missions (in second part) there was a Hallucinoid located far outside the map. I was able to find it by using XComUtil (SWP flag).

The question is as follows: can this Hallucinoid present there knowingly (by developers) to ensure that you will manually destroy the Synomium Device instead of just kill all the aliens? Or maybe this is just a bug of the Windows version of the game, or something like alien overflow on higher difficulties?

Thanks.

[[User:Player701|Player701]] 08:05, 29 June 2010 (EDT)

----

XComUtil sometimes generated X-COM units outside the boundaries of the map (I'm not sure if this has been corrected on the latest version), so it is possible that it is simply an XComUtil generated bug. [[User:Hobbes|Hobbes]] 08:25, 29 June 2010 (EDT)

----

I know that, but I haven't used XComUtil before. I have installed it just to find that last alien, so this bug can't be related to XComUtil. And I have installed it in another game directory, so it couldn't corrupt my save files. [[User:Player701|Player701]] 10:05, 29 June 2010 (EDT)

----

If you upload the save file (here for eg: [[Image:Out_of_bounds_Hallucinoid.zip]]), I could take a look at it. I would guess the map ran out of spawn nodes (higher difficulty = more aliens to place on the map). - [[User:Bomb Bloke|Bomb Bloke]] 23:24, 29 June 2010 (EDT)

----

There are a few maps in TFTD where large units may end up spawned in odd locations, probably due to what Bomb Bloke mentioned. Actually, in one odd example I helped troubleshoot a while back was a Xarquid that was stuck in the cargo hold shaft at the front of the boat in a shipping lane mission. Since it cannot be breached even by alien weapons, it made the first map impossible to complete without aborting. As for the aliens getting stuck in walls in the colonies, I don't know if that was deliberate or accidental on the part of the mappers.

I had a feeling Zombie had a series of map pack sets that corrected the placement problems, but currently I can only find the ones for the two small subs and the ones for UFO. -[[User:NKF|NKF]] 01:56, 30 June 2010 (EDT)

----

Uploaded the save game: [[Image:Out of bounds Hallucinoid.zip]], you can take a look. That's my fourth Artefact Site mission in this campaign, and the third case of a Hallucinoid outside of the map (There is only one alien remaining, and the SWP flag was applied using XComUtil). [[User:Player701|Player701]] 05:53, 1 July 2010 (EDT)

----

Well this is odd.

First off, he's not outside the map - he's actually just within it, albeit embedded in some black wall blocks.

Second - and rather more to the point - he's sitting on spawn node 118 (he hasn't been able to move off it). The problem is that the map module he's in (GRUNGE08) doesn't have a spawn node there (and yes, I'm checking the Windows release, of which there was one version).

In fact, both nodes 117 and 119 are placed miles away, over an entirely different map module (GRUNGE12, that large 20x20 area in the southern-center of the battlescape). That ''certainly'' shouldn't be the case - all nodes should be placed on a per-module basis (so if you suddenly jump from one module to another while placing nodes, it shouldn't be possible to jump back again).

I guess there must be something screwy in the [[ROUTES|GRUNGE12.RMP file]], but I haven't yet looked to see what it might be.

- [[User:Bomb Bloke|Bomb Bloke]] 08:02, 1 July 2010 (EDT)

== Alien garrison ==

I noted down what I killed when I cleared two sites completely playing on superhuman difficulty. I got:
<table {{StdCenterTable}}>
<tr><td>1st stage</td><td>first site</td><td>second site</td></tr>
<tr><td>aquatoid</td> <td>4</td><td>3</td></tr>
<tr><td>tasoth</td><td> 10</td><td>7</td></tr>
<tr><td>tentaculat</td> <td>0</td><td>2</td></tr>
<tr><td>halucinoid</td><td> 0</td><td>2</td></tr>
<tr><td>2nd stage</td><td>first site</td><td>second site</td></tr>
<tr><td>aquatoid</td><td> 4</td><td>4</td></tr>
<tr><td>tasoth</td><td> 12</td><td>7</td></tr>
<tr><td>tentaculat</td><td> 6</td><td>8</td></tr>
<tr><td>halucinoid</td><td> 1</td><td>3</td></tr>
</table>
Looking at these numbers I would guess that the total numbers are around 14 for the first and 22-23 for the second. The composition seems to be very variable. I also recall missions with more then 10 tentaculats for the second stage. The map size of the first stage seems to be variable as well if I recall correctly.

: Here's some more numbers (3 missions, Veteran). Please note I'm not the author of the above table. For me, it seemed that the number of aliens on Level 1 and 2 are the same, just very random. So the following is for '''each level''':
*Tasoth Soldier x5-8
*Tasoth Squad Leader x1-3
*Tentaculat x6-7
*Aquatoid Soldier x2-3
*Aquatoid Squad Leader x1-3
*Hallucinoid x1-3
--[[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 13:07, 13 July 2014 (EDT)

== Loot ==

As already mentioned in the article there is a substantial recovery if both stages are completely(or maybe only the second is sufficient).
From the debriefing I got:
<table {{StdCenterTable}}>
<tr><td>item</td><td>first site</td><td>second site</td></tr>
<tr><td> magnetic navigation</td><td>1</td><td>1</td></tr>
<tr><td> sub construction</td><td>1</td><td>1</td></tr>
<tr><td> learning arrays</td><td>2</td><td>2</td></tr>
<tr><td> cryogenics</td><td>12</td><td>0</td></tr>
<tr><td> implanter</td><td>2</td><td>0</td></tr>
<tr><td> aqua plastics</td><td>519</td><td>503</td></tr>
<tr><td> reanimation</td><td>3</td><td>3</td></tr>
<tr><td> score</td><td>2132</td><td>2161</td></tr>
</table>
In addition there are also the corpses of the approx. 37-39 aliens and their weapons. Since the maps are not that large it seems quite beneficial to clear them completely for the additional 500-700 score points(compared to demolishing the device and running) and the recovery money. By the time you reach the device most aliens should be dead anyway. If there are aliens in the walls or of the map as it happens sometimes you might be robbed of the fruits of your labor however - saving the game before landing recommended.
--[[User:Tauon|Tauon]] 23:15, 30 October 2010 (BST)

==Appear only after Alien Origins are researched?==

This probably is just a coincidence but on my current game the 1st Artefact Mission appeared some 4/5 months right after I completed research on Alien Origins (who explains them). Just a coincidence or you need to complete research in order for them to appear? Anyone else can check this out? [[User:Hobbes|Hobbes]] 16:57, 6 January 2011 (EST)
: I have not had the time to look through the save files of my latest campaigns but that would mean that on should not expect a Artefact Mission before May/June earliest. And if memory serves me right I recall a few occasions where I had to fight such missions with gauss weapons and sonic pulsers which in turn means that it was rather early because I tend to upgrade weapons early and delay the alien origin research until I am about to research my first lobsterman navigator/gillman commander/lobsterman commander for the ultimate threat in order to get both T'Leth and the Leviathan with the second lobster Commander.--[[User:Tauon|Tauon]] 09:01, 11 January 2011 (EST)

== Edits looking good ==

More useful info here, thanks NKF. [[User:4th Cuirassier|4th Cuirassier]] 08:46, 8 February 2011 (EST)

== Equipment recovery ==

Packor's recent update's alerted me to the fact the 2-parter equipment recovery info on this page hasn't been updated to reflect the v1.0 vs. v2.0 item recovery differences.

As mentioned in [[Known Bugs (TFTD)]], v1.0 loses the equipment (including what's in the Triton) except what you're carrying. v2.0 keeps everything from the first part if cleared, not just what you're carrying.

I'll have a crack at that later tonight - looks like the Colony Assault and Shipping Lane pages need some attention too. -[[User:NKF|NKF]] 02:19, 21 April 2011 (EDT)

== THE SHORTCUT - A way to cheat a little. ==

I've only just returned to XCOM TFTD after a long break, so my memory on this is a little fuzzy.

What I found you could do was fire a Disruptor Pulse missile at the wall of one (or more) of the starting spawn areas on the top level. You'd have to park your Aquanaut as far as possible from the target point to avoid the blast. 1-2 shots at one wall section might destroy it and create a direct path into the central Synomium chamber. This way you can complete the main objective without having to meet any opposition.

You could just exit at that point if you want - though you'd be giving up on all that phat lewt!

I'm putting this in the discussion page for now, as I'm not sure you want possible cheats/exploits up on the main page.

: Due to the randomness of the layout, you would have to start quite near the synomium chamber for it to work. However, a small variation of this requires you to find the black chamber first (mouse cursor probing, or actual scouting), then fire a DPL in the area and angle it up towards the synomium device, bypassing the elevator completely. I think standing in one of the passages and firing up with a GC-HE shell or two will work for a more adventurous/low-tech solution. At the very least you won't have to deal with all the tentaculats in there and just hoof it back to the entry points! [[User:NKF|NKF]] 03:59, 29 August 2012 (EDT)

: Aha! But you do always start right next to the synomium chamber. You start randomly in four towers at the corners of the map. All four corners connect with the synomium chamber, which fills the space between the towers on the top level. You just need one chap with a DPL in one of the towers. Having your other Aquanauts spawn in other towers actually helps, because it allows you to orient your DPL guy correctly. If there are aquanauts in towers both West and South of him then the DPL guy is in the Northeast tower. He therefore needs to blast a hole in the Southwest wall to access the synomium chamber.

This used to work for me every time. I even stopped doing it for a while because I felt I wasn't playing the game the way it was meant to be played.

The only random element is the initial placement of the Aquanauts. Unlike the colony missions, all the Aquanauts will start within - or immediately below - one of the towers. If your DPL guy isn't in place at the top of a tower, it is easy to move him there.

== Synonium? ==

Why is this a spelling variant of the correct Syno'''m'''ium? Just to note, this is the spelling in-game and in the text files. Can I change the spellings to the correct one? --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 05:19, 4 June 2016 (UTC)

Talk:Scoring

2016-05-09T03:59:30Z

Zombie: /* TFTD */ My opinion.

Losing the game through finances - currently it suggests you lose if you are over $1 million in debt twice in a row, my tests seems to suggest they dont mention it until you are around -$1 million (not sure of exact figure yet, -$500k was okay though in a few tests). Just over -$1.6 million i got a warning three times out of four, the other time I lost the game (in February, so you dont need two in a row). At -$2.6 I lost 4 times of 8, at -$16 million it was 3/6, -$536 million 2/4. Seems like a boundary condition of a million in debt, then 50/50 you lose each month you are over that.

Checked the boundary, its actually $1,000,001 dollars overdrawn at the start of the new month (after council funding in, maintenance out), and i lost 1 out of 2 on february with that much debt, so presuming still you lose 50% of the time if past the boundary.

Will update the page to reflect this.

--[[User:Sfnhltb|Sfnhltb]] 12:12, 2 March 2007 (PST)

----

Amitakartok: I've personally had the number of funding nations reduced to a lone holdout. This means that if you can lose by losing all countries, the only way to do it would be to lose every single nation on the funding council. [[User:Arrow Quivershaft|Arrow Quivershaft]] 22:49, 18 January 2008 (PST)

: Just to elaborate a bit, if you do a little editing in diplom.dat so that all the countries sign a pact at the end of the month, the game doesn't end. Losing all the countries (even if it is possible) isn't one of the ways to end the game. --[[User:Zombie|Zombie]] 00:16, 19 January 2008 (PST)

Thank you for the response, Zombie; I'll edit that bit out of the main page. On a second note...I don't think the data about scoring is strictly accurate. I think that if you're running a deficit on your money and are below the amount the funding council likes, or have a bad score, it's not two consecutive months. It's simply that you have a 50% chance of being shut down. I say this because in prior games, I've had a poor score in a single month and got shut down at the end of the month. Similarly, I've run bad scores sometimes more than three months in a row and kept getting warnings about POSSIBLY getting shut down, but never actually do. I haven't tested this with money, but any insight into the situation? [[User:Arrow Quivershaft|Arrow Quivershaft]] 00:21, 19 January 2008 (PST)

:Well, I haven't done much editing to see what happens when funds are low. [[User:Sfnhltb|Sfnhltb]] did some tests on this (see top of this page) and his results seem to indicate a 50% chance your game will end if funds are below $1 million for even one month. So that basically backs up your observations. I would assume it also applies to score as well and there would be a 50% chance of getting shut down every month if your score falls below the skill-modified "bad" score level. --[[User:Zombie|Zombie]] 00:50, 19 January 2008 (PST)

Yeah, that's what I'm thinking. Currently it says that if you run a bad score for two consecutive months, they make you close up, but as I've noted, that doesn't seem to be the case. You want the honors? [[User:Arrow Quivershaft|Arrow Quivershaft]] 00:52, 19 January 2008 (PST)

:Ok, I just did some testing on score right now and it brought back a flood of old memories. See, I did some tests on this long ago and noticed something strange. With a score of -2062 for one month, the game always starts by giving a warning. If you reload the game, it terminates the project. Reload again and the game gives a warning. Reload again and it terminates. So here is where the 50% chance comes into play. This would indicate the roll isn't random, it's predetermined since the result is structured.

:Let's say you get a warning. Instead of loading the game, try aborting and then loading the game. The game only gives warnings now. See? Reloading the game without aborting plays a role in the result. But performing a fresh load always gives a warning and never terminates the project. So, I'll have to say the 50% deal only happens if you save a game and reload, the "true" result is that the game only gives a warning the first month. Confusing, eh? I'll have to test on the second month to see if the 2-month rule really applies. I bet it does. --[[User:Zombie|Zombie]] 01:35, 19 January 2008 (PST)

: Edit: the second bad month I had a score of -1663. Same deal as before. Initially it gives a warning, but if you reload the game without aborting it shuts you down. Therefore the 2-month rule doesn't apply either. Its a bug basically. An exploitable bug to be more specific. See the importance of thorough testing now? :O --[[User:Zombie|Zombie]] 01:46, 19 January 2008 (PST)

Wow, quite a find! I barely have the knowledge base for hacking and can struggle through it, but yeah, that shows what tests can do. In any case, that's a ridiculously simple bug to be exploiting, considering the amount of time one month of gameplay can take after including all the missions; many people will save and reload at least a time or two unless they've set the whole day aside! This should be added to the Exploits page, then...again, you want the honors? [[User:Arrow Quivershaft|Arrow Quivershaft]] 03:16, 19 January 2008 (PST)

:If I don't get to it, feel free to add away, Arrow. BTW: I just did some more tests, this time with funds. Edited my base to have a ton of Mind/Grav Shields and 250 Scientists/Engineers, then knocked my kitty down to $0. At the start of the next month I would be -$9,968,000 in the hole - enough to be below the $2 million debt level. It works exactly the same way as score, if below the level you just get a warning that month. Reload the game after that and you face automatic termination. Reloading after that and you get the warning again. Of course, if you abort and load the game, you always get the warning first. Not sure if the debt level is -$2 million or -$1 million as Sfnhltb mentioned, so I'll need to run some more tests. Anyway, it's an exploitation plain and simple no matter which way you look at the issue. --[[User:Zombie|Zombie]] 16:22, 20 January 2008 (PST)

----

== Alien Scoring: details? ==
I was thinking about [[Scoring#Alien Scoring|how aliens score]] and I had a bunch of unanswered questions...
* Does being shot down count as "landed"?
* Is there a time component for alien landing? Ie: Is it 2 points per instance an O becomes an X on the geoscape, or is it 2 points per ''30 mins'' a ufo has landed? (or per some other unit of time?)
* For abduction and harvest missions, what counts as ''"success"''?
* What's the maximum number of successes?
* Is it only if the ufo flies off to space unmolested?
* Is it each time it lands/takes off? (Ufos like to hop multiple times on those missions.)
* Each time it lands, does it harvest multiple times, resulting in 30 x 4= 120 score if lands once but makes off with 4 cows?
* When does it tick the score? On the act of landing, or the act of taking off, or on a certain time unit?
* Does it count as success if a ufo is shot down but a squad is never sent in to clean it up? (Crash just expires.)

BTW I assume that a player can view the total alien score by looking at the alien activity graph in the graphs menu. (Someone confirm?)

My gut tells me that a ufo can be "successful" multiple times in a single mission. Plus they continue to score if crashed and that crashing is effectively the same as landing. I base this on my general observations of the graphs rather than real testing. Without some extra ways to score over and above [[Scoring#Alien Scoring]] (or a more complex way of using that table) a typical ufo would get 10 points (20 if it was lucky) in my games. It's normally shot down as soon as it slows down enough to be caught, then it's immediately salvaged. The actual result of alien scores is much much higher.

Ufos score quickly while flying, and still continue to gain score after I've shot it down. (They would score slowly at first with a big jump at the end as they left if the opposite were true.) Plus it seems as though they often get a lot of score even if I shoot one down and immediately land to clean it up. 1 point per 30mins + 2 points (per 30mins or not) would be negligible if they weren't getting some mission score on top.
=== Example ===
A harvester ship on a harvest mission.
It flies over China for 5 hours. Lands for 10 hours. Flies for 6 hours, lands in Japan for 7 hours. Takes off and is immediately shot down by an interceptor waiting for it. The wreckage lasts for 3 days before disappearing. No UFO Crash Recovery mission attempted.
How much do the aliens score? I would guess:
(5hrs/.5 x 1)+ 30 +(10hrs/.5 x 2) + (6hrs/.5 x1) + 30 + (7hrs/.5 x2) + 30 + (72hrs/.5 x 2)
= 10 + 30 + 40 + 12 + 30 + 28 + 30 + 288
= 468 alien score

That seems high, way too high compared to actual. Cutting out the last variable (over half the total) is more reasonable. But I don't have a lot of data on that as I rarely leave a salvaged ufo, and always feel like I messed up if I have to. However I'm still pretty sure that a crashed ufo continues to tick the score. Maybe it goes to per day instead of per 30 mins? I don't know.

Anyone done any testing along these lines?

BTW I'm surprised that there isn't a wiki page for graphs, and alien scoring is barely mentioned across the whole site. It's a very important source of tactical information. I look at the aliens score every 12 hours or so to see if it's changed. If it has changed I can figure out where the aliens are and send in the planes. It effectively gives me world wide radar coverage long before I have HWDs, or even a 2nd base.
--[[User:Brunpal|Brunpal]] 11:27, 5 August 2008 (PDT)

:: Does being shot down count as "landed"? Not only does it not count, the alien score per game-time half-hour (as reported in the graphs, which are completely accurate) for a shot-down UFO is 0.
:: For abduction and harvest missions, what counts as ''"success"''? Same criterion as any other mission: the UFO disappears from the Geoscape on-schedule. Note that only an Avenger goes fast enough to even consider catching up to a UFO on a escape track, and obviously TerrorShips' normal escape is a terror site.
:: Ufos score quickly while flying, and still continue to gain score after I've shot it down. Because not all of them are shot down. In particular, the game starts with two UFOs at once, and only one of them is guaranteed to be working in your first bases' region of operations. So if you shoot down one UFO, that ufo is not scoring; the other one is. This gets really ugly if the other one isn't even in Interceptor range (it happens, although Base Nigeria means it doesn't happen a lot.) Things will get much clearer in-game once you have total-coverage hyperwave decoder detection.
:: However I'm still pretty sure that a crashed ufo continues to tick the score. Maybe it goes to per day instead of per 30 mins? I don't know. Mere confidence in categorical falsity doesn't make it so. Crashed UFOs do not tick up the score at all; furthermore, there is no special score tick for midnight (Skyranger just takes too long to get to a Siberia shootdown from Base Nigeria, so this was easy for me to test in vivo.) --[[User:Zaimoni|Zaimoni]] 16:50, 5 August 2008 (CDT)
:::''the game starts with two UFOs at once, and only one of them is guaranteed to be working in your first bases' region of operations.'' I'm aware of that. I'm not talking about the first day of the game, and I'm not simply forgetting to count one as you suggest. I also have total coverage with HWDs and seen the score behavior I describe above. (I have played xcom more than once in the many years I've had it.) I can also tell when the score has changed and when it '''has not''' changed so I know and can account for ufos and can discount undetected bases. (Score can't be flat with an alien base.) In different games I've seen the aliens score quickly in rapid jumps that isn't explained by 1 point per 30mins or 2points per 30mins while landed*. I do know how to read the graphs and I don't only look at total score. I break it down by region. I'm not going to miss another UFO in the same region as my main base with a HWD and 2 interceptors buzzing around looking for it. I'm certainly willing to accept that a crashed ufo is worth 0, but I've seen behavior in the score not explained by [[Scoring#Alien Scoring|the known chart]] and not explained by undetected activity.
:::BTW *The 2 points while landed ''per 30 mins'' is not listed on [[Scoring#Alien Scoring]].--[[User:Brunpal|Brunpal]] 20:55, 5 August 2008 (PDT)
==Test results==
I've discovered something while watching the score closely. A battleship on a harvest mission '''got points soon as the ufo took off'''. The landed ufo at 18:25 had 60 points in China at ~18:35 it took off and at 18:45 China had 90 points. It quickly flew off the Earth and maybe hit 1 or 2 half hour ticks. It may have scored an extra point or 2 world wide but wasn't able to see any measurable difference in the graph before OR after it left detection. It only landed the once. It got no extra points for landing, but did tick up points at 2 per 30mins while on the ground.
*'''Therefore an alien harvest mission counts as success as it takes off.''' Leaving the geoscape doesn't matter at all for score. Hopefully I'll encounter a harvest mission where an ufo lands multiple times to test if it's the first or last time it takes off, or every time it takes off.--[[User:Brunpal|Brunpal]] 21:19, 6 August 2008 (PDT)
*I had a single sectoid harvester on a harvest mission. It landed twice. Watching the score closely it scored 30 points each time it took off. If I forced it to take off early by sending a skyranger there and then immediately aborting mission, it still got 30 points as soon as it took off. Therefore a single ufo can ''succeed'' at a mission multiple times.[[User:Brunpal|Brunpal]] 19:51, 7 August 2008 (PDT)
*Single terror ship on a terror mission. It did not land. I ignored it for the total 7 hours it was on Earth. World wide score ticked up a total of 14 points. (1 point per 30mins) It did not get any mission points which is the expected result.--[[User:Brunpal|Brunpal]] 11:36, 18 August 2008 (PDT)

:A Terror Ship on a Terror Mission sometimes will not land if you shoot down the scouts before the Terror Ship(which will also read as on a Alien Terror mission). Instead, it will randomly wander around the map for a bit, but since it lacks a city to target, will do nothing, and eventually leave. Since it did not do its job(spit a bunch of aliens into a major population center), this would stand to reason it would not have accomplished its task and thus would not earn "Mission Completed!" points. (For reference, Terror Ships which have a city as a target will steam towards that city at maximum speed.) [[User:Arrow Quivershaft|Arrow Quivershaft]] 11:41, 18 August 2008 (PDT)

: The first TerrorShip (indexing 2/0) [[UFO Flight Patterns#Terror_UFOs|need not land]] even if you do not shoot it down, so it should not get mission points. --[[User:Zaimoni|Zaimoni]] 10:08, 19 August 2008 (CDT)
:Yup. I'm aware of that ufo behavior being normal. I'm just examining the effects on score. Nothing weird happened that's why I called it an "expected result".--[[User:Brunpal|Brunpal]] 15:03, 28 August 2008 (PDT)
*Single snakeman large scout on a terror mission. It landed in remote area. I took a save as soon as it landed, and as it took off 6 hours later. Comparing alien.dat values it gained 33 points. Expected value is 24, not 33. (=6hrs/.5 x 2 points). Even if the ufo double counted the start and end blocks as landed and flying at the same time this doesn't account for 9 points. Watching the graph carefully every few seconds there was a jump in score as it took off so that's when it got the extra 9 points. Therefore unexplained increase in alien score has been found.

*Same Ufo flew for an extra 5 hours and landed 2nd time for 6.5 hours. 46 points tallied in this time. Expected should be 10 points for flying and 26 while landed for 36 total. Something else is interesting about these numbers; If the ufo was landed for the full 11.5 hours instead of flying around looking for a spot to land it would have scored 46 points according to the known 2 points per 30 mins for landed ufos. Assuming I was a little slow on my reactions the first time, aliens scored a bonus 10 points for taking off both times. '''This is either a flat bonus of 10 points for a tiny terror ''mission succeeded'' or perhaps a revaluation of the time it spent flying as 100% landed.'''--[[User:Brunpal|Brunpal]] 14:52, 28 August 2008 (PDT)

==Destroying Larger Craft and Skyranger Being Shot Down==

Jasonred: In answer to your comments, this data is taken straight out of the executable. There is no practical way to destroy the larger UFOs. To ground a UFO(crash-land), you need to deal more than 50% of its HP in damage to it. To destroy it, you have to deal 100% or more of its HP in damage. This precludes X-COM from destroying the Supply Ship, the Terror Ship, and the Battleship(outside of glitched or hacked craft weapons). However, it IS possible, albeit '''incredibly''' unlikely, for X-COM to destroy the Harvester and Abductor with twin [[Fusion Ball Launcher]]s. Craft weapons deal between 50% and 100% of their damage listed in the UFOpaedia. The FBL has 100% accuracy...if the first two FBs hit and deal minimum damage(115 each), they would deal 230 damage to the UFO...below the 250 needed to crash it. The next shot, both hit again, and if they do more than 270 damage, the UFO will be vaporized. So while you can destroy up to medium sized UFOs, its very unlikely you'll incinerate anything larger than a Large Scout.

As for shooting down the Skyranger, that can only happen if the game has been edited to allow the Skyranger to mount weapons(XComUtil does this). Then you can send it into battle and let it get shot down to your heart's content. Of course, you lose the same points if it's lost on a ground mission. The reason the Skyranger has "Shot down" points and the large UFOs have "Destroyed" points in the executable has very little to do with how feasible it is and a lot to do with preventing crashes and keeping the data reading code simple. [[User:Arrow Quivershaft|Arrow Quivershaft]] 20:42, 26 February 2009 (CST)

:Hmm... can you destroy those craft by assigning multiple craft armed with Fusion Ball Launchers at them? Assuming that you get simlutaneous hits?
:As for the skyranger, it CAN get blown up, quite easily... just set your skyranger to Aggresive Attack... despite not having weapons, it will close in to point blank range, and will soon get shot down. [[User:Jasonred|Jasonred]]

The larger craft? No, because as soon as the UFO goes over 50% damage, it crash-lands. Shooting more guns at it will simply make it crash faster, since the faster you shoot, the faster you get above 50%, but you're still incapable of dealing out more than 460 damage in a single attack, which means you aren't able to breach that rather large gap between 49% damage and 100% damage. As for the Skyranger, in order for it to be able to intercept at all, a craft must have a hardpoint on it(even if no weapons are mounted.) A Skyranger in a default game can't even be sent to intercept a UFO, as it has no hardpoint. XComUtil will give the Skyranger a hardpoint by default, thus allowing it to intercept UFOs and shoot them down and get shot down. [[User:Arrow Quivershaft|Arrow Quivershaft]] 21:34, 26 February 2009 (CST)

NO, you can always launch a skyranger to intercept a UFO. In fact, you SHOULD often do this, since it's better to start tailing it before it lands, rather than wait for it to land first. I just checked, you can definitely do so. The only problem is that just about any UFO can outrun your skyranger.
As for the multiple aircraft, I was hoping that the UFO would start to crash land, and be hit by the Fusion Balls in mid-air. Similiar to how mounting 2 Fusion Ball Launchers instead of 1 will let you destroy a large scout instead of forcing it to crash land?
[[User:Jasonred|Jasonred]] [[User:Jasonred|Jasonred]] 22:10, 26 February 2009 (CST)

:: I must concur that you can indeed "attack" a UFO with an unarmed Skyranger in the plain vanilla non-X-Comutil games. Back in my n00b days, I used to send them out against UFOs to soak up some damage to give the interceptors a fighting chance. They have more hitpoints than the Interceptor. Though since discovering that the fire rate vs. individual interceptor varies independently of the interceptor's range to the UFO (say if you had two engaging a UFO at the same time, one at aggressive firing range will get attacked a lot more frequently than one at cautious range), I'm beginning to wonder if they ever did split their attacks. Oh yeah the Skyranger's also the last ship you want in a dogfight, since it can't really keep up, but still... -[[User:NKF|NKF]] 23:15, 26 February 2009 (CST)

Yes... I wonder about this myself. Must check how much damage is received when I attack a battleship with 1 avenger, 2 avengers, 3 avengers, 4 avengers. In theory, 4 avengers kill a battleship in 1/4 the time taken by 1 avenger. Therefore, the battleship should only perform 1/4 TOTAL damage, compared to 1 avenger. Therefore, on average, 4 avengers should receive 1/16 damage EACH.
It doesn't seem like that, to me. I suspect that the UFOs get to fire at all your ships at the same time. Cunning evil bastards.
Can someone test this out for us?
... yes. Those skyrangers have a LOT of HP. [[User:Jasonred|Jasonred]] 23:35, 26 February 2009 (CST)

:Just found this comment - I did indeed to the "1 Avenger, 2 Avenger, 3 Avengers, 4" test. Well sort of. I was seeing how long the Avengers take to get shot down, rather than how long the Avengers take to shoot the UFO down. Here's a link to the stuff.

[[Talk:UFO Interception#Survival Time of Multiple Attackers]]

It's not the most rigorous of tests but it's not totally sloppy either. YMMV, as they say. [[User:Spike|Spike]] 15:39, 9 August 2009 (EDT)

==Stunning Civilians==

''"Yes Major, I've met some stunning civilians in my time... now where was I? Oh yes. Review of the advisability of the use Stun-type weapons on civilians in a terrorist-type situation, for their own protection, obviously. The fact that it '''hugely''' simplifies X-Com's tactical situation during the Op is just an added bonus, don'tcha know?". ''

It looks like when you stun civilians, you do not get the "Civilian is Saved" bonus, but neither do you get the "Civilian Killed by Aliens" penalty nor the "Civilian killed by X-Com" penalty.

''"In conclusion, Major, it seems the Powers-That-Be would really prefer we just let the darned civvies wander about as they please, right in the middle of our Op! Outrageous! How can we be expected to save the world, working under conditions like this. I ask you!"''

[[User:Spike|Spike]] 15:39, 9 August 2009 (EDT)

==Captured aliens==
Okay, I'm hereby challenging the "captured alien" points as they're written. In my game I have had five captures so far - a Reaper, a Floater Navigator, two Floater Engineers, and a Sectoid Leader. The Navigator and Engineers were in the same mission, so I don't know what I scored for those, but I scored 0 points for capturing the Reaper and 10 points for capturing the Sectoid Leader. This is in direct contradiction with the point values and explanation given. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 03:02, 30 April 2016 (UTC)

== TFTD ==

I'm wondering if we should make a "Scoring (TFTD)" page. While the basic mechanics are the same, there's a few differences in numbers (among other things, the lose-the-game cutoff differs on high difficulties) and the Artefact Sites have new scoring mechanics.

Any opinions? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 03:17, 7 May 2016 (UTC)

:I vote to create the page as I think there are enough differences in scoring between the games to warrant it. --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 03:59, 9 May 2016 (UTC)

Talk:UFO Interception

2016-05-09T03:54:43Z

Zombie: /* When do most people bother intercepting? */ Formatting.

==Pursuit==

TBD: Discuss pursuit on the Geoscape, bad intercept vector algorithm, speed differences, etc.
Also re-engaging targets, targets that land, over land vs over water, multiple interceptors.

==Engagement==

===Interception Attack Modes===

[TBD Summarise. Actually the main article already summarises this well.]

I noticed recently that the different attack modes have different functions. I'll briefly summarize what I saw here, and if someone can confirm, we can add it to the wiki.

Cautious Attack: Enter range to fire with longest range weapon. Pull back to standoff distance if craft takes damage from UFO return fire. 
Standard Attack: Enter range to fire with both weapons. Pull back to standoff distance if craft takes significant damage from UFO return fire [in one shot?]. 
Aggressive Attack: Chase UFO to get as close as possible(64 range units), firing weapons all the way. Never pull back to standoff distance.

Also, the UFO seems to have a greater chance of running away at the more cautious settings, [and vice versa] but that makes sense. ;) [[User:Arrow Quivershaft|Arrow Quivershaft]] 01:29, 29 February 2008 (PST)

: I'm not entirely sure what the differences in behaviour regarding pulling out into standoff range when damaged are between the various modes (hadn't really noticed it too much myself), but the modes mainly function at adjusting the range of the craft and UFO.

: In short: out of firing range, longest ranged weapon, shortest range weapon and as close as possible. One note about cautious mode is that it will revert to the next closest ''loaded'' weapon. If the longest range weapon runs out of ammo, the ship will close in to the next best weapon.

: It's odd we left this explanation out, but yeah it needs to be there. - [[User:NKF|NKF]] 02:22, 29 February 2008 (PST)

Any Interception craft at "Cautious Attack" that takes damage will attempt to retreat out of range to Standoff distance. Craft on "Standard Attack" will do the same sometimes. I see it most often when chasing Battleships with Firestorms or Avengers, and they get knocked good by a shot from the Battleship. Happens more often with Firestorms, so it's probably percentage based. Craft on "Aggressive Attack" will never return to standoff distance unless changed to a different mode or ordered to pull back or disengage; in that mode, the mentality is "Him or me."

I don't get to see this much anymore because I usually use Aggressive Attack because a lone Avenger can go toe-to-toe with a Battleship and still make it back in fairly good shape(30% damage or so). A Firestorm can usually manage to limp back as well, but in considerably worse condition. [[User:Arrow Quivershaft|Arrow Quivershaft]] 12:25, 29 February 2008 (PST)

----

I've changed the main page to show some scepticism as to whether UFO damage vs interceptors increases due to interceptor attack mode. I don't believe it does. [[User:spike|Spike]] 08:40, 16 August 2014 (PST)

====Engaging with multiple craft====

If I understand the latest edit, UFOs will not "divide" their fire amongst multiple targets, but will fire at each of them as frequently as they would fire at a single ship. If that's the case, is there really any advantage to having all ships engage at the same time?--[[User:Ethereal Cereal|Ethereal Cereal]] 15:29, 5 March 2007 (PST)

Thats because whoever wrote it was a moron, thats precisely what doesn't happen as I finally managed to identify just before writing it. Its tough to tell though, especially as you cant get them all to go in at once, and if you go in on aggressive attack it gets very quick at the end and hard to say whats going on. --[[User:Sfnhltb|Sfnhltb]] 15:43, 5 March 2007 (PST)

The most convincing aspect for me anyway was the results - three interceptors armed with plasma mostly going in singly almost always get eaten, three at once (or as close as you can get it, and setting the cycle speed way down helps synchronise them better) nearly always wins and often doesn't take a single casualty. --[[User:Sfnhltb|Sfnhltb]] 15:47, 5 March 2007 (PST)

: From what I can remember, the UFO's rate of fire gets faster and faster the closer you get to the UFO. I've tested this with two different ships with identical armament, with one on aggressive and the other on cautious. The one on cautious fired normally, but the one that got right up to the UFO was exchanging and receiving ammo at a considerably faster rate than the one on cautious.

: That still this doesn't answer the question wether the UFO splits the attacks or fires on the ships normally.

: Still, I find the odds of knocking out a UFO with multiple ships a lot better than to attempt it sequentially. (edit: or mind you if I'd checked through all the edits, all this has been covered already. Oh well.) - [[User:NKF|NKF]]

:I did 10 tests each way yesterday from the same save - sequentially 1 win from 10, even that the last interceptor was fully red damage at the end (cant tell the exact numbers, for some reason after the fight the geoscape was zooming out past maximum and crashing to the battlescape). Simultaneous was 9 wins from 10, 0 shot down 2 times, 1 down 4 times, 2 down three times. I then did a few further tries later with all three having slowed the cycle rate down and got 0 shot down 3 times out of 4, as generally the first one in was the one that almost always died if any did, if you can get them all attacking closer together it ensures it doesnt take the first two or two of the first three salvoes. --[[User:Sfnhltb|Sfnhltb]] 05:06, 6 March 2007 (PST)

I think some of what's written at [[Battleship#Weapons]] should be copied over. I've never tried it myself, personally; I don't bother engaging battleships until I have an Avenger. What I'd really like is some way to stop Terror Ships before I get Plasma Cannons... two Interceptors armed with Avalanches? Or does it take three?--[[User:Ethereal Cereal|Ethereal Cereal]] 21:59, 5 March 2007 (PST)

:From the encounter I had yesterday, would suggest 3 is needed, it can trash them so quickly that you need to throw in loads. The one thing I noticed was that Avalanches in some ways seemed better than the Plasma cannons because you can get off a 1-2 rounds of missiles before the Plasma even starts firing due to the range difference, which is critical with your paper thin Interceptors vs the Battleships. --[[User:Sfnhltb|Sfnhltb]] 04:56, 6 March 2007 (PST)

:2 interceptors with avalanches can bring down a terror ship and make it back to base in one piece. I think 10 avalanches will kill it. You do need to do the agressive trick with at least one interceptor to make sure all 6 missiles actually hit.
:(Never tried interceptors vs battleship, it sounds suicidal.) --[[User:MB|MB]] 11:56, 6 March 2007 (PST)

===Review of Air Combat Mechanics===

Moved to its own article [[Air Combat Mechanics]]

==Operational and Logistic Aspects==

===[[Repairs]]===
===[[Refueling]]===
===[[Rearming]]===

*Seb76 Loader option to relaunch aircraft before they are fully ready.
*Add link to "Duty Cycle" discussions & table

===Patrolling fuel usage===

TBD: Summarise fuel consumption for patrol/not, hybrid/not.
----

I saw somewhere that the skyranger at least uses less fuel when patrolling, but I have this vague recollection that the hybrids don't. Am I right in this or does it need investigating to determine one way or the other? --[[User:Sfnhltb|Sfnhltb]] 16:05, 5 March 2007 (PST)

:You are correct, hybrids don't conserve fuel while patrolling. Only the originals do. --[[User:Pi Masta|Pi Masta]] 17:15, 5 March 2007 (PST)

::That does appear to be the case. I just tested this with a Firestorm (not an Avenger), and there were a few quirks: fuel consumption was the same whether patrolling or not (which is what you were asking about); fuel readout only decreased in 5% increments (not well-documented); it returned to base when it hit 50% fuel, regardless of distance-to-base (argh). (Skyrangers and Interceptors will stay out below 50%, based on distance.) Fuel consumption was 0.5% of total per minute.

::A patrolling Skyranger used up 0.02% of fuel per minute. A constantly-moving one used up 0.0455% per minute. This is more or less consistent with what is documented at [[Skyranger]].--[[User:Ethereal Cereal|Ethereal Cereal]] 18:29, 5 March 2007 (PST)

==Strategic Aspects==

===Scoring vs Location of Intercept===

I am currently on 23rd January, so should be able to check whether XCOM Activity relates more or less directly to your pay rise at the end of the month fairly soon, but if it does then clearly you will always want to shoot down UFOs over a sponsor country instead of neutral territory (especially the big scoring recovery missions).

--[[User:Sfnhltb|Sfnhltb]] 06:31, 28 February 2007 (PST)
----
IIRC the amount of money you get is randomly assigned, though increase, decrease, or no change is based upon 'score', and the country's 'happiness' with XCOM. I think this can be seen by saving near the end of the month and noting the funding changes on each save (w/o doing anything special), I believe each time they will be random amounts (but again the sign of the change is dependent on the score, directly or indirectly).

I'm not sure if a higher score as an effect on the average increase (or conversely lower score with average decrease). It is possible. However I imagine that you are still correct that downing a UFO over a sponsors country is better than over a neutral country.
[[User:Pi Masta|Pi Masta]] 11:51, 28 February 2007 (PST)

:Hmm, we should add a graphic to the wiki showing where the sponsor land masses are.--[[User:Ethereal Cereal|Ethereal Cereal]] 12:22, 28 February 2007 (PST)

Yeah I had noticed it was random, I think your starting cash is as well, where the random range comes is was something I will be testing at the end of the current month of the game I am on, which might take a while as I am only playing intermittently (lots of work on atm)

--13:11, 28 February 2007 (PST)

----
Don't bother with the funding deals. I did this looong ago, both at the [http://www.strategycore.co.uk/forums/index.php?showtopic=652 StrategyCore forums] as well as a complete country-by-country funding breakdown at the [http://www.xcomufo.com/forums/index.php?showtopic=7424 xcomufo.com forums]. Granted, this was for the starting funds, not for subsequent months. But I did run about 2000 trials on that scenario and found that funding was random within a certain range. --[[User:Zombie|Zombie]] 14:44, 28 February 2007 (PST)

Hmm, well compared to the starting funds that you tested that were almost static overall (unless I am misreading it, +/- 15k or so?), the monthly amount varies a whole lot more, certainly +/- 250k from the average on a given good month I tested briefly to get an idea of it (and could grow more for an even better month I suspect). I would be interested in finding out what exactly affects it, and how responsive it is to key elements you might be able to control (like how beneficial is shooting down more aliens in sponsor country, compared to the same region (if that affects anything at all), and overall.

Btw, in case you still are thinking about the question regarding the discrepancy between your income and expenditure at startup, i can tell you where the 1860000 comes from at least - its in LIGLOB (A0611C00 in backwards hex) - its basically the source of the Finance graph (except score, which comes from XCOM.DAT combined with UIGLOB), which of course assigns it all to Maintenance - which in theory could include 1.7 million for the planes, 300k for the scientists, 250k for the engineers, 160k for the soldiers, and 224k for the maintaince of facilities of the base, so it doesnt solve it, but at least you can eliminate paying for things in trying to work out what it is.

The most obvious answer here is that you pay for craft rental (1.7 mill) and your soldiers (160k) = 1.86 million, and you dont pay for the scientists, engineers or base maintainance. --[[User:Sfnhltb|Sfnhltb]] 16:41, 28 February 2007 (PST)

----
The monthly funding (according to the OSG) is determined by these two equations:

Alien activity in country + (Overall alien activity/5) 
X-COM activity in country + (Overall X-COM activity/10)

These numbers are compared and if the alien score is greater than X-COM, the country decreases funding by a random amount, but no less than 20%. If X-COM is greater than the alien score, the country increases funding by a random amount, but no greater than 20%. I'm not sure what the upper or lower boundary is. It could be 0%. Who knows, the frequency of the non-20% limits may increase as score does. Suppose the easiest way would be to edit alien score to 0 and X-COM score to something high and check the results. That would correspond to "EXCELLENT" on the End Of Month report. Another test is to edit both X-COM and alien score to zero and check the funding there. This would correspond to "OK" on the EOM report. One thing is for certain, it would take a great many reloads to form any type of conclusion. One of these days I'll have to write up an AHK script and dedicate some computer time to this project. It won't be right away though. --[[User:Zombie|Zombie]] 21:47, 28 February 2007 (PST)

:Ah, that explains something I was seeing - basically if you get double the Alien score, everything is good, if you are less than that everything is bad. When using very large numbers that is, to minimise other factors.

:I think the increase is between 5-20%, if they come up as happy. But sometimes even with the same scores they turn out just to be satisified (current game I am playing, overall score 2.6k, alien score was 132 (and I think quite a bit of that I am double counting, country and region)

:And yeah, no matter how high the XCOM scores went (very high values in the 4th byte didnt register, but I could get 30k or 60k I think, and there was no change in the range of values to cursory inspection at least. I am fairly sure that happy/satisfied/unhappy is an on/off switch that is fired by a comparision of the scores in a manner as you list above (but there is some randomness in it however).

:The scale of the increase in funds seems to be based entirely on the existing funding level, so basically you just get a random percentage value within fixed limits (5-20% on the upswing, havent explored going down enough to say with enough confidence). If US is paying out 10 Million (and you have removed the funding cap, or it wont go higher), values are in the range of 500k to 2 Million if it increases, or 0 if they are only satisfied.

:There isnt a whole lot of random numbers it rolls either, which you see with that nice round 10 mill, you get nice neat values spread out every 100k (rounding issues would make it look like there were more possibilities with a smaller existing fund). So its a random int between 5 and 20. Going down is probably a mirror image I would guess, but thats not got any real evidence behind it. --[[User:Sfnhltb|Sfnhltb]] 18:16, 1 March 2007 (PST)

==When do most people bother intercepting?==
I'll be frank, I usually don't bother. The Elerium and loot is worth more than the UFO Downed points (funding changes are typically on the order of half a million or less; one Medium Scout and one Large Scout saved from Power Source detonation give $660,000 just in extra Power Sources and Navigations), and I can handle a night mission or two. I only bother intercepting in a few cases:
*'''Small Scouts''' - Downing them doesn't lose anything. Destroying them loses the alien's gun, but they don't generally land and downing them safely is nearly impossible before advanced craft. Pretty easy choice.
*'''Alien Retaliation''' - Nothing on that mission ever lands recoverably, so this is another no-brainer.
*'''Terror ships performing Alien Terror''' - They don't land recoverably. See above.
*'''Alien Base flotillas''' - Unless you've got multiple squads, you can't Ground Assault all four ships in the flotilla. And shooting down some of them breaks up the flotilla (because any that haven't spawned yet will get delayed), so you can get in two Ground Assaults instead of potentially only one. I'll take two Ground Assaults and two Crash Recoveries over a single Ground Assault any day.
*'''Alien Infiltration''' - Not only is there a five-ship flotilla at the end, but Alien Infiltrations have a large and direct impact on X-Com's financing in addition to the points issue. You can't stop them, of course, but you can delay them, and since the mission repeats until all countries in the region are infiltrated, the delays are cumulative (potentially keeping countries in for several months longer than they would otherwise have lasted). So I generally shoot down as many of these as possible.

I just kinda wonder what we should say about this dilemma and where we should say it. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 03:57, 7 April 2016 (UTC)

: I think this is really best left up to the judgement of the player as the ability to get to a landed UFO can be quite situational. In the early game, unless you are plain lucky or have lots of bases, your Skyranger is most likely not going to be able get to every landed UFO in time. You need the ability to shoot down the UFOs in this instance if only to get some work at the lesser reward. Later in the game you have more options on how to approach the UFOs as you spread out and get better tech to find and deal with them. This is when you can start going for landed UFOs. Much later into the game you'll have enough resources that you end up shooting down the UFOs down simply for the sake of shooting them down and ignoring the crash sites. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 06:11, 7 April 2016 (UTC)

I don't find it difficult at all. You usually detect UFOs on the flight in (or on the flight out, but in that case you can't do anything about them anyway). When you detect it, you send an Interceptor to shadow it and a Skyranger to the area it seems to be heading for, changing it to intercept when it gets close enough. Maximum time for the Skyranger to arrive in any location is 14 hours and it's usually a lot less; you'll generally be detecting the UFOs 4-5 hours before they land and they land for several hours. It's rare that you'll actually be unable to get there until you're dealing with actual antipodes (and at the point you're running Hyper-Wave Decoders on six continents, you're in most cases getting instant detection on UFO appearance, giving you significantly more time). [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 06:39, 7 April 2016 (UTC)

Oh, something else that factors in that I forgot to mention: interception draws Retaliation, while Ground Assaults don't. Intercepting too early on Superhuman is one of the more plausible ways to lose outright, because if you get a Sectoid Retaliation on your main base in January you'll have a very hard time recovering. Later on, of course, the Retaliation spiral (Retaliation -> shoot down scouts to avoid Base Defence -> more Retaliation) is a good thing for X-Com, but starting it too early is suicide. I know my first attempt at TFTD Superhuman came to an ignominious end that way. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 01:22, 7 May 2016 (UTC)

:I agree with a lot of points everyone brings up. For me, the decision to intercept instead of going for the landed UFO or ignoring it altogether is situational. Mostly it depends on UFO mission type, craft type, location, severity and quantity.

:*'''Mission Type''': Early in the game you need points to keep your score up in order to eclipse what the aliens can manage themselves and you also need alloys/elerium/bodies/weapons etc for research/manufacturing/funds. If a mission UFO is going to land, I'll wait for it to do so. Why bother wasting a missile on it? (Pending night time missions may prompt an interception to make things safer/easier). Obviously, if there is going to be a Terror Mission, I'd much rather shoot the UFO down so I don't have to deal with the hefty penalty if the mission goes pear shaped, or to defend the stupid civilians. Alien Resupply? C'mon, it always lands so you might as well wait (or ignore). Retaliation? Might as well shoot everything down, you don't want to lose country funding. Research? Ignore for the most part, unless nothing is going on. Harvest? Wait - most land and the ships are easy to recover. Abduction? I normally shoot these down if possible. While not overly critical, I don't want the aliens to get too many points. Alien base building? Yeah, I'll try to, especially with the tougher races. Otherwise the base itself is faster to take out than the UFOs building it.

:*'''Craft Type''': With Small Scouts, it's faster to just shoot them down and destroy them outright rather than waste an X-COM ship with weaker weapons on it. Medium or Large Scouts I'll try to let land. Same for harvesters or abductors. As I mentioned above, wait for the Supply Ships to land and shoot down the Terror Ships. Battleships are the only ship where I have to make a decision on it. Can my troops handle it? Can my ships handle it? Will it land on it's own? What is the race? What is the mission? Those all factor into a final decision.

:*'''Location''': If an alien mission is being carried out halfway around the world, I'm more likely to shoot it down as it takes time for the Skyranger to get there.

:*'''Severity''': As mentioned above, a mission with a higher severity will be met with interceptions.

:*'''Quantity''': If the UFOs arrive one at a time with days between landings, you can go after them while landed as there isn't a rush. What throws a spanner into the works is when the ships arrive in a big wave or group. If all of them are going to land, you can probably get to at least a couple before the rest take off and leave for good so I usually shoot down most of them and leave a couple. Visit the landed ones first, then go after the crashed ones when time permits. --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 03:52, 9 May 2016 (UTC)

=Misc=

==Old Chat==

===Ye Olde Bayse Maynetaynanse===

Of course the thing that has lead me onto, is trying to work out how it calculates base maintenance. A lift only new base costs 30k (4k for the lift, 26k extra somewhere), and a vanilla starter base costs 224k, but the parts only add up to 169k, so the extra unassigned part raises to 55k. Whats going on?

So I dismantle the starter base (after dumping all loose objects like people, planes and guns), the first Hangar drops the cost by 10k (not 25k), the next one by 4k (huh?), then 10k again for the last hangar, workshop drops it by 35k (correct!), the radar drops it another 35k (way high!), the living quarters are 30k, the lab 35k (a bit high), the stores 35k (massive - 7 times what it should be), and the lift 30k (4k in UFOpedia).

I thought maybe this was messed up somehow because of being the starter base, but it seems to behave the same way in new bases - as I say empty base with lift 30k, lift + stores + small radar = 95k, adding alien containment, stores, living quarters to starter base is 55k up on the starting cost (second stores 10k off when removed, second living quarters 10k, alien containment 35k)

So the same facilities take different maintainance depending on how many you have of them (it seems), and most of them cost different to what it says they do. No idea what the relationship or reasoning is behind all of this.

--[[User:Sfnhltb|Sfnhltb]] 17:05, 28 February 2007 (PST)

:No what's happening is that there are completed 'empty' modules. When you dismantle a facility it doesn't set the days to build to 255 like it should, and instead just puts the dirt tile there. Apparently these completed dirt modules take monthly maintenance (but isn't shown in the monthly costs IIRC). If you want me to find the post I can, but this is something I'm familiar with and in fact the 'editor' I'm making (PyXCom) should be able to fix it. (another thing is even if you build something and dismantle it before it's built, it will still count down and suck your money away)

:Atleast I think this is the issue you are having. [[User:Pi Masta|Pi Masta]] 19:57, 28 February 2007 (PST)

No I worked it out, I added the basic details to [[Known_Bugs#Facility_Maintenance_Costs]], there might be something additional as you say, as destruction a facility doesnt clear the construction counter as you say - in fact you can see that it keeps construction counters from previous saves as well at times, the clearest indication its doing stuff like this is if you start a game and name your first base something long, say 'ABCDEFG', and then start again and make a new base with a one character 'X', in the BASE.DAT you will see something like 'X CDEFG' (the space indicating actually a null (00) to show end of string). So when you save it doesnt 100% overwrite all bytes, just the minimum it needs to save the information for your current save (which may have errors like you suggest).

--[[User:Sfnhltb|Sfnhltb]] 20:03, 28 February 2007 (PST)

Talk:UFO Interception

2016-05-09T03:52:57Z

Zombie: /* When do most people bother intercepting? */ A few reasons.

==Pursuit==

TBD: Discuss pursuit on the Geoscape, bad intercept vector algorithm, speed differences, etc.
Also re-engaging targets, targets that land, over land vs over water, multiple interceptors.

==Engagement==

===Interception Attack Modes===

[TBD Summarise. Actually the main article already summarises this well.]

I noticed recently that the different attack modes have different functions. I'll briefly summarize what I saw here, and if someone can confirm, we can add it to the wiki.

Cautious Attack: Enter range to fire with longest range weapon. Pull back to standoff distance if craft takes damage from UFO return fire. 
Standard Attack: Enter range to fire with both weapons. Pull back to standoff distance if craft takes significant damage from UFO return fire [in one shot?]. 
Aggressive Attack: Chase UFO to get as close as possible(64 range units), firing weapons all the way. Never pull back to standoff distance.

Also, the UFO seems to have a greater chance of running away at the more cautious settings, [and vice versa] but that makes sense. ;) [[User:Arrow Quivershaft|Arrow Quivershaft]] 01:29, 29 February 2008 (PST)

: I'm not entirely sure what the differences in behaviour regarding pulling out into standoff range when damaged are between the various modes (hadn't really noticed it too much myself), but the modes mainly function at adjusting the range of the craft and UFO.

: In short: out of firing range, longest ranged weapon, shortest range weapon and as close as possible. One note about cautious mode is that it will revert to the next closest ''loaded'' weapon. If the longest range weapon runs out of ammo, the ship will close in to the next best weapon.

: It's odd we left this explanation out, but yeah it needs to be there. - [[User:NKF|NKF]] 02:22, 29 February 2008 (PST)

Any Interception craft at "Cautious Attack" that takes damage will attempt to retreat out of range to Standoff distance. Craft on "Standard Attack" will do the same sometimes. I see it most often when chasing Battleships with Firestorms or Avengers, and they get knocked good by a shot from the Battleship. Happens more often with Firestorms, so it's probably percentage based. Craft on "Aggressive Attack" will never return to standoff distance unless changed to a different mode or ordered to pull back or disengage; in that mode, the mentality is "Him or me."

I don't get to see this much anymore because I usually use Aggressive Attack because a lone Avenger can go toe-to-toe with a Battleship and still make it back in fairly good shape(30% damage or so). A Firestorm can usually manage to limp back as well, but in considerably worse condition. [[User:Arrow Quivershaft|Arrow Quivershaft]] 12:25, 29 February 2008 (PST)

----

I've changed the main page to show some scepticism as to whether UFO damage vs interceptors increases due to interceptor attack mode. I don't believe it does. [[User:spike|Spike]] 08:40, 16 August 2014 (PST)

====Engaging with multiple craft====

If I understand the latest edit, UFOs will not "divide" their fire amongst multiple targets, but will fire at each of them as frequently as they would fire at a single ship. If that's the case, is there really any advantage to having all ships engage at the same time?--[[User:Ethereal Cereal|Ethereal Cereal]] 15:29, 5 March 2007 (PST)

Thats because whoever wrote it was a moron, thats precisely what doesn't happen as I finally managed to identify just before writing it. Its tough to tell though, especially as you cant get them all to go in at once, and if you go in on aggressive attack it gets very quick at the end and hard to say whats going on. --[[User:Sfnhltb|Sfnhltb]] 15:43, 5 March 2007 (PST)

The most convincing aspect for me anyway was the results - three interceptors armed with plasma mostly going in singly almost always get eaten, three at once (or as close as you can get it, and setting the cycle speed way down helps synchronise them better) nearly always wins and often doesn't take a single casualty. --[[User:Sfnhltb|Sfnhltb]] 15:47, 5 March 2007 (PST)

: From what I can remember, the UFO's rate of fire gets faster and faster the closer you get to the UFO. I've tested this with two different ships with identical armament, with one on aggressive and the other on cautious. The one on cautious fired normally, but the one that got right up to the UFO was exchanging and receiving ammo at a considerably faster rate than the one on cautious.

: That still this doesn't answer the question wether the UFO splits the attacks or fires on the ships normally.

: Still, I find the odds of knocking out a UFO with multiple ships a lot better than to attempt it sequentially. (edit: or mind you if I'd checked through all the edits, all this has been covered already. Oh well.) - [[User:NKF|NKF]]

:I did 10 tests each way yesterday from the same save - sequentially 1 win from 10, even that the last interceptor was fully red damage at the end (cant tell the exact numbers, for some reason after the fight the geoscape was zooming out past maximum and crashing to the battlescape). Simultaneous was 9 wins from 10, 0 shot down 2 times, 1 down 4 times, 2 down three times. I then did a few further tries later with all three having slowed the cycle rate down and got 0 shot down 3 times out of 4, as generally the first one in was the one that almost always died if any did, if you can get them all attacking closer together it ensures it doesnt take the first two or two of the first three salvoes. --[[User:Sfnhltb|Sfnhltb]] 05:06, 6 March 2007 (PST)

I think some of what's written at [[Battleship#Weapons]] should be copied over. I've never tried it myself, personally; I don't bother engaging battleships until I have an Avenger. What I'd really like is some way to stop Terror Ships before I get Plasma Cannons... two Interceptors armed with Avalanches? Or does it take three?--[[User:Ethereal Cereal|Ethereal Cereal]] 21:59, 5 March 2007 (PST)

:From the encounter I had yesterday, would suggest 3 is needed, it can trash them so quickly that you need to throw in loads. The one thing I noticed was that Avalanches in some ways seemed better than the Plasma cannons because you can get off a 1-2 rounds of missiles before the Plasma even starts firing due to the range difference, which is critical with your paper thin Interceptors vs the Battleships. --[[User:Sfnhltb|Sfnhltb]] 04:56, 6 March 2007 (PST)

:2 interceptors with avalanches can bring down a terror ship and make it back to base in one piece. I think 10 avalanches will kill it. You do need to do the agressive trick with at least one interceptor to make sure all 6 missiles actually hit.
:(Never tried interceptors vs battleship, it sounds suicidal.) --[[User:MB|MB]] 11:56, 6 March 2007 (PST)

===Review of Air Combat Mechanics===

Moved to its own article [[Air Combat Mechanics]]

==Operational and Logistic Aspects==

===[[Repairs]]===
===[[Refueling]]===
===[[Rearming]]===

*Seb76 Loader option to relaunch aircraft before they are fully ready.
*Add link to "Duty Cycle" discussions & table

===Patrolling fuel usage===

TBD: Summarise fuel consumption for patrol/not, hybrid/not.
----

I saw somewhere that the skyranger at least uses less fuel when patrolling, but I have this vague recollection that the hybrids don't. Am I right in this or does it need investigating to determine one way or the other? --[[User:Sfnhltb|Sfnhltb]] 16:05, 5 March 2007 (PST)

:You are correct, hybrids don't conserve fuel while patrolling. Only the originals do. --[[User:Pi Masta|Pi Masta]] 17:15, 5 March 2007 (PST)

::That does appear to be the case. I just tested this with a Firestorm (not an Avenger), and there were a few quirks: fuel consumption was the same whether patrolling or not (which is what you were asking about); fuel readout only decreased in 5% increments (not well-documented); it returned to base when it hit 50% fuel, regardless of distance-to-base (argh). (Skyrangers and Interceptors will stay out below 50%, based on distance.) Fuel consumption was 0.5% of total per minute.

::A patrolling Skyranger used up 0.02% of fuel per minute. A constantly-moving one used up 0.0455% per minute. This is more or less consistent with what is documented at [[Skyranger]].--[[User:Ethereal Cereal|Ethereal Cereal]] 18:29, 5 March 2007 (PST)

==Strategic Aspects==

===Scoring vs Location of Intercept===

I am currently on 23rd January, so should be able to check whether XCOM Activity relates more or less directly to your pay rise at the end of the month fairly soon, but if it does then clearly you will always want to shoot down UFOs over a sponsor country instead of neutral territory (especially the big scoring recovery missions).

--[[User:Sfnhltb|Sfnhltb]] 06:31, 28 February 2007 (PST)
----
IIRC the amount of money you get is randomly assigned, though increase, decrease, or no change is based upon 'score', and the country's 'happiness' with XCOM. I think this can be seen by saving near the end of the month and noting the funding changes on each save (w/o doing anything special), I believe each time they will be random amounts (but again the sign of the change is dependent on the score, directly or indirectly).

I'm not sure if a higher score as an effect on the average increase (or conversely lower score with average decrease). It is possible. However I imagine that you are still correct that downing a UFO over a sponsors country is better than over a neutral country.
[[User:Pi Masta|Pi Masta]] 11:51, 28 February 2007 (PST)

:Hmm, we should add a graphic to the wiki showing where the sponsor land masses are.--[[User:Ethereal Cereal|Ethereal Cereal]] 12:22, 28 February 2007 (PST)

Yeah I had noticed it was random, I think your starting cash is as well, where the random range comes is was something I will be testing at the end of the current month of the game I am on, which might take a while as I am only playing intermittently (lots of work on atm)

--13:11, 28 February 2007 (PST)

----
Don't bother with the funding deals. I did this looong ago, both at the [http://www.strategycore.co.uk/forums/index.php?showtopic=652 StrategyCore forums] as well as a complete country-by-country funding breakdown at the [http://www.xcomufo.com/forums/index.php?showtopic=7424 xcomufo.com forums]. Granted, this was for the starting funds, not for subsequent months. But I did run about 2000 trials on that scenario and found that funding was random within a certain range. --[[User:Zombie|Zombie]] 14:44, 28 February 2007 (PST)

Hmm, well compared to the starting funds that you tested that were almost static overall (unless I am misreading it, +/- 15k or so?), the monthly amount varies a whole lot more, certainly +/- 250k from the average on a given good month I tested briefly to get an idea of it (and could grow more for an even better month I suspect). I would be interested in finding out what exactly affects it, and how responsive it is to key elements you might be able to control (like how beneficial is shooting down more aliens in sponsor country, compared to the same region (if that affects anything at all), and overall.

Btw, in case you still are thinking about the question regarding the discrepancy between your income and expenditure at startup, i can tell you where the 1860000 comes from at least - its in LIGLOB (A0611C00 in backwards hex) - its basically the source of the Finance graph (except score, which comes from XCOM.DAT combined with UIGLOB), which of course assigns it all to Maintenance - which in theory could include 1.7 million for the planes, 300k for the scientists, 250k for the engineers, 160k for the soldiers, and 224k for the maintaince of facilities of the base, so it doesnt solve it, but at least you can eliminate paying for things in trying to work out what it is.

The most obvious answer here is that you pay for craft rental (1.7 mill) and your soldiers (160k) = 1.86 million, and you dont pay for the scientists, engineers or base maintainance. --[[User:Sfnhltb|Sfnhltb]] 16:41, 28 February 2007 (PST)

----
The monthly funding (according to the OSG) is determined by these two equations:

Alien activity in country + (Overall alien activity/5) 
X-COM activity in country + (Overall X-COM activity/10)

These numbers are compared and if the alien score is greater than X-COM, the country decreases funding by a random amount, but no less than 20%. If X-COM is greater than the alien score, the country increases funding by a random amount, but no greater than 20%. I'm not sure what the upper or lower boundary is. It could be 0%. Who knows, the frequency of the non-20% limits may increase as score does. Suppose the easiest way would be to edit alien score to 0 and X-COM score to something high and check the results. That would correspond to "EXCELLENT" on the End Of Month report. Another test is to edit both X-COM and alien score to zero and check the funding there. This would correspond to "OK" on the EOM report. One thing is for certain, it would take a great many reloads to form any type of conclusion. One of these days I'll have to write up an AHK script and dedicate some computer time to this project. It won't be right away though. --[[User:Zombie|Zombie]] 21:47, 28 February 2007 (PST)

:Ah, that explains something I was seeing - basically if you get double the Alien score, everything is good, if you are less than that everything is bad. When using very large numbers that is, to minimise other factors.

:I think the increase is between 5-20%, if they come up as happy. But sometimes even with the same scores they turn out just to be satisified (current game I am playing, overall score 2.6k, alien score was 132 (and I think quite a bit of that I am double counting, country and region)

:And yeah, no matter how high the XCOM scores went (very high values in the 4th byte didnt register, but I could get 30k or 60k I think, and there was no change in the range of values to cursory inspection at least. I am fairly sure that happy/satisfied/unhappy is an on/off switch that is fired by a comparision of the scores in a manner as you list above (but there is some randomness in it however).

:The scale of the increase in funds seems to be based entirely on the existing funding level, so basically you just get a random percentage value within fixed limits (5-20% on the upswing, havent explored going down enough to say with enough confidence). If US is paying out 10 Million (and you have removed the funding cap, or it wont go higher), values are in the range of 500k to 2 Million if it increases, or 0 if they are only satisfied.

:There isnt a whole lot of random numbers it rolls either, which you see with that nice round 10 mill, you get nice neat values spread out every 100k (rounding issues would make it look like there were more possibilities with a smaller existing fund). So its a random int between 5 and 20. Going down is probably a mirror image I would guess, but thats not got any real evidence behind it. --[[User:Sfnhltb|Sfnhltb]] 18:16, 1 March 2007 (PST)

==When do most people bother intercepting?==
I'll be frank, I usually don't bother. The Elerium and loot is worth more than the UFO Downed points (funding changes are typically on the order of half a million or less; one Medium Scout and one Large Scout saved from Power Source detonation give $660,000 just in extra Power Sources and Navigations), and I can handle a night mission or two. I only bother intercepting in a few cases:
*'''Small Scouts''' - Downing them doesn't lose anything. Destroying them loses the alien's gun, but they don't generally land and downing them safely is nearly impossible before advanced craft. Pretty easy choice.
*'''Alien Retaliation''' - Nothing on that mission ever lands recoverably, so this is another no-brainer.
*'''Terror ships performing Alien Terror''' - They don't land recoverably. See above.
*'''Alien Base flotillas''' - Unless you've got multiple squads, you can't Ground Assault all four ships in the flotilla. And shooting down some of them breaks up the flotilla (because any that haven't spawned yet will get delayed), so you can get in two Ground Assaults instead of potentially only one. I'll take two Ground Assaults and two Crash Recoveries over a single Ground Assault any day.
*'''Alien Infiltration''' - Not only is there a five-ship flotilla at the end, but Alien Infiltrations have a large and direct impact on X-Com's financing in addition to the points issue. You can't stop them, of course, but you can delay them, and since the mission repeats until all countries in the region are infiltrated, the delays are cumulative (potentially keeping countries in for several months longer than they would otherwise have lasted). So I generally shoot down as many of these as possible.

I just kinda wonder what we should say about this dilemma and where we should say it. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 03:57, 7 April 2016 (UTC)

: I think this is really best left up to the judgement of the player as the ability to get to a landed UFO can be quite situational. In the early game, unless you are plain lucky or have lots of bases, your Skyranger is most likely not going to be able get to every landed UFO in time. You need the ability to shoot down the UFOs in this instance if only to get some work at the lesser reward. Later in the game you have more options on how to approach the UFOs as you spread out and get better tech to find and deal with them. This is when you can start going for landed UFOs. Much later into the game you'll have enough resources that you end up shooting down the UFOs down simply for the sake of shooting them down and ignoring the crash sites. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 06:11, 7 April 2016 (UTC)

I don't find it difficult at all. You usually detect UFOs on the flight in (or on the flight out, but in that case you can't do anything about them anyway). When you detect it, you send an Interceptor to shadow it and a Skyranger to the area it seems to be heading for, changing it to intercept when it gets close enough. Maximum time for the Skyranger to arrive in any location is 14 hours and it's usually a lot less; you'll generally be detecting the UFOs 4-5 hours before they land and they land for several hours. It's rare that you'll actually be unable to get there until you're dealing with actual antipodes (and at the point you're running Hyper-Wave Decoders on six continents, you're in most cases getting instant detection on UFO appearance, giving you significantly more time). [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 06:39, 7 April 2016 (UTC)

Oh, something else that factors in that I forgot to mention: interception draws Retaliation, while Ground Assaults don't. Intercepting too early on Superhuman is one of the more plausible ways to lose outright, because if you get a Sectoid Retaliation on your main base in January you'll have a very hard time recovering. Later on, of course, the Retaliation spiral (Retaliation -> shoot down scouts to avoid Base Defence -> more Retaliation) is a good thing for X-Com, but starting it too early is suicide. I know my first attempt at TFTD Superhuman came to an ignominious end that way. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 01:22, 7 May 2016 (UTC)

:I agree with a lot of points everyone brings up. For me, the decision to intercept instead of going for the landed UFO or ignoring it altogether is situational. Mostly it depends on UFO mission type, craft type, location, severity and quantity.

'''Mission Type''': Early in the game you need points to keep your score up in order to eclipse what the aliens can manage themselves and you also need alloys/elerium/bodies/weapons etc for research/manufacturing/funds. If a mission UFO is going to land, I'll wait for it to do so. Why bother wasting a missile on it? (Pending night time missions may prompt an interception to make things safer/easier). Obviously, if there is going to be a Terror Mission, I'd much rather shoot the UFO down so I don't have to deal with the hefty penalty if the mission goes pear shaped, or to defend the stupid civilians. Alien Resupply? C'mon, it always lands so you might as well wait (or ignore). Retaliation? Might as well shoot everything down, you don't want to lose country funding. Research? Ignore for the most part, unless nothing is going on. Harvest? Wait - most land and the ships are easy to recover. Abduction? I normally shoot these down if possible. While not overly critical, I don't want the aliens to get too many points. Alien base building? Yeah, I'll try to, especially with the tougher races. Otherwise the base itself is faster to take out than the UFOs building it.

'''Craft Type''': With Small Scouts, it's faster to just shoot them down and destroy them outright rather than waste an X-COM ship with weaker weapons on it. Medium or Large Scouts I'll try to let land. Same for harvesters or abductors. As I mentioned above, wait for the Supply Ships to land and shoot down the Terror Ships. Battleships are the only ship where I have to make a decision on it. Can my troops handle it? Can my ships handle it? Will it land on it's own? What is the race? What is the mission? Those all factor into a final decision.

'''Location''': If an alien mission is being carried out halfway around the world, I'm more likely to shoot it down as it takes time for the Skyranger to get there.

'''Severity''': As mentioned above, a mission with a higher severity will be met with interceptions.

'''Quantity''': If the UFOs arrive one at a time with days between landings, you can go after them while landed as there isn't a rush. What throws a spanner into the works is when the ships arrive in a big wave or group. If all of them are going to land, you can probably get to at least a couple before the rest take off and leave for good so I usually shoot down most of them and leave a couple. Visit the landed ones first, then go after the crashed ones when time permits. --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 03:52, 9 May 2016 (UTC)

=Misc=

==Old Chat==

===Ye Olde Bayse Maynetaynanse===

Of course the thing that has lead me onto, is trying to work out how it calculates base maintenance. A lift only new base costs 30k (4k for the lift, 26k extra somewhere), and a vanilla starter base costs 224k, but the parts only add up to 169k, so the extra unassigned part raises to 55k. Whats going on?

So I dismantle the starter base (after dumping all loose objects like people, planes and guns), the first Hangar drops the cost by 10k (not 25k), the next one by 4k (huh?), then 10k again for the last hangar, workshop drops it by 35k (correct!), the radar drops it another 35k (way high!), the living quarters are 30k, the lab 35k (a bit high), the stores 35k (massive - 7 times what it should be), and the lift 30k (4k in UFOpedia).

I thought maybe this was messed up somehow because of being the starter base, but it seems to behave the same way in new bases - as I say empty base with lift 30k, lift + stores + small radar = 95k, adding alien containment, stores, living quarters to starter base is 55k up on the starting cost (second stores 10k off when removed, second living quarters 10k, alien containment 35k)

So the same facilities take different maintainance depending on how many you have of them (it seems), and most of them cost different to what it says they do. No idea what the relationship or reasoning is behind all of this.

--[[User:Sfnhltb|Sfnhltb]] 17:05, 28 February 2007 (PST)

:No what's happening is that there are completed 'empty' modules. When you dismantle a facility it doesn't set the days to build to 255 like it should, and instead just puts the dirt tile there. Apparently these completed dirt modules take monthly maintenance (but isn't shown in the monthly costs IIRC). If you want me to find the post I can, but this is something I'm familiar with and in fact the 'editor' I'm making (PyXCom) should be able to fix it. (another thing is even if you build something and dismantle it before it's built, it will still count down and suck your money away)

:Atleast I think this is the issue you are having. [[User:Pi Masta|Pi Masta]] 19:57, 28 February 2007 (PST)

No I worked it out, I added the basic details to [[Known_Bugs#Facility_Maintenance_Costs]], there might be something additional as you say, as destruction a facility doesnt clear the construction counter as you say - in fact you can see that it keeps construction counters from previous saves as well at times, the clearest indication its doing stuff like this is if you start a game and name your first base something long, say 'ABCDEFG', and then start again and make a new base with a one character 'X', in the BASE.DAT you will see something like 'X CDEFG' (the space indicating actually a null (00) to show end of string). So when you save it doesnt 100% overwrite all bytes, just the minimum it needs to save the information for your current save (which may have errors like you suggest).

--[[User:Sfnhltb|Sfnhltb]] 20:03, 28 February 2007 (PST)

User talk:Zombie

2016-05-09T02:55:44Z

Zombie: /* Welcome back! */ Thanks!

== Ping ponging with PNGS==

Zombie, while you're replacing some of the jpegs with higher quality png's, might I recommend using an optimizer to crush the file size down? Ken Silverman's [http://advsys.net/ken/utils.htm PNGOUT] is one compressor that I've been using (as it has an irfanview plugin). Takes a moment to compress each image, but it does shave off some kb's on larger images. -[[User:NKF|NKF]] 01:11, 19 July 2009 (EDT)

:Sure, I ran a few of my HQs through just now and it averages a 80% drop in file size. It's slow going though doing them all one by one in a directory. --[[User:Zombie|Zombie]] 01:38, 19 July 2009 (EDT)

:Just uploaded PNGGauntlet (a front end for pngout) to StrategyCore's files section [http://www.strategycore.co.uk/files/index.php?dlid=754 here]. The nice thing about it is that it is windows-based and allows drag-'n-drop. ;) --[[User:Zombie|Zombie]] 01:53, 25 October 2009 (EDT)

----

Here is a recent discussion from the main page about images. Instead of deleting it, I decided to add it to my talk page. Conclusion reached was that PNG's are the preferred image choice for the wiki as most X-COM screenshots are well-suited to this format and are smaller than a GIF. JPEG's should only be considered for pictures as the quality sucks. --[[User:Zombie|Zombie]] 13:45, 25 June 2006 (PDT)

== Image Types ==
I was fooling around with images today and decided I should show everyone what an image looks like in a particular format. Just for this example, I used the Level 0 view of the Small Scout. Here are the images (don't peek, just look at them and try to figure out which is which for now):

<center>[[Image:Scout GIF.GIF|GIF image]] [[Image:Scout PNG.PNG|PNG image]] [[Image:Scout JPEG.JPG|JPEG image]]</center>

From what I can tell, the image quality of a GIF and a PNG is minimal. Both look very good. The PNG image seems a tad bit lighter over the GIF, though. Not bad. But compare either a GIF or a PNG with a JPEG and there is a huge difference. The JPEG has "artifacts" strewn all over the place and has a "mottled" appearance. Ugh! Terrible! That's all for the image quality aspect. (So does anyone know the technical difference between a GIF and a PNG? Please explain.)

Let's move on to size. The GIF image is usually the largest in size. In this case the GIF image of the Scout example is 7897 bytes. The JPEG is 6784 bytes (or 86% of the GIF) while the PNG is 6090 bytes (or 77% of the GIF).

Finally, compare size against image quality. PNG wins hands down. Not only is it smaller in size, but it also has an image quality equaling that of a GIF. JPEGs are smaller than a GIF but the image quality sucks. Granted, in some instances a JPEG is fine (especially if the background is a dark color), but in all the comparisons I did they were bad.

So, have you figured out what is what? The first image is a GIF, the second is a PNG and the third is a JPEG.

I implore everyone to consider uploading either a GIF or a PNG image type over a JPEG. The quality is better in those formats. If you have a choice, PNG is better because of the size on disc. --[[User:Zombie|Zombie]] 19:40, 11 June 2006 (PDT)

----

The most important difference between PNG and GIF is GIFs can only use 256 colors. I think most graphics from Enemy Unknown are in 8-bit color, so it doesn't cause a problem, but if you ever converted a normal photo to GIF, it'd look horrendous. PNGs can handle "truecolor" (24-bit), and as you said, they tend to compress better too.

JPGs can have different "quality settings" which reduce the artifacts but increase file size. JPG tends to compress photos better than PNG, but PNG is great for non-natural images, such as cartoons or computer graphics. For graphics pulled from X-COM, PNG is probably best.

--[[User:Ethereal Cereal|Ethereal Cereal]] 21:43, 11 June 2006 (PDT)

----

PNG's can vary in size depending on the size of the palette used. A standard 256 colour image would allow PNGs to be more or less the same if not better than GIFs. 'True Colour' PNGs are generally abominations.

For more information on the PNG format: [http://www.libpng.org/pub/png/ Portable Network Graphics ]

GIF and PNG provide lossless compression while Jpeg's offer lossy compression. GIF and PNGs are best used when the image is generally small and contains a limited number of colours. X-Com screenshots fit this bill perfectly.

Jpegs tend to lose image accuracy every time you save the image and it gets worse the higher you set the compression. However, that said, Jpegs are best used when your image is full of colour and minor losses in image quality will not matter.

For example, the above pictures are best done with GIF/PNGs (especially if you intend to include transparent pixels). However if you had a cut out shot of the action in the battlescape, it probably wouldn't matter too much if it were saved as a Jpeg.

Now if you want an image with transparency pixels, you will most definitely pick GIF and PNG. I actually hadn't realised the PNG format allowed tranparencies, but it does.

Just use what's best for the occasion.

- [[User:NKF|NKF]]

----

''In Which an Uneccessary Discussion of Formats Ensues''

PNG's not only do transparency, but they are capable of doing alpha channel-- that is, partial transparency. A GIF can only do normal colors (completely opaque) or complete transparency. PNG's can do all this, as well as allowing color that are partially transparent (say, a red tint with the background showing through).

I put this in mostly to hear myself talk. There are two limitations to these neato PNG effects:
* For X-Com screen shots, it's not needed-- X-Com 1 and 2 never did such fancy tricks.
* Alpha channel PNG's are, last I checked, not supported by Internet Explorer-- IE will let PNG's mimmick GIF-style transparency (that is, an 8-bit palette with all-or-nothing transparency), but nothing more sophisticated. Firefox and the Mozilla-derived browsers can do them (including Safari, I think), but it's not much good when most of the traffic is still using IE. Yes, I'm bitter about this.

PNG's are in every respect superior to GIF's. In matters of compatibility and filesize, the PNG can be set to work just as well or better than GIF). The only reason you use GIFs is to cater to people with seriously archaic browsers. Widespread PNG support has been around for several years now.

[http://entropymine.com/jason/testbed/pngtrans/ PNG transparency test]

''Edit: IE7 does complete support for PNG alpha, but of course it's still in beta testing. Even when it's out of beta, sensible web designers will have to wait until the majority of users switch over to it to start designing with it in mind.''

--[[User:Papa Legba|Papa Legba]] 20:36, 14 June 2006 (PDT)

--------

GIF was originally made waaaay back in the late 80's. The format recieved an update around 1990, but has not been upgraded since. (Although Microsoft Paint will save lossy GIFs, I don't think this is an attempt to restandardise the format).

Later JPG came along, which really made high color images practical because it compressed so well. That compression came at a cost, however - quality is lost when you save a JPG file, no matter how high you set the quality.

PNG was designed with the intention of replacing GIF. A lot of people started using it once the original GIF copyright ran out - It was re-registered by a company who demanded royalties for anyone who used the format! (Which would only have affected you if you lived in America - of course.)

Although I gather that bit of patent madness has been overthrown, returning GIF to the populance at large, a lot of people still use PNG when possible. JPG files still yield better compression when images have a lot of color depth, however, PNG files do not lose color information, so it's the best format to use whenever quality is important.

I'm not sure if PNG supports multiple images in the one file, however. We've all seen animating GIFs, but I'm sure I've never seen an animating PNG.

One feature I've always wanted added to web browsers is the ability for HTML to referrence individual images loaded into GIF files. That way, you could put all the images into one file, as opposed to lots of little ones. This would improve page load times no end. One example where this would be useful is your average forum skin.

- [[User:Bomb_Bloke|Bomb Bloke]]

One attempt to animate PNG is MNG. However, development on that appears to have stopped in late 2004 when Mozilla abandoned the format (only one implementation, so hard to catch bugs in the specification).

Regarding PNG transparency/IE5,6: I don't think this is completely portably solvable in MediaWiki. Even if (contrary to what I would expect; need to check documentation for other reasons) JavaScript was enabled in MediaWiki, the general solution is to use that JavaScript to define whether to use HTML-standard, or IE extensions that do render PNG transparency. I haven't tested how to do this with inline images [img tag], but it should be possible to do this inline. Background images require using the JavaScript to define a CSS class, which should be done in the head tag: disallowed.

EDIT: MediaWiki Technical FAQ intimates that JavaScript should be stripped. So, cross-browser PNG transparency not possible by legitimate design for security.

--[[User:Zaimoni|Zaimoni]] 11:49, 17 June 2006 (CDT)

I just started a discussion on the main page about this--people are still adding nasty JPGs to the wiki, and I thought we should add a notice somewhere obvious. [[User:Phasma Felis|Phasma Felis]] 10:57, 12 June 2008 (PDT)

----

Zombie: Just so you know, armor for aliens is only one of two values. In Beginner, it's 50% the base armor score listed in the game files; in Experienced/Veteran/Genius/Superhuman, the armor rating for aliens is the base listing. This is also why [[Chryssalid]]s spawned from Zombies are actually MORE dangerous than mission-spawn Chryssalids in Beginner mode, because the Zombie-spawned critters have twice as much armor! (In all other difficulties, Zombie spawned Chryssies are weaker; the armor is the same, but they don't get the above 100% modifiers for their other stats, like TUs, Stamina, Psi Strength, etc.) [[User:Arrow Quivershaft|Arrow Quivershaft]] 00:43, 29 October 2008 (CDT)

:Why do you mention this? I of all people should know about [[Alien Stats]]. Ahem. ;) --[[User:Zombie|Zombie]] 01:02, 29 October 2008 (CDT)

I thought you did, but your comment to the Stun Rod page about "Veteran-Superhuman" Sectopods kinda threw some doubt on it; so I figured that it was better safe then sorry. Guess I jumped the gun, apologies. (Also, I need to try that "Aliens Own Earth" thing.) [[User:Arrow Quivershaft|Arrow Quivershaft]] 01:04, 29 October 2008 (CDT)

:Sorry, it was a mistype. Experienced it is. :D --[[User:Zombie|Zombie]] 01:09, 29 October 2008 (CDT)

Sorry for jumping on you like that. >_> [[User:Arrow Quivershaft|Arrow Quivershaft]] 01:17, 29 October 2008 (CDT)

:I probably deserved a good beating for a rookie mistake like that. If you catch me doing strange stuff, feel free to edit. --[[User:Zombie|Zombie]] 01:28, 29 October 2008 (CDT)

== New Milestone. ==

With my previous edit, I now have 2,000 contributions to the Wiki. :) --[[User:Zombie|Zombie]] 22:25, 20 December 2008 (CST)

:A little over twice as many as me! (This'll be edit 1010). Incidentally, looking at your recent record, it seems you've had a few days off. Busy Zombie, you definitely don't sleep. Wanna leave some editing for the rest of us? ;) All you need to do is ask...or point. [[User:Arrow Quivershaft|Arrow Quivershaft]] 23:34, 20 December 2008 (CST)

:: Do we get a counter? Never noticed that before. One thing about the millions of recent edits: Some of the older and probably less visited articles are brought to the surface again. Some of them are long overdue a bit of preening and pruning. -[[User:NKF|NKF]] 01:42, 21 December 2008 (CST)

I didn't realize there was a counter till the last upgrade to the wiki software. If you go to My Preferences and look at your user profile it'll say how many edits you have under your screen name and ID#. @AQ: Yeah, I had a couple days off in the last week due to finals and a heavy snowfall which basically stopped everything. All I've been doing here recently is updating the pages to reflect the nomenclature in-game. Maintaining this consistency is necessary for people trying to find something in a hurry. And my work ethic has always been that if I want something done, I might as well do it myself. With an aging mind, it better to get stuff done while it's still fresh in my memory too. Don't worry, there's still plenty to do around here. There are a lot of articles floating around with little to no text, which need a spell checking, or even a rewrite. TFTD in particular needs some attention. --[[User:Zombie|Zombie]] 16:35, 21 December 2008 (CST)

:I got that same snowfall, still being only a few hours north, and yeah, we got shut down too. :) As for TFTD, I know it needs attention, but I've never been able to get TFTD to run half-decently. [[User:Arrow Quivershaft|Arrow Quivershaft]] 16:49, 21 December 2008 (CST)

And now I'm up to 3000+ edits. :) --[[User:Zombie|Zombie]] 01:01, 19 July 2009 (EDT)

== The New Templates. ==
Hey Zombie, great job on these new templates, and now we even have a stub template! If possible could we get a template about adding more pictures? If so, thanks! If not, oh well, it wasn't the biggest deal here yet. It would be nice if we did have pictures for every page though. [[User:Muton commander|Muton commander]] 19:35, 8 January 2009 (CST)

:Thanks, the stub template already existed, I just reused it to create pages which needed something in them. The reason for the other templates is to aid in navigation and also cut down on the number of orphaned and dead-end pages (currently 7 and 60 respectively). Eventually I'd like those numbers to be as close to 0 as possible. Anyway, I created a stub picture template out of some of our other table templates. All you need to do is put <nowiki>{{PicStub}}</nowiki> in a page and it'll show up to the right side of the screen. If there isn't much text in the article, you may want to put a clearing break ( <nowiki> </nowiki> ) after it to keep the template from continuing into the "See Also" heading, for example. Other than that, it's pretty simple to use. --[[User:Zombie|Zombie]] 23:10, 8 January 2009 (CST)

== Site database problems? ==

Hi Zombie

Some weird stuff going on with the site I think. I got an email saying you posted an Update to Talk:Incendiary, but when I view the page there is nothing there, nothing on the history/diff since Jasonred's post about 8 hrs ago.

I'd been noticing a lot of slowness with the Special:Recent Changes page and wondered if the database needs maintenance. But then I put it down to my flaky internet connection. Now I'm not so sure.

[[User:Spike|Spike]] 17:05, 13 March 2009 (EDT)

:Yeah, I posted an update to the Incendiary talk page, but now it's gone. Ah well. Anyway, as you may know, StrategyCore is hosting UfOpaedia now. Pete (the admin and owner of StrategyCore) switched hosts for SC about a week ago and mentioned this wiki would also have to be moved to the new location. I asked him to kindly give me a heads up of at least 24hrs so that I could mention it here. Well, this morning I briefly saw a message saying something like the site is down for maintenance and should be up again on the 14th (I think that's what it said at least). I know Pete was talking about putting a message up so I figured he just shut the site down and moved it to the new host. Have no idea if that actually happened as he hasn't contacted me at all. Might have been a dry run, but since my post disappeared I'm thinking we are on the new hosts server. I'll try and send him an email to confirm what is going on. Looks like everything is showing up in the Recent Changes now, so the worst is probably over. One contribution missing by me is a small price to pay. ;) --[[User:Zombie|Zombie]] 18:44, 13 March 2009 (EDT)

I'm still unable to post to Talk:Incendiary, I get a 500 Server error. I've tried rebooting my computer, using IE instead of Mozilla, logging out and in from the Wiki, no joy. I seem to be ok to post to other pages, but maybe that's a coincidence. [[User:Spike|Spike]] 07:59, 15 March 2009 (EDT)

I also have email alerts for another update that is not visible on the wiki, suggesting the database is still in flux:
*Talk:Firing_Accuracy_Testing by Bomb Bloke at 02:05 GMT, 03:05 system time (10 hrs ago - the server must be on British Summer Time)
[[User:Spike|Spike]] 08:08, 15 March 2009 (EDT)

:The talk page for Incendiary is 40kb long (huge), so maybe we should cut some of it back. That may be what is causing the problem, especially if you are attempting to add long rambling posts to it. The email thing is probably a delayed reaction after the move. The site probably generated the emails before the move, then were unable to be sent out. When we moved over and everything was running again, it probably sent those emails out, even though the id code for the contribution didn't exist anymore. That's my guess. --[[User:Zombie|Zombie]] 11:17, 15 March 2009 (EDT)

::That sounds right, I was trying to add a lot of text. Should be ok to clean up the older part of the discussion. I will do that if I get time. [[User:Spike|Spike]] 12:13, 15 March 2009 (EDT)

The server change must've occurred just before I went to bed last night. Thought I'd give the recents a scan and was rather dismayed to see a whole day's worth of edits just go. Spent some time reinstating the few of mine that I could remember. This morning those edits were gone and the old ones were back. Strange experience indeed. Shame to see some of the new material that was added during the "lost" day that we just lost again - didn't get round to reviewing it. Oh well. -[[User:NKF|NKF]] 01:01, 16 March 2009 (EDT)

----

Shame indeed. In hindsight, and in future, during maintenance can we put a big notice on the home page so that people can wait to post until after the maintenance is done? [[User:Spike|Spike]] 01:45, 16 March 2009 (EDT)

:Well, there was a message telling people the site was having maintenance done. The only problem was that it only was up for 5 min at most. Supposedly Pete had put some locks down to prevent people from posting but those didn't work for some reason either. In addition, I never received a message from him telling me the move was happening, otherwise I would have plastered a big "Do Not Post Today" banner across he front page. So it was a "Perfect Storm" of unfortunate incidents which led to this. I made it perfectly clear to Pete that issues like this CANNOT happen ever again. I don't like to see stuff like this and I'm sure most of you feel the same way. On the positive side, this is the last server/host move we'll be making for a long time. At least I hope so, as this move was a total disaster in my book. --[[User:Zombie|Zombie]] 02:08, 16 March 2009 (EDT)

==Welcome back!==

There's a name I haven't seen in a long, long time. I thought you'd gotten out of the game. Glad to see that isn't the case. :) [[User:Arrow Quivershaft|Arrow Quivershaft]] ([[User talk:Arrow Quivershaft|talk]]) 22:33, 3 May 2016 (UTC)
: Yep. I concur! Nice to see you here! #OldXCommersNeverDie --[[User:IvanDogovich|IvanDogovich]] ([[User talk:IvanDogovich|talk]]) 23:08, 3 May 2016 (UTC)
I was surprised too. Pleasantly. You know more about the guts of X-Com than anyone besides the Gollops, methinks, and it's been like a dark age without you around. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 04:01, 4 May 2016 (UTC)
:Thanks guys! I haven't given up on X-COM, it's my favorite game of all time! To be honest, I haven't contributed here for a number of reasons, primarily because I felt like an old relic now that XCOM/XCOM2 came out and also because my mother died late last year. I either couldn't contribute anything new or didn't feel up to it. I began to realize though that there is still work to be done in the X-COM area and that I could be of assistance. Hehe. So yeah, for a while there I just lurked. As always though, you can find me at StrategyCore. :) --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 02:55, 9 May 2016 (UTC)

Fatal Wounds

2016-05-03T05:50:25Z

Zombie: /* Probability of Fatal Wounds */ Grammar, consistency.

For each Fatal Wound a unit has, they will lose one point of [[Health]] each turn. For instance, a soldier with 2 Fatal Wounds will lose 2 Health points per turn. Each time a soldier is shot but not killed by weapons fire, he or she may be dealt 1-3 fatal wounds. All of these fatal wounds will be dealt to the same part of the body.

Fatal Wounds can be healed using a [[Medi-Kit]]. 3 Health points will also be restored with each wound healed. Quickly healing a wounded soldier also means less [[recovery_time|wound recovery time]] (back at base), because recovery time is based on the number of health points lost in a mission.

'''Warning:''' Unconcious soldiers still take damage from Fatal Wounds each turn and CAN DIE if not treated. So if one of your soldiers is knocked unconscious by shots or explosions (as opposed to a stun bomb), it is important that you immediately run a diagnostics scan on him or her. See [[Medi-Kit]] and [[Unconscious]] for more information on how to do this. Keep in mind that you can pick up and move (or even throw) someone, if you have a man down in a hot zone.

== Other effects of Fatal Wounds ==

*Each wound to the '''head''' or '''gun-holding arm''' applies a 10% penalty to your [[Firing Accuracy]], down to but not below -90%. This means that someone with 100 '''base''' firing accuracy who has 9 or more wounds will be left with a '''base''' accuracy level of 10 points. This is before you consider any other accuracy modifiers such as your remaining health percentage (see [[Accuracy formula]]).
*Each wound to the '''legs''' reduces the soldier's [[Time Units]] by 10%.
*Each wound to the '''torso''' reduces the soldier's [[Energy]] by 10%.

''I did a test on this and have lots of doubts on this info above, my unit got 3 fatal wounds on the torso only, and I got a penalty to both throwing and firing accuracy. But no penalty on energy. And with a unit with fatal wounds to the left arm, I got a penalty on the Energy Replenishment level. - [[Daiky|Daiky]]''

== Aliens and Fatal Wounds ==

Aliens never get fatal wounds - they never crawl off and die - except if you were mind controlling them when they were wounded. In other words, only friendlies can get Fatal Wounds, and MC'd aliens count as friendlies. Be careful of mixing MC'd with non-MC'd aliens - you might reaction shoot the one, and hit the other. But wait, there's more - aliens with Fatal Wounds do not suffer any health decrease, for as long as you MC them. They only suffer health loss from their Fatal Wounds on turns that you do not MC them.

''Once I had an MC'd alien taking point, when a different one blaster bombed the lot of us. All hell broke loose, and I lost track of the pet (I assumed he got killed in the blast). Many turns later I heard the entirely unexpected cry of an alien dying, far off in the distance. "Oops" - [[User:MikeTheRed|MikeTheRed]]''

== Probability of Fatal Wounds ==

As shown by Zombie's [http://www.strategycore.co.uk/forums/index.php?showtopic=746&view=findpost&p=72949 research], if you receive more than 10 health [[damage]], you have an equal, random chance of receiving from 1 to 3 Fatal Wounds (a 33.3% chance of 1, 2, or 3 FWs). Higher damage does not change these chances, and you can never receive more than 3 FWs (in a given shot or blast!), even if you're hit so hard you only have 1 hitpoint of life left. Stated another way, if you take 11+ damage, you always get at least one Fatal Wound, an average of 2, and a maximum of 3. Thus, never leave your [[Medi-Kit]]s behind.

If you receive from 1 to 10 damage, the likelihood of a Fatal Wound ''roll'' increases, in which case you roll again for 1, 2, or 3 FWs, evenly. In other words:
Chance of Fatal Wounds
Damage 0 1, 2, or 3 1-3_
1 90.9% 3.03% 9.1%
2 81.8% 6.06% 18.2%
3 72.7% 9.09% 27.3%
4 63.6% 12.12% 36.4%
5 54.5% 15.15% 45.5%
6 45.5% 18.18% 54.5%
7 36.4% 21.21% 63.6%
8 27.3% 24.24% 72.7%
9 18.2% 27.27% 81.8%
10 9.1% 30.30% 90.9%
11+ 0.0% 33.33% 100.0%
Stated another way, the chance of receiving NO Fatal Wounds is: (11 - Damage) / 11, if you receive 1-10 damage. And as discussed, at 11+ hits, you receive the even 33.3% chance of 1 to 3 FWs. Of course, if you receive no damage (0 Health lost), you never get a Fatal Wound.

==See Also==
*[[Medi-Kit]]
*[[Damage]]
*[[Unconscious]]
*[[Accuracy formula]]
*[[Recovery time]]

{{Unit Stats Navbar}}
[[Category:Soldiers]]
[[Category:Enemy Unknown/UFO Defense]]

UNITREF.DAT

2015-06-24T06:53:26Z

Zombie: /* Structure */ Apparently o is not the same as 0. DOH!

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=inside, 1=outside). When alien units are generated for a battle, there is a random chance for this byte to be set. That unit is a "scout" and can be assigned to one of the neutral spawn points on the map without the need to fill up all the alien exclusive points first. In other words with "1" alien unit is spawned at exact random node marked as "civilian/scout" ignoring actual rank of unit. As result - Commander can occasionally be spawned outside of the UFO craft (and ramble around UFO), not in the "contol room", which has 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
|- 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
|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
!0x78
|Unit bit flags, 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"
!121
!0x79
|Possible Values: 0 or 16. All units in unitref.dat get a value of 0 except for the second unit in the list which gets 16. Doesn't matter if the second unit is a soldier, a tank, or an alien. It's always 16. Editing it to 0 doesn't crash the game or have any dire consequences.
|- valign="top"
!122
!0x7A
|Always 0? Possible low byte of 123(0x7B)
|- valign="top"
!123
!0x7B
|Always 0? Possible high byte for 122(0x7A).
|- 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)
|- valign="top"
!130-131
!0x82-0x83
|TFTD ONLY - Called "floorabove" flag. Is there a floor above unit? (0=no, 1=yes)
|-
|}

== 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-06-24T05:59:30Z

Zombie: /* Notes */ Updated known/unknown list.

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=inside, 1=outside). When alien units are generated for a battle, there is a random chance for this byte to be set. That unit is a "scout" and can be assigned to one of the neutral spawn points on the map without the need to fill up all the alien exclusive points first. In other words with "1" alien unit is spawned at exact random node marked as "civilian/scout" ignoring actual rank of unit. As result - Commander can occasionally be spawned outside of the UFO craft (and ramble around UFO), not in the "contol room", which has 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
|- 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
|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
!0x78
|Unit bit flags, 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"
!121
!0x79
|Possible Values: 0 or 16. All units in unitref.dat get a value of 0 except for the second unit in the list which gets 16. Doesn't matter if the second unit is a soldier, a tank, or an alien. It's always 16. Editing it to 0 doesn't crash the game or have any dire consequences.
|- valign="top"
!122
!0x7A
|Always 0? Possible low byte of 123(0x7B)
|- valign="top"
!123
!0x7B
|Always 0? Possible high byte for 122(0x7A).
|- 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-ox81
|TFTD ONLY - Bubble animation enable. (0=disable, 1=enable)
|- valign="top"
!130-131
!0x82-0x83
|TFTD ONLY - Called "floorabove" flag. Is there a floor above unit? (0=no, 1=yes)
|-
|}

== 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-06-24T05:51:27Z

Zombie: /* Structure */ Changed a bit in 0x78 and added some possible info on 0x7A&B.

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=inside, 1=outside). When alien units are generated for a battle, there is a random chance for this byte to be set. That unit is a "scout" and can be assigned to one of the neutral spawn points on the map without the need to fill up all the alien exclusive points first. In other words with "1" alien unit is spawned at exact random node marked as "civilian/scout" ignoring actual rank of unit. As result - Commander can occasionally be spawned outside of the UFO craft (and ramble around UFO), not in the "contol room", which has 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
|- 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
|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
!0x78
|Unit bit flags, 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"
!121
!0x79
|Possible Values: 0 or 16. All units in unitref.dat get a value of 0 except for the second unit in the list which gets 16. Doesn't matter if the second unit is a soldier, a tank, or an alien. It's always 16. Editing it to 0 doesn't crash the game or have any dire consequences.
|- valign="top"
!122
!0x7A
|Always 0? Possible low byte of 123(0x7B)
|- valign="top"
!123
!0x7B
|Always 0? Possible high byte for 122(0x7A).
|- 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-ox81
|TFTD ONLY - Bubble animation enable. (0=disable, 1=enable)
|- valign="top"
!130-131
!0x82-0x83
|TFTD ONLY - Called "floorabove" flag. Is there a floor above unit? (0=no, 1=yes)
|-
|}

== 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 111 values.
Unknown values (13 in total):
[[#34|[034 / 0x22]]] - Always 0?
[[#36|[036 / 0x24]]] - Always 0?
[[#43|[043 / 0x2B]]] - Set to 1 on occasion, usually 0.
[[#52|[052 / 0x34]]] - Seems to be a mirror of 48 / 0x30, the LOFTemp index for the unit.
[[#71|[071 / 0x47]]] - Appears to relate to lighting caused by the unit, [[Talk:UNITREF.DAT#Offset_0x47|discussion here]].
[[#74|[074 / 0x4A]]] - Appears to relate to the AI-mode used by the unit, [[Talk:UNITREF.DAT#Offset_0x4A_.2874.29|discussion here]].
[[#75|[075 / 0x4B]]] - Always 0?
[[#112|[112 / 0x70]]] - Set to 1 for some aliens, 0 otherwise.
[[#119|[119 / 0x77]]] - No idea, possible bitfield, could be anything.
[[#120|[120 / 0x78]]] - Unit bit flags, mainly re: mobility. Only one bit not 100% identified.
[[#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?

Know 1 TFTD value.
Unknown TFTD values (7 in total):
[[#125|[125]]] [[#126|[126]]] [[#127|[127]]] [[#128|[128]]] [[#129|[129]]] [[#130|[130]]] [[#131|[131]]]

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-06-24T05:29:47Z

Zombie: /* Structure */ A little info on 0x4B, not sure of it is correct.

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=inside, 1=outside). When alien units are generated for a battle, there is a random chance for this byte to be set. That unit is a "scout" and can be assigned to one of the neutral spawn points on the map without the need to fill up all the alien exclusive points first. In other words (and if I understand the terminology correctly), a value of 0 means the alien will spawn on (aka inside) the tile it was assigned to, while a value of 1 means the alien will spawn outside of the assigned node on a civ-scout route.
|- 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
|- 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). Probably unused 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
|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
!0x78
|Unit bit flags, mainly re: mobility. They do NOT affect the soldier in inventory screen: ''(Mix of notes by BB and NKF)''
( 1) 1: 1 = Dead. ''This was only set for 2 of 3 dead aliens in my current game.''
''[[#13|[13]]] (Health=0) is the most reliable indicator for me.''
''-[[User:MikeTheRed|MikeTheRed]]''
( 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"
!121
!0x79
|Possible Values: 0 or 16. All units in unitref.dat get a value of 0 except for the second unit in the list which gets 16. Doesn't matter if the second unit is a soldier, a tank, or an alien. It's always 16. Editing it to 0 doesn't crash the game or have any dire consequences.
|- valign="top"
!122
!0x7A
|Always 0?
|- valign="top"
!123
!0x7B
|Always 0?
|- 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-ox81
|TFTD ONLY - Bubble animation enable. (0=disable, 1=enable)
|- valign="top"
!130-131
!0x82-0x83
|TFTD ONLY - Called "floorabove" flag. Is there a floor above unit? (0=no, 1=yes)
|-
|}

== 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 111 values.
Unknown values (13 in total):
[[#34|[034 / 0x22]]] - Always 0?
[[#36|[036 / 0x24]]] - Always 0?
[[#43|[043 / 0x2B]]] - Set to 1 on occasion, usually 0.
[[#52|[052 / 0x34]]] - Seems to be a mirror of 48 / 0x30, the LOFTemp index for the unit.
[[#71|[071 / 0x47]]] - Appears to relate to lighting caused by the unit, [[Talk:UNITREF.DAT#Offset_0x47|discussion here]].
[[#74|[074 / 0x4A]]] - Appears to relate to the AI-mode used by the unit, [[Talk:UNITREF.DAT#Offset_0x4A_.2874.29|discussion here]].
[[#75|[075 / 0x4B]]] - Always 0?
[[#112|[112 / 0x70]]] - Set to 1 for some aliens, 0 otherwise.
[[#119|[119 / 0x77]]] - No idea, possible bitfield, could be anything.
[[#120|[120 / 0x78]]] - Unit bit flags, mainly re: mobility. Only one bit not 100% identified.
[[#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?

Know 1 TFTD value.
Unknown TFTD values (7 in total):
[[#125|[125]]] [[#126|[126]]] [[#127|[127]]] [[#128|[128]]] [[#129|[129]]] [[#130|[130]]] [[#131|[131]]]

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-06-24T05:00:47Z

Zombie: /* Structure */ Updated the TFTD only fields.

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=inside, 1=outside). When alien units are generated for a battle, there is a random chance for this byte to be set. That unit is a "scout" and can be assigned to one of the neutral spawn points on the map without the need to fill up all the alien exclusive points first. In other words (and if I understand the terminology correctly), a value of 0 means the alien will spawn on (aka inside) the tile it was assigned to, while a value of 1 means the alien will spawn outside of the assigned node on a civ-scout route.
|- 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
|- 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
|Always 0?
|- 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
|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
!0x78
|Unit bit flags, mainly re: mobility. They do NOT affect the soldier in inventory screen: ''(Mix of notes by BB and NKF)''
( 1) 1: 1 = Dead. ''This was only set for 2 of 3 dead aliens in my current game.''
''[[#13|[13]]] (Health=0) is the most reliable indicator for me.''
''-[[User:MikeTheRed|MikeTheRed]]''
( 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"
!121
!0x79
|Possible Values: 0 or 16. All units in unitref.dat get a value of 0 except for the second unit in the list which gets 16. Doesn't matter if the second unit is a soldier, a tank, or an alien. It's always 16. Editing it to 0 doesn't crash the game or have any dire consequences.
|- valign="top"
!122
!0x7A
|Always 0?
|- valign="top"
!123
!0x7B
|Always 0?
|- 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-ox81
|TFTD ONLY - Bubble animation enable. (0=disable, 1=enable)
|- valign="top"
!130-131
!0x82-0x83
|TFTD ONLY - Called "floorabove" flag. Is there a floor above unit? (0=no, 1=yes)
|-
|}

== 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 111 values.
Unknown values (13 in total):
[[#34|[034 / 0x22]]] - Always 0?
[[#36|[036 / 0x24]]] - Always 0?
[[#43|[043 / 0x2B]]] - Set to 1 on occasion, usually 0.
[[#52|[052 / 0x34]]] - Seems to be a mirror of 48 / 0x30, the LOFTemp index for the unit.
[[#71|[071 / 0x47]]] - Appears to relate to lighting caused by the unit, [[Talk:UNITREF.DAT#Offset_0x47|discussion here]].
[[#74|[074 / 0x4A]]] - Appears to relate to the AI-mode used by the unit, [[Talk:UNITREF.DAT#Offset_0x4A_.2874.29|discussion here]].
[[#75|[075 / 0x4B]]] - Always 0?
[[#112|[112 / 0x70]]] - Set to 1 for some aliens, 0 otherwise.
[[#119|[119 / 0x77]]] - No idea, possible bitfield, could be anything.
[[#120|[120 / 0x78]]] - Unit bit flags, mainly re: mobility. Only one bit not 100% identified.
[[#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?

Know 1 TFTD value.
Unknown TFTD values (7 in total):
[[#125|[125]]] [[#126|[126]]] [[#127|[127]]] [[#128|[128]]] [[#129|[129]]] [[#130|[130]]] [[#131|[131]]]

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-06-24T04:32:19Z

Zombie: /* Structure */ Must've deleted the valign by accident.

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=inside, 1=outside). When alien units are generated for a battle, there is a random chance for this byte to be set. That unit is a "scout" and can be assigned to one of the neutral spawn points on the map without the need to fill up all the alien exclusive points first. In other words (and if I understand the terminology correctly), a value of 0 means the alien will spawn on (aka inside) the tile it was assigned to, while a value of 1 means the alien will spawn outside of the assigned node on a civ-scout route.
|- 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
|- 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
|Always 0?
|- 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
|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
!0x78
|Unit bit flags, mainly re: mobility. They do NOT affect the soldier in inventory screen: ''(Mix of notes by BB and NKF)''
( 1) 1: 1 = Dead. ''This was only set for 2 of 3 dead aliens in my current game.''
''[[#13|[13]]] (Health=0) is the most reliable indicator for me.''
''-[[User:MikeTheRed|MikeTheRed]]''
( 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"
!121
!0x79
|Possible Values: 0 or 16. All units in unitref.dat get a value of 0 except for the second unit in the list which gets 16. Doesn't matter if the second unit is a soldier, a tank, or an alien. It's always 16. Editing it to 0 doesn't crash the game or have any dire consequences.
|- valign="top"
!122
!0x7A
|Always 0?
|- valign="top"
!123
!0x7B
|Always 0?
|- valign="top"
!124
!0x7C
|TFTD ONLY - Appears to be a count as to which frame of bubbles the soldier is on. Can be 0 to 16 (0x0F), most likely 125/7D is included with this.
|- valign="top"
!125
!0x7D
|TFTD ONLY, unknown.
|- valign="top"
!126
!0x7E
|TFTD ONLY, unknown.
|- valign="top"
!127
!0x7F
|TFTD ONLY, unknown.
|- valign="top"
!128
!0x80
|TFTD ONLY, unknown.
|- valign="top"
!129
!0x81
|TFTD ONLY, unknown.
|- valign="top"
!130
!0x82
|TFTD ONLY, unknown.
|- valign="top"
!131
!0x83
|TFTD ONLY, unknown.
|-
|}

== 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 111 values.
Unknown values (13 in total):
[[#34|[034 / 0x22]]] - Always 0?
[[#36|[036 / 0x24]]] - Always 0?
[[#43|[043 / 0x2B]]] - Set to 1 on occasion, usually 0.
[[#52|[052 / 0x34]]] - Seems to be a mirror of 48 / 0x30, the LOFTemp index for the unit.
[[#71|[071 / 0x47]]] - Appears to relate to lighting caused by the unit, [[Talk:UNITREF.DAT#Offset_0x47|discussion here]].
[[#74|[074 / 0x4A]]] - Appears to relate to the AI-mode used by the unit, [[Talk:UNITREF.DAT#Offset_0x4A_.2874.29|discussion here]].
[[#75|[075 / 0x4B]]] - Always 0?
[[#112|[112 / 0x70]]] - Set to 1 for some aliens, 0 otherwise.
[[#119|[119 / 0x77]]] - No idea, possible bitfield, could be anything.
[[#120|[120 / 0x78]]] - Unit bit flags, mainly re: mobility. Only one bit not 100% identified.
[[#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?

Know 1 TFTD value.
Unknown TFTD values (7 in total):
[[#125|[125]]] [[#126|[126]]] [[#127|[127]]] [[#128|[128]]] [[#129|[129]]] [[#130|[130]]] [[#131|[131]]]

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-06-24T04:27:49Z

Zombie: /* Structure */ Elaborated on 0x2B

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=inside, 1=outside). When alien units are generated for a battle, there is a random chance for this byte to be set. That unit is a "scout" and can be assigned to one of the neutral spawn points on the map without the need to fill up all the alien exclusive points first. In other words (and if I understand the terminology correctly), a value of 0 means the alien will spawn on (aka inside) the tile it was assigned to, while a value of 1 means the alien will spawn outside of the assigned node on a civ-scout route.
!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
|- 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
|Always 0?
|- 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
|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
!0x78
|Unit bit flags, mainly re: mobility. They do NOT affect the soldier in inventory screen: ''(Mix of notes by BB and NKF)''
( 1) 1: 1 = Dead. ''This was only set for 2 of 3 dead aliens in my current game.''
''[[#13|[13]]] (Health=0) is the most reliable indicator for me.''
''-[[User:MikeTheRed|MikeTheRed]]''
( 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"
!121
!0x79
|Possible Values: 0 or 16. All units in unitref.dat get a value of 0 except for the second unit in the list which gets 16. Doesn't matter if the second unit is a soldier, a tank, or an alien. It's always 16. Editing it to 0 doesn't crash the game or have any dire consequences.
|- valign="top"
!122
!0x7A
|Always 0?
|- valign="top"
!123
!0x7B
|Always 0?
|- valign="top"
!124
!0x7C
|TFTD ONLY - Appears to be a count as to which frame of bubbles the soldier is on. Can be 0 to 16 (0x0F), most likely 125/7D is included with this.
|- valign="top"
!125
!0x7D
|TFTD ONLY, unknown.
|- valign="top"
!126
!0x7E
|TFTD ONLY, unknown.
|- valign="top"
!127
!0x7F
|TFTD ONLY, unknown.
|- valign="top"
!128
!0x80
|TFTD ONLY, unknown.
|- valign="top"
!129
!0x81
|TFTD ONLY, unknown.
|- valign="top"
!130
!0x82
|TFTD ONLY, unknown.
|- valign="top"
!131
!0x83
|TFTD ONLY, unknown.
|-
|}

== 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 111 values.
Unknown values (13 in total):
[[#34|[034 / 0x22]]] - Always 0?
[[#36|[036 / 0x24]]] - Always 0?
[[#43|[043 / 0x2B]]] - Set to 1 on occasion, usually 0.
[[#52|[052 / 0x34]]] - Seems to be a mirror of 48 / 0x30, the LOFTemp index for the unit.
[[#71|[071 / 0x47]]] - Appears to relate to lighting caused by the unit, [[Talk:UNITREF.DAT#Offset_0x47|discussion here]].
[[#74|[074 / 0x4A]]] - Appears to relate to the AI-mode used by the unit, [[Talk:UNITREF.DAT#Offset_0x4A_.2874.29|discussion here]].
[[#75|[075 / 0x4B]]] - Always 0?
[[#112|[112 / 0x70]]] - Set to 1 for some aliens, 0 otherwise.
[[#119|[119 / 0x77]]] - No idea, possible bitfield, could be anything.
[[#120|[120 / 0x78]]] - Unit bit flags, mainly re: mobility. Only one bit not 100% identified.
[[#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?

Know 1 TFTD value.
Unknown TFTD values (7 in total):
[[#125|[125]]] [[#126|[126]]] [[#127|[127]]] [[#128|[128]]] [[#129|[129]]] [[#130|[130]]] [[#131|[131]]]

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

Starting Stats

2015-06-24T03:51:54Z

Zombie: Updated to reflect Soldier Name Stats page discussion.

Raw recruits have the following possible statistics. Range (Min to Max), Number of possible values (Max-Min+1), and Percent chance of getting any one of those values (1/Values). Also, [[Experience#Regarding_Caps|caps]] are shown for your convenience:

<table {{StdCenterTable}} width="70%">
<tr {{StdDescTable_Heading}}><th align="left" width="140">Stat</th><th width="45">Min</th><th width="45">Max</th><th width="45">Values</th><th width="45">%ofOne</th><th width="45">MinCap</th><th width="45">MaxCap</th><th>Notes</th></tr>
<tr><td align="left">[[Time Units]]</td><td>50</td><td>60</td><td>11</td><td>9.09%</td><td>80</td><td>81</td><td></td></tr>
<tr><td align="left">[[Energy|Stamina/Energy]]</td><td>40</td><td>70</td><td>31</td><td>3.23%</td><td>100</td><td>101</td><td></td></tr>
<tr><td align="left">[[Health]]</td><td>25</td><td>40</td><td>16</td><td>6.25%</td><td>60</td><td>61</td><td></td></tr>
<tr><td align="left">[[Bravery]]</td><td>10</td><td>60</td><td>6</td><td>16.67%</td><td>100</td><td>100</td><td align="left">Only uses increments of 10.</td></tr>
<tr><td align="left">[[Reactions]]</td><td>30</td><td>60</td><td>31</td><td>3.23%</td><td>100</td><td>105</td><td></td></tr>
<tr><td align="left">[[Firing Accuracy]]</td><td>40</td><td>70</td><td>31</td><td>3.23%</td><td>120</td><td>125</td><td></td></tr>
<tr><td align="left">[[Throwing Accuracy]]</td><td>50</td><td>80</td><td>31</td><td>3.23%</td><td>120</td><td>125</td><td></td></tr>
<tr><td align="left">[[Strength]]</td><td>20</td><td>40</td><td>21</td><td>4.76%</td><td>70</td><td>71</td><td></td></tr>
<tr><td align="left">[[Psionic Strength|Psi Strength]]</td><td>0</td><td>100</td><td>101</td><td>0.99%</td><td>0</td><td>100</td><td align="left">Fixed for life, never changes.</td></tr>
<tr><td align="left">[[Psionic Skill|Psi Skill]]</td><td>16</td><td>24</td><td>9</td><td>11.11%</td><td>100</td><td>105+</td><td align="left">Initially 0 (a.k.a. psi locked); values are for first [[Psionic_Laboratory|Psi Lab]] result.</td></tr>
<tr><td align="left">[[Melee Accuracy]]</td><td>20</td><td>40</td><td>21</td><td>4.76%</td><td>120</td><td>125</td><td align="left">Non-displayed skill; see text.</td></tr>
</table> 

[[Image:XcomStatsBarChart.png]]

[[Experience#Primary Stats|Primary stats]] are Psi Skill, Firing Accuracy, Reactions, Throwing Accuracy, Bravery, and Melee Accuracy. [[Experience#Secondary Stats|Secondary stats]] are TUs, Stamina (a.k.a. Energy in combat), Health, and Strength. Secondaries increase whenever a Primary action is taken (except for Throwing). For more info, see [[Experience#How_Experience_Points_Are_Applied|Experience]]. [[Psionic Skill]] is the only value that can increase past its combat cap (via the [[Psionic Laboratory|Psi Lab]]). (In theory, a soldier can improve his Psi Skill to 255 with the Lab, at which point it [[Psionic Skill#Psi_Improvement_Strategies|wraps]] back to 0 - but this would take six years of game time.)

All statistics are rolled randomly and independently. So if you only want recruits with 60 TUs, you will retain 1 out of 11 recruits (9%). If you only want ones with 60 TUs and 70 FA, you'll only keep 1 in 351 recruits (0.28%; 1/11 * 1/31). Et cetera.

As discussed [[Energy|elsewhere]], '''initial''' TUs/3 (not total TUs after increases!) govern energy recovery on the battlefield. In other words, your raw recruit's TUs forever after determine how much energy they recover each combat turn. 50 recruit TUs means you recover 17 energy per combat turn; 60 TUs means you recover 20. This gives TUs more importance than you might expect, and makes 60 a pleasure to see.

There are six sets of first and last names, each containing 20 first names and 20 last names. They are ostensibly American, British, French, German, Japanese, and Russian. Soldiers' first and last names are randomly chosen from a single set; thus, there are 2,400 possible unique names (20x20x6). No differences due to nationality, names, etc., have been observed - all stats appear to be entirely random. In each of the six name sets, five of the first names are feminine and the other 15 male; thus, one fourth of all recruits are female. Being female has absolutely no effect on stats or anything else in the game, except for the obvious graphics differences and death sounds. For more detailed info on soldier names, see [[Soldier_Name_Stats|Soldier Name Stats]].

The [[Melee Accuracy]] stat is not shown in displays anywhere but it increases (and secondaries, too) if you use the stun rod. The programmers appear to have put it on the back burner for XCOM, but it does get used more in TFTD.

And now for some useless trivia:

*If you tried to get a soldier who was best in every single stat (including psi strength = 100, but not including psi skill because it's trained, nor the relatively worthless stats of throwing and melee) - given the number of possible values and resulting combinations these eight stats have (shown above),

*You only expect to see the highest across the board in 1 in 66,725,166,816 soldiers (approx. 1 in 67 billion soldiers). This is actually the likelihood of getting any one particular combination, no matter what it is (who says we're not all unique?).

*The current real world population is ~6.5 billion people.

*Given the theoretical maximum screening rate of 1,000 soldiers per month (only 100 fit in the transfer queue at a time, they take 3 days to show up, so only 10 batches of 100 per month),

*You would expect to come across such a soldier by 66,725,167 months (the above number divided by 1,000).

*That's once every 5½ million game years.

And now, back to our regularly scheduled wiki.

==See Also==

*[[Soldiers|Soldier Attributes]]
*[[Experience#How_Experience_Points_Are_Applied|Experience]]
*[[Hiring/firing]]
*[[Soldier Name Stats|Soldier Names]]

[[Category:Soldiers]]
[[Category:Enemy Unknown/UFO Defense]]

Alien Weapon Loadouts

2015-06-22T06:14:29Z

Zombie: A little new info on byte 5.

{| {{StdCenterTable}}
|-
| width="120" | [[Alien Rank]]
! width="30" | 1E
! width="30" | 2E
! width="30" | 3E
! width="30" | 4E
! width="30" | 5E
! width="30" | 1M
! width="30" | 2M
! width="30" | 3M
! width="30" | 4M
! width="30" | 5M
! width="30" | 1L
! width="30" | 2L
! width="30" | 3L
! width="30" | 4L
! width="30" | 5L
|- {{StdDescTable_Heading}}
! colspan="16" | Small Scout
|-
| align="left" | Soldier
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|MP|Mind Probe}}
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| <div style="color:red;">PPC</div>
| {{Abbr|MP|Mind Probe}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|MP|Mind Probe}}
| 0
| 0
|- {{StdDescTable_Heading}}
! colspan="16" | Medium Scout
|-
| align="left" | Soldier
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| 0
| 0
|-
| align="left" | Navigator
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|MP|Mind Probe}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| 0
| 0
|- {{StdDescTable_Heading}}
! colspan="16" | Large Scout
|-
| align="left" | Soldier
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| 0
|-
| align="left" | Navigator
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|MP|Mind Probe}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Engineer
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|MP|Mind Probe}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|MP|Mind Probe}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| {{Abbr|SL|Small Launcher}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| 0
|- {{StdDescTable_Heading}}
! colspan="16" | Harvester
|-
| align="left" | Soldier
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| 0
| 0
|-
| align="left" | Navigator
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|AG|Alien Grenade}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| 0
|-
| align="left" | Medic
| {{Abbr|SL|Small Launcher}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| 0
| {{Abbr|SL|Small Launcher}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| 0
| {{Abbr|SL|Small Launcher}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
|-
| align="left" | Engineer
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| 0
| 0
|-
| align="left" | Leader
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
|- {{StdDescTable_Heading}}
! colspan="16" | Abductor
|-
| align="left" | Soldier
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Navigator
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Medic
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Engineer
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Leader
| <div style="color:red;">PRC</div>
| <div style="color:red;">PP</div>
| <div style="color:red;">PP</div>
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|- {{StdDescTable_Heading}}
! colspan="16" | Terror Ship
|-
| align="left" | Soldier
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Navigator
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| 0
|-
| align="left" | Medic
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| {{Abbr|SL|Small Launcher}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| 0
|-
| align="left" | Engineer
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Leader
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Terrorist 1
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|-
| align="left" | Terrorist 2
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|- {{StdDescTable_Heading}}
! colspan="16" | Battleship
|-
| align="left" | Soldier
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Navigator
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Medic
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|SL|Small Launcher}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Engineer
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|BL|Blaster Launcher}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
|-
| align="left" | Leader
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| {{Abbr|BL|Blaster Launcher}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
|-
| align="left" | Commander
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|BL|Blaster Launcher}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
|-
| align="left" | Terrorist 1
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|-
| align="left" | Terrorist 2
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|- {{StdDescTable_Heading}}
! colspan="16" | Supply Ship
|-
| align="left" | Soldier
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Navigator
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Medic
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|SL|Small Launcher}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| 0
|-
| align="left" | Engineer
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Leader
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|- {{StdDescTable_Heading}}
! colspan="16" | Base Missions
|-
| align="left" | Terrorist 1
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|-
| align="left" | Terrorist 2
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|-
| align="left" | Soldier
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Navigator
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Medic
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|SL|Small Launcher}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| {{Abbr|SB|Stun Bomb}}
| 0
|-
| align="left" | Engineer
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|BL|Blaster Launcher}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
|-
| align="left" | Leader
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| {{Abbr|BL|Blaster Launcher}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
|-
| align="left" | Commander
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|- {{StdDescTable_Heading}}
! colspan="16" | Mars 1
|-
| align="left" | Sectoid Soldiers
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| 0
| 0
|-
| align="left" | Sectoid Leaders
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| 0
| 0
|-
| align="left" | Sectoid Commander
| {{Abbr|PP|Plasma Pistol}}
| {{Abbr|PPC|Plasma Pistol Clip}}
| 0
| 0
| 0
| {{Abbr|PR|Plasma Rifle}}
| {{Abbr|PRC|Plasma Rifle Clip}}
| 0
| 0
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| 0
| 0
|-
| align="left" | Cyberdiscs
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|- {{StdDescTable_Heading}}
! colspan="16" | Mars 2
|-
| align="left" | Ethereal Soldiers
| {{Abbr|BL|Blaster Launcher}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BL|Blaster Launcher}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BL|Blaster Launcher}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
| {{Abbr|BB|Blaster Bomb}}
|-
| align="left" | Ethereal Leaders
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Ethereal Commander
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
| {{Abbr|HP|Heavy Plasma}}
| {{Abbr|HP|Heavy Plasma Clip}}
| {{Abbr|AG|Alien Grenade}}
| {{Abbr|HP|Heavy Plasma Clip}}
| 0
|-
| align="left" | Chryssalids
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|-
| align="left" | Silacoids
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|-
| align="left" | Celatids
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|-
| align="left" | Sectopods
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
| 0
|}

'''Table Key'''
:<div style="color:red;">Red entries indicate an error in loadout (mismatched clips and/or weapons).</div>

:'''E''' = Early
:'''M''' = Middle
:'''L''' = Late

:'''PP''' = [[Plasma Pistol]]
:'''PPC''' = Plasma Pistol Clip
:'''PR''' = [[Plasma Rifle]]
:'''PRC''' = Plasma Rifle Clip
:'''HP''' = [[Heavy Plasma]]
:'''HPC''' = Heavy Plasma Clip
:'''SL''' = [[Small Launcher]]
:'''SB''' = Stun Bomb
:'''BL''' = [[Blaster Launcher]]
:'''BB''' = Blaster Bomb
:'''AG''' = [[Alien Grenade]]
:'''MP''' = [[Mind Probe]]

(all weapons start loaded)

DOS v1.4 data starts at byte 367014 in [[GEOSCAPE.EXE]]; entries are 21 bytes and correspond to the following (borrowed from [[User:Zombie|Zombie]]'s post [http://www.strategycore.co.uk/forums/Alien-Loadouts-Of-Weapons-t6441.html&view=findpost&p=77795#entry77795 at StrategyCore]):
:'''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''': Apparently this is a % chance the alien will spawn outside the craft, needs testing.
:'''06-10''' (x06-x0A): Early game loadout
:'''11-15''' (x0B-x0F): Mid game loadout
:'''16-20''' (x10-x14): Late game loadout

'''Note''': Certain aliens are restricted from being certain ranks. For instance, Mutons are not allowed to be Medics, Leaders or Commanders. When the game populates a map, all of the ranks appropriate to the mission type and difficulty level are created regardless of the race type. The aliens will then be armed according to their rank. Finally the game will then demote any alien with a rank that is not allowed by its race. Demoted aliens will keep the weapons they are assigned prior to the demotion.

[[Category:Enemy Unknown/UFO Defense]]

Scoring

2015-06-21T03:50:45Z

Zombie: /* Losing The Game */ Added equation and one spelling change. I hope it isn't a regional spelling difference.

==X-COM Scoring==
X-COM's performance is measured by way of a score that accrues monthly and is used in part to make the decisions of the funding countries in both their council deliberations on the organisations success, and also when making their individual judgements to change funding levels.

===Interception===
X-COM receive points each time a UFO is destroyed or grounded. Note that if a UFO 'crashes' (per Intercept popup) over the ocean, it only counts as 'grounded' as the funding countries cannot be sure the aliens do not have the ability to repair craft and return from an underwater crash site, and there is no way to do a [[UFO Crash Recovery]] in the oceans to be sure.

<table {{StdCenterTable}} width="30%">
<tr {{StdDescTable_Heading}}><th>UFO Type</th>
<th>UFO Destroyed</th>
<th>UFO Grounded</th></tr>
<tr><td>Small Scout</td><td>100</td><td>50</td></tr>
<tr><td>Medium Scout</td><td>150</td><td>75</td></tr>
<tr><td>Large Scout</td><td>250</td><td>125</td></tr>
<tr><td>Harvester</td><td>500</td><td>250</td></tr>
<tr><td>Abductor</td><td>500</td><td>250</td></tr>
<tr><td>Supply Ship</td><td>800</td><td>400</td></tr>
<tr><td>Terror Ship</td><td>1000</td><td>500</td></tr>
<tr><td>Battleship</td><td>1400</td><td>700</td></tr>
</table>

However, it is actually impossible to destroy a Supply Ship, Terror Ship or Battleship, unless you use a game editor.

X-COM lose points if one of their own craft are destroyed.

<table {{StdCenterTable}} width="30%">
<tr {{StdDescTable_Heading}}><th>Craft Type</th>
<th>Craft Destroyed</th></tr>
<tr><td>Skyranger</td><td>-200</td></tr>
<tr><td>Interceptor</td><td>-250</td></tr>
<tr><td>Firestorm</td><td>-250</td></tr>
<tr><td>Lightning</td><td>-300</td></tr>
<tr><td>Avenger</td><td>-400</td></tr>
</table>

===Battlescape Missions===
During an X-COM battlescape mission, points can be gained or lost by the following actions.

Note that if you abort the mission without completing it, you still get points for performing the actions below. Specifically, you have to kill aliens and/or drag stunned aliens, equipment, and/or [[Elerium-115|Elerium]] back to your ship (or base green area - NOT the red elevator area). Aliens that were killed in a UFO crash (already dead when you got there) do not count. (Briefly visiting a crash site, then dusting off, doesn't get you any points - you have to do things to get points.)

Also note that generally speaking, you get more points from Destroying small UFOs, than for Crashing them and then completing a ground mission. The reverse is true for large UFOs. (Compare Destroying vs. Grounding points vs. Points you can walk away from a Crash with.)

However, the [[UFO Recovery Values|salvage value]] of UFOs may be of greatest importance -- and no equipment can be recovered from destroyed UFOs. The greatest possible recovery value can be gotten from UFOs which are attacked after they land under their own power -- although that earns you no [[#Interception|Interception]] points.

==== Mission Objectives ====

<table {{StdCenterTable}} width="30%">
<tr {{StdDescTable_Heading}}><th>Action</th>
<th>Points</th></tr>
<tr><td>Civilian killed by X-COM</td><td>-50</td></tr>
<tr><td>Civilian killed by Aliens</td><td>-30</td></tr>
<tr><td>X-COM soldier MIA</td><td>-20</td></tr>
<tr><td>X-COM soldier killed</td><td>-20*</td></tr>
<tr><td>HWP destroyed</td><td>-20</td></tr>
<tr><td>Civilian Saved</td><td>30</td></tr>
<tr><td>Alien Base destroyed</td><td>500</td></tr>
</table>

<nowiki>*</nowiki> This increases as the soldier gains rank and experience.

==== Alien Casualties ====
X-COM receives point for capturing or killing an Alien during a battlescape mission.

<table {{StdCenterTable}} width="30%">
<tr {{StdDescTable_Heading}}><th>Race/Rank</th>
<th width="70">Killed</th>
<th width="70">Captured*</th></tr>
<tr><td>Floater Soldier</td><td>12</td><td>24</td></tr>
<tr><td>Floater Navigator</td><td>14</td><td>28</td></tr>
<tr><td>Floater Medic</td><td>16</td><td>32</td></tr>
<tr><td>Floater Engineer</td><td>18</td><td>36</td></tr>
<tr><td>Floater Leader</td><td>25</td><td>50</td></tr>
<tr><td>Floater Commander</td><td>35</td><td>70</td></tr>
<tr><td>Sectoid Soldier</td><td>10</td><td>20</td></tr>
<tr><td>Sectoid Navigator</td><td>12</td><td>24</td></tr>
<tr><td>Sectoid Medic</td><td>14</td><td>28</td></tr>
<tr><td>Sectoid Engineer</td><td>16</td><td>32</td></tr>
<tr><td>Sectoid Leader</td><td>20</td><td>40</td></tr>
<tr><td>Sectoid Commander</td><td>25</td><td>50</td></tr>
<tr><td>Snakeman Soldier</td><td>15</td><td>30</td></tr>
<tr><td>Snakeman Navigator</td><td>17</td><td>34</td></tr>
<tr><td>Snakeman Engineer</td><td>20</td><td>40</td></tr>
<tr><td>Snakeman Leader</td><td>28</td><td>56</td></tr>
<tr><td>Snakeman Commander</td><td>36</td><td>72</td></tr>
<tr><td>Ethereal Soldier</td><td>20</td><td>40</td></tr>
<tr><td>Ethereal Leader</td><td>30</td><td>60</td></tr>
<tr><td>Ethereal Commander</td><td>40</td><td>80</td></tr>
<tr><td>Muton Soldier</td><td>15</td><td>30</td></tr>
<tr><td>Muton Navigator</td><td>17</td><td>34</td></tr>
<tr><td>Muton Engineer</td><td>19</td><td>38</td></tr>
<tr><td>Reaper</td><td>25</td><td>50</td></tr>
<tr><td>Chryssalid</td><td>25</td><td>50</td></tr>
<tr><td>Silacoid</td><td>20</td><td>40</td></tr>
<tr><td>Celatid</td><td>20</td><td>40</td></tr>
<tr><td>Sectopod</td><td>30</td><td>60</td></tr>
<tr><td>Cyberdisc</td><td>20</td><td>40</td></tr>
<tr><td>Zombie</td><td>18</td><td>--</td></tr>
</table>

However, it is actually impossible to capture a live Sectopod or Cyberdisk.

<nowiki>*</nowiki> You will only receive 10 points for capturing any alien species + rank combo already in containment. ''[[User:Ethereal Cereal|Ethereal Cereal]]: What about ones that have been researched & are no longer in containment? Needs more testing.'' ''[[User:Tequilachef|tequilachef]]: I repeatedly got zero points for capturing Reapers while already having a bunch of them in containment, but not researched.''

==== Item Recovery ====
Collection of [[Alien Artefacts]], corpses and craft parts also gains X-COM points. An "artefact" is something you have yet to [[research]] that was carried by the aliens (weapons, ammo and [[Mind Probe]]). Once you research an artefact you no longer receive points for finding that item in future missions. This is a reason not to research alien weapons you likely won't use such as the [[Plasma Pistol]]. Items that spawn in the [[Battlescape]] (as opposed to alien inventories) continue to generate X-COM points after they have been researched.

<table {{StdCenterTable}} width="30%">
<tr {{StdDescTable_Heading}}><th>Item</th>
<th>Points</th></tr>
<tr><td>Alien Alloys</td><td>1</td></tr>
<tr><td>Alien Grenade</td><td>1</td></tr>
<tr><td>Blaster Bomb</td><td>1</td></tr>
<tr><td>Heavy Plasma Clip</td><td>1</td></tr>
<tr><td>Mind Probe</td><td>1</td></tr>
<tr><td>Plasma Pistol Clip</td><td>1</td></tr>
<tr><td>Plasma Rifle Clip</td><td>1</td></tr>
<tr><td>Stun Bomb</td><td>1</td></tr>
<tr><td>Alien Entertainment</td><td>2</td></tr>
<tr><td>Alien Food</td><td>2</td></tr>
<tr><td>Alien Surgery</td><td>2</td></tr>
<tr><td>Examination Room</td><td>2</td></tr>
<tr><td>Celatid Corpse</td><td>3</td></tr>
<tr><td>Chryssalid Corpse</td><td>3</td></tr>
<tr><td>Cyberdisc Corpse</td><td>3</td></tr>
<tr><td>Plasma Pistol</td><td>3</td></tr>
<tr><td>Reaper Corpse</td><td>3</td></tr>
<tr><td>Sectopod Corpse</td><td>3</td></tr>
<tr><td>Silacoid Corpse</td><td>3</td></tr>
<tr><td>Plasma Rifle</td><td>4</td></tr>
<tr><td>Small Launcher</td><td>4</td></tr>
<tr><td>Blaster Launcher</td><td>5</td></tr>
<tr><td>Elerium-115 (Per 50 units)</td><td>5</td></tr>
<tr><td>Ethereal Corpse</td><td>5</td></tr>
<tr><td>Floater Corpse</td><td>5</td></tr>
<tr><td>Heavy Plasma</td><td>5</td></tr>
<tr><td>Muton Corpse</td><td>5</td></tr>
<tr><td>Sectoid Corpse</td><td>5</td></tr>
<tr><td>Snakeman Corpse</td><td>5</td></tr>
<tr><td>UFO Navigation</td><td>5</td></tr>
<tr><td>UFO Power Source</td><td>20</td></tr>
</table>

==== Evaluations ====
An evaluation on your total score is given at the end of each mission.

<table {{StdCenterTable}} width="30%">
<tr {{StdDescTable_Heading}}><th>Ranking</th>
<th>Score</th></tr>
<tr><td>Excellent</td><td>501 or better</td></tr>
<tr><td>Good</td><td>201 to 500</td></tr>
<tr><td>OK</td><td>1 to 200</td></tr>
<tr><td>Poor</td><td>-199 to 0</td></tr>
<tr><td>Terrible</td><td>-200 or worse</td></tr>
</table>

===Research===
X-COM also receive points for the completion of research projects.

<table {{StdCenterTable}} width="30%">
<tr {{StdDescTable_Heading}}><th>Research Project</th><th>Points</th></tr>
<tr><td>Plasma Pistol Clip</td><td>5</td></tr>
<tr><td>Plasma Rifle Clip</td><td>6</td></tr>
<tr><td>Heavy Plasma Clip</td><td>7</td></tr>
<tr><td>Blaster Bomb</td><td>10</td></tr>
<tr><td>Craft Laser Cannon</td><td>10</td></tr>
<tr><td>Heavy Laser</td><td>10</td></tr>
<tr><td>Laser Pistol</td><td>10</td></tr>
<tr><td>Laser Rifle</td><td>10</td></tr>
<tr><td>Laser Weapons</td><td>10</td></tr>
<tr><td>Stun Bomb</td><td>10</td></tr>
<tr><td>Laser Defenses</td><td>15</td></tr>
<tr><td>Tank/Laser Cannon</td><td>15</td></tr>
<tr><td>Alien Grenade</td><td>20</td></tr>
<tr><td>Flying Suit</td><td>20</td></tr>
<tr><td>Medi-Kit</td><td>20</td></tr>
<tr><td>Motion Scanner</td><td>20</td></tr>
<tr><td>Personal Armor</td><td>20</td></tr>
<tr><td>Plasma Pistol</td><td>20</td></tr>
<tr><td>Power Suit</td><td>20</td></tr>
<tr><td>Psi-Amp</td><td>20</td></tr>
<tr><td>Craft Fusion Weapon</td><td>25</td></tr>
<tr><td>Craft Plasma Weapon</td><td>25</td></tr>
<tr><td>Fusion Defenses</td><td>25</td></tr>
<tr><td>Grav Shield</td><td>25</td></tr>
<tr><td>Hovertank/Launcher</td><td>25</td></tr>
<tr><td>Hovertank/Plasma</td><td>25</td></tr>
<tr><td>Hyper-Wave Decoder</td><td>25</td></tr>
<tr><td>Mind Probe</td><td>25</td></tr>
<tr><td>Mind Shield</td><td>25</td></tr>
<tr><td>Plasma Defenses</td><td>25</td></tr>
<tr><td>Plasma Rifle</td><td>25</td></tr>
<tr><td>Psi-Lab</td><td>25</td></tr>
<tr><td>Alien Abduction</td><td>30</td></tr>
<tr><td>Alien Alloys</td><td>30</td></tr>
<tr><td>Alien Entertainment</td><td>30</td></tr>
<tr><td>Alien Food</td><td>30</td></tr>
<tr><td>Alien Reproduction</td><td>30*</td></tr>
<tr><td>Alien Surgery</td><td>30</td></tr>
<tr><td>Heavy Plasma</td><td>30</td></tr>
<tr><td>New Fighter Craft (Firestorm)</td><td>30</td></tr>
<tr><td>New Fighter-Transporter (Lightning)</td><td>30</td></tr>
<tr><td>Small Launcher</td><td>30</td></tr>
<tr><td>UFO Construction</td><td>30</td></tr>
<tr><td>UFO Navigation</td><td>30</td></tr>
<tr><td>UFO Propulsion</td><td>30</td></tr>
<tr><td>Ultimate Craft (Avenger)</td><td>30</td></tr>
<tr><td>Blaster Launcher</td><td>40</td></tr>
<tr><td>Elerium-115</td><td>40</td></tr>
<tr><td>Alien Autopsies (Each)</td><td>50</td></tr>
<tr><td>Alien Interrogations</td><td>50**</td></tr>
<tr><td>Alien Origins</td><td>60</td></tr>
<tr><td>Cydonia or Bust</td><td>60</td></tr>
<tr><td>The Martian Solution</td><td>60</td></tr>
</table>

<nowiki>*</nowiki> Alien Reproduction is normally not accessible (or researchable) during the game, but you can add one to your General Stores via hacking.

<nowiki>**</nowiki> You receive 50 points for each new [[UFOpaedia]] entry generated by an alien interrogation. A given alien can generate several UFOpaedia entries, or none at all. (See [[Research#Researching aliens|Researching aliens]] for more information.)

==Alien Scoring==
Aliens score points for various actions as well.

<table {{StdCenterTable}} width="30%">
<tr {{StdDescTable_Heading}}><th>Alien Action</th><th width="50">Score</th></tr>
<tr><td align="left">Each UFO that flies over the Earth (per 30 mins)</td><td>1</td></tr>
<tr><td align="left">Each UFO that lands (per 30 mins)</td><td>2</td></tr>
<tr><td align="left">Each day an alien base exists on Earth (Per base)</td><td>5</td></tr>
<tr><td align="left">A terror mission in a remote area is performed successfully*</td><td>10</td></tr>
<tr><td align="left">A harvest mission is performed successfully*</td><td>30</td></tr>
<tr><td align="left">An abduction is performed successfully*</td><td>50</td></tr>
<tr><td align="left">Alien base is built</td><td>50</td></tr>
<tr><td align="left">Aliens sign a [[pact]] with a funding country</td><td>150</td></tr>
<tr><td align="left">A city terror site is ignored by X-COM</td><td>1000</td></tr>
</table>

===Notes on Alien Score===
* Success is counted each time an UFO takes off. If a single ufo lands multiple times, it will score each time it starts flying again including if disturbed by an unsuccessful X-COM mission.
* Successful Alien Research, Retaliation and Supply missions do not score any points for the aliens.
* The aliens' score can be viewed by looking in the graphs menu. At the end of the month it is subtracted from X-COM's score to give the player's score for the month. It is reset at the end of each month just like the player's.

==Losing The Game==

You can lose the game in the following ways:

* If you are in debt over $1 million at the end of any month, after funding and maintenance has been calculated, the council will give you a warning. The warning they give about not going over $2 million in debt should presumably read $1 million. The 2nd time you are over $1 million in debt, the project is cancelled. However, there is a rather large bug. There is actually a check whether the "Has X-COM received a financial warning?" flag has been raised. If no, a warning is issued and the flag is raised. If yes, then the game ends, and the flag is lowered. HOWEVER, this flag is erroneously not connected to any particular savegame, it is global across all savegames. This allows strange results when saving and loading games.
* If you have two consecutive "bad" months in terms of score--
** '''-900''' (Beginner)
** '''-800''' (Experienced)
** '''-700''' (Veteran)
** '''-600''' (Genius)
** '''-500''' (Superhuman)
** The actual equation is Terminator= -900 + difficulty*100; where beginner is 0, experienced is 1, veteran is 2, genius is 3 and superhuman is 4.
* If all X-COM bases are captured by Aliens. (But you can stay in the game by starting a new base before your last base is captured - see [[Access_Lift|Access Lift]].)
* If you fail your attempt to destroy Cydonia!

==See Also==
[[ALIEN.DAT]] - Where the aliens' score is tracked 
[[XCOM.DAT]] - Where score from missions and interceptions is tracked 
[[UIGLOB.DAT]] - Where scores generated from research completion is stored 

[[Category: data tables]]
[[Category:Enemy Unknown/UFO Defense]]

Talk:MCD

2015-06-20T05:08:42Z

Zombie: /* Offset 38 (0x26) */ Reply

52: Footstep sound effect.

I didn't log in because I don't have an account... yet. I looks like I was wrong on the arctic terrain, I thought it uses sand effect, but I checked it's actually normal (2).

----
I've started writing a section on Terrain/Map Editing and the technical portion (the structure of the MCD files and so on) has been already presented here. Should I add the Terrain Editing material to this page or start a new one? [[User:Hobbes|Hobbes]] 19:39, 18 Nov 2005 (PST)

----
I am wondering if we might not have a major restructuring of all this stuff. Instead of first "Under the Hood", then "Game File Analysis", and then on yet another link, "Saved Games"... I think these parts warrant enough attention (at least by many wiki regulars) that they have their own link off the main page, and then something like this structure:

Overviews
(right here goes overviews of everything, then:)
Main Programs And Data
Savegame Files
Specific Directories And Files
Main Programs And Data
Savegame Files

Something like that... ANY suggestions welcome, but I think it's time to revamp the lot of it to show it's importance to many regulars, and leave places for overviews versus specific things.

Edit: To answer you more specifically, Hobbes: Choose your place; a general place is fine for me. I think we should overhaul the whole structure. I think it's grown past its original little pecks and nibbles.

What do the rest of you think? ---[[User:MikeTheRed|MikeTheRed]] 19:58, 18 Nov 2005 (PST)

----
Sounds spiffy. --[[User:Danial|Danial]] 20:01, 18 Nov 2005 (PST)

----

Yup, I was planning on doing something like that later on... We'll have to do it a few times as we introduce more pages, in order to keep everything easy to find.

--[[User:Bomb Bloke|Bomb Bloke]] 20:59, 18 Nov 2005 (PST)

== Offsets 22-29 / 0x16-0x1D ==

They seem to be the same as 2-9 bytes of UnitRef table. After MCD loading they are filled with pointers to appropriate pck/tab.

v60 = &a_mcd_data[result];
v60->field_1A_pck = a_TileSet_Catalog[v_BF_Tileset_Cnt].pck;
v60->field_16_tab = a_TileSet_Catalog[v_BF_Tileset_Cnt].tab;

I've found this the same way as for unit pck/tab pointers.
--[[User:Volutar|Volutar]] 14:27, 21 February 2011 (EST)

== Offset 47 / 0x2F ==

It is set to 1 when the MCD data is used as an opened door tile type. It is only set at runtime when a door is opened. Since MCD data is not saved, this explains the door jam bug that makes the doors stay opened when you reload. You can test that on the medium scout ship: if you open the door to the central reactor room and save/reload, the door will stay stuck. If you now open a door of the same type (and same orientation) and end the turn, the door to the reactor chamber will be closed again on the next turn. [[User:Seb76|Seb76]] 14:18, 13 December 2008 (CST)

== Offset 51 / 0x33 ==

Who said this is LIGHT block?
Game uses this field in calculations of explosion wave permeability, so it apparently should be called "explosion block"
Function at address .text:00417F40 refers to this field and to the table (dimensions is 11x17: 11 block values for 17 levels of intensity) at .data:0046C45C. This function is used for calculation of how much explosion will come from x/y/z to its neighbour x1/y1.
--[[User:Volutar|Volutar]] 14:28, 15 April 2011 (EDT)

It's not that easy as it meets the eye. This function (using field 51) works only for second chained explosion. It doesn't create lot of smoke comparing to original and first chained explosions...

Does anyone have particular observation of such ''non standard'' explosions behaviour?
--[[User:Volutar|Volutar]] 05:55, 16 April 2011 (EDT)

This field indeed was ment to be used for lighing calculation (they were using same function for explosion field calculation and for lighting). But they calceled use of this function for light blocking, I dont know why, maybe its results wasn't very good. Still they've left this "lighting" function and it is used after first chained explosion (original, chained1,(enabling!), chained2, chained3, etc). Results are quite unpredictable, since intensivity more than 16 cause getting out of bounds. If you manage to get to this second chained explosion you may notice it looks weird.

void DoExplosion(x,y,z,intens,radius)
{
isExplosion=1;
ClearChainedExplBuffer();
CalcExplosionLightMap(x,y,z,intense,radius); //<--- depending on isExplosion it calculates damage field or lighting
ApplyExplosionDamage(); //<--- adds chained, if something with flag "HE" got exploded
while(!ChainedExplosionsEOF())
{
GetNextChainedExplosion(&x,&y,&z,&intense,&radius)
CalcExplosionLightMap(x,y,z,intense,radius);
ApplyExplosionDamage();
isExplosion=0; /// <--- WHY??? Obviously a bug
}
isExplosion=0;
}
BTW, there are only 50 chained explosions possible, 51th won't explode.
--[[User:Volutar|Volutar]] 06:41, 16 April 2011 (EDT)

== MCDedit ==

Urgh. MCDedit and support files are gone. Anyone want to put it somewhere more ... permanent? Strategycore files section, for example?
[[User:Knan|Knan]] 21:25, 13 March 2009 (EDT)

:It's been in StrategyCore's files section for years now. [http://www.strategycore.co.uk/files/index.php?dlid=415 Clicky]. :) --[[User:Zombie|Zombie]] 21:52, 13 March 2009 (EDT)

::Right. Only went looking in the Editors section, Maps didn't register on the radar. --[[User:Knan|Knan]] 17:47, 14 March 2009 (EDT)

== Ground with TUs = 0 ==

There are at least 2 ground tiles which consumes 0 TUs to walk through them.
Interesting thing, that pathfinder deny walk directly on them, you can only walk ''through''.
These are 6 and 7 tiles in U_BITS tileset.
--[[User:Volutar|Volutar]] 08:02, 12 October 2011 (EDT)

== Offset 38 (0x26) ==

Zombie: Defined as "printype"; 3=whole, 2=right side, 1=left side.
Since this is always 3 the game prints the entire object, while the assumption is that
values of 2 or 1 are possibly used for the map designer.

Where is it "defined"? It's not used in the game code AT ALL. There is no check whether it 3,2 or 1.
What map designer do you mean?

I seems to me as just a fantasy.
--[[User:Volutar|Volutar]] ([[User talk:Volutar|talk]]) 10:34, 19 June 2015 (EDT)

:Before you accuse me of being delusional or making stuff up, consider that I am working directly off of dev comments from part of the ACTUAL C code from UFO which I received recently. It's commented in there plain as day. Whether it is actually used in-game anymore is not a earth shattering concern - providing explanations to the remaining unknowns is what I'm after. The burden of proof lies in testing or code digging to see if it is used or not. (You are more than welcome to provide any additional information you can find out). And before this discussion degrades into a "but you only have it, I can't trust you unless I can see it myself" issue, no, you may not get the C code until I can get it cleared through 2K/Firaxis. --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 01:08, 20 June 2015 (EDT)

SMOKREF.DAT

2015-06-18T06:07:55Z

Zombie: /* Structure */ Minor additions, etc.

'''SMOKEREF.DAT''' contains 400 records of 9 values of one byte each for a total of 3600 bytes.

There are a total of 12 sprites available for displaying smoke. Any given patch will animate through 4 consecutive sprites. The first sprite is (int)(smokeref[3] / 6 + 8) in [[SMOKE.PCK]].

That is to say, if the smoke is due to last for less then six turns, smoke sprites 0 to 3 will be used. If the smoke is due to last less the twelve but more then five turns, sprites 1 to 4 will be used, and so forth.

This allows for nine different densities of ''displayable'' smoke. If the smoke is due to last fifty four or more turns, however, then [[rank]] badges will be included in the smoke animation. Values higher still will include bullet animations.

Smoke hinders vision according to a similar formula - (int)(smokeref[3] / 3). That is to say, take a cloud's "time to live", divide that by three and round the result down: This tells you how many tiles it chops off your effective range.

For example, say there are ten clouds with a TTL of 1 directly between you and your target. In this scenario, they won't affect your vision at all (1/3 rounded down = 0). But if they each have a TTL of 8, they'll each require you to move closer by two tiles (8/3 rounded down = 2) - removing 20 tiles from your visibility range!

Because the formula for what you see on the screen doesn't match the formula for how smoke obscures vision, it's impossible to tell a cloud's effect just by looking at it. For example, a cloud with a TTL of 7 will look the same as a cloud with a TTL of 10 - But the first cloud will only remove two tiles from your vision, whereas the second removes three.

Smoke clouds will drift around the battlescape and merge with others (effectively making them denser), though the rules for how are currently unknown. Summed up simply this means that smoke grenades are most likely more effective a few turns after they actually go off.

==Structure==
* '''0:''' Y position of smoke/fire.
* '''1:''' X position of smoke/fire.
* '''2:''' Z position of smoke/fire.
* '''3:''' Time smoke will last (also used as density). AKA "Intensity"
* '''4:''' Time fire will last. AKA "Age"
* '''5:''' Number of smoke patches overlapped (used only in runtime). Called "justspread"; 0=hasn't spread recently otherwise intensity of new spread.
* '''6:''' Fire or smoke?
** 0 Empty
** 1 Fire
** 2 Smoke
** 3-6 Gas (probably unused)
* '''7:''' Visibility flag. Note that smoke still won't be rendered unless the tile it's in is also visible.
* '''8:''' Animation frame offset. Set at random, to break tile pattern in cloud of smoke. Ranges from 0 to 3. (My game description has values 0-4, not sure if 4 is used or not).

==See Also==
* [[Saved Game Files]]
* [[Saved_Game_Files#Battlescape_Files|Battlescape Files]]
* [[Smoke and Fire]]
* [[Smoke Grenade]]
* [[SMOKBIT.DAT]]

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

OBDATA.DAT

2015-06-18T04:52:38Z

Zombie: /* Structure */ Some new info, described some fields to better match game.

'''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[0x0~0x13]: 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[0x14]:''' [[BIGOBS.PCK]] reference (pointer to graphic for inventory)

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

'''22[0x16]:''' 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[0x17]:''' 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[0x18]:''' Inventory X Size (width)

'''25[0x19]:''' Inventory Y Size (height)

'''26-28[0x1A~1C]:''' 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[0x1D]:''' [[HANDOB.PCK]] Image of item when held in a units's hands in the battlescape view.

'''30[0x1E]:''' Often corresponds to 29, but does not appear to be used. Called "graphics type firing" by the game. Is this the shot graphic to use for the weapon?

'''31[0x1F]:''' 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[0x20]:''' Accuracy, Auto

'''33[0x21]:''' Accuracy, Snap

'''34[0x22]:''' 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[0x23]:''' Percent TUs Used, Auto

'''36[0x24]:''' Percent TUs Used, Snap

'''37[0x25]:''' Percent TUs Used, Aimed

'''38[0x26]:''' 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: Turn detonation condition for "grenade" objects, but is otherwise unused. If the Grenade ([44]) and the 'is ammo?' ([49]) fields are set to true, this will create an explosive that is pre-armed to go off at a turn designated by this field. A side effect is that the grenade object will show an ammo count with this field's value.

'''39[0x27]:''' 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[0x28]:''' Melee Accuracy. Zombie [http://www.strategycore.co.uk/forums/topic/746-damage-modifiers-for-aliens/page__st__160#entry70596 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% for UFO, but in TFTD it is a valid and effective variable. (TFTD uses much more melee than UFO.)
0 All Corpses
0 Electroflare
0 Plasma Weapon Clips
100 ''Everything else...''

'''41[0x29]:''' TU% cost when attacking as a melee weapon
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[0x2A]:''' Explosive strength needed to [[Explosions#Object_Destruction|destroy object]]. AKA "Constitution".

'''43[0x2B]:''' [[Item Weight]], used for both throwing and encumbrance purposes.

'''44[0x2C]:''' Grenade Type
1 Standard explosive grenade
2 Proximity Grenade
3 Smoke Grenade
4-7 Gas - probably unused.

'''45[0x2D]:''' Value (or "priority") to the AI of picking up this weapon.

This field used as AI "worth to take" estimation flag, and only when it's >5. By accident or by design, it was not implemented. However this can be easily implemented by setting values above 5. This would have the benefit of making Aliens smarter after they lose their weapons or run out of ammo. See the talk section of this page: [[Talk:OBDATA.DAT#Field_0x2D_.2845.29]]

'''46[0x2E]:''' Boolean: Is Weapon That Shoots? (AKA Is Ranged Weapon)?

'''47[0x2F]:''' Boolean: Is Weapon? (AKA Close Combat Weapon)?

'''48[0x30]:''' Boolean: Is Non-Waypoint Weapon? (AKA Is Ranged Combat Weapon)?

'''49[0x31]:''' Boolean: Is Ammo?

'''50[0x32]:''' Boolean: Is Two-Handed Weapon? (AKA Is Large Weapon/Object)?

'''51[0x33]:''' Boolean: Is Blaster Launcher? (AKA Weapon Fires Guided Missile)?

'''52[0x34]:''' Boolean: Is Alien? (AKA Is Alien Artefact)?

'''53[0x35]:''' [[Scoring]] points (except for Elerium which works per 50 units). (AKA Victory Points for recovery).

==Extra Notes==
===Unique Objects===

Certain unique objects have "unique" features that are assigned to them. These are:

* Motion Scanner - can access motion scanner panel
* Medikit - brings up medikit panel
* Flare - will cast light around its object if on ground whenever the light level of the map is updated, such as when throwing a flare or when walking.
* Stun Rod - only weapon that can access its melee attack
* Mind Probe - can probe enemies
* Psi Amp - can access two different psi attacks
* Elerium - adds 50 units of elerium to storage at end of battle

TFTD's equivalents are same but also add the three drill weapons as melee weapons.

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

One way around the melee command 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===

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 the weapon a valid damage type (set offset [31] to a value from 0-7), and give the weapon a power rating (set offset [22] to the average you want the weapon to deal). All the usual flags for standard firearms apply.

===Grenades===

Grenades are similar to laser weapons in that the object's power (offset[22]) and damage type (offset[31]) must be set. In addition, to complete the object as a grenade, the Grenade type (offset[44]) must also be set to standard (1), proximity (2) or smoke (3) in order for the item to be turned into an object that can be primed.

Be aware that regardless of the damage type entered, it will default to HE.

Any object that's not functioning as a gun or as ammo can be turned into a grenade of some description.

Note that if you set the Is Ammo? (offset[49]) field to true, the grenade will be pre-armed at the start of the battle to explode after the turn specified in offset[38], which is normally used for ammo count or melee attack strength. The grenade will also gain an ammo-count display on it with the value in offset[38].

One practical application of this is to create exploding elerium pods that will explode after a pre-set number of turns. For example, setting offset[38] to 40, and by the time you reach turn 20, any elerium pods that have not been destroyed or picked up will explode. Set the damage to strength to something insignificant like 1 to let them wink out of existence, or up to 255 for violent explosions.

===Guided Weapons===

The flag in Offset[51] controls whether the object fires a way-point guided projectile. Projectiles fired by this weapon will also default to HE damage.

Once set, the flag overrides various obdata.dat settings. Firing costs will default to 60% while the accuracy of the projectile will not be influenced by the user's base accuracy.

==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]]
[[Category:Enemy Unknown/UFO Defense]]

MCD

2015-06-18T04:25:16Z

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

{{tocright}}MCD (Map Control Data) files, which are stored in the [[TERRAIN]] folder, contain multiple 62-byte records that define the tiles that make up a given terrain. For example, BARN.MCD defines a number of terrain items such as walls, haybales, floors and ceilings, while DESERT.MCD defines things like sand (ground tiles), sand dunes, rocks, and cacti.

Each MCD file is accompanied by a [[Image_Formats#PCK|PCK and a TAB file]] with the same filename. These contain the image data referenced by the MCD itself. The tiles within the MCD files are referenced by both the files in the [[MAPS|MAPS folder]] and [[MAP.DAT]], in order to create "map modules"; these are then grouped together at run-time to create randomly generated battlescapes.

Often, more than one MCD file will be required to represent a given map. For example, farms are made using tiles from both the CULTIVAT (fields) and BARN (farmhouse) sets.

 
==Usage==
At run-time, a collated MCD array is created from the smaller sets stored in this folder. In order, this is made up of:

* BLANKS.MCD (two records, the first of which is the black tiles rendered outside of the "map boundaries", and the second of which is the burnt dirt resulting from explosions).
* The set(s) corresponding to the terrain (for example, the MCD files corresponding to the desert or forest areas).
* The set corresponding to the X-COM dropship, if one is present on the map.
* The set(s) corresponding to the alien craft, if one is present on the map.

This large table may never exceed 256 total entries (or the game will crash). For example, you can't have an X-COM and an alien craft present in an urban map; this will result in a "too many map-codes" error.

The [[MAPS|associated map modules]] are also loaded into a [[MAP.DAT|single large map array]], with the tile indexes modified to account for the re-positioning caused by appending the MCD tables together. For example, a wall tile in the Supply Ship MCD file might be the second record, and that's what the map module file will index to (well, that plus 2, but see the [[MAPS]] page for more on that): However, after appending the Supply Ship MCD file to the end of the collated MCD array, that wall tile might now be index number two hundred!

Likewise, any tile indexes within the collated MCD files themselves, or to the associated PCK sprites (which are ''also'' collated into a single array), need to be "updated" in the same way (tile indexes within the MCD structure are at offsets [[#44|44]] and [[#46|46]] of each record).

Because the collated MCD array can be (mostly) recreated at any time, it is not written to the hard drive when the user saves the game mid-battle. This has a side effect of causing [[Known_Bugs#Door_jam|doors to stick open]], as offset [[#47|47]] won't be correctly tracked.

==Structure==

{| class="wikitable"
|-
!Offset (Decimal)
!Offset (Hex)
!Usage
|- valign="top"
!0-7
!0x00-0x07
|Animation of the tile.

The eight bytes refer to images on the PCK files which are used in a sequence (from the first byte to the last) to animate tiles. This animation is used by several tiles on both games, such as doors (see [[#46|[46]]]), bubbles on TFTD, blinking lifts, etc. If all eight frames are the same, it's a static tile.
|- valign="top"
!8-19
!0x08-0x13
|Line Of Fire Template (LOFT) for the tile. 12 values, each references into [[LOFTEMPS.DAT]] file.

Each LOFT record is a 16x16 grid; these are stacked one over the other, with mcd[8] being the bottom. Used to create a 3D map (16x16x12) of the tile, for LOS. For more info, see [[LOFTEMPS.DAT]].
|- valign="top"
!20-21
!0x14-0x15
|Reference into [[SCANG.DAT]] file. Two-byte integer ([20] + [21] * 256 + 35 = offset). 4x4 bmp images for the top-down map; see [[SCANG.DAT]].
|- valign="top"
!22-25
!0x16-0x19
|Four byte value pointing to the RAM location of the [[Image_Formats#PCK|TAB index for the PCK data]] used by the terrain file. Only used at run-time.
|- valign="top"
!26-29
!0x1A-0x1D
|Four byte value pointing to the RAM location of the [[Image_Formats#PCK|PCK set]] used by the terrain file. Only used at run-time.
|- valign="top"
!30
!0x1E
|Boolean: Is sliding door? See [[#46|[46]]].
|- valign="top"
!31
!0x1F
|Boolean: Blocks visibility of terrain? AKA LOS (Line Of Sight)
0 = False = Doesn't block visibility.
1 = True = Blocks visibility.
Visibility of units is blocked by voxels formed with [[LOFTEMPS.DAT]].
Note that floor tiles always block visibility of terrain, although their flag is 0, but it's ignored for floor tiles.
|- valign="top"
!32
!0x20
|Boolean: Can't be stood on? For ground tiles: non-flying units fall through. ''Only two ground tiles have this set: BLANKS MCD id 0 and UFO1 MCD id 0''
|- valign="top"
!33
!0x21
|Boolean: Is Wall? Used for Objects intended to act as Walls; used to make UFO, Skyranger, and Avenger outer "walls" that aren't otherwise possible as "real" North or West walls. If that sounds ambiguous, that's because no one's worked out what it actually does; whether an object can be walked on/through depends on it's TU cost ([[#39|[39]]]) and height ([[#48|[48]]]). Called "BigWall" in [[MapView]].
|- valign="top"
!34
!0x22
|Boolean: Is Grav lift? Up/down of lifts is determined by whether there is another one above or below in the .MAP.
|- valign="top"
!35
!0x23
|Boolean: Is hinged door? See [[#46|[46]]].
|- valign="top"
!36
!0x24
|Boolean: Blocks fire?
|- valign="top"
!37
!0x25
|Boolean: Tile blocks smoke (or a "gas" type which was never implemented) from spreading. Used in smoke propagation routine.
|- valign="top"
!38
!0x26
|Always 3. Defined as "printype"; 3=whole, 2=right side, 1=left side. Since this is always 3 the game prints the entire object, while the assumption is that values of 2 or 1 are possibly used for the map designer.
|- valign="top"
!39
!0x27
|Time units used to walk across the tile (255 means unpassable).
|- valign="top"
!40
!0x28
|Time units used to slide across the tile (255 means unpassable).
|- valign="top"
!41
!0x29
|Time units used to fly across the tile (255 means unpassable).
|-
|colspan="3"|For [[#39|[39]]] to [[#41|[41]]], values range from 0 to 8, or are 255. There are only a few places where they are not all the same ([[#39|[39]]]=[[#40|[40]]]=[[#41|[41]]]):

Walk Slide Fly File Description

2 0 2 Avenger Middle ramp object

255 255 4 Arctic Water pools in ice (18 ground MCDs)

2 2 0 U_Base Death ''objects'' for large round containers in alien bases (four quadrants)...
thus, their remnants don't ''add'' TUs for fliers

1 1 0 U_Base Little green plant objects found on black "base garden" flooring

2 2 0 Urbits Two death objects (splinters on ground) for city's tall green picket fence
(one is a North-wall fence, the other is a West-wall fence)

Which of the three movement types a given unit uses is determined by [[UNITREF.DAT#11|UnitRef[11]]]. Note that by default, ALL units are "walkers".
|- valign="top"
!42
!0x2A
|Armor of tile.

*Tile must take this amount of damage to be destroyed, at which point it changes to a tile set according to [[#44|[44]]].
*Terrain items do not "remember" damage (like units); terrain is either destroyed in a single blast/shot (if damage >= armor) or not.
*Some things are set to 255 to mean "indestructible" but actually, anything >100 is indestructible in a non-hacked game, and anything >127 (for explosives, 255/2) or >191 (firearms, 255x.75) cannot be destroyed, even in a hacked game (see [[Damage]] re: Damage to terrain).
*With explosions, all four terrain items in the tile are hit by the same strength, but firearm shots target only one of them.
*For a loopy exception to explosions being equally applied (due to erroneous data), see [[Explosions#Mile-High Madness|Mountain Madness]].
*''[[User:NKF|NKF]]:'' I suppose you could make a gate out of this by creating two tiles, each easily destroyed, which change to the other when hit. One could be walked across, the other could not.
|- valign="top"
!43
!0x2B
|[[Explosions#HE Block|HE Blockage]]
|- valign="top"
!44
!0x2C
|Tile becomes a tile of this type (i.e., this other MCD record in the same MCD file) when destroyed. Also known as the '''death tile'''. Also see [[#53|[53]]].

'''Note:''' If [44]=0, it means there is no death tile per se; it reverts to a "raw earth" (BLANKS[01]) tile if on ground, or nothing if in air. (It does not revert to the MCD id 0 record in the current collection.)
|- valign="top"
!45
!0x2D
|Flammability - the higher this is, the less likely the tile will be set on fire.
|- valign="top"
!46
!0x2E
|If the tile is a door ([[#30|[30]]] or [[#35|[35]]]), the tile will become this tile number when opened. Animation [0] (see [[#0-7|[0-7]]]) is shown until someone walks through the door, in which case it cycles through its animation stopping and holding Animation [7]. Then it will return to a closed door next turn.
|- valign="top"
!47
!0x2F
|Flags 1 for the "open" version of a sliding door if a door of that type was opened this turn (hence notifying the game that it needs to search the map for doors to close on the next). Because this value is only used at run-time, and the collated MCD array is not written to disk if the player saves the game, reloading while sliding doors are open will [[Known_Bugs#Door_jam|cause them to jam]] until another door of the same type is opened.
|- valign="top"
!48
!0x30
|Signed value, usually negative; add this to the graphical Y offset of units or objects on this tile (adding a negative is the same as subtracting, and the lower the Y offset is, the higher the unit will appear on-screen). The value is relative to the level the tile is placed on, so it's usually 0 (meaning "at the same level").

A unit may only step from one tile to another if the effective difference in tile heights are 8 or less. For example, ground level is at 0, while the lower segment of a staircase will typically have this set to -8 and the higher segment at -16. A soldier can step onto the lower segment from the ground, then onto the upper segment, then finally onto the next level above. He cannot step directly from the ground to the upper staircase, let alone to the next level, as it's too great a "jump" to perform in a single movement.

The effective difference between levels on the map is 24.
|- valign="top"
!49
!0x31
|Subtract this value from the graphical Y offset of the tile image (used for hills).
|- valign="top"
!50
!0x32
|Received damage modifier type (taken from [[Damage#Damage_Modifiers|Damage modifier table]]) - Always 0.
|- valign="top"
!51
!0x33
|Lightblock. Note that the actual game seems to ignore this value.
0 Blocks no light.
''... up to ...''
10 Blocks all light.
Is apparently percentage based: 1=10%, 10=100%.
|- valign="top"
!52
!0x34
|Footstep sound effect. Most likely an index to the .CAT file RAW wave ''-[http://www.strategycore.co.uk/forums/Map-Control-Data-MCD-long-Post-t1468.html BladeFireLight]
0 Not used in XCOM (makes a metal sound if hacked); is used on TFTD for some objects
1 Metal
2 Normal (Grass, Wood, Dirt)
3 Three mountain ground tiles, and some city apt. furniture objects that can't be
walked on? (six furniture objects might've been - but they're death tiles that
nothing points to.) Uses same sound as 6 in DOS version.
4 Pool of water (Not used in XCOM)
5 Sand (Desert)
6 Martian ground (DOS version), snow (CE version)
7 Snow (only DOS version, Not used in XCOM, Arctic terrain actually uses 2)
|- valign="top"
!53
!0x35
|Tile type:
0 Floor
1 West Wall
2 North Wall
3 Object

In the map, there are four bytes per tile: One each for the floor, west wall, north wall and object. If one of those changes (eg is destroyed, or in the case of a door, opened), it is removed from the map and a new object is placed instead. This byte is used to work out which of the four map bytes should recieve the new object.

For example, in the mountains, if you destroy the ground tile you get an object (tree stump). The new tile gets written into the fourth byte of the map record, even though the original tile that was destroyed belonged in the first byte.

As for the potential for change in tile type when becoming death tile ([[#44|[44]]]): There are 22 instances of [[Explosions#Mile-High Madness|Mountain Madness]] (ground to object), 1 instance of North Wall becoming an object (XCOM1 northwall door becomes rubble), one MCD record with tile type of '''10''' (Barn 7 which looks like a North Wall and becomes northwall when killed; obviously a typo'd Tile Type), and 31 total instances on 18 different tilesets where objects become ground upon dying (probably to "scorched earth", but this was not checked).
|- valign="top"
!54
!0x36
|Explosive type; [[#55|[55]]] must be >0:
0 HE
1 Smoke
''Notes:''
#To see explosive objects in XCOM, see [[Explosions#Explosive Map Objects]].
#Type 0 (HE) explosions follow the usual rules for [[explosions]] (average damage to units decreases by 10 per tile outward, etc.).
#Hackers: Type 0 (HE) terrain items with little or no armor ([[#42|[42]]]=0) are obliterated before exploding (i.e., they won't explode, no matter how high [[#55|[55]]] is). Probably also depends on whether it was a very big blast relative to the armor.
#Chain reactions are exceedingly difficult to set up (per Hobbes). Most of the time when you see e.g. the four sections of the Navigator's table explode, it's because you used explosives that actually set off each one individually. It has to do with a balance of, among other things, not obliterating the object (see previous point).
#Type 1 (Smoke) explosives are strange, and mainly only affect aliens - and very haphazardly at that. XCOM units are only very rarely affected; I could only get it to work if they were 1) unarmored, 2) on a diagonal, and 3) no other objects are "in the way" between the blast moving "over and up" or "up and over" to the diagonal (blast propagation never moves directly diagonally per se; see [[Explosions#Playing With Fire]]). ''-MTR''
#Chain reactions are not possible with Type 1 (Smoke) explosive objects.
#Also, when dealing with smoke damage, remember that if there is already tons of smoke on the map (filling up the smoke table) such that no new smoke can appear, you might get unexpected results (or no effect). ''[[user:Hobbes|Hobbes]]:'' One strange thing that can happen when there's already too much smoke on the map and an object with [54]=1 explodes is that the alien dies and in the dying animation there's smoke on that square. ''Just in the dying animation, not after he's down? -MTR'' - ''I can't remember right now if the smoke remains afterward. Next time it happens I will check it [[User:Hobbes|Hobbes]] 12:00, 18 Nov 2005 (PST)''
#There are no "naturally occurring" HE explosives tiles in UFO. All explosive objects are MCD[54]=1.
#The game show values of 0=not explosive, 1=normal (which I assume is HE), 2=gas (again, unused feature).
#TFTD uses both values for [54], 0 (more common, like the barrels on Port) and 1 (the Synomium device on Grunge/Artifact Site).
|- valign="top"
!55
!0x37
|Strength of explosion when tile is destroyed.
|- valign="top"
!56
!0x38
|Smoke blockage. This is set to 0 for all UFO tiles!
Technically called "gasblock" by the game. Supposedly it would block the gas type from spreading. Not sure if this is intended to be just smoke, gas or a combination of the two. Needs testing.
|- valign="top"
!57
!0x39
|Fuel. The amount of turns this tile will burn for.
|- valign="top"
!58
!0x3A
|Brightness of tile. Amount of light produced.

11 MCDs produce light: 7 alien base objects (several pulsing fuel pods and several 4-part round "museum containers"), 2 XCOM base ground tiles, and 2 city objects (street lamp and large standing room lamp). See [[Night_Missions#Artificial_Lighting|Night Missions]] for pictures. Oddly, values range from 1 for the street lamp to 16 for the alien base museum containers, so lower values must be brighter. The [[Night Missions|distances]] of projected light have yet to be determined, but note that flares and personal lighting ignore vertical distance... at night, a soldier can see aliens on the ground exactly 9 tiles away, regardless of whether the soldier is at ground level or 4 levels high.

''In practise, it seems if this is not zero then the tile will be fully illuminated regardless of the value. - [[User:Bomb Bloke|Bomb Bloke]] 06:48, 20 June 2008 (PDT)''
|- valign="top"
!59
!0x3B
|Special properties of tile. Determines what is salvaged at end of mission. Note that some are not actually used within their respective games:

UFO TFTD TFTD (per MapView)
0: ''No Special Properties'' 0: ''No Special Properties'' 0: ''No Special Properties''
1: Entry Point 1: Entry Point 1: Entry Point
2: [[UFO Power Source]] 2: [[Ion-Beam Accelerators]] 2: [[Ion-Beam Accelerators]]
3: [[UFO Navigation]] 3: [[Magnetic Navigation]] 3: "Destroy Objective"
4: [[UFO Construction]] 4: [[Alien Sub Construction]] 4: [[Magnetic Navigation]]
5: [[Alien Food]] 5: [[Alien Cryogenics]] 5: [[Alien Cryogenics]]
6: [[Alien Reproduction]] 6: [[Alien Cloning]] 6: [[Alien Cloning]]
7: [[Alien Entertainment]] 7: [[Alien Learning Arrays]] 7: [[Alien Learning Arrays]]
8: [[Alien Surgery]] 8: [[Alien Implanter]] 8: [[Alien Implanter]]
9: [[Examination Room]] 9: [[Examination Room (TFTD)|Examination Room]] 9: "Unknown9"
10: [[Alien Alloys]] 10: [[Aqua Plastics]] 10: [[Aqua Plastics]]
11: [[Alien Habitat]] 11: [[Alien Re-animation Zone]] 11: [[Examination Room (TFTD)|Examination Room]]
12: Dead Tile 12: Dead Tile 12: Dead Tile
13: Exit Point 13: Exit Point 13: Exit Point
14: Alien Brain 14: T'leth Power Cylinders 14: T'leth Power Cylinders

Notes:
* The images in the TFTD in-game UFOpedia do NOT match the tile-types you'll recover from the battlescape. For example, the [[Dreadnought]] has tiles which match the UFOpedia entries for the [[Magnetic Navigation]] systems - but they're really [[Alien Sub Construction]] units, or so your USO recovery team will tell you! Daishiva's [[MapView]] presents tiles according to the UFOpedia, hence the additional column.
* The "entry points" are where your troopers spawn at the start of the map. If you wish to safely abort, your solders must return to those tiles first.
* The "exit points" are where soldiers must be if you wish to proceed to the next stage of a [[Two Part Missions|two-part mission]] without killing all aliens (by aborting instead).
* The Brain and Power Cylinder tiles must be destroyed in the final mission, in order to win ''UFO:EU'' and ''TFTD'' respectively.
* In ''UFO:EU'', [[Alien Reproduction]] and [[Alien Habitat]] tiles never appear. [[Alien Reproduction]] tiles do have a UFOpedia entry that can be accessed by hacking those units into your stores, but [[Alien Habitat]] tiles do not.
* In ''TFTD'', [[Examination Room (TFTD)|Examination Room]] tiles never appear. They do have a UFOpedia entry that can be accessed by hacking those units into your stores, however. [[Alien Re-animation Zone]] tiles can be found naturally, but have no research entry.
|- valign="top"
!60
!0x3C
|Set to 1 for [[Base_Defence#Destruction_Of_Base_Facilities|some]] X-COM base tiles, 0 otherwise. At the end of the battle, the game tallies up the amount of these existing within each "module" of the base (the results are stored in [[MISSION2.DAT]], offsets 80-151) - if the end result for any given module is 0, [[Base_Defence#Destruction_Of_Base_Facilities|it may be destroyed]].

If an alien patrols to a route node which has [[ROUTES.DAT#21|offset [21]]] flagged as anything other then 0, it will intentionally shoot at any tiles with ''this'' offset likewise flagged. If you're playing a CE version of UFO/TFTD the game will then crash immediately afterwards... either way, best not to let them go up the stairs to where these objects can be found. ;)
|- valign="top"
!61
!0x3D
|Unused. Almost half (560 of 1317) MCD records have widely varying values here, from 1 to 255 with no apparent pattern or preferred value. The remaining MCD records are 0. Called "VPs" by the game, this was supposed to be a victory point value for recovery/destruction. Doubt it's actually used, but needs to be tested.
|-
|}

==List of MCD Files==
Here are the MCD files in Enemy Unknown and Terror From The Deep along with a list of the number of records in each one. Refer to [[TERRAIN]] for more info on their usage in-game (load orders etc):
<table cellpadding="10">
<tr><td valign="top">
<table {{StdCenterTable}} class="sortable">
<caption>X-COM MCD Files</caption>
<tr {{StdDescTable_Heading}}><th width="100" align="left">File</th><th>Terrain</th><th>Records</th></tr>
<tr><td align="left">avenger</td><td>Avenger</td><td>59</td></tr>
<tr><td align="left">barn</td><td>Farm</td><td>29</td></tr>
<tr><td align="left">blanks</td><td>All</td><td>2</td></tr>
<tr><td align="left">brain</td><td>Alien Base</td><td>4</td></tr>
<tr><td align="left">cultivat</td><td>Farm</td><td>37</td></tr>
<tr><td align="left">desert</td><td>Desert</td><td>66</td></tr>
<tr><td align="left">forest</td><td>Forest</td><td>83</td></tr>
<tr><td align="left">frniture</td><td>City</td><td>26</td></tr>
<tr><td align="left">jungle</td><td>Jungle</td><td>82</td></tr>
<tr><td align="left">lightnin</td><td>Lightning</td><td>42</td></tr>
<tr><td align="left">mars</td><td>Cydonia</td><td>36</td></tr>
<tr><td align="left">mount</td><td>Mountain</td><td>78</td></tr>
<tr><td align="left">plane</td><td>Skyranger</td><td>65</td></tr>
<tr><td align="left">polar</td><td>Polar</td><td>81</td></tr>
<tr><td align="left">roads</td><td>City</td><td>23</td></tr>
<tr><td align="left">ufo1</td><td>Small Scout</td><td>20</td></tr>
<tr><td align="left">urban</td><td>City</td><td>112</td></tr>
<tr><td align="left">urbits</td><td>City</td><td>25</td></tr>
<tr><td align="left">u_base</td><td>Alien Base</td><td>67</td></tr>
<tr><td align="left">u_bits</td><td>UFOs</td><td>8</td></tr>
<tr><td align="left">u_disec2</td><td>UFOs</td><td>17</td></tr>
<tr><td align="left">u_ext02</td><td>UFOs</td><td>34</td></tr>
<tr><td align="left">u_oper2</td><td>UFOs</td><td>15</td></tr>
<tr><td align="left">u_pods</td><td>UFO/Alien Base</td><td>11</td></tr>
<tr><td align="left">u_wall02</td><td>UFO/Alien Base/Cydonia</td><td>47</td></tr>
<tr><td align="left">xbase1</td><td>X-COM Base</td><td>97</td></tr>
<tr><td align="left">xbase2</td><td>X-COM Base</td><td>62</td></tr></table>
</td>
<td>
<table {{StdCenterTable}} class="sortable">
<caption>TFTD MCD Files</caption>
<tr {{StdDescTable_Heading}}><th width="100" align="left">File</th><th>Terrain</th><th>Records</th></tr>
<tr><td align="left">asunk</td><td>Sunken Galleon</td><td>50</td></tr>
<tr><td align="left">atlantis</td><td>Atlantis</td><td>77</td></tr>
<tr><td align="left">barracud</td><td>Barracuda</td><td>46</td></tr>
<tr><td align="left">blanks</td><td>All</td><td>2</td></tr>
<tr><td align="left">cargo1</td><td>Cargo Ship</td><td>103</td></tr>
<tr><td align="left">cargo2</td><td>Cargo Ship</td><td>13</td></tr>
<tr><td align="left">cargo3</td><td>Cargo Ship</td><td>6</td></tr>
<tr><td align="left">coral</td><td>Coral</td><td>28</td></tr>
<tr><td align="left">crypt1</td><td>Crypt</td><td>45</td></tr>
<tr><td align="left">crypt2</td><td>Crypt</td><td>49</td></tr>
<tr><td align="left">crypt3</td><td>Crypt</td><td>12</td></tr>
<tr><td align="left">crypt4</td><td>Crypt</td><td>7</td></tr>
<tr><td align="left">debris</td><td>Seabed</td><td>50</td></tr>
<tr><td align="left">deckc</td><td>Liner Ship (Top)</td><td>18</td></tr>
<tr><td align="left">entry</td><td>Entry</td><td>12</td></tr>
<tr><td align="left">grunge1</td><td>Artifact Site</td><td>38</td></tr>
<tr><td align="left">grunge2</td><td>Artifact Site</td><td>8</td></tr>
<tr><td align="left">grunge3</td><td>Artifact Site</td><td>10</td></tr>
<tr><td align="left">grunge4</td><td>Artifact Site</td><td>37</td></tr>
<tr><td align="left">hammer</td><td>Hammerhead</td><td>44</td></tr>
<tr><td align="left">island1</td><td>Island</td><td>50</td></tr>
<tr><td align="left">island2</td><td>Island</td><td>50</td></tr>
<tr><td align="left">island3</td><td>Island</td><td>35</td></tr>
<tr><td align="left">leviath</td><td>Leviathan</td><td>47</td></tr>
<tr><td align="left">linera</td><td>Liner Ship</td><td>99</td></tr>
<tr><td align="left">linerb</td><td>Liner Ship</td><td>24</td></tr>
<tr><td align="left">linerc</td><td>Liner Ship</td><td>40</td></tr>
<tr><td align="left">linerd</td><td>Liner Ship</td><td>23</td></tr>
<tr><td align="left">manta</td><td>Manta</td><td>44</td></tr>
<tr><td align="left">msunk1</td><td>Sunken Ship</td><td>50</td></tr>
<tr><td align="left">msunk2</td><td>Sunken Ship</td><td>29</td></tr>
<tr><td align="left">mu</td><td>Mu</td><td>80</td></tr>
<tr><td align="left">organic1</td><td>Alien Base/Level/Entry</td><td>96</td></tr>
<tr><td align="left">organic2</td><td>Alien Base/Level</td><td>10</td></tr>
<tr><td align="left">organic3</td><td>Alien Base/Level</td><td>4</td></tr>
<tr><td align="left">pipes</td><td>Pipes</td><td>55</td></tr>
<tr><td align="left">planes</td><td>Sunken Plane</td><td>79</td></tr>
<tr><td align="left">port01</td><td>Port</td><td>95</td></tr>
<tr><td align="left">port02</td><td>Port</td><td>78</td></tr>
<tr><td align="left">psynom</td><td>Alien Base/Level</td><td>2</td></tr>
<tr><td align="left">pyramid</td><td>Artifact</td><td>24</td></tr>
<tr><td align="left">rocks</td><td>Artifact/Seabed/Galleon</td><td>15</td></tr>
<tr><td align="left">sand</td><td>several</td><td>20</td></tr>
<tr><td align="left">sea</td><td>several</td><td>18</td></tr>
<tr><td align="left">triton</td><td>Triton</td><td>46</td></tr>
<tr><td align="left">uext1</td><td>?</td><td>4</td></tr>
<tr><td align="left">uext2</td><td>USO/Entry</td><td>9</td></tr>
<tr><td align="left">uext3</td><td>USO/Entry</td><td>25</td></tr>
<tr><td align="left">ufobits</td><td>several</td><td>5</td></tr>
<tr><td align="left">uint1</td><td>USO</td><td>41</td></tr>
<tr><td align="left">uint2</td><td>USO</td><td>11</td></tr>
<tr><td align="left">uint3</td><td>USO</td><td>14</td></tr>
<tr><td align="left">volc</td><td>Volcanic</td><td>80</td></tr>
<tr><td align="left">weeds</td><td>Artifact/Coral/Seabed</td><td>10</td></tr>
<tr><td align="left">xbases1</td><td>X-COM Base</td><td>87</td></tr>
<tr><td align="left">xbases2</td><td>X-COM Base</td><td>42</td></tr>
<tr><td align="left">xbases3</td><td>X-COM Base</td><td>37</td></tr>
<tr><td align="left">xbases4</td><td>X-COM Base</td><td>43</td></tr>
<tr><td align="left">xbases5</td><td>X-COM Base</td><td>42</td></tr>
<tr><td align="left">xbits</td><td>Cargo Ship</td><td>39</td></tr></table>
</td></tr></table>

==Additional Information==

===MikeTheRed's MCD Database===
An Access 2000 copy of all MCD data is [[Media:XcomMCD.zip|here]]. It's from X-COM DOS 1.4, but AFAIK, all X-COM versions use the same data (even down to the buggy [[Explosions#Mile-High_Madness|Mile-High Madness]] MCD record). You will need to use this wiki page to understand it; I did not name the fields. They're just called by their offset address (see above). This Access database can be readily exported to Excel if you want. Or contact me. There are also a few files giving overall stats; the "Exclude" field for tblFileTypes only means, I excluded them for most counts I've made. There are also a few queries that might or might not be helpful.

===BladeFireLight's MCD Info===
Another in-depth look at MCD (and more) can be found on [http://www.strategycore.co.uk/forums/lofiversion/index.php?t1468.html this] message by BladeFireLight. His post also contains a [http://www.HexWorkshop.com HexWorkshop] template for viewing MCD files in a logical manner.

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

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

===MapView===
DaiShiva has an excellent utility called [http://www.daishiva.com/phpBB2/generic.php?page=progLinks.shtml MapView] for viewing or editing maps. However, it does not allow editing of MCD terrain items per se, AFAIK; just moving/placement of them. Caution: You must install the extensive Microsoft .NET platform to use MapView; see DaiShiva's site.

===BombBloke's Hacked Desert Terrain===
[[User:Bomb Bloke|Bomb Bloke]] has a numerical (ground) tileset which makes weapon damage blast testing easy as pie. It also has a little applet that lets you edit MCD variables Armor [[#42|[42]]], HE Block [[#43|[43]]], and Explosion Strength [[#55|[55]]] (but not type, [[#55|[54]]]), and it includes all four types of terrain item. Find his hacked terrain
[http://www.strategycore.co.uk/forums/index.php?showtopic=746&st=195&# here] or bundled with a savegame [http://www.xcomufo.com/forums/index.php?showtopic=8701&st=114&# here]. To see a screencap of the tiles in action, see [http://www.xcomufo.com/forums/index.php?showtopic=8701&st=112&# this] message.

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

Talk:Main Page

2015-06-04T04:04:26Z

Zombie: /* XCOM2 */ Reply

'''Welcome To All Rookies'''

This is the place to talk/ask about general issues concerning the wiki and hopefully someone will answer/reply to them.

Specific game questions should be asked on the game's individual talk pages.

For new users, in order to reduce spam you'll need to register to be able to edit pages.

To start a new topic simply press the '''edit''' button above. Then place your <nowiki>==Topic Name==</nowiki> like it is written here.
* To add a line you can either type <nowiki>----</nowiki> or use the buttons that appear on the edit screen.
* If replying to an existing topic use colons '''<nowiki>:</nowiki>''' before your answer
* Don't forget to sign your posts in the talk pages by typing '''<nowiki>~~~~</nowiki>''' at the end.
* Finally when creating/editing wiki articles have a look at the [[Guidelines to writing articles|guidelines]] page.

That's it. Happy editing!
----

Old articles have been moved to [[Talk:Main Page/Archive]] for later perusal.

__TOC__

== New Main Page layout. ==

I'm working on a new Main Page layout. Found here: [http://www.ufopaedia.org/index.php?title=User:Kokkan/Main_Page]. So I was wondering if it would be possible to apply something like this ([http://www.mediawiki.org/wiki/Manual:FAQ#How_do_I_hide_the_main_page_title.3F])? Preferable (http://www.mediawiki.org/wiki/Extension:NoTitle) --[[User:Kokkan|Kokkan]] 16:34, 18 September 2012 (EDT)
:Looks good to me, just one thing: why is the OpenXcom logo displayed? [[User:Hobbes|Hobbes]] 09:11, 4 October 2012 (EDT)
:: That was just a aesthetic choice. =) --[[User:Kokkan|Kokkan]] 12:36, 4 October 2012 (EDT)
::: I see :) Well the thing is that it's that placing that logo there is going to bring a lot of attention to that project. My question was if that was intentional or not. [[User:Hobbes|Hobbes]] 12:43, 4 October 2012 (EDT)
:::: Kokkan, would it be possible to squeeze the 'featured article' on the corner below the 'UFOpaedia News' (probably enlarge the corner)? I like how the new design has a compact look to it and to me it would look better if the 'featured article' was integrated with the news sections. Or probably even switch its position and put it on top rather than the 'UFOpaedia news' [[User:Hobbes|Hobbes]] 12:57, 4 October 2012 (EDT)
::::: Right now it depends on the width of the browser and the content in the Featured Article. I might be able to set some auto-width on the XCOM New window. --[[User:Kokkan|Kokkan]] 09:11, 5 October 2012 (EDT)
:::::: I was wondering if it wouldn't be better to bring up the Enemy Unknown 2012 table as the first table, at least for some time after the game is released. With my current maximum resolution both tables still appear one over the other, and I think the UFO Defense table might need a little reorganization and after it is done both games go back to being side by side. Or any other ideas. [[User:Hobbes|Hobbes]] 20:15, 8 October 2012 (EDT)
::::::: What?! This layout should work with all resolutions down to 1280x720 without stacking items. So it should be fine on everything except the smallest ( <11" ) notepads and pads. --[[User:Kokkan|Kokkan]] 04:49, 9 October 2012 (EDT)
:::::::: My resolution on my monitor is 1280x1024 and both tables are stacked. [[User:Hobbes|Hobbes]] 05:00, 9 October 2012 (EDT)

Same issue here with the overlapping tables, and my screen's 1024 pixels wide. Doesn't look any better on the tablet. Quick solution: Break the table out and have it on top ala the original's old main table, and have the original follow immediately after.

A while back I had wanted to redesign the front page but had to shelve it (and then quickly forgot about it). That was to make the main page just contain the news and a list of box art for the various games that point the users to separate main pages for the different titles, allowing the main tables for each title to be a bit more elaborate. Perhaps this might be a good time to resurrect that concept? [[User:NKF|NKF]] 07:15, 9 October 2012 (EDT)
:I'll place the EU 2012 table on top of the original game table (*sniff* *sniff*) for now until a permanent solution is found or the issue is fixed. I'm good with that solution or any other.
:Quick fix: I've moved it to the Featured section. [[User:Hobbes|Hobbes]] 08:03, 9 October 2012 (EDT)
----

:Hi folks, I think the partition to having the XCOM 2012 on its own main page is a really good one... now, folks can go to town on it, without having to keep touching the original fansite per se. But it is still kept close by having a highlighted announcement - Thanks for that, Kokkan! Some other comments:
[[File:X-COM UFOpaedia screen.jpg|100px|right|thumb|It's UFOpaedia]]
::*Do we need two "action" pictures at a time? Maybe we could have one, and use it to help balance the X-COM and the UFOpaedia news so that both "sides" of the news end at about the same place. For that matter, either side of the news could otherwise be tightened up, or expanded. But I wish they both ended at the same place so the main page looks more professional.
::*This is the time to make the standard for the new XCOM 2012 pages. Can I please ask that, for the URLs themselves, we not put parentheses around EU2012? I see it leading to a lot of hassle because ultimately there will be citations in citations in citations and other future complexities, including for other sites trying to cite us... parens just make everything more difficult and clunky. If you agree but say "but it'd be a hassle to fix it now", I say that's the wrong answer because it's about to explode (I'm sure!!!), so it's really now or never. Just append EU2012, without parens... everybody can figure out what it means. :)
::*I'm not sure just how/when it happened, but there's a lot of "Ufopaedia" on the main page. We use the original game as the convention setter, right? It's a minor thing, but still, we should have a convention, one way or the other. Does someone think it should be Ufopaedia?
::*To me, the brief OpenXcom logo nip slip (laugh) raises the issue that I wish we highlighted these efforts better... maybe they could use a little shout-out at the bottom of X-COM News section (just a very brief mention or link - little or no write-up), instead of the tiny section they now have, way at the bottom of the main UFOpaedia page.
:Again, the above points are minor... the big thing is the new place from EU2012 (great idea!). Thanks!! -[[User:MikeTheRed|MikeTheRed]] 14:24, 4 October 2012 (EDT)

:: We can set the hight at fixed values, but I really don't see a point to it. Since the size of the content will change. I prefer the parentheses in the naming, it clarifies what game the page relates to, and I don't see an extensive problem in linking to pages. Like ( [[Enemy_Unknown_(2012)|Enemy Unknown]]). On the UFOpaedia & OpenXcom logo, I fully agree. --[[User:Kokkan|Kokkan]] 09:11, 5 October 2012 (EDT)
::: One easy trick to link pages with the (EU2012) suffix is to open the top page on the category, which usually contains a list of all items related with that subject, press edit and then copy/paste the links. [[User:Hobbes|Hobbes]] 09:19, 5 October 2012 (EDT)

== XCOM Sidebar logo==
One possibility I thought of would be to replace the old logo/badge on the upper left corner of the wiki with the newer XCOM badge. Here's some options: 
[[File:Xcomnewlogo.png|100px|XCOM badge used ingame on the soldiers armor - I can't get a better pic than this one]]
[[File:Blue badge XCOM EU.png|100px|XCOM icon used on packing and ingame for menus, etc.]]
[[File:Xcom_eu_logo.jpg|100px|And there's also the game logo]] 

Anymore ideas? Which would be best? [[User:Hobbes|Hobbes]] 13:44, 4 October 2012 (EDT)

:The game logo is much cooler, while the insignias seem much more real-to-life. That said, I vote for cooler. The essence of the old X-COM was how scary cool it was. -[[User:MikeTheRed|MikeTheRed]] 14:33, 4 October 2012 (EDT)

:: I say keep the old X-logo, show the roots and lets not take over the entire wiki with EU2012. Use the new logos at appropriate EU2012 pages. --[[User:Kokkan|Kokkan]] 08:55, 5 October 2012 (EDT)

::: Not selling ourselves completely eh? ;) Well I just have to say I love the yellow and black insignia - that's probably the first XCOM logo/icon I really enjoy :) [[User:Hobbes|Hobbes]] 09:15, 5 October 2012 (EDT)

:Showing roots is good, too. The gold one does not seem as high-rez as the other... can we get it any better? -[[User:MikeTheRed|MikeTheRed]] 09:55, 5 October 2012 (EDT)

== Disambiguation of 1994 vs 2012 Entries ==

See for example the Sectoid entry, where a link to Sectoid (EU2012) has just been added as the first line of the entry. Are we going to do that for every entry that has the same name in 1994 as in 2012? That's a lot of minor edits someone will need to make! And putting these cross references under See Also would be less intrusive. But maybe a lot of enquiries from new site users are going to be related to EU 2012, and they will be confused if the cross reference is not clear and up-front. Let's agree a standard approach for this. As an alternative we could use disambiguation pages that show links to both the 1994 and the 2012 versions. Instead or as well, we could start moving 1994 pages by appending (EU1994) to the name. That's also quite a lot of work, but may be clearer in the long term. Even more work comes in if we were to use for example [[Sectoid]] as the disambiguation page, because that would mean rewriting all links to Sectoid in all the 1994 entries of the Ufopaedia. Thoughts everyone? [[User:Spike|Spike]] 03:56, 19 October 2012 (EDT)

On a related point - do we really need to append (EU2012) to every entry? I would think it's only necessary when the same term is used in both games. So it makes sense for Sectoid, but not so much sense for Gollop Chamber. I would suggest that for a term that is ''definitely'' unique to EU 2012, the (EU2012) suffix is not required. But there should always be an EU 2012 Category tag on the entry. [[User:Spike|Spike]] 06:28, 19 October 2012 (EDT)

: If we don't tag everything now, do we risk the same issue we're running into with UFO Defense? Also, the new Sectoid page has a space between EU and 2012. No other new page has that. My OCD is making me want to stab people. Is there a way to edit it to not have a space? As far as which way to go, I prefer disambiguation pages much like wikipedia does, but that typically requires tagging both. I would be happy to do the leg work and chase down all the 1994 ones but I don't like how EU1994 looks (especially since it says 1994 in the Games column to the left [sorry - fixed that - Spike] ) and I don't know how to update page names. --[[User:PixelOrange|PixelOrange]] 06:34, 19 October 2012 (EDT)

:: Yes, we do need to keep the games a part to not run into conflicting pages/links. Hence we suffix ALL pages on the NEW game ''(EU2012)''; this is the simplest and most clear way to do it. It does make it a bit of a hassle to link stuff yes. Even if some parts are unique, keep with the naming convention to keep it all as clear as possible. No, There is NO WAY we can do the same for the original game, there is just to much pages and links (and if we start and don't complete or something goes wrong, the wiki is in a fucked up state). So all pages on Enemy Unknown without the suffix refers to the original game. --[[User:Kokkan|Kokkan]] 07:12, 19 October 2012 (EDT)

:::So, if we're not going to retroactively update the old Enemy Unknown, redirects at the top of every page is my favorite choice (just as they do over at wikipedia). It gives you a quick link right at the top of the page, it's non-intrusive, and it's easy to implement across the board. --[[User:PixelOrange|PixelOrange]] 07:38, 19 October 2012 (EDT)
:::: OK but that's only going to be workable for the EU2012 pages, right? Any modification to all of the EU1994 pages is a big task, whether it's a disambiguation link at the top of the page, or a systematic rename to suffix "EU1994" on to the end of the page name - the workload is similar. I guess we could take a policy that says - anytime you create an EU2012 page, check to see if an EU1994 page of the same name exists. If so, add disambiguation links to the top of both pages. Or, for that matter, Move the EU1994 page by adding the suffix to its name. By the way, Move is how you rename a page, and the old name is preserved as a redirect to the new name. [[User:Spike|Spike]] 08:12, 19 October 2012 (EDT)

::::: I agree that disambiguation notices/links on top of pages probably is the best way to handle this (as in the [[Sectoid]] page). Moving and creating disambiguation pages is to much workload, and to have some (EU1994) pages and some without would be even more confusing. So I say no (EU1994) suffixes at all. --[[User:Kokkan|Kokkan]] 09:17, 19 October 2012 (EDT)

:::::: I don't think it's that cut and dried myself. Moving (renaming) the old pages is less workload than creating the disambiguation links. Also, adding the disambiguation links will disrupt the style / formatting of the existing EU 1994 pages which were not designed to have these links at the top, and which have had a lot of effort put into their layout over the years. Creating a disambiguation page with the "base" name, eg "Sectoid", the same name as the existing 1994 page, is a huge workload, because then all the links will break. Creating a new page called "Sectoid (disambiguation" and redirecting to it is not much better. A simple Move/rename will not break any links, meaning low workload - same as inserting a disambiguation link/notice. Keep in mind that the scope of the problem is only the pages for terms that exist in both games. "Sectoid (EU1994)" vs "Sectoid (EU2012)" is part of the required disambiguation workload. Heavy Cannon (unique to EU1994) vs Alloy Cannon (unique to EU2012) does not need to be part of the workload. It's a safe strategy to keep naming all new 2012 pages with the EU2012 suffix, but whatever method is selected does not need to be applied to all pages in both games. For example, we do not label all TFTD pages with (TFTD). We don't say "Tentaculat (TFTD)" and "Chrysallid (EU)". We do say "Zombie (TFTD)" and "Zombie (EU)" (even though the differences are only cosmetic). [[User:Spike|Spike]] 09:51, 19 October 2012 (EDT)

::::::: We already had this discussion a while ago because of Apocalypse and the common elements of the series that extend to it and TFTD. I don't recall the discussion but you guys mentioned the main topics but the idea was to start using the suffixes, specially when creating new pages, and not to worry about the existing pages because of the workload involved. It's basically to avoid the mess of the original game's pages regarding naming and to help categorize identify pages.
::::::: This method makes linking a bit harder but it's a matter of using a few tricks (which I already use when linking on the original game), like open and edit the section page (Soldiers, Weapons, Alien Life Forms, etc.) and just copy/paste the links you need. That's also why the section pages usually consist of lists of items.
::::::: Finally me and Spike can delete, move and rename pages, as an administrators so just let us know what you need :) [[User:Hobbes|Hobbes]] 11:09, 19 October 2012 (EDT)

:::::::: I've been thinking about the effects these new XCOM games (EU 2012 and the upcoming FPS) may have on the future of the series. If XCOM sees more games even further in the future that involve the aliens from the original, I don't think links at the top of the page is going to do the trick. We should make disimbaguation pages now to pave the way for recurring aliens and items that may make an appearance in any potential future installments. Just a thought!--[[User:SuicidalSectoid|SuicidalSectoid]] 21:26, 19 October 2012 (EDT)

Another option that I've been thinking over is asking Pete if he could set up a separate Wiki for the modern title(s) and keep this one for the classic titles. It would keep things tidy, and there's actually little crossover or common material between the new and old apart for historical and ancestry referential purposes. [[User:NKF|NKF]] 21:46, 19 October 2012 (EDT)

:: Personally I think all games of the series, old or new, should be all united in a single wiki. It helps this one grow, instead of just running out of material. It also shows how the series began and progressed to become what it is today. It helps people who are new to the series find older games in the series far easier and learn all their quirks and strategies. Of course there is what I mentioned above to consider, if this series really has been revived, then more games in the series may emerge and the new wiki could end up being "untidy".--[[User:SuicidalSectoid|SuicidalSectoid]] 10:54, 20 October 2012 (EDT)

== Pretty Colours ==

You know what'd be cool? Different page themes depending on the game. Say for example, yellow for TFTD, red for Apocalypse, black / dark grey for XCOM, and so on. Or maybe even custom wallpaper for each title - nothing overly eye-catching, just an easy way to differentiate what you're looking at with a glance.

We'd need an extension to do it (I've already got my eye on [http://www.mediawiki.org/wiki/Extension%3aPageCSS a simple looking one]), but before I bug Pete about it, what say ye all? The way I see it, we'd need to make one template page per "theme" - but then we'd need to edit just about every page on the wiki to implement them...

-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 02:59, 18 January 2013 (EST)

: I wanted to do something similar many years ago when I started making the navbars so that when people went to a page, they'd go "oh, this is EU or TFTD" just by the colours. Didn't get received very well if I remember correctly. But, with todays better versions of wiki software and scripts, why not? Go for it I say. -[[User:NKF|NKF]] 17:47, 18 January 2013 (EST)
: I think that's a wonderful idea, the issue is to pick a good color design that retains readability. [[User:Hobbes|Hobbes]] 18:30, 18 January 2013 (EST)
:Great Idea! I second what Hobbes is saying about readability. If you can't read what's on the page there's no point to new colours.--[[User:SuicidalSectoid|SuicidalSectoid]] 17:45, 25 March 2013 (EDT)

<nowiki>{{StyleTest01}}</nowiki>So, yeah, I did bug Pete, and not long after he delivered: We've had the plugin online a while now...

Anyway, this afternoon I sat down and plugged some stuff into it. It works much like I hoped (though unfortunately it doesn't have much control over images - can't set them as background for eg). Adding the tag ''<nowiki>{{StyleTest01}}</nowiki>'' to a page and saving it (or, perhaps for now, previewing it - though I've applied it to THIS page for now) applies the effects within that template.

That one's just an experiment, might be a little garish maybe (I basically grabbed colour codes out of screenshots from EU2012; I won't call myself an artist), and doesn't yet override every wiki element that needs to be handled - but I reckon it's a decent start. :)

-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 03:47, 21 April 2013 (EDT)
:I like it. [[User:Leman Russ|Leman Russ]] 04:05, 21 April 2013 (EDT) ''Thanks! -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 06:41, 21 April 2013 (EDT)''
:Nice, I like trying to replicate but the colors sure need some testing. One thing I'm wondering: is it possible to use the font used in EU2012 (it seems to be Century Gothic)? Another suggestion I'd make is to replace the XCOM logo on the top left with the new one.
:I've applied the styling to the page I'm currently working on: [[Class_Builds_(EU2012)]]. The main issue is the color of the links (dark blue isn't the best for contrast). Another thing needed would be to change the default colors used in the table templates to match the new style. [[User:Hobbes|Hobbes]] 04:36, 21 April 2013 (EDT)
::Apparently Century Gothic is not installed on most machines by default. It may be possible to load it on to the wiki somewhere and get viewers to download it as needed, but I really dunno. I'm guessing 'MS PGothic' is the best match that's widespread - I've tweaked the template to use that if Century Gothic isn't available, or to fall back to the wiki default if neither are on the viewer's machine.

::I did try switching the logo, but apparently the plugin doesn't allow it. Or the icon isn't accessible to CSS. Or I didn't know which element to tweak. What I've read specifically states I shouldn't be able to use the required "background-image" tag, but that's exactly what I needed to do to change the toolbar at the top of the page...

::I HAVE overridden the main 'wikitable' template, and there should be no blue links visible (except for ones leading off-site, I forgot about those)... In fact I'd go as far as to say the table looks great on that Class Builds page in particular (where the text matches the icons) - are you seeing what I'm seeing? [http://img.photobucket.com/albums/v213/BombBloke/StyleTest01_01_zps93e4e66e.jpg A screenshot may be in order]? I'm a little worried about browser compatibility in regards to my CSS overriding that which is already in the wiki site files.

::Depending on how I go for time I may deal with image thumbnails, the category bar, table of contents etc tonight.

::Please feel free to experiment if you feel so inclined! Either make a new ''StyleTestXX'' page and copy/paste my starter version in, or go right ahead and modify mine! If you lack any tools on your system for colour code generation, [http://www.2createawebsite.com/build/hex-colors.html here's an online one].

::-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 06:41, 21 April 2013 (EDT)
:::On my laptop I see it like this, I think it's the same and it seems to be using Century Gothic: [[:File:style1.png|style1.png]] - [[User:Hobbes|Hobbes]]

::::Ah yes, that was a match of colours, though you're definitely using a different font (it's installed by Office, see).

::::Still not sure what you're meaning about the tables, but I've switched monitors and see what you're saying about the links. I think maybe yellowy? Dunno.

::::-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 09:50, 21 April 2013 (EDT)
:::::Yellow links look better than the previous ones. What I meant about the tables is that on the Class Builds the background color of each table is table while the page background is dark grey. I got Century Gothic installed (it's a free font IIRC), is it the one being used? [[User:Hobbes|Hobbes]] 11:20, 21 April 2013 (EDT)
::::::Er...

::::::The cells should have a black background, the header cells should be grey. This is what I intended, though if you're expecting something different (or have a different suggestion) I'm more then happy to try other styles.

::::::I'd say you're indeed using Century Gothic. If you check the "font-family" line in the template, the web browser reads it from left to right, and uses the first font specified that exists on the computer (so if it can't find one, it falls back to the next, and so on). Hence if you start removing fonts from the front of the list and previewing the page you can compare each one. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 19:11, 21 April 2013 (EDT)
:::::::There were a couple of white backgrounds on table but those seen to have disappeared. Century Gothic still looks the better (and it seems to be free) since it is the one (or really close) used in Enemy Unknown 2012. [[User:Hobbes|Hobbes]] 20:43, 21 April 2013 (EDT)
::::::::Best I can make out it should be possible to use an uploaded font no worries, though I'd need to bug Pete to actually get it on to the server.

::::::::In the meantime, bold tildes are pretty much rendered blobs under PGothic ('''~'''). They looking ok to you? -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 09:04, 22 April 2013 (EDT)
:::::::::This is what I see using it as a font [[:File:PSGothic.png]] [[User:Hobbes|Hobbes]] 17:37, 22 April 2013 (EDT)
:::::::::I'm trying the new Style in a few pages and it is looking great. What I'm starting to wonder is what will happen to the other pages (non-EU2012). With UFO, TFTD and Apoc it should be possible to replicate it (although I have quite a few doubts about TFTD's colors...). But what about the other pages not directly related to a game? [[User:Hobbes|Hobbes]] 17:55, 22 April 2013 (EDT)

::::::::::We can currently only skin pages we manually add the template link to. That means that certain pages (like recent changes or page history) ''can't'' be skinned, not unless the skin files are changed on the server side... Which'd be a lot harder then skinning through these templates is (lots of files to modify with no simple way of previewing the changes, unless someone sets up their own wiki to play with on a home computer).

::::::::::In short, for now we may just have to leave 'em. While it might currently seem a bit jarring with just a black skin and a white skin, I think it won't seem so bad once there's a few others floating around the place.

::::::::::In particular I was thinking of leaving talk pages unskinned regardless of what game they belong to (if only because most articles don't HAVE a talk page). -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 19:05, 22 April 2013 (EDT)
:::::::::::Please tell me you're not sticking to the green background when showing a page's changes... ;) [[User:Hobbes|Hobbes]] 14:01, 23 April 2013 (EDT)
::::::::::::Can't think of anything better for it myself. :|

::::::::::::You do mean the green background that goes against added lines, yes? The bit of code to tweak goes along the lines of:

:::::::::::: td.diff-addedline {
:::::::::::: background: #559E06;
:::::::::::: }

::::::::::::-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 09:11, 25 April 2013 (EDT)

Indent resetinator activated! I certainly hope this is a work in progress. It's very hard to read on my smartphone browser, and even on my laptop it's a real squint-fest. I'd probably recommend a slightly lighter dark background rather than having extreme darks or lights.

But that aside, we could ask Pete to implement a few snazzy skins that you can access from the appearance tab under your preferences screen. The skin will then apply to all the wiki pages with no specific skins assigned to them. Mind you, this change will only affect the individual accounts. [[User:NKF|NKF]] 02:36, 24 April 2013 (EDT)

:Yep, if I considered it done it'd have a rather more official looking name and I'd be slapping it onto pages left right and center. ;)

:I will say I can't see much room for improvement myself - I'm no graphic design artist. I'm more then happy to implement any mock-ups people show me if they're not interested in tweaking the colours themselves, though.

:-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 09:11, 25 April 2013 (EDT)
::Well, no one else suggested improvements, so I'm wondering if we should start using the new style on the EU2012 pages. [[User:Hobbes|Hobbes]] 10:52, 26 August 2013 (EDT)

::: I disagree with the use of individual styles over-riding the default one at special pages, it makes the wiki inconsistent and messy. If you are to add a new style to site, do it RIGHT and add it as a skin in the user preferences. --[[User:Kokkan|Kokkan]] 07:34, 6 September 2013 (EDT)
:::: I agree since I made a test the other day of the proposed EU2012 style and I wasn't satisfied with the results regarding readability - the colors make it too tiring to read. I have no idea of how to add skins though [[User:Hobbes|Hobbes]] 17:10, 6 September 2013 (EDT)

==The Bureau==
We better start thinking of adding a section for the game since it will be released next month. [[User:Hobbes|Hobbes]] 08:30, 17 July 2013 (EDT)
: And we have the starting page and table for the [[The Bureau: XCOM Declassified|The Bureau]] online, although it is completely bare for the moment. [[User:Hobbes|Hobbes]] 22:30, 22 July 2013 (EDT)

==UFO: Alien Invasion==
I am one of the developers of [http://ufoai.org UFO: Alien Invasion], an open-source game inspired by X-Com. Ufopaedia.org taught me how to not suck at the original X-Com years ago and I've always been grateful. I wondered if the maintainers of ufopaedia.org would be interested in adding support for our game. While we have our own development wiki where we could host strategy advice, I think there are several benefits to having a third-party strategy guide. Of course, the fact that our game undergoes rolling development will lead to extra maintenance work. But I think this could be limited by only providing data on the latest stable version (released once every year or two). I am willing to undertake the work to prepare the initial content for our upcoming stable release 2.5. --[[User:H-Hour|H-Hour]] 09:55, 26 August 2013 (EDT)
:Hi there. I'm one of the administrators and although I can't speak for the other admins or the site owner (Pete), I think that it would make sense to add UFO:AI to the Featured Projects section. I'll ask them if there's any objection on the UFOPaedia's [http://www.strategycore.co.uk/forums/UFOPaediaorg-f96.html| forum] at Strategycore and if they're good about it, I'll add the link to the wiki sidebar. Should the initial page be named [[UFO:AI]] or do you prefer something else? Also, the game needs a wiki suffix, to be used in the guide's individual pages name and for their category tags, as an example all XCOM: Enemy Unknown pages use <nowiki>(EU2012)</nowiki>. [[User:Hobbes|Hobbes]] 10:25, 26 August 2013 (EDT)
::That's great, Hobbes. UFO:AI is fine for both the main page name and as a page suffix. If you think it is better given our rolling development, we can include the version for clarity (UFOAI2.5). --[[User:H-Hour|H-Hour]] 10:44, 26 August 2013 (EDT)
:::Better to keep version out otherwise it might be confusing. I'm just going to wait a day or two to give the other admins time to read it. [[User:Hobbes|Hobbes]] 11:47, 26 August 2013 (EDT)
:I've just added UFO:AI to the Wiki Sidebar. Happy editing :) [[User:Hobbes|Hobbes]] 05:33, 28 August 2013 (EDT)
::Thanks Hobbes! I'll get to it soon. --[[User:H-Hour|H-Hour]] 11:08, 28 August 2013 (EDT)
:I've put up the initial table. Please let me know if there is anything that should be changed regarding the format or structure to ensure it complies with ufopaedia standards. --[[User:H-Hour|H-Hour]] 10:41, 29 August 2013 (EDT)
::We don't really have any standard for those tables, just use what you feel is more comfortable/logic :) [[User:Hobbes|Hobbes]] 11:25, 29 August 2013 (EDT)

== Extensions ==

Over on wikia ot is possible to put sub-pages into tabs so that when u click on one it has different info than the other. If we had them on here then we could split the main page into 2 different tabs with old X-COM on one and new XCOM on the other while leaving the news where it is and the spin off/based off titles below it.

Just an idea--[[User:Ditto51|Ditto51]] 04:08, 25 November 2013 (EST)
:Just checked to see how subpages work on Wikimedia but by default they're limited to the user and talk pages. Might be interesting to implement for specific game items that are changed between EU and EW (Chitin Plating, etc.). I'm still waiting for Pete to fix the login process though since we need to get rid of the spammers before anything else. [[User:Hobbes|Hobbes]] 06:56, 25 November 2013 (EST)

:: I've been spending some time browsing the Minecraft wiki recently, and a couple of convenient extensions like expanding/collapsing content would be nice to have here as well. It would handy for the EW content as per the discussion elsewhere. It would be worth forming a list of the extensions we could use (and a link to said extension on www.mediawiki.org if possible). Once the signup issue is sorted we could suggest them to Pete. -[[User:NKF|NKF]] 07:06, 25 November 2013 (EST)

:::The info about the subpage is here [http://www.mediawiki.org/wiki/Help:Subpages]. The other extension we were discussing before was spoilers [http://www.mediawiki.org/wiki/Extension:Spoilers]. We might as well ask this already for Pete so that he can set time for it. [[User:Hobbes|Hobbes]] 07:33, 25 November 2013 (EST)
::::Spoilers is now installed. Subpages are an interesting idea - essentially categorising the content better as you would on a normal website (if you were thinking of going /terror from the deep/aliens or something like that?). Since MediaWiki handles moved pages pretty sensibly (moves the page and its Talk page to the new location and points the old URL to the new page) there shouldn't be an issue with this. I would say that it's more of a library format then and it needs a few librarians to be in charge of the categorisation, but you guys seem to be doing a grand job of that anyway :) --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 08:33, 29 December 2013 (EST)

:::Found the tabs I was talking about [https://www.mediawiki.org/wiki/Tabber tabber] --[[User:Ditto51|Ditto51]] 08:37, 25 November 2013 (EST)
::::Tabber is now installed --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 08:33, 29 December 2013 (EST)
:::::I can't get this to work, even when I use the example coding on the mediawiki page.--[[User:Ditto51|Ditto51]] ([[User talk:Ditto51|talk]]) 18:01, 29 December 2013 (EST)
::::::My bad - was updating the wrong version of the settings file. The other extensions should now be avalable.

:::[http://www.mediawiki.org/wiki/Multiple_upload Multiple Upload], to make it easier to upload images multiple images.--[[User:Ditto51|Ditto51]] 10:48, 1 December 2013 (EST)
::::The author doesn't seem to be maintaining this which is a worry, plus the discussion page for it mentions security issues so I'm not going to bother with this one --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 08:33, 29 December 2013 (EST)
:::::Installed an extension called MsUpload instead - you can see a bar at the top of the editor where you can drop files, or click the up arrow on the toolbar. This adds files to the queue and you can click on the name to rename them before uploading them. It then provides links to insert them --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 09:41, 29 December 2013 (EST)

:::Seems like only MsUpload is installed based on [[Special:Version]]; doesn't seem to show any other mentioned extensions?--[[User:DracoGriffin|DracoGriffin]] ([[User talk:DracoGriffin|talk]]) 19:47, 29 December 2013 (EST)
::::My bad - was updating the wrong version of the settings file. The other extensions should now be avalable.
----

==Wiki Software Upgrade ==
The Wiki software has now been upgraded to version 1.22 (was 1.16) so a few things have changed cosmetically and functionally. Whilst I've tested things myself and they seem alright, you guys might spot some things I won't, so please let me know here if there are any issues. Now we're up to date, I can look at the extensions requested above :) --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 07:24, 29 December 2013 (EST)

Pete has asked in a [http://www.strategycore.co.uk/forums/topic/10805-wiki-software-key-features/ thread] on the Strategycore.co.uk forums for suggestions of new features to add during the wiki software upgrade. Please go there for the discussion or post here what features you think relevant for the UFOPaedia upgrade. [[User:Hobbes|Hobbes]] 08:42, 27 December 2013 (EST)

:That wasn't ''exactly'' what I was asking there - it was more "if there were an ideal WIKI software what would its main features be?". Though I suppose if there are other features that are required (aside from the obvious "better spam filtering") then I could see what's available after I've upgraded. Just so you all know, I've pencilled in 10am GMT tomorrow (see link for current time: http://wwp.greenwichmeantime.co.uk/time-zone/europe/uk/time/ ) to move UFOPaedia to the same server that StrategyCore now sits on. The move gives us more power to run the software and expand it and sees the end of recent server instability. I'll put up a message at the top of the site in a few minutes, but just so you all know what's going on and that there will be downtime for a few hours. Once you see the message disappear from the top of the screen, you'll be looking at the new server and can post again. Apologies for the short notice, but whilst it's quiet and I have time, I really need to do the move and get things more stable before attempting the upgrade. --[[User:Pete|Pete]] 14:39, 27 December 2013 (EST)

::Most embedded images no longer display properly with the update, barring for a brief period during page load, only to disappear after page fully loads. Tested in two browsers. [[User:Arrow Quivershaft|Arrow Quivershaft]] ([[User talk:Arrow Quivershaft|talk]]) 16:48, 29 December 2013 (EST)

:::Can you give me a few examples of pages where this happens? I know I caused a weird issue for a while earlier on if you had www. at the start of the web address, so make sure you don't have that in your address bar, but aside from that I can't think of anything that would cause that without seeing a page where it's happening. If you can link a page AND describe which images disappear on it I can investigate further. --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 17:54, 29 December 2013 (EST)

::Seems to be working fine now, thanks for the response! [[User:Arrow Quivershaft|Arrow Quivershaft]] ([[User talk:Arrow Quivershaft|talk]]) 19:50, 30 December 2013 (EST)

== Watchlist E-Mails ==

When I recieve E-Mails about edits on the EU2012 pages, it always take me to a new page because the bracket at the end is no included in the link for some reason
Eg. An E-Mail about Second Wave (EU2012) takes be to Second Wave (EU2012

--[[User:Ditto51|Ditto51]] 03:45, 28 November 2013 (EST)

== Simpler Main Page ==

[[File:Cleaner Homepage Idea.png|200px|thumb|left]] I know this is going to generate all sorts of responses - there are some people here being quite negative about the new games (the old ones aren't coming back, nor have they gone away though!) and since UFO and TFTD seem to get the most love of all of the original series of games this idea might not go down too well, but what do you think?

It is just an idea after all, but my train of thought was that (not intending to offend) the homepage is too busy. The links next to the intro text are a bit small, and then the game "contents" links are just way too far down the page for people to bother with so I thought perhaps something a bit more visible might be good, then lose EVERYTHING below the news. To my mind, the homepage should have your introduction, obvious links to the content people are searching for and then news - that's it. The contents further down the page are merely replicating what you get when you click on the game links anyway.

I have introduced an issue using the 1994 UK box cover at the beginning there, so might be best having it alternate between the two or be half and half somehow, but I suspect that's the least of the comments I'm going to get.

So why would I want to promote the other minor games? Well... they're incomplete. Obviously this is because people aren't contributing content, but I'm not sure it helps that the Games list on the left doesn't list them (I know ''why'' it doesn't, just pointing out that that will cause people to miss them).

Another thought I had was a simple graphic - half and half - for old and new and go to a page listing the old and new games, but can't think of a sensible graphic for that.

[[File:Analytics Content.gif|200px|thumb|left]]Something interesting to note is that since I fixed the tracking code for Google Analytics, it shows just how popular the new games are on this website.

: Once upon a time I had been toying with the idea of changing the main page into a very simple page with almost no content, but instead set it up as a launchpad to the various 'main pages' for the different games by way of the box covers as you have done. That never eventuated - partly forgotten as with many ambitious ideas on the wiki in favour of other more exciting things in the recent updates, and a major change like that would've been too much of a culture shock. But with all he new fangled extensions and other things the new software can do, perhaps a move back in that direction isn't a bad idea. It would be nice change to the traditional game intro screen at the top of the page. -[[User:NKF|NKF]] ([[User talk:NKF|talk]]) 08:07, 30 December 2013 (EST)
:Pete, I completely agree with your idea of dropping everything below the News since it's easier to simply use the left links and I doubt a lot of people bother to scroll down so much.
:Regarding the old vs. new games, one of the most telling graphs from Google Analytics is this one:
[[File:EU stats.png]]

The first increase in daily visits on January 2012 is when XCOM: Enemy Unknown was announced, the massive spike in November 2012 is when it was released. But what's even more interesting is that for the same period, the Apocalypse page was the 2nd most visited, UFO Defense the 3th and TFTD the 7th. There's no info for Enemy Unknown 2012 though (there must have been a problem with Analytics since it only started recording visits to the EU2012 pages last month - this might also explain why the visits decreased from November 2012 onwards since visits to the EU2012 were not recorded by Analytics). To me this means that the old games are still live and kicking but also that the new game brought again a big interest on the series. [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 08:23, 30 December 2013 (EST)

[[File:Homepage 2.jpeg|200px|thumb|left|]] [[File:UFOPaedia-Homepage-3.jpg|200px|thumb|left|]]I've been toying with some alternative graphics that are better than my original idea. There's a colour version, but it's a bit "full-on" on a predominantly black and white page, and a greyscale version that might work better. My thinking is that if they are both set to something like 49% width with the latter having 2% left padding, they will scale with the different screen sizes people will view it at. That sort of thing works a lot better in browsers nowadays. Any good? If they're both still a bit bold I could wash out the backgrounds a bit more (that or change the colour of UFOPaedia :D )

:Grey Scale looks better, but it looks like you forgot [[The Bureau: XCOM Declassified|The Bureau Case]] on the Reboot series image--[[User:Ditto51|Ditto51]] ([[User talk:Ditto51|talk]]) 08:44, 1 January 2014 (EST)
::I agree with Ditto51, Grey Scale looks better. [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 11:52, 4 January 2014 (EST)
 
==Long War at Featured Projects==
I've been having a discussion at the Nexusmods forums regarding the possibility of having a subwiki hosted at the UFOPaedia for the Enemy Unknown (2012)'s Long War mod. This is a mod that has been in development for the past two years and has been highly praised by gaming magazines and EU's developers and the [http://www.nexusmods.com/xcom/mods/88/? beta] for Long War 3 (compatible with Enemy Within) has just been released. Any comments? [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 20:15, 26 May 2014 (EDT)
:Hm, I'd certianly say it's a noteworthy mod (though it may be more due to the fact that, in this day and age, information simply travels faster and with greater acessability/ease, than say, the mods for the '94 game, but that's a different lecture), so I'd say yes, a sub-wiki under XCOM:EU/EW, not as sure as to has a separate sidebar/front page space (besides in the news section, and "yes we have no bannanas" perma-link)(if you understand a thing of what the hell I just said/usually say) like the offical releases (ie; like how EW isn't in the sidebar, just vanilla EU). Also, I don't even see a mod/hack page on the xcom.wikia, so that'd be another thing we'd have over them, heh heh~ --[[User:Xuncu|Xuncu]] ([[User talk:Xuncu|talk]]) 07:35, 27 May 2014 (EDT)
::Well I've just tried it the first time and downloading the latest beta. I had participated in a few discussions at Nexusmods regarding new features but I had never bothered playing (just another mod and it required a lot of user steps to install) since I had my hands more than full with EU/EW. All I can say is that this is as big as the Enemy Within DLC regarding new features and reworking of the existing ones, turning it into a different game and installation is much easier than before.
::So I'd definitely add this to the Featured Projects since it's as big as UFO2000 and OpenXcom and it is more comparable to them rather than EW. The reason why EW is not on the sidebar is because it would require its own separate table and either a lot of duplication of already existing pages or it would be a rather small table. Long War on the other hand reworks the Strategic Layer (air interceptions, panic system, AI), soldier classes/abilities, equipment, Research tree, and several aspects of combat so it will require specific pages to detail all those changes.
::To finish, I'd use the same rules for Long War as OpenXcom/UFO200: keep its pages completely separate from the EU2012 ones by using a (Long War) category and suffix; no links on EU/EW pages to Long War pages (to separate official games from fandom), and finally create a specific table for Long War, based on the current EU2012 table format. [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 09:19, 27 May 2014 (EDT)
==Wiki Etiquette and Word Choice==
You should probably change "COULD OF" to "COULD HAVE". Particularly since it's in bold. Unless you want everyone to notice your awful grasp of the language, of course. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 02:34, 19 September 2014 (EDT)
:Keep in mind that for several users English might not be their first language (myself included). Or that 'awful' can be understood to be as insulting as 'autistic' ;) [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 08:35, 19 September 2014 (EDT)
::Spanish is my first language. Feel free to edit my Bureau entries, 'Shroom.... Which is pretty much "all entries for The Bureau." Have fun! --[[User:Xuncu|Xuncu]] ([[User talk:Xuncu|talk]]) 17:27, 19 September 2014 (EDT)
:Hobbes: I have an awful grasp of French (significantly more awful, at that). Also, the reason I reacted to Connor wasn't that he'd insulted Xuncu, but that he did so using a slur that implicitly insulted others (including me). Compare, for instance, the reason people get angry if someone calls a miser a Jew; they're not angry because of the insult to the miser, but because of the insult to all Jews by equating them with misers. My autistic obsession with X-Com has produced useful pages on this wiki; Connor's slur denied that and implicitly told me to GTFO. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 18:42, 19 September 2014 (EDT)
::You have a right to feel insulted whenever someone says something that offends you, but the way you communicate it to the offender is your decision. I find it easier not to take these situations too personally because ignorance is far more common than malice :) [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 18:57, 19 September 2014 (EDT)
:The two blend together in the context of hate speech; while specific malice toward the group in question is not necessarily required, a generally xenophobic mindset and a willingness to stereotype with callous disregard for accuracy '''is''' present in basically all cases. Hate speech "by mistake" (ie, using slurs without intending to) is extremely rare and easily distinguishable from the intentional sort. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 21:17, 19 September 2014 (EDT)
::Wikis have one [http://www.example.com principle] (amongst others) to work: '''assume good faith on the part of its users'''. I've been [[Talk:Impossible_Difficulty_(EU2012)|called]] here 'pedantic' due to my obsession with detail and personally the term has a negative connotation to me but I chose to assume good faith and accept the feedback. Otherwise, if we take slight on every badly chosen word, then this really hurts collaboration, which is what wikis are all about. [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 08:50, 20 September 2014 (EDT)

==XCOM2==
Off to the madness we head out again. :)
First issue is what suffix to add to page names to help classify and identify their content: (TFTD) for Terror From the Deep, (EU2012) for Enemy Unknown, etc. Any suggestions? [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 22:34, 2 June 2015 (EDT)
:Like we've been doing up to this point. EU, TFTD, Apoc, Int?, EU2012 and now I assume XCOM2. If the name changes in the future, we'll have to adjust the suffix accordingly. Which reminds me, I wonder why we use EU2012 suffix instead of just XCOM?--[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 23:49, 2 June 2015 (EDT)
:: EU2012 is a bit clumsy, but it helps disambiguate it from the original game. XCOM for the reboot would probably have been too generic (a bit like Gunship!). On the other hand XCOM2 should work as a temporary suffix for the new game. Or ADVENT perhaps? [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 02:00, 3 June 2015 (EDT)
::: IIRC the discussion, the EU2012 suffix came from with distinguishing the original EU from the remake, while avoiding using of XCOM as a suffix (too generic). I've avoided using XCOM2 for this reason although there aren't other options at the moment. [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 07:43, 3 June 2015 (EDT)
::::Hmmm, well I have no trouble telling the original apart from the reboot because the original had the dash (e.g. X-COM). Granted, the dash wasn't there right from the start, but it did become the de facto standard by TFTD and remained that way in one form or another (the middot: X·COM was used for the logo a lot too). Likewise, I'll have no trouble differentiating between TFTD and XCOM2. Have no idea why others would get hung up on this, but whatever. --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 00:04, 4 June 2015 (EDT)

Talk:UFOGRAPH

2015-06-04T03:52:24Z

Zombie: /* MOC1.LBM */ Reply

How can I get all the graphic tiles? Can I download them here or is there a way I can extract them from my game? [[User:RedNifre|RedNifre]] 13:24, 10 May 2008 (PDT)

: You could try PCKView to extract the tiles. The [http://www.strategycore.co.uk/files/index.php?cid=43 Strategy Core file listings] should be of help there. -[[User:NKF|NKF]] 15:00, 10 May 2008 (PDT)

== MOC1.LBM ==

So is this '''really''' used for palette information by the game? From what I gather, it looks to just be an artifact that was packaged up by mistake by the devs. --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 00:18, 3 June 2015 (EDT)

: Amusingly, yes. It does hold the palette data. First I renamed it, and TACTICAL would keep hanging every time the game switched to it. Then I replaced it with TFTD's ISLAND1.LBM, and suddenly I had blue skinned men with red hair walking around on orange grass. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 02:29, 3 June 2015 (EDT)

::Thanks NKF, I updated the description to reflect this. Thinking back, I probably did test this out at one time but my memory isn't like it used to be. ;) --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 23:52, 3 June 2015 (EDT)

UFOGRAPH

2015-06-04T03:50:35Z

Zombie: /* LBM (Atari Graphics File) */ Whoopsie, I guess hanging and crashing are different.

Various graphics files for the battlescape.

==DAT==
{|class="wikitable"
! File
!Description
|-
|[[BGLOB.DAT]]
|Describes ambient light on map
|-
|[[DETBLOB.DAT]]
|Motion scanner "blips" and directional arrows
|-
|[[MEDIBITS.DAT]]
|Medi-Kit body parts
|-
|[[SPICONS.DAT]]
|Special icons
|}

==LBM (Atari Graphics File)==
[[File:MOC1.png|MOC1.LBM|thumb]]

{|class="wikitable"
!File
!Description
|-
| MOC1.LBM
| A partial jungle terrain graphic used for palette information. The game absolutely uses this, removing it causes the game to hang and supplying a different LBM will change the palette.
|}
 

==PCK==

{|class="wikitable"
!File
!Description
|-
|BIGOB_00.PCK to BIGOB_56.PCK
|Single image PCK files for inventory items. The indexes and pictures mimic the images in [[BIGOBS.PCK|UNITS\BIGOBS.PCK]] and are used only in the inventory screen.
|-
|[[CURSOR.PCK]]
|Animated cursor frames
|-
|[[DETBORD2.PCK]]
|Motion Scanner background
|-
|[[DETBORD.PCK]]
|Motion Scanner frame. Probably short for Detector Border
|-
|[[HIT.PCK]]
|Melee (HTH) attack hits
|-
|[[ICONS.PCK]]
|Battlescape icons
|-
|[[INTICON.PCK]]
|Interception icons
|-
|[[MEDIBORD.PCK]]
|Medi-Kit frame
|-
|[[SCANBORD.PCK]]
|Top-down map frame or Scanner Border
|-
|[[SMOKE.PCK]]
|Fire, Smoke, [[Rank]] Badges, and Weapon hits
|-
|[[UNIBORD.PCK]]
|Stat background
|-
|[[X1.PCK]]
|Explosions
|}

==SCR==
{|class="wikitable"
!File
!Description
|-
|[[TAC00.SCR]]
|Turn background
|-
|[[TAC01.SCR]]
|Inventory Screen Icons
|}

==SPK==
{|class=wikitable
!File
!Description
|-
|[[Inventory_Backgrounds|MAN_0F0.SPK to MAN_3.SPK]]
|"Paperdoll" inventory images
|}

==TAB==

{| class=wikitable
! File
! Description
|-
| CURSOR.TAB
|Cursor frames
|-
| HIT.TAB
|Melee (HTH) attack hits
|-
| INTICON.TAB
|Interception Icons
|-
| SMOKE.TAB
|Fire, Smoke, Rank Badges, and Weapon hits
|-
| X1.TAB
|Explosion
|}

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

UFOGRAPH

2015-06-04T03:49:23Z

Zombie: /* LBM (Atari Graphics File) */ Added breaking space.

Various graphics files for the battlescape.

==DAT==
{|class="wikitable"
! File
!Description
|-
|[[BGLOB.DAT]]
|Describes ambient light on map
|-
|[[DETBLOB.DAT]]
|Motion scanner "blips" and directional arrows
|-
|[[MEDIBITS.DAT]]
|Medi-Kit body parts
|-
|[[SPICONS.DAT]]
|Special icons
|}

==LBM (Atari Graphics File)==
[[File:MOC1.png|MOC1.LBM|thumb]]

{|class="wikitable"
!File
!Description
|-
| MOC1.LBM
| A partial jungle terrain graphic used for palette information. The game absolutely uses this, removing it causes the game to crash and supplying a different LBM will change the palette.
|}
 

==PCK==

{|class="wikitable"
!File
!Description
|-
|BIGOB_00.PCK to BIGOB_56.PCK
|Single image PCK files for inventory items. The indexes and pictures mimic the images in [[BIGOBS.PCK|UNITS\BIGOBS.PCK]] and are used only in the inventory screen.
|-
|[[CURSOR.PCK]]
|Animated cursor frames
|-
|[[DETBORD2.PCK]]
|Motion Scanner background
|-
|[[DETBORD.PCK]]
|Motion Scanner frame. Probably short for Detector Border
|-
|[[HIT.PCK]]
|Melee (HTH) attack hits
|-
|[[ICONS.PCK]]
|Battlescape icons
|-
|[[INTICON.PCK]]
|Interception icons
|-
|[[MEDIBORD.PCK]]
|Medi-Kit frame
|-
|[[SCANBORD.PCK]]
|Top-down map frame or Scanner Border
|-
|[[SMOKE.PCK]]
|Fire, Smoke, [[Rank]] Badges, and Weapon hits
|-
|[[UNIBORD.PCK]]
|Stat background
|-
|[[X1.PCK]]
|Explosions
|}

==SCR==
{|class="wikitable"
!File
!Description
|-
|[[TAC00.SCR]]
|Turn background
|-
|[[TAC01.SCR]]
|Inventory Screen Icons
|}

==SPK==
{|class=wikitable
!File
!Description
|-
|[[Inventory_Backgrounds|MAN_0F0.SPK to MAN_3.SPK]]
|"Paperdoll" inventory images
|}

==TAB==

{| class=wikitable
! File
! Description
|-
| CURSOR.TAB
|Cursor frames
|-
| HIT.TAB
|Melee (HTH) attack hits
|-
| INTICON.TAB
|Interception Icons
|-
| SMOKE.TAB
|Fire, Smoke, Rank Badges, and Weapon hits
|-
| X1.TAB
|Explosion
|}

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

UFOGRAPH

2015-06-04T03:48:34Z

Zombie: /* LBM (Atari Graphics File) */ Added more of a description.

Various graphics files for the battlescape.

==DAT==
{|class="wikitable"
! File
!Description
|-
|[[BGLOB.DAT]]
|Describes ambient light on map
|-
|[[DETBLOB.DAT]]
|Motion scanner "blips" and directional arrows
|-
|[[MEDIBITS.DAT]]
|Medi-Kit body parts
|-
|[[SPICONS.DAT]]
|Special icons
|}

==LBM (Atari Graphics File)==
[[File:MOC1.png|MOC1.LBM|thumb]]

{|class="wikitable"
!File
!Description
|-
| MOC1.LBM
| A partial jungle terrain graphic used for palette information. The game absolutely uses this, removing it causes the game to crash and supplying a different LBM will change the palette.
|}

==PCK==

{|class="wikitable"
!File
!Description
|-
|BIGOB_00.PCK to BIGOB_56.PCK
|Single image PCK files for inventory items. The indexes and pictures mimic the images in [[BIGOBS.PCK|UNITS\BIGOBS.PCK]] and are used only in the inventory screen.
|-
|[[CURSOR.PCK]]
|Animated cursor frames
|-
|[[DETBORD2.PCK]]
|Motion Scanner background
|-
|[[DETBORD.PCK]]
|Motion Scanner frame. Probably short for Detector Border
|-
|[[HIT.PCK]]
|Melee (HTH) attack hits
|-
|[[ICONS.PCK]]
|Battlescape icons
|-
|[[INTICON.PCK]]
|Interception icons
|-
|[[MEDIBORD.PCK]]
|Medi-Kit frame
|-
|[[SCANBORD.PCK]]
|Top-down map frame or Scanner Border
|-
|[[SMOKE.PCK]]
|Fire, Smoke, [[Rank]] Badges, and Weapon hits
|-
|[[UNIBORD.PCK]]
|Stat background
|-
|[[X1.PCK]]
|Explosions
|}

==SCR==
{|class="wikitable"
!File
!Description
|-
|[[TAC00.SCR]]
|Turn background
|-
|[[TAC01.SCR]]
|Inventory Screen Icons
|}

==SPK==
{|class=wikitable
!File
!Description
|-
|[[Inventory_Backgrounds|MAN_0F0.SPK to MAN_3.SPK]]
|"Paperdoll" inventory images
|}

==TAB==

{| class=wikitable
! File
! Description
|-
| CURSOR.TAB
|Cursor frames
|-
| HIT.TAB
|Melee (HTH) attack hits
|-
| INTICON.TAB
|Interception Icons
|-
| SMOKE.TAB
|Fire, Smoke, Rank Badges, and Weapon hits
|-
| X1.TAB
|Explosion
|}

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

Incendiary

2015-06-03T05:13:18Z

Zombie: /* Damage */ Added equation and example for probability of catching fire.

[[Image:Fire_ground.gif|Ground Fire Animation]] [[Image:Fire_unit.gif|Unit Fire Animation]]

'''[[Incendiary]]''' (IN) ammunition creates a large area of '''fire''' on the [[battlescape]] equal to its [[#Blast Diameter|blast diameter]]. Incendiary rounds will burn for two turns on non-flammable terrain. Flammable terrain will burn for longer, and the fire is likely to spread to any adjacent flammable tiles. Aliens and unarmored X-COM agents can catch fire as well.

Incendiary rounds do very little direct damage -- between 0 and 10 points per hit -- but continue to do damage every turn that a unit is in fire or on fire. Due to the "[[Known_Bugs#Funky_Fire|funky fire]]" bug, units in or on fire will also take damage every time an incendiary round goes of ''anywhere'' on the Battlescape.

== Source ==
Incendiary rounds are available for the following weapons:

*[[Auto-Cannon]]
*[[Heavy Cannon]]
*[[Rocket Launcher]]

Some tiles may already be on fire at the start of the mission if the [[UFO Crash Recovery|UFO crashed]].

== Blast Diameter ==

*Auto-Cannon incendiary rounds have a blast diameter of 5 tiles; note that the southern tip of the "diamond" will always be missing.
*Heavy Cannon incendiary rounds have a blast diameter of 7 tiles.
*Incendiary rockets have a blast diameter of 9 tiles.

X
X XXXXXXX
X XXXXX XXXXXXX
XXX XXXXX XXXXXXX
XXXXX XXXXXXX XXXXXXXXX
XXX XXXXX XXXXXXX
X XXXXX XXXXXXX
X XXXXXXX
X

AC-IN HC-IN RL-IN

==Smoke==
[[Image:Smoke1.gif]] [[Image:Smoke2.gif]] [[Image:Smoke3.gif]]
A burning fire can also be used as an impromptu smoke screen. No smoke appears immediately, but smoke will appear outside the edges of the fire, as the fire slowly spreads in subsequent turns. The smoke begins on the first turn after the turn the incendiary round is fired. The smoke will spread vertically (upwards) as well as laterally. Smoke can block [[Line_of_sight|line of sight]].

==Light==
[[File:FlarePattern.png|thumb|right|A single square of fire will illuminate the area within the grey line.]]
Fire not only damages aliens and obstacles hiding in dark corners of the map, but also illuminates the area for several turns. This is especially useful during [[Night Missions]].

Any tile on fire will provide illumination within a 9 tile radius. A large patch of fire will illuminate everything within 9 tiles of the outer edge of the fire. Curiously, aliens on fire do not provide illumination. Maybe they're [http://firecritic.com/2010/12/firefighters-guide-to-invisible-fire-otherwise-known-as-ethanol-fires/ made of ethanol] or something.

==Damage==
<div style="color:red;">Incendiary damage mechanics are not fully understood and are being re-investigated by [[User:Zombie|Zombie]]. The information below is part of the picture but not the completely accurate picture. Treat with caution! More discussion is on the [[Talk:Incendiary|Talk page]].</div>

* Brush and wood on fire will eventually be consumed, leaving a flat scorched-earth [[MCD|tile]].

* If a [[Zombie]] is killed by the explosive impact of any form of Incendiary munitions, the [[Chryssalid]] larva will be burnt up instead of hatching. However, Zombies have high [[Alien Stats|hit points]] and will have to be near death to be killed by an IN round, per se.

* UFO interiors and dropped items are fireproof, even if their owners aren't. Silverblade recommends combining this fact with the diagonal wall bug and an incendiary rocket to roast them in the shell.

* Damage caused by fire does not alter [[Morale]] level.

* '''All''' forms of manufactured X-COM armor will completely block the effects of fire -- including direct hits from incendiary rounds. Soldiers not wearing armor take [[Health]] damage.

* '''Soldiers wearing armour, if wounded, can die from spreading fire.''' Apparently if the damage the fire would inflict exceeds the soldier's remaining [[health]], the soldier will die. If the damage is not enough to kill the soldier that turn, no damage will be inflicted. This bug only applies to ''spreading'' fire, and will not affect a wounded soldier already standing in fire.

* Certain creatures take increased or decreased [[Damage#Damage_Modifiers|damage]] from incendiary rounds:
**More Vulnerable:
***170% - Reaper
**Less Vulnerable:
***80% - Chryssalid
***70% - Ethereal, Snakeman
***40% - Tanks/Hovertanks
*** 0% - Silacoid (rocks don't burn!)

* Initial "impact" damage from incendiary ammunition is either for no points (unit does not catch fire), or between 5-10 points (unit catches fire). Since the distribution is randomly chosen from the set [ 0, 5, 6, 7, 8, 9, 10 ] (seven values), the probability of remaining unharmed is 14% (1/7), while there is an 86% chance (6/7) a unit will take some damage. The average damage is 6.4.

* Units standing in a blaze (as opposed to being on fire themselves) will receive between 1-12 damage points, most likely determined by the flammability rating of their tile ([[MCD]] offset 45). The chance of catching fire is determined by an if-then statement: IF Random(100)<40*Damage Modifier/100 THEN Catch Fire. So for example, a normal unarmored soldier (with a damage modifier to IN=100) has a probability of catching fire of: Random(100)<40*100/100 = Random(100)<40 Which means that rookie will catch fire 40% of the time. From a previous 6000+ trial conducted by [[User:Zombie|Zombie]] soldiers have a 33% chance of catching fire. It's unknown why these numbers don't match, but it's possible the sample size was still too small.

* Once lit, units burn for a slightly random amount of time, taking 5-10 damage points each turn. (If units fall unconscious, they do not continue to burn.) Thus the average total damage is 21.5 points (3 x 7.5), but could be as high as 50. Compare that [[Alien Stats|alien health values]] range from 30 to 120... it can kill or seriously damage sectoids, floaters (if on ground!), and maybe snakes, but barely warms up mutons. Terrorists are hardly touched (but now you might have their attention). Unsurprisingly, the equation used to determine how long a unit will remain on fire depends on the damage modifier of the unit in question: MaxTime=5*Damage Modifier/100, Duration=Random(MaxTime). So for example, if a tank (damage modifier to IN=40) catches fire it will remain lit for MaxTime=5*40/100=2; Duration=Random(2) or 1-2 turns.

* Smoke does not snuff out units on fire.

* Ultimately, in comparison with other ammo types, incendiary ammo is both weak and slow. Most of the time you will want to use it for other purposes (light, blocking LOS, clearing areas) and consider any damage a plus. However, it can be particularly effective against sectoids - so have plenty of IN for your early-game missions. Barbecue spits are optional.

==Spreading==
Fires can spread one tile in every direction, in ideal conditions (such as wheat fields and haylofts). However, since [[Battlescape_Map_Generation|no map]] is a pure wheat field and many tile types are unlikely to burn, they eventually go out.

Unarmored soldiers can walk through fire unscathed, but don't be left standing on '''''or next to''''' a burning tile at the end of the turn. That's when the fire-spreading code runs. Incendiaries also restrict alien movement; they, too, try to avoid fire.

Explosives (any weapon with [[damage]] type [[Explosives|HE]]) can start fires, particularly in mountains (due to a [[Explosives#Mile-High_Madness|bug]]). Copious use of explosives on thick cover can flush out the enemy - but you have an [[Managing_the_Item_Limit|80-item limit]].

Explosives will not put out fires, per se. You can directly destroy tile flammability via [[Explosives#Tile_Characteristics|explosives]] so that areas can't burn (or stop burning), but it's tricky. (How accurate is your [[Throwing_Accuracy|throwing]]?) In theory, it's possible for your team to corral or even direct flames, but how many folks have tried this? Please put any good war stories along these lines on this page's Discussion.

==Quirks, Tips, And Tricks==
XCOM makes a brave attempt to model fire. However, there are some quirks:

*If a unit (alien or friendly) is on fire or standing in flames, an incendiary explosion ''anywhere else on the map'' will damage it, even if you just shoot an IN round at a random patch of ground.

*Friendly units standing in '''smoke''' will take '''STUN''' damage every time an incendiary round explodes, '''even if armored.''' Alien units are not affected (needs further testing).

*Aliens not facing you will not respond with reaction fire when hit (directly or indirectly) by an incendiary round (see [[Reaction fire triggers]]).

* Smoke and flames do not mix. Only one type may exist on a particular tile on a particular turn. To quickly smother a blaze simply drop a primed [[Smoke Grenade]] in the center. This is a fairly useful trick for unarmored soldiers who want to safely cross a blaze without waiting for it to burn out by itself. But remember, you can cross a blaze safely - just don't stop in or next to one.

*There is an upper limit to how many squares can be on fire or in smoke (400 squares total for both). Once you have a good sized blaze going (forest fire, anyone?) further incendiary rounds will seem to fizzle, because no more fire can be created. Impact damage will still be dealt and units can still be set on fire. Still, existing smoke-covered tiles can be turned into fire instead of smoke, and vice versa.

*The damage values listed in the [[UFOpaedia]] do not determine how powerful an incendiary round deals damage; it only determines how wide an area will be blanketed with flames. Fire is unlike other damage; it works at initial blast and then over time, as described above.

*Shots made with IN rounds never count as "hitting" for the purposes of firing accuracy [[experience]], but reaction shots are counted and can go towards better reaction stats.

*Incendiary rounds (and other forms of fire) do not damage valuable equipment/loot; even corpses will not burn.

[[Category:Enemy Unknown/UFO Defense]]

Talk:UFOGRAPH

2015-06-03T04:18:13Z

Zombie: /* MOC1.LBM */ new section

UFOGRAPH

2015-06-03T04:13:51Z

Zombie: /* TAB */ Added description.

Various graphics files for the battlescape.

==DAT==
{|class="wikitable"
! File
!Description
|-
|[[BGLOB.DAT]]
|Describes ambient light on map
|-
|[[DETBLOB.DAT]]
|Motion scanner "blips" and directional arrows
|-
|[[MEDIBITS.DAT]]
|Medi-Kit body parts
|-
|[[SPICONS.DAT]]
|Special icons
|}

==LBM (Atari Graphics File)==
[[File:MOC1.png|MOC1.LBM|thumb]]

{|class="wikitable"
!File
!Description
|-
| MOC1.LBM
| A partial jungle terrain graphic used for palette information
|}

==PCK==

{|class="wikitable"
!File
!Description
|-
|BIGOB_00.PCK to BIGOB_56.PCK
|Single image PCK files for inventory items. The indexes and pictures mimic the images in [[BIGOBS.PCK|UNITS\BIGOBS.PCK]] and are used only in the inventory screen.
|-
|[[CURSOR.PCK]]
|Animated cursor frames
|-
|[[DETBORD2.PCK]]
|Motion Scanner background
|-
|[[DETBORD.PCK]]
|Motion Scanner frame. Probably short for Detector Border
|-
|[[HIT.PCK]]
|Melee (HTH) attack hits
|-
|[[ICONS.PCK]]
|Battlescape icons
|-
|[[INTICON.PCK]]
|Interception icons
|-
|[[MEDIBORD.PCK]]
|Medi-Kit frame
|-
|[[SCANBORD.PCK]]
|Top-down map frame or Scanner Border
|-
|[[SMOKE.PCK]]
|Fire, Smoke, [[Rank]] Badges, and Weapon hits
|-
|[[UNIBORD.PCK]]
|Stat background
|-
|[[X1.PCK]]
|Explosions
|}

==SCR==
{|class="wikitable"
!File
!Description
|-
|[[TAC00.SCR]]
|Turn background
|-
|[[TAC01.SCR]]
|Inventory Screen Icons
|}

==SPK==
{|class=wikitable
!File
!Description
|-
|[[Inventory_Backgrounds|MAN_0F0.SPK to MAN_3.SPK]]
|"Paperdoll" inventory images
|}

==TAB==

{| class=wikitable
! File
! Description
|-
| CURSOR.TAB
|Cursor frames
|-
| HIT.TAB
|Melee (HTH) attack hits
|-
| INTICON.TAB
|Interception Icons
|-
| SMOKE.TAB
|Fire, Smoke, Rank Badges, and Weapon hits
|-
| X1.TAB
|Explosion
|}

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

UFOGRAPH

2015-06-03T04:12:25Z

Zombie: /* PCK */ Added description.

Various graphics files for the battlescape.

==DAT==
{|class="wikitable"
! File
!Description
|-
|[[BGLOB.DAT]]
|Describes ambient light on map
|-
|[[DETBLOB.DAT]]
|Motion scanner "blips" and directional arrows
|-
|[[MEDIBITS.DAT]]
|Medi-Kit body parts
|-
|[[SPICONS.DAT]]
|Special icons
|}

==LBM (Atari Graphics File)==
[[File:MOC1.png|MOC1.LBM|thumb]]

{|class="wikitable"
!File
!Description
|-
| MOC1.LBM
| A partial jungle terrain graphic used for palette information
|}

==PCK==

{|class="wikitable"
!File
!Description
|-
|BIGOB_00.PCK to BIGOB_56.PCK
|Single image PCK files for inventory items. The indexes and pictures mimic the images in [[BIGOBS.PCK|UNITS\BIGOBS.PCK]] and are used only in the inventory screen.
|-
|[[CURSOR.PCK]]
|Animated cursor frames
|-
|[[DETBORD2.PCK]]
|Motion Scanner background
|-
|[[DETBORD.PCK]]
|Motion Scanner frame. Probably short for Detector Border
|-
|[[HIT.PCK]]
|Melee (HTH) attack hits
|-
|[[ICONS.PCK]]
|Battlescape icons
|-
|[[INTICON.PCK]]
|Interception icons
|-
|[[MEDIBORD.PCK]]
|Medi-Kit frame
|-
|[[SCANBORD.PCK]]
|Top-down map frame or Scanner Border
|-
|[[SMOKE.PCK]]
|Fire, Smoke, [[Rank]] Badges, and Weapon hits
|-
|[[UNIBORD.PCK]]
|Stat background
|-
|[[X1.PCK]]
|Explosions
|}

==SCR==
{|class="wikitable"
!File
!Description
|-
|[[TAC00.SCR]]
|Turn background
|-
|[[TAC01.SCR]]
|Inventory Screen Icons
|}

==SPK==
{|class=wikitable
!File
!Description
|-
|[[Inventory_Backgrounds|MAN_0F0.SPK to MAN_3.SPK]]
|"Paperdoll" inventory images
|}

==TAB==

{| class=wikitable
! File
! Description
|-
| CURSOR.TAB
|Cursor frames
|-
| HIT.TAB
|
|-
| INTICON.TAB
|Interception Icons
|-
| SMOKE.TAB
|Fire, Smoke, Rank Badges, and Weapon Hits
|-
| X1.TAB
|Explosion
|}

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

Talk:Main Page

2015-06-03T03:52:11Z

Zombie: /* XCOM2 */

Talk:Main Page

2015-06-03T03:49:43Z

Zombie: /* XCOM2 */ Reply

'''Welcome To All Rookies'''

This is the place to talk/ask about general issues concerning the wiki and hopefully someone will answer/reply to them.

Specific game questions should be asked on the game's individual talk pages.

For new users, in order to reduce spam you'll need to register to be able to edit pages.

To start a new topic simply press the '''edit''' button above. Then place your <nowiki>==Topic Name==</nowiki> like it is written here.
* To add a line you can either type <nowiki>----</nowiki> or use the buttons that appear on the edit screen.
* If replying to an existing topic use colons '''<nowiki>:</nowiki>''' before your answer
* Don't forget to sign your posts in the talk pages by typing '''<nowiki>~~~~</nowiki>''' at the end.
* Finally when creating/editing wiki articles have a look at the [[Guidelines to writing articles|guidelines]] page.

That's it. Happy editing!
----

Old articles have been moved to [[Talk:Main Page/Archive]] for later perusal.

__TOC__

== New Main Page layout. ==

I'm working on a new Main Page layout. Found here: [http://www.ufopaedia.org/index.php?title=User:Kokkan/Main_Page]. So I was wondering if it would be possible to apply something like this ([http://www.mediawiki.org/wiki/Manual:FAQ#How_do_I_hide_the_main_page_title.3F])? Preferable (http://www.mediawiki.org/wiki/Extension:NoTitle) --[[User:Kokkan|Kokkan]] 16:34, 18 September 2012 (EDT)
:Looks good to me, just one thing: why is the OpenXcom logo displayed? [[User:Hobbes|Hobbes]] 09:11, 4 October 2012 (EDT)
:: That was just a aesthetic choice. =) --[[User:Kokkan|Kokkan]] 12:36, 4 October 2012 (EDT)
::: I see :) Well the thing is that it's that placing that logo there is going to bring a lot of attention to that project. My question was if that was intentional or not. [[User:Hobbes|Hobbes]] 12:43, 4 October 2012 (EDT)
:::: Kokkan, would it be possible to squeeze the 'featured article' on the corner below the 'UFOpaedia News' (probably enlarge the corner)? I like how the new design has a compact look to it and to me it would look better if the 'featured article' was integrated with the news sections. Or probably even switch its position and put it on top rather than the 'UFOpaedia news' [[User:Hobbes|Hobbes]] 12:57, 4 October 2012 (EDT)
::::: Right now it depends on the width of the browser and the content in the Featured Article. I might be able to set some auto-width on the XCOM New window. --[[User:Kokkan|Kokkan]] 09:11, 5 October 2012 (EDT)
:::::: I was wondering if it wouldn't be better to bring up the Enemy Unknown 2012 table as the first table, at least for some time after the game is released. With my current maximum resolution both tables still appear one over the other, and I think the UFO Defense table might need a little reorganization and after it is done both games go back to being side by side. Or any other ideas. [[User:Hobbes|Hobbes]] 20:15, 8 October 2012 (EDT)
::::::: What?! This layout should work with all resolutions down to 1280x720 without stacking items. So it should be fine on everything except the smallest ( <11" ) notepads and pads. --[[User:Kokkan|Kokkan]] 04:49, 9 October 2012 (EDT)
:::::::: My resolution on my monitor is 1280x1024 and both tables are stacked. [[User:Hobbes|Hobbes]] 05:00, 9 October 2012 (EDT)

Same issue here with the overlapping tables, and my screen's 1024 pixels wide. Doesn't look any better on the tablet. Quick solution: Break the table out and have it on top ala the original's old main table, and have the original follow immediately after.

A while back I had wanted to redesign the front page but had to shelve it (and then quickly forgot about it). That was to make the main page just contain the news and a list of box art for the various games that point the users to separate main pages for the different titles, allowing the main tables for each title to be a bit more elaborate. Perhaps this might be a good time to resurrect that concept? [[User:NKF|NKF]] 07:15, 9 October 2012 (EDT)
:I'll place the EU 2012 table on top of the original game table (*sniff* *sniff*) for now until a permanent solution is found or the issue is fixed. I'm good with that solution or any other.
:Quick fix: I've moved it to the Featured section. [[User:Hobbes|Hobbes]] 08:03, 9 October 2012 (EDT)
----

:Hi folks, I think the partition to having the XCOM 2012 on its own main page is a really good one... now, folks can go to town on it, without having to keep touching the original fansite per se. But it is still kept close by having a highlighted announcement - Thanks for that, Kokkan! Some other comments:
[[File:X-COM UFOpaedia screen.jpg|100px|right|thumb|It's UFOpaedia]]
::*Do we need two "action" pictures at a time? Maybe we could have one, and use it to help balance the X-COM and the UFOpaedia news so that both "sides" of the news end at about the same place. For that matter, either side of the news could otherwise be tightened up, or expanded. But I wish they both ended at the same place so the main page looks more professional.
::*This is the time to make the standard for the new XCOM 2012 pages. Can I please ask that, for the URLs themselves, we not put parentheses around EU2012? I see it leading to a lot of hassle because ultimately there will be citations in citations in citations and other future complexities, including for other sites trying to cite us... parens just make everything more difficult and clunky. If you agree but say "but it'd be a hassle to fix it now", I say that's the wrong answer because it's about to explode (I'm sure!!!), so it's really now or never. Just append EU2012, without parens... everybody can figure out what it means. :)
::*I'm not sure just how/when it happened, but there's a lot of "Ufopaedia" on the main page. We use the original game as the convention setter, right? It's a minor thing, but still, we should have a convention, one way or the other. Does someone think it should be Ufopaedia?
::*To me, the brief OpenXcom logo nip slip (laugh) raises the issue that I wish we highlighted these efforts better... maybe they could use a little shout-out at the bottom of X-COM News section (just a very brief mention or link - little or no write-up), instead of the tiny section they now have, way at the bottom of the main UFOpaedia page.
:Again, the above points are minor... the big thing is the new place from EU2012 (great idea!). Thanks!! -[[User:MikeTheRed|MikeTheRed]] 14:24, 4 October 2012 (EDT)

:: We can set the hight at fixed values, but I really don't see a point to it. Since the size of the content will change. I prefer the parentheses in the naming, it clarifies what game the page relates to, and I don't see an extensive problem in linking to pages. Like ( [[Enemy_Unknown_(2012)|Enemy Unknown]]). On the UFOpaedia & OpenXcom logo, I fully agree. --[[User:Kokkan|Kokkan]] 09:11, 5 October 2012 (EDT)
::: One easy trick to link pages with the (EU2012) suffix is to open the top page on the category, which usually contains a list of all items related with that subject, press edit and then copy/paste the links. [[User:Hobbes|Hobbes]] 09:19, 5 October 2012 (EDT)

== XCOM Sidebar logo==
One possibility I thought of would be to replace the old logo/badge on the upper left corner of the wiki with the newer XCOM badge. Here's some options: 
[[File:Xcomnewlogo.png|100px|XCOM badge used ingame on the soldiers armor - I can't get a better pic than this one]]
[[File:Blue badge XCOM EU.png|100px|XCOM icon used on packing and ingame for menus, etc.]]
[[File:Xcom_eu_logo.jpg|100px|And there's also the game logo]] 

Anymore ideas? Which would be best? [[User:Hobbes|Hobbes]] 13:44, 4 October 2012 (EDT)

:The game logo is much cooler, while the insignias seem much more real-to-life. That said, I vote for cooler. The essence of the old X-COM was how scary cool it was. -[[User:MikeTheRed|MikeTheRed]] 14:33, 4 October 2012 (EDT)

:: I say keep the old X-logo, show the roots and lets not take over the entire wiki with EU2012. Use the new logos at appropriate EU2012 pages. --[[User:Kokkan|Kokkan]] 08:55, 5 October 2012 (EDT)

::: Not selling ourselves completely eh? ;) Well I just have to say I love the yellow and black insignia - that's probably the first XCOM logo/icon I really enjoy :) [[User:Hobbes|Hobbes]] 09:15, 5 October 2012 (EDT)

:Showing roots is good, too. The gold one does not seem as high-rez as the other... can we get it any better? -[[User:MikeTheRed|MikeTheRed]] 09:55, 5 October 2012 (EDT)

== Disambiguation of 1994 vs 2012 Entries ==

See for example the Sectoid entry, where a link to Sectoid (EU2012) has just been added as the first line of the entry. Are we going to do that for every entry that has the same name in 1994 as in 2012? That's a lot of minor edits someone will need to make! And putting these cross references under See Also would be less intrusive. But maybe a lot of enquiries from new site users are going to be related to EU 2012, and they will be confused if the cross reference is not clear and up-front. Let's agree a standard approach for this. As an alternative we could use disambiguation pages that show links to both the 1994 and the 2012 versions. Instead or as well, we could start moving 1994 pages by appending (EU1994) to the name. That's also quite a lot of work, but may be clearer in the long term. Even more work comes in if we were to use for example [[Sectoid]] as the disambiguation page, because that would mean rewriting all links to Sectoid in all the 1994 entries of the Ufopaedia. Thoughts everyone? [[User:Spike|Spike]] 03:56, 19 October 2012 (EDT)

On a related point - do we really need to append (EU2012) to every entry? I would think it's only necessary when the same term is used in both games. So it makes sense for Sectoid, but not so much sense for Gollop Chamber. I would suggest that for a term that is ''definitely'' unique to EU 2012, the (EU2012) suffix is not required. But there should always be an EU 2012 Category tag on the entry. [[User:Spike|Spike]] 06:28, 19 October 2012 (EDT)

: If we don't tag everything now, do we risk the same issue we're running into with UFO Defense? Also, the new Sectoid page has a space between EU and 2012. No other new page has that. My OCD is making me want to stab people. Is there a way to edit it to not have a space? As far as which way to go, I prefer disambiguation pages much like wikipedia does, but that typically requires tagging both. I would be happy to do the leg work and chase down all the 1994 ones but I don't like how EU1994 looks (especially since it says 1994 in the Games column to the left [sorry - fixed that - Spike] ) and I don't know how to update page names. --[[User:PixelOrange|PixelOrange]] 06:34, 19 October 2012 (EDT)

:: Yes, we do need to keep the games a part to not run into conflicting pages/links. Hence we suffix ALL pages on the NEW game ''(EU2012)''; this is the simplest and most clear way to do it. It does make it a bit of a hassle to link stuff yes. Even if some parts are unique, keep with the naming convention to keep it all as clear as possible. No, There is NO WAY we can do the same for the original game, there is just to much pages and links (and if we start and don't complete or something goes wrong, the wiki is in a fucked up state). So all pages on Enemy Unknown without the suffix refers to the original game. --[[User:Kokkan|Kokkan]] 07:12, 19 October 2012 (EDT)

:::So, if we're not going to retroactively update the old Enemy Unknown, redirects at the top of every page is my favorite choice (just as they do over at wikipedia). It gives you a quick link right at the top of the page, it's non-intrusive, and it's easy to implement across the board. --[[User:PixelOrange|PixelOrange]] 07:38, 19 October 2012 (EDT)
:::: OK but that's only going to be workable for the EU2012 pages, right? Any modification to all of the EU1994 pages is a big task, whether it's a disambiguation link at the top of the page, or a systematic rename to suffix "EU1994" on to the end of the page name - the workload is similar. I guess we could take a policy that says - anytime you create an EU2012 page, check to see if an EU1994 page of the same name exists. If so, add disambiguation links to the top of both pages. Or, for that matter, Move the EU1994 page by adding the suffix to its name. By the way, Move is how you rename a page, and the old name is preserved as a redirect to the new name. [[User:Spike|Spike]] 08:12, 19 October 2012 (EDT)

::::: I agree that disambiguation notices/links on top of pages probably is the best way to handle this (as in the [[Sectoid]] page). Moving and creating disambiguation pages is to much workload, and to have some (EU1994) pages and some without would be even more confusing. So I say no (EU1994) suffixes at all. --[[User:Kokkan|Kokkan]] 09:17, 19 October 2012 (EDT)

:::::: I don't think it's that cut and dried myself. Moving (renaming) the old pages is less workload than creating the disambiguation links. Also, adding the disambiguation links will disrupt the style / formatting of the existing EU 1994 pages which were not designed to have these links at the top, and which have had a lot of effort put into their layout over the years. Creating a disambiguation page with the "base" name, eg "Sectoid", the same name as the existing 1994 page, is a huge workload, because then all the links will break. Creating a new page called "Sectoid (disambiguation" and redirecting to it is not much better. A simple Move/rename will not break any links, meaning low workload - same as inserting a disambiguation link/notice. Keep in mind that the scope of the problem is only the pages for terms that exist in both games. "Sectoid (EU1994)" vs "Sectoid (EU2012)" is part of the required disambiguation workload. Heavy Cannon (unique to EU1994) vs Alloy Cannon (unique to EU2012) does not need to be part of the workload. It's a safe strategy to keep naming all new 2012 pages with the EU2012 suffix, but whatever method is selected does not need to be applied to all pages in both games. For example, we do not label all TFTD pages with (TFTD). We don't say "Tentaculat (TFTD)" and "Chrysallid (EU)". We do say "Zombie (TFTD)" and "Zombie (EU)" (even though the differences are only cosmetic). [[User:Spike|Spike]] 09:51, 19 October 2012 (EDT)

::::::: We already had this discussion a while ago because of Apocalypse and the common elements of the series that extend to it and TFTD. I don't recall the discussion but you guys mentioned the main topics but the idea was to start using the suffixes, specially when creating new pages, and not to worry about the existing pages because of the workload involved. It's basically to avoid the mess of the original game's pages regarding naming and to help categorize identify pages.
::::::: This method makes linking a bit harder but it's a matter of using a few tricks (which I already use when linking on the original game), like open and edit the section page (Soldiers, Weapons, Alien Life Forms, etc.) and just copy/paste the links you need. That's also why the section pages usually consist of lists of items.
::::::: Finally me and Spike can delete, move and rename pages, as an administrators so just let us know what you need :) [[User:Hobbes|Hobbes]] 11:09, 19 October 2012 (EDT)

:::::::: I've been thinking about the effects these new XCOM games (EU 2012 and the upcoming FPS) may have on the future of the series. If XCOM sees more games even further in the future that involve the aliens from the original, I don't think links at the top of the page is going to do the trick. We should make disimbaguation pages now to pave the way for recurring aliens and items that may make an appearance in any potential future installments. Just a thought!--[[User:SuicidalSectoid|SuicidalSectoid]] 21:26, 19 October 2012 (EDT)

Another option that I've been thinking over is asking Pete if he could set up a separate Wiki for the modern title(s) and keep this one for the classic titles. It would keep things tidy, and there's actually little crossover or common material between the new and old apart for historical and ancestry referential purposes. [[User:NKF|NKF]] 21:46, 19 October 2012 (EDT)

:: Personally I think all games of the series, old or new, should be all united in a single wiki. It helps this one grow, instead of just running out of material. It also shows how the series began and progressed to become what it is today. It helps people who are new to the series find older games in the series far easier and learn all their quirks and strategies. Of course there is what I mentioned above to consider, if this series really has been revived, then more games in the series may emerge and the new wiki could end up being "untidy".--[[User:SuicidalSectoid|SuicidalSectoid]] 10:54, 20 October 2012 (EDT)

== Pretty Colours ==

You know what'd be cool? Different page themes depending on the game. Say for example, yellow for TFTD, red for Apocalypse, black / dark grey for XCOM, and so on. Or maybe even custom wallpaper for each title - nothing overly eye-catching, just an easy way to differentiate what you're looking at with a glance.

We'd need an extension to do it (I've already got my eye on [http://www.mediawiki.org/wiki/Extension%3aPageCSS a simple looking one]), but before I bug Pete about it, what say ye all? The way I see it, we'd need to make one template page per "theme" - but then we'd need to edit just about every page on the wiki to implement them...

-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 02:59, 18 January 2013 (EST)

: I wanted to do something similar many years ago when I started making the navbars so that when people went to a page, they'd go "oh, this is EU or TFTD" just by the colours. Didn't get received very well if I remember correctly. But, with todays better versions of wiki software and scripts, why not? Go for it I say. -[[User:NKF|NKF]] 17:47, 18 January 2013 (EST)
: I think that's a wonderful idea, the issue is to pick a good color design that retains readability. [[User:Hobbes|Hobbes]] 18:30, 18 January 2013 (EST)
:Great Idea! I second what Hobbes is saying about readability. If you can't read what's on the page there's no point to new colours.--[[User:SuicidalSectoid|SuicidalSectoid]] 17:45, 25 March 2013 (EDT)

<nowiki>{{StyleTest01}}</nowiki>So, yeah, I did bug Pete, and not long after he delivered: We've had the plugin online a while now...

Anyway, this afternoon I sat down and plugged some stuff into it. It works much like I hoped (though unfortunately it doesn't have much control over images - can't set them as background for eg). Adding the tag ''<nowiki>{{StyleTest01}}</nowiki>'' to a page and saving it (or, perhaps for now, previewing it - though I've applied it to THIS page for now) applies the effects within that template.

That one's just an experiment, might be a little garish maybe (I basically grabbed colour codes out of screenshots from EU2012; I won't call myself an artist), and doesn't yet override every wiki element that needs to be handled - but I reckon it's a decent start. :)

-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 03:47, 21 April 2013 (EDT)
:I like it. [[User:Leman Russ|Leman Russ]] 04:05, 21 April 2013 (EDT) ''Thanks! -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 06:41, 21 April 2013 (EDT)''
:Nice, I like trying to replicate but the colors sure need some testing. One thing I'm wondering: is it possible to use the font used in EU2012 (it seems to be Century Gothic)? Another suggestion I'd make is to replace the XCOM logo on the top left with the new one.
:I've applied the styling to the page I'm currently working on: [[Class_Builds_(EU2012)]]. The main issue is the color of the links (dark blue isn't the best for contrast). Another thing needed would be to change the default colors used in the table templates to match the new style. [[User:Hobbes|Hobbes]] 04:36, 21 April 2013 (EDT)
::Apparently Century Gothic is not installed on most machines by default. It may be possible to load it on to the wiki somewhere and get viewers to download it as needed, but I really dunno. I'm guessing 'MS PGothic' is the best match that's widespread - I've tweaked the template to use that if Century Gothic isn't available, or to fall back to the wiki default if neither are on the viewer's machine.

::I did try switching the logo, but apparently the plugin doesn't allow it. Or the icon isn't accessible to CSS. Or I didn't know which element to tweak. What I've read specifically states I shouldn't be able to use the required "background-image" tag, but that's exactly what I needed to do to change the toolbar at the top of the page...

::I HAVE overridden the main 'wikitable' template, and there should be no blue links visible (except for ones leading off-site, I forgot about those)... In fact I'd go as far as to say the table looks great on that Class Builds page in particular (where the text matches the icons) - are you seeing what I'm seeing? [http://img.photobucket.com/albums/v213/BombBloke/StyleTest01_01_zps93e4e66e.jpg A screenshot may be in order]? I'm a little worried about browser compatibility in regards to my CSS overriding that which is already in the wiki site files.

::Depending on how I go for time I may deal with image thumbnails, the category bar, table of contents etc tonight.

::Please feel free to experiment if you feel so inclined! Either make a new ''StyleTestXX'' page and copy/paste my starter version in, or go right ahead and modify mine! If you lack any tools on your system for colour code generation, [http://www.2createawebsite.com/build/hex-colors.html here's an online one].

::-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 06:41, 21 April 2013 (EDT)
:::On my laptop I see it like this, I think it's the same and it seems to be using Century Gothic: [[:File:style1.png|style1.png]] - [[User:Hobbes|Hobbes]]

::::Ah yes, that was a match of colours, though you're definitely using a different font (it's installed by Office, see).

::::Still not sure what you're meaning about the tables, but I've switched monitors and see what you're saying about the links. I think maybe yellowy? Dunno.

::::-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 09:50, 21 April 2013 (EDT)
:::::Yellow links look better than the previous ones. What I meant about the tables is that on the Class Builds the background color of each table is table while the page background is dark grey. I got Century Gothic installed (it's a free font IIRC), is it the one being used? [[User:Hobbes|Hobbes]] 11:20, 21 April 2013 (EDT)
::::::Er...

::::::The cells should have a black background, the header cells should be grey. This is what I intended, though if you're expecting something different (or have a different suggestion) I'm more then happy to try other styles.

::::::I'd say you're indeed using Century Gothic. If you check the "font-family" line in the template, the web browser reads it from left to right, and uses the first font specified that exists on the computer (so if it can't find one, it falls back to the next, and so on). Hence if you start removing fonts from the front of the list and previewing the page you can compare each one. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 19:11, 21 April 2013 (EDT)
:::::::There were a couple of white backgrounds on table but those seen to have disappeared. Century Gothic still looks the better (and it seems to be free) since it is the one (or really close) used in Enemy Unknown 2012. [[User:Hobbes|Hobbes]] 20:43, 21 April 2013 (EDT)
::::::::Best I can make out it should be possible to use an uploaded font no worries, though I'd need to bug Pete to actually get it on to the server.

::::::::In the meantime, bold tildes are pretty much rendered blobs under PGothic ('''~'''). They looking ok to you? -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 09:04, 22 April 2013 (EDT)
:::::::::This is what I see using it as a font [[:File:PSGothic.png]] [[User:Hobbes|Hobbes]] 17:37, 22 April 2013 (EDT)
:::::::::I'm trying the new Style in a few pages and it is looking great. What I'm starting to wonder is what will happen to the other pages (non-EU2012). With UFO, TFTD and Apoc it should be possible to replicate it (although I have quite a few doubts about TFTD's colors...). But what about the other pages not directly related to a game? [[User:Hobbes|Hobbes]] 17:55, 22 April 2013 (EDT)

::::::::::We can currently only skin pages we manually add the template link to. That means that certain pages (like recent changes or page history) ''can't'' be skinned, not unless the skin files are changed on the server side... Which'd be a lot harder then skinning through these templates is (lots of files to modify with no simple way of previewing the changes, unless someone sets up their own wiki to play with on a home computer).

::::::::::In short, for now we may just have to leave 'em. While it might currently seem a bit jarring with just a black skin and a white skin, I think it won't seem so bad once there's a few others floating around the place.

::::::::::In particular I was thinking of leaving talk pages unskinned regardless of what game they belong to (if only because most articles don't HAVE a talk page). -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 19:05, 22 April 2013 (EDT)
:::::::::::Please tell me you're not sticking to the green background when showing a page's changes... ;) [[User:Hobbes|Hobbes]] 14:01, 23 April 2013 (EDT)
::::::::::::Can't think of anything better for it myself. :|

::::::::::::You do mean the green background that goes against added lines, yes? The bit of code to tweak goes along the lines of:

:::::::::::: td.diff-addedline {
:::::::::::: background: #559E06;
:::::::::::: }

::::::::::::-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 09:11, 25 April 2013 (EDT)

Indent resetinator activated! I certainly hope this is a work in progress. It's very hard to read on my smartphone browser, and even on my laptop it's a real squint-fest. I'd probably recommend a slightly lighter dark background rather than having extreme darks or lights.

But that aside, we could ask Pete to implement a few snazzy skins that you can access from the appearance tab under your preferences screen. The skin will then apply to all the wiki pages with no specific skins assigned to them. Mind you, this change will only affect the individual accounts. [[User:NKF|NKF]] 02:36, 24 April 2013 (EDT)

:Yep, if I considered it done it'd have a rather more official looking name and I'd be slapping it onto pages left right and center. ;)

:I will say I can't see much room for improvement myself - I'm no graphic design artist. I'm more then happy to implement any mock-ups people show me if they're not interested in tweaking the colours themselves, though.

:-  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 09:11, 25 April 2013 (EDT)
::Well, no one else suggested improvements, so I'm wondering if we should start using the new style on the EU2012 pages. [[User:Hobbes|Hobbes]] 10:52, 26 August 2013 (EDT)

::: I disagree with the use of individual styles over-riding the default one at special pages, it makes the wiki inconsistent and messy. If you are to add a new style to site, do it RIGHT and add it as a skin in the user preferences. --[[User:Kokkan|Kokkan]] 07:34, 6 September 2013 (EDT)
:::: I agree since I made a test the other day of the proposed EU2012 style and I wasn't satisfied with the results regarding readability - the colors make it too tiring to read. I have no idea of how to add skins though [[User:Hobbes|Hobbes]] 17:10, 6 September 2013 (EDT)

==The Bureau==
We better start thinking of adding a section for the game since it will be released next month. [[User:Hobbes|Hobbes]] 08:30, 17 July 2013 (EDT)
: And we have the starting page and table for the [[The Bureau: XCOM Declassified|The Bureau]] online, although it is completely bare for the moment. [[User:Hobbes|Hobbes]] 22:30, 22 July 2013 (EDT)

==UFO: Alien Invasion==
I am one of the developers of [http://ufoai.org UFO: Alien Invasion], an open-source game inspired by X-Com. Ufopaedia.org taught me how to not suck at the original X-Com years ago and I've always been grateful. I wondered if the maintainers of ufopaedia.org would be interested in adding support for our game. While we have our own development wiki where we could host strategy advice, I think there are several benefits to having a third-party strategy guide. Of course, the fact that our game undergoes rolling development will lead to extra maintenance work. But I think this could be limited by only providing data on the latest stable version (released once every year or two). I am willing to undertake the work to prepare the initial content for our upcoming stable release 2.5. --[[User:H-Hour|H-Hour]] 09:55, 26 August 2013 (EDT)
:Hi there. I'm one of the administrators and although I can't speak for the other admins or the site owner (Pete), I think that it would make sense to add UFO:AI to the Featured Projects section. I'll ask them if there's any objection on the UFOPaedia's [http://www.strategycore.co.uk/forums/UFOPaediaorg-f96.html| forum] at Strategycore and if they're good about it, I'll add the link to the wiki sidebar. Should the initial page be named [[UFO:AI]] or do you prefer something else? Also, the game needs a wiki suffix, to be used in the guide's individual pages name and for their category tags, as an example all XCOM: Enemy Unknown pages use <nowiki>(EU2012)</nowiki>. [[User:Hobbes|Hobbes]] 10:25, 26 August 2013 (EDT)
::That's great, Hobbes. UFO:AI is fine for both the main page name and as a page suffix. If you think it is better given our rolling development, we can include the version for clarity (UFOAI2.5). --[[User:H-Hour|H-Hour]] 10:44, 26 August 2013 (EDT)
:::Better to keep version out otherwise it might be confusing. I'm just going to wait a day or two to give the other admins time to read it. [[User:Hobbes|Hobbes]] 11:47, 26 August 2013 (EDT)
:I've just added UFO:AI to the Wiki Sidebar. Happy editing :) [[User:Hobbes|Hobbes]] 05:33, 28 August 2013 (EDT)
::Thanks Hobbes! I'll get to it soon. --[[User:H-Hour|H-Hour]] 11:08, 28 August 2013 (EDT)
:I've put up the initial table. Please let me know if there is anything that should be changed regarding the format or structure to ensure it complies with ufopaedia standards. --[[User:H-Hour|H-Hour]] 10:41, 29 August 2013 (EDT)
::We don't really have any standard for those tables, just use what you feel is more comfortable/logic :) [[User:Hobbes|Hobbes]] 11:25, 29 August 2013 (EDT)

== Extensions ==

Over on wikia ot is possible to put sub-pages into tabs so that when u click on one it has different info than the other. If we had them on here then we could split the main page into 2 different tabs with old X-COM on one and new XCOM on the other while leaving the news where it is and the spin off/based off titles below it.

Just an idea--[[User:Ditto51|Ditto51]] 04:08, 25 November 2013 (EST)
:Just checked to see how subpages work on Wikimedia but by default they're limited to the user and talk pages. Might be interesting to implement for specific game items that are changed between EU and EW (Chitin Plating, etc.). I'm still waiting for Pete to fix the login process though since we need to get rid of the spammers before anything else. [[User:Hobbes|Hobbes]] 06:56, 25 November 2013 (EST)

:: I've been spending some time browsing the Minecraft wiki recently, and a couple of convenient extensions like expanding/collapsing content would be nice to have here as well. It would handy for the EW content as per the discussion elsewhere. It would be worth forming a list of the extensions we could use (and a link to said extension on www.mediawiki.org if possible). Once the signup issue is sorted we could suggest them to Pete. -[[User:NKF|NKF]] 07:06, 25 November 2013 (EST)

:::The info about the subpage is here [http://www.mediawiki.org/wiki/Help:Subpages]. The other extension we were discussing before was spoilers [http://www.mediawiki.org/wiki/Extension:Spoilers]. We might as well ask this already for Pete so that he can set time for it. [[User:Hobbes|Hobbes]] 07:33, 25 November 2013 (EST)
::::Spoilers is now installed. Subpages are an interesting idea - essentially categorising the content better as you would on a normal website (if you were thinking of going /terror from the deep/aliens or something like that?). Since MediaWiki handles moved pages pretty sensibly (moves the page and its Talk page to the new location and points the old URL to the new page) there shouldn't be an issue with this. I would say that it's more of a library format then and it needs a few librarians to be in charge of the categorisation, but you guys seem to be doing a grand job of that anyway :) --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 08:33, 29 December 2013 (EST)

:::Found the tabs I was talking about [https://www.mediawiki.org/wiki/Tabber tabber] --[[User:Ditto51|Ditto51]] 08:37, 25 November 2013 (EST)
::::Tabber is now installed --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 08:33, 29 December 2013 (EST)
:::::I can't get this to work, even when I use the example coding on the mediawiki page.--[[User:Ditto51|Ditto51]] ([[User talk:Ditto51|talk]]) 18:01, 29 December 2013 (EST)
::::::My bad - was updating the wrong version of the settings file. The other extensions should now be avalable.

:::[http://www.mediawiki.org/wiki/Multiple_upload Multiple Upload], to make it easier to upload images multiple images.--[[User:Ditto51|Ditto51]] 10:48, 1 December 2013 (EST)
::::The author doesn't seem to be maintaining this which is a worry, plus the discussion page for it mentions security issues so I'm not going to bother with this one --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 08:33, 29 December 2013 (EST)
:::::Installed an extension called MsUpload instead - you can see a bar at the top of the editor where you can drop files, or click the up arrow on the toolbar. This adds files to the queue and you can click on the name to rename them before uploading them. It then provides links to insert them --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 09:41, 29 December 2013 (EST)

:::Seems like only MsUpload is installed based on [[Special:Version]]; doesn't seem to show any other mentioned extensions?--[[User:DracoGriffin|DracoGriffin]] ([[User talk:DracoGriffin|talk]]) 19:47, 29 December 2013 (EST)
::::My bad - was updating the wrong version of the settings file. The other extensions should now be avalable.
----

==Wiki Software Upgrade ==
The Wiki software has now been upgraded to version 1.22 (was 1.16) so a few things have changed cosmetically and functionally. Whilst I've tested things myself and they seem alright, you guys might spot some things I won't, so please let me know here if there are any issues. Now we're up to date, I can look at the extensions requested above :) --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 07:24, 29 December 2013 (EST)

Pete has asked in a [http://www.strategycore.co.uk/forums/topic/10805-wiki-software-key-features/ thread] on the Strategycore.co.uk forums for suggestions of new features to add during the wiki software upgrade. Please go there for the discussion or post here what features you think relevant for the UFOPaedia upgrade. [[User:Hobbes|Hobbes]] 08:42, 27 December 2013 (EST)

:That wasn't ''exactly'' what I was asking there - it was more "if there were an ideal WIKI software what would its main features be?". Though I suppose if there are other features that are required (aside from the obvious "better spam filtering") then I could see what's available after I've upgraded. Just so you all know, I've pencilled in 10am GMT tomorrow (see link for current time: http://wwp.greenwichmeantime.co.uk/time-zone/europe/uk/time/ ) to move UFOPaedia to the same server that StrategyCore now sits on. The move gives us more power to run the software and expand it and sees the end of recent server instability. I'll put up a message at the top of the site in a few minutes, but just so you all know what's going on and that there will be downtime for a few hours. Once you see the message disappear from the top of the screen, you'll be looking at the new server and can post again. Apologies for the short notice, but whilst it's quiet and I have time, I really need to do the move and get things more stable before attempting the upgrade. --[[User:Pete|Pete]] 14:39, 27 December 2013 (EST)

::Most embedded images no longer display properly with the update, barring for a brief period during page load, only to disappear after page fully loads. Tested in two browsers. [[User:Arrow Quivershaft|Arrow Quivershaft]] ([[User talk:Arrow Quivershaft|talk]]) 16:48, 29 December 2013 (EST)

:::Can you give me a few examples of pages where this happens? I know I caused a weird issue for a while earlier on if you had www. at the start of the web address, so make sure you don't have that in your address bar, but aside from that I can't think of anything that would cause that without seeing a page where it's happening. If you can link a page AND describe which images disappear on it I can investigate further. --[[User:Pete|Pete]] ([[User talk:Pete|talk]]) 17:54, 29 December 2013 (EST)

::Seems to be working fine now, thanks for the response! [[User:Arrow Quivershaft|Arrow Quivershaft]] ([[User talk:Arrow Quivershaft|talk]]) 19:50, 30 December 2013 (EST)

== Watchlist E-Mails ==

When I recieve E-Mails about edits on the EU2012 pages, it always take me to a new page because the bracket at the end is no included in the link for some reason
Eg. An E-Mail about Second Wave (EU2012) takes be to Second Wave (EU2012

--[[User:Ditto51|Ditto51]] 03:45, 28 November 2013 (EST)

== Simpler Main Page ==

[[File:Cleaner Homepage Idea.png|200px|thumb|left]] I know this is going to generate all sorts of responses - there are some people here being quite negative about the new games (the old ones aren't coming back, nor have they gone away though!) and since UFO and TFTD seem to get the most love of all of the original series of games this idea might not go down too well, but what do you think?

It is just an idea after all, but my train of thought was that (not intending to offend) the homepage is too busy. The links next to the intro text are a bit small, and then the game "contents" links are just way too far down the page for people to bother with so I thought perhaps something a bit more visible might be good, then lose EVERYTHING below the news. To my mind, the homepage should have your introduction, obvious links to the content people are searching for and then news - that's it. The contents further down the page are merely replicating what you get when you click on the game links anyway.

I have introduced an issue using the 1994 UK box cover at the beginning there, so might be best having it alternate between the two or be half and half somehow, but I suspect that's the least of the comments I'm going to get.

So why would I want to promote the other minor games? Well... they're incomplete. Obviously this is because people aren't contributing content, but I'm not sure it helps that the Games list on the left doesn't list them (I know ''why'' it doesn't, just pointing out that that will cause people to miss them).

Another thought I had was a simple graphic - half and half - for old and new and go to a page listing the old and new games, but can't think of a sensible graphic for that.

[[File:Analytics Content.gif|200px|thumb|left]]Something interesting to note is that since I fixed the tracking code for Google Analytics, it shows just how popular the new games are on this website.

: Once upon a time I had been toying with the idea of changing the main page into a very simple page with almost no content, but instead set it up as a launchpad to the various 'main pages' for the different games by way of the box covers as you have done. That never eventuated - partly forgotten as with many ambitious ideas on the wiki in favour of other more exciting things in the recent updates, and a major change like that would've been too much of a culture shock. But with all he new fangled extensions and other things the new software can do, perhaps a move back in that direction isn't a bad idea. It would be nice change to the traditional game intro screen at the top of the page. -[[User:NKF|NKF]] ([[User talk:NKF|talk]]) 08:07, 30 December 2013 (EST)
:Pete, I completely agree with your idea of dropping everything below the News since it's easier to simply use the left links and I doubt a lot of people bother to scroll down so much.
:Regarding the old vs. new games, one of the most telling graphs from Google Analytics is this one:
[[File:EU stats.png]]

The first increase in daily visits on January 2012 is when XCOM: Enemy Unknown was announced, the massive spike in November 2012 is when it was released. But what's even more interesting is that for the same period, the Apocalypse page was the 2nd most visited, UFO Defense the 3th and TFTD the 7th. There's no info for Enemy Unknown 2012 though (there must have been a problem with Analytics since it only started recording visits to the EU2012 pages last month - this might also explain why the visits decreased from November 2012 onwards since visits to the EU2012 were not recorded by Analytics). To me this means that the old games are still live and kicking but also that the new game brought again a big interest on the series. [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 08:23, 30 December 2013 (EST)

[[File:Homepage 2.jpeg|200px|thumb|left|]] [[File:UFOPaedia-Homepage-3.jpg|200px|thumb|left|]]I've been toying with some alternative graphics that are better than my original idea. There's a colour version, but it's a bit "full-on" on a predominantly black and white page, and a greyscale version that might work better. My thinking is that if they are both set to something like 49% width with the latter having 2% left padding, they will scale with the different screen sizes people will view it at. That sort of thing works a lot better in browsers nowadays. Any good? If they're both still a bit bold I could wash out the backgrounds a bit more (that or change the colour of UFOPaedia :D )

:Grey Scale looks better, but it looks like you forgot [[The Bureau: XCOM Declassified|The Bureau Case]] on the Reboot series image--[[User:Ditto51|Ditto51]] ([[User talk:Ditto51|talk]]) 08:44, 1 January 2014 (EST)
::I agree with Ditto51, Grey Scale looks better. [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 11:52, 4 January 2014 (EST)
 
==Long War at Featured Projects==
I've been having a discussion at the Nexusmods forums regarding the possibility of having a subwiki hosted at the UFOPaedia for the Enemy Unknown (2012)'s Long War mod. This is a mod that has been in development for the past two years and has been highly praised by gaming magazines and EU's developers and the [http://www.nexusmods.com/xcom/mods/88/? beta] for Long War 3 (compatible with Enemy Within) has just been released. Any comments? [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 20:15, 26 May 2014 (EDT)
:Hm, I'd certianly say it's a noteworthy mod (though it may be more due to the fact that, in this day and age, information simply travels faster and with greater acessability/ease, than say, the mods for the '94 game, but that's a different lecture), so I'd say yes, a sub-wiki under XCOM:EU/EW, not as sure as to has a separate sidebar/front page space (besides in the news section, and "yes we have no bannanas" perma-link)(if you understand a thing of what the hell I just said/usually say) like the offical releases (ie; like how EW isn't in the sidebar, just vanilla EU). Also, I don't even see a mod/hack page on the xcom.wikia, so that'd be another thing we'd have over them, heh heh~ --[[User:Xuncu|Xuncu]] ([[User talk:Xuncu|talk]]) 07:35, 27 May 2014 (EDT)
::Well I've just tried it the first time and downloading the latest beta. I had participated in a few discussions at Nexusmods regarding new features but I had never bothered playing (just another mod and it required a lot of user steps to install) since I had my hands more than full with EU/EW. All I can say is that this is as big as the Enemy Within DLC regarding new features and reworking of the existing ones, turning it into a different game and installation is much easier than before.
::So I'd definitely add this to the Featured Projects since it's as big as UFO2000 and OpenXcom and it is more comparable to them rather than EW. The reason why EW is not on the sidebar is because it would require its own separate table and either a lot of duplication of already existing pages or it would be a rather small table. Long War on the other hand reworks the Strategic Layer (air interceptions, panic system, AI), soldier classes/abilities, equipment, Research tree, and several aspects of combat so it will require specific pages to detail all those changes.
::To finish, I'd use the same rules for Long War as OpenXcom/UFO200: keep its pages completely separate from the EU2012 ones by using a (Long War) category and suffix; no links on EU/EW pages to Long War pages (to separate official games from fandom), and finally create a specific table for Long War, based on the current EU2012 table format. [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 09:19, 27 May 2014 (EDT)
==Wiki Etiquette and Word Choice==
You should probably change "COULD OF" to "COULD HAVE". Particularly since it's in bold. Unless you want everyone to notice your awful grasp of the language, of course. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 02:34, 19 September 2014 (EDT)
:Keep in mind that for several users English might not be their first language (myself included). Or that 'awful' can be understood to be as insulting as 'autistic' ;) [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 08:35, 19 September 2014 (EDT)
::Spanish is my first language. Feel free to edit my Bureau entries, 'Shroom.... Which is pretty much "all entries for The Bureau." Have fun! --[[User:Xuncu|Xuncu]] ([[User talk:Xuncu|talk]]) 17:27, 19 September 2014 (EDT)
:Hobbes: I have an awful grasp of French (significantly more awful, at that). Also, the reason I reacted to Connor wasn't that he'd insulted Xuncu, but that he did so using a slur that implicitly insulted others (including me). Compare, for instance, the reason people get angry if someone calls a miser a Jew; they're not angry because of the insult to the miser, but because of the insult to all Jews by equating them with misers. My autistic obsession with X-Com has produced useful pages on this wiki; Connor's slur denied that and implicitly told me to GTFO. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 18:42, 19 September 2014 (EDT)
::You have a right to feel insulted whenever someone says something that offends you, but the way you communicate it to the offender is your decision. I find it easier not to take these situations too personally because ignorance is far more common than malice :) [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 18:57, 19 September 2014 (EDT)
:The two blend together in the context of hate speech; while specific malice toward the group in question is not necessarily required, a generally xenophobic mindset and a willingness to stereotype with callous disregard for accuracy '''is''' present in basically all cases. Hate speech "by mistake" (ie, using slurs without intending to) is extremely rare and easily distinguishable from the intentional sort. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 21:17, 19 September 2014 (EDT)
::Wikis have one [http://www.example.com principle] (amongst others) to work: '''assume good faith on the part of its users'''. I've been [[Talk:Impossible_Difficulty_(EU2012)|called]] here 'pedantic' due to my obsession with detail and personally the term has a negative connotation to me but I chose to assume good faith and accept the feedback. Otherwise, if we take slight on every badly chosen word, then this really hurts collaboration, which is what wikis are all about. [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 08:50, 20 September 2014 (EDT)

==XCOM2==
Off to the madness we head out again. :)
First issue is what suffix to add to page names to help classify and identify their content: (TFTD) for Terror From the Deep, (EU2012) for Enemy Unknown, etc. Any suggestions? [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 22:34, 2 June 2015 (EDT)
:Like we've been doing up to this point. EU, TFTD, Apoc, Int?, EU2012 and now I assume XCOM2. If the name changes in the future, we'll have to adjust the suffix accordingly. --[[User:Zombie|Zombie]] ([[User talk:Zombie|talk]]) 23:49, 2 June 2015 (EDT)

Incendiary

2015-06-03T03:44:27Z

Zombie: /* Damage */ Added equation and example for duration of unit fire.

[[Image:Fire_ground.gif|Ground Fire Animation]] [[Image:Fire_unit.gif|Unit Fire Animation]]

'''[[Incendiary]]''' (IN) ammunition creates a large area of '''fire''' on the [[battlescape]] equal to its [[#Blast Diameter|blast diameter]]. Incendiary rounds will burn for two turns on non-flammable terrain. Flammable terrain will burn for longer, and the fire is likely to spread to any adjacent flammable tiles. Aliens and unarmored X-COM agents can catch fire as well.

Incendiary rounds do very little direct damage -- between 0 and 10 points per hit -- but continue to do damage every turn that a unit is in fire or on fire. Due to the "[[Known_Bugs#Funky_Fire|funky fire]]" bug, units in or on fire will also take damage every time an incendiary round goes of ''anywhere'' on the Battlescape.

== Source ==
Incendiary rounds are available for the following weapons:

*[[Auto-Cannon]]
*[[Heavy Cannon]]
*[[Rocket Launcher]]

Some tiles may already be on fire at the start of the mission if the [[UFO Crash Recovery|UFO crashed]].

== Blast Diameter ==

*Auto-Cannon incendiary rounds have a blast diameter of 5 tiles; note that the southern tip of the "diamond" will always be missing.
*Heavy Cannon incendiary rounds have a blast diameter of 7 tiles.
*Incendiary rockets have a blast diameter of 9 tiles.

X
X XXXXXXX
X XXXXX XXXXXXX
XXX XXXXX XXXXXXX
XXXXX XXXXXXX XXXXXXXXX
XXX XXXXX XXXXXXX
X XXXXX XXXXXXX
X XXXXXXX
X

AC-IN HC-IN RL-IN

==Smoke==
[[Image:Smoke1.gif]] [[Image:Smoke2.gif]] [[Image:Smoke3.gif]]
A burning fire can also be used as an impromptu smoke screen. No smoke appears immediately, but smoke will appear outside the edges of the fire, as the fire slowly spreads in subsequent turns. The smoke begins on the first turn after the turn the incendiary round is fired. The smoke will spread vertically (upwards) as well as laterally. Smoke can block [[Line_of_sight|line of sight]].

==Light==
[[File:FlarePattern.png|thumb|right|A single square of fire will illuminate the area within the grey line.]]
Fire not only damages aliens and obstacles hiding in dark corners of the map, but also illuminates the area for several turns. This is especially useful during [[Night Missions]].

Any tile on fire will provide illumination within a 9 tile radius. A large patch of fire will illuminate everything within 9 tiles of the outer edge of the fire. Curiously, aliens on fire do not provide illumination. Maybe they're [http://firecritic.com/2010/12/firefighters-guide-to-invisible-fire-otherwise-known-as-ethanol-fires/ made of ethanol] or something.

==Damage==
<div style="color:red;">Incendiary damage mechanics are not fully understood and are being re-investigated by [[User:Zombie|Zombie]]. The information below is part of the picture but not the completely accurate picture. Treat with caution! More discussion is on the [[Talk:Incendiary|Talk page]].</div>

* Brush and wood on fire will eventually be consumed, leaving a flat scorched-earth [[MCD|tile]].

* If a [[Zombie]] is killed by the explosive impact of any form of Incendiary munitions, the [[Chryssalid]] larva will be burnt up instead of hatching. However, Zombies have high [[Alien Stats|hit points]] and will have to be near death to be killed by an IN round, per se.

* UFO interiors and dropped items are fireproof, even if their owners aren't. Silverblade recommends combining this fact with the diagonal wall bug and an incendiary rocket to roast them in the shell.

* Damage caused by fire does not alter [[Morale]] level.

* '''All''' forms of manufactured X-COM armor will completely block the effects of fire -- including direct hits from incendiary rounds. Soldiers not wearing armor take [[Health]] damage.

* '''Soldiers wearing armour, if wounded, can die from spreading fire.''' Apparently if the damage the fire would inflict exceeds the soldier's remaining [[health]], the soldier will die. If the damage is not enough to kill the soldier that turn, no damage will be inflicted. This bug only applies to ''spreading'' fire, and will not affect a wounded soldier already standing in fire.

* Certain creatures take increased or decreased [[Damage#Damage_Modifiers|damage]] from incendiary rounds:
**More Vulnerable:
***170% - Reaper
**Less Vulnerable:
***80% - Chryssalid
***70% - Ethereal, Snakeman
***40% - Tanks/Hovertanks
*** 0% - Silacoid (rocks don't burn!)

* Initial "impact" damage from incendiary ammunition is either for no points (unit does not catch fire), or between 5-10 points (unit catches fire). Since the distribution is randomly chosen from the set [ 0, 5, 6, 7, 8, 9, 10 ] (seven values), the probability of remaining unharmed is 14% (1/7), while there is an 86% chance (6/7) a unit will take some damage. The average damage is 6.4.

* Units standing in a blaze (as opposed to being on fire themselves) will receive between 1-12 damage points, most likely determined by the flammability rating of their tile ([[MCD]] offset 45). They have a 33% chance of catching fire (observation from 6000+ trials).

* Once lit, units burn for a slightly random amount of time, taking 5-10 damage points each turn. (If units fall unconscious, they do not continue to burn.) Thus the average total damage is 21.5 points (3 x 7.5), but could be as high as 50. Compare that [[Alien Stats|alien health values]] range from 30 to 120... it can kill or seriously damage sectoids, floaters (if on ground!), and maybe snakes, but barely warms up mutons. Terrorists are hardly touched (but now you might have their attention). Unsurprisingly, the equation used to determine how long a unit will remain on fire depends on the damage modifier of the unit in question: MaxTime=5*Damage Modifier/100, Duration=Random(MaxTime). So for example, if a tank (damage modifier to IN=40) catches fire it will remain lit for MaxTime=5*40/100=2; Duration=Random(2) or 1-2 turns.

* Smoke does not snuff out units on fire.

* Ultimately, in comparison with other ammo types, incendiary ammo is both weak and slow. Most of the time you will want to use it for other purposes (light, blocking LOS, clearing areas) and consider any damage a plus. However, it can be particularly effective against sectoids - so have plenty of IN for your early-game missions. Barbecue spits are optional.

==Spreading==
Fires can spread one tile in every direction, in ideal conditions (such as wheat fields and haylofts). However, since [[Battlescape_Map_Generation|no map]] is a pure wheat field and many tile types are unlikely to burn, they eventually go out.

Unarmored soldiers can walk through fire unscathed, but don't be left standing on '''''or next to''''' a burning tile at the end of the turn. That's when the fire-spreading code runs. Incendiaries also restrict alien movement; they, too, try to avoid fire.

Explosives (any weapon with [[damage]] type [[Explosives|HE]]) can start fires, particularly in mountains (due to a [[Explosives#Mile-High_Madness|bug]]). Copious use of explosives on thick cover can flush out the enemy - but you have an [[Managing_the_Item_Limit|80-item limit]].

Explosives will not put out fires, per se. You can directly destroy tile flammability via [[Explosives#Tile_Characteristics|explosives]] so that areas can't burn (or stop burning), but it's tricky. (How accurate is your [[Throwing_Accuracy|throwing]]?) In theory, it's possible for your team to corral or even direct flames, but how many folks have tried this? Please put any good war stories along these lines on this page's Discussion.

==Quirks, Tips, And Tricks==
XCOM makes a brave attempt to model fire. However, there are some quirks:

*If a unit (alien or friendly) is on fire or standing in flames, an incendiary explosion ''anywhere else on the map'' will damage it, even if you just shoot an IN round at a random patch of ground.

*Friendly units standing in '''smoke''' will take '''STUN''' damage every time an incendiary round explodes, '''even if armored.''' Alien units are not affected (needs further testing).

*Aliens not facing you will not respond with reaction fire when hit (directly or indirectly) by an incendiary round (see [[Reaction fire triggers]]).

* Smoke and flames do not mix. Only one type may exist on a particular tile on a particular turn. To quickly smother a blaze simply drop a primed [[Smoke Grenade]] in the center. This is a fairly useful trick for unarmored soldiers who want to safely cross a blaze without waiting for it to burn out by itself. But remember, you can cross a blaze safely - just don't stop in or next to one.

*There is an upper limit to how many squares can be on fire or in smoke (400 squares total for both). Once you have a good sized blaze going (forest fire, anyone?) further incendiary rounds will seem to fizzle, because no more fire can be created. Impact damage will still be dealt and units can still be set on fire. Still, existing smoke-covered tiles can be turned into fire instead of smoke, and vice versa.

*The damage values listed in the [[UFOpaedia]] do not determine how powerful an incendiary round deals damage; it only determines how wide an area will be blanketed with flames. Fire is unlike other damage; it works at initial blast and then over time, as described above.

*Shots made with IN rounds never count as "hitting" for the purposes of firing accuracy [[experience]], but reaction shots are counted and can go towards better reaction stats.

*Incendiary rounds (and other forms of fire) do not damage valuable equipment/loot; even corpses will not burn.

[[Category:Enemy Unknown/UFO Defense]]