Differences

This shows you the differences between two versions of the page.

--- en:games:star_trek_armada_1:obscure_game_mechanics [2022-06-27-15-39] – [Units Vanish From Control Groups] 7saturn
+++ en:games:star_trek_armada_1:obscure_game_mechanics [2024-12-02-17-21] (current) – [The AI Cheats] 7saturn
@@ Line 5: / Line 5: @@
 ===== Cloaked But not Invisible =====
 When turning off the fog of war, cloaked ships will still appear visible for an opponent, once inside the already visible map space of him. You will still need to use a [[detector_mechanics|detector]] to uncover the >>invisible<< unit, in order to be able to target it. You will however, not need to uncover it in order to beam in...
+===== Line of Sight of a Team Member is not Shown Entirely =====
+Usually you can see all that your team members see, too. This goes with one exception: If a part is uncovered for a player only due to an active [[Romulan Spy]], then these units and stations are not part of the shared line of sight. Meaning a ship that is very much visible for your team mate due to being spied upon is still not visible for you, if it is cloaked.
 ===== Freighters Behavior =====
 All [[Freighter|Freighters]] will continue gathering Dilithium from a newly chosen Dilithium Moon, once the Moon they are working on runs dry. They will select the nearest Moon still having Dilithium. That usually leads to the situation, that two empty Freighters and one partially filled one will head into the direction of a new moon. They will gather Dilithium there and return it to the [[Mining Stations|Mining Station]] they were returning the Ore to before. If that partially filled Freighter does empty entirely and stay at the Mining Station instead of heading out and filling the rest of their cargo hold, you can be sure that there is no Dilithium out there anywhere any more.
@@ Line 31: / Line 33: @@
   * When playing against a medium or hard AI, you can notice that the build time and resources are considerably lower. For the hard AI it's only 40%, for the medium AI 80% of the normal cost of time and materials.
   * All AIs cheat in the way that they disregard the tech tree altogether. That's advantageous and disadvantageous at the same time. While it allows the AI to build [[freighter|mining freighters]] before even having a [[mining_stations|mining station]], it also makes it waste resources on not required buildings, such as research stations and [[special weapons|special weapon]] research, when playing with //Free Tech// techtree.
-  * Also the AI //always// knows where your ships are, even when they are cloaked (similar how using no fog of war and no shroud works for humans). So when placing a sensor station remotely, where the AI cannot have seen it, it will still head straight for that spot and attack it. You can see that particularly well in the Mission [[single-player_campaign#tasks4|To the Gates of Sto'vo'Kor]].
+  * Also the AI //always// knows where your ships are, even when they are cloaked (similar how using no fog of war and no shroud works for humans). The AI system creates a threat map for the entire map, regardless of visible or visited at all. And the AI uses this threat map to evaluate what to target. That also includes the targets not even seen yet. So when placing a sensor station remotely, where the AI cannot have seen it, it will still head straight for that spot and attack it. You can see that particularly well in the Mission [[single-player_campaign#tasks4|To the Gates of Sto'vo'Kor]].
 What the AI will //not// do however, is cheating itself more resources. So it is possible to starve the AI out. As the AI never deconstructs ships or stations, it has no way of recovering, once it has no freighters and less than 160 Dilithium left (to build a new freighter).
@@ Line 38: / Line 40: @@
 ===== Phoenix Bug =====
 The [[Rift Creator]] of the [[Phoenix]] has a control key definition bug. By default, all normal [[cloak|cloaks]] are used with the ''F5'' key. This also goes for the Phoenix, which actually has a cloak. But as its special weapons F-key slot is also activated by ''F5'', the cloak is not usable for human players. It is neither visible as a button nor can it be used with the F-key. Instead, the [[super_weapons|super weapon]] is triggered. The AI on the other hand can use both functions independently, which leaves the AI with the advantage of being able to send the Phoenix into battle cloaked.
+===== Firing on Ones Self Bug =====
+The game does allow for stations and ships to fire on one's own units. When you order a unit that is capable of firing conventional weapons to fire, you can direct that fire explicitly (attack command) onto one of your friendlies. That may be an intended design aspect of the game. (Yet a strange one. If you want to get rid of one of your own units, you simply deconstruct it.) What's very likely not intended, is the ability of ships to actually fire on themselves (not: another friendly ship of sorts).
+When having selected more than one ship at the same time, making the group attack a friendly of the group makes //all// ships attack the target, including the ship being targeted. Even when ceasing fire with the other ships, the ship firing on itself will not stop, until given another order (or weapons fail). So basically you can order a ship to fire on itself. This is not very well visible for Phase fire. But torpedoes make it very well visible, that a ship can in fact fire on itself. This does not work with stations, as you cannot select multiple stations at the same time.
 ===== Increased Mining Rate by Death Chant =====
 The increased firing rate caused by a [[Death Chant]] also affects the [[Mining Beam]], increasing the output rate by 50%. When having less than 3 [[Freighter|freighters]] at a [[map objects#Dilithium Moon]], this may boost income rate. If you already have 3 or more freighters at one moon, there is little point in using this method, as the processing speed of [[mining stations]] is not increased, making them the bottle neck.