Editing Typical opening

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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

Latest revision Your text
Line 1: Line 1:
A guide about how to start a game and what your opening moves would typically be. The specifics could change according to the map and game mode played, but the moves below are generally a good start to any game.
+
A guide about how to start a game and what your opening moves would typically be.
  
 
==Location selection phase==
 
==Location selection phase==
Line 15: Line 15:
 
===Your first buildings===
 
===Your first buildings===
 
Before the game starts, you are allowed to queue up to 30 buildings (using shift) that your commander will start to work on when it appears. Most people open with the following:
 
Before the game starts, you are allowed to queue up to 30 buildings (using shift) that your commander will start to work on when it appears. Most people open with the following:
#A starting factory, placed somewhere close to the starting mex cluster.
+
#Choose a factory and place it somewhere close to your starting mexes.
#*This is to ensure the Commander has to move around as little as possible for this initial phase - time spent moving is time not spent building.
+
#*You want your Commander to move around as little as possible for this initial phase - time spent moving is time not spent building.
#All surrounding mexes.
+
#Queue up all your surrounding mexes.
#3 [[Solar Collector]]s or 5-6 [[Wind/Tidal Generator]]s.
+
#Build 3 [[Solar Collector]]s or 5-6 [[Wind/Tidal Generator]]s.
 
#*This should give you enough energy to match the metal you will get from the mexes you just took and the next few mexes you will take as you start to expand.
 
#*This should give you enough energy to match the metal you will get from the mexes you just took and the next few mexes you will take as you start to expand.
#A [[Radar Tower]], preferably in an elevated location.
+
#Build a [[Radar Tower]], preferably in an elevated location.
#*Helps to protect against early raids.
+
#*Helps you protect against raids.
#1 or 2 light defensive towers, usually an [[Lotus|LLT]] or [[Picket|MT]].
+
#Build 1 or 2 defensive towers, usually an [[Lotus|LLT]] or [[Picket|MT]].
#The commander, in a location close to all the buildings.
+
#Finally, place your commander, and wait for the game to start.
  
 
==After the game has started - initial moves==
 
==After the game has started - initial moves==
 
===Your first units===
 
===Your first units===
The first thing your Commander should have done is teleported in a factory - the first factory placed is free of charge. It is now sitting idle.
+
The first thing your Commander should have done is plopped a factory. It is now sitting idle.
#Queue up a scout unit. This would be something light - a [[Flea]], [[Dart]], [[Glaive]], [[Dirtbag]], etc.
+
#Queue up a scout unit. This would be a [[Flea]], [[Dart]], [[Glaive]], [[Dirtbag]], etc.
 
#Set its rally point to somewhere '''near''' where you think your opponents' base will be.
 
#Set its rally point to somewhere '''near''' where you think your opponents' base will be.
 
#*The point of doing this is to see if your opponent is up to something [[cheese|cheesy]].
 
#*The point of doing this is to see if your opponent is up to something [[cheese|cheesy]].
Line 38: Line 38:
 
Send your first constructor to a nearby group of mexes and start building them. Use your raiders to either protect this constructor or send them over to your opponents' base to keep them from being too greedy with their expansion.
 
Send your first constructor to a nearby group of mexes and start building them. Use your raiders to either protect this constructor or send them over to your opponents' base to keep them from being too greedy with their expansion.
  
On a large map, your Commander is probably best used by staying in base and building lots of energy structures; [[Caretaker]]s when necessary. This is because the Commander is much slower than any constructor and on large maps it is easy to get a decent ball of raiders quickly. These can overwhelm and destroy an unescorted Commander easily, a blow so severe that you might as well resign there and then.
+
On a large map, your Commander is probably best used by staying in base and building lots of energy structures; [[Caretaker]]s when necessary. This is because the Commander is much slower than any constructor and on large maps it is easy to get a big ball of raiders quickly. These can overwhelm the Commander easily, putting it at much risk.
 +
 
 +
On small maps, it is generally best to march your Commander towards your opponent's base, taking mexes and building defences along the way. On smaller maps, the Commander's combat strength is relevant for much longer than on other maps, and you can leverage this to gain map control.
  
On small maps, it is generally best to march your Commander towards your opponent's base, taking mexes and building light defences along the way. On smaller maps, the Commander's combat strength is relevant for much longer than on other maps, and you can leverage this to gain map control.
 
  
 
====What next?====
 
====What next?====
What happens after this is beyond the scope of this guide. Read about [[typical game progression]] here.
+
Read about [[typical game progression]] here.
  
 
{{Navbox manual}}
 
{{Navbox manual}}

Please note that all contributions to Zero-K are considered to be released under the Creative Commons Attribution-ShareAlike (see Zero-K: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)