UFOpaedia - User contributions [en]

ENGLISH2.DAT (TFTD)

2010-10-28T18:32:00Z

Hatfarm:

ENGLISH2.DAT (TFTD)

2010-10-28T04:36:11Z

Hatfarm: Created page with "These files contain the strings used by the tactical game engine. Each string is terminated by a null character (x00). Line breaks are defined by x0A, though in ..."

Tactical String Files

2010-10-28T04:32:56Z

Hatfarm:

These files contain the strings used by the [[TACTICAL.EXE|tactical game engine]]. Each string is terminated by a null character (x00). Line breaks are defined by x0A, though in these files, that symbol is only used by index 26.

There are 183 entries in all, not all of which are used by the release version of the game.

{| {{StdDescTable}}
|- {{StdDescTable_Heading}}
! Index !! English2.Dat (2272 Bytes) !! French2.Dat (2724 Bytes) !! German2.Dat (2695 Bytes)
|-
| 000/x00 || UNIT> || UNITE> || EINHEIT>
|-
| 001/x01 || TIME UNITS || UNITES DE TEMPS || ZEITEINHEITEN
|-
| 002/x02 || ENERGY || ENERGIE || ENERGIE
|-
| 003/x03 || HEALTH || SANTE || GESUNDHEIT
|-
| 004/x04 || REACTIONS || REACTIONS || REAKTION
|-
| 005/x05 || FIRING ACCURACY || PRECISION AU TIR || SCHUSSGENAUIGKEIT
|-
| 006/x06 || THROWING ACCURACY || PRECISION AU LANCER || WURFGENAUIGKEIT
|-
| 007/x07 || MORALE || MORAL || MORAL
|-
| 008/x08 || ARMOUR> || ARMURE> || RšSTUNG>
|-
| 009/x09 || FRONT ARMOUR || ARMURE AVANT || RšSTUNG VORN
|-
| 010/x0A || LEFT ARMOUR || ARMURE GAUCHE || RšSTUNG LINKS
|-
| 011/x0B || RIGHT ARMOUR || ARMURE DROITE || RšSTUNG RECHTS
|-
| 012/x0C || REAR ARMOUR || ARMURE ARRIERE || RšSTUNG HINTEN
|-
| 013/x0D || SKILLS> || COMPETENCES> || FŽHIGKEITEN>
|-
| 014/x0E || LEVEL> || NIVEAU> || LEVEL>
|-
| 015/x0F || HEAD || TETE || KOPF
|-
| 016/x10 || TORSO || TORSE || RUMPF
|-
| 017/x11 || RIGHT ARM || BRAS DROIT || RECHTER ARM
|-
| 018/x12 || LEFT ARM || BRAS GAUCHE || LINKER ARM
|-
| 019/x13 || RIGHT LEG || JAMBE DROITE || RECHTES BEIN
|-
| 020/x14 || LEFT LEG || JAMBE GAUCHE || LINKES BEIN
|-
| 021/x15 || PAIN KILLER || CALMANT || SCHMERZMITTEL
|-
| 022/x16 || STIMULANT || STIMULANT || STIMULANS
|-
| 023/x17 || HEAL || SOIGNER || HEILEN
|-
| 024/x18 || TUs> || UT> || ZE>
|-
| 025/x19 || Alien Artefact || Objet alien || Auáerirdisches Artefakt
|-
| 026/x1A || AMMO: ROUNDS LEFT= || MUNITIONS: CARTOUCHES RESTANTES= || MUNITION: VERBLEIBENDE SCHšSSE=
|-
| 027/x1B || GROUND || TERRAIN || BODEN
|-
| 028/x1C || Throw || Lancer || Werfen
|-
| 029/x1D || Auto Shot || Tir Automatique || Auto-Schuá
|-
| 030/x1E || Snap Shot || Tir Instantan‚ || Schnellschuá
|-
| 031/x1F || Aimed Shot || Tir Vis‚ || Zielschuá
|-
| 032/x20 || Open || Ouvert || Offen
|-
| 033/x21 || Close || Ferm‚ || Geschlossen
|-
| 034/x22 || Stun || Frapper || Treffer
|-
| 035/x23 || Prime Grenade || Amorcer Grenade || Granate scharf machen
|-
| 036/x24 || Use Scanner || Utiliser Scanner || Scanner einsetzen
|-
| 037/x25 || Use Medi-kit || Utiliser Trousse de Soins || Sani-Tasche nutzen
|-
| 038/x26 || Launch Missile || Lancer Missile || Rakete feuern
|-
| 039/x27 || Acc> || Pr‚> || Gen>
|-
| 040/x28 || TUs> || UT> || ZE>
|-
| 041/x29 || Not Enough Time Units! || Pas Assez d'Unit‚s de Temps! || Nicht genug Zeiteinheiten!
|-
| 042/x2A || Not Enough Energy! || Pas Assez d'Energie! || Nicht genug Energie!
|-
| 043/x2B || No Rounds left! || Plus de Munitions! || Nicht genug Munition!
|-
| 044/x2C || No Ammunition Loaded! || Pas de Munitions Charg‚es! || Keine Munition geladen!
|-
| 045/x2D || Wrong Ammunition for this Weapon! || Mauvaise Munition pour cette Arme! || Falsche Munition fr diese Waffe!
|-
| 046/x2E || Weapon is already loaded! || L'Arme est D‚j… Charg‚e! || Waffe ist bereits geladen!
|-
| 047/x2F || No Line of Fire! || Pas de Ligne de Tir! || Keine Visierlinie!
|-
| 048/x30 || Grenade is Activated! || La Grenade est Activ‚e! || Granate ist aktiviert!
|-
| 049/x31 || There is no one there! || Il n'y a Personne ici! || Dort ist niemand!
|-
| 050/x32 || Unable to use alien artefact until researched! || Impossible d'Utiliser Objet Alien avant son Etude! || Artefakt muá erst untersucht werden!
|-
| 051/x33 || Out of Range! || Hors de Port‚e! || Auáer Reichweite!
|-
| 052/x34 || Unable to throw here! || Impossible de Lancer … cet Endroit! || Kann hier nicht werfen!
|-
| 053/x35 || Number of Rounds? || Nombre de Cartouches? || Anzahl der Schsse?
|-
| 054/x36 || Set Timer || D‚tonateur || Zeit einstellen
|-
| 055/x37 || HIDDEN MOVEMENT || DEPLACEMENT CACHE || VERSTECKTE BEWEGUNG
|-
| 056/x38 || TURN> || TOUR> || RUNDE>
|-
| 057/x39 || SIDE> || CAMP> || SEITE>
|-
| 058/x3A || UFO || OVNI || UFO
|-
| 059/x3B || Press button to continue || Appuyez sur le bouton pour continuer || Zum Fortfahren Knopf drcken
|-
| 060/x3C || Mind Control || Contr“le de l'Esprit || Gedankenkontrolle
|-
| 061/x3D || Panic Unit || Panique de l'Unit‚ || Einheit in Panik strzen
|-
| 062/x3E || Mind Control Successful || Contr“le de l'Esprit R‚ussi || Gedankenkontrolle erfolgreich
|-
| 063/x3F || has gone Beserk || est devenu Fou || hat einen Tobsuchtsanfall
|-
| 064/x40 || Has Panicked || A Paniqu‚ || ist in Panik ausgebrochen
|-
| 065/x41 || Xcom || Xcom || XCom
|-
| 066/x42 || Aliens || Aliens || Auáerirdische
|-
| 067/x43 || RIGHT HAND || MAIN DROITE || RECHTE HAND
|-
| 068/x44 || LEFT HAND || MAIN GAUCHE || LINKE HAND
|-
| 069/x45 || RIGHT LEG || JAMBE DROITE || RECHTES BEIN
|-
| 070/x46 || LEFT LEG || JAMBE GAUCHE || LINKES BEIN
|-
| 071/x47 || RIGHT SHOULDER || EPAULE DROITE || RECHTE SCHULTER
|-
| 072/x48 || LEFT SHOULDER || EPAULE GAUCHE || LINKE SCHULTER
|-
| 073/x49 || BACK PACK || SAC A DOS || RUCKSACK
|-
| 074/x4A || BELT || CEINTURE || GšRTEL
|-
| 075/x4B || is under alien control || est sous contr“le alien || wird von den Auáerirdischen kontrolliert
|-
| 076/x4C || TOO MANY BUTTONS || TROP DE BOUTONS || ZU VIELE KN™PFE
|-
| 077/x4D || OK || OK || OK
|-
| 078/x4E || GAME OPTIONS || OPTIONS DE JEU || SPIELOPTIONEN
|-
| 079/x4F || SCROLL SPEED || VITESSE DE DEFILEMENT || SCROLLGESCHWINDIGKEIT
|-
| 080/x50 || SCROLL TYPE || TYPE DE DEFILEMENT || SCROLL-ART
|-
| 081/x51 || TRIGGER SCROLL || DEFILEMENT MANUEL || MANUELLES SCROLLEN
|-
| 082/x52 || AUTO-SCROLL || DEFILEMENT AUTOMATIQUE || AUTOM. SCROLLEN
|-
| 083/x53 || FIRE SPEED || VITESSE DE TIR || FEUERRATE
|-
| 084/x54 || XCOM MOVEMENT SPEED || VITESSE DE DEPLACEMENT XCOM || GESCHWINDIGKEIT DER XCOM
|-
| 085/x55 || ALIEN MOVEMENT SPEED || VITESSE DE DEPLACEMENT ALIEN || GESCHWINDIGKEIT DER AUSSERIRDISCHEN
|-
| 086/x56 || SAVE GAME || SAUVEGARDER JEU || SPIEL SICHERN
|-
| 087/x57 || Select save position || S‚lectionner position de sauvegarde || Speicherplatz w„hlen
|-
| 088/x58 || CANCEL || ANNULER || ABBRECHEN
|-
| 089/x59 || Name || Nom || Name
|-
| 090/x5A || Time || Temps || Zeit
|-
| 091/x5B || Date || Date || Datum
|-
| 092/x5C || st || || .
|-
| 093/x5D || nd || || .
|-
| 094/x5E || rd || || .
|-
| 095/x5F || th || || .
|-
| 096/x60 || Jan || Jan || Jan
|-
| 097/x61 || Feb || F‚v || Feb
|-
| 098/x62 || Mar || Mar || M„r
|-
| 099/x63 || Apr || Avr || Apr
|-
| 100/x64 || May || Mai || Mai
|-
| 101/x65 || Jun || Jui || Jun
|-
| 102/x66 || Jul || Jul || Jul
|-
| 103/x67 || Aug || Ao– || Aug
|-
| 104/x68 || Sep || Sep || Sep
|-
| 105/x69 || Oct || Oct || Okt
|-
| 106/x6A || Nov || Nov || Nov
|-
| 107/x6B || Dec || D‚c || Dez
|-
| 108/x6C || has become unconscious || a perdu conscience || ist bewuátlos
|-
| 109/x6D || has died from a fatal wound || est mort d'une blessure || ist an einer Verletzung gestorben
|-
| 110/x6E || Use Mind Probe || Utiliser Sonde d'Esprit || Gedankensonde einsetzen
|-
| 111/x6F || FATAL WOUNDS || BLESSURES || T™DLICHE WUNDEN
|-
| 112/x70 || BRAVERY || COURAGE || MUT
|-
| 113/x71 || STRENGTH || FORCE || STŽRKE
|-
| 114/x72 || PSIONIC STRENGTH || FORCE PSIONIQUE || PSIONISCHE STŽRKE
|-
| 115/x73 || PSIONIC SKILL || COMPETENCE PSIONIQUE || PSIONISCHE FŽHIGKEITEN
|-
| 116/x74 || UNDER ARMOUR || ARMURE DE DESSOUS || GERšSTET
|-
| 117/x75 || Time Units reserved for Snap Shot || Unit‚s de temps r‚serv‚es au tir instantan‚ || Zeiteinheiten fr Schnellschuá
|-
| 118/x76 || Time Units reserved for Auto Shot || Unit‚s de temps r‚serv‚es au tir automatique || Zeiteinheiten fr Auto-Schuá
|-
| 119/x77 || Time Units reserved for Aimed Shot || Unit‚s de temps r‚serv‚es au tir vis‚ || Zeiteinheiten fr Zielschuá
|-
| 120/x78 || Units in Exit Area || Unit‚s dans la zone de sortie || Einheiten im Ausgangsbereich
|-
| 121/x79 || Units outside Exit Area || Unit‚s hors de la zone de sortie || Einheiten auáerhalb des Ausgangsbereichs
|-
| 122/x7A || Abort Mission ? || Annuler mission? || Mission abbrechen?
|-
| 123/x7B || Pistol || Pistolet || Pistole
|-
| 124/x7C || Pistol Clip || Cartouche de Pistolet || Pistolen-Ladestreifen
|-
| 125/x7D || Rifle || Fusil || Gewehr
|-
| 126/x7E || Rifle Clip || Cartouche de Fusil || Gewehr-Ladestreifen
|-
| 127/x7F || Heavy Cannon || Canon Lourd || Schweres Geschtz
|-
| 128/x80 || HC-AP Ammo || Munitions CL-PA || SG-PB-Munition
|-
| 129/x81 || HC-HE Ammo || Munitions CL-E || SG-HE-Munition
|-
| 130/x82 || HC-I Ammo || Munitions CL-I || SG-B-Munition
|-
| 131/x83 || Auto-Cannon || Canon Auto || Autom. Geschtz
|-
| 132/x84 || AC-AP Ammo || Munitions CA-PA || AG-PB-Munition
|-
| 133/x85 || AC-HE Ammo || Munitions CA-E || AG-HE-Munition
|-
| 134/x86 || AC-I Ammo || Munitions CA-I || AG-B-Munition
|-
| 135/x87 || Rocket Launcher || Lance-Roquettes || Raketenwerfer
|-
| 136/x88 || Small Rocket || Petite Roquette || Kleine Rakete
|-
| 137/x89 || Large Rocket || Grande Roquette || Groáe Rakete
|-
| 138/x8A || Incendiary Rocket || Roquette Incendiaire || Brandrakete
|-
| 139/x8B || Laser Pistol || Pistolet Laser || Laserpistole
|-
| 140/x8C || Laser Rifle || Fusil Laser || Lasergewehr
|-
| 141/x8D || Heavy Laser || Laser Lourd || Schwerer Laser
|-
| 142/x8E || Grenade || Grenade || Granate
|-
| 143/x8F || Smoke Grenade || Grenade FumigŠne || Rauchgranate
|-
| 144/x90 || Proximity Grenade || Grenade de Proximit‚ || Granate mit Ann„herungsznder
|-
| 145/x91 || High Explosive || Explosif || Brisanz-Sprengstoff
|-
| 146/x92 || Motion Scanner || Scanner de Mouvement || Bewegungsscanner
|-
| 147/x93 || Medi-Kit || Trousse de Soins || Sani-Tasche
|-
| 148/x94 || Psi-Amp || Psi-Amp || Psi-Verst„rker
|-
| 149/x95 || Stun Rod || Bƒton pour Assommer || Bet„ubungsstab
|-
| 150/x96 || Heavy Plasma || Canon … Plasma Lourd || Schweres Plasma
|-
| 151/x97 || Heavy Plasma Clip || Munition de Canon … Plasma Lourd || Ladestreifen mit Schwerem Plasma
|-
| 152/x98 || Plasma Rifle || Fusil … Plasma || Plasmagewehr
|-
| 153/x99 || Plasma Rifle Clip || Cartouche de Fusil … Plasma || Plasmagewehr-Ladestreifen
|-
| 154/x9A || Plasma Pistol || Pistolet … Plasma || Plasmapistole
|-
| 155/x9B || Plasma Pistol Clip || Cartouche de Pistolet … Plasma || Plasmapistolen-Ladestreifen
|-
| 156/x9C || Blaster Launcher || Lanceur Blaster || Blaster-Abschuárampe
|-
| 157/x9D || Blaster Bomb || Bombe Blaster || Blaster-Bombe
|-
| 158/x9E || Small Launcher || Petit Lanceur || Kleine Abschuárampe
|-
| 159/x9F || Stun Bomb || Bombe Assommante || Bet„ubungsbombe
|-
| 160/xA0 || Alien Grenade || Grenade Alienne || Auáerirdischen-Granate
|-
| 161/xA1 || Elerium-115 || Elerium-115 || Elerium-115
|-
| 162/xA2 || Mind Probe || Sonde d'Esprit || Gedankensonde
|-
| 163/xA3 || Sectoid Corpse || Corps Secto‹de || Toter Sektoid
|-
| 164/xA4 || Snakeman Corpse || Corps Homme-Serpent || Toter Schlangenmensch
|-
| 165/xA5 || Ethereal Corpse || Corps Ethereal || Toter Žtherer
|-
| 166/xA6 || Muton Corpse || Corps Muton || Toter Mutone
|-
| 167/xA7 || Floater Corpse || Corps Flottant || Toter Treiber
|-
| 168/xA8 || Celatid Corpse || Corps Celatid || Toter Celatid
|-
| 169/xA9 || Silacoid Corpse || Corps Silaco‹de || Toter Silakoid
|-
| 170/xAA || Chryssalid Corpse || Corps Chryssalid || Toter Chryssalid
|-
| 171/xAB || Reaper Corpse || Corps Reaper || Toter Schnitter
|-
| 172/xAC || Sectopod Corpse || Corps Sectopode || Toter Sektopod
|-
| 173/xAD || Cyberdisc Corpse || Corps Cyberdisc || Tote Cyberdisc
|-
| 174/xAE || Corpse || Corps || Toter
|-
| 175/xAF || Unload || D‚charger || Entladen
|-
| 176/xB0 || Electro-flare || Leurre ‚lectronique || E-Leuchtk”rper
|-
| 177/xB1 || Rookie || Nouvelle Recrue || Einfacher Soldat
|-
| 178/xB2 || Squaddie || DeuxiŠme Classe || Gefreiter
|-
| 179/xB3 || Sergeant || Sergent || Feldwebel
|-
| 180/xB4 || Captain || Capitaine || Hauptmann
|-
| 181/xB5 || Colonel || Colonel || Oberst
|-
| 182/xB6 || Commander || Commandant || Kommandant
|}
==See Also==
* [[ENGLISH2.DAT (TFTD)]] - Uses the strings in these files.
* [[TACTICAL.EXE]] - Uses the strings in these files.
* [[GEODATA]] - Parent Folder for these files.
* [[GeoScape String Files]] - The GeoScape equivalents of these files.
* [[Saved Game Files]]
[[Category:Game Files]]

ENGLISH.DAT (TFTD)

2010-10-28T04:26:51Z

Hatfarm: Created page with "This is one of the files containing the strings used by the geoscape game engine. Each string is terminated by a null character (x00). ..."

This is [[GeoScape String Files|one of the files]] containing the strings used by the [[GEOSCAPE.EXE|geoscape game engine]]. Each string is terminated by a null character (x00). Line breaks are defined by x0A. Every now and then x02 pops up, not sure why, probably something to do with the large font.

There are 1006 entries in all, not all of which are used by the release version of the game.

{| {{StdDescTable}}
|- {{StdDescTable_Heading}}
! Index !! English.Dat (54427 Bytes)
|-
| 0 ||A TRANSPORT AND INTERCEPT FLYING SUB, WITH EXTREME DEPTH CAPABILITY. A SUPERB SYNTHESIS OF ALIEN AND HUMAN TECHNOLOGY, UTILISING ION PROPULSION SYSTEMS AND MAGNETIC ARRAY NAVIGATION.
|-
| 1 ||THE BRITISH HYDROSPACE BARRACUDA, POWERED BY SUPER-HEATED LASER ENGINES. ONE OF THE FASTEST INTERCEPT SHIPS IN THE WORLD, CAPABLE OF SUBMERSIBLE AND ATMOSPHERIC FLIGHT, A KEY CRAFT IN THE COMING BATTLE.
|-
| 2 ||A TRANSPORT AND INTERCEPT CRAFT. A REPLICATION OF MAGNETIC ARRAY SYSTEMS IN AN X-COM SHIP. ALTHOUGH SMALL, ITS' DESIGN IS A BREATHTAKING TECHNICAL ACHIEVEMENT.
|-
| 3 ||THE TRITON, AN ASSAULT SQUAD TRANSPORTER, FITTED WITH FULL ATMOSPHERIC AND AQUATIC FLIGHT ENGINES. ITS LARGE CAPACITY AND ROBUST CONSTRUCTION ENSURES IT IS THE MAINSTAY OF THE X-COM FLEET.
|-
| 4 ||MANTA HIGH SPEED CRAFT, A ONE-MAN INTERCEPT FLYING SUBMARINE CLOSELY RESEMBLING ION-POWERED ALIEN SHIPS. A HIGHLY EFFECTIVE STRIKE CRAFT IN THE ESCALATING CONFLICT.
|-
| 5 ||THE AJAX TORPEDO IS THE STANDARD WEAPON OF UNDERSEA COMBAT THE WORLD OVER. EMPLOYED AS AN ACCURATE AND POWERFUL DETERRENT.
|-
| 6 ||DEPLETED URANIUM PELLET HEADED WEAPON TECHNOLOGY IS RELATIVELY NEW, AND THIS IS THE FIRST COMMERCIAL AQUATIC WEAPON SYSTEM TO EMPLOY IT FULLY.
|-
| 7 ||A COMPRESSED GAS POWERED CANNON SYSTEM FIRING SOLID BOLTS WITH HIGH ARMOUR PIERCING CAPABILITY.
|-
| 8 ||THE PULSE WAVE TORPEDO UTILISES A SUPERHEATED FUEL SYSTEM AND AN EXTREMELY DENSE WARHEAD WHICH CAN PUNCH THROUGH MOST ALLOYS.
|-
| 9 ||THE GAUSS WEAPON IS NEWLY DEVELOPED X-COM TECHNOLOGY. THIS SYSTEM'S PARTICLE ACCELERATOR IS POWERED BY A COMPACT, LIQUID NITROGEN COOLED, FUSION REACTOR.
|-
| 10 ||A POWERFUL AUDITORY OSCILLATOR CREATES WAVES OF SONIC FORCE. DESTROYING THE TARGET BY VIBRATING ITS MOLECULAR BONDS APART.
|-
| 11 ||The Aquatoid Race is an ancient society, having existed millennia before man's first faltering steps upon the world. Their compact form and bulbous features are a throwback to their space faring brethren, the Sectoids. Their power is based on the powerful Molecular Control technology. The Aquatoid race seeks to propagate its sterile race by genetic modification, the ideal subjects being human beings. Experiments have spawned numerous hybrid races.
|-
| 12 ||A detailed analysis of this creature allows us to make some basic assumptions. It is a Sectoid, our former foes, but changed by surgical methods and implants to be an aquatic creature. Vestigial lungs allow the breathing of air and limited surface mobility. There are cybernetic implants throughout the body, enhancing the strength of its atrophied limbs and the function of its organs. As all the members of this race are identical, we may hypothesise that these creatures are clones.
|-
| 13 ||Almost human, a strange creature who appears to be a reptilian humanoid, very closely related to man. This creature is extremely powerful and fast in the undersea world. Gillmen are a fully fledged race, there being male and female specimens of varying ages. They are unlike the majority of the underwater aliens as they bear none of the signs of genetic alteration or surgical deformation It is possible we are looking at some ancient branch of our own species.
|-
| 14 ||Once surgery began it became clear this is no alien, but an Earth born creature, an ancient pre-historic race that was thought destroyed at the very moment mammals became dominant. In a time when dinosaurs roamed these creatures lived, the Gillmen- amphibious, intelligent and strong. The cataclysm that ended the reptile rule on this planet forced these creatures into a symbiotic relationship with the newly arrived aliens. A small electronic device is lodged in the skulls of the creatures.
|-
| 15 ||This is a staggering creature, taller than a man and boasting six limbs, it resembles nothing more than an aquatic Demon. The similarities between this creature and the Earth lobster have earned it the nickname of Lobsterman with the X-Com troops. This is a behemoth of the deep. A carefully designed fighting creature of incredible strength and practically invulnerable to missile fire. Its pincers alone can crush steel.
|-
| 16 ||Once past its virtually indestructible shell the creature is an amazing construction. Powerful muscles ripple around a titanium skeleton, a sophisticated targeting system with multi-band scanning ability is hooked directly into the creature's brain. Its multiple eyes are protected by harder than steel plastics and it is clear that when well deployed by their masters these creatures are all but unstoppable. Buried deep within its body are devices of unknown construction and function.
|-
| 17 ||These agile and fast enemies are a mainstay of the alien army. Hundreds are birthed, in massive breeding vats deep in the heart of the Alien colonies. Vastly more powerful than a man, the Tasoth is a true alien and its behaviour and carnivorous nature unmatched on the planet. The Tasoth often forms the spearhead of an alien attack and never seems to shrink from the fight even in the face of overwhelming odds.
|-
| 18 ||Dissection revealed a cybernetic organism possessed of strange power. Inside the body cavity is a small power unit, but no identifiable organs. The power is transmitted throughout the body by a Bio-electric transmission system. The whole body lacks bones or any other supporting structure. Once dead the power stops and the creature becomes a lifeless rag doll of oozing alien flesh and fluids. The only other internal construction is a pair of ceramic cells, which if energised briefly revive the creature.
|-
| 19 ||The Deep One is a biological nightmare, a cross breed, produced by the mind warping experiments of the Aquatoids. We have encountered several variations of this creature. After extensive research we conclude that these are manufactured by the invaders. Swelling their ranks when fresh human stock has been captured. Each of these sub-humans is armed with an electrical energy discharge powerful enough to kill an aquanaut.
|-
| 20 ||The creature is a graft of man and alien organism. The human brain is massively altered to accommodate control electronics and the Alien cortex. All vestiges of the human body seem lost save one: the eyes. The surgical graft appears to allow the alien foetus to consume the human host as it grows. The tough skin of the creature appears to be a non-organic, metallic mesh, extremely strong and flexible. The resulting cross breed is strong, fast and utterly under the control of the aliens.
|-
| 21 ||The Bio-drone is a creation only an alien mind could conceive of. It is a brain, (human or alien) suspended in amniotic fluids and connected to a powered base unit that can fly on land or below water. Each Bio-drone is armed with a powerful auditory disruptor, part machine and part organism. Some of our scientists have suggested that the weapon is driven by the host organisms original vocal cords. Highly accurate and tenacious these super guard dogs are widely used by the aliens to protect valuable assets.
|-
| 22 ||The hypothesis that the auditory disruptor is a biological device are true. This unfortunate creature literally screams its enemies to death. Every example has massive surgical trauma scars and is severely mutilated. The aliens appear to butcher the brain into obedience. Most of the cortex's used in the creatures are alien in origin, but nothing can compare to the horror of finding a human based unit.The Bio-drones are powered by an ION engine and incorporate some form of remote control system.
|-
| 23 ||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.
|-
| 24 ||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.
|-
| 25 ||Like the diving suits of lost mariners these aliens stalk the seabed for the unwary. A vicious swipe by the creature's stronger than steel claws can be enough to send the best divers to the bottom. Swirling around in the face mask a gelatinous green form can be seen. No hint of the real creature can be divined from the often lethal encounters we have had with them.
|-
| 26 ||Once the armoured suit is stripped away the Calcinite is revealed to be a huge amorphous blob of protoplasm. No visible brain, limbs or sensory organs exist, a small metallic component resides deep in the liquid body. Once dead we can only guess at the creature's nature. An inexplicable enigma of our alien enemies.
|-
| 27 ||This bipedal reptile is a throwback to the age of the Dinosaurs. It seems to be a Cretaceous creature in every sense save its ability to survive in water and on land. These creatures are slung with weapons pods and have a jaw lined with huge metallic teeth. Often these monsters have been at the core of the alien attack forces as the Aliens launch assaults upon the land. A heavyweight and potent weapon, the Lobster men commanders deploy them with lethal efficiency.
|-
| 28 ||Once subjected to the scientist's knife the Triscene reveals that it is an ancient creature, supplemented with cybernetic implants and weapons systems. Its tiny brain is supplemented by a small computer module mounted in the control harness all the creatures wear. A tough natural skin, a predatory instinct enhanced by additional weapons makes this a lethal opponent in all environments.
|-
| 29 ||Having harvested the oceans the aliens have bred these huge Earth creatures as a weapon. Do not be lulled into a false sense of security when facing these harmless looking sailors of the deeps. Possessed of a formidable, ranged, freezing blast and a close combat icy strike, the Hallucinoid is a deadly foe.
|-
| 30 ||Nested in the many layers of the gelatinous body of this organism is a powerful chemical freezer, its' main offensive capability. The soft and supple skin of the Hallucinoid seems susceptible to heat based attacks. Often this mutant is found in the company of its masters, the Aquatoids.
|-
| 31 ||Another modified Earth invertebrate, the Xarquid is a creature of great beauty and danger. The swift swimming gargantuan hides a devastating arsenal of weapons, a smothering ink spray and an ionised particle blast. Since our first encounters with this powerful creature we have been wary of its power and its controllers the vengeful Gillmen.
|-
| 32 ||This overgrown Nautilus has been made huge on a diet of Alien drugs and surgical alterations. Perverted beyond the scope of nature, the Gillmen have added mechanical control systems to the creature and now none of the creature's original nature exists. Deployed as an organic weapons platform, the Xarquids tough shell and mobility make it a formidable opponent.
|-
| 33 ||Alien flying submarines rely on complex power systems to drive them at incredible speed through the deeps. The basis for their technology is the ION DISPLACER, utilising Zrbite as a catalyst, the engines displace 100 times their own volume in water per second. This enormous power means that the aliens' are capable of outrunning most Earth subs. We can replicate this system of propulsion using aqua-plastics and Zrbite power cells.
|-
| 34 ||These units generate a spherical multi-layer magnetic field, which the array projects up to 1000m around the sub. The Alien navigators are directly linked into the machines and feel their way around the invisible world beneath the waves. The interface system operates using Alien modified cerebral matter that communicates directly with the operator's brain via a neural link.
|-
| 35 ||Each vessel has a chameleon-like structure, carefully modelled on sea creatures, and constructed of Aqua Plastics. Each submarine functions as an organism: crew and craft in harmony. Most of these systems can be replicated and a hybrid technology can be evolved to allow us to move up to the same technological level.
|-
| 36 ||The innumerable Aliens that have lain hidden on the Earth are held in suspended animation, cryogenically frozen. All the creatures are sealed into units, their body temperature reduced to a point where bodily functions are all but stopped. An examination of the units so far reveals the unbelievable time periods that the bodies have been kept suspended for, some over 60 million years.
|-
| 37 ||Many of the Aliens we have captured are identical even down to their DNA, duplicates in every way. Cell samples are placed into the units from the frozen gene banks of the Aliens. Some units contain humans or body parts. It is possible that another use for these cloning units is to create some Alien-human hybrid.
|-
| 38 ||Utilising Molecular Control Implants in the skulls of all Aliens these machines inject information directly into the brain. Freshly cloned Aliens are brought to these units and have racial memories and all scientific or combat information downloaded into their blank minds.
|-
| 39 ||This unit is used to fit Aliens with Molecular Control Implants, fertilise reproducing races, and insert or remove organs and electronics from any creature. The process was thought to be done on subdued patients, but the subject is very aware of the process and unfortunately human anatomy seems to fit the unit perfectly.
|-
| 40 ||We now have the evidence to work out why Aliens capture humans. They are not food, they are not fertilised with Alien embryos, rather they form the basis of a range of creatures and control systems. Alien technology is based on a common mind, a shared intellect and the human brain is the ideal receptacle for these systems. Human brain tissue is used in most of the Alien biological computer storage and retrieval systems, the remains are used for building and for breeding.
|-
| 41 ||Alien submarines and structures utilise an incredibly strong, flexible and durable material for the majority of their construction. Aqua plastics are complex multi-bonded and Zrbite catalysed materials. Dense, yet light, the substance has strength above even Titanium or Kevlar.
|-
| 42 ||Research required in

|-
| 43 ||This is an alloy of Alien origin, part gold part Alien Bio-material. When utilised as a power source, small quantities will generate more power than a nuclear unit of 10 times the size. It is beyond our technical ability to replicate this material as most of its constituents are Alien in origin.
|-
| 44 ||The Aliens strike all across the globe, with ruthless efficiency. We cannot pin down their source. Could it be in some ocean deep too impenetrable for us to locate? Not all the organisms we have encountered are Alien, some are very old, some are from evolutionary paths long thought extinct. We are dealing with a menace that has been sleeping for millennia, a subtle symbiosis of human and Alien. Deep in the oceans there lie ancient sites used by the Aliens to contact their stellar cousins. Each of these twelve sites contains a Synomium device, a powerful Alien technology. Now with their war machine on the march the Aliens are re-activating these sites to widen their Molecular Control net, we must destroy these sites at all costs.
|-
| 45 ||Gauss Pistol Clip
|-
| 46 ||Gauss Rifle Clip
|-
| 47 ||Terror Site-
|-
| 48 ||CENTRE ON SITE-TIME=5 Secs
|-
| 49 ||CANCEL
|-
| 50 ||None
|-
| 51 ||Unknown
|-
| 52 ||Poor
|-
| 53 ||Average
|-
| 54 ||Good
|-
| 55 ||Excellent
|-
| 56 ||FUNDS> $
|-
| 57 ||BUILD NEW BASE
|-
| 58 ||BASE INFORMATION
|-
| 59 ||EQUIP SUBMARINE
|-
| 60 ||BUILD FACILITIES
|-
| 61 ||RESEARCH
|-
| 62 ||MANUFACTURE
|-
| 63 ||TRANSFER
|-
| 64 ||PURCHASE/RECRUIT
|-
| 65 ||SELL/SACK
|-
| 66 ||GEOSCAPE
|-
| 67 ||X-Com Bases
|-
| 68 ||Name
|-
| 69 ||Area
|-
| 70 ||Build New Base
|-
| 71 ||Cancel
|-
| 72 ||COST>
|-
| 73 ||CONSTRUCTION TIME>
|-
| 74 || days
|-
| 75 ||MAINTENANCE>
|-
| 76 ||OK
|-
| 77 ||Installation
|-
| 78 ||CURRENT RESEARCH
|-
| 79 ||Scientists Available>
|-
| 80 ||Scientists Allocated>
|-
| 81 ||Laboratory Space Available>
|-
| 82 ||RESEARCH PROJECT
|-
| 83 ||SCIENTISTS ALLOCATED
|-
| 84 ||PROGRESS
|-
| 85 ||New Project
|-
| 86 ||NEW RESEARCH PROJECTS
|-
| 87 ||SCIENTISTS AVAILABLE>
|-
| 88 ||LABORATORY SPACE AVAILABLE>
|-
| 89 ||Increase
|-
| 90 ||Decrease
|-
| 91 ||START PROJECT
|-
| 92 ||CURRENT PRODUCTION
|-
| 93 ||Technicians Available>
|-
| 94 ||Technicians Allocated>
|-
| 95 ||Workshop Space Available>
|-
| 96 ||Current Funds>
|-
| 97 ||ITEM
|-
| 98 ||Technicians
Allocated
|-
| 99 ||Units
Produced
|-
| 100 ||Total to
Produce
|-
| 101 ||Cost
per
Unit
|-
| 102 ||Days/Hours
Left
|-
| 103 ||New Production
|-
| 104 ||Production Items
|-
| 105 ||CATEGORY
|-
| 106 ||START PRODUCTION
|-
| 107 ||Technician hours to produce one unit
|-
| 108 ||Cost per unit>$
|-
| 109 ||Work Space Required>
|-
| 110 ||SPECIAL MATERIALS REQUIRED
|-
| 111 ||ITEM
REQUIRED
|-
| 112 ||UNITS
REQUIRED
|-
| 113 ||UNITS
AVAILABLE
|-
| 114 ||STOP PRODUCTION
|-
| 115 ||TECHNICIANS AVAILABLE>
|-
| 116 ||WORKSHOP SPACE AVAILABLE>
|-
| 117 ||Technicians
|-
| 118 ||Allocated
|-
| 119 ||INCREASE
|-
| 120 ||DECREASE
|-
| 121 ||Units to
|-
| 122 ||Produce
|-
| 123 ||Purchase/Hire Personnel
|-
| 124 ||Current Funds>
|-
| 125 ||Cost of Purchases>
|-
| 126 ||COST PER UNIT
|-
| 127 ||QUANTITY
|-
| 128 ||PERSONNEL AVAILABLE:PERSONNEL TOTAL>
|-
| 129 ||Aquanauts
|-
| 130 ||Technicians
|-
| 131 ||Scientists
|-
| 132 ||SPACE USED:SPACE AVAILABLE>
|-
| 133 ||Living Quarters
|-
| 134 ||Stores
|-
| 135 ||Laboratories
|-
| 136 ||Work Shops
|-
| 137 ||Flying Sub Pens
|-
| 138 ||Short Range Sonar
|-
| 139 ||Defence Strength
|-
| 140 ||TRANSFERS
|-
| 141 ||Transfers
|-
| 142 ||Arrival Time (hours)
|-
| 143 ||Cost>$
|-
| 144 ||Area>
|-
| 145 ||Base Name?
|-
| 146 ||SELECT POSITION FOR AIR-LOCK
|-
| 147 ||Transfer
|-
| 148 ||AMOUNT TO
TRANSFER
|-
| 149 ||Select Destination Base
|-
| 150 ||Current Funds>
|-
| 151 ||Cost
|-
| 152 ||The Sonic Cannon the most potent of the Sonic weapons family.Featuring a higher range audio oscillator and a larger reverberation chamber than the Blasta. The Cannon also has a pulse detonation system that alters the ultra-sonic wave by modulation to produce a more effective Sonic Shock.
|-
| 153 ||Heavy Gauss Clip
|-
| 154 ||Vibro Blade
|-
| 155 ||The Alien forces over run the land. Once the Ultimate Alien has been revived they flood the world by melting the ice caps. The huge Alien ship, T'leth, rises from the ocean and sears the remaining cities to rubble. The atmosphere becomes clogged with the dust of the carnage and the world begins to warm. The remaining humans are rounded up and utilised to produce breeding stock for a new Alien world. We can offer no resistance to the new world order.
|-
| 156 ||The knowledge gained during the conflict is lost forever. You have failed to save the Earth. Humankind is reduced to materials for Alien schemes, soon the Earth is a flooded and desolate place.
|-
| 157 ||Thermic Lance
|-
| 158 ||Heavy Thermic Lance
|-
| 159 ||You have failed to stop the Alien war machine. The funding organisations, disillusioned with your ability try to negotiate a non military solution with the Aliens. The Invaders have a very different agenda and soon the whole world is aware of the truth...
|-
| 160 ||TOTAL
|-
| 161 ||Income
|-
| 162 ||Expenditure
|-
| 163 ||Maintenance
|-
| 164 ||Balance
|-
| 165 ||Alien Activity in Seas
|-
| 166 ||Alien Activity in Zones
|-
| 167 ||X-Com Activity in Seas
|-
| 168 ||X-Com Activity in Zones
|-
| 169 ||Finance
|-
| 170 ||st
|-
| 171 ||nd
|-
| 172 ||rd
|-
| 173 ||th
|-
| 174 ||Not enough special materials to produce

|-
| 175 ||Not enough money to produce

|-
| 176 ||Production complete:

|-
| 177 ||Production of

|-
| 178 ||
at

|-
| 179 ||
is complete
|-
| 180 ||OK - 5 secs
|-
| 181 ||Research Completed
|-
| 182 ||VIEW REPORTS
|-
| 183 ||We can now research
|-
| 184 ||We can now produce
|-
| 185 ||SUNDAY
|-
| 186 ||MONDAY
|-
| 187 ||TUESDAY
|-
| 188 ||WEDNESDAY
|-
| 189 ||THURSDAY
|-
| 190 ||FRIDAY
|-
| 191 ||SATURDAY
|-
| 192 ||Not enough
|-
| 193 || to refuel
|-
| 194 || to rearm
|-
| 195 || at
|-
| 196 ||ALIEN SUB is not recovered
|-
| 197 ||ALIEN SUB is recovered
|-
| 198 ||Flying Sub is lost
|-
| 199 ||Alien Activity continues
|-
| 200 ||Aliens defeated
|-
| 201 ||Flying Sub is lost
|-
| 202 ||Base is lost
|-
| 203 ||Base is saved
|-
| 204 ||Base is lost
|-
| 205 ||Alien Colony still intact
|-
| 206 ||Alien Colony destroyed
|-
| 207 ||Flying Sub is lost
|-
| 208 ||ALIENS KILLED
|-
| 209 ||ALIEN CORPSES RECOVERED
|-
| 210 ||LIVE ALIENS RECOVERED
|-
| 211 ||ALIEN ARTEFACTS RECOVERED
|-
| 212 ||ALIEN COLONY CONTROL DESTROYED
|-
| 213 ||CIVILIANS KILLED BY ALIENS
|-
| 214 ||CIVILIANS KILLED BY X-COM OPERATIVES
|-
| 215 ||CIVILIANS SAVED
|-
| 216 ||X-COM OPERATIVES KILLED
|-
| 217 ||X-COM OPERATIVES RETIRED THROUGH INJURY
|-
| 218 ||X-COM OPERATIVES MISSING IN ACTION
|-
| 219 ||X-COM WEAPONS PLATFORM DESTROYED
|-
| 220 ||X-COM SUBMARINE LOST
|-
| 221 ||UFO RECOVERY
|-
| 222 ||ALIEN COLONY RECOVERY
|-
| 223 || under attack!
|-
| 224 ||BASE DEFENCES INITIATED
|-
| 225 ||SHIELDS REPEL ALIEN SUB!
|-
| 226 ||FIRING
|-
| 227 ||HIT!
|-
| 228 ||ALIEN SUB DESTROYED!
|-
| 229 ||MISSED!
|-
| 230 ||Sell Items/Sack Personnel
|-
| 231 ||VALUE OF SALES>
|-
| 232 ||FUNDS>
|-
| 233 ||Sell/Sack
|-
| 234 ||Value
|-
| 235 ||ALIEN SUB-
|-
| 236 ||FLYING SUB>
|-
| 237 ||ALIEN SUB CRASH RECOVERY
|-
| 238 ||EXTREME CAUTION - There will be Aliens in the submarine and around the site. This mission will be completed when all enemy units have been eliminated or neutralised. Recovery of Alien Sub remains, technology and alien corpses can then be initiated. To abort the mission return X-Com aquanauts to the submarine and click on the 'Abort Mission' icon.
|-
| 239 ||ALIEN SUBMARINE ASSAULT
|-
| 240 ||Explore the touchdown site and, if possible, gain entry to the Alien Sub. The mission will be successful when all enemy units have been eliminated or neutralised. Recovery of the Alien Sub, artefacts and Alien corpses can then be initiated. To abort the mission return X-Com aquanauts to the submarine and click on the 'Abort Mission' icon.
|-
| 241 ||BASE DEFENCE
|-
| 242 ||BASE>
|-
| 243 ||An Alien vessel has touched down nearby. Our base is in severe danger. As per standard procedure all non combat personnel and functional X-Com subs have been evacuated. Aliens will enter the base via Submarine Pen gates or the air-lock. Defend the base and its vital installations at all costs - this is a fight to the death. If you click on the 'abort mission' icon you will concede defeat and lose the base.
|-
| 244 ||ARTEFACT SITE-
|-
| 245 ||CRAFT>
|-
| 246 ||AIRBORNE
|-
| 247 ||Mixed
|-
| 248 ||ALIEN SYNOMIUM DEVICE DESTROYED
|-
| 249 ||UNABLE TO ENGAGE ENEMY
WHEN AIRBORNE
|-
| 250 ||FAILED TO DESTROY SYNOMIUM DEVICE
|-
| 251 ||NO FREE SUB PENS FOR CRAFT PRODUCTION!�Each Flying Sub assigned to a base, transferred to a base, purchased or constructed uses one Sub Pen. Build a new Sub Pen or transfer a sub to another base.
|-
| 252 ||NO FREE SUB PENS FOR PURCHASE!�Each Flying Sub assigned to a base, transferred to a base, purchased or constructed uses one Sub Pen. Build a new Sub Pen or transfer a sub to another base.
|-
| 253 ||NO FREE SUB PENS FOR TRANSFER!�Each Flying Sub assigned to a base, transferred to a base, purchased or constructed uses one Sub Pen. Build a new Sub Pen or transfer a sub to another base.
|-
| 254 ||CANNOT BUILD HERE!�You must build next to an existing pod.
|-
| 255 ||NO FREE ACCOMODATION!�The destination base does not have enough space in living quarters.
|-
| 256 ||NOT ENOUGH WORK SPACE AVAILABLE!�Build a new workshop or reduce work on other projects.
|-
| 257 ||NOT ENOUGH MONEY!
|-
| 258 ||NOT ENOUGH TRANSFER SUPPORT!�Wait for existing transfers or purchases to reach destination.
|-
| 259 ||NO MORE AQUANAUTS ALLOWED!�You have already recruited the maximum number of aquanauts.
|-
| 260 ||NOT ENOUGH STORE SPACE!�Build a new store facility or transfer existing stores to other bases.
|-
| 261 ||NOT ENOUGH LIVING SPACE!�Build new living quarters or transfer personnel to other bases.
|-
| 262 ||NO MORE EQUIPMENT ALLOWED ON BOARD!�You are only allowed to take a maximum of 80 items of equipment on missions.
|-
| 263 ||TOO MANY BUTTONS!
|-
| 264 ||LAUNCH INTERCEPTION
|-
| 265 ||CRAFT
|-
| 266 ||STATUS
|-
| 267 ||BASE
|-
| 268 ||READY
|-
| 269 ||OUT
|-
| 270 ||REPAIRS
|-
| 271 ||REFUELLING
|-
| 272 ||REARMING
|-
| 273 ||TARGET:
|-
| 274 ||ALIEN COLONY-
|-
| 275 ||CRASH SITE-
|-
| 276 ||TOUCHDOWN SITE-
|-
| 277 ||TARGET: WAY POINT
|-
| 278 ||Are you sure you want to send this Sub on a mission to T'leth?
|-
| 279 ||YES
|-
| 280 ||NO
|-
| 281 ||SELECT DESTINATION
|-
| 282 ||This Site is too Deep
Returning to base
|-
| 283 ||SELECT SITE FOR NEW BASE
|-
| 284 ||RETURN TO BASE
|-
| 285 ||SELECT NEW TARGET
|-
| 286 ||PATROL
|-
| 287 ||STATUS>
|-
| 288 ||DAMAGED - RETURNING TO BASE
|-
| 289 ||LOW FUEL - RETURNING TO BASE
|-
| 290 ||PATROLLING
|-
| 291 ||TAILING ALIEN SUB
|-
| 292 ||INTERCEPTING ALIEN SUB-
|-
| 293 ||RETURNING TO BASE
|-
| 294 ||DESTINATION: ALIEN COLONY-
|-
| 295 ||DESTINATION: CRASH SITE-
|-
| 296 ||DESTINATION: TOUCH DOWN SITE-
|-
| 297 ||DESTINATION: WAY POINT-
|-
| 298 ||BASE>
|-
| 299 ||SPEED>
|-
| 300 ||MAXIMUM SPEED>
|-
| 301 ||DEPTH>
|-
| 302 ||SHALLOW
|-
| 303 ||NORMAL
|-
| 304 ||DEEP
|-
| 305 ||VERY DEEP
|-
| 306 ||FUEL>
|-
| 307 ||WEAPON-1>
|-
| 308 ||NONE
|-
| 309 ||ROUNDS>
|-
| 310 ||WEAPON-2>
|-
| 311 ||HOSTILE
|-
| 312 ||NEUTRAL
|-
| 313 ||FRIENDLY
|-
| 314 ||COMMITTED
|-
| 315 ||GAME OPTIONS
|-
| 316 ||LOAD GAME
|-
| 317 ||SAVE GAME
|-
| 318 ||FLYING SUB
|-
| 319 ||Base>
|-
| 320 ||NAME
|-
| 321 ||STATUS
|-
| 322 ||AMMO>
|-
| 323 ||CREW
|-
| 324 ||EQUIPMENT
|-
| 325 ||ARMOUR
|-
| 326 ||MAX>
|-
| 327 ||Seaman
|-
| 328 ||Able Seaman
|-
| 329 ||Ensign
|-
| 330 ||Lieutenant
|-
| 331 ||Commander
|-
| 332 ||Captain
|-
| 333 ||Select Squad for
|-
| 334 ||SPACE AVAILABLE>
|-
| 335 ||SPACE USED>
|-
| 336 ||RANK
|-
| 337 ||CRAFT
|-
| 338 ||WOUNDED
|-
| 339 ||Equipment for
|-
| 340 ||Arm
|-
| 341 ||Defence Value
|-
| 342 ||Hit Ratio
|-
| 343 ||ready to
touchdown near
|-
| 344 ||Begin Mission?
|-
| 345 ||Select Armament
|-
| 346 ||AMMUNITION
|-
| 347 ||ARMAMENT
|-
| 348 ||AVAILABLE
|-
| 349 ||N.A.
|-
| 350 ||SELECT ARMOUR FOR
|-
| 351 ||TYPE
|-
| 352 ||PLASTIC AQUA ARMOUR
|-
| 353 ||ION ARMOUR
|-
| 354 ||MAGNETIC ION ARMOUR
|-
| 355 ||Select Armour
|-
| 356 ||ARMOUR
|-
| 357 ||NORTH
|-
| 358 ||NORTH EAST
|-
| 359 ||EAST
|-
| 360 ||SOUTH EAST
|-
| 361 ||SOUTH
|-
| 362 ||SOUTH WEST
|-
| 363 ||WEST
|-
| 364 ||NORTH WEST
|-
| 365 ||SELECT ACTION
|-
| 366 ||CONTINUE INTERCEPTION PURSUIT
|-
| 367 ||PURSUE WITHOUT INTERCEPTION
|-
| 368 ||VERY LARGE
|-
| 369 ||LARGE
|-
| 370 ||MEDIUM
|-
| 371 ||SMALL
|-
| 372 ||VERY SMALL
|-
| 373 ||TOUCHED DOWN
|-
| 374 ||SHALLOW
|-
| 375 ||NORMAL
|-
| 376 ||DEEP
|-
| 377 ||VERY DEEP
|-
| 378 ||Detected
|-
| 379 ||SIZE
|-
| 380 ||DEPTH
|-
| 381 ||HEADING
|-
| 382 ||SPEED
|-
| 383 ||CENTRE ON ALIEN SUB-TIME=5 Secs
|-
| 384 ||TRACKING LOST
|-
| 385 ||REDIRECT CRAFT
|-
| 386 ||GO TO LAST KNOWN ALIEN SUB POSITION
|-
| 387 ||ALIEN SUB-
|-
| 388 ||CRAFT-
|-
| 389 ||BASE-
|-
| 390 ||ALIEN COLONY-
|-
| 391 ||CRASH SITE-
|-
| 392 ||TOUCHDOWN SITE-
|-
| 393 ||WAY POINT-
|-
| 394 ||TERROR SITE-
|-
| 395 ||has reached
|-
| 396 ||Destination
|-
| 397 ||Now patrolling
|-
| 398 ||Alien Origins
|-
| 399 ||The Ultimate Threat
|-
| 400 ||T'leth, the Alien's City
|-
| 401 ||UFOpedia
|-
| 402 ||X-COM CRAFT & WEAPONS
|-
| 403 ||SUBMERSIBLE WEAPONS SYSTEMS
|-
| 404 ||GENERAL EQUIPMENT
|-
| 405 ||AQUATIC ARTEFACTS
|-
| 406 ||X-COM FACILITIES
|-
| 407 ||ALIEN CREATURES
|-
| 408 ||ALIEN TECHNOLOGY
|-
| 409 ||NEW SUBMERSIBLE TECHNOLOGIES
|-
| 410 ||ALIEN SUBMARINES
|-
| 411 ||SELECT ITEM
|-
| 412 || autopsy
|-
| 413 ||MAXIMUM SPEED>
|-
| 414 ||ACCELERATION>
|-
| 415 ||FUEL CAPACITY>
|-
| 416 ||WEAPON PODS>
|-
| 417 ||DAMAGE CAPACITY>
|-
| 418 ||CARGO SPACE>
|-
| 419 ||SWS CAPACITY>
|-
| 420 ||Damage...............
|-
| 421 ||Range..................
|-
| 422 || km
|-
| 423 ||Accuracy.............
|-
| 424 ||Re-load time....
|-
| 425 ||s
|-
| 426 ||ARMOUR PIERCING
|-
| 427 ||PHOSPHOROUS
|-
| 428 ||HIGH EXPLOSIVE
|-
| 429 ||GAUSS BEAM
|-
| 430 ||SONIC BEAM
|-
| 431 ||FREEZE
|-
| 432 ||6-?
|-
| 433 ||7-?
|-
| 434 ||8-?
|-
| 435 ||9-?
|-
| 436 ||TYPE
|-
| 437 ||ACCURACY
|-
| 438 ||TU COST
|-
| 439 ||DAMAGE
|-
| 440 ||AMMO
|-
| 441 ||Auto
|-
| 442 ||Snap
|-
| 443 ||Aimed
|-
| 444 ||Construction Time
|-
| 445 ||days
|-
| 446 ||Construction Cost
|-
| 447 ||Maintenance Cost
|-
| 448 || autopsy
|-
| 449 ||-
|-
| 450 ||Low
|-
| 451 ||Medium
|-
| 452 ||High
|-
| 453 ||High
|-
| 454 ||Sub Weapon
|-
| 455 ||Sub Ammunition
|-
| 456 ||Heavy Weapons System
|-
| 457 ||Weapon
|-
| 458 ||Ammunition
|-
| 459 ||Equipment
|-
| 460 ||Alien Corpse
|-
| 461 ||ALIEN SUB component
|-
| 462 ||Plastic Aqua Armour
|-
| 463 ||Raw Materials
|-
| 464 ||Solid Harpoon Bolts
|-
| 465 ||Alien
|-
| 466 ||Aquatoid
|-
| 467 ||Gill Man
|-
| 468 ||Lobster Man
|-
| 469 ||Tasoth
|-
| 470 ||Calcinite
|-
| 471 ||Deep One
|-
| 472 ||Bio-Drone
|-
| 473 ||Tentaculat
|-
| 474 ||Triscene
|-
| 475 ||Hallucinoid
|-
| 476 ||Xarquid
|-
| 477 || Commander
|-
| 478 || Navigator
|-
| 479 || Medic
|-
| 480 || Technician
|-
| 481 || Squad Leader
|-
| 482 || Soldier
|-
| 483 || Terrorist
|-
| 484 ||Ion-Beam Accelerators
|-
| 485 ||Magnetic Navigation
|-
| 486 ||Alien Sub Construction
|-
| 487 ||Alien Cryogenics
|-
| 488 ||Alien Cloning
|-
| 489 ||Alien Learning Arrays
|-
| 490 ||Alien Implanter
|-
| 491 ||Examination Room
|-
| 492 ||Aqua Plastics
|-
| 493 ||Alien Re-animation Zone
|-
| 494 ||Plastic Aqua-Armour
|-
| 495 ||Ion Armour
|-
| 496 ||Mag. Ion Armour
|-
| 497 ||Aqua Jet Missiles
|-
| 498 ||P.W. Torpedo
|-
| 499 ||Gauss Technology
|-
| 500 ||New Fighter Flying Sub
|-
| 501 ||New Fighter-Transporter
|-
| 502 ||The Latest Flying Sub
|-
| 503 ||Gauss Pistol
|-
| 504 ||Gauss Rifle
|-
| 505 ||Heavy Gauss Cannon
|-
| 506 ||Gauss Cannon
|-
| 507 ||Sonic Cannon
|-
| 508 ||D.U.P. head Missile
|-
| 509 ||Gauss Defences
|-
| 510 ||Sonic Defences
|-
| 511 ||P.W.T. Defences
|-
| 512 ||Bombardment Shield
|-
| 513 ||M.C. Generator
|-
| 514 ||M.C.-Lab
|-
| 515 ||Transmission Resolver
|-
| 516 ||Sixty five million years ago a vast colony ship was sent to the Earth from a distant Alien world. As the enormous craft approached the infant planet a massive and violent solar flare caused a navigation systems failure. Crippled and failing the vast bulk plummeted through the stratosphere to emerge into Cretaceous skies. On the Earth innumerable species of life strained their gazes skywards as their nemesis ploughed into the planet.
A vast cloud of dust clogged the atmosphere and as the land cooled so the dominant life, the mighty dinosaurs, perished. But the 400 billion tonnes of T'leth was not destroyed in the impact, sophisticated super computers initiated a cryogenic sleep cycle for the creatures deep in its holds. As the aeons passed the computers woke parties of Aliens to attempt communication with their stellar cousins, all in vain for the core of the Alien power slept on.
|-
| 517 ||T'leth the huge Alien colony ship lies embedded in the Sigsbee Deep, in the Gulf of Mexico. At the Heart of the city is an Alien horror, so vile and so powerful that not even death can claim it. In a chamber of Alien metal lies the sleeping form of the great dreamer, the Ultimate Alien. Raising T'leth above the waves will begin his re-animation cycle, and once risen he will be unstoppable. Although not alive and some how not dead the Alien mind controls the Alien army. The weird technology of molecular control connects all Aliens to the One mind and the One mind to all the Aliens. Genetically mutated Alien/human foetuses supply the Alien mind with energy and form the link between the ruler and his subjects. The myth of the Ultimate Alien has existed in the hearts and minds of humankind for centuries, the sea has always hidden the ultimate truth.
|-
| 518 ||T'LETH
|-
| 519 ||Alien Sub Construction
|-
| 520 ||Alien Origins
|-
| 521 ||The Final Solution
|-
| 522 ||T'leth the Alien's City
|-
| 523 ||Particle Dist. Sensor
|-
| 524 ||Medi-Kit
|-
| 525 ||Coelacanth/G. Cannon
|-
| 526 ||Coelacanth/Aqua Jet
|-
| 527 ||Coelacanth/Gauss
|-
| 528 ||Displacer /Sonic
|-
| 529 ||Displacer /P. W. T.
|-
| 530 ||Ajax Launcher
|-
| 531 ||D.U.P. Head Launcher
|-
| 532 ||Craft Gas Cannon
|-
| 533 ||P.W.T. Cannon
|-
| 534 ||Gauss Cannon
|-
| 535 ||Sonic Wave
|-
| 536 ||Ajax Torpedoes
|-
| 537 ||D.U.P. Head Torpedoes
|-
| 538 ||Gas Rounds(x50)
|-
| 539 ||P.W.T Ammo
|-
| 540 ||Aquanaut
|-
| 541 ||Scientist
|-
| 542 ||Technician
|-
| 543 ||North Atlantic
|-
| 544 ||South Atlantic
|-
| 545 ||North Pacific
|-
| 546 ||South Pacific
|-
| 547 ||Mediterranean
|-
| 548 ||South China Sea
|-
| 549 ||Indian Ocean
|-
| 550 ||Sea of Japan
|-
| 551 ||North Sea
|-
| 552 ||Caribbean
|-
| 553 ||Antarctic
|-
| 554 ||Arctic
|-
| 555 ||Eurasia
|-
| 556 ||North America
|-
| 557 ||Africa
|-
| 558 ||Alien Probe Mission
|-
| 559 ||Alien Interdiction
|-
| 560 ||Alien Resource Raid
|-
| 561 ||Alien Infiltration
|-
| 562 ||Alien Colony Expansion
|-
| 563 ||Alien Surface Attacks
|-
| 564 ||Floating Base Attack
|-
| 565 ||Colony Supply Missions
|-
| 566 ||Power Sources
|-
| 567 ||Maximum Speed
|-
| 568 ||TRANSMISSION RESOLVER
|-
| 569 ||TRITON
|-
| 570 ||HAMMERHEAD
|-
| 571 ||LEVIATHAN
|-
| 572 ||BARRACUDA
|-
| 573 ||MANTA
|-
| 574 ||ALIEN SUB
|-
| 575 ||AJAX
|-
| 576 ||D.U.P. HEAD
|-
| 577 ||CRAFT GAS CANNON
|-
| 578 ||P.W.T CANNON
|-
| 579 ||GAUSS CANNON
|-
| 580 ||SONIC OSCILLATOR
|-
| 581 ||Damage Capacity
|-
| 582 ||Weapon Power
|-
| 583 ||Weapon Range
|-
| 584 ||Air-Lock
|-
| 585 ||Living Quarters
|-
| 586 ||Laboratory
|-
| 587 ||Workshop
|-
| 588 ||Standard Sonar
|-
| 589 ||Wide Array Sonar
|-
| 590 ||Torpedo Defences
|-
| 591 ||General Stores
|-
| 592 ||Alien Containment
|-
| 593 ||Gauss Defences
|-
| 594 ||Sonic Defences
|-
| 595 ||P.W.T. Defences
|-
| 596 ||Pressure Bombardment Shield
|-
| 597 ||Molecular Control Shield
|-
| 598 ||Molecular Control Laboratory
|-
| 599 ||Transmission Resolver
|-
| 600 ||Sub Pen
|-
| 601 ||USA
|-
| 602 ||ALASKA
|-
| 603 ||EURO-SYNDICATE
|-
| 604 ||ARABIAN BLOC
|-
| 605 ||EGYPTIAN CARTEL
|-
| 606 ||AFRICA CORP
|-
| 607 ||BRAZILIAN UNION
|-
| 608 ||NEW MEXICO
|-
| 609 ||ASIAN COALITION
|-
| 610 ||SCANDINAVIA
|-
| 611 ||NEO-JAPAN
|-
| 612 ||FREE CHINA
|-
| 613 ||AUSTRALASIA
|-
| 614 ||FED KOREA
|-
| 615 ||EURASIA
|-
| 616 ||ICELANDIC UNION
|-
| 617 ||The Heavy Thermic Lance is a more powerful version of the TL. Twin heat sources and a extremely high rotation speed means that the Heavy Thermic lance is virtually unstoppable against all materials.
|-
| 618 ||THE ENEMY HAS ENTERED AN OCEAN DEEP BEYOND THE DEPTH CAPABILITY OF THIS FLYING SUB.
|-
| 619 ||X-Com Aqua-facilities cannot be built on land
|-
| 620 ||Sonic Oscillator
|-
| 621 ||
|-
| 622 ||
|-
| 623 ||
|-
| 624 ||Submersible Weapons System
|-
| 625 ||Civilian
|-
| 626 ||Jan
|-
| 627 ||Feb
|-
| 628 ||Mar
|-
| 629 ||Apr
|-
| 630 ||May
|-
| 631 ||Jun
|-
| 632 ||Jul
|-
| 633 ||Aug
|-
| 634 ||Sep
|-
| 635 ||Oct
|-
| 636 ||Nov
|-
| 637 ||Dec
|-
| 638 ||International Relations
|-
| 639 ||Organisation
|-
| 640 ||Funding
|-
| 641 ||Change
|-
| 642 ||WEAPON
SYSTEMS
|-
| 643 ||CREW
|-
| 644 ||SWSs
|-
| 645 ||DAMAGE>
|-
| 646 ||The Air-lock allows equipment and personnel to be transferred into or out of an undersea base. It is always the first facility to be constructed at a new site. The Air-lock area is vulnerable to intrusion from any potential hostile force.
|-
| 647 ||Each accommodation area provides for up to 50 personnel. The facilities are somewhat basic and functional.
|-
| 648 ||Fifty scientists can work in a single laboratory block. Laboratories are equipped with all the latest technologies for research into materials, biochemistry and weaponry. X-Com has access to all the best research labs throughout the world, both civilian and military.
|-
| 649 ||A workshop contains all the equipment necessary to manufacture equipment based on the latest designs from the science labs. 50 Technicians can occupy one workshop, items under construction will also consume space.
|-
| 650 ||A standard sonar system has an effective range of over 450 kilometres at most depths and is linked to geostationary satellite nets for surface analysis. Each scanner has a 5% chance of detecting a submersible or airborne craft per 10 minute scan cycle.
|-
| 651 ||A wide array sonar system has an effective range of over 700 kilometres at all depths and is linked to geostationary satellite nets for surface analysis. Each scanner has a 5% chance of detecting a submersible or airborne craft every 10 minute scan cycle.
|-
| 652 ||Torpedo defence systems provide protection against attack by hostile submersibles which are attempting to dock at the base.
|-
| 653 ||All equipment, weapons systems, munitions, recovered material and Submersible Weapons Systems are placed in stores, with the exception of equipment assigned to Subs in Pens.
|-
| 654 ||Live Aliens will require special containment facilities to hold them. These units maintain their life systems and render their combat potential to zero. The containment facility can keep 10 Alien life forms in confinement units.
|-
| 655 ||The Gauss defence provides the latest and most effective protection against attack by hostile submarines.
|-
| 656 ||Sonic Oscillator defences provide powerful and efficient protection against aggressors.
|-
| 657 ||Pulse Wave Torpedoes provide the most effective defence against Alien attacks. These missiles have super dense war heads which can penetrate all known armour. The magnetic waves they produce disable electronic defences.
|-
| 658 ||The Pressure Bombardment shield protects the base from Alien submersibles docking and sets up a resonating field that repulses attacking subs long enough for defence systems to fire repeatedly. In effect this doubles the effectiveness of any defence systems already deployed.
|-
| 659 ||Since Alien subs utilise Molecular Control Technology to detect the presence of living creatures, using a negative M.C. emitter will blanket a base with an impenetrable shield to confuse the Aliens and disguise our presence
|-
| 660 ||The Molecular Control lab can implant and train up to ten aquanauts at one time.. Implants are surgically installed in the skulls of aquanauts. Extensive training allows them to utilise their implants. Implant skills are used in conjunction with a Molecular Devices and can be used for attacks during combat.
|-
| 661 ||Alien communications utilise the Molecular control implant network the Aliens have built up. The transmission resolver facility intercepts Alien Sub transmissions and decodes the information. This will show the type of Alien Sub, the Alien race and the type of activity that is occurring.
|-
| 662 ||Each Pen can accommodate one submarine. There are facilities for maintenance, refuelling and repair of the X-Com submarine fleet. Each Flying Sub stationed at a base must have a free Pen assigned to it which cannot be used by other Subs, even if the assigned submarine is out on a mission.
|-
| 663 ||The X-Com dart gun is a small, accurate, high powered unit with a 10 hollow dart ammo clip. The darts are fired by a gas cartridge in the ammo pod.
|-
| 664 ||This aqua-rifle is accurate and powerful, firing hollow steel harpoons from sealed packs of 10. Each harpoon has its own gas reservoir.
|-
| 665 ||The heavyweight of the gas technology family, this cannon fires solid bolts, some with HE or phosphor tips. A favourite weapon amongst experienced aquanauts.
|-
| 666 ||Hydro-Jet Cannons are a heavy infantry weapon system. The cannon fires magnesium fuelled mini-torpedoes. Although powerful, the Hydro-Jet Cannon is a clumsy and unwieldy device, suitable for aquatic use only.
|-
| 667 ||A real heavyweight, this large launcher fires three types of torpedo, each with its own propulsion unit. A devastating weapon, with only manual loading being its drawback. Ammunition types available include large or small high explosive and phosphor tipped torpedoes, all for submerged use only.
|-
| 668 ||The Gauss pistol uses accelerated particle technology, a new development in modern weaponry. It is fast, accurate and functions above and below water. Gauss technology is a development of the Plasma technologies learned from the previous war.
|-
| 669 ||A step beyond the Gauss pistol, the rifle packs a real punch, with its twin particle accelerators. Replacing the Elerium powered Plasma system we have utilised a micro particle accelerator that generates a stream of anti-protons.
|-
| 670 ||The heavy Gauss is cumbersome, but extremely effective. It operates with 3 particle accelerators and is virtually unstoppable. The anti-proton stream is confined inside a Gallium Arsenide shell that implodes on impact releasing the anti-matter.
|-
| 671 ||This standard issue grenade has an accurate and sophisticated timer for precision control.
|-
| 672 ||Dye grenades are dual role items, useful for providing cover in exposed situations. Functioning in both water and land environments the dye is ejected as a particle cloud, producing an octopus like ink spray in water or dense air borne cloud on land.
|-
| 673 ||A proximity grenade which can be thrown like an ordinary grenade but is triggered by nearby movement after it is deployed. Skill and training are required to use these devices properly.
|-
| 674 ||This explosive should only be used for demolition purposes. However past experience has shown that these powerful explosive packs are ideal weapons for rooting out Aliens. The blast radius is large so ensure no aquanauts are within the minimum safe distance.
|-
| 675 ||This new device uses a variety of detectors and advanced computer systems to identify moving enemy units in water. Click on the Disturbance Sensor icon on the tactical display. Select 'Use Sensor' from the menu. The Sensor display shows an arrow in the centre which is the direction the aquanaut is facing (North is at the top). The blips show units which have moved recently. Large units, or fast moving units, will produce larger blips. Static units will not show up.
|-
| 676 ||To use this you face the injured X-Com agent or stand over the body of a stunned aquanaut.
HEALING> Red indicates wounds. Select body part and click on the 'Heal' button. One fatal wound will be healed and health restored.
STIMULANT> Restores energy and revives stunned aquanauts. To revive an unconscious aquanaut you must stand directly over the body.
PAIN KILLER> Restores the morale of wounded aquanauts.
|-
| 677 ||The ultimate in M.C. technology. This can only be used underwaterby aquanauts with M.C. skills. Click on the Disruptor, select the type of attack, and select a target unit with the cursor. There are two types of Disruptor attack:
JAM IMPLANT> If successful the unit becomes confused and it may panic.
CONTROL IMPLANT> If successful you will gain control of the enemy unit.
|-
| 678 ||This device can only be used in close combat, but will stun a living organism without killing it by freezing the creature.
|-
| 679 ||The subject has died due to the trauma of interrogation.
|-
| 680 ||Inside the bodies of Aliens we have found small surgically implanted units. These are Control Implants designed by the Aquatoids to allow the constant supply of information from the battlefield, even at great distances. The Molecular Control Reader is an Alien communication device which is used to take information directly from M.C. Implants. X-Com units can use this device in combat to display an Alien's characteristics. Select the 'use' option. Then click on an Alien with the cursor.
|-
| 681 ||Sonic pistols are an Alien weapon based on ultra-sonic audio waves that can jellify bone in seconds. The Ultra-Sonic waves occupy a range beyond the scope of human hearing.
|-
| 682 ||A more powerful Sonic device. Not even high carbon steel is immune to this weapon. The highly compact wave emitter is enhanced by a super conductor amplifier to increase the power of this weapon.
|-
| 683 ||Size
|-
| 684 ||The corpse may be researched for a full autopsy report.
|-
| 685 ||Not enough ammunition to arm
|-
| 686 ||This is an Alien aquatic use only guided weapon firing self propelled 'Disruptor Projectiles'. When you click to fire the weapon it will generate 'way points' for the Projectile to follow. When you have positioned enough way points click on the launch icon.
|-
| 687 ||A small Thermal Shok launcher which fires chemical freeze bombs. Very useful for capturing live Aliens.
|-
| 688 ||This device works in the same way as a standard issue grenade - except that it is many times more powerful. The grenade uses a single pulse sonic blast that is emitted in all directions simultaneously.
|-
| 689 ||Survey Ship
|-
| 690 ||Escort
|-
| 691 ||Cruiser
|-
| 692 ||Heavy Cruiser
|-
| 693 ||Hunter
|-
| 694 ||Battleship
|-
| 695 ||Dreadnought
|-
| 696 ||Fleet Supply Cruiser
|-
| 697 ||RATING>
|-
| 698 ||TERRIBLE!
|-
| 699 ||POOR!
|-
| 700 ||OK
|-
| 701 ||GOOD!
|-
| 702 ||EXCELLENT!
|-
| 703 ||SCORE
|-
| 704 ||X-COM MONTHLY REPORT
|-
| 705 ||Month>
|-
| 706 ||The committee of funding organisations is generally satisfied with your progress so far.
|-
| 707 ||The committee of funding organisations is very pleased with your excellent progress. Keep up the good work.
|-
| 708 ||The committee of funding organisations is dissatisfied with your performance. You must improve your effectiveness in dealing with the Alien menace or risk termination funding support for X-Com.
|-
| 709 ||You have not succeeded in dealing with the Alien invasion and the committee of funding organisations has regrettably decided to terminate funding X-Com. Each organisation shall deal with the problem as they see fit. We can only hope that we can come to some accommodation with these ancient forces, and that the general population will come to terms with the aquatic visitors.
|-
| 710 || is particularly pleased with your ability to deal with the localised threat and has agreed to increase its funding.
|-
| 711 || are particularly happy with your progress in dealing with local Alien incursion and have agreed to increase their funding.
|-
| 712 || and
|-
| 713 || is unhappy with your ability to deal with Alien activity in its Seas and has decided to reduce its financial commitment.
|-
| 714 || are unhappy with your ability to deal with Alien activity in their Sea and have decided to reduce their funding.
|-
| 715 ||km
|-
| 716 || has signed a co-operation agreement with the Alien forces and has withdrawn from X-Com funding.
|-
| 717 || have signed a co-operation agreement with Alien forces and have withdrawn from the X-Com funding.
|-
| 718 ||Monthly Rating>
|-
| 719 ||Funding change>
|-
| 720 ||The funding organisation is not happy with your financial position. You must reduce your debts below $2million or the X-Com will be terminated.
|-
| 721 ||SUB-PARTICLE TRANSMISSIONS RESOLVED
|-
| 722 ||SUB TYPE
|-
| 723 ||RACE
|-
| 724 ||MISSION
|-
| 725 ||ZONE
|-
| 726 ||Allocate Research
|-
| 727 ||Allocate Manufacture
|-
| 728 ||Azores
|-
| 729 ||Reykjavik
|-
| 730 ||Bermuda
|-
| 731 ||New York
|-
| 732 ||Boston
|-
| 733 ||Fort Severn
|-
| 734 ||Dakar
|-
| 735 ||Recife
|-
| 736 ||Accra
|-
| 737 ||Ascension Island
|-
| 738 ||Trinidade Island
|-
| 739 ||Falkland Island
|-
| 740 ||Canary Islands
|-
| 741 ||Anchorage
|-
| 742 ||St Lawrence Island
|-
| 743 ||San Francisco
|-
| 744 ||Midway Island
|-
| 745 ||Vancouver
|-
| 746 ||Tasmania
|-
| 747 ||Hawaii
|-
| 748 ||Fiji
|-
| 749 ||Tonga
|-
| 750 ||Easter Island
|-
| 751 ||Galapagos Island
|-
| 752 ||Wellington
|-
| 753 ||Solomon Island
|-
| 754 ||Crete
|-
| 755 ||Lisbon
|-
| 756 ||Port Said
|-
| 757 ||Marseilles
|-
| 758 ||Tripoli
|-
| 759 ||Manila
|-
| 760 ||Hong Kong
|-
| 761 ||Singapore
|-
| 762 ||Bangkok
|-
| 763 ||Darwin
|-
| 764 ||Bombay
|-
| 765 ||Seychelles Island
|-
| 766 ||Maldive Island
|-
| 767 ||Sri Lanka
|-
| 768 ||Mauritius
|-
| 769 ||Tokyo
|-
| 770 ||Shanghai
|-
| 771 ||Vladivostok
|-
| 772 ||London
|-
| 773 ||Faeroe Island
|-
| 774 ||Aberdeen
|-
| 775 ||Oslo
|-
| 776 ||Jamaica
|-
| 777 ||Panama
|-
| 778 ||Miami
|-
| 779 ||X-Com:� Terror from the Deep
|-
| 780 ||New Game
|-
| 781 ||Load Saved Game
|-
| 782 ||Select Difficulty Level
|-
| 783 ||1> Beginner
|-
| 784 ||2> Experienced
|-
| 785 ||3> Veteran
|-
| 786 ||4> Genius
|-
| 787 ||5> Superhuman
|-
| 788 ||Time
|-
| 789 ||Date
|-
| 790 ||Select game to load
|-
| 791 ||Select save position
|-
| 792 ||MOLECULAR CONTROL TRAINING
|-
| 793 ||Remaining M.C. capacity>
|-
| 794 ||M.C.
Strength
|-
| 795 ||M.C. Skill
/Improvement
|-
| 796 ||M.C. Reader
|-
| 797 ||In
Training?
|-
| 798 ||TARGETTED BY:
|-
| 799 ||WEAPONS/
CREW/SWSs
|-
| 800 ||ABANDON GAME
|-
| 801 ||Quit to DOS
|-
| 802 ||is low on fuel,
returning to base
|-
| 803 ||Aquanaut List
|-
| 804 ||RANK>
|-
| 805 ||MISSIONS>
|-
| 806 ||KILLS>
|-
| 807 ||WOUND RECOVERY>
|-
| 808 ||TIME UNITS
|-
| 809 ||STAMINA
|-
| 810 ||HEALTH
|-
| 811 ||BRAVERY
|-
| 812 ||REACTIONS
|-
| 813 ||FIRING ACCURACY
|-
| 814 ||THROWING ACCURACY
|-
| 815 ||STRENGTH
|-
| 816 ||M.C. STRENGTH
|-
| 817 ||M.C. SKILL
|-
| 818 ||NEW RANK
|-
| 819 ||Promotions
|-
| 820 ||AQUANAUTS
|-
| 821 ||Automated SWS's have high manuverability and hull strength. They provide heavy troop support at all depths. SWS's are re-armed automatically if you have enough ammunition.
|-
| 822 ||This submersible is armed with Aqua-Jet torpedoes. This weapon system only functions underwater. Ensure stores are well stocked with Aqua-Jet Torpedoes.
|-
| 823 ||Gauss technology provides a powerful weapon system for SWS's. Offering heavy firepower compared with earlier models, and uses proprietary X-Com technology.
|-
| 824 ||Alien technology has redefined the SWS. The ability to utilise Ion Displacers means that SWS's are no longer restricted to the land/seabed. Sonic weaponry gives a real advantage in battle.
|-
| 825 ||This SWS features Pulse Wave weapons for aquatic use. You must manufacture PWT's to keep them fully armed. To fire, select a number of 'way points' then click on the launch icon.
|-
| 826 ||This compact device is used as ammunition for a Heavy Sonic Gun. It contains a small quantity of Zrbite.
|-
| 827 ||This small object is used as a power source for a Sonic Rifle, a potent Alien weapon, and contains a small quantity of Zrbite.
|-
| 828 ||Power source for the compact Alien Sonic Pistol. Contains Zrbite - the source of all Alien power.
|-
| 829 ||The Thermal Shok bomb is used for capturing live humans, but it can also be used against most Alien races. It is fired from a Thermal Shok Cannon.
|-
| 830 ||The Vibroblade is a long sharp knife blade of titanium which spins at over 6000 rpm, this device can crack even the toughest diving armour. The power source is an Alien invention, our attempt at building these items before met with dismal failure, our blades rotated too slowly or exploded under pressure.
|-
| 831 ||The Thermic Lance is a logical extension of the Vibroblade technology The blade revolves at high speed and a Zrbite power source superheats the blade to cut armour like a warm knife through butter
|-
| 832 ||The Alien Probe Mission is used for correlating data about the seabed, the resources, shipping and aeroplane flight paths of an area. The Alien subs involved in these missions are not a major threat in themselves, but they indicate sites of activity that may flare at any time.
|-
| 833 ||The Aliens have a policy of policing areas they are interested in, sending out craft with the express purpose of securing an area before more intensive missions are begun. They will land at specific sites they intend to raid later to lock down the areas and prepare the way for the next level of activity.
|-
| 834 ||The sinking of ships and the downing of aircraft are key elements of the Alien strategy. The acquisition of materials is one of the prime Alien activities and as such is allied to these overtly aggressive acts. The Aliens also raid areas of geo-thermal activity, mining sites and sites of antiquity for minerals and refined metals and other human produced items.
|-
| 835 ||This can result in official contact between Aliens and corporations or governments at the highest level. The climax of this activity is characterised by intense Alien Sub activity in the waters of the organisation concerned. The Aliens will attempt to sign an agreement with a government or organisation by offering knowledge of their superior technologies. This Alien activity represents a major threat to X-Com. If a corporation or government co-operates with the invaders then its funding ceases.
|-
| 836 ||Aliens will construct secret undersea colonies in remote locations. After some initial reconnaissance flights some intense Alien Sub activity will occur as the colony is being built. These colonies are known to contain labs, cloning centres, surgical facilities for human and Alien experimentation. The presence of Alien colonies will generate more Alien activity without the presence of Alien Subs. In order to locate a colony an X-Com sub must patrol an area for a few hours to stand some chance of successful detection.
|-
| 837 ||When the Aliens need humans they terrorise a port, attack an island, or raid a ship. Civilians will be directly threatened, to fulfil the perverse breeding needs of the Aliens and their hideous experiments.
|-
| 838 ||If X-Com intercept subs are being particularly successful in sinking Alien craft then the Aliens may take some aggressive retaliatory action. This could result in a direct attack against an X-Com facility. However, the Aliens have to find an X-Com base in order to attack it, and provided Alien Subs are kept away then there should be little danger of an assault.
|-
| 839 ||Once an Alien colony is constructed then it is re-supplied on a regular basis by a special supply ship. If one of these vessels is detected while touching down then it is certain that an Alien colony is nearby.
|-
| 840 ||This tiny submarine is used for reconnaissance and survey missions. It normally precedes larger vessels at the start of an Alien task force.
|-
| 841 ||A medium sized escort vessel that is of little threat on its own. This craft precedes the arrival of larger vessels and increased activities.
|-
| 842 ||The Cruiser is a general purpose craft, the mainstay of the Alien fleet, it is used in all types of Alien missions and is a dangerous adversary.
|-
| 843 ||The heavy cruiser is a more powerful ship than the cruiser, larger weapons and propulsion systems boost its power. The Heavy Cruiser is used for resource missions to collect large quantities of minerals and equipment.
|-
| 844 ||This vessel is equipped with an examination room for performing experiments and surgery on human subjects. The victims are subjected to the foulest tortures and the brain is often removed and stored for processing en-route.
|-
| 845 ||The battleship is the most aggressive ship the Aliens posses, it features all the Alien technologies and systems to act as a base of operations for any form of aggressive act the Aliens may want to perform, it carries a wide array of weapons.
|-
| 846 ||The Dreadnought is a super troop carrier, fully equipped with all Alien technologies and a vast payload. The Dreadnought is a tough and formidable opponent.
|-
| 847 ||The supply vessel is used during the construction of Alien colonies or for supplying existing colonies. It carries Alien nutrients, DNA, foetuses and other biological components.
|-
| 848 ||Dismantle
|-
| 849 ||AQUA-POD IN USE
|-
| 850 ||CANNOT DISMANTLE AQUA-POD!�All base Pods must be linked to the air-lock.
|-
| 851 ||Transfer Items to
|-
| 852 ||NO ALIEN CONTAINMENT FOR TRANSFER!�Live Aliens need an Alien containment equipment in order to survive.
|-
| 853 ||AMOUNT AT
DESTINATION
|-
| 854 ||Alien dies as there is no Alien containment facility
|-
| 855 ||NO FREE ACCOMODATION!�The destination base does not have enough space in the living quarters for the crew assigned to the sub.
|-
| 856 ||Items Arriving
|-
| 857 ||Dart Gun
|-
| 858 ||Dart Clip
|-
| 859 ||Jet Harpoon
|-
| 860 ||Harpoon Clip
|-
| 861 ||Gas Cannon
|-
| 862 ||GC-AP Bolts
|-
| 863 ||GC-HE Bolts
|-
| 864 ||GC-Phosphorous Bolts
|-
| 865 ||Hydro-Jet Cannon
|-
| 866 ||HJ-AP Ammo
|-
| 867 ||HJ-HE Ammo
|-
| 868 ||HJ-P Ammo
|-
| 869 ||Torpedo Launcher
|-
| 870 ||Small Torpedo
|-
| 871 ||Large Torpedo
|-
| 872 ||Phosphor Torpedo
|-
| 873 ||Gauss Pistol
|-
| 874 ||Gauss Rifle
|-
| 875 ||Heavy Gauss
|-
| 876 ||Magna-Blast Grenade
|-
| 877 ||Dye Grenade
|-
| 878 ||Particle Disturbance Grenade
|-
| 879 ||Magna-Pack Explosive
|-
| 880 ||Particle Disturbance Sensor
|-
| 881 ||Medi-Kit
|-
| 882 ||M.C. Disruptor
|-
| 883 ||Thermal Tazer
|-
| 884 ||Sonic Cannon
|-
| 885 ||Cannon Power Clip
|-
| 886 ||Sonic-Blasta Rifle
|-
| 887 ||Blasta Power Clip
|-
| 888 ||Sonic Pistol
|-
| 889 ||Pistol Power Clip
|-
| 890 ||Disruptor Pulse Launcher
|-
| 891 ||Disruptor Ammo
|-
| 892 ||Thermal Shok Launcher
|-
| 893 ||Thermal Shok Bomb
|-
| 894 ||Sonic Pulser
|-
| 895 ||Zrbite
|-
| 896 ||M.C. Reader
|-
| 897 ||Aquatoid Corpse
|-
| 898 ||Gill Man Corpse
|-
| 899 ||Lobster Man Corpse
|-
| 900 ||Tasoth Corpse
|-
| 901 ||Calcinite Corpse
|-
| 902 ||Deep One Corpse
|-
| 903 ||Bio-Drone Corpse
|-
| 904 ||Tentaculat Corpse
|-
| 905 ||Triscene Corpse
|-
| 906 ||Hallucinoid Corpse
|-
| 907 ||Xarquid Corpse
|-
| 908 ||Not enough rounds to arm SWS
|-
| 909 ||Not enough Torpedoes to arm SWS
|-
| 910 ||Not enough PWT's to arm SWS
|-
| 911 ||Not enough equipment to fully re-equip squad
|-
| 912 ||SHOTS
|-
| 913 ||This Armour utilises the newly discovered Alien substance, Aqua-plastic, and ensures our Aquanauts are given a fighting chance against the Alien incursion
|-
| 914 ||A powerful new protection for Aquanauts, this armour is powered by an ION energy source and greatly amplifies the speed and strength of the wearer, it offers the best protection yet for combat troops.
|-
| 915 ||An enhancement for the ION armour incorporating the Magnetic Array technology to allow full freedom of movement in the aquatic environment.
|-
| 916 ||
in order to use or produce the

|-
| 917 ||The Aliens have destroyed the undefended base
|-
| 918 ||X-Com patrols have located an Alien colony in
|-
| 919 ||STANDOFF
|-
| 920 ||CAUTIOUS ATTACK
|-
| 921 ||STANDARD ATTACK
|-
| 922 ||AGGRESSIVE ATTACK
|-
| 923 ||DISENGAGING
|-
| 924 ||ALIEN SUB HIT!
|-
| 925 ||ALIEN SUB DESTROYED!
|-
| 926 ||ALIEN SUB DOWNED!
|-
| 927 ||Minimise at Stand-off Range Only
|-
| 928 ||ALIEN SUB RETURN FIRE!
|-
| 929 ||>>> FLYING SUB DAMAGED <<<
|-
| 930 ||>>> FLYING SUB DESTROYED <<<
|-
| 931 ||ALIEN FLYING SUB ESCAPING!
|-
| 932 ||ALIENS LAUNCH
|-
| 933 ||Wide band Detection
|-
| 934 ||STORES
|-
| 935 ||Difficulty Level
|-
| 936 ||INTERCEPT
|-
| 937 ||BASES
|-
| 938 ||GRAPHS
|-
| 939 ||UFOPEADIA
|-
| 940 ||OPTIONS
|-
| 941 ||FUNDING
|-
| 942 ||5 Secs
|-
| 943 ||1 Min
|-
| 944 ||5 Mins
|-
| 945 ||30 Mins
|-
| 946 ||1 Hour
|-
| 947 ||1 Day
|-
| 948 ||X-Com Performance Roster
|-
| 949 ||Enter Name
|-
| 950 ||Performance Rating
|-
| 951 ||Victory Date
|-
| 952 ||Chemical-flare
|-
| 953 ||This compact device produces a bright flare of light at any depth or on dry land. This illuminates enemy units in the vicinity of the flare during deep sea or night missions.
|-
| 954 ||Monthly Costs
|-
| 955 ||Flying Sub Rental
|-
| 956 ||Salaries
|-
| 957 ||Base maintenance
|-
| 958 ||Cost per unit
|-
| 959 ||Quantity
|-
| 960 ||Total
|-
| 961 || day
|-
| 962 || days
|-
| 963 ||In M.C. Implantation
|-
| 964 ||This device is a Disruptor Pulse Projectile fitted with an onboard computer guidance system. It is fired from a Disruptor Pulse launcher.
|-
| 965 ||Please look up the page listed below in your Game Manual, and enter the eight digit code listed at the bottom of the page.
EG: Page 13 of Game Manual Code: 3994-9668
Please Enter the Code from Page
|-
| 966 ||Front Armour
|-
| 967 ||Left Armour
|-
| 968 ||Right Armour
|-
| 969 ||Rear Armour
|-
| 970 ||Lower Armour
|-
| 971 ||ALIEN ACTIVITY SITE-
|-
| 972 ||SHIP RESCUE MISSION
|-
| 973 ||This mission is a bug hunt, eliminate all Alien units on the ship, and preserve the lives of any civilians onboard. The Aliens are dispersed above and below decks, secure the upper decks before entering the lower ones. To quit, place aquanauts into the flying sub and click on the 'Abort Mission' icon.
|-
| 974 ||Now the upper deck is clear proceed to the lower decks. Using the cargo lift you descend into the hold. Your squad must eliminate all Aliens on this level to complete the mission. To abort place all aquanauts on the lift start point and click on 'Abort Mission' icon.
|-
| 975 ||ALIEN ACTIVITY DETECTED
|-
| 976 ||
|-
| 977 ||ALIEN CONTACT SITE MISSION
|-
| 978 ||This mission is a raid on a freshly activated Alien communications site. There are 2 levels to the site, the seabed with its Alien pyramids and a hidden Alien complex. Get all the aquanauts to the entrance of the complex and click on the 'Abort Mission' icon to proceed. To quit, place aquanauts into the flying sub and click on the 'Abort Mission' icon.
|-
| 979 ||Having negotiated the Alien structures and entered the complex the mission goals are clear. Penetrate the heart of the Alien facility and destroy the Synomium Molecular Control Device to complete the mission. To abort place all aquanauts on the access lift start point and click on 'Abort Mission' icon.
|-
| 980 ||ALIENS ATTACK
|-
| 981 ||SHIPPING ROUTE
|-
| 982 ||ALIENS LAUNCH PORT ATTACK
|-
| 983 ||Aliens have launched an attack against surface sites. The port and its civilian population have been put at risk. Your squad must eliminate all Aliens and protect the innocent bystanders from this Alien incursion. To quit, place aquanauts into the flying sub and click on the 'Abort Mission' icon.
|-
| 984 ||PORT ATTACK ON
|-
| 985 ||ISLAND ATTACK ON
|-
| 986 ||ALIENS LAUNCH ISLAND ATTACK
|-
| 987 ||Aliens have launched an attack against surface sites. The island and its civilian population have been put at risk. Your squad must eliminate all Aliens and protect the innocent bystanders from this Alien incursion. To quit, place aquanauts into the flying sub and click on the 'Abort Mission' icon.
|-
| 988 ||THIS EQUIPMENT WILL NOT FUNCTION ABOVE WATER
|-
| 989 ||ALIEN COLONY-
|-
| 990 ||ALIEN COLONY ATTACK MISSION
|-
| 991 ||This mission is a raid on an Alien colony site. There are 2 levels to the site, get all the aquanauts to the glowing exit in the first complex and click on the 'Abort Mission' icon to proceed. Any equipment left behind will stay on the seabed until the 2nd section is resolved. To quit, place aquanauts into the Submarine and click on the 'Abort Mission' icon.
|-
| 992 ||Having negotiated the first level and entered the core of the colony. The mission is to now destroy the control centre, the Synomium Device, or eliminate all Aliens. To abort place all aquanauts on the start point and click on 'Abort Mission' icon. All viable X-Com equipment will be returned to base.
|-
| 993 ||
|-
| 994 ||SIGSBEE DEEP MISSION
|-
| 995 ||ALIEN CITY LEVEL ONE
|-
| 996 ||We are entering the unknown, from here on in there could be anything waiting for us. We know there are 2 further levels to the Alien city and your squad must race to the exit on this level to enter the next. Place all aquanauts on the exit and click the 'Abort Mission' icon to advance.Aborting elsewhere will terminate the mission.
|-
| 997 ||
|-
| 998 ||T'LETH ATTACK MISSION
|-
| 999 ||ALIEN CITY LEVEL TWO
|-
| 1000 ||Further into the unknown, from here on in there could be anything waiting for us. We know there is a further level to the Alien city and your squad must race to the exit on this level to enter the next. Place all aquanauts on the exit and click the 'Abort Mission' icon to advance.Aborting elsewhere will terminate the mission.
|-
| 1001 ||
|-
| 1002 ||FINAL T'LETH MISSION
|-
| 1003 ||ALIEN CITY LEVEL THREE
|-
| 1004 ||The end is in sight, from here on in we are searching for the crypt of the Ultimate Alien. Destroy the 8 power feeds to the tomb to finish off the Alien threat. Don't give up now! Aborting will terminate the mission.
|-
| 1005 ||Gauss Cannon Ammo
|}
==See Also==
* [[ENGLISH.DAT]]
* [[GEOSCAPE.EXE]] - Uses the strings in this file.
* [[GEODATA]] - Parent Folder for this file.
* [[GeoScape String Files]] - A summary of the use of these strings.
* [[Tactical String Files]] - The BattleScape equivalents of these files.
* [[Saved Game Files]]
[[Category:Game Files]]

ENGLISH.DAT

2010-10-28T04:09:56Z

Hatfarm:

This is [[GeoScape String Files|one of the files]] containing the strings used by the [[GEOSCAPE.EXE|geoscape game engine]]. Each string is terminated by a null character (x00). Line breaks are defined by x0A. Every now and then x02 pops up, not sure why, probably something to do with the large font.

There are 972 entries in all, not all of which are used by the release version of the game.

{| {{StdDescTable}}
|- {{StdDescTable_Heading}}
! Index !! English.Dat (46601 Bytes)
|-
| 000/x000 || TRANSPORTER AND COMBAT SPACECRAFT. THE ULTIMATE REPLICATION OF ALIEN TECHNOLOGY.
|-
| 001/x001 || COMBAT AIRCRAFT WITH DUAL PULSE DETONATION ENGINES AND SPECIALLY SHIELDED ELECTRONIC SYSTEMS. THE BEST AVAILABLE EARTH BASED TECHNOLOGY.
|-
| 002/x002 || TRANSPORTER AND COMBAT CRAFT. A CRUDE BUT EFFECTIVE REPLICATION OF ALIEN PROPULSION SYSTEMS.
|-
| 003/x003 || TROOP TRANSPORTER. THE FASTEST OF ITS KIND, WITH VERTICAL TAKE OFF AND LANDING (V.T.O.L) CAPABILITY.
|-
| 004/x004 || COMBAT CRAFT. THIS ONE-MAN FIGHTER REPLICATES THE CLASSIC ALIEN FLYING SAUCER DESIGN, WITH CENTRAL PROPULSION UNIT.
|-
| 005/x005 || ADVANCED AIR TO AIR MISSILE WITH SPECIALLY SHIELDED ELECTRONICS.
|-
| 006/x006 || AIR TO AIR MISSILE WITH NUCLEAR WARHEAD, BUT AN EXTREMELY HEAVY LOAD.
|-
| 007/x007 || HIGH POWERED CANNON WHICH FIRES ARMOUR PIERCING ROUNDS CAPABLE OF PENETRATING 16 INCHES OF STEEL.
|-
| 008/x008 || THIS LAUNCHER FIRES A BALL SHAPED MISSILE POWERED BY ANTI-MATTER REACTION. THE BALL DESTROYS THE TARGET WITH A GRAVITY WAVE IMPLOSION.
|-
| 009/x009 || THIS CONVENTIONAL LASER BEAM IS POWERED BY AN ANTI-MATTER REACTION CHAMBER.
|-
| 010/x00A || THE GRAVITY BEAM DIRECTS A FINELY CHANNELLED IMPLODING GRAVITY FIELD.
|-
| 011/x00B || The Sectoid Hierarchy ranges from soldiers to leaders with powerful psionic abilities. These psionic powers can be used to demoralise soldiers in combat, or even take control of their minds. They tend to indulge in human abductions and cattle mutilation. The abduction is used to extract genetic material for cross breeding and developing clones for infiltrating human society. The cattle provide both nutrition and genetic material. This race appears to want to develop superior genetic hybrids to increase the efficiency of their hive-like society.
|-
| 012/x00C || The autopsy reveals vestigial digestive organs and a simple structure. The brain and eyes are very well developed. The structure suggests genetic alteration or mutation. The small mouth and nose appear to have little function. The webbing between the fingers, and the flat feet suggest aquatic origins. There are no reproductive organs, and no clues as to how this species can reproduce. They are most probably a genetically engineered species.
|-
| 013/x00D || This race developed in an extremely hostile environment. They are extremely tough and can resist extreme temperature variations. Their mobility depends on a snake-like giant 'foot' which protects all the vital organs. Their objectives appear to be purely predatory and they appear to be under the command of some other Intelligence which directs their military-style incursions on earth.
|-
| 014/x00E || The skin is extremely tough and heat resistant. The cardio-vascular system is part of the muscular system which uses the hydraulic principle to create motion. The only true muscle is the 'heart'. The reproductive system appears to be very efficient. Reproduction is asexual, with each snakeman carrying up to fifty eggs inside its body at any one time. Left to its own devices this species would be a severe threat to life on earth.
|-
| 015/x00F || This being has awesome mental powers which allow for telepathic communication and telekinetic abilities. The apparently weak physical abilities of this creature are sustained by its mental powers. We do not understand how these telekinetic powers work, since they seem to defy the laws of physics as we know them. They are extremely dangerous in any combat situation, where they rely on their mental powers for combat. They rarely appear on earth since they seem to rely on other races to pursue their objectives.
|-
| 016/x010 || This being is physically retarded and seems incapable of sustaining any life functions. The muscles are severely atrophied and the internal organs appear to be under-developed. The sensory organs, including the eyes, do not appear to function at all. The brain, however, is well developed and draws on a high proportion of the body's blood supply. It is a mystery as to how this creature can sustain itself without external support.
|-
| 017/x011 || This humanoid creature is physically powerful and intelligent. They have a particular appetite for consuming raw flesh of any kind, which they need for sustenance like earth based carnivores. They appear to rely on telepathic commands from a race known as 'Ethereals'. Once separated from this telepathic link their mental system appears to break down and they die. The cybernetic implants are used to enhance their combat performance. They are clearly the foot soldiers for a higher intelligence.
|-
| 018/x012 || The 'skin' of this creature appears to be an organically created protective armour which is grafted onto the body. There are numerous cybernetic implants which are used to enhance the cardio-vascular system and the senses. The reproductive organs appear to have been surgically removed. Evidently these unfortunate creatures are limited to a life of warfare and conquest. Armour piercing ammunition is not very effective against their toughened skin.
|-
| 019/x013 || This life-form has the mysterious natural ability to float through the air. It appears to detect human brain waves and will move towards a human target even if well hidden. Once a target is detected the Celatid lands and fires small globules of extremely corrosive venom. The creature has the ability to clone itself at an alarming rate. It accompanies the Muton race in its wonderings.
|-
| 020/x014 || The core contains a small bio-mechanical device which appears to be a naturally evolved anti-gravity propulsion system. The sac of venom is the largest organ and there does not appear to be a separate brain structure. There is no discernible digestive or reproductive system. A small organ contains embryos which can grow rapidly into a new being.
|-
| 021/x015 || This silicon based life form generates an enormous amount of heat. It has the strength to crush rocks which can then be ingested by the hot core. It has a primitive intelligence and can be controlled by implants or telepathic beings. It works with the Muton alien race.
|-
| 022/x016 || The core of the creature is extremely hot, and seems to be the basis for a digestive system. Its unique muscle system has tremendous power and speed. Its rock like skin is not harmed by fire or incendiary ammunition.
|-
| 023/x017 || The crab like claws of this creature are a powerful weapon in close combat. The high metabolism and strength of this creature give it speed and dexterity. Instead of killing its victim it impregnates it with an egg and injects a venom which turns it into a walking zombie. A new Chryssalid will burst from the victim shortly after impregnation. Chryssalids are associated with the Snakeman race.
|-
| 024/x018 || The exo-skeleton of this creature is extremely tough, but surprisingly vulnerable to explosive ammunition. The brain is well developed, and its cell growth rate very fast. The creature carries twenty eggs which are laid inside other organisms. This creature is a very effective terror weapon.
|-
| 025/x019 || The Floaters are primarily soldiers and terror agents. They are naturally predatory beasts, genetically engineered and cybernetically enhanced to make formidable warriors. The lower half of the body and most internal organs are surgically removed, and a life support system is installed. This implant contains an anti-grav unit which enables the creature to float, albeit unsteadily, through the air.
|-
| 026/x01A || The creature has been drastically altered by surgery. The device which seems to form the core of the body is a life support system, taking over the function of heart, lungs and digestive system. This would enable the creature to survive in extremely hostile environments. The brain is smaller than ours, but the sensory organs are well developed.
|-
| 027/x01B || This bipedal carnivore has powerful jaws and a voracious appetite. It has a number of brain implants which are used to control its activity. the primitive predatory instincts of this creature are of little use except to terrorise and destroy. Reapers are commonly associated with Floaters.
|-
| 028/x01C || The Reaper contains two 'brains' and two 'hearts' which allow it to function even when heavily wounded. However its furry skin is highly flammable, making the creature vulnerable to incendiary weapons.
|-
| 029/x01D || Sectopods are robot creatures with a powerful plasma beam weapon. The control if these mechanical beasts is via a telepathic link to their controllers, the Ethereals. Sectopods are the most powerful terror weapon available to the alien forces.
|-
| 030/x01E || The robot is sturdily constructed with powered armour capable of resisting most forms of attack, in particular plasma weapons. However, the sensing circuitry seems particularly vulnerable to laser weapons.
|-
| 031/x01F || This miniature flying saucer is an automated terror weapon armed with a powerful plasma beam. The anti-grav propulsion gives it a big advantage in difficult terrain. Its primary function is destruction and terror in the service of the Sectoid race.
|-
| 032/x020 || The Cyberdisc is well shielded and is particularly good at withstanding explosive ammunition. The primary anti-gravity system is too badly damaged to gain any understanding of its functioning.
|-
| 033/x021 || The power source of alien craft is an anti-matter reactor which uses Elerium (element 115) to generate powerful gravity waves as well as other forms of energy. The conversion of matter to energy is an incredible 99% efficient, therefore tiny quantities of Elerium can produce a huge amount of power. This unit can be reproduced easily using alien alloys.
|-
| 034/x022 || Alien craft use sophisticated computers to navigate on earth and through space. The system is based on optical processors arranged in network fashion. The control interface is relatively simple - the navigator controls the direction of gravity waves generated by the power source to move the craft in any direction. This system can be used easily by humans, and it can be reproduced using alien alloys and other components.
|-
| 035/x023 || Alien craft consist of three main components - a power source, a navigation system and a hull built from alien alloys. The hull is specially designed to allow gravity waves to be directed and controlled. In addition a small quantity of Elerium is required to fuel the power source. Once the principles of construction are understood, and the functions of each component are known, then it is possible to build these types of craft.
|-
| 036/x024 || These chambers contain various enzymes which are used to digest the body parts of cattle, other animals and even humans. The liquid is then consumed as ready digested food - probably direct to the bloodstream. This suggests a certain dependence on earth for food - a symbiosis between earth and alien society.
|-
| 037/x025 || These chambers contain alien foetuses. The design of these containers seems to suggest that the aliens which use this process rely completely on laboratory reproduction. The rich nutrients ensure rapid development of the foetus. This factory line system could generate thousands of alien clones in a short space of time. The process could be easily adapted for human reproduction, or alien-human hybrids.
|-
| 038/x026 || The most likely function of these spheres is recreational. The psionic circuitry stimulates various centres of the brain. The effect is similar to hallucinogenic drugs. This is the only evidence that aliens have any cultural or recreational pastimes.
|-
| 039/x027 || This surgical equipment uses laser cutters to extract certain body parts from cattle and other animals. The widespread cattle mutilations can be accounted for by this bizarre alien activity. It is likely that these parts are used for nutritional or genetic purposes.
|-
| 040/x028 || In the past many thousands of people have claimed to have been abducted by aliens, sometimes repeatedly. The truth is far more horrific. Humans are abducted, researched and monitored. The best specimens have genetic material extracted. Women have human-alien hybrid foetuses implanted, and then removed several months later. Who knows what sinister motives the aliens have?
|-
| 041/x029 || Alien craft are constructed from special alloys with unique properties. They are extremely light and durable, and can be moulded by electro-magnetic methods. This material can be reproduced and used in many kinds of manufacturing processes.
|-
| 042/x02A || You will need to research a 
|-
| 043/x02B || This element has the unusual property of generating anti-matter power when bombarded with certain particles. This creates gravity waves and other forms of energy. It is not naturally found in our solar system and cannot be reproduced.
|-
| 044/x02C || It is clear that we are fighting a losing battle on earth. The alien hordes are overwhelming in number. The best we can do is slow down their progress. The only hope for humanity is to tackle the aliens at their source. Our research seems to indicate a nearby base of operations within our solar system. Aliens indicate this place to be the centre of an ancient civilisation that pre-dates Human history. We must locate this place as soon as possible. However we need to capture and interrogate an alien leader to gain more detailed information. The larger UFOs probably contain at least one Alien leader.
|-
| 045/x02D || Our research now points to Mars as the base of alien operations. The base is well hidden, and contains all the manufacturing and cloning facilities to fuel the infiltration of earth. It also seems to contain a controlling computer of some kind that controls the whole operation. It seems that the hive-like alien society has some kind of 'queen bee'. This is their fundamental weakness - if we can eliminate the 'brain' then the body will die. We must step up our research efforts before it is too late. In order to progress we must capture the highest ranking aliens - the commanders - which only reside in alien bases.
|-
| 046/x02E || It is now clear that the alien hordes are being controlled from an underground base in Cydonia - which is an unusual area of Mars featuring five sided pyramids and a large formation resembling a human face. Cydonian civilisation once flourished on Mars many millions of years ago, but we do not know why it died out, or what the connection is with the latest alien activity there. Whatever the explanation we must send an expedition to Cydonia. This is the only way that we can defeat the aliens. We must destroy the controlling master 'brain'. We will need an Avenger craft equipped with the most awesome destructive power at our disposal. There is nothing more we can learn here - we must await the outcome of the Cydonian assault.
|-
| 047/x02F || Terror Site-
|-
| 048/x030 || CENTRE ON SITE-TIME=5 Secs
|-
| 049/x031 || CANCEL
|-
| 050/x032 || None
|-
| 051/x033 || Unknown
|-
| 052/x034 || Poor
|-
| 053/x035 || Average
|-
| 054/x036 || Good
|-
| 055/x037 || Excellent
|-
| 056/x038 || FUNDS> $
|-
| 057/x039 || BUILD NEW BASE
|-
| 058/x03A || BASE INFORMATION
|-
| 059/x03B || EQUIP CRAFT
|-
| 060/x03C || BUILD FACILITIES
|-
| 061/x03D || RESEARCH
|-
| 062/x03E || MANUFACTURE
|-
| 063/x03F || TRANSFER
|-
| 064/x040 || PURCHASE/RECRUIT
|-
| 065/x041 || SELL/SACK
|-
| 066/x042 || GEOSCAPE
|-
| 067/x043 || XCom Bases
|-
| 068/x044 || Name
|-
| 069/x045 || Area
|-
| 070/x046 || Build New Base
|-
| 071/x047 || Cancel
|-
| 072/x048 || COST>
|-
| 073/x049 || CONSTRUCTION TIME>
|-
| 074/x04A || days
|-
| 075/x04B || MAINTENANCE>
|-
| 076/x04C || OK
|-
| 077/x04D || Installation
|-
| 078/x04E || CURRENT RESEARCH
|-
| 079/x04F || Scientists Available>
|-
| 080/x050 || Scientists Allocated>
|-
| 081/x051 || Laboratory Space Available>
|-
| 082/x052 || RESEARCH PROJECT
|-
| 083/x053 || SCIENTISTS ALLOCATED
|-
| 084/x054 || PROGRESS
|-
| 085/x055 || New Project
|-
| 086/x056 || NEW RESEARCH PROJECTS
|-
| 087/x057 || SCIENTISTS AVAILABLE>
|-
| 088/x058 || LABORATORY SPACE AVAILABLE>
|-
| 089/x059 || Increase
|-
| 090/x05A || Decrease
|-
| 091/x05B || START PROJECT
|-
| 092/x05C || CURRENT PRODUCTION
|-
| 093/x05D || Engineers Available>
|-
| 094/x05E || Engineers Allocated>
|-
| 095/x05F || Workshop Space Available>
|-
| 096/x060 || Current Funds>
|-
| 097/x061 || ITEM
|-
| 098/x062 || Engineers Allocated
|-
| 099/x063 || Units Produced
|-
| 100/x064 || Total to Produce
|-
| 101/x065 || Cost per Unit
|-
| 102/x066 || Days/Hours Left
|-
| 103/x067 || New Production
|-
| 104/x068 || Production Items
|-
| 105/x069 || CATEGORY
|-
| 106/x06A || START PRODUCTION
|-
| 107/x06B || Engineer hours to produce one unit
|-
| 108/x06C || Cost per unit>$
|-
| 109/x06D || Work Space Required>
|-
| 110/x06E || SPECIAL MATERIALS REQUIRED
|-
| 111/x06F || ITEM REQUIRED
|-
| 112/x070 || UNITS REQUIRED
|-
| 113/x071 || UNITS AVAILABLE
|-
| 114/x072 || STOP PRODUCTION
|-
| 115/x073 || ENGINEERS AVAILABLE>
|-
| 116/x074 || WORKSHOP SPACE AVAILABLE>
|-
| 117/x075 || Engineers
|-
| 118/x076 || Allocated
|-
| 119/x077 || INCREASE
|-
| 120/x078 || DECREASE
|-
| 121/x079 || Units to
|-
| 122/x07A || Produce
|-
| 123/x07B || Purchase/Hire Personnel
|-
| 124/x07C || Current Funds>
|-
| 125/x07D || Cost of Purchases>
|-
| 126/x07E || COST PER UNIT
|-
| 127/x07F || QUANTITY
|-
| 128/x080 || PERSONNEL AVAILABLE:PERSONNEL TOTAL>
|-
| 129/x081 || Soldiers
|-
| 130/x082 || Engineers
|-
| 131/x083 || Scientists
|-
| 132/x084 || SPACE USED:SPACE AVAILABLE>
|-
| 133/x085 || Living Quarters
|-
| 134/x086 || Stores
|-
| 135/x087 || Laboratories
|-
| 136/x088 || Work Shops
|-
| 137/x089 || Hangars
|-
| 138/x08A || Short Range Detection
|-
| 139/x08B || Defence Strength
|-
| 140/x08C || TRANSFERS
|-
| 141/x08D || Transfers
|-
| 142/x08E || Arrival Time (hours)
|-
| 143/x08F || Cost>$
|-
| 144/x090 || Area>
|-
| 145/x091 || Base Name?
|-
| 146/x092 || SELECT POSITION FOR ACCESS LIFT
|-
| 147/x093 || Transfer
|-
| 148/x094 || AMOUNT TO TRANSFER
|-
| 149/x095 || Select Destination Base
|-
| 150/x096 || Current Funds>
|-
| 151/x097 || Cost
|-
| 152/x098 || As you enter the chamber you see the alien brain - the object of your quest. Before you can fire it communicates to you via a screen at its base. It implores you to listen to its arguments for survival before you make the decision to pull the trigger...
|-
| 153/x099 || The brain speaks: 'Many millions of years ago the planet you call Mars was alive. This life was brought to a barren planet by our civilisation as it was to yours. For millions of years we have visited your planet and genetically developed your species. You cannot kill us, you are part of us...
|-
| 154/x09A || Here is the centre of Martian civilisation - the pyramids built millions of years before yours - by a species which is your ancestor. No planet is beyond our reach. This power could be yours before long. All we ask is your co-operation...
|-
| 155/x09B || The aliens attempt to exterminate all humanity, destroying cities and poisoning the air and sea. The resistance of earth armies is futile in the face of vastly superior technology. Surviving generations suffer terrible mutations as they flee alien destruction. They are rounded up into slave camps to help transform earth into an alien colony which is part of some unknown empire.
|-
| 156/x09C || The knowledge gained through the XCom project is lost forever. You have failed to save the earth.
|-
| 157/x09D || The alien brain is interrupted by a burst of hot plasma, and the entire alien force is defeated.
|-
| 158/x09E || Once the aliens have lost Mars they have lost the earth. Before long the XCom research allows humanity to flourish once more, and claim Mars for itself. The alien menace has gone, but for how long, no one knows...
|-
| 159/x09F || You have failed to stop the alien onslaught. One by one the funding nations sign pacts with aliens promising technology, prosperity and peace. However it soon becomes clear that the aliens have other plans...
|-
| 160/x0A0 || TOTAL
|-
| 161/x0A1 || Income
|-
| 162/x0A2 || Expenditure
|-
| 163/x0A3 || Maintenance
|-
| 164/x0A4 || Balance
|-
| 165/x0A5 || UFO Activity in Areas
|-
| 166/x0A6 || UFO Activity in Countries
|-
| 167/x0A7 || XCom Activity in Areas
|-
| 168/x0A8 || XCom Activity in Countries
|-
| 169/x0A9 || Finance
|-
| 170/x0AA || st
|-
| 171/x0AB || nd
|-
| 172/x0AC || rd
|-
| 173/x0AD || th
|-
| 174/x0AE || Not enough special materials to produce 
|-
| 175/x0AF || Not enough money to produce 
|-
| 176/x0B0 || Production complete: 
|-
| 177/x0B1 || Production of 
|-
| 178/x0B2 || at 
|-
| 179/x0B3 || is complete
|-
| 180/x0B4 || OK - 5 secs
|-
| 181/x0B5 || Research Completed
|-
| 182/x0B6 || VIEW REPORTS
|-
| 183/x0B7 || We can now research
|-
| 184/x0B8 || We can now produce
|-
| 185/x0B9 || SUNDAY
|-
| 186/x0BA || MONDAY
|-
| 187/x0BB || TUESDAY
|-
| 188/x0BC || WEDNESDAY
|-
| 189/x0BD || THURSDAY
|-
| 190/x0BE || FRIDAY
|-
| 191/x0BF || SATURDAY
|-
| 192/x0C0 || Not enough
|-
| 193/x0C1 || to refuel
|-
| 194/x0C2 || to rearm
|-
| 195/x0C3 || at
|-
| 196/x0C4 || UFO is not recovered
|-
| 197/x0C5 || UFO is recovered
|-
| 198/x0C6 || Craft is lost
|-
| 199/x0C7 || Terror continues
|-
| 200/x0C8 || Aliens defeated
|-
| 201/x0C9 || Craft is lost
|-
| 202/x0CA || Base is lost
|-
| 203/x0CB || Base is saved
|-
| 204/x0CC || Base is lost
|-
| 205/x0CD || Alien Base still intact
|-
| 206/x0CE || Alien Base destroyed
|-
| 207/x0CF || Craft is lost
|-
| 208/x0D0 || ALIENS KILLED
|-
| 209/x0D1 || ALIEN CORPSES RECOVERED
|-
| 210/x0D2 || LIVE ALIENS RECOVERED
|-
| 211/x0D3 || ALIEN ARTEFACTS RECOVERED
|-
| 212/x0D4 || ALIEN BASE CONTROL DESTROYED
|-
| 213/x0D5 || CIVILIANS KILLED BY ALIENS
|-
| 214/x0D6 || CIVILIANS KILLED BY XCOM OPERATIVES
|-
| 215/x0D7 || CIVILIANS SAVED
|-
| 216/x0D8 || XCOM OPERATIVES KILLED
|-
| 217/x0D9 || XCOM OPERATIVES RETIRED THROUGH INJURY
|-
| 218/x0DA || XCOM OPERATIVES MISSING IN ACTION
|-
| 219/x0DB || TANKS DESTROYED
|-
| 220/x0DC || XCOM CRAFT LOST
|-
| 221/x0DD || UFO RECOVERY
|-
| 222/x0DE || ALIEN BASE RECOVERY
|-
| 223/x0DF || under attack!
|-
| 224/x0E0 || BASE DEFENCES INITIATED
|-
| 225/x0E1 || GRAV SHIELD REPELS UFO!
|-
| 226/x0E2 || FIRING
|-
| 227/x0E3 || HIT!
|-
| 228/x0E4 || UFO DESTROYED!
|-
| 229/x0E5 || MISSED!
|-
| 230/x0E6 || Sell Items/Sack Personnel
|-
| 231/x0E7 || VALUE OF SALES>
|-
| 232/x0E8 || FUNDS>
|-
| 233/x0E9 || Sell/Sack
|-
| 234/x0EA || Value
|-
| 235/x0EB || UFO-
|-
| 236/x0EC || CRAFT>
|-
| 237/x0ED || UFO CRASH RECOVERY
|-
| 238/x0EE || Exercise caution - There may be operatives in the UFO or around the crash site. Mission will be successful when all enemy units have been eliminated or neutralised. Recovery of UFO remains, artefacts and alien corpses can then be initiated. To abort the mission return XCom operatives to transport vehicle and click on the 'Abort Mission' icon.
|-
| 239/x0EF || UFO GROUND ASSAULT
|-
| 240/x0F0 || Explore landing site and, if possible, gain entry to the UFO. Mission will be successful when all enemy units have been eliminated or neutralised. Recovery of UFO, artefacts and alien corpses can then be initiated. To abort the mission return XCom operatives to transport vehicle and click on the 'Abort Mission' icon.
|-
| 241/x0F1 || BASE DEFENCE
|-
| 242/x0F2 || BASE>
|-
| 243/x0F3 || An Alien vessel has landed nearby. Our base is in severe danger. As per standard procedure all non combat personnel and XCom craft have been evacuated. Alien units will enter the base via hangar doors or the access lift. Defend the base and its vital installations at all costs - this is a fight to the death. If you click on the 'abort mission' icon you will concede defeat and lose the base.
|-
| 244/x0F4 || ALIEN BASE ASSAULT
|-
| 245/x0F5 || CRAFT>
|-
| 246/x0F6 || XCom operatives have gained entrance to an alien base. The control centre must be destroyed to render the base inoperative. The Mission will terminate when all enemies are eliminated, or when your squad has returned to the green exit area (click on the 'abort mission' icon to escape).
|-
| 247/x0F7 || You have arrived in Cydonia. You gain entry to a large underground complex near the Martian Sphinx. You must destroy the Alien Brain that controls all alien activity. The fate of humanity is in your hands....
|-
| 248/x0F8 || TERROR SITE-
|-
| 249/x0F9 || TERROR MISSION
|-
| 250/x0FA || Mission will be successful when all enemy units have been eliminated or neutralised. You must attempt to save the lives of any civilians in the area by neutralising the alien menace. To abort the mission return XCom operatives to transport vehicle and click on the 'Abort Mission' icon.
|-
| 251/x0FB || NO FREE HANGARS FOR CRAFT PRODUCTION!x02Each craft assigned to a base, transferred to a base, purchased or constructed uses one hangar. Build a new hangar or transfer a craft to another base.
|-
| 252/x0FC || NO FREE HANGARS FOR PURCHASE!x02Each craft assigned to a base, transferred to a base, purchased or constructed uses one hangar. Build a new hangar or transfer a craft to another base.
|-
| 253/x0FD || NO FREE HANGARS FOR TRANSFER!x02Each craft assigned to a base, transferred to a base, purchased or constructed uses one hangar. Build a new hangar or transfer a craft to another base.
|-
| 254/x0FE || CANNOT BUILD HERE!x02You must build next to an existing base facility.
|-
| 255/x0FF || NO FREE ACCOMODATION!x02The destination base does not have enough space in living quarters.
|-
| 256/x100 || NOT ENOUGH WORK SPACE AVAILABLE!x02Build a new workshop or reduce work on other projects.
|-
| 257/x101 || NOT ENOUGH MONEY!
|-
| 258/x102 || NOT ENOUGH TRANSFER SUPPORT!x02Wait for existing transfers or purchases to reach destination.
|-
| 259/x103 || NO MORE SOLDIERS ALLOWED!x02You have already recruited the maximum number of soldiers.
|-
| 260/x104 || NOT ENOUGH STORE SPACE!x02Build a new store facility or transfer existing stores to other bases.
|-
| 261/x105 || NOT ENOUGH LIVING SPACE!x02Build new living quarters or transfer personnel to other bases.
|-
| 262/x106 || NO MORE EQUIPMENT ALLOWED ON BOARD!x02You are only allowed to take a maximum of 80 items of equipment on missions.
|-
| 263/x107 || TOO MANY BUTTONS!
|-
| 264/x108 || LAUNCH INTERCEPTION
|-
| 265/x109 || CRAFT
|-
| 266/x10A || STATUS
|-
| 267/x10B || BASE
|-
| 268/x10C || READY
|-
| 269/x10D || OUT
|-
| 270/x10E || REPAIRS
|-
| 271/x10F || REFUELLING
|-
| 272/x110 || REARMING
|-
| 273/x111 || TARGET:
|-
| 274/x112 || ALIEN BASE-
|-
| 275/x113 || CRASH SITE-
|-
| 276/x114 || LANDING SITE-
|-
| 277/x115 || TARGET: WAY POINT
|-
| 278/x116 || Are you sure you want to send this craft on a mission to Cydonia?
|-
| 279/x117 || YES
|-
| 280/x118 || NO
|-
| 281/x119 || SELECT DESTINATION
|-
| 282/x11A || CYDONIA
|-
| 283/x11B || SELECT SITE FOR NEW BASE
|-
| 284/x11C || RETURN TO BASE
|-
| 285/x11D || SELECT NEW TARGET
|-
| 286/x11E || PATROL
|-
| 287/x11F || STATUS>
|-
| 288/x120 || DAMAGED - RETURNING TO BASE
|-
| 289/x121 || LOW FUEL - RETURNING TO BASE
|-
| 290/x122 || PATROLLING
|-
| 291/x123 || TAILING UFO
|-
| 292/x124 || INTERCEPTING UFO-
|-
| 293/x125 || RETURNING TO BASE
|-
| 294/x126 || DESTINATION: ALIEN BASE-
|-
| 295/x127 || DESTINATION: CRASH SITE-
|-
| 296/x128 || DESTINATION: LANDING SITE-
|-
| 297/x129 || DESTINATION: WAY POINT-
|-
| 298/x12A || BASE>
|-
| 299/x12B || SPEED>
|-
| 300/x12C || MAXIMUM SPEED>
|-
| 301/x12D || ALTITUDE>
|-
| 302/x12E || VERY LOW
|-
| 303/x12F || LOW
|-
| 304/x130 || HIGH
|-
| 305/x131 || VERY HIGH
|-
| 306/x132 || FUEL>
|-
| 307/x133 || WEAPON-1>
|-
| 308/x134 || NONE
|-
| 309/x135 || ROUNDS>
|-
| 310/x136 || WEAPON-2>
|-
| 311/x137 || HOSTILE
|-
| 312/x138 || NEUTRAL
|-
| 313/x139 || FRIENDLY
|-
| 314/x13A || COMMITTED
|-
| 315/x13B || GAME OPTIONS
|-
| 316/x13C || LOAD GAME
|-
| 317/x13D || SAVE GAME
|-
| 318/x13E || INTERCEPTION CRAFT
|-
| 319/x13F || Base>
|-
| 320/x140 || NAME
|-
| 321/x141 || STATUS
|-
| 322/x142 || AMMO>
|-
| 323/x143 || CREW
|-
| 324/x144 || EQUIPMENT
|-
| 325/x145 || ARMOUR
|-
| 326/x146 || MAX>
|-
| 327/x147 || Rookie
|-
| 328/x148 || Squaddie
|-
| 329/x149 || Sergeant
|-
| 330/x14A || Captain
|-
| 331/x14B || Colonel
|-
| 332/x14C || Commander
|-
| 333/x14D || Select Squad for
|-
| 334/x14E || SPACE AVAILABLE>
|-
| 335/x14F || SPACE USED>
|-
| 336/x150 || RANK
|-
| 337/x151 || CRAFT
|-
| 338/x152 || WOUNDED
|-
| 339/x153 || Equipment for
|-
| 340/x154 || Arm
|-
| 341/x155 || Defence Value
|-
| 342/x156 || Hit Ratio
|-
| 343/x157 || ready to land near
|-
| 344/x158 || Begin Mission?
|-
| 345/x159 || Select Armament
|-
| 346/x15A || AMMUNITION
|-
| 347/x15B || ARMAMENT
|-
| 348/x15C || AVAILABLE
|-
| 349/x15D || N.A.
|-
| 350/x15E || SELECT ARMOUR FOR
|-
| 351/x15F || TYPE
|-
| 352/x160 || PERSONAL ARMOUR
|-
| 353/x161 || POWER SUIT
|-
| 354/x162 || FLYING SUIT
|-
| 355/x163 || Select Armour
|-
| 356/x164 || ARMOUR
|-
| 357/x165 || NORTH
|-
| 358/x166 || NORTH EAST
|-
| 359/x167 || EAST
|-
| 360/x168 || SOUTH EAST
|-
| 361/x169 || SOUTH
|-
| 362/x16A || SOUTH WEST
|-
| 363/x16B || WEST
|-
| 364/x16C || NORTH WEST
|-
| 365/x16D || SELECT ACTION
|-
| 366/x16E || CONTINUE INTERCEPTION PURSUIT
|-
| 367/x16F || PURSUE WITHOUT INTERCEPTION
|-
| 368/x170 || VERY LARGE
|-
| 369/x171 || LARGE
|-
| 370/x172 || MEDIUM
|-
| 371/x173 || SMALL
|-
| 372/x174 || VERY SMALL
|-
| 373/x175 || GROUND
|-
| 374/x176 || VERY LOW
|-
| 375/x177 || LOW
|-
| 376/x178 || HIGH
|-
| 377/x179 || VERY HIGH
|-
| 378/x17A || Detected
|-
| 379/x17B || SIZE
|-
| 380/x17C || ALTITUDE
|-
| 381/x17D || HEADING
|-
| 382/x17E || SPEED
|-
| 383/x17F || CENTRE ON UFO-TIME=5 Secs
|-
| 384/x180 || TRACKING LOST
|-
| 385/x181 || REDIRECT CRAFT
|-
| 386/x182 || GO TO LAST KNOWN UFO POSITION
|-
| 387/x183 || UFO-
|-
| 388/x184 || CRAFT-
|-
| 389/x185 || BASE-
|-
| 390/x186 || ALIEN BASE-
|-
| 391/x187 || CRASH SITE-
|-
| 392/x188 || LANDING SITE-
|-
| 393/x189 || WAY POINT-
|-
| 394/x18A || TERROR SITE-
|-
| 395/x18B || has reached
|-
| 396/x18C || Destination
|-
| 397/x18D || Now patrolling
|-
| 398/x18E || Alien Origins
|-
| 399/x18F || The Martian Solution
|-
| 400/x190 || Cydonia or Bust
|-
| 401/x191 || UFOpaedia
|-
| 402/x192 || XCOM CRAFT & ARMAMENT
|-
| 403/x193 || HEAVY WEAPONS PLATFORMS
|-
| 404/x194 || WEAPONS AND EQUIPMENT
|-
| 405/x195 || ALIEN ARTEFACTS
|-
| 406/x196 || BASE FACILITIES
|-
| 407/x197 || ALIEN LIFE FORMS
|-
| 408/x198 || ALIEN RESEARCH
|-
| 409/x199 || UFO COMPONENTS
|-
| 410/x19A || UFOs
|-
| 411/x19B || SELECT ITEM
|-
| 412/x19C || autopsy
|-
| 413/x19D || MAXIMUM SPEED>
|-
| 414/x19E || ACCELERATION>
|-
| 415/x19F || FUEL CAPACITY>
|-
| 416/x1A0 || WEAPON PODS>
|-
| 417/x1A1 || DAMAGE CAPACITY>
|-
| 418/x1A2 || CARGO SPACE>
|-
| 419/x1A3 || HWP CAPACITY>
|-
| 420/x1A4 || Damage...................
|-
| 421/x1A5 || Range......................
|-
| 422/x1A6 || km
|-
| 423/x1A7 || Accuracy...............
|-
| 424/x1A8 || Re-load time........
|-
| 425/x1A9 || s
|-
| 426/x1AA || ARMOUR PIERCING
|-
| 427/x1AB || INCENDIARY
|-
| 428/x1AC || HIGH EXPLOSIVE
|-
| 429/x1AD || LASER BEAM
|-
| 430/x1AE || PLASMA BEAM
|-
| 431/x1AF || STUN
|-
| 432/x1B0 || 6-?
|-
| 433/x1B1 || 7-?
|-
| 434/x1B2 || 8-?
|-
| 435/x1B3 || 9-?
|-
| 436/x1B4 || SHOT TYPE>
|-
| 437/x1B5 || ACCURACY>
|-
| 438/x1B6 || TU COST>
|-
| 439/x1B7 || DAMAGE
|-
| 440/x1B8 || AMMO
|-
| 441/x1B9 || Auto
|-
| 442/x1BA || Snap
|-
| 443/x1BB || Aimed
|-
| 444/x1BC || Construction Time
|-
| 445/x1BD || days
|-
| 446/x1BE || Construction Cost
|-
| 447/x1BF || Maintenance Cost
|-
| 448/x1C0 || autopsy
|-
| 449/x1C1 || -
|-
| 450/x1C2 || Low
|-
| 451/x1C3 || Medium
|-
| 452/x1C4 || High
|-
| 453/x1C5 || High
|-
| 454/x1C6 || Craft Weapon
|-
| 455/x1C7 || Craft Ammunition
|-
| 456/x1C8 || Heavy Weapons Platform
|-
| 457/x1C9 || Weapon
|-
| 458/x1CA || Ammunition
|-
| 459/x1CB || Equipment
|-
| 460/x1CC || Alien Corpse
|-
| 461/x1CD || UFO component
|-
| 462/x1CE || Personal Armour
|-
| 463/x1CF || Raw Materials
|-
| 464/x1D0 || HWP Cannon Shells
|-
| 465/x1D1 || Alien
|-
| 466/x1D2 || Sectoid
|-
| 467/x1D3 || Snakeman
|-
| 468/x1D4 || Ethereal
|-
| 469/x1D5 || Muton
|-
| 470/x1D6 || Floater
|-
| 471/x1D7 || Celatid
|-
| 472/x1D8 || Silacoid
|-
| 473/x1D9 || Chryssalid
|-
| 474/x1DA || Reaper
|-
| 475/x1DB || Sectopod
|-
| 476/x1DC || Cyberdisc
|-
| 477/x1DD || Commander
|-
| 478/x1DE || Leader
|-
| 479/x1DF || Engineer
|-
| 480/x1E0 || Medic
|-
| 481/x1E1 || Navigator
|-
| 482/x1E2 || Soldier
|-
| 483/x1E3 || Terrorist
|-
| 484/x1E4 || UFO Power Source
|-
| 485/x1E5 || UFO Navigation
|-
| 486/x1E6 || UFO Construction
|-
| 487/x1E7 || Alien Food
|-
| 488/x1E8 || Alien Reproduction
|-
| 489/x1E9 || Alien Entertainment
|-
| 490/x1EA || Alien Surgery
|-
| 491/x1EB || Examination Room
|-
| 492/x1EC || Alien Alloys
|-
| 493/x1ED || Alien Habitat
|-
| 494/x1EE || Personal Armour
|-
| 495/x1EF || Power Suit
|-
| 496/x1F0 || Flying Suit
|-
| 497/x1F1 || HWP Rockets
|-
| 498/x1F2 || HWP Fusion Bomb
|-
| 499/x1F3 || Laser Weapons
|-
| 500/x1F4 || New Fighter Craft
|-
| 501/x1F5 || New Fighter-Transporter
|-
| 502/x1F6 || Ultimate Craft
|-
| 503/x1F7 || Laser Pistol
|-
| 504/x1F8 || Laser Rifle
|-
| 505/x1F9 || Heavy Laser
|-
| 506/x1FA || Laser Cannon
|-
| 507/x1FB || Plasma Cannon
|-
| 508/x1FC || Fusion Missile
|-
| 509/x1FD || Laser Defence
|-
| 510/x1FE || Plasma Defence
|-
| 511/x1FF || Fusion Defence
|-
| 512/x200 || Grav Shield
|-
| 513/x201 || Mind Shield
|-
| 514/x202 || Psi-Lab
|-
| 515/x203 || Hyper Wave Decoder
|-
| 516/x204 || NOT USED
|-
| 517/x205 || NOT USED
|-
| 518/x206 || NOT USED
|-
| 519/x207 || UFO construction
|-
| 520/x208 || Alien Origins
|-
| 521/x209 || The Martian Solution
|-
| 522/x20A || Cydonia or Bust
|-
| 523/x20B || Motion Scanner
|-
| 524/x20C || Medi-Kit
|-
| 525/x20D || Tank/Cannon
|-
| 526/x20E || Tank/Rocket Launcher
|-
| 527/x20F || Tank/Laser Cannon
|-
| 528/x210 || Hovertank/Plasma
|-
| 529/x211 || Hovertank/Launcher
|-
| 530/x212 || Stingray Launcher
|-
| 531/x213 || Avalanche Launcher
|-
| 532/x214 || Cannon
|-
| 533/x215 || Fusion Ball Launcher
|-
| 534/x216 || Laser Cannon
|-
| 535/x217 || Plasma Beam
|-
| 536/x218 || Stingray Missile
|-
| 537/x219 || Avalanche Missile
|-
| 538/x21A || Cannon Rounds(x50)
|-
| 539/x21B || Fusion Ball
|-
| 540/x21C || Soldier
|-
| 541/x21D || Scientist
|-
| 542/x21E || Engineer
|-
| 543/x21F || North America
|-
| 544/x220 || Arctic
|-
| 545/x221 || Antarctica
|-
| 546/x222 || South America
|-
| 547/x223 || Europe
|-
| 548/x224 || North Africa
|-
| 549/x225 || Southern Africa
|-
| 550/x226 || Central Asia
|-
| 551/x227 || South East Asia
|-
| 552/x228 || Siberia
|-
| 553/x229 || Australasia
|-
| 554/x22A || Pacific
|-
| 555/x22B || North Atlantic
|-
| 556/x22C || South Atlantic
|-
| 557/x22D || Indian Ocean
|-
| 558/x22E || Alien Research
|-
| 559/x22F || Alien Harvest
|-
| 560/x230 || Alien Abduction
|-
| 561/x231 || Alien Infiltration
|-
| 562/x232 || Alien Base
|-
| 563/x233 || Alien Terror
|-
| 564/x234 || Alien Retaliation
|-
| 565/x235 || Alien Supply
|-
| 566/x236 || Power Sources
|-
| 567/x237 || Maximum Speed
|-
| 568/x238 || HYPER-WAVE DECODER
|-
| 569/x239 || SKYRANGER
|-
| 570/x23A || LIGHTNING
|-
| 571/x23B || AVENGER
|-
| 572/x23C || INTERCEPTOR
|-
| 573/x23D || FIRESTORM
|-
| 574/x23E || UFO
|-
| 575/x23F || STINGRAY
|-
| 576/x240 || AVALANCHE
|-
| 577/x241 || CANNON
|-
| 578/x242 || FUSION BALL
|-
| 579/x243 || LASER CANNON
|-
| 580/x244 || PLASMA BEAM
|-
| 581/x245 || Damage Capacity
|-
| 582/x246 || Weapon Power
|-
| 583/x247 || Weapon Range
|-
| 584/x248 || Access Lift
|-
| 585/x249 || Living Quarters
|-
| 586/x24A || Laboratory
|-
| 587/x24B || Workshop
|-
| 588/x24C || Small Radar System
|-
| 589/x24D || Large Radar System
|-
| 590/x24E || Missile Defences
|-
| 591/x24F || General Stores
|-
| 592/x250 || Alien Containment
|-
| 593/x251 || Laser Defences
|-
| 594/x252 || Plasma Defences
|-
| 595/x253 || Fusion Ball Defences
|-
| 596/x254 || Grav Shield
|-
| 597/x255 || Mind Shield
|-
| 598/x256 || Psionic Laboratory
|-
| 599/x257 || Hyper-wave Decoder
|-
| 600/x258 || Hangar
|-
| 601/x259 || USA
|-
| 602/x25A || RUSSIA
|-
| 603/x25B || UK
|-
| 604/x25C || FRANCE
|-
| 605/x25D || GERMANY
|-
| 606/x25E || ITALY
|-
| 607/x25F || SPAIN
|-
| 608/x260 || CHINA
|-
| 609/x261 || JAPAN
|-
| 610/x262 || INDIA
|-
| 611/x263 || BRAZIL
|-
| 612/x264 || AUSTRALIA
|-
| 613/x265 || NIGERIA
|-
| 614/x266 || SOUTH AFRICA
|-
| 615/x267 || EGYPT
|-
| 616/x268 || CANADA
|-
| 617/x269 || Floater Soldier
|-
| 618/x26A || Floater Navigator
|-
| 619/x26B || Floater Medic
|-
| 620/x26C || Floater Engineer
|-
| 621/x26D || Floater Leader
|-
| 622/x26E || Floater Commander
|-
| 623/x26F || Reaper
|-
| 624/x270 || Tank
|-
| 625/x271 || Civilian
|-
| 626/x272 || Jan
|-
| 627/x273 || Feb
|-
| 628/x274 || Mar
|-
| 629/x275 || Apr
|-
| 630/x276 || May
|-
| 631/x277 || Jun
|-
| 632/x278 || Jul
|-
| 633/x279 || Aug
|-
| 634/x27A || Sep
|-
| 635/x27B || Oct
|-
| 636/x27C || Nov
|-
| 637/x27D || Dec
|-
| 638/x27E || International Relations
|-
| 639/x27F || Country
|-
| 640/x280 || Funding
|-
| 641/x281 || Change
|-
| 642/x282 || WEAPON SYSTEMS
|-
| 643/x283 || CREW
|-
| 644/x284 || HWPs
|-
| 645/x285 || DAMAGE>
|-
| 646/x286 || The access lift allows equipment and personnel to be transferred into or out of an underground base. It is always the first facility to be constructed on a new site. The lift area is vulnerable to intrusion from any potential hostile force.
|-
| 647/x287 || Each accommodation block provides for up to 50 personnel. The facility provides basic recreation, food and sleeping areas.
|-
| 648/x288 || Up to 50 scientists can work in a laboratory facility. Laboratories are equipped with the latest technology for research into materials, biochemistry and cosmology. There is privileged access to the best research labs throughout the world, including military establishments.
|-
| 649/x289 || A workshop contains all the equipment necessary to manufacture equipment based on designs from the science labs. Up to 50 engineers can occupy a workshop, although items under construction will also consume some space.
|-
| 650/x28A || A small detection system has an effective radar range of 300 nautical miles and is linked to satellite systems for ground search. Each system has a 5% chance of detecting an average sized object every 10 minutes.
|-
| 651/x28B || A large detection system has an effective range of 450 nautical miles and is linked to satellite systems for ground search. Each system has a 5% chance of detecting an average sized object every 10 minutes.
|-
| 652/x28C || Missile defences provide some protection against incursion by hostile craft which are attempting to land near the base.
|-
| 653/x28D || All equipment, weapons systems, munitions, recovered material and Heavy Weapons Platforms are placed in stores, with the exception of equipment assigned to craft in hangars.
|-
| 654/x28E || Living aliens are likely to require a special habitat to maintain their life systems. The containment facility can keep up to 10 alien life forms in self contained units.
|-
| 655/x28F || Laser defences provide protection against incursion by hostile craft.
|-
| 656/x290 || Plasma beam defences provide powerful and efficient protection against incursion by hostile craft.
|-
| 657/x291 || Fusion missiles provide the most effective defence against alien attacks. These missiles create an anti-matter implosion which destroys everything within a specific radius.
|-
| 658/x292 || The Gravity shield repels alien craft attempting to land near the base long enough for all defence systems to fire again. In practice this will double the effectiveness of any defence systems at your base.
|-
| 659/x293 || Since alien craft rely on brain waves to detect human presence then the most effective counter measure is to shield brain waves from the base. This facility will drastically reduce the chances of detection by alien craft.
|-
| 660/x294 || The psionics lab can assess the psionic potential of all soldiers at the base and give them the necessary training to utilise their psionic skills. Each lab can train up to ten soldiers. Training is allocated at the end of each month. Psionic skills used in conjunction with a Psi-amp can be used for psionic attacks during combat.
|-
| 661/x295 || Alien communications rely on a supra-dimensional wave which travels almost instantaneously. The decoder facility intercepts UFO transmissions and decodes the information. This will show the type of UFO, the alien race and the type of activity.
|-
| 662/x296 || Each hangar can accommodate one craft. There are facilities for maintenance, refuelling and repair of XCom craft. Each craft stationed at a base must have a free hangar assigned to it which cannot be used by other craft, even if the assigned craft is out on a mission.
|-
| 663/x297 || The standard issue XCom pistol is a high powered semi-automatic with a 12 round capacity.
|-
| 664/x298 || This highly accurate sniper rifle has laser guided sights and takes 6.7mm ammunition in 20 round clips.
|-
| 665/x299 || The heavy cannon is a devastating, but cumbersome, weapon. Its versatility comes from the fact that it can take three types of ammunition - armour piercing, incendiary and high explosive.
|-
| 666/x29A || The auto-cannon combines the versatility and power of a heavy cannon with a faster fire rate.
|-
| 667/x29B || The rocket launcher is a laser guided system which can fire three different sizes of missile.
|-
| 668/x29C || The laser pistol is an effective implementation of new technology. It has the convenience of a pistol with faster and more accurate firing.
|-
| 669/x29D || The laser rifle is a more powerful and accurate version of the earlier pistol design.
|-
| 670/x29E || The heavy laser is cumbersome, but extremely effective.
|-
| 671/x29F || This standard issue grenade has an accurate and sophisticated timer for precision control.
|-
| 672/x2A0 || Smoke grenades are useful for providing cover in exposed combat situations. Use with care because they can benefit the enemy as well
|-
| 673/x2A1 || A proximity grenade can be thrown like an ordinary grenade but is triggered by nearby movement after it lands. Great skill and care is required to use these devices properly.
|-
| 674/x2A2 || This explosive should only be used for demolition purposes. Keep personnel clear of demolition sites.
|-
| 675/x2A3 || This sophisticated device uses a variety of detectors and advanced computer algorithms to identify moving enemy units. However, it requires some practice to use effectively. Click on the motion scanner icon on the tactical display. Select 'Use Scanner' from the menu. The Scanner display shows an arrow in the centre which is the direction the soldier is facing (North is at the top). The flashing blobs show units which have moved recently. Large units, or fast moving units, will produce larger blobs. Static units will not be detected.
|-
| 676/x2A4 || The medi-kit combines a healing facility with pain killers and stimulants. In order to use the medi-kit you must face towards the soldier requiring treatment. If the soldier is stunned you must stand over the body. Click on the medi-kit icon and select 'use medi-kit' from the menu. HEALING> Red body parts show fatal wounds. Click on a body part that is wounded. Click on the 'Heal' button. One fatal wound will be cured and some health restored. STIMULANT> This will restore energy and revive unconscious (stunned) soldiers. In order to revive an unconscious soldier you must stand directly over the body. PAIN KILLER> This will restore the morale of wounded soldiers up to an amount equivalent to the soldier's lost health.
|-
| 677/x2A5 || The Psi-amp can only be used by soldiers with psionic skill. During combat, click on the Psi-amp, select the type of attack, and select a target unit with the cursor. There are two types of psionic attack: PANIC UNIT> If the attack is successful it will reduce the target's morale and may cause it to panic. MIND CONTROL> If this is successful then you will gain immediate control of the enemy unit as if it was one of your own (except that you cannot access the object screen). It is more difficult to be successful with this type of attack.
|-
| 678/x2A6 || This device can only be used in close combat, but will stun a living organism without killing it by using electric shocks.
|-
| 679/x2A7 || The subject has died due to the trauma of interrogation.
|-
| 680/x2A8 || The mind probe is an alien communication device which is used to take information directly from brain waves. XCom units can use this device in combat to display an alien's characteristics. Click on the mind probe and the 'use' option. Then click on an alien with the cursor.
|-
| 681/x2A9 || Plasma pistols are a lethal alien weapon based on accelerating particles from within a minute anti-gravity field
|-
| 682/x2AA || This is a devastatingly powerful weapon based on accelerating particles from within a minute anti-gravity field
|-
| 683/x2AB || Size
|-
| 684/x2AC || The corpse may be researched for a full autopsy report.
|-
| 685/x2AD || Not enough ammunition to arm
|-
| 686/x2AE || This is an alien guided missile launcher which fires powerful 'blaster bombs'. When you click to fire the weapon it will generate 'way points' for the blaster bomb to follow. When you have positioned enough way points click on the special launch icon.
|-
| 687/x2AF || A small launcher which fires stun bombs. Very useful for capturing live aliens.
|-
| 688/x2B0 || This device works in the same way as a terrestrial grenade - except that it is more powerful.
|-
| 689/x2B1 || Small Scout
|-
| 690/x2B2 || Medium Scout
|-
| 691/x2B3 || Large Scout
|-
| 692/x2B4 || Harvester
|-
| 693/x2B5 || Abducter
|-
| 694/x2B6 || Terror ship
|-
| 695/x2B7 || Battleship
|-
| 696/x2B8 || Supply ship
|-
| 697/x2B9 || RATING>
|-
| 698/x2BA || TERRIBLE!
|-
| 699/x2BB || POOR!
|-
| 700/x2BC || OK
|-
| 701/x2BD || GOOD!
|-
| 702/x2BE || EXCELLENT!
|-
| 703/x2BF || SCORE
|-
| 704/x2C0 || XCOM PROJECT MONTHLY REPORT
|-
| 705/x2C1 || Month>
|-
| 706/x2C2 || The council of funding nations is generally satisfied with your progress so far.
|-
| 707/x2C3 || The council of funding nations is very pleased with your excellent progress. Keep up the good work.
|-
| 708/x2C4 || The council of funding nations is dissatisfied with your performance. You must improve your effectiveness in dealing with the alien menace or risk termination of the project.
|-
| 709/x2C5 || You have not succeeded in dealing with the alien invasion and the council of funding nations has regrettably decided to terminate the project. Each nation shall deal with the problem as they see fit. We can only hope that we can come to some accommodation with these apparently hostile forces, and that the general population will come to terms with the alien visitors.
|-
| 710/x2C6 || is particularly pleased with your ability to deal with the localised threat and has agreed to increase its funding.
|-
| 711/x2C7 || are particularly happy with your progress in dealing with local alien incursion and have agreed to increase their funding.
|-
| 712/x2C8 || and
|-
| 713/x2C9 || is unhappy with your ability to deal with alien activity in its territory and has decided to reduce its financial commitment.
|-
| 714/x2CA || are unhappy with your ability to deal with alien activity in their territory and have decided to reduce their funding.
|-
| 715/x2CB || knots
|-
| 716/x2CC || has signed a secret pact with unknown alien forces and has withdrawn from the project.
|-
| 717/x2CD || have signed a secret pact with unknown alien forces and have withdrawn from the project.
|-
| 718/x2CE || Monthly Rating>
|-
| 719/x2CF || Funding change>
|-
| 720/x2D0 || The funding council is not happy with your financial position. You must reduce your debts below $2million or the project will be terminated.
|-
| 721/x2D1 || HYPER-WAVE TRANSMISSIONS ARE DECODED
|-
| 722/x2D2 || CRAFT TYPE
|-
| 723/x2D3 || RACE
|-
| 724/x2D4 || MISSION
|-
| 725/x2D5 || ZONE
|-
| 726/x2D6 || Allocate Research
|-
| 727/x2D7 || Allocate Manufacture
|-
| 728/x2D8 || New York
|-
| 729/x2D9 || Washington
|-
| 730/x2DA || Los Angeles
|-
| 731/x2DB || Montreal
|-
| 732/x2DC || Havana
|-
| 733/x2DD || Mexico City
|-
| 734/x2DE || Chicago
|-
| 735/x2DF || Vancouver
|-
| 736/x2E0 || Dallas
|-
| 737/x2E1 || Brasilia
|-
| 738/x2E2 || Bogota
|-
| 739/x2E3 || Buenos Aires
|-
| 740/x2E4 || Santiago
|-
| 741/x2E5 || Rio De Janeiro
|-
| 742/x2E6 || Lima
|-
| 743/x2E7 || Caracas
|-
| 744/x2E8 || London
|-
| 745/x2E9 || Paris
|-
| 746/x2EA || Berlin
|-
| 747/x2EB || Moscow
|-
| 748/x2EC || Rome
|-
| 749/x2ED || Madrid
|-
| 750/x2EE || Budapest
|-
| 751/x2EF || Lagos
|-
| 752/x2F0 || Cairo
|-
| 753/x2F1 || Casablanca
|-
| 754/x2F2 || Pretoria
|-
| 755/x2F3 || Nairobi
|-
| 756/x2F4 || Cape Town
|-
| 757/x2F5 || Kinshasa
|-
| 758/x2F6 || Ankara
|-
| 759/x2F7 || Delhi
|-
| 760/x2F8 || Karachi
|-
| 761/x2F9 || Baghdad
|-
| 762/x2FA || Tehran
|-
| 763/x2FB || Bombay
|-
| 764/x2FC || Calcutta
|-
| 765/x2FD || Tokyo
|-
| 766/x2FE || Beijing
|-
| 767/x2FF || Bangkok
|-
| 768/x300 || Manila
|-
| 769/x301 || Seoul
|-
| 770/x302 || Singapore
|-
| 771/x303 || Jakarta
|-
| 772/x304 || Shanghai
|-
| 773/x305 || Hong Kong
|-
| 774/x306 || Novosibirsk
|-
| 775/x307 || Canberra
|-
| 776/x308 || Wellington
|-
| 777/x309 || Melbourne
|-
| 778/x30A || Perth
|-
| 779/x30B || UFOx02Enemy Unknown
|-
| 780/x30C || New Game
|-
| 781/x30D || Load Saved Game
|-
| 782/x30E || Select Difficulty Level
|-
| 783/x30F || 1> Beginner
|-
| 784/x310 || 2> Experienced
|-
| 785/x311 || 3> Veteran
|-
| 786/x312 || 4> Genius
|-
| 787/x313 || 5> Superhuman
|-
| 788/x314 || Time
|-
| 789/x315 || Date
|-
| 790/x316 || Select game to load
|-
| 791/x317 || Select save position
|-
| 792/x318 || PSIONIC TRAINING
|-
| 793/x319 || Remaining Psi-lab capacity>
|-
| 794/x31A || Psionic Strength
|-
| 795/x31B || Psionic Skill /Improvement
|-
| 796/x31C || Psi-Amp
|-
| 797/x31D || In Training?
|-
| 798/x31E || TARGETTED BY:
|-
| 799/x31F || WEAPONS/ CREW/HWPs
|-
| 800/x320 || ABANDON GAME
|-
| 801/x321 || Quit
|-
| 802/x322 || is low on fuel, returning to base
|-
| 803/x323 || Soldier List
|-
| 804/x324 || RANK>
|-
| 805/x325 || MISSIONS>
|-
| 806/x326 || KILLS>
|-
| 807/x327 || WOUND RECOVERY>
|-
| 808/x328 || TIME UNITS
|-
| 809/x329 || STAMINA
|-
| 810/x32A || HEALTH
|-
| 811/x32B || BRAVERY
|-
| 812/x32C || REACTIONS
|-
| 813/x32D || FIRING ACCURACY
|-
| 814/x32E || THROWING ACCURACY
|-
| 815/x32F || STRENGTH
|-
| 816/x330 || PSIONIC STRENGTH
|-
| 817/x331 || PSIONIC SKILL
|-
| 818/x332 || NEW RANK
|-
| 819/x333 || Promotions
|-
| 820/x334 || SOLDIERS
|-
| 821/x335 || Automated heavy weapons platforms are designed to complement an XCom squad. The combination of high fire power and strong armour makes these units valuable for open terrain fire fights. Make sure that there are sufficient cannon shells in your stores to re-arm tanks. They are armed automatically when you assign them to a squad.
|-
| 822/x336 || This automated heavy weapons platform is armed with powerful rockets. This will be devastating for any alien foe. Make sure your stores are kept supplied with HWP rockets.
|-
| 823/x337 || Laser weapons are a useful addition for HWPs. It combines heavy firepower with no ammunition restrictions.
|-
| 824/x338 || Alien technology has given the HWP a new lease of life. The added manoeuvrability of air travel and the power of plasma beams is a lethal combination.
|-
| 825/x339 || This hovertank has a fusion ball launcher that is capable of immense devastation. Use it with great care. You will have to manufacture the fusion balls to keep these HWPs fully armed. A fusion ball is an intelligent guided weapon. In order to fire it you select a number of 'way points' with the cursor and then click on the launch icon to fire the fusion ball.
|-
| 826/x33A || This compact device is used as ammunition for a Heavy Plasma Gun. It contains a small quantity of Elerium.
|-
| 827/x33B || This small object is used as a power source for a plasma rifle - a medium powered alien weapon. Contains a small quantity of Elerium.
|-
| 828/x33C || Power source for the small alien plasma pistol. Contains Elerium - the source of all alien power.
|-
| 829/x33D || The Stun bomb is used for capturing live human specimens, but it can also be used against most alien races. It is fired from a small launcher.
|-
| 830/x33E ||
|-
| 831/x33F ||
|-
| 832/x340 || The alien research mission is used for collecting basic data on earth and its inhabitants. Small vehicles are predominantly used, with occasional landings in deserted areas. This type of alien activity poses the least threat to XCom, with little concern from governments or the public.
|-
| 833/x341 || The aliens have many uses for earth's fauna. Animals are abducted secretly, and returned with various organs removed. Cattle mutilations are predominantly reported along with UFO sightings. This type of alien activity causes great concern by governments and considerable anxiety amongst the population. This type of activity occurs mainly in farming land. The theory behind the 'alien harvest' suggests that alien races originally 'seeded' the planet with its flora and fauna, and now they have returned to reap the harvest they have sown.
|-
| 834/x342 || This is the most insidious form of alien activity. The abduction by aliens is widely reported, despite the aliens' attempts to erase the experience from their victims' memories. Abductees report being subject to humiliating physical examinations, including impregnation of alien foetuses and bizarre genetic experiments. The purpose behind this activity appears to be linked to genetic mutation and manipulation of the aliens own genetic material. This activity causes great alarm, and occurs in populated areas or cities
|-
| 835/x343 || Earth governments can be infiltrated by alien agents which are human in appearance. This can result in official contact between aliens and governments at the highest level. The climax of this activity is characterised by intense UFO activity in the vicinity of major cities. The aliens will attempt to sign a pact with an earth government by offering knowledge of their superior technology. In return the government will allow the aliens to conduct their activity unhindered. This alien mission represents the worst threat to XCom. If a government agrees to a pact then its funding will cease.
|-
| 836/x344 || Aliens will construct secret underground bases in remote locations. After some initial reconnaissance flights some intense UFO activity will occur as the base is being built. These bases are known to contain experimental labs for human abductees, and supplies for further activity in the region. The presence of alien bases will generate a large amount of reported alien activity without the presence of UFOs. In order to locate a base an XCom craft must patrol an area for a few hours to stand some chance of detection.
|-
| 837/x345 || When the aliens terrorise a city they will deploy some special forces with awesome powers. Civilians will be directly threatened, and governments will be forced to evacuate whole areas. The main purpose behind this activity is to generate sufficient public hysteria so that governments will threaten the XCom project.
|-
| 838/x346 || If XCom interceptors are being particularly successful in shooting down UFOs then the aliens may take some retaliatory action. This could result in a direct attack against an XCom base. However, the aliens have to find an XCom base in order to attack it, and provided UFOs are kept away then there should be little danger of an assault.
|-
| 839/x347 || Once an alien base is constructed then it is resupplied on a regular basis by a special supply vessel. If one of these vessels is detected while landing then it is certain that an alien base is nearby.
|-
| 840/x348 || This tiny craft is primarily used for reconnaissance or research. It normally precedes larger vessels at the start of an alien mission.
|-
| 841/x349 || A medium sized scout vessel that poses little threat to earth forces. Normally appears before larger vessels during missions.
|-
| 842/x34A || The largest alien scout craft is a general purpose vessel that is used in all types of alien mission.
|-
| 843/x34B || The harvester has a trap door in its base and is equipped with lifting gear to haul up cattle or other beasts. Laser cutters are used to extract the desired material and the carcass is dumped on the. ground. There are also storage containers for body parts.
|-
| 844/x34C || This vessel is equipped with an examination room for performing horrific experiments on human subjects. The victim is normally paralysed by telepathic powers, but remains conscious while on the operating table.
|-
| 845/x34D || The terror ship has a containment facility for large alien terror weapons or creatures. It is used to transport these alien terrorists into populated areas.
|-
| 846/x34E || The battleship is the largest and most powerful alien craft. It is normally the primary alien mission craft, equipped with powerful weapons and numerous crew members.
|-
| 847/x34F || The supply vessel is used during the construction of alien bases or for supplying existing bases. It carries alien food containers and reproduction chambers.
|-
| 848/x350 || Dismantle
|-
| 849/x351 || FACILITY IN USE
|-
| 850/x352 || CANNOT DISMANTLE FACILITY!x02All base facilities must be linked to the access lift.
|-
| 851/x353 || Transfer Items to
|-
| 852/x354 || NO ALIEN CONTAINMENT FOR TRANSFER!x02Live aliens need an alien containment facility in order to survive
|-
| 853/x355 || AMOUNT AT DESTINATION
|-
| 854/x356 || Alien dies as there is no alien containment facility
|-
| 855/x357 || NO FREE ACCOMODATION!x02The destination base does not have enough space in the living quarters for the crew assigned to the craft.
|-
| 856/x358 || Items Arriving
|-
| 857/x359 || Pistol
|-
| 858/x35A || Pistol Clip
|-
| 859/x35B || Rifle
|-
| 860/x35C || Rifle Clip
|-
| 861/x35D || Heavy Cannon
|-
| 862/x35E || HC-AP Ammo
|-
| 863/x35F || HC-HE Ammo
|-
| 864/x360 || HC-I Ammo
|-
| 865/x361 || Auto-Cannon
|-
| 866/x362 || AC-AP Ammo
|-
| 867/x363 || AC-HE Ammo
|-
| 868/x364 || AC-I Ammo
|-
| 869/x365 || Rocket Launcher
|-
| 870/x366 || Small Rocket
|-
| 871/x367 || Large Rocket
|-
| 872/x368 || Incendiary Rocket
|-
| 873/x369 || Laser Pistol
|-
| 874/x36A || Laser Rifle
|-
| 875/x36B || Heavy Laser
|-
| 876/x36C || Grenade
|-
| 877/x36D || Smoke Grenade
|-
| 878/x36E || Proximity Grenade
|-
| 879/x36F || High Explosive
|-
| 880/x370 || Motion Scanner
|-
| 881/x371 || Medi-Kit
|-
| 882/x372 || Psi-Amp
|-
| 883/x373 || Stun Rod
|-
| 884/x374 || Heavy Plasma
|-
| 885/x375 || Heavy Plasma Clip
|-
| 886/x376 || Plasma Rifle
|-
| 887/x377 || Plasma Rifle Clip
|-
| 888/x378 || Plasma Pistol
|-
| 889/x379 || Plasma Pistol Clip
|-
| 890/x37A || Blaster Launcher
|-
| 891/x37B || Blaster Bomb
|-
| 892/x37C || Small Launcher
|-
| 893/x37D || Stun Bomb
|-
| 894/x37E || Alien Grenade
|-
| 895/x37F || Elerium-115
|-
| 896/x380 || Mind Probe
|-
| 897/x381 || Sectoid Corpse
|-
| 898/x382 || Snakeman Corpse
|-
| 899/x383 || Ethereal Corpse
|-
| 900/x384 || Muton Corpse
|-
| 901/x385 || Floater Corpse
|-
| 902/x386 || Celatid Corpse
|-
| 903/x387 || Silacoid Corpse
|-
| 904/x388 || Chryssalid Corpse
|-
| 905/x389 || Reaper Corpse
|-
| 906/x38A || Sectopod Corpse
|-
| 907/x38B || Cyberdisc Corpse
|-
| 908/x38C || Not enough cannon rounds to arm HWP
|-
| 909/x38D || Not enough rockets to arm HWP
|-
| 910/x38E || Not enough fusion balls to arm HWP
|-
| 911/x38F || Not enough equipment to fully re-equip squad
|-
| 912/x390 || Mars: Cydonia Landing
|-
| 913/x391 || Your Avenger craft has landed in the region of Cydonia on the surface of Mars. Our information indicates that one of the pyramid constructions contains a green access lift to an underground complex. Once you have assembled all your soldiers in the lift area click on the 'abort mission' icon to continue to the next stage.
|-
| 914/x392 || Mars: The Final Assault
|-
| 915/x393 || The pyramid lift takes your battle weary soldiers deep below the planet's surface. They arrive in the heart of a large complex of tunnels and chambers. The alien brain is hidden somewhere in the labyrinth. It must be destroyed if the earth is to be saved from alien enslavement. Good Luck!
|-
| 916/x394 || in order to use or produce the 
|-
| 917/x395 || The aliens have destroyed the undefended base
|-
| 918/x396 || XCom agents have located an alien base in
|-
| 919/x397 || STANDOFF
|-
| 920/x398 || CAUTIOUS ATTACK
|-
| 921/x399 || STANDARD ATTACK
|-
| 922/x39A || AGGRESSIVE ATTACK
|-
| 923/x39B || DISENGAGING
|-
| 924/x39C || UFO HIT!
|-
| 925/x39D || UFO DESTROYED!
|-
| 926/x39E || UFO CRASH LANDS!
|-
| 927/x39F || Minimise at Standoff Range Only
|-
| 928/x3A0 || UFO RETURN FIRE!
|-
| 929/x3A1 || >>> INTERCEPTOR DAMAGED <<<
|-
| 930/x3A2 || >>> INTERCEPTOR DESTROYED <<<
|-
| 931/x3A3 || UFO OUTRUNNING INTERCEPTOR!
|-
| 932/x3A4 || ALIENS TERRORISE
|-
| 933/x3A5 || Long Range Detection
|-
| 934/x3A6 || STORES
|-
| 935/x3A7 || Difficulty Level
|-
| 936/x3A8 || INTERCEPT
|-
| 937/x3A9 || BASES
|-
| 938/x3AA || GRAPHS
|-
| 939/x3AB || UFOPEDIA
|-
| 940/x3AC || OPTIONS
|-
| 941/x3AD || FUNDING
|-
| 942/x3AE || 5 Secs
|-
| 943/x3AF || 1 Min
|-
| 944/x3B0 || 5 Mins
|-
| 945/x3B1 || 30 Mins
|-
| 946/x3B2 || 1 Hour
|-
| 947/x3B3 || 1 Day
|-
| 948/x3B4 || XCom Performance Roster
|-
| 949/x3B5 || Enter Name
|-
| 950/x3B6 || Performance Rating
|-
| 951/x3B7 || Victory Date
|-
| 952/x3B8 || Electro-flare
|-
| 953/x3B9 || This compact device produces a bright flare light when it is thrown. This will highlight enemy units in the vicinity of the electro-flare during night time missions.
|-
| 954/x3BA || Monthly Costs
|-
| 955/x3BB || Craft Rental
|-
| 956/x3BC || Salaries
|-
| 957/x3BD || Base maintenance
|-
| 958/x3BE || Cost per unit
|-
| 959/x3BF || Quantity
|-
| 960/x3C0 || Total
|-
| 961/x3C1 || day
|-
| 962/x3C2 || days
|-
| 963/x3C3 || In Psionic Training
|-
| 964/x3C4 || This device is a highly explosive missile that has an intelligent guidance system. It is fired from a blaster launcher.
|-
| 965/x3C5 || Please look up the page listed below in your Game Manual, and enter the eight digit code listed at the bottom of the page. EG: Page 13 of Game Manual Code: 3994-9668 Please Enter the Code from Page
|-
| 966/x3C6 || Front Armour
|-
| 967/x3C7 || Left Armour
|-
| 968/x3C8 || Right Armour
|-
| 969/x3C9 || Rear Armour
|-
| 970/x3CA || Under Armour
|-
| 971/x3CB || Rounds
|}
==See Also==
* [[FRENCH.DAT]]
* [[GERMAN.DAT]]
* [[ENGLISH.DAT (TFTD)]]
* [[GEOSCAPE.EXE]] - Uses the strings in this file.
* [[GEODATA]] - Parent Folder for this file.
* [[GeoScape String Files]] - A summary of the use of these strings.
* [[Tactical String Files]] - The BattleScape equivalents of these files.
* [[Saved Game Files]]
[[Category:Game Files]]

ENGLISH.DAT

2010-10-28T04:09:03Z

Hatfarm:

This is [[GeoScape String Files|one of the files]] containing the strings used by the [[GEOSCAPE.EXE|geoscape game engine]]. Each string is terminated by a null character (x00). Line breaks are defined by x0A. Every now and then x02 pops up, not sure why, probably something to do with the large font.

There are 972 entries in all, not all of which are used by the release version of the game.

{| {{StdDescTable}}
|- {{StdDescTable_Heading}}
! Index !! English.Dat (46601 Bytes)
|-
| 000/x000 || TRANSPORTER AND COMBAT SPACECRAFT. THE ULTIMATE REPLICATION OF ALIEN TECHNOLOGY.
|-
| 001/x001 || COMBAT AIRCRAFT WITH DUAL PULSE DETONATION ENGINES AND SPECIALLY SHIELDED ELECTRONIC SYSTEMS. THE BEST AVAILABLE EARTH BASED TECHNOLOGY.
|-
| 002/x002 || TRANSPORTER AND COMBAT CRAFT. A CRUDE BUT EFFECTIVE REPLICATION OF ALIEN PROPULSION SYSTEMS.
|-
| 003/x003 || TROOP TRANSPORTER. THE FASTEST OF ITS KIND, WITH VERTICAL TAKE OFF AND LANDING (V.T.O.L) CAPABILITY.
|-
| 004/x004 || COMBAT CRAFT. THIS ONE-MAN FIGHTER REPLICATES THE CLASSIC ALIEN FLYING SAUCER DESIGN, WITH CENTRAL PROPULSION UNIT.
|-
| 005/x005 || ADVANCED AIR TO AIR MISSILE WITH SPECIALLY SHIELDED ELECTRONICS.
|-
| 006/x006 || AIR TO AIR MISSILE WITH NUCLEAR WARHEAD, BUT AN EXTREMELY HEAVY LOAD.
|-
| 007/x007 || HIGH POWERED CANNON WHICH FIRES ARMOUR PIERCING ROUNDS CAPABLE OF PENETRATING 16 INCHES OF STEEL.
|-
| 008/x008 || THIS LAUNCHER FIRES A BALL SHAPED MISSILE POWERED BY ANTI-MATTER REACTION. THE BALL DESTROYS THE TARGET WITH A GRAVITY WAVE IMPLOSION.
|-
| 009/x009 || THIS CONVENTIONAL LASER BEAM IS POWERED BY AN ANTI-MATTER REACTION CHAMBER.
|-
| 010/x00A || THE GRAVITY BEAM DIRECTS A FINELY CHANNELLED IMPLODING GRAVITY FIELD.
|-
| 011/x00B || The Sectoid Hierarchy ranges from soldiers to leaders with powerful psionic abilities. These psionic powers can be used to demoralise soldiers in combat, or even take control of their minds. They tend to indulge in human abductions and cattle mutilation. The abduction is used to extract genetic material for cross breeding and developing clones for infiltrating human society. The cattle provide both nutrition and genetic material. This race appears to want to develop superior genetic hybrids to increase the efficiency of their hive-like society.
|-
| 012/x00C || The autopsy reveals vestigial digestive organs and a simple structure. The brain and eyes are very well developed. The structure suggests genetic alteration or mutation. The small mouth and nose appear to have little function. The webbing between the fingers, and the flat feet suggest aquatic origins. There are no reproductive organs, and no clues as to how this species can reproduce. They are most probably a genetically engineered species.
|-
| 013/x00D || This race developed in an extremely hostile environment. They are extremely tough and can resist extreme temperature variations. Their mobility depends on a snake-like giant 'foot' which protects all the vital organs. Their objectives appear to be purely predatory and they appear to be under the command of some other Intelligence which directs their military-style incursions on earth.
|-
| 014/x00E || The skin is extremely tough and heat resistant. The cardio-vascular system is part of the muscular system which uses the hydraulic principle to create motion. The only true muscle is the 'heart'. The reproductive system appears to be very efficient. Reproduction is asexual, with each snakeman carrying up to fifty eggs inside its body at any one time. Left to its own devices this species would be a severe threat to life on earth.
|-
| 015/x00F || This being has awesome mental powers which allow for telepathic communication and telekinetic abilities. The apparently weak physical abilities of this creature are sustained by its mental powers. We do not understand how these telekinetic powers work, since they seem to defy the laws of physics as we know them. They are extremely dangerous in any combat situation, where they rely on their mental powers for combat. They rarely appear on earth since they seem to rely on other races to pursue their objectives.
|-
| 016/x010 || This being is physically retarded and seems incapable of sustaining any life functions. The muscles are severely atrophied and the internal organs appear to be under-developed. The sensory organs, including the eyes, do not appear to function at all. The brain, however, is well developed and draws on a high proportion of the body's blood supply. It is a mystery as to how this creature can sustain itself without external support.
|-
| 017/x011 || This humanoid creature is physically powerful and intelligent. They have a particular appetite for consuming raw flesh of any kind, which they need for sustenance like earth based carnivores. They appear to rely on telepathic commands from a race known as 'Ethereals'. Once separated from this telepathic link their mental system appears to break down and they die. The cybernetic implants are used to enhance their combat performance. They are clearly the foot soldiers for a higher intelligence.
|-
| 018/x012 || The 'skin' of this creature appears to be an organically created protective armour which is grafted onto the body. There are numerous cybernetic implants which are used to enhance the cardio-vascular system and the senses. The reproductive organs appear to have been surgically removed. Evidently these unfortunate creatures are limited to a life of warfare and conquest. Armour piercing ammunition is not very effective against their toughened skin.
|-
| 019/x013 || This life-form has the mysterious natural ability to float through the air. It appears to detect human brain waves and will move towards a human target even if well hidden. Once a target is detected the Celatid lands and fires small globules of extremely corrosive venom. The creature has the ability to clone itself at an alarming rate. It accompanies the Muton race in its wonderings.
|-
| 020/x014 || The core contains a small bio-mechanical device which appears to be a naturally evolved anti-gravity propulsion system. The sac of venom is the largest organ and there does not appear to be a separate brain structure. There is no discernible digestive or reproductive system. A small organ contains embryos which can grow rapidly into a new being.
|-
| 021/x015 || This silicon based life form generates an enormous amount of heat. It has the strength to crush rocks which can then be ingested by the hot core. It has a primitive intelligence and can be controlled by implants or telepathic beings. It works with the Muton alien race.
|-
| 022/x016 || The core of the creature is extremely hot, and seems to be the basis for a digestive system. Its unique muscle system has tremendous power and speed. Its rock like skin is not harmed by fire or incendiary ammunition.
|-
| 023/x017 || The crab like claws of this creature are a powerful weapon in close combat. The high metabolism and strength of this creature give it speed and dexterity. Instead of killing its victim it impregnates it with an egg and injects a venom which turns it into a walking zombie. A new Chryssalid will burst from the victim shortly after impregnation. Chryssalids are associated with the Snakeman race.
|-
| 024/x018 || The exo-skeleton of this creature is extremely tough, but surprisingly vulnerable to explosive ammunition. The brain is well developed, and its cell growth rate very fast. The creature carries twenty eggs which are laid inside other organisms. This creature is a very effective terror weapon.
|-
| 025/x019 || The Floaters are primarily soldiers and terror agents. They are naturally predatory beasts, genetically engineered and cybernetically enhanced to make formidable warriors. The lower half of the body and most internal organs are surgically removed, and a life support system is installed. This implant contains an anti-grav unit which enables the creature to float, albeit unsteadily, through the air.
|-
| 026/x01A || The creature has been drastically altered by surgery. The device which seems to form the core of the body is a life support system, taking over the function of heart, lungs and digestive system. This would enable the creature to survive in extremely hostile environments. The brain is smaller than ours, but the sensory organs are well developed.
|-
| 027/x01B || This bipedal carnivore has powerful jaws and a voracious appetite. It has a number of brain implants which are used to control its activity. the primitive predatory instincts of this creature are of little use except to terrorise and destroy. Reapers are commonly associated with Floaters.
|-
| 028/x01C || The Reaper contains two 'brains' and two 'hearts' which allow it to function even when heavily wounded. However its furry skin is highly flammable, making the creature vulnerable to incendiary weapons.
|-
| 029/x01D || Sectopods are robot creatures with a powerful plasma beam weapon. The control if these mechanical beasts is via a telepathic link to their controllers, the Ethereals. Sectopods are the most powerful terror weapon available to the alien forces.
|-
| 030/x01E || The robot is sturdily constructed with powered armour capable of resisting most forms of attack, in particular plasma weapons. However, the sensing circuitry seems particularly vulnerable to laser weapons.
|-
| 031/x01F || This miniature flying saucer is an automated terror weapon armed with a powerful plasma beam. The anti-grav propulsion gives it a big advantage in difficult terrain. Its primary function is destruction and terror in the service of the Sectoid race.
|-
| 032/x020 || The Cyberdisc is well shielded and is particularly good at withstanding explosive ammunition. The primary anti-gravity system is too badly damaged to gain any understanding of its functioning.
|-
| 033/x021 || The power source of alien craft is an anti-matter reactor which uses Elerium (element 115) to generate powerful gravity waves as well as other forms of energy. The conversion of matter to energy is an incredible 99% efficient, therefore tiny quantities of Elerium can produce a huge amount of power. This unit can be reproduced easily using alien alloys.
|-
| 034/x022 || Alien craft use sophisticated computers to navigate on earth and through space. The system is based on optical processors arranged in network fashion. The control interface is relatively simple - the navigator controls the direction of gravity waves generated by the power source to move the craft in any direction. This system can be used easily by humans, and it can be reproduced using alien alloys and other components.
|-
| 035/x023 || Alien craft consist of three main components - a power source, a navigation system and a hull built from alien alloys. The hull is specially designed to allow gravity waves to be directed and controlled. In addition a small quantity of Elerium is required to fuel the power source. Once the principles of construction are understood, and the functions of each component are known, then it is possible to build these types of craft.
|-
| 036/x024 || These chambers contain various enzymes which are used to digest the body parts of cattle, other animals and even humans. The liquid is then consumed as ready digested food - probably direct to the bloodstream. This suggests a certain dependence on earth for food - a symbiosis between earth and alien society.
|-
| 037/x025 || These chambers contain alien foetuses. The design of these containers seems to suggest that the aliens which use this process rely completely on laboratory reproduction. The rich nutrients ensure rapid development of the foetus. This factory line system could generate thousands of alien clones in a short space of time. The process could be easily adapted for human reproduction, or alien-human hybrids.
|-
| 038/x026 || The most likely function of these spheres is recreational. The psionic circuitry stimulates various centres of the brain. The effect is similar to hallucinogenic drugs. This is the only evidence that aliens have any cultural or recreational pastimes.
|-
| 039/x027 || This surgical equipment uses laser cutters to extract certain body parts from cattle and other animals. The widespread cattle mutilations can be accounted for by this bizarre alien activity. It is likely that these parts are used for nutritional or genetic purposes.
|-
| 040/x028 || In the past many thousands of people have claimed to have been abducted by aliens, sometimes repeatedly. The truth is far more horrific. Humans are abducted, researched and monitored. The best specimens have genetic material extracted. Women have human-alien hybrid foetuses implanted, and then removed several months later. Who knows what sinister motives the aliens have?
|-
| 041/x029 || Alien craft are constructed from special alloys with unique properties. They are extremely light and durable, and can be moulded by electro-magnetic methods. This material can be reproduced and used in many kinds of manufacturing processes.
|-
| 042/x02A || You will need to research a 
|-
| 043/x02B || This element has the unusual property of generating anti-matter power when bombarded with certain particles. This creates gravity waves and other forms of energy. It is not naturally found in our solar system and cannot be reproduced.
|-
| 044/x02C || It is clear that we are fighting a losing battle on earth. The alien hordes are overwhelming in number. The best we can do is slow down their progress. The only hope for humanity is to tackle the aliens at their source. Our research seems to indicate a nearby base of operations within our solar system. Aliens indicate this place to be the centre of an ancient civilisation that pre-dates Human history. We must locate this place as soon as possible. However we need to capture and interrogate an alien leader to gain more detailed information. The larger UFOs probably contain at least one Alien leader.
|-
| 045/x02D || Our research now points to Mars as the base of alien operations. The base is well hidden, and contains all the manufacturing and cloning facilities to fuel the infiltration of earth. It also seems to contain a controlling computer of some kind that controls the whole operation. It seems that the hive-like alien society has some kind of 'queen bee'. This is their fundamental weakness - if we can eliminate the 'brain' then the body will die. We must step up our research efforts before it is too late. In order to progress we must capture the highest ranking aliens - the commanders - which only reside in alien bases.
|-
| 046/x02E || It is now clear that the alien hordes are being controlled from an underground base in Cydonia - which is an unusual area of Mars featuring five sided pyramids and a large formation resembling a human face. Cydonian civilisation once flourished on Mars many millions of years ago, but we do not know why it died out, or what the connection is with the latest alien activity there. Whatever the explanation we must send an expedition to Cydonia. This is the only way that we can defeat the aliens. We must destroy the controlling master 'brain'. We will need an Avenger craft equipped with the most awesome destructive power at our disposal. There is nothing more we can learn here - we must await the outcome of the Cydonian assault.
|-
| 047/x02F || Terror Site-
|-
| 048/x030 || CENTRE ON SITE-TIME=5 Secs
|-
| 049/x031 || CANCEL
|-
| 050/x032 || None
|-
| 051/x033 || Unknown
|-
| 052/x034 || Poor
|-
| 053/x035 || Average
|-
| 054/x036 || Good
|-
| 055/x037 || Excellent
|-
| 056/x038 || FUNDS> $
|-
| 057/x039 || BUILD NEW BASE
|-
| 058/x03A || BASE INFORMATION
|-
| 059/x03B || EQUIP CRAFT
|-
| 060/x03C || BUILD FACILITIES
|-
| 061/x03D || RESEARCH
|-
| 062/x03E || MANUFACTURE
|-
| 063/x03F || TRANSFER
|-
| 064/x040 || PURCHASE/RECRUIT
|-
| 065/x041 || SELL/SACK
|-
| 066/x042 || GEOSCAPE
|-
| 067/x043 || XCom Bases
|-
| 068/x044 || Name
|-
| 069/x045 || Area
|-
| 070/x046 || Build New Base
|-
| 071/x047 || Cancel
|-
| 072/x048 || COST>
|-
| 073/x049 || CONSTRUCTION TIME>
|-
| 074/x04A || days
|-
| 075/x04B || MAINTENANCE>
|-
| 076/x04C || OK
|-
| 077/x04D || Installation
|-
| 078/x04E || CURRENT RESEARCH
|-
| 079/x04F || Scientists Available>
|-
| 080/x050 || Scientists Allocated>
|-
| 081/x051 || Laboratory Space Available>
|-
| 082/x052 || RESEARCH PROJECT
|-
| 083/x053 || SCIENTISTS ALLOCATED
|-
| 084/x054 || PROGRESS
|-
| 085/x055 || New Project
|-
| 086/x056 || NEW RESEARCH PROJECTS
|-
| 087/x057 || SCIENTISTS AVAILABLE>
|-
| 088/x058 || LABORATORY SPACE AVAILABLE>
|-
| 089/x059 || Increase
|-
| 090/x05A || Decrease
|-
| 091/x05B || START PROJECT
|-
| 092/x05C || CURRENT PRODUCTION
|-
| 093/x05D || Engineers Available>
|-
| 094/x05E || Engineers Allocated>
|-
| 095/x05F || Workshop Space Available>
|-
| 096/x060 || Current Funds>
|-
| 097/x061 || ITEM
|-
| 098/x062 || Engineers Allocated
|-
| 099/x063 || Units Produced
|-
| 100/x064 || Total to Produce
|-
| 101/x065 || Cost per Unit
|-
| 102/x066 || Days/Hours Left
|-
| 103/x067 || New Production
|-
| 104/x068 || Production Items
|-
| 105/x069 || CATEGORY
|-
| 106/x06A || START PRODUCTION
|-
| 107/x06B || Engineer hours to produce one unit
|-
| 108/x06C || Cost per unit>$
|-
| 109/x06D || Work Space Required>
|-
| 110/x06E || SPECIAL MATERIALS REQUIRED
|-
| 111/x06F || ITEM REQUIRED
|-
| 112/x070 || UNITS REQUIRED
|-
| 113/x071 || UNITS AVAILABLE
|-
| 114/x072 || STOP PRODUCTION
|-
| 115/x073 || ENGINEERS AVAILABLE>
|-
| 116/x074 || WORKSHOP SPACE AVAILABLE>
|-
| 117/x075 || Engineers
|-
| 118/x076 || Allocated
|-
| 119/x077 || INCREASE
|-
| 120/x078 || DECREASE
|-
| 121/x079 || Units to
|-
| 122/x07A || Produce
|-
| 123/x07B || Purchase/Hire Personnel
|-
| 124/x07C || Current Funds>
|-
| 125/x07D || Cost of Purchases>
|-
| 126/x07E || COST PER UNIT
|-
| 127/x07F || QUANTITY
|-
| 128/x080 || PERSONNEL AVAILABLE:PERSONNEL TOTAL>
|-
| 129/x081 || Soldiers
|-
| 130/x082 || Engineers
|-
| 131/x083 || Scientists
|-
| 132/x084 || SPACE USED:SPACE AVAILABLE>
|-
| 133/x085 || Living Quarters
|-
| 134/x086 || Stores
|-
| 135/x087 || Laboratories
|-
| 136/x088 || Work Shops
|-
| 137/x089 || Hangars
|-
| 138/x08A || Short Range Detection
|-
| 139/x08B || Defence Strength
|-
| 140/x08C || TRANSFERS
|-
| 141/x08D || Transfers
|-
| 142/x08E || Arrival Time (hours)
|-
| 143/x08F || Cost>$
|-
| 144/x090 || Area>
|-
| 145/x091 || Base Name?
|-
| 146/x092 || SELECT POSITION FOR ACCESS LIFT
|-
| 147/x093 || Transfer
|-
| 148/x094 || AMOUNT TO TRANSFER
|-
| 149/x095 || Select Destination Base
|-
| 150/x096 || Current Funds>
|-
| 151/x097 || Cost
|-
| 152/x098 || As you enter the chamber you see the alien brain - the object of your quest. Before you can fire it communicates to you via a screen at its base. It implores you to listen to its arguments for survival before you make the decision to pull the trigger...
|-
| 153/x099 || The brain speaks: 'Many millions of years ago the planet you call Mars was alive. This life was brought to a barren planet by our civilisation as it was to yours. For millions of years we have visited your planet and genetically developed your species. You cannot kill us, you are part of us...
|-
| 154/x09A || Here is the centre of Martian civilisation - the pyramids built millions of years before yours - by a species which is your ancestor. No planet is beyond our reach. This power could be yours before long. All we ask is your co-operation...
|-
| 155/x09B || The aliens attempt to exterminate all humanity, destroying cities and poisoning the air and sea. The resistance of earth armies is futile in the face of vastly superior technology. Surviving generations suffer terrible mutations as they flee alien destruction. They are rounded up into slave camps to help transform earth into an alien colony which is part of some unknown empire.
|-
| 156/x09C || The knowledge gained through the XCom project is lost forever. You have failed to save the earth.
|-
| 157/x09D || The alien brain is interrupted by a burst of hot plasma, and the entire alien force is defeated.
|-
| 158/x09E || Once the aliens have lost Mars they have lost the earth. Before long the XCom research allows humanity to flourish once more, and claim Mars for itself. The alien menace has gone, but for how long, no one knows...
|-
| 159/x09F || You have failed to stop the alien onslaught. One by one the funding nations sign pacts with aliens promising technology, prosperity and peace. However it soon becomes clear that the aliens have other plans...
|-
| 160/x0A0 || TOTAL
|-
| 161/x0A1 || Income
|-
| 162/x0A2 || Expenditure
|-
| 163/x0A3 || Maintenance
|-
| 164/x0A4 || Balance
|-
| 165/x0A5 || UFO Activity in Areas
|-
| 166/x0A6 || UFO Activity in Countries
|-
| 167/x0A7 || XCom Activity in Areas
|-
| 168/x0A8 || XCom Activity in Countries
|-
| 169/x0A9 || Finance
|-
| 170/x0AA || st
|-
| 171/x0AB || nd
|-
| 172/x0AC || rd
|-
| 173/x0AD || th
|-
| 174/x0AE || Not enough special materials to produce 
|-
| 175/x0AF || Not enough money to produce 
|-
| 176/x0B0 || Production complete: 
|-
| 177/x0B1 || Production of 
|-
| 178/x0B2 || at 
|-
| 179/x0B3 || is complete
|-
| 180/x0B4 || OK - 5 secs
|-
| 181/x0B5 || Research Completed
|-
| 182/x0B6 || VIEW REPORTS
|-
| 183/x0B7 || We can now research
|-
| 184/x0B8 || We can now produce
|-
| 185/x0B9 || SUNDAY
|-
| 186/x0BA || MONDAY
|-
| 187/x0BB || TUESDAY
|-
| 188/x0BC || WEDNESDAY
|-
| 189/x0BD || THURSDAY
|-
| 190/x0BE || FRIDAY
|-
| 191/x0BF || SATURDAY
|-
| 192/x0C0 || Not enough
|-
| 193/x0C1 || to refuel
|-
| 194/x0C2 || to rearm
|-
| 195/x0C3 || at
|-
| 196/x0C4 || UFO is not recovered
|-
| 197/x0C5 || UFO is recovered
|-
| 198/x0C6 || Craft is lost
|-
| 199/x0C7 || Terror continues
|-
| 200/x0C8 || Aliens defeated
|-
| 201/x0C9 || Craft is lost
|-
| 202/x0CA || Base is lost
|-
| 203/x0CB || Base is saved
|-
| 204/x0CC || Base is lost
|-
| 205/x0CD || Alien Base still intact
|-
| 206/x0CE || Alien Base destroyed
|-
| 207/x0CF || Craft is lost
|-
| 208/x0D0 || ALIENS KILLED
|-
| 209/x0D1 || ALIEN CORPSES RECOVERED
|-
| 210/x0D2 || LIVE ALIENS RECOVERED
|-
| 211/x0D3 || ALIEN ARTEFACTS RECOVERED
|-
| 212/x0D4 || ALIEN BASE CONTROL DESTROYED
|-
| 213/x0D5 || CIVILIANS KILLED BY ALIENS
|-
| 214/x0D6 || CIVILIANS KILLED BY XCOM OPERATIVES
|-
| 215/x0D7 || CIVILIANS SAVED
|-
| 216/x0D8 || XCOM OPERATIVES KILLED
|-
| 217/x0D9 || XCOM OPERATIVES RETIRED THROUGH INJURY
|-
| 218/x0DA || XCOM OPERATIVES MISSING IN ACTION
|-
| 219/x0DB || TANKS DESTROYED
|-
| 220/x0DC || XCOM CRAFT LOST
|-
| 221/x0DD || UFO RECOVERY
|-
| 222/x0DE || ALIEN BASE RECOVERY
|-
| 223/x0DF || under attack!
|-
| 224/x0E0 || BASE DEFENCES INITIATED
|-
| 225/x0E1 || GRAV SHIELD REPELS UFO!
|-
| 226/x0E2 || FIRING
|-
| 227/x0E3 || HIT!
|-
| 228/x0E4 || UFO DESTROYED!
|-
| 229/x0E5 || MISSED!
|-
| 230/x0E6 || Sell Items/Sack Personnel
|-
| 231/x0E7 || VALUE OF SALES>
|-
| 232/x0E8 || FUNDS>
|-
| 233/x0E9 || Sell/Sack
|-
| 234/x0EA || Value
|-
| 235/x0EB || UFO-
|-
| 236/x0EC || CRAFT>
|-
| 237/x0ED || UFO CRASH RECOVERY
|-
| 238/x0EE || Exercise caution - There may be operatives in the UFO or around the crash site. Mission will be successful when all enemy units have been eliminated or neutralised. Recovery of UFO remains, artefacts and alien corpses can then be initiated. To abort the mission return XCom operatives to transport vehicle and click on the 'Abort Mission' icon.
|-
| 239/x0EF || UFO GROUND ASSAULT
|-
| 240/x0F0 || Explore landing site and, if possible, gain entry to the UFO. Mission will be successful when all enemy units have been eliminated or neutralised. Recovery of UFO, artefacts and alien corpses can then be initiated. To abort the mission return XCom operatives to transport vehicle and click on the 'Abort Mission' icon.
|-
| 241/x0F1 || BASE DEFENCE
|-
| 242/x0F2 || BASE>
|-
| 243/x0F3 || An Alien vessel has landed nearby. Our base is in severe danger. As per standard procedure all non combat personnel and XCom craft have been evacuated. Alien units will enter the base via hangar doors or the access lift. Defend the base and its vital installations at all costs - this is a fight to the death. If you click on the 'abort mission' icon you will concede defeat and lose the base.
|-
| 244/x0F4 || ALIEN BASE ASSAULT
|-
| 245/x0F5 || CRAFT>
|-
| 246/x0F6 || XCom operatives have gained entrance to an alien base. The control centre must be destroyed to render the base inoperative. The Mission will terminate when all enemies are eliminated, or when your squad has returned to the green exit area (click on the 'abort mission' icon to escape).
|-
| 247/x0F7 || You have arrived in Cydonia. You gain entry to a large underground complex near the Martian Sphinx. You must destroy the Alien Brain that controls all alien activity. The fate of humanity is in your hands....
|-
| 248/x0F8 || TERROR SITE-
|-
| 249/x0F9 || TERROR MISSION
|-
| 250/x0FA || Mission will be successful when all enemy units have been eliminated or neutralised. You must attempt to save the lives of any civilians in the area by neutralising the alien menace. To abort the mission return XCom operatives to transport vehicle and click on the 'Abort Mission' icon.
|-
| 251/x0FB || NO FREE HANGARS FOR CRAFT PRODUCTION!x02Each craft assigned to a base, transferred to a base, purchased or constructed uses one hangar. Build a new hangar or transfer a craft to another base.
|-
| 252/x0FC || NO FREE HANGARS FOR PURCHASE!x02Each craft assigned to a base, transferred to a base, purchased or constructed uses one hangar. Build a new hangar or transfer a craft to another base.
|-
| 253/x0FD || NO FREE HANGARS FOR TRANSFER!x02Each craft assigned to a base, transferred to a base, purchased or constructed uses one hangar. Build a new hangar or transfer a craft to another base.
|-
| 254/x0FE || CANNOT BUILD HERE!x02You must build next to an existing base facility.
|-
| 255/x0FF || NO FREE ACCOMODATION!x02The destination base does not have enough space in living quarters.
|-
| 256/x100 || NOT ENOUGH WORK SPACE AVAILABLE!x02Build a new workshop or reduce work on other projects.
|-
| 257/x101 || NOT ENOUGH MONEY!
|-
| 258/x102 || NOT ENOUGH TRANSFER SUPPORT!x02Wait for existing transfers or purchases to reach destination.
|-
| 259/x103 || NO MORE SOLDIERS ALLOWED!x02You have already recruited the maximum number of soldiers.
|-
| 260/x104 || NOT ENOUGH STORE SPACE!x02Build a new store facility or transfer existing stores to other bases.
|-
| 261/x105 || NOT ENOUGH LIVING SPACE!x02Build new living quarters or transfer personnel to other bases.
|-
| 262/x106 || NO MORE EQUIPMENT ALLOWED ON BOARD!x02You are only allowed to take a maximum of 80 items of equipment on missions.
|-
| 263/x107 || TOO MANY BUTTONS!
|-
| 264/x108 || LAUNCH INTERCEPTION
|-
| 265/x109 || CRAFT
|-
| 266/x10A || STATUS
|-
| 267/x10B || BASE
|-
| 268/x10C || READY
|-
| 269/x10D || OUT
|-
| 270/x10E || REPAIRS
|-
| 271/x10F || REFUELLING
|-
| 272/x110 || REARMING
|-
| 273/x111 || TARGET:
|-
| 274/x112 || ALIEN BASE-
|-
| 275/x113 || CRASH SITE-
|-
| 276/x114 || LANDING SITE-
|-
| 277/x115 || TARGET: WAY POINT
|-
| 278/x116 || Are you sure you want to send this craft on a mission to Cydonia?
|-
| 279/x117 || YES
|-
| 280/x118 || NO
|-
| 281/x119 || SELECT DESTINATION
|-
| 282/x11A || CYDONIA
|-
| 283/x11B || SELECT SITE FOR NEW BASE
|-
| 284/x11C || RETURN TO BASE
|-
| 285/x11D || SELECT NEW TARGET
|-
| 286/x11E || PATROL
|-
| 287/x11F || STATUS>
|-
| 288/x120 || DAMAGED - RETURNING TO BASE
|-
| 289/x121 || LOW FUEL - RETURNING TO BASE
|-
| 290/x122 || PATROLLING
|-
| 291/x123 || TAILING UFO
|-
| 292/x124 || INTERCEPTING UFO-
|-
| 293/x125 || RETURNING TO BASE
|-
| 294/x126 || DESTINATION: ALIEN BASE-
|-
| 295/x127 || DESTINATION: CRASH SITE-
|-
| 296/x128 || DESTINATION: LANDING SITE-
|-
| 297/x129 || DESTINATION: WAY POINT-
|-
| 298/x12A || BASE>
|-
| 299/x12B || SPEED>
|-
| 300/x12C || MAXIMUM SPEED>
|-
| 301/x12D || ALTITUDE>
|-
| 302/x12E || VERY LOW
|-
| 303/x12F || LOW
|-
| 304/x130 || HIGH
|-
| 305/x131 || VERY HIGH
|-
| 306/x132 || FUEL>
|-
| 307/x133 || WEAPON-1>
|-
| 308/x134 || NONE
|-
| 309/x135 || ROUNDS>
|-
| 310/x136 || WEAPON-2>
|-
| 311/x137 || HOSTILE
|-
| 312/x138 || NEUTRAL
|-
| 313/x139 || FRIENDLY
|-
| 314/x13A || COMMITTED
|-
| 315/x13B || GAME OPTIONS
|-
| 316/x13C || LOAD GAME
|-
| 317/x13D || SAVE GAME
|-
| 318/x13E || INTERCEPTION CRAFT
|-
| 319/x13F || Base>
|-
| 320/x140 || NAME
|-
| 321/x141 || STATUS
|-
| 322/x142 || AMMO>
|-
| 323/x143 || CREW
|-
| 324/x144 || EQUIPMENT
|-
| 325/x145 || ARMOUR
|-
| 326/x146 || MAX>
|-
| 327/x147 || Rookie
|-
| 328/x148 || Squaddie
|-
| 329/x149 || Sergeant
|-
| 330/x14A || Captain
|-
| 331/x14B || Colonel
|-
| 332/x14C || Commander
|-
| 333/x14D || Select Squad for
|-
| 334/x14E || SPACE AVAILABLE>
|-
| 335/x14F || SPACE USED>
|-
| 336/x150 || RANK
|-
| 337/x151 || CRAFT
|-
| 338/x152 || WOUNDED
|-
| 339/x153 || Equipment for
|-
| 340/x154 || Arm
|-
| 341/x155 || Defence Value
|-
| 342/x156 || Hit Ratio
|-
| 343/x157 || ready to land near
|-
| 344/x158 || Begin Mission?
|-
| 345/x159 || Select Armament
|-
| 346/x15A || AMMUNITION
|-
| 347/x15B || ARMAMENT
|-
| 348/x15C || AVAILABLE
|-
| 349/x15D || N.A.
|-
| 350/x15E || SELECT ARMOUR FOR
|-
| 351/x15F || TYPE
|-
| 352/x160 || PERSONAL ARMOUR
|-
| 353/x161 || POWER SUIT
|-
| 354/x162 || FLYING SUIT
|-
| 355/x163 || Select Armour
|-
| 356/x164 || ARMOUR
|-
| 357/x165 || NORTH
|-
| 358/x166 || NORTH EAST
|-
| 359/x167 || EAST
|-
| 360/x168 || SOUTH EAST
|-
| 361/x169 || SOUTH
|-
| 362/x16A || SOUTH WEST
|-
| 363/x16B || WEST
|-
| 364/x16C || NORTH WEST
|-
| 365/x16D || SELECT ACTION
|-
| 366/x16E || CONTINUE INTERCEPTION PURSUIT
|-
| 367/x16F || PURSUE WITHOUT INTERCEPTION
|-
| 368/x170 || VERY LARGE
|-
| 369/x171 || LARGE
|-
| 370/x172 || MEDIUM
|-
| 371/x173 || SMALL
|-
| 372/x174 || VERY SMALL
|-
| 373/x175 || GROUND
|-
| 374/x176 || VERY LOW
|-
| 375/x177 || LOW
|-
| 376/x178 || HIGH
|-
| 377/x179 || VERY HIGH
|-
| 378/x17A || Detected
|-
| 379/x17B || SIZE
|-
| 380/x17C || ALTITUDE
|-
| 381/x17D || HEADING
|-
| 382/x17E || SPEED
|-
| 383/x17F || CENTRE ON UFO-TIME=5 Secs
|-
| 384/x180 || TRACKING LOST
|-
| 385/x181 || REDIRECT CRAFT
|-
| 386/x182 || GO TO LAST KNOWN UFO POSITION
|-
| 387/x183 || UFO-
|-
| 388/x184 || CRAFT-
|-
| 389/x185 || BASE-
|-
| 390/x186 || ALIEN BASE-
|-
| 391/x187 || CRASH SITE-
|-
| 392/x188 || LANDING SITE-
|-
| 393/x189 || WAY POINT-
|-
| 394/x18A || TERROR SITE-
|-
| 395/x18B || has reached
|-
| 396/x18C || Destination
|-
| 397/x18D || Now patrolling
|-
| 398/x18E || Alien Origins
|-
| 399/x18F || The Martian Solution
|-
| 400/x190 || Cydonia or Bust
|-
| 401/x191 || UFOpaedia
|-
| 402/x192 || XCOM CRAFT & ARMAMENT
|-
| 403/x193 || HEAVY WEAPONS PLATFORMS
|-
| 404/x194 || WEAPONS AND EQUIPMENT
|-
| 405/x195 || ALIEN ARTEFACTS
|-
| 406/x196 || BASE FACILITIES
|-
| 407/x197 || ALIEN LIFE FORMS
|-
| 408/x198 || ALIEN RESEARCH
|-
| 409/x199 || UFO COMPONENTS
|-
| 410/x19A || UFOs
|-
| 411/x19B || SELECT ITEM
|-
| 412/x19C || autopsy
|-
| 413/x19D || MAXIMUM SPEED>
|-
| 414/x19E || ACCELERATION>
|-
| 415/x19F || FUEL CAPACITY>
|-
| 416/x1A0 || WEAPON PODS>
|-
| 417/x1A1 || DAMAGE CAPACITY>
|-
| 418/x1A2 || CARGO SPACE>
|-
| 419/x1A3 || HWP CAPACITY>
|-
| 420/x1A4 || Damage...................
|-
| 421/x1A5 || Range......................
|-
| 422/x1A6 || km
|-
| 423/x1A7 || Accuracy...............
|-
| 424/x1A8 || Re-load time........
|-
| 425/x1A9 || s
|-
| 426/x1AA || ARMOUR PIERCING
|-
| 427/x1AB || INCENDIARY
|-
| 428/x1AC || HIGH EXPLOSIVE
|-
| 429/x1AD || LASER BEAM
|-
| 430/x1AE || PLASMA BEAM
|-
| 431/x1AF || STUN
|-
| 432/x1B0 || 6-?
|-
| 433/x1B1 || 7-?
|-
| 434/x1B2 || 8-?
|-
| 435/x1B3 || 9-?
|-
| 436/x1B4 || SHOT TYPE>
|-
| 437/x1B5 || ACCURACY>
|-
| 438/x1B6 || TU COST>
|-
| 439/x1B7 || DAMAGE
|-
| 440/x1B8 || AMMO
|-
| 441/x1B9 || Auto
|-
| 442/x1BA || Snap
|-
| 443/x1BB || Aimed
|-
| 444/x1BC || Construction Time
|-
| 445/x1BD || days
|-
| 446/x1BE || Construction Cost
|-
| 447/x1BF || Maintenance Cost
|-
| 448/x1C0 || autopsy
|-
| 449/x1C1 || -
|-
| 450/x1C2 || Low
|-
| 451/x1C3 || Medium
|-
| 452/x1C4 || High
|-
| 453/x1C5 || High
|-
| 454/x1C6 || Craft Weapon
|-
| 455/x1C7 || Craft Ammunition
|-
| 456/x1C8 || Heavy Weapons Platform
|-
| 457/x1C9 || Weapon
|-
| 458/x1CA || Ammunition
|-
| 459/x1CB || Equipment
|-
| 460/x1CC || Alien Corpse
|-
| 461/x1CD || UFO component
|-
| 462/x1CE || Personal Armour
|-
| 463/x1CF || Raw Materials
|-
| 464/x1D0 || HWP Cannon Shells
|-
| 465/x1D1 || Alien
|-
| 466/x1D2 || Sectoid
|-
| 467/x1D3 || Snakeman
|-
| 468/x1D4 || Ethereal
|-
| 469/x1D5 || Muton
|-
| 470/x1D6 || Floater
|-
| 471/x1D7 || Celatid
|-
| 472/x1D8 || Silacoid
|-
| 473/x1D9 || Chryssalid
|-
| 474/x1DA || Reaper
|-
| 475/x1DB || Sectopod
|-
| 476/x1DC || Cyberdisc
|-
| 477/x1DD || Commander
|-
| 478/x1DE || Leader
|-
| 479/x1DF || Engineer
|-
| 480/x1E0 || Medic
|-
| 481/x1E1 || Navigator
|-
| 482/x1E2 || Soldier
|-
| 483/x1E3 || Terrorist
|-
| 484/x1E4 || UFO Power Source
|-
| 485/x1E5 || UFO Navigation
|-
| 486/x1E6 || UFO Construction
|-
| 487/x1E7 || Alien Food
|-
| 488/x1E8 || Alien Reproduction
|-
| 489/x1E9 || Alien Entertainment
|-
| 490/x1EA || Alien Surgery
|-
| 491/x1EB || Examination Room
|-
| 492/x1EC || Alien Alloys
|-
| 493/x1ED || Alien Habitat
|-
| 494/x1EE || Personal Armour
|-
| 495/x1EF || Power Suit
|-
| 496/x1F0 || Flying Suit
|-
| 497/x1F1 || HWP Rockets
|-
| 498/x1F2 || HWP Fusion Bomb
|-
| 499/x1F3 || Laser Weapons
|-
| 500/x1F4 || New Fighter Craft
|-
| 501/x1F5 || New Fighter-Transporter
|-
| 502/x1F6 || Ultimate Craft
|-
| 503/x1F7 || Laser Pistol
|-
| 504/x1F8 || Laser Rifle
|-
| 505/x1F9 || Heavy Laser
|-
| 506/x1FA || Laser Cannon
|-
| 507/x1FB || Plasma Cannon
|-
| 508/x1FC || Fusion Missile
|-
| 509/x1FD || Laser Defence
|-
| 510/x1FE || Plasma Defence
|-
| 511/x1FF || Fusion Defence
|-
| 512/x200 || Grav Shield
|-
| 513/x201 || Mind Shield
|-
| 514/x202 || Psi-Lab
|-
| 515/x203 || Hyper Wave Decoder
|-
| 516/x204 || NOT USED
|-
| 517/x205 || NOT USED
|-
| 518/x206 || NOT USED
|-
| 519/x207 || UFO construction
|-
| 520/x208 || Alien Origins
|-
| 521/x209 || The Martian Solution
|-
| 522/x20A || Cydonia or Bust
|-
| 523/x20B || Motion Scanner
|-
| 524/x20C || Medi-Kit
|-
| 525/x20D || Tank/Cannon
|-
| 526/x20E || Tank/Rocket Launcher
|-
| 527/x20F || Tank/Laser Cannon
|-
| 528/x210 || Hovertank/Plasma
|-
| 529/x211 || Hovertank/Launcher
|-
| 530/x212 || Stingray Launcher
|-
| 531/x213 || Avalanche Launcher
|-
| 532/x214 || Cannon
|-
| 533/x215 || Fusion Ball Launcher
|-
| 534/x216 || Laser Cannon
|-
| 535/x217 || Plasma Beam
|-
| 536/x218 || Stingray Missile
|-
| 537/x219 || Avalanche Missile
|-
| 538/x21A || Cannon Rounds(x50)
|-
| 539/x21B || Fusion Ball
|-
| 540/x21C || Soldier
|-
| 541/x21D || Scientist
|-
| 542/x21E || Engineer
|-
| 543/x21F || North America
|-
| 544/x220 || Arctic
|-
| 545/x221 || Antarctica
|-
| 546/x222 || South America
|-
| 547/x223 || Europe
|-
| 548/x224 || North Africa
|-
| 549/x225 || Southern Africa
|-
| 550/x226 || Central Asia
|-
| 551/x227 || South East Asia
|-
| 552/x228 || Siberia
|-
| 553/x229 || Australasia
|-
| 554/x22A || Pacific
|-
| 555/x22B || North Atlantic
|-
| 556/x22C || South Atlantic
|-
| 557/x22D || Indian Ocean
|-
| 558/x22E || Alien Research
|-
| 559/x22F || Alien Harvest
|-
| 560/x230 || Alien Abduction
|-
| 561/x231 || Alien Infiltration
|-
| 562/x232 || Alien Base
|-
| 563/x233 || Alien Terror
|-
| 564/x234 || Alien Retaliation
|-
| 565/x235 || Alien Supply
|-
| 566/x236 || Power Sources
|-
| 567/x237 || Maximum Speed
|-
| 568/x238 || HYPER-WAVE DECODER
|-
| 569/x239 || SKYRANGER
|-
| 570/x23A || LIGHTNING
|-
| 571/x23B || AVENGER
|-
| 572/x23C || INTERCEPTOR
|-
| 573/x23D || FIRESTORM
|-
| 574/x23E || UFO
|-
| 575/x23F || STINGRAY
|-
| 576/x240 || AVALANCHE
|-
| 577/x241 || CANNON
|-
| 578/x242 || FUSION BALL
|-
| 579/x243 || LASER CANNON
|-
| 580/x244 || PLASMA BEAM
|-
| 581/x245 || Damage Capacity
|-
| 582/x246 || Weapon Power
|-
| 583/x247 || Weapon Range
|-
| 584/x248 || Access Lift
|-
| 585/x249 || Living Quarters
|-
| 586/x24A || Laboratory
|-
| 587/x24B || Workshop
|-
| 588/x24C || Small Radar System
|-
| 589/x24D || Large Radar System
|-
| 590/x24E || Missile Defences
|-
| 591/x24F || General Stores
|-
| 592/x250 || Alien Containment
|-
| 593/x251 || Laser Defences
|-
| 594/x252 || Plasma Defences
|-
| 595/x253 || Fusion Ball Defences
|-
| 596/x254 || Grav Shield
|-
| 597/x255 || Mind Shield
|-
| 598/x256 || Psionic Laboratory
|-
| 599/x257 || Hyper-wave Decoder
|-
| 600/x258 || Hangar
|-
| 601/x259 || USA
|-
| 602/x25A || RUSSIA
|-
| 603/x25B || UK
|-
| 604/x25C || FRANCE
|-
| 605/x25D || GERMANY
|-
| 606/x25E || ITALY
|-
| 607/x25F || SPAIN
|-
| 608/x260 || CHINA
|-
| 609/x261 || JAPAN
|-
| 610/x262 || INDIA
|-
| 611/x263 || BRAZIL
|-
| 612/x264 || AUSTRALIA
|-
| 613/x265 || NIGERIA
|-
| 614/x266 || SOUTH AFRICA
|-
| 615/x267 || EGYPT
|-
| 616/x268 || CANADA
|-
| 617/x269 || Floater Soldier
|-
| 618/x26A || Floater Navigator
|-
| 619/x26B || Floater Medic
|-
| 620/x26C || Floater Engineer
|-
| 621/x26D || Floater Leader
|-
| 622/x26E || Floater Commander
|-
| 623/x26F || Reaper
|-
| 624/x270 || Tank
|-
| 625/x271 || Civilian
|-
| 626/x272 || Jan
|-
| 627/x273 || Feb
|-
| 628/x274 || Mar
|-
| 629/x275 || Apr
|-
| 630/x276 || May
|-
| 631/x277 || Jun
|-
| 632/x278 || Jul
|-
| 633/x279 || Aug
|-
| 634/x27A || Sep
|-
| 635/x27B || Oct
|-
| 636/x27C || Nov
|-
| 637/x27D || Dec
|-
| 638/x27E || International Relations
|-
| 639/x27F || Country
|-
| 640/x280 || Funding
|-
| 641/x281 || Change
|-
| 642/x282 || WEAPON SYSTEMS
|-
| 643/x283 || CREW
|-
| 644/x284 || HWPs
|-
| 645/x285 || DAMAGE>
|-
| 646/x286 || The access lift allows equipment and personnel to be transferred into or out of an underground base. It is always the first facility to be constructed on a new site. The lift area is vulnerable to intrusion from any potential hostile force.
|-
| 647/x287 || Each accommodation block provides for up to 50 personnel. The facility provides basic recreation, food and sleeping areas.
|-
| 648/x288 || Up to 50 scientists can work in a laboratory facility. Laboratories are equipped with the latest technology for research into materials, biochemistry and cosmology. There is privileged access to the best research labs throughout the world, including military establishments.
|-
| 649/x289 || A workshop contains all the equipment necessary to manufacture equipment based on designs from the science labs. Up to 50 engineers can occupy a workshop, although items under construction will also consume some space.
|-
| 650/x28A || A small detection system has an effective radar range of 300 nautical miles and is linked to satellite systems for ground search. Each system has a 5% chance of detecting an average sized object every 10 minutes.
|-
| 651/x28B || A large detection system has an effective range of 450 nautical miles and is linked to satellite systems for ground search. Each system has a 5% chance of detecting an average sized object every 10 minutes.
|-
| 652/x28C || Missile defences provide some protection against incursion by hostile craft which are attempting to land near the base.
|-
| 653/x28D || All equipment, weapons systems, munitions, recovered material and Heavy Weapons Platforms are placed in stores, with the exception of equipment assigned to craft in hangars.
|-
| 654/x28E || Living aliens are likely to require a special habitat to maintain their life systems. The containment facility can keep up to 10 alien life forms in self contained units.
|-
| 655/x28F || Laser defences provide protection against incursion by hostile craft.
|-
| 656/x290 || Plasma beam defences provide powerful and efficient protection against incursion by hostile craft.
|-
| 657/x291 || Fusion missiles provide the most effective defence against alien attacks. These missiles create an anti-matter implosion which destroys everything within a specific radius.
|-
| 658/x292 || The Gravity shield repels alien craft attempting to land near the base long enough for all defence systems to fire again. In practice this will double the effectiveness of any defence systems at your base.
|-
| 659/x293 || Since alien craft rely on brain waves to detect human presence then the most effective counter measure is to shield brain waves from the base. This facility will drastically reduce the chances of detection by alien craft.
|-
| 660/x294 || The psionics lab can assess the psionic potential of all soldiers at the base and give them the necessary training to utilise their psionic skills. Each lab can train up to ten soldiers. Training is allocated at the end of each month. Psionic skills used in conjunction with a Psi-amp can be used for psionic attacks during combat.
|-
| 661/x295 || Alien communications rely on a supra-dimensional wave which travels almost instantaneously. The decoder facility intercepts UFO transmissions and decodes the information. This will show the type of UFO, the alien race and the type of activity.
|-
| 662/x296 || Each hangar can accommodate one craft. There are facilities for maintenance, refuelling and repair of XCom craft. Each craft stationed at a base must have a free hangar assigned to it which cannot be used by other craft, even if the assigned craft is out on a mission.
|-
| 663/x297 || The standard issue XCom pistol is a high powered semi-automatic with a 12 round capacity.
|-
| 664/x298 || This highly accurate sniper rifle has laser guided sights and takes 6.7mm ammunition in 20 round clips.
|-
| 665/x299 || The heavy cannon is a devastating, but cumbersome, weapon. Its versatility comes from the fact that it can take three types of ammunition - armour piercing, incendiary and high explosive.
|-
| 666/x29A || The auto-cannon combines the versatility and power of a heavy cannon with a faster fire rate.
|-
| 667/x29B || The rocket launcher is a laser guided system which can fire three different sizes of missile.
|-
| 668/x29C || The laser pistol is an effective implementation of new technology. It has the convenience of a pistol with faster and more accurate firing.
|-
| 669/x29D || The laser rifle is a more powerful and accurate version of the earlier pistol design.
|-
| 670/x29E || The heavy laser is cumbersome, but extremely effective.
|-
| 671/x29F || This standard issue grenade has an accurate and sophisticated timer for precision control.
|-
| 672/x2A0 || Smoke grenades are useful for providing cover in exposed combat situations. Use with care because they can benefit the enemy as well
|-
| 673/x2A1 || A proximity grenade can be thrown like an ordinary grenade but is triggered by nearby movement after it lands. Great skill and care is required to use these devices properly.
|-
| 674/x2A2 || This explosive should only be used for demolition purposes. Keep personnel clear of demolition sites.
|-
| 675/x2A3 || This sophisticated device uses a variety of detectors and advanced computer algorithms to identify moving enemy units. However, it requires some practice to use effectively. Click on the motion scanner icon on the tactical display. Select 'Use Scanner' from the menu. The Scanner display shows an arrow in the centre which is the direction the soldier is facing (North is at the top). The flashing blobs show units which have moved recently. Large units, or fast moving units, will produce larger blobs. Static units will not be detected.
|-
| 676/x2A4 || The medi-kit combines a healing facility with pain killers and stimulants. In order to use the medi-kit you must face towards the soldier requiring treatment. If the soldier is stunned you must stand over the body. Click on the medi-kit icon and select 'use medi-kit' from the menu. HEALING> Red body parts show fatal wounds. Click on a body part that is wounded. Click on the 'Heal' button. One fatal wound will be cured and some health restored. STIMULANT> This will restore energy and revive unconscious (stunned) soldiers. In order to revive an unconscious soldier you must stand directly over the body. PAIN KILLER> This will restore the morale of wounded soldiers up to an amount equivalent to the soldier's lost health.
|-
| 677/x2A5 || The Psi-amp can only be used by soldiers with psionic skill. During combat, click on the Psi-amp, select the type of attack, and select a target unit with the cursor. There are two types of psionic attack: PANIC UNIT> If the attack is successful it will reduce the target's morale and may cause it to panic. MIND CONTROL> If this is successful then you will gain immediate control of the enemy unit as if it was one of your own (except that you cannot access the object screen). It is more difficult to be successful with this type of attack.
|-
| 678/x2A6 || This device can only be used in close combat, but will stun a living organism without killing it by using electric shocks.
|-
| 679/x2A7 || The subject has died due to the trauma of interrogation.
|-
| 680/x2A8 || The mind probe is an alien communication device which is used to take information directly from brain waves. XCom units can use this device in combat to display an alien's characteristics. Click on the mind probe and the 'use' option. Then click on an alien with the cursor.
|-
| 681/x2A9 || Plasma pistols are a lethal alien weapon based on accelerating particles from within a minute anti-gravity field
|-
| 682/x2AA || This is a devastatingly powerful weapon based on accelerating particles from within a minute anti-gravity field
|-
| 683/x2AB || Size
|-
| 684/x2AC || The corpse may be researched for a full autopsy report.
|-
| 685/x2AD || Not enough ammunition to arm
|-
| 686/x2AE || This is an alien guided missile launcher which fires powerful 'blaster bombs'. When you click to fire the weapon it will generate 'way points' for the blaster bomb to follow. When you have positioned enough way points click on the special launch icon.
|-
| 687/x2AF || A small launcher which fires stun bombs. Very useful for capturing live aliens.
|-
| 688/x2B0 || This device works in the same way as a terrestrial grenade - except that it is more powerful.
|-
| 689/x2B1 || Small Scout
|-
| 690/x2B2 || Medium Scout
|-
| 691/x2B3 || Large Scout
|-
| 692/x2B4 || Harvester
|-
| 693/x2B5 || Abducter
|-
| 694/x2B6 || Terror ship
|-
| 695/x2B7 || Battleship
|-
| 696/x2B8 || Supply ship
|-
| 697/x2B9 || RATING>
|-
| 698/x2BA || TERRIBLE!
|-
| 699/x2BB || POOR!
|-
| 700/x2BC || OK
|-
| 701/x2BD || GOOD!
|-
| 702/x2BE || EXCELLENT!
|-
| 703/x2BF || SCORE
|-
| 704/x2C0 || XCOM PROJECT MONTHLY REPORT
|-
| 705/x2C1 || Month>
|-
| 706/x2C2 || The council of funding nations is generally satisfied with your progress so far.
|-
| 707/x2C3 || The council of funding nations is very pleased with your excellent progress. Keep up the good work.
|-
| 708/x2C4 || The council of funding nations is dissatisfied with your performance. You must improve your effectiveness in dealing with the alien menace or risk termination of the project.
|-
| 709/x2C5 || You have not succeeded in dealing with the alien invasion and the council of funding nations has regrettably decided to terminate the project. Each nation shall deal with the problem as they see fit. We can only hope that we can come to some accommodation with these apparently hostile forces, and that the general population will come to terms with the alien visitors.
|-
| 710/x2C6 || is particularly pleased with your ability to deal with the localised threat and has agreed to increase its funding.
|-
| 711/x2C7 || are particularly happy with your progress in dealing with local alien incursion and have agreed to increase their funding.
|-
| 712/x2C8 || and
|-
| 713/x2C9 || is unhappy with your ability to deal with alien activity in its territory and has decided to reduce its financial commitment.
|-
| 714/x2CA || are unhappy with your ability to deal with alien activity in their territory and have decided to reduce their funding.
|-
| 715/x2CB || knots
|-
| 716/x2CC || has signed a secret pact with unknown alien forces and has withdrawn from the project.
|-
| 717/x2CD || have signed a secret pact with unknown alien forces and have withdrawn from the project.
|-
| 718/x2CE || Monthly Rating>
|-
| 719/x2CF || Funding change>
|-
| 720/x2D0 || The funding council is not happy with your financial position. You must reduce your debts below $2million or the project will be terminated.
|-
| 721/x2D1 || HYPER-WAVE TRANSMISSIONS ARE DECODED
|-
| 722/x2D2 || CRAFT TYPE
|-
| 723/x2D3 || RACE
|-
| 724/x2D4 || MISSION
|-
| 725/x2D5 || ZONE
|-
| 726/x2D6 || Allocate Research
|-
| 727/x2D7 || Allocate Manufacture
|-
| 728/x2D8 || New York
|-
| 729/x2D9 || Washington
|-
| 730/x2DA || Los Angeles
|-
| 731/x2DB || Montreal
|-
| 732/x2DC || Havana
|-
| 733/x2DD || Mexico City
|-
| 734/x2DE || Chicago
|-
| 735/x2DF || Vancouver
|-
| 736/x2E0 || Dallas
|-
| 737/x2E1 || Brasilia
|-
| 738/x2E2 || Bogota
|-
| 739/x2E3 || Buenos Aires
|-
| 740/x2E4 || Santiago
|-
| 741/x2E5 || Rio De Janeiro
|-
| 742/x2E6 || Lima
|-
| 743/x2E7 || Caracas
|-
| 744/x2E8 || London
|-
| 745/x2E9 || Paris
|-
| 746/x2EA || Berlin
|-
| 747/x2EB || Moscow
|-
| 748/x2EC || Rome
|-
| 749/x2ED || Madrid
|-
| 750/x2EE || Budapest
|-
| 751/x2EF || Lagos
|-
| 752/x2F0 || Cairo
|-
| 753/x2F1 || Casablanca
|-
| 754/x2F2 || Pretoria
|-
| 755/x2F3 || Nairobi
|-
| 756/x2F4 || Cape Town
|-
| 757/x2F5 || Kinshasa
|-
| 758/x2F6 || Ankara
|-
| 759/x2F7 || Delhi
|-
| 760/x2F8 || Karachi
|-
| 761/x2F9 || Baghdad
|-
| 762/x2FA || Tehran
|-
| 763/x2FB || Bombay
|-
| 764/x2FC || Calcutta
|-
| 765/x2FD || Tokyo
|-
| 766/x2FE || Beijing
|-
| 767/x2FF || Bangkok
|-
| 768/x300 || Manila
|-
| 769/x301 || Seoul
|-
| 770/x302 || Singapore
|-
| 771/x303 || Jakarta
|-
| 772/x304 || Shanghai
|-
| 773/x305 || Hong Kong
|-
| 774/x306 || Novosibirsk
|-
| 775/x307 || Canberra
|-
| 776/x308 || Wellington
|-
| 777/x309 || Melbourne
|-
| 778/x30A || Perth
|-
| 779/x30B || UFOx02Enemy Unknown
|-
| 780/x30C || New Game
|-
| 781/x30D || Load Saved Game
|-
| 782/x30E || Select Difficulty Level
|-
| 783/x30F || 1> Beginner
|-
| 784/x310 || 2> Experienced
|-
| 785/x311 || 3> Veteran
|-
| 786/x312 || 4> Genius
|-
| 787/x313 || 5> Superhuman
|-
| 788/x314 || Time
|-
| 789/x315 || Date
|-
| 790/x316 || Select game to load
|-
| 791/x317 || Select save position
|-
| 792/x318 || PSIONIC TRAINING
|-
| 793/x319 || Remaining Psi-lab capacity>
|-
| 794/x31A || Psionic Strength
|-
| 795/x31B || Psionic Skill /Improvement
|-
| 796/x31C || Psi-Amp
|-
| 797/x31D || In Training?
|-
| 798/x31E || TARGETTED BY:
|-
| 799/x31F || WEAPONS/ CREW/HWPs
|-
| 800/x320 || ABANDON GAME
|-
| 801/x321 || Quit
|-
| 802/x322 || is low on fuel, returning to base
|-
| 803/x323 || Soldier List
|-
| 804/x324 || RANK>
|-
| 805/x325 || MISSIONS>
|-
| 806/x326 || KILLS>
|-
| 807/x327 || WOUND RECOVERY>
|-
| 808/x328 || TIME UNITS
|-
| 809/x329 || STAMINA
|-
| 810/x32A || HEALTH
|-
| 811/x32B || BRAVERY
|-
| 812/x32C || REACTIONS
|-
| 813/x32D || FIRING ACCURACY
|-
| 814/x32E || THROWING ACCURACY
|-
| 815/x32F || STRENGTH
|-
| 816/x330 || PSIONIC STRENGTH
|-
| 817/x331 || PSIONIC SKILL
|-
| 818/x332 || NEW RANK
|-
| 819/x333 || Promotions
|-
| 820/x334 || SOLDIERS
|-
| 821/x335 || Automated heavy weapons platforms are designed to complement an XCom squad. The combination of high fire power and strong armour makes these units valuable for open terrain fire fights. Make sure that there are sufficient cannon shells in your stores to re-arm tanks. They are armed automatically when you assign them to a squad.
|-
| 822/x336 || This automated heavy weapons platform is armed with powerful rockets. This will be devastating for any alien foe. Make sure your stores are kept supplied with HWP rockets.
|-
| 823/x337 || Laser weapons are a useful addition for HWPs. It combines heavy firepower with no ammunition restrictions.
|-
| 824/x338 || Alien technology has given the HWP a new lease of life. The added manoeuvrability of air travel and the power of plasma beams is a lethal combination.
|-
| 825/x339 || This hovertank has a fusion ball launcher that is capable of immense devastation. Use it with great care. You will have to manufacture the fusion balls to keep these HWPs fully armed. A fusion ball is an intelligent guided weapon. In order to fire it you select a number of 'way points' with the cursor and then click on the launch icon to fire the fusion ball.
|-
| 826/x33A || This compact device is used as ammunition for a Heavy Plasma Gun. It contains a small quantity of Elerium.
|-
| 827/x33B || This small object is used as a power source for a plasma rifle - a medium powered alien weapon. Contains a small quantity of Elerium.
|-
| 828/x33C || Power source for the small alien plasma pistol. Contains Elerium - the source of all alien power.
|-
| 829/x33D || The Stun bomb is used for capturing live human specimens, but it can also be used against most alien races. It is fired from a small launcher.
|-
| 830/x33E ||
|-
| 831/x33F ||
|-
| 832/x340 || The alien research mission is used for collecting basic data on earth and its inhabitants. Small vehicles are predominantly used, with occasional landings in deserted areas. This type of alien activity poses the least threat to XCom, with little concern from governments or the public.
|-
| 833/x341 || The aliens have many uses for earth's fauna. Animals are abducted secretly, and returned with various organs removed. Cattle mutilations are predominantly reported along with UFO sightings. This type of alien activity causes great concern by governments and considerable anxiety amongst the population. This type of activity occurs mainly in farming land. The theory behind the 'alien harvest' suggests that alien races originally 'seeded' the planet with its flora and fauna, and now they have returned to reap the harvest they have sown.
|-
| 834/x342 || This is the most insidious form of alien activity. The abduction by aliens is widely reported, despite the aliens' attempts to erase the experience from their victims' memories. Abductees report being subject to humiliating physical examinations, including impregnation of alien foetuses and bizarre genetic experiments. The purpose behind this activity appears to be linked to genetic mutation and manipulation of the aliens own genetic material. This activity causes great alarm, and occurs in populated areas or cities
|-
| 835/x343 || Earth governments can be infiltrated by alien agents which are human in appearance. This can result in official contact between aliens and governments at the highest level. The climax of this activity is characterised by intense UFO activity in the vicinity of major cities. The aliens will attempt to sign a pact with an earth government by offering knowledge of their superior technology. In return the government will allow the aliens to conduct their activity unhindered. This alien mission represents the worst threat to XCom. If a government agrees to a pact then its funding will cease.
|-
| 836/x344 || Aliens will construct secret underground bases in remote locations. After some initial reconnaissance flights some intense UFO activity will occur as the base is being built. These bases are known to contain experimental labs for human abductees, and supplies for further activity in the region. The presence of alien bases will generate a large amount of reported alien activity without the presence of UFOs. In order to locate a base an XCom craft must patrol an area for a few hours to stand some chance of detection.
|-
| 837/x345 || When the aliens terrorise a city they will deploy some special forces with awesome powers. Civilians will be directly threatened, and governments will be forced to evacuate whole areas. The main purpose behind this activity is to generate sufficient public hysteria so that governments will threaten the XCom project.
|-
| 838/x346 || If XCom interceptors are being particularly successful in shooting down UFOs then the aliens may take some retaliatory action. This could result in a direct attack against an XCom base. However, the aliens have to find an XCom base in order to attack it, and provided UFOs are kept away then there should be little danger of an assault.
|-
| 839/x347 || Once an alien base is constructed then it is resupplied on a regular basis by a special supply vessel. If one of these vessels is detected while landing then it is certain that an alien base is nearby.
|-
| 840/x348 || This tiny craft is primarily used for reconnaissance or research. It normally precedes larger vessels at the start of an alien mission.
|-
| 841/x349 || A medium sized scout vessel that poses little threat to earth forces. Normally appears before larger vessels during missions.
|-
| 842/x34A || The largest alien scout craft is a general purpose vessel that is used in all types of alien mission.
|-
| 843/x34B || The harvester has a trap door in its base and is equipped with lifting gear to haul up cattle or other beasts. Laser cutters are used to extract the desired material and the carcass is dumped on the. ground. There are also storage containers for body parts.
|-
| 844/x34C || This vessel is equipped with an examination room for performing horrific experiments on human subjects. The victim is normally paralysed by telepathic powers, but remains conscious while on the operating table.
|-
| 845/x34D || The terror ship has a containment facility for large alien terror weapons or creatures. It is used to transport these alien terrorists into populated areas.
|-
| 846/x34E || The battleship is the largest and most powerful alien craft. It is normally the primary alien mission craft, equipped with powerful weapons and numerous crew members.
|-
| 847/x34F || The supply vessel is used during the construction of alien bases or for supplying existing bases. It carries alien food containers and reproduction chambers.
|-
| 848/x350 || Dismantle
|-
| 849/x351 || FACILITY IN USE
|-
| 850/x352 || CANNOT DISMANTLE FACILITY!x02All base facilities must be linked to the access lift.
|-
| 851/x353 || Transfer Items to
|-
| 852/x354 || NO ALIEN CONTAINMENT FOR TRANSFER!x02Live aliens need an alien containment facility in order to survive
|-
| 853/x355 || AMOUNT AT DESTINATION
|-
| 854/x356 || Alien dies as there is no alien containment facility
|-
| 855/x357 || NO FREE ACCOMODATION!x02The destination base does not have enough space in the living quarters for the crew assigned to the craft.
|-
| 856/x358 || Items Arriving
|-
| 857/x359 || Pistol
|-
| 858/x35A || Pistol Clip
|-
| 859/x35B || Rifle
|-
| 860/x35C || Rifle Clip
|-
| 861/x35D || Heavy Cannon
|-
| 862/x35E || HC-AP Ammo
|-
| 863/x35F || HC-HE Ammo
|-
| 864/x360 || HC-I Ammo
|-
| 865/x361 || Auto-Cannon
|-
| 866/x362 || AC-AP Ammo
|-
| 867/x363 || AC-HE Ammo
|-
| 868/x364 || AC-I Ammo
|-
| 869/x365 || Rocket Launcher
|-
| 870/x366 || Small Rocket
|-
| 871/x367 || Large Rocket
|-
| 872/x368 || Incendiary Rocket
|-
| 873/x369 || Laser Pistol
|-
| 874/x36A || Laser Rifle
|-
| 875/x36B || Heavy Laser
|-
| 876/x36C || Grenade
|-
| 877/x36D || Smoke Grenade
|-
| 878/x36E || Proximity Grenade
|-
| 879/x36F || High Explosive
|-
| 880/x370 || Motion Scanner
|-
| 881/x371 || Medi-Kit
|-
| 882/x372 || Psi-Amp
|-
| 883/x373 || Stun Rod
|-
| 884/x374 || Heavy Plasma
|-
| 885/x375 || Heavy Plasma Clip
|-
| 886/x376 || Plasma Rifle
|-
| 887/x377 || Plasma Rifle Clip
|-
| 888/x378 || Plasma Pistol
|-
| 889/x379 || Plasma Pistol Clip
|-
| 890/x37A || Blaster Launcher
|-
| 891/x37B || Blaster Bomb
|-
| 892/x37C || Small Launcher
|-
| 893/x37D || Stun Bomb
|-
| 894/x37E || Alien Grenade
|-
| 895/x37F || Elerium-115
|-
| 896/x380 || Mind Probe
|-
| 897/x381 || Sectoid Corpse
|-
| 898/x382 || Snakeman Corpse
|-
| 899/x383 || Ethereal Corpse
|-
| 900/x384 || Muton Corpse
|-
| 901/x385 || Floater Corpse
|-
| 902/x386 || Celatid Corpse
|-
| 903/x387 || Silacoid Corpse
|-
| 904/x388 || Chryssalid Corpse
|-
| 905/x389 || Reaper Corpse
|-
| 906/x38A || Sectopod Corpse
|-
| 907/x38B || Cyberdisc Corpse
|-
| 908/x38C || Not enough cannon rounds to arm HWP
|-
| 909/x38D || Not enough rockets to arm HWP
|-
| 910/x38E || Not enough fusion balls to arm HWP
|-
| 911/x38F || Not enough equipment to fully re-equip squad
|-
| 912/x390 || Mars: Cydonia Landing
|-
| 913/x391 || Your Avenger craft has landed in the region of Cydonia on the surface of Mars. Our information indicates that one of the pyramid constructions contains a green access lift to an underground complex. Once you have assembled all your soldiers in the lift area click on the 'abort mission' icon to continue to the next stage.
|-
| 914/x392 || Mars: The Final Assault
|-
| 915/x393 || The pyramid lift takes your battle weary soldiers deep below the planet's surface. They arrive in the heart of a large complex of tunnels and chambers. The alien brain is hidden somewhere in the labyrinth. It must be destroyed if the earth is to be saved from alien enslavement. Good Luck!
|-
| 916/x394 || in order to use or produce the 
|-
| 917/x395 || The aliens have destroyed the undefended base
|-
| 918/x396 || XCom agents have located an alien base in
|-
| 919/x397 || STANDOFF
|-
| 920/x398 || CAUTIOUS ATTACK
|-
| 921/x399 || STANDARD ATTACK
|-
| 922/x39A || AGGRESSIVE ATTACK
|-
| 923/x39B || DISENGAGING
|-
| 924/x39C || UFO HIT!
|-
| 925/x39D || UFO DESTROYED!
|-
| 926/x39E || UFO CRASH LANDS!
|-
| 927/x39F || Minimise at Standoff Range Only
|-
| 928/x3A0 || UFO RETURN FIRE!
|-
| 929/x3A1 || >>> INTERCEPTOR DAMAGED <<<
|-
| 930/x3A2 || >>> INTERCEPTOR DESTROYED <<<
|-
| 931/x3A3 || UFO OUTRUNNING INTERCEPTOR!
|-
| 932/x3A4 || ALIENS TERRORISE
|-
| 933/x3A5 || Long Range Detection
|-
| 934/x3A6 || STORES
|-
| 935/x3A7 || Difficulty Level
|-
| 936/x3A8 || INTERCEPT
|-
| 937/x3A9 || BASES
|-
| 938/x3AA || GRAPHS
|-
| 939/x3AB || UFOPEDIA
|-
| 940/x3AC || OPTIONS
|-
| 941/x3AD || FUNDING
|-
| 942/x3AE || 5 Secs
|-
| 943/x3AF || 1 Min
|-
| 944/x3B0 || 5 Mins
|-
| 945/x3B1 || 30 Mins
|-
| 946/x3B2 || 1 Hour
|-
| 947/x3B3 || 1 Day
|-
| 948/x3B4 || XCom Performance Roster
|-
| 949/x3B5 || Enter Name
|-
| 950/x3B6 || Performance Rating
|-
| 951/x3B7 || Victory Date
|-
| 952/x3B8 || Electro-flare
|-
| 953/x3B9 || This compact device produces a bright flare light when it is thrown. This will highlight enemy units in the vicinity of the electro-flare during night time missions.
|-
| 954/x3BA || Monthly Costs
|-
| 955/x3BB || Craft Rental
|-
| 956/x3BC || Salaries
|-
| 957/x3BD || Base maintenance
|-
| 958/x3BE || Cost per unit
|-
| 959/x3BF || Quantity
|-
| 960/x3C0 || Total
|-
| 961/x3C1 || day
|-
| 962/x3C2 || days
|-
| 963/x3C3 || In Psionic Training
|-
| 964/x3C4 || This device is a highly explosive missile that has an intelligent guidance system. It is fired from a blaster launcher.
|-
| 965/x3C5 || Please look up the page listed below in your Game Manual, and enter the eight digit code listed at the bottom of the page. EG: Page 13 of Game Manual Code: 3994-9668 Please Enter the Code from Page
|-
| 966/x3C6 || Front Armour
|-
| 967/x3C7 || Left Armour
|-
| 968/x3C8 || Right Armour
|-
| 969/x3C9 || Rear Armour
|-
| 970/x3CA || Under Armour
|-
| 971/x3CB || Rounds
|}
==See Also==
* [[FRENCH.DAT]]
* [[GERMAN.DAT]]
* [[ENGLISH.DAT_(TFTD)]]
* [[GEOSCAPE.EXE]] - Uses the strings in this file.
* [[GEODATA]] - Parent Folder for this file.
* [[GeoScape String Files]] - A summary of the use of these strings.
* [[Tactical String Files]] - The BattleScape equivalents of these files.
* [[Saved Game Files]]
[[Category:Game Files]]

Talk:MAP.DAT

2010-06-28T02:19:21Z

Hatfarm:

Just recalling years ago when I was exploring the map files to see how they were put together, I seem to recall that there were a few extra bytes beyond the end of the map data. Does anyone what these were for or were they just extraneous bytes that never got used? -[[User:NKF|NKF]] 03:53, 19 May 2009 (EDT)

The description of this file makes it really hard to understand. How does it know which MCD file to link to? Where is that information stored? Is that just from GEODATA.DAT? What about when there are multiple MCD's used? [[User:Hatfarm|Hatfarm]] 13:19, 26 June 2010 (EDT)

: No it's not the easiest thing to read. Basically each tile is 4 bytes in length, detailing the two wall, floor and object space (for walls, furniture, etc), and the tiles are stored like a bitmap, similar to the lightmaps, etc. Now, what MCD records to use I'm not entirely sure, so this is just conjecture on my part. All of the map sets that are used for the current map are recorded in Geodata.dat. Since each tile set has an associated MCD file, the game might set up its own tile/MCD lookup table based on the tilesets that it is using for the current map.-[[User:NKF|NKF]] 17:22, 26 June 2010 (EDT)

:: Yes, the actual MCD file used by a map is a composite of the terrain, UFO, and X-COM tilesets. I think the order of tile set indexes is terrain, then UFO, then X-COM. You have problems if there are more than 253 non-blank tiles (0 and 1 are reserved indexes). -- [[User:Zaimoni|Zaimoni]] 19:32, 26 June 2010 (CDT)

BB you've outdown yourself with this redo, really well done. REALLY clear now, thanks for the info. I think I had put it all together after looking at all of the files together, but having it all here makes it a lot easier to refer to. [[User:Hatfarm|Hatfarm]] 22:03, 26 June 2010 (EDT)

: Regarding where the MCD array, it's always made up of BLANKS.MCD first, followed by the MCD files for the terrain, the X-COM dropship, then the UFO. This "collated" table never gets saved to the HDD, as it's always possible to re-assemble it from scratch when loading a save game, based on the terrain and what craft are present.

: Some terrains and UFOs are, themselves, made up of multiple MCD files. For example, the Battleship uses U_Ext02, U_Wall02, U_Pods and U_Bits. An urban map uses Roads, Urbits, Urban and Frniture. All of these "mini-sets" are hardcoded into the Tactical executable and aren't yet documented on this wiki. If you look at the file "TilesetLister.java" in my toolkit you'll see these listed out. The one method in that file, "String[] getList(int[], int)", expects the entire contents of [[GEODATA.DAT]] as the int[], and offset 20 of [[MISSION.DAT|MISDATA/MISSION.DAT]] as the int.

: The details on the MCD stuff really belong on a dedicated MCD page, which I'll make at some point. - [[User:Bomb Bloke|Bomb Bloke]] 22:41, 26 June 2010 (EDT)

:: How do you know which value points to U_Ext02 and which value points to U_Wall02? I mean, is a value of 15 for U_Ext02 and then 62 is U_Wall02? Is it just alphabetical? Also, what is the value of 1 (the reserved bit)? I know I just count up the BLANKS.MCD tiles, then the Terrain tiles, then the x-com ship tiles, then the UFO tiles? That's the order they go in? It still doesn't tell me whether U_Ext or U_Wall02 would be first, but it least gives me something to go on. Thanks. [[User:Hatfarm|Hatfarm]] 10:45, 27 June 2010 (EDT)

: I'm not sure what you're on about with your first two questions. Are you talking about where the indexes for each of these separate MCD files would be located within the collated version? That was my first guess, but then you asked if it was "alphabetical"?! The records are only referred to via numbers... There's no way you can refer to them alphabetically. O_o

: To determine the index for the first record of U_Ext02 within the collated MCD array, you'd need to keep track of exactly how many MCD records you'd added before adding that first U_Ext02 record. Note that you only need to do this for the purpose of assembling a map out of modules (not when loading a pre-assembled [[MAP.DAT]] file), and for keeping offsets 44 and 46 within your MCD records accurate as you build your collated array (which the tactical game engine does every time it starts up).

: I also have no idea what you mean by "the reserved bit".

: Yes, the ordering is as I've written it...

: Say the game wants to know what MCD files it needs to load to represent a Battleship. It refers to a hardcoded string array which is compiled directly into the tactical executable. This array holds multiple lists of filenames (though I think the extensions are inferred, to memory), in the order it expects the game engine to load them. The files are loaded in whatever order then appear within that hard-coded array.

: If it's still not making sense to you after reading that java file I mentioned, run my battlescape editor, then hit the esc button to close the main window. You'll still have a text console remaining on the screen, which'll show you the exact MCD files loaded, in the order it loaded them. - [[User:Bomb Bloke|Bomb Bloke]] 11:44, 27 June 2010 (EDT)

What I meant was I wasn't sure how you would figure out the order the MCD files are collated. Looking at your file gives me the order, but I wasn't sure if there was some sort of specific order. I thought it was possible it would be collated alphabetically. However, it's collated in a way they just happened to code it to be collated. So, if I'm catching this correctly, the values in Map.DAT refer to this collated MCD. [[User:Hatfarm|Hatfarm]] 22:19, 27 June 2010 (EDT)

Talk:MAP.DAT

2010-06-28T02:04:46Z

Hatfarm:

Talk:MAP.DAT

2010-06-27T15:12:39Z

Hatfarm:

Talk:MAP.DAT

2010-06-27T14:48:17Z

Hatfarm:

Talk:MAP.DAT

2010-06-27T14:45:12Z

Hatfarm:

Talk:GEODATA.DAT

2010-06-27T02:15:57Z

Hatfarm:

What does "This is the RMP (or LZ depending on how you look at it) flag. It says if the craft or ground RMP file is used." for offsets 37-83 mean? [[User:Hatfarm|Hatfarm]] 17:53, 26 June 2010 (EDT)

----

Each map module has a [[ROUTES|RMP file]] that goes with it. This lists all the nodes which are used for spawning units on the map, and also are used by patrolling aliens.

When the battle begins, all of these nodes are compiled together into one table (which gets dumped into [[ROUTES.DAT]] if you save the game). It's possible to view all these points in my battlescape editor by tapping the D button a few times. By comparing offsets 69 and 70 of a given alien's [[UNITREF.DAT]] record, it's even possible to get some idea as to where that alien is "going".

Anyway! With all that in mind, craft (both X-COM and alien) have their own route node tables. I guess what Blade is trying to say is that these 29 bytes form a table that indicates whether a craft or a normal "terrain" RMP file should be used for each map module (I know both are never used).

The problem with this is that a 5x5 map (the largest on which craft can appear within UFO:EU) would only require 25 bytes (well, 25 ''bits'' really, but let's assume the devs were lazy). A 6x6 craft map is possible in TFTD and would require 36! But assuming Blade is right, altering these values prior to [[Battlescape Map Generation]] should affect the resulting [[ROUTES.DAT]] file if you save the resulting battle (though they'd have no affect on anything once the battle begins). - [[User:Bomb Bloke|Bomb Bloke]] 20:30, 26 June 2010 (EDT)

: No, 36 bytes. Only way to get 29 bytes is subtract the hexadecimal offsets as decimal. -- [[User:Zaimoni|Zaimoni]], 19:52 June 26 2010

Whoops! - [[User:Bomb Bloke|Bomb Bloke]] 21:49, 26 June 2010 (EDT)

That makes sense, thanks again! [[User:Hatfarm|Hatfarm]] 22:15, 26 June 2010 (EDT)

Talk:MAP.DAT

2010-06-27T02:03:13Z

Hatfarm:

Talk:MAP.DAT

2010-06-27T02:02:55Z

Hatfarm:

Talk:MAP.DAT

2010-06-27T01:59:02Z

Hatfarm:

Talk:GEODATA.DAT

2010-06-26T21:53:25Z

Hatfarm:

What does "This is the RMP (or LZ depending on how you look at it) flag. It says if the craft or ground RMP file is used." for offsets 37-83 mean? [[User:Hatfarm|Hatfarm]] 17:53, 26 June 2010 (EDT)

Talk:GEODATA.DAT

2010-06-26T21:53:08Z

Hatfarm: New page: What does "This is the RMP (or LZ depending on how you look at it) flag. It says if the craft or ground RMP file is used." for offsets 37-83 mean?

What does "This is the RMP (or LZ depending on how you look at it) flag. It says if the craft or ground RMP file is used." for offsets 37-83 mean?

Talk:MAP.DAT

2010-06-26T17:21:32Z

Hatfarm:

Talk:MAP.DAT

2010-06-26T17:19:39Z

Hatfarm:

UNITREF.DAT

2010-06-14T15:02:39Z

Hatfarm: /* Structure */

UNITREF.DAT has a row width of 124 bytes for UFO, 132 for TFTD. Bytes are unsigned, except for Missions and Kills. 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). The same format is used by the files [[UNIREF.DAT]] and [[UNIREF2.DAT]]. These are images of UNITREF.DAT saved in [[Saved_Game_Files#Missdat_Files|MISSDAT]] as of, respectively, the beginning of the last "live" combat game (i.e., not loaded from a savegame) and the last finished combat.

Values are presented according to byte offset (0 to 123) followed by the equivalent hex offset (00 to 7B) in bold. Notes only apply to UFO (as opposed to TFTD) unless otherwise stated. Let us know what else you can find!!

== Structure ==
'''0 / 00:''' 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] & [54] (weapons in hands), [115] (gender) and [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 10: BioDrone
11: Chryssalid 11: Tentaculat
12: Reaper 12: Triscene
13: Sectopod 13: Hallucinoid
14: Cyberdisc 14: Xarquid
15: Male civilian 15: Male civilians
16: Female civilian 16: Female civilians
17: Zombie 17: Zombie
18: Unused (but it made the sound of a tank?) 255: Unused
255: Unused

<blockquote>If the corresponding [[UNITPOS.DAT]] record is unused, then the record is unused.</blockquote>

'''1 / 01:''' 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, unitref[115] and unitref[116] are used to determine the picture.
0: No armor.
1: Personal armour.
2: Power suit.
3: Flying suit.

'''2 / 02:''' Bitflags. NKF: Seems to be consistent with different character models. ''MTR:'' I pulled those out of Hobbes' savegame (see Note 4). There seems to be some differences. Could it be a dynamic byte instead of e.g. static relative to model or whatever?
87654321
NKF: 00100100 36 Floater
10000000 128 Personal armour
10001100 140 Power suit/flying suits
11101000 232 Reaper
''BB:'' 00010000 16 Hovertank/Plasma
00111000 56 Psi unlocked soldier in flying suit
00110000 48 Psi locked soldier in kevlar
01010000 80 Aliens
01010100 84 Cyberdisc
''MTR:'' 00000100 4 Celatid
00100100 36 Chryssalid, Civvie, Ethereal, Floater, Muton, Snakeman,
11011100 220 Sectoid PA Soldier, Tank/Laser
11111000 248 Silacoid

( 1) 1: ?
( 2) 2: ?
( 4) 3: Common to Cyberdiscs
( 8) 4: Common to flying suits
( 16) 5: Common to all units
( 32) 6: Common to X-COM troopers
( 64) 7: Common to all enemies
(128) 8: ?

'''3 / 03:''' Bitflags:
87654321
''NKF:'' 00101110 46 Pers. armor
10000101 133 Floater
10111111 191 PS/FS
11101100 236 Reaper
''BB:'' 00100100 36 Psi locked soldier in kevlar
01010000 80 Hovertank/Plasma
10000001 129 Cyberdisc
10100101 165 Aliens
10110101 181 Psi unlocked soldier in flying suit
''MTR:'' 00000000 0 Chryssalid ''- from Hobbes' savegame''
00000100 4 Celatid
00100000 32 Floater
00110000 48 Muton, Snakeman, Tank/Laser
01110101 117 Sectoid
10100000 160 Ethereal
10110000 176 Civilian, PS (Power Suit) Soldier

( 1) 1: ?
( 2) 2: ?
( 4) 3: Small units
( 8) 4: ?
( 16) 5: Flying X-COM units
( 32) 6: Small units
( 64) 7: ?
(128) 8: ?

'''4 / 04:''' Possible bitflags.
87654321
''NKF:'' 10010001 145 PS/FS
10011011 155 PA Soldier, Floater, Reaper
''BB:'' 01100001 97 Hovertank/Plasma, Psi unlocked soldier in flying suit
01100010 98 Psi locked soldier in kevlar, Cyberdisc, Aliens
''MTR:'' 00100000 32 Silacoid ''- Hobbes' game''
00100100 36 Celatid, PA Soldier, Tank/Laser
00100101 37 Civilian, Muton, Snakeman
01010011 83 Sectoid
01011111 95 Chryssalid, Ethereal, Floater

'''5 / 05:''' Flags 1 for units in play, 0 otherwise. Possible bitflags.

'''6 / 06:''' Possible bitflags.
87654321
''NKF:'' 00000000 0 Reaper
00010000 16 Pers. armor
00100000 32 PS/FS
01010000 80 Floater
''BB:'' 01000000 64 Psi unlocked soldier in flying suit
01010000 80 Hovertank/Plasma
11000100 196 Aliens
11010100 212 Cyberdisc
11101000 232 Psi locked soldier in kevlar
''MTR:'' 00000100 4 Chryssalid '' - Hobbes' game''
01000000 64 Floater
10000100 132 Muton
10000100 132 Snakeman
10010100 148 Ethereal
10011000 152 Tank/Laser
10011100 156 Soldier psi locked in a power suit
10101000 168 Celatid
10101100 172 Sectoid
11011000 216 Civilian
11100100 228 Silacoid

( 1) 1: ?
( 2) 2: ?
( 4) 3: Enemies
( 8) 4: ?
( 16) 5: Large units
( 32) 6: ?
( 64) 7: Always flagged?
(128) 8: ?

'''7 / 07:''' NKF:
87654321
''BB:'' 00000000 0 Hovertank/Plasma
00010000 16 Cyberdisc
00010001 17 Psi unlocked flying suit troopers
00101011 43 Sectoid
00101101 45 Psi locked kevlar troopers
''MTR:'' 01001110 78 Chryssalid, Floater ''- Hobbes' game''
01111011 123 Tank/Laser
01111100 124 PA Soldier
01111101 125 Sectoid
01111110 126 Civilian
11001011 203 Ethereal
11011111 223 Celatid, Silacoid
11111011 251 Muton, Snakeman

( 1) 1: Small units
( 2) 2: Small aliens
( 4) 3: Psi locked kevlar troopers
( 8) 4: ?
( 16) 5: ?
( 32) 6: ?
( 64) 7: ?
(128) 8: ?

'''8 / 08:''' Same for all units? (171) (11000011)
87654321
''MTR:'' 00010011 19 Celatid, Silacoid ''- from Hobbes''
00011110 30 Civilian, Muton, Snakeman, PA Soldier, Tank/Laser
01001110 78 Sectoid
01011001 89 Chryssalid, Ethereal, Floater

''Zaimoni:'' Bit 3 (significance 4) sometimes changes during alien turn/patrol AI.

'''9 / 09:''' Always 0?

'''10 / 0A:''' Unit facing. Does NOT control HWP turret direction; see [024].
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)

'''11 / 0B:''' Movement type. When entering a given map location, each tile is checked to see the TU requirements accordingly. [[TERRAIN|MCD]][39+UnitRef[11]] is the offset used. Note: By default, this is 0 for ALL unit types.
0: Walking
1: Sliding
2: Flying

'''12 / 0C:''' Current TUs

'''13 / 0D:''' Current Health. Health of 0 = Dead. Compare [42], [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)''

'''14 / 0E:''' Current Stun level ''how much falloff of paralysis every turn? What determines it?''

'''15 / 0F:''' Current Energy

'''16 / 10:''' Current Reactions ''NKF: affected by health percentage''

'''17 / 11:''' Strength

'''18 / 12:''' Current Front Armour

'''19 / 13:''' Current Left Armour

'''20 / 14:''' Current Right Armour

'''21 / 15:''' Current Rear Armour

'''22 / 16:''' Current Under Armour

"Base" means the original (total) value (as carried forward from geoscape) - Also see Note 1 re: Base soldier stat values.

'''23 / 17:''' Base Firing accuracy. Current value = this * [013]/[026] (percent health)

'''24 / 18:''' Base Throwing accuracy. Current value = this * [013]/[026] (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 [010].

'''25 / 19:''' Base TUs

'''26 / 1A:''' Base Health

'''27 / 1B:''' Base Energy

'''28 / 1C:''' Base Reactions

'''29 / 1D:''' Base Front Armour

'''30 / 1E:''' Base Left Armour

'''31 / 1F:''' Base Right Armour

'''32 / 20:''' Base Rear Armour

'''33 / 21:''' Base Under Armour

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

'''34 / 22:''' Always 0?

'''35 / 23:''' 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] (energy usage when walking/turning). ''BombBloke: Is this affected by damage?''

'''36 / 24:''' Always 0?

'''37 / 25:''' Psi skill. Psi stats not displayed/usable until this is greater then 0.

'''38 / 26:''' Item to create when unit is unconcious/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.

'''39 / 27:''' "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.

'''40 / 28:''' 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.''

'''41 / 29:''' ''BombBloke:'' Something to do with large units. Changes during gameplay. Have seen values of 2, 3, 5, 6.

'''42 / 2A:''' 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] (Health=0) seems to be the only reliable death indicator for them. Compare [120]. -[[User:MikeTheRed|MikeTheRed]]''

'''43 / 2B:''' 0 or 1? In Hobbes' savegame, civvies and sectoids are 1. All others are 0 (soldiers, aliens, terrorists, tank).

''MTR: If the next byte is "aggression", and civvies and sectoids have a 1 here, could this be "cowardliness"? Likelihood to panic; to do something dumb/random? We've all seen civvies running around in a mad / random panic.''

'''44 / 2C:''' Alien aggression. The higher it is, the less likely an alien will take cover. Maximum of 2. ''MTR: This is true for aliens in Hobbes game, but soldiers have values from 4 to 254. Garbage? Delete this comment if so.''

'''45 / 2D:''' Used to calculate energy loss when walking or turning as: INT( TUs / 2[45] ). See [[Energy#Usage]]; compare [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?''

'''46 / 2E:''' HWP turret image. Only used (and only appears) if unit type [00]=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] and [117].

'''47 / 2F:''' This is a direct copy of offset[48] from the MCD record (see [[TERRAIN]]) of the tile the unit is standing on. A signed byte.

'''48 / 30:''' Values for this byte always equal [52] and are:
2 (5 pixels): Sectoid
3 (7 pixels): Celatid, Chryssalid, Civvie, Ethereal, Floater, Muton, Snake, '''Soldier'''
4 (9 pixels): Cyberdisc, Hovertank, Reaper, Sectopod, Tank
5 (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]).

This cylindrical shape is used in conjunction with height [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] Pxls X Ht (16x24) UR[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.

The unit Float number (Unitref[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.

'''49 / 31:''' [[height|Standing height]].

'''50 / 32:''' [[height|Kneeling height]].

'''51 / 33:''' Floating [[height]]. A unit 'floats' this high above the ground, thus allowing shots to fly underneath. The heighest point of a unit can be found by adding this to the units height stat. Does this have an effect on explosive damage?

'''52 / 34:''' Always the same as [48] in all known saved games. XCOMmies are trying to test its significance, as seen at [[Talk:UNITREF.DAT#Offsets_0x30_.26_0x34|Talk:UNITREF.DAT#Offsets_0x30_&_0x34]] ([48] and [52]).

'''53 / 35''' and '''54 / 36:''' Image index for item in left and right hand, respectively. 255 for none. Indexes into obdata.dat, not obpos.dat.

''NKF:'' If there is no item in the unit's hands, but these 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.

'''55 / 37:''' [[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

'''56 / 38:''' [[Melee Accuracy]] ([[SOLDIER.DAT]] bytes 50 (initial) & 60 (increase) added together)

'''57 / 39:''' [[Psionic Strength]]

'''58 / 3A:''' Current [[Morale]]. Base morale is hardcoded to 100.

'''59 / 3B:''' [[Bravery]] = 110 - (10 * value)

'''60 / 3C:''' 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

'''61 / 3D:''' Unitref[062] 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

'''62 / 3E:''' Visibility via motion scanner. The bigger it is, the bigger the blip. Test this one out for values.

'''63 / 3F:''' Number of [[Fatal Wounds]] to head.

'''64 / 40:''' Number of fatal wounds to torso.

'''65 / 41:''' Number of fatal wounds to right arm.

'''66 / 42:''' Number of fatal wounds to left arm.

'''67 / 43:''' Number of fatal wounds to right leg.

'''68 / 44:''' Number of fatal wounds to left leg.

'''69 / 45''' and '''70 / 46:''' 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

'''71 / 47:''' ''NKF:'' Always 16 for XCom units, 1 for cyberdisc, 0 for others? Perhaps involves mobile lighting - see the [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page.

'''72 / 48:''' Always 0? May be paired with [71].

'''73 / 49:''' 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? :(''

'''74 / 4A:''' ''NKF:'' Could be the unit spotted icon identifier? Could point to visible enemy units?

''MikeTheRed:'' XCOMs always have 0, but Mutons have values of 0-3 (usually 0 or 2, and often fluctuating) in a firing squad situation.

'''75 / 4B:''' Always 0?

'''76-77 / 4C-4D:''' 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?

'''78-79 / 4E-4F:''' 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!

'''80 / 50:''' [[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?

'''81 / 51:''' [[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.)

'''82 / 52:''' [[Melee Accuracy]] experience counter, for number of times stun rod has been used (not stun bombs).

'''83 / 53:''' [[Throwing Accuracy]] experience counter, for number of times unit has thrown any object.

<div id="Psi_Skill_Experience_Counter"></div>'''84 / 54:''' [[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).

'''85 / 55:''' [[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.

'''86-111 / 56-6F:''' Unit's Name. Standard string ended by null byte. The rest can hold garbage.

'''112 / 70:''' 0; sometimes 1 for aliens.

'''113 / 71:''' 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.

UnitRef[1] actually determines the inventory screen used, might be worth playing with that. UnitRef[46] determines the layout.

'''114 / 72:''' If not 0, then unit is on fire, and will burn for this amount of turns.

'''115 / 73:''' Gender: 0 = male, 1 = female.

'''116 / 74:''' Hair/skin colour (for inventory; all other units = 0):
0: Blond caucasian
1: Brunette caucasian
2: Asian
3: Black

'''117 / 75:''' 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], [113], and [118].

'''118 / 76:''' Ammo for [117] turret weapon

'''119 / 77:''' 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

'''120 / 78:''' 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] (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: ??? Seems to flag if the unit has 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?

'''121 / 79:''' 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.

'''122 / 7A:''' Always 0?

'''123 / 7B:''' Always 0?

'''124 / 7C:''' - 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.

== Notes ==
1) The original/base values for soldier stats (offsets 23-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) 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-85) causes stat and rank increases, and decreased health (offset 26 - offset 13) means hospital time. And, of course, death is permanent. Heh.

2) Experience counters (offsets 80-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) 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-82 or 84-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 99 values.
Unknown values (25 in total):
[002] [003] [004] [005] [006] [007] [008] [009] [034]
[036] [041] [043] [052] [069] [070] [071] [072] [074]
[075] [112] [119] [120] [121] [122] [123]

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

Talk:UNITREF.DAT

2010-06-13T05:07:49Z

Hatfarm: /* TFTD's extra bytes */

Anyone who has it - can we get listings of values for various aliens on the Unitref page, for some of the variables found in both Unitref and the Geoscape [[Talk:Overviews_of_Aliens|Alien stats]]? E.g. energy recharge (Unitref[35]), energy loss [45]... like what Danial did for Height. Some of it might go to NKF's redesigned [[Soldier]] page. I am trying to flesh out the Geoscape data so I know what everything is there (and can then extend it across difficulty levels). It has unlabelled fields with values, some of which I know must be these values... but there's no list for me to compare against. Thanks if you can help! ---[[User:MikeTheRed|MikeTheRed]] 19:37, 25 Nov 2005 (PST)

P.S. We probably should clean up this Discussion some time. I will if I find the time to make sure everything has made its way to wherever it should go.

----

== Offsets 0x30 & 0x34 ==

I've chopped out the majority of this page as it is no longer required. I'm keeping the heights chart in case it is required - I've also changed the "H-F" field to "H+F", as this actually makes sense.
[49] [51] "Tall" [48] | [49] [48]
Class Ht. Flt H+F Wide | Ht. Wide Area
--------- --- --- ---- ---- | --- ---- ----
Sectoid 16 0 16 2 | 16 2 32 Area=Ht.*Wide
Celatid 12 6 18 3 | 12 3 36
Hovertank* 12 6 18 4 | 12 4 48
Silacoid 10 0 10 5 | 10 5 50
Snakeman 18 0 18 3 | 18 3 54
Zombie 18 0 18 3 | 18 3 54
Cyberdisc 15 2 17 4 | 15 4 60
Ethereal 20 0 20 3 | 20 3 60 ''All Hover/Tanks in their
Chryssalid 21 0 21 3 | 21 3 63 ''class assumed to be same
Civilian 21 2 23 3 | 21 3 63 ''altho not tested yet
Floater 21 2 23 3 | 21 3 63
Muton 21 0 21 3 | 21 3 63
Tank* 16 0 16 4 | 16 4 64
Soldier 22 0 22 3 | 22 3 66
Reaper 23 0 23 4 | 23 4 92
Sectopod 23 0 23 4 | 23 4 92

Anyway, unitref[48] and unitref[52] remain somewhat of a mystery. Thus far we've assumed them to be the unit's width. Today I tried tinkering with [48] to see of this was correct. As I cranked it up, I found no change in my accuracy, or as to how the Sectoid target blocked line of fire to the tiles behind it.

When it reached the value of 37, however, the alien disappeared! I could not view it regardless of distance. In fact, I could even fire right through the tile it was standing on with no obstruction. The only sign that the alien was still there was the fact that my unit could not stand on the same square.

I lowered [48] a bit and tried viewing the alien from different distances, and found that it appeared in the same way as it usually would, regardless of the value used. It's simply the case that going to 37 or above makes the alien invisible.

I also tweaked [52] a bit, but found that it seemed to have no similar effects, if any at all.

Although I haven't tested this any further as yet, it might be possible to use this effect in reverse - Create an 'invisible' X-Com unit, and use it to observe how aliens act when they think we're not looking.

- [[User:Bomb Bloke|Bomb Bloke]] 00:44, 31 July 2006 (PDT)

----

I have a strong belief that offset 48 is nothing else but the loftemps.dat entry used for collision checking with bullets. A first check is done against the unit height (taking into account floating height, terrain height, kneeling). If the check is OK, the loftemps entry is then used as a final check (effectively treating the unit as a cylinder). I'll try to decypher the code further. If others want to have a look, the code is around here:
.text:004116AE 8B 15 5C 28 4A 00 mov edx, pUnitPos
...
[[User:Seb76|Seb76]] 13:24, 10 April 2008 (PDT)

----

I'm inclined to agree with you, though I'm not much good at reading through executable code. :( I hit on the same idea on my [[User_talk:Bomb_Bloke|talk page]]... I've got some notes in there about how I think the firing system works, if you could find code to back it up I'd be a happy boy.

It's something of a long winded work-in-progress ramble, and I'm sure some parts are confusing and/or dead wrong, but with any luck you can make some sort of sense of it. :) - [[User:Bomb Bloke|Bomb Bloke]] 18:34, 11 April 2008 (PDT)

----

[[Image:Loftemps.png|thumb|right]]I mentionned it earlier but got no real feedback so I'm adding a new section for it ;)
It looks like it is the loftemps entry used for collision detection with bullets. The main page says that setting it to 37 make the shots go right through the guys. If you have a look at the entry, you'll see why... The interesting thing is that the big units do not have special entries (unitref is common for all 4 parts so it would not have been possible to do otherwise) so a shot should be able to go through them (between the 4 parts). However, for the shot to be almost horizontal (or vertical) and traveling at the frontier between tiles (to go between the 4 "collision" circles), the shot should come from far far away so it is not likely to happened. Also depending on how the visibility check is performed, it may explain why alien suddenly disappeared when messing with the value (see discussion upper in this page). I suspect it is done using some kind of raytracing between the center of the 2 tiles (between the current unit and the target); so if the loftemps entry for the target has a "hole" in its center, it may become invisible. [[User:Seb76|Seb76]] 07:00, 1 June 2008 (PDT)

----

I just edited unitref 048 and 052 of all my soldiers to 0 and the aliens never tried to shoot at me. When I edited 048 to 0 for all the Sectoids on a mission, my soldiers couldn't see them anymore (only takes effect the following round if edited in unitef.dat, but surprisingly aliens remain visible to you during their movement phase). Since loftemps 0 is an empty cell, the results make perfect sense. A value of 76 (both 48&52) makes aliens disappear too. I'm not sure what the threshold is for disappearing, but a 3x3 block (loftemps 1) is still enough to be seen. --[[User:Zombie|Zombie]] 15:08, 17 August 2008 (PDT)

----

Am I understanding correctly... for purposes of shots hitting, we're all "barrels" with a specific diameter (i.e. [[LOFTEMPS.DAT]] 2-5), height ([49]), and distance (float) off the ground ([51])? Right or wrong, it sounds like this is finally pretty sown up, excellent work. We could update the page's entries. I wonder why they repeated this value twice (i.e. [48] and [52] always the same)... maybe they once considered the possibility of a unit whose diameter can change from turn to turn? If so, some other heretofore unfathomable UNITREF bit or byte may have been intended to dictate whether they're currently using the diameter at [48] or [52]. -[[User:MikeTheRed|MikeTheRed]] 17:06, 17 August 2008 (PDT)

----

While I've no problem believing [48] is a LOF template reference, I hadn't added it to the main page because I wanted to be sure as to it's relationship with [52].

See, at present, all we know about [52] is that it's the same as [48]. We haven't seen any effects from changing it.

What I ''suspect'' is that one offset might be used for shots traveling along an angle parallel to the target, and one offset might be used for shots traveling perpendicular. This would basically allow units to be effectively oval shaped (or it would, if [48] and [52] weren't the same for all units).

Just one of those things that I never got around to finishing the testing on. Would be dead easy to check, though.

There's still a little more to be researched before the entirety of the firing system is understood (see my talk page for a rambling explanation as to what IS known), but that's pretty much the basics of it.

- [[User:Bomb Bloke|Bomb Bloke]] 19:51, 17 August 2008 (PDT)

----

BB and others, see my edits for [48]. Does it make sense? In particular, I estimated pixel width from that little LOFTEMPS .png by magnifying it a ton. Any and all comments or edits welcomed. It's interesting that the silacoid has the highest width, but a low cross-section - did anyone see the Star Trek TOS show with the very short, wide silicon aliens? -[[User:MikeTheRed|MikeTheRed]] 22:53, 23 August 2008 (PDT)

----

Yes, you got the LOF widths correct. Though as you mentioned, they're only accurate assuming you're firing head on at your targets (as the templates aren't perfect circles, their width varies from other angles).

I threw in the kneeling soldier stats and made a note concerning large units.

- [[User:Bomb Bloke|Bomb Bloke]] 22:21, 24 August 2008 (PDT)

== Offset 0x3C ==

I have a gut feeling it is related to the panic/berserk status of the unit... Any volunteer for testing? [[User:Seb76|Seb76]] 10:36, 22 March 2008 (PDT)

----

Made a save where all soldiers had no morale. Ended turn, most of them panicked etc. Saved the game but that offset still came up as 0. Might only be flagged at runtime.

- [[User:Bomb Bloke|Bomb Bloke]] 18:01, 26 May 2008 (PDT)

----

I checked and indeed the game sets and clears it in the same turn so it is always 0 in a savegame and hence there is no 'black box' way of confirming it. I can provide disassembly screenshots if you want proofs however ;) [[User:Seb76|Seb76]] 05:45, 28 May 2008 (PDT)
:Actually after some thinking, it _might_ be possible... If you set the value to 3 for all entries, everyone may go berserk, with 2 they should run in fear and 1, they'll just crap their pants in place... [[User:Seb76|Seb76]] 07:09, 28 May 2008 (PDT)

----

I tried it, and indeed my units did exactly that (at the start of their next turn - not that of the aliens).

- [[User:Bomb Bloke|Bomb Bloke]] 21:08, 28 May 2008 (PDT)

== Offset 0x71 ==
Hmm, the code checks this offset before applying stun damage... It looks more like an 'immune to stun damage' flag then. Strange... [[User:Seb76|Seb76]] 13:48, 7 April 2008 (PDT)

----

By memory, the only things that use this are X-Com HWPs (which shouldn't have stun applied). It does toggle inventory access as described though it wouldn't surprise me if it also toggled stun damage.

- [[User:Bomb Bloke|Bomb Bloke]] 05:46, 8 April 2008 (PDT)

:OK, I located the check and it is exactly what happens. BTW, if you want to try something, try to patch this with nops (0x90):
.text:00412A20 A8 40 test al, 40h
.text:00412A22 0F 85 00 02 00 00 jnz exit ; default
:It should enable inventory screen for memory controlled units (could not test since I have no save files with psy units...) [[User:Seb76|Seb76]] 11:37, 8 April 2008 (PDT)

:: So, to be clear, is this the location of the inventory screen check for mind controlled alien units? And here you are disabling the check by overwriting it with NOPS? Is there a nearby section of code that does the same check for tanks? I would like to be able to override this tank inventory check in order to play with [[User:Spike#Tank mods|Tank mods]]. It looks like NOPing the check logic is the right way to do it, since if instead I toggled the 0x71 flag for the tanks, they would than also become vulnerable to Stun? Though I also I think read somewhere that if you get to the inventory screen of a tank, the game crashes. It doesn't crash if you get to the inventory screen of an Alien large unit via the Alien Inventory or Alien Pets hacks (not sure which) in your UFOExtender. I was able to arm Reapers with dual Heavy Plasma or dual Blaster Launchers. (Unpleasant. They have 0% FA so they have to run up to you and spray with the Heavy Plasma. Not a problem with the Blaster Launcher.) [[User:Spike|Spike]] 13:59, 20 August 2009 (EDT)

== Offset 0xB ==
The value is used together as an offset to [[TERRAIN|MCDData]] offset 39 (describing TUs required to cross a tile walking/flying/sliding) so it most likely represent the way the unit moves. Still needs testing. [[User:Seb76|Seb76]] 13:27, 23 May 2008 (PDT)

----

I took a look at it for Snakemen and Silacoids, it's still 0 (same as it is for everything else).

But that doesn't mean it remains at 0 when the game's running. Do you mean to say that the value here + 39 = the offset in the MCD array that says how many TUs were required to move past any given obstacles in the current map location?

(That is, you'd expect to see a 2 there for sliding units?)

- [[User:Bomb Bloke|Bomb Bloke]] 05:14, 25 May 2008 (PDT)

----

Yep, exactly like that. Also it checks if the value is 0xff and prevent movement in that case. I'll try a live check with a debugger when I encounter snakemen. Maybe it's a part of code that was implemented but not put into usage. [[User:Seb76|Seb76]] 05:20, 25 May 2008 (PDT)
:Did the check and the value is indeed zero even for snakemen... BTW, is the movement type really working? I mean has anybody ever checked that e.g. snakemen really use different TU amount for tiles where TU usage is not the same between crawling and walking? [[User:Seb76|Seb76]] 06:43, 25 May 2008 (PDT)

----

Truth be told I don't remember reading of anyone doing the tests, so I had a go myself.

I tried first with the Avenger ramp, stuck it up in the air and had soldiers walk/fly onto it. Made no effect to their TU usage.

Next I rigged a Snakeman mission in the arctic, stuck one of them in the middle of a pond. It wouldn't move on it's own, and I couldn't move it under mind control.

So then I set 0xB to 2 just for that unit, and hey presto! Suddenly it was able to move freely, either under my control or otherwise. That's certainly the movement type flag... It's just not set in practise.

Still, now I'm wondering if 2 really was for sliders... It doesn't make sense that "fliers" (which I guess was supposed to include the likes of CyberDiscs, which "hover" even when on the ground) wouldn't be able to cross water, yet Snakemen could. Perhaps it should be the other way around?

- [[User:Bomb Bloke|Bomb Bloke]] 19:22, 25 May 2008 (PDT)

----

Note that there are some tiles that have 0 MP cost for sliders. - [[User:Zaimoni|Zaimoni]] 22:28, 25 May 2008 (CDT)

: Yeah, I guess that puts the clincher on it. Only fliers would really be totally unhindered by ground rubble. I've tweaked the MCD details page accordingly. - [[User:Bomb Bloke|Bomb Bloke]] 05:25, 26 May 2008 (PDT)

----

Hehe, I knew it couldn't be anything else but movement type. Yet another entry for known bugs ;) I'll check if it's possible to reenable the feature. It'll depends if it's a bug or if it was voluntarily removed I guess... [[User:Seb76|Seb76]] 04:37, 26 May 2008 (PDT)
: Did a quick check and can confirm what is said in [[GEOSCAPE.EXE#Alien_Stats|Alien Stats]] page. Offset 0xB is filled with the 3rd "unknown" value of alien stats. It is set to 0 for all entries. Could not find any other place where it could possibly be set to another value. [[User:Seb76|Seb76]] 05:17, 26 May 2008 (PDT)

----

So it's just a matter of tweaking that for all relevant units, then. However, I reckon it was left unused intentionally - I doubt the map files really contain enough variety to make it worth including.

- [[User:Bomb Bloke|Bomb Bloke]] 05:25, 26 May 2008 (PDT)

----

Since TFTD was done later with the same engine, perhaps it makes use of this? However, given that a different team made it ([http://www.lasersquadnemesis.com/AboutUs.htm Terror from the Deep was developed by Microprose using code licensed by Mythos]), developers may not have known the feature was available... [[User:Seb76|Seb76]] 07:25, 28 May 2008 (PDT)

----

I took a quick check, and sure enough found a Hallucinoid (the big flying squid thing) set to 2.

- [[User:Bomb Bloke|Bomb Bloke]] 21:31, 28 May 2008 (PDT)

== Offset 0x47 ==

The only use I could find is that of updating [[SOURCEMP.DAT|mobile light sources]] (or something like that) when the unit dies/is rendered unconscious. Could not find anything else about this flag. [[User:Seb76|Seb76]] 05:24, 29 May 2008 (PDT)

:Good work there. As a general statement, can I say - I've been waiting for somebody to disassemble XCOM :) -[[User:MikeTheRed|MikeTheRed]] 21:18, 30 May 2008 (PDT)

I sat down to do some tests with this, but didn't bother too read to closely... I was selecting/moving units around when I probably shoulda been shooting at them.

Oh well. For the record:

Moving a unit causes a light check to be done on all your units. You may not see this light if one of your units is standing in a fog-of-war covered zone (say you just mind controlled an alien and haven't selected it yet).

Selecting a unit does a fog-of-war check concerning what it can see, but does not do a light check.

Whatever this offset is has no effect on the light produced by your units, or the aliens units. Your active guys ALWAYS fully illuminate their tile (even if this is 0) and the aliens provide no illumination at all. Will have to do some tests concerning what happens when you shoot them, but it seems odd: If a unit is dead I'd expect a full light check to be done, since the unit isn't "active" it won't produce light, so I don't see how this offset is helpful there... You can't just remove the light values for this one unit because you might interfere with other nearby light sources, so you really have to calculate them all from scratch.

But likewise it seems [[TERRAIN|MCD[58/3A]]] is similar; a street lamp is set to 1, a normal lamp to 10, but they both provide maximum illumination.

Perhaps the programmers changed their mind about the lighting system at some point? Dunno.

- [[User:Bomb Bloke|Bomb Bloke]] 07:03, 20 June 2008 (PDT)

:Some of your note reminds me of what I wrote at [[Night_Missions#Personal_lighting]] ... does that help any? (probably not) -[[User:MikeTheRed|MikeTheRed]] 16:01, 20 June 2008 (PDT)

== On Fire Flag or Timer ? ==

Do we have any idea where a flag is set to show the unit is on fire? This is persistent between saved games so it must be stored in a file somewhere. Possibly UNITPOS.DAT? It could be a flag, but more likely is either a countdown timer for turns remaining on fire, (values 1-5?), or a "what turn do I stop being on fire" timer value (like a grenade timer).

I have uploaded a saved game file with a burning Aquatoid if anyone wants to take a look. I just don't have the right diff tools. Maybe with the Hex Workshop template... [[User:Spike|Spike]] 19:05, 10 March 2009 (CDT)

:Offset 114 in Unitref holds that data. --[[User:Zombie|Zombie]] 19:15, 10 March 2009 (CDT)

:: Sorry I did not read the article carefully enough. It's in there. [[User:Spike|Spike]] 19:16, 10 March 2009 (CDT)

114 / 72: If not 0, then unit is on fire, and will burn for this amount of turns.

== Floating Civilians ==

Civilians float 2 units off the ground, like Floaters and Cyberdisks. Soldiers don't. Should we consider this to be a bug? [[User:Spike|Spike]] 13:41, 20 August 2009 (EDT)

:Probably. I really doubt it's an intentional feature. --[[User:Zombie|Zombie]] 23:09, 20 August 2009 (EDT)

== Remembering morale vs health and pain killers ==

The game remembers whether a health loss has or has not been used to regain morale via pain killers. Presumably this is stored somewhere in UNITREF.DAT? [[User:Spike|Spike]] 10:30, 5 September 2009 (EDT)

== TFTD ==

It appears the name string starts at the same point in TFTD save points, which leads me to believe that the extra bytes are probably just appended at the end of the file, without much changing in the first 124 bytes per entry, anyone know what these extra 8 bytes might represent? - [[User:Hatfarm|Hatfarm]]

----

They are indeed appended. My battlescape editor deals with TFTD's UnitRef by just adjusting for the larger record size, and then ignoring the extra bytes completely - didn't need to do anything else to make it all match up. I've yet to actually look at some sample values in order to work out what they might be for.

Incidently, you can insert signatures into your postings using four tildes (<nowiki>~~~~</nowiki>). - [[User:Bomb Bloke|Bomb Bloke]] 21:48, 20 January 2010 (EST)

== TFTD's extra bytes ==

It appears that byte 126 is a bit flag array of some sort as I have mostly seen values of 1 and 0 for it, but others have appeared. I saved a single mission at several different times and each one had 0 or 1, but a terror mission save had some different values for this, Like 0x20 and 0x4F. I tried adjusting it and checking the saved game, but nothing seemed to change...

Byte 124 I've seen values of 0,4,6,7,0x0A and 0x0E. No idea what these mean, and changing them did not do anything for me.

They appear to only be for Soldiers as well, none of the aliens in any of my saved games have values for these.
[[User:Hatfarm|Hatfarm]] 15:16, 5 June 2010 (EDT)

----

124 may have something to do with the air-bubbles that trickle up from soldiers when they're underwater - an animation counter, similar to offset 8 of [[SMOKREF.DAT]], but with a higher range (0-15, probably). Granted, there's no real reason to keep track of bubbles when saving the game, but they have to be tracked somewhere at run-time, and this seems to be the logical place (the save files are just raw dumps of RAM anyway).

In theory, if you set this to the same value for all soldiers (say 5), on loading the game, they'd all have identical air bubbles over their heads. - [[User:Bomb Bloke|Bomb Bloke]] 22:26, 5 June 2010 (EDT)

----

You're right, I set them all to 5 and they were all in the same place bubble wise,. However, they don't all "rebubble" at the same time. Good call BB. [[User:Hatfarm|Hatfarm]] 02:16, 12 June 2010 (EDT)

----

I'd guess they "rebubble" randomly, though it may be a rather more elaborate setup - bubbles might appear more often for soldiers with lower stamina levels, maybe, to indicate they're out of breath.

Unfortunately, I can't think of anything else TFTD adds that would warrant using those extra bytes at the end of the file. - [[User:Bomb Bloke|Bomb Bloke]] 05:20, 12 June 2010 (EDT)

----

I'm guessing it's a 2 byte count at least, which would account for the 124 and 125 bytes. If I think of anything for the others, I'll let you know. [[User:Hatfarm|Hatfarm]] 01:07, 13 June 2010 (EDT)

Talk:UNITREF.DAT

2010-06-12T06:16:50Z

Hatfarm: /* TFTD's extra bytes */

Anyone who has it - can we get listings of values for various aliens on the Unitref page, for some of the variables found in both Unitref and the Geoscape [[Talk:Overviews_of_Aliens|Alien stats]]? E.g. energy recharge (Unitref[35]), energy loss [45]... like what Danial did for Height. Some of it might go to NKF's redesigned [[Soldier]] page. I am trying to flesh out the Geoscape data so I know what everything is there (and can then extend it across difficulty levels). It has unlabelled fields with values, some of which I know must be these values... but there's no list for me to compare against. Thanks if you can help! ---[[User:MikeTheRed|MikeTheRed]] 19:37, 25 Nov 2005 (PST)

P.S. We probably should clean up this Discussion some time. I will if I find the time to make sure everything has made its way to wherever it should go.

----

== Offsets 0x30 & 0x34 ==

I've chopped out the majority of this page as it is no longer required. I'm keeping the heights chart in case it is required - I've also changed the "H-F" field to "H+F", as this actually makes sense.
[49] [51] "Tall" [48] | [49] [48]
Class Ht. Flt H+F Wide | Ht. Wide Area
--------- --- --- ---- ---- | --- ---- ----
Sectoid 16 0 16 2 | 16 2 32 Area=Ht.*Wide
Celatid 12 6 18 3 | 12 3 36
Hovertank* 12 6 18 4 | 12 4 48
Silacoid 10 0 10 5 | 10 5 50
Snakeman 18 0 18 3 | 18 3 54
Zombie 18 0 18 3 | 18 3 54
Cyberdisc 15 2 17 4 | 15 4 60
Ethereal 20 0 20 3 | 20 3 60 ''All Hover/Tanks in their
Chryssalid 21 0 21 3 | 21 3 63 ''class assumed to be same
Civilian 21 2 23 3 | 21 3 63 ''altho not tested yet
Floater 21 2 23 3 | 21 3 63
Muton 21 0 21 3 | 21 3 63
Tank* 16 0 16 4 | 16 4 64
Soldier 22 0 22 3 | 22 3 66
Reaper 23 0 23 4 | 23 4 92
Sectopod 23 0 23 4 | 23 4 92

Anyway, unitref[48] and unitref[52] remain somewhat of a mystery. Thus far we've assumed them to be the unit's width. Today I tried tinkering with [48] to see of this was correct. As I cranked it up, I found no change in my accuracy, or as to how the Sectoid target blocked line of fire to the tiles behind it.

When it reached the value of 37, however, the alien disappeared! I could not view it regardless of distance. In fact, I could even fire right through the tile it was standing on with no obstruction. The only sign that the alien was still there was the fact that my unit could not stand on the same square.

I lowered [48] a bit and tried viewing the alien from different distances, and found that it appeared in the same way as it usually would, regardless of the value used. It's simply the case that going to 37 or above makes the alien invisible.

I also tweaked [52] a bit, but found that it seemed to have no similar effects, if any at all.

Although I haven't tested this any further as yet, it might be possible to use this effect in reverse - Create an 'invisible' X-Com unit, and use it to observe how aliens act when they think we're not looking.

- [[User:Bomb Bloke|Bomb Bloke]] 00:44, 31 July 2006 (PDT)

----

I have a strong belief that offset 48 is nothing else but the loftemps.dat entry used for collision checking with bullets. A first check is done against the unit height (taking into account floating height, terrain height, kneeling). If the check is OK, the loftemps entry is then used as a final check (effectively treating the unit as a cylinder). I'll try to decypher the code further. If others want to have a look, the code is around here:
.text:004116AE 8B 15 5C 28 4A 00 mov edx, pUnitPos
...
[[User:Seb76|Seb76]] 13:24, 10 April 2008 (PDT)

----

I'm inclined to agree with you, though I'm not much good at reading through executable code. :( I hit on the same idea on my [[User_talk:Bomb_Bloke|talk page]]... I've got some notes in there about how I think the firing system works, if you could find code to back it up I'd be a happy boy.

It's something of a long winded work-in-progress ramble, and I'm sure some parts are confusing and/or dead wrong, but with any luck you can make some sort of sense of it. :) - [[User:Bomb Bloke|Bomb Bloke]] 18:34, 11 April 2008 (PDT)

----

[[Image:Loftemps.png|thumb|right]]I mentionned it earlier but got no real feedback so I'm adding a new section for it ;)
It looks like it is the loftemps entry used for collision detection with bullets. The main page says that setting it to 37 make the shots go right through the guys. If you have a look at the entry, you'll see why... The interesting thing is that the big units do not have special entries (unitref is common for all 4 parts so it would not have been possible to do otherwise) so a shot should be able to go through them (between the 4 parts). However, for the shot to be almost horizontal (or vertical) and traveling at the frontier between tiles (to go between the 4 "collision" circles), the shot should come from far far away so it is not likely to happened. Also depending on how the visibility check is performed, it may explain why alien suddenly disappeared when messing with the value (see discussion upper in this page). I suspect it is done using some kind of raytracing between the center of the 2 tiles (between the current unit and the target); so if the loftemps entry for the target has a "hole" in its center, it may become invisible. [[User:Seb76|Seb76]] 07:00, 1 June 2008 (PDT)

----

I just edited unitref 048 and 052 of all my soldiers to 0 and the aliens never tried to shoot at me. When I edited 048 to 0 for all the Sectoids on a mission, my soldiers couldn't see them anymore (only takes effect the following round if edited in unitef.dat, but surprisingly aliens remain visible to you during their movement phase). Since loftemps 0 is an empty cell, the results make perfect sense. A value of 76 (both 48&52) makes aliens disappear too. I'm not sure what the threshold is for disappearing, but a 3x3 block (loftemps 1) is still enough to be seen. --[[User:Zombie|Zombie]] 15:08, 17 August 2008 (PDT)

----

Am I understanding correctly... for purposes of shots hitting, we're all "barrels" with a specific diameter (i.e. [[LOFTEMPS.DAT]] 2-5), height ([49]), and distance (float) off the ground ([51])? Right or wrong, it sounds like this is finally pretty sown up, excellent work. We could update the page's entries. I wonder why they repeated this value twice (i.e. [48] and [52] always the same)... maybe they once considered the possibility of a unit whose diameter can change from turn to turn? If so, some other heretofore unfathomable UNITREF bit or byte may have been intended to dictate whether they're currently using the diameter at [48] or [52]. -[[User:MikeTheRed|MikeTheRed]] 17:06, 17 August 2008 (PDT)

----

While I've no problem believing [48] is a LOF template reference, I hadn't added it to the main page because I wanted to be sure as to it's relationship with [52].

See, at present, all we know about [52] is that it's the same as [48]. We haven't seen any effects from changing it.

What I ''suspect'' is that one offset might be used for shots traveling along an angle parallel to the target, and one offset might be used for shots traveling perpendicular. This would basically allow units to be effectively oval shaped (or it would, if [48] and [52] weren't the same for all units).

Just one of those things that I never got around to finishing the testing on. Would be dead easy to check, though.

There's still a little more to be researched before the entirety of the firing system is understood (see my talk page for a rambling explanation as to what IS known), but that's pretty much the basics of it.

- [[User:Bomb Bloke|Bomb Bloke]] 19:51, 17 August 2008 (PDT)

----

BB and others, see my edits for [48]. Does it make sense? In particular, I estimated pixel width from that little LOFTEMPS .png by magnifying it a ton. Any and all comments or edits welcomed. It's interesting that the silacoid has the highest width, but a low cross-section - did anyone see the Star Trek TOS show with the very short, wide silicon aliens? -[[User:MikeTheRed|MikeTheRed]] 22:53, 23 August 2008 (PDT)

----

Yes, you got the LOF widths correct. Though as you mentioned, they're only accurate assuming you're firing head on at your targets (as the templates aren't perfect circles, their width varies from other angles).

I threw in the kneeling soldier stats and made a note concerning large units.

- [[User:Bomb Bloke|Bomb Bloke]] 22:21, 24 August 2008 (PDT)

== Offset 0x3C ==

I have a gut feeling it is related to the panic/berserk status of the unit... Any volunteer for testing? [[User:Seb76|Seb76]] 10:36, 22 March 2008 (PDT)

----

Made a save where all soldiers had no morale. Ended turn, most of them panicked etc. Saved the game but that offset still came up as 0. Might only be flagged at runtime.

- [[User:Bomb Bloke|Bomb Bloke]] 18:01, 26 May 2008 (PDT)

----

I checked and indeed the game sets and clears it in the same turn so it is always 0 in a savegame and hence there is no 'black box' way of confirming it. I can provide disassembly screenshots if you want proofs however ;) [[User:Seb76|Seb76]] 05:45, 28 May 2008 (PDT)
:Actually after some thinking, it _might_ be possible... If you set the value to 3 for all entries, everyone may go berserk, with 2 they should run in fear and 1, they'll just crap their pants in place... [[User:Seb76|Seb76]] 07:09, 28 May 2008 (PDT)

----

I tried it, and indeed my units did exactly that (at the start of their next turn - not that of the aliens).

- [[User:Bomb Bloke|Bomb Bloke]] 21:08, 28 May 2008 (PDT)

== Offset 0x71 ==
Hmm, the code checks this offset before applying stun damage... It looks more like an 'immune to stun damage' flag then. Strange... [[User:Seb76|Seb76]] 13:48, 7 April 2008 (PDT)

----

By memory, the only things that use this are X-Com HWPs (which shouldn't have stun applied). It does toggle inventory access as described though it wouldn't surprise me if it also toggled stun damage.

- [[User:Bomb Bloke|Bomb Bloke]] 05:46, 8 April 2008 (PDT)

:OK, I located the check and it is exactly what happens. BTW, if you want to try something, try to patch this with nops (0x90):
.text:00412A20 A8 40 test al, 40h
.text:00412A22 0F 85 00 02 00 00 jnz exit ; default
:It should enable inventory screen for memory controlled units (could not test since I have no save files with psy units...) [[User:Seb76|Seb76]] 11:37, 8 April 2008 (PDT)

:: So, to be clear, is this the location of the inventory screen check for mind controlled alien units? And here you are disabling the check by overwriting it with NOPS? Is there a nearby section of code that does the same check for tanks? I would like to be able to override this tank inventory check in order to play with [[User:Spike#Tank mods|Tank mods]]. It looks like NOPing the check logic is the right way to do it, since if instead I toggled the 0x71 flag for the tanks, they would than also become vulnerable to Stun? Though I also I think read somewhere that if you get to the inventory screen of a tank, the game crashes. It doesn't crash if you get to the inventory screen of an Alien large unit via the Alien Inventory or Alien Pets hacks (not sure which) in your UFOExtender. I was able to arm Reapers with dual Heavy Plasma or dual Blaster Launchers. (Unpleasant. They have 0% FA so they have to run up to you and spray with the Heavy Plasma. Not a problem with the Blaster Launcher.) [[User:Spike|Spike]] 13:59, 20 August 2009 (EDT)

== Offset 0xB ==
The value is used together as an offset to [[TERRAIN|MCDData]] offset 39 (describing TUs required to cross a tile walking/flying/sliding) so it most likely represent the way the unit moves. Still needs testing. [[User:Seb76|Seb76]] 13:27, 23 May 2008 (PDT)

----

I took a look at it for Snakemen and Silacoids, it's still 0 (same as it is for everything else).

But that doesn't mean it remains at 0 when the game's running. Do you mean to say that the value here + 39 = the offset in the MCD array that says how many TUs were required to move past any given obstacles in the current map location?

(That is, you'd expect to see a 2 there for sliding units?)

- [[User:Bomb Bloke|Bomb Bloke]] 05:14, 25 May 2008 (PDT)

----

Yep, exactly like that. Also it checks if the value is 0xff and prevent movement in that case. I'll try a live check with a debugger when I encounter snakemen. Maybe it's a part of code that was implemented but not put into usage. [[User:Seb76|Seb76]] 05:20, 25 May 2008 (PDT)
:Did the check and the value is indeed zero even for snakemen... BTW, is the movement type really working? I mean has anybody ever checked that e.g. snakemen really use different TU amount for tiles where TU usage is not the same between crawling and walking? [[User:Seb76|Seb76]] 06:43, 25 May 2008 (PDT)

----

Truth be told I don't remember reading of anyone doing the tests, so I had a go myself.

I tried first with the Avenger ramp, stuck it up in the air and had soldiers walk/fly onto it. Made no effect to their TU usage.

Next I rigged a Snakeman mission in the arctic, stuck one of them in the middle of a pond. It wouldn't move on it's own, and I couldn't move it under mind control.

So then I set 0xB to 2 just for that unit, and hey presto! Suddenly it was able to move freely, either under my control or otherwise. That's certainly the movement type flag... It's just not set in practise.

Still, now I'm wondering if 2 really was for sliders... It doesn't make sense that "fliers" (which I guess was supposed to include the likes of CyberDiscs, which "hover" even when on the ground) wouldn't be able to cross water, yet Snakemen could. Perhaps it should be the other way around?

- [[User:Bomb Bloke|Bomb Bloke]] 19:22, 25 May 2008 (PDT)

----

Note that there are some tiles that have 0 MP cost for sliders. - [[User:Zaimoni|Zaimoni]] 22:28, 25 May 2008 (CDT)

: Yeah, I guess that puts the clincher on it. Only fliers would really be totally unhindered by ground rubble. I've tweaked the MCD details page accordingly. - [[User:Bomb Bloke|Bomb Bloke]] 05:25, 26 May 2008 (PDT)

----

Hehe, I knew it couldn't be anything else but movement type. Yet another entry for known bugs ;) I'll check if it's possible to reenable the feature. It'll depends if it's a bug or if it was voluntarily removed I guess... [[User:Seb76|Seb76]] 04:37, 26 May 2008 (PDT)
: Did a quick check and can confirm what is said in [[GEOSCAPE.EXE#Alien_Stats|Alien Stats]] page. Offset 0xB is filled with the 3rd "unknown" value of alien stats. It is set to 0 for all entries. Could not find any other place where it could possibly be set to another value. [[User:Seb76|Seb76]] 05:17, 26 May 2008 (PDT)

----

So it's just a matter of tweaking that for all relevant units, then. However, I reckon it was left unused intentionally - I doubt the map files really contain enough variety to make it worth including.

- [[User:Bomb Bloke|Bomb Bloke]] 05:25, 26 May 2008 (PDT)

----

Since TFTD was done later with the same engine, perhaps it makes use of this? However, given that a different team made it ([http://www.lasersquadnemesis.com/AboutUs.htm Terror from the Deep was developed by Microprose using code licensed by Mythos]), developers may not have known the feature was available... [[User:Seb76|Seb76]] 07:25, 28 May 2008 (PDT)

----

I took a quick check, and sure enough found a Hallucinoid (the big flying squid thing) set to 2.

- [[User:Bomb Bloke|Bomb Bloke]] 21:31, 28 May 2008 (PDT)

== Offset 0x47 ==

The only use I could find is that of updating [[SOURCEMP.DAT|mobile light sources]] (or something like that) when the unit dies/is rendered unconscious. Could not find anything else about this flag. [[User:Seb76|Seb76]] 05:24, 29 May 2008 (PDT)

:Good work there. As a general statement, can I say - I've been waiting for somebody to disassemble XCOM :) -[[User:MikeTheRed|MikeTheRed]] 21:18, 30 May 2008 (PDT)

I sat down to do some tests with this, but didn't bother too read to closely... I was selecting/moving units around when I probably shoulda been shooting at them.

Oh well. For the record:

Moving a unit causes a light check to be done on all your units. You may not see this light if one of your units is standing in a fog-of-war covered zone (say you just mind controlled an alien and haven't selected it yet).

Selecting a unit does a fog-of-war check concerning what it can see, but does not do a light check.

Whatever this offset is has no effect on the light produced by your units, or the aliens units. Your active guys ALWAYS fully illuminate their tile (even if this is 0) and the aliens provide no illumination at all. Will have to do some tests concerning what happens when you shoot them, but it seems odd: If a unit is dead I'd expect a full light check to be done, since the unit isn't "active" it won't produce light, so I don't see how this offset is helpful there... You can't just remove the light values for this one unit because you might interfere with other nearby light sources, so you really have to calculate them all from scratch.

But likewise it seems [[TERRAIN|MCD[58/3A]]] is similar; a street lamp is set to 1, a normal lamp to 10, but they both provide maximum illumination.

Perhaps the programmers changed their mind about the lighting system at some point? Dunno.

- [[User:Bomb Bloke|Bomb Bloke]] 07:03, 20 June 2008 (PDT)

:Some of your note reminds me of what I wrote at [[Night_Missions#Personal_lighting]] ... does that help any? (probably not) -[[User:MikeTheRed|MikeTheRed]] 16:01, 20 June 2008 (PDT)

== On Fire Flag or Timer ? ==

Do we have any idea where a flag is set to show the unit is on fire? This is persistent between saved games so it must be stored in a file somewhere. Possibly UNITPOS.DAT? It could be a flag, but more likely is either a countdown timer for turns remaining on fire, (values 1-5?), or a "what turn do I stop being on fire" timer value (like a grenade timer).

I have uploaded a saved game file with a burning Aquatoid if anyone wants to take a look. I just don't have the right diff tools. Maybe with the Hex Workshop template... [[User:Spike|Spike]] 19:05, 10 March 2009 (CDT)

:Offset 114 in Unitref holds that data. --[[User:Zombie|Zombie]] 19:15, 10 March 2009 (CDT)

:: Sorry I did not read the article carefully enough. It's in there. [[User:Spike|Spike]] 19:16, 10 March 2009 (CDT)

114 / 72: If not 0, then unit is on fire, and will burn for this amount of turns.

== Floating Civilians ==

Civilians float 2 units off the ground, like Floaters and Cyberdisks. Soldiers don't. Should we consider this to be a bug? [[User:Spike|Spike]] 13:41, 20 August 2009 (EDT)

:Probably. I really doubt it's an intentional feature. --[[User:Zombie|Zombie]] 23:09, 20 August 2009 (EDT)

== Remembering morale vs health and pain killers ==

The game remembers whether a health loss has or has not been used to regain morale via pain killers. Presumably this is stored somewhere in UNITREF.DAT? [[User:Spike|Spike]] 10:30, 5 September 2009 (EDT)

== TFTD ==

It appears the name string starts at the same point in TFTD save points, which leads me to believe that the extra bytes are probably just appended at the end of the file, without much changing in the first 124 bytes per entry, anyone know what these extra 8 bytes might represent? - [[User:Hatfarm|Hatfarm]]

----

They are indeed appended. My battlescape editor deals with TFTD's UnitRef by just adjusting for the larger record size, and then ignoring the extra bytes completely - didn't need to do anything else to make it all match up. I've yet to actually look at some sample values in order to work out what they might be for.

Incidently, you can insert signatures into your postings using four tildes (<nowiki>~~~~</nowiki>). - [[User:Bomb Bloke|Bomb Bloke]] 21:48, 20 January 2010 (EST)

== TFTD's extra bytes ==

It appears that byte 126 is a bit flag array of some sort as I have mostly seen values of 1 and 0 for it, but others have appeared. I saved a single mission at several different times and each one had 0 or 1, but a terror mission save had some different values for this, Like 0x20 and 0x4F. I tried adjusting it and checking the saved game, but nothing seemed to change...

Byte 124 I've seen values of 0,4,6,7,0x0A and 0x0E. No idea what these mean, and changing them did not do anything for me.

They appear to only be for Soldiers as well, none of the aliens in any of my saved games have values for these.
[[User:Hatfarm|Hatfarm]] 15:16, 5 June 2010 (EDT)

----

124 may have something to do with the air-bubbles that trickle up from soldiers when they're underwater - an animation counter, similar to offset 8 of [[SMOKREF.DAT]], but with a higher range (0-15, probably). Granted, there's no real reason to keep track of bubbles when saving the game, but they have to be tracked somewhere at run-time, and this seems to be the logical place (the save files are just raw dumps of RAM anyway).

In theory, if you set this to the same value for all soldiers (say 5), on loading the game, they'd all have identical air bubbles over their heads. - [[User:Bomb Bloke|Bomb Bloke]] 22:26, 5 June 2010 (EDT)

You're right, I set them all to 5 and they were all in the same place bubble wise,. However, they don't all "rebubble" at the same time. Good call BB. [[User:Hatfarm|Hatfarm]] 02:16, 12 June 2010 (EDT)

User:Hatfarm

2010-06-08T20:24:11Z

Hatfarm:

Creator of the [http://www.stonepool.com/xcom/ X-Com Hack] saved game editor.

Talk:GEOSCAPE.EXE

2010-06-05T22:45:51Z

Hatfarm: /* Difficulty patch information wrong? */

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

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

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

- [[User:NKF|NKF]]

----

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

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

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

== Offsets ==

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

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

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

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

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

===Damage modifiers===
.data:0046DE74 damageModifierIncendiary dw 64h,64h,50h, 0,28h,46h,46h,64h, 0,50h,0AAh,64h,64h,64h; 0
.data:0046DE74 ; DATA XREF: sub_429CA0+2B�r
.data:0046DE74 ; sub_429CA0+132�r ...
.data:0046DE90 damageModifierHE dw 64h,64h,64h,64h,4Bh,64h,64h,64h,82h,64h,64h,50h,3Ch,50h; 0
.data:0046DEAC damageModifierLaser dw 64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,96h,64h,46h; 0
.data:0046DEC8 damageModifierPlasma dw 64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,50h,64h,46h; 0
.data:0046DEE4 damageModifierStun dw 64h,64h,5Ah,50h,64h,64h,50h,64h,64h,5Ah,64h,64h,64h, 0; 0
.data:0046DF00 damageModifierMelee dw 64h,78h,64h,64h,5Ah,64h,64h,64h,64h,64h,64h,64h,64h,64h; 0
.data:0046DF1C damageModifierAcidSpit dw 64h,0A0h,6Eh,64h,28h,64h,64h,64h,64h,64h,64h,64h,64h,64h; 0

===HWP weapons data===
.data:0046D57C builtinWeaponStats structBuiltinWeaponStats <0, 4, 3Ch, 3Ch, 21h, 0, 0, 5Ah, 50h, 0>; 0
.data:0046D57C ; DATA XREF: sub_403350+99�r
.data:0046D57C ; sub_40FF70+105�r ...
.data:0046D57C structBuiltinWeaponStats <2, 0Ch, 55h, 37h, 2Dh, 0, 0, 73h, 4Bh, 0>; 1
.data:0046D57C structBuiltinWeaponStats <3, 11h, 6Eh, 32h, 21h, 0, 0, 55h, 4Bh, 0>; 2
.data:0046D57C structBuiltinWeaponStats <4, 24h, 6Eh, 56h, 1Eh, 0, 0, 64h, 3Ch, 0>; 3
.data:0046D57C structBuiltinWeaponStats <2, 28h, 8Ch, 0, 0, 0, 0, 78h, 50h, 1>; 4
.data:0046D57C structBuiltinWeaponStats <7, 26h, 8Ch, 4Bh, 1Eh, 0, 0, 6Eh, 3Ch, 0>; 5
.data:0046D57C structBuiltinWeaponStats <4, 22h, 82h, 4Bh, 1Eh, 0, 0, 6Eh, 3Ch, 0>; 6
.data:0046D57C structBuiltinWeaponStats <3, 22h, 64h, 4Bh, 1Eh, 32h, 23h, 6Eh, 3Ch, 0>; 7
The structure is:
00000000 structBuiltinWeaponStats struc ; (sizeof=0x14)
00000000 damageType dw ?
00000002 ammoType dw ?
00000004 damage dw ?
00000006 snapshotAcc dw ?
00000008 snapshotTU dw ?
0000000A autoshotAcc dw ?
0000000C autoshotTU dw ?
0000000E aimshotAcc dw ?
00000010 aimshotTU dw ?
00000012 blasterEffect dw ?
00000014 structBuiltinWeaponStats ends

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

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

===Craft type data===
.data:0046F9A8 ; DATA XREF: sub_432B90+1C�r
.data:0046F9A8 ; sub_436970+59�r ...
craftsData
.data:0046F9A8 structCraftData <23Ah, 65336, 0, 760, 2, 1500, 150, 4, 0, 0, 0, 0Eh, 0,\
.data:0046F9A8 3, 0> ; 0 ''Skyranger''
.data:0046F9A8 structCraftData <23Bh, 65236, 1, 3100, 8, 30, 800, 4, 0, 0, 0, 0Ch, 0,\
.data:0046F9A8 0, 0> ; 1 ''Lightning''
.data:0046F9A8 structCraftData <23Ch, 65136, 2, 5400, 0Ah, 60, 1200, 4, 0, 0, 0, 1Ah,\
.data:0046F9A8 0, 4, 0> ; 2 ''Avenger''
.data:0046F9A8 structCraftData <23Dh, 65286, 2, 2100, 3, 1000, 100, 4, 0, 0, 0, 0, 0,\
.data:0046F9A8 0, 0> ; 3 ''Interceptor''
.data:0046F9A8 structCraftData <23Eh, 65286, 2, 4200, 9, 20, 500, 4, 0, 0, 0, 0, 0, 0,\
.data:0046F9A8 0> ; 4 ''Firestorm''
.data:0046F9A8 structCraftData <2B2h, 100, 2, 2200, 0Ch, 0, 50, 5, 38h, 0C8h, 0, 0, 0,\
.data:0046F9A8 0, 0> ; 5 ''Small Scout (VS)''
.data:0046F9A8 structCraftData <2B3h, 150, 2, 2400, 9, 0, 200, 4, 38h, 0FAh, 140078h,\
.data:0046F9A8 0, 0, 0, 0> ; 6 ''Medium Scout (S)''
.data:0046F9A8 structCraftData <2B4h, 250, 2, 2700, 9, 0, 250, 4, 30h, 12Ch, 140110h,\
.data:0046F9A8 0, 0, 0, 0> ; 7 ''Large Scout (S)''
.data:0046F9A8 structCraftData <2B5h, 500, 2, 4000, 8, 0, 500, 3, 30h, 1F4h, 2800B0h,\
.data:0046F9A8 0, 0, 0, 0> ; 8 ''Abductor (M)''
.data:0046F9A8 structCraftData <2B6h, 500, 2, 4300, 8, 0, 500, 3, 20h, 1F4h, 2800A0h,\
.data:0046F9A8 0, 0, 0, 0> ; 9 ''Harvester (M)''
.data:0046F9A8 structCraftData <2B7h, 1000, 2, 4800, 6, 0, 1200, 2, 18h, 7D0h, \
.data:0046F9A8 780150h, 0, 0, 0, 0> ; 10 ''Terror Ship (L)''
.data:0046F9A8 structCraftData <2B8h, 1400, 2, 5000, 6, 0, 3000, 1, 18h, 0FA0h, \
.data:0046F9A8 8C0208h, 0, 0, 0, 0> ; 11 ''Battleship (VL'')
.data:0046F9A8 structCraftData <2B9h, 800, 2, 3200, 6, 0, 2200, 2, 18h, 0BB8h, \
.data:0046F9A8 3C0120h, 0, 0, 0, 0> ; 12 ''Supply Ship (L)''

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

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

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

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

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

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

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

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

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

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

:Seb, I realise your formula above for variable firing intervals, from 100%-200% of the base value, explains the 2/3 factor I found which I thought might be UFO Accuracy. The average of a 100-200% range is 1.5, and the inverse of this is 2/3. So perhaps there is no accuracy factor in UFO weapon damage at all. Possibly you just have a base damage and a base firing interval, plus a 50%-100% variation on the base damage and a 100%-200% variation on the firing interval. This would certainly match the data I have so far.

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

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

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

:In the code, do you see any evidence of cannon-type weapons being treated differenly from missile weapons? For example, do cannon rounds not "travel"? Also, do you see the same '''rnd (0,tmp) + tmp''' function being applied to the firing interval of XCom air attacks? Regards, [[User:Spike|Spike]] 14:30, 5 July 2009 (EDT)

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

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

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

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

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

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

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

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

===Flare pattern===
(tactical mode):
.data:0046C558 flarePattern db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 0
.data:0046C558 ; DATA XREF: LightmapAddFlarePattern+7�o
.data:0046C558 ; LightmapAddFlarePattern+19�o
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Fh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Fh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 31
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Eh, 0Eh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Eh, 0Eh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 62
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Eh, 0Dh, 0Dh, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Dh, 0Dh, 0Eh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h; 93
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Dh, 0Ch, 0Ch, 0Ch, 0Bh, 0Bh, 0Bh, 0Bh, 0Bh, 0Ch, 0Ch, 0Ch, 0Dh, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h; 124
.data:0046C558 db 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Bh, 0Bh, 0Ah, 0Ah, 0Ah, 0Ah, 0Ah, 0Bh, 0Bh, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h; 155
.data:0046C558 db 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 0Ah, 0Ah, 9, 9, 9, 9, 9, 0Ah, 0Ah, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h; 186
.data:0046C558 db 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 0Ah, 9, 9, 8, 8, 8, 8, 8, 9, 9, 0Ah, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h; 217
.data:0046C558 db 10h, 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 9, 9, 8, 8, 7, 7, 7, 7, 7, 8, 8, 9, 9, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 10h, 10h; 248
.data:0046C558 db 10h, 0Fh, 0Eh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 9, 8, 7, 7, 6, 6, 6, 6, 6, 7, 7, 8, 9, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Eh, 0Fh, 10h; 279
.data:0046C558 db 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 0Ah, 9, 8, 7, 6, 6, 6, 5, 5, 5, 6, 6, 6, 7, 8, 9, 0Ah, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh, 10h; 310
.data:0046C558 db 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 6, 5, 5, 4, 4, 4, 5, 5, 6, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh, 10h; 341
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 5, 4, 4, 3, 3, 3, 4, 4, 5, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh; 372
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 6, 5, 4, 3, 2, 2, 2, 3, 4, 5, 6, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh; 403
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 5, 4, 3, 2, 1, 1, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh; 434
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh; 465
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 5, 4, 3, 2, 1, 1, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh; 496
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 6, 5, 4, 3, 2, 2, 2, 3, 4, 5, 6, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh; 527
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 5, 4, 4, 3, 3, 3, 4, 4, 5, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh; 558
.data:0046C558 db 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 6, 5, 5, 4, 4, 4, 5, 5, 6, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh, 10h; 589
.data:0046C558 db 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 0Ah, 9, 8, 7, 6, 6, 6, 5, 5, 5, 6, 6, 6, 7, 8, 9, 0Ah, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh, 10h; 620
.data:0046C558 db 10h, 0Fh, 0Eh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 9, 8, 7, 7, 6, 6, 6, 6, 6, 7, 7, 8, 9, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Eh, 0Fh, 10h; 651
.data:0046C558 db 10h, 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 9, 9, 8, 8, 7, 7, 7, 7, 7, 8, 8, 9, 9, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 10h, 10h; 682
.data:0046C558 db 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 0Ah, 9, 9, 8, 8, 8, 8, 8, 9, 9, 0Ah, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h; 713
.data:0046C558 db 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 0Ah, 0Ah, 9, 9, 9, 9, 9, 0Ah, 0Ah, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h; 744
.data:0046C558 db 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Bh, 0Bh, 0Ah, 0Ah, 0Ah, 0Ah, 0Ah, 0Bh, 0Bh, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h; 775
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Dh, 0Ch, 0Ch, 0Ch, 0Bh, 0Bh, 0Bh, 0Bh, 0Bh, 0Ch, 0Ch, 0Ch, 0Dh, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h; 806
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Eh, 0Dh, 0Dh, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Dh, 0Dh, 0Eh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h; 837
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Eh, 0Eh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Eh, 0Eh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 868
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Fh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Fh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 899
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 930

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

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

=== Craft weapon stats ===

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

----

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

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

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

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

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

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

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

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

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

Here is X as a bitmask

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

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

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

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

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

=== Manufacturing stats? ===

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

==New Bundles==

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

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

== Difficulty patch information wrong? ==

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

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

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

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

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

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

GEOSCAPE.EXE

2010-06-05T22:43:31Z

Hatfarm: /* XCOM: UFO Defense DOS Versions, difficulty setting bug */

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

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

Also see [[Versions]].

= X-COM Complete Packages =

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

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

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

''Thanks, and welcome!''

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

==Review #1 by wfames==

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

==Review #2 by Draco Cracona==

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

==Review #3 by Muton commander==

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

==Review #4 by Diegoba==

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

==Review #5 by niffiwan==

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

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

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

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

===Note on x_patched.exe===

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

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

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

= Craft Stats =

At offset 353,020 in X-COM 1.4 (DOS - modified by XCUtil), the aircraft statistics begin. In WinCE (XCUtil) this starts at hex offset 0x6F9A8 and Alien craft start at 0x6fa34.
''Emphyrio: start at 353014?, each entry 14 records of 2 bytes, 5 Xcom craft and then 8 Alien''

Each Vessel Statistic is two bytes and is 0 through 65,535 (in UGE format), and go in the following order:

Pointer to craft name in [[ENGLISH.DAT]] 
Points 
Weapon Pods 
Maximum Speed 
Acceleration 
Fuel 
Damage (armor) 
Size Class 
Unknown (UFO only stat). Believed to be the base firing interval of the weapon 
Unknown (UFO only stat). Value is roughly similar to score for destroying? 
Weapon Range (in 1/8ths of km)(UFOs only) 
Weapon Damage (UFOs only) 
Crew 
HWP 

To help you find it in UGE, here are the various X-COM vessel section in UGE format:

Skyranger: 248 - 2 - 2 - 0 - 220 - 5 - 150 - 0 
Lightning: 28 - 12 - 8 - 0 - 30 - 0 - 32 - 3 
Avenger: 24 - 21 - 10 - 0 - 60 - 0 - 176 - 4 
Interceptor: 52 - 8 - 3 - 0 - 232 - 3 - 100 - 0 
Firestorm: 104 - 16 - 9 - 0 - 20 - 0 - 244 - 1 

A bit below the Firestorm statistics are the stats for various Alien Ships, I'll probably do them later.

Here is a hex signature to help find the first alien craft record (Small Scout):

b2 02 64 00 02 00 98 08 0c 00 00 00 32 00

At offset 380,668 the Tank Statistics begin.

= Armor Stats =

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

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

Front Armor 
Left Armor 
Right Armor 
Rear Armor 
Under Armor 

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

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

So on, etc.

= Alien Stats =

This section is for the structure of the alien stats, as found in GEOSCAPE. For actual data and additional information, see the [[Alien_Stats|alien statistics]] page. Also see Zombie's excellent alien stats page at [http://www.strategycore.co.uk/xcom/pg/ufoalienstats StrategyCore]. ''(Have YOU made your StratCore and [http://www.xcomufo.com XCOMUFO] accounts yet?)''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

'''12:''' Front Armor - Corresponds to Unitref[029]

'''13:''' Left Armor - Corresponds to Unitref[030]

'''14:''' Right Armor - Corresponds to Unitref[031]

'''15:''' Rear Armor - Corresponds to Unitref[032]

'''16:''' Under Armor - Corresponds to Unitref[033]

'''17:''' ''Unknown - Always 0'' - Corresponds to Unitref[034]

'''18:''' Energy Recharge - Corresponds to Unitref[035]

'''19:''' ''Unknown - Always 0'' - Corresponds to Unitref[036]

'''20:''' ''Unknown - Always 1'' No Corresponding Unitref offset

'''21:''' ''Unknown - Always 0'' - Corresponds to Unitref[046]

'''22:''' ''Unknown'' - Corresponds to Unitref[048] (see below)

'''23:''' ''Unknown'' - Corresponds to Unitref[052] (see below)

''NOTE: For additional important info on the last two bytes, see [[Talk:UNITREF.DAT]]. My notes below do not take that info into account. For the moment though I'm leaving it as is. I sure wish we could figure the bytes out, and get rid of all the conjecture! - [[User:MikeTheRed|MikeTheRed]] 08:05, 6 November 2006 (PST)''

These Unitref bytes ([48] and [52]) and now Geoscape Core values have long stumped us hardcore X-Commies. The two bytes always equal the same value for a given alien, including all aliens of the same race (the N's below). And, they're the same between Geoscape and Unitref. Clearly it must be important (or a goof!), but exactly what it is, who knows. Although this page is for X-COM, I've included TFTD in the hopes it helps folks - but it's been so long since I've played TFTD, I can't remember those units at all.

How's this for a thought?...
Dimension Byte(s)

X 22

Y 23

Z 24 (top when standing)
25 (top when kneeling)
26 (bottom)

Maybe they represent the "size in profile" ("width"), affecting likelihood to hit. A game could be tried with a target 20 squares away, set 22 and 23 alternately to 5 or 2 (or 1 or 0?), and see if it affects the successful shots percentage. 0 or even 1 might break the game, though.

Also, how do these values (2 to 5) correlate with the "pixel drawings" of units? I can't seem to find that info at the moment... aren't units and tiles defined as something like 16x16x[[Height|28]]? If so, then perhaps the values (2 to 5) are multiplied by 3 or something to get their final "width" for bullet interception?? --[[User:MikeTheRed|MikeTheRed]] 05:20, 17 September 2006 (PDT)

:I finally got the OSG (w00t!), and noticed the following: The section on weapon accuracy says (p. 221) that target size affects the chance to hit, and "the 'size' of each alien is listed along with all other alien statistics in Chapter 9". But the alien stats tables (p. 250 ff.) only lists Height as a possible 'size' stat, and the text write-ups don't otherwise address "target size" with any precision. This discrepancy - that Chapter 8 talks about '''size''', but Chapter 9 only has '''height''' - might (might!) mean there are more variables that determine target area size, but somehow they didn't make it to the alien stats tables.

:The description for Height (p. 249) does say, "Taller creatures are easier to hit than short ones are. An alien with a height of 40, for example, is twice as easy to hit as an alien with a height of 20." (Note: The tallest [[Height]] is actually 23. And also notice, Float is never mentioned.) This ''might'' mean only height affects this, or it could be read in a general way; other dimensions (X and Y in addition to Z) might also affect it.

:Somebody should do some firing accuracy tests while hacking these potential X & Y bytes! But I still don't know how the values for [22] & [23] compare to what X-COM considers tile width... we know the Height byte accurately reflects the full range of possible values (0 to 23), but I doubt 5 is the full (pixel?) width of a tile. This might mean it's not width, then (or maybe [22] & [23] are added, or they are individually multiplied by 3 or something??) If anyone who knows about tile width could say something, I'd appreciate it. --[[User:MikeTheRed|MikeTheRed]] 11:24, 1 October 2006 (PDT)

In any event, here's a summary of bytes [22] and [23], in the hopes we can figure it out. They're always identical for a given race, and [22] always equals [23].

'''X-COM TFTD'''

Value Alien N Value Alien N

2 Sectoid 6 2 Aquatoid 6
Bio-Drone 1
3 Celatid 1 Tentaculat 1
Chryssalid 1
Civilian 2 3 Calcinite 1
Ethereal 3 Civilian 2
Floater 6 Deep_One 1
Muton 3 Gill_Man 4
Snakeman 5 Tasoth 2

4 Cyberdisc 1 4 Coelacant 1
Hovertank 1 Displacer 1
Reaper 1 Hallucinoid 1
Sectopod 1 Lobster_Man 5
Tank 1 Triscene 1
Xarquid 1
5 Silacoid 1

'''24:''' Standing Height - Corresponds to Unitref[049]

'''25:''' Kneeling Height - Corresponds to Unitref[050]

'''26:''' Floating Height - Corresponds to Unitref[051]

'''27:''' [[Damage#Susceptible_to...|Damage Modifier]] Category - Corresponds to Unitref[055]

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

'''Category''' '''Unit Type(s)'''
'''0''' Not for units, but is used for Terrain and Items
'''1''' Civilian, Sectoid, Celatid, Floater
'''2''' Personal Armor
'''3''' Power Suit, Flying Suit
'''4''' Tanks, Hovertanks
'''5''' Snakemen
'''6''' Ethereal
'''7''' Muton
'''8''' Silacoid
'''9''' Chryssalid
'''10''' Reaper
'''11''' Sectopod
'''12''' Cyberdisc
'''13''' Zombie

'''28:''' Psi Skill - Corresponds to Unitref[037]

'''29:''' Psi Strength - Corresponds to Unitref[057]

'''30:''' Bravery (encoded) - Corresponds to Unitref[059]

'''31:''' Motion scanner size - Corresponds to Unitref[061]

'''32:''' ''1 for Cyberdisc, 0 for all others including TFTD... isn't "Explodes"; the TFTD Bio-Drone also explodes...'' - Corresponds to Unitref[071]

I edited the Cyberdisc's field to 0 and checked to see if it exploded. It still did. Obviously this field is for something else. I'll work on this some more. --[[User:Zombie|Zombie]] 20:15, 15 September 2006 (PDT)

:I have a theory. I vaguely remember something about Cyberdiscs cannot be stunned. Even if you poke it with a Stun Rod and bypass it's self-destruct, it still counts as a kill. Maybe this has something to do with it (as I also remember that none of the other aliens exhibit this behavior)?--[[User:Amitakartok|amitakartok]] 12:55, 23 June 2009 (EDT)

::Good thinking. But the [[Stun]] page shows that Cyberdiscs can be stunned. Checking [[Unitref.Dat]] byte 71 (hex 0x47) shows that, after Zombie posted his statement, there's been a lot of on its [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page about this byte. -[[User:MikeTheRed|MikeTheRed]] 20:07, 2 July 2009 (EDT)

'''33:''' ''Unknown - Always 0'' No Corresponding Unitref offset

'''34:''' Corpse type - Corresponds to Unitref[038]

'''35:''' Big unit (2x2) No Corresponding Unitref offset

'''36:''' Victory point score - Corresponds to Unitref[039]

'''37:''' Aggression - Corresponds to Unitref[044]

'''38:''' Intelligence - Corresponds to Unitref[073]

''This data was just put together working heavily with Zombie and his great SC [http://www.strategycore.co.uk/xcom/pg/ufoalienstats alien stats] page.

= Country Labels =
Starting at offset 396480 (hex: 0x60CC0) are the records that contain the location of the labels for the country names on the world. In order they are X, Y, and English.dat index all signed short integers (6 bytes for each record). X should never be negative but between 0 and 2880, Y should be between -720 and 720 (See [[WORLD.DAT]]). The English.dat file, despite all other array indexes appears to start at 1 and not 0, thus a value of 611 in here represents index 610 in a zero based English.dat array. (It stands to reason that these work for the other language files as well)

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

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

= Detection Ranges =

Detection ranges are hard coded into the executable at the following locations (Win CE / Gold edition):

{| cellspacing="0" border="1"
!Platform
!Address
!Data bytes
!Hex
!Range
!nm
|-
|Aircraft||591EA||C8 00||x00C8||200||600
|-
|Hyperwave||59237||20 03||x0328||800||2400
|-
|Lg Radar||5926D||EE 02||x02EE||750||2250
|-
|Sm Radar||59278||F4 01||x01F4||500||1500
|}

Patching "88 13" to these locations = x1388 = 5000 range units = 15,000 nm pretty much gives that platform visibility over the whole world. Of course Small Radar still only has a 10% detection chance per half hour.

= Battlescape Terrain List =

In the UFO CE executable, offset 476156 (743FCx) marks the beginning of the [[WORLD.DAT]] terrain to battlescape terrain conversion list. 13 double byte values.

02 00 01 00 01 00 01 00 01 00 07 00 02 00 06 00 06 00 08 00 00 00 02 00 08 00

For example, a mission initiated in a GeoScape polygon of type 5 will be performed in battlescape terrain type 7 (mountains).

Note that jungle (type 00) missions in the north will end up as forest missions, and forest (type 02) missions in the south will end up as jungle missions. See offset 10 in [[GEODATA.DAT]] for the full battlescape terrain list.

= Manufacturing stats =

The original data for the product manufacturing information in [[PRODUCT.DAT]] is contained in the geoscape executable, at offset 355600 (for plain 1.4 version).

= XCOM: UFO Defense DOS Versions, difficulty setting bug =
In the DOS versions of the game there was a problem when saving the [[IGLOB.DAT]] file, that would cut off the last four bytes. When the saved game was loaded or at the end of a mission, the game would then be set to beginner, never to return again. There is a single byte that can be adjusted to fix this problem, you change the value from 60 (0x3C) to 64 (0x40). Below are the offsets so you can fix them in your game. 
 
<table {{StdDescTable}}>
<tr>
<th {{StdDescTable_Heading}}>'''Offset dec (hex)'''</th><th {{StdDescTable_Heading}}>'''Game Version'''</th>
</tr>
<tr><td>97228 (0x17BCC)</td><td>DOS Version 1.0</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.2</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.3</td></tr>
<tr><td>95676 (0x175BC)</td><td>DOS Version 1.4</td></tr>
</table>
 
You can read more about the bug at the [[Known_Bugs#Difficulty_Bug|known bugs]] area.

= See Also =
* [[TACTICAL.EXE]] - Sister executable used for Turn based strategy (merged with geoscape.exe in WinCE edition)
* [[UNITREF.DAT]] - Stats on current units (both XCOM and Alien) in play
* [[Talk:GEOSCAPE.EXE]] - More offsets and investigations are on the Discussion page.
* [[Saved Game Files]]

[[Category:Game Files]]

User:Hatfarm

2010-06-05T22:27:35Z

Hatfarm: New page: Creator of the [http://www.stonepool..com/xcom/ X-Com Hack] saved game editor.

Creator of the [http://www.stonepool..com/xcom/ X-Com Hack] saved game editor.

Talk:GEOSCAPE.EXE

2010-06-05T22:24:03Z

Hatfarm: /* Difficulty patch information wrong? */

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

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

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

- [[User:NKF|NKF]]

----

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

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

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

== Offsets ==

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

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

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

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

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

===Damage modifiers===
.data:0046DE74 damageModifierIncendiary dw 64h,64h,50h, 0,28h,46h,46h,64h, 0,50h,0AAh,64h,64h,64h; 0
.data:0046DE74 ; DATA XREF: sub_429CA0+2B�r
.data:0046DE74 ; sub_429CA0+132�r ...
.data:0046DE90 damageModifierHE dw 64h,64h,64h,64h,4Bh,64h,64h,64h,82h,64h,64h,50h,3Ch,50h; 0
.data:0046DEAC damageModifierLaser dw 64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,96h,64h,46h; 0
.data:0046DEC8 damageModifierPlasma dw 64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,64h,50h,64h,46h; 0
.data:0046DEE4 damageModifierStun dw 64h,64h,5Ah,50h,64h,64h,50h,64h,64h,5Ah,64h,64h,64h, 0; 0
.data:0046DF00 damageModifierMelee dw 64h,78h,64h,64h,5Ah,64h,64h,64h,64h,64h,64h,64h,64h,64h; 0
.data:0046DF1C damageModifierAcidSpit dw 64h,0A0h,6Eh,64h,28h,64h,64h,64h,64h,64h,64h,64h,64h,64h; 0

===HWP weapons data===
.data:0046D57C builtinWeaponStats structBuiltinWeaponStats <0, 4, 3Ch, 3Ch, 21h, 0, 0, 5Ah, 50h, 0>; 0
.data:0046D57C ; DATA XREF: sub_403350+99�r
.data:0046D57C ; sub_40FF70+105�r ...
.data:0046D57C structBuiltinWeaponStats <2, 0Ch, 55h, 37h, 2Dh, 0, 0, 73h, 4Bh, 0>; 1
.data:0046D57C structBuiltinWeaponStats <3, 11h, 6Eh, 32h, 21h, 0, 0, 55h, 4Bh, 0>; 2
.data:0046D57C structBuiltinWeaponStats <4, 24h, 6Eh, 56h, 1Eh, 0, 0, 64h, 3Ch, 0>; 3
.data:0046D57C structBuiltinWeaponStats <2, 28h, 8Ch, 0, 0, 0, 0, 78h, 50h, 1>; 4
.data:0046D57C structBuiltinWeaponStats <7, 26h, 8Ch, 4Bh, 1Eh, 0, 0, 6Eh, 3Ch, 0>; 5
.data:0046D57C structBuiltinWeaponStats <4, 22h, 82h, 4Bh, 1Eh, 0, 0, 6Eh, 3Ch, 0>; 6
.data:0046D57C structBuiltinWeaponStats <3, 22h, 64h, 4Bh, 1Eh, 32h, 23h, 6Eh, 3Ch, 0>; 7
The structure is:
00000000 structBuiltinWeaponStats struc ; (sizeof=0x14)
00000000 damageType dw ?
00000002 ammoType dw ?
00000004 damage dw ?
00000006 snapshotAcc dw ?
00000008 snapshotTU dw ?
0000000A autoshotAcc dw ?
0000000C autoshotTU dw ?
0000000E aimshotAcc dw ?
00000010 aimshotTU dw ?
00000012 blasterEffect dw ?
00000014 structBuiltinWeaponStats ends

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

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

===Craft type data===
.data:0046F9A8 ; DATA XREF: sub_432B90+1C�r
.data:0046F9A8 ; sub_436970+59�r ...
craftsData
.data:0046F9A8 structCraftData <23Ah, 65336, 0, 760, 2, 1500, 150, 4, 0, 0, 0, 0Eh, 0,\
.data:0046F9A8 3, 0> ; 0 ''Skyranger''
.data:0046F9A8 structCraftData <23Bh, 65236, 1, 3100, 8, 30, 800, 4, 0, 0, 0, 0Ch, 0,\
.data:0046F9A8 0, 0> ; 1 ''Lightning''
.data:0046F9A8 structCraftData <23Ch, 65136, 2, 5400, 0Ah, 60, 1200, 4, 0, 0, 0, 1Ah,\
.data:0046F9A8 0, 4, 0> ; 2 ''Avenger''
.data:0046F9A8 structCraftData <23Dh, 65286, 2, 2100, 3, 1000, 100, 4, 0, 0, 0, 0, 0,\
.data:0046F9A8 0, 0> ; 3 ''Interceptor''
.data:0046F9A8 structCraftData <23Eh, 65286, 2, 4200, 9, 20, 500, 4, 0, 0, 0, 0, 0, 0,\
.data:0046F9A8 0> ; 4 ''Firestorm''
.data:0046F9A8 structCraftData <2B2h, 100, 2, 2200, 0Ch, 0, 50, 5, 38h, 0C8h, 0, 0, 0,\
.data:0046F9A8 0, 0> ; 5 ''Small Scout (VS)''
.data:0046F9A8 structCraftData <2B3h, 150, 2, 2400, 9, 0, 200, 4, 38h, 0FAh, 140078h,\
.data:0046F9A8 0, 0, 0, 0> ; 6 ''Medium Scout (S)''
.data:0046F9A8 structCraftData <2B4h, 250, 2, 2700, 9, 0, 250, 4, 30h, 12Ch, 140110h,\
.data:0046F9A8 0, 0, 0, 0> ; 7 ''Large Scout (S)''
.data:0046F9A8 structCraftData <2B5h, 500, 2, 4000, 8, 0, 500, 3, 30h, 1F4h, 2800B0h,\
.data:0046F9A8 0, 0, 0, 0> ; 8 ''Abductor (M)''
.data:0046F9A8 structCraftData <2B6h, 500, 2, 4300, 8, 0, 500, 3, 20h, 1F4h, 2800A0h,\
.data:0046F9A8 0, 0, 0, 0> ; 9 ''Harvester (M)''
.data:0046F9A8 structCraftData <2B7h, 1000, 2, 4800, 6, 0, 1200, 2, 18h, 7D0h, \
.data:0046F9A8 780150h, 0, 0, 0, 0> ; 10 ''Terror Ship (L)''
.data:0046F9A8 structCraftData <2B8h, 1400, 2, 5000, 6, 0, 3000, 1, 18h, 0FA0h, \
.data:0046F9A8 8C0208h, 0, 0, 0, 0> ; 11 ''Battleship (VL'')
.data:0046F9A8 structCraftData <2B9h, 800, 2, 3200, 6, 0, 2200, 2, 18h, 0BB8h, \
.data:0046F9A8 3C0120h, 0, 0, 0, 0> ; 12 ''Supply Ship (L)''

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

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

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

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

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

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

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

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

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

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

:Seb, I realise your formula above for variable firing intervals, from 100%-200% of the base value, explains the 2/3 factor I found which I thought might be UFO Accuracy. The average of a 100-200% range is 1.5, and the inverse of this is 2/3. So perhaps there is no accuracy factor in UFO weapon damage at all. Possibly you just have a base damage and a base firing interval, plus a 50%-100% variation on the base damage and a 100%-200% variation on the firing interval. This would certainly match the data I have so far.

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

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

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

:In the code, do you see any evidence of cannon-type weapons being treated differenly from missile weapons? For example, do cannon rounds not "travel"? Also, do you see the same '''rnd (0,tmp) + tmp''' function being applied to the firing interval of XCom air attacks? Regards, [[User:Spike|Spike]] 14:30, 5 July 2009 (EDT)

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

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

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

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

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

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

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

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

===Flare pattern===
(tactical mode):
.data:0046C558 flarePattern db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 0
.data:0046C558 ; DATA XREF: LightmapAddFlarePattern+7�o
.data:0046C558 ; LightmapAddFlarePattern+19�o
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Fh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Fh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 31
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Eh, 0Eh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Eh, 0Eh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 62
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Eh, 0Dh, 0Dh, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Dh, 0Dh, 0Eh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h; 93
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Dh, 0Ch, 0Ch, 0Ch, 0Bh, 0Bh, 0Bh, 0Bh, 0Bh, 0Ch, 0Ch, 0Ch, 0Dh, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h; 124
.data:0046C558 db 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Bh, 0Bh, 0Ah, 0Ah, 0Ah, 0Ah, 0Ah, 0Bh, 0Bh, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h; 155
.data:0046C558 db 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 0Ah, 0Ah, 9, 9, 9, 9, 9, 0Ah, 0Ah, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h; 186
.data:0046C558 db 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 0Ah, 9, 9, 8, 8, 8, 8, 8, 9, 9, 0Ah, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h; 217
.data:0046C558 db 10h, 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 9, 9, 8, 8, 7, 7, 7, 7, 7, 8, 8, 9, 9, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 10h, 10h; 248
.data:0046C558 db 10h, 0Fh, 0Eh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 9, 8, 7, 7, 6, 6, 6, 6, 6, 7, 7, 8, 9, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Eh, 0Fh, 10h; 279
.data:0046C558 db 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 0Ah, 9, 8, 7, 6, 6, 6, 5, 5, 5, 6, 6, 6, 7, 8, 9, 0Ah, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh, 10h; 310
.data:0046C558 db 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 6, 5, 5, 4, 4, 4, 5, 5, 6, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh, 10h; 341
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 5, 4, 4, 3, 3, 3, 4, 4, 5, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh; 372
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 6, 5, 4, 3, 2, 2, 2, 3, 4, 5, 6, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh; 403
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 5, 4, 3, 2, 1, 1, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh; 434
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh; 465
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 5, 4, 3, 2, 1, 1, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh; 496
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 6, 5, 4, 3, 2, 2, 2, 3, 4, 5, 6, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh; 527
.data:0046C558 db 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 5, 4, 4, 3, 3, 3, 4, 4, 5, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh; 558
.data:0046C558 db 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 8, 7, 6, 6, 5, 5, 4, 4, 4, 5, 5, 6, 6, 7, 8, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh, 10h; 589
.data:0046C558 db 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 0Ah, 9, 8, 7, 6, 6, 6, 5, 5, 5, 6, 6, 6, 7, 8, 9, 0Ah, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Fh, 10h; 620
.data:0046C558 db 10h, 0Fh, 0Eh, 0Eh, 0Dh, 0Ch, 0Bh, 0Ah, 9, 9, 8, 7, 7, 6, 6, 6, 6, 6, 7, 7, 8, 9, 9, 0Ah, 0Bh, 0Ch, 0Dh, 0Eh, 0Eh, 0Fh, 10h; 651
.data:0046C558 db 10h, 10h, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 9, 9, 8, 8, 7, 7, 7, 7, 7, 8, 8, 9, 9, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 10h, 10h; 682
.data:0046C558 db 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 0Ah, 9, 9, 8, 8, 8, 8, 8, 9, 9, 0Ah, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h; 713
.data:0046C558 db 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Ah, 0Ah, 0Ah, 9, 9, 9, 9, 9, 0Ah, 0Ah, 0Ah, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h; 744
.data:0046C558 db 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Ch, 0Ch, 0Bh, 0Bh, 0Bh, 0Ah, 0Ah, 0Ah, 0Ah, 0Ah, 0Bh, 0Bh, 0Bh, 0Ch, 0Ch, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h; 775
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Dh, 0Dh, 0Ch, 0Ch, 0Ch, 0Bh, 0Bh, 0Bh, 0Bh, 0Bh, 0Ch, 0Ch, 0Ch, 0Dh, 0Dh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h; 806
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Eh, 0Dh, 0Dh, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Ch, 0Dh, 0Dh, 0Eh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h; 837
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Eh, 0Eh, 0Eh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Dh, 0Eh, 0Eh, 0Eh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 868
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Fh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Eh, 0Fh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 899
.data:0046C558 db 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 0Fh, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h, 10h; 930

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

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

=== Craft weapon stats ===

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

----

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

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

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

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

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

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

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

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

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

Here is X as a bitmask

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

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

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

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

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

=== Manufacturing stats? ===

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

==New Bundles==

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

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

== Difficulty patch information wrong? ==

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

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

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

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

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

I just checked it against my 1.4 executable and it was right. Has the value been corrected since this was posted?
[[User:Hatfarm|Hatfarm]] 18:24, 5 June 2010 (EDT)

Talk:UNITREF.DAT

2010-06-05T20:07:20Z

Hatfarm: /* TFTD's extra bytes */

Talk:UNITREF.DAT

2010-06-05T19:16:48Z

Hatfarm: /* TFTD's extra bytes */

Anyone who has it - can we get listings of values for various aliens on the Unitref page, for some of the variables found in both Unitref and the Geoscape [[Talk:Overviews_of_Aliens|Alien stats]]? E.g. energy recharge (Unitref[35]), energy loss [45]... like what Danial did for Height. Some of it might go to NKF's redesigned [[Soldier]] page. I am trying to flesh out the Geoscape data so I know what everything is there (and can then extend it across difficulty levels). It has unlabelled fields with values, some of which I know must be these values... but there's no list for me to compare against. Thanks if you can help! ---[[User:MikeTheRed|MikeTheRed]] 19:37, 25 Nov 2005 (PST)

P.S. We probably should clean up this Discussion some time. I will if I find the time to make sure everything has made its way to wherever it should go.

----

== Offsets 0x30 & 0x34 ==

I've chopped out the majority of this page as it is no longer required. I'm keeping the heights chart in case it is required - I've also changed the "H-F" field to "H+F", as this actually makes sense.
[49] [51] "Tall" [48] | [49] [48]
Class Ht. Flt H+F Wide | Ht. Wide Area
--------- --- --- ---- ---- | --- ---- ----
Sectoid 16 0 16 2 | 16 2 32 Area=Ht.*Wide
Celatid 12 6 18 3 | 12 3 36
Hovertank* 12 6 18 4 | 12 4 48
Silacoid 10 0 10 5 | 10 5 50
Snakeman 18 0 18 3 | 18 3 54
Zombie 18 0 18 3 | 18 3 54
Cyberdisc 15 2 17 4 | 15 4 60
Ethereal 20 0 20 3 | 20 3 60 ''All Hover/Tanks in their
Chryssalid 21 0 21 3 | 21 3 63 ''class assumed to be same
Civilian 21 2 23 3 | 21 3 63 ''altho not tested yet
Floater 21 2 23 3 | 21 3 63
Muton 21 0 21 3 | 21 3 63
Tank* 16 0 16 4 | 16 4 64
Soldier 22 0 22 3 | 22 3 66
Reaper 23 0 23 4 | 23 4 92
Sectopod 23 0 23 4 | 23 4 92

Anyway, unitref[48] and unitref[52] remain somewhat of a mystery. Thus far we've assumed them to be the unit's width. Today I tried tinkering with [48] to see of this was correct. As I cranked it up, I found no change in my accuracy, or as to how the Sectoid target blocked line of fire to the tiles behind it.

When it reached the value of 37, however, the alien disappeared! I could not view it regardless of distance. In fact, I could even fire right through the tile it was standing on with no obstruction. The only sign that the alien was still there was the fact that my unit could not stand on the same square.

I lowered [48] a bit and tried viewing the alien from different distances, and found that it appeared in the same way as it usually would, regardless of the value used. It's simply the case that going to 37 or above makes the alien invisible.

I also tweaked [52] a bit, but found that it seemed to have no similar effects, if any at all.

Although I haven't tested this any further as yet, it might be possible to use this effect in reverse - Create an 'invisible' X-Com unit, and use it to observe how aliens act when they think we're not looking.

- [[User:Bomb Bloke|Bomb Bloke]] 00:44, 31 July 2006 (PDT)

----

I have a strong belief that offset 48 is nothing else but the loftemps.dat entry used for collision checking with bullets. A first check is done against the unit height (taking into account floating height, terrain height, kneeling). If the check is OK, the loftemps entry is then used as a final check (effectively treating the unit as a cylinder). I'll try to decypher the code further. If others want to have a look, the code is around here:
.text:004116AE 8B 15 5C 28 4A 00 mov edx, pUnitPos
...
[[User:Seb76|Seb76]] 13:24, 10 April 2008 (PDT)

----

I'm inclined to agree with you, though I'm not much good at reading through executable code. :( I hit on the same idea on my [[User_talk:Bomb_Bloke|talk page]]... I've got some notes in there about how I think the firing system works, if you could find code to back it up I'd be a happy boy.

It's something of a long winded work-in-progress ramble, and I'm sure some parts are confusing and/or dead wrong, but with any luck you can make some sort of sense of it. :) - [[User:Bomb Bloke|Bomb Bloke]] 18:34, 11 April 2008 (PDT)

----

[[Image:Loftemps.png|thumb|right]]I mentionned it earlier but got no real feedback so I'm adding a new section for it ;)
It looks like it is the loftemps entry used for collision detection with bullets. The main page says that setting it to 37 make the shots go right through the guys. If you have a look at the entry, you'll see why... The interesting thing is that the big units do not have special entries (unitref is common for all 4 parts so it would not have been possible to do otherwise) so a shot should be able to go through them (between the 4 parts). However, for the shot to be almost horizontal (or vertical) and traveling at the frontier between tiles (to go between the 4 "collision" circles), the shot should come from far far away so it is not likely to happened. Also depending on how the visibility check is performed, it may explain why alien suddenly disappeared when messing with the value (see discussion upper in this page). I suspect it is done using some kind of raytracing between the center of the 2 tiles (between the current unit and the target); so if the loftemps entry for the target has a "hole" in its center, it may become invisible. [[User:Seb76|Seb76]] 07:00, 1 June 2008 (PDT)

----

I just edited unitref 048 and 052 of all my soldiers to 0 and the aliens never tried to shoot at me. When I edited 048 to 0 for all the Sectoids on a mission, my soldiers couldn't see them anymore (only takes effect the following round if edited in unitef.dat, but surprisingly aliens remain visible to you during their movement phase). Since loftemps 0 is an empty cell, the results make perfect sense. A value of 76 (both 48&52) makes aliens disappear too. I'm not sure what the threshold is for disappearing, but a 3x3 block (loftemps 1) is still enough to be seen. --[[User:Zombie|Zombie]] 15:08, 17 August 2008 (PDT)

----

Am I understanding correctly... for purposes of shots hitting, we're all "barrels" with a specific diameter (i.e. [[LOFTEMPS.DAT]] 2-5), height ([49]), and distance (float) off the ground ([51])? Right or wrong, it sounds like this is finally pretty sown up, excellent work. We could update the page's entries. I wonder why they repeated this value twice (i.e. [48] and [52] always the same)... maybe they once considered the possibility of a unit whose diameter can change from turn to turn? If so, some other heretofore unfathomable UNITREF bit or byte may have been intended to dictate whether they're currently using the diameter at [48] or [52]. -[[User:MikeTheRed|MikeTheRed]] 17:06, 17 August 2008 (PDT)

----

While I've no problem believing [48] is a LOF template reference, I hadn't added it to the main page because I wanted to be sure as to it's relationship with [52].

See, at present, all we know about [52] is that it's the same as [48]. We haven't seen any effects from changing it.

What I ''suspect'' is that one offset might be used for shots traveling along an angle parallel to the target, and one offset might be used for shots traveling perpendicular. This would basically allow units to be effectively oval shaped (or it would, if [48] and [52] weren't the same for all units).

Just one of those things that I never got around to finishing the testing on. Would be dead easy to check, though.

There's still a little more to be researched before the entirety of the firing system is understood (see my talk page for a rambling explanation as to what IS known), but that's pretty much the basics of it.

- [[User:Bomb Bloke|Bomb Bloke]] 19:51, 17 August 2008 (PDT)

----

BB and others, see my edits for [48]. Does it make sense? In particular, I estimated pixel width from that little LOFTEMPS .png by magnifying it a ton. Any and all comments or edits welcomed. It's interesting that the silacoid has the highest width, but a low cross-section - did anyone see the Star Trek TOS show with the very short, wide silicon aliens? -[[User:MikeTheRed|MikeTheRed]] 22:53, 23 August 2008 (PDT)

----

Yes, you got the LOF widths correct. Though as you mentioned, they're only accurate assuming you're firing head on at your targets (as the templates aren't perfect circles, their width varies from other angles).

I threw in the kneeling soldier stats and made a note concerning large units.

- [[User:Bomb Bloke|Bomb Bloke]] 22:21, 24 August 2008 (PDT)

== Offset 0x3C ==

I have a gut feeling it is related to the panic/berserk status of the unit... Any volunteer for testing? [[User:Seb76|Seb76]] 10:36, 22 March 2008 (PDT)

----

Made a save where all soldiers had no morale. Ended turn, most of them panicked etc. Saved the game but that offset still came up as 0. Might only be flagged at runtime.

- [[User:Bomb Bloke|Bomb Bloke]] 18:01, 26 May 2008 (PDT)

----

I checked and indeed the game sets and clears it in the same turn so it is always 0 in a savegame and hence there is no 'black box' way of confirming it. I can provide disassembly screenshots if you want proofs however ;) [[User:Seb76|Seb76]] 05:45, 28 May 2008 (PDT)
:Actually after some thinking, it _might_ be possible... If you set the value to 3 for all entries, everyone may go berserk, with 2 they should run in fear and 1, they'll just crap their pants in place... [[User:Seb76|Seb76]] 07:09, 28 May 2008 (PDT)

----

I tried it, and indeed my units did exactly that (at the start of their next turn - not that of the aliens).

- [[User:Bomb Bloke|Bomb Bloke]] 21:08, 28 May 2008 (PDT)

== Offset 0x71 ==
Hmm, the code checks this offset before applying stun damage... It looks more like an 'immune to stun damage' flag then. Strange... [[User:Seb76|Seb76]] 13:48, 7 April 2008 (PDT)

----

By memory, the only things that use this are X-Com HWPs (which shouldn't have stun applied). It does toggle inventory access as described though it wouldn't surprise me if it also toggled stun damage.

- [[User:Bomb Bloke|Bomb Bloke]] 05:46, 8 April 2008 (PDT)

:OK, I located the check and it is exactly what happens. BTW, if you want to try something, try to patch this with nops (0x90):
.text:00412A20 A8 40 test al, 40h
.text:00412A22 0F 85 00 02 00 00 jnz exit ; default
:It should enable inventory screen for memory controlled units (could not test since I have no save files with psy units...) [[User:Seb76|Seb76]] 11:37, 8 April 2008 (PDT)

:: So, to be clear, is this the location of the inventory screen check for mind controlled alien units? And here you are disabling the check by overwriting it with NOPS? Is there a nearby section of code that does the same check for tanks? I would like to be able to override this tank inventory check in order to play with [[User:Spike#Tank mods|Tank mods]]. It looks like NOPing the check logic is the right way to do it, since if instead I toggled the 0x71 flag for the tanks, they would than also become vulnerable to Stun? Though I also I think read somewhere that if you get to the inventory screen of a tank, the game crashes. It doesn't crash if you get to the inventory screen of an Alien large unit via the Alien Inventory or Alien Pets hacks (not sure which) in your UFOExtender. I was able to arm Reapers with dual Heavy Plasma or dual Blaster Launchers. (Unpleasant. They have 0% FA so they have to run up to you and spray with the Heavy Plasma. Not a problem with the Blaster Launcher.) [[User:Spike|Spike]] 13:59, 20 August 2009 (EDT)

== Offset 0xB ==
The value is used together as an offset to [[TERRAIN|MCDData]] offset 39 (describing TUs required to cross a tile walking/flying/sliding) so it most likely represent the way the unit moves. Still needs testing. [[User:Seb76|Seb76]] 13:27, 23 May 2008 (PDT)

----

I took a look at it for Snakemen and Silacoids, it's still 0 (same as it is for everything else).

But that doesn't mean it remains at 0 when the game's running. Do you mean to say that the value here + 39 = the offset in the MCD array that says how many TUs were required to move past any given obstacles in the current map location?

(That is, you'd expect to see a 2 there for sliding units?)

- [[User:Bomb Bloke|Bomb Bloke]] 05:14, 25 May 2008 (PDT)

----

Yep, exactly like that. Also it checks if the value is 0xff and prevent movement in that case. I'll try a live check with a debugger when I encounter snakemen. Maybe it's a part of code that was implemented but not put into usage. [[User:Seb76|Seb76]] 05:20, 25 May 2008 (PDT)
:Did the check and the value is indeed zero even for snakemen... BTW, is the movement type really working? I mean has anybody ever checked that e.g. snakemen really use different TU amount for tiles where TU usage is not the same between crawling and walking? [[User:Seb76|Seb76]] 06:43, 25 May 2008 (PDT)

----

Truth be told I don't remember reading of anyone doing the tests, so I had a go myself.

I tried first with the Avenger ramp, stuck it up in the air and had soldiers walk/fly onto it. Made no effect to their TU usage.

Next I rigged a Snakeman mission in the arctic, stuck one of them in the middle of a pond. It wouldn't move on it's own, and I couldn't move it under mind control.

So then I set 0xB to 2 just for that unit, and hey presto! Suddenly it was able to move freely, either under my control or otherwise. That's certainly the movement type flag... It's just not set in practise.

Still, now I'm wondering if 2 really was for sliders... It doesn't make sense that "fliers" (which I guess was supposed to include the likes of CyberDiscs, which "hover" even when on the ground) wouldn't be able to cross water, yet Snakemen could. Perhaps it should be the other way around?

- [[User:Bomb Bloke|Bomb Bloke]] 19:22, 25 May 2008 (PDT)

----

Note that there are some tiles that have 0 MP cost for sliders. - [[User:Zaimoni|Zaimoni]] 22:28, 25 May 2008 (CDT)

: Yeah, I guess that puts the clincher on it. Only fliers would really be totally unhindered by ground rubble. I've tweaked the MCD details page accordingly. - [[User:Bomb Bloke|Bomb Bloke]] 05:25, 26 May 2008 (PDT)

----

Hehe, I knew it couldn't be anything else but movement type. Yet another entry for known bugs ;) I'll check if it's possible to reenable the feature. It'll depends if it's a bug or if it was voluntarily removed I guess... [[User:Seb76|Seb76]] 04:37, 26 May 2008 (PDT)
: Did a quick check and can confirm what is said in [[GEOSCAPE.EXE#Alien_Stats|Alien Stats]] page. Offset 0xB is filled with the 3rd "unknown" value of alien stats. It is set to 0 for all entries. Could not find any other place where it could possibly be set to another value. [[User:Seb76|Seb76]] 05:17, 26 May 2008 (PDT)

----

So it's just a matter of tweaking that for all relevant units, then. However, I reckon it was left unused intentionally - I doubt the map files really contain enough variety to make it worth including.

- [[User:Bomb Bloke|Bomb Bloke]] 05:25, 26 May 2008 (PDT)

----

Since TFTD was done later with the same engine, perhaps it makes use of this? However, given that a different team made it ([http://www.lasersquadnemesis.com/AboutUs.htm Terror from the Deep was developed by Microprose using code licensed by Mythos]), developers may not have known the feature was available... [[User:Seb76|Seb76]] 07:25, 28 May 2008 (PDT)

----

I took a quick check, and sure enough found a Hallucinoid (the big flying squid thing) set to 2.

- [[User:Bomb Bloke|Bomb Bloke]] 21:31, 28 May 2008 (PDT)

== Offset 0x47 ==

The only use I could find is that of updating [[SOURCEMP.DAT|mobile light sources]] (or something like that) when the unit dies/is rendered unconscious. Could not find anything else about this flag. [[User:Seb76|Seb76]] 05:24, 29 May 2008 (PDT)

:Good work there. As a general statement, can I say - I've been waiting for somebody to disassemble XCOM :) -[[User:MikeTheRed|MikeTheRed]] 21:18, 30 May 2008 (PDT)

I sat down to do some tests with this, but didn't bother too read to closely... I was selecting/moving units around when I probably shoulda been shooting at them.

Oh well. For the record:

Moving a unit causes a light check to be done on all your units. You may not see this light if one of your units is standing in a fog-of-war covered zone (say you just mind controlled an alien and haven't selected it yet).

Selecting a unit does a fog-of-war check concerning what it can see, but does not do a light check.

Whatever this offset is has no effect on the light produced by your units, or the aliens units. Your active guys ALWAYS fully illuminate their tile (even if this is 0) and the aliens provide no illumination at all. Will have to do some tests concerning what happens when you shoot them, but it seems odd: If a unit is dead I'd expect a full light check to be done, since the unit isn't "active" it won't produce light, so I don't see how this offset is helpful there... You can't just remove the light values for this one unit because you might interfere with other nearby light sources, so you really have to calculate them all from scratch.

But likewise it seems [[TERRAIN|MCD[58/3A]]] is similar; a street lamp is set to 1, a normal lamp to 10, but they both provide maximum illumination.

Perhaps the programmers changed their mind about the lighting system at some point? Dunno.

- [[User:Bomb Bloke|Bomb Bloke]] 07:03, 20 June 2008 (PDT)

:Some of your note reminds me of what I wrote at [[Night_Missions#Personal_lighting]] ... does that help any? (probably not) -[[User:MikeTheRed|MikeTheRed]] 16:01, 20 June 2008 (PDT)

== On Fire Flag or Timer ? ==

Do we have any idea where a flag is set to show the unit is on fire? This is persistent between saved games so it must be stored in a file somewhere. Possibly UNITPOS.DAT? It could be a flag, but more likely is either a countdown timer for turns remaining on fire, (values 1-5?), or a "what turn do I stop being on fire" timer value (like a grenade timer).

I have uploaded a saved game file with a burning Aquatoid if anyone wants to take a look. I just don't have the right diff tools. Maybe with the Hex Workshop template... [[User:Spike|Spike]] 19:05, 10 March 2009 (CDT)

:Offset 114 in Unitref holds that data. --[[User:Zombie|Zombie]] 19:15, 10 March 2009 (CDT)

:: Sorry I did not read the article carefully enough. It's in there. [[User:Spike|Spike]] 19:16, 10 March 2009 (CDT)

114 / 72: If not 0, then unit is on fire, and will burn for this amount of turns.

== Floating Civilians ==

Civilians float 2 units off the ground, like Floaters and Cyberdisks. Soldiers don't. Should we consider this to be a bug? [[User:Spike|Spike]] 13:41, 20 August 2009 (EDT)

:Probably. I really doubt it's an intentional feature. --[[User:Zombie|Zombie]] 23:09, 20 August 2009 (EDT)

== Remembering morale vs health and pain killers ==

The game remembers whether a health loss has or has not been used to regain morale via pain killers. Presumably this is stored somewhere in UNITREF.DAT? [[User:Spike|Spike]] 10:30, 5 September 2009 (EDT)

== TFTD ==

It appears the name string starts at the same point in TFTD save points, which leads me to believe that the extra bytes are probably just appended at the end of the file, without much changing in the first 124 bytes per entry, anyone know what these extra 8 bytes might represent? - [[User:Hatfarm|Hatfarm]]

----

They are indeed appended. My battlescape editor deals with TFTD's UnitRef by just adjusting for the larger record size, and then ignoring the extra bytes completely - didn't need to do anything else to make it all match up. I've yet to actually look at some sample values in order to work out what they might be for.

Incidently, you can insert signatures into your postings using four tildes (<nowiki>~~~~</nowiki>). - [[User:Bomb Bloke|Bomb Bloke]] 21:48, 20 January 2010 (EST)

== TFTD's extra bytes ==

It appears that byte 126 is a bit flag of some sort as I have mostly seen values of 1 and 0 for it, but others have appeared. I saved a single mission at several different times and each one had 0 or 1, but a terror mission save had some different values for this, Like 0x20 and 0x4F. I tried adjusting it and checking the saved game, but nothing seemed to change...

Byte 124 I've seen values of 0,4,6,7,0x0A and 0x0E. No idea what these mean, and changing them did not do anything for me.

They appear to only be for Soldiers as well, none of the aliens in any of my saved games have values for these.
[[User:Hatfarm|Hatfarm]] 15:16, 5 June 2010 (EDT)

Talk:UNITREF.DAT

2010-06-05T19:16:29Z

Hatfarm: New section: TFTD's extra bytes

Anyone who has it - can we get listings of values for various aliens on the Unitref page, for some of the variables found in both Unitref and the Geoscape [[Talk:Overviews_of_Aliens|Alien stats]]? E.g. energy recharge (Unitref[35]), energy loss [45]... like what Danial did for Height. Some of it might go to NKF's redesigned [[Soldier]] page. I am trying to flesh out the Geoscape data so I know what everything is there (and can then extend it across difficulty levels). It has unlabelled fields with values, some of which I know must be these values... but there's no list for me to compare against. Thanks if you can help! ---[[User:MikeTheRed|MikeTheRed]] 19:37, 25 Nov 2005 (PST)

P.S. We probably should clean up this Discussion some time. I will if I find the time to make sure everything has made its way to wherever it should go.

----

== Offsets 0x30 & 0x34 ==

I've chopped out the majority of this page as it is no longer required. I'm keeping the heights chart in case it is required - I've also changed the "H-F" field to "H+F", as this actually makes sense.
[49] [51] "Tall" [48] | [49] [48]
Class Ht. Flt H+F Wide | Ht. Wide Area
--------- --- --- ---- ---- | --- ---- ----
Sectoid 16 0 16 2 | 16 2 32 Area=Ht.*Wide
Celatid 12 6 18 3 | 12 3 36
Hovertank* 12 6 18 4 | 12 4 48
Silacoid 10 0 10 5 | 10 5 50
Snakeman 18 0 18 3 | 18 3 54
Zombie 18 0 18 3 | 18 3 54
Cyberdisc 15 2 17 4 | 15 4 60
Ethereal 20 0 20 3 | 20 3 60 ''All Hover/Tanks in their
Chryssalid 21 0 21 3 | 21 3 63 ''class assumed to be same
Civilian 21 2 23 3 | 21 3 63 ''altho not tested yet
Floater 21 2 23 3 | 21 3 63
Muton 21 0 21 3 | 21 3 63
Tank* 16 0 16 4 | 16 4 64
Soldier 22 0 22 3 | 22 3 66
Reaper 23 0 23 4 | 23 4 92
Sectopod 23 0 23 4 | 23 4 92

Anyway, unitref[48] and unitref[52] remain somewhat of a mystery. Thus far we've assumed them to be the unit's width. Today I tried tinkering with [48] to see of this was correct. As I cranked it up, I found no change in my accuracy, or as to how the Sectoid target blocked line of fire to the tiles behind it.

When it reached the value of 37, however, the alien disappeared! I could not view it regardless of distance. In fact, I could even fire right through the tile it was standing on with no obstruction. The only sign that the alien was still there was the fact that my unit could not stand on the same square.

I lowered [48] a bit and tried viewing the alien from different distances, and found that it appeared in the same way as it usually would, regardless of the value used. It's simply the case that going to 37 or above makes the alien invisible.

I also tweaked [52] a bit, but found that it seemed to have no similar effects, if any at all.

Although I haven't tested this any further as yet, it might be possible to use this effect in reverse - Create an 'invisible' X-Com unit, and use it to observe how aliens act when they think we're not looking.

- [[User:Bomb Bloke|Bomb Bloke]] 00:44, 31 July 2006 (PDT)

----

I have a strong belief that offset 48 is nothing else but the loftemps.dat entry used for collision checking with bullets. A first check is done against the unit height (taking into account floating height, terrain height, kneeling). If the check is OK, the loftemps entry is then used as a final check (effectively treating the unit as a cylinder). I'll try to decypher the code further. If others want to have a look, the code is around here:
.text:004116AE 8B 15 5C 28 4A 00 mov edx, pUnitPos
...
[[User:Seb76|Seb76]] 13:24, 10 April 2008 (PDT)

----

I'm inclined to agree with you, though I'm not much good at reading through executable code. :( I hit on the same idea on my [[User_talk:Bomb_Bloke|talk page]]... I've got some notes in there about how I think the firing system works, if you could find code to back it up I'd be a happy boy.

It's something of a long winded work-in-progress ramble, and I'm sure some parts are confusing and/or dead wrong, but with any luck you can make some sort of sense of it. :) - [[User:Bomb Bloke|Bomb Bloke]] 18:34, 11 April 2008 (PDT)

----

[[Image:Loftemps.png|thumb|right]]I mentionned it earlier but got no real feedback so I'm adding a new section for it ;)
It looks like it is the loftemps entry used for collision detection with bullets. The main page says that setting it to 37 make the shots go right through the guys. If you have a look at the entry, you'll see why... The interesting thing is that the big units do not have special entries (unitref is common for all 4 parts so it would not have been possible to do otherwise) so a shot should be able to go through them (between the 4 parts). However, for the shot to be almost horizontal (or vertical) and traveling at the frontier between tiles (to go between the 4 "collision" circles), the shot should come from far far away so it is not likely to happened. Also depending on how the visibility check is performed, it may explain why alien suddenly disappeared when messing with the value (see discussion upper in this page). I suspect it is done using some kind of raytracing between the center of the 2 tiles (between the current unit and the target); so if the loftemps entry for the target has a "hole" in its center, it may become invisible. [[User:Seb76|Seb76]] 07:00, 1 June 2008 (PDT)

----

I just edited unitref 048 and 052 of all my soldiers to 0 and the aliens never tried to shoot at me. When I edited 048 to 0 for all the Sectoids on a mission, my soldiers couldn't see them anymore (only takes effect the following round if edited in unitef.dat, but surprisingly aliens remain visible to you during their movement phase). Since loftemps 0 is an empty cell, the results make perfect sense. A value of 76 (both 48&52) makes aliens disappear too. I'm not sure what the threshold is for disappearing, but a 3x3 block (loftemps 1) is still enough to be seen. --[[User:Zombie|Zombie]] 15:08, 17 August 2008 (PDT)

----

Am I understanding correctly... for purposes of shots hitting, we're all "barrels" with a specific diameter (i.e. [[LOFTEMPS.DAT]] 2-5), height ([49]), and distance (float) off the ground ([51])? Right or wrong, it sounds like this is finally pretty sown up, excellent work. We could update the page's entries. I wonder why they repeated this value twice (i.e. [48] and [52] always the same)... maybe they once considered the possibility of a unit whose diameter can change from turn to turn? If so, some other heretofore unfathomable UNITREF bit or byte may have been intended to dictate whether they're currently using the diameter at [48] or [52]. -[[User:MikeTheRed|MikeTheRed]] 17:06, 17 August 2008 (PDT)

----

While I've no problem believing [48] is a LOF template reference, I hadn't added it to the main page because I wanted to be sure as to it's relationship with [52].

See, at present, all we know about [52] is that it's the same as [48]. We haven't seen any effects from changing it.

What I ''suspect'' is that one offset might be used for shots traveling along an angle parallel to the target, and one offset might be used for shots traveling perpendicular. This would basically allow units to be effectively oval shaped (or it would, if [48] and [52] weren't the same for all units).

Just one of those things that I never got around to finishing the testing on. Would be dead easy to check, though.

There's still a little more to be researched before the entirety of the firing system is understood (see my talk page for a rambling explanation as to what IS known), but that's pretty much the basics of it.

- [[User:Bomb Bloke|Bomb Bloke]] 19:51, 17 August 2008 (PDT)

----

BB and others, see my edits for [48]. Does it make sense? In particular, I estimated pixel width from that little LOFTEMPS .png by magnifying it a ton. Any and all comments or edits welcomed. It's interesting that the silacoid has the highest width, but a low cross-section - did anyone see the Star Trek TOS show with the very short, wide silicon aliens? -[[User:MikeTheRed|MikeTheRed]] 22:53, 23 August 2008 (PDT)

----

Yes, you got the LOF widths correct. Though as you mentioned, they're only accurate assuming you're firing head on at your targets (as the templates aren't perfect circles, their width varies from other angles).

I threw in the kneeling soldier stats and made a note concerning large units.

- [[User:Bomb Bloke|Bomb Bloke]] 22:21, 24 August 2008 (PDT)

== Offset 0x3C ==

I have a gut feeling it is related to the panic/berserk status of the unit... Any volunteer for testing? [[User:Seb76|Seb76]] 10:36, 22 March 2008 (PDT)

----

Made a save where all soldiers had no morale. Ended turn, most of them panicked etc. Saved the game but that offset still came up as 0. Might only be flagged at runtime.

- [[User:Bomb Bloke|Bomb Bloke]] 18:01, 26 May 2008 (PDT)

----

I checked and indeed the game sets and clears it in the same turn so it is always 0 in a savegame and hence there is no 'black box' way of confirming it. I can provide disassembly screenshots if you want proofs however ;) [[User:Seb76|Seb76]] 05:45, 28 May 2008 (PDT)
:Actually after some thinking, it _might_ be possible... If you set the value to 3 for all entries, everyone may go berserk, with 2 they should run in fear and 1, they'll just crap their pants in place... [[User:Seb76|Seb76]] 07:09, 28 May 2008 (PDT)

----

I tried it, and indeed my units did exactly that (at the start of their next turn - not that of the aliens).

- [[User:Bomb Bloke|Bomb Bloke]] 21:08, 28 May 2008 (PDT)

== Offset 0x71 ==
Hmm, the code checks this offset before applying stun damage... It looks more like an 'immune to stun damage' flag then. Strange... [[User:Seb76|Seb76]] 13:48, 7 April 2008 (PDT)

----

By memory, the only things that use this are X-Com HWPs (which shouldn't have stun applied). It does toggle inventory access as described though it wouldn't surprise me if it also toggled stun damage.

- [[User:Bomb Bloke|Bomb Bloke]] 05:46, 8 April 2008 (PDT)

:OK, I located the check and it is exactly what happens. BTW, if you want to try something, try to patch this with nops (0x90):
.text:00412A20 A8 40 test al, 40h
.text:00412A22 0F 85 00 02 00 00 jnz exit ; default
:It should enable inventory screen for memory controlled units (could not test since I have no save files with psy units...) [[User:Seb76|Seb76]] 11:37, 8 April 2008 (PDT)

:: So, to be clear, is this the location of the inventory screen check for mind controlled alien units? And here you are disabling the check by overwriting it with NOPS? Is there a nearby section of code that does the same check for tanks? I would like to be able to override this tank inventory check in order to play with [[User:Spike#Tank mods|Tank mods]]. It looks like NOPing the check logic is the right way to do it, since if instead I toggled the 0x71 flag for the tanks, they would than also become vulnerable to Stun? Though I also I think read somewhere that if you get to the inventory screen of a tank, the game crashes. It doesn't crash if you get to the inventory screen of an Alien large unit via the Alien Inventory or Alien Pets hacks (not sure which) in your UFOExtender. I was able to arm Reapers with dual Heavy Plasma or dual Blaster Launchers. (Unpleasant. They have 0% FA so they have to run up to you and spray with the Heavy Plasma. Not a problem with the Blaster Launcher.) [[User:Spike|Spike]] 13:59, 20 August 2009 (EDT)

== Offset 0xB ==
The value is used together as an offset to [[TERRAIN|MCDData]] offset 39 (describing TUs required to cross a tile walking/flying/sliding) so it most likely represent the way the unit moves. Still needs testing. [[User:Seb76|Seb76]] 13:27, 23 May 2008 (PDT)

----

I took a look at it for Snakemen and Silacoids, it's still 0 (same as it is for everything else).

But that doesn't mean it remains at 0 when the game's running. Do you mean to say that the value here + 39 = the offset in the MCD array that says how many TUs were required to move past any given obstacles in the current map location?

(That is, you'd expect to see a 2 there for sliding units?)

- [[User:Bomb Bloke|Bomb Bloke]] 05:14, 25 May 2008 (PDT)

----

Yep, exactly like that. Also it checks if the value is 0xff and prevent movement in that case. I'll try a live check with a debugger when I encounter snakemen. Maybe it's a part of code that was implemented but not put into usage. [[User:Seb76|Seb76]] 05:20, 25 May 2008 (PDT)
:Did the check and the value is indeed zero even for snakemen... BTW, is the movement type really working? I mean has anybody ever checked that e.g. snakemen really use different TU amount for tiles where TU usage is not the same between crawling and walking? [[User:Seb76|Seb76]] 06:43, 25 May 2008 (PDT)

----

Truth be told I don't remember reading of anyone doing the tests, so I had a go myself.

I tried first with the Avenger ramp, stuck it up in the air and had soldiers walk/fly onto it. Made no effect to their TU usage.

Next I rigged a Snakeman mission in the arctic, stuck one of them in the middle of a pond. It wouldn't move on it's own, and I couldn't move it under mind control.

So then I set 0xB to 2 just for that unit, and hey presto! Suddenly it was able to move freely, either under my control or otherwise. That's certainly the movement type flag... It's just not set in practise.

Still, now I'm wondering if 2 really was for sliders... It doesn't make sense that "fliers" (which I guess was supposed to include the likes of CyberDiscs, which "hover" even when on the ground) wouldn't be able to cross water, yet Snakemen could. Perhaps it should be the other way around?

- [[User:Bomb Bloke|Bomb Bloke]] 19:22, 25 May 2008 (PDT)

----

Note that there are some tiles that have 0 MP cost for sliders. - [[User:Zaimoni|Zaimoni]] 22:28, 25 May 2008 (CDT)

: Yeah, I guess that puts the clincher on it. Only fliers would really be totally unhindered by ground rubble. I've tweaked the MCD details page accordingly. - [[User:Bomb Bloke|Bomb Bloke]] 05:25, 26 May 2008 (PDT)

----

Hehe, I knew it couldn't be anything else but movement type. Yet another entry for known bugs ;) I'll check if it's possible to reenable the feature. It'll depends if it's a bug or if it was voluntarily removed I guess... [[User:Seb76|Seb76]] 04:37, 26 May 2008 (PDT)
: Did a quick check and can confirm what is said in [[GEOSCAPE.EXE#Alien_Stats|Alien Stats]] page. Offset 0xB is filled with the 3rd "unknown" value of alien stats. It is set to 0 for all entries. Could not find any other place where it could possibly be set to another value. [[User:Seb76|Seb76]] 05:17, 26 May 2008 (PDT)

----

So it's just a matter of tweaking that for all relevant units, then. However, I reckon it was left unused intentionally - I doubt the map files really contain enough variety to make it worth including.

- [[User:Bomb Bloke|Bomb Bloke]] 05:25, 26 May 2008 (PDT)

----

Since TFTD was done later with the same engine, perhaps it makes use of this? However, given that a different team made it ([http://www.lasersquadnemesis.com/AboutUs.htm Terror from the Deep was developed by Microprose using code licensed by Mythos]), developers may not have known the feature was available... [[User:Seb76|Seb76]] 07:25, 28 May 2008 (PDT)

----

I took a quick check, and sure enough found a Hallucinoid (the big flying squid thing) set to 2.

- [[User:Bomb Bloke|Bomb Bloke]] 21:31, 28 May 2008 (PDT)

== Offset 0x47 ==

The only use I could find is that of updating [[SOURCEMP.DAT|mobile light sources]] (or something like that) when the unit dies/is rendered unconscious. Could not find anything else about this flag. [[User:Seb76|Seb76]] 05:24, 29 May 2008 (PDT)

:Good work there. As a general statement, can I say - I've been waiting for somebody to disassemble XCOM :) -[[User:MikeTheRed|MikeTheRed]] 21:18, 30 May 2008 (PDT)

I sat down to do some tests with this, but didn't bother too read to closely... I was selecting/moving units around when I probably shoulda been shooting at them.

Oh well. For the record:

Moving a unit causes a light check to be done on all your units. You may not see this light if one of your units is standing in a fog-of-war covered zone (say you just mind controlled an alien and haven't selected it yet).

Selecting a unit does a fog-of-war check concerning what it can see, but does not do a light check.

Whatever this offset is has no effect on the light produced by your units, or the aliens units. Your active guys ALWAYS fully illuminate their tile (even if this is 0) and the aliens provide no illumination at all. Will have to do some tests concerning what happens when you shoot them, but it seems odd: If a unit is dead I'd expect a full light check to be done, since the unit isn't "active" it won't produce light, so I don't see how this offset is helpful there... You can't just remove the light values for this one unit because you might interfere with other nearby light sources, so you really have to calculate them all from scratch.

But likewise it seems [[TERRAIN|MCD[58/3A]]] is similar; a street lamp is set to 1, a normal lamp to 10, but they both provide maximum illumination.

Perhaps the programmers changed their mind about the lighting system at some point? Dunno.

- [[User:Bomb Bloke|Bomb Bloke]] 07:03, 20 June 2008 (PDT)

:Some of your note reminds me of what I wrote at [[Night_Missions#Personal_lighting]] ... does that help any? (probably not) -[[User:MikeTheRed|MikeTheRed]] 16:01, 20 June 2008 (PDT)

== On Fire Flag or Timer ? ==

Do we have any idea where a flag is set to show the unit is on fire? This is persistent between saved games so it must be stored in a file somewhere. Possibly UNITPOS.DAT? It could be a flag, but more likely is either a countdown timer for turns remaining on fire, (values 1-5?), or a "what turn do I stop being on fire" timer value (like a grenade timer).

I have uploaded a saved game file with a burning Aquatoid if anyone wants to take a look. I just don't have the right diff tools. Maybe with the Hex Workshop template... [[User:Spike|Spike]] 19:05, 10 March 2009 (CDT)

:Offset 114 in Unitref holds that data. --[[User:Zombie|Zombie]] 19:15, 10 March 2009 (CDT)

:: Sorry I did not read the article carefully enough. It's in there. [[User:Spike|Spike]] 19:16, 10 March 2009 (CDT)

114 / 72: If not 0, then unit is on fire, and will burn for this amount of turns.

== Floating Civilians ==

Civilians float 2 units off the ground, like Floaters and Cyberdisks. Soldiers don't. Should we consider this to be a bug? [[User:Spike|Spike]] 13:41, 20 August 2009 (EDT)

:Probably. I really doubt it's an intentional feature. --[[User:Zombie|Zombie]] 23:09, 20 August 2009 (EDT)

== Remembering morale vs health and pain killers ==

The game remembers whether a health loss has or has not been used to regain morale via pain killers. Presumably this is stored somewhere in UNITREF.DAT? [[User:Spike|Spike]] 10:30, 5 September 2009 (EDT)

== TFTD ==

It appears the name string starts at the same point in TFTD save points, which leads me to believe that the extra bytes are probably just appended at the end of the file, without much changing in the first 124 bytes per entry, anyone know what these extra 8 bytes might represent? - [[User:Hatfarm|Hatfarm]]

----

They are indeed appended. My battlescape editor deals with TFTD's UnitRef by just adjusting for the larger record size, and then ignoring the extra bytes completely - didn't need to do anything else to make it all match up. I've yet to actually look at some sample values in order to work out what they might be for.

Incidently, you can insert signatures into your postings using four tildes (<nowiki>~~~~</nowiki>). - [[User:Bomb Bloke|Bomb Bloke]] 21:48, 20 January 2010 (EST)

== TFTD's extra bytes ==

It appears that byte 126 is a bit flag of some sort as I have mostly seen values of 1 and 0 for it, but others have appeared. I saved a single mission at several different times and each one had 0 or 1, but a terror mission save had some different values for this, Like 0x20 and 0x4F. I tried adjusting it and checking the saved game, but nothing seemed to change...

Byte 124 I've seen values of 0,4,6,7,0x0A and 0x0E. No idea what these mean, and changing them did not do anything for me.

They appear to only be for Soldiers as well, none of the aliens in any of my saved games have values for these.

SOLDIER.DAT (TFTD)

2010-06-04T14:24:04Z

Hatfarm: /* Structure */

== General Notes ==

SOLDIER.DAT has a fixed structure of 250 entries of 70 bytes each. (Only a maximum of 250 soldiers can be had). Thus it is always 17,500 bytes long (250x70).

Values are presented according to byte count (0 to 69) followed by the equivalent hex offset (00 to 45) 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!

Unfortunately, this file is not conveniently ordered like Enemy Unknown's file so everything is just jumbled together.

== Structure ==
0 / 00: How much the MC Skill changed in the last month

1 / 01: Time Unit Improvement

2 / 02: In MC Implantation Flag

3 / 03: Promotion Flag

4 / 04: Health Improvement

5 / 05: Strength Improvement

6-7 / 06-07: Base Reference using values from LOC.DAT for where soldier is. First base is always 0 (first entry in [[LOC.DAT]]). Value of FF means the soldier is being transferred.

8-9 / 08-09: Craft Reference

10-11 / 0A-0B: Rank

12-13 / 0C-0D: Craft soldier was assigned to before being wounded and spending time in the infirmary. Half-implemented feature or not used.

14-15 / 0E-0F: Kills

16-17 / 10-11: Wound Recovery

18-19 / 12-13: Missions

20-21 / 14-15: Soldier Value

22 / 16: Always 0 except for existing soldiers being transferred, in which case it equals the LOC.DAT value for destination base.

23 / 17: Stamina Improvement

24 / 18: Reaction Improvement

25 / 19: Firing Accuracy Improvement

26 / 1A: Initial Time Units

27 / 1B: Initial Health

28 / 1C: Initial Stamina

29 / 1D: Initial Throwing Accuracy

30 / 1E: Armor

31 / 1F: Gender

32 / 20: Race

33 / 21: Initial Firing Accuracy

34 / 22: Initial Strength

35-61 / 23-3D: Name. 21 characters can be entered in-game, 27 via hex editing. Does not need to be null terminated.

62 / 3E: Bravery Improvement

63 / 3F: Throwing Accuracy Improvement

64 / 40: Initial Bravery

65 / 41: MC Skill

66 / 42: Melee Accuracy Improvement

67 / 43: MC Strength

68 / 44: Initial Melee Accuracy

69 / 45: Initial Reactions

== See Also ==

[[SOLDIER.DAT]]

[[Saved Game Files]]

[[Category:Game Files (TFTD)]]

BASE.DAT (TFTD)

2010-05-21T04:17:19Z

Hatfarm: /* Other */

==Structure==
'''BASE.DAT:''' Each entry is 296 Bytes long.

==Name==

'''00-0E:''' Base Name, pretty obvious.

'''0F:''' Null character if the Base Name uses all 15 characters. If this byte is non-0, the base name will happily overflow and read from the item quantities.

==Stores==

'''10-D3:''' Quantity of each item available at that base (signed 2-byte little-endian integers; see explanation in UFO section for details).

10 Ajax Launchers
12 D.U.P. Head Launcher
14 Craft Gas Cannon
16 P.W.T. Cannon
18 Gauss Cannon
1A Sonic Oscillator
1C Ajax Torpedoes
1E D.U.P. Head Torpedoes
20 Gas Rounds(x50)
22 P.W.T Ammo
24 Coelacanth/G. Cannon
26 Coelacanth/Aqua Jet
28 Coelacanth/Gauss
2A Displacer /Sonic
2C Displacer /P. W. T.
2E Dart Gun
30 Dart Clip
32 Jet Harpoon
34 Harpoon Clip
36 Gas Cannon
38 GC-AP Bolts
3A GC-HE Bolts
3C GC-Phosphorous Bolts
3E Hydro-Jet Cannon
40 HJ-AP Ammo
42 HJ-HE Ammo
44 HJ-P Ammo
46 Torpedo Launcher
48 Small Torpedo
4A Large Torpedo
4C Phosphor Torpedo
4E Gauss Pistol
50 Gauss Rifle
52 Heavy Gauss
54 Magna-Blast Grenade
56 Dye Grenade
58 Particle Disturbance Grenade
5A Magna-Pack Explosive
5C Particle Disturbance Sensor
5E Medi-Kit
60 M.C. Disruptor
62 Thermal Tazer
64 Chemical-flare
66 Vibro Blade
68 Thermic Lance
6A Heavy Thermic Lance
6C ''(invalid - prints garbage if used)''
6E ''(invalid - prints garbage if used)''
70 ''(invalid - prints garbage if used)''
72 Sonic Cannon
74 Cannon Power Clip
76 Sonic-Blasta Rifle
78 Blasta Power Clip
7A Sonic Pistol
7C Pistol Power Clip
7E Disruptor Pulse Launcher
80 Disruptor Ammo
82 Thermal Shok Launcher
84 Thermal Shok Bomb
86 Sonic Pulser
88 Zrbite
8A M.C. Reader
8C Gauss Pistol Clip
8E Gauss Rifle Clip
90 Heavy Gauss Clip
92 Aquatoid Corpse
94 Gill Man Corpse
96 Lobster Man Corpse
98 Tasoth Corpse
9A Calcinite Corpse
9C Deep One Corpse
9E Bio-Drone Corpse
A0 Tentaculat Corpse
A2 Triscene Corpse
A4 Hallucinoid Corpse
A6 Xarquid Corpse
A8 ''(invalid - prints ' Technician' if used)''
AA ''(invalid - prints ' Squad Leader' if used)''
AC ''(invalid - prints ' Soldier' if used)''
AE ''(invalid - prints ' Terrorist' if used)''
B0 Ion-Beam Accelerators
B2 Magnetic Navigation
B4 Alien Sub Construction
B6 Alien Cryogenics
B8 Alien Cloning
BA Alien Learning Arrays
BC Alien Implanter
BE Examination Room
C0 Aqua Plastics
C2 Alien Re-animation Zone
C4 Plastic Aqua Armour
C6 Ion Armour
C8 Mag. Ion Armour
CA Solid Harpoon Bolts
CC Aqua Jet Missiles
CE P.W. Torpedo
D0 Gauss Cannon Ammo (for Coelacanth/G. Cannon)
D2 Gauss Cannon Ammo (for Craft Gauss Cannon)

==Base Detection Values==

'''D4:''' Short range detection value (%).

'''D6:''' Long range detection value (%).

'''D8:''' Transmission Resolver detection value (%).

Each base detection value byte is a low byte, followed by a high byte which is null (x0).

Detection values are identical to XCom1:

Possible decimal values are 0/10/20/30 for Short, 0/20 for Long, 0/100 for Transmission Resolver. The XCom1 Radar Stacking Bug still applies - there is no detection advantage to building multiple detection modules of the same type.

==Facilities==

'''DA-FD:''' The next offsets are arranged so they're easier to understand. They are for facilities in the base:

{| {{stdTable}} border="1" cellpadding="5" style="border: 0px solid; text-align: center" width="210"
|-
| DA || DB || DC || DD || DE || DF
|-
| E0 || E1 || E2 || E3 || E4 || E5
|-
| E6 || E7 || E8 || E9 || EA || EB
|-
| EC || ED || EE || EF || F0 || F1
|-
| F2 || F3 || F4 || F5 || F6 || F7
|-
| F8 || F9 || FA || FB || FC || FD
|}

The possible values are as follows:
00 - Air Lock
01 - Living Quarters
02 - Laboratory
03 - Workshop
04 - Standard Sonar
05 - Wide Array Sonar
06 - Torpedo Defences
07 - General Stores
08 - Alien Containment
09 - Gauss Defences
0A - Sonic Defences
0B - P.W.T. Defences
0C - Bomb Shield
0D - M.C. Defences
0E - M.C.-Lab
0F - Transmission Resolver
10 - Sub Pen (Top Left)
11 - Sub Pen (Top Right)
12 - Sub Pen (Bottom Left)
13 - Sub Pen (Bottom Right)
FF - Empty

'''FE-121:''' The next offsets represent the days until a facility is completed. They're set up the same way:
{| {{stdTable}} border="1" cellpadding="5" style="border: 0px solid; text-align: center" width="210"
|-
| FE || FF || 100 || 101 || 102 || 103
|-
| 104 || 105 || 106 || 107 || 108 || 109
|-
| 10A || 10B || 10C || 10D || 10E || 10F
|-
| 110 || 111 || 112 || 113 || 114 || 115
|-
| 116 || 117 || 118 || 119 || 11A || 11B
|-
| 11C || 11D || 11E || 11F || 120 || 121
|}

Possible values are 00 to FF. Empty spaces must have a FF value in their corresponding offset.

==Personnel==

'''0122:''' Number of technicians (00-FF).

'''0123:''' Number of scientists (00-FF).

==Other==
'''0124:''' Disabled flag, if 1 the base is disabled, if 0 the base is in use. 
'''0125-0127:''' Unknown.

==See Also==
* [[BASE.DAT]]

* [[Saved Game Files]]

[[Category:Game Files (TFTD)]]

BASE.DAT (TFTD)

2010-05-21T04:16:34Z

Hatfarm: /* Other */

==Structure==
'''BASE.DAT:''' Each entry is 296 Bytes long.

==Name==

'''00-0E:''' Base Name, pretty obvious.

'''0F:''' Null character if the Base Name uses all 15 characters. If this byte is non-0, the base name will happily overflow and read from the item quantities.

==Stores==

'''10-D3:''' Quantity of each item available at that base (signed 2-byte little-endian integers; see explanation in UFO section for details).

10 Ajax Launchers
12 D.U.P. Head Launcher
14 Craft Gas Cannon
16 P.W.T. Cannon
18 Gauss Cannon
1A Sonic Oscillator
1C Ajax Torpedoes
1E D.U.P. Head Torpedoes
20 Gas Rounds(x50)
22 P.W.T Ammo
24 Coelacanth/G. Cannon
26 Coelacanth/Aqua Jet
28 Coelacanth/Gauss
2A Displacer /Sonic
2C Displacer /P. W. T.
2E Dart Gun
30 Dart Clip
32 Jet Harpoon
34 Harpoon Clip
36 Gas Cannon
38 GC-AP Bolts
3A GC-HE Bolts
3C GC-Phosphorous Bolts
3E Hydro-Jet Cannon
40 HJ-AP Ammo
42 HJ-HE Ammo
44 HJ-P Ammo
46 Torpedo Launcher
48 Small Torpedo
4A Large Torpedo
4C Phosphor Torpedo
4E Gauss Pistol
50 Gauss Rifle
52 Heavy Gauss
54 Magna-Blast Grenade
56 Dye Grenade
58 Particle Disturbance Grenade
5A Magna-Pack Explosive
5C Particle Disturbance Sensor
5E Medi-Kit
60 M.C. Disruptor
62 Thermal Tazer
64 Chemical-flare
66 Vibro Blade
68 Thermic Lance
6A Heavy Thermic Lance
6C ''(invalid - prints garbage if used)''
6E ''(invalid - prints garbage if used)''
70 ''(invalid - prints garbage if used)''
72 Sonic Cannon
74 Cannon Power Clip
76 Sonic-Blasta Rifle
78 Blasta Power Clip
7A Sonic Pistol
7C Pistol Power Clip
7E Disruptor Pulse Launcher
80 Disruptor Ammo
82 Thermal Shok Launcher
84 Thermal Shok Bomb
86 Sonic Pulser
88 Zrbite
8A M.C. Reader
8C Gauss Pistol Clip
8E Gauss Rifle Clip
90 Heavy Gauss Clip
92 Aquatoid Corpse
94 Gill Man Corpse
96 Lobster Man Corpse
98 Tasoth Corpse
9A Calcinite Corpse
9C Deep One Corpse
9E Bio-Drone Corpse
A0 Tentaculat Corpse
A2 Triscene Corpse
A4 Hallucinoid Corpse
A6 Xarquid Corpse
A8 ''(invalid - prints ' Technician' if used)''
AA ''(invalid - prints ' Squad Leader' if used)''
AC ''(invalid - prints ' Soldier' if used)''
AE ''(invalid - prints ' Terrorist' if used)''
B0 Ion-Beam Accelerators
B2 Magnetic Navigation
B4 Alien Sub Construction
B6 Alien Cryogenics
B8 Alien Cloning
BA Alien Learning Arrays
BC Alien Implanter
BE Examination Room
C0 Aqua Plastics
C2 Alien Re-animation Zone
C4 Plastic Aqua Armour
C6 Ion Armour
C8 Mag. Ion Armour
CA Solid Harpoon Bolts
CC Aqua Jet Missiles
CE P.W. Torpedo
D0 Gauss Cannon Ammo (for Coelacanth/G. Cannon)
D2 Gauss Cannon Ammo (for Craft Gauss Cannon)

==Base Detection Values==

'''D4:''' Short range detection value (%).

'''D6:''' Long range detection value (%).

'''D8:''' Transmission Resolver detection value (%).

Each base detection value byte is a low byte, followed by a high byte which is null (x0).

Detection values are identical to XCom1:

Possible decimal values are 0/10/20/30 for Short, 0/20 for Long, 0/100 for Transmission Resolver. The XCom1 Radar Stacking Bug still applies - there is no detection advantage to building multiple detection modules of the same type.

==Facilities==

'''DA-FD:''' The next offsets are arranged so they're easier to understand. They are for facilities in the base:

{| {{stdTable}} border="1" cellpadding="5" style="border: 0px solid; text-align: center" width="210"
|-
| DA || DB || DC || DD || DE || DF
|-
| E0 || E1 || E2 || E3 || E4 || E5
|-
| E6 || E7 || E8 || E9 || EA || EB
|-
| EC || ED || EE || EF || F0 || F1
|-
| F2 || F3 || F4 || F5 || F6 || F7
|-
| F8 || F9 || FA || FB || FC || FD
|}

The possible values are as follows:
00 - Air Lock
01 - Living Quarters
02 - Laboratory
03 - Workshop
04 - Standard Sonar
05 - Wide Array Sonar
06 - Torpedo Defences
07 - General Stores
08 - Alien Containment
09 - Gauss Defences
0A - Sonic Defences
0B - P.W.T. Defences
0C - Bomb Shield
0D - M.C. Defences
0E - M.C.-Lab
0F - Transmission Resolver
10 - Sub Pen (Top Left)
11 - Sub Pen (Top Right)
12 - Sub Pen (Bottom Left)
13 - Sub Pen (Bottom Right)
FF - Empty

'''FE-121:''' The next offsets represent the days until a facility is completed. They're set up the same way:
{| {{stdTable}} border="1" cellpadding="5" style="border: 0px solid; text-align: center" width="210"
|-
| FE || FF || 100 || 101 || 102 || 103
|-
| 104 || 105 || 106 || 107 || 108 || 109
|-
| 10A || 10B || 10C || 10D || 10E || 10F
|-
| 110 || 111 || 112 || 113 || 114 || 115
|-
| 116 || 117 || 118 || 119 || 11A || 11B
|-
| 11C || 11D || 11E || 11F || 120 || 121
|}

Possible values are 00 to FF. Empty spaces must have a FF value in their corresponding offset.

==Personnel==

'''0122:''' Number of technicians (00-FF).

'''0123:''' Number of scientists (00-FF).

==Other==
0124: Disabled flag, if 1 the base is disabled, if 0 the base is in use.
'''0125-0127:''' Unknown.

==See Also==
* [[BASE.DAT]]

* [[Saved Game Files]]

[[Category:Game Files (TFTD)]]

Psi-Amp

2010-05-15T16:49:49Z

Hatfarm:

The Psi-Amp, or Psionic Amplifier, is device that allows X-COM soldiers to access and make use of the same psionic powers that are available to [[Ethereal]]s and high ranking [[Sectoid]]s. Unlike the [[Mind Probe]], the Psi-Amp can only be used by soldiers with [[Psionic Skill]].

The amplifier allows soldiers to attack enemies with two types of mental attacks. Panic and Mind Control. Panic, the easiest of the two attacks, saps a unit's morale, and puts it in a prime position to panic or go berserk. Panic attacks are an efficient means of training Psi Skill.

Mind control takes direct control over the target's actions, but is very difficult to perform until some skill is built up.

The range of the amplifier covers the entire field and does not require line of sight to operate. However, targets for the amp must be sighted before they can be attacked.

The prerequisite for researching the Psi-Amp is the [[Psionic Laboratory|Psi-Lab]].

This item appears in ''[[X-COM|UFO: Enemy Unknown]]''. For the ''[[TFTD|Terror from the Deep]]'' equivalent, refer to the [[M.C. Disruptor]].

== Stats ==
<table><tr><td>[[Image:BIGOBS33.GIF|left|64 px]]</td><td>
*Size: 3 high x 1 wide
*Weight: 10
*TUs:
**25 TUs per use.
*[[Buying/Selling/Transferring#Manufacturable_Prices|Manufacturing]]: $160,000 for parts, 500 Engineer Hours, 1 Elerium
*Sell Price: $194,700</td></tr></table>

== How To Use ==
During combat, click on the Psi-Amp, select the type of attack, and select a target unit with the cursor.

There are two types of psionic attack:

; PANIC UNIT : If the attack is successful it will reduce the target's morale and may cause it to panic.
; MIND CONTROL : If this is successful, then you will gain immediate control of the enemy unit as if it was one of your own units (except that you cannot directly access the object screen). It is more difficult to control an alien than to panic it, but soldiers with high Psi Skill (say 60 or more) and Strength can capture many additional "soldiers" during a mission. See [[Psionics]] for the specific formulas.

Unlike other combat actions, failure with any of the above attacks will still count towards experience.

Note: if you mind control a large unit, such as a [[Cyberdisc]], be sure to get all four quarters of the unit under control.
If not, once moved, the Cyberdisc may shoot the 'Alien' quarters of itself because of its high reaction stat.
Other large aliens (such as the [[Sectopod]]) do the same, but the [[Cyberdisc]] is deadly because of its explosive nature. Melee aliens like the [[Reaper]] will not attack themselves.

== See Also ==
*[[Psionic Laboratory|Psi-Lab]]
*[[Psionics]]
*[[Psionic Skill]]
*[[Psionic Strength]]

{{Equipment (UFO Defense) Navbar}}
[[Category:Equipment (EU)]]
[[Category:Research (EU)]]

UP001.SPK-UP042.SPK

2010-02-24T13:30:49Z

Hatfarm: /* General Information */

==General Information==
Images used by the [[UFOpaedia]], stored in the [[Image_Formats#SPK|SPK format]]. They use palette 3.

==Images==
<gallery caption="UP001.SPK-UP042.SPK UFOpaedia Images" widths="200px" perrow="3">
Image:UP001.gif|UP001.SPK - [[Avenger]]
Image:UP002.gif|UP002.SPK - [[Interceptor]]
Image:UP003.gif|UP003.SPK - [[Lightning]]
Image:UP004.gif|UP004.SPK - [[Skyranger]]
Image:UP005.gif|UP005.SPK - [[Firestorm]]
Image:UP006.gif|UP006.SPK - [[Stingray]]
Image:UP007.gif|UP007.SPK - [[Avalanche]]
Image:UP008.gif|UP008.SPK - [[Cannon]]
Image:UP009.gif|UP009.SPK - [[Fusion Ball Launcher]]
Image:UP010.gif|UP009.SPK - [[Laser Cannon]]
Image:UP011.gif|UP011.SPK - [[Plasma Beam]]
Image:UP012.gif|UP012.SPK - [[Celatid]]
Image:UP013.gif|UP013.SPK - [[Celatid]] autopsy
Image:UP014.gif|UP014.SPK - [[Chryssalid]]
Image:UP015.gif|UP015.SPK - [[Chryssalid]] autopsy
Image:UP016.gif|UP016.SPK - [[Ethereal]]
Image:UP017.gif|UP017.SPK - [[Ethereal]] autopsy
Image:UP018.gif|UP018.SPK - [[Floater]]
Image:UP019.gif|UP019.SPK - [[Floater]] autopsy
Image:UP020.gif|UP020.SPK - [[Muton]]
Image:UP021.gif|UP021.SPK - [[Muton]] autopsy
Image:UP022.gif|UP022.SPK - [[Reaper]]
Image:UP023.gif|UP023.SPK - [[Reaper]] autopsy
Image:UP024.gif|UP024.SPK - [[Sectoid]]
Image:UP025.gif|UP025.SPK - [[Sectoid]] autopsy
Image:UP026.gif|UP026.SPK - [[Sectopod]]
Image:UP027.gif|UP027.SPK - [[Sectopod]] autopsy
Image:UP028.gif|UP028.SPK - [[Silacoid]]
Image:UP029.gif|UP029.SPK - [[Silacoid]] autopsy
Image:UP030.gif|UP030.SPK - [[Snakeman]]
Image:UP031.gif|UP031.SPK - [[Snakeman]] autopsy
Image:UP032.gif|UP032.SPK - [[UFO Power Source]]
Image:UP033.gif|UP033.SPK - [[UFO Navigation]]
Image:UP034.gif|UP034.SPK - [[UFO Construction]]
Image:UP035.gif|UP035.SPK - [[Alien Food]]
Image:UP036.gif|UP036.SPK - [[Alien Reproduction]]
Image:UP037.gif|UP037.SPK - [[Alien Entertainment]]
Image:UP038.gif|UP038.SPK - [[Alien Surgery]]
Image:UP039.gif|UP039.SPK - [[Examination Room]]
Image:UP040.gif|UP040.SPK - [[Alien Alloys]]
Image:UP041.gif|UP041.SPK - [[Cyberdisc]]
Image:UP042.gif|UP042.SPK - [[Cyberdisc]] autopsy
</gallery>

 

==See Also==
* [[GEOGRAPH]]
[[Category:Game Files]]

UP001.SPK-UP042.SPK

2010-02-24T05:09:09Z

Hatfarm: /* Images */

==General Information==
Images used by the [[UFOpaedia]], stored in the [[Image_Formats#SPK|SPK format]].

==Images==
<gallery caption="UP001.SPK-UP042.SPK UFOpaedia Images" widths="200px" perrow="3">
Image:UP001.gif|UP001.SPK - [[Avenger]]
Image:UP002.gif|UP002.SPK - [[Interceptor]]
Image:UP003.gif|UP003.SPK - [[Lightning]]
Image:UP004.gif|UP004.SPK - [[Skyranger]]
Image:UP005.gif|UP005.SPK - [[Firestorm]]
Image:UP006.gif|UP006.SPK - [[Stingray]]
Image:UP007.gif|UP007.SPK - [[Avalanche]]
Image:UP008.gif|UP008.SPK - [[Cannon]]
Image:UP009.gif|UP009.SPK - [[Fusion Ball Launcher]]
Image:UP010.gif|UP009.SPK - [[Laser Cannon]]
Image:UP011.gif|UP011.SPK - [[Plasma Beam]]
Image:UP012.gif|UP012.SPK - [[Celatid]]
Image:UP013.gif|UP013.SPK - [[Celatid]] autopsy
Image:UP014.gif|UP014.SPK - [[Chryssalid]]
Image:UP015.gif|UP015.SPK - [[Chryssalid]] autopsy
Image:UP016.gif|UP016.SPK - [[Ethereal]]
Image:UP017.gif|UP017.SPK - [[Ethereal]] autopsy
Image:UP018.gif|UP018.SPK - [[Floater]]
Image:UP019.gif|UP019.SPK - [[Floater]] autopsy
Image:UP020.gif|UP020.SPK - [[Muton]]
Image:UP021.gif|UP021.SPK - [[Muton]] autopsy
Image:UP022.gif|UP022.SPK - [[Reaper]]
Image:UP023.gif|UP023.SPK - [[Reaper]] autopsy
Image:UP024.gif|UP024.SPK - [[Sectoid]]
Image:UP025.gif|UP025.SPK - [[Sectoid]] autopsy
Image:UP026.gif|UP026.SPK - [[Sectopod]]
Image:UP027.gif|UP027.SPK - [[Sectopod]] autopsy
Image:UP028.gif|UP028.SPK - [[Silacoid]]
Image:UP029.gif|UP029.SPK - [[Silacoid]] autopsy
Image:UP030.gif|UP030.SPK - [[Snakeman]]
Image:UP031.gif|UP031.SPK - [[Snakeman]] autopsy
Image:UP032.gif|UP032.SPK - [[UFO Power Source]]
Image:UP033.gif|UP033.SPK - [[UFO Navigation]]
Image:UP034.gif|UP034.SPK - [[UFO Construction]]
Image:UP035.gif|UP035.SPK - [[Alien Food]]
Image:UP036.gif|UP036.SPK - [[Alien Reproduction]]
Image:UP037.gif|UP037.SPK - [[Alien Entertainment]]
Image:UP038.gif|UP038.SPK - [[Alien Surgery]]
Image:UP039.gif|UP039.SPK - [[Examination Room]]
Image:UP040.gif|UP040.SPK - [[Alien Alloys]]
Image:UP041.gif|UP041.SPK - [[Cyberdisc]]
Image:UP042.gif|UP042.SPK - [[Cyberdisc]] autopsy
</gallery>

 

==See Also==
* [[GEOGRAPH]]
[[Category:Game Files]]

UP001.SPK-UP042.SPK

2010-02-24T05:08:26Z

Hatfarm: /* Images */

==General Information==
Images used by the [[UFOpaedia]], stored in the [[Image_Formats#SPK|SPK format]].

==Images==
<gallery caption="UP001.SPK-UP042.SPK UFOpaedia Images" widths="200px" perrow="3">
Image:UP001.gif|UP001.SPK - [[Avenger]]
Image:UP002.gif|UP002.SPK - [[Interceptor]]
Image:UP003.gif|UP003.SPK - [[Lightning]]
Image:UP004.gif|UP004.SPK - [[Skyranger]]
Image:UP005.gif|UP005.SPK - [[Firestorm]]
Image:UP006.gif|UP006.SPK - [[Stingray]]
Image:UP007.gif|UP007.SPK - [[Avalanche]]
Image:UP008.gif|UP008.SPK - [[Cannon]]
Image:UP009.gif|UP009.SPK - [[Fusion Ball Launcher]]
Image:UP010.gif|UP009.SPK - [[Laser Cannon]]
Image:UP011.gif|UP011.SPK - [[Plasma Beam]]
Image:UP012.gif|UP012.SPK - [[Celatid]]
Image:UP013.gif|UP013.SPK - [[Celatid]] autopsy
Image:UP014.gif|UP014.SPK - [[Chryssalid]]
Image:UP015.gif|UP015.SPK - [[Chryssalid]] autopsy
Image:UP016.gif|UP016.SPK - [[Ethereal]]
Image:UP017.gif|UP017.SPK - [[Ethereal]] autopsy
Image:UP018.gif|UP018.SPK - [[Floater]]
Image:UP019.gif|UP019.SPK - [[Floater]] autopsy
Image:UP020.gif|UP020.SPK - [[Muton]]
Image:UP021.gif|UP021.SPK - [[Muton]] autopsy
Image:UP022.gif|UP022.SPK - [[Reaper]]
Image:UP023.gif|UP023.SPK - [[Reaper]] autopsy
Image:UP024.gif|UP024.SPK - [[Sectoid]]
Image:UP025.gif|UP025.SPK - [[Sectoid]] autopsy
Image:UP026.gif|UP026.SPK - [[Sectopod]]
Image:UP027.gif|UP027.SPK - [[Sectopod]] autopsy
Image:UP028.gif|UP028.SPK - [[Silacoid]]
Image:UP029.gif|UP029.SPK - [[Silacoid]] autopsy
Image:UP030.gif|UP029.SPK - [[Snakeman]]
Image:UP031.gif|UP031.SPK - [[Snakeman]] autopsy
Image:UP032.gif|UP032.SPK - [[UFO Power Source]]
Image:UP033.gif|UP033.SPK - [[UFO Navigation]]
Image:UP034.gif|UP034.SPK - [[UFO Construction]]
Image:UP035.gif|UP035.SPK - [[Alien Food]]
Image:UP036.gif|UP036.SPK - [[Alien Reproduction]]
Image:UP037.gif|UP037.SPK - [[Alien Entertainment]]
Image:UP038.gif|UP038.SPK - [[Alien Surgery]]
Image:UP039.gif|UP039.SPK - [[Examination Room]]
Image:UP040.gif|UP039.SPK - [[Alien Alloys]]
Image:UP041.gif|UP041.SPK - [[Cyberdisc]]
Image:UP042.gif|UP042.SPK - [[Cyberdisc]] autopsy
</gallery>

 

==See Also==
* [[GEOGRAPH]]
[[Category:Game Files]]

Talk:UNITREF.DAT

2010-01-21T02:23:33Z

Hatfarm: /* TFTD Support */

Talk:UNITREF.DAT

2010-01-21T02:23:15Z

Hatfarm: New section: TFTD Support

Anyone who has it - can we get listings of values for various aliens on the Unitref page, for some of the variables found in both Unitref and the Geoscape [[Talk:Overviews_of_Aliens|Alien stats]]? E.g. energy recharge (Unitref[35]), energy loss [45]... like what Danial did for Height. Some of it might go to NKF's redesigned [[Soldier]] page. I am trying to flesh out the Geoscape data so I know what everything is there (and can then extend it across difficulty levels). It has unlabelled fields with values, some of which I know must be these values... but there's no list for me to compare against. Thanks if you can help! ---[[User:MikeTheRed|MikeTheRed]] 19:37, 25 Nov 2005 (PST)

P.S. We probably should clean up this Discussion some time. I will if I find the time to make sure everything has made its way to wherever it should go.

----

== Offsets 0x30 & 0x34 ==

I've chopped out the majority of this page as it is no longer required. I'm keeping the heights chart in case it is required - I've also changed the "H-F" field to "H+F", as this actually makes sense.
[49] [51] "Tall" [48] | [49] [48]
Class Ht. Flt H+F Wide | Ht. Wide Area
--------- --- --- ---- ---- | --- ---- ----
Sectoid 16 0 16 2 | 16 2 32 Area=Ht.*Wide
Celatid 12 6 18 3 | 12 3 36
Hovertank* 12 6 18 4 | 12 4 48
Silacoid 10 0 10 5 | 10 5 50
Snakeman 18 0 18 3 | 18 3 54
Zombie 18 0 18 3 | 18 3 54
Cyberdisc 15 2 17 4 | 15 4 60
Ethereal 20 0 20 3 | 20 3 60 ''All Hover/Tanks in their
Chryssalid 21 0 21 3 | 21 3 63 ''class assumed to be same
Civilian 21 2 23 3 | 21 3 63 ''altho not tested yet
Floater 21 2 23 3 | 21 3 63
Muton 21 0 21 3 | 21 3 63
Tank* 16 0 16 4 | 16 4 64
Soldier 22 0 22 3 | 22 3 66
Reaper 23 0 23 4 | 23 4 92
Sectopod 23 0 23 4 | 23 4 92

Anyway, unitref[48] and unitref[52] remain somewhat of a mystery. Thus far we've assumed them to be the unit's width. Today I tried tinkering with [48] to see of this was correct. As I cranked it up, I found no change in my accuracy, or as to how the Sectoid target blocked line of fire to the tiles behind it.

When it reached the value of 37, however, the alien disappeared! I could not view it regardless of distance. In fact, I could even fire right through the tile it was standing on with no obstruction. The only sign that the alien was still there was the fact that my unit could not stand on the same square.

I lowered [48] a bit and tried viewing the alien from different distances, and found that it appeared in the same way as it usually would, regardless of the value used. It's simply the case that going to 37 or above makes the alien invisible.

I also tweaked [52] a bit, but found that it seemed to have no similar effects, if any at all.

Although I haven't tested this any further as yet, it might be possible to use this effect in reverse - Create an 'invisible' X-Com unit, and use it to observe how aliens act when they think we're not looking.

- [[User:Bomb Bloke|Bomb Bloke]] 00:44, 31 July 2006 (PDT)

----

I have a strong belief that offset 48 is nothing else but the loftemps.dat entry used for collision checking with bullets. A first check is done against the unit height (taking into account floating height, terrain height, kneeling). If the check is OK, the loftemps entry is then used as a final check (effectively treating the unit as a cylinder). I'll try to decypher the code further. If others want to have a look, the code is around here:
.text:004116AE 8B 15 5C 28 4A 00 mov edx, pUnitPos
...
[[User:Seb76|Seb76]] 13:24, 10 April 2008 (PDT)

----

I'm inclined to agree with you, though I'm not much good at reading through executable code. :( I hit on the same idea on my [[User_talk:Bomb_Bloke|talk page]]... I've got some notes in there about how I think the firing system works, if you could find code to back it up I'd be a happy boy.

It's something of a long winded work-in-progress ramble, and I'm sure some parts are confusing and/or dead wrong, but with any luck you can make some sort of sense of it. :) - [[User:Bomb Bloke|Bomb Bloke]] 18:34, 11 April 2008 (PDT)

----

[[Image:Loftemps.png|thumb|right]]I mentionned it earlier but got no real feedback so I'm adding a new section for it ;)
It looks like it is the loftemps entry used for collision detection with bullets. The main page says that setting it to 37 make the shots go right through the guys. If you have a look at the entry, you'll see why... The interesting thing is that the big units do not have special entries (unitref is common for all 4 parts so it would not have been possible to do otherwise) so a shot should be able to go through them (between the 4 parts). However, for the shot to be almost horizontal (or vertical) and traveling at the frontier between tiles (to go between the 4 "collision" circles), the shot should come from far far away so it is not likely to happened. Also depending on how the visibility check is performed, it may explain why alien suddenly disappeared when messing with the value (see discussion upper in this page). I suspect it is done using some kind of raytracing between the center of the 2 tiles (between the current unit and the target); so if the loftemps entry for the target has a "hole" in its center, it may become invisible. [[User:Seb76|Seb76]] 07:00, 1 June 2008 (PDT)

----

I just edited unitref 048 and 052 of all my soldiers to 0 and the aliens never tried to shoot at me. When I edited 048 to 0 for all the Sectoids on a mission, my soldiers couldn't see them anymore (only takes effect the following round if edited in unitef.dat, but surprisingly aliens remain visible to you during their movement phase). Since loftemps 0 is an empty cell, the results make perfect sense. A value of 76 (both 48&52) makes aliens disappear too. I'm not sure what the threshold is for disappearing, but a 3x3 block (loftemps 1) is still enough to be seen. --[[User:Zombie|Zombie]] 15:08, 17 August 2008 (PDT)

----

Am I understanding correctly... for purposes of shots hitting, we're all "barrels" with a specific diameter (i.e. [[LOFTEMPS.DAT]] 2-5), height ([49]), and distance (float) off the ground ([51])? Right or wrong, it sounds like this is finally pretty sown up, excellent work. We could update the page's entries. I wonder why they repeated this value twice (i.e. [48] and [52] always the same)... maybe they once considered the possibility of a unit whose diameter can change from turn to turn? If so, some other heretofore unfathomable UNITREF bit or byte may have been intended to dictate whether they're currently using the diameter at [48] or [52]. -[[User:MikeTheRed|MikeTheRed]] 17:06, 17 August 2008 (PDT)

----

While I've no problem believing [48] is a LOF template reference, I hadn't added it to the main page because I wanted to be sure as to it's relationship with [52].

See, at present, all we know about [52] is that it's the same as [48]. We haven't seen any effects from changing it.

What I ''suspect'' is that one offset might be used for shots traveling along an angle parallel to the target, and one offset might be used for shots traveling perpendicular. This would basically allow units to be effectively oval shaped (or it would, if [48] and [52] weren't the same for all units).

Just one of those things that I never got around to finishing the testing on. Would be dead easy to check, though.

There's still a little more to be researched before the entirety of the firing system is understood (see my talk page for a rambling explanation as to what IS known), but that's pretty much the basics of it.

- [[User:Bomb Bloke|Bomb Bloke]] 19:51, 17 August 2008 (PDT)

----

BB and others, see my edits for [48]. Does it make sense? In particular, I estimated pixel width from that little LOFTEMPS .png by magnifying it a ton. Any and all comments or edits welcomed. It's interesting that the silacoid has the highest width, but a low cross-section - did anyone see the Star Trek TOS show with the very short, wide silicon aliens? -[[User:MikeTheRed|MikeTheRed]] 22:53, 23 August 2008 (PDT)

----

Yes, you got the LOF widths correct. Though as you mentioned, they're only accurate assuming you're firing head on at your targets (as the templates aren't perfect circles, their width varies from other angles).

I threw in the kneeling soldier stats and made a note concerning large units.

- [[User:Bomb Bloke|Bomb Bloke]] 22:21, 24 August 2008 (PDT)

== Offset 0x3C ==

I have a gut feeling it is related to the panic/berserk status of the unit... Any volunteer for testing? [[User:Seb76|Seb76]] 10:36, 22 March 2008 (PDT)

----

Made a save where all soldiers had no morale. Ended turn, most of them panicked etc. Saved the game but that offset still came up as 0. Might only be flagged at runtime.

- [[User:Bomb Bloke|Bomb Bloke]] 18:01, 26 May 2008 (PDT)

----

I checked and indeed the game sets and clears it in the same turn so it is always 0 in a savegame and hence there is no 'black box' way of confirming it. I can provide disassembly screenshots if you want proofs however ;) [[User:Seb76|Seb76]] 05:45, 28 May 2008 (PDT)
:Actually after some thinking, it _might_ be possible... If you set the value to 3 for all entries, everyone may go berserk, with 2 they should run in fear and 1, they'll just crap their pants in place... [[User:Seb76|Seb76]] 07:09, 28 May 2008 (PDT)

----

I tried it, and indeed my units did exactly that (at the start of their next turn - not that of the aliens).

- [[User:Bomb Bloke|Bomb Bloke]] 21:08, 28 May 2008 (PDT)

== Offset 0x71 ==
Hmm, the code checks this offset before applying stun damage... It looks more like an 'immune to stun damage' flag then. Strange... [[User:Seb76|Seb76]] 13:48, 7 April 2008 (PDT)

----

By memory, the only things that use this are X-Com HWPs (which shouldn't have stun applied). It does toggle inventory access as described though it wouldn't surprise me if it also toggled stun damage.

- [[User:Bomb Bloke|Bomb Bloke]] 05:46, 8 April 2008 (PDT)

:OK, I located the check and it is exactly what happens. BTW, if you want to try something, try to patch this with nops (0x90):
.text:00412A20 A8 40 test al, 40h
.text:00412A22 0F 85 00 02 00 00 jnz exit ; default
:It should enable inventory screen for memory controlled units (could not test since I have no save files with psy units...) [[User:Seb76|Seb76]] 11:37, 8 April 2008 (PDT)

:: So, to be clear, is this the location of the inventory screen check for mind controlled alien units? And here you are disabling the check by overwriting it with NOPS? Is there a nearby section of code that does the same check for tanks? I would like to be able to override this tank inventory check in order to play with [[User:Spike#Tank mods|Tank mods]]. It looks like NOPing the check logic is the right way to do it, since if instead I toggled the 0x71 flag for the tanks, they would than also become vulnerable to Stun? Though I also I think read somewhere that if you get to the inventory screen of a tank, the game crashes. It doesn't crash if you get to the inventory screen of an Alien large unit via the Alien Inventory or Alien Pets hacks (not sure which) in your UFOExtender. I was able to arm Reapers with dual Heavy Plasma or dual Blaster Launchers. (Unpleasant. They have 0% FA so they have to run up to you and spray with the Heavy Plasma. Not a problem with the Blaster Launcher.) [[User:Spike|Spike]] 13:59, 20 August 2009 (EDT)

== Offset 0xB ==
The value is used together as an offset to [[TERRAIN|MCDData]] offset 39 (describing TUs required to cross a tile walking/flying/sliding) so it most likely represent the way the unit moves. Still needs testing. [[User:Seb76|Seb76]] 13:27, 23 May 2008 (PDT)

----

I took a look at it for Snakemen and Silacoids, it's still 0 (same as it is for everything else).

But that doesn't mean it remains at 0 when the game's running. Do you mean to say that the value here + 39 = the offset in the MCD array that says how many TUs were required to move past any given obstacles in the current map location?

(That is, you'd expect to see a 2 there for sliding units?)

- [[User:Bomb Bloke|Bomb Bloke]] 05:14, 25 May 2008 (PDT)

----

Yep, exactly like that. Also it checks if the value is 0xff and prevent movement in that case. I'll try a live check with a debugger when I encounter snakemen. Maybe it's a part of code that was implemented but not put into usage. [[User:Seb76|Seb76]] 05:20, 25 May 2008 (PDT)
:Did the check and the value is indeed zero even for snakemen... BTW, is the movement type really working? I mean has anybody ever checked that e.g. snakemen really use different TU amount for tiles where TU usage is not the same between crawling and walking? [[User:Seb76|Seb76]] 06:43, 25 May 2008 (PDT)

----

Truth be told I don't remember reading of anyone doing the tests, so I had a go myself.

I tried first with the Avenger ramp, stuck it up in the air and had soldiers walk/fly onto it. Made no effect to their TU usage.

Next I rigged a Snakeman mission in the arctic, stuck one of them in the middle of a pond. It wouldn't move on it's own, and I couldn't move it under mind control.

So then I set 0xB to 2 just for that unit, and hey presto! Suddenly it was able to move freely, either under my control or otherwise. That's certainly the movement type flag... It's just not set in practise.

Still, now I'm wondering if 2 really was for sliders... It doesn't make sense that "fliers" (which I guess was supposed to include the likes of CyberDiscs, which "hover" even when on the ground) wouldn't be able to cross water, yet Snakemen could. Perhaps it should be the other way around?

- [[User:Bomb Bloke|Bomb Bloke]] 19:22, 25 May 2008 (PDT)

----

Note that there are some tiles that have 0 MP cost for sliders. - [[User:Zaimoni|Zaimoni]] 22:28, 25 May 2008 (CDT)

: Yeah, I guess that puts the clincher on it. Only fliers would really be totally unhindered by ground rubble. I've tweaked the MCD details page accordingly. - [[User:Bomb Bloke|Bomb Bloke]] 05:25, 26 May 2008 (PDT)

----

Hehe, I knew it couldn't be anything else but movement type. Yet another entry for known bugs ;) I'll check if it's possible to reenable the feature. It'll depends if it's a bug or if it was voluntarily removed I guess... [[User:Seb76|Seb76]] 04:37, 26 May 2008 (PDT)
: Did a quick check and can confirm what is said in [[GEOSCAPE.EXE#Alien_Stats|Alien Stats]] page. Offset 0xB is filled with the 3rd "unknown" value of alien stats. It is set to 0 for all entries. Could not find any other place where it could possibly be set to another value. [[User:Seb76|Seb76]] 05:17, 26 May 2008 (PDT)

----

So it's just a matter of tweaking that for all relevant units, then. However, I reckon it was left unused intentionally - I doubt the map files really contain enough variety to make it worth including.

- [[User:Bomb Bloke|Bomb Bloke]] 05:25, 26 May 2008 (PDT)

----

Since TFTD was done later with the same engine, perhaps it makes use of this? However, given that a different team made it ([http://www.lasersquadnemesis.com/AboutUs.htm Terror from the Deep was developed by Microprose using code licensed by Mythos]), developers may not have known the feature was available... [[User:Seb76|Seb76]] 07:25, 28 May 2008 (PDT)

----

I took a quick check, and sure enough found a Hallucinoid (the big flying squid thing) set to 2.

- [[User:Bomb Bloke|Bomb Bloke]] 21:31, 28 May 2008 (PDT)

== Offset 0x47 ==

The only use I could find is that of updating [[SOURCEMP.DAT|mobile light sources]] (or something like that) when the unit dies/is rendered unconscious. Could not find anything else about this flag. [[User:Seb76|Seb76]] 05:24, 29 May 2008 (PDT)

:Good work there. As a general statement, can I say - I've been waiting for somebody to disassemble XCOM :) -[[User:MikeTheRed|MikeTheRed]] 21:18, 30 May 2008 (PDT)

I sat down to do some tests with this, but didn't bother too read to closely... I was selecting/moving units around when I probably shoulda been shooting at them.

Oh well. For the record:

Moving a unit causes a light check to be done on all your units. You may not see this light if one of your units is standing in a fog-of-war covered zone (say you just mind controlled an alien and haven't selected it yet).

Selecting a unit does a fog-of-war check concerning what it can see, but does not do a light check.

Whatever this offset is has no effect on the light produced by your units, or the aliens units. Your active guys ALWAYS fully illuminate their tile (even if this is 0) and the aliens provide no illumination at all. Will have to do some tests concerning what happens when you shoot them, but it seems odd: If a unit is dead I'd expect a full light check to be done, since the unit isn't "active" it won't produce light, so I don't see how this offset is helpful there... You can't just remove the light values for this one unit because you might interfere with other nearby light sources, so you really have to calculate them all from scratch.

But likewise it seems [[TERRAIN|MCD[58/3A]]] is similar; a street lamp is set to 1, a normal lamp to 10, but they both provide maximum illumination.

Perhaps the programmers changed their mind about the lighting system at some point? Dunno.

- [[User:Bomb Bloke|Bomb Bloke]] 07:03, 20 June 2008 (PDT)

:Some of your note reminds me of what I wrote at [[Night_Missions#Personal_lighting]] ... does that help any? (probably not) -[[User:MikeTheRed|MikeTheRed]] 16:01, 20 June 2008 (PDT)

== On Fire Flag or Timer ? ==

Do we have any idea where a flag is set to show the unit is on fire? This is persistent between saved games so it must be stored in a file somewhere. Possibly UNITPOS.DAT? It could be a flag, but more likely is either a countdown timer for turns remaining on fire, (values 1-5?), or a "what turn do I stop being on fire" timer value (like a grenade timer).

I have uploaded a saved game file with a burning Aquatoid if anyone wants to take a look. I just don't have the right diff tools. Maybe with the Hex Workshop template... [[User:Spike|Spike]] 19:05, 10 March 2009 (CDT)

:Offset 114 in Unitref holds that data. --[[User:Zombie|Zombie]] 19:15, 10 March 2009 (CDT)

:: Sorry I did not read the article carefully enough. It's in there. [[User:Spike|Spike]] 19:16, 10 March 2009 (CDT)

114 / 72: If not 0, then unit is on fire, and will burn for this amount of turns.

== Floating Civilians ==

Civilians float 2 units off the ground, like Floaters and Cyberdisks. Soldiers don't. Should we consider this to be a bug? [[User:Spike|Spike]] 13:41, 20 August 2009 (EDT)

:Probably. I really doubt it's an intentional feature. --[[User:Zombie|Zombie]] 23:09, 20 August 2009 (EDT)

== Remembering morale vs health and pain killers ==

The game remembers whether a health loss has or has not been used to regain morale via pain killers. Presumably this is stored somewhere in UNITREF.DAT? [[User:Spike|Spike]] 10:30, 5 September 2009 (EDT)

== TFTD Support ==

It appears the name string starts at the same point in TFTD save points, which leads me to believe that the extra bytes are probably just appended at the end of the file, without much changing in the first 124 bytes per entry, anyone know what these extra 8 bytes might represent?

UNITREF.DAT

2010-01-21T02:20:20Z

Hatfarm: /* Structure */

UNITREF.DAT has a row width of 124 bytes for UFO, 132 for TFTD. Bytes are unsigned, except for Missions and Kills. 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). The same format is used by the files [[UNIREF.DAT]] and [[UNIREF2.DAT]]. These are images of UNITREF.DAT saved in [[Saved_Game_Files#Missdat_Files|MISSDAT]] as of, respectively, the beginning of the last "live" combat game (i.e., not loaded from a savegame) and the last finished combat.

Values are presented according to byte offset (0 to 123) followed by the equivalent hex offset (00 to 7B) in bold. Notes only apply to UFO (as opposed to TFTD) unless otherwise stated. Let us know what else you can find!!

== Structure ==
'''0 / 00:''' 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] & [54] (weapons in hands), [115] (gender) and [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 10: BioDrone
11: Chryssalid 11: Tentaculat
12: Reaper 12: Triscene
13: Sectopod 13: Hallucinoid
14: Cyberdisc 14: Xarquid
15: Male civilian 15: Male civilians
16: Female civilian 16: Female civilians
17: Zombie 17: Zombie
18: Unused (but it made the sound of a tank?) 255: Unused
255: Unused

<blockquote>If the corresponding [[UNITPOS.DAT]] record is unused, then the record is unused.</blockquote>

'''1 / 01:''' 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, unitref[115] and unitref[116] are used to determine the picture.
0: No armor.
1: Personal armour.
2: Power suit.
3: Flying suit.

'''2 / 02:''' Bitflags. NKF: Seems to be consistent with different character models. ''MTR:'' I pulled those out of Hobbes' savegame (see Note 4). There seems to be some differences. Could it be a dynamic byte instead of e.g. static relative to model or whatever?
87654321
NKF: 00100100 36 Floater
10000000 128 Personal armour
10001100 140 Power suit/flying suits
11101000 232 Reaper
''BB:'' 00010000 16 Hovertank/Plasma
00111000 56 Psi unlocked soldier in flying suit
00110000 48 Psi locked soldier in kevlar
01010000 80 Aliens
01010100 84 Cyberdisc
''MTR:'' 00000100 4 Celatid
00100100 36 Chryssalid, Civvie, Ethereal, Floater, Muton, Snakeman,
11011100 220 Sectoid PA Soldier, Tank/Laser
11111000 248 Silacoid

( 1) 1: ?
( 2) 2: ?
( 4) 3: Common to Cyberdiscs
( 8) 4: Common to flying suits
( 16) 5: Common to all units
( 32) 6: Common to X-COM troopers
( 64) 7: Common to all enemies
(128) 8: ?

'''3 / 03:''' Bitflags:
87654321
''NKF:'' 00101110 46 Pers. armor
10000101 133 Floater
10111111 191 PS/FS
11101100 236 Reaper
''BB:'' 00100100 36 Psi locked soldier in kevlar
01010000 80 Hovertank/Plasma
10000001 129 Cyberdisc
10100101 165 Aliens
10110101 181 Psi unlocked soldier in flying suit
''MTR:'' 00000000 0 Chryssalid ''- from Hobbes' savegame''
00000100 4 Celatid
00100000 32 Floater
00110000 48 Muton, Snakeman, Tank/Laser
01110101 117 Sectoid
10100000 160 Ethereal
10110000 176 Civilian, PS (Power Suit) Soldier

( 1) 1: ?
( 2) 2: ?
( 4) 3: Small units
( 8) 4: ?
( 16) 5: Flying X-COM units
( 32) 6: Small units
( 64) 7: ?
(128) 8: ?

'''4 / 04:''' Possible bitflags.
87654321
''NKF:'' 10010001 145 PS/FS
10011011 155 PA Soldier, Floater, Reaper
''BB:'' 01100001 97 Hovertank/Plasma, Psi unlocked soldier in flying suit
01100010 98 Psi locked soldier in kevlar, Cyberdisc, Aliens
''MTR:'' 00100000 32 Silacoid ''- Hobbes' game''
00100100 36 Celatid, PA Soldier, Tank/Laser
00100101 37 Civilian, Muton, Snakeman
01010011 83 Sectoid
01011111 95 Chryssalid, Ethereal, Floater

'''5 / 05:''' Flags 1 for units in play, 0 otherwise. Possible bitflags.

'''6 / 06:''' Possible bitflags.
87654321
''NKF:'' 00000000 0 Reaper
00010000 16 Pers. armor
00100000 32 PS/FS
01010000 80 Floater
''BB:'' 01000000 64 Psi unlocked soldier in flying suit
01010000 80 Hovertank/Plasma
11000100 196 Aliens
11010100 212 Cyberdisc
11101000 232 Psi locked soldier in kevlar
''MTR:'' 00000100 4 Chryssalid '' - Hobbes' game''
01000000 64 Floater
10000100 132 Muton
10000100 132 Snakeman
10010100 148 Ethereal
10011000 152 Tank/Laser
10011100 156 Soldier psi locked in a power suit
10101000 168 Celatid
10101100 172 Sectoid
11011000 216 Civilian
11100100 228 Silacoid

( 1) 1: ?
( 2) 2: ?
( 4) 3: Enemies
( 8) 4: ?
( 16) 5: Large units
( 32) 6: ?
( 64) 7: Always flagged?
(128) 8: ?

'''7 / 07:''' NKF:
87654321
''BB:'' 00000000 0 Hovertank/Plasma
00010000 16 Cyberdisc
00010001 17 Psi unlocked flying suit troopers
00101011 43 Sectoid
00101101 45 Psi locked kevlar troopers
''MTR:'' 01001110 78 Chryssalid, Floater ''- Hobbes' game''
01111011 123 Tank/Laser
01111100 124 PA Soldier
01111101 125 Sectoid
01111110 126 Civilian
11001011 203 Ethereal
11011111 223 Celatid, Silacoid
11111011 251 Muton, Snakeman

( 1) 1: Small units
( 2) 2: Small aliens
( 4) 3: Psi locked kevlar troopers
( 8) 4: ?
( 16) 5: ?
( 32) 6: ?
( 64) 7: ?
(128) 8: ?

'''8 / 08:''' Same for all units? (171) (11000011)
87654321
''MTR:'' 00010011 19 Celatid, Silacoid ''- from Hobbes''
00011110 30 Civilian, Muton, Snakeman, PA Soldier, Tank/Laser
01001110 78 Sectoid
01011001 89 Chryssalid, Ethereal, Floater

''Zaimoni:'' Bit 3 (significance 4) sometimes changes during alien turn/patrol AI.

'''9 / 09:''' Always 0?

'''10 / 0A:''' Unit facing. Does NOT control HWP turret direction; see [024].
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)

'''11 / 0B:''' Movement type. When entering a given map location, each tile is checked to see the TU requirements accordingly. [[TERRAIN|MCD]][39+UnitRef[11]] is the offset used. Note: By default, this is 0 for ALL unit types.
0: Walking
1: Sliding
2: Flying

'''12 / 0C:''' Current TUs

'''13 / 0D:''' Current Health. Health of 0 = Dead. Compare [42], [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)''

'''14 / 0E:''' Current Stun level ''how much falloff of paralysis every turn? What determines it?''

'''15 / 0F:''' Current Energy

'''16 / 10:''' Current Reactions ''NKF: affected by health percentage''

'''17 / 11:''' Strength

'''18 / 12:''' Current Front Armour

'''19 / 13:''' Current Left Armour

'''20 / 14:''' Current Right Armour

'''21 / 15:''' Current Rear Armour

'''22 / 16:''' Current Under Armour

"Base" means the original (total) value (as carried forward from geoscape) - Also see Note 1 re: Base soldier stat values.

'''23 / 17:''' Base Firing accuracy. Current value = this * [013]/[026] (percent health)

'''24 / 18:''' Base Throwing accuracy. Current value = this * [013]/[026] (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 [010].

'''25 / 19:''' Base TUs

'''26 / 1A:''' Base Health

'''27 / 1B:''' Base Energy

'''28 / 1C:''' Base Reactions

'''29 / 1D:''' Base Front Armour

'''30 / 1E:''' Base Left Armour

'''31 / 1F:''' Base Right Armour

'''32 / 20:''' Base Rear Armour

'''33 / 21:''' Base Under Armour

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

'''34 / 22:''' Always 0?

'''35 / 23:''' 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] (energy usage when walking/turning). ''BombBloke: Is this affected by damage?''

'''36 / 24:''' Always 0?

'''37 / 25:''' Psi skill. Psi stats not displayed/usable until this is greater then 0.

'''38 / 26:''' Item to create when unit is unconcious/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.

'''39 / 27:''' "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.

'''40 / 28:''' 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.''

'''41 / 29:''' ''BombBloke:'' Something to do with large units. Changes during gameplay. Have seen values of 2, 3, 5, 6.

'''42 / 2A:''' 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] (Health=0) seems to be the only reliable death indicator for them. Compare [120]. -[[User:MikeTheRed|MikeTheRed]]''

'''43 / 2B:''' 0 or 1? In Hobbes' savegame, civvies and sectoids are 1. All others are 0 (soldiers, aliens, terrorists, tank).

''MTR: If the next byte is "aggression", and civvies and sectoids have a 1 here, could this be "cowardliness"? Likelihood to panic; to do something dumb/random? We've all seen civvies running around in a mad / random panic.''

'''44 / 2C:''' Alien aggression. The higher it is, the less likely an alien will take cover. Maximum of 2. ''MTR: This is true for aliens in Hobbes game, but soldiers have values from 4 to 254. Garbage? Delete this comment if so.''

'''45 / 2D:''' Used to calculate energy loss when walking or turning as: INT( TUs / 2[45] ). See [[Energy#Usage]]; compare [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?''

'''46 / 2E:''' HWP turret image. Only used (and only appears) if unit type [00]=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] and [117].

'''47 / 2F:''' This is a direct copy of offset[48] from the MCD record (see [[TERRAIN]]) of the tile the unit is standing on. A signed byte.

'''48 / 30:''' Values for this byte always equal [52] and are:
2 (5 pixels): Sectoid
3 (7 pixels): Celatid, Chryssalid, Civvie, Ethereal, Floater, Muton, Snake, '''Soldier'''
4 (9 pixels): Cyberdisc, Hovertank, Reaper, Sectopod, Tank
5 (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]).

This cylindrical shape is used in conjunction with height [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] Pxls X Ht (16x24) UR[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.

The unit Float number (Unitref[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.

'''49 / 31:''' [[height|Standing height]].

'''50 / 32:''' [[height|Kneeling height]].

'''51 / 33:''' Floating [[height]]. A unit 'floats' this high above the ground, thus allowing shots to fly underneath. The heighest point of a unit can be found by adding this to the units height stat. Does this have an effect on explosive damage?

'''52 / 34:''' Always the same as [48] in all known saved games. XCOMmies are trying to test its significance, as seen at [[Talk:UNITREF.DAT#Offsets_0x30_.26_0x34|Talk:UNITREF.DAT#Offsets_0x30_&_0x34]] ([48] and [52]).

'''53 / 35''' and '''54 / 36:''' Image index for item in left and right hand, respectively. 255 for none. Indexes into obdata.dat, not obpos.dat.

''NKF:'' If there is no item in the unit's hands, but these 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.

'''55 / 37:''' [[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

'''56 / 38:''' [[Melee Accuracy]] ([[SOLDIER.DAT]] bytes 50 (initial) & 60 (increase) added together)

'''57 / 39:''' [[Psionic Strength]]

'''58 / 3A:''' Current [[Morale]]. Base morale is hardcoded to 100.

'''59 / 3B:''' [[Bravery]] = 110 - (10 * value)

'''60 / 3C:''' 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

'''61 / 3D:''' Unitref[062] 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

'''62 / 3E:''' Visibility via motion scanner. The bigger it is, the bigger the blip. Test this one out for values.

'''63 / 3F:''' Number of [[Fatal Wounds]] to head.

'''64 / 40:''' Number of fatal wounds to torso.

'''65 / 41:''' Number of fatal wounds to right arm.

'''66 / 42:''' Number of fatal wounds to left arm.

'''67 / 43:''' Number of fatal wounds to right leg.

'''68 / 44:''' Number of fatal wounds to left leg.

'''69 / 45''' and '''70 / 46:''' 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

'''71 / 47:''' ''NKF:'' Always 16 for XCom units, 1 for cyberdisc, 0 for others? Perhaps involves mobile lighting - see the [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page.

'''72 / 48:''' Always 0? May be paired with [71].

'''73 / 49:''' 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? :(''

'''74 / 4A:''' ''NKF:'' Could be the unit spotted icon identifier? Could point to visible enemy units?

''MikeTheRed:'' XCOMs always have 0, but Mutons have values of 0-3 (usually 0 or 2, and often fluctuating) in a firing squad situation.

'''75 / 4B:''' Always 0?

'''76-77 / 4C-4D:''' 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?

'''78-79 / 4E-4F:''' 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!

'''80 / 50:''' [[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?

'''81 / 51:''' [[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.)

'''82 / 52:''' [[Melee Accuracy]] experience counter, for number of times stun rod has been used (not stun bombs).

'''83 / 53:''' [[Throwing Accuracy]] experience counter, for number of times unit has thrown any object.

<div id="Psi_Skill_Experience_Counter"></div>'''84 / 54:''' [[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).

'''85 / 55:''' [[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.

'''86-111 / 56-6F:''' Unit's Name. Standard string ended by null byte. The rest can hold garbage.

'''112 / 70:''' 0; sometimes 1 for aliens.

'''113 / 71:''' 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.

UnitRef[1] actually determines the inventory screen used, might be worth playing with that. UnitRef[46] determines the layout.

'''114 / 72:''' If not 0, then unit is on fire, and will burn for this amount of turns.

'''115 / 73:''' Gender: 0 = male, 1 = female.

'''116 / 74:''' Hair/skin colour (for inventory; all other units = 0):
0: Blond caucasian
1: Brunette caucasian
2: Asian
3: Black

'''117 / 75:''' 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], [113], and [118].

'''118 / 76:''' Ammo for [117] turret weapon

'''119 / 77:''' 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

'''120 / 78:''' 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] (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: ??? Seems to flag if the unit has 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?

'''121 / 79:''' 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.

'''122 / 7A:''' Always 0?

'''123 / 7B:''' Always 0?

== Notes ==
1) The original/base values for soldier stats (offsets 23-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) 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-85) causes stat and rank increases, and decreased health (offset 26 - offset 13) means hospital time. And, of course, death is permanent. Heh.

2) Experience counters (offsets 80-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) 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-82 or 84-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
Offset of weapon from unit image?
Firing sprite offset?
<strike>Inventory lockout?</strike> ''All mind controlled units are locked out.''
Kneel lockout?
<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 99 values.
Unknown values (25 in total):
[002] [003] [004] [005] [006] [007] [008] [009] [034]
[036] [041] [043] [052] [069] [070] [071] [072] [074]
[075] [112] [119] [120] [121] [122] [123]

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

UNITREF.DAT

2010-01-15T04:03:12Z

Hatfarm: /* Structure */

UNITREF.DAT has a row width of 124 bytes for UFO, 132 for TFTD. Bytes are unsigned, except for Missions and Kills. 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). The same format is used by the files [[UNIREF.DAT]] and [[UNIREF2.DAT]]. These are images of UNITREF.DAT saved in [[Saved_Game_Files#Missdat_Files|MISSDAT]] as of, respectively, the beginning of the last "live" combat game (i.e., not loaded from a savegame) and the last finished combat.

Values are presented according to byte offset (0 to 123) followed by the equivalent hex offset (00 to 7B) in bold. Notes only apply to UFO (as opposed to TFTD) unless otherwise stated. Let us know what else you can find!!

== Structure ==
'''0 / 00:''' 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] & [54] (weapons in hands), [115] (gender) and [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 10: BioDrone
11: Chryssalid 11: Tentaculat
12: Reaper 12: Triscene
13: Sectopod 13: Hallucinoid
14: Cyberdisc 14: Xarquid
15: Male civilian 15: Male civilians
16: Female civilian 16: Female civilians
17: Zombie 17: Zombie
18: Unused (but it made the sound of a tank?)
255: Unused

<blockquote>If the corresponding [[UNITPOS.DAT]] record is unused, then the record is unused.</blockquote>

'''1 / 01:''' 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, unitref[115] and unitref[116] are used to determine the picture.
0: No armor.
1: Personal armour.
2: Power suit.
3: Flying suit.

'''2 / 02:''' Bitflags. NKF: Seems to be consistent with different character models. ''MTR:'' I pulled those out of Hobbes' savegame (see Note 4). There seems to be some differences. Could it be a dynamic byte instead of e.g. static relative to model or whatever?
87654321
NKF: 00100100 36 Floater
10000000 128 Personal armour
10001100 140 Power suit/flying suits
11101000 232 Reaper
''BB:'' 00010000 16 Hovertank/Plasma
00111000 56 Psi unlocked soldier in flying suit
00110000 48 Psi locked soldier in kevlar
01010000 80 Aliens
01010100 84 Cyberdisc
''MTR:'' 00000100 4 Celatid
00100100 36 Chryssalid, Civvie, Ethereal, Floater, Muton, Snakeman,
11011100 220 Sectoid PA Soldier, Tank/Laser
11111000 248 Silacoid

( 1) 1: ?
( 2) 2: ?
( 4) 3: Common to Cyberdiscs
( 8) 4: Common to flying suits
( 16) 5: Common to all units
( 32) 6: Common to X-COM troopers
( 64) 7: Common to all enemies
(128) 8: ?

'''3 / 03:''' Bitflags:
87654321
''NKF:'' 00101110 46 Pers. armor
10000101 133 Floater
10111111 191 PS/FS
11101100 236 Reaper
''BB:'' 00100100 36 Psi locked soldier in kevlar
01010000 80 Hovertank/Plasma
10000001 129 Cyberdisc
10100101 165 Aliens
10110101 181 Psi unlocked soldier in flying suit
''MTR:'' 00000000 0 Chryssalid ''- from Hobbes' savegame''
00000100 4 Celatid
00100000 32 Floater
00110000 48 Muton, Snakeman, Tank/Laser
01110101 117 Sectoid
10100000 160 Ethereal
10110000 176 Civilian, PS (Power Suit) Soldier

( 1) 1: ?
( 2) 2: ?
( 4) 3: Small units
( 8) 4: ?
( 16) 5: Flying X-COM units
( 32) 6: Small units
( 64) 7: ?
(128) 8: ?

'''4 / 04:''' Possible bitflags.
87654321
''NKF:'' 10010001 145 PS/FS
10011011 155 PA Soldier, Floater, Reaper
''BB:'' 01100001 97 Hovertank/Plasma, Psi unlocked soldier in flying suit
01100010 98 Psi locked soldier in kevlar, Cyberdisc, Aliens
''MTR:'' 00100000 32 Silacoid ''- Hobbes' game''
00100100 36 Celatid, PA Soldier, Tank/Laser
00100101 37 Civilian, Muton, Snakeman
01010011 83 Sectoid
01011111 95 Chryssalid, Ethereal, Floater

'''5 / 05:''' Flags 1 for units in play, 0 otherwise. Possible bitflags.

'''6 / 06:''' Possible bitflags.
87654321
''NKF:'' 00000000 0 Reaper
00010000 16 Pers. armor
00100000 32 PS/FS
01010000 80 Floater
''BB:'' 01000000 64 Psi unlocked soldier in flying suit
01010000 80 Hovertank/Plasma
11000100 196 Aliens
11010100 212 Cyberdisc
11101000 232 Psi locked soldier in kevlar
''MTR:'' 00000100 4 Chryssalid '' - Hobbes' game''
01000000 64 Floater
10000100 132 Muton
10000100 132 Snakeman
10010100 148 Ethereal
10011000 152 Tank/Laser
10011100 156 Soldier psi locked in a power suit
10101000 168 Celatid
10101100 172 Sectoid
11011000 216 Civilian
11100100 228 Silacoid

( 1) 1: ?
( 2) 2: ?
( 4) 3: Enemies
( 8) 4: ?
( 16) 5: Large units
( 32) 6: ?
( 64) 7: Always flagged?
(128) 8: ?

'''7 / 07:''' NKF:
87654321
''BB:'' 00000000 0 Hovertank/Plasma
00010000 16 Cyberdisc
00010001 17 Psi unlocked flying suit troopers
00101011 43 Sectoid
00101101 45 Psi locked kevlar troopers
''MTR:'' 01001110 78 Chryssalid, Floater ''- Hobbes' game''
01111011 123 Tank/Laser
01111100 124 PA Soldier
01111101 125 Sectoid
01111110 126 Civilian
11001011 203 Ethereal
11011111 223 Celatid, Silacoid
11111011 251 Muton, Snakeman

( 1) 1: Small units
( 2) 2: Small aliens
( 4) 3: Psi locked kevlar troopers
( 8) 4: ?
( 16) 5: ?
( 32) 6: ?
( 64) 7: ?
(128) 8: ?

'''8 / 08:''' Same for all units? (171) (11000011)
87654321
''MTR:'' 00010011 19 Celatid, Silacoid ''- from Hobbes''
00011110 30 Civilian, Muton, Snakeman, PA Soldier, Tank/Laser
01001110 78 Sectoid
01011001 89 Chryssalid, Ethereal, Floater

''Zaimoni:'' Bit 3 (significance 4) sometimes changes during alien turn/patrol AI.

'''9 / 09:''' Always 0?

'''10 / 0A:''' Unit facing. Does NOT control HWP turret direction; see [024].
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)

'''11 / 0B:''' Movement type. When entering a given map location, each tile is checked to see the TU requirements accordingly. [[TERRAIN|MCD]][39+UnitRef[11]] is the offset used. Note: By default, this is 0 for ALL unit types.
0: Walking
1: Sliding
2: Flying

'''12 / 0C:''' Current TUs

'''13 / 0D:''' Current Health. Health of 0 = Dead. Compare [42], [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)''

'''14 / 0E:''' Current Stun level ''how much falloff of paralysis every turn? What determines it?''

'''15 / 0F:''' Current Energy

'''16 / 10:''' Current Reactions ''NKF: affected by health percentage''

'''17 / 11:''' Strength

'''18 / 12:''' Current Front Armour

'''19 / 13:''' Current Left Armour

'''20 / 14:''' Current Right Armour

'''21 / 15:''' Current Rear Armour

'''22 / 16:''' Current Under Armour

"Base" means the original (total) value (as carried forward from geoscape) - Also see Note 1 re: Base soldier stat values.

'''23 / 17:''' Base Firing accuracy. Current value = this * [013]/[026] (percent health)

'''24 / 18:''' Base Throwing accuracy. Current value = this * [013]/[026] (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 [010].

'''25 / 19:''' Base TUs

'''26 / 1A:''' Base Health

'''27 / 1B:''' Base Energy

'''28 / 1C:''' Base Reactions

'''29 / 1D:''' Base Front Armour

'''30 / 1E:''' Base Left Armour

'''31 / 1F:''' Base Right Armour

'''32 / 20:''' Base Rear Armour

'''33 / 21:''' Base Under Armour

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

'''34 / 22:''' Always 0?

'''35 / 23:''' 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] (energy usage when walking/turning). ''BombBloke: Is this affected by damage?''

'''36 / 24:''' Always 0?

'''37 / 25:''' Psi skill. Psi stats not displayed/usable until this is greater then 0.

'''38 / 26:''' Item to create when unit is unconcious/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.

'''39 / 27:''' "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.

'''40 / 28:''' 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.''

'''41 / 29:''' ''BombBloke:'' Something to do with large units. Changes during gameplay. Have seen values of 2, 3, 5, 6.

'''42 / 2A:''' 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] (Health=0) seems to be the only reliable death indicator for them. Compare [120]. -[[User:MikeTheRed|MikeTheRed]]''

'''43 / 2B:''' 0 or 1? In Hobbes' savegame, civvies and sectoids are 1. All others are 0 (soldiers, aliens, terrorists, tank).

''MTR: If the next byte is "aggression", and civvies and sectoids have a 1 here, could this be "cowardliness"? Likelihood to panic; to do something dumb/random? We've all seen civvies running around in a mad / random panic.''

'''44 / 2C:''' Alien aggression. The higher it is, the less likely an alien will take cover. Maximum of 2. ''MTR: This is true for aliens in Hobbes game, but soldiers have values from 4 to 254. Garbage? Delete this comment if so.''

'''45 / 2D:''' Used to calculate energy loss when walking or turning as: INT( TUs / 2[45] ). See [[Energy#Usage]]; compare [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?''

'''46 / 2E:''' HWP turret image. Only used (and only appears) if unit type [00]=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] and [117].

'''47 / 2F:''' This is a direct copy of offset[48] from the MCD record (see [[TERRAIN]]) of the tile the unit is standing on. A signed byte.

'''48 / 30:''' Values for this byte always equal [52] and are:
2 (5 pixels): Sectoid
3 (7 pixels): Celatid, Chryssalid, Civvie, Ethereal, Floater, Muton, Snake, '''Soldier'''
4 (9 pixels): Cyberdisc, Hovertank, Reaper, Sectopod, Tank
5 (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]).

This cylindrical shape is used in conjunction with height [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] Pxls X Ht (16x24) UR[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.

The unit Float number (Unitref[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.

'''49 / 31:''' [[height|Standing height]].

'''50 / 32:''' [[height|Kneeling height]].

'''51 / 33:''' Floating [[height]]. A unit 'floats' this high above the ground, thus allowing shots to fly underneath. The heighest point of a unit can be found by adding this to the units height stat. Does this have an effect on explosive damage?

'''52 / 34:''' Always the same as [48] in all known saved games. XCOMmies are trying to test its significance, as seen at [[Talk:UNITREF.DAT#Offsets_0x30_.26_0x34|Talk:UNITREF.DAT#Offsets_0x30_&_0x34]] ([48] and [52]).

'''53 / 35''' and '''54 / 36:''' Image index for item in left and right hand, respectively. 255 for none. Indexes into obdata.dat, not obpos.dat.

''NKF:'' If there is no item in the unit's hands, but these 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.

'''55 / 37:''' [[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

'''56 / 38:''' [[Melee Accuracy]] ([[SOLDIER.DAT]] bytes 50 (initial) & 60 (increase) added together)

'''57 / 39:''' [[Psionic Strength]]

'''58 / 3A:''' Current [[Morale]]. Base morale is hardcoded to 100.

'''59 / 3B:''' [[Bravery]] = 110 - (10 * value)

'''60 / 3C:''' 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

'''61 / 3D:''' Unitref[062] 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

'''62 / 3E:''' Visibility via motion scanner. The bigger it is, the bigger the blip. Test this one out for values.

'''63 / 3F:''' Number of [[Fatal Wounds]] to head.

'''64 / 40:''' Number of fatal wounds to torso.

'''65 / 41:''' Number of fatal wounds to right arm.

'''66 / 42:''' Number of fatal wounds to left arm.

'''67 / 43:''' Number of fatal wounds to right leg.

'''68 / 44:''' Number of fatal wounds to left leg.

'''69 / 45''' and '''70 / 46:''' 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

'''71 / 47:''' ''NKF:'' Always 16 for XCom units, 1 for cyberdisc, 0 for others? Perhaps involves mobile lighting - see the [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page.

'''72 / 48:''' Always 0? May be paired with [71].

'''73 / 49:''' 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? :(''

'''74 / 4A:''' ''NKF:'' Could be the unit spotted icon identifier? Could point to visible enemy units?

''MikeTheRed:'' XCOMs always have 0, but Mutons have values of 0-3 (usually 0 or 2, and often fluctuating) in a firing squad situation.

'''75 / 4B:''' Always 0?

'''76-77 / 4C-4D:''' 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?

'''78-79 / 4E-4F:''' 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!

'''80 / 50:''' [[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?

'''81 / 51:''' [[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.)

'''82 / 52:''' [[Melee Accuracy]] experience counter, for number of times stun rod has been used (not stun bombs).

'''83 / 53:''' [[Throwing Accuracy]] experience counter, for number of times unit has thrown any object.

<div id="Psi_Skill_Experience_Counter"></div>'''84 / 54:''' [[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).

'''85 / 55:''' [[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.

'''86-111 / 56-6F:''' Unit's Name. Standard string ended by null byte. The rest can hold garbage.

'''112 / 70:''' 0; sometimes 1 for aliens.

'''113 / 71:''' 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.

UnitRef[1] actually determines the inventory screen used, might be worth playing with that. UnitRef[46] determines the layout.

'''114 / 72:''' If not 0, then unit is on fire, and will burn for this amount of turns.

'''115 / 73:''' Gender: 0 = male, 1 = female.

'''116 / 74:''' Hair/skin colour (for inventory; all other units = 0):
0: Blond caucasian
1: Brunette caucasian
2: Asian
3: Black

'''117 / 75:''' 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], [113], and [118].

'''118 / 76:''' Ammo for [117] turret weapon

'''119 / 77:''' 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

'''120 / 78:''' 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] (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: ??? Seems to flag if the unit has 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?

'''121 / 79:''' 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.

'''122 / 7A:''' Always 0?

'''123 / 7B:''' Always 0?

== Notes ==
1) The original/base values for soldier stats (offsets 23-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) 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-85) causes stat and rank increases, and decreased health (offset 26 - offset 13) means hospital time. And, of course, death is permanent. Heh.

2) Experience counters (offsets 80-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) 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-82 or 84-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
Offset of weapon from unit image?
Firing sprite offset?
<strike>Inventory lockout?</strike> ''All mind controlled units are locked out.''
Kneel lockout?
<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 99 values.
Unknown values (25 in total):
[002] [003] [004] [005] [006] [007] [008] [009] [034]
[036] [041] [043] [052] [069] [070] [071] [072] [074]
[075] [112] [119] [120] [121] [122] [123]

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

DIPLOM.DAT

2010-01-13T07:08:08Z

Hatfarm:

This file contains the information about how much money the various nations are giving you in funding, both current and for the graph, among other things. It is 576 bytes long, split into 16 records of 36 bytes long, one for each country. The record start points, by country are:

<table {{StdCenterTable}} class="sortable">
<tr {{StdDescTable_Heading}}>
<th>Offset dec (hex)</th>
<th width="150">Country</th></tr>
<tr><td>0 (0x0000)</td><td>USA</td></tr>
<tr><td>36 (0x0024)</td><td>Russia</td></tr>
<tr><td>72 (0x0048)</td><td>UK</td></tr>
<tr><td>108 (0x006C)</td><td>France</td></tr>
<tr><td>144 (0x0090)</td><td>Germany</td></tr>
<tr><td>180 (0x00B4)</td><td>Italy</td></tr>
<tr><td>216 (0x00D8)</td><td>Spain</td></tr>
<tr><td>252 (0x00FC)</td><td>China</td></tr>
<tr><td>288 (0x0120)</td><td>Japan</td></tr>
<tr><td>324 (0x0144)</td><td>India</td></tr>
<tr><td>360 (0x0168)</td><td>Brazil</td></tr>
<tr><td>396 (0x018C)</td><td>Australia</td></tr>
<tr><td>432 (0x01B0)</td><td>Nigeria</td></tr>
<tr><td>468 (0x01D4)</td><td>South Africa</td></tr>
<tr><td>504 (0x01F8)</td><td>Egypt</td></tr>
<tr><td>540 (0x021C)</td><td>Canada</td></tr>
</table>

Within each record, there are several pieces of information, they are all signed 2 byte numeric fields:

<table {{StdDescTable}}>
<tr>
<th {{StdDescTable_Heading}}>'''Offset dec (hex)'''</th><th {{StdDescTable_Heading}}>'''Meaning'''</th>
</tr>
<tr><td>0 (0x00)</td><td>Pointer to country name in string table (starts at 602 (0x025A), increase 1 each record) </td></tr>
<tr><td>2 (0x02)</td><td>Satisfaction Rating, 3 is happy, 2 is average, 1 is unhappy, 0 will sign pact/stop funding </td></tr>
<tr><td>4 to 26 (0x04 to 0x1A)</td><td>Funding values (in $k) starts with Jan, runs to Dec</td></tr>
<tr><td>28 (0x1C)</td><td>Funding change (in $k) </td></tr>
<tr><td>30 (0x1E)</td><td>Non zero (1 when game sets it) means that the country will sign pact at end of month</td></tr>
<tr><td>32 (0x20)</td><td>Starting Funding base value, ranges 110 to 600 (in $k)</td></tr>
<tr><td>34 (0x22)</td><td>Funding cap (ranges 2k to 10k, equates to 2-10M)</td></tr>
</table>

Note that Satisfaction rating does not seem to drop to 2 any month a country doesnt increase funding, so not sure of the extra relationship here, but 0 always results in them stopping funding at the end of the month (I think you still get paid the one last time, as you are always seeing next months budget effectively). Possibly happy countries can randomly decide to not increase funding anyway. Setting this value to 2 or 1 before month end doesnt seem to affect the funding change either, setting it 0 will though, at least when you have a good score.

Bytes 32 to 33 are what is used to base the starting Funding on, it initially randomly gets a value from 100-200% of the value listed for each country. For game balance reasons it then scales the entire result so that it comes to approximately 6 million, with an error of +-15 because of the way it scales the result, this can sometimes push a country slightly higher or lower than the original range would have allowed it to. Changing these values has no in game effect anyway, as they are used before the first save is created.

The funding change is the difference from last month to the current month. It is not the amount that the funding will be increased in the upcoming month change.

<table {{StdCenterTable}} class="sortable">
<tr {{StdDescTable_Heading}}>
<th width="150">Country</th>
<th>Starting Funding base</th>
<th>Funding Cap (k)</th></tr>
<tr><td>USA</td><td>600</td><td>10000</td></tr>
<tr><td>Russia</td><td>230</td><td>8000</td></tr>
<tr><td>UK</td><td>240</td><td>7000</td></tr>
<tr><td>France</td><td>320</td><td>8000</td></tr>
<tr><td>Germany</td><td>250</td><td>9000</td></tr>
<tr><td>Italy</td><td>160</td><td>6000</td></tr>
<tr><td>Spain</td><td>140</td><td>5000</td></tr>
<tr><td>China</td><td>245</td><td>7000</td></tr>
<tr><td>Japan</td><td>400</td><td>10000</td></tr>
<tr><td>India</td><td>150</td><td>5000</td></tr>
<tr><td>Brazil</td><td>300</td><td>4000</td></tr>
<tr><td>Australia</td><td>280</td><td>5000</td></tr>
<tr><td>Nigeria</td><td>180</td><td>2000</td></tr>
<tr><td>South Africa</td><td>310</td><td>3000</td></tr>
<tr><td>Egypt</td><td>160</td><td>2000</td></tr>
<tr><td>Canada</td><td>110</td><td>4000</td></tr>
</table>

According to these values, the maximum theoretical funding you can get is 95M per month, if you can max out all 16 countries budgets.

Note that you can manually insert a monthly funding number into the current month for any country, and it will award you that amount at the end of the month. If funding for that country increases (changes?) it will apply the funding cap to next months budget, and then it will remain at the cap from then on (unless you do badly and it drops), so to permanently increase funding beyond these limits the cap has to be modified. If funding is static for that month, it just copies the value across without applying the funding cap.

==See Also==
[[Saved Game Files]]
[[Category:Game Files]]

GEOSCAPE.EXE

2010-01-07T00:30:12Z

Hatfarm: /* XCOM: UFO Defense DOS Versions, difficulty setting bug */

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

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

Also see [[Versions]].

= X-COM Complete Packages =

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

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

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

''Thanks, and welcome!''

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

==Review #1 by wfames==

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

==Review #2 by Draco Cracona==

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

==Review #3 by Muton commander==

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

==Review #4 by Diegoba==

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

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

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

= Craft Stats =

At offset 353,020 in X-COM 1.4 (DOS - modified by XCUtil), the aircraft statistics begin. In WinCE (XCUtil) this starts at hex offset 0x6F9A8 and Alien craft start at 0x6fa34.
''Emphyrio: start at 353014?, each entry 14 records of 2 bytes, 5 Xcom craft and then 8 Alien''

Each Vessel Statistic is two bytes and is 0 through 65,535 (in UGE format), and go in the following order:

Pointer to craft name in [[ENGLISH.DAT]] 
Points 
Weapon Pods 
Maximum Speed 
Acceleration 
Fuel 
Damage (armor) 
Size Class 
Unknown (UFO only stat). Believed to be the base firing interval of the weapon 
Unknown (UFO only stat). Value is roughly similar to score for destroying? 
Weapon Range (in 1/8ths of km)(UFOs only) 
Weapon Damage (UFOs only) 
Crew 
HWP 

To help you find it in UGE, here are the various X-COM vessel section in UGE format:

Skyranger: 248 - 2 - 2 - 0 - 220 - 5 - 150 - 0 
Lightning: 28 - 12 - 8 - 0 - 30 - 0 - 32 - 3 
Avenger: 24 - 21 - 10 - 0 - 60 - 0 - 176 - 4 
Interceptor: 52 - 8 - 3 - 0 - 232 - 3 - 100 - 0 
Firestorm: 104 - 16 - 9 - 0 - 20 - 0 - 244 - 1 

A bit below the Firestorm statistics are the stats for various Alien Ships, I'll probably do them later.

Here is a hex signature to help find the first alien craft record (Small Scout):

b2 02 64 00 02 00 98 08 0c 00 00 00 32 00

At offset 380,668 the Tank Statistics begin.

= Armor Stats =

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

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

Front Armor 
Left Armor 
Right Armor 
Rear Armor 
Under Armor 

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

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

So on, etc.

= Alien Stats =

This section is for the structure of the alien stats, as found in GEOSCAPE. For actual data and additional information, see the [[Alien_Stats|alien statistics]] page. Also see Zombie's excellent alien stats page at [http://www.strategycore.co.uk/xcom/pg/ufoalienstats StrategyCore]. ''(Have YOU made your StratCore and [http://www.xcomufo.com XCOMUFO] accounts yet?)''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

'''12:''' Front Armor - Corresponds to Unitref[029]

'''13:''' Left Armor - Corresponds to Unitref[030]

'''14:''' Right Armor - Corresponds to Unitref[031]

'''15:''' Rear Armor - Corresponds to Unitref[032]

'''16:''' Under Armor - Corresponds to Unitref[033]

'''17:''' ''Unknown - Always 0'' - Corresponds to Unitref[034]

'''18:''' Energy Recharge - Corresponds to Unitref[035]

'''19:''' ''Unknown - Always 0'' - Corresponds to Unitref[036]

'''20:''' ''Unknown - Always 1'' No Corresponding Unitref offset

'''21:''' ''Unknown - Always 0'' - Corresponds to Unitref[046]

'''22:''' ''Unknown'' - Corresponds to Unitref[048] (see below)

'''23:''' ''Unknown'' - Corresponds to Unitref[052] (see below)

''NOTE: For additional important info on the last two bytes, see [[Talk:UNITREF.DAT]]. My notes below do not take that info into account. For the moment though I'm leaving it as is. I sure wish we could figure the bytes out, and get rid of all the conjecture! - [[User:MikeTheRed|MikeTheRed]] 08:05, 6 November 2006 (PST)''

These Unitref bytes ([48] and [52]) and now Geoscape Core values have long stumped us hardcore X-Commies. The two bytes always equal the same value for a given alien, including all aliens of the same race (the N's below). And, they're the same between Geoscape and Unitref. Clearly it must be important (or a goof!), but exactly what it is, who knows. Although this page is for X-COM, I've included TFTD in the hopes it helps folks - but it's been so long since I've played TFTD, I can't remember those units at all.

How's this for a thought?...
Dimension Byte(s)

X 22

Y 23

Z 24 (top when standing)
25 (top when kneeling)
26 (bottom)

Maybe they represent the "size in profile" ("width"), affecting likelihood to hit. A game could be tried with a target 20 squares away, set 22 and 23 alternately to 5 or 2 (or 1 or 0?), and see if it affects the successful shots percentage. 0 or even 1 might break the game, though.

Also, how do these values (2 to 5) correlate with the "pixel drawings" of units? I can't seem to find that info at the moment... aren't units and tiles defined as something like 16x16x[[Height|28]]? If so, then perhaps the values (2 to 5) are multiplied by 3 or something to get their final "width" for bullet interception?? --[[User:MikeTheRed|MikeTheRed]] 05:20, 17 September 2006 (PDT)

:I finally got the OSG (w00t!), and noticed the following: The section on weapon accuracy says (p. 221) that target size affects the chance to hit, and "the 'size' of each alien is listed along with all other alien statistics in Chapter 9". But the alien stats tables (p. 250 ff.) only lists Height as a possible 'size' stat, and the text write-ups don't otherwise address "target size" with any precision. This discrepancy - that Chapter 8 talks about '''size''', but Chapter 9 only has '''height''' - might (might!) mean there are more variables that determine target area size, but somehow they didn't make it to the alien stats tables.

:The description for Height (p. 249) does say, "Taller creatures are easier to hit than short ones are. An alien with a height of 40, for example, is twice as easy to hit as an alien with a height of 20." (Note: The tallest [[Height]] is actually 23. And also notice, Float is never mentioned.) This ''might'' mean only height affects this, or it could be read in a general way; other dimensions (X and Y in addition to Z) might also affect it.

:Somebody should do some firing accuracy tests while hacking these potential X & Y bytes! But I still don't know how the values for [22] & [23] compare to what X-COM considers tile width... we know the Height byte accurately reflects the full range of possible values (0 to 23), but I doubt 5 is the full (pixel?) width of a tile. This might mean it's not width, then (or maybe [22] & [23] are added, or they are individually multiplied by 3 or something??) If anyone who knows about tile width could say something, I'd appreciate it. --[[User:MikeTheRed|MikeTheRed]] 11:24, 1 October 2006 (PDT)

In any event, here's a summary of bytes [22] and [23], in the hopes we can figure it out. They're always identical for a given race, and [22] always equals [23].

'''X-COM TFTD'''

Value Alien N Value Alien N

2 Sectoid 6 2 Aquatoid 6
Bio-Drone 1
3 Celatid 1 Tentaculat 1
Chryssalid 1
Civilian 2 3 Calcinite 1
Ethereal 3 Civilian 2
Floater 6 Deep_One 1
Muton 3 Gill_Man 4
Snakeman 5 Tasoth 2

4 Cyberdisc 1 4 Coelacant 1
Hovertank 1 Displacer 1
Reaper 1 Hallucinoid 1
Sectopod 1 Lobster_Man 5
Tank 1 Triscene 1
Xarquid 1
5 Silacoid 1

'''24:''' Standing Height - Corresponds to Unitref[049]

'''25:''' Kneeling Height - Corresponds to Unitref[050]

'''26:''' Floating Height - Corresponds to Unitref[051]

'''27:''' [[Damage#Susceptible_to...|Damage Modifier]] Category - Corresponds to Unitref[055]

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

'''Category''' '''Unit Type(s)'''
'''0''' Not for units, but is used for Terrain and Items
'''1''' Civilian, Sectoid, Celatid, Floater
'''2''' Personal Armor
'''3''' Power Suit, Flying Suit
'''4''' Tanks, Hovertanks
'''5''' Snakemen
'''6''' Ethereal
'''7''' Muton
'''8''' Silacoid
'''9''' Chryssalid
'''10''' Reaper
'''11''' Sectopod
'''12''' Cyberdisc
'''13''' Zombie

'''28:''' Psi Skill - Corresponds to Unitref[037]

'''29:''' Psi Strength - Corresponds to Unitref[057]

'''30:''' Bravery (encoded) - Corresponds to Unitref[059]

'''31:''' Motion scanner size - Corresponds to Unitref[061]

'''32:''' ''1 for Cyberdisc, 0 for all others including TFTD... isn't "Explodes"; the TFTD Bio-Drone also explodes...'' - Corresponds to Unitref[071]

I edited the Cyberdisc's field to 0 and checked to see if it exploded. It still did. Obviously this field is for something else. I'll work on this some more. --[[User:Zombie|Zombie]] 20:15, 15 September 2006 (PDT)

:I have a theory. I vaguely remember something about Cyberdiscs cannot be stunned. Even if you poke it with a Stun Rod and bypass it's self-destruct, it still counts as a kill. Maybe this has something to do with it (as I also remember that none of the other aliens exhibit this behavior)?--[[User:Amitakartok|amitakartok]] 12:55, 23 June 2009 (EDT)

::Good thinking. But the [[Stun]] page shows that Cyberdiscs can be stunned. Checking [[Unitref.Dat]] byte 71 (hex 0x47) shows that, after Zombie posted his statement, there's been a lot of on its [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page about this byte. -[[User:MikeTheRed|MikeTheRed]] 20:07, 2 July 2009 (EDT)

'''33:''' ''Unknown - Always 0'' No Corresponding Unitref offset

'''34:''' Corpse type - Corresponds to Unitref[038]

'''35:''' Big unit (2x2) No Corresponding Unitref offset

'''36:''' Victory point score - Corresponds to Unitref[039]

'''37:''' Aggression - Corresponds to Unitref[044]

'''38:''' Intelligence - Corresponds to Unitref[073]

''This data was just put together working heavily with Zombie and his great SC [http://www.strategycore.co.uk/xcom/pg/ufoalienstats alien stats] page.

= Country Labels =
Starting at offset 396480 (hex: 0x60CC0) are the records that contain the location of the labels for the country names on the world. In order they are X, Y, and English.dat index all signed short integers (6 bytes for each record). X should never be negative but between 0 and 2880, Y should be between -720 and 720 (See [[WORLD.DAT]]). The English.dat file, despite all other array indexes appears to start at 1 and not 0, thus a value of 611 in here represents index 610 in a zero based English.dat array. (It stands to reason that these work for the other language files as well)

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

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

= Detection Ranges =

Detection ranges are hard coded into the executable at the following locations (Win CE / Gold edition):

{| cellspacing="0" border="1"
!Platform
!Address
!Data bytes
!Hex
!Range
!nm
|-
|Aircraft||591EA||C8 00||x00C8||200||600
|-
|Hyperwave||59237||20 03||x0328||800||2400
|-
|Lg Radar||5926D||EE 02||x02EE||750||2250
|-
|Sm Radar||59278||F4 01||x01F4||500||1500
|}

Patching "88 13" to these locations = x1388 = 5000 range units = 15,000 nm pretty much gives that platform visibility over the whole world. Of course Small Radar still only has a 10% detection chance per half hour.

= Battlescape Terrain List =

In the UFO CE executable, offset 476156 (743FCx) marks the beginning of the [[WORLD.DAT]] terrain to battlescape terrain conversion list. 13 double byte values.

02 00 01 00 01 00 01 00 01 00 07 00 02 00 06 00 06 00 08 00 00 00 02 00 08 00

For example, a mission initiated in a GeoScape polygon of type 5 will be performed in battlescape terrain type 7 (mountains).

Note that jungle (type 00) missions in the north will end up as forest missions, and forest (type 02) missions in the south will end up as jungle missions. See offset 10 in [[GEODATA.DAT]] for the full battlescape terrain list.

= Manufacturing stats =

The original data for the product manufacturing information in [[PRODUCT.DAT]] is contained in the geoscape executable, at offset 355600 (for plain 1.4 version).

= XCOM: UFO Defense DOS Versions, difficulty setting bug =
In the DOS versions of the game there was a problem when saving the [[IGLOB.DAT]] file, that would cut off the last four bytes. When the saved game was loaded or at the end of a mission, the game would then be set to beginner, never to return again. There is a single byte that can be adjusted to fix this problem, you change the value from 60 (0x3C) to 64 (0x40). Below are the offsets so you can fix them in your game. 
 
<table {{StdDescTable}}>
<tr>
<th {{StdDescTable_Heading}}>'''Offset dec (hex)'''</th><th {{StdDescTable_Heading}}>'''Game Version'''</th>
</tr>
<tr><td>97228 (0x17BCC)</td><td>DOS Version 1.0</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.2</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.3</td></tr>
<tr><td>97228 (0x17BCC)</td><td>DOS Version 1.4</td></tr>
</table>
 
You can read more about the bug at the [[Known_Bugs#Difficulty_Bug|known bugs]] area.

= See Also =
* [[TACTICAL.EXE]] - Sister executable used for Turn based strategy (merged with geoscape.exe in WinCE edition)
* [[UNITREF.DAT]] - Stats on current units (both XCOM and Alien) in play
* [[Talk:GEOSCAPE.EXE]] - More offsets and investigations are on the Discussion page.
* [[Saved Game Files]]

[[Category:Game Files]]

GEOSCAPE.EXE

2010-01-07T00:29:37Z

Hatfarm: /* XCOM: UFO Defense DOS Versions, difficulty setting bug */

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

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

Also see [[Versions]].

= X-COM Complete Packages =

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

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

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

''Thanks, and welcome!''

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

==Review #1 by wfames==

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

==Review #2 by Draco Cracona==

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

==Review #3 by Muton commander==

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

==Review #4 by Diegoba==

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

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

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

= Craft Stats =

At offset 353,020 in X-COM 1.4 (DOS - modified by XCUtil), the aircraft statistics begin. In WinCE (XCUtil) this starts at hex offset 0x6F9A8 and Alien craft start at 0x6fa34.
''Emphyrio: start at 353014?, each entry 14 records of 2 bytes, 5 Xcom craft and then 8 Alien''

Each Vessel Statistic is two bytes and is 0 through 65,535 (in UGE format), and go in the following order:

Pointer to craft name in [[ENGLISH.DAT]] 
Points 
Weapon Pods 
Maximum Speed 
Acceleration 
Fuel 
Damage (armor) 
Size Class 
Unknown (UFO only stat). Believed to be the base firing interval of the weapon 
Unknown (UFO only stat). Value is roughly similar to score for destroying? 
Weapon Range (in 1/8ths of km)(UFOs only) 
Weapon Damage (UFOs only) 
Crew 
HWP 

To help you find it in UGE, here are the various X-COM vessel section in UGE format:

Skyranger: 248 - 2 - 2 - 0 - 220 - 5 - 150 - 0 
Lightning: 28 - 12 - 8 - 0 - 30 - 0 - 32 - 3 
Avenger: 24 - 21 - 10 - 0 - 60 - 0 - 176 - 4 
Interceptor: 52 - 8 - 3 - 0 - 232 - 3 - 100 - 0 
Firestorm: 104 - 16 - 9 - 0 - 20 - 0 - 244 - 1 

A bit below the Firestorm statistics are the stats for various Alien Ships, I'll probably do them later.

Here is a hex signature to help find the first alien craft record (Small Scout):

b2 02 64 00 02 00 98 08 0c 00 00 00 32 00

At offset 380,668 the Tank Statistics begin.

= Armor Stats =

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

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

Front Armor 
Left Armor 
Right Armor 
Rear Armor 
Under Armor 

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

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

So on, etc.

= Alien Stats =

This section is for the structure of the alien stats, as found in GEOSCAPE. For actual data and additional information, see the [[Alien_Stats|alien statistics]] page. Also see Zombie's excellent alien stats page at [http://www.strategycore.co.uk/xcom/pg/ufoalienstats StrategyCore]. ''(Have YOU made your StratCore and [http://www.xcomufo.com XCOMUFO] accounts yet?)''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

'''12:''' Front Armor - Corresponds to Unitref[029]

'''13:''' Left Armor - Corresponds to Unitref[030]

'''14:''' Right Armor - Corresponds to Unitref[031]

'''15:''' Rear Armor - Corresponds to Unitref[032]

'''16:''' Under Armor - Corresponds to Unitref[033]

'''17:''' ''Unknown - Always 0'' - Corresponds to Unitref[034]

'''18:''' Energy Recharge - Corresponds to Unitref[035]

'''19:''' ''Unknown - Always 0'' - Corresponds to Unitref[036]

'''20:''' ''Unknown - Always 1'' No Corresponding Unitref offset

'''21:''' ''Unknown - Always 0'' - Corresponds to Unitref[046]

'''22:''' ''Unknown'' - Corresponds to Unitref[048] (see below)

'''23:''' ''Unknown'' - Corresponds to Unitref[052] (see below)

''NOTE: For additional important info on the last two bytes, see [[Talk:UNITREF.DAT]]. My notes below do not take that info into account. For the moment though I'm leaving it as is. I sure wish we could figure the bytes out, and get rid of all the conjecture! - [[User:MikeTheRed|MikeTheRed]] 08:05, 6 November 2006 (PST)''

These Unitref bytes ([48] and [52]) and now Geoscape Core values have long stumped us hardcore X-Commies. The two bytes always equal the same value for a given alien, including all aliens of the same race (the N's below). And, they're the same between Geoscape and Unitref. Clearly it must be important (or a goof!), but exactly what it is, who knows. Although this page is for X-COM, I've included TFTD in the hopes it helps folks - but it's been so long since I've played TFTD, I can't remember those units at all.

How's this for a thought?...
Dimension Byte(s)

X 22

Y 23

Z 24 (top when standing)
25 (top when kneeling)
26 (bottom)

Maybe they represent the "size in profile" ("width"), affecting likelihood to hit. A game could be tried with a target 20 squares away, set 22 and 23 alternately to 5 or 2 (or 1 or 0?), and see if it affects the successful shots percentage. 0 or even 1 might break the game, though.

Also, how do these values (2 to 5) correlate with the "pixel drawings" of units? I can't seem to find that info at the moment... aren't units and tiles defined as something like 16x16x[[Height|28]]? If so, then perhaps the values (2 to 5) are multiplied by 3 or something to get their final "width" for bullet interception?? --[[User:MikeTheRed|MikeTheRed]] 05:20, 17 September 2006 (PDT)

:I finally got the OSG (w00t!), and noticed the following: The section on weapon accuracy says (p. 221) that target size affects the chance to hit, and "the 'size' of each alien is listed along with all other alien statistics in Chapter 9". But the alien stats tables (p. 250 ff.) only lists Height as a possible 'size' stat, and the text write-ups don't otherwise address "target size" with any precision. This discrepancy - that Chapter 8 talks about '''size''', but Chapter 9 only has '''height''' - might (might!) mean there are more variables that determine target area size, but somehow they didn't make it to the alien stats tables.

:The description for Height (p. 249) does say, "Taller creatures are easier to hit than short ones are. An alien with a height of 40, for example, is twice as easy to hit as an alien with a height of 20." (Note: The tallest [[Height]] is actually 23. And also notice, Float is never mentioned.) This ''might'' mean only height affects this, or it could be read in a general way; other dimensions (X and Y in addition to Z) might also affect it.

:Somebody should do some firing accuracy tests while hacking these potential X & Y bytes! But I still don't know how the values for [22] & [23] compare to what X-COM considers tile width... we know the Height byte accurately reflects the full range of possible values (0 to 23), but I doubt 5 is the full (pixel?) width of a tile. This might mean it's not width, then (or maybe [22] & [23] are added, or they are individually multiplied by 3 or something??) If anyone who knows about tile width could say something, I'd appreciate it. --[[User:MikeTheRed|MikeTheRed]] 11:24, 1 October 2006 (PDT)

In any event, here's a summary of bytes [22] and [23], in the hopes we can figure it out. They're always identical for a given race, and [22] always equals [23].

'''X-COM TFTD'''

Value Alien N Value Alien N

2 Sectoid 6 2 Aquatoid 6
Bio-Drone 1
3 Celatid 1 Tentaculat 1
Chryssalid 1
Civilian 2 3 Calcinite 1
Ethereal 3 Civilian 2
Floater 6 Deep_One 1
Muton 3 Gill_Man 4
Snakeman 5 Tasoth 2

4 Cyberdisc 1 4 Coelacant 1
Hovertank 1 Displacer 1
Reaper 1 Hallucinoid 1
Sectopod 1 Lobster_Man 5
Tank 1 Triscene 1
Xarquid 1
5 Silacoid 1

'''24:''' Standing Height - Corresponds to Unitref[049]

'''25:''' Kneeling Height - Corresponds to Unitref[050]

'''26:''' Floating Height - Corresponds to Unitref[051]

'''27:''' [[Damage#Susceptible_to...|Damage Modifier]] Category - Corresponds to Unitref[055]

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

'''Category''' '''Unit Type(s)'''
'''0''' Not for units, but is used for Terrain and Items
'''1''' Civilian, Sectoid, Celatid, Floater
'''2''' Personal Armor
'''3''' Power Suit, Flying Suit
'''4''' Tanks, Hovertanks
'''5''' Snakemen
'''6''' Ethereal
'''7''' Muton
'''8''' Silacoid
'''9''' Chryssalid
'''10''' Reaper
'''11''' Sectopod
'''12''' Cyberdisc
'''13''' Zombie

'''28:''' Psi Skill - Corresponds to Unitref[037]

'''29:''' Psi Strength - Corresponds to Unitref[057]

'''30:''' Bravery (encoded) - Corresponds to Unitref[059]

'''31:''' Motion scanner size - Corresponds to Unitref[061]

'''32:''' ''1 for Cyberdisc, 0 for all others including TFTD... isn't "Explodes"; the TFTD Bio-Drone also explodes...'' - Corresponds to Unitref[071]

I edited the Cyberdisc's field to 0 and checked to see if it exploded. It still did. Obviously this field is for something else. I'll work on this some more. --[[User:Zombie|Zombie]] 20:15, 15 September 2006 (PDT)

:I have a theory. I vaguely remember something about Cyberdiscs cannot be stunned. Even if you poke it with a Stun Rod and bypass it's self-destruct, it still counts as a kill. Maybe this has something to do with it (as I also remember that none of the other aliens exhibit this behavior)?--[[User:Amitakartok|amitakartok]] 12:55, 23 June 2009 (EDT)

::Good thinking. But the [[Stun]] page shows that Cyberdiscs can be stunned. Checking [[Unitref.Dat]] byte 71 (hex 0x47) shows that, after Zombie posted his statement, there's been a lot of on its [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page about this byte. -[[User:MikeTheRed|MikeTheRed]] 20:07, 2 July 2009 (EDT)

'''33:''' ''Unknown - Always 0'' No Corresponding Unitref offset

'''34:''' Corpse type - Corresponds to Unitref[038]

'''35:''' Big unit (2x2) No Corresponding Unitref offset

'''36:''' Victory point score - Corresponds to Unitref[039]

'''37:''' Aggression - Corresponds to Unitref[044]

'''38:''' Intelligence - Corresponds to Unitref[073]

''This data was just put together working heavily with Zombie and his great SC [http://www.strategycore.co.uk/xcom/pg/ufoalienstats alien stats] page.

= Country Labels =
Starting at offset 396480 (hex: 0x60CC0) are the records that contain the location of the labels for the country names on the world. In order they are X, Y, and English.dat index all signed short integers (6 bytes for each record). X should never be negative but between 0 and 2880, Y should be between -720 and 720 (See [[WORLD.DAT]]). The English.dat file, despite all other array indexes appears to start at 1 and not 0, thus a value of 611 in here represents index 610 in a zero based English.dat array. (It stands to reason that these work for the other language files as well)

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

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

= Detection Ranges =

Detection ranges are hard coded into the executable at the following locations (Win CE / Gold edition):

{| cellspacing="0" border="1"
!Platform
!Address
!Data bytes
!Hex
!Range
!nm
|-
|Aircraft||591EA||C8 00||x00C8||200||600
|-
|Hyperwave||59237||20 03||x0328||800||2400
|-
|Lg Radar||5926D||EE 02||x02EE||750||2250
|-
|Sm Radar||59278||F4 01||x01F4||500||1500
|}

Patching "88 13" to these locations = x1388 = 5000 range units = 15,000 nm pretty much gives that platform visibility over the whole world. Of course Small Radar still only has a 10% detection chance per half hour.

= Battlescape Terrain List =

In the UFO CE executable, offset 476156 (743FCx) marks the beginning of the [[WORLD.DAT]] terrain to battlescape terrain conversion list. 13 double byte values.

02 00 01 00 01 00 01 00 01 00 07 00 02 00 06 00 06 00 08 00 00 00 02 00 08 00

For example, a mission initiated in a GeoScape polygon of type 5 will be performed in battlescape terrain type 7 (mountains).

Note that jungle (type 00) missions in the north will end up as forest missions, and forest (type 02) missions in the south will end up as jungle missions. See offset 10 in [[GEODATA.DAT]] for the full battlescape terrain list.

= Manufacturing stats =

The original data for the product manufacturing information in [[PRODUCT.DAT]] is contained in the geoscape executable, at offset 355600 (for plain 1.4 version).

= XCOM: UFO Defense DOS Versions, difficulty setting bug =
In the DOS versions of the game there was a problem when saving the [[IGLOB.DAT]] file, that would cut off the last four bytes. When the saved game was loaded or at the end of a mission, the game would then be set to beginner, never to return again. There is a single byte that can be adjusted to fix this problem, you change the value from 60 (0x3C) to 64 (0x40). Below are the offsets so you can fix them in your game.
 
<table {{StdDescTable}}>
<tr>
<th {{StdDescTable_Heading}}>'''Offset dec (hex)'''</th><th {{StdDescTable_Heading}}>'''Game Version'''</th>
</tr>
<tr><td>97228 (0x17BCC)</td><td>DOS Version 1.0</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.2</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.3</td></tr>
<tr><td>97228 (0x17BCC)</td><td>DOS Version 1.4</td></tr>
</table>
 
You can read more about the bug at the [[Known_Bugs#Difficulty_Bug|known bugs]] area.

= See Also =
* [[TACTICAL.EXE]] - Sister executable used for Turn based strategy (merged with geoscape.exe in WinCE edition)
* [[UNITREF.DAT]] - Stats on current units (both XCOM and Alien) in play
* [[Talk:GEOSCAPE.EXE]] - More offsets and investigations are on the Discussion page.
* [[Saved Game Files]]

[[Category:Game Files]]

GEOSCAPE.EXE

2010-01-07T00:28:56Z

Hatfarm: /* XCOM: UFO Defense DOS Versions, difficulty setting bug */

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

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

Also see [[Versions]].

= X-COM Complete Packages =

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

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

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

''Thanks, and welcome!''

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

==Review #1 by wfames==

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

==Review #2 by Draco Cracona==

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

==Review #3 by Muton commander==

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

==Review #4 by Diegoba==

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

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

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

= Craft Stats =

At offset 353,020 in X-COM 1.4 (DOS - modified by XCUtil), the aircraft statistics begin. In WinCE (XCUtil) this starts at hex offset 0x6F9A8 and Alien craft start at 0x6fa34.
''Emphyrio: start at 353014?, each entry 14 records of 2 bytes, 5 Xcom craft and then 8 Alien''

Each Vessel Statistic is two bytes and is 0 through 65,535 (in UGE format), and go in the following order:

Pointer to craft name in [[ENGLISH.DAT]] 
Points 
Weapon Pods 
Maximum Speed 
Acceleration 
Fuel 
Damage (armor) 
Size Class 
Unknown (UFO only stat). Believed to be the base firing interval of the weapon 
Unknown (UFO only stat). Value is roughly similar to score for destroying? 
Weapon Range (in 1/8ths of km)(UFOs only) 
Weapon Damage (UFOs only) 
Crew 
HWP 

To help you find it in UGE, here are the various X-COM vessel section in UGE format:

Skyranger: 248 - 2 - 2 - 0 - 220 - 5 - 150 - 0 
Lightning: 28 - 12 - 8 - 0 - 30 - 0 - 32 - 3 
Avenger: 24 - 21 - 10 - 0 - 60 - 0 - 176 - 4 
Interceptor: 52 - 8 - 3 - 0 - 232 - 3 - 100 - 0 
Firestorm: 104 - 16 - 9 - 0 - 20 - 0 - 244 - 1 

A bit below the Firestorm statistics are the stats for various Alien Ships, I'll probably do them later.

Here is a hex signature to help find the first alien craft record (Small Scout):

b2 02 64 00 02 00 98 08 0c 00 00 00 32 00

At offset 380,668 the Tank Statistics begin.

= Armor Stats =

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

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

Front Armor 
Left Armor 
Right Armor 
Rear Armor 
Under Armor 

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

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

So on, etc.

= Alien Stats =

This section is for the structure of the alien stats, as found in GEOSCAPE. For actual data and additional information, see the [[Alien_Stats|alien statistics]] page. Also see Zombie's excellent alien stats page at [http://www.strategycore.co.uk/xcom/pg/ufoalienstats StrategyCore]. ''(Have YOU made your StratCore and [http://www.xcomufo.com XCOMUFO] accounts yet?)''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

'''12:''' Front Armor - Corresponds to Unitref[029]

'''13:''' Left Armor - Corresponds to Unitref[030]

'''14:''' Right Armor - Corresponds to Unitref[031]

'''15:''' Rear Armor - Corresponds to Unitref[032]

'''16:''' Under Armor - Corresponds to Unitref[033]

'''17:''' ''Unknown - Always 0'' - Corresponds to Unitref[034]

'''18:''' Energy Recharge - Corresponds to Unitref[035]

'''19:''' ''Unknown - Always 0'' - Corresponds to Unitref[036]

'''20:''' ''Unknown - Always 1'' No Corresponding Unitref offset

'''21:''' ''Unknown - Always 0'' - Corresponds to Unitref[046]

'''22:''' ''Unknown'' - Corresponds to Unitref[048] (see below)

'''23:''' ''Unknown'' - Corresponds to Unitref[052] (see below)

''NOTE: For additional important info on the last two bytes, see [[Talk:UNITREF.DAT]]. My notes below do not take that info into account. For the moment though I'm leaving it as is. I sure wish we could figure the bytes out, and get rid of all the conjecture! - [[User:MikeTheRed|MikeTheRed]] 08:05, 6 November 2006 (PST)''

These Unitref bytes ([48] and [52]) and now Geoscape Core values have long stumped us hardcore X-Commies. The two bytes always equal the same value for a given alien, including all aliens of the same race (the N's below). And, they're the same between Geoscape and Unitref. Clearly it must be important (or a goof!), but exactly what it is, who knows. Although this page is for X-COM, I've included TFTD in the hopes it helps folks - but it's been so long since I've played TFTD, I can't remember those units at all.

How's this for a thought?...
Dimension Byte(s)

X 22

Y 23

Z 24 (top when standing)
25 (top when kneeling)
26 (bottom)

Maybe they represent the "size in profile" ("width"), affecting likelihood to hit. A game could be tried with a target 20 squares away, set 22 and 23 alternately to 5 or 2 (or 1 or 0?), and see if it affects the successful shots percentage. 0 or even 1 might break the game, though.

Also, how do these values (2 to 5) correlate with the "pixel drawings" of units? I can't seem to find that info at the moment... aren't units and tiles defined as something like 16x16x[[Height|28]]? If so, then perhaps the values (2 to 5) are multiplied by 3 or something to get their final "width" for bullet interception?? --[[User:MikeTheRed|MikeTheRed]] 05:20, 17 September 2006 (PDT)

:I finally got the OSG (w00t!), and noticed the following: The section on weapon accuracy says (p. 221) that target size affects the chance to hit, and "the 'size' of each alien is listed along with all other alien statistics in Chapter 9". But the alien stats tables (p. 250 ff.) only lists Height as a possible 'size' stat, and the text write-ups don't otherwise address "target size" with any precision. This discrepancy - that Chapter 8 talks about '''size''', but Chapter 9 only has '''height''' - might (might!) mean there are more variables that determine target area size, but somehow they didn't make it to the alien stats tables.

:The description for Height (p. 249) does say, "Taller creatures are easier to hit than short ones are. An alien with a height of 40, for example, is twice as easy to hit as an alien with a height of 20." (Note: The tallest [[Height]] is actually 23. And also notice, Float is never mentioned.) This ''might'' mean only height affects this, or it could be read in a general way; other dimensions (X and Y in addition to Z) might also affect it.

:Somebody should do some firing accuracy tests while hacking these potential X & Y bytes! But I still don't know how the values for [22] & [23] compare to what X-COM considers tile width... we know the Height byte accurately reflects the full range of possible values (0 to 23), but I doubt 5 is the full (pixel?) width of a tile. This might mean it's not width, then (or maybe [22] & [23] are added, or they are individually multiplied by 3 or something??) If anyone who knows about tile width could say something, I'd appreciate it. --[[User:MikeTheRed|MikeTheRed]] 11:24, 1 October 2006 (PDT)

In any event, here's a summary of bytes [22] and [23], in the hopes we can figure it out. They're always identical for a given race, and [22] always equals [23].

'''X-COM TFTD'''

Value Alien N Value Alien N

2 Sectoid 6 2 Aquatoid 6
Bio-Drone 1
3 Celatid 1 Tentaculat 1
Chryssalid 1
Civilian 2 3 Calcinite 1
Ethereal 3 Civilian 2
Floater 6 Deep_One 1
Muton 3 Gill_Man 4
Snakeman 5 Tasoth 2

4 Cyberdisc 1 4 Coelacant 1
Hovertank 1 Displacer 1
Reaper 1 Hallucinoid 1
Sectopod 1 Lobster_Man 5
Tank 1 Triscene 1
Xarquid 1
5 Silacoid 1

'''24:''' Standing Height - Corresponds to Unitref[049]

'''25:''' Kneeling Height - Corresponds to Unitref[050]

'''26:''' Floating Height - Corresponds to Unitref[051]

'''27:''' [[Damage#Susceptible_to...|Damage Modifier]] Category - Corresponds to Unitref[055]

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

'''Category''' '''Unit Type(s)'''
'''0''' Not for units, but is used for Terrain and Items
'''1''' Civilian, Sectoid, Celatid, Floater
'''2''' Personal Armor
'''3''' Power Suit, Flying Suit
'''4''' Tanks, Hovertanks
'''5''' Snakemen
'''6''' Ethereal
'''7''' Muton
'''8''' Silacoid
'''9''' Chryssalid
'''10''' Reaper
'''11''' Sectopod
'''12''' Cyberdisc
'''13''' Zombie

'''28:''' Psi Skill - Corresponds to Unitref[037]

'''29:''' Psi Strength - Corresponds to Unitref[057]

'''30:''' Bravery (encoded) - Corresponds to Unitref[059]

'''31:''' Motion scanner size - Corresponds to Unitref[061]

'''32:''' ''1 for Cyberdisc, 0 for all others including TFTD... isn't "Explodes"; the TFTD Bio-Drone also explodes...'' - Corresponds to Unitref[071]

I edited the Cyberdisc's field to 0 and checked to see if it exploded. It still did. Obviously this field is for something else. I'll work on this some more. --[[User:Zombie|Zombie]] 20:15, 15 September 2006 (PDT)

:I have a theory. I vaguely remember something about Cyberdiscs cannot be stunned. Even if you poke it with a Stun Rod and bypass it's self-destruct, it still counts as a kill. Maybe this has something to do with it (as I also remember that none of the other aliens exhibit this behavior)?--[[User:Amitakartok|amitakartok]] 12:55, 23 June 2009 (EDT)

::Good thinking. But the [[Stun]] page shows that Cyberdiscs can be stunned. Checking [[Unitref.Dat]] byte 71 (hex 0x47) shows that, after Zombie posted his statement, there's been a lot of on its [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page about this byte. -[[User:MikeTheRed|MikeTheRed]] 20:07, 2 July 2009 (EDT)

'''33:''' ''Unknown - Always 0'' No Corresponding Unitref offset

'''34:''' Corpse type - Corresponds to Unitref[038]

'''35:''' Big unit (2x2) No Corresponding Unitref offset

'''36:''' Victory point score - Corresponds to Unitref[039]

'''37:''' Aggression - Corresponds to Unitref[044]

'''38:''' Intelligence - Corresponds to Unitref[073]

''This data was just put together working heavily with Zombie and his great SC [http://www.strategycore.co.uk/xcom/pg/ufoalienstats alien stats] page.

= Country Labels =
Starting at offset 396480 (hex: 0x60CC0) are the records that contain the location of the labels for the country names on the world. In order they are X, Y, and English.dat index all signed short integers (6 bytes for each record). X should never be negative but between 0 and 2880, Y should be between -720 and 720 (See [[WORLD.DAT]]). The English.dat file, despite all other array indexes appears to start at 1 and not 0, thus a value of 611 in here represents index 610 in a zero based English.dat array. (It stands to reason that these work for the other language files as well)

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

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

= Detection Ranges =

Detection ranges are hard coded into the executable at the following locations (Win CE / Gold edition):

{| cellspacing="0" border="1"
!Platform
!Address
!Data bytes
!Hex
!Range
!nm
|-
|Aircraft||591EA||C8 00||x00C8||200||600
|-
|Hyperwave||59237||20 03||x0328||800||2400
|-
|Lg Radar||5926D||EE 02||x02EE||750||2250
|-
|Sm Radar||59278||F4 01||x01F4||500||1500
|}

Patching "88 13" to these locations = x1388 = 5000 range units = 15,000 nm pretty much gives that platform visibility over the whole world. Of course Small Radar still only has a 10% detection chance per half hour.

= Battlescape Terrain List =

In the UFO CE executable, offset 476156 (743FCx) marks the beginning of the [[WORLD.DAT]] terrain to battlescape terrain conversion list. 13 double byte values.

02 00 01 00 01 00 01 00 01 00 07 00 02 00 06 00 06 00 08 00 00 00 02 00 08 00

For example, a mission initiated in a GeoScape polygon of type 5 will be performed in battlescape terrain type 7 (mountains).

Note that jungle (type 00) missions in the north will end up as forest missions, and forest (type 02) missions in the south will end up as jungle missions. See offset 10 in [[GEODATA.DAT]] for the full battlescape terrain list.

= Manufacturing stats =

The original data for the product manufacturing information in [[PRODUCT.DAT]] is contained in the geoscape executable, at offset 355600 (for plain 1.4 version).

= XCOM: UFO Defense DOS Versions, difficulty setting bug =
In the DOS versions of the game there was a problem when saving the [[IGLOB.DAT]] file, that would cut off the last four bytes. When the saved game was loaded or at the end of a mission, the game would then be set to beginner, never to return again. There is a single byte that can be adjusted to fix this problem, you change the value from 0x3C (60) to 0x40 (64). Below are the offsets so you can fix them in your game.
 
<table {{StdDescTable}}>
<tr>
<th {{StdDescTable_Heading}}>'''Offset dec (hex)'''</th><th {{StdDescTable_Heading}}>'''Game Version'''</th>
</tr>
<tr><td>97228 (0x17BCC)</td><td>DOS Version 1.0</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.2</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.3</td></tr>
<tr><td>97228 (0x17BCC)</td><td>DOS Version 1.4</td></tr>
</table>
 
You can read more about the bug at the [[Known_Bugs#Difficulty_Bug|known bugs]] area.

= See Also =
* [[TACTICAL.EXE]] - Sister executable used for Turn based strategy (merged with geoscape.exe in WinCE edition)
* [[UNITREF.DAT]] - Stats on current units (both XCOM and Alien) in play
* [[Talk:GEOSCAPE.EXE]] - More offsets and investigations are on the Discussion page.
* [[Saved Game Files]]

[[Category:Game Files]]

GEOSCAPE.EXE

2010-01-07T00:19:24Z

Hatfarm:

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

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

Also see [[Versions]].

= X-COM Complete Packages =

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

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

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

''Thanks, and welcome!''

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

==Review #1 by wfames==

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

==Review #2 by Draco Cracona==

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

==Review #3 by Muton commander==

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

==Review #4 by Diegoba==

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

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

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

= Craft Stats =

At offset 353,020 in X-COM 1.4 (DOS - modified by XCUtil), the aircraft statistics begin. In WinCE (XCUtil) this starts at hex offset 0x6F9A8 and Alien craft start at 0x6fa34.
''Emphyrio: start at 353014?, each entry 14 records of 2 bytes, 5 Xcom craft and then 8 Alien''

Each Vessel Statistic is two bytes and is 0 through 65,535 (in UGE format), and go in the following order:

Pointer to craft name in [[ENGLISH.DAT]] 
Points 
Weapon Pods 
Maximum Speed 
Acceleration 
Fuel 
Damage (armor) 
Size Class 
Unknown (UFO only stat). Believed to be the base firing interval of the weapon 
Unknown (UFO only stat). Value is roughly similar to score for destroying? 
Weapon Range (in 1/8ths of km)(UFOs only) 
Weapon Damage (UFOs only) 
Crew 
HWP 

To help you find it in UGE, here are the various X-COM vessel section in UGE format:

Skyranger: 248 - 2 - 2 - 0 - 220 - 5 - 150 - 0 
Lightning: 28 - 12 - 8 - 0 - 30 - 0 - 32 - 3 
Avenger: 24 - 21 - 10 - 0 - 60 - 0 - 176 - 4 
Interceptor: 52 - 8 - 3 - 0 - 232 - 3 - 100 - 0 
Firestorm: 104 - 16 - 9 - 0 - 20 - 0 - 244 - 1 

A bit below the Firestorm statistics are the stats for various Alien Ships, I'll probably do them later.

Here is a hex signature to help find the first alien craft record (Small Scout):

b2 02 64 00 02 00 98 08 0c 00 00 00 32 00

At offset 380,668 the Tank Statistics begin.

= Armor Stats =

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

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

Front Armor 
Left Armor 
Right Armor 
Rear Armor 
Under Armor 

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

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

So on, etc.

= Alien Stats =

This section is for the structure of the alien stats, as found in GEOSCAPE. For actual data and additional information, see the [[Alien_Stats|alien statistics]] page. Also see Zombie's excellent alien stats page at [http://www.strategycore.co.uk/xcom/pg/ufoalienstats StrategyCore]. ''(Have YOU made your StratCore and [http://www.xcomufo.com XCOMUFO] accounts yet?)''

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

'''12:''' Front Armor - Corresponds to Unitref[029]

'''13:''' Left Armor - Corresponds to Unitref[030]

'''14:''' Right Armor - Corresponds to Unitref[031]

'''15:''' Rear Armor - Corresponds to Unitref[032]

'''16:''' Under Armor - Corresponds to Unitref[033]

'''17:''' ''Unknown - Always 0'' - Corresponds to Unitref[034]

'''18:''' Energy Recharge - Corresponds to Unitref[035]

'''19:''' ''Unknown - Always 0'' - Corresponds to Unitref[036]

'''20:''' ''Unknown - Always 1'' No Corresponding Unitref offset

'''21:''' ''Unknown - Always 0'' - Corresponds to Unitref[046]

'''22:''' ''Unknown'' - Corresponds to Unitref[048] (see below)

'''23:''' ''Unknown'' - Corresponds to Unitref[052] (see below)

''NOTE: For additional important info on the last two bytes, see [[Talk:UNITREF.DAT]]. My notes below do not take that info into account. For the moment though I'm leaving it as is. I sure wish we could figure the bytes out, and get rid of all the conjecture! - [[User:MikeTheRed|MikeTheRed]] 08:05, 6 November 2006 (PST)''

These Unitref bytes ([48] and [52]) and now Geoscape Core values have long stumped us hardcore X-Commies. The two bytes always equal the same value for a given alien, including all aliens of the same race (the N's below). And, they're the same between Geoscape and Unitref. Clearly it must be important (or a goof!), but exactly what it is, who knows. Although this page is for X-COM, I've included TFTD in the hopes it helps folks - but it's been so long since I've played TFTD, I can't remember those units at all.

How's this for a thought?...
Dimension Byte(s)

X 22

Y 23

Z 24 (top when standing)
25 (top when kneeling)
26 (bottom)

Maybe they represent the "size in profile" ("width"), affecting likelihood to hit. A game could be tried with a target 20 squares away, set 22 and 23 alternately to 5 or 2 (or 1 or 0?), and see if it affects the successful shots percentage. 0 or even 1 might break the game, though.

Also, how do these values (2 to 5) correlate with the "pixel drawings" of units? I can't seem to find that info at the moment... aren't units and tiles defined as something like 16x16x[[Height|28]]? If so, then perhaps the values (2 to 5) are multiplied by 3 or something to get their final "width" for bullet interception?? --[[User:MikeTheRed|MikeTheRed]] 05:20, 17 September 2006 (PDT)

:I finally got the OSG (w00t!), and noticed the following: The section on weapon accuracy says (p. 221) that target size affects the chance to hit, and "the 'size' of each alien is listed along with all other alien statistics in Chapter 9". But the alien stats tables (p. 250 ff.) only lists Height as a possible 'size' stat, and the text write-ups don't otherwise address "target size" with any precision. This discrepancy - that Chapter 8 talks about '''size''', but Chapter 9 only has '''height''' - might (might!) mean there are more variables that determine target area size, but somehow they didn't make it to the alien stats tables.

:The description for Height (p. 249) does say, "Taller creatures are easier to hit than short ones are. An alien with a height of 40, for example, is twice as easy to hit as an alien with a height of 20." (Note: The tallest [[Height]] is actually 23. And also notice, Float is never mentioned.) This ''might'' mean only height affects this, or it could be read in a general way; other dimensions (X and Y in addition to Z) might also affect it.

:Somebody should do some firing accuracy tests while hacking these potential X & Y bytes! But I still don't know how the values for [22] & [23] compare to what X-COM considers tile width... we know the Height byte accurately reflects the full range of possible values (0 to 23), but I doubt 5 is the full (pixel?) width of a tile. This might mean it's not width, then (or maybe [22] & [23] are added, or they are individually multiplied by 3 or something??) If anyone who knows about tile width could say something, I'd appreciate it. --[[User:MikeTheRed|MikeTheRed]] 11:24, 1 October 2006 (PDT)

In any event, here's a summary of bytes [22] and [23], in the hopes we can figure it out. They're always identical for a given race, and [22] always equals [23].

'''X-COM TFTD'''

Value Alien N Value Alien N

2 Sectoid 6 2 Aquatoid 6
Bio-Drone 1
3 Celatid 1 Tentaculat 1
Chryssalid 1
Civilian 2 3 Calcinite 1
Ethereal 3 Civilian 2
Floater 6 Deep_One 1
Muton 3 Gill_Man 4
Snakeman 5 Tasoth 2

4 Cyberdisc 1 4 Coelacant 1
Hovertank 1 Displacer 1
Reaper 1 Hallucinoid 1
Sectopod 1 Lobster_Man 5
Tank 1 Triscene 1
Xarquid 1
5 Silacoid 1

'''24:''' Standing Height - Corresponds to Unitref[049]

'''25:''' Kneeling Height - Corresponds to Unitref[050]

'''26:''' Floating Height - Corresponds to Unitref[051]

'''27:''' [[Damage#Susceptible_to...|Damage Modifier]] Category - Corresponds to Unitref[055]

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

'''Category''' '''Unit Type(s)'''
'''0''' Not for units, but is used for Terrain and Items
'''1''' Civilian, Sectoid, Celatid, Floater
'''2''' Personal Armor
'''3''' Power Suit, Flying Suit
'''4''' Tanks, Hovertanks
'''5''' Snakemen
'''6''' Ethereal
'''7''' Muton
'''8''' Silacoid
'''9''' Chryssalid
'''10''' Reaper
'''11''' Sectopod
'''12''' Cyberdisc
'''13''' Zombie

'''28:''' Psi Skill - Corresponds to Unitref[037]

'''29:''' Psi Strength - Corresponds to Unitref[057]

'''30:''' Bravery (encoded) - Corresponds to Unitref[059]

'''31:''' Motion scanner size - Corresponds to Unitref[061]

'''32:''' ''1 for Cyberdisc, 0 for all others including TFTD... isn't "Explodes"; the TFTD Bio-Drone also explodes...'' - Corresponds to Unitref[071]

I edited the Cyberdisc's field to 0 and checked to see if it exploded. It still did. Obviously this field is for something else. I'll work on this some more. --[[User:Zombie|Zombie]] 20:15, 15 September 2006 (PDT)

:I have a theory. I vaguely remember something about Cyberdiscs cannot be stunned. Even if you poke it with a Stun Rod and bypass it's self-destruct, it still counts as a kill. Maybe this has something to do with it (as I also remember that none of the other aliens exhibit this behavior)?--[[User:Amitakartok|amitakartok]] 12:55, 23 June 2009 (EDT)

::Good thinking. But the [[Stun]] page shows that Cyberdiscs can be stunned. Checking [[Unitref.Dat]] byte 71 (hex 0x47) shows that, after Zombie posted his statement, there's been a lot of on its [[Talk:UNITREF.DAT#Offset_0x47|Talk]] page about this byte. -[[User:MikeTheRed|MikeTheRed]] 20:07, 2 July 2009 (EDT)

'''33:''' ''Unknown - Always 0'' No Corresponding Unitref offset

'''34:''' Corpse type - Corresponds to Unitref[038]

'''35:''' Big unit (2x2) No Corresponding Unitref offset

'''36:''' Victory point score - Corresponds to Unitref[039]

'''37:''' Aggression - Corresponds to Unitref[044]

'''38:''' Intelligence - Corresponds to Unitref[073]

''This data was just put together working heavily with Zombie and his great SC [http://www.strategycore.co.uk/xcom/pg/ufoalienstats alien stats] page.

= Country Labels =
Starting at offset 396480 (hex: 0x60CC0) are the records that contain the location of the labels for the country names on the world. In order they are X, Y, and English.dat index all signed short integers (6 bytes for each record). X should never be negative but between 0 and 2880, Y should be between -720 and 720 (See [[WORLD.DAT]]). The English.dat file, despite all other array indexes appears to start at 1 and not 0, thus a value of 611 in here represents index 610 in a zero based English.dat array. (It stands to reason that these work for the other language files as well)

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

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

= Detection Ranges =

Detection ranges are hard coded into the executable at the following locations (Win CE / Gold edition):

{| cellspacing="0" border="1"
!Platform
!Address
!Data bytes
!Hex
!Range
!nm
|-
|Aircraft||591EA||C8 00||x00C8||200||600
|-
|Hyperwave||59237||20 03||x0328||800||2400
|-
|Lg Radar||5926D||EE 02||x02EE||750||2250
|-
|Sm Radar||59278||F4 01||x01F4||500||1500
|}

Patching "88 13" to these locations = x1388 = 5000 range units = 15,000 nm pretty much gives that platform visibility over the whole world. Of course Small Radar still only has a 10% detection chance per half hour.

= Battlescape Terrain List =

In the UFO CE executable, offset 476156 (743FCx) marks the beginning of the [[WORLD.DAT]] terrain to battlescape terrain conversion list. 13 double byte values.

02 00 01 00 01 00 01 00 01 00 07 00 02 00 06 00 06 00 08 00 00 00 02 00 08 00

For example, a mission initiated in a GeoScape polygon of type 5 will be performed in battlescape terrain type 7 (mountains).

Note that jungle (type 00) missions in the north will end up as forest missions, and forest (type 02) missions in the south will end up as jungle missions. See offset 10 in [[GEODATA.DAT]] for the full battlescape terrain list.

= Manufacturing stats =

The original data for the product manufacturing information in [[PRODUCT.DAT]] is contained in the geoscape executable, at offset 355600 (for plain 1.4 version).

= XCOM: UFO Defense DOS Versions, difficulty setting bug =
In the DOS versions of the game there was a problem when saving the [[IGLOB.DAT]] file, that would cut off the last four bytes. When the saved game was loaded or at the end of a mission, the game would then be set to beginner, never to return again. There is a single byte that can be adjusted to fix this problem, below are those offsets so you can fix them in your game.
 
<table {{StdDescTable}}>
<tr>
<th {{StdDescTable_Heading}}>'''Offset dec (hex)'''</th><th {{StdDescTable_Heading}}>'''Game Version'''</th>
</tr>
<tr><td>97228 (0x17BCC)</td><td>DOS Version 1.0</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.2</td></tr>
<tr><td>101068 (0x18ACC)</td><td>DOS Version 1.3</td></tr>
<tr><td>97228 (0x17BCC)</td><td>DOS Version 1.4</td></tr>
</table>
 
You can read more about the bug at the [[Known_Bugs#Difficulty_Bug|known bugs]] area.

= See Also =
* [[TACTICAL.EXE]] - Sister executable used for Turn based strategy (merged with geoscape.exe in WinCE edition)
* [[UNITREF.DAT]] - Stats on current units (both XCOM and Alien) in play
* [[Talk:GEOSCAPE.EXE]] - More offsets and investigations are on the Discussion page.
* [[Saved Game Files]]

[[Category:Game Files]]

DIPLOM.DAT

2009-12-31T09:03:45Z

Hatfarm:

This file contains the information about how much money the various nations are giving you in funding, both current and for the graph, among other things. It is 576 bytes long, split into 16 records of 36 bytes long, one for each country. The record start points, by country are:

<table {{StdCenterTable}} class="sortable">
<tr {{StdDescTable_Heading}}>
<th>Offset dec (hex)</th>
<th width="150">Country</th></tr>
<tr><td>0 (0x0000)</td><td>USA</td></tr>
<tr><td>36 (0x0024)</td><td>Russia</td></tr>
<tr><td>72 (0x0048)</td><td>UK</td></tr>
<tr><td>108 (0x006C)</td><td>France</td></tr>
<tr><td>144 (0x0090)</td><td>Germany</td></tr>
<tr><td>180 (0x00B4)</td><td>Italy</td></tr>
<tr><td>216 (0x00D8)</td><td>Spain</td></tr>
<tr><td>252 (0x00FC)</td><td>China</td></tr>
<tr><td>288 (0x0120)</td><td>Japan</td></tr>
<tr><td>324 (0x0144)</td><td>India</td></tr>
<tr><td>360 (0x0168)</td><td>Brazil</td></tr>
<tr><td>396 (0x018C)</td><td>Australia</td></tr>
<tr><td>432 (0x01B0)</td><td>Nigeria</td></tr>
<tr><td>468 (0x01D4)</td><td>South Africa</td></tr>
<tr><td>504 (0x01F8)</td><td>Egypt</td></tr>
<tr><td>540 (0x021C)</td><td>Canada</td></tr>
</table>

Within each record, there are several pieces of information, they are all signed 2 byte numeric fields:

<table {{StdDescTable}}>
<tr>
<th {{StdDescTable_Heading}}>'''Offset dec (hex)'''</th><th {{StdDescTable_Heading}}>'''Meaning'''</th>
</tr>
<tr><td>0 (0x00)</td><td>Pointer to country name in string table (starts at 602 (0x025A), increase 1 each record) </td></tr>
<tr><td>2 (0x02)</td><td>Satisfaction Rating, 3 is happy, 2 is average, 1 is unhappy, 0 will sign pact/stop funding </td></tr>
<tr><td>4 to 26 (0x04 to 0x1A)</td><td>Funding values (in $k) starts with Jan, runs to Dec</td></tr>
<tr><td>28 (0x1C)</td><td>Funding change (in $k) </td></tr>
<tr><td>30 (0x1E)</td><td>Non zero (1 when game sets it) means that the country will sign pact at end of month</td></tr>
<tr><td>32 (0x20)</td><td>Starting Funding base value, ranges 110 to 600 (in $k)</td></tr>
<tr><td>34 (0x22)</td><td>Funding cap (ranges 2k to 10k, equates to 2-10M)</td></tr>
</table>

Note that Satisfaction rating does not seem to drop to 2 any month a country doesnt increase funding, so not sure of the extra relationship here, but 0 always results in them stopping funding at the end of the month (I think you still get paid the one last time, as you are always seeing next months budget effectively). Possibly happy countries can randomly decide to not increase funding anyway. Setting this value to 2 or 1 before month end doesnt seem to affect the funding change either, setting it 0 will though, at least when you have a good score.

Bytes 32 to 33 are what is used to base the starting Funding on, it initially randomly gets a value from 100-200% of the value listed for each country. For game balance reasons it then scales the entire result so that it comes to approximately 6 million, with an error of +-15 because of the way it scales the result, this can sometimes push a country slightly higher or lower than the original range would have allowed it to. Changing these values has no in game effect anyway, as they are used before the first save is created.

<table {{StdCenterTable}} class="sortable">
<tr {{StdDescTable_Heading}}>
<th width="150">Country</th>
<th>Starting Funding base</th>
<th>Funding Cap (k)</th></tr>
<tr><td>USA</td><td>600</td><td>10000</td></tr>
<tr><td>Russia</td><td>230</td><td>8000</td></tr>
<tr><td>UK</td><td>240</td><td>7000</td></tr>
<tr><td>France</td><td>320</td><td>8000</td></tr>
<tr><td>Germany</td><td>250</td><td>9000</td></tr>
<tr><td>Italy</td><td>160</td><td>6000</td></tr>
<tr><td>Spain</td><td>140</td><td>5000</td></tr>
<tr><td>China</td><td>245</td><td>7000</td></tr>
<tr><td>Japan</td><td>400</td><td>10000</td></tr>
<tr><td>India</td><td>150</td><td>5000</td></tr>
<tr><td>Brazil</td><td>300</td><td>4000</td></tr>
<tr><td>Australia</td><td>280</td><td>5000</td></tr>
<tr><td>Nigeria</td><td>180</td><td>2000</td></tr>
<tr><td>South Africa</td><td>310</td><td>3000</td></tr>
<tr><td>Egypt</td><td>160</td><td>2000</td></tr>
<tr><td>Canada</td><td>110</td><td>4000</td></tr>
</table>

According to these values, the maximum theoretical funding you can get is 95M per month, if you can max out all 16 countries budgets.

Note that you can manually insert a monthly funding number into the current month for any country, and it will award you that amount at the end of the month. If funding for that country increases (changes?) it will apply the funding cap to next months budget, and then it will remain at the cap from then on (unless you do badly and it drops), so to permanently increase funding beyond these limits the cap has to be modified. If funding is static for that month, it just copies the value across without applying the funding cap.

==See Also==
[[Saved Game Files]]
[[Category:Game Files]]

SOLDIER.DAT

2009-12-18T18:32:05Z

Hatfarm: /* Odds and Ends */

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

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

===Basic Information===
0-1 / 00-01 (0-5, FFFF): Integer set to [[Rank]] or FFFF if soldier is dead (or slot not yet used). Values are actually a pointer within [[ENGLISH.DAT]]. Ranks are:
0 Rookie
1 Squaddie
2 Sergeant (SGT)
3 Captain (CPT)
4 Colonel (COL)
5 Commander (CDR)
6 Select Squad for
7 SPACE AVAILABLE>
2-3 / 02-03 (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.

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

6-7 / 06-07 (various, FFFF): Craft soldier was assigned to before being wounded and spending time in the infirmary.

8-9 / 08-09 (0+): Missions. Signed integer. (The soldier display shows a negative value if highest/16th bit is set!)

10-11 / 0A-0B (0+): Kills. Signed integer.

12-13 / 0C-0D (0+): Wound recovery days. Signed integer.

14-15 / 0E-0F (20+): Soldier value a.k.a. victory point loss if dies on a mission. Signed integer. Is equal to 20 + Missions + Rank Bonus, as follows:
0 Recruit
+1 Squaddie
+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 when promoted (e.g. COL to CDR +4). In other words, although it uses the equation shown above, it's not actually computed from Missions and Rank, per se.

16-40 / 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. The end of the current name is a null byte; garbage can be present after that (ends of longer previous names, etc.).

41 / 29 (various): Always 0 except for existing soldiers being transferred, in which case it equals the [[LOC.DAT]] value for destination base. New recruits 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, via [[TRANSFER.DAT]].

===Initial Recruit Stats===

''Denoted in the geoscape soldier display by the two-tone stat bars (not viewable in combat)

<div style="float:right;padding-left:10px;">
<table {{StdCenterTable}} class="sortable">
<tr {{StdDescTable_Heading}}><th>[52] Value</th><th width="100">Bravery</th></tr>
<tr><td>0</td><td>110</td></tr>
<tr><td>1</td><td>100</td></tr>
<tr><td>2</td><td>90</td></tr>
<tr><td>3</td><td>80</td></tr>
<tr><td>4</td><td>70</td></tr>
<tr><td>5</td><td>60</td></tr>
<tr><td>6</td><td>50</td></tr>
<tr><td>7</td><td>40</td></tr>
<tr><td>8</td><td>30</td></tr>
<tr><td>9</td><td>20</td></tr>
<tr><td>10</td><td>10</td></tr>
<tr><td>11</td><td>0</td></tr></table>
</div>

42 / 2A (50-60): Initial [[Time Units]]

43 / 2B (25-40): Initial [[Health]]

44 / 2C (40-70): Initial [[Energy|Energy a.k.a. Stamina]]

45 / 2D (30-60): Initial [[Reactions]]

46 / 2E (20-40): Initial [[Strength]]

47 / 2F (40-70): Initial [[Firing Accuracy]]

48 / 30 (50-80): Initial [[Throwing Accuracy]]

49 / 31 (20-40): Initial [[Melee Accuracy]] a.k.a. Close Combat Accuracy

50 / 32 (0-100): [[Psionic Strength]]. Never changes.

51 / 33 (0-105+): Current [[Psionic Skill]]. 0 = Not yet trained / Psi stats not visible. See Note 1.

''Unlike other stats, Psi Skill always starts at 0. So it stores its current skill in what would've otherwise been its initial skill byte, if you will. Also see Bytes 64 and 65.

52 / 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 (see table at right). Initial Bravery can be 10-60, and it only uses increments of 10.

===Stat Improvement===
''Add to initial values to get current total.''

53 / 35 (0-31): Time Unit Improvement. (Max total TUs possible (initial+improvement) is 81. See Note 1.)

54 / 36 (0-36): Health Improvement. (Max total 61)

55 / 37 (0-61): Stamina Improvement. (Max total 101)

56 / 38 (0-75): Reaction Improvement. (Max total 105)

57 / 39 (0-51): Strength Improvement. (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.

58 / 3A (0-85): Firing Accuracy Improvement. (Max total 125)

59 / 3B (0-75): Throwing Accuracy Improvement Improvement. (Max total 125)

60 / 3C (0-105): Melee/Close Combat Accuracy Improvement. (Max total 125)

61 / 3D (0-9): Bravery Improvement (multiply by 10). (Max total 9; 100 Bravery)

===Odds and Ends===

62 / 3E (0-3): Armor. 0=None, 1=Personal Armor, 2=Power Suit, 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. However, when you start a new mission, the CE version crashes because it cannot find a skin for that value.

63 / 3F (0-24): Most-recent month's Psi Lab training increase. Largest values for newly trained (16-24). For Psi Lab point-award functionality, see [[Psionic Skill]].

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

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

66 / 42 (0,1): 0=Male, 1=Female. Editing values greater than 1 does not change the appearance in the soldier equip screens. However, the soldier image will always take the outward appearance of a female during a mission.

67 / 43 (0-3): Appearance (for loadout, no armor): 0=blonde, 1=brown hair, 2=Oriental, 3=African. Refers to the [[UFOGRAPH]]/MAN.spk [[Inventory_Backgrounds|images]]. Because there are only 4 nationalities, editing values greater than 3 will result in an error code: <code>cannot open file ufograph/man_XYZ.spk</code> where X is 0 or 1 (Light armored or personnel armored), Y is "M" or "F" (Male or Female) and Z is the nationality value listed in this field.

== Notes ==
#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'. [[Experience#Primary_Stats|Primary skills]] can have up to cap+5, and secondary skills can have up to 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. For more info, see [[Experience#Regarding_Caps|Regarding Caps]].
#When you enter combat, the [[UNITREF.DAT|Unitref]] stat values (offset 23-28 etc.) are 'read only' (for that combat only). If you edit Unitref stat values and end the combat, the changed stats are not reflected in the soldier's stats in the geoscape. Instead, the stat values from Soldier.Dat are used. Makes sense, since the current stat level doesn't change during combat, per se - you only get stat changes (increases, if any) when the mission ends. "Kills" is the only value known to carry directly from geoscape to combat and back (due to its "unpredictability").
#If you hack your stats, the game doesn't care if you put larger values than a recruit can get in the "initial" bytes. Or if you totally zero out a skill, for that matter. Not in the geoscape, anyway... Could lead to a very bad day on the battlefield, though.
#If your total skill value (initial + increase) is high enough, your skill bar will wrap around the stat display screen. (See how it goes to 150 in combat, 170 in geoscape?)
#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 ==
*For information on individual skills see [[Soldiers]]
*For information on increasing skills see [[Experience]]
*[[UNITREF.DAT]] tracks items on the battlefield, including soldiers and their stats, and experience counters. Also see the notes at bottom of Unitref.
*For more info on starting soldier stats, see [[Raw_recruit_statistical_likelihood|Recruit Statistics]]
*Notes on [[HackerTools|hex editing]]
* A Hex Workshop Structure Library for editing this file can be found [[SOLDIER_DAT_HSL|here]]

Return to [[Saved_Game_Files|Saved Game Files]]

== See Also ==

[[SOLDIER.DAT (TFTD)]]

[[Category:Game Files]]

PALETTES.DAT

2009-10-27T16:56:43Z

Hatfarm: /* Introduction */

=Introduction=

Back in the days of low video memory, storing each pixel as a multi-byte color value (such as in today's "High Color" and "True Color" modes common under MS Windows) was not practical. Instead, a common method for was to create a palette of 256 different colors (usually of 3 bytes each), and then use single byte values to index into that. The ability of a video card to use such a palette was known as "VGA compatibility". 
 
This dramatically decreased the memory requirements of a given image, though it lowered the amount of colors that could be used in any single moment. 
 
There are a total of five "complete" palettes for UFO and three for TFTD, each for a different situation. Each is made up of the standard 256 colors stored as three byte RGB records (A value for Red, a value for Green, and a value for Blue). This makes a total of 768 bytes per palette. 
 
Each RGB value has a maximum intensity of 63/x3F (making a total of 262,144 shades available, which seems to be standard for VGA), as opposed to 255/xFF (which would have provided 16,777,216). If you want to use the 64 color values in a 256 color world, just multiply each value by 4 and you'll achieve the correct color. Each palette has a six byte 'buffer' following it. While their meanings are unknown, they are:

UFO: TFTD:
Pal1: B7 13 FF 76 FE 50 Pal1: 66 83 7D F8 01 75
Pal2: A1 E8 13 0B 06 E6 Pal2: 45 F0 01 C0 01 D0
Pal3: 01 00 8B 46 FA 0B Pal3: B8 13 00 00 00 E8
Pal4: FF 76 10 FF 76 0E
Pal5: C8 1E 00 00 1E B8

Five palettes of 768 bytes each, plus five buffers of 6 bytes each,
makes 3,870 bytes in Palettes.Dat (or 2,322 for TFTD's three palettes).

=Usage=

Color 0 is not used in the game, it instead represents "transparency" (ie. Pixels which should not be drawn to the screen). 
 
The UFOpedia uses the first, second, fourth or fifth palettes, depending on the requirements of the entry being displayed. 
 
The final 16 colors of each palette are reserved. These are replaced in-game by the colors from the appropriate [[PALETTES.DAT#BACKPALS.DAT|BACKPALS.DAT]] palette, and used to draw the backgrounds of the bordered windows; where there are no background images they are unused. 
 
[[Image:5_BattleScapePal2.Png|right|frame]]
The exception to this is the Tactical palette, where the final 16 colors are replaced by a greyscale set stored in neither of the palette files (pictured right; presumably they are hard coded into the [[TACTICAL.EXE|executable]] instead). These colors can be used by objects or terrain, etc, but are not loaded for the UFOpedia display. 
 
Because of this there are two different sets of item images, each bearing the title "[[BIGOBS.PCK|BigObs]]": Those used in the UFOpedia (a collection of 57 PCK files in the [[UFOGRAPH]] folder), and those used in Tactical mode (a single PCK archive in the [[UNITS]] folder). 
 
TFTD has less palettes stored in this file then UFO and instead re-writes them as required on the fly (or uses hard coded versions from the executable).

=Color Indexes=

==UFO==

[[image:1_GeoScapePal.Png|center|frame|1. GeoScape World View.]]
[[image:2_UnknownPal.Png|center|frame|2. Base Palette.]]
[[image:3_GraphPal.Png|center|frame|3. Graph Views.]]
[[image:4_ResearchPal.Png|center|frame|4. Research Displays.]]
[[image:5_BattleScapePal.Png|center|frame|5. Tactical Palette.]]
==TFTD==

[[image:TFTD_Pal1.png|center|frame|1. GeoScape World View.]]
[[image:TFTD_Pal2.png|center|frame|2. Unknown.]]
[[image:TFTD_Pal3.png|center|frame|3. Graph Views.]]

=TFTD Tactical Palettes=

Like UFO, TFTD has a basic set of sprites for use in the battlescape which it shades according to the time of day. Unlike the original however TFTD has underwater missions of three different depths, as well as land missions - For each depth level a different palette is used (though none of these are stored in PALETTES.DAT). 
 
[[image:TFTD_Tact1.png|center|frame|1. Land & Inventory Displays.]]
[[image:TFTD_Tact2.png|center|frame|2. Shallow Water.]]
[[image:TFTD_Tact3.png|center|frame|3. Medium Depths.]]
[[image:TFTD_Tact4.png|center|frame|4. Deep Sea.]]

=BACKPALS.DAT=

This file contains palettes used to draw [[BACK01.SCR-BACK17.SCR|background images]]. These small 16 color palettes replace the final 16 entries of the primary palettes in game. They are used to display the background images of bordered windows as well as the background of the load game screens, and the terror site announcement window. They are stored using the same 3 byte RGB format as the primary palettes. This file contains eight, 16 color palettes. 128 colors in total. 384 bytes in all.

[[image:BackPals.Png|center|frame|Palettes used for background images.]]
[[image:TFTD_BackPals.Png|center|frame|Version used by TFTD.]]

[[Category:Game Files]]

BASE.DAT

2009-10-11T05:34:02Z

Hatfarm: /* UFO Structure */

__TOC__
==UFO Structure==
''Ripped from [http://www.stonepool.com/xcom/hacking/index.html Hatfarm / Chris Voss's] great pages

'''BASE.DAT:''' Each entry is 292 Bytes long

'''00-0E:''' Base Name, pretty obvious

'''0F:''' Presumably the Null character if the Base Name uses all 15 characters

'''10:''' Base's short range detection capability.

'''12:''' Base's long range detection capability.

'''14:''' Base's hyperwave detection capability.

'''11, 13, 15:''' These are probably the high bytes for the Short, Long, and Hyper-wave detections respectively. Should always be 0 as a value of 100 (hex: 64 00) is perfect detection.

Logical values for the detection capabilities:

''10 short, 0 long:'' This base has small radar(s) only.

''20 short, 20 long:'' This base has large radar(s) only.

''30 short, 20 long:'' This base has small and large radar(s).

''100 hyperwave:'' This base has a hyperwave decoder(s).

The radar values can be set to 100 for perfect short range detection (presumably -- it definitely makes UFOs appear more often), but these reset to the correct values any time you complete a build in that base.

{| width = "35%" style = "border: 1px solid; border-collapse:collapse; text-align:center"
|+ Table 1: Radar Ability Combinations
|- style = "font-size:larger; font-weight: bold; border-bottom: 1px black solid; background: gray; color:white;"
| Radar Module / Scan Type || Short || Long || Hyperwave
|- style = ""
| Small Radar || 10 || 0 || 0
|-
| Large Radar || 20 || 20 || 0
|-
| Hyperwave || 0 || 0 || 100
|- colspan = "4" style = "border-top: 1px dotted; font-wight: bold;"
|colspan=4| '''Radar Combinations'''
|- style = "background: #EEE;"
| Sm + Sm || 10 || 0 || 0
|-
| Sm + Lg || 30 || 20 || 0
|-style = "background: #EEE;"
| Sm + Hyp || 10 || 0 || 100
|-
| Lg + Lg || 20 || 20 || 0
|-style = "background: #EEE;"
| Lg + Hyp || 20 || 20 || 100
|-
| Hyp + Hyp || 0 || 0 || 100
|-style = "background: #EEE;"
| Sm + Lg + Hyp || 30 || 20 || 100
|}

'''16-39:''' The next offsets are arranged so they're easier to understand. They are for facilities in the base:

{| {{stdTable}} border="1" cellpadding="5" style="border: 0px solid; text-align: center" width="210"
|-
| 16 || 17 || 18 || 19 || 1A || 1B
|-
| 1C || 1D || 1E || 1F || 20 || 21
|-
| 22 || 23 || 24 || 25 || 26 || 27
|-
| 28 || 29 || 2A || 2B || 2C || 2D
|-
| 2E || 2F || 30 || 31 || 32 || 33
|-
| 34 || 35 || 36 || 37 || 38 || 39
|}

The possible values are as follows:
00 - Access Lift
01 - Living Quarters
02 - Laboratory
03 - Workshop
04 - Small Radar System
05 - Large Radar System
06 - Missile Defense
07 - General Stores
08 - Alien Containment
09 - Laser Defense
0A - Plasma Defense
0B - Fusion Ball Defense
0C - Grav Shield
0D - Mind Shield
0E - Psionic Laboratory
0F - Hyper-wave Decoder
10 - Hangar (Top Left)
11 - Hangar (Top Right)
12 - Hangar (Bottom Left)
13 - Hangar (Bottom Right)
FF - Empty

'''3A-5D:''' The next offsets represent the days until a facility is completed. They're set up the same way:

{| {{stdTable}} border="1" cellpadding="5" style="border: 0px solid; text-align: center" width="210"
|-
| 3A || 3B || 3C || 3D || 3E || 3F
|-
| 40 || 41 || 42 || 43 || 44 || 45
|-
| 46 || 47 || 48 || 49 || 4A || 4B
|-
| 4C || 4D || 4E || 4F || 50 || 51
|-
| 52 || 53 || 54 || 55 || 56 || 57
|-
| 58 || 59 || 5A || 5B || 5C || 5D
|}

Possible values are 00 to FF. Empty spaces must have a FF value in their corresponding offset.

The following are the rest of the offsets I know. There are holes in the numbering but I have no idea what they are. With the exception of '''scientists and technicians''', which are '''one byte each''', all values are 2-byte signed little-endian values (-32,768 to +32,767). Example: 05 00 should be read as 0005; FE FF should be read as FFFE (-2).

It should be noted that despite the range of values a two-byte signed field gives you, due to a [[Known_Bugs#Storage_Limit|known issue]], you cannot have more than 9,999 units of a given item in storage at any given base, regardless of what item it is.

Here's the info for bytes '''5E-11E'''. The Record Number (Rec#) is used for e.g. [[PRODUCT.DAT]]:

Hex Dec Rec# Item
---- --- ---- ----
'''005E''' 94 - Engineer
'''005F''' 95 - Scientist
'''0060''' 96 0 Stingray Launcher
'''0062''' 98 1 Avalanche Launcher
'''0064''' 100 2 Cannon
'''0066''' 102 3 Fusion Ball Launcher
'''0068''' 104 4 Laser Cannon
'''006A''' 106 5 Plasma Beam
'''006C''' 108 6 Stingray Missile
'''006E''' 110 7 Avalanche Missile
'''0070''' 112 8 Cannon Rounds
'''0072''' 114 9 Fusion Balls
'''0074''' 116 10 Tank/Cannon
'''0076''' 118 11 Tank/Rocket Launcher
'''0078''' 120 12 Tank/Laser Cannon
'''007A''' 122 13 Hovertank/Plasma
'''007C''' 124 14 Hovertank/Launcher
'''007E''' 126 15 Pistol
'''0080''' 128 16 Pistol Clip
'''0082''' 130 17 Rifle
'''0084''' 132 18 Rifle Clip
'''0086''' 134 19 Heavy Cannon
'''0088''' 136 20 HC-AP Ammo
'''008A''' 138 21 HC-HE Ammo
'''008C''' 140 22 HC-IN Ammo
'''008E''' 142 23 Auto Cannon
'''0090''' 144 24 AC-AP Ammo
'''0092''' 146 25 AC-HE Ammo
'''0094''' 148 26 AC-IN Ammo
'''0096''' 150 27 Rocket Launcher
'''0098''' 152 28 Small Rocket
'''009A''' 154 29 Large Rocket
'''009C''' 156 30 Incendiary Rocket
'''009E''' 158 31 Laser Pistol
'''00A0''' 160 32 Laser Rifle
'''00A2''' 162 33 Heavy Laser
'''00A4''' 164 34 Grenade
'''00A6''' 166 35 Smoke Grenade
'''00A8''' 168 36 Proximity Grenade
'''00AA''' 170 37 High Explosive
'''00AC''' 172 38 Motion Scanner
'''00AE''' 174 39 Medi-Kit
'''00B0''' 176 40 Psi-Amp
'''00B2''' 178 41 Stun Rod
'''00B4''' 180 42 Electro Flare
'''00B6''' 182 43 empty
'''00B8''' 184 44 empty
'''00BA''' 186 45 empty
'''00BC''' 188 46 CORPSE
'''00BE''' 190 47 CORPSE & ARMOUR
'''00C0''' 192 48 CORPSE & POWER SUIT
'''00C2''' 194 49 Heavy Plasma
'''00C4''' 196 50 Heavy Plasma Clip
'''00C6''' 198 51 Plasma Rifle
'''00C8''' 200 52 Plasma Rifle Clip
'''00CA''' 202 53 Plasma Pistol
'''00CC''' 204 54 Plasma Pistol Clip
'''00CE''' 206 55 Blaster Launcher
'''00D0''' 208 56 Blaster Bomb
'''00D2''' 210 57 Small Launcher
'''00D4''' 212 58 Stun Bomb
'''00D6''' 214 59 Alien Grenade
'''00D8''' 216 60 Elerium-115
'''00DA''' 218 61 Mind Probe
'''00DC''' 220 62 >>UNDEFINED <<
'''00DE''' 222 63 >> empty <<
'''00E0''' 224 64 >> empty <<
'''00E2''' 226 65 Sectoid Corpse
'''00E4''' 228 66 Snakeman Corpse
'''00E6''' 230 67 Ethereal Corpse
'''00E8''' 232 68 Muton Corpse
'''00EA''' 234 69 Floater Corpse
'''00EC''' 236 70 Celatid Corpse
'''00EE''' 238 71 Silacoid Corpse
'''00F0''' 240 72 Chryssalid Corpse
'''00F2''' 242 73 Reaper Corpse
'''00F4''' 244 74 Sectopod Corpse
'''00F6''' 246 75 Cyberdisc Corpse
'''00F8''' 248 76 Hovertank Corpse
'''00FA''' 250 77 Tank Corpse
'''00FC''' 252 78 Male Civilian Corpse
'''00FE''' 254 79 Female Civilian Corpse
'''0100''' 256 80 UFO Power Source
'''0102''' 258 81 UFO Navigation
'''0104''' 260 82 UFO Construction
'''0106''' 262 83 Alien Food
'''0108''' 264 84 Alien Reproduction
'''010A''' 266 85 Alien Entertainment
'''010C''' 268 86 Alien Surgery
'''010E''' 270 87 Examination Room
'''0110''' 272 88 Alien Alloys
'''0112''' 274 89 Alien Habitat
'''0114''' 276 90 Personal Armour
'''0116''' 278 91 Power Suit
'''0118''' 280 92 Flying Suit
'''011A''' 282 93 HWP Cannon Shell
'''011C''' 284 94 HWP Rockets
'''011E''' 286 95 HWP Fusion Bomb

'''0120-0123:''' I have no idea, any help would be appreciated.

'''0120:''' Mark the base as active. Bases which are dismantled or which have not been built have a value of 1. Active bases have a value of 0. If a base is dismantled, the only change to the record is this value. A new base will overwrite the first slot with a value of 1. It is possible to restore a dismantled base (Access lift removed) by setting this value to 0. The game will 'restore' the base to the configuration just before the access lift was removed, including inventory. --[[User:SeulDragon|SeulDragon]] 12:24, 11 July 2008 (PDT)

==See Also==
* [[ASTORE.DAT]] - Information on captured aliens at bases
* [[BPROD.DAT]] - Information on what bases are producing
* [[CRAFT.DAT]] - Information on crafts (both X-Com and Alien)
* [[FACIL.DAT]] - Information on the facilities you can build in bases
* [[LOC.DAT]] - Location Data for bases and crafts
* [[PROJECT.DAT]] - Information on current research
* [[SOLDIER.DAT]] - Information on soldiers at bases
* [[TRANSFER.DAT]] - Information on item/personnel being transferred to/from bases
* [[BASE.DAT (TFTD)]] - Terror From The Deep's base file
* [[Saved Game Files]]
[[Category:Game Files]]