History GoodBadBugs / RealTimeStrategy

** Flamers generally deal little direct damage; their main duty is to break enemy infantry's morale. However, Tau Crisis battlesuits in ''Dark Crusade'' can be equipped with heavy flamers that deal absolutely devastating damage to anything caught in the fairly large AoE. They're the only flame weapon with a three-digit damage rating, and the conspicuous zero at the end implies an oversight that wasn't intended this way. However, since Tau AI players rarely, if ever, upgrade their Crisis suits with anything, few players complain about this highly useful close combat asset for an army that's sorely lacking in viable close combat capabilities.

* ''VideoGame/CommandAndConquerTiberianDawn'' and ''[[VideoGame/CommandAndConquerRedAlert Red Alert]]'', the first two entries in the series, both have a bug where a grenadier can throw his grenades across an entire screen if you change the target halfway through him throwing it. Particularly pronounced in the DOS versions. If you had radar, the grenadier could ''fling his explosive payload across the map''.

** Silos are actually unnecessary, as unused ore/tiberium could simply be used up by building something and then canceling its production, which results in a refund in cash rather than in ore/tiberium. ''Tiberian Sun'' solved this simply by making the game use the cash money ''before'' the silo-stored resource, before ''Red Alert 2'' removed the need for silos and just immediately giving you cash for your harvested ore.

* In vanilla ''VideoGame/SupremeCommander'', it was possible to fire a nuclear missile and have it detonate right above your base (or possibly an opponent's base). The reason? The missile could physically collide with aircraft, essentially turning air units into ghetto nuclear missile defenses. This was mostly fixed in ''Forged Alliance''... at least except for the experimental UEF Novax satellite, which could still block nukes due to it technically not being counted as an "air unit" by the game (as a satellite, it's immune to all weapons and can only be taken down by destroying its command center building).

** Like ''VideoGame/TotalAnnihilation''', the game also shares the bug where you can block an enemy factory with destroyed units. It's quite a bit harder to pull off in ''Supreme Commander'' than in TA however.

* In vanilla ''VideoGame/SupremeCommander'', it was possible to fire a nuclear missile and have it detonate right above your base (or possibly an opponent's base). The reason? The missile could physically collide with aircraft, essentially turning air units into ghetto nuclear missile defenses. This was fixed in ''Forged Alliance''.
** There are a lot of situations like this even in Forged Alliance. Everything collides with everything which leads to tanks shooting in the hill trying to hit the enemy on its other side, flocks of fighters getting accidentally shot by artillery, nukes and tactical missiles destroyed by any random projectile, and there was THREE ways to stop enemy nuke with UEF satellite. Also this allows you to stop enemy commander from escape by gathering land units around it or block fatal shot by starting to build something tall on its path. And {{friendly fire}} is rather common thing here too which led to nuke silo suicide if you use one of aforementioned satellite tricks.
** As ''VideoGame/TotalAnnihilation'''s SpiritualSuccessor, Supreme Commander also has a bug with blocking enemy factory by unit's "corpse". This gets especially ridiculous when happened to aircraft factory which have no need for free space around unless it is building an engineer.

** Projectile damage is calculated on impact, not on being fired. Since dead units don't always have the same stats of they did when they were alive, if an attacker dies between firing its projectile and hitting something the damage is drastically lower. Cue trebuchets launching enormous boulders at barely-armoured structures and doing one point of damage.

* The Amiga game ''{{K240}}'' (at least the earlier versions) allowed the player to access missile control for ''any'' asteroid he can see, not just his own. This allows you to tell the silos on an enemy asteroid to launch all its missiles ''at itself''.

** The F2kzzzz glitch basically puts several different command queries for scouts together to make them flying ninjas of doom. First, you press the F2 key, which sets the scouts to evasive, making them slightly faster for a cost in firepower. Then, you press "k," which initiates the kamikaze attack. Normally, this would be lethal, but by then pressing "z" repeatedly on the keyboard, you initiate a special UpToEleven ability for scouts that makes them even ''faster'', so fast in fact, that they prove ''too agile to '''die'''''. As a result, the scouts become nigh impossible to kill and trail closely behind enemy fighters, shooting the entire way.

* Both ''VideoGame/{{Myth}} I'' and ''Myth II'' have an excellent bug: the menu pops up when pressing Escape, pausing the game. What the game doesn't do is prevent you from giving orders when the menu is active, thus this can act as an active, if not tedious, pause.
* ''VideoGame/{{StarCraft|I}}'' has quite a few bugs which have been incorporated into the metagame, the most prominent being the mutalisk stack, a pathfinding bug which causes air units to occupy the same space, making focus-firing impossible. Not surprisingly, the developers are ''breaking the engine'' to [[AscendedGlitch incorporate stacking into the sequel]].
** Of course, who can forget that both the Terran Valkyrie and Protoss Corsair from the expansion were specifically designed to deal with those stacking air units.
** By using fan made map editors, a bug similar to this allowed for an entire new game type known as Stack Defense (Stack D for short) which consisted of players using "lights out" commands to "turn off the lights"--activating fog of war even where the player controls units. Usually this would be considered a disadvantage, but it happens that the game doesn't particularly care if you warp in 20 Photon Cannons on the same spot as long as Fog of War is covering that spot when it happens. Then turn the "lights" back on and you have either several structures on the same spot (so that you can't tell there are more than one [[MoreDakka until they start shooting at things]]) or overlapping structures forming a wall.
*** Lights on/off stacking has some bugs of its own. The maps have a maximum unit limit onscreen at one time, maximum number of objects, and buildings. Meaning if you stack fifty cannons in one spot, you'll end up with only 5 or 6 of them firing at one time, and depending on the wave of enemies the map spawns, you can have ''none of them firing at all!''
** This overlapping movement proved so useful in simply getting a huge aerial army from point A to murder target B, that when Blizzard's next RTS, VideoGame/WarCraftIII, had some issues with large groups of flying units, they '''patched in''' a modified version of the bug - one that turns off the moment they reach their destination, shooting the units out at high speed into focus-firable formation.
** Honestly, making custom maps for ''VideoGame/StarCraft'' requires using many GoodBadBugs and a substantial amount of DummiedOut content, in addition to some odd (non-glitch) quirks in the game. The most common example is Hyper Triggers, which cause triggers in the map to execute much faster (almost once a frame, as opposed to once every two seconds); this requires adding four triggers to the map that always execute and do nothing but repeatedly call the Wait action, which normally [[ExactlyWhatItSaysOnTheTin pauses a trigger's execution]]. (On the other hand, running hyper triggers will cause chaotic effects if the Wait action is used normally; this is one of the main reasons for [[NotTheIntendedUse Death Count timers]].) Extended Unit Deaths are another example, where a condition that checks how many times a player has lost a certain type of unit is used to read other portions of the game's memory, such as how many HP a unit has (which, oddly, the game does not normally allow). Computer-controlled Medics will try to heal injured allies anywhere on the map, causing the Medic to move; this can be used to detect a unit being injured. AI Dark Archons will move to cast Feedback, which drains a caster's energy and damages it based on the amount drained, at infinite range if it will kill a non-hero, which can be used to detect either damage or spellcasting. The list, as they say, goes on.
* In ''VideoGame/StarcraftII'''s single-player campaign, once you max out Zerg and Protoss research, you can redo previously-completed missions, and the game will deposit some free research points in the research console (without telling you). If you check the console, you get credit for them. Why is this good when you've already completed the research? Extra research points are converted into credits, and even if you found every normal research point in the game and did every mission to collect every single credit, there isn't enough money to max out all the armory upgrades. On the other hand, by utilizing the bug after every mission, you will always have super-units except for the mission you first get them. This one has unfortunately been fixed, as you weren't supposed to get enough money per playthrough to afford everything. Sorry, achievement hunters!
** Patch 5.0 very briefly broke the way Terran Command Centers loaded [=SCVs=]. With a specific order of actions, it allowed Command Centers to load anything, including ''buildings'', on them, with an incredibly ridiculous potential. You could load Refineries to relocate vespene geysers (with the opponent all too unaware that this ever happened, as while the geyser looks unoccupied, it technically still was), load defensive structures like filled Bunkers or Planetary Fortresses (or Zerg Crawlers and Protoss Photon Cannons) to get a bona-fide DeathStar that wipes out anything on the map, load the aforementioned Planetary Fortresses to relocate them (as they otherwise cannot lift off) or, in an extreme case of MindScrew, you could load the Command Center into ''itself'', making it vanish from the map while still technically existing (providing Supply and preventing the InstantWinCondition of getting all buildings destroyed, while also still potentially carrying whatever it had, allowing Terran players to effectively delete vespene geysers). It doubles as a GameBreakingBug because it was impossible to fight back against (and in fact forced Blizzard to disable Ranked Matches until the bug was fixed), but it also brought untold hilarity.
* ''{{VideoGame/Stronghold}} Crusader'' has a glitch that, upon pausing the game, suspending the activity of a building, resuming it and then unpausing the game, marks the building as unoccupied without firing the current worker, making another worker take up the job while the old one kept working.A player could repeat this glitch at their heart's content with interesting results, such as feeding a 100+ people fortress off a single apple patch with a dozen farmers, immensely speed up transportation of materials, or fill up the armory in one single production cycle.

* ''VideoGame/TotalAnnihilation'' has quite a few of these. [[http://www.angelfire.com/ga/gnugs/ You can see many of them on the Gnug clan's site]].
** Commanding long-range turrets and artillery to force-fire at the ground in front of them would force their barrels to elevate and hurl shells far beyond their usual range in that direction - albeit at much reduced accuracy. A similar "feature" allowed submarines (normally anti-sea only) to attack land units on the coast by lobbing their ''torpedoes'' in a parabolic trajectory.
** Bombers have zero reload rate; if you can time their attacks well enough, you can make bombers drop an endless bomb stream.
** A particularly game-breaking trick is to send a unit into the driveway of a factory and kill it, preventing it from building anything until the unit is reclaimed.
** It's possible to share Metal Makers with a multiplayer opponent, depleting his energy stores. This is quite nasty for the other player since it prevents their commander from using their D-gun along with slowing their production.
* In vanilla ''VideoGame/SupremeCommander'', it was possible to fire a nuclear missile and have it detonate right above your base (or possibly an opponent's base). The reason? The missile could physically collide with aircraft, essentially turning air units into ghetto nuclear missile defenses. This was fixed in ''Forged Alliance''.
** There are a lot of situations like this even in Forged Alliance. Everything collides with everything which leads to tanks shooting in the hill trying to hit the enemy on its other side, flocks of fighters getting accidentally shot by artillery, nukes and tactical missiles destroyed by any random projectile, and there was THREE ways to stop enemy nuke with UEF satellite. Also this allows you to stop enemy commander from escape by gathering land units around it or block fatal shot by starting to build something tall on its path. And {{friendly fire}} is rather common thing here too which led to nuke silo suicide if you use one of aforementioned satellite tricks.
** As ''VideoGame/TotalAnnihilation'''s SpiritualSuccessor, Supreme Commander also has a bug with blocking enemy factory by unit's "corpse". This gets especially ridiculous when happened to aircraft factory which have no need for free space around unless it is building an engineer.
** An attempt to make the UEF T3 mobile sonar into something actually useful accidentally glitched and turned it into a ridiculously overpowered motor torpedo boat, requiring another patch to stop the ridiculous sight of flotillas of things which were technically ''buildings'' chasing battleships around.
* The Amiga game ''{{K240}}'' (at least the earlier versions) allowed the player to access missile control for ''any'' asteroid he can see, not just his own. This allows you to tell the silos on an enemy asteroid to launch all its missiles ''at itself''.
* ''VideoGame/EvilGenius'' had a few of them, which were very useful if the player knew how to exploit them.
** Lord Kane has two of the most useful bugs in the entire game. One of his powers forces any group of enemies to cower in fear before him, even soldiers and veterans. If you force Kane to physically attack the cowering enemies before he finishes his animation for the power, he will do so, but the enemies will ''still be cowering in fear'', allowing you to easily kill off a few of them before they get a chance to hit Kane. His other power erases all heat from a single target. And, for no apparent reason, also forces them to stand perfectly still while Kane runs up to them to use it. If Kane is far enough away, the target will be a sitting duck for so long that even a lowly construction worker can single-handedly take down the mighty John Steele.
** Double clicking on a minion will make him salute the camera (and thus salute you), but, ironically, they will still salute even if they are abandoning you because of low loyalty. This is a great way to prevent important minions from escaping, since you can tag them for capture, then keep double clicking on them to force them to stop running and thus get beaten by everyone else in the vicinity.
** Another useful bug allows one to be rid of meddling super agents indefinitely, long before discovering the methods to actually eliminate them, provided the player can baby-sit them long enough. Super agents have an easy time breaking out of a cell if they are captured, and if you leave them unattended, they will escape. However, if a prisoner is tagged for interrogation, they cannot escape. They will wait for someone to come along and take them to the device you chose, no matter how long it takes. This includes super agents. In fact, super agents have it worse because they will also wait for the Evil Genius avatar to arrive at the scene to laugh maniacally which, depending on the layout of your base, can take quite some time. As long as you watch them carefully, you can effectively juggle any number of super agents around your lair without ever giving them a chance to escape and cause damage.
** Until you kidnap the maid in one of the game's first missions, you will never be attacked. You won't get any more missions, of course, but by then you are able to go out into the world and steal cash. Simply set up your basic base, rob the world blind, come back a few hours later, let the world cool off and forget about you, and get back to work several million richer.
** If you build a multi-sectioned strongroom, then make another one, and then delete the first one, it will double your money.
** There's a bug that will permanently disable a Super Agent (or anyone for that matter) without even having to defeat them. You first need to have the Moko and The Matron in your employ. Have Moko run up to your target and use his ground-pound ability. Then have The Matron use her shock therapy ability on the target before he/she gets up. If done right the target will be locked into a loop of electrocution animation. People so glitched can still agro you minions but can't attack or take normal damage which means that you could have a pile-up of minions beating ineffectually on a guy having a constant seizure. Funny but not productive. To solve this issue a capture tag which will be effective at dealing damage. You can trap them in prison using one of the above methods or you can torture the agent with an smarts draining device and then repeat the glitch process once he's been escorted outside. The smarts damage from the shock therapy will lock the agent in "in need of assistance" and since he's already outside the base he doesn't need to be escorted. Take that John Steele!
* In ''VideoGame/{{Demigod}}'' (lovingly ripped off and improved from ''[[VideoGame/DefenseOfTheAncients DotA]]''), one of the characters has an ability that allows him to, instead of dropping healing mana/health potions on death, drop a potion that does a sizeable chunk of damage. You can kill yourself with this potion. By doing this, you deny any enemies attacking you the kill, and you gain gold and EXP as if you had killed a demigod of your level (which you did!)

* ''VideoGame/DawnOfWar II'''s expansion has an excellent bugged skill in the form of Command Mastery. It drops the energy cost of abilities for anyone who gets the Force Commander's Battlecry buff. The thing is, it doesn't reset when the Battlecry buff fades. And it's self-stacking. Apparently the Force Commander's really an excellent bard in disguise.
** Normally when you play the Imperial Guard in the expansion pack, if a squad is suppressed, a Commissar can execute one of the squad to break suppression. But in the Beta for Retribution, if a squad only had the Commissar left and it was suppressed, you could still have him use the ability, in which he valiantly executes himself for cowardice on the field in order to inspire himself to fight harder. [[ObviousRulePatch This is specifically forbidden by the tabletop rules.]]
*** "[[BrickJoke Emperor forgive me...]] [[https://www.youtube.com/watch?v=4sgimfISzPs#t=84 I have failed thee.]]"
** There's an amusing bug where a corpse doesn't stay still but instead floats skyward in an ever-expanding spiral.
* ''VideoGame/OgreBattle64'' contained an item duplication glitch that would allow players to create as many weapons and [[RareCandy stat-boosting items]] as needed, provided you already had at least one of whatever you were trying to copy. Given that certain powerful character classes had very specific stat requirements, which could otherwise be tricky to meet (not least because of the trademark "alignment/charisma" system), this came in very handy when a great upgrade was just a few points out of reach.
* ''VideoGame/{{Homeworld}}'' has both the F2kzzzz and "probe bomb" tricks, which both exploit different bugs for viable strategies in the game.
** The F2kzzzz glitch basically puts several different command queries for scouts together to make them flying ninjas of doom. First, you press the F2 key, which sets the scouts to evasive, making them slightly faster for a cost in firepower. Then, you press "k," which initiates the kamikaze attack. Normally, this would be lethal, but by then pressing "z" repeatedly on the keyboard, you initiate a special UpToEleven ability for scouts that makes them even ''faster'', so fast in fact, that they prove ''too agile to '''die'''''. As a result, the scouts become nigh impossible to kill and trail closely behind enemy fighters, shooting the entire way.
** The probe bomb trick takes advantage of the unusually wide area of effect for scuttling a probe, thereby enabling you to kill any number of unfortunate strike craft to wander in range.

* In ''VideoGame/DuneII'', a building that constructs troops could be surrounded by walls or other buildings to block it off. When a unit is built in a walled off building an airlift will pick it up and drop it in a nearby open spot. If you have no available airlifts (either you have none, or all are busy), then one will come from off screen, perform its function, and leave (also occurs if you lose your last harvester). If another unit calls an airlift just with the right timing, said airlift will pick it up and bring it where it needs to go, and will on random occasions, remain as a free airlift unit (normally one of the most expensive and useful units in the game, and very high tech). This allows access to airlift units much earlier then they should be available, and for free.
** At least in MS-DOS version, range and precision of weapons depend on the game speed. High speed increases range and decreases precision, and vice versa. At lowest speed missiles hardly miss and at highest speed they hardly hit the intended target. Meanwhile, specification range for sonic tank is only available at maximum speed, and at minimum speed it's only 2 squares. This is useful even in large battles, but in small skirmishes, when you can set speed for every shot, allows to neutralize enemies and give your units sniper precision.
* ''The Lord of the Rings: VideoGame/TheBattleForMiddleEarth II'' has two great glitches, both to do with custom heroes. One allows the player to give their heroes powers from any class, by clicking from one to the other very fast (there are walkthroughs available for this). The other allows a custom hero to use the self heal power over and over, by clicking the power and then moving instantly.
* In the ''VideoGame/AgeOfWar'' Flash game, units continue to be built even when the game is paused. Meaning that if your base is under attack, you can stack a very large amount of firepower hiding behind a StoneWall. A case of AwesomeButImpractical, as they then move in single file towards the enemy's base.
* ''VideoGame/WarcraftII'' had the lumber bug: having your peasants start harvesting trees then immediately canceling and building your town hall would net an extra 100 lumber. It was never patched because it actually improved the game by speeding up the slow-paced beginning of a match, and was recommended to use in all tournament games. The UpdatedRerelease fixed the bug but also gave every player an extra 100 lumber to start with.
* ''VideoGame/WarcraftIII'': Since {{knockback}} has to be triggered into the game, it can lead to some very strange situations on maps that use it, like a GrapplingHook overshooting its target and catapulting itself over walls, boundaries, and over the horizon.
** Units that use the same animation model (for example, the Archer unit and Dark Ranger HeroUnit) can have the same skin applied to them with very different results. For example, putting an Archer skin on the Dark Ranger [[EyesDoNotBelongThere moves her eyes to her cheeks,]] while her filled-in eye sockets [[GlowingEyesOfDoom continue to burn.]] Similarly, playing around with Myrmidon and Royal Guard skins gets ''massive'' dorsal fins and bizarre weapons.
* ''VideoGame/AgeOfEmpiresII''
** If your villager is being attacked by a wild animal, you can throw it off by having the villager start to build something underneath it. Animals can't share space with active construction sites, so it will obligingly walk away until it is off the space. While it's doing that, cancel the construction and get a head start.
** In the fourth Attila the Hun mission, you are tasked with destroying three major cities. Destroying the third spawns the massive Roman Army, a force of over a hundred top-tier units...unless you found and killed the placeholder unit on the map, which causes the army to be instantly defeated.
** In the fifth Saladin mission, "Jihad!", one of the three cities, Ascalon, is intended to attempt a Wonder victory. However, sometimes the AI for Ascalon bugs out and doesn't do anything. Given as how "Jihad!" is ThatOneLevel even without Ascalon going for the Wonder, this is immensely helpful.
** The in game scenario editor can do some interesting things with structures and terrain elements that shouldn't be possible. This has been abused ''thoroughly'' by the modding community creating custom campaigns.
** In the first scenario of the Attila the Hun campaign, it's possible to fire both the "Attila fleeing the Hun camp" and the "Bleda getting killed in the boar hunt" events if your timing is good. Because of the first event, the Huns will argue over whether Attila is a worthy leader or an honorless cur, but you get some free villagers to build a new force to fight back for your power; while the second event will make all Hun units instantly join your side upon Bleda's death. This has the practical benefit of giving you Bleda's entire faction with minimal bloodshed and also some free villagers. Another bug in the same scenario can occur if the player allies with the Scythians. While the Scythians will break their alliance with the Persians, the Persians don't always do the same and won't even bother to fight back as the Scythians slaughter their way through their base.
** In the fourth Sundjata scenario "Blood on The River Bank", a bug can cause Gbetos to be produced every second on one of your allies' Barracks, resulting in the player having a massive amount of infinitely-generated troops.
** In an early version of the game, in "The Crucible", the first Genghis Khan level, Genghis Khan -- an extremely strong and powerful hero with a Mangudai model -- could be converted to player control at the start, making it ridiculously easy.
** The AI never builds transport ships despite making docks, at least on lower difficulty levels, making an Island game of deathmatch much easier and regicide impossible to lose because you only need to worry about navy fights.
** It's possible to bypass the inability to attack your allies by having non-archer projectile units target the ground that just so happens to be where something of your ally's is at. Since you technically aren't attacking ''them'', the AI will never change their stance to you.
** Projectile damage is calculated on impact, not on being fired. Since dead units don't always have the same stats of they did when they were alive, if an attacker dies between firing its projectile and hitting something the damage is drastically lower. Cue trebuchets launching enormous boulders at barely-armoured structures and doing one point of damage.
*** Also, a bolt from a dead Scorpion can fell trees for some reason.
** If a Caravel (the Portugese unique naval unit) tries to hit something really, really close to it, the bolts will actually fly into the air backwards over the ship.
** Regicide mode is won by killing the enemy's King unit (which is unique to the mode). In the original release, playing any other game mode after a game of Regicide in the same play session would cause all players to be immediately defeated, probably due to the computer still associating victory with a surviving King unit.
* In ''VideoGame/PacificStorm'', before being patched, if you controlled directly a submarine (not tested with another warships) you could accelerate it indefinitely. Cue a submerged WWII sub going at, say, ''more than a hundred kilometers per hour'', far faster than in RealLife.
* In ''Videogame/BattleZone1998'', the Thumper is an EarthquakeMachine. Normally the Thumper wave just causes the typical HoverTank to spin about for a few moments as it regains control, but the Thumper has... interesting effects on the HumongousMecha, which are programmed to always remain vertical. Hit a walker with a Thumper wave and it will send the unit spinning wildly and ''violently'' out of control as it gets catapulted into the distance.
* In ''VideoGame/CrusaderKingsII'', there is an event in which a ruler with the Lunatic trait can [[CaligulasHorse appoint their horse Glitterhoof as chancellor]]. Naturally, the game does not allow Glitterhoof to get married or be granted land in the usual way, but due to an oversight he can be appointed as the successor to a bishop, including a powerful prince-bishop who rules a province or two. If this happens, he'll gain some courtiers of the same culture as him, i.e. more horses. These ones are treated by the game the same as regular human characters other than their appearance, and can marry humans and produce children who have a 50% chance of appearing as horses. Several people have made use of this to create powerful world-spanning horse empires. (The best-known example being detailed [[https://imgur.com/a/K1utf here]].)
** This later became an AscendedGlitch when randomised starts were introduced. As well as having the usual mode that mixes up the traditional historical countries, there was also added an "animal kingdom" mode which replaces several cultures with a variety of different animals. There are no restrictions on marriages or children.

** In the first scenario of the Attila the Hun campaign, it's possible to fire both the "Bleda getting killed in the boar hunt" and the "Attila fleeing the Hun camp" events if your timing is good. Because of the first event, the Huns will argue over whether Attila is a worthy leader or an honorless cur, but the second event will make all Hun units instantly join your side upon Bleda's death. This has the practical benefit of giving you Bleda's entire faction with minimal bloodshed. Another bug in the same scenario can occur if the player allies with the Scythians. While the Scythians will break their alliance with the Persians, the Persians don't always do the same and won't even bother to fight back as the Scythians slaughter their way through their base.

* ''VideoGame/EmpireEarth'' had an interesting one involving the AI: they'd attack the first unit to attack them until the unit died or was out of sight. So send a ranged unit to attack melee soldiers, they'll follow without fighting the rest of your army currently ripping them to shreds. While less useful in later ages, what with the disappearance of melee units, it still does wonders for your self esteem to lead Alexander's army without losing a single man.

* In ''VideoGame/AgeOfEmpiresI'', using multiple priests to convert one computer controlled unit would sometimes lock up the AI; since it couldn't decide which priest was a greater threat, it would get within attack range and just stop.

** The AI will try to garrison attacked villagers inside the Town Centre. There they can fire back at attackers with arrows while being less squishy. However, if you don't have any units in range of the Town Centre, the villagers will all ungarrison again. Repeat, indefinitely.