Jump to navigation Jump to search

You are not logged in. Please consider registering an account. By having a StrategyWiki account, you can have your own user page, upload images for your guide, and even customize the look of the site to match your tastes! Also, another benefit of registering an account is that your IP address is not logged whenever you edit, so it adds security and privacy as well. Sign up today! It takes less than one minute and requires no personal information — you're not even required to provide an e-mail address!

If you choose not to register, don't worry! You can still edit StrategyWiki all the same, just with fewer luxuries than registered users have. Your IP address will be recorded in this page's edit history, you must use the Show Preview feature to check over your work before being allowed to save your changes, and your edit may be scrutinized a bit more than that of a registered user's edit. If you don't wish any of the preceding things to happen to you or your edit, please log in or register. Please make sure that you are following all applicable policies and guidelines when making your edit, and we hope that you continue to contribute to StrategyWiki in the future!

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 7: Line 7:
In order to succeed, however, rushes must be conducted swiftly, either by quickly obtaining a handful of low-level units at the expense of economy and technology, or by quickly obtaining a handful of high-level units at the expense of both economy and all other military. Should the enemy defenses complete before the rush, the rush would either fail or be called off, and in each situation the rushing player would be at a loss.
In order to succeed, however, rushes must be conducted swiftly, either by quickly obtaining a handful of low-level units at the expense of economy and technology, or by quickly obtaining a handful of high-level units at the expense of both economy and all other military. Should the enemy defenses complete before the rush, the rush would either fail or be called off, and in each situation the rushing player would be at a loss.


Good recon is the cornerstone of any successful rush (see [[StarCraft/Scouting|Scouting]]).  A good recon strategy, once you get around your eighth or ninth worker, is to send one of those workers to the enemy base (or, if you're Zerg, send your Overlord).  At his point, the other player will probably be either 1) building more workers and supply (Supply Depot for Terran, Overlord for Zerg, and Pylon for Protoss) to bolster his/her economy, or 2) starting his/her basic military production facility (Barracks for Terran, Gateway for Protoss, Spawning Pool for Zerg to allow production at hatchery).  The ideal would be to position your worker so that you can observe their production strategy undetected; with the worker's short line of sight this may not be possible, but if your opponent isn't watching his base carefully, he may miss the worker somehow.  Of course, be sure to continue the production of workers and units during the worker's trip there, and don't get too preoccupied with micromanaging the recon mission.  If, somehow, you observe that your opponent has built a superior defense and/or military force, do not be foolish and force the rush; instead, tech up a bit and/or build more units, and go for an early middle/mid game rush.  But, if you believe that you can catch your opponent off-guard, go ahead with the early game rush.  As with any rush, timing and speed is essential.
Good recon is the cornerstone of any successful rush (see the Scouting section of the Wikibook for more information).  A good recon strategy, once you get around your eighth or ninth worker, is to send one of those workers to the enemy base (or, if you're Zerg, send your Overlord).  At his point, the other player will probably be either 1) building more workers and supply (Supply Depot for Terran, Overlord for Zerg, and Pylon for Protoss) to bolster his/her economy, or 2) starting his/her basic military production facility (Barracks for Terran, Gateway for Protoss, Spawning Pool for Zerg to allow production at hatchery).  The ideal would be to position your worker so that you can observe their production strategy undetected; with the worker's short line of sight this may not be possible, but if your opponent isn't watching his base carefully, he may miss the worker somehow.  Of course, be sure to continue the production of workers and units during the worker's trip there, and don't get too preoccupied with micromanaging the recon mission.  If, somehow, you observe that your opponent has built a superior defense and/or military force, do not be foolish and force the rush; instead, tech up a bit and/or build more units, and go for an early middle/mid game rush.  But, if you believe that you can catch your opponent off-guard, go ahead with the early game rush.  As with any rush, timing and speed is essential.


In order to properly resist an enemy rush, it is best to have either one defensive structure protecting the base and mining operations or a handful of units to repulse an enemy attack. The former is cheaper, because defenses are inherently cheaper than normal units, but is also inflexible, especially when the enemy scouts can report what structures a player is building and the enemy can thus choose to expand instead of obtaining military units. In other words, the enemy would be forced to obtain units for each of your units, while the enemy would likely create one expansion for about every three defensive structures, because the enemy would never fear an attack by your static defense (they DON'T MOVE).  If your opponent's rush fails and you still have a handful of units, a possible strategy is to execute a counter-rush.  Being that the enemy rush failed, your opponent will likely have lost most of his/her units, which you can confirm by recon (see above).  If this is indeed the case, take advantage of it and try and strike back.  However, don't be too quick to try this if you haven't conducted proper recon and you're not sure what's happening at your opponent's base.
In order to properly resist an enemy rush, it is best to have either one defensive structure protecting the base and mining operations or a handful of units to repulse an enemy attack. The former is cheaper, because defenses are inherently cheaper than normal units, but is also inflexible, especially when the enemy scouts can report what structures a player is building and the enemy can thus choose to expand instead of obtaining military units. In other words, the enemy would be forced to obtain units for each of your units, while the enemy would likely create one expansion for about every three defensive structures, because the enemy would never fear an attack by your static defense (they DON'T MOVE).  If your opponent's rush fails and you still have a handful of units, a possible strategy is to execute a counter-rush.  Being that the enemy rush failed, your opponent will likely have lost most of his/her units, which you can confirm by recon (see above).  If this is indeed the case, take advantage of it and try and strike back.  However, don't be too quick to try this if you haven't conducted proper recon and you're not sure what's happening at your opponent's base.
Please note that all contributions to StrategyWiki are considered to be released under the Creative Commons Attribution-ShareAlike (see StrategyWiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION!
Cancel Editing help (opens in new window)

Notice to contributors: The StrategyWiki administration does not condone plagiarism or the use of materials from any other source. Period. By saving this page you are promising us that you wrote this yourself, or copied it from a public domain or similar free resource. With the exception of official media (screenshots, artwork, symbols, etc., but not text) and materials released under the CC-BY-SA you must have the rights to or ownership of all work you submit to StrategyWiki. Do not copy text or images from other websites without permission. They will be deleted.

Copy and paste: – — ° ′ ″ ≈ ≠ ≤ ≥ ± − × ÷ ← → · §   Cite your sources: <ref></ref>


{{}}   {{{}}}   |   []   [[]]   [[Category:]]   #REDIRECT [[]]   &nbsp;   <s></s>   <sup></sup>   <sub></sub>   <code></code>   <pre></pre>   <blockquote></blockquote>   <ref></ref> <ref name="" />   {{Reflist}}   <references />   <includeonly></includeonly>   <noinclude></noinclude>   {{DEFAULTSORT:}}   <nowiki></nowiki>   <!-- -->   <span class="plainlinks"></span>


{{Header Nav|game={{subst:BASEPAGENAME}}}}   {{Footer Nav|game={{subst:BASEPAGENAME}}|prevpage=|nextpage=}}   {{spoilers}}   {{spoiler|}}   {{delete|Unused}}   {{rename|MS Monster .png}}   {{floatingtoc}}   {{stub}}


Symbols: ~ | ¡ ¿ † ‡ ↔ ↑ ↓ • ¶   # ∞   ‘ ’ “ ” ‹› «»   ¤ ₳ ฿ ₵ ¢ ₡ ₢ $ ₫ ₯ € ₠ ₣ ƒ ₴ ₭ ₤ ℳ ₥ ₦ № ₧ ₰ £ ៛ ₨ ₪ ৳ ₮ ₩ ¥   ♠ ♣ ♥ ♦   ♭ ♯ ♮   © ® ™
Latin: A a Á á À à  â Ä ä Ǎ ǎ Ă ă Ā ā à ã Å å Ą ą Æ æ Ǣ ǣ   B b   C c Ć ć Ċ ċ Ĉ ĉ Č č Ç ç   D d Ď ď Đ đ Ḍ ḍ Ð ð   E e É é È è Ė ė Ê ê Ë ë Ě ě Ĕ ĕ Ē ē Ẽ ẽ Ę ę Ẹ ẹ Ɛ ɛ Ǝ ǝ Ə ə   F f   G g Ġ ġ Ĝ ĝ Ğ ğ Ģ ģ   H h Ĥ ĥ Ħ ħ Ḥ ḥ   I i İ ı Í í Ì ì Î î Ï ï Ǐ ǐ Ĭ ĭ Ī ī Ĩ ĩ Į į Ị ị   J j Ĵ ĵ   K k Ķ ķ   L l Ĺ ĺ Ŀ ŀ Ľ ľ Ļ ļ Ł ł Ḷ ḷ Ḹ ḹ   M m Ṃ ṃ   N n Ń ń Ň ň Ñ ñ Ņ ņ Ṇ ṇ Ŋ ŋ   O o Ó ó Ò ò Ô ô Ö ö Ǒ ǒ Ŏ ŏ Ō ō Õ õ Ǫ ǫ Ọ ọ Ő ő Ø ø Œ œ   Ɔ ɔ   P p   Q q   R r Ŕ ŕ Ř ř Ŗ ŗ Ṛ ṛ Ṝ ṝ   S s Ś ś Ŝ ŝ Š š Ş ş Ș ș Ṣ ṣ ß   T t Ť ť Ţ ţ Ț ț Ṭ ṭ Þ þ   U u Ú ú Ù ù Û û Ü ü Ǔ ǔ Ŭ ŭ Ū ū Ũ ũ Ů ů Ų ų Ụ ụ Ű ű Ǘ ǘ Ǜ ǜ Ǚ ǚ Ǖ ǖ   V v   W w Ŵ ŵ   X x   Y y Ý ý Ŷ ŷ Ÿ ÿ Ỹ ỹ Ȳ ȳ   Z z Ź ź Ż ż Ž ž   ß Ð ð Þ þ Ŋ ŋ Ə ə   {{Unicode|}}
Greek: Ά ά Έ έ Ή ή Ί ί Ό ό Ύ ύ Ώ ώ   Α α Β β Γ γ Δ δ   Ε ε Ζ ζ Η η Θ θ   Ι ι Κ κ Λ λ Μ μ   Ν ν Ξ ξ Ο ο Π π   Ρ ρ Σ σ ς Τ τ Υ υ   Φ φ Χ χ Ψ ψ Ω ω   {{Polytonic|}}
Cyrillic: А а Б б В в Г г   Ґ ґ Ѓ ѓ Д д Ђ ђ   Е е Ё ё Є є Ж ж   З з Ѕ ѕ И и І і   Ї ї Й й Ј ј К к   Ќ ќ Л л Љ љ М м   Н н Њ њ О о П п   Р р С с Т т Ћ ћ   У у Ў ў Ф ф Х х   Ц ц Ч ч Џ џ Ш ш   Щ щ Ъ ъ Ы ы Ь ь   Э э Ю ю Я я   ́
IPA: t̪ d̪ ʈ ɖ ɟ ɡ ɢ ʡ ʔ   ɸ β θ ð ʃ ʒ ɕ ʑ ʂ ʐ ç ʝ ɣ χ ʁ ħ ʕ ʜ ʢ ɦ   ɱ ɳ ɲ ŋ ɴ   ʋ ɹ ɻ ɰ   ʙ ⱱ ʀ ɾ ɽ   ɫ ɬ ɮ ɺ ɭ ʎ ʟ   ɥ ʍ ɧ   ʼ   ɓ ɗ ʄ ɠ ʛ   ʘ ǀ ǃ ǂ ǁ   ɨ ʉ ɯ   ɪ ʏ ʊ   ø ɘ ɵ ɤ   ə ɚ   ɛ œ ɜ ɝ ɞ ʌ ɔ   æ   ɐ ɶ ɑ ɒ   ʰ ʱ ʷ ʲ ˠ ˤ ⁿ ˡ   ˈ ˌ ː ˑ ̪   {{IPA|}}

Your changes will be visible immediately.
  • For testing, please use the sandbox instead.
  • On talk pages, please sign your comment by typing four tildes (~~~~).

Please note:
  • If you don't want your writing to be edited mercilessly or redistributed by others, do not submit it.
  • Only public domain resources can be copied without permission — this does not include the vast majority of web pages or images.
  • See our policies and guidelines for more information on editing.

This page is a member of a hidden category: