Zero-K - User contributions [en]

Cheese

2019-09-16T16:17:55Z

213.35.139.72: /* Defending against it */

Cheese strategies are strategies that can be described as high-risk and high-reward. These typically rely on winning hard and winning early. Below we will detail some of the finest cheese known to lobster-kind. 
Disclaimer: Some of these are quite bad strategies, but will probably sometimes work nonetheless.
==On the use of commanders==
A good rush will often include your commander. In the early parts of the game, this unit represents the majority of your combat strength. Most rushes just utilize the commander as a support unit that fills in a role that you need. However, some cheese strategies utilize the commander as a centerpiece of the strategy.

==The strategies==
===Fencer rush===
Plop [[Rover Assembly]], and put [[fencer]]s on repeat queue. Once you have made 2 to 3, it is time to start moving towards your opponent. Once your [[Commander]] builds the starting mexes/energy move it towards the opponents base as well. Once you get to your opponent's base and see what they have been up to, choose an appropriate comm morph option. Continue streaming fencers across the map. When you have a critical mass of fencers you can just move in and kill them. But don't wait too long! If they get up significant defense you could end up losing.
*Rocket launcher is the best morph to get if they try to counter you with [[Unit_classes#Skirmisher|skirmishers]].
*Riot cannon if they build lots of low-hp raiders.
*Heat ray is good if they try to make heavies.
====Defending against it====
A well-executed Fencer rush is extremely difficult to stop with conventional units. The natural counter to Fencers in the face of assault units is likely to be stopped by the enemy commander. Using your own commander is typically also a mistake because the enemy will be upgraded for combat and will have the benefit of fire support from their Fencers.

The best answer is to drop everything and rush a Stinger. Having sacrificed all their economy, the opponent is likely to not have any economy, at most one mex. If you succeed in building a Stinger, they will have their zero mexes against your three, and no way to reasonably expand. After this, you can proceed to counter their contain with more conventional approaches.

Typically, a Fencer rush will also see the enemy factory left entirely defenceless - after all, each bit of metal spent on defence for your enemy is one not spent assisting in the actual rush. Sneaking away a single raider will usually suffice to kill this factory and prevent Fencer reinforcements or sneak expansion.

===Reaver rush===
Much like the fencer rush.
#Plop [[Cloaky Bot Factory]] and take 1 [[mex]].
#Make [[Reaver]]s on repeat queue.
#Move out with your comm and have reavers rally to it.
This rush is more time sensitive, and requires that you hit sooner than a fencer rush. Reavers are a bit faster than your comm so they will catch up to it.

===Ogre rush===
The [[Ogre]] is probably the most robust [[Unit_classes#Riot|riot]] unit in the game, with high DPS and HP. It can be quite difficult to stop earlygame, especially if it is unscouted. The ogre is capable of killing commanders by itself and it has splash damage, making it quite effective against the raiders people typically build as well. This rush is time sensitive, as if they scout you they can throw up lots of light defense turrets and hold it off. 
#Plop the [[Tank Foundry]].
#Queue up an ogre, set the rally point to your opponents base.
#Assist the factory with your commander.
This rush is especially effective against factories with no skirmishers, like HT or rovers. Factories with awkward skirmishers like spider may struggle to deal with it as well, but HT vs spider is a rare match-up anyways.

====Defending against it====
The best defense against any cheese is scouting, and this is true here. Build your lightest raider and send it to your opponent's base. Since the Ogre is an expensive unit, by the time your raider gets there it should still see the Ogre in the factory being built, or just as it moves out. Since the opponent has commited quite a bit of resources to this rush you can affort to just spam lots of LLTs and the occasional Picket to hold it off. If your factory has a skirmisher, that would be a good choice to make as well.

While Rovers don't have any normal skirmishers, being able to produce a Dominatrix by the time the Ogre hits you turns the cheese upside down, as the Dominatrix will easily capture the Ogre, making it your enemy's problem now.

===Com-Morph Push===
===Com-Drop===
===Blastwing opening===
===Raider rush===
These types of rushes are distinct from the others in that they don't bring along the commander, and rely on overwhelming your opponent with an unexpected raider force. Below are listed some of the raiders that are most effective at rushing.
====Flea rush====
Plop [[Spider Factory]] and build your initial 500 metal into fleas. Send your first two out to scout. Once you get your flea swarm you can either attack the opponents base, or their commander. If their commander morphed to a splash damage weapon this will not work, but it should lead to a dead commander if the commander is alone and un-morphed. Alternatively, if they only built like 1 [[Picket]] or [[Lotus]] in their base and all their units are gone, you are able to quickly kill the defensive turrets and possibly win the game by killing all their eco structures and factory. You need to be careful with your fleas though, the death explosions from most buildings can instantly kill them. Obviously, this strategy fails if they are not very greedy and bother to build some raiders.
====Glaive/Bandit rush====

They maneuver around defenses and take out constructors, factories, and economic structures.

====Scorcher rush====

Map Creation

2019-04-18T16:11:14Z

213.35.139.72: /* Startboxes */

Maps are 7z archives which, at their most basic, consist of three image files packaged in a particular way. They can be found in <code>Zero-K/Maps</code> and be zipped or unziped with [https://www.7-zip.org/download.html| 7zip]. Maps can contain more than their three image files, including:
* Metal spot layout.
* Start area configuration.
* Tree, rock or any other models to be placed as map features.
* Arbitrary code and units changes that can arbitrarily modify the game. See [[Mod Creation]].

= Creating maps =
Beginner mapping tutorial for SpringRTS is located here: https://springrts.com/wiki/Mapdev:Tutorial_Simple

Ask for help in #zkmap in on the [https://discord.gg/PRv7uy| Zero-K Discord server].

Here are some SpringRTS (the engine) links [https://springrts.com/wiki/Mapdev:Main] [https://springrts.com/wiki/Map,_Game,_And_Unit_Development_Programs#Map_Creation]

== Startboxes ==

Startboxes are loaded from /mapconfig/map_startboxes.lua and can be generated ingame with the Startbox Editor widget included with the game. Alt-F11 to toggle.

Full guide for the startbox editor here: [[Startbox API]]

== Metal Configuration and Spot Graphics ==

Metal spots on maps are done via Lua configs. They can be generated ingame with the dbg_mouse_to_mex_portable.lua widget, available at [https://github.com/The-Yak/mexes_grounddecal_autoplacer | TheMooseIsLoose's github.]

Download that repo as a zip and extract into your map folder. Load the map in ZK, enable cheats, and then enable Mouse to Mexes in your alt-f11 widget menu. Click to create new metal spots, the values and positions will be automatically saved to your game data directory. Copy and paste the content from MexSpots_YourMap to your /mapconfig/map_metal_layout.lua

= Running maps =
== Local testing ==
To run a map locally put it in <code>Zero-K/Maps</code> then start the game. Untick 'Only featured maps' in <code>Settings -> Lobby</code> and start a singleplayer skirmish game. Select 'Advanced', click 'Change Map' and select your map from the list.

== Multiplayer ==
Upload your map to https://springfiles.com/ to make it downloadable and playable by others. Some admin action to feature/support the map may also be required.

= Links =

* [[User:Aquanim/WaterMapDesign|Some subjective comments on design of sea maps, by Aquanim]]

{{Navbox manual}} [[Category: Development]]

User:Anarchid/OmniCommanderDesign

2019-01-24T12:25:38Z

213.35.139.72: /* Why */

This is my attempt to figure out a design for an unified commander chassis.

= Why =

Historically ZK has had several commander chassis to provide variety for a bunch of reasons:
* Initially it was the only way to provide commander variety (because procedural generation of unitdefs was not available)
* Later, because while <code>unitdefs_post</code> solved the former problem, the models existed, and provided some, albeit limited, visual feedback on what the commander was
* Even later, as commanders became mostly "dynamic", for the same legacy reasons
* No model that would display more useful information than the current system exists.

This is bad for several reasons:
* Significantly initially different chassis are pregame RPS in several situations - such as Recon commander's jump available at level zero, or Support commander's build range
* This provides useful visual representation only for one important commander ability - jump - while all other abilities are essentially hidden. Especially guns all look exactly alike.

= Design Design =
Before approaching the design of this thing, it is useful to approach the design of designing this thing.

# As with current commander design requirements, this design should not have degenerate, overpowered or useless paths.
#* Commanders should not be significantly stronger than same fair cost in units at any point, but should not be that much worse either
#* A single build or a series of builds should not be always better than the others
#* It's also a good idea to avoid as much lock-in as possible; branching systems that prohibit modules further down the line are boring (but "this module goes in the helmet slot, which is already occupied" is fine).
# For a transition from chassis to modules entirely, the first level-up should be important enough to encompass all of the variety in current chassis and first-morph modules
#* A significant part of this is chassis passive bonuses and specialization - there should be modules to imitate this
#* With the following criterion, this also means that the first morph should make commanders very *visibly* different as well.
# As much interesting information about the commander as possible should be meaningfully visible on the commander body.
#* This intrinsically suggests tying commander modules to their respective body parts, and maybe even have body part based equipment slots
#* Current stackable or weapon modules are insufficient to encompass this. A "subsystem module" approach like in Aquanim's draft may be useful.
#* The important qualitatively difference items should take priority. Guns and jump ability are first tier; everything else is secondary or tertiary.
# The technical considerations of the omni-commander model should be considered at every step
#* The model should be reasonably easy to modify and generally as low-maintenance as possible
#* Replacement or refund of current commander skins should be considered and made as easy as possible
#* Additional types of "hats" could be considered

= General Stuff =
# The omni-commander model is at least partially an atlas/lego system. The texture provides various materials to be splatted onto various geometry bits, with few of it strictly dedicated (except for core geometry). Weapons have their own dedicated mini-zones and can share materials.
## Weapons and important abilities are emissive and color coded; some may be animated
# Every module is visually represented on the model.
## Important modules are called **subsystems** and take equipment **slots**. They completely take over a given body part, and more than one module cannot use the same body part. Advanced versions of a subsystem can replace a weaker version. The following slots are available:
### Head (helmet, crown, antenna, etc) - intel, aura abilities like shield, cloaker, radar
### Chest (torso front, breastplate, etc) - armor, regeneration
### Forearms (left, right) or whole arms - weapons. These should be huge and prominent as the most important things ever.
### Shoulders (left, right) - secondary weapons, construction abilities
### Back - active abilities (jump, float?)
### Legs - passive movement-related abilities (jump? climb? hover? goomba stomp?).
## Subsystem module _choices_ in the UI have to somehow show which slot they occupy
## Stackable modules, as much as they exist, are represented as small bits on or near the things they affect.
### Armor modules - rivets or small plates on chest
### Damage modules - small glowy bits on upper arms
### Speed modules - small bits on upper/lower legs
### .. etc
## Stackable module choices need to show their stacking limits in the UI.
## Enhancement modules are treated as new modules. E.g. a longer-stun version of a lightning gun simply has a different lightning gun model.

= Draft Bucket List Of Modules =

{| class="wikitable sortable" style="text-align: center"
! Name
! Type
! Slot
! Level
! scope="col" class="unsortable" | Description
! scope="col" class="unsortable" | Comments
|-
! Jetpack
| System
| Back
| 1
| Allows commander to jump
| Large, bulky, visible
|-
! Beam Laser
| Weapon
| Arm
| 1
| Kills things
| Long teal/blue emissive line along top
|-
! Combat Drone Kit
| System
| Back
| 2
| Launches Fireflies
| Moving mechanical stuff. Possibly can also dock drones if drone tech advances?
Conflicts with jump, but not with shield/cloak.
|-
! Personal Shield
| System
| Head
| 2
| Provides a small shield
| Crown that reminds an Aspis. Incompatible with cloak.
|-
! Personal Cloak
| System
| Head
| 2
| Cloaks commander
| Teal glowing halo, like Scythe/Iris backpacks. Incompatible with shield.
|-
! Advanced Nanolathe
| System
| Shoulder
| 1
| More nano range, slightly more build power
| Replaces default nano, bigger.
|}

User:Anarchid/OmniCommanderDesign

2018-12-28T12:39:24Z

213.35.139.72: /* Design Design */ a

This is my attempt to figure out a design for an unified commander chassis.

= Why =

Historically ZK has had several commander chassis to provide variety for a bunch of reasons:
* Initially it was the only way to provide commander variety (because procedural generation of unitdefs was not available)
* Later, because while <code>unitdefs_post</code> solved the former problem, the models existed, and provided some, albeit visual feedback on what the commander was
* Even later, as commanders became mostly "dynamic", for the same legacy reasons
* No model that would display more useful information than the current system exists.

This is bad for several reasons:
* Significantly initially different chassis are pregame RPS in several situations - such as Recon commander's jump available at level zero, or Support commander's build range
* This provides useful visual representation only for one important commander ability - jump - while all other abilities are essentially hidden. Especially guns all look exactly alike.

= Design Design =
Before approaching the design of this thing, it is useful to approach the design of designing this thing.

# As with current commander design requirements, this design should not have degenerate, overpowered or useless paths.
#* Commanders should not be significantly stronger than same fair cost in units at any point, but should not be that much worse either
#* A single build or a series of builds should not be always better than the others
#* It's also a good idea to avoid as much lock-in as possible; branching systems that prohibit modules further down the line are boring (but "this module goes in the helmet slot, which is already occupied" is fine).
# For a transition from chassis to modules entirely, the first level-up should be important enough to encompass all of the variety in current chassis and first-morph modules
#* With the following criterion, this also means that the first morph should make commanders very *visibly* different as well.
# As much interesting information about the commander as possible should be meaningfully visible on the commander body.
#* This intrinsically suggests tying commander modules to their respective body parts, and maybe even have body part based equipment slots
#* Current stackable or weapon modules are insufficient to encompass this. A "subsystem module" approach like in Aquanim's draft may be useful.
#* The important qualitatively difference items should take priority. Guns and jump ability are first tier; everything else is secondary or tertiary.
# The technical considerations of the omni-commander model should be considered at every step
#* The model should be reasonably easy to modify and generally as low-maintenance as possible
#* Replacement or refund of current commander skins should be considered and made as easy as possible
#* Additional types of "hats" could be considered

= General Stuff =
# The omni-commander model is at least partially an atlas/lego system. The texture provides various materials to be splatted onto various geometry bits, with few of it strictly dedicated (except for core geometry). Weapons have their own dedicated mini-zones and can share materials.
## Weapons and important abilities are emissive and color coded; some may be animated
# Every module is visually represented on the model.
## Important modules are called **subsystems** and take equipment **slots**. They completely take over a given body part, and more than one module cannot use the same body part. Advanced versions of a subsystem can replace a weaker version. The following slots are available:
### Head (helmet, crown, antenna, etc) - intel, aura abilities like shield, cloaker, radar
### Chest (torso front, breastplate, etc) - armor, regeneration
### Forearms (left, right) or whole arms - weapons. These should be huge and prominent as the most important things ever.
### Shoulders (left, right) - secondary weapons, construction abilities
### Back - active abilities (jump, float?)
### Legs - passive movement-related abilities (jump? climb? hover? goomba stomp?).
## Subsystem module _choices_ in the UI have to somehow show which slot they occupy
## Stackable modules, as much as they exist, are represented as small bits on or near the things they affect.
### Armor modules - rivets or small plates on chest
### Damage modules - small glowy bits on upper arms
### Speed modules - small bits on upper/lower legs
### .. etc
## Stackable module choices need to show their stacking limits in the UI.
## Enhancement modules are treated as new modules. E.g. a longer-stun version of a lightning gun simply has a different lightning gun model.

User:Anarchid/OmniCommanderDesign

2018-12-28T11:37:45Z

213.35.139.72: shift radix

This is my attempt to figure out a design for an unified commander chassis.

= Why =

Historically ZK has had several commander chassis to provide variety for a bunch of reasons:
* Initially it was the only way to provide commander variety (because procedural generation of unitdefs was not available)
* Later, because while <code>unitdefs_post</code> solved the former problem, the models existed, and provided some, albeit visual feedback on what the commander was
* Even later, as commanders became mostly "dynamic", for the same legacy reasons
* No model that would display more useful information than the current system exists.

This is bad for several reasons:
* Significantly initially different chassis are pregame RPS in several situations - such as Recon commander's jump available at level zero, or Support commander's build range
* This provides useful visual representation only for one important commander ability - jump - while all other abilities are essentially hidden. Especially guns all look exactly alike.

= Design Design =
Before approaching the design of this thing, it is useful to approach the design of designing this thing.

# As with current commander design requirements, this design should not have degenerate, overpowered or useless paths.
#* Commanders should not be significantly stronger than same fair cost in units at any point, but should not be that much worse either
#* A single build or a series of builds should not be always better than the others
#* It's also a good idea to avoid as much lock-in as possible; branching systems that prohibit modules further down the line are boring (but "this module goes in the helmet slot, which is already occupied" is fine).
# For transition from chassis to modules entirely, the first level-up should be important enough to encompass all of the variety in current chassis and first-morph modules
#* With the following criterion, this also means that the first morph should make commanders very *visibly* different as well.
# As much interesting information about the commander as possible should be meaningfully visible on the commander body.
#* This intrinsically suggests tying commander modules to their respective body parts, and maybe even have body part based equipment slots
#* Current stackable or weapon modules are insufficient to encompass this. A "subsystem module" approach like in Aquanim's draft may be useful.
#* The important qualitatively difference items should take priority. Guns and jump ability are first tier; everything else is secondary or tertiary.
# The technical considerations of the omni-commander model should be considered at every step
#* The model should be reasonably easy to modify and generally as low-maintenance as possible
#* Replacement or refund of current commander skins should be considered and made as easy as possible
#* Additional types of "hats" could be considered

= General Stuff =
# The omni-commander model is at least partially an atlas/lego system. The texture provides various materials to be splatted onto various geometry bits, with few of it strictly dedicated (except for core geometry). Weapons have their own dedicated mini-zones and can share materials.
## Weapons and important abilities are emissive and color coded; some may be animated
# Every module is visually represented on the model.
## Important modules are called **subsystems** and take equipment **slots**. They completely take over a given body part, and more than one module cannot use the same body part. Advanced versions of a subsystem can replace a weaker version. The following slots are available:
### Head (helmet, crown, antenna, etc) - intel, aura abilities like shield, cloaker, radar
### Chest (torso front, breastplate, etc) - armor, regeneration
### Forearms (left, right) or whole arms - weapons. These should be huge and prominent as the most important things ever.
### Shoulders (left, right) - secondary weapons, construction abilities
### Back - active abilities (jump, float?)
### Legs - passive movement-related abilities (jump? climb? hover? goomba stomp?).
## Subsystem module _choices_ in the UI have to somehow show which slot they occupy
## Stackable modules, as much as they exist, are represented as small bits on or near the things they affect.
### Armor modules - rivets or small plates on chest
### Damage modules - small glowy bits on upper arms
### Speed modules - small bits on upper/lower legs
### .. etc
## Stackable module choices need to show their stacking limits in the UI.
## Enhancement modules are treated as new modules. E.g. a longer-stun version of a lightning gun simply has a different lightning gun model.

Talk:Manual

2018-10-19T11:32:09Z

213.35.139.72: DISAGREE

What is the point of the dumb l33t-speak quotes on this page? 
I vote we remove them and put something real there like "This is the official Zerok manual. You can learn about units, strategy, and UI commanders, and more here!"
--[[User:Fealthas|Fealthas]] ([[User talk:Fealthas|talk]]) 05:39, 15 October 2018 (CEST)
:It was a bit of nice humour back in the day, but I suppose it's outlived its value. I've edited the page along the suggested lines. — [[User:Histidine|Histidine]] ([[User talk:Histidine|talk]]) 13:55, 18 October 2018 (CEST)
:I disagree with the removal of the KDR quote. It contained no leetspeak and was not dumb, in fact it's one of the most useful maxims for playing ZK well. The other quotes are much less useful. [[Special:Contributions/213.35.139.72|213.35.139.72]] 13:32, 19 October 2018 (CEST)

Funnelweb

2018-09-19T10:42:38Z

213.35.139.72: /* Tactics and Strategy */ This is not warcraft in space. This is king arthur in space.

The '''{{PAGENAME}}''' is a drone/shield support strider from the [[Strider Hub]].{{ Infobox zkunit
| name = Funnelweb
| defname = striderfunnelweb
| description = Drone/Shield Support Strider
| image = http://manual.zero-k.info/unitpics/striderfunnelweb.png
| icontype = t3special
| cost = 4500
| hitpoints = 11000
| movespeed = 45
| turnrate = 40
| sight = 650
| transportable = Heavy
| abilities =
{{ Infobox zkability drone
| drone = [[Firefly]]
| maxdrones = 6
| range = 800
| interval = 15
| spawnsize = 2
| buildtime = 6
| maxbuilding = 1
}}
{{ Infobox zkability drone
| drone = [[Viper]]
| maxdrones = 2
| range = 800
| interval = 25
| spawnsize = 1
| buildtime = 9
| maxbuilding = 1
}}
{{ Infobox zkability shield
| name = Energy Shield
| strength = 3600
| regen = 50
| regencost = 12
| radius = 350
}}
}}==Description==
The slow all-terrain Funnelweb features an area shield and a powerful drone complement.

== Tactics and Strategy ==

The Funnelweb's (and [[Reef]]'s) drones can travel a fairly long distance away from the Funnelweb, so it can be used in a similar role as a Skirmisher (as opposed to the [[Dante]] and [[Scorpion]], which are like riot units compared to the Funnelweb). Moreover, when you've built up enough drones (each Funnelweb can have up to 6 [[Firefly]] companion drones, and up to 2 [[Viper]] battle drones, which have a combined dps of 440 + 400 slow damage), they can easily overwhelm enemies through sheer numbers (especially when you have many Funnelwebs). However, anti-swarm units and structures, including anti-air weapons, can and will give the Funnelweb's drones problems (in which case, if you're noticing that your Funnelwebs are not breaking through the enemy's defenses in a reasonable amount of time, then it might be time to send them back to recover).

- Still, even when the Funnelweb's (and Reef's) drones are being shot down, at least they can distract the enemy from your other units, including other, more dangerous striders like the Dante. Besides, the drones are totally expendable, while the Funnelweb is sitting at a safe distance away.

- Amusingly enough, since anti-air units will target the Funnelweb's drones, a single Funnelweb can cause an enemy's [[Artemis]] to waste its supply of insanely-powerful anti-air missiles on constantly-respawning drones, potentially allowing allied aircraft to take advantage of the situation.

Like the [[Aspis]], the Funnelweb's protective bubble shield can not only give it an additional layer of protection (that regenerates faster than the Funnelweb's basic auto-repair system), but it can even be used to protect nearby units from harm, including [[Catapult]]s, [[Dante]]s, [[Scorpion]]s, [[Paladin]]s, and even other Funnelwebs, and can share shield energy with other shielded units (similarly to how [[Thug]]s, [[Felon]]s, [[Convict]]s, and [[Aspis]] can share their shield energy with eachother). Of course, unlike the Aegis, the Funnelweb has alot of health on top of the shield, so it won't go down in a fight that easily.

Overall, unlike assault-oriented striders, like the [[Dante]], [[Paladin]], or [[Detriment]], the Funnelweb is more of a support-oriented strider, whose main purposes are to harass enemies from far away with its drones, and protect other units, including other striders, with its large bubble shield. Unfortunately, a lone Funnelweb isn't likely to get much accomplished in a given period of time. In fact, chances are that you'd be better off picking the more assault-oriented [[Dante]], or the harder-hitting longer-ranged [[Merlin]], as the 1st strider that you'd want to build in a given match (though said striders could still benefit from support from a Funnelweb).

{{Navbox units}}

Cheese

2018-08-14T15:52:17Z

213.35.139.72: /* Defending against it */

Cheese strategies are strategies that can be described as high-risk and high-reward. These typically rely on winning hard and winning early. Below we will detail some of the finest cheese known to lobster-kind. 
Disclaimer: Some of these are quite bad strategies, but will probably sometimes work nonetheless.
==On the use of commanders==
A good rush will often include your commander. In the early parts of the game, this unit represents the majority of your combat strength. Most rushes just utilize the commander as a support unit that fills in a role that you need. However, some cheese strategies utilize the commander as a centerpiece of the strategy.

==The strategies==
===Fencer rush===
Plop rover factory, and put fencers on repeat queue. Once you have made like 2 it is time to start moving towards your opponent. Once your comm builds the starting mexes/energy move it towards the opponents base as well. Once you get to your opponent's base and see what they have been up to, choose an appropriate comm morph option. Continue streaming fencers across the map. When you have a critical mass of fencers you can just move in and kill them. But don't wait too long! If they get up significant defense you could end up losing.
*Rocket launcher is the best morph to get if they try to counter you with skirmishers.
*Riot cannon if they build lots of low-hp raiders.
*Heat ray is good if they try to make heavies.
====Defending against it====
A well-executed Fencer rush is extremely difficult to stop with conventional units. The natural counter to Fencers in the face of assault units is likely to be stopped by the enemy commander. Using your own commander is typically also a mistake because the enemy will be upgraded for combat and will have the benefit of fire support from their Fencers.

The best answer is to drop everything and rush a Stinger. Having sacrificed all their economy, the opponent is likely to not have any economy, at most one mex. If you succeed in building a Stinger, they will have their zero mexes against your three, and no way to reasonably expand. After this, you can proceed to counter their contain with more conventional approaches.

Typically, a Fencer rush will also see the enemy factory left entirely defenceless - after all, each bit of metal spent on defence for your enemy is one not spent assisting in the actual rush. Sneaking away a single raider will usually suffice to kill this factory and prevent Fencer reinforcements or sneak expansion.

===Reaver rush===
Much like the fencer rush.
#Plop cloaky and take 1 mex.
#Make reavers on repeat queue.
#Move out with your comm and have reavers rally to it.
This rush is more time sensitive, and requires that you hit sooner than a fencer rush. Reavers are a bit faster than your comm so they will catch up to it.

===Ogre rush===
The Ogre is probably the most robust riot unit in the game, with high DPS and HP. It can be quite difficult to stop earlygame, especially if it is unscouted. The ogre is capable of killing commanders by itself and it has splash damage, making it quite effective against the raiders people typically build as well. This rush is time sensitive, as if they scout you they can throw up lots of light defense turrets and hold it off. 
#Plop the HT foundry.
#Queue up an ogre, set the rally point to your opponents base.
#Assist the factory with your commander.
This rush is especially effective against factories with no skirmishers, like HT or rovers. Factories with awkward skirmishers like spider may struggle to deal with it as well, but HT vs spider is a rare match-up anyways.

====Defending against it====
The best defense against any cheese is scouting, and this is true here. Build your lightest raider and send it to your opponent's base. Since the Ogre is an expensive unit, by the time your raider gets there it should still see the banisher in the factory being built, or just as it moves out. Since the opponent has commited quite a bit of resources to this rush you can affort to just spam lots of LLTs and the occasional Picket to hold it off. If your factory has a skirmisher, that would be a good choice to make as well.

While Rovers don't have any normal skirmishers, being able to produce a Dominatrix by the time the Ogre hits you turns the cheese upside down, as the Dominatrix will easily capture the Ogre, making it your enemy's problem now.

===Com-Morph Push===
===Com-Drop===
===Blastwing opening===
===Raider rush===
These types of rushes are distinct from the others in that they don't bring along the commander, and rely on overwhelming your opponent with an unexpected raider force. Below are listed some of the raiders that are most effective at rushing.
====Flea rush====
Plop spider factory and build your initial 500 metal into fleas. Send your first two out to scout. Once you get your flea swarm you can either attack the opponents base, or their commander. If their commander morphed to a splash damage weapon this will not work, but it should lead to a dead commander if the commander is alone and un-morphed. Alternatively, if they only built like 1 MT or LLT in their base and all their units are gone, you are able to quickly kill the defensive turrets and possibly win the game by killing all their eco structures and factory. You need to be careful with your fleas though, the death explosions from most buildings can instantly kill them. Obviously, this strategy fails if they are not very greedy and bother to build some raiders.
====Glaive/Bandit rush====
====Scorcher rush====

Cheese

2018-08-14T15:51:25Z

213.35.139.72: /* Fencer rush */

Cheese strategies are strategies that can be described as high-risk and high-reward. These typically rely on winning hard and winning early. Below we will detail some of the finest cheese known to lobster-kind. 
Disclaimer: Some of these are quite bad strategies, but will probably sometimes work nonetheless.
==On the use of commanders==
A good rush will often include your commander. In the early parts of the game, this unit represents the majority of your combat strength. Most rushes just utilize the commander as a support unit that fills in a role that you need. However, some cheese strategies utilize the commander as a centerpiece of the strategy.

==The strategies==
===Fencer rush===
Plop rover factory, and put fencers on repeat queue. Once you have made like 2 it is time to start moving towards your opponent. Once your comm builds the starting mexes/energy move it towards the opponents base as well. Once you get to your opponent's base and see what they have been up to, choose an appropriate comm morph option. Continue streaming fencers across the map. When you have a critical mass of fencers you can just move in and kill them. But don't wait too long! If they get up significant defense you could end up losing.
*Rocket launcher is the best morph to get if they try to counter you with skirmishers.
*Riot cannon if they build lots of low-hp raiders.
*Heat ray is good if they try to make heavies.
====Defending against it====
A well-executed Fencer rush is extremely difficult to stop with conventional units. The natural counter to Fencers in the face of assault units is likely to be stopped by the enemy commander. Using your own commander is typically also a mistake because the enemy will be upgraded for combat and will focus their slashers on you.

The best answer is to drop everything and rush a Stinger. Having sacrificed all their economy, the opponent is likely to not have any economy, at most one mex. If you succeed in building a Stinger, they will have their zero mexes against your three, and no way to reasonably expand. After this, you can proceed to counter their contain with more conventional approaches.

Typically, a Fencer rush will also see the enemy factory left entirely defenceless - after all, each bit of metal spent on defence for your enemy is one not spent assisting in the actual rush. Sneaking away a single raider will usually suffice to kill this factory and prevent Fencer reinforcements or sneak expansion.

===Reaver rush===
Much like the fencer rush.
#Plop cloaky and take 1 mex.
#Make reavers on repeat queue.
#Move out with your comm and have reavers rally to it.
This rush is more time sensitive, and requires that you hit sooner than a fencer rush. Reavers are a bit faster than your comm so they will catch up to it.

===Ogre rush===
The Ogre is probably the most robust riot unit in the game, with high DPS and HP. It can be quite difficult to stop earlygame, especially if it is unscouted. The ogre is capable of killing commanders by itself and it has splash damage, making it quite effective against the raiders people typically build as well. This rush is time sensitive, as if they scout you they can throw up lots of light defense turrets and hold it off. 
#Plop the HT foundry.
#Queue up an ogre, set the rally point to your opponents base.
#Assist the factory with your commander.
This rush is especially effective against factories with no skirmishers, like HT or rovers. Factories with awkward skirmishers like spider may struggle to deal with it as well, but HT vs spider is a rare match-up anyways.

====Defending against it====
The best defense against any cheese is scouting, and this is true here. Build your lightest raider and send it to your opponent's base. Since the Ogre is an expensive unit, by the time your raider gets there it should still see the banisher in the factory being built, or just as it moves out. Since the opponent has commited quite a bit of resources to this rush you can affort to just spam lots of LLTs and the occasional Picket to hold it off. If your factory has a skirmisher, that would be a good choice to make as well.

While Rovers don't have any normal skirmishers, being able to produce a Dominatrix by the time the Ogre hits you turns the cheese upside down, as the Dominatrix will easily capture the Ogre, making it your enemy's problem now.

===Com-Morph Push===
===Com-Drop===
===Blastwing opening===
===Raider rush===
These types of rushes are distinct from the others in that they don't bring along the commander, and rely on overwhelming your opponent with an unexpected raider force. Below are listed some of the raiders that are most effective at rushing.
====Flea rush====
Plop spider factory and build your initial 500 metal into fleas. Send your first two out to scout. Once you get your flea swarm you can either attack the opponents base, or their commander. If their commander morphed to a splash damage weapon this will not work, but it should lead to a dead commander if the commander is alone and un-morphed. Alternatively, if they only built like 1 MT or LLT in their base and all their units are gone, you are able to quickly kill the defensive turrets and possibly win the game by killing all their eco structures and factory. You need to be careful with your fleas though, the death explosions from most buildings can instantly kill them. Obviously, this strategy fails if they are not very greedy and bother to build some raiders.
====Glaive/Bandit rush====
====Scorcher rush====

Cheese

2018-08-14T14:26:32Z

213.35.139.72: /* Defending against it */

Cheese strategies are strategies that can be described as high-risk and high-reward. These typically rely on winning hard and winning early. Below we will detail some of the finest cheese known to lobster-kind. 
Disclaimer: Some of these are quite bad strategies, but will probably sometimes work nonetheless.
==On the use of commanders==
A good rush will often include your commander. In the early parts of the game, this unit represents the majority of your combat strength. Most rushes just utilize the commander as a support unit that fills in a role that you need. However, some cheese strategies utilize the commander as a centerpiece of the strategy.

==The strategies==
===Fencer rush===
Plop rover factory, and put fencers on repeat queue. Once you have made like 2 it is time to start moving towards your opponent. Once your comm builds the starting mexes/energy move it towards the opponents base as well. Once you get to your opponent's base and see what they have been up to, choose an appropriate comm morph option. Continue streaming fencers across the map. When you have a critical mass of fencers you can just move in and kill them. But don't wait too long! If they get up significant defense you could end up losing.
*Rocket launcher is the best morph to get if they try to counter you with skirmishers.
*Riot cannon if they build lots of low-hp raiders.
*Heat ray is good if they try to make heavies.

===Reaver rush===
Much like the fencer rush.
#Plop cloaky and take 1 mex.
#Make reavers on repeat queue.
#Move out with your comm and have reavers rally to it.
This rush is more time sensitive, and requires that you hit sooner than a fencer rush. Reavers are a bit faster than your comm so they will catch up to it.

===Ogre rush===
The Ogre is probably the most robust riot unit in the game, with high DPS and HP. It can be quite difficult to stop earlygame, especially if it is unscouted. The ogre is capable of killing commanders by itself and it has splash damage, making it quite effective against the raiders people typically build as well. This rush is time sensitive, as if they scout you they can throw up lots of light defense turrets and hold it off. 
#Plop the HT foundry.
#Queue up an ogre, set the rally point to your opponents base.
#Assist the factory with your commander.
This rush is especially effective against factories with no skirmishers, like HT or rovers. Factories with awkward skirmishers like spider may struggle to deal with it as well, but HT vs spider is a rare match-up anyways.

====Defending against it====
The best defense against any cheese is scouting, and this is true here. Build your lightest raider and send it to your opponent's base. Since the Ogre is an expensive unit, by the time your raider gets there it should still see the banisher in the factory being built, or just as it moves out. Since the opponent has commited quite a bit of resources to this rush you can affort to just spam lots of LLTs and the occasional Picket to hold it off. If your factory has a skirmisher, that would be a good choice to make as well.

While Rovers don't have any normal skirmishers, being able to produce a Dominatrix by the time the Ogre hits you turns the cheese upside down, as the Dominatrix will easily capture the Ogre, making it your enemy's problem now.

===Com-Morph Push===
===Com-Drop===
===Blastwing opening===
===Raider rush===
These types of rushes are distinct from the others in that they don't bring along the commander, and rely on overwhelming your opponent with an unexpected raider force. Below are listed some of the raiders that are most effective at rushing.
====Flea rush====
Plop spider factory and build your initial 500 metal into fleas. Send your first two out to scout. Once you get your flea swarm you can either attack the opponents base, or their commander. If their commander morphed to a splash damage weapon this will not work, but it should lead to a dead commander if the commander is alone and un-morphed. Alternatively, if they only built like 1 MT or LLT in their base and all their units are gone, you are able to quickly kill the defensive turrets and possibly win the game by killing all their eco structures and factory. You need to be careful with your fleas though, the death explosions from most buildings can instantly kill them. Obviously, this strategy fails if they are not very greedy and bother to build some raiders.
====Glaive/Bandit rush====
====Scorcher rush====

Typical game progression

2018-08-14T14:23:04Z

213.35.139.72: /* Late-Lategame */

This is a guide explaining how a typical game progresses, after a [[typical opening]].
The game can be thought of as being organically split up into a few phases, each with a characteristic set of units and goals.
*Note that these are general scenarios - depending on the map and factory match-up the game can play very differently!
*From a 1v1 perspective
*(wip)
==Raider phase==
The raider phase is the first phase in a typical game. It is defined by a few characteristics:
*Most of the map is untaken by either player.
*No defenses covering most areas.
Due to this, the mobility that raiders have tends to make them the dominant unit class. When the map is fortified with light defenses, raiders are much less useful and it will be time to switch to something else.
===Expansion===
You will want to expand as fast as possible here, and try to grab at least 50% of the map. Try to have two groups of constructors moving around the map taking mexes. Near each mex cluster you can put some light defences, but do not overbuild defences early game, and in non-critical locations (i.e. not a choke point or the centre of the map). Run around the map with your raiders, keeping track of where your opponents raiders are as well.

You should be able to defend your expansion from enemy raiders with some light defenses and some of your own raiders. Since raiding properly is considerably more difficult than expanding, you should be encouraged to expand as fast as possible.
*Try to expand much faster and in a more risky manner than you think is possible for a few games. You might be surprised at how much greed you get away with! It is much harder to punish greed than it is to be greedy. Doing this will also help you learn the safe maximum limits for expansion.
If you succeed in this phase of the game, you will have a massive eco advantage and will be able to swarm your opponent to death with units.
====Energy production====
A very common mistake players make is that they don't build enough energy structures. This leads to a situation in which your metal income exceeds your energy income and you are unable to spend all your metal (called "e-stalling"). Having 1 constructor dedicated to only building energy structures can solve this issue.

===Raider Usage===
You want to have good radar coverage of your side of the map and keep your raiders as close to the enemy as possible. This puts pressure on them, and also forces them to keep their raiders near their base, away from your expansion. Against good players you will not be able to do much damage with raiders, but that does not mean you have accomplished nothing by keeping your raiders near them.
*Because of the threat of your raiders, they are not able to "naked expand" (very fast expansion with minimal or no defense). If you allow your opponent to naked expand, they will typically just roll you over a few minutes later with a massive eco advantage.
*Forces your opponent to keep their own raiders near their own base to defend from yours. It can also force them to build more defense, slowing down their expansion and reducing the amount of pressure they can put on your own expansion.
*Gives scouting information. By running around at the edges of your opponents territory you will be able to see what they are up to. If they are trying to rush a heavy unit or do something silly you will often just be able to overrun them and win.

If you find yourself on being the one that has raiders at their front door, things are a little more challenging, but don't panic.
*Try to expand where your enemies raiders are not(with that other group of builders on the other side of the map that you have...right?).
*You can slowly creep forward with LLTs and the protection of your own raiders.

In higher level games what usually ends up happening is that both players are good at raider control and don't really kill much of importance on either side. While raiders are chasing each other, each player is slowly building up and fortifying territory as they move closer to the center of the map.
*Fortifying territory means building maybe 1 or 2 defensive towers near mex clusters and also putting some defensive towers near some critical locations to block off pathing. You should get essentially a full line of sight across your front line, so your opponent cannot sneak units into the middle of your territory without taking some damage from towers and you not knowing about their movements.

Note that you do not need to kill anything to have a successful raider phase. Your primary goals are to expand and grab territory while slowing your opponents expansion to a reasonable pace, and also have the energy to use all the metal you took control of. Your raiders will be useful later, so try to keep them alive. There is a "reasonable maximum speed" at which players can safely expand, and as long as you make sure your opponent doesn't exceed this and you are close to it, you will probably enter the later stages of the game on equal footing. Not every game is won or lost in the raider phase, and in fact, probably most aren't.

Often you will see a location that is lightly defended with towers, and you will correctly assume that you can run into it with your raiders and kill everything. However, this is a risky (and often unnecessary) thing to do.
*There might be some defense you don't see, like nearby units ready to help.
*Killing towers with raiders is not cost efficient, so the payoff might not be that good.
**This could lead to your opponent taking a temporary raider number advantage, which could put you on the defensive and actually put you behind from where you were before, as you are no longer able to exert as much map pressure.
*Committing your raiders to an attack like this open you up for the possibility of a counter-attack, and since your raiders are somewhere else, you might not be able to defend.

====Finding a lone commander====
Sometimes your opponent may be a bit greedy and have their commander out alone. If it is a low level you might be able to kill it with your raiders if you have like 10 or so. It is almost always worth it to kill a commander. Some raiders like kodachae or daggers are bad at this, but others like scorchers are amazing at it.
*Spread your units out right before it dies, as they have a death explosion which could wipe out your raiders if they are really close to the commander.

===Why not other unit classes?===
====Riots====
It may seem intuitive to make riot units in this phase of the game. "They're good against raiders, aren't they?" you may say (correctly). However, their downside is that they are very slow. This makes them unusable for offense, as your opponent will see them coming and be able to easily respond. Also:
*Early game, lone riot units can be overwhelmed by raiders.
**You can use line move to spread out your raiders (preferably in a concave) and then just run at the lone riot unit and kill it. Try to get your raiders to encircle the riot to minimize any AOE damage it may do.
*Light defenses are effective against riots, as riots are DPS, not HP focused. Light defenses will take a significant portion of the riot's HP away before the riot is close enough to fire. What usually happens is that the riot maybe kills one or two defensive towers and then just dies(very cost inefficient).
**Due to targeting oddities, the riot will often stay locked into firing at a defensive tower. This gives you an opportunity to swoop in with raiders and kill the riot quickly, before it even gets a chance to fire at your raiders.
Because of the above reasons, they do not pose much of a threat (unless you don't scout a [[cheese|riot rush]] of some sort and lose anyway).
*You can just run past the riots and ignore them. Because of this, players tend to spread out their riots to try to cover every location so you can't run past them.
**Notice how this contributes to the first point.
The correct way to deal with an opponent making riots is to just expand faster than they do - they won't be able to punish this. When you inevitably get superior eco, you can just overwhelm them.
Try also running around with your raiders near your opponents front lines. They will often be scared by this and will need to be constantly re-positioning their riots to defend from a possible raider run-by into their base. If you see that they are doing this, you can expand even faster, as they don't have any way to punish your expansion.

====Any other class====
Skirmishers, artillery, assaults - all of these do very badly against raiders, so are not worth building at this point.
===Importance of radar===
Radar coverage is very important to get in this phase. If you do not have it, you have to play defensively in case your opponents tries to raid some of your expansions. The alternative is building tons of defenses everywhere, but this is a losing strategy, as it leaves you unable to punish your opponent for expanding. If they expand they will just overrun you with units. By building radar you can reduce the amount you spend on defense, and can use it on offensive units instead. In the worst case scenario, you prevent greedy expansion from your opponent. In the best case, you just win because they were too greedy and have no units.
===Dealing with defensive players===
A strategy that many have trouble dealing with is when your opponent just builds lots of defenses at every expansion site. The best way to deal with this, paradoxically, is to just ignore them and focus on expanding yourself. If they want to sit in the corner building defense, that is fine (for you). Since they have spent so much metal on this, they won't be able to prevent you from expanding, so just take the whole map, make lots of eco, and then come to their base with artillery and win. There is really no situation in which fortifying yourself into a small section of the map is a winning strategy.

===End of raider phase===
Eventually, the map will become covered with a line of defenses from both players, partitioning the map roughly in half. This limits the mobility advantage that raider have, and it becomes time to switch to something else. Some areas might be lightly defended, and if you know the enemie's raiders are not close, you can punish this, but by this point people often have full radar coverage and its not that difficult to spot and defend these sorts of things.

==Midgame phase==
In this phase, strategic diversity opens up significantly. Players typically transition out of raiders into some of the following:
===Skirmishers===
A common strategic switch people make is a shift to building raiders skirmishers rather than raiders. These units are capable of killing light defenses fairly well, so you can start pushing back your opponent and try to grab more territory. Use your raiders (which are hopefully still alive) to protect your skirmishers from harm. It is also common to see a few riots dedicated to protecting your skirmishers.
===Assaults===
For some factories, it is possible to switch to assault units. These units will be able to punch through light defenses (unlike raiders) and do some economic damage to your opponent.
Some examples:
*Thuglaw - Outlaws and Thugs - this combination from the shieldbot factory is a very potent assault force. It is good against raiders and light defences, giving it the potential to do lots of damage to an unprepared opponent.
*Ravagers - Fast assault rovers that can be used for raiding. They are able to eat through light defences, and due to their speed it is harder to position raiders to defend against them.
===Air switch===
A very typical midgame transition is switching to air. Air units are typically quite a bit faster than ground units, and do not suffer from pathing difficulties that ground units do. It is advantageous to get air units for a few reasons.
*They are very good at shutting down raiding, both from raiders and fast assaults like ravagers.
**These units are difficult to chase down with more typical midgame units like riots or skirmishers. It is often a losing move to chase units this way, as the lack of riots/skirmishers at your frontlines means your outermost expansions will probably be taken from you.
**Air units are fast enough to catch anything, and typically will take little return damage.
**Helps further consolidate your front lines as you no longer have to worry so much about being counterattacked as much.
*Air gives you the ability to scout easily.
**You can see what your opponent is up to. Are they rushing a strider? Lots of fusions? Other greedy things?
*You can punish very greedy behavior.
**Kill expansions with minimal defense. For example, if they just have like 1 LLT and defender.
**Kill undefended eco structures(fusions,windmills).
*Forces your opponent to divert some metal to anti-air(if they don't want to die).
**Can take some pressure off your front lines, as they can't send as many ground reinforcements. Anti-air units are pretty useless against anything that isn't air.
**Typically this makes both players back off on the front lines for a bit and get readjusted for air game play.

There are two air factories, which play very differently from each-other.

====Airplane Factory====

====Gunships====

Gunship units are a little slower than their air counterparts, and they also are DPS focused, instead of alpha focused like planes.

====Playing against air====

===Fortification===
In the midgame, players will sometimes fortify certain locations on the map with heavier defenses such as stingers or stardusts. This happens at central locations of the map as it gives you a sort of staging point that you can keep your units at safely. Heavier defenses generally require a specialized response of artillery or heavy units, so by building some, you can buy yourself some time as your opponent is figuring out a way to deal with the heavy defenses.
Stingers are especially tricky at this part of the game, as they are the first type of tower that can actually fight skirmishers well. If you find yourself losing ground to skirmishers or expect them soon, it may be a good idea to put up a stinger. Stingers do not do that well against lots of light units, so make sure to keep building lots of LLTs(or even add a stardust).

==Lategame==
Both players with have built up sizable armies of skirmishers/riots/assaults and will probably have some air presence. The map will be more fortified, and it will be difficult to make progress with "lighter" units.
===Eco===
If things have stabilized in the midgame, it may be time to build some eco.
*Build all the available geothermal power plants(they are super efficient!). If you feel that some are very safely located, upgrade them.
*Connect your energy grid together. The more mexes you connect, the more efficiently energy will be used and the more metal you will have.
**Overdrive is VERY efficient at low levels of energy. Something like 2 e/s can increase production 50%.
*Build fusion energy reactors.

As with expansion, it is much harder to punish greedy eco-ing than it is to do it yourself. Try to be a greedy as possible and learn what the safe limits are.

===Heavies===
At this stage in the game you will start to see heavies coming out. "Heavies" are units that are generally 1500+ cost. Most of them massacre the lighter skirmisher/assualt/riot balls that are predominant in the midgame, and they also can stand up the to defenses built in the midgame(ie they can actually kill stingers). Units such as cyclops, sumo, grizzly will be often seen.

===Bot specialist units===
The bot factories do not really have "heavies", but they do have more expensive upper tier units that can be used to fight heavies of other factories.
*Cloaky factory will start to build Snipers and area-cloakers.
*Shield bots can build felons and aspis. Felons supported by aspis can deal a very large amount of damage very quickly, burning through the health of almost anything. Racketeers are commonly added too, and these are good at disabling heavy units.

===Light striders===
Someone putting down a strider hub and making either a scorpion or dante is quite common.
*Dante is very good against skirmisher balls as its "D-gun" can 1 shot most of them. It is also one of the faster striders so it can get into action quickly. Due to all its aoe damage, it massacres riots and raiders as well. It fights assaults decently, but be careful, it actually loses to most of them by cost. You need to retreat and repair it to get full value out of it.
**Be carefull with your own units around the dante. The dante causes alot of chaos and fire and flames everywhere, and this can also hit your own units and kill them.
*Scorpions are invisible and have their EMP- D-gun. This can be used to sneak up on valuable targets like commanders or a bunched up set of units, stun them, and then kill them. Scorpions are probably more of a support unit, as their dps is much lower than a dante, and also get kitied by skirmishers easily.
**Scorpions beat dantes quite easily, especially if they get their stun off.

==Late-Lategame==
In this phase you will see heavy striders and some of the more exotic tools available to the player.
*Nuke
*Ultra-heavy porc
**Desplator/Lucifer
**Bertha/Cerberus
*Paladin/Detriment
*Starlight/Zenith/DRP
*Singularity

==Conclusion==
Note that this is a general overview. Sometimes people may rush heavies in the midgame, or eco during the raider phase or whatever else. Zero-k is a very flexible game, and there is no really hard or set meta-game like in starcraft 2. Lots of game play is map-dependent or match-up dependent.

Abbreviations

2018-07-30T11:27:35Z

213.35.139.72:

Maybe ideal for new player (under construction). So please add something useful here. Also expand into ZK slang in general, not just abbreviations.

===A===
*AA - Anti Air
*anni - [[Lucifer]] (anni is from Annihilator, the old name) (heavy tachyon tower)
*AoE - Area of Effect (splash damage)
*avenger - old name for [[Swift]] (multirole fighter)
*Amph - Amphibious bots
*Air - Typically plane factory; rarely gunships.

===B===
* Bantha - Old name for [[Paladin]]
*BB - Big Bertha - the long range cannon
*BD - Revenant, comes from old name Black Dawn - Heavy Raider/Assault gunship
*behe - Cerberus, from old name Behemoth
*BW - BlastWing - flying bomb unit

===C===
*cata - [[Merlin]]. From the old name, Catapult. - artillery strider
*CCR - Comet Catcher Redux - the flat vehicle map
*com(m) - Commander - the starting unit
*con - Constructor - any mobile unit with ability to build stuff
*CS - ChainSaw - Long Range Anti Air

===D===
*det - (also detri) - Detriment (the largest strider)
*DDM - Desolator, formerly known as the Doomsday Machine - heavy defensive structure
*dgun - Disintegrator Gun - class of special weapons that need manual activation using "D" key - for example Dante's missile volley or special commander weapons
*domi - [[Dominatrix]] (capture vehicle)
*DPS - Damage Per Second
*DRP - Disco Rave Party - the superweapon
*Drop - A "drop" happens when units are loaded into transports and then "dropped" somewhere, like the enemy base
*DSD - Delta Siege Dry - a popular teams map

===E===
*E - Energy - the resource
*eco - Economy - all resource-producing units and buildings
*elo - a rating system used for balancing games basing on estimated players skill
*EMP - ElectroMagnetic Pulse - paralyzer weapons, can also be used to mean an air player using thunderbird.

===F===
*fac- Factory - building that produces mobile units
*FW - Firewalker (artillery bot)
*fus - Fusion Reactor
*Firepluk award - Named after the player Firepluk; When a player resigns very early into the game but ends up winning anyways.

===G===
*geo - Geothermal Powerplant or the spot where it can be built (also ''geospot'')
*GS - Gunships
*golly or Goli - [[Cyclops]], formerly known as Goliath (heavy tank)
*grid - energy grid - system of connected energy sources, part of overdrive. Structures are in the same grid if their "circles" touch.

===H===
*HLT - Heavy Laser Tower ([[Stinger]])

===J===
*JJ - JumpJet factory

===L===
*Licho - old name for [[Likho]] (heavy bomber plane)
*link - to link disconnected parts of energy grid together OR to link shields together
*LLT - Light Laser Tower (the [[Lotus]] turret)
*lobster - a taunt for a player who haven't performed well in ongoing or previous battle(s).
*LoS - line of sight
*LV - Light Vehicles (Factory) - LV got renamed to Rover factory

===M===
*M - Metal - the resource
*mex - Metal Extractor, to mex the action of constructing extractors on untapped metal spots
*morph - to upgrade a commander or a geothermal generator
*moho - old name for Advanced Geothermal
*MT - Missile Tower (the Picket turret)

===N===
*nano - Caretaker nanolathe tower (static constructor)
*nap - to kidnap - usually "comnap" - capture enemy commander with air transport

===O===
*OD - OverDrive - overdrive pumps spare energy to metal extractors to improve their output, see [http://zero-k.info/wiki/Overdrive economic section of the manual]
*OP - OverPowered - something is considered too good for its cost (eg a unit/module/ability)
*owled - weak enough it might as well not be in the game

===P===
*pene - Lance. From old name penetrator. (hovercraft artillery)
*porc - (from porcupine) - heavy defenses, usually useless
*porcing - playing too defensively, not taking enough land
*PW - PlanetWars - the online multiplayer campaign
*plop (fac) - deploying your first factory, which is free and builds instantly

===R===
*rec - Reclaim - command to recycle units, wreckages and map features
*ress/rez - Ressurection (common misspelled version of resurrection) - ability to recreate a unit from its wreckage

===S===
*SD - Stardust
*singu - Singularity Reactor - most powerful, and most dangerous energy-producing structure
*Shadow - old name for Raven (bomber plane)
*shiny - huge explosion caused either by nuke, advanced geothermal or destruction of Singularity Reactor. Can also be used when a lot of bombs chain explode.
*skydust - Stardust on a terraformed spire
*Starlulz - [[Starlight]]
*stiletto - old name for Thunderbird (disarming plane)
*selfd - Self Destruct - usually meant as an encouragement to self destruct all your things using CTRL+A, CTRL+D keys to end the game; sometimes to self destruct a single unit for its powerful death explosion
*shield-ball - A group of units that have shields, usually containing thugs, felons, and possibly an aspis(mobile area shield)

===T===
*TB - Thunderbird - area disable bomber plane.
*terra - Terraform - a way to modify map's landscape
*Trollcom - Typically a disintegrator gun command with high movement speed.

===U===
*ubermex - a metal extractor spot with much more yield than usual (4+ while typical mex is 2)
*UP - UnderPowered - something is considered too weak for its cost (eg a unit/module/ability)
*Ulti - Ultimatum - cloaked anti-heavy strider

===W===
* Wubbernaut - A new player. Comes from wub (similar to nub) + naut (to explore).

===Z===
*ZK - Zero Kelvin - the name of this game

{{Navbox manual}}

Crab

2018-07-30T11:22:37Z

213.35.139.72:

The '''{{PAGENAME}}''' is a heavy riot/skirmish spider that curls into armored form when stationary from the [[Spider Factory]].{{ Infobox zkunit
| name = Crab
| defname = spidercrabe
| description = Heavy Riot/Skirmish Spider - Curls into Armored Form When Stationary
| image = http://manual.zero-k.info/unitpics/spidercrabe.png
| icontype = spidersupport
| cost = 1600
| hitpoints = 4000
| movespeed = 41
| turnrate = 99
| sight = 660
| transportable = Heavy
| weapons =
{{ Infobox zkweapon
| name = Heavy Plasma Cannon
| type = Cannon
| damage = 601
| reloadtime = 4
| dps = 150
| range = 600
| aoe = 100
| projectilespeed = 290
}}
| abilities =
{{ Infobox zkability armored
| reduction = 75%
}}
}}==Description==
The Crab's huge shells obliterate large swarms of cheap units, and can also outrange basic defenses. When it stops walking, Crab curls up into armored form reducing incoming damage to a quarter. The Crab's main weakness is its lack of mobility.

==Tactics and Strategy==
It is better for defense than attack despite it's high damage, because if it is not moving it gets a much stronger defense and can tank hits better.

For a particular type of offense, it is often useful to convert the Crab in to a a flex-artillery piece by moving it towards enemy fortifications, stopping just outside of their range, and terraforming a spire underneath to extend its range.

{{Navbox units}}

Crab

2018-07-30T11:22:21Z

213.35.139.72: /* Tactics and Strategy */

The '''{{PAGENAME}}''' is a heavy riot/skirmish spider that curls into armored form when stationary from the [[Spider Factory]].{{ Infobox zkunit
| name = Crab
| defname = spidercrabe
| description = Heavy Riot/Skirmish Spider - Curls into Armored Form When Stationary
| image = http://manual.zero-k.info/unitpics/spidercrabe.png
| icontype = spidersupport
| cost = 1600
| hitpoints = 4000
| movespeed = 41
| turnrate = 99
| sight = 660
| transportable = Heavy
| weapons =
{{ Infobox zkweapon
| name = Heavy Plasma Cannon
| type = Cannon
| damage = 601
| reloadtime = 4
| dps = 150
| range = 600
| aoe = 100
| projectilespeed = 290
}}
| abilities =
{{ Infobox zkability armored
| reduction = 75%
}}
}}==Description==
The Crab's huge shells obliterate large swarms of cheap units, and can also outrange basic defenses. When it stops walking, Crab curls up into armored form reducing incoming damage to a quarter. The Crab's main weakness is its lack of mobility.

==Tactics and Strategy==
It is better for defense than attack despite it's high damage, because if it is not moving it gets a much stronger defense and can tank hits better.

For a particualr type of offense, it is often useful to convert the Crab in to a a flex-artillery piece by moving it towards enemy fortifications, stopping just outside of their range, and terraforming a spire underneath to extend its range.

{{Navbox units}}

Self Destruct Command

2018-07-26T13:25:21Z

213.35.139.72: Differences between Self Destruct, Detonate, and Cancel Terraform

The '''Self Destruct''' command causes the unit to self destruct after a delay. The self destruct timer is 5 seconds, with the exception of bomb units, which self destruct instantly. This command is only accessible via the '''Ctrl+D''' hotkey.

Self destruction can be cancelled by issuing the Self Destruct command again during the delay period.

All of the instant-detonating bomb units have a version of Self Destruct called '''Detonate''', accessible via menu button or by pressing '''D''', which detonates them immediately but does not directly affect non-suicide units in the current selection. You can use this to prevent accidental self-destruction of important units.

The '''Cancel Terraform''' command on individual terraform blueprint objects has a similar effect to '''Detonate''', with the difference that terraform units don't have any explosions and will disappear silently.

{{navbox commands}}

Nimbus

2018-07-11T12:27:41Z

213.35.139.72: Undo revision 4304 by 75.97.197.255 (talk)

The '''{{PAGENAME}}''' is a fire support gunship from the [[Gunship Plant]].{{ Infobox zkunit
| name = Nimbus
| defname = gunshipheavyskirm
| description = Fire Support Gunship
| image = http://manual.zero-k.info/unitpics/gunshipheavyskirm.png
| icontype = heavygunshipskirm
| cost = 760
| hitpoints = 2800
| movespeed = 99
| turnrate = 99
| sight = 600
| weapons =
{{ Infobox zkweapon
| name = Heavy Pulse MG
| type = Cannon
| damage = 19.3 × 4
| reloadtime = 0.45
| dps = 172
| range = 600
| aoe = 20
| inaccuracy = 2.8
| projectilespeed = 420
}}
}}==Description==
The Nimbus is a fire support gunship that flies out of the reach of most ground mobiles. It is tough enough to survive limited anti-air fire, and its twin EMGs chew through units stupid enough to stay put.

{{Navbox units}}

Missile Silo Tutorial

2018-05-31T12:03:36Z

213.35.139.72: /* Stationary/Predictable Bantha */

Properly used, the [[Missile Silo]] can be detrimental to even the most extreme fortifications. It is not cheap, so it should only be used when everything else fails.

== Damage ==
Damage can be dealt to single structures or over large areas. The [[Eos]] does 3500 damage with a small blast radius, aim for points where multiple buildings touch to apply this damage to more than one building. If there are bigger clusters of structures, the [[Inferno]] can be used as it has a much bigger area of effect.

== Shields and Terraform ==
Every missile except the [[Shockley]] will be stopped by full shields. If the shields are slightly below full charge, the [[Eos]] can pass through them as well. Shields can be circumvented by either stunning or weakening them before firing the remaining missiles. For a successful stun, first scout all aegis and then use Shockleys to stun them, keep the small AOE of the Shockley in mind. Multiple stuns might be needed to deactivate all shields if they are spread out. Alternatively, an Eos can be used to weaken all shields in a shield network. After firing one Eos, any following Eos will pass freely through the shields, as long as the shield get a few seconds to equalize their charges.

Terraform can be flattened by the use of a [[Quake]] missile. Those have a high trajectory, so you have to target them at the terraform. They don't pass through shields, even at low charge. Alternatively, the AOE of the Eos or Inferno can be used to do damage through terrain.

== Timing and Trajectories ==
The trajectory of the Shockley and Quake missiles are much higher than those of the Inferno and Eos. Those subsequently have a longer flight time than the latter and can mostly ignore terrain. Make sure to account for the additional flight time of those missiles, firing them at the same time as low trajectory missiles will otherwise result in the latter impacting before the defenses are stunned/the terrain smoothed.

You should never fire multiple missiles simultaneously, as it only has downsides over firing them in quick succession. Repair is compensated by a small extra damage over the stated values. When the enemy has multiple shields, a small delay between missiles ensures that the damage is spread over all shields. Thus the other shields can't block the remaining missiles as they would if the missiles were fired simultaneously.

== Examples ==

=== Shielded Cerberus ===
Fire one Eos, wait 2 seconds, fire other 2 Eos.

=== Terraformed Shielded Advanced Geo ===
Either fire a Shockley at the shields, wait for it to impact and then finish it off with a Quake followed by an Eos, or try to splash damage it by aiming 2 Eos at either the back of the moho or the base of the terraform.

=== Stationary/Predictable Paladin ===
Fire 2 Shockleys to stun it, finish off with Raiders. Restun with a single Shockley after 40 seconds if needed. The same works for Detriment with 4 Shockleys.

{{Navbox manual}}

Missile Silo Tutorial

2018-05-31T12:03:24Z

213.35.139.72: /* Terraformed Shielded Moho */

Properly used, the [[Missile Silo]] can be detrimental to even the most extreme fortifications. It is not cheap, so it should only be used when everything else fails.

== Damage ==
Damage can be dealt to single structures or over large areas. The [[Eos]] does 3500 damage with a small blast radius, aim for points where multiple buildings touch to apply this damage to more than one building. If there are bigger clusters of structures, the [[Inferno]] can be used as it has a much bigger area of effect.

== Shields and Terraform ==
Every missile except the [[Shockley]] will be stopped by full shields. If the shields are slightly below full charge, the [[Eos]] can pass through them as well. Shields can be circumvented by either stunning or weakening them before firing the remaining missiles. For a successful stun, first scout all aegis and then use Shockleys to stun them, keep the small AOE of the Shockley in mind. Multiple stuns might be needed to deactivate all shields if they are spread out. Alternatively, an Eos can be used to weaken all shields in a shield network. After firing one Eos, any following Eos will pass freely through the shields, as long as the shield get a few seconds to equalize their charges.

Terraform can be flattened by the use of a [[Quake]] missile. Those have a high trajectory, so you have to target them at the terraform. They don't pass through shields, even at low charge. Alternatively, the AOE of the Eos or Inferno can be used to do damage through terrain.

== Timing and Trajectories ==
The trajectory of the Shockley and Quake missiles are much higher than those of the Inferno and Eos. Those subsequently have a longer flight time than the latter and can mostly ignore terrain. Make sure to account for the additional flight time of those missiles, firing them at the same time as low trajectory missiles will otherwise result in the latter impacting before the defenses are stunned/the terrain smoothed.

You should never fire multiple missiles simultaneously, as it only has downsides over firing them in quick succession. Repair is compensated by a small extra damage over the stated values. When the enemy has multiple shields, a small delay between missiles ensures that the damage is spread over all shields. Thus the other shields can't block the remaining missiles as they would if the missiles were fired simultaneously.

== Examples ==

=== Shielded Cerberus ===
Fire one Eos, wait 2 seconds, fire other 2 Eos.

=== Terraformed Shielded Advanced Geo ===
Either fire a Shockley at the shields, wait for it to impact and then finish it off with a Quake followed by an Eos, or try to splash damage it by aiming 2 Eos at either the back of the moho or the base of the terraform.

=== Stationary/Predictable Bantha ===
Fire 2 Shockleys to stun it, finish off with Raiders. Restun with a single Shockley after 40 seconds if needed. The same works for Detriment with 4 Shockleys.

{{Navbox manual}}

Missile Silo Tutorial

2018-05-31T12:03:11Z

213.35.139.72: /* Shielded Behemoth */

Properly used, the [[Missile Silo]] can be detrimental to even the most extreme fortifications. It is not cheap, so it should only be used when everything else fails.

== Damage ==
Damage can be dealt to single structures or over large areas. The [[Eos]] does 3500 damage with a small blast radius, aim for points where multiple buildings touch to apply this damage to more than one building. If there are bigger clusters of structures, the [[Inferno]] can be used as it has a much bigger area of effect.

== Shields and Terraform ==
Every missile except the [[Shockley]] will be stopped by full shields. If the shields are slightly below full charge, the [[Eos]] can pass through them as well. Shields can be circumvented by either stunning or weakening them before firing the remaining missiles. For a successful stun, first scout all aegis and then use Shockleys to stun them, keep the small AOE of the Shockley in mind. Multiple stuns might be needed to deactivate all shields if they are spread out. Alternatively, an Eos can be used to weaken all shields in a shield network. After firing one Eos, any following Eos will pass freely through the shields, as long as the shield get a few seconds to equalize their charges.

Terraform can be flattened by the use of a [[Quake]] missile. Those have a high trajectory, so you have to target them at the terraform. They don't pass through shields, even at low charge. Alternatively, the AOE of the Eos or Inferno can be used to do damage through terrain.

== Timing and Trajectories ==
The trajectory of the Shockley and Quake missiles are much higher than those of the Inferno and Eos. Those subsequently have a longer flight time than the latter and can mostly ignore terrain. Make sure to account for the additional flight time of those missiles, firing them at the same time as low trajectory missiles will otherwise result in the latter impacting before the defenses are stunned/the terrain smoothed.

You should never fire multiple missiles simultaneously, as it only has downsides over firing them in quick succession. Repair is compensated by a small extra damage over the stated values. When the enemy has multiple shields, a small delay between missiles ensures that the damage is spread over all shields. Thus the other shields can't block the remaining missiles as they would if the missiles were fired simultaneously.

== Examples ==

=== Shielded Cerberus ===
Fire one Eos, wait 2 seconds, fire other 2 Eos.

=== Terraformed Shielded Moho ===
Either fire a Shockley at the shields, wait for it to impact and then finish it off with a Quake followed by an Eos, or try to splash damage it by aiming 2 Eos at either the back of the moho or the base of the terraform.

=== Stationary/Predictable Bantha ===
Fire 2 Shockleys to stun it, finish off with Raiders. Restun with a single Shockley after 40 seconds if needed. The same works for Detriment with 4 Shockleys.

{{Navbox manual}}

Thug

2018-05-07T16:08:58Z

213.35.139.72: outlaw has no beam

The '''{{PAGENAME}}''' is a shielded assault bot from the [[Shieldbot Factory]].{{ Infobox zkunit
| name = Thug
| defname = shieldassault
| description = Shielded Assault Bot
| image = http://manual.zero-k.info/unitpics/shieldassault.png
| icontype = walkerassault
| cost = 180
| hitpoints = 960
| movespeed = 58
| turnrate = 330
| sight = 420
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Light Plasma Cannon
| type = Cannon
| damage = 170
| reloadtime = 4
| dps = 43
| range = 280
| aoe = 18
| projectilespeed = 200
}}
| abilities =
{{ Infobox zkability shield
| name = Energy Shield
| strength = 1250
| regen = 16
| regencost = 0
| radius = 80
}}
}}==Description==
Weak on its own, the Thug makes an excellent screen for Outlaws and Rogues. The linking shield gives Thugs strength in numbers, but can be defeated by AoE weapons or focus fire.

==Tactics And Strategy==

Send Thugs to destroy the opponent's static defenses while tanking the damage for Rogues and Outlaws.

A small group of Thugs benefit greatly from an Outlaw, as the Outlaw slows down the fire rate of turrets, allowing the Thugs to tank damage for a longer time, while also slowing down raiders who attack the group. As a benefit, the Thugs can tank for the Outlaw, allowing the Outlaw's disruptor pulse to finish its work.

Use Thugs with Felons to tank damage intended for the Felon, while also helping regenerate the Felon's shields.

Thugs can be used as heavy raiders as they can go through light defense by themselves or with a partner that Bandits wouldn't be able to.

Thugs lack damage, so they take time to destroy enemy static defense, so bringing some Bandits along will allow the Bandits to get close and destroy the static defense while the Thugs tank damage for them.
{{Navbox units}}

Attack Move Command

2018-04-18T10:26:53Z

213.35.139.72: grammer

The '''Attack Move''' command, also known as Fight, tells units to proceed to the command's designated goal while engaging encountered targets.

Units with their [[Unit_states#Unit_AI|Unit AI]] state will use their tactical AI when encountering the enemy - raiders will swarm skirmishers, skirmishers will kite assaults, and so on. This is very distinct from e.g. Move command, which doesn't engage the AI and can be considered a manual override.

Builders given the Attack Move command will indiscriminately use their buildpower to perform every possible build task en route, such as reclaiming any wrecks and other features, repairing damaged units, and assisting incomplete constructions.

For this reason, a factory whose rally point is given using the Attack Move command will usually have every builder produced at that factory automatically assist the factory. This can be both beneficial or harmful - on one hand, it automates construction of new buildpower for the factory; on the other, this means the builders will not go where they may be more needed unless explicitly ordered.

{{Navbox commands}}

Stop Command

2018-04-17T11:26:19Z

213.35.139.72: STAHP

The '''Stop''' command immediately clears the unit's command queue and resets its target.

It does not affect unit states or arrest movement, however: unless under effects of Hold Fire and Hold Position, the unit will immediately resume fighting if enemies are nearby.

Addtionally, Stop doesn't interrupt Commander upgrade or other unit morphs, and cannot prevent an already unleashed salvo weapon (like Thunderbird Lightning) from finishing the salvo.

Stopping airplanes with Land State set to Land will also cause them to land immediately. This can be used to land Swifts in precise positions that allow them to use their blasters against static targets without having to waste time on fly-bys.

{{Navbox commands}}

Capture

2018-04-17T10:49:50Z

213.35.139.72: fix typo

The Dominatrix is a unit in the Vehicle Factory capable of '''capturing''' enemy units.

http://manual.zero-k.info/unitpics/vehcapture.png

Capture uses a progress bar with a maximum value for each unit equal to its ''cost''. Dealing capture damage increases the progress along this bar. Every allyteam has independent capture progress for every unit so that you cannot steal a capture "kill" from an enemy. Capture damage decays at 4% per second if none has been taken within the five seconds second. Damaged units are captured more quickly than healthy units. A unit at 0% health is captured 3x faster, with the multiplier linearly decreasing to 1x at 100% health.

A unit is captured upon filling its capture bar. The Dominatrix that contributed the last section of capture progress takes control of the unit and the target becomes controllable by the player who owns the Dominatrix. This control is shown by a control line leading from the Dominatrix to the captured unit. The full line is visible to any enemy player who has vision of either end of the line, so they can spot hidden controllers. The Dominatrix that takes control must recharge for 8 seconds before it is able to fire. Note that contributing Dominatrices can continue firing at new targets immediately.

Killing a Dominatrix returns all the units under its control to their original owners. The returned units start with 95% capture progress so are easy to re-capture if there are Dominatrices around. Capturing a Dominatrix grants control of it as well as its subordinates. Battles with Dominatrices on both side can result in a tree-like control structure.

Capturing a unit that originally belonged to an ally returns it to that ally without creating a control link.

{{Navbox manual}}

Area Mex Command

2018-04-17T10:39:09Z

213.35.139.72: add basic description

The '''Area Mex''' command queues construction of metal extractors in a given area.

The individual constructions are ordered from the nearest mex to the builder in the area to the farthest, disregarding obstacles - for this reason it may be better to queue several Area Mex orders to guarantee an optimal builder walk path.

Holding '''ALT''' while placing an Area Mex order will place 4 solars around each mex in the area. This protects the extractor and provides [[Overdrive]].

You can use the ALT modifier for adding Solars to existing metal extractors as well.

{{Navbox commands}}

Sling

2017-11-01T09:23:14Z

213.35.139.72: /* Tactics and Strategy */

The '''{{PAGENAME}}''' is a light artillery bot from the [[Cloakbot Factory]].{{ Infobox zkunit
| name = Sling
| defname = cloakarty
| description = Light Artillery Bot
| image = http://manual.zero-k.info/unitpics/cloakarty.png
| icontype = kbotarty
| cost = 130
| hitpoints = 350
| movespeed = 49
| turnrate = 247
| sight = 660
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Light Plasma Cannon
| type = Cannon
| damage = 150
| reloadtime = 6
| dps = 25
| range = 840
| projectilespeed = 260
}}
}}==Description==
The Sling has a long range plasma cannon that allows indirect fire over obstacles, and outranges static defenses up to heavy laser towers. Although effective versus mobile units, it should be guarded in order to prevent raiders and other fast units from closing range.

== Tactics and Strategy ==
Slings are the cheapest artillery in the game. On the one hand, this means you may need lots of them to accomplish the same task as a single [[Impaler]] or [[Penetrator]]. On the other hand, Slings are far better suited to combating light static defences like [[Picket|Pickets]], against which a Penetrator would be overkill. Building a few Slings for this task is often a good idea. Since their projectiles are slow and do not have a significant area of effect, Slings are poor against mobile units except in large-scale engagements. Make sure to protect your Slings against raids since they are flimsy and weak at short range combat.

{{Navbox units}}

Reaver

2017-11-01T09:16:03Z

213.35.139.72:

The '''{{PAGENAME}}''' is a riot bot from the [[Cloakbot Factory]].{{ Infobox zkunit
| name = Reaver
| defname = cloakriot
| description = Riot Bot
| image = http://manual.zero-k.info/unitpics/cloakriot.png
| icontype = kbotriot
| cost = 220
| hitpoints = 820
| movespeed = 51
| turnrate = 297
| sight = 345
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Heavy Pulse MG
| type = Cannon
| damage = 40 × 3
| reloadtime = 0.45
| dps = 267
| range = 270
| aoe = 48
| projectilespeed = 550
}}
| abilities =
{{ Infobox zkability regen
| idleregen = 30
| timetoenable = 5.0
}}
}}==Description==
The Reaver's devastating heavy Energy Machine Gun is effective versus most enemy units, in particular raiders. It performs poorly versus static defense, so do not use it as an assault unit. Counter by staying out of their range, as they are slow. Reavers quickly regenerate damage when out of combat.

== Tactics and Strategy ==
The Reaver is a fearsome combatant at close quarters, but suffers from low range and speed. As such, they are best employed in combination with another unit (like the [[Glaive]] or [[Ronin]]) which can deal with any opposing long-range attackers. Alternatively, an [[Iris]] or multiple [[Charon|Charons]] will let your Reavers close the distance before the opposition can react.

{{Navbox units}}

Reaver

2017-11-01T09:15:34Z

213.35.139.72:

The '''{{PAGENAME}}''' is a riot bot from the [[Cloakbot Factory]].{{ Infobox zkunit
| name = Reaver
| defname = cloakriot
| description = Riot Bot
| image = http://manual.zero-k.info/unitpics/cloakriot.png
| icontype = kbotriot
| cost = 220
| hitpoints = 820
| movespeed = 51
| turnrate = 297
| sight = 345
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Heavy Pulse MG
| type = Cannon
| damage = 40 × 3
| reloadtime = 0.45
| dps = 267
| range = 270
| aoe = 48
| projectilespeed = 550
}}
| abilities =
{{ Infobox zkability regen
| idleregen = 30
| timetoenable = 5.0
}}
}}==Description==
The Reaver's devastating heavy Energy Machine Gun is effective versus most enemy units, in particular raiders. It performs poorly versus static defense, so do not use it as an assault unit. Counter by staying out of their range, as they are slow. Reavers quickly regenerate damage when out of combat.

== Tactics and Strategy ==
The Reaver is a fearsome combatant at close quarters, but suffers from low range and speed. As such, they are best employed in combination with another unit (like the [[Glaive]] or [[Ronin]]) which can deal with any opposing long-range attackers. Alternatively, an [[Iris]] or multiple [[Valkyrie|Valkyries]] will let your Reavers close the distance before the opposition can react.

{{Navbox units}}

Rover Assembly

2017-10-30T11:29:22Z

213.35.139.72: /* Beating Rovers */

The '''{{PAGENAME}}''' is a factory that produces light wheeled vehicles.{{ Infobox zkunit
| name = Rover Assembly
| defname = factoryveh
| description = Produces Light Wheeled Vehicles, Builds at 10 m/s
| image = http://manual.zero-k.info/unitpics/factoryveh.png
| icontype = facvehicle
| cost = 600
| hitpoints = 4000
| energy = 0.3
| sight = 273
| abilities =
{{ Infobox zkability construction
| buildpower = 10
}}
}}==Description==
A traditional favourite, the Rover Assembly is the ideal blitzkrieg fac with its fast, highly aggressive units. Those units that lack speed make up for it with copious firepower. Key Units: Dart, Scorcher, Ravager, Ripper, Slasher

The Rover Assembly builds:
* [[Mason]]
* [[Dart]]
* [[Scorcher]]
* [[Fencer]]
* [[Ripper]]
* [[Ravager]]
* [[Dominatrix]]
* [[Badger]]
* [[Impaler]]
* [[Crasher]]

==Tactics and Strategy==

The Rover Assembly is the most versatile of the flat-terrain factories. The Dart, Scorcher, Ripper and Ravager are fast and effective combat units which excel at rapid response and swift punishment of enemy weakness. When the game has slowed down and mobility is less important, the Ripper, Badger and Impaler punish your opponent from a safe distance.

The greatest weakness of the Rover Assembly is its lacklustre heavy and utility options; all of the main Vehicle combat units are cheap but not exceptionally strong individually, and if a frontal assault with Scorchers won't work the Vehicles don't have another good solution to opposing heavies. If you combine Vehicles with the raw strength of [[Heavy Tank Factory|Heavy Tanks]] or the utility of [[Shield Bot Factory|Shield Bots]], the Vehicle factory's combination of swift attacks and slow attrition will serve you very well.

=== Example Unit Combinations ===

Scout ahead of your Scorchers with the faster and cheaper Darts, so you can commit your Scorchers where they will inflict the most damage.

Escort your Ravagers with Rippers to deal with small and swift opponents. The Ravagers will be more effective against heavier units and static defence.

Protect your long-range units like Fencer, Dominatrix, Badger and Impaler with combat units like the Ripper, static defences, or shields.

Conceal your mobile strike force with an [[Eraser]] so it can attack before your opponent has a chance to react.

Bomb your opponent's critical units or defences with [[Raven|Ravens]], a [[Thunderbird]] or a [[Likho]], then follow up with a Scorcher attack, striking where and when the enemy is weak.

=== Beating Rovers ===

Of all the factories in Zero-K, the Rover Assembly presents the greatest game-ending threat in the early game. Even a small number of Scorchers can kill a Commander or a Factory in an incredibly short time by using their Heat Rays at close range, and they will also make short work of isolated Defenders and Lotuses. Make sure you are protected from Scorchers by defences and your own raiders, while at the same time pressuring the Rover player so they cannot expand unhindered.

If your opponent is building up a large force of Ravagers, you will need to be prepared. They will not be deterred by light static defences, and if you build a denser concentration of defences in one spot the Ravagers will likely attack elsewhere. Raiders are capable of keeping up with Ravagers, but will be ineffective if the Ravagers are escorted by Ripper. Other assault units and some riots will hold their own in combat, but they are generally slower than Ravagers so good radar coverage to predict the Ravagers' attacks is required. Perhaps the best solution is to disable the Ravagers instead of trying to punch through their large HP pool directly; the [[Placeholder]] and [[Thunderbird]] are especially effective.

Over-reliance on static defences will be punished by a Rover player - they can run around (or through!) with Scorchers and Ravagers, or clean up defences swiftly with Impalers and Badgers. The [[Gauss]] turret is more resistant to the Rover artillery while it is closed and can buy you some time, but you will eventually need to fight the Rovers directly with a mobile army. The best way to engage Badgers is by flanking them, so that you don't have to run through their minefield and they cannot retreat effectively. Outranging them with heavier area-denial artillery like a [[Firewalker]], [[Tremor]] or [[Merlin]] is also possible.

{{Navbox buildings}}

Rover Assembly

2017-10-30T11:28:35Z

213.35.139.72: /* Beating Rovers */ apply newspeak

Rover Assembly

2017-10-30T11:26:54Z

213.35.139.72: /* Example Unit Combinations */

The '''{{PAGENAME}}''' is a factory that produces light wheeled vehicles.{{ Infobox zkunit
| name = Rover Assembly
| defname = factoryveh
| description = Produces Light Wheeled Vehicles, Builds at 10 m/s
| image = http://manual.zero-k.info/unitpics/factoryveh.png
| icontype = facvehicle
| cost = 600
| hitpoints = 4000
| energy = 0.3
| sight = 273
| abilities =
{{ Infobox zkability construction
| buildpower = 10
}}
}}==Description==
A traditional favourite, the Rover Assembly is the ideal blitzkrieg fac with its fast, highly aggressive units. Those units that lack speed make up for it with copious firepower. Key Units: Dart, Scorcher, Ravager, Ripper, Slasher

The Rover Assembly builds:
* [[Mason]]
* [[Dart]]
* [[Scorcher]]
* [[Fencer]]
* [[Ripper]]
* [[Ravager]]
* [[Dominatrix]]
* [[Badger]]
* [[Impaler]]
* [[Crasher]]

==Tactics and Strategy==

The Rover Assembly is the most versatile of the flat-terrain factories. The Dart, Scorcher, Ripper and Ravager are fast and effective combat units which excel at rapid response and swift punishment of enemy weakness. When the game has slowed down and mobility is less important, the Ripper, Badger and Impaler punish your opponent from a safe distance.

The greatest weakness of the Rover Assembly is its lacklustre heavy and utility options; all of the main Vehicle combat units are cheap but not exceptionally strong individually, and if a frontal assault with Scorchers won't work the Vehicles don't have another good solution to opposing heavies. If you combine Vehicles with the raw strength of [[Heavy Tank Factory|Heavy Tanks]] or the utility of [[Shield Bot Factory|Shield Bots]], the Vehicle factory's combination of swift attacks and slow attrition will serve you very well.

=== Example Unit Combinations ===

Scout ahead of your Scorchers with the faster and cheaper Darts, so you can commit your Scorchers where they will inflict the most damage.

Escort your Ravagers with Rippers to deal with small and swift opponents. The Ravagers will be more effective against heavier units and static defence.

Protect your long-range units like Fencer, Dominatrix, Badger and Impaler with combat units like the Ripper, static defences, or shields.

Conceal your mobile strike force with an [[Eraser]] so it can attack before your opponent has a chance to react.

Bomb your opponent's critical units or defences with [[Raven|Ravens]], a [[Thunderbird]] or a [[Likho]], then follow up with a Scorcher attack, striking where and when the enemy is weak.

=== Beating Rovers ===

Of all the factories in Zero-K, the Rover Assembly presents the greatest game-ending threat in the early game. Even a small number of Scorchers can kill a Commander or a Factory in an incredibly short time by using their Heat Rays at close range, and they will also make short work of isolated Defenders and Lotuses. Make sure you are protected from Scorchers by defences and your own raiders, while at the same time pressuring the Vehicle player so they cannot expand unhindered.

If your opponent is building up a large force of Ravagers, you will need to be prepared. They will not be deterred by light static defences, and if you build a denser concentration of defences in one spot the Ravagers will likely attack elsewhere. Raiders are capable of keeping up with Ravagers, but will be ineffective if the Ravagers are escorted by Ripper. Other assault units and some riots will hold their own in combat, but they are generally slower than Ravagers so good radar coverage to predict the Ravagers' attacks is required. Perhaps the best solution is to disable the Ravagers instead of trying to punch through their large HP pool directly; the [[Placeholder]] and [[Thunderbird]] are especially effective.

Over-reliance on static defences will be punished by a Rover player - they can run around (or through!) with Scorchers and Ravagers, or clean up defences swiftly with Impalers and Badgers. The [[Gauss]] turret is more resistant to the Vehicle artillery while it is closed and can buy you some time, but you will eventually need to fight the Vehicles directly with a mobile army. The best way to engage Badgers is by flanking them, so that you don't have to run through their minefield and they cannot retreat effectively. Outranging them with heavier area-denial artillery like a [[Firewalker]], [[Tremor]] or [[Catapult]] is also possible.

{{Navbox buildings}}

Cheats

2017-09-14T14:17:20Z

213.35.139.72: /* Commands */

:''See also: [https://springrts.com/wiki/UI_commands UI commands]''
There are several '''cheat''' commands that can be used in the game.

== Cheat mode ==
Before any other cheat command can be used, cheating mode must be enabled. This is done by typing <code>/cheat</code> in console in singleplayer, or <code>!cheats</code> in multiplayer.
* If <code>!cheats</code> fails to work, makesure ally/spectator chat mode is off (remove the <code>a:</code> or <code>s:</code> prefix)

Entering the command again disables cheat mode.

== Commands ==
=== atm ===
Syntax: <code>/atm</code>

Gives 1,000 metal and energy to the entering player's team.

=== give ===
Syntax: <code>/give [optional number] <unitname> [optional team number]</code>

Spawns a given number of units at the location of the mouse cursor. Can also be used to spawn features, e.g. wreckage.

Unit names are the machine-facing identifiers rather than the human names, e.g. <code>cloakraid</code> for the [[Glaive]]. Unit names can be found on [https://github.com/ZeroK-RTS/Zero-K/tree/master/units GitHub] or in the source of the unit's page on the wiki.

If no team is specified, will give to the player's current team, or the team currently being spectated.

=== globallos ===
Syntax: <code>/globallos [optional team number]</code>

Enables/disables full map view for that team (no team specified means it applies to everyone).

=== godmode ===
Syntax: <code>/godmode</code>

When enabled, any player (including spectators) can give commands to units on any team.

=== nocost ===
Syntax: <code>/nocost</code>

Enables/disables building everything for free and near-instantly.

=== destroy ===
Syntax: <code>/destroy</code>

Instantly destroys currently selected units.

{{Navbox manual}}

Cheats

2017-09-14T14:17:00Z

213.35.139.72:

Commander

2017-03-07T11:00:44Z

213.35.139.72: /* Special */ blue -> cyan for less eye destruction

<div style="float:right;">__TOC__</div>
= Warning: portions of this page are out of date =

The commander system was substantially revamped in winter 2016. This page has only partially been updated to the new system.

= Commander intro =
Your commander can be configured with a variety of modules to suit your play-style.

After the update, modules are added only at the game and are all unlocked, and you do not need to level up to get any modules.

To keep the game balanced commander modules cost metal ingame and are not all applied at the start of the game. Commanders start at level 1 with a free peashooter and no modules but they can morph an unlimited number of times (but you'll eventually run out of modules after which it is pointless to morph). At Morph 1 (Level 2), commanders gain a single weapon. At morph 3 commanders gain a second weapon which can either be a second regular weapon or a special weapon. If a weapon slot is left empty the commander will be given a free peashooter in its place. Some weapons will replace any other weapons (e.g I get shock rifle, it will replace the first weapon I got)

Each morph level gives a commander more health, more modules or weapons. Morphs have a base cost and additional cost based on the value of the modules or weapons that it will gain when the morph is complete. You can pre-configure your commander buildouts only through level 6 but you can upgrade any number of times in-game.

Unlike regular units, your commander is not disabled while morphing.

= Modules and weapons =

== Number of slots per level ==

Commanders start at level 1. The number of modules and weapons increases with levels.

{|
! Commander level !! 1 !! 2 !! 3 !! 4 !! 5 !! 6
|-
| Base [[File:Ibeam.png|20px]] cost || -     ||251 || 150 || 500 || 300 || 400
|-
| Total Weapon slots || 0 || 1 || 1 || 2 || 2 || 2
|-
| Total Module slots || 0 || 1 || 3 || 5 || 8 || 11
|-
|}

1 Equipping weapons and modules costs additional metal.

== Module types ==
Modules have cyan names in the unlock list, although their icon color depends on their nature. They fall into four categories.

=== Stackable ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/module_ablative_armor.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/module_autorepair.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/module_high_power_servos.png

These modules are able to stacked as many times as they allow, 8x for some and 10x for drones. Stacking them repeatedly will create a powerful commander, even though their bonuses as quite minor. (10% range/damage/speed for those modules) These are cyan.
This type of module is the one that should be used the most, and because of their versatility, it is useful if you intend on getting commanders which do many things, or a single buff commander that is fast, invisible and deals lots of damage. Some of these modules will subtract speed or HP, and should be used with caution as too much will leave the commander a sitting duck.
Modules:
Advanced targeting system +10% range for all weapons.-2.5% speed.
Damage booster +10% damage for all weapons.
High density plating +1600 HP,-10% speed. Requires Ablative armor plates.
Ablative armor plates +600 HP
Companion drone +Weak attack drone
Battle drone +Upgraded drone, requires Companion drone first.
Carrepairer's nanolathe +5 Buildpower.
High power servos +10% speed.
Autorepair system +10HP/sec -100 HP

=== Support===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/module_fieldradar.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/module_areashield.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/module_jammer.png

Support modules are not stackable. They can provide large expensive bonuses such as a shield, cloaking, jamming or a cloaker. There are also cheap ones such as resurrect and inbuilt radar or an area shield/cloak. These are cyan as well.

=== Weapon Boosters ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/weaponmod_standoff_rocket.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/weaponmod_autoflechette.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/weaponmod_high_frequency_beam.png

These modules are expensive but give a large bonus to a few specific weapons but can only be applied once. They are a space effective way to spend a module slot but make sure you have the weapon that they affect. They are purple.

== Weapon types ==
There are 2 types of weapon, special and normal. Both weapon types are affected by the stackable range and damage modules. Weapon names are in red.

=== Normal ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_beamlaser.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_rocketlauncher.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_gaussrifle.png

These are auto-targetting normal weapons that behave the same was as any other unit. They can be affected by weapon boosters and weapon converters given that it is the right weapon. They are all affected by stackable modules. They are red.

{|
! Name !! Range !! Reload time !! Damage !! DPS !! Notes
|-
|Beam Laser||330||||||150||
|-
|Flame thrower||270||0.16 ||10 || 60|| Sets units on fire for 15s(15 DPS) pierces units Does more damage against larger units
|-
|Heatray||300||0.1 ||45 ||450 || Damage falls off with range
|-
|Machine Gun||285||0.16 ||30 ||180 ||
|-
|Light particle beam||310||0.34 ||55 || 165||
|-
|Lightning gun||300||1.66 ||220+550 || 132+330 || EMP duration: 1s
|-
|Missile launcher||415||1 ||80 || 80|| Homing
|-
|Riot cannon||275||2 ||220.2 || 110.1||
|-
|Shotgun||290||2 ||32x12 (384) || 192||
|-
|Rocket launcher ||430||3 ||360 || 120||Not homing
|-
|Pea Shooter ||300||.1 ||12 || 120||Default weapon
|-
|}

=== Special ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_napalmgrenade.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_disruptorbomb.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_sunburst.png

Special weapons have a long reload time and must be manually aimed with the 'D' key. They are only affected by stackable modules. They are orange and can only be put on the level 4 weapon slot.

{|
! Name !! Range !! Reload time !! Damage !! DPS !! Special Notes
|-
|Cluster bomb ||360 || 30 || 300x8 (2400)|| 80 || Bomblets spread (like a shotgun)
|-
| Concussion shell||450 || 25 ||750 || 30 || Has Impulse (Tosses some units)
|-
| Disintigrator ||200 ||30 ||1400 || 46.67 || Damage varies on unit size
|-
|Disrupter bomb ||450 ||25 ||350+2100 || 14+84 || Has large AOE (512)
|-
| Hellfire grenade||450 || 25||200 || 8 || Sets an area on fire (45s,40dps+3s burning)
|-
| Multistunner||360 || 25||550/800 x 16 (8800/12800) ||352/512 || Affected by flux amplifier. Max EMP time: 8s [upgraded: 12s]
|-
| SLAM||700 ||30 || 1512|| 50.4 || High vertical arc
|-
|}
Key: EMP Damage, Slow Damage

= Commander Chassis =
There are 4 types of commander chassis to choose for a battle.

== Common attributes ==
The commander you start the game with produces 4 metal and 6 energy per second. Additional commanders produced from the Strider Hub produce 0.4 metal and 0.4 energy per second. They all provide a sight distance of 500 and a sonar of 300. Chassis other than the Engineer Commander have 10 build power and 120 build range and the Engineer commander has 12 build power and 250 build range.

== Chassis list ==
Note that '''attributes on level 1 and level 2 are equal'''. Morphing to level 2 provides no bonus other than the weapon and module slot.

=== Strike Commander ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commstrike.png 
* All rounder
* Decent health and speed
* Can use the most weapon types
* Auto-regen bonus

{|
! Base Attributes !! Level 2 !! Level 3 !! Level 4 !! Level 5
|-
|HP: 2500 Speed: 40.5 Autoheal: 5||HP: 3000 Autoheal: 12.5||HP: 4000 Autoheal: 20||HP: 5000 Autoheal: 27.5||HP: 6000 Autoheal: 35
|-
|}

=== Guardian Commander ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commassault.png 
* Best HP
* Medium speed
* Gains more HP from increased levels than other chasis do
* Able to use most non-exotic weapons

{|
! Base Attributes !! Level 2 !! Level 3 !! Level 4 !! Level 5
|-
|HP: 3000 Speed: 40||HP: 3800 ||HP: 4900 ||HP: 6000 ||HP: 7200 
|-
|}

=== Recon Commander ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commrecon.png 
* Lowest HP
* Highest Speed (for a commander)
* Jumpjets
* Uses light weapons

{|
! Base Attributes !! Level 2 !! Level 3 !! Level 4 !! Level 5
|-
|HP: 1600 Speed: 43.5 Can Jump||HP: 2100||HP: 2600||HP: 3100||HP: 3600
|-
|}

=== Engineer Commander ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commsupport.png 
* Lowest speed
* Low HP
* Gains buildpower with levels
* Increased build range (250 compared to 120 for others)
* Fewer direct damage weapons

{|
! Base Attributes !! Level 2 !! Level 3 !! Level 4 !! Level 5
|-
|HP: 2000 Speed: 36 Build Power: 12||HP: 2500 Build Power: 14||HP: 3000 Build Power: 16||HP: 3700 Build Power: 18||HP: 4500 Build Power: 20
|-
|}

= Exact effects of attribute modifiers =
Attribute modifiers are applied in this order:
* Commander Chassis absolute statistics
* Percentage modifiers both from modules and chassis
* Absolute modifiers

Percentage modifiers from commanders and stackable modules are additive, not cumulative. Five +10% speed modules multiply a commander's speed by 1.5 instead of by 1.1^5 = 1.61.

Percentage modifiers from weapon boosters and converters are cumulative and applied before other percentage modifiers. Think of them as changing the intrinsic stats of the weapon, rather than adding a bonus.

{{Navbox manual}}

Template:Navbox units

2016-09-29T14:19:18Z

213.35.139.72: unused factory best factory

{{Navbox
| name = Navbox units
| title = Units
| state = uncollapsed
| listclass = hlist

| group1 = [[Cloaky Bot Factory|Cloaky Bots]]
| list1 = * [[Conjurer]]
* [[Glaive]]
* [[Scythe]]
* [[Rocko]]
* [[Warrior]]
* [[Zeus]]
* [[Hammer]]
* [[Spectre]]
* [[Gremlin]]
* [[Tick]]
* [[Eraser]]

| group2 = [[Shield Bot Factory|Shield Bots]]
| list2 = * [[Convict]]
* [[Dirtbag]]
* [[Bandit]]
* [[Rogue]]
* [[Thug]]
* [[Outlaw]]
* [[Felon]]
* [[Racketeer]]
* [[Vandal]]
* [[Roach]]
* [[Aspis]]

| group3 = [[Light Vehicle Factory|Light Vehicle]]
| list3 = * [[Mason]]
* [[Dart]]
* [[Scorcher]]
* [[Slasher]]
* [[Leveler]]
* [[Ravager]]
* [[Dominatrix]]
* [[Wolverine]]
* [[Impaler]]
* [[Crasher]]

| group4 = [[Hovercraft Platform|Hovercraft]]
| list4 = * [[Quill]]
* [[Dagger]]
* [[Scalpel]]
* [[Halberd]]
* [[Claymore]]
* [[Mace]]
* [[Penetrator]]
* [[Flail]]

| group5 = [[Gunship Plant|Gunships]]
| list5 = * [[Wasp]]
* [[Blastwing]]
* [[Gnat]]
* [[Banshee]]
* [[Rapier]]
* [[Brawler]]
* [[Black Dawn]]
* [[Krow]]
* [[Trident]]
* [[Valkyrie]]
* [[Vindicator]]

| group6 = [[Airplane Plant|Airplanes]]
| list6 = * [[Crane]]
* [[Swift]]
* [[Hawk]]
* [[Raven]]
* [[Phoenix]]
* [[Thunderbird]]
* [[Wyvern]]
* [[Vulture]]

| group7 = [[Spider Factory|Spiders]]
| list7 = * [[Weaver]]
* [[Flea]]
* [[Hermit]]
* [[Vemom]]
* [[Redback]]
* [[Recluse]]
* [[Crabe]]
* [[Tarantula]]
* [[Infiltrator]]

| group8 = [[Jump/Specialist Plant|Jump/Specialist Bots]]
| list8 = * [[Constable]]
* [[Puppy]]
* [[Pyro]]
* [[Placeholder]]
* [[Moderator]]
* [[Jack]]
* [[Sumo]]
* [[Firewalker]]
* [[Archangel]]
* [[Skuttle]]

| group9 = [[Heavy Tank Factory|Heavy Tanks]]
| list9 = * [[Welder]]
* [[Kodachi]]
* [[Panther]]
* [[Banisher]]
* [[Reaper]]
* [[Goliath]]
* [[Pillager]]
* [[Tremor]]
* [[Copperhead]]

| group10 = [[Amphibious Bot Plant|Amphibious Bots]]
| list10 = * [[Conch]]
* [[Duck]]
* [[Archer]]
* [[Buoy]]
* [[Scallop]]
* [[Grizzly]]
* [[Angler]]
* [[Djinn]]

| group11 = [[Shipyard|Ships]]
| list11 = * [[Mariner]]
* [[Skeeter]]
* [[Snake]]
* [[Typhoon]]
* [[Hunter]]
* [[Enforcer]]
* [[Crusader]]
* [[Serpent]]
* [[Shredder]]
* [[Surfboard]]

| group12 = [[Strider Hub|Striders]]
| list12 = * [[Ultimatum]]
* [[Scorpion]]
* [[Dante]]
* [[Catapult]]
* [[Funnelweb]]
* [[Bantha]]
* [[Detriment]]
* [[Leviathan]]
* [[Reef]]
* [[Warlord]]

| group13 = [[Missile Silo|Tactical Missiles]]
| list13 = * [[Eos]]
* [[Quake]]
* [[Shockley]]
* [[Inferno]]

| group14 = [[Other Units]]
| list14 = * [[Commander]]
* [[Athena]]

| group15 = [[Chicken Defense|Chickens]]
| list15 = * [[Chicken]]
* [[Pigeon]]
* [[Spiker]]
* [[Cockatrice]]
* [[Lobber]]
* [[Wurm]]
* [[Roc]]
* [[Sporeshooter]]
* [[Talon]]
* [[Basilisk]]
* [[Spiker]]
* [[Blobber]]
* [[Blimpy]]
* [[Tiamat]]
* [[White Dragon]]
* [[Chicken Flyer Queen|Chicken Queen]] ([[Chicken Land Queen|landed]])
* [[Dodo]]
* [[Toad]]

| group16 = Unused Units
| list16 = * [[Nebula]]
* [[Kestrel]]
* [[Eclipse]]
* [[Trisula]]
* [[Morningstar]]
* [[Lancet]]
* [[Vanquisher]]
* [[Daimyo]]

| below = [[Template:Navbox buildings|Buildings]]

}}

<includeonly>
[[Category:Units]]
</includeonly>