UFOpaedia - User contributions [en]

Capturing Live Aliens (Apocalypse)

2025-12-18T14:55:29Z

Magic9mushroom: /* General capture procedure */ further clarification

Unlike in previous and subsequent X-Com games, the primary goal of X-COM: Apocalypse - destroying the alien city - can be accomplished without capturing any live or dead aliens. However, capturing aliens is essential to the secondary goal of discovering [[The Real Alien Threat|what the aliens are planning]], and also unlocks the immensely-powerful [[Toxigun]], so it can be thought of as a sidequest.

==The Goals==

There are several distinct stages of this research path, which are worth keeping in mind when deciding which aliens to bother capturing. Each stage's information and toxin technology requires that of the previous stage.

*[[The Alien Genetic Structure (Apocalypse)|The Alien Genetic Structure]] and [[Biological Warfare (Apocalypse)|Biological Warfare]], the latter of which provides the Toxigun itself and Toxin Type A, merely require the autopsy of any one immature alien (Multiworm Egg, Multiworm or Hyperworm).
*[[The Alien Life Cycle (Apocalypse)|The Alien Life Cycle]] and [[Toxin B (Apocalypse)|Toxin Type B]] require the live examination and autopsy of the Multiworm, Hyperworm and Chrysalis - as you'll see below, the Multiworm is the only tricky one here.
*[[The Real Alien Threat]] and [[Toxin C (Apocalypse)|Toxin Type C]] require the live examination and autopsy of the Multiworm Egg, Brainsucker, Anthropod, Spitter, Popper, Skeletoid, Micronoid Aggregate, Megaspawn and Psimorph - i.e., every alien except the Queenspawn and Overspawn.
*[[Alien Gas (Apocalypse)|Alien Gas]] requires the live examination and autopsy of the Queenspawn.

(Additionally, you will need to research the [[Bio-Transport Module (Apocalypse)|Bio-Transport Module]] and [[Advanced Biochemistry Lab (Apocalypse)|Advanced Biochemistry Lab]]; both should be considered high-priority if you wish to pursue this path, although in the former case there's nothing else to research yet anyway.)

The important thing to note here is the enormous gulf between Toxin B and C; capturing a Multiworm is a high priority, as it is the only significant capture requirement for Toxin B, but unless you're willing to bother capturing ''all'' the aliens needed for Toxin C there's little reason to bother capturing ''any'' of them (or to capture the Queenspawn). Toxin B is already exceptionally good, so decide early on whether you want to get Toxin C and play accordingly.

Note that you don't need to separately capture an alien alive and dead like in UFO or TFTD; examining a live alien will give you the corresponding corpse.

==Methods of capture==

There are three methods of stunning aliens in order to capture them alive: the [[Megapol Stun Grapple]], the [[Megapol Stun Grenade]] and the psionic "stun" attack with a [[Mind Bender]]. Each has advantages and disadvantages.

*The Stun Grapple requires little micromanagement, is cheap and has infinite ammunition, but is short-ranged and cannot penetrate [[Personal Disruptor Shield]]s.
*The Stun Grenade ignores shields and has medium range, but the cloud of stun gas dissipates quickly and also affects X-COM personnel; the grenades are also consumable and must be manually transferred to hand as needed. It also has no effect on Micronoid Aggregates.
*Psionic stunning can be done anywhere within line of sight, ignores shields, and only uses (regenerating) Psi-energy, but you'll need to train [[Hybrids (Apocalypse)|hybrids]] to do it and it only has a high success rate on Anthropods and Skeletoids.

==General capture procedure==

The ideal way to capture aliens goes roughly like this:

1) Set up a situation where you can afford to concentrate on the capture. This means eliminating or drawing off other aliens, as well as bringing the proper equipment and/or soldiers to make the target itself less dangerous (you don't generally want to be risking soldiers for a capture).

2) Perform the capture. For most aliens, this simply means sending a few soldiers in with Stun Grapples or Stun Grenades while having the rest of your squad hold their fire. However, the maximum stun level is 255, and some aliens (Multiworms, Megaspawn, Psimorphs and the Queenspawn) have more health than this; they can receive stun normally, but you will also need to reduce their health below 256 (with lethal weapons, ideally weak ones to reduce the risk of critical wounds, and ideally ''slowly'' while maintaining a high stun level, as soldiers take a certain amount of time to stop firing at a stunned alien) in order to make them fall unconscious.

3) Pin the alien to the ground by having a soldier stand on top of it. This prevents the alien from "waking up" as its stun level decreases over time. It's generally best to put the soldier used for this in a squad by himself, so that you don't accidentally move him.

4) Complete the mission. Try to do this quickly, and without explosives going off near the unconscious alien (as unconscious aliens may be bleeding from critical wounds, and will still take damage from explosives).

==Specific alien notes==

===Zero-effort captures===

The [[Multiworm Egg]], [[Hyperworm]] and [[Chrysalis]] do not need to be stunned in order to research them. The Multiworm Egg and Chrysalis are recovered alive automatically if left alone, and researching a live Multiworm puts four Hyperworms into your Alien Containment.

===Low-effort captures===

[[Brainsucker]]s, [[Spitter]]s and early-game [[Anthropod]]s pose very little threat at range, so capturing these is a simple matter of walking up to them with a Stun Grapple (or, in the case of Brainsuckers, having a Stun Grapple in hand when they charge you).

You can also put a live Brainsucker into your Alien Containment by recovering and researching an unhatched [[Brainsucker Pod]], although this takes extra research time.

===[[Multiworm]]===

The problem with Multiworms is simply their high health and their high rate of fire. The safest way to capture these is to use Stun Grenades from long range (exploiting the short range of Multiworms' spit and their inability to escape the gas cloud) while chipping away with the [[Lawpistol]], [[M4000]] and [[Megapol Laser Sniper Gun|Laser Sniper Gun]].

Alternatively, charging in to point-blank range with a full squad of soldiers in [[Megapol Armor]] dual-wielding the above weapons with Stun Grapples will almost always bring down a worm before it can kill any of them (though they'll usually be wounded).

===[[Popper]]===

Poppers are easy enough to stun, assuming you see them coming (in real-time mode) or get the drop on them (in turn-based mode). What's worth noting is that Poppers take critical wounds very easily and will explode if they bleed to death. As such, you should ensure a Popper is '''undamaged''' if you plan to have an Agent stand on it.

===[[Skeletoid]]===

While Skeletoids are very similar to Anthropods in most respects, they only show up in Week 3. Depending on X-COM's [[Alien Tech Levels (Apocalypse)|performance]], this means that they may already be equipped with [[Devastator Cannon]]s. A Skeletoid, or even Anthropod, with a Devastator Cannon is a serious threat at long range, and attempting a live capture will frequently result in soldier deaths. The humanoid aliens will also eventually gain access to [[Personal Disruptor Shield]]s, which negate Stun Grapples.

Nabbing a well-armed Skeletoid safely is best done with psi from behind cover (line of sight is only required for the initial lock), or opportunistically (with Stun Grapples if encountered at close range, or with Stun Grenades if many Skeletoids are encountered in an enclosed space). If you find a lone Skeletoid with a Brainsucker Launcher or Disruptor Gun, of course, such caution is unnecessary.

===Psionic aliens===

The [[Psimorph]] and [[Micronoid Aggregate]] are very similar in that their only method of attack is psionic powers. Psionic powers are very effective against your [[Humans (Apocalypse)|human]] soldiers, but ineffective against [[Androids (Apocalypse)|androids]] or well-trained [[Hybrids (Apocalypse)|hybrids]]. As such, the trick here is to get them on their own (without supporting aliens) and send in a squad of ''only'' hybrids or androids - this renders them toothless and assures an easy capture (Psimorphs will need to be damaged, but with this tactic you'll have plenty of time to do it carefully).

Note that Stun Grenades are not very useful against either of these; Micronoids are immune, while Psimorphs can fly and have a great deal of health.

===[[Megaspawn]]===

Megaspawn are a notoriously-difficult capture due to their heavy armament - in particular, their infinite supply of long-range homing missiles. The ideal way to capture a Megaspawn is to wait until you have [[X-COM Disruptor Armor]], which largely obviates their missiles as a threat, and/or [[Personal Cloaking Field]]s, which prevent them from targetting your soldiers at long range (unless another alien is spotting for them).

If you aren't willing to wait that long, the best bet is to use several soldiers, each with a Stun Grapple and two shields and one additionally holding a Devastator Cannon, and try to take a Megaspawn by surprise in the cramped rooms of a UFO. Expect lost shields and possibly soldiers.

===[[Queenspawn]]===

The Queenspawn capture is a bit complicated due to her tentacle whip, but quite easy with Cloaking Fields, 20 or so Stun Grenades, and patience. Given the very fixed nature of the mission (she's always in exactly the same place and can't move), this section will be quite detailed.

1) Kill all the mobile aliens on the map, and blow up all the reinforcement pads. This deprives the Queenspawn of spotters, making her harmless to cloaked soldiers at medium to long range.

2) Throw two Vortex Mines into the raised dais holding the Queenspawn, one on each side of her. These will inflict some damage and, more importantly, destroy the Multiworm Eggs around her (allowing the mission to end as soon as the Queenspawn is stunned).

3) Start throwing Stun Grenades at the Queenspawn. Wait for the gas cloud to nearly dissipate before throwing the next grenade, to get the maximum effect from each grenade.

4) After five grenades or so, if she is not stunned, have a soldier start shooting her with a Devastator Cannon on aimed shot (to inflict damage slowly; a Toxigun will often be too fast and kill her in the couple of seconds before the mission ends). Keep throwing Stun Grenades until she drops.

[[Category: Apocalypse]]

Capturing Live Aliens (Apocalypse)

2025-12-18T14:53:20Z

Magic9mushroom: Undo revision 124008 by Kuchikirukia (talk) avoid restatement; rephrased to be clearer

Unlike in previous and subsequent X-Com games, the primary goal of X-COM: Apocalypse - destroying the alien city - can be accomplished without capturing any live or dead aliens. However, capturing aliens is essential to the secondary goal of discovering [[The Real Alien Threat|what the aliens are planning]], and also unlocks the immensely-powerful [[Toxigun]], so it can be thought of as a sidequest.

==The Goals==

There are several distinct stages of this research path, which are worth keeping in mind when deciding which aliens to bother capturing. Each stage's information and toxin technology requires that of the previous stage.

*[[The Alien Genetic Structure (Apocalypse)|The Alien Genetic Structure]] and [[Biological Warfare (Apocalypse)|Biological Warfare]], the latter of which provides the Toxigun itself and Toxin Type A, merely require the autopsy of any one immature alien (Multiworm Egg, Multiworm or Hyperworm).
*[[The Alien Life Cycle (Apocalypse)|The Alien Life Cycle]] and [[Toxin B (Apocalypse)|Toxin Type B]] require the live examination and autopsy of the Multiworm, Hyperworm and Chrysalis - as you'll see below, the Multiworm is the only tricky one here.
*[[The Real Alien Threat]] and [[Toxin C (Apocalypse)|Toxin Type C]] require the live examination and autopsy of the Multiworm Egg, Brainsucker, Anthropod, Spitter, Popper, Skeletoid, Micronoid Aggregate, Megaspawn and Psimorph - i.e., every alien except the Queenspawn and Overspawn.
*[[Alien Gas (Apocalypse)|Alien Gas]] requires the live examination and autopsy of the Queenspawn.

(Additionally, you will need to research the [[Bio-Transport Module (Apocalypse)|Bio-Transport Module]] and [[Advanced Biochemistry Lab (Apocalypse)|Advanced Biochemistry Lab]]; both should be considered high-priority if you wish to pursue this path, although in the former case there's nothing else to research yet anyway.)

The important thing to note here is the enormous gulf between Toxin B and C; capturing a Multiworm is a high priority, as it is the only significant capture requirement for Toxin B, but unless you're willing to bother capturing ''all'' the aliens needed for Toxin C there's little reason to bother capturing ''any'' of them (or to capture the Queenspawn). Toxin B is already exceptionally good, so decide early on whether you want to get Toxin C and play accordingly.

Note that you don't need to separately capture an alien alive and dead like in UFO or TFTD; examining a live alien will give you the corresponding corpse.

==Methods of capture==

There are three methods of stunning aliens in order to capture them alive: the [[Megapol Stun Grapple]], the [[Megapol Stun Grenade]] and the psionic "stun" attack with a [[Mind Bender]]. Each has advantages and disadvantages.

*The Stun Grapple requires little micromanagement, is cheap and has infinite ammunition, but is short-ranged and cannot penetrate [[Personal Disruptor Shield]]s.
*The Stun Grenade ignores shields and has medium range, but the cloud of stun gas dissipates quickly and also affects X-COM personnel; the grenades are also consumable and must be manually transferred to hand as needed. It also has no effect on Micronoid Aggregates.
*Psionic stunning can be done anywhere within line of sight, ignores shields, and only uses (regenerating) Psi-energy, but you'll need to train [[Hybrids (Apocalypse)|hybrids]] to do it and it only has a high success rate on Anthropods and Skeletoids.

==General capture procedure==

The ideal way to capture aliens goes roughly like this:

1) Set up a situation where you can afford to concentrate on the capture. This means eliminating or drawing off other aliens, as well as bringing the proper equipment and/or soldiers to make the target itself less dangerous (you don't generally want to be risking soldiers for a capture).

2) Perform the capture. For most aliens, this simply means sending a few soldiers in with Stun Grapples or Stun Grenades while having the rest of your squad hold their fire. However, the maximum stun level is 255, and some aliens (Multiworms, Megaspawn, Psimorphs and the Queenspawn) have more health than this; they can receive stun normally, but you will also need to reduce their health below 256 (with lethal weapons, ideally weak ones to reduce the risk of critical wounds, and ideally ''slowly'' as soldiers take a certain amount of time to stop firing at a stunned alien) in order to make them fall unconscious.

3) Pin the alien to the ground by having a soldier stand on top of it. This prevents the alien from "waking up" as its stun level decreases over time. It's generally best to put the soldier used for this in a squad by himself, so that you don't accidentally move him.

4) Complete the mission. Try to do this quickly, and without explosives going off near the unconscious alien (as unconscious aliens may be bleeding from critical wounds, and will still take damage from explosives).

==Specific alien notes==

===Zero-effort captures===

The [[Multiworm Egg]], [[Hyperworm]] and [[Chrysalis]] do not need to be stunned in order to research them. The Multiworm Egg and Chrysalis are recovered alive automatically if left alone, and researching a live Multiworm puts four Hyperworms into your Alien Containment.

===Low-effort captures===

[[Brainsucker]]s, [[Spitter]]s and early-game [[Anthropod]]s pose very little threat at range, so capturing these is a simple matter of walking up to them with a Stun Grapple (or, in the case of Brainsuckers, having a Stun Grapple in hand when they charge you).

You can also put a live Brainsucker into your Alien Containment by recovering and researching an unhatched [[Brainsucker Pod]], although this takes extra research time.

===[[Multiworm]]===

The problem with Multiworms is simply their high health and their high rate of fire. The safest way to capture these is to use Stun Grenades from long range (exploiting the short range of Multiworms' spit and their inability to escape the gas cloud) while chipping away with the [[Lawpistol]], [[M4000]] and [[Megapol Laser Sniper Gun|Laser Sniper Gun]].

Alternatively, charging in to point-blank range with a full squad of soldiers in [[Megapol Armor]] dual-wielding the above weapons with Stun Grapples will almost always bring down a worm before it can kill any of them (though they'll usually be wounded).

===[[Popper]]===

Poppers are easy enough to stun, assuming you see them coming (in real-time mode) or get the drop on them (in turn-based mode). What's worth noting is that Poppers take critical wounds very easily and will explode if they bleed to death. As such, you should ensure a Popper is '''undamaged''' if you plan to have an Agent stand on it.

===[[Skeletoid]]===

While Skeletoids are very similar to Anthropods in most respects, they only show up in Week 3. Depending on X-COM's [[Alien Tech Levels (Apocalypse)|performance]], this means that they may already be equipped with [[Devastator Cannon]]s. A Skeletoid, or even Anthropod, with a Devastator Cannon is a serious threat at long range, and attempting a live capture will frequently result in soldier deaths. The humanoid aliens will also eventually gain access to [[Personal Disruptor Shield]]s, which negate Stun Grapples.

Nabbing a well-armed Skeletoid safely is best done with psi from behind cover (line of sight is only required for the initial lock), or opportunistically (with Stun Grapples if encountered at close range, or with Stun Grenades if many Skeletoids are encountered in an enclosed space). If you find a lone Skeletoid with a Brainsucker Launcher or Disruptor Gun, of course, such caution is unnecessary.

===Psionic aliens===

The [[Psimorph]] and [[Micronoid Aggregate]] are very similar in that their only method of attack is psionic powers. Psionic powers are very effective against your [[Humans (Apocalypse)|human]] soldiers, but ineffective against [[Androids (Apocalypse)|androids]] or well-trained [[Hybrids (Apocalypse)|hybrids]]. As such, the trick here is to get them on their own (without supporting aliens) and send in a squad of ''only'' hybrids or androids - this renders them toothless and assures an easy capture (Psimorphs will need to be damaged, but with this tactic you'll have plenty of time to do it carefully).

Note that Stun Grenades are not very useful against either of these; Micronoids are immune, while Psimorphs can fly and have a great deal of health.

===[[Megaspawn]]===

Megaspawn are a notoriously-difficult capture due to their heavy armament - in particular, their infinite supply of long-range homing missiles. The ideal way to capture a Megaspawn is to wait until you have [[X-COM Disruptor Armor]], which largely obviates their missiles as a threat, and/or [[Personal Cloaking Field]]s, which prevent them from targetting your soldiers at long range (unless another alien is spotting for them).

If you aren't willing to wait that long, the best bet is to use several soldiers, each with a Stun Grapple and two shields and one additionally holding a Devastator Cannon, and try to take a Megaspawn by surprise in the cramped rooms of a UFO. Expect lost shields and possibly soldiers.

===[[Queenspawn]]===

The Queenspawn capture is a bit complicated due to her tentacle whip, but quite easy with Cloaking Fields, 20 or so Stun Grenades, and patience. Given the very fixed nature of the mission (she's always in exactly the same place and can't move), this section will be quite detailed.

1) Kill all the mobile aliens on the map, and blow up all the reinforcement pads. This deprives the Queenspawn of spotters, making her harmless to cloaked soldiers at medium to long range.

2) Throw two Vortex Mines into the raised dais holding the Queenspawn, one on each side of her. These will inflict some damage and, more importantly, destroy the Multiworm Eggs around her (allowing the mission to end as soon as the Queenspawn is stunned).

3) Start throwing Stun Grenades at the Queenspawn. Wait for the gas cloud to nearly dissipate before throwing the next grenade, to get the maximum effect from each grenade.

4) After five grenades or so, if she is not stunned, have a soldier start shooting her with a Devastator Cannon on aimed shot (to inflict damage slowly; a Toxigun will often be too fast and kill her in the couple of seconds before the mission ends). Keep throwing Stun Grenades until she drops.

[[Category: Apocalypse]]

User talk:Boromonokli

2025-08-05T22:45:41Z

Magic9mushroom: response to note on my user talk

==Re: repairing Apocalypse section==
Sorry for not getting back to you sooner. I've been in a bad way the past couple of months.

I'm in favour of repairing the Apoc wiki to something resembling its pre-EsTeR state, yes, and certainly re-adding the loadouts to the alien ship pages. There are a couple of caveats on that, though:

1) He added a lot of new images and most (though not all) of those are actually useful. Try to rescue images from his revisions when possible. (This, along with his contributions before he decided to rewrite the Apocalypse section, are why I didn't just undo every edit he'd ever made.)

2) He moved a lot of information from one article to another; make sure information isn't lost from reverting some pages without reverting others (or information that he himself added). [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 22:45, 5 August 2025 (UTC)

Chrysalis (Apocalypse)

2025-05-09T08:50:28Z

Magic9mushroom: rescuing images, correcting spelling

{{Ref Open | title = Chrysalis}}[[Image:Chrysalis_(Alive).jpg|right]]
A Chrysalis is the most vulnerable stage of Alien development because it possesses no attack mechanisms. Its skin is tough, but vulnerable to fire and incendiary ammunition. A new Alien will grow inside the Chrysalis and emerge after a period of three days. It seems that a variety of Alien forms could develop at this stage, dependent on the genetic information carried by the Hyperworm. The physiology of these new forms contains many new cell structures. We have now gained a significant understanding of Alien genetics.
{{Ref Close | source = X-COM Apocalypse Ufopaedia}}
{{Ref Open | title = Chrysalis Autopsy}}[[Image:Chrysalis_Autopsy.jpg|right]]
The Chrysalis appears to be an important stage in the Alien life cycle. The cell structures we have discovered seem to suggest that the emerging Aliens have a different physiology to those previously encountered. This could indicate that there will be further stages to our biological research. The Chrysalis contains no advanced brain structure and will not respond to Psionic attacks.
{{Ref Close | source = X-COM Apocalypse Ufopaedia}}

{{Infobox open}}
{{Apocalypse Statbox Module
| name = Chrysalis
| time_units = 30-34
| health = 86-99
| stamina = 40-46
| reactions = 5
| strength = 5
| bravery = 0
| psi_energy = 0
| psi_attack = 0
| psi_defense = 100
| accuracy = 100
}}
{{Apocalypse Statbox Module/Hidden
| armor_head = 12-19
| armor_torso = 12-19
| armor_arms = 12-19
| armor_legs = 12-19
| score = 3
| size_X = 20
| size_Y = 10
}}
{{Apocalypse Statbox Module/Unique Stats
| damage_modifier_group = Chrysalis
| inventory = no
| innate_weapon = none
| unique_attributes = immobile
}}
{{Infobox close}}

The Chrysalis is the form taken on by a matured (and fed) [[Hyperworm]], and is the pupal stage of the Multiworm life cycle. From here, depending on the information fed to it, it will grow into a [[Brainsucker]], [[Anthropod]], [[Spitter]] or [[Popper]].

Chrysalides can be found aboard [[Alien Transporter (Apocalypse)|Transporters]] and [[Alien Assault Ship (Apocalypse)|Assault Ships]]. They will not be deployed as part of any [[Alien_Infiltration_(Apocalypse)|infiltration force]] nor will they be encountered in the alien dimension.

Despite being immobile in [[Battlescape_Overview_(Apocalypse)|Battlescape]], Chrysalides '''are''' capable of moving from one Mega-Primus building to another. The presence of a Chrysalis will not cause an Organization's infiltration meter to rise, though this will of course change once the Chrysalis grows into another alien. Note that a building investigation will fail to find anything if the only present aliens are Chrysalides and/or [[Multiworm Egg (Apocalypse)|Multiworm Eggs]].

==Tactical Notes==
[[Image:LifeL-Isom-Chrys-(Apocalypse).png|frame|left|In-game sprites of living and dead Chrysalides]]
Chrysalides are immobile and defenseless. They pose no threat whatsoever to X-COM agents. Intact Chrysalides will be automatically collected at the end of a successful mission.

Unless ordered to hold their fire, X-COM agents will automatically fire at Chrysalides like they would at any other alien. This can potentially waste ammunition, and stray shots may damage the building they're in (angering the owning Organization), or even hit other X-COM agents in the vicinity. On the other hand, Chrysalides provide a safe way for agents to improve their stats. Furthermore, if X-COM decides to retreat from a mission, it is prudent to destroy any Chrysalides within reach before doing so, to prevent them from evolving into more dangerous aliens.

==See Also==
* [[Aliens (Apocalypse)|Aliens]]
* [[Alien Life Forms (Apocalypse)|Alien Life Forms]]
* [[The Alien Life Cycle (Apocalypse) | The Alien Life Cycle ]]
** [[Multiworm Egg (Apocalypse) | Multiworm Egg ]]
** [[Multiworm (Apocalypse) | Multiworm ]]
** [[Hyperworm (Apocalypse) | Hyperworm ]]
** [[Chrysalis (Apocalypse) | Chrysalis]]

{{Unit Navbar (Apocalypse)}}
[[Category: Apocalypse]]
[[Category: Aliens (Apocalypse)]]
[[Category: Research (Apocalypse)]]

Long War 2

2025-05-01T13:13:41Z

Magic9mushroom: Reverted edits by Makus (talk) to last revision by Solymr

[[File:LW_longwar_01_ALT-1_transparent.png|800px|center]]

Welcome to the '''XCOM2: Long War 2''' wiki, a part of '''UFOPaedia.org'''. Long War 2 is a mod designed by '''Pavonis Interactive''' for '''[[XCOM2]]''' that introduces many changes, large and small, to the vanilla version of the game. It is longer and more complex than the vanilla version but gives you many more tools to combat the alien threat.

This wiki is meant to explain the main changes introduced by the mod to the game and it is a work in progress - everyone can contribute by creating an ''Account'' and ''Edit'' the pages. Please use the ''Talk'' button to discuss any aspects of this wiki. If you want to discuss the mod with its creators, please use the [http://www.pavonisinteractive.com/phpBB3/viewforum.php?f=15 Pavonis Interactive forums].

If you're looking for the original mod for '''[[Enemy Unknown (EU2012)|XCOM:EU/EW]]''', see '''[[Long War]]'''.

For the alternate project aiming to port Long War 2 to the '''War of the Chosen''' expansion, see '''[[Long War of the Chosen]]'''.

{{:Long War 2 Table}}

[[Category: XCOM 2]]
[[Category: Long War 2| ]]

Talk:XCOM 2

2025-05-01T13:12:56Z

Magic9mushroom: /* basically no need make so many double pages */

Why do you need to convert XCOM Wikia links to UFOPaedia ones? It's better to write your own material than to be copying stuff from one wiki to the other. [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 08:11, 11 July 2015 (EDT)

== Anyway i add some infoboxes to XCOM 2 enemies ==

Anyway i add some infoboxes to XCOM 2 enemies pages with stats its just copy game info)

Links like ADVENT Priest and Resistance Factions and The Chosen need a (WotC) beside them like Res. Ring. -EH YOUUU 2, 3/June/2024, 22:24.

== basically no need make so many double pages ==

we just can all move to up to date page https://www.ufopaedia.org/index.php?title=Long_War_of_the_Chosen
coz no one need old info and no one play in pure xcom2

:Actually, yes, people do play the vanilla version of games. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 13:12, 1 May 2025 (UTC)

Talk:Known Bugs

2025-04-28T15:02:45Z

Magic9mushroom:

= Classification etc =

== Bugs vs Exploits ==

Could someone comment please on the distinction between a bug and an exploit, and where to put each one? I would guess that a bug is something that undesirable and an exploit "might be" desirable, if you want to cheat. But what about exploits that happen by accident, or bugs that need to be forced to happen?

I was going to add the Research Rollover bug to the Exploits sections, but they seem to all be under construction. What's the agreed approach?

[[User:Spike|Spike]] 04:16, 15 March 2008 (PDT)

* i think that an exploit is somthing you can trigger and gain an advantage from. a bug may or may not have a known trigger, and does not give an advantage if it does.
: All exploits are bugs, either in implementation or design. When using a bug to gain advantages that bug is used as an exploit (you are exploiting the bug). [[User:FrederikHertzum|FrederikHertzum]] 13:39, 10 May 2011 (EDT)

:: IMHO, Laser Pistols Gifts to train reactions is an exploit, but it does not involve any bugs. It merely exploits the fact that laser pistols will not penetrate the front armor of Flying Suits. [[User:Jasonred|Jasonred]] 16:31, 10 May 2011 (EDT)

::: I guess the point is to differentiate if it's a bug that's being exploited to your advantage, or it it's something confined within the game mechanics that you are exploiting to your advantage (even if using it as intended). -[[User:NKF|NKF]] 02:31, 11 May 2011 (EDT)

:::: Another definition: An exploit is
::::: a) a move allowed by game interface
::::: b) that sidesteps another part of the game mechanics
::::: c) and creates inadequate advantage for the moving player in the process.
::::: An exploit is not a bug, but it can be connected with a bug, if the latter allows a move mentioned in a). Most obvious exploits render whole parts of game mechanics obsolete (see b) above), because they are always more advantageous. In games that feature equal terms for AI and the player, an exploit can be discerned simply by the fact that AI does not use it (sadly this is not true in X-COM). Clear exploit in X-COM: Transfer soldiers = no monthly payment. Suspect exploits: grenade layout. Most probably not an exploit: Sniping (although the inequality with AI is suspect). Clearly not an exploit: dropping weapons to prevent Psi mass murder (this one is made exploitable by the AI unable to pick up weapons, but is not an exploit per se).--[[User:Kyrub|kyrub]] 05:30, 11 May 2011 (EDT)

The dropping weapons sort of turns into an exploit if you do the "everyone suspect of being a psi weakling drops their weapons at the end of the turn. They all pick up their weapons again if unpsied in the next turn." The grenade layout or grenade hot potato is probably not what the game designers had in mind, but I shudder at the thought of someone who only played X-com then joined the army pulling the pin out of his grenade and then dropping it into his haversack or slinging it on his belt. [[User:Jasonred|Jasonred]] 07:43, 11 May 2011 (EDT)

: Yeah, I think we agreed somewhere that shoving live grenades in your pockets and not having them go off is madness. The relay however is not sensible but certainly possible if only a very short one (if with a live grenade), or to toss a grenade forward and prime it at the second to last person. Or more reasonably, something like a stick of dynamite with an extra long fuse. Even that's very dangerous.

: By the way, what does everyone here think of using the mind probe to check if it's safe to attack an alien while standing in full view of it, or if you're right up next to it? I've been using it a lot lately (in lieu of the psi amp), so you could say I've been exploiting the mind probe to my advantage to help me with my decision making. But is that counted as a cheat since I'm picking my moments to attack up close when the enemy cannot return fire? -[[User:NKF|NKF]] 03:30, 12 May 2011 (EDT)

:: When identifying a mechanic as an "unfair exploit" (as opposed to just a "tactic"), perhaps a simpler checklist is this (though Kyrub's is spot-on):

:: a) Is this something the developers should've expected players to do?
:: b) Is this something the developers could've easily prevented?

:: If the answer to both is "yes", then it seems fair game to me. For eg, sniping at aliens: The game KNOWS whether the soldier can see the target (you get a flashing indicator if so), and so it would've been trivial to prevent it. Is it something the regular gamer will try? Certainly; therefore it can be considered expected behaviour. Ditto for using the Mind Probe to make attacks without fear of reaction fire; those things aren't cheap, they sell for a bunch, so it stands to reason that they'd have tactical value!

:: Things like the transfer bug are clear exploits. The devs would've implemented that system so that, if you order personal near the end of the month, you don't end up paying for them twice before they ever arrive - but in the process, they forgot that "purchase" transfers are treated in the same way as "between-base" transfers. To fix one scenario without breaking the other, they'd've needed to code in some extra stuff so the game could tell the difference - they probably just figured the regular gamer would never notice, assuming they ever realised the problem existed.

:: The "dropping weapons" thing is a little trickier to work out - yes, the devs should've seen it coming, but would it've been easy to fix? Aliens could've been twigged to either ignore un-armed soldiers... but those soldiers could re-equip next turn. Aliens could also've been twigged to attack randomly... but that would make their psi powers far LESS effective! I suppose the fix, if any, would've been unarmed melee attacks, but the implementation they went with seems to be the next best thing IMO.

:: In regards to the "grenades in inventory" thing, it's probably common knowledge by now, but they DO go off in the alpha of the game. Presumably someone made a conscious decision to change that, though it could still just be an accidental bug. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 09:02, 12 May 2011 (EDT)

Sniping at aliens is a very bizarre case, since almost all players will fall prey to the aliens sniping at you long before they snipe the aliens. The behaviour of the aliens to step within sight radius, take one step back, then fire without fear of retaliation *looks* and *feels* like clear exploitation of the rules, but the computer can't be a cheater, can it? So we humans carry that one step further. Mind you, I think X-com would be in trouble if the aliens could snipe you from across the map once they know your positions... especially since the aliens have cheating "if I spot 1 human, I spot ALL of them" abilities. Especially on maps where the aliens get Blaster Bombs...

An interesting note about sniping and LOS: When I first played Xcom, my first mission was in the jungle. Because of all those plants, when my first soldiers spotted an alien, after he shot at him, I tried to make my 2nd soldier open fire and was informed "NO Line of Fire". I could only get my 2nd soldier to fire by positioning him in such a way that I got the flashing number. Henceforth, I assumed that you could ONLY fire at the aliens when the flashing number was there. LOL. LOF. LOS.

Transfer bug wise, I thought that the devs merely programmed the game to count how many staff were currently in the base, then deduct that from Xcom coffers? As far as ordering personnel near month end goes, you end up paying salary for them if you order them more than 48 hours from month end, right? "realistically", they should make staff draw salaries based on when they were hired, but this would be too much effort.

"dropping weapons" would have been easy enough to fix... just teach alien AI how to pick up weapons. Like they did in Apocalypse.

As far as grenade relays go, if you ever join the army, and you toss a live grenade at your squadmate, you're gonna be court martialled! lol. Xcom grenades are weird cause they presumably come with a computer console where you program them or something that takes a lot of TU, if I already have a grenade in my hand I don't think it takes long to prime it compared to throwing it...

Pretty clear exploit/bug is tossing grenades through the ceiling? That breaks all laws of realism/logic/whatever, and I'm sure the devs didn't plan for THAT to happen! [[User:Jasonred|Jasonred]] 18:18, 12 May 2011 (EDT)

: Turns out the "spot one, spot all" thing was wrong all these years. However, units can be "spotted" by sniping an alien, hitting it, but failing to outright kill it; this may have contributed to the misconception.

: The game considers the base to have the correct amount of personal as soon as you initiate a transfer - if a base has room for ten people, you can't send two groups of ten, as soon as the first is in transit the game will correctly recognise that the destination is now filled up and won't allow you to send any more. Likewise, if you hire soldiers, they'll count towards the allowance of more promotions in your ranks before they ever arrive at a base. That is to say, the payment system deals with personal counts in a different way to every other system in the game, making it look like it's intentional (if badly exploitable) behaviour. In terms of transit times, those seem to vary, I know a purchase of scientists takes 72 hours to arrive.

: Er, yes, getting aliens to pick up weapons would've indeed fixed the dropping thing. Shoulda thought of that...

: The grenade thing is indeed unrealistic however you look at it. Certainly throwing the things through ceilings is a bug, and its use is a large exploit. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 20:02, 12 May 2011 (EDT)

:: Then how do the aliens "spot" the psi weakling to target him for psi attacks? Doesn't the game ALWAYS start blasting the juiciest target, regardless of LOS? Or is it just coincidence? [[User:Jasonred|Jasonred]] 22:22, 12 May 2011 (EDT)

::: They really have to "[[UNITPOS.DAT#8|spot]]" the target before they can blast them (however, it appears that later in a campaign this rule gets broken). If they've only spotted a psi-''resistant'' trooper, they typically won't bother to make attacks at all. There's a lot of relevant information in [http://www.strategycore.co.uk/forums/Can-alien-attempt-Mind-control-Pani-t8115.html this thread]. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 23:28, 12 May 2011 (EDT)

: Your talking about your post on http://www.strategycore.co.uk/forums/Can-alien-attempt-Mind-control-Pani-t8115.html&pid=96123&mode=threaded#entry96123 ? Well, I'd just like to point out a massive flaw in your testing logic. You forgot that aliens will launch psi attacks based on chance of success, and chance of success varies based on distance from aliens. In other words, it could easily be that the aliens only attempted psi when your soldier was within sight of them because your soldier was now NEAR to them and therefore they had a strong chance of success.

: Also, as you have noted, it appears that your rule gets broken. In fact, it is not uncommon at all for the Ethereal Commander who is boxed up in the Command Center to launch psi attacks on victims who are separated from him by several layers of walls, as long as their proximity to him is near enough. [[User:Jasonred|Jasonred]] 21:19, 13 May 2011 (EDT)

:: Those are valid points. I've hence built a somewhat more robust testing scenario, which you may wish to [[:Image:Alien Psi Demonstration 1.rar|try for yourself]].

:: The save game consists of cloned Ethereal soldiers (all cranked up to 100 psi strength/skill), and many clones of a single trooper (most of whom have the same psi values). The Ethereals are all cooped up in a sealed room in the SW of the map, with a single trooper who has 140 psi strength/skill.

:: Directly outside the building is another trooper who only has 1 strength/skill. In the NE of the map, in another sealed room, is a soldier with 40 strength/skill. Before placing him there, I had him shoot one of the Ethereals just once, resetting index 8 of his UnitPos record to 0. Only he and the trooper inside the room with the Ethereals have hence been "exposed" to the aliens, but the "best chance of success" is obviously the psi-weakling directly outside the building.

:: If you load the map and end turn, the aliens will first attempt to take control of the dude on the other side of the map, then get to work on the guy in the room with them. Once they've taken these two, they'll completely ignore all other units.

:: In short, aliens can't use psi attacks on a unit UNLESS their UnitPos[8] index is set to less then that of the alien's intelligence stat. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 05:41, 14 May 2011 (EDT)

::: Good one. That test definitely proves a lot, rather conclusively. [[User:Jasonred|Jasonred]] 06:53, 14 May 2011 (EDT)

== Bugs vs Limits ==

''(Discussion continued from [[Talk:Known Bugs#Soldier Recruiting Bugs Tested|Soldier Recruiting Bugs Tested]])''

The "Soldier Recruiting Limit" is not a bug, it is a limitation of the game. Therefore, this should be removed from the page. If we want it somewhere else (like a new page such as [[Game Limitations]]), that would be appropriate. --[[User:Zombie|Zombie]] 01:42, 9 November 2008 (CST)

::Not sure that's necessarily the best idea, Zombie, since many of the entries on the Known Bugs article(as well as some entries on the Exploits pages) are limitations of the game engine. On just a brief glance through, the following caught my eye as engine limitations: Manufacturing limit, Storage limit, Purchase limit, 80-item limit, Proximity Grenade limit, Large units not waking up from stun, Interception last shot bug, Alien UFL radar blitz-through bug(Passing through the detection range of a radar before the detection check comes up), Free manufacturing, free wages, UFO Redux, point-scoring with Ctrl-C, permanent MC of chryssalids, Zombie-MC resurrection of agents, alien inventory exploits, anything involved with bad collision detection, extinguishing fire with a Smoke Grenade, and even your personal favorite, denying the aliens access to their own spawn points. So in conclusion, maybe it should just be left as it is; conversely, all of these entries could be kept where they are and also on a Game Limitations page, or we could leave the headers there and link them over to the appropriate topics on Game Limitations. What do you think? [[User:Arrow Quivershaft|Arrow Quivershaft]] 10:21, 9 November 2008 (CST)

: I agree with AQ (great list of examples by the way - and the Smoke/Fire limit would be another). Many, if not most, of the bugs are "Limitations" but they are logically inconsistent and not what a player would expect to happen: they are imposed by (at best) memory limitations or (at worst) design/programming oversights. I think the easiest thing to do would be to change the title of the page to Known Bugs and Limitations, or put an explanatory note at the beginning of the section to explain that "Bugs" is taken to included "Limitations". [[User:Spike|Spike]] 13:16, 9 November 2008 (CST)

By the strictest sense of meaning, a "bug" is a mistake or error on the programmers part. Limitations imposed by design or memory are not the same creature as the people involved were consciously aware of the decision. I suppose that to the normal player, any type of behavior which is unexpected/unwanted is automatically dumped in the bug category because to them there is no difference. To those of us who study the game files however, the two are unequivalent. Programming oversights, yes, those are bugs.

Some of those limitations AQ mentions are (to me at least) bugs: free manufacturing, free wages, permanent MC of Cryssies (or actually any alien for that matter), Zombie resurrections and collision detection. Large aliens not waking up from stun is again, a bug. The programmers obviously had some issues when dealing with large units in general and never quite got it right. They made some progress in TFTD by trying to fix mind controlling each section of a large unit, but royally screwed it up by selecting the next 3 entries in UNITPOS.DAT no matter what they pointed to.

Perhaps it's just my background in logic which makes me want to push for a separate category for limitations. Then again, as long as everything is listed somewhere I'm happy. --[[User:Zombie|Zombie]] 22:06, 9 November 2008 (CST)

: Actually, taking a look through the page as a whole there are various other Limits described, and the distinction between Bugs and Limits is made quite rigorously throughout - not just in the Soldier Limits and Bugs section, where the Soldier Recruiting Limit is referred to as a Limit whereas other bugs (such as paying salaries for soldiers you can't recruit) are referred to as Bugs. So we maybe just need to rename the pages "Bugs and Limits" and add an explanatory note on the distinction. From a user point of view, rather than a programmer point of view, a bug is an unexpected (inconsistent or illogical) behaviour, so for that reason I think it makes sense to keep them on the same page but try to ensure they are all correctly classified as Bug or Limit.

: By the way, it could be hard to absolutely distinguish Bugs from Limits as I suspect there are going to be some grey areas where you would have to second-guess the intentions and decisions of the coders to know for sure if something was a designed-in Limit, or just an oversight (Bug). [[User:Spike|Spike]] 06:50, 10 November 2008 (CST)

::If we distinguish in this manner, I suggest the definition of "Limit" should be, "Something imposed by the game files or engine as a limitation, most likely in context to the capabilites of the then-current personal computer." More succinctly, anything that was done to allow the game to run acceptably on what was then a PC. This would include both the Soldier and 80-Item limits, the spawn limit(40 units per side), Smoke/Fire limit, and some of the others listed. (The Purchase limit was probably more of a convienence for the programmers than anything, but it is clearly an intended feature.) [[User:Arrow Quivershaft|Arrow Quivershaft]] 13:11, 10 November 2008 (CST)

: I would add to this that sometimes a Limit may be imposed as a game design / gameplay decision, rather than in order to conserve a constrained resource in the platform (=PC). Also, I would suggest that ''intended'' Limits are Limits, but ''unintended'' consequences of Limits are Bugs. Obviously, making this distinction involves some guesswork. But I would guess that while the limit on total smoke/fire hexes was an intended Limit (to conserve PC resources), the ability to put out fires with smoke grenades and disperse smoke with IC rounds is probably an unintended consequence of the Limit, and so should probably be considered a Bug. Similarly, Base Defence spawn points are probably an intended limit, but the ability to flood spawn points is an unintended consequence of this, and thus a Bug (and an Exploit). (Spawn points should have been shared out 50/50, not humans-first). [[User:Spike|Spike]] 12:07, 11 November 2008 (CST)

::The limit on Soldier and Interception craft were probably more of a limit imposed because they capped the file and figured that X-COM wouldn't ever need more than 40 interception craft or 250 soldiers. (And I've never needed that many, case in point.)

::As for spawns, its actually difficult to take advantage of it in any reasonably established base. X-COM can spawn up to 40 soldiers in a base defense mission(tanks count as 4 soldiers), as a limit of LOC.DAT. Aliens have the same limit. So in order to take advantage of the bug, the base needs 40 or less spawns total. The Access Lift has 8 spawn points, General Stores(weapon-handling) has 11, Living Quarters has 8 more. This is 27 Spawns just getting soldiers in a base and armed. (Although the General Stores can be cut out if you perform the bug properly). Large Radar and HWD have 6 spawns(Small Radar has 2), and Hangar has 15. So overall, the "Spawn prevention" can be hard to take advantage of with all but the smallest bases. [[User:Arrow Quivershaft|Arrow Quivershaft]] 14:48, 11 November 2008 (CST)

Just to clarify, X-COM interception craft are not capped at 40 ships. LOC.DAT has a cap of 50 "things" on the geoscape screen at a time. This is shared between X-COM bases, X-COM ships, alien bases, seen or unseen UFO's, terror sites, crash sites, landing sites and waypoints. In a perfect game world with little alien activity and normally constructed bases, the max number of X-COM craft possible is 44: 5 bases with 8 hangars each plus one base with 4 hangars (or any combination thereof). If you illegally modify your base layout with an editor to get rid of the access lift, the max can be increased to 45 ships (9 hangars in 5 bases). Once clogged, all alien activity will cease.

The base defense limit of 40 units exists because of UNITPOS.DAT which has a cap of 80 entries total (tanks occupy 4 entries in this file). Auto-win missions in a base defense mission by clogging all the spawn points with X-COM units isn't as tough as it sounds, especially if your base is small or doesn't contain hangars. The main thing is getting your full quota of 40 units to spawn (meaning you should try not to have any tanks as they count as 4 units but only occupy one spawn point). This limits the base size to something like 5-6 modules depending on what you build. Still, even having more than 6 modules isn't bad as it forces aliens to spawn intermingled between your troops. With 40 armed guys staring in every direction, you can get positions of all the aliens in the first round and possibly even kill them all (depends on weapons and alien race of course). --[[User:Zombie|Zombie]] 20:12, 11 November 2008 (CST)

: I would say that Limits are the CAUSE of bugs... also, I feel that fire/smoke limit can be called a bug, because a player normally has no way to tell this, other than observation. Whereas the game DIRECTLY and CLEARLY informs you whenever you hit the 80 item or 250 soldier limits, which is more fair. [[User:Jasonred|Jasonred]] 15:22, 23 March 2009 (EDT)

Also IMHO it is not true that, say, 250-soldiers limit is a real game bug. In fact, it is not, it is just a rule of the game, or its limitation. And it is unimportant what its reason is (such or another way to store game data).

A bug is, by definition, an unexpected and involuntary result of programmers' work. However, we can only guess what the programmers wanted to attain, so this definition is both unpractical and impossible to be applied. It would be better to assume that a bug is a feature which has negative influence in the game. To clarify: the (un)famous 250-soldiers limitation does not harm in practice, as the number is really enough to play the game. But the even-more-unfamous 80-item limitation does harm and it has negative consequences - it is enough to recall the disappearing of bodies during some missions.

OK, there is no objective criteria to judge whether a feature of the game is a bug or just a limitation. But sometimes subjective criteria have to be enough. Otherwise, we would have to consider the 8-bases limit a bug. Does it make any sense? And if no, what is the difference between the 8-bases limit and the 250-soldiers limit? I feel neither is a bug. Because neither leads to further negative consequences.

And further, IMHO the buggy nature of some game features is quite obvious. If you cannot send more than 100 "parcels" of items at the same time, it is still not the bug. But if you must pay for an item you are trying to send but you cannot do it - it is a bug, perhaps everybody will agree. And similarly: the 255-scientists limitation is not a bug. But the strange behaviour of the game when you bought the 256th scientist is a bug. It would be just a limitation if the game did not allow to buy another scientist. But it allows while it cannot serve the 256th scientist properly, and that is why it is a bug.

So, I vote for removing the 250-soldiers limit from the bug list. If I am wrong in it, please add to the list also:
# 8-bases limit,
# maps with limited terrain (why should they be limited?),
# base area and base facilities limit (why wouldn't we be able to have 10 hangars in a base?),
# etc.

In yet other words, in my opinion it is not enough to show that the game does not allow to have more certain items or to do more certain actions. In order to count this among bugs, we should show that it really harms during playing the game, or just bears negative consequences.

[[User:Sherlock|Sherlock]] 03:52, 27 December 2012 (EST)

= Specific Bug Discussions =

== Misc Technical Bug ? ==

''(The context of this discussion seems to have been lost)''

This is a technical bug that doesn't happen to everyone and one this article wasn't really meant to chronical - but we won't turn away helping a fellow player if it can't be helped. It's just that there are so many random crash points in this game that it would take far too long to find them all or come up with solutions for them.

Certainly, the transfer crash can happen to some players, but it's not one that can be reproduced easily. It's just like the random crash that some players get when they research a floater medic. It crashes the game for some of us, but others don't seem to notice it at all.

It really depends on your hardware and OS setup, whether or not your copy of the game is damaged or your savegame is damaged, etc.

Does it happen in all games or just this one savegame?

- [[User:NKF|NKF]]

-----

== "Invisible Muton" bug ==

Upon shooting repeatedly a Muton, it sometimes plays its "death" animation without sound (as if falling unconscious) and it is no longer displayed in the screen, while remaining visible to my soldiers (I can center the screen and the cursor appears yellow over them). Under this state, they cannot be targeted by Stun Rods. They may play their death animation anytime they get shot, until they truly die, when they emit their characteristic sound and leave a corpse (along with any items carried).

I'm quite fond of laser weapons, maybe this happens more often with those.

Also, though I remember experiencing this quite often fighting Mutons, it may happen to any other high health race.--[[User:Trotsky|Trotsky]] 02:59, 2 July 2006 (PDT)

-----

Never seen that one myself. Another "unpatched game" thing maybe?

There's a (very rare) bug that allows your soldiers to live if they become stunned by an explosion that happens to kill them. Sometimes the game will register their death, and THEN register that they've been stunned. In every case I've seen this happen, however, the unit will have such a low amount of health that a single fatal wound will render it dead (again) on the next turn. I have a vague memory that other players may have been able to get a medkit to the scene on time...

I dunno if that's related to your issue at all (I doubt it, but... meh). I'd advise using a Mind Probe on the alien the next time it happens so you can check the aliens stun/health levels.

- [[User:Bomb_Bloke|Bomb Bloke]]

----

I'm pretty sure I've seen this with Mutons. Possibly Chrysallids as well, another high health, high armor creature. They were still readily killed by shooting the place they are. Good thought on the MP, BB

---[[User:MikeTheRed|MikeTheRed]] 08:51, 2 July 2006 (PDT)

----

I've been known to have a dying muton(in fire) to spin around and then switch to the female civilian death animation. With the scream and everything. Even got a civilian death registered at the end of the mission. And this didn't just happen once, but on another separate occasion.

Hmm. shape-shifting reptilians in the game! LOL! Happens alot [[User:EsTeR|EsTeR]]

Unusually enough, I once had a sectopod die and then drop a tank corpse. I was using the Lightning at the time for my troop carrier, so you can imagine my surprise.

Then there was one occasion where a floater dropped a snakeman corpse. Let's not even get into the sort of things the aliens like to stuff themselves with.

Your invisible alien bug is quite common, although there appears to be many causes for it. I think one involves a full object table when it comes to invisible aliens in bases. But it can also happen in ordinary missions as well. I'm guessing the game may have tried to do something in the wrong order, and sprite information for the unit may have been lost or corrupted along the way.

Having had an experience where all the chryssalids become invisible in one base defence mission was quite a shocker. I fixed this by saving the game, quitting and then restarting the game. If you ever get an invisible alien again, try this and see if it helps. If it doesn't, well, just keep a careful watch on your map and any alerts that pop up as you play.

There's a similar but less severe bug where a dead alien will still leave its centre-on-unit alert button, but this goes away shortly after you move or turn.

- [[User:NKF|NKF]]

----

That last bug happens when exploding Cyberdiscs kill nearby Sectoids, doesn't it?--[[User:Trotsky|Trotsky]] 23:56, 2 July 2006 (PDT)

----

This is a pretty easy one. I guess this bug occured on UFO recovery on a battleship, an alien base assault or a base defense mission? As soon as there are too many items on the map, the game saves some item slots for the equipment to be displayed (since it is more valuable and more important to research). This would also make stun weapons lethal if the stunned aliens would vanish. therefore the game has a failsafe if an alien is stunned (or badly wounded and becoming uncontious). The downed alien's stun level is set exactly on its left health points therefore resurrecting it instantly. This cycle is broken when the alien is finally killed. This means if you want to stun an alien in such a situation you have to destroy some items first.

- by tequilachef (April 4th 2007)

== Vanishing snakemen ==

I've known snakemen to become invisible when standing on a hay bale. On the first occassion I had a poor tank getting shot while spending numerous turns looking for it. On the second occasion I had an alien under Psi-control, left it on the hay bale, and couldn't find it next turn. - Egor

---

This is not limited to snakemen. Hay bale block visibility quite much when a unit is standing on it. Two possible solutions:
- Destroy the hay before entering
- Shoot at the hay. If it is destroyed any unit on it will become visible (as long as no other bales are blocking the line of sight). You might also hit the enemy directly.

I Dnt know if the aliens are affected by this diminished sight, too. My guess would be no.

- By tequilachef (April 4th, 2007)

== Blaster Bomb Bug ==

I'm currently playing through X-com UFO Defense, I have the collectors edition version. I'm in the process of trying to catch a live alien commander and the blaster bomb bug is making this very difficult. If i remember correctly a commander is always in the command center of the the alien bases. The problem is anytime i get close there is always a dude with a blaster launcher up there that tries to kill my troops. When they try to fire it down at me the bug kicks in and they blow up the whole command room and all the aliens in it because they can't figure out how to get the blaster bomb down the grav lift thing in there. This is making it very dificult to actually catch a live commander. Anyone have any ideas for tactics or anything to breach that room without the aliens trying to fire a blaster launcher up there? - eL Hector

: I can suggest two possible solutions. The first is to wait outside the command room for the alien to move closer to you. If it comes out of the room or if you know it has moved down the lift, you then burst in and stand right next to it to stop it from firing the blaster. This is risky because there could very well be a heavy plasma toting alien in there. The other is to use a small launcher and launch it up at the ceiling near where you think the alien with the blaster is standing. -[[User:NKF|NKF]]

== Disappearing Ammunition ==

I have observed that problem with X-COM 1.2, modded with XCOMUTIL. My stun bombs and heavy rocket missiles, along with clips for the auto cannon went missing.
[[User:Vagabond|Vagabond]]

------

Just run a test using my 1.4 DOS version with XComUtil but my stun bombs didn't disappear: 30 + 1 back in the base they came from, same number after I went tactical and I dusted-off immediately. Are you running XComUtil with Runxcom.bat or did you simply run Xcusetup?

[[User:Hobbes|Hobbes]] 22:12, 22 February 2007 (PST)

:Is it a case of hitting the 80-item limit?--[[User:Ethereal Cereal|Ethereal Cereal]] 12:28, 23 February 2007 (PST)

------
With runxcomw.bat, as everytime. Apologies, I retested and it seems like I was mistakened, but I could have sworn that I lost them dang stunbombs. Had to manufacture some. I will test some more, using four heavy weapons and seeing whether their ammunition disappears at all. Thanks. [[User:Vagabond|Vagabond]]

==MC at end = MIA?==

I am sure I have seen this again recently, where I won a mission with no casualties (I thought), but the last thing I killed was a Commander that had been chain MC'ing a psi-attack-magnet trooper, and that trooper was listed as MIA at the end (presumably because he was on the enemy side at the end of combat). Is this a bug, or is there another way to get MIA's on a completed mission that I might have missed?

Since then I have been waiting for the leaders to panic at the end before killing them (or waiting for a rare resist), so I can safely exit, but am I being overcautious?

--[[User:Sfnhltb|Sfnhltb]] 13:45, 27 February 2007 (PST)

If the trooper was mind controlled on the turn you killed the last alien it will be listed as MIA. No bug there :)

[[User:Hobbes|Hobbes]] 18:16, 1 March 2007 (PST)

Huh, why would that happen - your soldier should recover the very next round, why would he go MIA?

--[[User:Sfnhltb|Sfnhltb]] 18:20, 1 March 2007 (PST)

Doesn't make sense to me as well but that's how the game works.

[[User:Hobbes|Hobbes]] 15:05, 2 March 2007 (PST)

----

It seems that regaining control of units under enemy mind control works different for alien and human players. My guess: aliens under human MC are reverted to alien control AFTER THE ALIEN AND BEFORE THE HUMAN TURN while human units under alien control are reverted RIGHT AT THE BEGINNING OF THE HUMAN TURN. This explains three different phenomenons:

- The discussed MIA "bug" (he unit would be returned in the next human turn, but since it never starts it is lost. The mission is still won since no unit with a "genuine alien" marking is left)

- The fact that a mission is lost when the last human falls under MC while it is not won when this happens to the last standing alien (the aliens get their unit back before their turn starts and therefore have a unit left to pass the "anyone alive?" check, the humans would have no unit left to start a turn with. They WOULD have as soon as the turn starts, but no unit left before turn means bust)

- The fact that aliens still can see all an MCed human saw at the end of the human turn that follows the MC while this is not vice versa (The MCed human can give information to the alien side before reverted while an MCed alien is reverted too early). The result is that aliens can control a human indefinitely without having any alien seeing him until the MC is disrupted for one turn.

All confused? Then I did a good job! No seriously, this must be the explanation, I couldn't think of any other way.

- By tequilachef (April 4th, 2007)

: You're absolutely correct on the first two points. It's a sequence issue - you never get round to recovering the unit before the new turn starts, so you end without any units whatsoever. Makes senses too since the aliens would continue to continue to mind control that same unit over and over indefinitely.

: The third point however: The aliens don't need to know the location of the last MC'd unit. They know the location of all your troops whether they've seen them or not from the very start. They appear to give you a few turns of grace where they won't attack you outright (unless, from my observation, all your soldiers are incredibly weak). This is evident because all of the aliens will eventually make their way towards the nearest soldier even though their movement pattern may seem semi-random. Also, they know where you are because they can initiate psionic attacks without having seen any of your troops. They generally go after the weakest troops first.

: Just to add a semi-related point, but from the alien's perspective. If an MC'd alien unit is in the exits when you abort the mission, this alien is not recovered and in fact simply vanishes. Any equipment it was carrying is recovered, unknown artefacts or otherwise. You could possibly think of this as their version of MIA. However, the aliens differ ever so slightly in that if it's the last alien standing and under temporary mind control by the player, the mission doesn't end straight away. But I guess this is only because the player has everything under control, whereas in the other scenario, the Ai is in control.

: -[[User:NKF|NKF]]

My observations show that, at least in some versions of the game (tested with clean DOS 1.4 version, under DOSBox), the game crashes at the end of the human turn if all alien units which are still alive, are Mind-Controlled. If it was confirmed, it would be another not-listed-yet (serious) bug.

[[User:Sherlock|Sherlock]] 17:52, 26 December 2012 (EST)

== Crash Site in the atlantic ocean ==

That's right, my game generated a crash site on water. Here are the details:

- Crash Site a bit southeast of the USA (which was infiltrated a few days before by sectoids, resulting base had already been taken out), but certainly not on land.

- UFO: battleship, floater, alien harvest

- Geoscape: 8 X-Com Bases, 1 (known) Alien base, 2 other crash sites, 1 other (known) flying UFO (though almost worldwide decoder coverage), 3 X-Com Crafts out, 1 waypoint

- Date: January 2000

- Most Interesting: The Craft that downed the ship was a recently finished Firestorm (first human-alien hybrid craft I had built, I know this is lame for that date. Limited myself on 25 Scientists to improve the challenge) equipped with twin plasma. I had it built and equipped in Antarctica and then transferred to Europe. This base had no Elerium, a fact that enabled me to use the infinite fuel exploit which was in effect when downing the UFO. My craft was only slightly damaged when doing so. The battleship was the first target assigned to the craft, it came directly from my base.

- When shot down, the UFO was not targetted by any other craft.

- I had not lost or sold a single craft to that point.

- When sending a squad to the crash site the game didn't crash but generated a farm land ground combat terrain.

- I was not able to reproduce the bug from the savegame dated 2 hours before downing the UFO

Well guys, any intelligent guesses? I still have the savegames (before and after downing)! If you want to have a look, write here.

- By tequilachef (April 5th 2007)
----
: Well I'm sure you know about crash sites that are near land can sometimes actually be on water, so I'm going to assume that this site is well far away from any land mass. Could it be a weird entry in GEODATA\WORLD.DAT that has a land mass out in the ocean? Also are you sure the game didn't crash? Sometimes when it does it will load the previous mission (and usually 90% are at farm terrain). Are you sure it generated a new map and not load the last one?
:No real guesses but maybe some starting points to look at. I've probably stated some obvious situations you know about and have accounted for, but it never hurts to double check :D
- [[User:Pi Masta|Pi Masta]] 14:23, 5 April 2007 (PDT)

== Inconsistencies in MCing Cyberdiscs and Sectopods ==

I experienced, that when MCing one quadrant of a large terror unit any action it does only affects this quadrant (especially use of time units). That means, when TUs are up for one part, MC another one and continue firing. This however does not work out when moving the unit while it is not under complete control. The TUs used up by the resulting reaction fire from the rest of the unit is also deducted from the TUs "your" part has left (making it impossible for the controlled parts to return fire). This however only happens under reaction fire, not if "your" part fires on it's own. I don't know if this comes up when uncontrolled parts shoot by themselves in the alien turn, since this is hard to find out.

: That's because large units literally are made up of four separate units. They only share the same set of general stats (in unitref.dat). Unfortunately the 'under mind control flag' is unique to the four units, not the shared stats! So you in effect have multiple units under different control sharing the same stats. So if you move and it results in a reaction from the unit, it will spend the TUs you're using.
: Successful mind control automatically fills up the unit's TUs, so each mind controlled sector gets to move or attack again until there are no more sectors to mind control. Useful way of turning reapers into long range scouts!
: In TFTD, they attempted to fix this bug, but in fact made it much-much worse! The only way to mind control the unit properly is to control the upper left quadrant. Only! Any other quadrant will result in a partial (clockwise) control, and you may gain control of units other than that unit, or may even get into situations where you gain permanent 'partial control' of a large unit you haven't even sited. Wackiness all around!

:- [[User:NKF|NKF]]

== Facility Dismantle Bug ==

Boba: I've never experienced this bug myself in all my games in the Collectors Edition. It may very well vary from computer to computer.

-[[User:NKF|NKF]]
:I, however, have experienced it. I lost an entire month's worth of playtime because I couldn't solve it. [[User:Arrow Quivershaft|Arrow Quivershaft]]

::Anyone, any ideas on why it might vary from PC to PC? -[[User:MikeTheRed|MikeTheRed]]

:::I'd check other factors before blaming a given system. Assuming no mods are being used the most obvious is the order in which you initiated the construction of the modules. Then we've got which one was due to be completed first, and I'm sure there's a few other things to test out. Usually, a player won't cancel in-progress modules on a regular basis, so you wouldn't expect this bug to turn up often. - [[User:Bomb Bloke|Bomb Bloke]] 01:53, 9 June 2007 (PDT)

:Easy way to reproduce: build 2 General Stores. Now delete the "second one" (see offset 16-39 in [[BASE.DAT]] for the order). Wait for the first one to complete. It'll crash immediately after the "end of construction" dialog. A fix is available [[User:Seb76#Bug_Fixes | here]]. [[User:Seb76|Seb76]] 15:52, 22 July 2008 (PDT)

== Manufacturing Limit Bug ==

Unfortunately, Mike, no you did not get it correct. It is the raw number of hours needed to complete the project, not the projected hours. I discussed this on the X-Com Forums a few months back at the following link: http://www.xcomufo.com/forums/index.php?showtopic=242027760&st=0&#entry164411

I did tests at the time in regard to the accuracy of the data given there, but I've lost the results. I'll quickly redo the tests in the next hour or so. [[User:Arrow Quivershaft|Arrow Quivershaft]] 19:00, 8 June 2007 (PDT)

:Tests complete. The breakpoints for every item were exactly where I predicted, regardless of number of engineers assigned. (I ran up a huge queue of items at my dedicated factory base on an old game, and then assigned whatever engineers would fit onto one project at a time, canceling projects as data was confirmed. This is only semi-random, but it serves our purposes.) I did run into a single issue, though. It appears that despite having 5 empty hangars at a (different!) base, the workshop there could not queue up more than 3 of any one craft at a time, thus making this bug impossible to replicate with the Firestorm or Lightning, as you must be producing more than three for the bug to occur. However, it still works with the Avenger. Later, I shall see about constructing a dedicated Hangar base with 7 hangars in order to attempt to replicate the bug. [[User:Arrow Quivershaft|Arrow Quivershaft]] 19:33, 8 June 2007 (PDT)

::Sounds great, Arrow. Why not post a simple example that shows how the problem works. As in, "with 1 Eng and 2 Avengers you might think X, but no, it's Y". And please delete my example. And it's a fine pleasure to meet you! Cool - [[User:MikeTheRed|MikeTheRed]]

:::When you say the usual resources are used by the "lost" resources, that includes cash, right? It sounds like if you're willing to foot the extra bill [[Buying/Selling/Transferring#Manufacturable_Prices|money/component-wise]], this could be used to build Avengers slightly faster then normal.

::: The usual time is 34000 hours. Double that and subtract 65535 and you're left with a paltry 2465 hours. Even a single workshop squad of 10 engineers will pull that off in a little over ten days. - [[User:Bomb Bloke|Bomb Bloke]] 01:53, 9 June 2007 (PDT)

::::Sadly, this exploit doesn't work, because the high bit is stored SOMEWHERE. I lack a hex reader and have no code reading skills to speak of, so I'm a bit limited here. If you set up a Workshop as you described, the game would take all the time for 2 Avengers, all the resources for the same, but in the end only produce 1 Avenger. Meanwhile, I'll run more tests on the resources thing. I could swear it consumes the resources, but I'll double check.

:::::There is no need to store the high bits if the actual completion condition (assuming adequate money) is "number made is number ordered", which wouldn't reference the hours remaining at all. - [[User:Zaimoni|Zaimoni]] 01:49, 9 Oct 2007 (CDT)

::::Tests done; I was unable to replicate the 'disappearing item' trick,(Which I didn't test for last night) even with Avengers! It appears I was wrong; this still counts as a bug, though, because the wraparound is a problem.

::::Ironic that so much of this discussion centers around Avengers, because that's where I discovered this in the first place! [[User:Arrow Quivershaft|Arrow Quivershaft]] 06:48, 9 June 2007 (PDT)

----

I'm revisiting XCOM and was working on [[Manufacturing Profitability]]... Arrow, can you (or anyone else) say a little bit more on the Known Bugs page about this [[Known_Bugs#Manufacturing_Limit_Bug]]? It's not clear to me exactly what the bug does, except that it understates hours. Is that all?... does it still take the (non-buggy) amount of time, still use all the same resources, still make the same number, etc.? It sounds like it could be a drastic bug - or is it only a very superficial one, a display bug for the hours? It sounds like you're leaning toward this latter.

Also on a semi-related note... I could swear I saw much more detailed info on the [[Known_Bugs#Facility_Maintenance_Costs]] issue... IIRC, the incorrect amount that's charged for maintenance, depends on exactly where a facility is in the base. IOW, different "rows" of the base cost different amounts. Could somebody provide a link there, and/or flesh the bug out better?

Thanks! - [[User:MikeTheRed|MikeTheRed]] 11:22, 8 October 2007 (PDT)

:I've actually seen the bug work both ways, but I've only been able to actually replicate the more superficial version of the bug. So the bug report up is about a superficial bug that drastically understates production time. If you wish to make this clearer, you have my blessings. As well, that 'different charging based on location' is dealt with here: http://ufopaedia.org/index.php?title=Talk:Base_Facilities ; however, the table has been broken with the Wikiupgrade, and I lack sufficient knowledge of HTML table code to fix it. But it should be of use to you. [[User:Arrow Quivershaft|Arrow Quivershaft]] 11:26, 8 October 2007 (PDT)

::Cool, I fixed [[Talk:Base Facilities]] but also re-organized and expanded [[Base Facilities]] so that it includes that bug in detail, as per Talk... this is an important issue that should be up front. I see that there's a separate [[Maintenance costs]] page, but I can't see having something so important (the maintenance bug explanation) all on its own page (which makes for a rather short page) rather than together with all the rest of the base facility info. If others agree (or don't care), I'll move anything remaining on Maintenance Costs to the Base Facilities page, then delete Maintenance Costs and re-route links. And if somebody does care, then please move my new section to Maintenance Costs, and move all the links, etc. Oh also I put in more words on your Manufacturing Limit Bug - how does it look? - [[User:MikeTheRed|MikeTheRed]] 16:37, 8 October 2007 (PDT)

:Looks pretty good, although it'll wrap fully; if you ask for 120000 hours, it won't be displaying 'almost no' time. The way I discovered it was when building two Avengers; I ordered two, paid for two, waited for two...and got one. But as said, haven't managed to repeat it, so until I do, we'll leave it like that. [[User:Arrow Quivershaft|Arrow Quivershaft]] 18:00, 8 October 2007 (PDT)

::I just revised and put in your specific example, because it's certainly possible some of us die-hard players will order up more than 1 Avenger at a time - and it's guaranteed it'd be a pain if 1 of them disappeared, laugh. I wasn't sure how concrete you were on that example but now I hear you say, you are sure it happened at least once. - [[User:MikeTheRed|MikeTheRed]] 18:33, 8 October 2007 (PDT)

:I have a question concerning the manufacturing "bug" which eats a craft in production due to wrap-over of the byte. Arrow (or whoever did the test), did you have a large quantity of craft already built at your bases? If so, I think this bug has more to deal with clogging up [[CRAFT.DAT]]. See, that file has a limit of 50 entries. Each craft takes up one record and each base you have built also consumes one spot. 8 bases allows 42 craft to be housed, while 6 bases allow 44. If you try to buy or manufacture craft once the file is full, nothing shows up in the game even if you have hangar space available. --[[User:Zombie|Zombie]] 19:00, 8 October 2007 (PDT)

::Huh, I never knew that. I don't see it listed on the Bugs page... I'll stick it in there. I've never approached that number, but some folks might. - [[User:MikeTheRed|MikeTheRed]] 19:07, 8 October 2007 (PDT)

:I was able to continue building other Avengers after that project, and they appeared correctly, so I do not believe that is the issue. In any event, I have a very bad case of 'archivism' and probably still have the save game and the CRAFT.DAT file around on my system; in fact, I think I was playing it a few days ago. I can see if I can find it and upload it; it created a 'hole' in the Avenger fleet numbers, where Avenger's x and x+2 were built, but x+1 was not. I'll look for it tonight and tomorrow and upload it to the wiki if I find it. [[User:Arrow Quivershaft|Arrow Quivershaft]] 19:10, 8 October 2007 (PDT) EDIT: I found the file; I have 28 Avengers and 1 Skyranger in my employ. All Avenger numbers EXCEPT #2(Avenger-2) are accounted for, and I have not sacked or lost any Avengers. So this is where the hole and 'eaten' Avenger is. If anyone wants the CRAFT.DAT file from this game, I'd be happy to forward it. [[User:Arrow Quivershaft|Arrow Quivershaft]] 21:20, 8 October 2007 (PDT)

::Sure, send it my way and I'll take a look at it. (Might as well send me the whole saved game as I may want to look at the other files too). I have tried to recreate this bug by manufacturing 1, 2 and 3 Avengers at a clip but all of them always show up. Don't know what else I could do to get this problem to crop up. --[[User:Zombie|Zombie]] 21:32, 8 October 2007 (PDT)

:File emailed. On the side, I've tried the same thing, and never been able to repeat the bug. It's been months since the first discovery, so I can't recall whether it was the first or the second Avenger that didn't appear. So maybe it was just a fluke. [[User:Arrow Quivershaft|Arrow Quivershaft]] 21:57, 8 October 2007 (PDT)

== Unconscious Enemy in Equipment Screen ==

The following happened to me repeatedly over the last few days.

In the last tactical Mission a live alien has been captured. When now beginning an UFO crash recovery mission this type of alien (same race and rank) appears in the equipment screen before the mission starts, meaning I can give it to any of my soldiers.
If I do so I can store the alien in the skyranger for the duration of the mission and, if it gains consciousness, kill or stun it at the end of it. A pile of equipment without a corpse will be in the UFO, indicating that the stunned alien is not some kind of duplicate but instead has been taken from the aliens of this mission. This is supported by the fact that in those missions the maximum number of crew members has not been surpassed.
If I do not do so the Alien will be placed in the crashed UFO. Whether it is unconscious or not I do not know, but the fact that it is completely disarmed when encountered in the battle suggests that it is.

So far it seems the following is necessary for the bug to occur:
# An alien has to be captured alive in the last tactical combat
# It has to be of the same race and rank as one of the aliens in the new tactical combat

So far this only worked...:
# If the new tactical combat was an UFO crash recovery of a medium scout.
# For floaters and mutons
# For soldiers and navigators
# If the alien in the last mission was stunned by normal weapon fire (although I do not think this is important) and not picked up (again, not likely to be important) or destroyed (which would mean it has to be actually captured)

It seems NOT to depend on the following:
# The type of the last mission (were, so far: Ground assault battleship, crash recovery large scout, base defense)
# Which squad or vessel was involved capturing the alien
# Where it is locked up
# If it has been transferred since capture or not

Would be interesting to know:
# What happens if the alien in the inventory screen is the only survivor
# If the alien in the invenory screen is one of the aliens randomly killed in the crash or not (it is likely to be one of the killed aliens, so far the equipment piles were always within the UFO)
# If this is not limited on crashed medium scouts: Does this work with terror units? What about large ones?

Maybe this is related to the proximity grenade bug (transfer of item properties to next tactical combat).

Additionally, in one of those mission a part of the terrain was not generated correctly. It was in farm terrain (The house on the right square, or north east square, in [[Image:Terrain-cult.gif|this pic]]). The outer wall right to the right window of the southern wall (1st Floor) was missing. Directly outside of the hole was a floor tile. I could walk a soldier through the wall, but he fell right through the tile. Dunno if this has to do with the stunned alien bug.

Version is collectors edition (the one from abandonia.com).

----------------

When a mission starts, the GeoScape engine generates the unit and object tables (in MissDat's [[OBPOSREF.DAT]], [[UNIPOS.DAT]], and [[UNIREF.DAT]]) before "shutting down". The Tactical engine then generates the maps, places the aliens on it, and blows up the UFO (if need be). Whether or not map generation and the subsequent events happen before you equip your soldiers I don't yet know.

The test would be to check the aforementioned files to see if they contain an unconcious alien, and/or the body.

Note that you can't see the bodies of large units on the ground (they count as four seperate objects covering four seperate tiles, so allowing the user to pick one up would essentially let you rip them apart).

- [[User:Bomb Bloke|Bomb Bloke]] 06:35, 5 August 2007 (PDT)

----------------

I honestly have no idea of how all those files work. But I still have a savegame in battlescape that is in one of those missions. So if anyone wants to have a look at those files...

I forgot to mention: I reloaded a geoscape savegame shortly before the battle to recreate the bug, but it seems that reloading in geoscape before the buggy battle eliminates the bug. I guess his should narrow down the possible reasons...

--------

Next time it happens, backup the aforementioned files before you start another mission. I'm afraid a savegame wouldn't be of much help.

- [[User:Bomb Bloke|Bomb Bloke]] 00:54, 7 August 2007 (PDT)

== Soldiers moved to outside of combat screen ==

Hi, I've got a DOS version of UFO:EU, and I've encountered a bug in the tactical combat. Sometimes (rarely) a X-COM soldier changes its location on the map on player's turn start and is placed on outside of the map, one tile north from the (north) border of the field. AFAIR the unit is then selectable (you get the flashing highlight when cursor is above), but is stuck outside of the field. Has anybody encountered this bug? It seems to happen randomly, but more frequently during the terror missions and on early turns (so maybe it's caused by high number of player/alien/civilian units?). --[[User:Maquina|Maquina]] 08:16, 3 September 2007 (PDT)

:I've never encountered this bug in CE of UFO. Presuming AFAIR means "As Far As I Recall," what exactly was the soldier doing? Any equipment data, location, or stat info might help us pin it down. Were afflicted soldiers always carrying a specific equipment set or weapon? Where were they on the map before they got moved? Did they get bumped a few spaces, or teleported halfway across the Battlescape? Does it happen more often on a specific difficulty?(Your theory would suggest this would happen most commonly on Superhuman) Against a certain type of alien? Best of all, if you can recreate the situation in a game, save the game and then you could upload the save file to the forums or this wiki, and the rest of us could take a look for ourselves and the code divers could root around for the cause. [[User:Arrow Quivershaft|Arrow Quivershaft]] 15:03, 3 September 2007 (PDT)

:: I've had this happen to me several times in UFO and TFTD. I don't know if it's specific to the Dos version or if it can happen in the CE as well. Sometimes the soldier ends up beyond the boundary of the map right at the start of the mission, at other times it happens after you load a game. This game is glitchy, which is the source for so many of its bugs, so your soldier's coordinates are probably getting corrupted to the point where they are -1 on either the X or Y axis of the maps's normal boundaries. For me it's commonly along the top edge of the map. I don't ever recall it happening mid-mission, only at the start or after a load. I cannot faithfully say whether it happened with or without XComutil, but that could be one of the possibly many causes for this. - [[User:NKF|NKF]]

:: I don't play UFO often, so I rely on just several campaigns played. This happens rarely (I've encountered this bug twice in my last campaign with ~80 missions played), but if you haven't seen this happen then it probably doesn't show up in the CE edition. In my experience the soldier is moved always beyond the north/top map border. I think (but I'm not sure) that this affects the first soldier from the team more commonly than others (or maybe even exclusevily?). The equipment/armor carried is probably not relevant, since the units moved this way don't have any special stuff, and this bug shows up on different stages of the gameplay (ie. sometimes when you have ordinary rifles, sometimes when all your units got heavy plasmas and power suits). --[[User:Maquina|Maquina]] 04:12, 4 September 2007 (PDT)

'''MY ramblings have been moved to my discussion page''' [[User:EsTeR|EsTeR]]

==Great Circle Route==

Should we have the Great Circle Route bug noted on this page at all? [[User:Arrow Quivershaft|Arrow Quivershaft]] 20:33, 6 October 2007 (PDT)

: what is the great circle route? [[User:Jasonred|Jasonred]] 07:56, 31 March 2009 (EDT)

:: Pick two points on a globe, then hold a thread or string taut at those two points. That practically minimizes the length of the thread/string on the globe. You're now looking at a great circle arc (or route), the shortest distance between two points on a globe. -- [[User:Zaimoni|Zaimoni]] 11:15 March 2009 (CDT)

: Just as a line is the shortest distance between 2 points on a flat plane, a great circle is the shortest distance between 2 points on the surface of a sphere. The bug, by the way, is that aircraft in the game ''don't'' follow this shortest, "great circle" route. [[User:Spike|Spike]] 12:38, 31 March 2009 (EDT)

:: What a grand sounding name, for something so simple, lol. ... I thought you were talking about when you tell your soldiers to go from point A to point B, and for some reason they figure that Zone A and Zone B are really far apart, despite actually being side by side. (I shot a hole through a wall, clicked to walk to the other side, and my idiot soldier walked one big circle... to use the door! And got ambushed and killed by an alien. ... dum dum DUMB DUMB.)
:: Even the more modern games have problems with their pathfinding algorythms. Admittedly, games like Baldur's Gate had to do it in realtime.
:: On a semi-related note, I remember this guy called E-man, he was chasing a guided laser beam that was going to kill his girl, around the world, but he couldn't outrun it since he couldn't break the speed of light, only equal it by changing into a Laser himself. So... inspiration! He turned into a very powerful laser, and made a shortcut THROUGH THE EARTH... the straight line beats the great circle route, lol.
:: Thanks for the reply guys [[User:Jasonred|Jasonred]] 15:56, 31 March 2009 (EDT)

Added to article. [[User:Spike|Spike]] 16:41, 3 September 2012 (EDT)

==Bug not listed: Missing soldiers during base defense==

I encountered an interesting bug concerning base defense missions:
My base got attacked while about 30 soldiers and 10 HWPs were present. The usual equipment assignment screen was skipped and the mission started instantly with only the HWPs spawned at the map. Not even a single soldier bothered to show up... *sigh*
Although this turned out to be in my favor (you should have seen the puzzled Ethereals trying to panic my tanks) I´d like to avoid this bug if possible. I was able to reproduce this bug several times and with different bases.
Can anyone explain this bug and/or tell me how to avoid it?

Game version: Collectors edition. - [[User:NewJoker|NewJoker]]

-----

Well, ideally, we need to know what your base's construction was to be sure of this, but I think the most likely circumstance is that the HWPs took up all the spawn points. HWPs have maximum priority for spawning(followed by Soldiers, and then Aliens), so if you have enough of them garrisoning a base, it's entirely possible that soldiers and aliens won't spawn. However, this doesn't explain why the soldiers didn't start stealing the Alien spawn points...in any event, you might want to take the save game file, zip it up, and get ready to email it. I'm sure [[User:Zombie|Zombie]] would be quite interested. [[User:Arrow Quivershaft|Arrow Quivershaft]] 15:28, 13 November 2007 (PST)

-----

It's not the spawn points, it's a [[UNITPOS.DAT]] limitation. A maximum of forty records (out of the total of eighty) are allocated for your units, and tanks (which take up four records each) get first pick. Having ten tanks means there's no room left for anything else.

Ditch one HWP and you should see four units take it's place. - [[User:Bomb Bloke|Bomb Bloke]] 16:42, 13 November 2007 (PST)

-----

I´ll try with a decreasing number of tanks and report the results. As I wrote above having only HWPs isn´t too bad dependent on what enemy is attacking. [[User:NewJoker|NewJoker]]

----

This should be mentioned in the [[ExploitsE#Base Defence Mission Spawning Issues]] section. The Bugs/Exploits really need to be sorted and consolidated. - [[User:NinthRank|NinthRank]] 16:57, 13 November 2007 (PST)

-----

The limitation to 40 records seems to be the case; each tank I dumped got replaced by four soldiers.
So this can be used to effectively manage unit combination. Thanks for the quick replies! [[User:NewJoker|NewJoker]]

==Bug not listed: Ufo Gold (Windows Vers. abandonia.com) crashing when plasma defense is finished==

I recordnized this bug a few times now. (with hacked AND unhacked game)
If i place a plasma defense in 7 bases at the same Time and they are finished at the same Time, the game crashes sometimes.
In hacked game, it seems to crash even more when Alien containment is finished, plasma defense, shield defense...etc.
couldnt find it here...greetz

: I somehow doubt the sourcing is the issue. [You may want to fund the next XCOM series game with a Take2 re-release of UFO :)] More generally: the game only reports the construction of a given type of facility once, no matter how many bases it completes at simultaneously. I've only tested this in vivo with three-of-a-kind at once across six bases, however. It does seem reasonable that some sort of counter of undisplayed completions would "overflow" (attaining crash). -- [[User:Zaimoni|Zaimoni]] 10:05, Feb. 28 2008 CST

::I've encountered this bug myself with General Stores, actually, not just Plasma Defense(which I never build). EDIT: Some quick tests seem to show that there's a chance the game will crash any time two base facilities are done at the same time, regardless of whether they're in the same base or not or if they're the same facility.(although it seems to happen MUCH more in the event they're in different bases.) [[User:Arrow Quivershaft|Arrow Quivershaft]] 10:13, 28 February 2008 (PST)

== Soldier Recruiting Bugs Tested ==

Just to note that I have positively tested and replicated the bugs listed under the new(ish) section [[Known Bugs#Soldier Recruiting Bugs|Soldier Recruiting Bugs]]. [[User:Spike|Spike]] 18:08, 19 March 2008 (PDT)

==Floater Medic Bug==

I have not thus far encountered the Floater Medic Bug; in fact, Floater Medics are often used to fill up my Rogue Gallery with interrogations. [[User:Arrow Quivershaft|Arrow Quivershaft]] 06:50, 24 April 2008 (PDT)

Strange, it would always occur in my version. I don't remember where I got it from, but I
know it was a download from the internet. Using the XCom Hack v2.5, I viewed the alien in
the Alien Containment edit. I now have Type (race):____, and a Rank: Soldier for the
Floater Medic. It might just be corruption, but I do not have the resources to look into
it. [[User:Muton commander|Muton commander]] 19:24, 12 May 2008 (Pacific Time Zone)

I've never encountered it either. [[User:Magic9mushroom|Magic9mushroom]] 07:47, 23 July 2009 (EDT)

I think this only happens in the CE version. A disassembly of the code reveals that the stack to hold the matrix for what topics have not yet been researched is too short. It seems that those who ported the code from DOS doubled the local variable sizes blindly. There is already a problem that there are two-few bytes necessary for the entire alien organism section of the UFOpaedia, but double the expected size of the registers and it fills up quite easily unless a lot of autopsies and interrorgations have already been done. The only other situations that are handled by the same routine are the navigator revealing mission data or engineers revealing ship data, but there isn't enough topics in either section to overflow the stack variables. - [[User:Morgan525|Tycho]] 08:27, 22 June 2013 (EDT)

==Strength Overflow==

During one of my games with TFTD I noticed a really annoying thing happen during battles.
As my troops rose up the 'stat.' ladder they got better and better (as you'd expect), until they hit about 50 strentgh and completely lost the ability to throw anything.
Even trying to throw something tiny like a grenade or flare into the adjacent tile resulted in the 'Out of Range' message being displayed.

Anyone come across this before?
This was in TFTD CE.
[[User:Tifi|Tifi]] 07:55, 27 April 2008 (PDT)

:This is fairly well documented. The pathfinding algorithm for throwing objects will balk if anything is in the way of the throw and refuse to allow you to throw. What's happening is that your soldiers have become so strong that their throws are intercepting the 'ceiling' of the Battlescape(the top of L3), and as such the game thinks that the throw is blocked(because in order for the throw to complete, the object would have to be tossed up to the nonexistant L4). There's two ways around this:

:The Normal Way: Try shorter throws, throwing from lower heights, or throwing while kneeling. Beyond that, possibly get some new troops.

:The Sneaky Way: Manually edit the Strength scores of your soldiers in [[SOLDIER.DAT]] so that they're back to a usable strength level. If you set "Initial Strength" (offset 46 decimal or 2E hex) to 0 and "Strength Improvement" (offset 57 decimal or 39 hex) to a value of 50, you can permanently lock the soldiers at 50 strength. (You can lock them higher than that if you so choose, but not lower.

:Other than this, there's no workarounds I can think of offhand. [[User:Arrow Quivershaft|Arrow Quivershaft]] 08:10, 27 April 2008 (PDT)

:: There's normally no problem with the max level of 70 in open settings. However TFTD has a lot of low ceilings such as in the shipping lane missions and colonies, and the lower ceilings impairs your throwing quite a bit. In addition to shorter throws/kneeling, try moving out from under any overhangs if there is one just above you. - [[User:NKF|NKF]] 12:33, 27 April 2008 (PDT)

== Bug not listed: Sticking your head through the ceiling ==
This is something I just discovered: When you step on a small object inside of a building your soldier sticks his/her head through the ceiling and can see what's upstairs. You can even see the soldiers head coming out of the floor and that soldiers can shoot aliens upstairs. When I did this the alien I saw/shot was facing the other way, but I guess you could get shot if the alien was facing you. [[User:RedNifre|RedNifre]] 17:34, 11 May 2008 (PDT)

:That's not listed under "Bugs" because it's covered under "Exploits", right here: [[Exploiting_Collison_Detection#See_Through_A_Ceiling]] [[User:Arrow Quivershaft|Arrow Quivershaft]] 18:26, 11 May 2008 (PDT)

:: I don't know if it was ever covered anywhere, but there's this neat trick that might sound similar to the walk-through-'wall object'-wall trick except that it involves your unit climbing slopes. They'll appear as though they've gone up a level, but are actually not on that level. They only visually appear to be there, but are really still on the bottom level.

:: It happens a lot when walking up the desert or forest slopes. I think the trick involves standing on ground level, and then ordering the unit to 'move' into the hill rather than setting the waypoint while on level 1. The soldier will move up the slope and perhaps stop on the slope or even reach the top of the slope, but will still appear when you're only viewing the ground map layer. The soldier is really still on the ground level, but will have elevation offset.

:: One really interesting way of using this trick is in the mountain region. If you can find a cliff face and a low hill nearby, you can literally have your soldier scale the cliff by standing the soldier on the hill, and then walking towards the cliff. It's ridiculous, but your soldier never quite reaches the top of the cliff tiles, so ends up walking up a slope.

:: On a side note, standing at the top of the ramp of the Skyranger is the same as standing on ground level - you're only offset a bit. This means that smoke on level 1 and the sides of the Skyranger will not provide protection when you're at the top of the ramp.

:: On another related note in relation: In TFTD (doesn't happen a lot in UFO), you might find it difficult to toss grenades onto underwater slopes. To remedy this, raise the level up by one. It might look like you're tossing at air(and you are), but it'll get the grenade where you want it. Odd, but true. I must remember to put this in the grenade explanation section. -[[User:NKF|NKF]] 23:11, 11 May 2008 (PDT)

== Base Defence bug that causes a crash? ==

Does anyone know about a bug in a base defence mission that causes the game to crash? The game keeps crashing on the 4th or 5th alien turn.

:I've encountered that myself, but it should be noted that overall, X-COM is not the most stable game and is prone to crashing often at anytime. The differences between the hardware it was designed for and the hardware we're running it on cannot be helping matters at all; it's really a small miracle it even runs without an emulator in the first place(I've got games from 1999 that will bluescreen my machine instantly). As such, I'm not sure it's worth noting as a bug, since it's a 'game feature'(albeit a detrimental one). In any case, what're you doing letting the aliens attack you anyways? ;) [[User:Arrow Quivershaft|Arrow Quivershaft]] 21:33, 18 July 2008 (PDT)

:It sounds like an alien is in one of the outlying locations and attempting to destroy the top floor item. Possibly a radar or defense station. - [[User:Morgan525|Tycho]]

== Sources for a DOS4GW transplant ==

I was specifically thinking of the LucasArts Dark Forces demo, but I half-recall the actual source I used when testing that ~1999 was Id's DOOM. -- [[User:Zaimoni|Zaimoni]] 16:03, 7 August 2008 (CDT)

== Phantom Carried Casualty ==

You are carrying an unconscious soldier in one hand, and the soldier dies of his/her wounds. The dead soldier remains visible on the "left hand / right hand object" battlescape display, but is no longer visible in the inventory display. The problem can be fixed by moving another object into the same hand.

I've seen this bug with UFO Extender by [[User:Seb76|Seb76]] - possibly might be something to do with his manipulation of the inventory screen, rather than a general bug. I believe I've also seen this with other objects that were being carried in the hands, disappearing from the Inventory screen, but I'm not sure. I don't think it's an item limit bug, as XcomUtil shows 40 item slots free. [[User:Spike|Spike]] 08:58, 21 September 2008 (PDT)

:I think it has to do with the KO units KIA mod. Its doesn't take into account units held so when it tries to detemine where to place the corpse, there is no location. The routine doesn't undo the item-carried-sprite-ID byte for the holder. -[[User:Morgan525|Tycho]]

== Civilians As Enemies to MC'd Aliens ==

I ran across this issue a few times and just wondered if you guys experienced this. I MC'd a part of a Reaper (I always do the lower left for large aliens) on a Terror Site, then moved it a few squares. It suddenly stopped dead in it's tracks and then the alien spotted indicator increased by 1. When I clicked on the indicator to see where the enemy unit was, it brought me to L2 of the large apartment complex. However, nothing was there. When I sent a Flying-Suited soldier up there to peek in the window (eeek! A peeping tom!) he saw a female civilian standing there. This type of problem has happened numerous times to me so it's not a once-off thing. Maybe it's a LOS issue? Or maybe an alien indicator problem? Or a combination of the two? Don't know, but I'm curious if you guys have seen it. --[[User:Zombie|Zombie]] 23:40, 19 December 2008 (CST)

:There are a lot of major issues with MC'ing 4 square aliens. One of them being that you could accidentally MC an alien far off in the corner of the map, IIRC? Anyhow, maybe you should have tried MC'ing all 4 squares of the reaper and see if that changed things. -[[User:Jasonred|Jasonred]]

The long-range MC of other aliens when Mind-Controlling large aliens is only present in Terror From The Deep, due to a workaround to try and resolve the earlier bugs(and exploits) associated with controlling one square of a large unit at the time. In TFTD, successfully MC'ing part of a Large unit will also grant you control of the next three units in UNITPOS.DAT, in order. If you didn't MC the upper left portion of the large unit(the first UNITPOS entry for any large unit), you can potentially wind up in control of other aliens. So this doesn't apply to UFO. As for Zombie's issue, never seen it. And finally...Jasonred, on Talk pages, please indent your statement with colons so it differentiates from other people's comments, and sign your posts with 4 ~'s, like I will now do. [[User:Arrow Quivershaft|Arrow Quivershaft]] 10:42, 19 February 2009 (CST)

==Elerium Base Bug==

Jasonred: This bug has long since been known about. Elerium units on the Battlescape can be picked up by shooting away the power source; this one item counts as 50 units, and as such ANY elerium item spawned on any Battlescape counts as 50 Elerium. This issue with your own Elerium spawning as collectable loot in a Base Defense mission only occurs in older DOS versions, and is at the whim of the 80 item limit. [[User:Arrow Quivershaft|Arrow Quivershaft]] 21:55, 18 February 2009 (CST)

:Base defense does not seem to follow the 80 item limit in that DOS version. There are a lot of bugs that have long been known about. However this one was not included in the ufopedia for some reason.
:Also, the main thing about this bug is that it does not potentially double your elerium stores. It potentially multiplies them 50 times.
:... First time this happened to me, I was pretty flabbergasted. Here I was being conservative with my limited Elerium, refraining from blowing up UFOs when possible, when I perform a base defense and gain 3000 Elerium from it. Holy spit. -[[User:Jasonred|Jasonred]]

Alright, my error. Thanks for clarifying. [[User:Arrow Quivershaft|Arrow Quivershaft]] 10:42, 19 February 2009 (CST)

==HWP Fusion Bomb and SWS PWT Displacer Ammo Manufacturing Cost Bug==

At a cost of $15000, 400 Tech hours, 5 Zrbite, and 8 Aqua Plastics, this is the exact same cost as the HWP Fusion Bomb from X-COM EU, converted over to the equivalent TFTD resources. As such, it shouldn't be counted as a bug, since it is clearly what Mythos intended. [[User:Arrow Quivershaft|Arrow Quivershaft]] 09:55, 15 November 2008 (CST)

:Hmm, in that case maybe it should be treated as a generic game engine issue and not a TFTD specific issue - but I still think it's a design error. Can you think of any logical reason why the SWS/HWP version of the ammo should be more expensive (in cost and in materials) than both the craft ammo and the (more powerful) personal ammo? It makes no logical sense. Hence I think it's a design error. Nothing can be inferred from the fact it's unchanged from XCOM-EU, that doesn't imply any deliberate decision. It could just be the replication of an original error in XCOM-EU. [[User:Spike|Spike]] 11:17, 15 November 2008 (CST)

:: I can think of a logical reason to justify this: X-Com doesn't understand the technology as well as the aliens do (which is obvious, given the length of time each side has known the tech). Handheld Blaster/Blaster Bombs are just a copy of the alien design and therefor relatively cheap and efficient, but that can't be mounted on a turret. So X-Com has to make a new design, and they obviously didn't do that good a job as the aliens would have done. This explains Tank/Plasma being weaker than Heavy Plasma too. (Why is FBL Craft ammo cheaper than the tank ammo though? Maybe X-Com gave up on/simplified the guidance system and made it just a "dumb" cannon shell/torpedo instead which doesn't have multiple waypoints? Or maybe they just did a better job there?). [[User:Cesium|Cesium]] 04:07, 25 November 2009 (EST)

:Whilst we discuss it, I'll park my original text in here:

* ''Displacer/PWT ammo cost bug - at over $100,000 total cost per round, the ammunition for this SWS weapon is far more expensive to manufacture (both in money and rare materials) than the equivalent ammo for the Aquanaut-carried Disruptor Pulse Launcher, or the craft-based Pulse Wave Torpedo, despite being less powerful than either. This would seem to be a design mistake.''

See Also [[Talk:Displacer/PWT]]

:: I don't like the higher cost either, but I think it's a tradeoff of expense and quality for the convenience of portability. Sort of like an MP3 player to the gramophone... or maybe that's not a good comparison. -[[User:NKF|NKF]] 13:43, 15 November 2008 (CST)

A better comparison might be a desktop computer to a laptop. As a general rule, laptops are more expensive, but a similarly priced desktop gives you more power. Desktops are cheaper and offer power, laptops are more expensive and offer portability(though the gap is rapidly narrowing). [[User:Arrow Quivershaft|Arrow Quivershaft]] 13:49, 15 November 2008 (CST)

:I think those are good analogies. But they don't apply in this case. To continue your analogies: We are paying mainframe prices for a clunky desktop that has only laptop processing power, and we're buying a mainframe for desktop prices. The vehicle version ("desktop") - is ''less'' portable and ''less'' powerful than the personal version (DPL = "laptop"), ''less'' capable than the craft version ("mainframe") - and costs ''more'' than either of the others in total cash and in materials. In particular, it makes no sense that the small missiles on the SWS use up ''more'' of both Zrbite and Aqua Plastics than the Craft version. Do we really think it's logical that a tactical battlefield round, less powerful than its man-carried equivalent, takes more explosive and structural material to produce than both the more powerful man-carried version and also more than the air-to-air round that has 60km range and can take down a major alien combat craft? There is a clearly perverse bang-per-buck here, on every measure. My sincere belief is that this was an original mistake in the XCOM-EU engine that got copied into TFTD as well. The craft round should have the higher base price, but the material requirements that are currently assigned to the SWS/HWP round. It's debatable whether the SWS/HWP rounds should be more expensive than the man-carried rounds. But what I don't think is debatable is that is not logical for the SWS/HWP rounds to be more expensive than the craft rounds. It's clearly a mistake. Even in game balance terms, the only thing the HWP/SWS rounds have going for them is conserving "80-Item Limit" space, which I severely doubt was ever a game design consideration since it's just an awkward programming compromise. Any advantage inherent in the HWP/SWS is already reflected in the very high platform cost - there is no need to inflate the ammo costs as well. The bottom line is that a round for a (mini-)tank does not cost more, does not use more materials, than the same type of round for a long range anti-aircraft weapon that has much greater damage capacity and penetrating capacity. [[User:Spike|Spike]] 14:35, 15 November 2008 (CST)

I'm going to add this to the bug list now. [[User:Spike|Spike]] 16:06, 25 February 2009 (CST)

:Still don't think this is a bug though. Just because it's more expensive to manufacture than the hand-held or craft-mounted ammo, it doesn't mean the stats are wrong. Perhaps the programmers wanted to balance the tactical portion of the game a little more by making the ammo cost more for tanks. It doesn't have to be logical to be intended. Now if you had proof which said that the ammo was supposed to cost less but the stats were wrong, then yes, I'd agree. So if you boil it all down it comes to a disparate logic issue, not a bug.--[[User:Zombie|Zombie]] 21:31, 25 February 2009 (CST)

::I have to side with Zombie here. While the ammo may be disproportionately expensive, by the definition used on the rest of the page for bug, it doesn't fit. All the other bugs are errors in program logic or function or routines that are unintentional problems with the game, most of which are not warned of ahead of time. The ammo for the tank costs exactly what is listed and operates entirely as intended, whereas the rest of the bugs are not intended game features. Even if the numbers were entered wrong, that would be a data entry error, not a program bug. [[User:Arrow Quivershaft|Arrow Quivershaft]] 00:28, 26 February 2009 (CST)

:If it was a data entry error, I'd consider that a type of bug... assuming we had proof of the goof so to speak. LOL. --[[User:Zombie|Zombie]] 00:49, 26 February 2009 (CST)

:: It feels too specific an entry to be a data entry error.

:: I'm reminded of the high explosive. I know, I know - it's not an exact parallel to the FBL issue. A High Explosive is practically two grenades. Double weight, double bulk. Slightly above two times the damage. However, it costs five times the price of a standard grenade. Even though you're paying more for not-as-much, I don't think that could be considered a bug. A rip off, yes, but not a bug.

:: Here's a thought: Think about the immediate benefits each of the two controversial ammo types give back to you. Aircraft ammo = activity points. Tank ammo = loot. Yes, I know that aircraft ammo also generate crash sites, but you still have the ground combat to contend with.

:: One other thought: With careful management of your ammo, you'll probably never spend any elerium on the handheld version's ammo. Could it be the handheld that's really at issue here rather than the others? In the end I feel that it doesn't really matter. -[[User:NKF|NKF]] 03:38, 26 February 2009 (CST)

: I'm with Zombie that a data entry error is a bug (we have other examples), but also agree some proof is probably needed. And I agree with NKF that in the scheme of things, it doesn't really matter much. I don't think the HE pack is a good comparison (though the HE pack should be heavier) as it's reasonable to pay disprortionately more to get additional power at the same tech level. The fusion weapons are a case of paying more to actually get ''less'' power. I am not bothered by the handheld vs vehicle balance, not least because the game generally makes handheld weapons better than their vehicle equivalents, so I can accept that as an across-the-board design decision.

: I can also see a game balance argument ''if'' we believe that Fusion Tank ammo is more of an overall game-winning weapon than craft Fusion Bombs. But I'm not sure I agree with that statement. And even if it's true, and there's a game balance argument (in which case it would apply equally to handheld Fusion launchers), it's still illogical. The less powerful, battlefield warhead should not cost massively more in exotic materials than the much more powerful air to air warhead that brings down Battleships. I agree though that just because it's illogical does not prove it's a bug (i.e. unintended). [[User:Spike|Spike]] 07:48, 26 February 2009 (CST)

Ok we more or less seem to be in agreement that this isn't a bug, but it is very confusing/illogical. Maybe we can shift the "bug" text from the article page and roll that into the [[Hovertank/Launcher]] and [[Displacer /P. W. T.]] pages now. Feel free to combine any text from the discussion above if necessary. --[[User:Zombie|Zombie]] 09:22, 26 February 2009 (CST)

: Unless we can ''prove'' it's a data entry error (unlikely), how about calling it an "Anomaly" instead of a bug? [[User:Spike|Spike]] 10:59, 26 February 2009 (CST)

Looks like plain old game imbalance to me.
The way I see it, Hovertank Plasma and Launcher were meant to be stronger. Much much stronger. Let's look at Tank Cannon, Launcher and Laser. The logic is that it's a tank mounted weapon, so the tank can carry a much larger and more powerful version of the same weapon, right?
It's pretty stupid that a Hovertank Plasma is weaker than the Heavy Plasma... you could just mount a Heavy Plasma on a Hovertank and get them exactly equal. In fact, I suspect that the hovertanks were ALSO meant to have more powerful weapons than the man-portable versions.
Unfortunatly, the game designers then realised that this made the hovertanks far too powerful. So... the programmers nerfed the power of the hovertank weapons. BUT they forgot to lower the ammo costs. [[User:Jasonred|Jasonred]] [[User:Jasonred|Jasonred]] 11:20, 26 February 2009 (CST)

: Well you are opening up a much larger issue there. The Fusion weapons are an anomaly, an inconsistency. But handheld weapons are more powerful than equivalent vehicle weapons across the board, consistently. So that looks like a deliberate design decision, not a mistake. [[User:Spike|Spike]] 17:33, 26 February 2009 (CST)

:: There are two exceptions to the rule: Tank/Cannon: 60AP vs. Heavy Cannon 56AP. Tank/Laser: 110 Laser vs. Heavy Laser: 85 Laser. The hovertank\plasma only differs by a measly 5 (an extra 0 - 10 damage, which means a lot vs. UFO inner hull armour). I guess the trend here was to moderate the area effect tank strengths. -[[User:NKF|NKF]] 23:22, 26 February 2009 (CST)

I'd have to agree with you there Spike. This wasn't a mistake, however odd it may seem. It was a deliberate attempt to try and balance the game. Below is a table I created ages ago for my (now defunct) strategy guide detailing the HWP's and what handheld weapon corresponds to it. When you stick them side-by-side, it really becomes apparent that the programmers were trying to base the HWP weapons off the handheld weapons somewhat. The only thing that doesn't follow a nice and distinct scheme is the damage. That's what is the clincher. --[[User:Zombie|Zombie]] 20:26, 26 February 2009 (CST)
 
<table {{StdCenterTable}} class="sortable">
<tr {{StdDescTable_Heading}}><th align="left" width="150">Tank Type</th><th width="70">DAM</th><th width="80">Snap</th><th width="90">Aimed</th><th width="90">Aimed</th><th width="80">Snap</th><th width="70">DAM</th><th align="right" width="140">Handheld</th></tr>
<tr><th align="left">Tank/Cannon</th><td>60</td><td>60%</td><td>90%</td><td>90%</td><td>60%</td><td>561</td><th align="right">Heavy Cannon</th></tr>
<tr><th align="left">Rocket Launcher</th><td>85</td><td>55%</td><td>115%</td><td>115%</td><td>55%</td><td>87.52</td><th align="right">Rocket Launcher</th></tr>
<tr><th align="left">Laser Cannon</th><td>110</td><td>50%</td><td>85%</td><td>84%</td><td>50%</td><td>85</td><th align="right">Heavy Laser</th></tr>
<tr><th align="left">Hovertank/Plasma</th><td>110</td><td>85%</td><td>100%</td><td>100%</td><td>86%</td><td>80</td><th align="right">Plasma Rifle</th></tr>
<tr><th align="left">Hovertank/Launch</th><td>140</td><td>--%</td><td>120%</td><td>120%</td><td>--%</td><td>200</td><th align="right">Blaster Launcher</th></tr>
</table>
1AP rounds. 
2Average between the Small and Large Rocket.

: Hold up! Tank rounds do 60AP. -[[User:NKF|NKF]] 23:22, 26 February 2009 (CST)

So what's wrong? The table says 60 for the Tank/Cannon and 56 for HC-AP. Those are correct, no? --[[User:Zombie|Zombie]] 23:41, 26 February 2009 (CST)

: Sorry, didn't realise it was two tables side by side (or rather mirrored). Eyes only noticed the left side of the table. -[[User:NKF|NKF]] 23:53, 26 February 2009 (CST)

:: If the Hovertank Launcher did 200 damage, or worse if the Hovertank Launcher did EVEN MORE damage than the Blaster Launcher... that would make them easily the most deadly things on the map. As it is, the hovertank launcher is already pretty overpowered, even with 140 power.

I might be six years late here, but I think there could be an explanation for this in RL physics — indeed, in RL nuclear weapons programs. Incoming wall of text.

There are two sorts of nuclear reactions that produce energy: fission of large nuclei, and fusion of small nuclei. Fission can occur under normal temperatures and pressures, but involves a neutron chain reaction. As such, fission devices have to have a certain mass of fissionable material (the ''critical mass'') so that the neutrons stay in the material and cause more fission rather than escaping; this means that such devices cannot be scaled down below about suitcase or large backpack size (not all of this is actually nuclear material; rather, most of it is conventional explosives used to rapidly assemble the supercritical mass from subcritical masses). They also produce large quantities of radioactive fallout, which is problematic. Fusion, on the other hand, requires extreme temperatures and pressures, but does not necessarily require a neutron chain reaction. This means that they can theoretically be scaled down to much smaller sizes... except that the only available compact source (ie, not building-sized) of those extreme temperatures and pressures is the detonation of a fission bomb. Thus, all known fusion weapons currently in existence involve a relatively-small fission stage that detonates a much more powerful fusion stage.

The "Holy Grail" of nuclear weapons research is what's called a [[wikipedia:Pure fusion weapon|pure-fusion weapon]]. Because it has no fission stage, a pure-fusion weapon would release little fallout (note here that fallout is material that emits radiation long '''after''' the detonation; a pure-fusion weapon would emit copious amounts of deadly neutron radiation when actually used, but that would dissipate within seconds) and could be scaled down to grenade-launcher size (though it would obviously be far more powerful than a conventional grenade). They would be far easier to produce, as well; producing weapons-grade uranium and plutonium requires large and powerful isotopic separation equipment and/or a full-sized nuclear reactor, whereas deuterium can be extracted from water with trivial ease and lithium and tritium are relatively simple to obtain and make respectively. The main issue is that while the pressures required to confine the fusion material during the reaction are achievable with chemical explosives, the temperatures necessary for fusion are emphatically not. You need a stronger initiator; some material with a higher energy density even than plutonium. In RL the only initiator strong enough is antimatter — hard to produce and contain, to say the least — but the aliens in X-Com have a source that's stored far more easily... Elerium.

I posit that the "fusion" line of weapons in X-Com are exactly what they're named: tactical fusion bombs, made possible by an Elerium detonator. (A more controlled reaction on those lines — a fusion reactor with Elerium-spiked fuel — in UFO Power Sources would also explain the discrepancy between the calculations based on fuel efficiency and the lack of city-killer blasts when a Power Source's Elerium cooks off.)

Given the assumption that "fusion" weapons are indeed fusion weapons, with Elerium serving only as a detonator, the oddly high Elerium cost of the Hovertank/Launcher's ammunition is finally explainable. The HWP Fusion Bombs are, literally, smaller than Blaster Bombs and craft Fusion Balls (presumably because of size constraints in the launching mechanism in tanks). Having less explosives to compress the fuel means you need an even higher temperature to compensate — thus, more Elerium detonator — but because the actual power of the bomb is mostly from fusion and not Elerium decomposition, the yield is still lower.

I intend to remove this from the list of Known Bugs on this basis if nobody can find a hole in my logic. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 02:03, 17 April 2015 (EDT)

:I'll have to disagree. Your argument while interesting, is just supposition and an attempt to give validation by taking ideas (that the developers probably never considered) to justify a flaw, very much in the same manner as those who try to explain why UFOs do not respond in interceptions. In truth, like many of the other bugs listed here, they are the result of issues caused by the time constraints the Gallops where under. Much of the production/buying/selling aspects of the game have game balance issues and don't make sense when cross referenced to other similar elements in the game and/or their overall effect to either combat or the strategy layer, especially in regards to the game's economics. [[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]]) 05:06, 17 April 2015 (EDT)

::Why would they match up in terminology with the actual use to which any military would put Elerium by accident? Because, no shit, if a military got their hands on a substance with Elerium's properties this is literally exactly what they'd do (at least as far as explosives go). I can cite a paper talking about the superiority of antimatter-fusion weapons to pure antimatter weapons if you want; the title is "Fourth Generation Nuclear Weapons: Military effectiveness and collateral effects". [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 05:21, 17 April 2015 (EDT)

:quote all the sources you like, it still doesn't explain the waste in the manufacture process. With elerium being such a "scarce" resource, there is no logic in producing something that require more elerium and delivers less of a battlefield effect. It would be more logical and efficient to have had the platform fire regular blaster bombs, since they only require 3 elerium not 5.[[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])
::IMHO, any logic argument can be presented to why those HWP Elerium Bombs should cost less/more or be more efficient. That is not the point here. A bug is when a game feature is working improperly or/and is causing technical issues, either due to limitations, insufficient testing, whatever. Design choices are a completely different matter: the Heavy Laser is a nearly useless weapon due to its stats but no one ever considers it to be bugged due to its stats. It was a choice, that was slightly changed on TFTD with the Heavy Gauss. To consider the stats of the HWP Fusion a bug then you'd have to label a lot of choices as bugs when they are simply design choices. You may not agree with them but that doesn't make them bugs in the generally accepted definition of the term. And quoting Arrow Quivershaft on the top comment of this discussion: "At a cost of $15000, 400 Tech hours, 5 Zrbite, and 8 Aqua Plastics, this is the exact same cost as the HWP Fusion Bomb from X-COM EU, converted over to the equivalent TFTD resources. As such, it shouldn't be counted as a bug, since it is clearly what Mythos intended"[[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 19:35, 25 April 2015 (EDT)
::Also, the consensus until now expressed by several people that previously discussed this is that this is not a bug. The main supporter of the bug argument seems to be Spike at the beginning but during the discussion but halfway the discussion he says: "I agree though that just because it's illogical does not prove it's a bug (i.e. unintended)" [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 20:54, 25 April 2015 (EDT)
You don't get to claim benefit of the doubt here, Tycho. All game features are assumed to not be bugs unless there is compelling evidence presented otherwise. You claim this is a bug based on the suppositional logic that more powerful weapons should cost more and almost nothing else. The price wasn't altered (and neither was the power) in TFTD, so there's no evidence of mistake there (as an aside, the Displacer/Sonic having its power listed as 130 when it's 110 in the game engine clearly ''is'' a bug). The only bit you might be able to interpret that way would be the description of the Hovertank/Launcher's weapon as causing "immense devastation" compared to the description of the Blaster Bomb as "highly powerful" (the potential implication being that the HWP Fusion Bomb is stronger), but that's iffy at best since there's hardly a graded table of adjectives in use and on those very same pages in the UFOpaedia it lists the damage of each weapon as what it actually is.

The claim that it's a bug is based entirely on theorising about yields. I've given alternate theorising that would explain the yields (and I already explained that the semi-automatic nature of the Hovertank/Launcher and physical space for its high ammo could justify the need for a smaller round), which undercuts that claim. We can't know who's right, but the assumption should always be that the designers knew what they were doing; to assume until proven otherwise that they had no clue is extreme hubris and contempt. Moreover, you are in a minority of one or perhaps of two against a majority of several. Your claim to representing consensus is blatantly false.

Now, I'm going to wait a couple more days to see if anyone comes forward with anything substantive, as I waited a week after my reply to your original non-refutatory dismissal, and then reinstate the removal if nobody puts forward a cogent objection. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 22:57, 25 April 2015 (EDT)
:Now that I think of it, though, an "oddities" page where we talk about this, the shitty Heavy Laser/Heavy Gauss, the No More Soldiers limit, and other not-bug things might be in order. It would help to make this page about actual bugs and not about weirdness that is nevertheless clearly as intended. Thoughts? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 23:04, 25 April 2015 (EDT)

:At the time, I didn't continue the argument as my point was that removing something based on one person's belief, no matter how cleverly thought out, wasn't good enough to warrant removing from the list. (I would have pointed out all the different theories on UFO interception AI, but I see that has already been removed.) I hadn't read all the discussions because I assumed that no consensus had been reached, similar to the Interception AI discussion. Mushroom, could have just pointed out that this issue was already settled years ago but no one bothered to removed it from the list, instead of resurrecting a "dead" discussion as though it had not been settled and just stated that the developers intended to discourage the use of this HWP by making the cost of its ammo high. I still don't agree that the HWP ammo is more efficient and thus justification for its production cost, especially since the developers would have never needed this level of justification or would have had the time to devote to so small an aspect of the game.

:I definitely agree that this page needs to be updated. Another reason I argued so strongly is because so many topics on this page do not fall into the category of bug as has been defined. I thought this page was also devoted to listing all the illogical aspects of the game due to the lack of enforcement on the definition. [[User:Morgan525|Tycho]] ([[User talk:Morgan525|talk]])

::If I only had a dime for each time someone proposes to change something on this wiki, everyone agrees, and then nobody ends up taking action... :) It's always better to take initiative and edit things. I agree also with an update to this page, and separating bugs from limitations. But definitely no more 'this should have been done this way' arguments to present design decisions as 'bugs' [[User:Hobbes|Hobbes]] ([[User talk:Hobbes|talk]]) 17:43, 26 April 2015 (EDT)

:Okay. I'm planning to rip out the following and stick them on a separate page:

:Great Circle "bug" (this isn't really a "bug" so much as unoptimised code)
:Side-on Intercept "bug" (ditto, but given UFOs' tendency to alter course suddenly it's not even particularly unoptimised)
:Head-on Intercept "bug" (come on, this is just bitching)
:Instant Getaway "bug" (more an anomaly than a bug)
:80-item limit (intentional and the rationale is obvious to boot)
:Purchase limit (working as intended)
:Soldier recruiting limit (being charged for attempting to buy more is a bug, but the limit itself isn't)
:Soldier battlescape limit (there's a consequence of this which is a bug, the CtD with 10+ tanks, but not the limit itself)
:Manufacturing Completion Time Display "bug" (you can look at it and see what time it finishes, and it goes down at the right rate; it may seem a little unintuitive but it isn't "wrong")
:Manufacturing Rate Interruption Loss "bug" (more bitching)
:Manufacturing Rate limit (working as intended; the attempt to get around it in TFTD is bugged, but the EU behaviour isn't)
:HWP Fusion Bomb Ammo Cost "bug" (we're in agreement here it seems)

:There's plenty that need a tidyup on top of that but as far as the page split itself goes, are we agreed? Also, I'm thinking of calling the page "Anomalies and Game Limits", opinions? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 01:58, 3 May 2015 (EDT)

== DOS4GW - What the heck is it? ==

It's been ages since I had to remember this stuff, so those who remember clearer than I do, forgive me if my descriptions aren't accurate. Hopefully the general idea will come across.

Back in ye olde days of computere gamynge - and where there were more E's to go around, memory handling was a tricky beast to handle. Computer memory is divided into several different categories. Conventional, extended and I think expanded. I might be jumbling the terminologies for the last two a bit. Doesn't matter - memory was just cut up into small segments. The two most common memory types to PCs at the time were pretty small but were readily available. The third one - the most expandable (aka the chip with its massive 4 Megs of RAM you just spent your whole month's allowance on!), wasn't as easy to get at.

To get access to the higher memory that was available to the computer, special memory handlers had to be used. Drivers like HIMEM, emm386, etc were used.

DOS4GW is one such handler that lets the game access the computer's available expanded memory. Lots of games that came out at the time use this. Doom, Duke Nukem 3d, Syndicate, Ultima Underworld, X-Com UFO/TFTD, etc. LOTS of games. Any time you ran a game from the dos console and you saw the Dos4GW message flash by briefly it would be assisted by it (well, it stayed on the screen for ages back when processors were slower!).

It took the hassle out of memory handling and let the game access the available memory on the computer as one big flat block of memory to play with.

So what was meant in the article was to simply replace the dos4gw.exe with a more up-to-date version from another game. I think the way to tell its version was just in the message that it displayed. You can just run the dos4gw.exe file in a console window. It'll give an error, but the message it shows will indicate its version. UFO 1.4 uses Dos4gw 1.95, for example.

-[[User:NKF|NKF]] 01:22, 6 March 2009 (CST)
:DOS4GW also switched the processor from 16bit to 32bit mode. [[User:Seb76|Seb76]] 13:58, 6 March 2009 (CST)

== Clipping ==
I have a new bug. Its harmless. I have a savegame (EU CE - modified game) which has a sectoid within another sectoid. In the alien turn, one secturd walked off the roof and dropped down <s>onto</s> into another. (I guess there DNA is indentical afterall, so they 'become one' with the world). If you want the savegame (superhuman edited using UFOloader, UFO Mod v1, xcomed, Khor Chin WeapEdit v0.1) drop me a request on the my page somewhere. [[User:EsTeR|EsTeR]] 01:40, 18 September 2009 (EDT)

: Not something many would encounter, but definitely something that can happen. Units can occupy the same physical space, but the game cannot display them all. It'll only draw one of them. Actually saw this effect happen back in the early days of XComutil when it gained the ability to manually add new aliens into a battlescape. It did this by slotting them into the same spaces occupied by existing aliens. Then the fun would happen when you saw a couple of Mutons suddenly walk out of a sectoid. Not sure how the game determines who gets hurt when struck by a bullet. May very well depend on the order they are stored in the unitpos.dat file.

: There are a couple of ways you can replicate this in-game, but I can only provide theories on how you could do it. Such as shooting the ceiling above you and letting the unit drop through, or moving a tank off a ledge and getting its non-primary segments land directly on top of another unit. By the way, the rear end of tanks get stuck in walls if you attempt to move north or east off any ledges. -[[User:NKF|NKF]] 02:18, 18 September 2009 (EDT)

: Ok, so as long as others know about this, then all is good. I had never seen it and was doing alot of head scratching until I shot the alien.

== Berserk HWP crashes the game ==
In the article page it mentions that aliens which go berserk with their integrated weapons will crash the game. This is only true for Mind Controlled aliens (or units under X-COM control) - alien controlled units which go berserk do not crash the game. I tested an MC'd Celatid just now and it doesn't crash the game either, though it doesn't immediately go berserk - it waits another turn for some odd reason. Someone want to check this to verify my results? --[[User:Zombie|Zombie]] 20:31, 27 December 2009 (EST)

==HWP Morale Loss==

HWPs have 110 Bravery, which [[Morale#Effect_of_Bravery|normally prevents morale loss]], but I wonder if they can still lose morale due to loss of units with a morale-loss modifier. It'd depend on how the math is done. If, for, example, the -20 to morale for a dead unit is static, then multiplied by any [[Morale#Officers|morale loss modifier]], then reduced by 2 for every ten point of bravery, any officer death without another officer on the field will necessarily reduce HWP Morale.

It all depends on how the equation plays out and when modifiers are added. For sake of this post, I propose the following as the morale-loss equation: 20*(rank death modifier)-((Bravery-10)/5)*(1.00-Leadership bonus)=Morale Lost. (Rather than using 22 as a base, I'm going to assume Bravery is internally decremented by 10 for this equation as 0 Bravery is impossible without editing and it makes the math easier for the purpose of the example.)

It makes sense to me that rather than having 110 bravery hard-coded as an exception to "No morale lost", it simply works the same way in the normal equation, but is high enough that it negates most morale loss events, as even if an officer is killed, another officer is usually left on the field to help negate the penalty. That said, if a large portion of the team is wiped out at once, any surviving officers may not be able to negate it all, allowing tanks to start having noticeable morale loss.

So with the death multipliers, we can determine that every XCOM officer killed has a set death value. Rookies and Squaddies are -20, Sergeants are -24, Captains are -26, Colonels -30, and Commanders -35.

For example, under this theory, if a Sergeant is killed with no other ranked units on the field, a Squaddie with 50 Bravery would lose 16 Morale. (20*1.2-(50-10)/5*1.00=16). A HWP would, at the same time, lose 4 morale. The Sergeant's death is worth -24 Morale, and without another officer on the field to ameliorate the loss, the Tank's bravery only can 'absorb' 20 points of the morale lost. If it was instead the Commander lost, with no other officers on the field, the HWP would lose instead 15 points of morale, given that a Commander's death (20*1.75) is worth a whopping 35 points of morale loss if no other officers are present.

And if you have, say, four colonels and the Commander on rear/psi duty, and some alien flings a grenade or a blaster bomb into the back of the Skyranger and blows all three of them up and they were the only officers, the HWP has now lost 55 morale, which gives it a 10% chance of panicking/berserking on the next turn!

In the end this'll probably need to be tested for accuracy, but those are my thoughts right now.

Also, for the record, most units that berserk go to 255 TUs while still using the original TU-expenditure calculations; it's part of what makes berserk units so dangerous. [[User:Arrow Quivershaft|Arrow Quivershaft]] 19:34, 11 January 2012 (EST)

:Tested it under vanilla CE. Took a squad out containing just about every rank there is (commander + colonel + captions + sergeants), plus a tank. Blew up and killed all soldiers with a single blaster bomb shell, leaving just the tank, which lost no morale (sorry).

:I also brought a group of rookies along with a single commander + tank, and killed just the ranked unit. Tank lost no morale. A rookie with 60 bravery lost 17 (which matches the loss predicted by the formula currently on the morale page), whereas under your formula he should've lost 25.

:Still, you're on the right track. I've long had my own theory as to why tanks have been known to lose morale. Take a look at [[UNITREF.DAT#42|UNITREF.DAT[42]]] - this is the offset that stores a unit's rank. Notice something? The value gets higher as the X-COM unit's rank gets higher. Works in ''reverse'' for aliens, for whatever reason. I sorta figure it's so killing a mind controlled alien commander doesn't mess with your morale too badly, but there's a big problem with that theory and you can probably tell what it is...

:If the highest this figure gets for an X-COM unit is 5 (commander rank), then a killing a mind controlled alien ''terrorist'' with a rank value of ''7'' should net an even higher morale loss penalty. And indeed it does - I took a rookie and a tank to a terror mission, mind controlled and killed a terrorist, and the tank lost 10 morale. Guess it would've lost six if I'd taken a commander instead of a rookie, but that's still something.

:Note that the formula on the morale page does ''not'' account for this - it states that at bravery 110 the alien's death loss multiplier would always be applied to a base morale loss of 0, but that's obviously wrong. You're spot on in saying that the base morale loss figures are not totally dependant on bravery, and the "death loss" penalty is applied first. Would probably require a few more trials to determine what that penalty ''is'' for alien soldiers and terrorists though.

:Just for kicks, I edited a plasma tank to have 0 morale. It panicked in the normal way (either sitting still or charging off to the SE). When it berserked, the game crashed as soon as I dismissed the status message. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 18:54, 12 January 2012 (EST)

:: Thought I'd give it a spin. I sent a laser tank in with a squad and had it start shooting at team members. Each time it killed an ally, it would lose morale. Once it was under 50 morale, I waited until it panicked. Since I was playing the dos version, the game didn't crash but I suspect a memory leak of some sort may have occurred that would normally shut down the CE version. What would happen in CE if a soldier were to be edited and granted a tank turret, and then made to panic? Would the game crash? I'm just wondering if it's related to the weapon as opposed to the fact the tank is a treated as a large unit. -[[User:NKF|NKF]] 00:43, 13 January 2012 (EST)

::: Ah, friendly fire! Thought I'd tested for that, but obviously not...

::: Oddly enough, now that I try it, I see that the twenty point hit for killing a unit on the same side can be adjusted by the leadership bonus of the victim. Eg, kill a lone commander and his 35% penalty reduction takes the extra morale lost from 20 down to 13 (which is exactly how much a tank will lose, given that it otherwise wouldn't lose any at all).

::: Of course, this completely messes up my theory about alien soldier/terrorist ranks overriding the 110 bravery score. It doesn't. My tank "only" lost 10 morale because the alien's rank acted as a 50% leadership bonus... Though I suppose that's still interesting to know, because it suggests that keeping a simple alien soldier under mind control is more effective then risking your own commander in the field.

::: I took an otherwise unarmed rookie and assigned him a tank cannon + ammo. He could manually fire this weapon in much the same way a tank can. Forcing him to berserk crashed CE, under DOS he just spun around. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 21:20, 13 January 2012 (EST)

== 80-items limit on CE edition ==

I have the feeling that the 80-items limit does not apply to the CE edition and is instead a 110-items limit (at least during base defence). Can anyone confirm? [[User:Seb76|Seb76]] 16:24, 24 February 2010 (EST)

:I believe this limit was increased for TFTD. Maybe it was also increased for the CE edition of UFO, and only ever applied to the DOS edition of UFO?? [[User:Spike|Spike]] 20:03, 11 March 2010 (EST)

== Paying for Dirt in TFTD ==

I have the steam version of TFTD and am unable to replicate this bug. Testing with the starting base, I dismantled a few modules, added up my income and expenses, and it reconciled with my cash at the beginning of the next month. I even tried again, dismantling every module except the access lift, and once again saw no income discrepancy. Am I missing something, or is it possible this bug was actually fixed in TFTD? --[[User:Jewcifer|Jewcifer]] 12:18, 16 March 2012 (EDT)

:'twas probably fixed. It would indeed be helpful to add a small note to bugs on this page which are EU-specific but not obviously so (like this one). -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 17:14, 16 March 2012 (EDT)

::Every now and then I get the urge to test some of the more important bugs myself in my steam version of TFTD. Perhaps I will make a more complete effort and record the results somewhere on the wiki. --[[User:Jewcifer|Jewcifer]] 12:08, 21 March 2012 (EDT)

== Paying for dirt: Source of bug discovered! ==

Well, I never have read this anywhere (which kind of strikes me as odd, thinking of how obvious this one seemed to me... And i have NO programming background whatsoever), so I'll post it here, hoping that there are still some active members willing to try and verify my findings. If so, please comment here, because then I will inform bladefirelight to include this in any upcoming xcomutil release. If it had been discovered before, well then I just wasted some time here. Comment below, I will delete this entry.

As the main bug page mentions, when dismantling a facility still under construction the premium will only be paid once it would have been finished. This suggests some connection between paying the premium and building time. Looking into the infos here: [[BASE.DAT]], I quickly discovered what the problem was: When a facility is dismantled, the Bytes related to the location of base facilities are updated correctly. HOWEVER the game omits to update build time to FF (which is "will never finish", an entry only found on unused squares). If the facility is finished when it is dismantled (or destroyed during combat), then the 00 in the build time byte will stand. If it was under construction, the value indicating the remainig build time will continue to tick down towards 00 as if the facility was still there.

Now at the end of the month the following seems to happen: The game checks for ANY 00 entry in the build time bytes, and if there are 00 entries, it will look up in the location bytes the type of structure to determine the amount of maintenance for that 00-construction-time-square. When it finds "dirt", then it will charge the 80 grand (my guess would be that those are somewhere hard-coded).

This explains all phenomena related to this bug, like a dismantled hangar costing 320.000 grand or the premium only popping up after the build time of a dismantled facility that was under construction has expired.

Now the fix is pretty easy: Open the BASE.DAT in a hex-editor and change the bytes in question to FF!

== Minimized Interceptor Bug (Ufo CE) ==

Maybe this bug is not just related to saving, because I had a similar problem last night. The game didn't crash, but it kept restarting the same Battlescape mission.
One Avenger (A-3) was pacing a Battleship, while another Avenger (A-1) was sent to pick up the pieces of a Terror Ship that had been shot down by an Interceptor. Despite having no weapons (oversight on my part), A-3 wanted to attack the Battleship, but I minimized the screen, hoping it would land.
While the screen was minimized, A-1 landed at the Crash Site from the Terror Ship and started this mission. Right after finishing it, I got the message that A-3 was ready to land next to the Battleship. Happy that I'd get the loot, I started the mission.
After cleaning it out, I got the usual Loot and Promotion screens and went back to the Geoscape. A few seconds later, I was back in the equipment screen and the Battleship Mission started again. I played it once more, because - hey - additional loot, right? Err... no. At the end, I got the correct Loot screen for this attempt and the very same promotion I had gotten in the first attempt (A Rookie from another base promoted to Sergeant).
Got back to Geoscape and a few seconds later back to the Equipment screen. I aborted this mission (same Battleship again), got back to Geoscape and - you guessed it - back to the Equipment screen. After aborting this mission as well and getting back to Geoscape, I used the few seconds I had to go to 'Options' and 'Abort Game'. Maybe I could have made A-3 disengage from the Battleship since I think I saw them both on the Geoscape, a yellow diamond and a red plus, but it was pretty late by that time.
--[[User:Matzebrei|Matzebrei]] 15:06, 15 May 2012 (EDT)

This is a known bug. There is a work around. You should patrol the ship with troops and not land... Finish shooting down the other airborne ships first. Then when the ships doing the shooting are returning to base, change patrolling ship with troops to advance to downed ship in order to commence ground combat mission.
--[[User:JGF|JGF]] ([[User talk:JGF|talk]]) 07:55, 9 November 2016 (UTC)

== Activity Overflow Bug ==

This is a potentially campaign-ending bug. This was seen in the Steam distribution, DOS version (on Windows 2003 Server EE). Not sure if UFO Extender was being used - probably it was. End of Jan 1999 turn shows an extreme negative/underflow Monthly Rating score, which in turn is caused by extreme overflow of UFO Activity levels. Note that that funding "score" - the increased funding by countries - was very positive at the same time!:

[[File:dissatisfied customers.png]]

UFO Activity, by Areas and by Countries, is literally off the chart. Clearly some kind of integer overflow:

[[File:ufo-areas.png]]
[[File:ufo-countries.png]]

X-Com activity is also off the chart:

[[File:xcom-areas.png]]
[[File:xcom-countries.png]]

In addition to the likely outcome that I will lose the game in Feb 1999, it means I can't use the graphs to detect UFO activity outside of my radar coverage.

I have only seen this bug once, and (probably very unusually) I am running under Windows 2003 Server EE (!!). My hunch would be that's the cause, Windows 2003 Server is not the best games platform. :)

[[User:Spike|Spike]] 07:22, 3 September 2012 (EDT)

Further information:

I don't necessarily lose the game in Feb or March 1999. The Monthly Ratings from Feb onward are just based on the current month, not historical score to-date. However it still greatly increases the risk of suffering from the [[Known_Bugs#Losing_My_Favourite_Game|Losing My Favourite Game]] bug - which also greatly complicates doing too many controlled experiments on this Activity Overflow bug, because a few restores of the saved game quickly leads to X-Com Project termination (and humanity's doom).

Possibly the Activity Overflow bug is caused by an initial value of the score (or an array of score values) not being correctly zeroed at the start of the game. See this graph, which shows a negative score in May 1998, prior to the start of the game in Jan 1999.

[[File:Prehistoric_negative_score.png]]

[[User:Spike|Spike]] 08:48, 3 September 2012 (EDT)

I encountered the same Activity Overflow Bug in Windows 7 using Steam version, Windows option with UFOExtender latest version.

[[User:Humbe|humbe]] 2012.10.04 09:05 UTC

I encountered the same bug at end of january with latest xcomutil patched CE version (with only bug fixes patched) with ufo extender newest version running (close to default options). Got many saves from that first month. Even if loading very early save where I had done no missions yet, and just did stuff in base, graphs still show negative for various periods in 1998. Sounds more like corruption than something actually overflowing to me.

[[User:Archlight|Archlight]] 18:34, 24 September 2012 (EDT)

== Bad Paths Bug ==

I suggest to add bad paths on UFOs maps to the article, as another bug in the game.

[[User:Sherlock|Sherlock]] 09:25, 26 December 2012 (EST)
:That sounds reasonable to me. [[User:Spike|Spike]] 10:03, 26 December 2012 (EST)

==Expenditure Graph==
The economy graph for "Expenditure" neglects funds spent on new facilities. I noticed this in my current (DOS) game when I built eight Psi-Labs at the start of April and it didn't increase. I know it counts everything on the Purchase screen; I'm not yet sure whether it counts manufacturing costs.

Is this enough of a bug to be mentioned? Can anyone confirm whether or not it occurs in CE, and whether it counts manufacturing costs? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 02:40, 17 May 2016 (UTC)

==Workshop Crowding==
It seems there is a bug whereby you can allocate more projects/engineers than available workshop space. This can be triggered by setting up two concurrent manufacturing jobs, setting one of them to have 0 engineers working on it, then set the other to have as many engineers as you can assign to it, filling the workshop space. Then go to the other job with 0 engineers, and it will show a negative workshop space available, now if you assign at least one engineer to this project, you can assign the rest of your engineers however you please.

This is my first edit. I find it hard to believe I'd be the first to find this bug after so many years, can someone please confirm a reproduction and that it isn't documented somewhere I've missed? I am running the DOS version of UFO, but I'm also running XComUtil, not sure if that has an impact, or what patch level I'm on. - [[User:Uncertainty|Uncertainty]] 11:00, 20 Dec 2016 (AEDT) Update: Cannot reproduce on the CE version, still unsure of the patch level of the DOS version I'm running and don't know how to accurately determine that. - [[User:Uncertainty|Uncertainty]] 22:00, 29 Dec 2016 (AEDT)

: An easy way to check is whether you can research Magnetic Navigation after collecting one from an alien sub, or if you have to research a Lobsterman Navigator beforehand. If you can research it right away then you have v2, which is what the CE version is mostly based on. If you can't research it and must get the navigator, then it's the unpatched copy of the game. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 22:24, 29 December 2016 (UTC)

Update 2: Thanks NKF, I'm not running TFTD, but I figured out that I was running v1.2 of XCOM1. I cannot reproduce the bug on v1.4 so the bug only applies to v1.2 and has been patched in newer versions. - [[User:Uncertainty|Uncertainty]] 16:45, 31 Dec 2016 (AEDT)

=Cleanup needed=
Hmm this whole Talk page needs a cleanup. A lot of the Not Listed bugs, should be listed, or are listed. [[User:Spike|Spike]] 10:03, 26 December 2012 (EST)

:So, before it will be made, yet three more observations.

:1. There is no possibility to give back (to stop hiring) a plane without craft weapon.

:2. Alien Reproduction is unavailable in a normal game without hacking/save editing. This is probably connected to further errors on maps. A bug/error/programmers' oversight of the some kind is present in TFTD where it is impossible to obtain Examination Room. It is so because many tiles on maps are wrongly assigned to game's objects. Namely, [[Examination Room (TFTD)]] is treated as Alien Implanter - but there is plenty of errors of this type, on various maps (perhaps also in UFO: EU).

:3. Among soldiers in UFO:EU, there are Russians. Some non-Slavs may not know that Slavic (also Russian) family names have different masculine and feminine forms. For example, Petrov, Belov, Likhachev, Gorokhov, Chukarin, Andianov, Voronin, Maleev are all masculine names; women must be called Petrova, Belova, Likhacheva, Gorokhova, Chukarina, Andianova, Voronina, Maleeva respectively (however, a rule that the feminine form is always made by adding -a is wrong, e.g. Tolstoy - Tolstaya). The soldier's name Mikhail Gorokhova (which is possible in UFO: EU) is just ridiculous (for everyone who has even little knowledge about Russian things). Tatyana Petrov is also an impossible combination. X-Com creators probably assumed that family names are the same for men and women in all languages, and, as a result, they made only mechanisms for storing masculine and feminine forms of first names, not family names. But taking reality under consideration, this is a bug.

: [[User:Sherlock|Sherlock]] 16:22, 26 December 2012 (EST)

== Common bugs vs. UFO EU specific bugs ==

I believethere is one more thing that needs to be cleaned. Namely, both EU and TFTD share the same game engine, so some bugs are common for them both. However, there exists a page with a list of TFTD bugs, and it is clear (or: should be clear) which of the bugs are specific for TFTD. I think the same should be done with EU specific bugs: to hold them apart from bugs common for both games. Some bugs exist in both games but manifest themselves differently (like problems with mind-controlling of big aliens) - they are not true common bugs.

Or even more: one could expect a clear information by each bug, in which game and in which version of the game the bug occurs. And whether a patch exists or not. Sometimes such information is given now, and sometimes it is not. And if one does not know exactly which versions are affected by the bug, it should also be mentioned clearly.

[[User:Sherlock|Sherlock]] 04:13, 27 December 2012 (EST)

== Rename page title to indicate which game this refers to? ==

I was looking for a list of bugs related to XCOM Apocalypse, and it took me a while to realize this was about a totally different game. There are 4 games (not counting the 2 opensource projecrs) here on UFOP - maybe that could be reflected in the article aswell?
[[User:Panzerlol|Panzerlol]] 20:35, 31 March 2013 (EDT)

==New "bugs" submitted directly to main page with no apparent explanation==

WakkaDakka, have you actually managed to replicate this "missing time units" bug, or was it just a one-off freak occurrence? I'm not sure it merits main-page space until we have some idea how to replicate it.

N21, how were you seeing the future to begin with? It's only a bug if it occurs in the normal course of play.

[[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 03:36, 28 May 2015 (EDT)

== Enemy Unknown 1994: Save game bug mid mission. ==

Effect : Loading saved game mid mission just displays a black screen with the cursor at the top left, whilst the music continues to play in the background.
I don't believe the game has crashed out to DOS, having tried both CLS and DIR to no avail. Your can no longer interact with the game, making you force quit the app.

[[File:Screen_shot_2016-11-07_at_19.39.31.png|thumb|left]] 

I'm using Boxer 1.40 on a Mac - which in turn is built off Dosbox 0.74.
I remember seeing this bug years ago on Windows XP too, so I don't think it is platform specific.
I'm currently running it with some of the XCOMUtil patches too - but have had the issue crop up without any of the patches.

Playing on Superhuman level, I use a Skyranger with 14 soldiers equipped with Laser Rifles.

Cause : Hard to be specific. But here are the facts.
I have my suspicions it may be do to with fog of war rendering issues.
I've had it occur frequently when going to the NW edge of a map.

I also had issue on Alien base 1. I have a save game and can suggest moving a unit and saving it in another slot - that alone causes the issue. So if someone knows how to debug this I can supply that. Not sure if the combined number of aliens and yourself casue this.. I managed to eventually work thru a series of corrupted saves that wouldn't load to one that worked again).

Here is a sample save game where the game only needs one specific movement to corrupt a game when you save after the move.

[[File:GAME_10.zip]]
I've uploaded two images to show the move for S Bradley
[[File:Screen_shot_2016-11-11_at_13.50.13.png|thumb|left]] 
and the destination square to move him too. When you complete that move and save the game it corrupts.
[[File:Screen_shot_2016-11-11_at_13.50.17.png|thumb|left]] 

Incidentally there were two downed UFO's at this time, with a second Skyranger en-route to UFO 42. This mission was for UFO 43 with another Skyranger.

The problem frequently occurs.
Ive had it occur recently on the following types of mission:
Terror, Alien Base, Supply ship, Large Scout, predominantly with Sectoids and Cyberdiscs, but also with Mutons and Floaters.
The only thing all these missions have had in common was lots of units on both sides. For example 13 Floaters on a Scout mission, 9 Cyberdiscs on a Terror mission etc.

--

Other quirky things I've seen relating to Stunned units:

1) You can't stun a unit, forcing you to shoot it to complete the mission.
The target being stunned drops to the ground in a heap, but the game says you can still see it and can re-stun unit....

2) Celatids. You stun it, then it wakes up and moves away. The unit no longer renders correctly. It's like a sheet of garbled colored/transparent dots.

3) A stunned unit, other than a Celatid wakes up, and is invisible but you get the '1' in red square for visible enemy. You can stun unit and get the animation for it falling to the ground again.

--

Teleported unit off screen (notice the yellow arrow over the unit, which alas is invisible at the split second I took screenshot - OS/X rendering crap-shoot).
[[File:Screen_shot_2016-11-12_at_14.18.07.png|thumb|left]] 
The unit was teleported from the top of the stairs in an entirely different building, rendering the unit unusable for the mission. I ended up reloading it and doing over.... - [[User:JGF|JGF]]

:Stop spamming [[Special:RecentChanges|the changelog]], please - if you're working on a page and want to see the results of your edits midway through, use the Preview button. Don't hit Save until you are ''done''.

:I can't replicate any issues with your provided save. Bradley doesn't have enough TUs to "complete" the requested move, but asking him to make the attempt anyway, then saving / reloading, works fine for me under 1.4 as well as CE. For what it's worth, as far as I'm aware the game in no way keeps track of the number of actions you've performed during a given turn; at least, I haven't been able to find any such counter embedded in the save files.

:I do suggest you leave your units with more time units - when ending turn, any agents who ''might'' spot an alien during the enemy's turn should ideally have some cover, a kneeling stance, and enough action points to defend themselves with a reaction shot. Using your full TU allocation on movement is somewhat suicidal, and even when you can get away with it, it tends to leave agents without enough energy to move when they really need to.

:Your invisible units may be related to [[Known_Bugs#Invisible_Chryssalids|this bug]] - presumably you can trigger similar behaviour by knocking out all instances of a given alien species within a map, saving / reloading, and then waiting for one of the aliens to awake. I was able to replicate it with an Ethereal, for example.

:Difficult to comment on your garbled Celatid without seeing it first-hand. Ditto for your un-stunnable target. I'd quite like to inspect them with my save editor, though, and ditto for the teleported unit. -  [[User:Bomb_Bloke|Bomb Bloke]] ([[User_talk:Bomb_Bloke|Talk]]/[[Special:Contributions/Bomb_Bloke|Contribs]]) 05:46, 13 November 2016 (UTC)

Thanks for scaling the images nice to see the wiki syntax.
It's odd to here you say he didn't have enough Time Units left, because for me the move is allowed.
Where did you get your 1.4 patch?
I applied 1.4 too and am wondering if I got a bad version.
Also did you get your original XCOM off GOG or some place like that?
I have the original CD. I think it's the US version as I used to live there.

== Time Units reset to 0 when soldier reaches 255 TUs ==

I have been playing an old version of UFO: Enemy Unknown, where there is no limit on TUs for soldiers. At certain point, two of my best soldiers reached the limit of 255 TUs, which rendered them useless at now they have 0 TUs.
I tried to reduce their TUs by editing Soldier.DAT, but it did not help. If I check soldiers from the base menu, I can see that the value has been changed, but in the battle their stats are still the same and thus they have 0 TUs and cannot be moved with.

Do any of you know, how to fix this bug? Where is the limiter located, can I change it so that is will be as in the new versions? In any case, I believe this bug should be mentioned on the page. It is mentioned here though: http://www.ufopaedia.org/index.php/Time_Units --[[User:Achernar|Achernar]] ([[User talk:Achernar|talk]]) 21:13, 9 May 2017 (UTC)

: Feel free to add the issue - the page is a hodge podge of whatever issues folks have at the time or as they come across them.

: While I'm no expert on the file structure of the executable for the first release of the game, I suspect you'll find the cause for the byte roll-over feature is that there were no stat limiters to begin with. Best way to cope with it is to either retire anyone approaching supersoldier status to base defence duty, buy more soldiers and spread the experience out more evenly, or update to 1.4 and find a sound patch to restore the original sound samples.

: For your broken soldier: I'm, assuming you edited the soldier.dat file. If you saved the game while in the battlescape, the game creates a temporary copy of the soldier stats and keeps them in unitref.dat. This is to keep track of in-battle status changes, experience, etc. You'll need to edit the current TU levels in this file as well. Or beat the mission with the soldiers that can move and you'll see your edits reflected in the next battle. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 05:45, 11 May 2017 (UTC)

== Fire rate bug & German version footsteps ==

These don't seem to be documented for some reason: (DOS Version)

The fire rate always resets to 3 if an alien or an alien mind controlled unit throws a grenade.

If German is chosen as language to play, the footsteps of all soldiers, regardless of the terrain they walk on, will sound as if they are walking on a metal surface like the inside of the Skyranger, UFO or the base. [[User:Bard|Bard]] ([[User talk:Bard|talk]]) 05:38, 8 April 2019 (CEST)

== Direct incendiary hit causing no reaction fire? ==

On the Incendiary page, it is reported that a direct hit will not cause an alien to spin around and return fire. I have tested this in OpenXcom and find that the aliens do, in fact, return fire. If this can be confirmed in original X-Com, it would be good to add to known bugs.

: It's safe to say everything you find on this wiki relating to the classic game pages were gleaned from the original games. OpenXcom, being an independently developed fan project, will have its own list of fixes and changes chronicled in its own documentation. In fact I would not be surprised that good deal of the more technical information on this wiki has been contributed by those that had some input into the OpenXcom project. [[User:NKF|NKF]] ([[User talk:NKF|talk]]) 05:16, 8 June 2021 (UTC)

:: Thanks, good to know. Would still love to know if anyone has tested this in classic game. If not, I will when I can, so it can be added to known bugs [[User:Mugwump|Mugwump]] ([[User talk:Mugwump|talk]]) 22:05, 15 June 2021 (UTC)

==Alien weapon loadouts bug/anomaly==
There are actually 10 alien weapon loadout sets, not 9. The actual first set is 70% "early"/20% "mid"/10% "late". This loadout set never appears in-game, though, because the setup at game start counts as a month rollover which means that weapon loadouts (which are called when the mission occurs, not at month start when the mission is scheduled) are called from the second set during January, the third set during February, and so on. This is probably an oversight by the Gollops (note that race weights reach their final values in October; were it not for this quirk, weapon loadouts also would), but it's hard to be sure. Should this be added? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 15:02, 28 April 2025 (UTC)

Disruptor Gun

2025-04-28T14:43:30Z

Magic9mushroom: adding infobox

{{Ref Open | title = Disruptor Gun}}[[Image:Disruptor_Gun.jpg|right]]
The Disruptor Gun is a remarkable piece of technology. It propels a beam of sub-atomic particles at immense speeds and quantity. The chamber which generates the energy is an inter-dimensional device which materializes energy from an alternative dimension. The power source, once initiated, is self-perpetuating and no ammunition or energy pods are required to sustain the fire power. Our replicators can reproduce this technology fairly accurately.
{{Ref Close | source = X-COM Apocalypse UFOpaedia}}

After a few engagements with X-COM forces, the aliens realise that arming their [[Anthropod]]s with actual weapons is a good idea. Their first attempt at this is the Disruptor Gun, a lightweight energy weapon powered by dimension chamber technology.

Unusually for an X-Com game, the Disruptor Gun is not really an improvement in firepower over the weapons X-COM can buy in Mega-Primus; its damage per shot is respectable but not amazing, its rate of fire and accuracy are mediocre at best, and it counts as a two-handed weapon for the purpose of [[dual-wield]]ing. On the other hand, the Disruptor Gun is a quite convenient weapon for those uninterested in heavy micromanagement, as it's very light and doesn't require scarce ammunition (allowing standardisation of loadouts). In any case, the weapon should generally be researched with moderate priority, as unresearched artifacts cannot be sold in Apocalypse and the enormous quantities you'll loot from the aliens early on are worth a pretty penny; it's also a research prerequisite for the far more useful [[Devastator Cannon]] and [[X-COM Disruptor Armor]].

Anthropods with this weapon are not especially dangerous except at point-blank range due to their laughably-bad accuracy, although [[Skeletoid]]s pose at least some threat.

The aliens will eventually [[Alien Tech Levels (Apocalypse)|phase out]] the Disruptor Gun as X-COM's tactical score grows ever-higher. However, by that point, the weapon will have found its way into the hands of Mega-Primus organisations, who will continue using it indefinitely, so X-COM can never be locked out of the technology.

When disruptor weapons are destroyed by explosion or fire, they usually discharge a couple of shots in random directions.

==Stats==
===Disruptor Gun===
{|
|[[Image:Disruptor Gun inventory.png|left]]
|
* Size: 2 × 3
* Weight: 5
* ROF: 1.125 r/s
* Accuracy: 30%
* Power: 42
* Damage Type: Disruptor
* Ammo: 28 (recharging)
* Range: 50m
* Base Price: $2100
* Battlescape Score: 8
|}

{{Equipment (Apocalypse) Navbar}}

[[Category: Apocalypse]]
[[Category: Aliens (Apocalypse)]]
[[Category: Alien Artifacts (Apocalypse)]]
[[Category: Agents Equipment (Apocalypse)]]
[[Category: Research (Apocalypse)]]

Alien Infiltration

2025-04-28T14:34:26Z

Magic9mushroom: adding infobox, undoing various style changes that had been made, removing "if successful" since it's always successful, removing word cruft

{{Ref Open | title = Alien Infiltration}}[[Image:Alien Infiltration.png|thumb]]
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.
{{Ref Close | source = UFO: Enemy Unknown UFOpaedia}}
The aliens will [[Scoring#Alien_Scoring|score]] 150 points for this mission. In addition, a country will cease funding X-Com, and an alien base will be constructed.

Initially, several Scouts will perform investigations prior to the main infiltration attempt.

In the main Infiltration wave, a Large Scout will appear, followed by a Terror Ship, Supply Ship and two Battleships. Shooting down any of these craft before they slow down will delay the next craft by a couple of days; if the craft are ignored even for a short while, long enough to slow down, the sequence proceeds extremely quickly.
Shooting down the UFOs or [[UFO Ground Assault|assaulting the landed ships]] will NOT stop the infiltration from succeeding. Shooting down the earlier ships will delay, but not entirely stop the second Battleship. The moment the second Battleship appears in Earth's atmosphere, the infiltration is successful and complete. The country infiltrated will still provide funding at the end of the month when the second Battleship arrives (due to the way funding is handled), but its contribution will be set to zero in all future months, directly harming X-Com's wallet.

Always search for the alien base after the second Battleship, as otherwise it will continue to score points for the Aliens.

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

Alien Infiltration

2025-04-28T14:18:04Z

Magic9mushroom: tidyup and link

[[Image:Alien Infiltration.png|thumb|right|Alien Infiltration research topic and mission.]]
This Alien mission represents the worst threat to X-COM. 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 [[UFOs|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.

If a government agrees to a pact then its funding will cease. If successful, the aliens will [[Scoring#Alien_Scoring|score]] 150 points, and an alien base will also be constructed which generates daily activity points, which are eventually subtracted from your score.

Initially, several Scouts will perform investigations prior to the main infiltration attempt.

In the main Infiltration wave, a Large Scout will appear, followed by a Terror Ship, Supply Ship and two Battleships. It has been shown that shooting down any of these craft before they slow down will delay the next craft by a couple of days; if the craft are ignored even for a short while, long enough to slow down, the sequence proceeds extremely quickly.
It has been conclusively shown that shooting down the UFOs or [[UFO Ground Assault|assaulting the landed ships]] will NOT stop the infiltration from succeeding. Shooting down the earlier ships will delay, but not entirely stop the second Battleship. The moment the second battleship appears in Earth's atmosphere, the infiltration is successful and complete. If the month ends before the second battleship arrives, the infiltrated country will still fund the project normally.

When a country is successfully infiltrated, an alien base will be instantly created in or near the country. Always search for the alien base after the second Battleship, as otherwise it will continue to [[Scoring|score points]] for the Aliens.

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

User:Magic9mushroom

2025-04-21T08:49:32Z

Magic9mushroom: /* Sectopod */ side; my computer ran out of RAM trying to do the Laser Pistol calc but those numbers are sufficiently high that it shouldn't be an issue

Hi.

1) It's a pun on my interest in fantasy novels and fungi. I don't use, sell or possess hallucinogenic drugs (though I do think they should be legalised).

2) I tend to be a [https://en.wikipedia.org/wiki/Wikipedia:WikiOgre WikiOgre]. Don't be surprised if you wake up one day and the "Recent changes" list is all me.

3) I now have admin permissions. Give me a yell if you want something done that requires those permissions (most obviously deleting pages).

==Accomplishments==
Comma indicates same run. Semicolon separates runs. All are without exploits, except Research Rollover (which is hard to avoid).

'''UFO: Enemy Unknown:''' Superhuman, Iron Man, no Psi-Amps, June 1 Cydonia.

'''Terror from the Deep:''' Superhuman, Iron Man.

'''X-Com: Apocalypse:''' Superhuman, Iron Man, no Toxigun, no infiltration graph.

==Battleship Farming==

I'm not sure whether this deserves its own page, so I'm putting it here.

There's a little trick I discovered to obtain huge amounts of money and points and fair amounts of Elerium in UFO (it should also work in TFTD but Leviathans and Bombardment Shields are much harder to obtain).
You will need: 1 or more [[Avenger]]s, [[Plasma Beam]]s, [[Fusion Ball Defences]], [[Grav Shield]], [[Hyper-Wave Decoder]].

How to execute:

1) Intercept lots of UFOs. You were doing that anyway, right?

2) When scouts start appearing with the mission (obtained via Hyper-Wave Decoder) of "Alien Retaliation", leave them alone.

3) Build six or more Fusion Ball Defences and a Grav Shield. Don't build a Mind Shield at the base that you're using for this trick.

4) When Battleships start appearing, shoot them down and recover them with Avengers.

5) Enjoy your points (likely just shy of 1000), money (2 million or more), and Elerium ([[UFO_Crash_Recovery#Power_Source_Explosions_and_Elerium_Recovery|around 50]])!

The reason I call this a "trick" is that it's a way to generate artificially high UFO numbers in order to give you something to shoot at. Alien Retaliation missions that have found your base will not ever end until a Base Defence mission is forced - they will not end on Battleship interception and they will not end if the Battleship is destroyed by your base defences. Here, the Battleships will be turned into confetti by your defences even if they are not intercepted (12 shots of Fusion Balls vs. 3 required to kill it gives 0.0009% odds of making it through - less than 1 in 100,000 will survive), so you're guaranteed a constant and plentiful supply (this is necessary because Avengers are usually damaged by fighting Battleships and as such all of them might still be damaged when a new Battleship appears). It's probably a good idea to keep a lot of Avengers in the base if you want to keep this up for a while, since a single Avenger will be in repairs for almost a month after destroying a Battleship (remember to transfer the crews to undamaged ones).

I find this to be a valid alternative to waylaying Supply Ships for Elerium (allowing the prompt destruction of the associated bases). By the time you have Avengers and Fusion Ball Defences, money and points are largely irrelevant, though it can still be fun to see five-digit scores at the end of a month.
: Good trick. It highlights the fact that Retaliation mission logic is dumb and inflexible, which is a design flaw. Also that Battleships are too weak (I made some suggestions on my Talk page for making them tougher )
: Would you add this to the [[Exploits]] section do you think? [[User:Spike|Spike]] 20:25, 11 February 2012 (EST)

::It's a much more minor exploit than most of the ones on that page. Supply Ship piracy is just as exploitative, it's just better known. Where would it go, anyway? [[User:Magic9mushroom|Magic9mushroom]] 01:53, 12 February 2012 (EST)

==My UFO Masterplan==

Figured I might as well post it. Feel free to criticise.

Initial base goes in Europe (Czechoslovakia). I immediately build a second in the USA (around North Dakota). Layout of the second base (and all later bases) follows:
{{UBK|=
|dirt|dirt|dirt|dirt|dirt|dirt|=
|dirt|dirt|dirt|dirt|dirt|dirt|=
|dirt|dirt|dirt|dirt|dirt|dirt|=
|dirt|dirt|dirt|dirt|quarters|stores|=
|dirt|dirt|dirt|hangar1|hangar2|lift|=
|dirt|dirt|dirt|hangar3|hangar4|large_radar|=}}
(The Living Quarters obviously have to wait for the General Stores to complete.)

Note a few things about this design:

1) The key facilities for an interception base (hangar, radar, general stores) are all available to construct immediately, with no delay.

2) This base design supports perfect base defence - a single choke point between alien spawns and X-Com spawns, and all firefights in indestructible modules - though it may not, at first, appear so. See, the Base Disjoint Bug blocks the Hangar/Large Radar, Large Radar/Access Lift, and Access Lift/General Stores doors, so the only route the aliens can take is through the door between the Hangar and Living Quarters.

3) A design like this has fewer squares left empty than a normal base supporting perfect defence. When fully decked-out, it looks something like this:
{{UBK|=
|fusion|fusion|grav|fusion|quarters|workshop|=
|fusion|fusion|psi|workshop|quarters|workshop|=
|fusion|workshop|quarters|quarters|stores|stores|=
|fusion|dirt|dirt|dirt|quarters|stores|=
|dirt|hangar1|hangar2|hangar1|hangar2|lift|=
|workshop|hangar3|hangar4|hangar3|hangar4|hyperwave|=}}
Note that only 4 squares are left empty, but there's still a single choke point. You can't do that for 2 hangars without using the BDB (a similar design has only 2 squares left empty for a single hangar, but then you risk the aliens overflowing their spawn points).

Initial base gets overhauled with a second hangar up top replacing the two at the bottom and living quarters moved out of where it is. I also immediately build Alien Containment and a Large Radar there. Initial Skyranger load is 10 soldiers, one tank, using the weapons you start with (preference for those with autofire). Interceptors are immediately upgraded to twin Avalanche loadouts. Build laser weapons as they're researched.

I transfer one Interceptor to my US base as soon as the hangars and large radar complete. As soon as I get a significant cash injection I build a third base in SE Asia (central China) with the same starting layout and a third Interceptor. After that cash goes into setting up a two-lab or three-lab research station so I can start crunching through the tech tree. Then three more bases in Africa, South America and Australia.

Final layout of the starting base looks something like this:
{{UBK|=
|hangar1|hangar2|hangar1|hangar2|dirt|mind|=
|hangar3|hangar4|hangar3|hangar4|dirt|psi|=
|dirt|dirt|lift|dirt|psi|hyperwave|=
|quarters|stores|stores|lab|workshop|containment|=
|quarters|stores|quarters|quarters|lab|lab|=
|psi|quarters|quarters|psi|psi|psi|=}}
Since it's best to use a single research base, and the starting base already has a lab, that's kinda a no-brainer. Note the six Psi-Labs, placed so that they can be constructed simultaneously once researched - this is to expedite psi-screening, which is usually the limiting factor in how fast you can get to Cydonia.

My research order is something along these lines:

Laser Weapons

Laser Pistol

Laser Rifle

Mind Probe

Small Launcher*

Stun Bomb*

(Alien Navigator)
->Hyper-Wave Decoder

(Sectoid Leader)
->Psionic Laboratory

Alien Alloys

Personal Armour

Medi-Kit

UFO Power Source

Elerium-115

Power Suit

UFO Navigation

Flying Suit

Heavy Plasma

Heavy Plasma Clip

Plasma Cannon

Psi-Amp

Heavy Laser

Laser Cannon

UFO Construction

New Fighter Craft

New Fighter/Transporter

Ultimate Craft

Blaster Launcher

Blaster Bomb

Alien Origins

(Alien Leader)
->The Martian Solution

(Alien Commander)
->Cydonia or Bust

Filling out the rest of the UFOpaedia entries

<nowiki>* These are skipped if/when I manage to nab both required aliens with Stun Rods.</nowiki>
() Obviously aliens can't be researched until they're captured, so these may be delayed.

Note the extreme beeline for Hyper-Wave Decoders and Psi-Labs. Hyper Wave Decoders are absolute gold. Psi-Labs have to be gotten as soon as possible thanks to the long lead time from their discovery to actually getting Psi.

==TFTD weapon effectiveness calculations==

I figured some were in order. Uses the [[Alien Stats (TFTD)|Alien Stats]] and [[Damage Modifiers (TFTD)|Damage Modifiers]] tables to calculate average damage of each weapon to each sort of alien after damage modifiers and armour. If/when I manage to finish this and turn it into something readable I'll stick it up on the wiki proper. You could do this for UFO:EU but the Heavy Plasma's so obviously dominant that there's little need. The accuracies given will be for a soldier with 70 Firing Accuracy and no bonuses or penalties; I choose this value — the maximum rookie value — rather than the simpler-to-calculate 100 because of the special cases of the Torpedo Launcher, Sonic Cannon and Thermal Shok Launcher - these weapons are most effective in Aimed mode and their 100%+ accuracy in that mode would be wasted for a 100 FA soldier, underselling the weapons.

Note that these "averages" take into account that damage values of "less than 0" after armour aren't actually any worse than 0 and that damage values greater than an alien's HP have no additional effect. Hence, a Gauss Rifle's average damage to a Triscene is 0 (because it cannot penetrate the armour) and a Sonic Cannon's average damage to an Aquatoid Soldier is 30 (because an Aquatoid Soldier will always be instagibbed by a Sonic Cannon hit, and it only has 30 health). I'm calculating the damage cap per shot; this gives a slight bias in favour of powerful, autofire weapons since they can't re-aim between shots in a burst, but this is really only a significant issue when dealing with Aquatoids and Gillmen and their land terror units since the Gauss Rifle isn't realistically likely to drop much else in one burst.

All values assume Superhuman difficulty and a direct hit to the front (front or under armour depending on weapon type). 95% of TU are assumed to be capable of being used per turn (facing considerations). Some values are marked "n/a". This is because one of three factors render this value useless:
*This alien is a land-only terror unit, and this weapon cannot be fired on land
*This weapon is a melee weapon, and you are attempting to use it at range
*This weapon is a thrown or guided weapon, and you are attempting to use it in close combat (since I'm assuming 100% accuracy for such weapons this will be identical to the "ranged" figures)

I will be assuming fired explosives that miss miss fully, and that thrown explosives and the DPL always hit dead-on, to avoid a bazillion cases. In practice, of course, thrown weapons will not work against enemies at extreme range or enemies that are not on the ground, and may miss (though since they are all explosives, some damage will likely still occur). It is also somewhat dangerous to use explosive weapons in close combat.

This has been mainspaced at [[Weapon Effectiveness (TFTD)]], where I have added 2-hit, 3-hit and 4-hit kill chances.

===Notes===
====Technical====

*'''DONE''' - Bio-Drones and Tentaculats have greatly asymmetric armour distributions, understating the effect of non-HE weapons against them when their front armour is considered (the Dart Gun can damage Bio-Drones from behind, and the Jet Harpoon can damage Tentaculats from behind, for instance). There's some effect on the Triscene as well. Otherwise, most aliens have similar armour (within 6 points) on front, side and rear. I'll probably do a second lot of calcs for those two terrorists hit from behind.

*'''DONE''' - I haven't done the exact calculations for average damage and 1-hit kill chance for large units hit by powerful area-effect weapons yet. This is because the four rolls stop being independent when a kill is possible (whether roll #1 rolls 45 or 46 may or may not matter depending on whether the other three add up to 45 already being a kill). I plan to do them before I put this on the main wiki.

*Yes, I'm aware that firing, reloading, and refiring a Torpedo Launcher requires over 95% of TU. The reason I said you could fire the Torpedo Launcher twice in close combat is because, when accuracy is no concern, you can dual-wield them (hardly more insane than firing Torpedo Launchers at point-blank in the first place).

====Analysis of data====

*I was already a fan of the GC-HE, but this has impressed me even more. It achieves damage way out of line with its supposed power. It does this because a) almost every TFTD alien has a giant weak spot in their Under Armour, b) HE gets a better set of damage modifiers than Gauss or even AP. It actually outdamages the Gauss Rifle against Lobster Men, Tasoths, Calcinites, Hallucinoids, Xarquid, Triscenes and (from the front) Tentaculats - and that impressive list is '''after''' accounting for the Gauss Rifle firing thrice as fast.

*A large part of the reason I did this was to settle the old Gauss Rifle vs. Sonic Pistol argument. So, with these numbers, I can say that the Gauss Rifle is better against Aquatoids, Gillmen, and Deep Ones, and worse vs. everything else (except Triscenes, which are immune to both weapons). So the Gauss Rifle will certainly help you in the first month (when, not-so-coincidentally, those three aliens are the only aliens you'll encounter), but if you can handle that first month [[Skipping Gauss Weapons]] starts looking like a pretty decent idea.

*You'll note that the Sonic weapons cluster pretty close to each other at range against basically everything. What this means is that they're pretty well balanced against each other in terms of damage-per-unit-time; which ones to hand out depends more on other factors (the Sonic Pistol's finer granulation allowing scouts to shoot more, one-handed grip, and better point-blank firepower vs. the Sonic Cannon's ongoing recoverable ammo, less off-target damage reducing friendly fire, and increased 1-hit kill rate reducing reaction fire, with the Blasta Rifle somewhere in-between).

*The Heavy Gauss is better than the Gauss Rifle against precisely one enemy (Xarquid) and tied with it against one (Triscenes, which are immune to both). Given that the GC-HE easily outclasses both against those two enemies, I think we can call the Heavy Gauss useless.

*Yes, throwing three pre-armed Sonic Pulsers at something in the same turn is going to kill it very, very dead. But 1) that's several turns of preparation, and the "carried grenades don't explode" behaviour that allows that preparation to be done at mission start is widely considered an exploit; 2) you don't have nearly enough Zrbite or item limit to make this a routine tactic.

*As far as drills go, the Heavy Thermic Lance is the best against Calcinites, Hallucinoids, Triscenes and the front armour of Tentaculats, the Thermic Lance is the best against Xarquid, and the Vibro Blade is best against everything else. Most aliens have enough armour that the HTL "should" do the most damage, but the Vibro Blade has better granularity so it doesn't waste as much damage on overkill. The Thermic Lance is usually in-between the Vibro Blade and HTL (one way or the other) rather than being the worst as might naïvely be expected.

==Firing Accuracy breakpoints==

Most of the time, Firing Accuracy is just something you generically want more of. But 100% accuracy gives a guarantee, which is particularly important in some situations (and obviously, more accuracy ceases to improve that mode of that weapon after that). I'm just going to write down all the breakpoints in Firing Accuracy where a particular weapon in a particular firing mode becomes 100%.

Remember that the starting range for Firing Accuracy is 40-70 and the cap range is 120-125.

{| class="wikitable" style="float:left;"
|+UFO
|-
!Firing Accuracy!!Weapon!!Mode
|-
|76||Rocket Launcher||Aimed, kneeling
|-
|80||Rifle Heavy Plasma Small Launcher||Aimed, kneeling Aimed, kneeling Aimed, kneeling
|-
|87||Laser Rifle Plasma Rifle Rocket Launcher||Aimed, kneeling Aimed, kneeling Aimed, standing
|-
|91||Rifle Heavy Plasma Small Launcher||Aimed, standing Aimed, standing Aimed, standing
|-
|97||Heavy Cannon||Aimed, kneeling
|-
|100||Laser Rifle Plasma Rifle||Aimed, standing Aimed, standing
|-
|102||Plasma Rifle||Snap, kneeling
|-
|103||Plasma Pistol||Aimed, kneeling
|-
|104||Heavy Laser||Aimed, kneeling
|-
|107||Auto-Cannon||Aimed, kneeling
|-
|112||Pistol Heavy Cannon||Aimed, kneeling Aimed, standing
|-
|116||Heavy Plasma||Snap, kneeling
|-
|117||Plasma Rifle||Snap, standing
|-
|118||Plasma Pistol||Aimed, standing
|-
|120||Heavy Laser||Aimed, standing
|-
|122||Auto-Cannon||Aimed, standing
|}

{| class="wikitable" style="float:left; margin-left:10px"
|+TFTD
|-
!Firing Accuracy!!Weapon!!Mode
|-
|73||Thermal Shok Launcher||Aimed, kneeling
|-
|76||Sonic Cannon||Aimed, kneeling
|-
|80||Torpedo Launcher Sonic-Blasta Rifle||Aimed, kneeling Aimed, kneeling
|-
|84||Thermal Shok Launcher||Aimed, standing
|-
|87||Gauss Rifle Sonic Cannon||Aimed, kneeling Aimed, standing
|-
|91||Torpedo Launcher Sonic-Blasta Rifle||Aimed, standing Aimed, standing
|-
|97||Jet Harpoon Gas Cannon Heavy Gauss||Aimed, kneeling Aimed, kneeling Aimed, kneeling
|-
|100||Gauss Rifle||Aimed, standing
|-
|103||Sonic Pistol||Aimed, kneeling
|-
|109||Dart Gun Hydro-Jet Cannon Sonic Cannon||Aimed, kneeling Aimed, kneeling Snap, kneeling
|-
|112||Jet Harpoon Gas Cannon Heavy Gauss||Aimed, standing Aimed, standing Aimed, standing
|-
|116||Sonic-Blasta Rifle||Snap, kneeling
|-
|118||Sonic Pistol||Aimed, standing
|-
|125||Gauss Pistol Dart Gun Hydro-Jet Cannon Thermal Shok Launcher Sonic Cannon||Aimed, kneeling Aimed, standing Aimed, standing Snap, kneeling Snap, standing
|}
{{clear}}

==UFO optimal firing modes==

This is a list of the optimal firing modes for every weapon in UFO, where optimal is defined as "most shots on-target (per 100% Firing Accuracy) achievable with 78/80 TU". There's little point doing one for TFTD, as mixtures of modes are never optimal under that definition (and only in one case with all 80 TU - the Sonic-Blasta Rifle).

{| class="wikitable"
!Weapon!!Combination!!Shots on-target!!TU!!Turns sustainable (+ Rounds left over)
|-
|Pistol||5 Snap||3.00||70||2 (+2)
|-
|Rifle||2 Auto + 1 Snap||2.70||76||2 (+6)
|-
|Heavy Cannon||3 Snap||1.80||78||2
|-
|Auto-Cannon||2 Auto||1.92||64||2 (+2)
|-
|Rocket Launcher||1 Aimed||1.15||60||1
|-
|Laser Pistol||3 Auto + 1 Snap||2.92||76||indefinite
|-
|Laser Rifle||2 Auto + 1 Snap||3.41||74||indefinite
|-
|Heavy Laser||3 Snap||1.50||78||indefinite
|-
|Plasma Pistol||3 Auto||4.50||72||2 (+8)
|-
|Plasma Rifle||1 Auto + 2 Snap||3.37||76||5 (+3)
|-
|Heavy Plasma||2 Auto||3.00||56||5 (+5)
|-
|"||1 Auto + 2 Snap||3.00||76||7
|-
|Small Launcher||1 Aimed||1.10||60||1
|-
|2 Small Launchers||Snap + Drop + Pick Up + Snap||1.30||74||1
|}

===Didn't quite make it===
*79 TU: Small Launcher Snap+Reload+Snap (1.30)
*80 TU: Pistol 4 Snap+1 Aimed (3.18), Laser Pistol 4 Auto (3.36), Plasma Rifle 2 Auto+1 Snap (4.16), Heavy Plasma 2 Auto+1 Snap (3.75)
*Impossible with 80 max TU, but possible with 81 max TU: Laser Rifle 3 Auto (4.14)

===Notes===
*I started this when I realised the Plasma Pistol would probably get the highest. Still inferior to the other plasma weapons due to damage.
*Note how the Laser Rifle significantly exceeds all other non-alien weapons. That's at least as important as the damage to its legendary utility.

==On Interception in UFO (and to some extent TFTD)==
I've seen a lot of talk about the correct craft weapons to use in UFO and TFTD, and while at least for UFO I agree with the ''conclusion'' that a lot of people reach (Avalanches only until Plasma Beams, then Plasma Beams only), I think the ''reasoning'' usually given is flawed, and that the conclusion doesn't apply to TFTD. I usually see people immediately talking about the range issues on specific UFOs (particularly the Large Scout/Cruiser); really, this isn't the right way to think about it. The real questions worth asking are these:
*What UFOs do I ''want'' to use craft weapons against?
*What weapons do I want to use against ''those'' UFOs?
See, the elephant in the room when talking about interception is that the majority of UFOs land, and there's little point wasting missiles on a craft that will land (not to mention the lost Elerium), '''unless''' it's part of a flotilla and therefore you wouldn't be able to get to them in time to perform a UFO Ground Assault. So, which UFOs don't land (recoverably), and what are the likely flotillas?
*Small Scouts never land unless they're on an Alien Base mission.
*Alien Abduction: there's a flotilla of two Abductors at the very end.
*Alien Infiltration: there's a flotilla of one Large Scout, one Terror Ship, one Supply Ship, and two Battleships at the end. Moreover, as the completion of this mission has effects beyond score (that is, you lose a funding country), you probably want to delay these as much as possible.
*Alien Base: there's a flotilla of one Large Scout, two Supply Ships and a Battleship at the end.
*Alien Terror: the first Terror Ship doesn't land. The second Terror Ship does, but as a Terror Site, which means you can't recover the UFO.
*Alien Retaliation: Nothing lands, except the base-attack Battleship, and that's a Base Defence so you can't recover it.
The flotillas don't show up very often, and certainly don't show up early (there's only one non-Terror alien mission per month, and the first one is hardcoded to be Sectoid Alien Research in the area of your first base; additionally, Abduction and Infiltration are very long missions that usually run over into the next month, or even the month after that if it's Infiltration and you're systematically crashing every UFO). The bread and butter of UFO interception is Small Scouts and Terror Ships on Alien Terror, plus the occasional Retaliation and Infiltration.
*You want to use the Avalanche on Small Scouts. Some people say you should use the Stingray (or even the Cannon) to have a chance of crashing them rather than destroying them; I'm guessing the majority of these people haven't actually tried it. The Small Scout has a flee time of '''200''', which is a mere 80-280 frames on Superhuman. 60% of the time you won't close to Stingray range before it runs, another 20% or so (total ~80%) it will run while the missile's in flight, and then more than half the time you actually hit the Stingray destroys it anyway. Your choices, really, are blowing them to bits with Avalanches or doing nothing, and blowing them to bits gets you 100 points (which is more than you get from shootdown + crash recovery, too, since there's a grand total of one alien and the UFO only contains 1 Alien Alloy). Advanced craft ''can'' bring the Small Scout down with Cannons, but by that point you're not hurting for money and there's a significant opportunity cost. The only time you should actually faff around with cannons on an Avenger is if you haven't managed to get a Sectoid Leader and it's rolling around to July (when Ethereals start to show up); the chance to get an Ethereal capture is the only thing from a Small Scout recovery that's remotely worth the effort to get one.
*You want to use dual Avalanches on Terror Ships. This is pretty self-explanatory; using anything else (before Plasma Beams) will get your Interceptors blown out of the sky. Speaking of Plasma Beams, this is the only truly-compelling reason to get them, since you need two Interceptors with Avalanches and that can be tricky (the only other reason to get Plasma Beams before advanced craft is to shoot down Supply Ships, but there aren't a lot of those and they always land). Indeed, Plasma Beams do have a downside in that they risk destroying Medium and Large Scouts (which, unlike in the case of Small Scouts, really ''is'' a waste).
*Anything will work against the Medium and Large Scouts on Retaliation missions. You can't really do anything about the Battleships until you get advanced craft.
The other argument I often see for Avalanches, the one about outranging Large Scouts, is a load of horseshit. A Large Scout is only going to get a couple of shots off against an Interceptor with Stingrays. That's not enough to destroy it, or even to send it to repairs for more than a day or two. Who cares?

And the thing to note about those two arguments for Avalanche missiles in UFO is that neither of them apply to D.U.P. Head torpedoes in TFTD. The TFTD Battleship matches the D.U.P. Head's range, removing it from the list of useful interceptions. And Survey Ships are both more lucrative and easier to crash than the UFO Small Scout, as they cannot run from a Barracuda and Ajaxes have a much lower likelihood to one-hit kill. So I think Ajaxes might actually be the best initial loadout in TFTD; sure, you'll get shot by Cruisers, but not enough to matter. The Sonic Oscillator is also not quite as big a deal in TFTD, as once April rolls around the aliens will mostly be doing scripted terror sites (shipping lane and artefact) which don't have a Battleship to shoot down; the ability to shoot down Large subs is still helpful, though.

Just something to consider.

==Kill tables through armour (UFO/TFTD)==

I'm just going to post some tables indicating the cost (including materials) of a soldier in various armour getting killed and the likelihood that it happens with various weapons. I'm assuming front armour for ballistic weapons, under armour for direct-hit explosives and side armour for edges of blast patterns, and assuming a 35-health soldier (slightly above rookie average; one or two combats would push the average up to here). I will count dying at the end of turn from fatal wounds as a kill, since there is no possibility of a Medi-Kit being applied during the alien turn.

===UFO===
{| class="wikitable"
!Armour!!Cost!!Plasma Pistol!!Plasma Rifle!!Heavy Plasma!!Alien Grenade direct hit!!Alien Grenade blast rim!!Blaster Bomb direct hit!!Blaster Bomb blast rim
|-
!Nothing
|$40,000||57.1%||72.0%||80.5%||100%||16.1%||100%||100%
|-
!Personal Armour
|$88,000 + 800h||21.0%||48.4%||64.1%||80.2%||0%||100%||69.2%
|-
!Power Suit
|$139,500 + 1000h||0%||17.4%||42.4%||47.2%||immune||100%||25.3%
|-
!Flying Suit
|$210,500 + 1400h||immune||11.2%||38.1%||36.3%||immune||98.5%||14.3%
|}

===TFTD===

{| class="wikitable"
!Armour!!Cost!!Sonic Pistol!!Sonic-Blasta Rifle!!Sonic Cannon!!Sonic Pulser direct hit!!Sonic Pulser blast rim!!Disruptor Pulse direct hit!!Disruptor Pulse blast rim
|-
!Nothing
|$40,000||93.8%||100%||100%||100%||78.7%||100%||100%
|-
!Plastic Aqua Armour
|$88,000 + 800h||21.0%||40.6%||70.2%||89.3%||9.3%||100%||65.0%
|-
!Ion Armour
|$139,500 + 1000h||immune||immune||9.2%||58.4%||0%||97.5%||21.8%
|-
!Magnetic Ion Armour
|$210,500 + 1400h||immune||immune||0.8%||47.9%||immune||91.5%||9.2%
|}

===Conclusions===
*UFO: Personal Armour is not worth building. Power/Flying Suits are rather dubious, and poor against Heavy Plasma in particular. The Flying Suit's definitely worth building for your snipers, has obvious massive advantages against Chryssalids, and is worth it for psi-screened troops (who effectively cost ~$320,000 to replace instead of $40,000 due to dropout rates and the need to pay wages for two months), but in other circumstances doesn't really measure up.
*TFTD: Plastic Aqua Armour is of varying effectiveness depending on what the aliens are packing; it's great against Sonic Pistols and pretty good against Sonic-Blasta Rifles, but poor against Sonic Cannons and only somewhat effective against Sonic Pulsers (cuts down the number of kills, but a direct hit is still nearly-always fatal). Ion and Magnetic Ion Armours are simply fantastic, turning 100%-kill shots into 0%. In Magnetic Ion Armour, you only really have to worry about direct hits from Sonic Pulsers and DPLs - and since you can fly, it's a mite hard to hit you with the former. Armour in TFTD is far, far more effective than in UFO, thanks to the narrower damage ranges and its significant damage resistances, and issuing top-of-the-line armour to all troops is a high priority. Indeed, armour levels the field against non-DPL Lobster Men; your guns don't work on them, but theirs don't work on you either, allowing you to close to mêlée range.

==List of organisations in Apocalypse by importance==
This is a list of the various organisations in X-Com: Apocalypse. I've sorted them into categories by how important their services are (and therefore how hard you should try to avoid making them hostile), as well as the timeframe in which they're important. Order within the categories is simply the game ordering; they're not ranked.

===Crucial===
Getting one of these organisations infiltrated or irrecoverably hostile makes the game extremely difficult.
*'''Government''' - Okay, this is kind of the obvious one. If you render the Government hostile and don't fix it by the end of the week, your funding goes away and that's terrible. However, this is incredibly unlikely to happen unless you actively raid or bomb government buildings, as the Government not only starts out friendly to you, but also hates the aliens (improving your relations every time you kill aliens) and is strongly resistant to infiltration.

:''Becomes irrelevant:'' When you research Cloaking Fields. The revenue from selling those is so enormous that the government funding becomes redundant. You can live without their funding quite a while earlier, but you'll probably lose air superiority for a while due to how incredibly cash-hungry the air game is.

*'''Megapol''' - Slightly less obvious than the Government, there are three main reasons you don't want to make an enemy of Megapol:
**First, and least important, Megapol is very aggressive and will perform both raids and air attacks on a regular basis. However, the raids, while second only to Osiron in strength, still aren't enough to get past Security Stations, and the air attacks are performed by Police Hovercars - which don't have any weapons capable of damaging most buildings.
**Second, Megapol Police Cars patrol the city (unless Megapol's balance is negative) and they will scramble Police Hovercars to attack any illegal flyers (which includes your aircraft, if Megapol hates you). This is a distraction you do not need when fighting UFOs. Bankrupting Megapol can allow you to avoid this (the only effect of bankruptcy that I know of), but is rather difficult due to Megapol's enormous budget.
**Third, and the reason Megapol's in "Crucial": Megapol manufactures nearly all the good tactical equipment. Lawpistols and Plasma Guns are the best of the bought equipment, the Auto-Cannon is pretty decent, and Stun Grapples and Stun Grenades are the only way to stun aliens unless you go into psionics. Megapol Armour is also the cheapest in the game, and generally more effective than Marsec Armour at least as far as protection goes (exception for explosives, but most alien explosives are so powerful that you're still dead anyway). They also make a few bits of aircraft equipment, but those aren't particularly necessary.

:On the plus side, like the Government, it's rather difficult to piss off Megapol... unless they get infiltrated. Don't let them get infiltrated.

:''Becomes irrelevant:'' Once you have access to the Devastator Cannon and/or Toxigun, plus Disruptor Armour, Megapol becomes much less useful. Stun Grenades are still nice, but not absolutely necessary. The Police Hovercar issue becomes mostly irrelevant once you have 3+ shielded Retaliators in the sky, as at that point the air game is basically over. Still moderately annoying, but no longer crucial.

*'''Marsec''' - Marsec is the only source of armed vehicles (General Metro makes the Blazer Turbo Bike, but it's unarmed). As such, if Marsec is hostile you cannot replenish craft losses or expand your fleet and will swiftly lose the air war. Hostile Marsec is possibly even worse than hostile Megapol or Government, and it can happen much more easily as well (as they don't inherently like you or hate the aliens).

:''Becomes irrelevant:'' When you have the UFO prereqs for the Explorer (Transporter and Destroyer). The Explorer is enough to shoot down UFOs, and the Bio-Trans can transport troops. Note that I said the prereqs, not actually having the Explorer deployed. You can afford to be knocked out of the air war for a week or two, as long as you have the means to get back into it eventually.

===Important===
You can live without these, but it will hurt.
*'''Transtellar''' - Provides transport services for agents, technical personnel and goods. The only reason this isn't in "Crucial" is because new hires can use the People Tubes (and ultratime prevents them from getting stuck), and because you can do an end run around Transtellar for sellable equipment via selling at one base and buying at another. Still, if Transtellar's hostile you won't be able to move already-hired scientists and engineers from one base to another, nor unresearched alien artifacts; you'll have to be very careful about where you drop mission loot and which base you hire at.

:Unfortunately, you're probably going to have to learn to live without Transtellar, since they start friendly to the aliens (and own a huge amount of very fragile infrastructure) and will as such nearly always go hostile on higher difficulties.

:''Becomes irrelevant:'' Never.

*'''S.E.L.F.''' - Provides androids. Androids have much higher Health than untrained humans (which substantially reduces the chance of critical wounds), and can't be brainsucked or mind-controlled. You don't absolutely need them, though.

:Note that S.E.L.F. doesn't just need to be non-hostile, but on the positive side of neutral for you to be able to recruit androids. On the plus side, they (logically enough) cannot be infiltrated.

:''Becomes irrelevant:'' Disruptor Shields reduce your casualty rate to very low levels. This means humans will survive to surpass androids. The immunity to subversion is still quite useful, though.

===Useful===
These organisations do provide services to X-Com, but they can be played around without much difficulty.
*'''Superdynamics''' - Provides aircraft engines, fuel, and the Cargo Module. They're only "Useful", rather than "Important", because all aircraft come with pre-installed engines and you start with enough fuel to last the entire game. You do lose out on the SD Special, though, which means that any further Hawks you buy won't be at their best in combat.

:''Becomes irrelevant:'' When you unlock the Explorer, since that has a built-in engine. The Bio-Trans has free Cargo Modules, too.

*'''General Metro''' - Provides road engines (which aren't much use) and the Passenger Module (which is quite useful, albeit only in small quantities).

:''Becomes irrelevant:'' When you have enough Passenger Modules for your Bio-Trans. You shouldn't ever lose it unless things have gone really sideways, so there's no need for more.

*'''Solmine''' - Sells only one item, Elerium. Elerium fuels the Lineage Plasma Cannon, which is the best craft weapon before Medium Disruptors. However, Elerium is commonly found as loot from raids, so you can work around a hostile Solmine quite easily (missile launchers are also quite decent alternatives).

:''Becomes irrelevant:'' When you get Retaliators (which can mount Medium Disruptors in all three slots) or anytime prior as long as you're willing to go on frequent raids.

*'''Nanotech''' - Nanotech's on the cusp of being "Important", because the Medi-Kit they sell is actually rather good. However, critical wounds aren't all that common in Apocalypse, it's fairly rare to actually lose a Medi-Kit, and a wounded soldier can be saved by evacuating them, so you can make do without them.

:''Becomes irrelevant:'' Never.

*'''Mutant Alliance''' - The Mutant Alliance provides Sectoid hybrids for recruitment. Hybrids are the only agents that can use psionics effectively, and even make better soldiers than humans after enough training (as they have the same physical stat caps, but can also become nearly immune to psionics). The problems are that psionics just aren't very good against aliens and that hybrids take a huge amount of training to reach their potential.

:Like S.E.L.F., the Mutant Alliance needs to actually like you, rather than just not be hostile, to provide their services.

:''Becomes irrelevant:'' Never. The second Alien Dimension mission, however, will switch the Mutant Alliance to Allied, so if that's imminent you probably don't want to bother paying them off.

===Irrelevant===
These organisations either don't provide anything, or provide only things that are largely irrelevant. Hostilities with these only have the usual consequence of occasional base raids (and air attacks, if they're a gang or have been infiltrated). Some of them are allied to more important organisations, though, so you might want to avoid gratuitous damage to those.

*'''Cult of Sirius''' - Useless. Also moot, since unless the Aliens accidentally level their temple with an Overspawn they'll always be hostile.
*'''Cyberweb''' - Weapons Control systems don't let you lead targets, so they're useless. The Missile Evasion Matrix doesn't seem to work. Allied with S.E.L.F., though.
*'''Sensovision''' - Useless.
*'''Lifetree''' - Useless.
*'''Nutrivend''' - Useless.
*'''Evonet''' - Useless.
*'''Sanctuary Clinic''' - Useless. Allied with Nanotech, though.
*'''Energen''' - Useless.
*'''Synthemesh''' - Useless. They appear to repair your buildings even if hostile.
*'''Gravball League''' - Useless. There's a rumour that they increase the number of humans for hire, but I think that's an urban legend.
*'''Psyke''' - Produces Psiclone. However, you never need to buy Psiclone, only sell it, and you can do that even when the manufacturer's hostile.
*'''Diablo''' - Produces the Incendiary Grenade, but the Auto-Cannon and Minilauncher are better at that anyway. Does perform frequent and large raids, but with Security Stations that's just more free money.
*'''Osiron''' - Useless. They launch huge raids, but that's about it.
*'''Extropians''' - Useless. Allied with Marsec and Solmine, though.
*'''Technocrats''' - Useless.

==Calcinite appearance chance==
You might wonder why I'm making a table listing the chance of a Calcinite appearing in TFTD. Well, there are a few aliens that are important to encounter in TFTD - here's a list of why they're important and where you can guarantee encountering them:

*Deep One corpse for Aqua Plastics and live capture for Ion Armour (guaranteed at first Terror Site, since it's always Gill Men)
*Lobster Man Commander live capture for T'Leth, the Alien's City (guaranteed in Alien Colonies)
*Tasoth live capture for M.C. Disruptor (guaranteed in Alien Colonies)
*Gill Man corpse for Thermic Lance (guaranteed at first Terror Site)
*Calcinite corpse for Vibroblade (guaranteed... '''nowhere''')

That's right, Calcinites are the one important alien that isn't guaranteed to show up. What's worse, they're ''rare''. Calcinites only appear on Aquatoid and Mixed Crew missions above water (i.e. Port/Island/Ship terror attacks and Base Defences). On my playthrough of TFTD on Superhuman, the damned things never appeared once in the entire game, until eventually I gave in, abandoned my "no psi" rule and used M.C. Disruptors to hit a colony and win. So, here's a table of how likely the terror mission for the month is to have Calcinites (this doesn't take into account retaliation, 'tis true, but early on an Aquatoid Base Defence is insanely hard and later on it can be difficult to provoke one). There's also a cumulative chance that, by the end of the month, you will have encountered Calcinites at some point. I'll only go up to May 2041, because things get complicated to calculate after that (there's a possibility that the aliens will run out of Artefact Sites).

{| class="wikitable"
!Month!!Chance!!Cumulative Chance
|-
!January 2040
|0%||0%
|-
!February
|20%||20%
|-
!March
|20%||36%
|-
!April
|26%||52.6%
|-
!May
|26%||65.0%
|-
!June
|13%||69.5%
|-
!July
|15%||74.1%
|-
!August
|15%||78.0%
|-
!September
|15%||81.3%
|-
!October
|19%||84.8%
|-
!November
|19%||87.7%
|-
!December
|19%||90.0%
|-
!January 2041
|19%||91.9%
|-
!February
|19%||93.5%
|-
!March
|19%||94.7%
|-
!April
|19%||95.7%
|-
!May
|19%||96.5%
|}

That's right: while you've got an even chance to get drills by May, there's a one-in-five chance of no drills by September (when alien loadouts finalise, and DPL Lobster Men become way too common) and a one-in-ten chance of having to wait for the new year. RNG, ho!

==Accuracy in Apocalypse==

You may have been rather perplexed by the total lack of hard numbers on accuracy in Apoc. Unlike other games, there's just a highly-inexact accuracy bar. Well, fear not. I'm going to explain what's going on, as best I've been able to figure out (from [https://pastebin.com/PuSSyziU this] code dig - a big thankyou to Skin36 and OpenApoc - and from my own substantial in-game testing).

===Accuracy formula===

Let's start with the accuracy formula that Apocalypse uses. There are quite a few terms, so buckle up.

*Agent inaccuracy term
**Start with the agent's inaccuracy (the value in the data files, 100-displayed accuracy).
**Multiply by 1.4 if both the agent's hands are full and ''either'' of the wielded items is over 2x2.
**Movement modes (in real-time; I haven't exhaustively tested TB, but I know it's different):
***If running, crawling, or run-flying, you cannot fire, so it doesn't matter what your accuracy is.
***If walking, multiply by 1.25.
***If standing, multiply by 0.8.
***If kneeling, multiply by 0.64 (0.8*0.8).
***If prone, multiply by 0.48 (0.6*0.8).
***If walk-flying, multiply by 1.4375 (1.25*1.15).
***If stand-flying, kneel-flying or prone-flying, multiply by 0.92 (0.8*1.15).
***If crawl-flying, multiply by... I'm not even sure. I know it's lower (better) than walking, but higher (worse) than stand-flying. My guess based on the numbers in that dump is either 1.15 (1*1.15, or 1.25*0.8*1.15) or 1.0925 (0.95*1.15), but in-game testing doesn't have the precision to tell them apart.
**Shooting modes:
***If aimed, multiply by 0.5.
***If snap, multiply by 1.
***If auto, multiply by 2.
*Weapon inaccuracy term
**Weapon's inaccuracy (100-displayed accuracy) divided by 2.
*Lost health term
**100*(lost health/current health). Note that this gets absurdly large if your agent is on very low health.
*Critical wound term
**For X-COM Agents and most enemies, this is 150 if the arm with the weapon is wounded and 0 otherwise. (I don't think a bodypart can have multiple wounds.)
**Some aliens don't have separate bodyparts; for those, this is 100*wounds.
*Berserk term
**This is 200 if berserk and 0 otherwise.
*Cloaking term
**If the target is cloaked (has a Personal Cloaking Field in hand), this is 2000/(distance + 3). Otherwise, it's 0.
*Summation of terms
**Add up (agent inaccuracy)^2 + (weapon inaccuracy)^2 + (health term)^2 + (wound term)^2 + (berserk term)^2 + (cloaking term)^2.
**Take the square root, and round down. This is the final inaccuracy rating of the shot.
**98+ inaccuracy corresponds to a completely-empty "accuracy bar"; a hypothetical 0 inaccuracy would correspond to a completely-full "accuracy bar".

===So a shot with 40 inaccuracy is 60% accurate?===
No.

There is no hit/miss test in Apocalypse. The inaccuracy rating is converted ''directly'' into the shot spread - a higher inaccuracy rating means a bigger spread. The actual chance to hit is determined by how much of that spread ends up hitting the target - this is going to vary dramatically depending on the target's cross-section, the distance to the target, and the presence or absence of cover obscuring parts of the target.

(The high complexity of figuring this out, even neglecting cover, is presumably why Apocalypse is so cagey about giving you numbers.)

I am not sure of the precise details of how the spread is generated, but I ''think'' that, for large inaccuracies and small targets, halving the inaccuracy should give you 4x the hit rate (as the spread will be half as wide and contain 1/4 the area). This doesn't hold if you're already hitting most of the time, however - obviously, your actual chance to hit can't go above 100%.

===Consequences of this===
There are a few results here that bear mentioning.
*All the modifiers from movement, dual-wielding and shot mode ''only affect the agent inaccuracy term''. This means that if the agent inaccuracy term is negligible (i.e., your agent has very high Accuracy), these become much less important. Let's do a worked example, with an Accuracy 20 and Accuracy 90 soldier both firing a Megapol Auto Cannon (accuracy 40), and assuming no special circumstances (full health, no cloaking or berserk).
**If the Accuracy 20 soldier is single-wielding, in aimed mode, and is prone, his inaccuracy is sqrt((80*0.48*0.5)^2 + 30^2) = 35.
**If the Accuracy 20 soldier is dual-wielding, in auto mode, and is walking, his inaccuracy is sqrt((80*1.4*1.25*2)^2 + 30^2) = 281.
**If the Accuracy 90 soldier is single-wielding, in aimed mode, and is prone, his inaccuracy is sqrt((10*0.48*0.5)^2 + 30^2) = 30.
**If the Accuracy 90 soldier is dual-wielding, in auto mode, and is walking, his inaccuracy is sqrt((10*1.4*1.25*2)^2 + 30^2) = 46.
:The Accuracy 20 soldier is going to be shooting all over the place if he doesn't pay attention to these modifiers, so much so that firing 8x as fast will still result in less hits. The Accuracy 90 soldier might hit half as often (at long range), but that's still 4x as many hits, and he gets more mobility to boot. This is a very nice emergent effect from the formula - well-trained soldiers can pull off cool stunts that rookies can't.
*In real-time mode, you should pretty much always dual-wield unless you can't afford (or can't get) the extra gun. Dual-wielding two-handed weapons in aimed mode ultimately gives a 0.7x modifier to agent inaccuracy (1.4*0.5), but single-wielding in snap mode - at the same rate of fire - gives a 1x modifier (i.e. strictly worse). Likewise, dual-wielding two-handed weapons in snap mode gives a 1.4x modifier, but single-wielding in auto mode gives 2x. However, because you get the two-handed penalty if ''either'' of your weapons is two-handed, you should generally give agents either two two-handed weapons or two one-handed weapons (not one of each).
*Because there's always a shot spread, anything you can do to cut down your cross-section (kneeling, crawling/prone, cover) will directly reduce how often you get hit. Since the first two ''also'' increase your own accuracy, they're critically important in a firefight and you should basically always be doing one of them unless you're moving or you need the elevated shooting position (to shoot over cover). The advantages of kneeling over prone are that a kneeling soldier can turn freely (a prone soldier has to get up to turn - not good in close quarters!) and that a kneeling soldier takes up less space (e.g. in a firing line) - but prone is better on the numbers in a long-range slugfest in open terrain (e.g. the upper floor of a Procreation Park, some Corporate HQ maps, much of the Alien Dimension)

==Weapon Effectiveness (UFO)==
Finally decided to do at least some of these; I want to get hard data regarding rifles vs. HC/AC, and regarding Cyberdiscs and Sectopods in particular. Note that these calculations render Spike's Firepower Tables obsolete, at least as far as they go, as the latter do not consider max-health and thus sometimes give nonsense numbers like 0.5 Blaster Bombs being required to kill a Sectopod.

===Sectoid===

{| class="wikitable"
|+Sectoid Soldier (health 30, front armour 4, under armour 2)
|-
!rowspan="2"|Weapon!!rowspan="2"|Power!!rowspan="2"|Modifier!!rowspan="2"|Damage range!!rowspan="2"|Average damage per hit!!rowspan="2"|1-hit kill!!rowspan="2"|2-hit kill!!rowspan="2"|3-hit kill!!rowspan="2"|4-hit kill!!rowspan="2"|5-hit kill!!rowspan="2"|6-hit kill!!colspan="3"|At range!!colspan="2"|Close combat
|-
!Mode!!Accuracy!!%TU/kill!!Mode!!%TU/kill
|-
!Pistol
|26||100%||0-30||19.0||35.8%||76.4%||93.6%||98.6%||99.7%||100.0%||Snap||42%||83.9||Snap||35.3
|-
!Rifle
|30||100%||0-30||20.4||44.3%||82.2%||95.8%||99.2%||99.9%||100.0%||Auto*||24.5%||97.6||Auto||36.5
|-
!HC-AP
|56||100%||0-30||24.8||69.9%||94.8%||99.3%||99.9%||100.0%||100.0%||Snap||42%||106.9||Snap||44.9
|-
!HC-HE
|52||100%||24-30||29.6||88.7%||100%||-||-||-||-||Snap||42%||87.5||Snap||36.7
|-
!AC-AP
|42||100%||0-30||23.1||60.0%||90.8%||98.5%||99.8%||100.0%||100.0%||Auto||22.4%||104.5||Auto||40.6
|-
!AC-HE
|44||100%||20-30||28.8||77.8%||100%||-||-||-||-||Auto*||22.4%||87.8||Auto||40.0
|-
!RL-Sml
|75||100%||30-30||30.0||100%||-||-||-||-||-||Aimed||80.5%||93.2||Snap||45.0
|-
!RL-Lge
|100||100%||30-30||30.0||100%||-||-||-||-||-||Aimed||80.5%||93.2||Snap||45.0
|-
!LasPist
|46||100%||0-30||23.7||63.4%||92.3%||98.8%||99.9%||100.0%||100.0%||Auto||19.6%||71.0||Auto||25.3
|-
!LasRfle
|60||100%||0-30||25.2||71.9%||95.5%||99.5%||99.9%||100.0%||100.0%||Auto*||32.2%||60.2||Snap||33.3
|-
!HvyLas
|85||100%||0-30||26.6||80.1%||97.7%||99.8%||100.0%||100.0%||100.0%||Snap||35%||115.4||Snap||40.4
|-
!PlasPist
|52||100%||0-30||24.4||67.6%||94.0%||99.2%||99.9%||100.0%||100.0%||Auto||35%||51.6||Auto||30.2
|-
!PlasRfle
|80||100%||0-30||26.4||78.9%||97.4%||99.8%||100.0%||100.0%||100.0%||Auto*||38.5%||53.4||Auto||36.1
|-
!HvyPlas
|115||100%||0-30||27.5||85.3%||98.8%||99.9%||100.0%||100.0%||100.0%||Auto*||35%||53.0||Snap||34.8
|-
!SmlLnch
|90||100%||0-30||27.1||82.3%||98.2%||99.9%||100.0%||100.0%||100.0%||Aimed||77%||116.5||Snap||47.8
|-
!Grenade
|50||100%||23-30||29.5||86.3%||100%||-||-||-||-||Throw||"100%"||"85.3"||n/a||n/a
|-
!PrxGrnd
|70||100%||30-30||30.0||100%||-||-||-||-||-||Throw||"100%"||"75.0"||n/a||n/a
|-
!HighEx
|110||100%||30-30||30.0||100%||-||-||-||-||-||Throw||"100%"||"75.0"||n/a||n/a
|-
!AlnGrnd
|90||100%||30-30||30.0||100%||-||-||-||-||-||Throw||"100%"||"75.0"||n/a||n/a
|-
!Blaster
|200||100%||30-30||30.0||100%||-||-||-||-||-||Launch||"100%"||"66.0"||n/a||n/a
|-
!StunRod
|65||100%||0-30||25.5||74.0%||95.8%||99.5%||99.9%||100.0%||100.0%||n/a||n/a||n/a||Melee||39.2
|}
<nowiki>*</nowiki>Snap fire becomes more TU-efficient at 114+/100+ (Rifle), never/111+ (AC-HE), 123+/107+ (Laser Rifle), 100+/87+ (Plasma Rifle), 117+/101+ (Heavy Plasma) Firing Accuracy (standing/kneeling)

===Floater===

{| class="wikitable"
|+Floater Soldier (health 35, front armour 8, under armour 12)
|-
!rowspan="2"|Weapon!!rowspan="2"|Power!!rowspan="2"|Modifier!!rowspan="2"|Damage range!!rowspan="2"|Avg. dmg. per hit!!rowspan="2"|1-hit kill!!rowspan="2"|2-hit kill!!rowspan="2"|3-hit kill!!rowspan="2"|4-hit kill!!rowspan="2"|5-hit kill!!rowspan="2"|6-hit kill!!rowspan="2"|7-hit kill!!rowspan="2"|8-hit kill!!colspan="3"|At range!!colspan="2"|Close combat
|-
!Mode!!Accuracy!!%TU/kill!!Mode!!%TU/kill
|-
!Pistol
|26||100%||0-35||17.8||18.9%||58.1%||82.9%||94.0%||98.1%||99.5%||99.9%||100.0%||Snap||42%||106.5||Snap||44.7
|-
!Rifle
|30||100%||0-35||20.1||29.5%||68.3%||88.8%||96.6%||99.1%||99.8%||99.9%||100.0%||Auto*||24.5%||116.0||Auto||39.0
|-
!HC-AP
|56||100%||0-35||26.9||61.9%||90.8%||98.2%||99.7%||100.0%||100.0%||100.0%||100.0%||Snap||42%||117.4||Snap||49.3
|-
!HC-HE
|52||100%||14-35||30.6||60.4%||99.5%||100%||-||-||-||-||-||Snap||42%||110.1||Snap||46.3
|-
!AC-AP
|42||100%||0-35||24.3||49.4%||83.7%||95.9%||99.1%||99.8%||100.0%||100.0%||100.0%||Auto||22.4%||116.8||Auto||41.7
|-
!AC-HE
|44||100%||10-35||27.8||44.4%||95.6%||100.0%||100%||-||-||-||-||Auto||22.4%||109.4||Auto||40.0
|-
!RL-Sml
|75||100%||25-35||34.3||86.8%||100%||-||-||-||-||-||-||Aimed||80.5%||105.4||Snap||50.9
|-
!RL-Lge
|100||100%||35-35||35.0||100%||-||-||-||-||-||-||-||Aimed||80.5%||93.2||Snap||45.0
|-
!LasPist
|46||100%||0-35||25.2||53.8%||86.4%||96.8%||99.4%||99.9%||100.0%||100.0%||100.0%||Auto||19.6%||78.6||Auto||25.8
|-
!LasRfle
|60||100%||0-35||27.5||64.5%||92.0%||98.6%||99.8%||100.0%||100.0%||100.0%||100.0%||Auto*||32.2%||64.2||Auto||34.5
|-
!HvyLas
|85||100%||0-35||29.7||74.9%||96.0%||99.5%||99.9%||100.0%||100.0%||100.0%||100.0%||Snap||35%||122.3||Snap||42.8
|-
!PlasPist
|52||100%||0-35||26.3||59.0%||89.3%||97.8%||99.6%||99.9%||100.0%||100.0%||100.0%||Auto||35%||55.6||Auto||30.7
|-
!PlasRfle
|80||100%||0-35||29.3||73.3%||95.5%||99.4%||99.9%||100.0%||100.0%||100.0%||100.0%||Auto*||38.5%||55.7||Auto||36.2
|-
!HvyPlas
|115||100%||0-35||31.1||81.4%||97.8%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto*||35%||54.6||Auto||35.1
|-
!SmlLnch
|90||100%||0-35||29.2||74.0%||95.1%||99.2%||99.9%||100.0%||100.0%||100.0%||100.0%||Aimed||77%||128.4||Snap||52.7
|-
!Grenade
|50||100%||13-35||30.0||56.9%||98.9%||100%||-||-||-||-||-||Throw||"100%"||"108.2"||n/a||n/a
|-
!PrxGrnd
|70||100%||23-35||33.9||83.1%||100%||-||-||-||-||-||-||Throw||"100%"||"87.7"||n/a||n/a
|-
!HighEx
|110||100%||35-35||35.0||100%||-||-||-||-||-||-||-||Throw||"100%"||"75.0"||n/a||n/a
|-
!AlnGrnd
|90||100%||33-35||35.0||97.8%||100%||-||-||-||-||-||-||Throw||"100%"||"76.6"||n/a||n/a
|-
!Blaster
|200||100%||35-35||35.0||100%||-||-||-||-||-||-||-||Launch||"100%"||"66.0"||n/a||n/a
|-
!StunRod
|65||100%||0-35||28.1||67.2%||92.7%||98.7%||99.8%||100.0%||100.0%||100.0%||100.0%||n/a||n/a||n/a||Melee||42.5
|}
<nowiki>*</nowiki>Snap fire becomes more TU-efficient at never/125 (Rifle), never/116+ (Laser Rifle), 107+/93-112 (Plasma Rifle), 122+/106+ (Heavy Plasma) Firing Accuracy (standing/kneeling)

===Snakeman===

{| class="wikitable"
|+Snakeman Soldier (health 45, front armour 20, under armour 12)
|-
!rowspan="2"|Weapon!!rowspan="2"|Pwr.!!rowspan="2"|Mod.!!rowspan="2"|Dmg. range!!rowspan="2"|Avg. per hit!!rowspan="2"|1HK!!rowspan="2"|2HK!!rowspan="2"|3HK!!rowspan="2"|4HK!!rowspan="2"|5HK!!rowspan="2"|6HK!!rowspan="2"|7HK!!rowspan="2"|8HK!!rowspan="2"|9HK!!rowspan="2"|10HK!!rowspan="2"|11HK!!rowspan="2"|12HK!!rowspan="2"|13HK!!rowspan="2"|14HK!!rowspan="2"|15HK!!rowspan="2"|16HK!!colspan="3"|At range!!colspan="2"|Close combat
|-
!Mode!!Acc.!!%TU/kill!!Mode!!%TU/kill
|-
!Pistol
|26||100%||0-32||10.0||0%||9.5%||27.8%||48.0%||65.3%||78.3%||87.1%||92.6%||95.9%||97.8%||98.8%||99.4%||99.7%||99.9%||99.9%||100.0%||Snap||42%||214.3||Snap||90.0
|-
!Rifle
|30||100%||0-40||13.4||0%||20.5%||45.9%||66.8%||81.2%||89.9%||94.8%||97.5%||98.8%||99.4%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||Auto||24.5%||204.8||Auto||57.9
|-
!HC-AP
|56||100%||0-45||27.9||42.5%||75.6%||91.2%||97.1%||99.1%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||42%||153.1||Snap||64.3
|-
!HC-HE
|52||100%||14-45||35.6||41.5%||96.0%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||Snap||42%||127.7||Snap||53.6
|-
!AC-AP
|42||100%||0-45||22.2||23.5%||56.9%||79.2%||91.0%||96.3%||98.6%||99.5%||99.8%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||22.4%||165.7||Auto||48.9
|-
!AC-HE
|44||100%||10-45||31.0||22.2%||87.0%||99.8%||100%||-||-||-||-||-||-||-||-||-||-||-||-||Auto||22.4%||127.4||Auto||40.1
|-
!RL-Sml
|75||100%||25-45||42.2||73.7%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Aimed||80.5%||117.7||Snap||56.8
|-
!RL-Lge
|100||100%||38-45||44.7||93.1%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Aimed||80.5%||99.6||Snap||48.1
|-
!LasPist
|46||100%||0-45||24.2||30.1%||64.0%||84.1%||93.7%||97.7%||99.2%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||19.6%||107.1||Auto||29.2
|-
!LasRfle
|60||100%||0-45||29.0||46.3%||78.7%||92.8%||97.8%||99.4%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||32.2%||77.7||Auto||36.5
|-
!HvyLas
|85||100%||0-45||33.7||62.0%||89.3%||97.4%||99.4%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||35%||143.2||Snap||50.1
|-
!PlasPist
|52||100%||0-45||26.6||38.1%||71.7%||89.0%||96.1%||98.7%||99.6%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||70.0||Auto||33.4
|-
!PlasRfle
|80||100%||0-45||33.0||59.6%||88.0%||96.9%||99.3%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||38.5%||62.8||Auto||37.1
|-
!HvyPlas
|115||100%||0-45||36.6||71.9%||94.2%||99.0%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||58.9||Auto||35.4
|-
!SmlLnch
|90||100%||0-45||36.0||68.5%||93.1%||98.7%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||77%||136.3||Snap||56.0
|-
!Grenade
|50||100%||13-45||34.6||37.3%||94.5%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"126.2"||n/a||n/a
|-
!PrxGrnd
|70||100%||23-45||41.4||69.0%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"98.2"||n/a||n/a
|-
!HighEx
|110||100%||43-45||45.0||98.2%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"76.4"||n/a||n/a
|-
!AlnGrnd
|90||100%||33-45||44.1||86.8%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"84.9"||n/a||n/a
|-
!Blaster
|200||100%||45-45||45.0||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Launch||"100%"||"66.0"||n/a||n/a
|-
!StunRod
|65||100%||0-45||30.2||50.4%||81.1%||93.8%||98.1%||99.5%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||n/a||n/a||n/a||Melee||53.2
|}

===Muton===
{| class="wikitable"
|+Muton Soldier (health 125, front armour 20, under armour 10)
|-
!rowspan="2"|Weapon!!rowspan="2"|Pwr.!!rowspan="2"|Mod.!!rowspan="2"|Dmg. range!!rowspan="2"|Avg. per hit!!rowspan="2"|1HK!!rowspan="2"|2HK!!rowspan="2"|3HK!!rowspan="2"|4HK!!rowspan="2"|5HK!!rowspan="2"|6HK!!rowspan="2"|7HK!!rowspan="2"|8HK!!rowspan="2"|9HK!!rowspan="2"|10HK!!rowspan="2"|15HK!!rowspan="2"|20HK!!rowspan="2"|25HK!!rowspan="2"|30HK!!rowspan="2"|35HK!!rowspan="2"|40HK!!rowspan="2"|50HK!!colspan="3"|At range!!colspan="2"|Close combat
|-
!Mode!!Acc.!!%TU/kill!!Mode!!%TU/kill
|-
!Pistol
|26||60%||0-11||1.9||0%||0%||0%||0%||0%||0%||0%||0.0%||0.0%||0.0%||2.2%||21.5%||56.7%||83.4%||95.2%||98.9%||100.0%||Snap||42%||1076.8||Snap||452.2
|-
!Rifle
|30||60%||0-16||3.5||0%||0%||0%||0%||0%||0.0%||0.0%||0.1%||0.3%||1.1%||25.1%||69.1%||92.6%||98.8%||99.8%||100.0%||100.0%||Auto||24.5%||901.1||Auto||229.6
|-
!HC-AP
|56||60%||0-47||16.4||0%||0%||1.4%||10.4%||27.2%||47.1%||65.2%||78.9%||88.1%||93.6%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||42%||545.4||Snap||229.1
|-
!HC-HE
|52||100%||16-68||42.0||0%||6.4%||69.6%||98.1%||100.0%||100%||-||-||-||-||-||-||-||-||-||-||-||Snap||42%||256.1||Snap||107.6
|-
!AC-AP
|42||60%||0-30||9.0||0%||0%||0%||0.0%||1.1%||5.3%||13.8%||26.1%||40.5%||54.8%||94.4%||99.7%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||22.4%||638.2||Auto||153.3
|-
!AC-HE
|44||100%||12-56||34.0||0%||0%||34.3%||87.5%||99.4%||100.0%||100.0%||100%||-||-||-||-||-||-||-||-||-||Auto||22.4%||238.8||Auto||66.3
|-
!RL-Sml
|75||100%||27-102||64.5||0%||63.2%||98.7%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||Aimed||80.5%||221.8||Snap||107.1
|-
!RL-Lge
|100||100%||40-125||88.8||15.8%||92.5%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Aimed||80.5%||178.6||Snap||86.3
|-
!LasPist
|46||100%||0-73||29.0||0%||4.2%||25.5%||52.3%||73.8%||87.2%||94.3%||97.6%||99.1%||99.7%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||19.6%||206.7||Auto||47.1
|-
!LasRfle
|60||100%||0-100||41.7||0%||23.5%||56.7%||79.9%||91.9%||97.1%||99.0%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||32.2%||135.3||Auto||49.8
|-
!HvyLas
|85||100%||0-125||64.3||15.2%||57.4%||83.7%||94.8%||98.5%||99.6%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||35%||236.4||Snap||82.7
|-
!PlasPist
|52||100%||0-84||34.0||0%||11.8%||40.3%||67.1%||84.4%||93.4%||97.4%||99.1%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||126.2||Auto||50.0
|-
!PlasRfle
|80||100%||0-125||60.6||9.9%||52.0%||80.5%||93.4%||98.0%||99.5%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||38.5%||95.3||Auto||43.2
|-
!HvyPlas
|115||100%||0-125||80.1||37.2%||76.7%||93.4%||98.4%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||77.5||Auto||37.3
|-
!SmlLnch
|90||100%||0-125||74.6||25.4%||68.0%||89.7%||97.3%||99.4%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||77%||214.6||Snap||88.1
|-
!Grenade
|50||100%||15-65||40.0||0%||3.2%||62.1%||96.9%||100.0%||100.0%||100%||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"253.4"||n/a||n/a
|-
!PrxGrnd
|70||100%||25-95||60.0||0%||52.5%||97.4%||100.0%||100%||-||-||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"187.6"||n/a||n/a
|-
!HighEx
|110||100%||45-125||95.8||27.9%||96.5%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"131.6"||n/a||n/a
|-
!AlnGrnd
|90||100%||35-125||80.0||1.1%||85.4%||100.0%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"160.1"||n/a||n/a
|-
!Blaster
|200||100%||90-125||121.9||82.6%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Launch||"100%"||"77.5"||n/a||n/a
|-
!StunRod
|65||100%||0-110||46.6||0%||27.1%||58.5%||79.9%||91.3%||96.5%||98.7%||99.5%||99.8%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||n/a||n/a||n/a||Melee||104.6
|}

===Ethereal===
====Soldier====
{| class="wikitable"
|+Ethereal Soldier (health 55, front armour 35, under armour 35)
|-
!rowspan="2"|Weapon!!rowspan="2"|Pwr.!!rowspan="2"|Mod.!!rowspan="2"|Dmg. range!!rowspan="2"|Avg. per hit!!rowspan="2"|1HK!!rowspan="2"|2HK!!rowspan="2"|3HK!!rowspan="2"|4HK!!rowspan="2"|5HK!!rowspan="2"|6HK!!rowspan="2"|7HK!!rowspan="2"|8HK!!rowspan="2"|9HK!!rowspan="2"|10HK!!rowspan="2"|15HK!!rowspan="2"|20HK!!rowspan="2"|25HK!!rowspan="2"|30HK!!rowspan="2"|35HK!!rowspan="2"|40HK!!rowspan="2"|50HK!!colspan="3"|At range!!colspan="2"|Close combat
|-
!Mode!!Acc.!!%TU/kill!!Mode!!%TU/kill
|-
!Pistol
|26||100%||0-17||2.9||0%||0%||0.0%||0.2%||1.1%||2.8%||5.7%||9.8%||15.0%||21.2%||56.8%||82.5%||94.3%||98.4%||99.6%||99.9%||100.0%||Snap||42%||655.8||Snap||275.4
|-
!Rifle
|30||100%||0-25||5.3||0%||0%||1.7%||6.1%||13.3%||22.5%||32.8%||43.4%||53.6%||62.7%||90.5%||98.3%||99.7%||100.0%||100.0%||100.0%||100.0%||Auto||24.5%||477.7||Auto||125.9
|-
!HC-AP
|56||100%||0-55||24.3||20.4%||49.6%||71.7%||85.4%||92.8%||96.6%||98.5%||99.3%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||42%||224.9||Snap||94.4
|-
!HC-HE
|52||100%||0-43||17.8||0%||22.5%||55.5%||79.2%||91.6%||97.0%||99.0%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||42%||279.3||Snap||117.3
|-
!AC-AP
|42||100%||0-49||14.4||0%||15.7%||36.5%||55.9%||71.1%||81.9%||89.1%||93.6%||96.3%||98.0%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||22.4%||289.7||Auto||74.4
|-
!AC-HE
|44||100%||0-31||11.0||0%||3.3%||19.7%||42.7%||63.8%||79.3%||89.0%||94.5%||97.4%||98.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||22.4%||318.2||Auto||81.5
|-
!RL-Sml
|75||100%||2-55||36.2||30.3%||79.6%||96.8%||99.7%||100.0%||100.0%||100.0%||100.0%||100.0%||100%||-||-||-||-||-||-||-||Aimed||80.5%||180.4||Snap||87.1
|-
!RL-Lge
|100||100%||15-55||46.9||60.4%||97.5%||100.0%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||Aimed||80.5%||132.4||Snap||63.9
|-
!LasPist
|46||100%||0-55||17.7||3.2%||25.5%||49.3%||68.1%||81.0%||89.2%||94.1%||96.8%||98.4%||99.2%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||19.6%||176.7||Auto||40.8
|-
!LasRfle
|60||100%||0-55||26.4||25.6%||56.0%||77.0%||88.9%||94.9%||97.8%||99.1%||99.6%||99.8%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||32.2%||103.9||Auto||42.6
|-
!HvyLas
|85||100%||0-55||34.7||47.4%||78.0%||91.8%||97.2%||99.1%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||35%||176.2||Snap||61.7
|-
!PlasPist
|52||100%||0-55||22.0||14.3%||41.6%||64.8%||80.4%||89.7%||94.8%||97.5%||98.8%||99.4%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||101.5||Auto||42.3
|-
!PlasRfle
|80||100%||0-55||33.5||44.1%||75.2%||90.2%||96.4%||98.8%||99.6%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||38.5%||74.5||Auto||39.7
|-
!HvyPlas
|115||100%||0-55||40.0||61.0%||87.9%||96.7%||99.2%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||65.3||Auto||36.2
|-
!SmlLnch
|90||80%||0-55||31.0||37.6%||68.1%||85.4%||93.8%||97.5%||99.0%||99.6%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||77%||213.5||Snap||87.7
|-
!Grenade
|50||100%||0-40||16.1||0%||16.8%||47.1%||72.4%||87.5%||94.9%||98.1%||99.3%||99.8%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"288.0"||n/a||n/a
|-
!PrxGrnd
|70||100%||0-55||33.3||22.5%||72.6%||94.3%||99.2%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"158.6"||n/a||n/a
|-
!HighEx
|110||100%||20-55||49.3||68.5%||99.4%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"99.1"||n/a||n/a
|-
!AlnGrnd
|90||100%||10-55||43.6||50.5%||93.6%||99.8%||100.0%||100%||-||-||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"117.0"||n/a||n/a
|-
!Blaster
|200||100%||55-55||55.0||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Launch||"100%"||"66.0"||n/a||n/a
|-
!StunRod
|65||80%||0-55||21.8||13.7%||39.2%||61.5%||77.3%||87.3%||93.1%||96.4%||98.2%||99.1%||99.6%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||n/a||n/a||n/a||Melee||100.5
|}
====Leader====
{| class="wikitable"
|+Ethereal Leader (health 55, front armour 40, under armour 40)
|-
!rowspan="2"|Weapon!!rowspan="2"|Pwr.!!rowspan="2"|Mod.!!rowspan="2"|Dmg. range!!rowspan="2"|Avg. per hit!!rowspan="2"|1HK!!rowspan="2"|2HK!!rowspan="2"|3HK!!rowspan="2"|4HK!!rowspan="2"|5HK!!rowspan="2"|6HK!!rowspan="2"|7HK!!rowspan="2"|8HK!!rowspan="2"|9HK!!rowspan="2"|10HK!!rowspan="2"|15HK!!rowspan="2"|20HK!!rowspan="2"|25HK!!rowspan="2"|30HK!!rowspan="2"|35HK!!rowspan="2"|40HK!!rowspan="2"|50HK!!colspan="3"|At range!!colspan="2"|Close combat
|-
!Mode!!Acc.!!%TU/kill!!Mode!!%TU/kill
|-
!Pistol
|26||100%||0-12||1.5||0%||0%||0%||0.0%||0.0%||0.1%||0.2%||0.6%||1.1%||2.0%||13.3%||34.6%||58.0%||76.5%||88.3%||94.7%||99.1%||Snap||42%||1063.5||Snap||446.7
|-
!Rifle
|30||100%||0-20||3.4||0%||0%||0.2%||1.0%||2.8%||6.0%||10.6%||16.5%||23.3%||30.7%||66.5%||87.9%||96.4%||99.1%||99.8%||100.0%||100.0%||Auto||24.5%||670.8||Auto||173.2
|-
!HC-AP
|56||100%||0-55||21.9||15.9%||42.3%||64.6%||79.7%||89.0%||94.3%||97.1%||98.6%||99.3%||99.7%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||42%||251.3||Snap||105.5
|-
!HC-HE
|52||100%||0-38||14.0||0%||11.6%||36.1%||60.5%||78.3%||89.1%||94.9%||97.7%||99.0%||99.6%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||42%||340.5||Snap||143.0
|-
!AC-AP
|42||100%||0-44||11.6||0%||9.8%||25.4%||42.4%||57.9%||70.4%||79.9%||86.8%||91.5%||94.6%||99.6%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||22.4%||340.5||Auto||86.1
|-
!AC-HE
|44||100%||0-26||7.8||0%||0.0%||5.8%||18.4%||34.9%||51.7%||66.3%||77.7%||85.9%||91.4%||99.5%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||22.4%||417.6||Auto||104.0
|-
!RL-Sml
|75||100%||0-55||32.6||23.7%||70.4%||92.4%||98.5%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||80.5%||200.5||Snap||96.9
|-
!RL-Lge
|100||100%||10-55||44.8||55.4%||94.8%||99.9%||100.0%||100%||-||-||-||-||-||-||-||-||-||-||-||-||Aimed||80.5%||139.6||Snap||67.4
|-
!LasPist
|46||100%||0-52||14.8||0%||16.6%||37.5%||56.4%||71.2%||81.7%||88.7%||93.3%||96.1%||97.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||19.6%||205.4||Auto||46.4
|-
!LasRfle
|60||100%||0-55||24.1||21.5%||49.7%||71.1%||84.6%||92.2%||96.2%||98.2%||99.2%||99.6%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||32.2%||113.2||Auto||45.2
|-
!HvyLas
|85||100%||0-55||33.1||44.4%||74.8%||89.8%||96.1%||98.6%||99.5%||99.8%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||35%||185.7||Snap||65.0
|-
!PlasPist
|52||100%||0-55||19.4||9.5%||33.2%||55.8%||72.8%||84.1%||91.1%||95.2%||97.4%||98.7%||99.3%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||114.0||Auto||46.4
|-
!PlasRfle
|80||100%||0-55||31.8||41.0%||71.6%||87.7%||95.1%||98.1%||99.3%||99.8%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||38.5%||78.0||Auto||40.7
|-
!HvyPlas
|115||100%||0-55||38.8||58.9%||86.2%||95.9%||98.8%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||67.0||Auto||36.5
|-
!SmlLnch
|90||80%||0-55||29.1||34.3%||63.8%||81.9%||91.5%||96.2%||98.4%||99.3%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||77%||228.9||Snap||94.0
|-
!Grenade
|50||100%||0-35||12.4||0%||7.3%||27.6%||51.0%||70.3%||83.5%||91.5%||95.8%||98.1%||99.1%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"357.3"||n/a||n/a
|-
!PrxGrnd
|70||100%||0-55||29.4||15.5%||61.5%||87.6%||96.9%||99.4%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"179.4"||n/a||n/a
|-
!HighEx
|110||100%||15-55||47.6||64.0%||97.9%||100.0%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"103.6"||n/a||n/a
|-
!AlnGrnd
|90||100%||5-55||41.0||45.1%||89.1%||99.1%||100.0%||100.0%||100.0%||100%||-||-||-||-||-||-||-||-||-||-||Throw||"100%"||"125.1"||n/a||n/a
|-
!Blaster
|200||100%||55-55||55.0||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Launch||"100%"||"66.0"||n/a||n/a
|-
!StunRod
|65||80%||0-55||19.2||9.2%||30.9%||52.4%||69.2%||81.0%||88.7%||93.4%||96.3%||97.9%||98.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||n/a||n/a||n/a||Melee||115.1
|}

===Cyberdisc===

{| class="wikitable"
|+Cyberdisc (health 120, front armour 34, under armour 34)
|-
!rowspan="2"|Weapon!!rowspan="2"|Pwr.!!rowspan="2"|Mod.!!rowspan="2"|Dmg. range!!rowspan="2"|Avg. per hit!!rowspan="2"|1HK!!rowspan="2"|2HK!!rowspan="2"|3HK!!rowspan="2"|4HK!!rowspan="2"|5HK!!rowspan="2"|6HK!!rowspan="2"|7HK!!rowspan="2"|8HK!!rowspan="2"|9HK!!rowspan="2"|10HK!!rowspan="2"|15HK!!rowspan="2"|20HK!!rowspan="2"|25HK!!rowspan="2"|30HK!!rowspan="2"|35HK!!rowspan="2"|40HK!!rowspan="2"|50HK!!colspan="3"|At range!!colspan="2"|Close combat
|-
!Mode!!Acc.!!%TU/kill!!Mode!!%TU/kill
|-
!Pistol
|26||80%||0-7||0.7||0%||0%||0%||0%||0%||0%||0%||0%||0%||0.0%||0.0%||0.0%||0.6%||3.4%||11.0%||24.1%||57.8%||Snap||42%||2115.1||Snap||888.3
|-
!Rifle
|30||80%||0-14||2.0||0%||0%||0%||0%||0%||0%||0.0%||0.0%||0.0%||0.0%||1.8%||13.2%||36.9%||63.1%||82.2%||92.7%||99.1%||Auto||24.5%||1366-1415||Auto||346.5
|-
!HC-AP
|56||80%||0-55||17.1||0%||0%||4.9%||16.8%||33.2%||50.4%||65.4%||77.2%||85.6%||91.3%||99.5%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||42%||539.6||Snap||226.6
|-
!HC-HE
|52||60%||0-30||3.6||0%||0%||0.0%||0.0%||0.7%||4.8%||15.3%||32.0%||50.9%||67.8%||98.5%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||42%||762.8||Snap||320.4
|-
!AC-AP
|42||80%||0-33||8.1||0%||0%||0%||0.2%||1.5%||4.9%||10.9%||19.3%||29.5%||40.6%||83.7%||97.4%||99.7%||100.0%||100.0%||100.0%||100.0%||Auto||22.4%||718.6||Auto||171.3
|-
!AC-HE
|44||60%||0-5||0.6||0%||0%||0%||0%||0%||0%||0.0%||0.0%||0.0%||0.0%||0.6%||8.4%||28.8%||53.8%||74.1%||86.9%||97.3%||Auto||22.4%||1839-1900||Auto||425.4
|-
!RL-Sml
|75||60%||0-120||39.4||0.0%||28.6%||83.8%||98.5%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||80.5%||269.5||Snap||130.2
|-
!RL-Lge
|100||60%||0-120||94.3||33.0%||98.3%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||80.5%||157.2||Snap||75.9
|-
!LasPist
|46||100%||0-58||18.4||0%||0.1%||6.8%||21.0%||39.0%||56.4%||70.8%||81.5%||88.8%||93.5%||99.7%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||19.6%||284.6||Auto||62.6
|-
!LasRfle
|60||100%||0-86||30.9||0%||12.2%||36.0%||59.5%||76.9%||87.8%||94.0%||97.2%||98.7%||99.4%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||32.2%||165.7||Auto||60.4
|-
!HvyLas
|85||100%||0-120||53.7||9.9%||45.9%||73.5%||88.6%||95.5%||98.4%||99.4%||99.8%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||35%||272.4||Snap||95.3
|-
!PlasPist
|52||100%||0-70||23.7||0%||3.5%||18.4%||39.2%||59.1%||74.7%||85.3%||91.9%||95.7%||97.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||163.3||Auto||63.5
|-
!PlasRfle
|80||100%||0-120||49.6||4.3%||39.0%||68.3%||85.5%||94.0%||97.7%||99.1%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||38.5%||109.3||Auto||48.3
|-
!HvyPlas
|115||100%||0-120||70.9||33.3%||70.4%||89.3%||96.6%||99.0%||99.7%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||83.1||Auto||38.9
|-
!SmlLnch
|90||100%||0-120||113.6||84.1%||99.5%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||77%||113.3||Snap||46.5
|-
!Grenade
|50||60%||0-26||2.3||0%||0%||0.0%||0.0%||0.0%||0.5%||2.6%||8.3%||18.1%||31.3%||86.9%||98.8%||99.9%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"913.2"||n/a||n/a
|-
!PrxGrnd
|70||60%||0-107||29.9||0%||9.6%||60.4%||92.3%||99.1%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"254.0"||n/a||n/a
|-
!HighEx
|110||60%||0-120||107.4||59.2%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"105.7"||n/a||n/a
|-
!AlnGrnd
|90||60%||0-120||74.7||9.6%||89.2%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"151.1"||n/a||n/a
|-
!Blaster
|200||60%||113-120||120.0||100.0%||100%||-||-||-||-||-||-||-||-||-||-||-||-||-||-||-||Launch||"100%"||"66.0"||n/a||n/a
|-
!StunRod
|65||100%||0-96||35.5||0%||15.7%||40.0%||62.2%||78.2%||88.2%||94.0%||97.0%||98.6%||99.3%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||n/a||n/a||n/a||Melee||128.2
|}

===Sectopod===
====Front====
{| class="wikitable"
|+Sectopod (health 96, front armour 145, under armour 90)
|-
!rowspan="2"|Weapon!!rowspan="2"|Pwr.!!rowspan="2"|Mod.!!rowspan="2"|Dmg. range!!rowspan="2"|Avg. per hit!!rowspan="2"|1HK!!rowspan="2"|2HK!!rowspan="2"|3HK!!rowspan="2"|4HK!!rowspan="2"|5HK!!rowspan="2"|6HK!!rowspan="2"|7HK!!rowspan="2"|8HK!!rowspan="2"|9HK!!rowspan="2"|10HK!!rowspan="2"|15HK!!rowspan="2"|20HK!!rowspan="2"|25HK!!rowspan="2"|30HK!!rowspan="2"|35HK!!rowspan="2"|40HK!!rowspan="2"|50HK!!colspan="3"|At range!!colspan="2"|Close combat
|-
!Mode!!Acc.!!%TU/kill!!Mode!!%TU/kill
|-
!Pistol
|26||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Snap||42%||∞||Snap||∞
|-
!Rifle
|30||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||24.5%||∞||Auto||∞
|-
!HC-AP
|56||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Snap||42%||∞||Snap||∞
|-
!HC-HE
|52||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Snap||42%||∞||Snap||∞
|-
!AC-AP
|42||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||22.4%||∞||Auto||∞
|-
!AC-HE
|44||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||22.4%||∞||Auto||∞
|-
!RL-Sml
|75||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Aimed||80.5%||∞||Snap||∞
|-
!RL-Lge
|100||80%||0-96||13.1||0.0%||0.9%||7.8%||24.0%||45.2%||65.1%||80.1%||89.6%||95.0%||97.7%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||80.5%||555.4||Snap||268.3
|-
!LasPist
|46||150%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||19.6%||∞||Auto||∞
|-
!LasRfle
|60||150%||0-35||3.5||0%||0%||0.0%||0.1%||0.4%||0.9%||1.7%||2.8%||4.3%||6.2%||20.6%||39.9%||58.8%||73.9%||84.5%||91.3%||97.6%||Auto||32.2%||868-904||Auto||291.1
|-
!HvyLas
|85||150%||0-96||23.4||5.8%||19.0%||34.3%||48.7%||61.1%||71.2%||79.1%||85.0%||89.4%||92.6%||98.9%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||35%||499.0||Snap||174.7
|-
!PlasPist
|52||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||35%||∞||Auto||∞
|-
!PlasRfle
|80||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||38.5%||∞||Auto||∞
|-
!HvyPlas
|115||80%||0-39||4.1||0%||0%||0.1%||0.4%||1.0%||1.9%||3.4%||5.3%||7.7%||10.5%||29.9%||51.7%||70.1%||83.0%||90.9%||95.4%||99.0%||Auto||35%||719-753||Auto||263.4
|-
!SmlLnch
|90||100%||0-96||59.3||27.8%||71.3%||91.5%||97.9%||99.5%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||77%||206.6||Snap||84.8
|-
!Grenade
|50||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Throw||"100%"||∞||n/a||n/a
|-
!PrxGrnd
|70||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Throw||"100%"||∞||n/a||n/a
|-
!HighEx
|110||80%||0-96||28.9||1.0%||20.9%||55.5%||81.1%||93.5%||98.1%||99.5%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"263.0"||n/a||n/a
|-
!AlnGrnd
|90||80%||0-45||3.2||0%||0.0%||0.0%||0.0%||0.2%||0.9%||2.6%||5.8%||10.8%||17.7%||63.9%||91.4%||98.6%||99.8%||100.0%||100.0%||100.0%||Throw||"100%"||"1081.4"||n/a||n/a
|-
!Blaster
|200||80%||0-96||95.4||97.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Launch||"100%"||"67.4"||n/a||n/a
|-
!StunRod
|65||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||n/a||n/a||n/a||Melee||∞
|}

====Side====
{| class="wikitable"
|+Sectopod (health 96, side armour 130, under armour 90)
|-
!rowspan="2"|Weapon!!rowspan="2"|Pwr.!!rowspan="2"|Mod.!!rowspan="2"|Dmg. range!!rowspan="2"|Avg. per hit!!rowspan="2"|1HK!!rowspan="2"|2HK!!rowspan="2"|3HK!!rowspan="2"|4HK!!rowspan="2"|5HK!!rowspan="2"|6HK!!rowspan="2"|7HK!!rowspan="2"|8HK!!rowspan="2"|9HK!!rowspan="2"|10HK!!rowspan="2"|15HK!!rowspan="2"|20HK!!rowspan="2"|25HK!!rowspan="2"|30HK!!rowspan="2"|35HK!!rowspan="2"|40HK!!rowspan="2"|50HK!!colspan="3"|At range!!colspan="2"|Close combat
|-
!Mode!!Acc.!!%TU/kill!!Mode!!%TU/kill
|-
!Pistol
|26||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Snap||42%||∞||Snap||∞
|-
!Rifle
|30||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||24.5%||∞||Auto||∞
|-
!HC-AP
|56||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Snap||42%||∞||Snap||∞
|-
!HC-HE
|52||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Snap||42%||∞||Snap||∞
|-
!AC-AP
|42||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||22.4%||∞||Auto||∞
|-
!AC-HE
|44||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||22.4%||∞||Auto||∞
|-
!RL-Sml
|75||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Aimed||80.5%||∞||Snap||∞
|-
!RL-Lge
|100||80%||0-96||13.1||0.0%||0.9%||7.8%||24.0%||45.2%||65.1%||80.1%||89.6%||95.0%||97.7%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||80.5%||555.4||Snap||268.3
|-
!LasPist
|46||150%||0-8||0.3||0%||0%||0%||0%||0%||0%||0%||0.0%||0.0%||0.0%||0.0%||0.0%||0.0%||0.0%||0.0%||0.0%||0.2%||Auto||19.6%||>5612||Auto||>1100
|-
!LasRfle
|60||150%||0-50||7.0||0%||0.2%||1.2%||3.3%||6.6%||11.0%||16.4%||22.4%||28.8%||35.4%||65.4%||84.4%||93.8%||97.7%||99.2%||99.8%||100.0%||Auto||32.2%||500.3||Auto||168.8
|-
!HvyLas
|85||150%||0-96||29.0||11.7%||29.7%||47.5%||62.5%||74.0%||82.5%||88.4%||92.5%||95.2%||96.9%||99.7%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||35%||399.8||Snap||139.9
|-
!PlasPist
|52||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||35%||∞||Auto||∞
|-
!PlasRfle
|80||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||38.5%||∞||Auto||∞
|-
!HvyPlas
|115||80%||0-54||7.9||0%||0.5%||2.1%||5.1%||9.6%||15.1%||21.6%||28.5%||35.6%||42.7%||72.3%||88.8%||96.0%||98.7%||99.6%||99.9%||100.0%||Auto||35%||432.9||Auto||159.1
|-
!SmlLnch
|90||100%||0-96||59.3||27.8%||71.3%||91.5%||97.9%||99.5%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||77%||206.6||Snap||84.8
|-
!Grenade
|50||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Throw||"100%"||∞||n/a||n/a
|-
!PrxGrnd
|70||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Throw||"100%"||∞||n/a||n/a
|-
!HighEx
|110||80%||0-96||28.9||1.0%||20.9%||55.5%||81.1%||93.5%||98.1%||99.5%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"263.0"||n/a||n/a
|-
!AlnGrnd
|90||80%||0-45||3.2||0%||0.0%||0.0%||0.0%||0.2%||0.9%||2.6%||5.8%||10.8%||17.7%||63.9%||91.4%||98.6%||99.8%||100.0%||100.0%||100.0%||Throw||"100%"||"1081.4"||n/a||n/a
|-
!Blaster
|200||80%||0-96||95.4||97.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Launch||"100%"||"67.4"||n/a||n/a
|-
!StunRod
|65||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||n/a||n/a||n/a||Melee||∞
|}

====Rear====
{| class="wikitable"
|+Sectopod (health 96, rear armour 100, under armour 90)
|-
!rowspan="2"|Weapon!!rowspan="2"|Pwr.!!rowspan="2"|Mod.!!rowspan="2"|Dmg. range!!rowspan="2"|Avg. per hit!!rowspan="2"|1HK!!rowspan="2"|2HK!!rowspan="2"|3HK!!rowspan="2"|4HK!!rowspan="2"|5HK!!rowspan="2"|6HK!!rowspan="2"|7HK!!rowspan="2"|8HK!!rowspan="2"|9HK!!rowspan="2"|10HK!!rowspan="2"|15HK!!rowspan="2"|20HK!!rowspan="2"|25HK!!rowspan="2"|30HK!!rowspan="2"|35HK!!rowspan="2"|40HK!!rowspan="2"|50HK!!colspan="3"|At range!!colspan="2"|Close combat
|-
!Mode!!Acc.!!%TU/kill!!Mode!!%TU/kill
|-
!Pistol
|26||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Snap||42%||∞||Snap||∞
|-
!Rifle
|30||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||24.5%||∞||Auto||∞
|-
!HC-AP
|56||100%||0-12||0.7||0%||0%||0%||0%||0%||0.0%||0.0%||0.0%||0.0%||0.0%||0.0%||0.1%||0.4%||1.4%||3.5%||7.1%||19.7%||Snap||42%||5460.5||Snap||2293.4
|-
!HC-HE
|52||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Snap||42%||∞||Snap||∞
|-
!AC-AP
|42||100%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||22.4%||∞||Auto||∞
|-
!AC-HE
|44||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||22.4%||∞||Auto||∞
|-
!RL-Sml
|75||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Aimed||80.5%||∞||Snap||∞
|-
!RL-Lge
|100||80%||0-96||13.1||0.0%||0.9%||7.8%||24.0%||45.2%||65.1%||80.1%||89.6%||95.0%||97.7%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||80.5%||555.4||Snap||268.3
|-
!LasPist
|46||150%||0-38||5.3||0%||0%||0.2%||0.8%||2.0%||4.1%||7.0%||10.8%||15.3%||20.5%||49.7%||73.9%||88.3%||95.3%||98.3%||99.4%||99.9%||Auto||19.6%||716.1||Auto||147.1
|-
!LasRfle
|60||150%||0-80||17.9||0%||7.6%||19.7%||33.5%||47.0%||59.1%||69.2%||77.2%||83.5%||88.2%||98.2%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||32.2%||236.9||Auto||83.7
|-
!HvyLas
|85||150%||0-96||40.2||23.4%||49.0%||68.7%||81.8%||89.8%||94.5%||97.1%||98.5%||99.2%||99.6%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Snap||35%||281.6||Snap||98.6
|-
!PlasPist
|52||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Auto||35%||∞||Auto||∞
|-
!PlasRfle
|80||80%||0-28||3.0||0%||0%||0%||0.0%||0.1%||0.3%||0.6%||1.2%||2.1%||3.3%||15.4%||34.8%||55.4%||72.5%||84.4%||91.8%||98.1%||Auto||38.5%||794-826||Auto||317.9
|-
!HvyPlas
|115||80%||0-84||19.1||0%||8.8%||22.2%||36.9%||50.8%||62.8%||72.6%||80.2%||86.0%||90.2%||98.6%||99.8%||100.0%||100.0%||100.0%||100.0%||100.0%||Auto||35%||214.9||Auto||82.4
|-
!SmlLnch
|90||100%||0-96||59.3||27.8%||71.3%||91.5%||97.9%||99.5%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Aimed||77%||206.6||Snap||84.8
|-
!Grenade
|50||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Throw||"100%"||∞||n/a||n/a
|-
!PrxGrnd
|70||80%||0-0||'''0.0'''||colspan="17" style="text-align:center;"|immune||Throw||"100%"||∞||n/a||n/a
|-
!HighEx
|110||80%||0-96||28.9||1.0%||20.9%||55.5%||81.1%||93.5%||98.1%||99.5%||99.9%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Throw||"100%"||"263.0"||n/a||n/a
|-
!AlnGrnd
|90||80%||0-45||3.2||0%||0.0%||0.0%||0.0%||0.2%||0.9%||2.6%||5.8%||10.8%||17.7%||63.9%||91.4%||98.6%||99.8%||100.0%||100.0%||100.0%||Throw||"100%"||"1081.4"||n/a||n/a
|-
!Blaster
|200||80%||0-96||95.4||97.8%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||100.0%||Launch||"100%"||"67.4"||n/a||n/a
|-
!StunRod
|65||100%||0-30||3.5||0%||0%||0%||0.0%||0.0%||0.1%||0.3%||0.6%||1.1%||1.7%||9.0%||23.0%||40.5%||57.8%||72.1%||82.7%||94.3%||n/a||n/a||n/a||Melee||893.0
|}

Skipping Laser Weapons

2025-04-18T10:04:32Z

Magic9mushroom: going straight to Heavy Plasma isn't the worst idea in the world

[[Skipping Laser Weapons]] is the strategy of skipping research on laser weapons entirely, and instead immediately researching plasma weapons (usually the [[Plasma Rifle]] or [[Heavy Plasma]] Gun, for reasons discussed below). Veteran players of UFO: Enemy Unknown typically consider this a suboptimal choice, but there is at least one well-known challenge which makes it worthwhile. This page will explain why skipping laser weapons is generally a bad idea, but also describe the situations in which it's worthwhile and how best to employ the strategy.

Article written by [[User:Magic9mushroom|magic9mushroom]].

==Why lasers are worthwhile==
Skipping laser weapons appears, from a naïve perspective, to be a great idea. If you're eventually going to abandon the [[Laser Rifle]] in favour of [[Heavy Plasma]], why bother getting the former at all? Well, there are several reasons, most relating to the first few months of UFO.

*First and foremost: until you assault your first UFO and get your hands on some alien artefacts, there's not much else worth researching. The [[Motion Scanner]] isn't particularly useful, and the [[Medi-Kit]] is less effective early on, because unarmoured rookies usually die in one hit and don't cost much more to replace than a Medi-Kit costs to produce. Lasers also get your ten starting engineers doing something productive early on.
*Plasma weapons need ammunition, while lasers do not. This is rarely a problem in a tactical sense - all plasma weapons have large clip sizes - but unless you deliberately conserve ammunition, it can be difficult to recover more clips of your chosen type than you use in every mission. This goes double if you're shooting for the [[Heavy Plasma]], because only a small proportion of aliens will carry the weapon early on.
*Lasers are researched very quickly - you receive the [[Laser Pistol]] after a mere 150 scientist-days, and the [[Laser Rifle]] 300 scientist-days after that (450 total). Unlocking the [[Plasma Rifle]] takes 1100 scientist-days (700 for the weapon, and 400 for the ammo). As such, researching plasma weapons early on will delay other important projects such as the [[Hyper-Wave Decoder]], and you're on the clock to develop some form of energy weapon, because of...
*Cyberdiscs. Your first Sectoid [[Terror Site]] will probably occur somewhere between January and March, and if you don't have energy weapons deployed, it's going to suck. Cyberdiscs have significant armour and a resistance to both Armour Piercing and High Explosive damage, making the standard [[Rifle]] nearly useless and even the [[Auto-Cannon]] and [[Heavy Cannon]] quite underwhelming. The [[Rocket Launcher]] and [[High Explosive]] ''will'' work on Cyberdiscs, but both are heavy, unwieldy weapons; energy weapons fire much more quickly and can be handed out to the whole squad. Plasma weapons inflict even more damage than lasers, but it's a smaller improvement compared to the enormous gulf between conventional weapons and lasers (for a single soldier with 100 Firing Accuracy, it takes on average 2/3 of a turn to kill a Cyberdisc with Heavy Plasma, 1 turn with a Plasma Rifle, and 1.5 turns with a Laser Rifle... but a bit over 4 turns with a Heavy Cannon, and almost 8 with an Auto-Cannon).
*There's also a significant opportunity cost to using plasma weapons, because the weapons themselves fetch very high prices when sold. A 14-man squad equipped with Plasma Rifles is using over 1.8 million dollars worth of equipment, not even counting the ongoing cost of clips; a squad using Laser Rifles only carries $500,000 worth. The difference could buy you 15 more scientists and their first month of pay, or a new radar base. Heavy Plasma Guns are even more expensive.

Between all these reasons, it's generally considered standard to immediately research and deploy the [[Laser Pistol]] and [[Laser Rifle]]. After a few months, when you've amassed a large stockpile of Heavy Plasma ammunition (and the aliens are employing it more often), money isn't as tight, [[Muton|tougher]] [[Ethereal|aliens]] are showing up, and you've got a little more freedom in your research, it's certainly worthwhile to switch over, but not right out of the gate.

There is one notable exception...

==Council Funding only==

One of the more well-known challenges, the rules of the "Council Funding only" scenario are that X-Com may not sell any manufactured or looted items. This immediately obviates the opportunity cost of plasma weaponry - because you can't sell it anyway - and makes the manufacturing cost of Laser Rifles much more noticeable. The [[Medi-Kit]] is also slightly more relevant. As such, [[Skipping Laser Weapons]] is actually a fairly-good idea.

===Which one?===
There are, of course, three plasma weapons to choose from, and each has to be researched separately from the others. With fewer scientists in this challenge (due to the expense), simply researching all of them is not feasible.

*The [[Plasma Pistol]] is the quickest to research, at 1000 scientist-days, but does not unlock [[Plasma Beam]] research and is quite weak (only 52 power, less than a Laser Rifle!). The Plasma Pistol also becomes rare from March onward, disappearing entirely at the start of June.
*The [[Plasma Rifle]] takes 1100 scientist-days to research, unlocks the Plasma Beam and is the most accurate Snap and Auto weapon in the game. It deals an average 80 damage. The Plasma Rifle appears regularly until the end of July, disappearing entirely at the start of September.
*The [[Heavy Plasma]] Gun is the most damaging weapon (average 115), but is subject to the aforementioned limited availability for the first few months. It also takes 1200 scientist-days to research, but unlocks the Plasma Beam.

Generally, the Plasma Rifle is the best choice early on, though it may become necessary to switch over to Heavy Plasma when the supply starts to dry up.

User talk:Magic9mushroom

2025-04-18T07:08:38Z

Magic9mushroom: /* i have OA backups */

== Rolling back NKF ==

Hi, and thanks for the heads-up. But my stance is to trust that wikipedia's ''[[wikipedia:Wikipedia:WAIN#Adminship_is_not_a_trophy|What adminship is not]]'' still applies here, particularly when it says that "An admin is just a normal user with a mop and a bucket." Are you implying that here they are exempt from the practice of resolving disputes through discussion? Anyway, IMO that stage wasn't reached yet, and i see no point worrying about "what if NKF disagrees about my revert?" until i'll know that he does... -- [[User:Jokes_Free4Me|Jokes_Free4Me]] ([[User_talk:Jokes_Free4Me|talk]]) 22:05, 9 April 2015 (EDT)

:I was not implying that NKF is exempt from resolving disputes through discussion. I was merely suggesting for the future that engaging in such discussion - on his talk page, perhaps - might be more prudent and courteous than rolling him back while yelling at him in all-caps. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 22:07, 11 April 2015 (EDT)

== Updates to UBK ==
Hey, I was looking at your "rewrite" section of the Base Layout Strategy:Talk page. I noticed that you used "lab"s as the default place holder to indicate any facility.
I have the image assets available to create an "empty room" tile that could be added to the UBK if you are interested. I reworked the UBK for the XPiratez mod of OpenXcom, and created all the tiles there, so it would be quite easy.
[[Template:UBK_Piratez]]

--[[User:IvanDogovich|IvanDogovich]] ([[User talk:IvanDogovich|talk]]) 13:02, 27 April 2016 (UTC)

:Well, I didn't make the UBK - NKF did - so he'd probably be the one to ask. I'm not sure it'd really clear anything up, though; since UBK's a copy of in-game pics, you'd still probably have to explain what the weird new graphic is. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 23:54, 27 April 2016 (UTC)
:Fair enough. :) Thanks for all the great work you have done to continue to make the Ufopaedia a vital resource --[[User:IvanDogovich|IvanDogovich]] ([[User talk:IvanDogovich|talk]]) 04:05, 28 April 2016 (UTC)
Thanks. It really helps to hear someone say that every so often. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 01:21, 29 April 2016 (UTC)

== Security Turrets in Alien Dimension (Apoc) ==

Hi Magic9mushroom

Ill try and screengrab a pic at some point, but there are disrupter pods on some alien buildings in battlescape
These do indeed fire if agents get close on UK CD-ROM (Original release) version

EDIT: These are the turrets...
https://media.discordapp.net/attachments/376028757183561728/481796205697957888/unknown.png?width=884&height=683

:Wow, the more you know. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 03:28, 23 August 2018 (CEST)

I guess they have the same flaw as X-com security turrets? I've never seen them fire on my agents in turn based mode. [[User:Jasonred79|Jasonred79]] ([[User talk:Jasonred79|talk]]) 18:07, 7 May 2022 (CEST)

== Zorium and Apoc Power ==
Hi magic9mushroom the final release does not contain this information no, but as we are talking about cut features i'm including the cut lore
Reason for linking the One Way to Win stuff was it refers to the eras of apoc development in which this was all covered
I'm trying to think of a way that this can all be incorporated without a long winded explanation
Will message again when ive had a think

No problem I have adjusted things to be clearer; let me know your thoughts.

:That makes more sense. Remind me where it says that the Alien Dimension is becoming inhospitable? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 14:09, 17 August 2019 (CEST)

==The pistol gif==
Hey man,tbh I’m on moblie site of this in safari tbh the pic on my screen was all white [[User:Michaelx2|Michaelx2]] ([[User talk:Michaelx2|talk]]) 13:21, 21 February 2020 (UTC)

:I believe you. It's just that if anyone can see it, the problem is likely on your end. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 22:38, 21 February 2020 (UTC)
::I’ll try to sent a new Gif of pistol to replace it
:::The image is fine. I can see it. The problem is on your end. Look for a fix on your end (such as reloading the image or checking whether Safari is allowing GIFs). [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 05:51, 22 February 2020 (UTC)

== Hi Magic9mushroom i can sand u converted Apoc files ==

Hi Magic9mushroom i can sand u converted Apoc files
here https://my-files.su/fyc4xb

== Yes i forgot to say that its graphics ==

Yes i forgot to say that its graphics ...
you can join our discord and some ppl can help you with code etc https://discord.com/invite/f8Rayre
i cant say about psionics for sure...

== Also about Unit Stat Box (EU2012) that used in XCom2 they became outdated ==

Also about Unit Stat Box (EU2012) that used in XCom2 they became outdated
so if u can modify them here good example from
https://xcom.fandom.com/wiki/Faceless_(XCOM_2)?action=edit

{{Infobox XCOM2enemy
|name = Faceless
|image = File:XCOM2_Faceless.png
|aim =60/75/75/75
|critchance = 0/15/15/15
|defense = 0/0/0/0
|health = 8/10/10/12
|mobility = 12/14/14/14
|will = 50/50/70/70
|weapon = Claws (3-4 damage)
|abilities =Regeneration, Leap
}}

== strange beacose i take color samples from apoc game interface ==

strange beacose i take color samples from apoc game interface

== Request - Apoc'd ==

Do you know how whether it's possible to have an organisation conduct a raid against X-COM using Apoc'd? If so, how? Thanks. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 07:48, 15 July 2020 (UTC)

:Yes. Savedgames -> desired savegame -> Organised Crime. Set the organisation to the one you want to raid you, the target to the desired X-COM base, the action to Raid or Storm, and the time remaining to something other than 0.

:Note that if the organisation is not hostile, the invaders will count as neutrals and neither they nor your forces will open fire immediately. If you want to simulate a real base defence, you need to annoy them first (pointless investigations are the simplest way). [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 09:18, 15 July 2020 (UTC)

::Thanks, that worked fine for a new game, but it doesn't seem to work when I try it with my existing game that's currently at Week 6 (I've even tried waiting for the next day and there's still no raid).
::That aside, I've discovered two pieces of random and probably useless information while fiddling around with this: setting the raiding Organisation to "X-COM" or "Civilian" will get you the "base under attack" screen followed by the time jumping forward straight to the first Alien Alert, while setting it to "Alien" will get your base attacked by the crew of a Mothership. Yes, crew, not infiltration force, so there will be Megaspawn and Psimorphs. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 19:18, 15 July 2020 (UTC)
:: That doesn't sound useless, that sounds EXTREMELY FUN!!! ... I'd love to experience a base defence with Megaspawn and Psimorphs! Watching psimorphs going up against security stations will just be sadistic lol [[User:Jasonred79|Jasonred79]] ([[User talk:Jasonred79|talk]]) 18:11, 7 May 2022 (CEST)

:Dunno what's going on there; all I can say is it works fine for me even in games that have been going on for a while. Megapol doesn't seem to want to launch illegal flyers, but otherwise it seems to work. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 08:59, 16 July 2020 (UTC)

== Overspawn Bug Deletion ==
No evidence? The purple segments (multiple with various window patterns) of transtellar apartments et al. on the superhuman map (located up near the north-east corner) will have an overspawn just walk straight thru the building AND any other building that has those particular segments. Craft stop firing because the overspawn is '''inside''' the segment. I'm sure this that is a bug in all sense of the word. I request you put that listing back.

Please use a little more caution in future.

:Lolz, ironic echo. Nice.

:More seriously, insofar as the segments are set to be able to be walked through that's technically not a bug (the program is doing what it's told, it's just told to do something dumb). Just about anything you can fix with Apoc'd is not strictly a bug for this reason (as Apoc'd only changes data tables, not code). You only mentioned trees, which probably were deliberately made walkable so as not to slow down the Overspawn destroying them - I've also seen that the roads are set this way (though the supports for them are not) which may also be deliberate. If you'd mentioned those buildings rather than ranting about "a big ugly baby" in mainspace I would have been less inclined to just blank it.

:Now, the thing with the purple buildings is an anomaly and could be considered a design flaw, so feel free to put that under that heading. Suggesting making ''all'' tiles unwalkable for the Overspawn is probably a cure worse than the disease, though. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 13:24, 6 August 2020 (UTC)

Thanks for the prompt reply. I've tried to inject a little humour with that baby reference but this place serious business. Point Noted. "...technically not a bug (the program is doing what it's told, it's just told to do something dumb)..." quite so.

:It's not so much that the whole place is super serious - humour's fine in talk pages and some of the less precise or opinion articles (see: Weapon Analysis). But Known Bugs is a pretty crucially important page and being exact is necessary to avoid confusion. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 15:03, 6 August 2020 (UTC)

== Apocalypse question ==

Hi, I was wondering if you knew whether being allied to an Organisation in Apocalypse has any "hidden" in-game effects? There are lots of internet rumours about this (e.g. allying with a gang gives more human recruits, allying with Technocrats makes smaller organisations friendlier...), and the Tips Book makes similar claims. However, from what I've observed, I'm 99% sure none of this was actually implemented. But it would be nice to have confirmation obtained by looking at the game code. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 22:34, 5 May 2022 (CEST)

:I'm not a primary code digger. What I do know from Skin36's work is that relations with factions are irrelevant to new hires with the sole exception that hybrid/android recruits are removed if you have <0 relations with the Mutants/SELF.

:I'm not aware of any hidden relations effects, besides the ones from factions' (hidden) relationship with the Aliens (factions allied with the Aliens will refuse X-Com bribes; I forget whether this is also why you never get Alerts from CoS temples or if that's a ''sui generis'' case). There is, however, the basic principle of Apocalypse relations to consider: "if faction A attacks faction B, then faction C that disliked B will start liking A and faction D that liked B will start disliking A". This principle, applied over many iterations, ''can'' work some magic. This is, for instance, why Marsec and the gangs are substantially more likely than usual to go hostile, despite having zero starting relations with both you and the aliens - they hate Megapol, so when the UFOs blow up Megapol cars and buildings they start liking the aliens, so when you blow up aliens they start disliking you. So it's not ''ridiculous'' to say that getting the Technocrats to like you might be good for getting some of the enemies of the Marsec/Solmine/Extropian/Transtellar alliance to like you. On the other hand, any relations process that routes through somebody non-militarised (i.e. not player/aliens/Megapol/gangs/infiltrated) performing attacks is going to take forever to work, because non-militarised factions don't attack people very often. And of course you can't ''see'' most of the relations grid, and it's partially random, so any attempts at more than the most basic manipulations are blind unless you cheat. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 17:49, 26 May 2022 (CEST)

:: Ok, thx. I'll run a couple more in-game tests just to make sure, but everything seems to point towards the conclusion that the Tips Book's claims about the effects of alliances are wrong (and I'll revert the edit accordingly after I'm reasonably certain).
:: <s>One more thing I've wanted to ask - could you remind me how the game rounds numbers, again? In particular, I'd like to put the exact numbers of guards/henchmen employed by an organization in the appropriate table.</s> Figured it out. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 15:40, 2 June 2022 (CEST)
:: <s>I've contacted Filmboy84 via Discord. His info directly contradicts Skin36's, as he claims the Tips Book is essentially correct, though the effects are minimal. Allying with a gang makes it more likely that the max number of recruits turns up. Apparently what affects the number of recruits is much more complex than it seems at first glance. It's apparently modified by your relations with several organizations, both positive and negative.</s> Filmboy is wrong. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 19:44, 16 June 2022 (CEST)
:::Yeah, I did kinda suspect Skin36 knew his stuff; he's walked me through .exe hacks before. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 14:29, 16 October 2023 (CEST)

==Hello==
If anything is found, please update the page: [[Organizations]]. I've just rewrittnen it (removed relations). 
...any feedback positive or negative, please post to my talk page about my recent actions (March 2022 to present) since I'm thinking I might be 'stepping on peoples toes' by rewriting quite a few pages. [[User:EsTeR|EsTeR]] ([[User talk:EsTeR|talk]]) 14:27, 17 June 2022 (CEST)

==Note==
I just came here to cross off some old stuff that has been resolved in the meantime as well as to say I greatly appreciate all the work you've put into the wiki, and hope you get better soon. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 16:26, 30 September 2023 (CEST)

== Known Bugs (TFTD) ==

I'd like to try cleaning this page up a bit, if that's ok: https://www.ufopaedia.org/index.php/Known_Bugs_(TFTD) 
1. I'd remove the entire "Exploits" section because 1) exploits are not really bugs, and 2) the one exploit listed requires actually editing game files - if you're doing that, you can just as well simply give yourself a bunch of money instead. 
2. I'm not sure about the "questionable logic" section either. The things listed there more like unrealistic features (mostly bad physics), but not bugs. 
3. I'd put all the bugs under two basic categories: Geoscape Bugs and Battlescape Bugs, and then list sections under each of them as appropriate. 
4. "The Deep One attack looks like the Celatid spit / mortar (holdover from UFO)" - As far as I know, it's not the attack that's weird, but the graphical presentation, i.e. Deep Ones ''are'' supposed to be carrying some kind of mortar-like weapon, but are instead depicted as having an innate spitting attack. Or am I missing something here? 
5. "'Medic Cannon' - USO being armed with 1/0 weapons, the 'weapon' being 'medic' shown as a purple rank badge with commander's chains. with an ammunition capacity of two, but without any rounds for it. (...)" - I assume this is supposed to say "X-COM sub" instead of "USO". 
6. Can TFTD Extender cause issues of its own? I sort of remember it can cause aliens to spawn in inaccessible places, but I might be misremembering. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 12:45, 8 November 2023 (CET)

: #1 - reasonable. #2 - I think that the "MC works on non-implanted people" thing needs to be explicitly mentioned somewhere (not necessarily this article), and having a single mention of TFTD treating water like air might be reasonable, but hammering it in like that section does is definite overkill. #3 - good. #4 - this doesn't even seem like a bug to me. #5 - I don't have information on this. #6 - TFTD Extender isn't the same as XcomUtil. The "stuck" aliens [[Talk:Artefact_Site|are apparently a thing in vanilla]], but XcomUtil may worsen the chances of them showing up. I know that Sherlock's route fixes [https://www.strategycore.co.uk/forums/topic/12679-strange-things-in-tftd/ break a lot of maps] (if non-fatally) due to the limits of ROUTES.DAT and the alien spawn algorithm. I've never used TFTD Extender so I don't know if it causes any bugs of its own; I'd suspect mostly not, though, as Tycho has a rather-deep understanding of the X-Com engine to the point of being able to straight-up add functionality. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 01:39, 9 November 2023 (CET)

==STOP==

...and if you don't I make sure you lose you admin status and possibly get banned for vandalism. [[User:EsTeR|EsTeR]] ([[User talk:EsTeR|talk]])

:EsTeR, I mentioned that I was intent on reverting a lot of your edits (not all of them; your addition of images in particular is great work, and I intend to preserve the use of all the ones that aren't duplicative), and intent on using admin powers to make you back off if you attempted an edit war, ''in my request for admin powers'', because indeed it would have been duplicitous not to. I am not going behind anyone's back by doing this; I have approval. Feel free to tell whomever you like, but I do not believe you have the ability to carry out your threat.

:You've been told by quite a few editors that you were acting unilaterally without regard for consensus. You got as far as you did because the admins were AWOL and nobody had the sheer bloody-mindedness needed to fight an edit war against you. I really, truly ''do not'' want to block you, because you actually do a lot of good work when you are not trying to turn the wiki into a poorly-written strategy guide; as I've said in the past, you're not a troll, and you're certainly not a spambot. But the buttons are there. I am, seriously, still open to discussion with you about what does and doesn't work. But you no longer have the ability to just ram things through with brute force when people don't agree with you. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 15:09, 10 April 2025 (UTC)

::1. The only people I have interacted with since the Apoc section revamp are Magic9mushroom (conflict), Darkpast (conflict), Bard (one revert on the cheats page), Jasonred (banter), Hobbes (praise). And no one else. To claim that quite a few editors have had objections is FALSE. The only to two so that have objections are you and Darkpast because I edited the pages with last edits by you or Darkpast. ...so your are a proven LIAR.
2. Consensus is why nothing got done. Mainstream wikipedia is now a sad joke of an encylopedia because consensus is preferred over truth. If all the lefty admins agree on something, then thats the 'truth'. What happens when their little circle agrees on something even though it is false. ...because consensus makes them feel like they are right. ie: "too many cooks in the kitchen". This place apoc was templated by me to be (1) uniform, (2) easy to read without novelisation (terse wording and bullet points), (3) removal of vast amounts of repetativeness on multiple pages, (4) removal of simplistic grasp on the english language, (5) massive amount of input with new data and uniform pics.
3. Like I mentioned. The only two that have had conflict are you and Darkpast because I changed the pages which either of you 'last edited by' in the history list. IT IS OBVIOUS without a doubt that you have a had a dummy-spit because you think those pages are the be-end-all-end of finality ...that is why you changed Law Pistol and Chrysalis (and others) back to those last users and destroyed(ing) the flow and uniformness and other aspects as mentioned in the numbered points above. There is nothing wrong with either of those pages, so why did you change them? You haven't added anything constructive to it but just blantant rollback. eg: on the Chrysalis roll back there is no pics of what the thing looks like on the battlescape? ...so you made the page worse. I don't own the pages and neither do you - if you change them, ADD information to it to make it better for everyone and don't just roll back pages, it makes you look petty and gives me concrete proof that you are vandalising the apoc wiki.
4. I don't ram things through, I constructively edited (the numbered points above) the whole Apoc section. How can one get concensus of all involved when most are AWOL or disinterested? So without mass approval or agreement nothing gets done! ...and eventually half-arsed repetative articles appear throughout Apoc section without organisation. The -number one- reason did it so for OPENAPOC.
5. Change the articles as you seem fit to do so but don't destroy information. Build the pages to be better. [[User:EsTeR|EsTeR]] ([[User talk:EsTeR|talk]])
:"The only to two so that have objections are you and Darkpast because I edited the pages with last edits by you or Darkpast." - you're forgetting Gamer500018.
:I rolled back Lawpistol because you removed the UFOpaedia entry for its clip and because you put in nonsense advice (it is one-handed, so it should always be dual-wielded). I rolled back Chrysalis because you changed all the plurals to "Chrysalises" rather than the correct "Chrysalides", and because you bizarrely removed the infobox formatting. I did actually miss that I'd removed the battlescape images of Chrysalides; thanks and I'll re-add those.
:I do understand the value of uniformity. I'm going to edit ''all'' of the weapon and alien pages back to use infoboxes and (for weapons) the old, cleaner Battlescape images. I'm just not as fast as you, so it's not done yet. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 22:33, 13 April 2025 (UTC)

Wrong. the plural is "The plural of chrysalis is chrysalises. Find more words at wordhippo.com".

Gamer500018 was a (ex)user on here that made a throwaway account just so they could call me a troll.

Now your nitpicking:

"it is one-handed, so it should always be dual-wielded" Read what the official blurb is. Dual handed? Yeah one could, but be prepared to a backpack full of ammo and playing like that won't last long since stock levels are low for ammo. Essentially what i wrote. The official wording suggests that it is a back-up weapon, so that wht was I impled in the text.

the "ammunition for law pistol clip", "the ammuntion for..." etc. etc. official blurb were left out because they are not necessary. It doesn't add usefulness to the page.

The info-box become large and take up alot of space if you resize the pic to bigger than a postage stamp. The article then has a lot of empty space which is not necessary and a waste of space... and it looks stupid and ametuerish.

I don't know why you are doing it? The Apoc section has only garnered positive comments from /v/ about the layout after I asked people to look at it by using history for each page they look at. Does it cut your soo deep that I didn't conform to the hivemind and because I didn't ask everyone. Are you a....

HOLY SHIT! I just looked up "Magic9mushroom" in google... your an adult and your into that asian pedophilic cartoons? 'Aminmey' or something? ... your a borderline pedo mate. FUCK OFF and don't message me again... and ban me if you want, I'm nevercoming back if this place is associated with filthy degenerates like you.

== i have OA backups ==

i have backups .. maybe i can try setup it on some host... Makus

:Keep me posted. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 07:08, 18 April 2025 (UTC)

== also spoiler code question ==

ufopaedia have spoiler code ? build in or custom? pls post this code here if so

:I don't know of any. Also, please sign talk-page posts with four tildes (~). [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 07:06, 18 April 2025 (UTC)

User talk:Magic9mushroom

2025-04-18T07:06:36Z

Magic9mushroom: /* also spoiler code question */

== Rolling back NKF ==

Hi, and thanks for the heads-up. But my stance is to trust that wikipedia's ''[[wikipedia:Wikipedia:WAIN#Adminship_is_not_a_trophy|What adminship is not]]'' still applies here, particularly when it says that "An admin is just a normal user with a mop and a bucket." Are you implying that here they are exempt from the practice of resolving disputes through discussion? Anyway, IMO that stage wasn't reached yet, and i see no point worrying about "what if NKF disagrees about my revert?" until i'll know that he does... -- [[User:Jokes_Free4Me|Jokes_Free4Me]] ([[User_talk:Jokes_Free4Me|talk]]) 22:05, 9 April 2015 (EDT)

:I was not implying that NKF is exempt from resolving disputes through discussion. I was merely suggesting for the future that engaging in such discussion - on his talk page, perhaps - might be more prudent and courteous than rolling him back while yelling at him in all-caps. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 22:07, 11 April 2015 (EDT)

== Updates to UBK ==
Hey, I was looking at your "rewrite" section of the Base Layout Strategy:Talk page. I noticed that you used "lab"s as the default place holder to indicate any facility.
I have the image assets available to create an "empty room" tile that could be added to the UBK if you are interested. I reworked the UBK for the XPiratez mod of OpenXcom, and created all the tiles there, so it would be quite easy.
[[Template:UBK_Piratez]]

--[[User:IvanDogovich|IvanDogovich]] ([[User talk:IvanDogovich|talk]]) 13:02, 27 April 2016 (UTC)

:Well, I didn't make the UBK - NKF did - so he'd probably be the one to ask. I'm not sure it'd really clear anything up, though; since UBK's a copy of in-game pics, you'd still probably have to explain what the weird new graphic is. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 23:54, 27 April 2016 (UTC)
:Fair enough. :) Thanks for all the great work you have done to continue to make the Ufopaedia a vital resource --[[User:IvanDogovich|IvanDogovich]] ([[User talk:IvanDogovich|talk]]) 04:05, 28 April 2016 (UTC)
Thanks. It really helps to hear someone say that every so often. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 01:21, 29 April 2016 (UTC)

== Security Turrets in Alien Dimension (Apoc) ==

Hi Magic9mushroom

Ill try and screengrab a pic at some point, but there are disrupter pods on some alien buildings in battlescape
These do indeed fire if agents get close on UK CD-ROM (Original release) version

EDIT: These are the turrets...
https://media.discordapp.net/attachments/376028757183561728/481796205697957888/unknown.png?width=884&height=683

:Wow, the more you know. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 03:28, 23 August 2018 (CEST)

I guess they have the same flaw as X-com security turrets? I've never seen them fire on my agents in turn based mode. [[User:Jasonred79|Jasonred79]] ([[User talk:Jasonred79|talk]]) 18:07, 7 May 2022 (CEST)

== Zorium and Apoc Power ==
Hi magic9mushroom the final release does not contain this information no, but as we are talking about cut features i'm including the cut lore
Reason for linking the One Way to Win stuff was it refers to the eras of apoc development in which this was all covered
I'm trying to think of a way that this can all be incorporated without a long winded explanation
Will message again when ive had a think

No problem I have adjusted things to be clearer; let me know your thoughts.

:That makes more sense. Remind me where it says that the Alien Dimension is becoming inhospitable? [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 14:09, 17 August 2019 (CEST)

==The pistol gif==
Hey man,tbh I’m on moblie site of this in safari tbh the pic on my screen was all white [[User:Michaelx2|Michaelx2]] ([[User talk:Michaelx2|talk]]) 13:21, 21 February 2020 (UTC)

:I believe you. It's just that if anyone can see it, the problem is likely on your end. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 22:38, 21 February 2020 (UTC)
::I’ll try to sent a new Gif of pistol to replace it
:::The image is fine. I can see it. The problem is on your end. Look for a fix on your end (such as reloading the image or checking whether Safari is allowing GIFs). [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 05:51, 22 February 2020 (UTC)

== Hi Magic9mushroom i can sand u converted Apoc files ==

Hi Magic9mushroom i can sand u converted Apoc files
here https://my-files.su/fyc4xb

== Yes i forgot to say that its graphics ==

Yes i forgot to say that its graphics ...
you can join our discord and some ppl can help you with code etc https://discord.com/invite/f8Rayre
i cant say about psionics for sure...

== Also about Unit Stat Box (EU2012) that used in XCom2 they became outdated ==

Also about Unit Stat Box (EU2012) that used in XCom2 they became outdated
so if u can modify them here good example from
https://xcom.fandom.com/wiki/Faceless_(XCOM_2)?action=edit

{{Infobox XCOM2enemy
|name = Faceless
|image = File:XCOM2_Faceless.png
|aim =60/75/75/75
|critchance = 0/15/15/15
|defense = 0/0/0/0
|health = 8/10/10/12
|mobility = 12/14/14/14
|will = 50/50/70/70
|weapon = Claws (3-4 damage)
|abilities =Regeneration, Leap
}}

== strange beacose i take color samples from apoc game interface ==

strange beacose i take color samples from apoc game interface

== Request - Apoc'd ==

Do you know how whether it's possible to have an organisation conduct a raid against X-COM using Apoc'd? If so, how? Thanks. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 07:48, 15 July 2020 (UTC)

:Yes. Savedgames -> desired savegame -> Organised Crime. Set the organisation to the one you want to raid you, the target to the desired X-COM base, the action to Raid or Storm, and the time remaining to something other than 0.

:Note that if the organisation is not hostile, the invaders will count as neutrals and neither they nor your forces will open fire immediately. If you want to simulate a real base defence, you need to annoy them first (pointless investigations are the simplest way). [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 09:18, 15 July 2020 (UTC)

::Thanks, that worked fine for a new game, but it doesn't seem to work when I try it with my existing game that's currently at Week 6 (I've even tried waiting for the next day and there's still no raid).
::That aside, I've discovered two pieces of random and probably useless information while fiddling around with this: setting the raiding Organisation to "X-COM" or "Civilian" will get you the "base under attack" screen followed by the time jumping forward straight to the first Alien Alert, while setting it to "Alien" will get your base attacked by the crew of a Mothership. Yes, crew, not infiltration force, so there will be Megaspawn and Psimorphs. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 19:18, 15 July 2020 (UTC)
:: That doesn't sound useless, that sounds EXTREMELY FUN!!! ... I'd love to experience a base defence with Megaspawn and Psimorphs! Watching psimorphs going up against security stations will just be sadistic lol [[User:Jasonred79|Jasonred79]] ([[User talk:Jasonred79|talk]]) 18:11, 7 May 2022 (CEST)

:Dunno what's going on there; all I can say is it works fine for me even in games that have been going on for a while. Megapol doesn't seem to want to launch illegal flyers, but otherwise it seems to work. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 08:59, 16 July 2020 (UTC)

== Overspawn Bug Deletion ==
No evidence? The purple segments (multiple with various window patterns) of transtellar apartments et al. on the superhuman map (located up near the north-east corner) will have an overspawn just walk straight thru the building AND any other building that has those particular segments. Craft stop firing because the overspawn is '''inside''' the segment. I'm sure this that is a bug in all sense of the word. I request you put that listing back.

Please use a little more caution in future.

:Lolz, ironic echo. Nice.

:More seriously, insofar as the segments are set to be able to be walked through that's technically not a bug (the program is doing what it's told, it's just told to do something dumb). Just about anything you can fix with Apoc'd is not strictly a bug for this reason (as Apoc'd only changes data tables, not code). You only mentioned trees, which probably were deliberately made walkable so as not to slow down the Overspawn destroying them - I've also seen that the roads are set this way (though the supports for them are not) which may also be deliberate. If you'd mentioned those buildings rather than ranting about "a big ugly baby" in mainspace I would have been less inclined to just blank it.

:Now, the thing with the purple buildings is an anomaly and could be considered a design flaw, so feel free to put that under that heading. Suggesting making ''all'' tiles unwalkable for the Overspawn is probably a cure worse than the disease, though. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 13:24, 6 August 2020 (UTC)

Thanks for the prompt reply. I've tried to inject a little humour with that baby reference but this place serious business. Point Noted. "...technically not a bug (the program is doing what it's told, it's just told to do something dumb)..." quite so.

:It's not so much that the whole place is super serious - humour's fine in talk pages and some of the less precise or opinion articles (see: Weapon Analysis). But Known Bugs is a pretty crucially important page and being exact is necessary to avoid confusion. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 15:03, 6 August 2020 (UTC)

== Apocalypse question ==

Hi, I was wondering if you knew whether being allied to an Organisation in Apocalypse has any "hidden" in-game effects? There are lots of internet rumours about this (e.g. allying with a gang gives more human recruits, allying with Technocrats makes smaller organisations friendlier...), and the Tips Book makes similar claims. However, from what I've observed, I'm 99% sure none of this was actually implemented. But it would be nice to have confirmation obtained by looking at the game code. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 22:34, 5 May 2022 (CEST)

:I'm not a primary code digger. What I do know from Skin36's work is that relations with factions are irrelevant to new hires with the sole exception that hybrid/android recruits are removed if you have <0 relations with the Mutants/SELF.

:I'm not aware of any hidden relations effects, besides the ones from factions' (hidden) relationship with the Aliens (factions allied with the Aliens will refuse X-Com bribes; I forget whether this is also why you never get Alerts from CoS temples or if that's a ''sui generis'' case). There is, however, the basic principle of Apocalypse relations to consider: "if faction A attacks faction B, then faction C that disliked B will start liking A and faction D that liked B will start disliking A". This principle, applied over many iterations, ''can'' work some magic. This is, for instance, why Marsec and the gangs are substantially more likely than usual to go hostile, despite having zero starting relations with both you and the aliens - they hate Megapol, so when the UFOs blow up Megapol cars and buildings they start liking the aliens, so when you blow up aliens they start disliking you. So it's not ''ridiculous'' to say that getting the Technocrats to like you might be good for getting some of the enemies of the Marsec/Solmine/Extropian/Transtellar alliance to like you. On the other hand, any relations process that routes through somebody non-militarised (i.e. not player/aliens/Megapol/gangs/infiltrated) performing attacks is going to take forever to work, because non-militarised factions don't attack people very often. And of course you can't ''see'' most of the relations grid, and it's partially random, so any attempts at more than the most basic manipulations are blind unless you cheat. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 17:49, 26 May 2022 (CEST)

:: Ok, thx. I'll run a couple more in-game tests just to make sure, but everything seems to point towards the conclusion that the Tips Book's claims about the effects of alliances are wrong (and I'll revert the edit accordingly after I'm reasonably certain).
:: <s>One more thing I've wanted to ask - could you remind me how the game rounds numbers, again? In particular, I'd like to put the exact numbers of guards/henchmen employed by an organization in the appropriate table.</s> Figured it out. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 15:40, 2 June 2022 (CEST)
:: <s>I've contacted Filmboy84 via Discord. His info directly contradicts Skin36's, as he claims the Tips Book is essentially correct, though the effects are minimal. Allying with a gang makes it more likely that the max number of recruits turns up. Apparently what affects the number of recruits is much more complex than it seems at first glance. It's apparently modified by your relations with several organizations, both positive and negative.</s> Filmboy is wrong. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 19:44, 16 June 2022 (CEST)
:::Yeah, I did kinda suspect Skin36 knew his stuff; he's walked me through .exe hacks before. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 14:29, 16 October 2023 (CEST)

==Hello==
If anything is found, please update the page: [[Organizations]]. I've just rewrittnen it (removed relations). 
...any feedback positive or negative, please post to my talk page about my recent actions (March 2022 to present) since I'm thinking I might be 'stepping on peoples toes' by rewriting quite a few pages. [[User:EsTeR|EsTeR]] ([[User talk:EsTeR|talk]]) 14:27, 17 June 2022 (CEST)

==Note==
I just came here to cross off some old stuff that has been resolved in the meantime as well as to say I greatly appreciate all the work you've put into the wiki, and hope you get better soon. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 16:26, 30 September 2023 (CEST)

== Known Bugs (TFTD) ==

I'd like to try cleaning this page up a bit, if that's ok: https://www.ufopaedia.org/index.php/Known_Bugs_(TFTD) 
1. I'd remove the entire "Exploits" section because 1) exploits are not really bugs, and 2) the one exploit listed requires actually editing game files - if you're doing that, you can just as well simply give yourself a bunch of money instead. 
2. I'm not sure about the "questionable logic" section either. The things listed there more like unrealistic features (mostly bad physics), but not bugs. 
3. I'd put all the bugs under two basic categories: Geoscape Bugs and Battlescape Bugs, and then list sections under each of them as appropriate. 
4. "The Deep One attack looks like the Celatid spit / mortar (holdover from UFO)" - As far as I know, it's not the attack that's weird, but the graphical presentation, i.e. Deep Ones ''are'' supposed to be carrying some kind of mortar-like weapon, but are instead depicted as having an innate spitting attack. Or am I missing something here? 
5. "'Medic Cannon' - USO being armed with 1/0 weapons, the 'weapon' being 'medic' shown as a purple rank badge with commander's chains. with an ammunition capacity of two, but without any rounds for it. (...)" - I assume this is supposed to say "X-COM sub" instead of "USO". 
6. Can TFTD Extender cause issues of its own? I sort of remember it can cause aliens to spawn in inaccessible places, but I might be misremembering. [[User:Darkpast|Darkpast]] ([[User talk:Darkpast|talk]]) 12:45, 8 November 2023 (CET)

: #1 - reasonable. #2 - I think that the "MC works on non-implanted people" thing needs to be explicitly mentioned somewhere (not necessarily this article), and having a single mention of TFTD treating water like air might be reasonable, but hammering it in like that section does is definite overkill. #3 - good. #4 - this doesn't even seem like a bug to me. #5 - I don't have information on this. #6 - TFTD Extender isn't the same as XcomUtil. The "stuck" aliens [[Talk:Artefact_Site|are apparently a thing in vanilla]], but XcomUtil may worsen the chances of them showing up. I know that Sherlock's route fixes [https://www.strategycore.co.uk/forums/topic/12679-strange-things-in-tftd/ break a lot of maps] (if non-fatally) due to the limits of ROUTES.DAT and the alien spawn algorithm. I've never used TFTD Extender so I don't know if it causes any bugs of its own; I'd suspect mostly not, though, as Tycho has a rather-deep understanding of the X-Com engine to the point of being able to straight-up add functionality. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 01:39, 9 November 2023 (CET)

==STOP==

...and if you don't I make sure you lose you admin status and possibly get banned for vandalism. [[User:EsTeR|EsTeR]] ([[User talk:EsTeR|talk]])

:EsTeR, I mentioned that I was intent on reverting a lot of your edits (not all of them; your addition of images in particular is great work, and I intend to preserve the use of all the ones that aren't duplicative), and intent on using admin powers to make you back off if you attempted an edit war, ''in my request for admin powers'', because indeed it would have been duplicitous not to. I am not going behind anyone's back by doing this; I have approval. Feel free to tell whomever you like, but I do not believe you have the ability to carry out your threat.

:You've been told by quite a few editors that you were acting unilaterally without regard for consensus. You got as far as you did because the admins were AWOL and nobody had the sheer bloody-mindedness needed to fight an edit war against you. I really, truly ''do not'' want to block you, because you actually do a lot of good work when you are not trying to turn the wiki into a poorly-written strategy guide; as I've said in the past, you're not a troll, and you're certainly not a spambot. But the buttons are there. I am, seriously, still open to discussion with you about what does and doesn't work. But you no longer have the ability to just ram things through with brute force when people don't agree with you. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 15:09, 10 April 2025 (UTC)

::1. The only people I have interacted with since the Apoc section revamp are Magic9mushroom (conflict), Darkpast (conflict), Bard (one revert on the cheats page), Jasonred (banter), Hobbes (praise). And no one else. To claim that quite a few editors have had objections is FALSE. The only to two so that have objections are you and Darkpast because I edited the pages with last edits by you or Darkpast. ...so your are a proven LIAR.
2. Consensus is why nothing got done. Mainstream wikipedia is now a sad joke of an encylopedia because consensus is preferred over truth. If all the lefty admins agree on something, then thats the 'truth'. What happens when their little circle agrees on something even though it is false. ...because consensus makes them feel like they are right. ie: "too many cooks in the kitchen". This place apoc was templated by me to be (1) uniform, (2) easy to read without novelisation (terse wording and bullet points), (3) removal of vast amounts of repetativeness on multiple pages, (4) removal of simplistic grasp on the english language, (5) massive amount of input with new data and uniform pics.
3. Like I mentioned. The only two that have had conflict are you and Darkpast because I changed the pages which either of you 'last edited by' in the history list. IT IS OBVIOUS without a doubt that you have a had a dummy-spit because you think those pages are the be-end-all-end of finality ...that is why you changed Law Pistol and Chrysalis (and others) back to those last users and destroyed(ing) the flow and uniformness and other aspects as mentioned in the numbered points above. There is nothing wrong with either of those pages, so why did you change them? You haven't added anything constructive to it but just blantant rollback. eg: on the Chrysalis roll back there is no pics of what the thing looks like on the battlescape? ...so you made the page worse. I don't own the pages and neither do you - if you change them, ADD information to it to make it better for everyone and don't just roll back pages, it makes you look petty and gives me concrete proof that you are vandalising the apoc wiki.
4. I don't ram things through, I constructively edited (the numbered points above) the whole Apoc section. How can one get concensus of all involved when most are AWOL or disinterested? So without mass approval or agreement nothing gets done! ...and eventually half-arsed repetative articles appear throughout Apoc section without organisation. The -number one- reason did it so for OPENAPOC.
5. Change the articles as you seem fit to do so but don't destroy information. Build the pages to be better. [[User:EsTeR|EsTeR]] ([[User talk:EsTeR|talk]])
:"The only to two so that have objections are you and Darkpast because I edited the pages with last edits by you or Darkpast." - you're forgetting Gamer500018.
:I rolled back Lawpistol because you removed the UFOpaedia entry for its clip and because you put in nonsense advice (it is one-handed, so it should always be dual-wielded). I rolled back Chrysalis because you changed all the plurals to "Chrysalises" rather than the correct "Chrysalides", and because you bizarrely removed the infobox formatting. I did actually miss that I'd removed the battlescape images of Chrysalides; thanks and I'll re-add those.
:I do understand the value of uniformity. I'm going to edit ''all'' of the weapon and alien pages back to use infoboxes and (for weapons) the old, cleaner Battlescape images. I'm just not as fast as you, so it's not done yet. [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 22:33, 13 April 2025 (UTC)

Wrong. the plural is "The plural of chrysalis is chrysalises. Find more words at wordhippo.com".

Gamer500018 was a (ex)user on here that made a throwaway account just so they could call me a troll.

Now your nitpicking:

"it is one-handed, so it should always be dual-wielded" Read what the official blurb is. Dual handed? Yeah one could, but be prepared to a backpack full of ammo and playing like that won't last long since stock levels are low for ammo. Essentially what i wrote. The official wording suggests that it is a back-up weapon, so that wht was I impled in the text.

the "ammunition for law pistol clip", "the ammuntion for..." etc. etc. official blurb were left out because they are not necessary. It doesn't add usefulness to the page.

The info-box become large and take up alot of space if you resize the pic to bigger than a postage stamp. The article then has a lot of empty space which is not necessary and a waste of space... and it looks stupid and ametuerish.

I don't know why you are doing it? The Apoc section has only garnered positive comments from /v/ about the layout after I asked people to look at it by using history for each page they look at. Does it cut your soo deep that I didn't conform to the hivemind and because I didn't ask everyone. Are you a....

HOLY SHIT! I just looked up "Magic9mushroom" in google... your an adult and your into that asian pedophilic cartoons? 'Aminmey' or something? ... your a borderline pedo mate. FUCK OFF and don't message me again... and ban me if you want, I'm nevercoming back if this place is associated with filthy degenerates like you.

== i have OA backups ==

i have backups .. maybe i can try setup it on some host... Makus

== also spoiler code question ==

ufopaedia have spoiler code ? build in or custom? pls post this code here if so

:I don't know of any. Also, please sign talk-page posts with four tildes (~). [[User:Magic9mushroom|Magic9mushroom]] ([[User talk:Magic9mushroom|talk]]) 07:06, 18 April 2025 (UTC)

Dual-wield

2025-04-13T23:57:37Z

Magic9mushroom: punctuation

In the original X-COM trilogy, it is possible for soldiers to wield a weapon in each hand at the same time. This is called dual-wielding.

==UFO & TFTD==

In UFO: Enemy Unknown and X-Com: Terror from the Deep, there is no firepower benefit from dual-wielding, as firing weapons uses the same amount of TU regardless of whether a soldier is wielding two weapons or only one (i.e. you cannot fire both weapons "at the same time"). There is a direct penalty, as two-handed weapons will suffer a 20% accuracy penalty (*0.8 accuracy) if the opposing hand is not free. As such, it is generally suboptimal to dual-wield most weapons.

However, as most items can only be used when in hand, and moving objects around in the inventory costs TU, it can be useful to keep two items in hand for the sake of versatility. Usually this consists of a soldier "dual-wielding" a pistol with a flare, grenade or medikit, but wielding two weapons can occasionally be worthwhile if they are sufficiently different (e.g. [[Laser Pistol]] + [[Blaster Launcher]] in UFO, or [[Sonic Pistol]] + [[Vibroblade]] in TFTD).

==Apocalypse (turn-based)==

In the turn-based mode of X-Com: Apocalypse, there is no TU cost for moving items around in the inventory, but there is an accuracy penalty for dual-wielding most weapons and both weapons cannot be fired simultaneously. As such, it is strictly better to put away or drop whatever is in a soldier's off-hand before firing a weapon and then pick it up afterwards. The only possible exception is if a soldier is using a [[Personal Cloaking Field]], as holding it in hand may prevent reaction fire (even then, reaction fire is uncommon in Apocalypse).

When dual-wielding in turn-based mode, shooting a target or tile repeatedly with Shift+LMB will cause the agent to alternate between the two weapons. However, the firing costs are no different than firing each weapon manually.

==Apocalypse (real-time)==

In stark contrast, dual-wielding is exceptionally effective in the real-time mode of Apocalypse, as both weapons can be fired simultaneously. This is obviously a straight firepower boost for pistols (as well as homing missiles, which will always hit regardless of calculated accuracy). Two-handed weapons (those with dimensions more than 2×2) suffer a 40% accuracy penalty (x1.4 inaccuracy) when dual-wielded, but this is a very good deal compared to switching fire modes (switching from Aimed to Snap, or from Snap to Auto, incurs a 100% accuracy penalty (x2 inaccuracy) for the same doubled fire rate). Of course, you do have to pay for the extra gun.

Note that dual-wielding the [[M4000 Machine Gun]] and [[Toxigun]] in Auto mode will not achieve a full doubling of firepower, as this will cap out the game's fire rate limit. It is therefore usually better to use another firing mode when dual-wielding these weapons.

Megapol Lawpistol

2025-04-13T23:46:55Z

Magic9mushroom: rewrite

{{Ref Open | title = Megapol Lawpistol}}[[Image:Lawpistol (UFOpaedia).png|right]]
A standard issue hand gun which is good at short range and quite powerful. Its usefulness should not be underestimated because it allows an Agent to use other equipment, such as a grenade, with the spare hand.
{{Ref Close | source = X-COM Apocalypse Ufopaedia}}
{{Ref Open | title = Megapol Lawpistol Clip}}[[Image:Lawpistol Clip (UFOpaedia).png|right]]
Ammunition for the Lawpistol.
{{Ref Close | source = X-COM Apocalypse Ufopaedia}}
The Megapol Lawpistol is Apocalypse's basic pistol weapon. Like its [[Pistol|counterpart]] in EU, the Lawpistol is fairly potent - it does more damage per shot than the [[Marsec M4000 Machine Gun]] - but has a small clip size.

In real-time mode, the Lawpistol is one of the better starting weapons, as it has a high ROF and can be dual-wielded with no loss of accuracy; only the [[Megapol Auto Cannon|Auto Cannon]] loaded with HE rounds has better on-target DPS. The main caveat on its use is the scarcity of its ammunition, which prevents the player from simply handing them out to the whole squad. Do remember that the Lawpistol ''will'' lose accuracy if the other hand contains a two-handed weapon.

In turn-based mode, the Lawpistol is generally outperformed by the [[Marsec M4000 Machine Gun|M4000]] due to TU truncation and the irrelevance of dual-wielding. It does remain useful for hybrids, as they will frequently fall below 45 TU due to their lower base TU and Strength stats, and hence be able to perform 1-TU autoshots.

==Stats==
{|
|[[Image:Lawpistol.png|left]]
|'''Megapol Lawpistol'''
* Size: 1 × 2
* Weight: 3
* ROF: 2.00 r/s
* Accuracy: 45%
* Manufacturer: [[Megapol]]
* Base Price: $300
* Minimum Weekly Stock: 15
* Maximum Weekly Stock: 50
* Battlescape Score: 2
|[[Image:Lawpistol Clip.png|left]]
|'''Megapol Lawpistol Clip'''
* Size: 1 × 1
* Weight: 1
* Power: 24
* Damage Type: Armor Piercing
* Ammo: 16
* Range: 43m
* Manufacturer: [[Megapol]]
* Base Price: $10
* Minimum Weekly Stock: 20
* Maximum Weekly Stock: 80
* Battlescape Score: 0
|}

{{Equipment (Apocalypse) Navbar}}

[[Category: Apocalypse]]
[[Category: Agents Equipment (Apocalypse)]]

User talk:Magic9mushroom

2025-04-13T22:33:24Z

Magic9mushroom: /* STOP */

User talk:Magic9mushroom

2025-04-10T15:09:39Z

Magic9mushroom: /* STOP */ sorry it's come to this

Disruptor Gun

2025-04-10T13:25:02Z

Magic9mushroom: page restoration

[[Image:Disruptor_Gun.jpg|frame|The Disruptor Gun, image from the UFOpaedia]]
After a few engagements with X-COM forces, the aliens realise that arming their [[Anthropod]]s with actual weapons is a good idea. Their first attempt at this is the Disruptor Gun, a lightweight energy weapon powered by dimension chamber technology.

Unusually for an X-Com game, the Disruptor Gun is not really an improvement in firepower over the weapons X-COM can buy in Mega-Primus; its damage per shot is respectable but not amazing, its rate of fire and accuracy are mediocre at best, and it counts as a two-handed weapon for the purpose of [[dual-wield]]ing. On the other hand, the Disruptor Gun is a quite convenient weapon for those uninterested in heavy micromanagement, as it's very light and doesn't require scarce ammunition (allowing standardisation of loadouts). In any case, the weapon should generally be researched with moderate priority, as unresearched artifacts cannot be sold in Apocalypse and the enormous quantities you'll loot from the aliens early on are worth a pretty penny; it's also a research prerequisite for the far more useful [[Devastator Cannon]] and [[X-COM Disruptor Armor]].

Anthropods with this weapon are not especially dangerous except at point-blank range due to their laughably-bad accuracy, although [[Skeletoid]]s pose at least some threat.

The aliens will eventually [[Alien Tech Levels (Apocalypse)|phase out]] the Disruptor Gun as X-COM's tactical score grows ever-higher. However, by that point, the weapon will have found its way into the hands of Mega-Primus organisations, who will continue using it indefinitely, so X-COM can never be locked out of the technology.

When disruptor weapons are destroyed by explosion or fire they usually discharge a couple of shots in random directions.

'''''Official Entry:''''' "The Disruptor Gun is a remarkable piece of technology. It propels a beam of sub-atomic particles at immense speeds and quantity. The chamber which generates the energy is an inter-dimensional device which materializes energy from an alternative dimension. The power source, once initiated, is self-perpetuating and no ammunition or energy pods are required to sustain the fire power. Our replicators can reproduce this technology fairly accurately."

==Stats==
===Disruptor Gun===
{|
|[[Image:Disruptor Gun inventory.png|left]]
|
* Size: 2 × 3
* Weight: 5
* ROF: 1.125 r/s
* Accuracy: 30%
* Power: 42
* Damage Type: Disruptor
* Ammo: 28 (recharging)
* Range: 50m
* Base Price: $2100
* Battlescape Score: 8
|}

{{Equipment (Apocalypse) Navbar}}

[[Category: Apocalypse]]
[[Category: Aliens (Apocalypse)]]
[[Category: Alien Artifacts (Apocalypse)]]
[[Category: Agents Equipment (Apocalypse)]]
[[Category: Research (Apocalypse)]]

Template:Unit Stats Navbar

2025-04-09T16:43:05Z