UFOpaedia - User contributions [en]

X-COM

2005-09-24T08:37:22Z

80.196.239.243:

In 1999, Unidentified Flying Objects (UFOs) started appearing with disturbing regularity in the night skies. Reports of violent human abductions and horrific experimentation struck terror into the hearts of millions. The mass public hysteria that ensued only served to expose Earth's impotence against a vastly superior technology.

Many countries attempted to deal independently with the aliens. In August 1998, Japan established an anti-alien combat force; the Kiryu-Kai. Equipped with Japanese-made fighter aircraft, the Kiryu-Kai certainly looked like a powerful force. However, after 5 months of expensive operations they had yet to intercept their first UFO. The lesson was clear: this was a worldwide problem which could not be dealt with by individual countries.

On December 11, 1998, representatives from the worlds most economically powerful countries gathered secretly in Geneva. After much debate, the decision was made to establish a covert independent body to combat, investigate and defeat the alien threat. This organization would be equipped with the worlds finest pilots, soldiers, scientists and engineers, working together as one multi-national force.

This organization was named the E'''x'''traterrestrial '''Com'''bat Unit.

However in 2040 X-Com was back on the road at the [[Second Alien War]]
against som underwater aliens. see [[TFTD]] for more info.

Base Facilities (TFTD)

2005-09-24T08:13:29Z

80.196.239.243:

Base Facilities

There are a number of base facilities that you can place in your installations. Some of these are available from the beginning of the game, others are gained through research. With the exception of the [[Airlock]], and the facilites you start the game with, all require an amount of time to be built and will charge you a monthly maintanance fee on top of the initial construction costs.

All base facilities must be linked, either directly or via other base facilities, to the Airlock. While you cannot dismantle a base facility that is in use or is linking other facilities to the Airlock, it can be destroyed in the process of a [[Base Defense]] mission. If a base facility is destroyed in this way, any other base facilities that were relying on that facility as a link to the Airlock will also be destroyed. Any pieces of equipment, craft, or personal will, however, remain in the base (despite the lack of room).

Initial Base Facilities:

[[Airlock]]

Researchable Base Facilities:

[[M.C Lab]]

--[[Bomb Bloke]] and [[Tentaculat_Commander]] 15:41, 4 Mar 2005 (GMT)

Base Facilities (TFTD)

2005-09-24T08:12:47Z

80.196.239.243:

Base Facilities

There are a number of base facilities that you can place in your installations. Some of these are available from the beginning of the game, others are gained through research. With the exception of the [[Airlock]], and the facilites you start the game with, all require an amount of time to be built and will charge you a monthly maintanance fee on top of the initial construction costs.

All base facilities must be linked, either directly or via other base facilities, to the Airlock. While you cannot dismantle a base facility that is in use or is linking other facilities to the Airlock, it can be destroyed in the process of a [[Base Defense]] mission. If a base facility is destroyed in this way, any other base facilities that were relying on that facility as a link to the Airlock will also be destroyed. Any pieces of equipment, craft, or personal will, however, remain in the base (despite the lack of room).

Initial Base Facilities:

[[Airlock]]

Researchable Base Facilities:

[[M.C Lab]]

--[[Bomb Bloke]]and [[Tentaculat_Commander]] 15:41, 4 Mar 2005 (GMT)

SOLDIER.DAT

2005-09-24T08:10:28Z

80.196.239.243: /* Structure */

= General Notes =
SOLDIER.DAT has a fixed structure of 250 entries of 68 bytes each. (Only a maximum of 250 soldiers can be had.) Thus it is always 17,000 bytes long (250x68).

In several places it uses Intel little-endian "Words". These are two-byte values with the low byte first, high byte second. Thus they can count to values greater than 255 (to 65,536). Sometimes they are "signed" however (8000h, when the highest bit is set), which makes the maximum positive value 32,767. It's of no concern in an ordinary game, but may be to hackers. "Signed" is noted below where applicable.

Values are presented according to byte count (1 to 68) followed by the equivalent hex offset (00 to 43) in bold, followed by the normal (non-hacked) range of values in italics. Most fields can be hacked up to FF, but sometimes it can make for weirdness!

= Structure =
1-2 / 00-01 (0-5, FFFF): Word set to Rank or FFFF if soldier is dead (or slot not yet used). These values are actually pointers within a text file, so if you change it to 6 it will say "Units in Entrance" as your rank. Strange stuff. Ranks are:
0 Recruit
1 Squaddie
2 Sargeant (SGT)
3 Captain (CPT)
4 Colonel (COL)
5 Commander (CDR)
6 Units in Entrance
7 Units in Target Exit
3 / 02 (various, FF): Base the soldier is at, using reference values from LOC.DAT. First base is always 0 (first entry in LOC.DAT). Value of FF means the soldier is being transferred.

5-6 / 04-05 (various, FFFF): Craft soldier is assigned to, using values from LOC.DAT. FFFF means not assigned to a craft.

7-8 / 06-07 (FFFF): Unknown. Presumed Word. Only ever seen to be FFFF.

9-10 / 08-09 (0+): Number of missions. Signed Word.

11-12 / 0A-0B (0+): Number of kills. Signed Word.

13-14 / 0C-0D (0+): Wound recovery days. Signed Word.

15-16 / 0E-0F (20+): Morale value (morale hit if this guy dies). Presumed to be a signed Word. Is equal to 20 + Missions + Rank Bonus, as follows:

0 Recruit
0? Squaddie (not yet tested)
1 SGT
3 CPT
6 COL
10 CDR

Note: Hex-editing Missions or Rank and performing a combat (while not touching this field) does not cause this field to reflect the edited values. This field simply adds 1 for each mission and a delta for rank bonus. IOW, although it uses the equation shown above, it's not actually computed from Missions and Rank, per se.

17-41 / 10-28 (Text): Name, 25 characters long. Only approx. 21 characters can be entered when editing the field within the game's Soldier display, but longer names can be hex edited and will be seen in the game. Almost any keyboard character can be entered (including within the game) because they are stored directly instead of going through Windows objects. Remainders of names are retained if a new soldier in a slot has a shorter name than the previous soldier. The end of the current name is denoted by a null character (00).

42 / 29 (various): Always 0 except for existing soldiers being transferred, in which case it equals the LOC.DAT value for destination base. New hirees on their way to a base will also have this set to 0, so if Byte 3 is set to FF and this byte is 0, you can't tell (from these two bytes alone) if it's an existing soldier going to your first base (LOC.DAT=0), or a new recruit going to any base. But the game knows where they're going, presumably via TRANSFER.DAT.

43 / 2A (50-60): Initial TUs.

44 / 2B (25-40): Initial Health.

45 / 2C (40-70): Initial Stamina.

46 / 2D (30-60): Initial Reaction.

47 / 2E (20-40): Initial Strength.

48 / 2F (40-70): Initial Firing Accuracy.

49 / 30 (50-80): Initial Throwing Accuracy.

50 / 31 (20-40): Initial Melee / Close Combat Accuracy. See Note 1.

51 / 32 (0-100): Psi Strength.

53 / 34 (5-10): Initial Bravery. Computed as 110-(10*ThisByte). E.g. if ThisByte=9, Bravery=20. So the lower this byte is, the better your Bravery is. Initial Bravery can be 10-60, and it only uses increments of 10.

52 / 33 (0-105++): Current Psi Skill. 0 = has not yet had any Psi Lab training. See Note 2.

54 / 35 (0-31): Increase in TUs. (Max total TUs possible (initial+increase) is 81. See Note 2.)

55 / 36 (0-36): Increase in Health. (Max total 61)

56 / 37 (0-61): Increase in Stamina. (Max total 101)

57 / 38 (0-75?): Increase in Reaction. (Max total 105?)
''[ [[User:MikeTheRed|MikeTheRed]]- Reaction needs testing - it is not 80 (as the wiki says) and even increases at 90 - must be 100 or 120 - I'll test it when I can, if you don't beat me to it! ]''

58 / 39 (0-51): Increase in Strength. (Max total 71) Note that very high (hacked) values can cause "unable to throw here", presumably because the arc would intercept the "ceiling" of the battlescape. See [[Throwing_Accuracy#Throwing_Distance|throwing distance]] for more on Strength versus Throwing.

59 / 3A (0-85): Increase in Firing Accuracy. (Max total 125)

60 / 3B (0-75): Increase in Throwing Accuracy. (Max total 125)

61 / 3C (0-105): Increase in Melee/Close Combat Accuracy. (Max total 125)
See Note 1.

62 / 3D (0-10): Increase in Bravery (multiply by 10). (Max total 10; 110 Bravery)

63 / 3E (0-3): Armor. 0=None, 1=Personal Armor, 2=Power Armor, 3=Flying Suit.

Can be hacked to: 4=Sectoid, 5=Snakeman, 6=Ethereal, 7=Muton, 8=Floater, 9=Celatid, 10=Silacoid, 11=Chryssalid. (Higher values are civilians and parts of big units.) NOTE: These are not real aliens, just skins... more research must be done e.g. on appearance and gender to make real aliens.

64 / 3F (0-24?): Most-recent month's Psi Lab training increase. Largest values for newly trained (16-24).

65 / 40 (0,1): In Psi Lab training.

66 / 41 (0,1): Promotion flag (as of most recent combat). Reset as of next combat.

67 / 42 (0,1): 0=Male, 1=Female. 2=???

''[[User:MikeTheRed|MikeTheRed]] - Was that a joke? Who put the 2 in there, lol''

''[[User:Tentaculat_Commander|Gurluas]] - I did to encourage research.''

68 / 43 (0-3): Appearance (for loadout, no armor): 0=blonde, 1=brown hair, 2=Oriental, 3=African, 4=???.

= Notes =

1) Melee a.k.a. Close Combat Accuracy is a somewhat abandoned skill. It does not appear in display screens, but Byte 61 does increase when the stun rod is used. Also, secondary skills will increase when you do this, as they do for other primary skills. Finally, it has a cap of 120 (Bytes 50+61). Given its placement in this file, then, it is presumed that this is a third 'accuracy' skill related to stun-rod use, with Byte 50 being the initial value and Byte 61 being the increase.

2) The possible values for skill increases (in a non-hacked game) depend both on the cap for each skill and on each soldiers' initial value. Thus the max possible value shown in the 'increase' range is for soldiers who started with the minimum initial skill, and got the max possible cap 'overflow'. Primary skills can have up to five over the target cap (if the player gets +6 from a combat when at Cap-1), and secondary skills can have up to one over the target cap (if they get +2 when at Cap-1). Also, Psi Skill is not truly capped - although soldiers cease to get combat increases once at or above 100, it will continue to increase by 2-3 each month the soldier stays in Psi Training.

3) Be careful of making total skill value (initial + increase) greater than 160 (A0h). This will make your skill bar wrap around the screen.

4) As can be seen, Armor is the only thing that 'stays with' a soldier. Yes, it's lost if you fire someone wearing it!

= For More Information =

*Information on individual skills can be seen at [[Soldiers (UFO Defense) | Soldiers]].
*For more information on increasing skills, see [[Experience]].
*For more information on starting soldier stats, see [[Raw_recruit_statistical_likelihood|Raw Recruit Statistical Likelihood]].
* A Hex Workshop Structure Library for editing this file can be found [[SOLDIER_DAT_HSL|here]].

SOLDIER.DAT

2005-09-24T08:09:58Z

80.196.239.243:

= General Notes =
SOLDIER.DAT has a fixed structure of 250 entries of 68 bytes each. (Only a maximum of 250 soldiers can be had.) Thus it is always 17,000 bytes long (250x68).

In several places it uses Intel little-endian "Words". These are two-byte values with the low byte first, high byte second. Thus they can count to values greater than 255 (to 65,536). Sometimes they are "signed" however (8000h, when the highest bit is set), which makes the maximum positive value 32,767. It's of no concern in an ordinary game, but may be to hackers. "Signed" is noted below where applicable.

Values are presented according to byte count (1 to 68) followed by the equivalent hex offset (00 to 43) in bold, followed by the normal (non-hacked) range of values in italics. Most fields can be hacked up to FF, but sometimes it can make for weirdness!

= Structure =
1-2 / 00-01 (0-5, FFFF): Word set to Rank or FFFF if soldier is dead (or slot not yet used). These values are actually pointers within a text file, so if you change it to 6 it will say "Units in Entrance" as your rank. Strange stuff. Ranks are:
0 Recruit
1 Squaddie
2 Sargeant (SGT)
3 Captain (CPT)
4 Colonel (COL)
5 Commander (CDR)
6 Units in Entrance
7 Units in Target Exit
3 / 02 (various, FF): Base the soldier is at, using reference values from LOC.DAT. First base is always 0 (first entry in LOC.DAT). Value of FF means the soldier is being transferred.

5-6 / 04-05 (various, FFFF): Craft soldier is assigned to, using values from LOC.DAT. FFFF means not assigned to a craft.

7-8 / 06-07 (FFFF): Unknown. Presumed Word. Only ever seen to be FFFF.

9-10 / 08-09 (0+): Number of missions. Signed Word.

11-12 / 0A-0B (0+): Number of kills. Signed Word.

13-14 / 0C-0D (0+): Wound recovery days. Signed Word.

15-16 / 0E-0F (20+): Morale value (morale hit if this guy dies). Presumed to be a signed Word. Is equal to 20 + Missions + Rank Bonus, as follows:

0 Recruit
0? Squaddie (not yet tested)
1 SGT
3 CPT
6 COL
10 CDR

Note: Hex-editing Missions or Rank and performing a combat (while not touching this field) does not cause this field to reflect the edited values. This field simply adds 1 for each mission and a delta for rank bonus. IOW, although it uses the equation shown above, it's not actually computed from Missions and Rank, per se.

17-41 / 10-28 (Text): Name, 25 characters long. Only approx. 21 characters can be entered when editing the field within the game's Soldier display, but longer names can be hex edited and will be seen in the game. Almost any keyboard character can be entered (including within the game) because they are stored directly instead of going through Windows objects. Remainders of names are retained if a new soldier in a slot has a shorter name than the previous soldier. The end of the current name is denoted by a null character (00).

42 / 29 (various): Always 0 except for existing soldiers being transferred, in which case it equals the LOC.DAT value for destination base. New hirees on their way to a base will also have this set to 0, so if Byte 3 is set to FF and this byte is 0, you can't tell (from these two bytes alone) if it's an existing soldier going to your first base (LOC.DAT=0), or a new recruit going to any base. But the game knows where they're going, presumably via TRANSFER.DAT.

43 / 2A (50-60): Initial TUs.

44 / 2B (25-40): Initial Health.

45 / 2C (40-70): Initial Stamina.

46 / 2D (30-60): Initial Reaction.

47 / 2E (20-40): Initial Strength.

48 / 2F (40-70): Initial Firing Accuracy.

49 / 30 (50-80): Initial Throwing Accuracy.

50 / 31 (20-40): Initial Melee / Close Combat Accuracy. See Note 1.

51 / 32 (0-100): Psi Strength.

53 / 34 (5-10): Initial Bravery. Computed as 110-(10*ThisByte). E.g. if ThisByte=9, Bravery=20. So the lower this byte is, the better your Bravery is. Initial Bravery can be 10-60, and it only uses increments of 10.

52 / 33 (0-105++): Current Psi Skill. 0 = has not yet had any Psi Lab training. See Note 2.

54 / 35 (0-31): Increase in TUs. (Max total TUs possible (initial+increase) is 81. See Note 2.)

55 / 36 (0-36): Increase in Health. (Max total 61)

56 / 37 (0-61): Increase in Stamina. (Max total 101)

57 / 38 (0-75?): Increase in Reaction. (Max total 105?)
''[ [[User:MikeTheRed|MikeTheRed]]- Reaction needs testing - it is not 80 (as the wiki says) and even increases at 90 - must be 100 or 120 - I'll test it when I can, if you don't beat me to it! ]''

58 / 39 (0-51): Increase in Strength. (Max total 71) Note that very high (hacked) values can cause "unable to throw here", presumably because the arc would intercept the "ceiling" of the battlescape. See [[Throwing_Accuracy#Throwing_Distance|throwing distance]] for more on Strength versus Throwing.

59 / 3A (0-85): Increase in Firing Accuracy. (Max total 125)

60 / 3B (0-75): Increase in Throwing Accuracy. (Max total 125)

61 / 3C (0-105): Increase in Melee/Close Combat Accuracy. (Max total 125)
See Note 1.

62 / 3D (0-10): Increase in Bravery (multiply by 10). (Max total 10; 110 Bravery)

63 / 3E (0-3): Armor. 0=None, 1=Personal Armor, 2=Power Armor, 3=Flying Suit.

Can be hacked to: 4=Sectoid, 5=Snakeman, 6=Ethereal, 7=Muton, 8=Floater, 9=Celatid, 10=Silacoid, 11=Chryssalid. (Higher values are civilians and parts of big units.) NOTE: These are not real aliens, just skins... more research must be done e.g. on appearance and gender to make real aliens.

64 / 3F (0-24?): Most-recent month's Psi Lab training increase. Largest values for newly trained (16-24).

65 / 40 (0,1): In Psi Lab training.

66 / 41 (0,1): Promotion flag (as of most recent combat). Reset as of next combat.

67 / 42 (0,1): 0=Male, 1=Female. 2=???

''[[User:MikeTheRed|MikeTheRed]] - Was that a joke? Who put the 2 in there, lol''

''[[User:Tenculat_Commander|Gurluas]] - I did to encourage research.''

68 / 43 (0-3): Appearance (for loadout, no armor): 0=blonde, 1=brown hair, 2=Oriental, 3=African, 4=???.

= Notes =

1) Melee a.k.a. Close Combat Accuracy is a somewhat abandoned skill. It does not appear in display screens, but Byte 61 does increase when the stun rod is used. Also, secondary skills will increase when you do this, as they do for other primary skills. Finally, it has a cap of 120 (Bytes 50+61). Given its placement in this file, then, it is presumed that this is a third 'accuracy' skill related to stun-rod use, with Byte 50 being the initial value and Byte 61 being the increase.

2) The possible values for skill increases (in a non-hacked game) depend both on the cap for each skill and on each soldiers' initial value. Thus the max possible value shown in the 'increase' range is for soldiers who started with the minimum initial skill, and got the max possible cap 'overflow'. Primary skills can have up to five over the target cap (if the player gets +6 from a combat when at Cap-1), and secondary skills can have up to one over the target cap (if they get +2 when at Cap-1). Also, Psi Skill is not truly capped - although soldiers cease to get combat increases once at or above 100, it will continue to increase by 2-3 each month the soldier stays in Psi Training.

3) Be careful of making total skill value (initial + increase) greater than 160 (A0h). This will make your skill bar wrap around the screen.

4) As can be seen, Armor is the only thing that 'stays with' a soldier. Yes, it's lost if you fire someone wearing it!

= For More Information =

*Information on individual skills can be seen at [[Soldiers (UFO Defense) | Soldiers]].
*For more information on increasing skills, see [[Experience]].
*For more information on starting soldier stats, see [[Raw_recruit_statistical_likelihood|Raw Recruit Statistical Likelihood]].
* A Hex Workshop Structure Library for editing this file can be found [[SOLDIER_DAT_HSL|here]].

SOLDIER.DAT

2005-09-24T08:09:21Z

80.196.239.243: /* Structure */

= General Notes =
SOLDIER.DAT has a fixed structure of 250 entries of 68 bytes each. (Only a maximum of 250 soldiers can be had.) Thus it is always 17,000 bytes long (250x68).

In several places it uses Intel little-endian "Words". These are two-byte values with the low byte first, high byte second. Thus they can count to values greater than 255 (to 65,536). Sometimes they are "signed" however (8000h, when the highest bit is set), which makes the maximum positive value 32,767. It's of no concern in an ordinary game, but may be to hackers. "Signed" is noted below where applicable.

Values are presented according to byte count (1 to 68) followed by the equivalent hex offset (00 to 43) in bold, followed by the normal (non-hacked) range of values in italics. Most fields can be hacked up to FF, but sometimes it can make for weirdness!

= Structure =
1-2 / 00-01 (0-5, FFFF): Word set to Rank or FFFF if soldier is dead (or slot not yet used). These values are actually pointers within a text file, so if you change it to 6 it will say "Units in Entrance" as your rank. Strange stuff. Ranks are:
0 Recruit
1 Squaddie
2 Sargeant (SGT)
3 Captain (CPT)
4 Colonel (COL)
5 Commander (CDR)
6 Units in Entrance
7 Units in Target Exit
3 / 02 (various, FF): Base the soldier is at, using reference values from LOC.DAT. First base is always 0 (first entry in LOC.DAT). Value of FF means the soldier is being transferred.

5-6 / 04-05 (various, FFFF): Craft soldier is assigned to, using values from LOC.DAT. FFFF means not assigned to a craft.

7-8 / 06-07 (FFFF): Unknown. Presumed Word. Only ever seen to be FFFF.

9-10 / 08-09 (0+): Number of missions. Signed Word.

11-12 / 0A-0B (0+): Number of kills. Signed Word.

13-14 / 0C-0D (0+): Wound recovery days. Signed Word.

15-16 / 0E-0F (20+): Morale value (morale hit if this guy dies). Presumed to be a signed Word. Is equal to 20 + Missions + Rank Bonus, as follows:

0 Recruit
0? Squaddie (not yet tested)
1 SGT
3 CPT
6 COL
10 CDR

Note: Hex-editing Missions or Rank and performing a combat (while not touching this field) does not cause this field to reflect the edited values. This field simply adds 1 for each mission and a delta for rank bonus. IOW, although it uses the equation shown above, it's not actually computed from Missions and Rank, per se.

17-41 / 10-28 (Text): Name, 25 characters long. Only approx. 21 characters can be entered when editing the field within the game's Soldier display, but longer names can be hex edited and will be seen in the game. Almost any keyboard character can be entered (including within the game) because they are stored directly instead of going through Windows objects. Remainders of names are retained if a new soldier in a slot has a shorter name than the previous soldier. The end of the current name is denoted by a null character (00).

42 / 29 (various): Always 0 except for existing soldiers being transferred, in which case it equals the LOC.DAT value for destination base. New hirees on their way to a base will also have this set to 0, so if Byte 3 is set to FF and this byte is 0, you can't tell (from these two bytes alone) if it's an existing soldier going to your first base (LOC.DAT=0), or a new recruit going to any base. But the game knows where they're going, presumably via TRANSFER.DAT.

43 / 2A (50-60): Initial TUs.

44 / 2B (25-40): Initial Health.

45 / 2C (40-70): Initial Stamina.

46 / 2D (30-60): Initial Reaction.

47 / 2E (20-40): Initial Strength.

48 / 2F (40-70): Initial Firing Accuracy.

49 / 30 (50-80): Initial Throwing Accuracy.

50 / 31 (20-40): Initial Melee / Close Combat Accuracy. See Note 1.

51 / 32 (0-100): Psi Strength.

53 / 34 (5-10): Initial Bravery. Computed as 110-(10*ThisByte). E.g. if ThisByte=9, Bravery=20. So the lower this byte is, the better your Bravery is. Initial Bravery can be 10-60, and it only uses increments of 10.

52 / 33 (0-105++): Current Psi Skill. 0 = has not yet had any Psi Lab training. See Note 2.

54 / 35 (0-31): Increase in TUs. (Max total TUs possible (initial+increase) is 81. See Note 2.)

55 / 36 (0-36): Increase in Health. (Max total 61)

56 / 37 (0-61): Increase in Stamina. (Max total 101)

57 / 38 (0-75?): Increase in Reaction. (Max total 105?)
''[ [[User:MikeTheRed|MikeTheRed]]- Reaction needs testing - it is not 80 (as the wiki says) and even increases at 90 - must be 100 or 120 - I'll test it when I can, if you don't beat me to it! ]''

58 / 39 (0-51): Increase in Strength. (Max total 71) Note that very high (hacked) values can cause "unable to throw here", presumably because the arc would intercept the "ceiling" of the battlescape. See [[Throwing_Accuracy#Throwing_Distance|throwing distance]] for more on Strength versus Throwing.

59 / 3A (0-85): Increase in Firing Accuracy. (Max total 125)

60 / 3B (0-75): Increase in Throwing Accuracy. (Max total 125)

61 / 3C (0-105): Increase in Melee/Close Combat Accuracy. (Max total 125)
See Note 1.

62 / 3D (0-10): Increase in Bravery (multiply by 10). (Max total 10; 110 Bravery)

63 / 3E (0-3): Armor. 0=None, 1=Personal Armor, 2=Power Armor, 3=Flying Suit.

Can be hacked to: 4=Sectoid, 5=Snakeman, 6=Ethereal, 7=Muton, 8=Floater, 9=Celatid, 10=Silacoid, 11=Chryssalid. (Higher values are civilians and parts of big units.) NOTE: These are not real aliens, just skins... more research must be done e.g. on appearance and gender to make real aliens.

64 / 3F (0-24?): Most-recent month's Psi Lab training increase. Largest values for newly trained (16-24).

65 / 40 (0,1): In Psi Lab training.

66 / 41 (0,1): Promotion flag (as of most recent combat). Reset as of next combat.

67 / 42 (0,1): 0=Male, 1=Female. 2=???

''[[User:MikeTheRed|MikeTheRed]] - Was that a joke? Who put the 2 in there, lol''
''[[User:Tenculat_Commander|Gurluas]] - I did to encourage research.''

68 / 43 (0-3): Appearance (for loadout, no armor): 0=blonde, 1=brown hair, 2=Oriental, 3=African, 4=???.

= Notes =

1) Melee a.k.a. Close Combat Accuracy is a somewhat abandoned skill. It does not appear in display screens, but Byte 61 does increase when the stun rod is used. Also, secondary skills will increase when you do this, as they do for other primary skills. Finally, it has a cap of 120 (Bytes 50+61). Given its placement in this file, then, it is presumed that this is a third 'accuracy' skill related to stun-rod use, with Byte 50 being the initial value and Byte 61 being the increase.

2) The possible values for skill increases (in a non-hacked game) depend both on the cap for each skill and on each soldiers' initial value. Thus the max possible value shown in the 'increase' range is for soldiers who started with the minimum initial skill, and got the max possible cap 'overflow'. Primary skills can have up to five over the target cap (if the player gets +6 from a combat when at Cap-1), and secondary skills can have up to one over the target cap (if they get +2 when at Cap-1). Also, Psi Skill is not truly capped - although soldiers cease to get combat increases once at or above 100, it will continue to increase by 2-3 each month the soldier stays in Psi Training.

3) Be careful of making total skill value (initial + increase) greater than 160 (A0h). This will make your skill bar wrap around the screen.

4) As can be seen, Armor is the only thing that 'stays with' a soldier. Yes, it's lost if you fire someone wearing it!

= For More Information =

*Information on individual skills can be seen at [[Soldiers (UFO Defense) | Soldiers]].
*For more information on increasing skills, see [[Experience]].
*For more information on starting soldier stats, see [[Raw_recruit_statistical_likelihood|Raw Recruit Statistical Likelihood]].
* A Hex Workshop Structure Library for editing this file can be found [[SOLDIER_DAT_HSL|here]].

Tentaculat

2005-09-23T17:42:28Z

80.196.239.243:

== General Information ==
[[Image:Tentaculat.PNG|right|Tentaculat]]

Not even the depths of a Lovecraftian nightmare could spawn such as this indescribable creature. No comparison to any Earth animal exists, the environment that could produce such as this is beyond imagination. Armed with long tentacles the Tentaculat paralyses its victims then transmutes them into mindless things. These progeny can cause death on touch, even through armour. The Tentaculat is the most fearsome alien yet encountered by X-Com. Even if one of the victims is killed, somehow, they are transformed into another Tentaculat.

Then Tentaculat is nearly always spotted on alien colonies, artefact (or artifact) sites and T'leth.
*
There is ALWAYS a Tentaculat somewhere onboard/near a Dreadnaught. Beware!

Basically a flying [[Chryssalid]], but with less armor.

== Autopsy ==
[[Image:Tentaculat_Autopsy.PNG|right|Dead Tentaculat]]

The autopsy reveals small cybernetic implants are lodged in the creature's large brain. The vision system is a complex combination of visible light and thermal imaging acquisition. Even in the inky depths of the ocean this monster can navigate with unerring accuracy. There are vestigial organs that seem to be the bare minimum for survival. Each creature has a small stomach with an external connector, it is logical to assume the being is fed by direct nutrient input by its masters.

Tentaculat

2005-09-23T17:42:23Z

80.196.239.243:

== General Information ==
[[Image:Tentaculat.PNG|right|Tentaculat]]

Not even the depths of a Lovecraftian nightmare could spawn such as this indescribable creature. No comparison to any Earth animal exists, the environment that could produce such as this is beyond imagination. Armed with long tentacles the Tentaculat paralyses its victims then transmutes them into mindless things. These progeny can cause death on touch, even through armour. The Tentaculat is the most fearsome alien yet encountered by X-Com. Even if one of the victims is killed, somehow, they are transformed into another Tentaculat.

Then Tentaculat is nearly always spotted on alien colonies, artefact (or artifact) sites and T'leth.
*
There is ALWAYS a Tentaculant somewhere onboard/near a Dreadnaught. Beware!

Basically a flying [[Chryssalid]], but with less armor.

== Autopsy ==
[[Image:Tentaculat_Autopsy.PNG|right|Dead Tentaculat]]

The autopsy reveals small cybernetic implants are lodged in the creature's large brain. The vision system is a complex combination of visible light and thermal imaging acquisition. Even in the inky depths of the ocean this monster can navigate with unerring accuracy. There are vestigial organs that seem to be the bare minimum for survival. Each creature has a small stomach with an external connector, it is logical to assume the being is fed by direct nutrient input by its masters.

Base Facilities (TFTD)

2005-09-23T17:19:38Z

80.196.239.243:

Base Facilities (TFTD)

2005-09-23T17:18:01Z

80.196.239.243:

Base Facilities (TFTD)
From UFOpaedia
There are a number of base facilities that you can place in your installations. Some of these are available from the beginning of the game, others are gained through research. With the exception of the Airlock, and the facilites you start the game with, all require an amount of time to be built and will charge you a monthly maintanance fee on top of the initial construction costs.

All base facilities must be linked, either directly or via other base facilities, to the Airlock. While you cannot dismantle a base facility that is in use or is linking other facilities to the Airlock, it can be destroyed in the process of a Base Defense mission. If a base facility is destroyed in this way, any other base facilities that were relying on that facility as a link to the Airlock will also be destroyed. Any pieces of equipment, craft, or personal will, however, remain in the base (despite the lack of room).

Initial Base Facilities:

[[Airlock]]

Researchable Base Facilities:

[[M.C Lab]]

--Bomb Bloke 15:41, 4 Mar 2005 (GMT)

M.C Skill

2005-09-23T17:13:16Z

80.196.239.243:

M.C Skill is a rating of the effectiveness with which the aquanaut can use his inherent M.C ability.

==Starting Values==
New recruits will always begin with a value between 16 and 24. This is awarded upon completion of first month's [[M.C_Lab|M.C Lab]] training.

==Maximum Caps==
An X-COM aquanaut's M.C Skill has a combat increase cap at 100, but can continue to grow past that through M.C Lab training.

==Improvement==
Is increased through use of M.C on the battlefield, and through M.C Lab training. Both successful and unsuccessful psi attempts during combat result in improvement.

Unlike any other skills, M.C Skill is not truly capped. Although you will cease to get any more combat increases once you reach 100, you will still get approx. 2-3 skill points per month as long as you stay in Psi training. (Not that it matters... you'll never fail a mind control with a Skill of 100, if your Psi Strength is fairly high.)

Also note that M.C Lab training (for a given month) is lost if the soldier is transferred to another base, even if the destination base has M.C Lab space available.

[[Category:Aquanauts]]

M.C Skill

2005-09-23T17:12:27Z

80.196.239.243:

M.C Skill is a rating of the effectiveness with which the aquanaut can use his inherent m.c ability.

==Starting Values==
New recruits will always begin with a value between 16 and 24. This is awarded upon completion of first month's [[M.C_Lab|M.C Lab]] training.

==Maximum Caps==
An X-COM aquanaut's M.C Skill has a combat increase cap at 100, but can continue to grow past that through M.C Lab training.

==Improvement==
Is increased through use of M.C on the battlefield, and through M.C Lab training. Both successful and unsuccessful psi attempts during combat result in improvement.

Unlike any other skills, M.C Skill is not truly capped. Although you will cease to get any more combat increases once you reach 100, you will still get approx. 2-3 skill points per month as long as you stay in Psi training. (Not that it matters... you'll never fail a mind control with a Skill of 100, if your Psi Strength is fairly high.)

Also note that M.C Lab training (for a given month) is lost if the soldier is transferred to another base, even if the destination base has M.C Lab space available.

[[Category:Aquanauts]]

M.C Skill

2005-09-23T17:11:21Z

80.196.239.243:

M.C Skill is a rating of the effectiveness with which the aquanaut can use his inherent m.c ability.

==Starting Values==
New recruits will always begin with a value between 16 and 24. This is awarded upon completion of first month's [[M.C_Lab|M.C Lab]] training.

==Maximum Caps==
An X-COM aquanaut's M.C Skill has a combat increase cap at 100, but can continue to grow past that through Psi Lab training.

==Improvement==
Is increased through use of M.C on the battlefield, and through M.C Lab training. Both successful and unsuccessful psi attempts during combat result in improvement.

Unlike any other skills, M.C Skill is not truly capped. Although you will cease to get any more combat increases once you reach 100, you will still get approx. 2-3 skill points per month as long as you stay in Psi training. (Not that it matters... you'll never fail a mind control with a Skill of 100, if your Psi Strength is fairly high.)

Also note that M.C Lab training (for a given month) is lost if the soldier is transferred to another base, even if the destination base has M.C Lab space available.

[[Category:Aquanauts]]

Aquanauts

2005-09-23T17:03:26Z

80.196.239.243:

Information regarding aquanauts.
# [[Hiring/firing]]
# Stats:
#*[[TU|Time Units]]
#*[[Energy]]
#*[[Health]]
#*[[Fatal Wounds]]
#*[[Bravery]]
#*[[Morale]]
#*[[Reactions]]
#*[[Firing Accuracy]]
#*[[Throwing Accuracy]]
#*[[Strength]]
#* [[Molecular Control]]
#** [[M.C Skill]]
#** [[M.C Strength]]
# How [[Experience]] is earned.
# [[Recovery time]] after being injured in battle
# [[Raw recruit statistical likelihood]]

Main Page

2005-09-23T17:00:53Z

80.196.239.243: /* Terror from the Deep */

Welcome to UFOpaedia.

This site has been created to serve as the ultimate resource for information based around the Extra Terrestrial Combat Unit (X-COM) and its encounters with the alien invaders.

Information about all previous encounters with the alien menace will be recorded here along with helpful strategic guides for new Commanding Officers.

For new authors:
# [[Help:Getting Started | Getting Started]]
# [[Guidelines to writing articles]]

= X-COM: Main UFOpaedia Entries =
<table style="width: 100%;">
<tr style="vertical-align: top;">
<td style="width: 33%;">
=== UFO Defense ===
*[[Base Facilities (UFO Defense)|Base Facilities]]
*[[Crafts (UFO Defense)|X-COM Crafts]]
**[[Craft Armaments (UFO Defense)|Craft Armaments]]
*[[Heavy Weapons Platforms (UFO Defense)|Heavy Weapons Platforms]]
*[[Equipment (UFO Defense)|Equipment]]
**[[Weapons (UFO Defense)|Weapons]]
*[[Alien Life Forms (UFO Defense)|Alien Life Forms]]
*[[Research (UFO Defense)|Research]]
**[[Alien Artefacts (UFO Defense)|Alien Artefacts]]
*[[UFO (UFO Defense)|Unidentified Flying Objects]]
**[[UFO Components (UFO Defense)|UFO Components]]
*[[Soldiers (UFO Defense) | Soldiers]]
*[[Missions (UFO Defense) | Missions]]
*[[Scoring (UFO Defense)|Scoring]]
-----
=== Supplementary Reference ===
* [[Item Weight]]s
</td>
<td style="width: 33%;">

=== Terror from the Deep ===

*[[Base Facilities (Tftd)|Base Facilities]]
*[[Subs (Tftd)|X-COM Subs]]
**[[Sub Armaments (Tftd)|Sub Armaments]]
*[[Heavy Weapons Platforms (Tftd)|Heavy Weapons Platforms]]
*[[Equipment (Tftd)|Equipment]]
**[[Weapons (Tftd)|Weapons]]
*[[Alien Life Forms (Tftd)|Alien Life Forms]]
*[[Alien Research (Tftd)|Alien Research]]
**[[Alien Artefacts (Tftd)|Alien Artefacts]]
*[[USO (Tftd)|Unidentified Submerging Objects]]
**[[Sub Components (Tftd)|USO Components]]
*[[Aquanauts(Tftd)|Aquanauts]]
*[[Missions(Tftd)|Missions]]
*[[Scoring (Tftd)|Scoring]]
</td>
<td style="width: 33%;">

=== Apocalypse ===


* [[Mega Primus]]
** [[Base Locations]]
** [[Firms, companies, collectives]]
** [[Relations]]
** [[Trade]]
* [[Bases]]
** [[Facilities]]
** [[Layouts]]
* [[Personnel]]
**[[Agents]]
**[[Research and Development]]
* [[Personnel Equipment]]
** [[Market]]
** [[X-COM Proprietary Goods]]
** [[Alien Artifacts]]
* [[Vehicles]]
** [[Roadcars and Tanks]]
** [[Air Vehicles]]
** [[X-COM Hybrid Aircraft]]
** [[UFOs]]
* [[Vehicle Equipment]]
** [[Common]]
** [[Road]]
** [[Air]]
** [[Alien Artifacts]]
* [[Research: Lab Reports]]
** [[Biochemistry]]
** [[Quantum Physics]]
</td>
</tr>

<tr style="vertical-align: top;">
<td style="width: 33%;">

=== Interceptor ===
* [[Technologies]]
</td>
<td style="width: 33%;">
=== X-COM: Genesis ===
* [[Info(Genesis)]]
</td>
<td style="width: 33%;">

=== Alliance ===
* [[Info(Alliance)]]
</td>
</tr>
</table>

==Miscellaneous==
This section contains articles that have yet to be classified. For now, everything that doesn't seem to go anywhere will go here and will later be moved where ever they will fit in.

* [[Under The Hood]] - General odds and ends regarding UFO and TFTD.
* [[Tricks, Tips and Hints]] - Information.. "acquired" from experienced X-COM players, full of tips that can help you fight the alien menace.
* [[Exploits]] - Ever wanted to get a little upper hand on the aliens? Enter and find some help.
* [[Known Bugs]] - Beware, all you need to know about bugs with X-COM and TFTD are contained here. These will help you avoid making a fool of yourself.
* [[Background]] - Game design notes, backstory, real-life equivalents.
* [[Community]] - People in the community, memes, etc.
* [[Fiction]] - Tasty links to inspired authors.
* [[Links]] - The, y'know, rest of the Internet.

Main Page

2005-09-23T16:57:55Z

80.196.239.243:

Welcome to UFOpaedia.

This site has been created to serve as the ultimate resource for information based around the Extra Terrestrial Combat Unit (X-COM) and its encounters with the alien invaders.

Information about all previous encounters with the alien menace will be recorded here along with helpful strategic guides for new Commanding Officers.

For new authors:
# [[Help:Getting Started | Getting Started]]
# [[Guidelines to writing articles]]

= X-COM: Main UFOpaedia Entries =
<table style="width: 100%;">
<tr style="vertical-align: top;">
<td style="width: 33%;">
=== UFO Defense ===
*[[Base Facilities (UFO Defense)|Base Facilities]]
*[[Crafts (UFO Defense)|X-COM Crafts]]
**[[Craft Armaments (UFO Defense)|Craft Armaments]]
*[[Heavy Weapons Platforms (UFO Defense)|Heavy Weapons Platforms]]
*[[Equipment (UFO Defense)|Equipment]]
**[[Weapons (UFO Defense)|Weapons]]
*[[Alien Life Forms (UFO Defense)|Alien Life Forms]]
*[[Research (UFO Defense)|Research]]
**[[Alien Artefacts (UFO Defense)|Alien Artefacts]]
*[[UFO (UFO Defense)|Unidentified Flying Objects]]
**[[UFO Components (UFO Defense)|UFO Components]]
*[[Soldiers (UFO Defense) | Soldiers]]
*[[Missions (UFO Defense) | Missions]]
*[[Scoring (UFO Defense)|Scoring]]
-----
=== Supplementary Reference ===
* [[Item Weight]]s
</td>
<td style="width: 33%;">

=== Terror from the Deep ===

*[[Base Facilities (Tftd)|Base Facilities]]
*[[Subs (Tftd)|X-COM Subs]]
**[[Sub Armaments (Tftd)|Sub Armaments]]
*[[Heavy Weapons Platforms (Tftd)|Heavy Weapons Platforms]]
*[[Equipment (Tftd)|Equipment]]
**[[Weapons (Tftd)|Weapons]]
*[[Alien Life Forms (Tftd)|Alien Life Forms]]
*[[Alien Research (Tftd)|Alien Research]]
**[[Alien Artefacts (Tftd)|Alien Artefacts]]
*[[USO (Tftd)|Unidentified Submerging Objects]]
**[[Sub Components (Tftd)|USO Components]]
*[[Missions(Tftd)|Missions]]
*[[Scoring (Tftd)|Scoring]]
</td>
<td style="width: 33%;">

=== Apocalypse ===


* [[Mega Primus]]
** [[Base Locations]]
** [[Firms, companies, collectives]]
** [[Relations]]
** [[Trade]]
* [[Bases]]
** [[Facilities]]
** [[Layouts]]
* [[Personnel]]
**[[Agents]]
**[[Research and Development]]
* [[Personnel Equipment]]
** [[Market]]
** [[X-COM Proprietary Goods]]
** [[Alien Artifacts]]
* [[Vehicles]]
** [[Roadcars and Tanks]]
** [[Air Vehicles]]
** [[X-COM Hybrid Aircraft]]
** [[UFOs]]
* [[Vehicle Equipment]]
** [[Common]]
** [[Road]]
** [[Air]]
** [[Alien Artifacts]]
* [[Research: Lab Reports]]
** [[Biochemistry]]
** [[Quantum Physics]]
</td>
</tr>

<tr style="vertical-align: top;">
<td style="width: 33%;">

=== Interceptor ===
* [[Technologies]]
</td>
<td style="width: 33%;">
=== X-COM: Genesis ===
* [[Info(Genesis)]]
</td>
<td style="width: 33%;">

=== Alliance ===
* [[Info(Alliance)]]
</td>
</tr>
</table>

==Miscellaneous==
This section contains articles that have yet to be classified. For now, everything that doesn't seem to go anywhere will go here and will later be moved where ever they will fit in.

* [[Under The Hood]] - General odds and ends regarding UFO and TFTD.
* [[Tricks, Tips and Hints]] - Information.. "acquired" from experienced X-COM players, full of tips that can help you fight the alien menace.
* [[Exploits]] - Ever wanted to get a little upper hand on the aliens? Enter and find some help.
* [[Known Bugs]] - Beware, all you need to know about bugs with X-COM and TFTD are contained here. These will help you avoid making a fool of yourself.
* [[Background]] - Game design notes, backstory, real-life equivalents.
* [[Community]] - People in the community, memes, etc.
* [[Fiction]] - Tasty links to inspired authors.
* [[Links]] - The, y'know, rest of the Internet.

Research (Interceptor)

2005-09-23T16:51:46Z

80.196.239.243:

Here is the Technologies from [[The Frontier]].

* [[Second Alien War]]
* [[First Alien War]]
* [[The Frontier]]
* [[Mega Primus]]

SOLDIER.DAT

2005-09-21T14:57:48Z

80.196.239.243:

= General Notes =
SOLDIER.DAT has a fixed structure of 250 entries of 68 bytes each. (Only a maximum of 250 soldiers can be had.) Thus it is always 17,000 bytes long (250x68).

In several places it uses Intel little-endian "Words". These are two bytes values with the low byte first, high byte second. Thus they can count over 255 (to 65,536). Sometimes they are "signed" however (8000h, when the highest bit is set), which makes the maximum positive value 32,767. It's of no concern in an ordinary game, but may be to hackers. "Signed" is noted below where applicable.

Values are presented according to byte count (1 to 68) followed by the equivalent hex offset (00 to 43) in bold, followed by the normal (non-hacked) range of values in italics. Most fields can be hacked up to FF, but sometimes it can make for weirdness!

= Structure =
1-2 / 00-01 (0-5, FFFF): Word set to Rank or FFFF if soldier is dead (or slot not yet used). These values are actually pointers within a text file, so if you change it to 7 it will say "SPACE AVAILABLE" as your rank. Strange stuff. Ranks are:

0 Recruit
1 Squaddie
2 Sargeant (SGT)
3 Captain (CPT)
4 Colonel (COL)
5 Commander (CDR)
6 Units in Entrance
7 Units in Target Exit
3 / 02 (varies, FF): Base the soldier is at, using reference numbers from LOC.DAT. First base is always 0 (first entry in LOC.DAT). Value of FF means the soldier is being transferred.

5-6 / 04-05 (varies, FFFF): Craft soldier is assigned to, using values from LOC.DAT. FFFF means not assigned to a craft.

7-8 / 06-07 (FFFF): Unknown. Presumed Word. Only ever seen to be FFFF.

9-10 / 08-09 (0+): Number of missions. Signed Word.

11-12 / 0A-0B (0+): Number of kills. Signed Word.

13-14 / 0C-0D (0+): Wound recovery days. Signed Word.

15-16 / 0E-0F (20+): Death Penalty (morale hit if this guy dies). Presumably a signed Word. Is equal to 20 + Missions + Rank Bonus, as follows:

0 Recruit
0? Squaddie (not yet tested)
1 SGT
3 CPT
6 COL
10 CDR

Note: A test of hex-editing Missions and performing a combat (while not touching this field) did not cause this field to reflect the edited Missions value. This field simply added 1, as it normally would. So it doesn't appear to be computed from Missions; instead, both Missions and this field have a 1 added at the end of each mission. Presumably then, directly editing Rank would likewise not cause this to change.

17-37 / 10-24 (Text): Name, 21 characters long. Note that players can enter almost any keyboard character (unlike in Windows programs) because they are directly stored here instead of going through any Windows objects. Also FWIW, the 'ends' of player names are still kept here, if a new soldier in a slot has a shorter name than the previous soldier. The end of the current name is denoted by a null character (ASCII 00).

38-41 / 25-28 (0): Unknown. Four bytes that have only ever been seen to be 0, 0, 0, 0. Two unused Words?

42 / 29 (varies): Always 0 except for existing soldiers being transferred, in which case it equals the LOC.DAT value for destination base. New hirees on their way to a base will also have this set to 0, so if Byte 3 is set to FF and this byte is 0, you can't tell (from these two bytes alone) if it's an existing soldier going to your first base (LOC.DAT=0), or a new recruit going to any base. But the game knows where they're going, presumably via TRANSFER.DAT.

43 / 2A (50-60): Initial TUs.

44 / 2B (25-40): Initial Health.

45 / 2C (40-70): Initial Stamina.

46 / 2D (30-60): Initial Reaction.

47 / 2E (20-40): Initial Strength.

48 / 2F (40-70): Initial Firing Accuracy.

49 / 30 (50-80): Initial Throwing Accuracy.

50 / 31 (20-40): Initial Melee / Close Combat Accuracy. See Note 1.

51 / 32 (0-100): Psi Strength.

53 / 34 (5-10): Initial Bravery. Computed as 110-(10*ThisByte). E.g. if ThisByte=9, Bravery=20. So the lower this byte is, the better your Bravery is. Initial Bravery can be 10-60. Bravery always works in units of 10.

52 / 33 (0-100+): Current Psi Skill. 0 = has not yet had any Psi Lab training.

54 / 35 (0-30+): Increase in TUs. (Max total TUs possible (initial+increase) is approximately 80. See Note 2.)

55 / 36 (0-35+): Increase in Health. (Max total approx. 60)

56 / 37 (0-60+): Increase in Stamina. (Max total approx. 100)

57 / 38 (0-60+): Increase in Reaction. (Max total approx. 90)

58 / 39 (0-50+): Increase in Strength. (Max total approx. 70). Note that more than 64 here will make you unable to throw anything. Possibly the [[Throwing_Accuracy#Throwing_Distance|throwing distance]] function only checks the lowest 6(?) bits of current strength, or a high value otherwise pushes the XCOM equation out of allowable bounds.

59 / 3A (0-80+): Increase in Firing Accuracy. (Max total approx. 120)

60 / 3B (0-70?): Increase in Throwing Accuracy. (Max total approx. 120?)

61 / 3C (0-?): Increase in Melee/Close Combat Accuracy. See Note 1.

62 / 3D (0-1?): Increase in Bravery (multiply by 10).

63 / 3E (0-3): Armor. 0=None, 1=Personal Armor, 2=Power Armor, 3=Flying Suit, 4=Sectoid 5=Snakeman, 6=Ethereal, 7=Muton, 8=Floater, 9=Celatid, 10=Silacoid, 11=Chryssalid. (the rest is just parts of the big units and civilians)NOTE: theese are not real aliens... just skins... more research must be taken about skins... like the appearance... or gender to find real aliens.

64 / 3F (0-24?): Most-recent month's Psi Lab training increase. Largest values for newly trained (16-24).

65 / 40 (0,1): In Psi Lab training.

66 / 41 (0,1): Promotion flag (as of most recent combat). Reset as of next combat.

67 / 42 (0,1): 0=Male, 1=Female, 2=???.

68 / 43 (0-3): Appearance (for loadout, no armor): 0=blonde, 1=brown hair, 2=Oriental, 3=African, 4=???.

= Notes =

1) Melee or Close Combat Accuracy is a somewhat abandoned skill. It does not appear in display screens, but Byte 61 does increase when the stun rod is used. Also, secondary skills will increase when you do this, as they do for other primary skills. Given their placement in this file, then, it is presumed that this is a third 'accuracy' skill related to stun-rod use, with Byte 50 being the initial value and Byte 61 being the increase.

2) The possible values for skill increases (in a non-hacked game) depend both on the cap for each skill and on each soldiers' initial value. Thus the max possible value shown in the 'increase' range is for soldiers who started with the minimum initial skill.

3) Be careful of making total skill value (initial + increase) greater than 160 (A0h). This will make your skill bar wrap around the screen.

4) As can be seen, Armor is the only thing that 'stays with' a soldier. Yes, it's lost if you fire someone wearing it!

5) This work was done by [http://www.stonepool.com/xcom/hacking/soldier.html hatfarm] and [[User:MikeTheRed|MikeTheRed]]. More info welcomed!

= For More Information =

*Information on individual skills can be seen at [[Soldiers (UFO Defense) | Soldiers]].
*For more information on increasing skills, see [[Experience]].
*For more information on starting soldier stats, see [[Raw_recruit_statistical_likelihood|Raw Recruit Statistical Likelihood]].

= Addendum: Hex Workshop Structure Library =

The following can be used to make an XCOMUFO.hsl file that will work with Hex Workshop (v4.23) available from [http://www.bpsoft.com www.BPSoft.com]. This allows one to overlay a structure while viewing/editing SOLDIER.DAT and work in a more organized fashion. Tip: Set the data view window to 34 bytes wide, and each SOLDIER record will take exactly two display lines. (It won't let you set it to higher than 64, unfortunately.)

/***********************************************************************************
* XCOMUFO.hsl - Structure definitions for XCOM UFO DEFENSE v1.4
* This structure def last edited Sept. 16, 2005
* Mike Fay mikestar@speedfactory.net
* MikeTheRed on www.xcomufo.com forums
* Also see the SOLDIER.DAT wiki at www.ufopaedia.org/index.php?title=SOLDIER.DAT
***********************************************************************************
* Revision History:
* 09/26/05 - MF - Original
*/

#include "standard-types.hsl"

// SOLDIER.DAT
struct SOLDIER_DAT
{
WORD Rank ;
WORD BaseOrTransfer ;
WORD Craft ;
WORD UnknownFFFF;
WORD Missions ;
WORD Kills ;
WORD WoundDays ;
WORD DeathPenalty ;
CHAR Name[21] ;
WORD UnknownUnused1 ;
WORD UnknownUnused2 ;
UBYTE TransferBase ;
UBYTE TUs_Init ;
UBYTE Health_Init ;
UBYTE Stam_Init ;
UBYTE Rxns_Init ;
UBYTE Str_Init ;
UBYTE FAcc_Init ;
UBYTE TAcc_Init ;
UBYTE MAcc_Init ;
UBYTE Psi_Str ;
UBYTE Psi_Skill ;
UBYTE Brave_Init ;
UBYTE TUs_Inc ;
UBYTE Health_Inc ;
UBYTE Stam_Inc ;
UBYTE Rxns_Inc ;
UBYTE Str_Inc ;
UBYTE FAcc_Inc ;
UBYTE TAcc_Inc ;
UBYTE MAcc_Inc ;
UBYTE Brave_Inc ;
UBYTE Armor ;
UBYTE PsiLab_Inc ;
UBYTE PsiLab_Flag ;
UBYTE Promotion_Flag ;
UBYTE Gender ;
UBYTE Appearance ;
} ;

SOLDIER.DAT

2005-09-21T14:55:38Z

80.196.239.243: /* Structure */

= General Notes =
SOLDIER.DAT has a fixed structure of 250 entries of 68 bytes each. (Only a maximum of 250 soldiers can be had.) Thus it is always 17,000 bytes long (250x68).

In several places it uses Intel little-endian "Words". These are two bytes values with the low byte first, high byte second. Thus they can count over 255 (to 65,536). Sometimes they are "signed" however (8000h, when the highest bit is set), which makes the maximum positive value 32,767. It's of no concern in an ordinary game, but may be to hackers. "Signed" is noted below where applicable.

Values are presented according to byte count (1 to 68) followed by the equivalent hex offset (00 to 43) in bold, followed by the normal (non-hacked) range of values in italics. Most fields can be hacked up to FF, but sometimes it can make for weirdness!

= Structure =
1-2 / 00-01 (0-5, FFFF): Word set to Rank or FFFF if soldier is dead (or slot not yet used). These values are actually pointers within a text file, so if you change it to 7 it will say "SPACE AVAILABLE" as your rank. Strange stuff. Ranks are:

0 Recruit
1 Squaddie
2 Sargeant (SGT)
3 Captain (CPT)
4 Colonel (COL)
5 Commander (CDR)
6 Units in Entrance
7 Units in Target Exit
3 / 02 (varies, FF): Base the soldier is at, using reference numbers from LOC.DAT. First base is always 0 (first entry in LOC.DAT). Value of FF means the soldier is being transferred.

5-6 / 04-05 (varies, FFFF): Craft soldier is assigned to, using values from LOC.DAT. FFFF means not assigned to a craft.

7-8 / 06-07 (FFFF): Unknown. Presumed Word. Only ever seen to be FFFF.

9-10 / 08-09 (0+): Number of missions. Signed Word.

11-12 / 0A-0B (0+): Number of kills. Signed Word.

13-14 / 0C-0D (0+): Wound recovery days. Signed Word.

15-16 / 0E-0F (20+): Death Penalty (morale hit if this guy dies). Presumably a signed Word. Is equal to 20 + Missions + Rank Bonus, as follows:

0 Recruit
0? Squaddie (not yet tested)
1 SGT
3 CPT
6 COL
10 CDR

Note: A test of hex-editing Missions and performing a combat (while not touching this field) did not cause this field to reflect the edited Missions value. This field simply added 1, as it normally would. So it doesn't appear to be computed from Missions; instead, both Missions and this field have a 1 added at the end of each mission. Presumably then, directly editing Rank would likewise not cause this to change.

17-37 / 10-24 (Text): Name, 21 characters long. Note that players can enter almost any keyboard character (unlike in Windows programs) because they are directly stored here instead of going through any Windows objects. Also FWIW, the 'ends' of player names are still kept here, if a new soldier in a slot has a shorter name than the previous soldier. The end of the current name is denoted by a null character (ASCII 00).

38-41 / 25-28 (0): Unknown. Four bytes that have only ever been seen to be 0, 0, 0, 0. Two unused Words?

42 / 29 (varies): Always 0 except for existing soldiers being transferred, in which case it equals the LOC.DAT value for destination base. New hirees on their way to a base will also have this set to 0, so if Byte 3 is set to FF and this byte is 0, you can't tell (from these two bytes alone) if it's an existing soldier going to your first base (LOC.DAT=0), or a new recruit going to any base. But the game knows where they're going, presumably via TRANSFER.DAT.

43 / 2A (50-60): Initial TUs.

44 / 2B (25-40): Initial Health.

45 / 2C (40-70): Initial Stamina.

46 / 2D (30-60): Initial Reaction.

47 / 2E (20-40): Initial Strength.

48 / 2F (40-70): Initial Firing Accuracy.

49 / 30 (50-80): Initial Throwing Accuracy.

50 / 31 (20-40): Initial Melee / Close Combat Accuracy. See Note 1.

51 / 32 (0-100): Psi Strength.

53 / 34 (5-10): Initial Bravery. Computed as 110-(10*ThisByte). E.g. if ThisByte=9, Bravery=20. So the lower this byte is, the better your Bravery is. Initial Bravery can be 10-60. Bravery always works in units of 10.

52 / 33 (0-100+): Current Psi Skill. 0 = has not yet had any Psi Lab training.

54 / 35 (0-30+): Increase in TUs. (Max total TUs possible (initial+increase) is approximately 80. See Note 2.)

55 / 36 (0-35+): Increase in Health. (Max total approx. 60)

56 / 37 (0-60+): Increase in Stamina. (Max total approx. 100)

57 / 38 (0-60+): Increase in Reaction. (Max total approx. 90)

58 / 39 (0-50+): Increase in Strength. (Max total approx. 70). Note that more than 64 here will make you unable to throw anything. Possibly the [[Throwing_Accuracy#Throwing_Distance|throwing distance]] function only checks the lowest 6(?) bits of current strength, or a high value otherwise pushes the XCOM equation out of allowable bounds.

59 / 3A (0-80+): Increase in Firing Accuracy. (Max total approx. 120)

60 / 3B (0-70?): Increase in Throwing Accuracy. (Max total approx. 120?)

61 / 3C (0-?): Increase in Melee/Close Combat Accuracy. See Note 1.

62 / 3D (0-1?): Increase in Bravery (multiply by 10).

63 / 3E (0-3): Armor. 0=None, 1=Personal Armor, 2=Power Armor, 3=Flying Suit, 4=Sectoid 5=Snakeman, 6=Ethereal, 7=Muton, 8=Floater, 9=Celatid, 10=Silacoid, 11=Chryssalid. (the rest is just parts of the big units and civilians)NOTE: theese are not real aliens... just skins... mor research must be taken about skinds... like the appearance... or gender to find real aliens

64 / 3F (0-24?): Most-recent month's Psi Lab training increase. Largest values for newly trained (16-24).

65 / 40 (0,1): In Psi Lab training.

66 / 41 (0,1): Promotion flag (as of most recent combat). Reset as of next combat.

67 / 42 (0,1): 0=Male, 1=Female, 2=???.

68 / 43 (0-3): Appearance (for loadout, no armor): 0=blonde, 1=brown hair, 2=Oriental, 3=African, 4=???.

= Notes =

1) Melee or Close Combat Accuracy is a somewhat abandoned skill. It does not appear in display screens, but Byte 61 does increase when the stun rod is used. Also, secondary skills will increase when you do this, as they do for other primary skills. Given their placement in this file, then, it is presumed that this is a third 'accuracy' skill related to stun-rod use, with Byte 50 being the initial value and Byte 61 being the increase.

2) The possible values for skill increases (in a non-hacked game) depend both on the cap for each skill and on each soldiers' initial value. Thus the max possible value shown in the 'increase' range is for soldiers who started with the minimum initial skill.

3) Be careful of making total skill value (initial + increase) greater than 160 (A0h). This will make your skill bar wrap around the screen.

4) As can be seen, Armor is the only thing that 'stays with' a soldier. Yes, it's lost if you fire someone wearing it!

5) This work was done by [http://www.stonepool.com/xcom/hacking/soldier.html hatfarm] and [[User:MikeTheRed|MikeTheRed]]. More info welcomed!

= For More Information =

*Information on individual skills can be seen at [[Soldiers (UFO Defense) | Soldiers]].
*For more information on increasing skills, see [[Experience]].
*For more information on starting soldier stats, see [[Raw_recruit_statistical_likelihood|Raw Recruit Statistical Likelihood]].

= Addendum: Hex Workshop Structure Library =

The following can be used to make an XCOMUFO.hsl file that will work with Hex Workshop (v4.23) available from [http://www.bpsoft.com www.BPSoft.com]. This allows one to overlay a structure while viewing/editing SOLDIER.DAT and work in a more organized fashion. Tip: Set the data view window to 34 bytes wide, and each SOLDIER record will take exactly two display lines. (It won't let you set it to higher than 64, unfortunately.)

/***********************************************************************************
* XCOMUFO.hsl - Structure definitions for XCOM UFO DEFENSE v1.4
* This structure def last edited Sept. 16, 2005
* Mike Fay mikestar@speedfactory.net
* MikeTheRed on www.xcomufo.com forums
* Also see the SOLDIER.DAT wiki at www.ufopaedia.org/index.php?title=SOLDIER.DAT
***********************************************************************************
* Revision History:
* 09/26/05 - MF - Original
*/

#include "standard-types.hsl"

// SOLDIER.DAT
struct SOLDIER_DAT
{
WORD Rank ;
WORD BaseOrTransfer ;
WORD Craft ;
WORD UnknownFFFF;
WORD Missions ;
WORD Kills ;
WORD WoundDays ;
WORD DeathPenalty ;
CHAR Name[21] ;
WORD UnknownUnused1 ;
WORD UnknownUnused2 ;
UBYTE TransferBase ;
UBYTE TUs_Init ;
UBYTE Health_Init ;
UBYTE Stam_Init ;
UBYTE Rxns_Init ;
UBYTE Str_Init ;
UBYTE FAcc_Init ;
UBYTE TAcc_Init ;
UBYTE MAcc_Init ;
UBYTE Psi_Str ;
UBYTE Psi_Skill ;
UBYTE Brave_Init ;
UBYTE TUs_Inc ;
UBYTE Health_Inc ;
UBYTE Stam_Inc ;
UBYTE Rxns_Inc ;
UBYTE Str_Inc ;
UBYTE FAcc_Inc ;
UBYTE TAcc_Inc ;
UBYTE MAcc_Inc ;
UBYTE Brave_Inc ;
UBYTE Armor ;
UBYTE PsiLab_Inc ;
UBYTE PsiLab_Flag ;
UBYTE Promotion_Flag ;
UBYTE Gender ;
UBYTE Appearance ;
} ;

Game Files

2005-09-21T14:52:45Z

80.196.239.243:

*[[SOLDIER.DAT]]
*[[CRAFT.DAT]]

SOLDIER.DAT

2005-09-21T14:47:56Z

80.196.239.243: /* Structure */ added more info to data corruption

= General Notes =
SOLDIER.DAT has a fixed structure of 250 entries of 68 bytes each. (Only a maximum of 250 soldiers can be had.) Thus it is always 17,000 bytes long (250x68).

In several places it uses Intel little-endian "Words". These are two bytes values with the low byte first, high byte second. Thus they can count over 255 (to 65,536). Sometimes they are "signed" however (8000h, when the highest bit is set), which makes the maximum positive value 32,767. It's of no concern in an ordinary game, but may be to hackers. "Signed" is noted below where applicable.

Values are presented according to byte count (1 to 68) followed by the equivalent hex offset (00 to 43) in bold, followed by the normal (non-hacked) range of values in italics. Most fields can be hacked up to FF, but sometimes it can make for weirdness!

= Structure =
1-2 / 00-01 (0-5, FFFF): Word set to Rank or FFFF if soldier is dead (or slot not yet used). These values are actually pointers within a text file, so if you change it to 7 it will say "SPACE AVAILABLE" as your rank. Strange stuff. Ranks are:

0 Recruit
1 Squaddie
2 Sargeant (SGT)
3 Captain (CPT)
4 Colonel (COL)
5 Commander (CDR)
6 Units in Entrance
7 Units in Target Exit
3 / 02 (varies, FF): Base the soldier is at, using reference numbers from LOC.DAT. First base is always 0 (first entry in LOC.DAT). Value of FF means the soldier is being transferred.

5-6 / 04-05 (varies, FFFF): Craft soldier is assigned to, using values from LOC.DAT. FFFF means not assigned to a craft.

7-8 / 06-07 (FFFF): Unknown. Presumed Word. Only ever seen to be FFFF.

9-10 / 08-09 (0+): Number of missions. Signed Word.

11-12 / 0A-0B (0+): Number of kills. Signed Word.

13-14 / 0C-0D (0+): Wound recovery days. Signed Word.

15-16 / 0E-0F (20+): Death Penalty (morale hit if this guy dies). Presumably a signed Word. Is equal to 20 + Missions + Rank Bonus, as follows:

0 Recruit
0? Squaddie (not yet tested)
1 SGT
3 CPT
6 COL
10 CDR

Note: A test of hex-editing Missions and performing a combat (while not touching this field) did not cause this field to reflect the edited Missions value. This field simply added 1, as it normally would. So it doesn't appear to be computed from Missions; instead, both Missions and this field have a 1 added at the end of each mission. Presumably then, directly editing Rank would likewise not cause this to change.

17-37 / 10-24 (Text): Name, 21 characters long. Note that players can enter almost any keyboard character (unlike in Windows programs) because they are directly stored here instead of going through any Windows objects. Also FWIW, the 'ends' of player names are still kept here, if a new soldier in a slot has a shorter name than the previous soldier. The end of the current name is denoted by a null character (ASCII 00).

38-41 / 25-28 (0): Unknown. Four bytes that have only ever been seen to be 0, 0, 0, 0. Two unused Words?

42 / 29 (varies): Always 0 except for existing soldiers being transferred, in which case it equals the LOC.DAT value for destination base. New hirees on their way to a base will also have this set to 0, so if Byte 3 is set to FF and this byte is 0, you can't tell (from these two bytes alone) if it's an existing soldier going to your first base (LOC.DAT=0), or a new recruit going to any base. But the game knows where they're going, presumably via TRANSFER.DAT.

43 / 2A (50-60): Initial TUs.

44 / 2B (25-40): Initial Health.

45 / 2C (40-70): Initial Stamina.

46 / 2D (30-60): Initial Reaction.

47 / 2E (20-40): Initial Strength.

48 / 2F (40-70): Initial Firing Accuracy.

49 / 30 (50-80): Initial Throwing Accuracy.

50 / 31 (20-40): Initial Melee / Close Combat Accuracy. See Note 1.

51 / 32 (0-100): Psi Strength.

53 / 34 (5-10): Initial Bravery. Computed as 110-(10*ThisByte). E.g. if ThisByte=9, Bravery=20. So the lower this byte is, the better your Bravery is. Initial Bravery can be 10-60. Bravery always works in units of 10.

52 / 33 (0-100+): Current Psi Skill. 0 = has not yet had any Psi Lab training.

54 / 35 (0-30+): Increase in TUs. (Max total TUs possible (initial+increase) is approximately 80. See Note 2.)

55 / 36 (0-35+): Increase in Health. (Max total approx. 60)

56 / 37 (0-60+): Increase in Stamina. (Max total approx. 100)

57 / 38 (0-60+): Increase in Reaction. (Max total approx. 90)

58 / 39 (0-50+): Increase in Strength. (Max total approx. 70). Note that more than 64 here will make you unable to throw anything. Possibly the [[Throwing_Accuracy#Throwing_Distance|throwing distance]] function only checks the lowest 6(?) bits of current strength, or a high value otherwise pushes the XCOM equation out of allowable bounds.

59 / 3A (0-80+): Increase in Firing Accuracy. (Max total approx. 120)

60 / 3B (0-70?): Increase in Throwing Accuracy. (Max total approx. 120?)

61 / 3C (0-?): Increase in Melee/Close Combat Accuracy. See Note 1.

62 / 3D (0-1?): Increase in Bravery (multiply by 10).

63 / 3E (0-3): Armor. 0=None, 1=Personal Armor, 2=Power Armor, 3=Flying Suit 4=Sectoid 5=Snakeman
6=Ethereal 7=Muton 8=Floater 9=Celatid 10=Silacoid 11=Chryssalid (the rest is just parts of the big units and civilians)

64 / 3F (0-24?): Most-recent month's Psi Lab training increase. Largest values for newly trained (16-24).

65 / 40 (0,1): In Psi Lab training.

66 / 41 (0,1): Promotion flag (as of most recent combat). Reset as of next combat.

67 / 42 (0,1): 0=Male, 1=Female.

68 / 43 (0-3): Appearance (for loadout, no armor): 0=blonde, 1=brown hair, 2=Oriental, 3=African.

= Notes =

1) Melee or Close Combat Accuracy is a somewhat abandoned skill. It does not appear in display screens, but Byte 61 does increase when the stun rod is used. Also, secondary skills will increase when you do this, as they do for other primary skills. Given their placement in this file, then, it is presumed that this is a third 'accuracy' skill related to stun-rod use, with Byte 50 being the initial value and Byte 61 being the increase.

2) The possible values for skill increases (in a non-hacked game) depend both on the cap for each skill and on each soldiers' initial value. Thus the max possible value shown in the 'increase' range is for soldiers who started with the minimum initial skill.

3) Be careful of making total skill value (initial + increase) greater than 160 (A0h). This will make your skill bar wrap around the screen.

4) As can be seen, Armor is the only thing that 'stays with' a soldier. Yes, it's lost if you fire someone wearing it!

5) This work was done by [http://www.stonepool.com/xcom/hacking/soldier.html hatfarm] and [[User:MikeTheRed|MikeTheRed]]. More info welcomed!

= For More Information =

*Information on individual skills can be seen at [[Soldiers (UFO Defense) | Soldiers]].
*For more information on increasing skills, see [[Experience]].
*For more information on starting soldier stats, see [[Raw_recruit_statistical_likelihood|Raw Recruit Statistical Likelihood]].

= Addendum: Hex Workshop Structure Library =

The following can be used to make an XCOMUFO.hsl file that will work with Hex Workshop (v4.23) available from [http://www.bpsoft.com www.BPSoft.com]. This allows one to overlay a structure while viewing/editing SOLDIER.DAT and work in a more organized fashion. Tip: Set the data view window to 34 bytes wide, and each SOLDIER record will take exactly two display lines. (It won't let you set it to higher than 64, unfortunately.)

/***********************************************************************************
* XCOMUFO.hsl - Structure definitions for XCOM UFO DEFENSE v1.4
* This structure def last edited Sept. 16, 2005
* Mike Fay mikestar@speedfactory.net
* MikeTheRed on www.xcomufo.com forums
* Also see the SOLDIER.DAT wiki at www.ufopaedia.org/index.php?title=SOLDIER.DAT
***********************************************************************************
* Revision History:
* 09/26/05 - MF - Original
*/

#include "standard-types.hsl"

// SOLDIER.DAT
struct SOLDIER_DAT
{
WORD Rank ;
WORD BaseOrTransfer ;
WORD Craft ;
WORD UnknownFFFF;
WORD Missions ;
WORD Kills ;
WORD WoundDays ;
WORD DeathPenalty ;
CHAR Name[21] ;
WORD UnknownUnused1 ;
WORD UnknownUnused2 ;
UBYTE TransferBase ;
UBYTE TUs_Init ;
UBYTE Health_Init ;
UBYTE Stam_Init ;
UBYTE Rxns_Init ;
UBYTE Str_Init ;
UBYTE FAcc_Init ;
UBYTE TAcc_Init ;
UBYTE MAcc_Init ;
UBYTE Psi_Str ;
UBYTE Psi_Skill ;
UBYTE Brave_Init ;
UBYTE TUs_Inc ;
UBYTE Health_Inc ;
UBYTE Stam_Inc ;
UBYTE Rxns_Inc ;
UBYTE Str_Inc ;
UBYTE FAcc_Inc ;
UBYTE TAcc_Inc ;
UBYTE MAcc_Inc ;
UBYTE Brave_Inc ;
UBYTE Armor ;
UBYTE PsiLab_Inc ;
UBYTE PsiLab_Flag ;
UBYTE Promotion_Flag ;
UBYTE Gender ;
UBYTE Appearance ;
} ;