Revision as of 09:24, 26 March 2024

This page is a collection of tricks, glitches and exploits that mainly relate to surprising or unintuitive bugs/glitches of the game engine. It is not so much intended to collect advice about normal game mechanics / sophisticated techniques for good unit control that exploit the idiosyncrasies of particular unit types/commands, because whole guides have been written about those, but there is some overlap. Be warned that some of these tricks and glitches can be illegal in some tournaments (exploits are always illegal). Most sections state whether it is generally considered legal or illegal in (non-UMS) competitive rules.
The icon next to the title means the race that can perform it.

Tricks

A trick is a game mechanic that has been used (or abused) in an unintended manner.

Allied Mines Template:RaceIcon

Illegal. A Terran player places Spider Mines and proceeds to ally the opponent player. When the opponent moves his army over the mines, the player then unallies the opponent. The mines then acquire enemy targets as intended.

Manner Pylon Template:RaceIcon

Legal. A player constructs a Pylon or other structure in the enemy's mineral line to prevent smooth flow of resources and potentially trap some workers, slowing down the opponent's economy. Example clip here.

More info in the liquipedia article: Manner Pylon.

Drops to Defuse Mines Template:RaceIcon

Legal. A player uses a transport to unload units above a Spider Mine field. The single unit will attract all nearby mines and the splash damage will kill all the other mines or units that may be nearby. It is possible to load the unit as the mines explode to avoid taking damage while still accomplishing the purpose. Mines can also be repeatedly dragged by repeatedly dropping & loading a unit. Example clip here.

Crushing Interceptors Template:RaceIcon

Legal. When a Terran building lands over an Interceptor, the Interceptor will be destroyed. This was overlooked but not necessarily a glitch since the Interceptor meets all the "getting crushed" requirements. Despite Blizzard knowing this for a long time, it has remained in the game.

Crushing Tanks or Burrowed Units Template:RaceIcon

Note: crushing interceptors is covered in #Crushing Interceptors. When a Terran building lands on a unit such as a tank that is sieging, or a fully burrowed Zerg unit, the unit will be destroyed (rather than being pushed out of the way). This can frequently happen to a Terran player by accident when they construct an addon over a tank and siege the tank, or get a tank pushed onto a structure by an SCV and siege.

Using Unavailable Commands Template:RaceIcon

Legal. A player can not use Hold Position on worker units normally, but when selected in a group this can be done. A glitch can also enable Terran Flying Buildings to patrol, and some other things like #Larva Trick.

Larva Trick Template:RaceIcon

Legal. If you select a Larva or Larvae, then shift-select them together with other unit(s) (usually just an Overlord), then press stop, your Larvae will immediately move to the left side of your Hatchery. This is useful if you want to make a drone with the Larvae to gather minerals but don't have enough minerals or supply yet and the base's mineral patches are mostly located toward the left of the Hatchery, since the larva will end up closer to the minerals when you start to morph a drone. For more info, see Larva Trick.

Stacking Air Units Template:RaceIcon

Legal. When a group of air units are selected and moved, they normally move to a location relative to its current location, instead of stacked at the same target location. When another unit is selected in the group (from far away), this behavior is nullified and the units then move to the exact position clicked by the mouse cursor.

The first part of the following video is a more comprehensive analysis of air stacking techniques, including the magic box technique for stacking mutalisks using an overlord, latency of patrol vs hold position vs stop vs attack, scourge periodically adjusting course vs mutalisks and the chinese triangle technique for mutalisks vs scourge:

Lurker Stacking Template:RaceIcon

Legal. Burrowing Lurkers on top of one another to attack as one. Burrow each lurker on top of each other one by one by moving onto the previous burrowed lurker, repeat as necessary. It is best used in combination with 'Hold Lurker' for ambushes or on top of ramps/cliffs.

Bypassing Zerg Supply Template:RaceIcon

Legal. When a Zerg Drone constructs an Extractor or other structure, the supply count will decrease, enabling the creation of more units. The player can then cancel the structures to retrieve their drones, bypassing the maximum supply, but only a proportion of the spent resources are refunded. If used with extractor(s), it's called the "extractor trick" (which always costs exactly 13 minerals overall).

Extractor Trick to Drop Minerals/Gas Template:RaceIcon

Legal. If a drone that is holding minerals or gas starts morphing an extractor then cancels the morph, whatever it was holding will be gone. This can be useful in some cases to clear a mineral patch or simply waste your opponent's resources. Note that morphing and cancelling an extractor costs exactly 13 minerals overall. Example clip here.

Drone Heal via Extractor Template:RaceIcon

Legal. A drone that is not at full hitpoints can be returned to full hitpoints by making the drone start to morph an extractor then cancel the morph. Example clip here.

Hopping/Pushing Template:RaceIcon

Legal. A unit can be "pushed" to hop over obstacles using several different mechanics. This can be abused to hop over obstacles such as walls.

Using Workers - In any match up, a worker can be used in conjunction with any unit to push it through minerals. The unit that wants to be pressed through should move towards the minerals, and once it is in position, a worker unit should be told to mine the minerals, and once it is over the unit that wants to be pressed through, the worker should be told to stop mining. Since two units are on top of each other, the units will try to separate themselves. During this process, the player should constantly tell the units to move past the minerals.
Using Buildings
1. A Protoss player can glitch a probe through minerals by having a probe mine minerals, then building a pylon that will cause the probe to jump past the minerals. Then the pylon will be cancelled to save money. Example clip here.
2. If a production building is built next to a cliff or wall and surrounded by buildings and units, units produced by the production building may be created on the other side of the cliff/wall. Example clip here and a TL thread here.
3. If a Terran player builds near cliffs, the SCV could be pushed down or up a cliff when it was ordered to stop building.
Using Landing Terran Buildings - Landing a Terran building then moving units beneath it before it finished landing. This trick was used by NaDa at BlizzCon 2005 against Yellow and gained him a spot in Pimpest Plays 2005.
Using Add-ons - Simply have a Factory, Starport or Science Facility in place as shown in the picture. Place a unit close to the minerals and on the spot where the add-on will be. Place the add-on and simply right-click the unit past the Mineral Line.
Using Burrow - This trick does not require a worker unit or minerals. It can only be done by Zerg. Tell two units to burrow on top of each other next to the area where they should be pressed through. Then, tell both units to unburrow at the same time, and constantly tell both units to move past the obstruction.
Using Spells - When vultures lay mines they can be pushed through buildings. Example clip here.
Special tricks to get vulture or archon through diagonally-placed pylons - Either spam right-click, or send your vulture or archon in between the pylon gap so that it looks like it's already on the other side, then use a single Stop command (or spam H and S (hold and stop)). For more info see TL thread here.

More detailed instructions here:

Teleport Drone over a Morphing Building Template:RaceIcon

Legal. You can teleport your drone over a morphing building to morph an extractor by spam-clicking on the building to move next to it then order the drone to morph the extractor. Example clip here.

Mineral Walk Template:RaceIcon

Legal. This trick is constantly used by all players. It is basically telling workers to mine a mineral patch or vespene geyser. They will then proceed to walk past all units until told to stop, then will un-stack immediately and push surrounding units away.
This is one of the examples of bugs influencing the way the game is played. Specifically, a worker sent to mine a mineral patch in vision of any kind of unit will simply move through any obstacle, such as blocking buildings and units. If a moving stack of workers gets a stop/attack/hold command they will un-stack immediately and push surrounding units away. Maneuvers using Mineral Walk are legal, such as Worker drill which you can use to break the entrance of an opponent's base that's being blocked by units (e.g. use your SCVs to push away stasised units from ramps), or to block incoming army masses in 2on2. It is strictly illegal if the workers remain permanently stacked while attacking, in which case it is not Mineral Walk - it is the #Stacking Workers exploit.

Spider Mine Trick Template:RaceIcon

Legal. If you have really fast reaction time, you can give a command to place the second spider mine somewhere beneath the first one, on which cast the vulture will most of the time change its path. For more info see TL thread here.

Burrow Lurkers Faster Template:RaceIcon

Legal. If a lurker or lurkers are moving and you want them to burrow, it is faster to press "stop" or "hold position" before you burrow, to avoid the time decelerating. TL thread here. Also, because the lurkers automatically turn to face a South-East direction before burrowing, it is even faster if you turn them to face South-East via a "patrol" or "move" command before you press "stop" or "hold position" then burrow. Then, as a lurker is burrowing, you can spam attack move orders to make it attack a little earlier than letting it acquire a target on its own.

Extra Larva when Lair Finishes Template:RaceIcon

Legal. When a lair finishes, it resets its larva spawn timer. If a larva spawns just before the lair finishes, when the lair finishes you'll have two larvae. Example clip here and an instructions & advice how to time it here. Paraphrasing Cadenzie's instructions: there are a lot of different ways to do it. You can memorize all the different times on the clock that the larva usually spawns, e.g. if you start your lair at 3:02, that is a good timer. Another way is to wait until a larva spawns, then select a drone and morph an extractor, then continue normally and make three drones gather gas as soon as the extractor finishes, then morph the lair as soon as you have 100 gas.

Return Cargo when Transferring Workers Template:RaceIcon

Legal. Workers will always mine from the patch you tell them to. But if they already have cargo, pressing "c" will force them to bring minerals to the closest nexus/CC/hatchery/lair/hive and then continue with your instructions. So when you are transferring workers to a new base, press "c" immediately after telling them to transfer, and the ones with cargo will drop it off first. E.g. select 12 workers at base A then right-click a mineral patch at base B then immediately press "c". TL thread here.

Re-scout with Worker through Wall without Cheating Template:RaceIcon

Legal. Paraphrasing the TL thread here: Scout with your first worker or overlord into the enemy base. Once you are about to lose vision of the enemy base's minerals you do this: take another worker and queue him in an area where enemy doesn't scout and wont interrupt this worker. Queue movements back and forth in that area for however long you want to wait for your 2nd scout to scout enemy base again. Once you've queued move orders enough you finish with a shift-right-click on a mineral patch inside enemy base (this has to be done before vision is lost of the minerals). You now have a timed 2nd scout which can walk through a walled ramp. The only thing you need to figure out is at what time you want your 2nd scout, and test this map specifically how many queues of random movement in said corner you need before it proceeds to the enemy base's minerals. This would seem like a hack from enemy point of view as you wont have vision of the mineral patch for a long time, but seeing as your 2nd scout NEVER touches a gas for the gas bug it would be obvious from replay you aren't cheating.
Also, similarly, rather than using a 2nd worker to scout, if you currently have vision of the enemy base's minerals but your worker needs to leave the enemy base (e.g. because a dragoon is about to finish and start attacking your worker), you can command it to move out of the enemy base and queue movement commands to an area where enemy doesn't scout and wont interrupt this worker (preferably in big circles so if anything chases it, it will be less likely to be caught and killed), then finish with a shift-right-click on a mineral patch inside enemy base (this has to be done before vision of the minerals is lost).

Clustered Recall or Total Recall Template:RaceIcon

You can use archon fusing or probe & mineral then spamming patrol to make the units cluster together in a small area, then recall them to recall about 2-3 times the usual army size. For more info, see here. An example clip in a KSL pro game that the user Movie won against Sharp is here.

Lifted Buildings or Air Units to Prevent Targeting Under Them Template:RaceIcon

Legal. When you click on a pixel to target a unit, Brood War only allows you to target the top-most unit if there are multiple units there (e.g. an air unit above a ground unit). Consequently, units that are fully obscured by other units above them can not be targeted (unless using BWAPI). You can use e.g. a lifted building above spider mines (example clip here), or an overlord to avoid a defiler or lurker being irradiated. However, it also means that you can not select the unit(s) underneath unless they are already grouped or are selectable using Ctrl+click or Alt+click on other units (or using BWAPI).
Also, units may auto-acquire attack targets even if they are unreachable because the path is completely blocked by other units. Consequently, you may be able to help avoid ramps & narrow chokes from being attacked by enemy ground melee units by placing low-priority ground unit(s) such as SCVs in front with higher-priority ground unit(s) adjacent behind them (e.g. marines or siege tanks) and leave a flying building or overlord(s) or other air units above the lower-priority ground unit(s). The lower-priority ground unit(s) will not be auto-acquired as an attack target if the higher-priority ground unit(s) are seen and close enough, and the lower-priority ground unit(s) can not be manually targeted because they can't be clicked on to target them (unless the opponent is using BWAPI). The opponent may need to attack using air units or ranged units instead of ground melee units. Example clip here.

Nuclear Strike on Air Unit to Hide Red Dot Template:RaceIcon

Legal. Because Brood War displays the red dot of a Nuclear Strike on the ground even if there are air units above it, if you target an air unit with Nuclear Strike, the red dot may be hidden underneath it, making it hard to spot (unless the opponent is using BWAPI) unless the air unit moves. Example clip here.

Exploding Critters in Single-Player Mode Template:RaceIcon

(Legal). This is not really a trick or glitch - just something fun. You may already know that if you repeatedly click on a unit, it starts to say some funny things. What you may not know is that in single-player mode, if you click a critter 30 times, it will explode! It will not damage anything around it though.

Glitches

Also known as a game bug, it is a situation or event that the game's programming clearly did not account for and is usually unintended.

Stacking Workers Template:RaceIcon

Illegal. Also called "Gas Walk" or "Gas Trick" or "SCV Stack". This glitch enables worker units to remain permanently stacked while moving and attacking. Shift-clicking on gas near opponent’s blocked entrance enables them to slide through any possible unit or building wall. With a combination of move, patrol and gather commands a player can stack up to twelve workers permanently and move them around. Even with an attack command those workers will not un-stack. Normally, workers can only remain stacked when traveling between minerals; with this however it's not the case.

Cargo Glitch

Illegal unless you're using it to defend your mineral line. This glitch enables worker units to be pressed through any obstacle by repeatedly press "return cargo" (hotkey "c").

Plague on Interceptor Template:RaceIcon

Legal. When an Interceptor is plagued and damaged, it will return to the Carrier to repair itself. Once the interceptor receives its one-time repair, the plague causes damage, and the damaged interceptor will "leave and return" to the carrier in the same frame. Since the repair only occurs when an interceptor from outside enters the Carrier, it becomes stuck in an infinite loop, attempted to return to the Carrier even though it did not completely exit.

Unlimited Attack Range Glitch Template:RaceIcon

Legal. If a unit is in its pre-attack animation, attacking a non-combat unit through automatic target acquisition, then if an enemy unit attacks your unit or a unit nearby to your unit, your unit will acquire it as a target from an unlimited range. For example, if a Sunken colony changes its target before ending the "pre-attack" sequence it doesn't check the range. For more info see TL thread here.

This phenomenon is not limited to the Sunken Colony. Any type of unit can have infinite range (possibly except the Lurker and Firebat), because of the existence of the interrupt without range checking. The only reason why the Sunken Colony is special is because it fires its pre-attack sequence every single time it attacks and that the sequence is quite long. The pre-attack sequence is the window in which the interrupt must occur.
This theory also explains the well-known "Zealot killing two marines in one attack" behavior (see TL thread here). Basically, the Zealot has a pre-attack sequence before each of its "blades", which are one frame long. What happened was that the first Zealot blade killed the first marine, and during the pre-attack sequence for the second blade, the second marine attacked it, causing the Zealot to change target without checking range, and thereby killing the second marine. I believe that the fact that the first marine was a combat unit doesn't matter because dead unit = non-combat unit.
This bug can also enable a unit to attack a target that is within its minimum range, e.g. a sieged tank attacking adjacent enemy units, e.g.:

Disable Missile Turret Template:RaceIcon

Legal. Also called "Observer Over Turret". When a turret targets an air unit at the exact same position, the turret may be unable to reach the angle needed to fire missiles and get stuck. This is usually achieved by placing an Observer over an under construction Missile Turret and holding the position. Example clip here. The owner of the turret can press Stop until the head of the turret faces north. The attack angle requirement will be met and the turret will continue to fire.

Hold Lurker Template:RaceIcon

Legal. Lurkers can be hindered from attacking permanently. This can be done with two different ways: the lurkers are ordered to attack a structure under the fog of war or get a hold position command when grouped with an overlord. Even if units come into range the lurkers will not attack. This trick was illegal for a long time, but was allowed again because a player can also spam the "stop" command for the same result. Example clip here.
More info in the liquipedia article: Hold Lurker.

Faster Units Template:RaceIcon

Legal. When two units with a speed upgrade (or stimmed Terran infantry) collide when trying to pass each other, they will sometimes pass the other in the same direction or both have "jetpack"-like movement Northwards, leading them all the way to the edge of the map or until they hit something. This is abnormal because they are twice as fast as they would be if they just moved there normally. This is mostly seen with Zerglings, Hydralisks, and Zealots. An example clip for zealots here.

Medic Hold can't be Pushed Template:RaceIcon

When a Medic uses Hold Position, the medic will not move from its location, even if they are stacked or pushed by other units. You could order a structure to land, move a Medic under it, and order that Medic to Hold Position. It will never be pushed out.

Recall Glitch Template:RaceIcon

Illegal. Recall has a very special property which nullifies some unit proximity checks for a single frame if the exit is blocked. This can cause various side effects such as:

Worker units will gather or return a resource from anywhere on the map.
Units can completely recharge their shields from anywhere on the map (when moving to a Shield Battery).
A SCV's terrain collision will be disabled when moving to finish construction on a structure.
Queens will teleport to infest a Command Center.

Cloak Burrowable Units Template:RaceIcon

For this glitch, you need an Arbiter and any burrowing Zerg units. Set the Arbiter on patrol over a short area back and forth over where the units are cloaked and away to a point where they uncloak. Now, burrow the units uncloaked. Wait until the Arbiter comes to the point where the units would just be cloaking and unburrow. These units should stay cloaked permanently, unless you bring them back near the Arbiter or if you burrow and unburrow them again.

Build Cloaked Zerg Buildings Template:RaceIcon

You must first use the Cloak Burrowable Units glitch on a drone. Then, simply use the drone to build a building. This works for all buildings EXCEPT: Hatcheries, Creep Colonies, and Extractors.

File:CloakedZerg.png

Selection Glitch Template:RaceIcon

This is a precursor to several other glitches. It enables you to control units with a different unit selected. For example, you can have a ghost selected, but when you order it to move, it moves a wraith. The two units (or groups of units) involved are determined by you. In the following steps, source unit refers to the unit you will have selected, and target unit is the unit that you will actually be controlling.

Select source(selected) unit
Save to hotkey 1
Select target(controlled) unit
Save to hotkey 1 and recall hotkey 1 within 4 frames (or whatever your network frame delay happens to be).

This can be used for several other glitches. Note that this glitch was accidentally patched in BWAPI. It is used to perform commands that are normally only possible through exploits, and restricted in BWAPI.

Unlimited Flag Beacon Placements Template:RaceIcon

Use the selection glitch with two flag beacons of the same type, and you can place (and replace) one of them an infinite number of times (or until the flag spawn timer runs out).

Enemy Rally Point Changer Template:RaceIcon

Use the selection glitch with one of your factories selected, and the enemy factory controlled. Then set a rally point. Your enemy's rally point will change. Note that the enemy's structure doesn't get hotkeyed, but this doesn't matter since it was the last selection you made.

Infinite Unburrow Template:RaceIcon

Use the selection glitch with one of your burrowed units selected, and one or more unburrowed lurkers controlled. You can issue the unburrow order and the lurkers will play the unburrow animation, even when already unburrowed.

Destroy Warping Protoss Building to Find Enemy Location Template:RaceIcon

This makes use of the selection glitch. It works with any Protoss building (not just Pylon), but a Pylon is easiest to abuse because it is cheap, fast and has no psi requirement. To do it, start warping a Pylon, then when the Pylon is nearly finished warping, attack it with Probe and then cancel it. You canceled the Pylon, but in the user interface you still have the Pylon selected. Once the opponent starts making something, you can click the portrait or Ctrl+C to center that unit of your screen, which indicates the location of their unit, and potentially the location of their base (avoiding the need to scout them). TL thread here.

Half-Priced Archons Template:RaceIcon

This uses the selection glitch. You can create a real archon using a real HT and a hallucinated HT, and can do this for multiple pairs at once. To do it:

Create hallucinated high templars.
For all pairs of units where each pair consists of a real high templar and a hallucination, move units so that the real high templar that you want to merge is next to a hallucination that you want to merge.
Create a control group containing the real high templars that you want to merge.
Select all the high templars that you want to merge (hallucinations and real).
In rapid succession, set the same control group then select the control group then press merge (i.e "ctrl + 1, 1, r").

For more information, see TL thread here and Twitch clips here and here.

Goon Stop Template:RaceIcon

(Legal). This bug occurs most often with dragoons but also appears from time to time with any non-air ranged unit. When a player tries to move and shoot micro and spams too many commands, the units will stop and wont react to any other orders until given the "stop" command.

Stuck Units Template:RaceIcon

(Legal). This bug occurs most often with zerglings, hydralisks and zealots but also appears from time to time with any non-air unit. If a unit is about to start an attack animation when the target unit moves out of range, the unit will stop and wont move or react to any other orders except changing the direction it is facing, until given the "stop" command.

Spawn Broodling on Merging Templar or Morphing Drone Template:RaceIcon

Legal. Normally, archons and dark archons and buildings are immune to spawn broodling. However, if you use spawn broodling on a high templar or dark templar, and then it merges into an archon or dark archon while the broodling projectile is in the air, then the entire archon or dark archon will die and spawn 2 broodlings. It works exactly the same if you use spawn broodling on a drone that then morphs into a building (the morphing building dies, you get broodlings). Thread here.

Steal a Nuclear Silo containing an Armed Nuke Template:RaceIcon

Legal. Stealing an enemy nuclear silo containing an armed nuke still makes the enemy pay for the supply until you use it! Thread here.

Infest Command Center using Queen Hallucination Template:RaceIcon

Not useful in 1v1 games except on special maps that have e.g. neutral command centers, because three races are involved. In order to do this, you need a high templar, a queen (e.g. by using a dark archon to mind control a queen), and a unit that can attack (e.g. a probe or drone). To do it, damage the command center to below half health, hallucinate the queen, select a queen hallucination together with the attacking unit, and command them to attack the command center. The command center will be infested even though the queen is only a hallucination, and the hallucinated queen is still available for use after it has infested the command center. Instructional video here.

Drone Stuck Making Extractor Template:RaceIcon

If maelstrom is cast on a drone as it is about to morph an extractor, then another drone morphs an extractor, when maelstrom wears off, the original drone will remain stuck on the extractor (because it is still trying to morph an extractor) and doesn't respond to commands. Even if e.g. recall is used to move the drone, it still won't respond to commands. If another maelstrom is used on the drone, it will float directly back to the extractor. If the extractor is destroyed and the original drone eventually has the necessary conditions to make an extractor in its place, the drone will go under the geyser and needs e.g. splash damage to be destroyed. Instructional video here.

Map Edge Bug

A bug where if a unit (e.g. SCV) is in the extreme top right of the map and a battlecruiser is on top of it, the battlecruiser will not damage the SCV when attacking it because Brood War thinks it is off the edge of the map. Instructional video here.

Siege-SCV Bug Template:RaceIcon

(Legal). When a tank was sieged in between harvesting workers it exploded.

Vortex Bug

(Legal). A bug that can happen at certain location(s) on certain maps, typically on or near a ramp (a "ramp vortex"), where units overlap and get stuck at the location.

Bullet and Sprite Limits

(Legal). Brood War restricts the number of bullets and sprites that are displayed concurrently. A common example is that valkyries may stop launching missiles if there are too many units on the screen such as interceptors from mass carriers. It affects any unit with a bullet or sprite attack such as valkyries, dragoons, battlecruisers, and even some regular units when the bullet limit or sprite limit is reached. It may happen a lot in some UMS maps that have large numbers of units.

Shooting Uphill Without Vision Template:RaceIcon

Paraphrasing the TL thread here, due to faulty/haphazardly constructed cliff tiles (particularly in the Brood War tilesets Desert, Ice and Twilight) and doodads (including the vast majority of the new ramps introduced by Blizzard in patch 1.22!), units may be able to shoot uphill without vision of the target, from certain locations on certain maps. Example clip here.

Plague and Ensnare on Drone that Morphs Template:RaceIcon

Legal. Plague and Ensnare will persist from a drone onto a building it morphs into. Thread here.

Plague on Geyser Template:RaceIcon

Legal. A useless glitch (aesthetic only). Plague a refinery, assimilator, or extractor and kill it. The geyser will now be plagued itself.

Stasis Skin on Archon or Dark Archon Template:RaceIcon

Legal. A useless glitch (aesthetic only). If you cast stasis on an Archon or Dark Archon just as it finishes merging, after the stasis effect wears off, it can be commanded as usual, but the stasis skin (graphic) will remain. Instructional video here.

Exploits

An exploit is a glitch that must be performed intentionally (it cannot happen by accident). It is usually initiated using a hack to execute actions that are not available to the human user interface.

Sliding Terran Buildings Template:RaceIcon

File:CCslide.png

Illegal. The player lands a Terran building, and it moves ("slides") while on the ground to another destination without needing to Lift Off (for example, sliding a Command Center closer to minerals than normal).
To perform, lift off the CC and order it to land on a valid location, then hold shift and press S followed by a right-click on the location you want it to slide to. The CC stops sliding if colliding with any solid material.
Only works on version 1.04 and lower.

Forward Nexus Template:RaceIcon

File:NexusBug.png

Illegal. Protoss Players could build a Nexus very close to minerals/gas. For that a probe had to be blinded by an optical flare. The probe's vision range was limited along with the standard forbidden space between minerals and Nexus. The same trick worked on Drones and SCVs in a similar way; the only difference was that SCVs/Drones could only leap one hex-field between building and resources.
Only works in old versions.

Tank Under Landed Building Template:RaceIcon

Illegal. A few patches ago, Blizzard had "fixed" the tank under a building bug. However, little know that it is possible when sieged EXACTLY as the Building becomes registered as a ground unit.

Train Units in the Air Template:RaceIcon

Illegal. The player trains a unit and lifts off in the same frame. The lifted building retains the unit in the queue. When ordered to land, the unit starts being constructed. When right clicking as the building is landed, the building will lift off once more while still constructing the unit (which will be created where the building lifted off from). This enables, for example, a player to land a Factory in the opponent's base and construct a Siege Tank without needing to build a Machine Shop.

Flying Ground Units Template:RaceIcon

File:FlyingDT.gif

Illegal. Glitches enable ground units such as drones (example clip here) and SCVs (instructional video in Korean here) and templar to act like air units. This essentially means that workers can mine and take island expansions without drop tech and templar can storm worker lines without the use of shuttles.

Controlling a Nuke

Illegal. A.K.A. "Godly Nuke", "Nuke Hack" or "Nuke Anywhere" or "Infinite Nuke Cheat on Top of Ladder. This exploit enables a player (with the assistance of an external program) to stop a Nuclear Missile from launching (or landing), and move it around like a regular unit. The player can then proceed to re-launch the nuke at any location on the map (without the need for vision or a nearby ghost). When the nuke lands and deals damage, the nuke death animation can be interrupted and the same nuke can be re-launched infinite times.

Flooding the Order Buffer Template:RaceIcon

Illegal. The player sends commands (usually with the assistance of an external program) in such a way that they are queued in a ridiculous order, preventing any new orders from being executed. This causes all units to stop moving, as well as other major effects such as units unable to execute the "die" command, resulting in 0 hit point unkillable units, or the "cancel" command, but still being refunded the resources. Cancelling a Zerg Extractor will also refund several drones along with resources. Merged templar or merged dark templar may remain with the same graphic as when they were merging. A queen may teleport after infesting a command center. An instructional video in Korean that shows many of these effects without using an external program is here.

Liftoff Bug Template:RaceIcon

File:LiftStackBug.png

Illegal. Terran could stack his buildings via abusing the lift function. Whenever a building was lifted and given an order to build a unit/research an upgrade immediately after the first command the building seemed to actually produce something. In this state the building could be float to any direction (over land). If the order got canceled the building would land anywhere ignoring the standard conditions. If the command was canceled while landing the building got stuck in the position it had but still seemed to float.
Only works on version 1.09 and lower.

Otherwise Stacking Ground Units Template:RaceIcon

This section is a catch-all section to cover miscellaneous tricks/glitches/exploits that involve stacking ground units (either temporarily or permanently, and either intentionally or unintentionally) that are not already covered by other sections like #Lurker Stacking, #Hopping/Pushing, #Mineral Walk, #Return Cargo when Transferring Workers, #Re-scout with Worker through Wall without Cheating, #Clustered Recall or Total Recall, #Stacking Workers, #Cargo Glitch, #Medic Hold can't be Pushed, #Recall Glitch, #Drone Stuck Making Extractor, #Vortex Bug, #Tank Under Landed Building, #Flying Ground Units, #Flooding the Order Buffer, #Liftoff Bug.
It is legal to stack burrowed units. It is legal to unburrow them, so long as they do not remain permanently stacked. It is legal for non-burrowed ground unit(s) to be on top of burrowed unit(s) or dropped on top of spider mine(s). Often, ground units may unintentionally become overlapped and continue colliding simply due to lack of walkable space around them to automatically become unstacked using the game engine's anti-collision movement logic. E.g. units produced from production buildings that are trapped in too small an area, or units may naturally become overlapped (hopefully only temporarily) while moving across the map. If partially-overlapping tanks or unburrowed units become sieged/burrowed they will remain partially overlapped - this may be unintentional/unplanned and may be understandable, especially if they siege/burrow as a reaction to seeing enemy units nearby, so the legality of this is a grey area. So long as you did not intentionally plan for units to originally overlap, and so long as reasonably timely attempts are made to clear walkable space to help them become unstuck (when not sieged and not burrowed etc), this is legal, but best avoided if you can. This is probably too hard to judge or code for in bot-vs-bot competitions though. For all other cases, by default, unless you hear otherwise, you should assume that stacking ground units is illegal, especially if the units remain stacked while attacking or remain permanently stacked. If in doubt, ask on the SSCAIT Discord. If it's a new type of trick/glitch/exploit, it could be added to this page.

Videos

Tips

Balance changes

Balance changes were made in patch 1.02, 1.04, 1.05 and 1.08. Thus the game version makes a huge difference when attempting to speedrun a mission, especially for the Protoss campaign since it is not relying on any glitches.

Visible in-game timer

Chaoslauncher is a third-party program that comes with a plugin called APMAlert, which features a visible in-game timer. Unfortunately it is only compatible with version 1.16.1.

Unit orientations

Units will take up to one second to respond to a movement order when idle depending on their orientation relative to the movement position. If facing the movement position, units will respond immediately. This is important in the beginning of some missions as the orientations of units are randomly chosen.

Manipulating spawns

For Terran and Protoss, you can manipulate units to spawn at a location different to the default one. Simply block the spawn location with a unit or building and the produced units will spawn at the next free location counterclockwise to the spawn location.

Incorrect elapsed time

Pre-1.03, a bug exists that incorrectly displays the elapsed time after finishing a mission. The time will be about two seconds slower on short missions (< 2 minutes), although the effect for longer missions is currently unknown.

AI behavior

The AI behavior was improved in patch 1.04. The changes are not completely known, although it has been noted that the enemy units have a larger awareness radius post-1.03 and will chase down attacking units from a greater distance.

Brood War

The minimum version Brood War runs on is 1.04, thus many of the glitches in the base game are not available.

Pause glitch

The in-game timer is paused while the game is in the menu. This can be abused during transmissions, which usually need to finish before the game can continue. There are three types of transmissions which require different pausing techniques:

Game goes on like normal: Just bring up the menu during the transmission. Go back to the game when the transmission is over.
Game pauses: Click the menu button and keep holding left-click until the transmission starts. Go back to the game before the transmission is over, or the in-game timer will have proceeded like normal.
Screen centers on a position followed by a pause: Press F10 right before the transmission starts. This is tricky as the timing window is just a few frames. Go back to the game before the transmission is over.

Note: Pausing the game does actually increase the in-game time by a certain amount each time (amount varies, but at least half a second). This can easily be seen when running the visible in-game timer and comparing it to the actual completion time. This means that, while it does make hitting the timing window of the third transmission type easier, excessive pausing should be avoided.

Super mutas

Be sure to have Lurker Aspect researched and at least 50/100 minerals/gas. Assign a Hydralisk to a control group (ctrl-1). Select any unit or building except another Hydralisk, then quickly press ctrl-1, 1, L. Lowering the game speed helps. The unit will turn into a cocoon which will hatch a Lurker. However, if you cancel the morphing of the cocoon, the unit will instead turn into a Mutalisk. The resources spent are returned, and the supply count will increase by 1. The Mutalisk will also gain certain upgrades that the unit had before being transformed. Thus this glitch is best performed on Zerglings; the Mutalisk will receive both the speed and attack rate upgrade once researched, at a cost of only 50 minerals and 3 supply for two Mutalisks. Works on version 1.04.

Notes on Types of Glitches (To keep in mind while glitch-hunting)

Starcraft has had a lot of hackers and similar in it's history, as well as a lot of players, so it is likely to be very barren. However, there is always the possibility of new glitches, and they will probably fit into one of these categories.

Order queue glitches

Order queue glitches are caused when adding a command to the order queue, causing the command to be carried out at an unintended time, as the previous order has finished but the full consequences of that order have not yet been carried out. Order queue glitches include the CC slide glitch, the floating drone glitch and the floating templar glitch.

Order to Unintended Receiver Glitches

These are caused when an order is given to an unintended receiver, through the GUI changing too slowly as the unit's state changes (as in the glitch that allows you to produce units in a floating building), or through the GUI/Game control split technique, which also relies on the GUI changing too slowly. The Stacking units glitch, mobile nydus exit glitch, super mutas glitch, and unit production in floating building glitch rely on this.

Screwed-up Proximity Check Glitches

These are caused when, for whatever reason, starcraft's proximity algorithm screws up and it thinks that a unit is in the position that it is attempting to path to and so that it can begin whatever action it was going to do when it got there. This can occur when a unit is trapped and at the end of it's pathfinding, or when a arbiter attempts to recall a unit while hovering over unwalkable terrain. The teleporting drone glitch and floating scv glitch rely on this.

Other glitches

Other glitches include the Ignore Mineral Proximity glitch and the invincible drone glitch. These do not belong to any large family of glitches.

@@ Line 1: / Line 1: @@
-= Glitches =
+This page is a collection of tricks, glitches and exploits that mainly relate to surprising or unintuitive bugs/glitches of the game engine. It is not so much intended to collect advice about normal game mechanics / sophisticated techniques for good unit control that exploit the idiosyncrasies of particular unit types/commands, because whole guides have been written about those, but there is some overlap.
+Be warned that some of these tricks and glitches can be [[liquipedia:Competitive_Rules|illegal in some tournaments]] (exploits are always illegal). Most sections state whether it is generally considered legal or illegal in (non-UMS) competitive rules.<br/>
+The icon next to the title means the race that can perform it.
-== All Races ==
+== Tricks ==
+A trick is a game mechanic that has been used (or abused) in an unintended manner.
-=== Avoiding the Hub Placement Constraints (Ignore Mineral Proximity glitch) ===
+=== Allied Mines {{RaceIcon|t}} ===
-If you cannot see minerals or vespene geysers, they do not constrict the location in which you can build your command centre/hatchery/nexus. Therefore, if you can manage to start construction of a hub next to minerals, before actually revealing the minerals through the fog of war, you can get the hub to be closer to the minerals than intended. This can be achieved through the use of optical flares, or the build anywhere terran and zerg glitches. Works on at least version 1.00, and possibly other versions.
+Illegal. A Terran player places Spider Mines and proceeds to ally the opponent player. When the opponent moves his army over the mines, the player then unallies the opponent. The mines then acquire enemy targets as intended.
-For some reason, this does not occur for all mineral patches, but it does for most.
+=== Manner Pylon {{RaceIcon|p}} ===
+Legal. A player constructs a Pylon or other structure in the enemy's mineral line to prevent smooth flow of resources and potentially trap some workers, slowing down the opponent's economy. Example clip [https://youtu.be/r2rjuH7krW8?t=11 here].
-=== GUI/Game control split ===
+More info in the liquipedia article: [[liquipedia:Manner Pylon|Manner Pylon]].
-If (on a slow game speed) you set a control group and quickly select the same control group, the game will update faster than the user interface, meaning that the game will select the control group you set it to, while the interface will select the control group that had previously been set. This allows you to appear to be controlling one unit but really be controlling another. This is a precursor to many other glitches, allowing you to issue orders to unintended receivers.
+<div style="clear:both;"></div>
-=== Free resources in laggy conditions (controversial) ===
+=== Drops to Defuse Mines {{RaceIcon|tzp}} ===
-If the game is lagging, you can cancel units or structures multiple times, which results in free resources. Deliberately using third party programs to create lag should be disallowed, but if someone were to use a computer that meets the minimum system requirements for starcraft, without using third party programs, and it is possible to make the game lag during normal gameplay, the game may be considered to be running as intended, and the use of this glitch may be acceptable. The use of this glitch is highly controversial. As it requires old hardware or third-party software, this may require a different category to ordinary speedrunning. This got fixed in version 1.01, although a version of this relating to Guardians remained until version 1.02.
+Legal. A player uses a transport to unload units above a Spider Mine field. The single unit will attract all nearby mines and the splash damage will kill all the other mines or units that may be nearby. It is possible to load the unit as the mines explode to avoid taking damage while still accomplishing the purpose. Mines can also be repeatedly dragged by repeatedly dropping & loading a unit. Example clip [https://www.youtube.com/watch?v=r2rjuH7krW8&t=28s here].
+=== Crushing Interceptors {{RaceIcon|t}} ===
+Legal. When a Terran building lands over an Interceptor, the Interceptor will be destroyed. This was overlooked but not necessarily a glitch since the Interceptor meets all the "getting crushed" requirements. Despite Blizzard knowing this for a long time, it has remained in the game.
-== Terran ==
+=== Crushing Tanks or Burrowed Units {{RaceIcon|t}} ===
+Note: crushing interceptors is covered in [[#Crushing Interceptors]]. When a Terran building lands on a unit such as a tank that is sieging, or a fully burrowed Zerg unit, the unit will be destroyed (rather than being pushed out of the way). This can frequently happen to a Terran player by accident when they construct an addon over a tank and siege the tank, or get a tank pushed onto a structure by an SCV and siege.
-===CC slide===
+=== Using Unavailable Commands {{RaceIcon|tzp}} ===
-Allows you to slide a Command Center to unbuildable locations, e.g. right next to resources. You can produce SCVs while the CC is moving and also build right on top of it after performing this glitch. To perform, lift off the CC and order it to land on a valid location, then hold shift and press S followed by a right-click on the location you want it to slide to. The CC stops sliding if colliding with any solid material. Works on version 1.04 and lower.
+Legal. A player can not use Hold Position on worker units normally, but when selected in a group this can be done. A glitch can also enable Terran Flying Buildings to patrol, and some other things like [[#Larva Trick]].
-===Produce units while lifting a building===
+=== Larva Trick {{RaceIcon|z}} ===
-Press L then immediately the hotkey for the unit/upgrade you want to produce. The building will begin production already while lifting off. If you float or slide the building after performing this glitch, units will still spawn where the building first lifted off. Works for any unit/upgrade, but annoyingly hard to pull off. Used together with the CC slide to get the first SCV out earlier. Works on version 1.05 and lower.
+Legal. If you select a Larva or Larvae, then shift-select them together with other unit(s) (usually just an Overlord), then press stop, your Larvae will immediately move to the left side of your Hatchery. This is useful if you want to make a drone with the Larvae to gather minerals but don't have enough minerals or supply yet and the base's mineral patches are mostly located toward the left of the Hatchery, since the larva will end up closer to the minerals when you start to morph a drone. For more info, see [[liquipedia:Larva Trick|Larva Trick]].
-===Build anywhere===
+=== Stacking Air Units {{RaceIcon|tzp}} ===
-By trapping an SCV near a cliff, you can force it to build basically anywhere on the map. The only exceptions are unexplored areas as well as areas unreachable by land (unless you have had units in that area already). Once trapped, be sure there is a little breathing space for the SCV and then order it to move diagonally, then simply place the building on a valid location. The construction of the building will start immediately and the SCV will fly to the set location. Works on version 1.07 and lower.
+Legal. When a group of air units are selected and moved, they normally move to a location relative to its current location, instead of stacked at the same target location. When another unit is selected in the group (from far away), this behavior is nullified and the units then move to the exact position clicked by the mouse cursor.
+{{#ev:youtube|NfqQYJzq7o0}}
+The first part of the following video is a more comprehensive analysis of air stacking techniques, including the magic box technique for stacking mutalisks using an overlord, latency of patrol vs hold position vs stop vs attack, scourge periodically adjusting course vs mutalisks and the chinese triangle technique for mutalisks vs scourge:
+{{#ev:youtube|rWvoMrYCQBU}}
+=== Lurker Stacking {{RaceIcon|z}} ===
+Legal. Burrowing Lurkers on top of one another to attack as one. Burrow each lurker on top of each other one by one by moving onto the previous burrowed lurker, repeat as necessary. It is best used in combination with 'Hold Lurker' for ambushes or on top of ramps/cliffs.
-== Zerg ==
+=== Bypassing Zerg Supply {{RaceIcon|z}} ===
+Legal. When a Zerg Drone constructs an Extractor or other structure, the supply count will decrease, enabling the creation of more units. The player can then cancel the structures to retrieve their drones, bypassing the maximum supply, but only a proportion of the spent resources are refunded. If used with extractor(s), it's called the "extractor trick" (which always costs exactly 13 minerals overall).
-===Invincible Drone===
+=== Extractor Trick to Drop Minerals/Gas {{RaceIcon|z}} ===
-Simply mutate a Drone into a building while its HP is one, then cancel the mutation. The Drone will stay invincible until mutated into another building. Does not work with Extractors. Works on version 1.03 and lower.
+Legal. If a drone that is holding minerals or gas starts morphing an extractor then cancels the morph, whatever it was holding will be gone. This can be useful in some cases to clear a mineral patch or simply waste your opponent's resources. Note that morphing and cancelling an extractor costs exactly 13 minerals overall. Example clip [https://youtu.be/TJoCMH0mhk4?t=242 here].
-===Teleporting Drone===
+=== Drone Heal via Extractor {{RaceIcon|z}} ===
-Similar to the Terran build anywhere glitch, except you have to follow the standard building rules for Zerg. Unlike the SCV, the Drone can be trapped anywhere and will instantly mutate into the selected building. Works on version 1.07 and lower.
+Legal. A drone that is not at full hitpoints can be returned to full hitpoints by making the drone start to morph an extractor then cancel the morph. Example clip [https://youtu.be/TJoCMH0mhk4?t=242 here].
-Note that the drone teleports to the destination for one frame before turning into a building. Ordinarily, when a drone is holding a quest item and turns into a building, the quest item will be teleported to it's "home". So when trying to move a quest item to it's destination with this method, we have to interrupt the process of turning into a building without stopping the order to build until after the drone has teleported. The easiest way to do this is to use up minerals between starting the teleport and the drone reaching it's destination, so that you no longer have enough minerals to build the structure.
+=== Hopping/Pushing {{RaceIcon|tzp}} ===
+Legal. A unit can be "pushed" to hop over obstacles using several different mechanics. This can be abused to hop over obstacles such as walls.
+# '''Using Workers''' - In any match up, a worker can be used in conjunction with any unit to push it through minerals. The unit that wants to be pressed through should move towards the minerals, and once it is in position, a worker unit should be told to mine the minerals, and once it is over the unit that wants to be pressed through, the worker should be told to stop mining. Since two units are on top of each other, the units will try to separate themselves. During this process, the player should constantly tell the units to move past the minerals.
+# '''Using Buildings'''
+## A Protoss player can glitch a probe through minerals by having a probe mine minerals, then building a pylon that will cause the probe to jump past the minerals. Then the pylon will be cancelled to save money. Example clip [https://youtu.be/r2rjuH7krW8?t=96 here].
+## If a production building is built next to a cliff or wall and surrounded by buildings and units, units produced by the production building may be created on the other side of the cliff/wall. Example clip [https://youtu.be/q3j5fUraMaQ?t=447 here] and a TL thread [https://tl.net/forum/bw-strategy/548773-cliff-jump-revisited-1-in-a-1000-strategy here].
+## If a Terran player builds near cliffs, the SCV could be pushed down or up a cliff when it was ordered to stop building.
+# '''Using Landing Terran Buildings''' - Landing a Terran building then moving units beneath it before it finished landing. This trick was used by [[liquipedia:NaDa|NaDa]] at [[liquipedia:BlizzCon_2005|BlizzCon 2005]] against [[liquipedia:Yellow|Yellow]] and gained him a spot in [[liquipedia:Pimpest_Plays/2005#Place_7:_Barracks_Hop|Pimpest Plays 2005]].
+# '''Using Add-ons''' - Simply have a Factory, Starport or Science Facility in place as shown in the picture. Place a unit close to the minerals and on the spot where the add-on will be. Place the add-on and simply right-click the unit past the Mineral Line.
+# '''Using Burrow''' - This trick does not require a worker unit or minerals. It can only be done by Zerg. Tell two units to burrow on top of each other next to the area where they should be pressed through. Then, tell both units to unburrow at the same time, and constantly tell both units to move past the obstruction.
+# '''Using Spells''' - When vultures lay mines they can be pushed through buildings. Example clip [https://youtu.be/-9Yoptm2OJY?t=9 here].
+# '''Special tricks to get vulture or archon through diagonally-placed pylons''' - Either spam right-click, or send your vulture or archon in between the pylon gap so that it looks like it's already on the other side, then use a single Stop command (or spam H and S (hold and stop)). For more info see TL thread [https://tl.net/forum/brood-war/555088-vultures-can-slip-through-diagonally-placed-pylons here].
+{{#ev:youtube|qjqTw1SRH7Q}}
+More detailed instructions here:
+* [[liquipedia:Sliding through Mineral Lines|Sliding through Mineral Lines]]
+* [[liquipedia:Sliding through Building Ramp|Sliding through Building Ramp]]
-===Floating Drone #1===
+=== Teleport Drone over a Morphing Building {{RaceIcon|z}} ===
-Order a Drone to mutate into an Extractor, then shift-right-click where you want the Drone to float. When the Drone is about to mutate, use up minerals so that you do not have the required 50 for the Extractor. The Drone will float over any obstacles until the destination is reached or it is given another order. Works on version 1.09 and lower.
+Legal. You can teleport your drone over a morphing building to morph an extractor by spam-clicking on the building to move next to it then order the drone to morph the extractor. Example clip [https://www.youtube.com/watch?v=n7A8Ck8o7xE&t=2m20s here].
-This bug can also be triggered by telling a helper drone to mutate to an extractor before the flyer drone reaches the extractor. This makes it easier to execute this glitch if you already have a lot of minerals or you do not want to interrupt your economy too much. However, it does require the use of an extra drone.
+=== Mineral Walk {{RaceIcon|tzp}} ===
+Legal. This trick is constantly used by all players. It is basically telling workers to mine a mineral patch or vespene geyser. They will then proceed to walk past all units until told to stop, then will un-stack immediately and push surrounding units away.<br/>
+This is one of the examples of bugs influencing the way the game is played. Specifically, a worker sent to mine a mineral patch in vision of any kind of unit will simply move through any obstacle, such as blocking buildings and units. If a moving stack of workers gets a stop/attack/hold command they will un-stack immediately and push surrounding units away. Maneuvers using Mineral Walk are legal, such as [[liquipedia:Worker drill|Worker drill]] which you can use to break the entrance of an opponent's base that's being blocked by units (e.g. use your SCVs to push away stasised units from ramps), or to block incoming army masses in 2on2. It is strictly illegal if the workers remain permanently stacked while attacking, in which case it is not Mineral Walk - it is the [[#Stacking Workers]] exploit.
-===Floating Drone #2===
+=== Spider Mine Trick {{RaceIcon|t}} ===
-Order a Drone to mutate into an Extractor, then shift-click the geyser a few times and shift-right-click where you want the Drone to float. When the Drone is about to mutate, spam the stop command as fast as you can until you see the Drone's shadow disappear. The Drone will float over any obstacles until the destination is reached or it is given another order. Hard to perform, recommended to lower the game speed two steps when ordering the stop command. Works on any version other than 1.10.
+Legal. If you have really fast reaction time, you can give a command to place the second spider mine somewhere beneath the first one, on which cast the vulture will most of the time change its path. For more info see TL thread [http://www.teamliquid.net/forum/bw-strategy/21752-spider-mine-trick#19 here].
+{{#ev:youtube|-Pr00bS-nRs}}
-You need to press stop exactly one frame before the drone's shadow disappears. You can buffer stop commands before this point, as they will have no effect. You cannot, however, buffer commands after or on the frame that the drone's shadow disappears, or you will cancel the move order and the drone will stop floating. So it is a one-frame trick that can be buffered in exactly one direction.
+=== Burrow Lurkers Faster {{RaceIcon|z}} ===
+Legal. If a lurker or lurkers are moving and you want them to burrow, it is faster to press "stop" or "hold position" before you burrow, to avoid the time decelerating. TL thread [https://tl.net/forum/bw-strategy/557199-burrowing-lurkers-faster here]. Also, because the lurkers automatically turn to face a South-East direction before burrowing, it is even faster if you turn them to face South-East via a "patrol" or "move" command before you press "stop" or "hold position" then burrow. Then, as a lurker is burrowing, you can spam attack move orders to make it attack a little earlier than letting it acquire a target on its own.
+{{#ev:youtube|8kWf7bcHjqE}}
-Floating Drone #2 allows you to command the drone after it has started floating, although doing so will cause it to cease to float. It also avoids the landing procedure that happens if you use the other version of the floating drone trick. This means that Floating Drone #2 is generally better than Floating Drone #1, but it is much harder to execute.
+=== Extra Larva when Lair Finishes {{RaceIcon|z}} ===
+Legal. When a lair finishes, it resets its larva spawn timer. If a larva spawns just before the lair finishes, when the lair finishes you'll have two larvae. Example clip [https://www.youtube.com/watch?v=xJe05zvBeio&t=359s here] and an instructions & advice how to time it [https://youtu.be/4Us3GWUa9c0?t=465 here]. Paraphrasing Cadenzie's instructions: there are a lot of different ways to do it. You can memorize all the different times on the clock that the larva usually spawns, e.g. if you start your lair at 3:02, that is a good timer. Another way is to wait until a larva spawns, then select a drone and morph an extractor, then continue normally and make three drones gather gas as soon as the extractor finishes, then morph the lair as soon as you have 100 gas.
-===Stacking units===
+=== Return Cargo when Transferring Workers {{RaceIcon|ptz}} ===
-Burrow any unit and assign it to a control group (ctrl-1). Select the units you want stacked, then quickly press U, ctrl-1, 1, U. Order the units around, and if the glitch was successful, the units should now be able to stack with each other. Burrowing turns them normal again. Also, lowering the game speed helps out a lot, since the key combination needs to be done before they have finished burrowing. Works on version 1.14 and lower.
+Legal. Workers will always mine from the patch you tell them to. But if they already have cargo, pressing "c" will force them to bring minerals to the closest nexus/CC/hatchery/lair/hive and then continue with your instructions. So when you are transferring workers to a new base, press "c" immediately after telling them to transfer, and the ones with cargo will drop it off first. E.g. select 12 workers at base A then right-click a mineral patch at base B then immediately press "c". TL thread [https://tl.net/forum/brood-war/534502-a-small-trick-when-transferring-workers here].
-===Mobile Nydus Canal exit===
+=== Re-scout with Worker through Wall without Cheating {{RaceIcon|ptz}} ===
-When the exit of a Nydus Canal is mutating, morph an Overlord and assign it to a control group (ctr-1). Select the exit then quickly press ctrl-1, 1 and esc. Lowering the game speed helps. If done correctly, a Drone will pop out of the canceled exit which now acts as a mobile exit, even while burrowed or when inside an Overlord. Works on version 1.14 and lower.
+Legal. Paraphrasing the TL thread [https://tl.net/forum/bw-strategy/552163-workers-through-wall-without-cheatgasbug here]: Scout with your first worker or overlord into the enemy base. Once you are about to lose vision of the enemy base's minerals you do this: take another worker and queue him in an area where enemy doesn't scout and wont interrupt this worker. Queue movements back and forth in that area for however long you want to wait for your 2nd scout to scout enemy base again. Once you've queued move orders enough you finish with a shift-right-click on a mineral patch inside enemy base (this has to be done before vision is lost of the minerals). You now have a timed 2nd scout which can walk through a walled ramp. The only thing you need to figure out is at what time you want your 2nd scout, and test this map specifically how many queues of random movement in said corner you need before it proceeds to the enemy base's minerals. This would seem like a hack from enemy point of view as you wont have vision of the mineral patch for a long time, but seeing as your 2nd scout NEVER touches a gas for the gas bug it would be obvious from replay you aren't cheating.<br/>
+Also, similarly, rather than using a 2nd worker to scout, if you currently have vision of the enemy base's minerals but your worker needs to leave the enemy base (e.g. because a dragoon is about to finish and start attacking your worker), you can command it to move out of the enemy base and queue movement commands to an area where enemy doesn't scout and wont interrupt this worker (preferably in big circles so if anything chases it, it will be less likely to be caught and killed), then finish with a shift-right-click on a mineral patch inside enemy base (this has to be done before vision of the minerals is lost).
-===Drone Heal===
+=== Clustered Recall or Total Recall {{RaceIcon|p}} ===
-Mutating a drone into a building will ordinarily mean that the drone turns into a building, using the drone's ID. However, turning a drone into an extractor will cause the geyser to turn into the extractor, and the drone to be deleted. When cancelling the extractor, it does not know what hp the drone that built it was at, and so it creates a completely new drone with full health. This is really only useful in RTA runs or marathon-safe strategies, so that if you fail the Invincible Drone glitch you can try again.
+You can use archon fusing or probe & mineral then spamming patrol to make the units cluster together in a small area, then recall them to recall about 2-3 times the usual army size. For more info, see [http://www.teamliquid.net/forum/brood-war/533467-game-changing-discovery-clustered-recall here]. An example clip in a KSL pro game that the user [[liquipedia:Movie|Movie]] won against [[liquipedia:Sharp|Sharp]] is [https://clips.twitch.tv/CallousHardAardvarkUncleNox here].
+{{#ev:youtube|Uk9oJl2Log8}}
-===Extractor Trick===
+=== Lifted Buildings or Air Units to Prevent Targeting Under Them {{RaceIcon|tzp}} ===
-This is a very well known trick, which relies on the fact that a drone is consumed when making a building, and refunded when it is cancelled. By mutating a drone into a cheap building (such as an extractor or creep colony), you will lose supply. You may then build units even if you were previously supply capped, and then cancel the building to get the drone back. This allows you to go over your supply cap at the cost of a small amount of minerals (as cancelling a building does not give a full refund). This is particularly useful in accelerating your economy during the earlygame.
+Legal. When you click on a pixel to target a unit, Brood War only allows you to target the top-most unit if there are multiple units there (e.g. an air unit above a ground unit). Consequently, units that are fully obscured by other units above them can not be targeted (unless using BWAPI). You can use e.g. a lifted building above spider mines (example clip [https://youtu.be/q3j5fUraMaQ?t=308 here]), or an overlord to avoid a defiler or lurker being irradiated. However, it also means that you can not select the unit(s) underneath unless they are already grouped or are selectable using Ctrl+click or Alt+click on other units (or using BWAPI).<br/>
+Also, units may auto-acquire attack targets even if they are unreachable because the path is completely blocked by other units. Consequently, you may be able to help avoid ramps & narrow chokes from being attacked by enemy ground melee units by placing low-priority ground unit(s) such as SCVs in front with higher-priority ground unit(s) adjacent behind them (e.g. marines or siege tanks) and leave a flying building or overlord(s) or other air units above the lower-priority ground unit(s). The lower-priority ground unit(s) will not be auto-acquired as an attack target if the higher-priority ground unit(s) are seen and close enough, and the lower-priority ground unit(s) can not be manually targeted because they can't be clicked on to target them (unless the opponent is using BWAPI). The opponent may need to attack using air units or ranged units instead of ground melee units. Example clip [https://youtu.be/-9Yoptm2OJY?t=126 here].
+=== Nuclear Strike on Air Unit to Hide Red Dot {{RaceIcon|t}} ===
+Legal. Because Brood War displays the red dot of a Nuclear Strike on the ground even if there are air units above it, if you target an air unit with Nuclear Strike, the red dot may be hidden underneath it, making it hard to spot (unless the opponent is using BWAPI) unless the air unit moves. Example clip [https://youtu.be/-9Yoptm2OJY?t=264 here].
-== Protoss ==
+=== Exploding Critters in Single-Player Mode {{RaceIcon|ptz}} ===
+(Legal). This is not really a trick or glitch - just something fun. You may already know that if you repeatedly click on a unit, it starts to say some funny things. What you may not know is that in single-player mode, if you click a critter 30 times, it will explode! It will not damage anything around it though.
-===Flying Templar===
+== Glitches ==
-If you give two high templar or dark templar the order to merge, shift-click some location and give them the stop command as they are about to merge, they will float over any terrain to travel to the location that was shift-clicked. Works on version 1.10 and lower.
+Also known as a game bug, it is a situation or event that the game's programming clearly did not account for and is usually unintended.
+=== Stacking Workers {{RaceIcon|tzp}} ===
+Illegal. Also called "Gas Walk" or "Gas Trick" or "SCV Stack". This glitch enables worker units to remain permanently stacked while moving and attacking. Shift-clicking on gas near opponent’s blocked entrance enables them to slide through any possible unit or building wall. With a combination of move, patrol and gather commands a player can stack up to twelve workers permanently and move them around. Even with an attack command those workers will not un-stack. Normally, workers can only remain stacked when traveling between minerals; with this however it's not the case.
+{{#ev:youtube|YizYdl5c0lY}}
-== Near-Useless but Interesting Glitches (in the interest of completeness) ==
+=== Cargo Glitch ===
+Illegal unless you're using it to defend your mineral line. This glitch enables worker units to be pressed through any obstacle by repeatedly press "return cargo" (hotkey "c").
-=== Mine from anywhere (at the cost of 150 energy) ===
+=== Plague on Interceptor {{RaceIcon|z}} ===
-Order a probe to mine from a patch of minerals. Place an arbiter on top of somewhere unwalkable, such as ocean or a cliff. Tell the arbiter to recall the probe, making sure to lead the shot so that the probe does not move out of the way. The probe will stop and begin mining minerals, even if it is nowhere near the mineral patch. This also works with probes returning minerals.
+Legal. When an [[liquipedia:Interceptor|Interceptor]] is [[liquipedia:Defiler#Plague|plagued]] and damaged, it will return to the [[liquipedia:Carrier|Carrier]] to repair itself. Once the interceptor receives its one-time repair, the plague causes damage, and the damaged interceptor will "leave and return" to the carrier in the same frame. Since the repair only occurs when an interceptor from outside enters the Carrier, it becomes stuck in an infinite loop, attempted to return to the Carrier even though it did not completely exit.
-This actually leads to a few more similar glitches, but not every ability can be used at long range in this way. Most disappointingly, long-range nuclear strikes cannot be initiated at long range (at least without additional, unknown steps)
+=== Unlimited Attack Range Glitch {{RaceIcon|ztp}} ===
+Legal. If a unit is in its pre-attack animation, attacking a non-combat unit through automatic target acquisition, then if an enemy unit attacks your unit or a unit nearby to your unit, your unit will acquire it as a target from an unlimited range. For example, if a Sunken colony changes its target before ending the "pre-attack" sequence it doesn't check the range. For more info see TL thread [http://www.teamliquid.net/forum/brood-war/96786-how-to-make-sunkens-have-infinite-range here].
+{{#ev:youtube|v1W_T1Us5RY}}
+This phenomenon is not limited to the Sunken Colony. Any type of unit can have infinite range (possibly except the Lurker and Firebat), because of the existence of the interrupt without range checking. The only reason why the Sunken Colony is special is because it fires its pre-attack sequence every single time it attacks and that the sequence is quite long. The pre-attack sequence is the window in which the interrupt must occur.<br/>
+This theory also explains the well-known "Zealot killing two marines in one attack" behavior (see TL thread [https://tl.net/forum/brood-war/372937-bug-zealot-double-kill here]). Basically, the Zealot has a pre-attack sequence before each of its "blades", which are one frame long. What happened was that the first Zealot blade killed the first marine, and during the pre-attack sequence for the second blade, the second marine attacked it, causing the Zealot to change target without checking range, and thereby killing the second marine. I believe that the fact that the first marine was a combat unit doesn't matter because dead unit = non-combat unit.<br/>
+This bug can also enable a unit to attack a target that is within its minimum range, e.g. a sieged tank attacking adjacent enemy units, e.g.:
+{{#ev:youtube|CcLgTPQPjoU}}
-For example, building structures with SCVs at a long range will work (but building structures with probes at long range will not). This can be done normally with the SCV float glitch, however, so this is useless. If used on probes gathering gas, the probes will teleport to be inside the refinary. This is still practically useless, however.
+=== Disable Missile Turret {{RaceIcon|p}} ===
+Legal. Also called "Observer Over Turret". When a turret targets an air unit at the exact same position, the turret may be unable to reach the angle needed to fire missiles and get stuck. This is usually achieved by placing an [[liquipedia:Observer|Observer]] over an under construction [[liquipedia:Missile Turret|Missile Turret]] and holding the position. Example clip [https://youtu.be/r2rjuH7krW8?t=128 here]. The owner of the turret can press Stop until the head of the turret faces north. The attack angle requirement will be met and the turret will continue to fire.
-=== Permanently Invisible Zerg Units and Buildings (requiring the use of the Protoss Arbiter ) ===
+=== Hold Lurker {{RaceIcon|z}} ===
-If a zerg drone or other burrowing unit (obtainable via mind-control) is burrowed at the same time as it enters the cloaking field of an arbiter, then it will become permanently invisible. Buildings (other than extractors) created from this drone will also be permanently invisible.
+Legal. Lurkers can be hindered from attacking permanently. This can be done with two different ways: the lurkers are ordered to attack a structure under the fog of war or get a hold position command when grouped with an overlord. Even if units come into range the lurkers will not attack. This trick was illegal for a long time, but was allowed again because a player can also spam the "stop" command for the same result. Example clip [https://youtu.be/TJoCMH0mhk4?t=59 here].<br/>
+More info in the liquipedia article: [[liquipedia:Hold Lurker|Hold Lurker]].
-=== Fully Refund Mutalisks (excluding larva cost) ===
+=== Faster Units {{RaceIcon|zpt}} ===
-Tell a mutalisk to morph to a guardian. Tell the mutalisk to stop morphing to a guardian twice in rapid succession on a slow gamespeed. The mutalisk will first revert to the morphing state, used for morphing larvae to mutalisks. The mutalisk would then revert to its normal state, but it is instead given a cancel order. Because it is in a state used for morphing larvae to mutalisks, it knows what to do and refunds it's full cost. Unfortunately, a similar glitch does not work on sunken colonies (this would be more useful), because they do not come out of larva. In laggy situations, according to the starcraft patch notes, this can give multiple refunds. Fixed in version 1.02.
+Legal. When two units with a speed upgrade (or stimmed Terran infantry) collide when trying to pass each other, they will sometimes pass the other in the same direction or both have "jetpack"-like movement Northwards, leading them all the way to the edge of the map or until they hit something. This is abnormal because they are twice as fast as they would be if they just moved there normally. This is mostly seen with Zerglings, Hydralisks, and Zealots. An example clip for zealots [https://youtu.be/wzWq6JfZkmY?t=13m16s here].
-=== Unlimited Range Glitch ===
+=== Medic Hold can't be Pushed {{RaceIcon|t}} ===
-If a unit is in it's pre-attack animation, attacking a non-combat unit through automatic target acquisition, then if an enemy unit attacks your unit or a unit nearby to your unit, your unit will acquire it as a target from an unlimited range. [http://www.teamliquid.net/forum/brood-war/96786-how-to-make-sunkens-have-infinite-range This is discussed here in Team Liquid]
+When a Medic uses Hold Position, the medic will not move from its location, even if they are stacked or pushed by other units. You could order a structure to land, move a Medic under it, and order that Medic to Hold Position. It will never be pushed out.
-=== Untested Crazy Drone Bug from some Random You-Tube video (lol) ===
+=== Recall Glitch {{RaceIcon|p}} ===
-If you tell a (presumably mind-controlled) drone to become an extractor, use maelstrom on it, and get another drone to become an extractor on the same geyser, the drone will continuously attempt to build an extractor on the geyser, resulting in a lot of error messages. Recalling the drone after it has reached the geyser will cause the drone to fly back to the geyser and continue to attempt to become an extractor. May also work if minerals become insufficient to build the geyser (similarly to the floating drone trick).
+Illegal. [[liquipedia:Recall|Recall]] has a very special property which nullifies some unit proximity checks for a single frame if the exit is blocked. This can cause various side effects such as:
+* Worker units will gather or return a resource from anywhere on the map.
+* Units can completely recharge their shields from anywhere on the map (when moving to a Shield Battery).
+* A SCV's terrain collision will be disabled when moving to finish construction on a structure.
+* Queens will teleport to infest a Command Center.
-=== Plague Recall ===
+=== Cloak Burrowable Units {{RaceIcon|zp}} ===
+For this glitch, you need an Arbiter and any burrowing Zerg units. Set the Arbiter on patrol over a short area back and forth over where the units are cloaked and away to a point where they uncloak. Now, burrow the units uncloaked. Wait until the Arbiter comes to the point where the units would just be cloaking and unburrow. These units should stay cloaked permanently, unless you bring them back near the Arbiter or if you burrow and unburrow them again.
+{{#ev:youtube|3NF3QR58a-0}}
-Untested, but according to multiple sources:
+=== Build Cloaked Zerg Buildings {{RaceIcon|zp}} ===
+You must first use the [[#Cloak_Burrowable_Units|Cloak Burrowable Units]] glitch on a drone. Then, simply use the drone to build a building. This works for all buildings EXCEPT: Hatcheries, Creep Colonies, and Extractors.
+[[File:CloakedZerg.png|center]]
-"Plague can be "recalled" by enemy's Arbiter. This Plague + Recall replay is an example of Plague + Recall effect that was caused at about 39:10 when Recall from center to 3 o'clock natural was done and Plague was casted to center. The animation of Plague was shown at center but effect (units and building affected) was applied at 3 o'clock natural. (recalling Arbiter was affected too)." - Liquipedia
+=== Selection Glitch {{RaceIcon|zpt}} ===
+This is a precursor to several other glitches. It enables you to control units with a different unit selected. For example, you can have a ghost selected, but when you order it to move, it moves a wraith. The two units (or groups of units) involved are determined by you. In the following steps, source unit refers to the unit you will have selected, and target unit is the unit that you will actually be controlling.
-Replay link was broken.
+# Select source(selected) unit
+# Save to hotkey 1
+# Select target(controlled) unit
+# Save to hotkey 1 and recall hotkey 1 within 4 frames (or whatever your network frame delay happens to be).
+This can be used for several other glitches. ''Note that this glitch was accidentally patched in BWAPI.'' It is used to perform commands that are normally only possible through exploits, and restricted in BWAPI.
+==== Unlimited Flag Beacon Placements {{RaceIcon|zpt}} ====
+Use the selection glitch with two flag beacons of the same type, and you can place (and replace) one of them an infinite number of times (or until the flag spawn timer runs out).
+==== Enemy Rally Point Changer {{RaceIcon|zpt}} ====
+Use the selection glitch with one of your factories selected, and the enemy factory controlled. Then set a rally point. Your enemy's rally point will change. Note that the enemy's structure doesn't get hotkeyed, but this doesn't matter since it was the last selection you made.
+==== Infinite Unburrow {{RaceIcon|z}} ====
+Use the selection glitch with one of your burrowed units selected, and one or more unburrowed lurkers controlled. You can issue the unburrow order and the lurkers will play the unburrow animation, even when already unburrowed.
+==== Destroy Warping Protoss Building to Find Enemy Location {{RaceIcon|p}} ====
+This makes use of the selection glitch. It works with any Protoss building (not just Pylon), but a Pylon is easiest to abuse because it is cheap, fast and has no psi requirement. To do it, start warping a Pylon, then when the Pylon is nearly finished warping, attack it with Probe and then cancel it. You canceled the Pylon, but in the user interface you still have the Pylon selected. Once the opponent starts making something, you can click the portrait or Ctrl+C to center that unit of your screen, which indicates the location of their unit, and potentially the location of their base (avoiding the need to scout them). TL thread [https://tl.net/forum/brood-war/551565-pylon-bug-to-find-opponents-location here].
+==== Half-Priced Archons {{RaceIcon|p}} ====
+This uses the selection glitch. You can create a real archon using a real HT and a hallucinated HT, and can do this for multiple pairs at once. To do it:
+# Create hallucinated high templars.
+# For all pairs of units where each pair consists of a real high templar and a hallucination, move units so that the real high templar that you want to merge is next to a hallucination that you want to merge.
+# Create a control group containing the real high templars that you want to merge.
+# Select all the high templars that you want to merge (hallucinations and real).
+# In rapid succession, set the same control group then select the control group then press merge (i.e "ctrl + 1, 1, r").
+For more information, see TL thread [https://www.teamliquid.net/forum/brood-war/543897-half-priced-archons-new-bug here] and Twitch clips [https://clips.twitch.tv/PeppySmilingNostrilMcaT here] and [https://clips.twitch.tv/TastyElatedMagpieWoofer here].
+{{#ev:youtube|MopKfp3RamY}}
+=== Goon Stop {{RaceIcon|ptz}} ===
+(Legal). This bug occurs most often with dragoons but also appears from time to time with any non-air ranged unit. When a player tries to move and shoot micro and spams too many commands, the units will stop and wont react to any other orders until given the "stop" command.
+=== Stuck Units {{RaceIcon|ptz}} ===
+(Legal). This bug occurs most often with zerglings, hydralisks and zealots but also appears from time to time with any non-air unit. If a unit is about to start an attack animation when the target unit moves out of range, the unit will stop and wont move or react to any other orders except changing the direction it is facing, until given the "stop" command.
+=== Spawn Broodling on Merging Templar or Morphing Drone {{RaceIcon|z}} ===
+Legal. Normally, archons and dark archons and buildings are immune to spawn broodling. However, if you use spawn broodling on a high templar or dark templar, and then it merges into an archon or dark archon while the broodling projectile is in the air, then the entire archon or dark archon will die and spawn 2 broodlings. It works exactly the same if you use spawn broodling on a drone that then morphs into a building (the morphing building dies, you get broodlings). Thread [https://satirist.org/ai/starcraft/blog/archives/418-useless-and-amusing-Brood-War-mechanics-trivia.html#c6624 here].
+{{#ev:youtube|watch?v=k2HvWmMaC6M}}
+=== Steal a Nuclear Silo containing an Armed Nuke {{RaceIcon|t}} ===
+Legal. Stealing an enemy nuclear silo containing an armed nuke still makes the enemy pay for the supply until you use it! Thread [https://satirist.org/ai/starcraft/blog/archives/418-useless-and-amusing-Brood-War-mechanics-trivia.html#c6610 here].
+=== Infest Command Center using Queen Hallucination {{RaceIcon|p}} ===
+Not useful in 1v1 games except on special maps that have e.g. neutral command centers, because three races are involved. In order to do this, you need a high templar, a queen (e.g. by using a dark archon to mind control a queen), and a unit that can attack (e.g. a probe or drone). To do it, damage the command center to below half health, hallucinate the queen, select a queen hallucination together with the attacking unit, and command them to attack the command center. The command center will be infested even though the queen is only a hallucination, and the hallucinated queen is still available for use after it has infested the command center. Instructional video [https://www.youtube.com/watch?v=3NF3QR58a-0&t=9m4s here].
+=== Drone Stuck Making Extractor {{RaceIcon|p}} ===
+If maelstrom is cast on a drone as it is about to morph an extractor, then another drone morphs an extractor, when maelstrom wears off, the original drone will remain stuck on the extractor (because it is still trying to morph an extractor) and doesn't respond to commands. Even if e.g. recall is used to move the drone, it still won't respond to commands. If another maelstrom is used on the drone, it will float directly back to the extractor. If the extractor is destroyed and the original drone eventually has the necessary conditions to make an extractor in its place, the drone will go under the geyser and needs e.g. splash damage to be destroyed. Instructional video [https://youtu.be/3NF3QR58a-0?t=3m45s here].
+=== Map Edge Bug ===
+A bug where if a unit (e.g. SCV) is in the extreme top right of the map and a battlecruiser is on top of it, the battlecruiser will not damage the SCV when attacking it because Brood War thinks it is off the edge of the map. Instructional video [https://www.youtube.com/watch?v=3NF3QR58a-0&t=13m48s here].
+=== Siege-SCV Bug {{RaceIcon|t}} ===
+(Legal). When a tank was sieged in between harvesting workers it exploded.
+=== Vortex Bug ===
+(Legal). A bug that can happen at certain location(s) on certain maps, typically on or near a ramp (a "ramp vortex"), where units overlap and get stuck at the location.
+=== Bullet and Sprite Limits ===
+(Legal). Brood War restricts the number of bullets and sprites that are displayed concurrently. A common example is that valkyries may stop launching missiles if there are too many units on the screen such as interceptors from mass carriers. It affects any unit with a bullet or sprite attack such as valkyries, dragoons, battlecruisers, and even some regular units when the bullet limit or sprite limit is reached. It may happen a lot in some UMS maps that have large numbers of units.
+=== Shooting Uphill Without Vision {{RaceIcon|ptz}} ===
+Paraphrasing the TL thread [https://tl.net/forum/brood-war/569009-shooting-uphill-with-no-vision here], due to faulty/haphazardly constructed cliff tiles (particularly in the Brood War tilesets Desert, Ice and Twilight) and doodads (including the vast majority of the new ramps introduced by Blizzard in patch 1.22!), units may be able to shoot uphill without vision of the target, from certain locations on certain maps. Example clip [https://youtu.be/bGob3nObjkU?t=4732 here].
+=== Plague and Ensnare on Drone that Morphs {{RaceIcon|z}} ===
+Legal. Plague and Ensnare will persist from a drone onto a building it morphs into. Thread [https://satirist.org/ai/starcraft/blog/archives/418-useless-and-amusing-Brood-War-mechanics-trivia.html#c6624 here].
+=== Plague on Geyser {{RaceIcon|z}} ===
+Legal. A useless glitch (aesthetic only). Plague a refinery, assimilator, or extractor and kill it. The geyser will now be plagued itself.
+=== Stasis Skin on Archon or Dark Archon {{RaceIcon|p}} ===
+Legal. A useless glitch (aesthetic only). If you cast stasis on an Archon or Dark Archon just as it finishes merging, after the stasis effect wears off, it can be commanded as usual, but the stasis skin (graphic) will remain. Instructional video [https://youtu.be/3NF3QR58a-0?t=9m55s here].
+== Exploits ==
+An exploit is a glitch that must be performed intentionally (it cannot happen by accident). It is usually initiated using a hack to execute actions that are not available to the human user interface.
+=== Sliding Terran Buildings {{RaceIcon|t}} ===
+[[Image:CCslide.png|left]]
+Illegal. The player lands a Terran building, and it moves ("slides") while on the ground to another destination without needing to Lift Off (for example, sliding a Command Center closer to minerals than normal).<br/>
+To perform, lift off the CC and order it to land on a valid location, then hold shift and press S followed by a right-click on the location you want it to slide to. The CC stops sliding if colliding with any solid material. <br/>'''Only works on version 1.04 and lower'''.
+<div style="clear:both;"></div>
+=== Forward Nexus {{RaceIcon|p}} ===
+[[Image:NexusBug.png|left]]
+Illegal. Protoss Players could build a Nexus very close to minerals/gas. For that a probe had to be blinded by an optical flare. The probe's vision range was limited along with the standard forbidden space between minerals and Nexus. The same trick worked on Drones and SCVs in a similar way; the only difference was that SCVs/Drones could only leap one hex-field between building and resources. <br/>'''Only works in old versions'''.
+<div style="clear:both;"></div>
+=== Tank Under Landed Building {{RaceIcon|t}} ===
+Illegal. A few patches ago, Blizzard had "fixed" the tank under a building bug. However, little know that it is possible when sieged '''EXACTLY''' as the Building becomes registered as a ground unit.
+{{#ev:youtube|eo_oVaZYWXA}}
+=== Train Units in the Air {{RaceIcon|t}} ===
+Illegal. The player trains a unit and lifts off in the same frame. The lifted building retains the unit in the queue. When ordered to land, the unit starts being constructed. When right clicking as the building is landed, the building will lift off once more while still constructing the unit (which will be created where the building lifted off from). This enables, for example, a player to land a Factory in the opponent's base and construct a Siege Tank without needing to build a Machine Shop.
+{{#ev:youtube|iSwVE665tGE}}
+=== Flying Ground Units {{RaceIcon|zp}} ===
+[[Image:FlyingDT.gif|left]]
+Illegal. Glitches enable ground units such as drones (example clip [https://youtu.be/TJoCMH0mhk4?t=201 here]) and SCVs (instructional video in Korean [https://youtu.be/BqMHI8OSrBw?t=81 here]) and templar to act like air units. This essentially means that workers can mine and take island expansions without drop tech and templar can storm worker lines without the use of shuttles.<br/>
+<div style="clear:both;"></div>
+=== Controlling a Nuke ===
+Illegal. A.K.A. "Godly Nuke", "Nuke Hack" or "[http://www.ghoztcraft.net/forums/files/file/1472-nukeblitz-nuke-anywhere/ Nuke Anywhere]" or "[https://tl.net/forum/brood-war/559554-infinite-nuke-cheat-on-top-of-ladder/ Infinite Nuke Cheat on Top of Ladder]. This exploit enables a player (with the assistance of an external program) to stop a Nuclear Missile from launching (or landing), and move it around like a regular unit. The player can then proceed to re-launch the nuke at any location on the map (without the need for vision or a nearby ghost). When the nuke lands and deals damage, the nuke death animation can be interrupted and the same nuke can be re-launched infinite times.
+=== Flooding the Order Buffer {{RaceIcon|tzp}} ===
+Illegal. The player sends commands (usually with the assistance of an external program) in such a way that they are queued in a ridiculous order, preventing any new orders from being executed. This causes all units to stop moving, as well as other major effects such as units unable to execute the "die" command, resulting in 0 hit point unkillable units, or the "cancel" command, but still being refunded the resources. Cancelling a Zerg Extractor will also refund several drones along with resources. Merged templar or merged dark templar may remain with the same graphic as when they were merging. A queen may teleport after infesting a command center. An instructional video in Korean that shows many of these effects without using an external program is [https://youtu.be/BqMHI8OSrBw?t=110 here].
+=== Liftoff Bug {{RaceIcon|t}} ===
+[[Image:LiftStackBug.png|left]]
+Illegal. Terran could stack his buildings via abusing the lift function. Whenever a building was lifted and given an order to build a unit/research an upgrade immediately after the first command the building seemed to actually produce something. In this state the building could be float to any direction (over land). If the order got canceled the building would land anywhere ignoring the standard conditions. If the command was canceled while landing the building got stuck in the position it had but still seemed to float. <br/>'''Only works on version 1.09 and lower'''.
+<div style="clear:both;"></div>
+=== Otherwise Stacking Ground Units {{RaceIcon|ptz}} ===
+This section is a catch-all section to cover miscellaneous tricks/glitches/exploits that involve stacking ground units (either temporarily or permanently, and either intentionally or unintentionally) that are not already covered by other sections like [[#Lurker Stacking]], [[#Hopping/Pushing]], [[#Mineral Walk]], [[#Return Cargo when Transferring Workers]], [[#Re-scout with Worker through Wall without Cheating]], [[#Clustered Recall or Total Recall]], [[#Stacking Workers]], [[#Cargo Glitch]], [[#Medic Hold can't be Pushed]], [[#Recall Glitch]], [[#Drone Stuck Making Extractor]], [[#Vortex Bug]], [[#Tank Under Landed Building]], [[#Flying Ground Units]], [[#Flooding the Order Buffer]], [[#Liftoff Bug]].<br/>
+It is legal to stack burrowed units. It is legal to unburrow them, so long as they do not remain permanently stacked. It is legal for non-burrowed ground unit(s) to be on top of burrowed unit(s) or dropped on top of spider mine(s). Often, ground units may unintentionally become overlapped and continue colliding simply due to lack of walkable space around them to automatically become unstacked using the game engine's anti-collision movement logic. E.g. units produced from production buildings that are trapped in too small an area, or units may naturally become overlapped (hopefully only temporarily) while moving across the map. If partially-overlapping tanks or unburrowed units become sieged/burrowed they will remain partially overlapped - this may be unintentional/unplanned and may be understandable, especially if they siege/burrow as a reaction to seeing enemy units nearby, so the legality of this is a grey area. So long as you did not intentionally plan for units to originally overlap, and so long as reasonably timely attempts are made to clear walkable space to help them become unstuck (when not sieged and not burrowed etc), this is legal, but best avoided if you can. This is probably too hard to judge or code for in bot-vs-bot competitions though. For all other cases, by default, unless you hear otherwise, you should assume that stacking ground units is illegal, especially if the units remain stacked while attacking or remain permanently stacked. If in doubt, ask on the SSCAIT Discord. If it's a new type of trick/glitch/exploit, it could be added to this page.
+{{#ev:youtube|GrNxjyQjPZU}}
+== Videos ==
+{{#ev:youtube|TJoCMH0mhk4}}
+{{#ev:youtube|r2rjuH7krW8}}
+{{#ev:youtube|-9Yoptm2OJY}}
+{{#ev:youtube|3NF3QR58a-0}}
+{{#ev:youtube|zdvjSZirURU}}
+== See Also ==
+* [[liquipedia:Competitive_Rules|Competitive Rules on Liquipedia]]
+* [[liquipedia:Bugs|Brood War Bugs page on Liquipedia]]. Includes Battle.net bugs, chat bugs, GUI bugs, platform/language-specific bugs, replay-related bugs.
+* [https://web.archive.org/web/https://kb.speeddemosarchive.com/StarCraft/Game_Mechanics_and_Glitches StarCraft/Game Mechanics and Glitches on SpeedDemosArchive]. A lot of these only work on older versions of the game.
+* [https://web.archive.org/web/http://www.starcraftsector.com/glitches.shtml Glitches page on StarcraftSector]. A lot of these only work on older versions of the game.
+* [https://web.archive.org/web/http://code.google.com/p/bwapi/wiki/TournamentGuideline Guidelines for BWAPI Tournament Rules]. The predecessor of this page.
 = Tips =

Difference between revisions of "StarCraft/Game Mechanics and Glitches"

From SDA Knowledge Base