Zero-K - User contributions [en]

Terraform

2021-05-01T21:49:41Z

Legomenon: Prettify terraform hotkeys

All [[Unit_classes#Constructor|construction units]], [[Commander]]s and [[Caretaker]]s can modify the terrain in Zero-K. '''Terraforming''' costs [[Energy]], [[Metal]] and time.

http://licho.eu/alba/terraform/intro.png <div style="float:right;">__TOC__</div>

== Terraform Types ==

There are also 5 terraform commands found under the 'Special' tab in the menu:

* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/ramp.png — Ramp
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/level.png — Level
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/raise.png — Raise
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/smooth.png — Smooth
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/restore.png — Restore

Note: {{Key press|Right Click}} at any time during the terraform will cancel the command.

== Interface: Lasso Selection ==

'''Level''', '''Raise''', '''Smooth''' and '''Restore''' have the same interface for selecting the effected area. They differ in what they do to the terrain.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/level.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/raise.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/smooth.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/restore.png

{{Key press|Left click}} on the ground and hold the mouse to start drawing a line. Drawing the area selects the area to be terraformed. If the end of the line is close to the start when the left mouse button is released the area inside the loop will be terraformed (like lasso selection), if the ends are far away the drawn line will be terraformed (good for making walls).

http://licho.eu/alba/terraform/lasso.jpg

If you are using '''Smooth''' or '''Restore''' the command will be given when you release the mouse. If you are using '''Level''' or '''Raise''' you will have to chose either which height to level to or how much to raise the land. This is done by moving the mouse up/down then clicking when it looks like it is at the desired height.

http://licho.eu/alba/terraform/setheight.jpg

== Effects of Terraform and Modifiers ==

Here are the effects of '''Level''', '''Raise''', '''Smooth''' and '''Restore'''. The modifiers {{Key press|Alt}} and {{Key press|Ctrl}} can be held during the Height Choosing phase of the '''Level''' and '''Raise''' commands for more height choosing control.

=== Level ===

http://licho.eu/alba/terraform/level.sized.jpg

'''Level''' will move the terrain in the area to exactly the same height, the result terrain will be flat. For example a hill could be flattened.

* Hold {{Key press|Alt}} to snap to either the starting height, just below water level (so that ships can't pass) or the level just below water level that land units cannot pass (23 deep).

* Hold {{Key press|Ctrl}} and move the mouse to select the height to be levelled to from terrain by mousing over the terrain.

* Tap {{Key press|Space}} to cycle through only raise or only level. This limits the terraform to either take away or add terrain instead of a mix of both. Can be toggled during Lasso stage.

=== Raise ===

http://licho.eu/alba/terraform/raise.sized.jpg

'''Raise''' raises or lowers the terrain in the area by the same amount, the relative height of the terrain within the area is not changed.

* Hold {{Key press|Alt}} to snap to heights by steps of 15. A 15 high (or deep) wall (or trench) will be impassable to vehicles but passable to bots. A 18 high wall will be impassable to most common bots. A 30 high wall will be impassable to everything except spiders.

* Press {{Key press|Ctrl}} to reset the height to 0.

=== Smooth ===

<img src="http://licho.eu/alba/terraform/smooth1.sized.jpg" width="360"/><img src="http://licho.eu/alba/terraform/smooth2.sized.jpg" width="360"/>

'''Smooth''' smooths the terrain, cliffs become less sharp.

=== Restore ===

<img src="http://licho.eu/alba/terraform/restore1.sized.jpg" width="360"/><img src="http://licho.eu/alba/terraform/restore2.sized.jpg" width="360"/>

'''Restore''' reverts the height of the terrain to what it was at the start of the game.

* Tap {{Key press|Space}} to cycle through only raise or only level. This limits the terraform to either take away or add terrain instead of a mix of both. Toggle during Lasso stage.

== Advanced Area Selection ==

For easier terraforming, {{Key press|Alt}} and/or {{Key press|Ctrl}} can be used to modify the way the lasso command is given.

* Hold {{Key press|Alt}} while clicking to terraform a rectangular area.

http://licho.eu/alba/terraform/square.jpg

* Hold {{Key press|Alt}} and click on a building or unit to create a wall around that unit.

http://licho.eu/alba/terraform/autowall.sized.jpg

* Hold {{Key press|Alt}} + {{Key press|Ctrl}} while clicking to create a hollow rectangle of terraform.

http://licho.eu/alba/terraform/ring.sized.jpg

* Hold {{Key press|Ctrl}} at any time during line drawing to create a straight section of line. Straight and non-straight lines can be mixed by pressing and releasing {{Key press|Ctrl}}.

http://licho.eu/alba/terraform/loopy.sized.jpg

== Terraforming Under Buildings In One Click ==

The default option of terraforming the ground under buildings is to press the {{Key press|B}} key after choosing the structure, changing the height of the project with {{Key press|C}} and {{Key press|V}} afterwards. By far the simplest way to use this kind of terraforming is to press {{Key press|Alt}} key while placing a structure and adjust the height of the structure by scrolling with the mouse wheel, but this option should first be enabled in the settings.

[[File:terraform_structure.gif]]

Structure terrforming controls can be changed in the menu: <code>Settings > Interface > Building placement</code>. Tick the <code>Alt mouse wheel to set height</code> to enable the easier construction option.

See [[Structure Placement]] for more information on structure terraforming.

== Terraforming Presets ==

There are terraforming presets that allow to create terraforming with a specific height and can be configured under Hotkeys/Construction. Default hokeys include:
* {{Key press|Alt}} + {{Key press|V}}: Make the smallest wall that is not Vehicle pathable.
* {{Key press|Alt}} + {{Key press|B}}: Make the smallest wall that is not Bot pathable.
* {{Key press|Alt}} + {{Key press|N}}: Make a wall that will block direct fire weapons like lasers. This allows indirect fire units like [[Rogue]] or [[Recluse]] to shoot at a [[Stinger]] with impunity,
* {{Key press|Alt}} + {{Key press|H}}: Make a tall spire to give high ground advantage for units like [[Crab]].

== Ramp ==

The ramp command interface is different from that of the other terraform commands.

First select the '''Ramp''' command from the command menu.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/ramp.png

=== Simple Ramp ===
This is a simple way to make a ramp between 2 points on the ground. It uses exactly the same interface as advanced ramp but it can be unclear how to make a simple ramp just from the explanation of the full features of advanced ramp.

In short:
* {{Key press|Left Click}} the start of the ramp
* {{Key press|Left Click}} the end of the ramp
* {{Key press|Left Click}} again

==== Advanced Ramp ====
Using the full ramp interface you can make a ramp between any 2 arbitrary points above or below the terrain and chose the width of this ramp.

{{Key press|Left Click}} on the ground to set the start of the ramp. '''If''' you want to choose the height of the start of the ramp hold the click and move the mouse up or down. A little green line will appear out of the ground to indicate the height. The default height is the ground height, release the mouse to select the height.

* Hold {{Key press|Alt}} when choosing the start height to snap to the original ground height or just below water level(helpful for getting hovers out of the water).

<img src="http://licho.eu/alba/terraform/ramp1.sized.jpg" width="480"/>

* {{Key press|Left Click}} on the ground to set the end of the ramp. As with the start of the ramp, you can hold the mouse and move to choose the height.

* Hold {{Key press|Alt}} when choosing the end height to snap the gradient of the ramp to either upwards bot pathable, upwards vehicle pathable, flat, downwards vehicle pathable, downwards bot pathable, the original ground height or just below water level.

<img src="http://licho.eu/alba/terraform/ramp2.sized.jpg" width="480"/>

* Move the mouse up/down (not held down) and click to set the width of the ramp. Then {{Key press|Left Click}} to build it.

<img src="http://licho.eu/alba/terraform/ramp3.sized.jpg" width="480"/>

The ramp colour indicates whether all units will be able to use it, if vehicles/tanks will not be able to use it and if only spiders can use it.

<img src="http://licho.eu/alba/terraform/ramp_green.jpg" width="240"/><img src="http://licho.eu/alba/terraform/ramp_yellow.jpg" width="240"/><img src="http://licho.eu/alba/terraform/ramp_red.jpg" width="240"/>

Optional: Tap {{Key press|Space}} to cycle through only raise or only level. This limits the terraform to either take away or add terrain instead of a mix of both. Can be toggled at any stage during the ramp command.

== Cost ==

Terraform by default costs 1 metal, energy and build power to raise or lower 1 heightmap grid, each vertex of the blue grid maps onto a point on the heightmap grid. Due to the sloped sides it will be costly to make a very high spire. Equal volumes of terraform will have the same cost regardless of shape. Cost can be changed with the "terraform cost multiplier" [[Setting_Up_a_Game#Advanced_Options|ModOption]].

As a general guideline, assuming the base value for terraforming cost, creating a 15 deep wall (or trench) will cost roughly 19 resources per 'segment'.

Building a "skydust" (i.e. [[Stardust]] on a pillar) costs about 50 resources for a 50 height pillar, or 85 resources for 100 height.

== Terraform blocking ==

By placing troops or structures near the terraforming projects of your opponent you can deny their construction indefinitely. Use this to stop the enemy from building mountain ranges in your backyard or to defend your own creations from being deconstructed by enemy builders.

[[Image:Tera_block.png]]

== Tips ==

You can protect non-combat structures not sensitive to terrain such as [[Cornea|cloak]]/[[Aegis|shield generators]], [[Caretaker|nanoturrets]], [[Gunship Plant]]s and [[Missile Silo]]s with walls or holes.

Buildings cannot be moved vertically once placed. If you want to put a [[Fusion Reactor|Fusion]] in a hole for safety the hole will have to be built before the Fusion.

[[Big Bertha]]s, [[Crab]]s and [[Ogre]]s are very good at knocking down walls. [[Quake]] missiles are the ultimate solution against landscape designers.

http://licho.eu/alba/terraform/crabesmooth.sized.jpg

You can use terraforming to make a trench or wall underwater to stop amphibious bots.

[[Lobster|Lobsters]] can throw units over low walls.

Terraform ramp can be used with [[Newton]]s [[Newton_Firezones|to fire units at the enemy]]!

http://licho.eu/alba/terraform/newtonramp.sized.jpg

To set hotkeys for terraform commands, navigate into the game menu and look under hotkeys for <code>Levelground</code>, <code>Raiseground</code>, <code>Rampground</code>, <code>Smoothground</code> and <code>Restoreground</code>.

{{Navbox manual}}

Terraform

2021-05-01T21:48:15Z

Legomenon: Mention some terraform presets

All [[Unit_classes#Constructor|construction units]], [[Commander]]s and [[Caretaker]]s can modify the terrain in Zero-K. '''Terraforming''' costs [[Energy]], [[Metal]] and time.

http://licho.eu/alba/terraform/intro.png <div style="float:right;">__TOC__</div>

== Terraform Types ==

There are also 5 terraform commands found under the 'Special' tab in the menu:

* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/ramp.png — Ramp
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/level.png — Level
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/raise.png — Raise
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/smooth.png — Smooth
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/restore.png — Restore

Note: {{Key press|Right Click}} at any time during the terraform will cancel the command.

== Interface: Lasso Selection ==

'''Level''', '''Raise''', '''Smooth''' and '''Restore''' have the same interface for selecting the effected area. They differ in what they do to the terrain.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/level.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/raise.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/smooth.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/restore.png

{{Key press|Left click}} on the ground and hold the mouse to start drawing a line. Drawing the area selects the area to be terraformed. If the end of the line is close to the start when the left mouse button is released the area inside the loop will be terraformed (like lasso selection), if the ends are far away the drawn line will be terraformed (good for making walls).

http://licho.eu/alba/terraform/lasso.jpg

If you are using '''Smooth''' or '''Restore''' the command will be given when you release the mouse. If you are using '''Level''' or '''Raise''' you will have to chose either which height to level to or how much to raise the land. This is done by moving the mouse up/down then clicking when it looks like it is at the desired height.

http://licho.eu/alba/terraform/setheight.jpg

== Effects of Terraform and Modifiers ==

Here are the effects of '''Level''', '''Raise''', '''Smooth''' and '''Restore'''. The modifiers {{Key press|Alt}} and {{Key press|Ctrl}} can be held during the Height Choosing phase of the '''Level''' and '''Raise''' commands for more height choosing control.

=== Level ===

http://licho.eu/alba/terraform/level.sized.jpg

'''Level''' will move the terrain in the area to exactly the same height, the result terrain will be flat. For example a hill could be flattened.

* Hold {{Key press|Alt}} to snap to either the starting height, just below water level (so that ships can't pass) or the level just below water level that land units cannot pass (23 deep).

* Hold {{Key press|Ctrl}} and move the mouse to select the height to be levelled to from terrain by mousing over the terrain.

* Tap {{Key press|Space}} to cycle through only raise or only level. This limits the terraform to either take away or add terrain instead of a mix of both. Can be toggled during Lasso stage.

=== Raise ===

http://licho.eu/alba/terraform/raise.sized.jpg

'''Raise''' raises or lowers the terrain in the area by the same amount, the relative height of the terrain within the area is not changed.

* Hold {{Key press|Alt}} to snap to heights by steps of 15. A 15 high (or deep) wall (or trench) will be impassable to vehicles but passable to bots. A 18 high wall will be impassable to most common bots. A 30 high wall will be impassable to everything except spiders.

* Press {{Key press|Ctrl}} to reset the height to 0.

=== Smooth ===

<img src="http://licho.eu/alba/terraform/smooth1.sized.jpg" width="360"/><img src="http://licho.eu/alba/terraform/smooth2.sized.jpg" width="360"/>

'''Smooth''' smooths the terrain, cliffs become less sharp.

=== Restore ===

<img src="http://licho.eu/alba/terraform/restore1.sized.jpg" width="360"/><img src="http://licho.eu/alba/terraform/restore2.sized.jpg" width="360"/>

'''Restore''' reverts the height of the terrain to what it was at the start of the game.

* Tap {{Key press|Space}} to cycle through only raise or only level. This limits the terraform to either take away or add terrain instead of a mix of both. Toggle during Lasso stage.

== Advanced Area Selection ==

For easier terraforming, {{Key press|Alt}} and/or {{Key press|Ctrl}} can be used to modify the way the lasso command is given.

* Hold {{Key press|Alt}} while clicking to terraform a rectangular area.

http://licho.eu/alba/terraform/square.jpg

* Hold {{Key press|Alt}} and click on a building or unit to create a wall around that unit.

http://licho.eu/alba/terraform/autowall.sized.jpg

* Hold {{Key press|Alt}} + {{Key press|Ctrl}} while clicking to create a hollow rectangle of terraform.

http://licho.eu/alba/terraform/ring.sized.jpg

* Hold {{Key press|Ctrl}} at any time during line drawing to create a straight section of line. Straight and non-straight lines can be mixed by pressing and releasing {{Key press|Ctrl}}.

http://licho.eu/alba/terraform/loopy.sized.jpg

== Terraforming Under Buildings In One Click ==

The default option of terraforming the ground under buildings is to press the {{Key press|B}} key after choosing the structure, changing the height of the project with {{Key press|C}} and {{Key press|V}} afterwards. By far the simplest way to use this kind of terraforming is to press {{Key press|Alt}} key while placing a structure and adjust the height of the structure by scrolling with the mouse wheel, but this option should first be enabled in the settings.

[[File:terraform_structure.gif]]

Structure terrforming controls can be changed in the menu: <code>Settings > Interface > Building placement</code>. Tick the <code>Alt mouse wheel to set height</code> to enable the easier construction option.

See [[Structure Placement]] for more information on structure terraforming.

== Terraforming Presets ==

There are terraforming presets that allow to create terraforming with a specific height and can be configured under Hotkeys/Construction. Default hokeys include:
* Alt+V: Make the smallest wall that is not Vehicle pathable.
* Alt+B: Make the smallest wall that is not Bot pathable.
* Alt+N: Make a wall that will block direct fire weapons like lasers. This allows indirect fire units like [[Rogue]] or [[Recluse]] to shoot at a [[Stinger]] with impunity,
* Alt+H: Make a tall spire to give high ground advantage for units like [[Crab]].

== Ramp ==

The ramp command interface is different from that of the other terraform commands.

First select the '''Ramp''' command from the command menu.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/ramp.png

=== Simple Ramp ===
This is a simple way to make a ramp between 2 points on the ground. It uses exactly the same interface as advanced ramp but it can be unclear how to make a simple ramp just from the explanation of the full features of advanced ramp.

In short:
* {{Key press|Left Click}} the start of the ramp
* {{Key press|Left Click}} the end of the ramp
* {{Key press|Left Click}} again

==== Advanced Ramp ====
Using the full ramp interface you can make a ramp between any 2 arbitrary points above or below the terrain and chose the width of this ramp.

{{Key press|Left Click}} on the ground to set the start of the ramp. '''If''' you want to choose the height of the start of the ramp hold the click and move the mouse up or down. A little green line will appear out of the ground to indicate the height. The default height is the ground height, release the mouse to select the height.

* Hold {{Key press|Alt}} when choosing the start height to snap to the original ground height or just below water level(helpful for getting hovers out of the water).

<img src="http://licho.eu/alba/terraform/ramp1.sized.jpg" width="480"/>

* {{Key press|Left Click}} on the ground to set the end of the ramp. As with the start of the ramp, you can hold the mouse and move to choose the height.

* Hold {{Key press|Alt}} when choosing the end height to snap the gradient of the ramp to either upwards bot pathable, upwards vehicle pathable, flat, downwards vehicle pathable, downwards bot pathable, the original ground height or just below water level.

<img src="http://licho.eu/alba/terraform/ramp2.sized.jpg" width="480"/>

* Move the mouse up/down (not held down) and click to set the width of the ramp. Then {{Key press|Left Click}} to build it.

<img src="http://licho.eu/alba/terraform/ramp3.sized.jpg" width="480"/>

The ramp colour indicates whether all units will be able to use it, if vehicles/tanks will not be able to use it and if only spiders can use it.

<img src="http://licho.eu/alba/terraform/ramp_green.jpg" width="240"/><img src="http://licho.eu/alba/terraform/ramp_yellow.jpg" width="240"/><img src="http://licho.eu/alba/terraform/ramp_red.jpg" width="240"/>

Optional: Tap {{Key press|Space}} to cycle through only raise or only level. This limits the terraform to either take away or add terrain instead of a mix of both. Can be toggled at any stage during the ramp command.

== Cost ==

Terraform by default costs 1 metal, energy and build power to raise or lower 1 heightmap grid, each vertex of the blue grid maps onto a point on the heightmap grid. Due to the sloped sides it will be costly to make a very high spire. Equal volumes of terraform will have the same cost regardless of shape. Cost can be changed with the "terraform cost multiplier" [[Setting_Up_a_Game#Advanced_Options|ModOption]].

As a general guideline, assuming the base value for terraforming cost, creating a 15 deep wall (or trench) will cost roughly 19 resources per 'segment'.

Building a "skydust" (i.e. [[Stardust]] on a pillar) costs about 50 resources for a 50 height pillar, or 85 resources for 100 height.

== Terraform blocking ==

By placing troops or structures near the terraforming projects of your opponent you can deny their construction indefinitely. Use this to stop the enemy from building mountain ranges in your backyard or to defend your own creations from being deconstructed by enemy builders.

[[Image:Tera_block.png]]

== Tips ==

You can protect non-combat structures not sensitive to terrain such as [[Cornea|cloak]]/[[Aegis|shield generators]], [[Caretaker|nanoturrets]], [[Gunship Plant]]s and [[Missile Silo]]s with walls or holes.

Buildings cannot be moved vertically once placed. If you want to put a [[Fusion Reactor|Fusion]] in a hole for safety the hole will have to be built before the Fusion.

[[Big Bertha]]s, [[Crab]]s and [[Ogre]]s are very good at knocking down walls. [[Quake]] missiles are the ultimate solution against landscape designers.

http://licho.eu/alba/terraform/crabesmooth.sized.jpg

You can use terraforming to make a trench or wall underwater to stop amphibious bots.

[[Lobster|Lobsters]] can throw units over low walls.

Terraform ramp can be used with [[Newton]]s [[Newton_Firezones|to fire units at the enemy]]!

http://licho.eu/alba/terraform/newtonramp.sized.jpg

To set hotkeys for terraform commands, navigate into the game menu and look under hotkeys for <code>Levelground</code>, <code>Raiseground</code>, <code>Rampground</code>, <code>Smoothground</code> and <code>Restoreground</code>.

{{Navbox manual}}

Repair

2021-04-17T18:48:06Z

Legomenon: Spacing tweak

== Repair basics ==
All Zero-K units can regain lost health through repair. The main method of repair is active repair using constructors, but some units also feature passive repair that happens automatically under certain conditions.

=== Constructor repair ===

All constructor units can use buildpower to repair damaged units, gradually restoring their health. This costs energy only and is both faster and cheaper than building an identical unit from scratch. Every unit can be actively repaired by constructors. Air units can also land on [[Airpad|air repair pads]] to get repaired. Taking damage slows down active repair. The time to fully repair a unit is proportional to its cost. The default hotkey for the repair order is R; it will also be given automatically upon right-clicking a damaged unit if a constructor is selected or if a Patrolling constructor is nearby. With an air unit selected, right-clicking an airpad will order it to land there, aircraft have a "Land At" state to do that automatically and bombers automatically return for repairs after each run.

=== Passive repair ===

Units can also regain health by themselves without the need for a constructor, but this ability is generally limited. All units will automatically start slowly regenerating health after one minute of not taking damage. Some units: [[Glaive]], [[Locust]], [[Scythe]] and [[Kodachi]] have a more potent version of this idle regeneration, which starts after just a few seconds and is more intensive. [[Amphbot Factory|Amphibious Bots]] will regenerate health when in water. The [[Gauss]] turret will regenerate when closed. Finally, some Striders have constant regeneration that happens all the time, even under fire. EMPing or disarming a unit will disable its passive repair.

== Advanced mechanics ==

=== Active repair ===

* Total cost of full repair is 66% the original energy cost; it does not use metal
* Repair takes only 66% of the time compared to construction
* Energy drain per second is equal to buildpower, except with the combat penalty in which case it is 25% of buildpower
* Health regained per buildpower is proportional to the unit's health/cost
* Units that have taken damage in the last 10 seconds are repaired at 25% of the normal repair speed (i.e. is 3 times slower than construction).
* The in-combat penalty matters for the unit being repaired only; constructors' in-combat status is irrelevant
* Status effects such as slow, disarm or EMP do not affect active repair in any way other than the buildpower reduction
* Constructors cannot repair themselves, but can repair each other.

=== Airpad repair ===

* Units can have multiple pads; each pad can service one aircraft.
* Pads have separate buildpower. Adding more aircraft does not slow down existing repair jobs.
* Airpads also rearm bombers. Rearm takes 5-30 seconds (depending on aircraft type) and during that time, a bomber will not be repaired by the pad.
* Air units have a "Land At" unit state to control when they want to land. Bombers will land automatically when needing rearm.
* All traits of constructor repair are also present.
* Drones cannot land on airpads.

=== Idle regeneration ===
Idle regeneration occurs after a unit hasn't taken damage for a certain amount of time.

* Default idle regeneration is 5 HP/s, and starts 60s after taking damage. This applies to units not found in the list below.
* EMP, Disarm and Slow status effects do not affect the timer other than when receiving the damage.
* Combat regeneration replaces idle regeneration (these units won't regenerate even faster when idle).

=== Amphibious regeneration ===

* Full regeneration rate is achieved linearly at some depth.
* Is based on the seabed depth below the unit, not the unit's depth, meaning floaters regenerate fully as if they were underwater.
* Works in acid, though doesn't stop acid damage (the effects work against each other).

=== Armored regeneration ===

* Present while the unit is in the armored state.
* Present only on Gauss at 10 HP/s.

= Lists of units with passive regeneration =

=== Idle regeneration ===
{|
!Name!!Regen [HP/s]!!Timer [s]
|-
||[[Glaive]]||20||5
|-
||[[Locust]]||5||5
|-
||[[Kodachi]]||5||10
|-
||[[Reaver]]||20||5
|-
||[[Scythe]]||10||10
|-
||[[Claw]]||10||10
|-
||[[Chicken]]s||20||10
|-
||Everything else||5||60
|}

=== Combat regeneration ===
{|
!Name!!Regen [HP/s]
|-
|[[Ultimatum]]||5
|-
|[[Athena]]||20
|-
|[[Detriment]]||30
|-
|[[Commander|Strike Commander level 1 Strike Commander level 2 Other Commanders]]||5
|-
|[[Commander|Strike Commander level 3]]||12.5
|-
|[[Commander|Strike Commander level 4]]||20
|-
|[[Commander|Strike Commander level 5]]||27.5
|-
|[[Commander|Strike Commander level 6+]]||35
|-
|Comm Autorepair Module||+10 each
|-
|}

=== Amphibious regeneration ===
{|
!Name!!Regen [HP/s]!!Depth
|-
|[[Conch]]||10||40
|-
|[[Duck]]||5||40
|-
|[[Archer]]||15||40
|-
|[[Bulkhead]]||15||30
|-
|[[Buoy]]||60||30
|-
|[[Scallop]]||10||40
|-
|[[Grizzly]]||40||40
|-
|[[Angler]]||20||40
|-
|[[Limpet]]||10||30
|-
|[[Lobster]]||10||40
|-
|[[Djinn]]||30||40
|-
|}

{{Navbox manual}}

Repair

2021-04-17T18:47:27Z

Legomenon:

Repair

2021-04-17T18:46:56Z

Legomenon: Add missing amph units regeneration

Capture

2021-04-14T22:48:38Z

Legomenon: Update Dominatrix capture recharge time

The [[Dominatrix]] is a unit in the Rover 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 last five seconds. 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 12 seconds before it is able to fire again. 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 other 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}}

LLT

2021-04-05T03:29:19Z

Legomenon: Add LLT -> Lotus redirect

#REDIRECT [[Lotus]]

Bulkhead

2021-03-30T02:26:23Z

Legomenon: Fix typo in Bulkhead edit

The '''{{PAGENAME}}''' is a deployable plasma projectile amphbot from the [[Amphbot Factory]], effective against slow-moving and static units. It must stop to fire.{{ Infobox zkunit
| name = Bulkhead
| defname = amphsupport
| description = Deployable Amphibious Fire Support (must stop to fire)
| image = http://manual.zero-k.info/unitpics/amphsupport.png
| icontype = amphsupport
| cost = 230
| hitpoints = 1700
| movespeed = 48
| turnrate = 181
| sight = 660
| sonar = 660
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Plasma Cannon
| type = Cannon
| damage = 165
| reloadtime = 1.90
| dps = 87
| range = 600
| aoe = 20
| projectilespeed = 320
}}
| abilities =
{{ Infobox zkability regen
| waterregen = 15
| atdepth = 30
}}
}}==Description==
The Bulkhead is a heavily armored dual plasma cannon balanced atop a cheap set of legs. While this gives it an impressive combination of health and range, it is unable to aim or fire its cannons without first stopping to brace itself. This drawback is less pronounced in the water, where it can float to fire then sink to reposition.

=Tactics And Strategy=
The Bulkhead allows for easier disposal of static defenses, and just 3 of them can even topple a [[Stinger]]. In combination with [[Limpet]]s, Bulkheads can target faster units, such as raiders.
{{Navbox units}}

Bulkhead

2021-03-30T02:25:32Z

Legomenon: Add Bulkhead regeneration box

The '''{{PAGENAME}}''' is a deployable plasma projectile amphbot from the [[Amphbot Factory]], effective against slow-moving and static units. It must stop to fire.{{ Infobox zkunit
| name = Bulkhead
| defname = amphsupport
| description = Deployable Amphibious Fire Support (must stop to fire)
| image = http://manual.zero-k.info/unitpics/amphsupport.png
| icontype = amphsupport
| cost = 230
| hitpoints = 1700
| movespeed = 48
| turnrate = 181
| sight = 660
| sonar = 660
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Plasma Cannon
| type = Cannon
| damage = 165
| reloadtime = 1.90
| dps = 87
| range = 600
| aoe = 20
| projectilespeed = 320
}}
| abilities =
{{ Infobox zkability regen
| waterregen = 15
| atdepth = 30
}}
}}
}}==Description==
The Bulkhead is a heavily armored dual plasma cannon balanced atop a cheap set of legs. While this gives it an impressive combination of health and range, it is unable to aim or fire its cannons without first stopping to brace itself. This drawback is less pronounced in the water, where it can float to fire then sink to reposition.

=Tactics And Strategy=
The Bulkhead allows for easier disposal of static defenses, and just 3 of them can even topple a [[Stinger]]. In combination with [[Limpet]]s, Bulkheads can target faster units, such as raiders.
{{Navbox units}}

Weapons

2021-03-22T02:01:22Z

Legomenon: Minor typo fixes

This is a list of some of the commonly found '''weapons''' in Zero-K and their unique characteristics.<div style="float:right;">__TOC__</div>

==Overview==

{| class="wikitable sortable"
! Name !! Range Type !! Notes
|-
| Plasma Cannons || Ballistic || -
|-
| EMG || Ballistic || High damage, short range
|-
| Lasers || Spherical || Instant hit, straight line
|-
| Missiles || Cylindrical || Tracking
|-
| Rockets || Cylindrical || Doesn't track
|-
| Gauss || Ballistic || Penetrates
|-
| Heatray || Spherical || Damage falls off with range
|-
| Fire || Cylindrical || Penetrates, puts units on fire
|-
| EMP || || No damage, temporarily disables unit
|-
| Lightning || Spherical || Inaccurate, temporarily disables unit
|-
| Slow || || Temporarily slows units
|}

==Plasma Cannons==
Plasma shells are a standard weapon for many units. Plasma Cannons are mostly fairly accurate with the exception of high trajectory plasma artillery. Plasma shells move relatively slowly and are affected by gravity which gives them a ballistic trajectory significantly increasing their range downhill while decreasing range uphill. The trajectory also means they can often shoot over friendly units. Their slow projectile speed means most plasma weapons are good against large, slow-moving, or stationary targets, but generally are not as good against fast moving targets or airborne units.

[[File:Weapon cannon.jpg]]

==EMG==
EMG's are fast rapid firing weapons that shoot numerous small plasma bullets. They are effective against any land targets and also against air targets that get in range. They have high damage output but short range. They have a ballistic trajectory like the plasma cannon that makes them signifincantly better at fighting downhill. Additionally, bullets from "Heavy EMG"s burst on impact, doing damage in an area of effect.

[[File:Weapon EMG.jpg]]

==Lasers==
Laser are accurate weapons that require a direct path between the weapon and target. They have no area of effect with the exception of the Starlight superweapon. Laser thickness is a good indicator of how much damage it does. They have spherical range and thus have their maximum 2D range against units at the same height as them. Lasers instantly hit which makes the constant fire lasers good against fast ground units and air, burst fire lasers can still hit fast units but are not good against them. If the target of a burst laser dies the laser can continue on and deal the remaining damage to units behind the target.

[[File:Weapon laser.jpg]]

==Missiles==
Missiles are projectiles that track their targets. Missiles have yellow exhaust and white smoke. All missiles will attack air, and most missiles will attack ground, except the missiles of dedicated anti-air units (which have blue exhaust). Missile range is not affected by terrain giving them a cylindrical target shape. This is useful as with a large enough height difference missiles will outrange lasers that they would not normally outrange.

[[File:Weapon missile.jpg]]

==Rockets==
Rockets are projectiles that do not track, but continue along their trajectory until impact. Rockets have red exhaust and black smoke. Rocket range, like missile, is not affected by terrain. Some rockets require a direct line to fire which makes them more likely to hit enemies other than their target if they miss. Other rockets have an arcing trajectory that makes them very good at shooting over allies so they can be quite powerful in groups. Rockets are slow so almost never hit air and are poor at hitting fast units.

[[File:Weapon rocket.jpg]]

==Gauss==
Like fire, gauss is also a penetrating weapon that moves through units. Unlike disintegrators and flamethrowers, gauss weapons do not deal more then their listed damage to a single unit despite being penetrating like disintegrators and flamethrowers. It is ballistic like a plasma cannon which increases its range downhill. The faster projectile makes it able to often hit air and fast units, though it can miss.

[[File:Weapon gauss.jpg]]

==Heatray==
Heatrays, similar to lasers, require a direct path of fire between the weapon and target. Unlike lasers, the damage falls off with range, so the more distant the target the less damage is done. Close the distance to your target for more damage. Like lasers, they have spherical range.

[[File:Weapon heatray.jpg]]

==[[Fire]]==
[[Fire]] is a penetrating weapon with cylindrical range. It will do damage to all units in its firing line. Units hit by [[fire]] weapons also catch on [[fire]] and will continue to take damage for some time. This is useful for disabling cloak and repair. It can hit fast units and aircraft.

[[File:Weapon fire.jpg]]

==EMP==
Unlike most other weapons, EMP does not directly damage the enemy. Instead it fills up a separate EMP bar on the enemy. The size of a unit's "EMP health" is its ''current'' health so damaged units are easier to EMP. When 100% EMP damage is reached (EMP damage exceeds current health) a unit is completely disabled and cannot move or return fire. Damage above 100% increases EMP time by 1 second per 2.5% up to a maximum EMP time that is different for each weapon. EMP heals automatically and a unit will be re-enabled once the EMP bar drops below 100% again. Against shields EMP will deal 1/3 of its damage. EMP is yellow, or in the case of the self-destructing [[Imp]], blue.

'''Disarm''' is a particular type of EMP that will leave the afflicted units able to move, but unable to use any weapons or special abilities (this includes jumping, using build power, regeneration or receiving income from the commander's Vanguard economy module). Disarmed units flash yellow instead of blue. '''Disarm''' has a separate bar.

[[File:Weapon EMP.jpg]]

==Lightning==
Lightning is direct-fire and carries EMP stun along with its damage. It has spherical range. Lightning weapons usually disable their targets before killing them, allowing them to be finished off with no fear of retaliation. Lightning is always blue. Lighting is somewhat inaccurate but should reliably hit any large unit.

[[File:Weapon lightning.jpg]]

==Slow==
Slow damage, similar to EMP, does not reduce enemy hitpoints. Instead it gradually decreases the move speed and rate of fire of enemy units. Like EMP the slow health of a unit is the current health of the unit. The reduction is the slow damage taken divided by the max health of the unit. Slow damage maxes out at 50% and cannot be increased past that point. Like EMP damage, slow damage also deals 1/3 of its damage against shields and automatically heals by 4% of the unit's current health per second once it has stopped taking further slow damage. Weapons with slow ability are purple.

Many slowing weapons are actually ''disruptors'', represented as purple projectiles or beams with a white core. These do both normal and slow damage.

[[File: Weapon slow.jpg]]

==Conclusion==
While this guide covers many of the more common types of weapons, there is still a wide variety of interesting devices at your disposal. The best way to learn them all is to have fun experimenting with them!

{{Navbox manual}}

Claw

2021-03-18T04:16:13Z

Legomenon: Update Claw damage after Badger nerf

The '''{{PAGENAME}}''' is a mine placed by the [[Badger]].{{ Infobox zkunit
| name = Claw
| defname = wolverine_mine
| description = Badger Mine
| image = http://manual.zero-k.info/unitpics/wolverine_mine.png
| icontype = mine
| cost = 5
| hitpoints = 40
| sight = 64
| weapons =
{{ Infobox zkweapon
| name = Bomblet
| type = MissileLauncher
| damage = 34.01 × 5
| reloadtime = 20
| dps = 8.5
| range = 115
| homing = 198
| projectilespeed = 300
}}
| abilities =
{{ Infobox zkability cloak
| customdata1 = Only when idle
| customdata2 = Free and automated
| decloakradius = 50
}}
{{ Infobox zkability regen
| idleregen = 10
| timetoenable = 10.0
}}
{{ Infobox zkability line
| customdata1 = Invisible to radar
| customdata2 = Instant self-destruction
}}
}}==Description==
This mine doesn't explode - instead, it releases a flurry of bomblets at trespassing enemies. It deactivates after one minute.

{{Navbox buildings}}

Advanced Radar

2021-03-10T20:08:29Z

Legomenon: v1.9.3.0 Advanced Radar changes

The '''{{PAGENAME}}''' is a long-range radar.{{ Infobox zkunit
| name = Advanced Radar
| defname = staticheavyradar
| description = Long-Range Radar
| image = http://manual.zero-k.info/unitpics/staticheavyradar.png
| icontype = advradar
| cost = 400
| hitpoints = 330
| energy = -3
| sight = 1100
| abilities =
{{ Infobox zkability intel
| radar = 5600
}}
}}==Description==
The advanced Radar Tower has a considerably greater range than the basic version.

{{Navbox buildings}}

Terraform

2021-02-27T22:53:16Z

Legomenon: Fix typo

All [[Unit_classes#Constructor|construction units]], [[Commander]]s and [[Caretaker]]s can modify the terrain in Zero-K. '''Terraforming''' costs [[Energy]], [[Metal]] and time.

http://licho.eu/alba/terraform/intro.png <div style="float:right;">__TOC__</div>

== Terraform Types ==

There are also 5 terraform commands found under the 'Special' tab in the menu:

* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/ramp.png — Ramp
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/level.png — Level
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/raise.png — Raise
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/smooth.png — Smooth
* https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/restore.png — Restore

Note: {{Key press|Right Click}} at any time during the terraform will cancel the command.

== Interface: Lasso Selection ==

'''Level''', '''Raise''', '''Smooth''' and '''Restore''' have the same interface for selecting the effected area. They differ in what they do to the terrain.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/level.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/raise.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/smooth.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/restore.png

{{Key press|Left click}} on the ground and hold the mouse to start drawing a line. Drawing the area selects the area to be terraformed. If the end of the line is close to the start when the left mouse button is released the area inside the loop will be terraformed (like lasso selection), if the ends are far away the drawn line will be terraformed (good for making walls).

http://licho.eu/alba/terraform/lasso.jpg

If you are using '''Smooth''' or '''Restore''' the command will be given when you release the mouse. If you are using '''Level''' or '''Raise''' you will have to chose either which height to level to or how much to raise the land. This is done by moving the mouse up/down then clicking when it looks like it is at the desired height.

http://licho.eu/alba/terraform/setheight.jpg

== Effects of Terraform and Modifiers ==

Here are the effects of '''Level''', '''Raise''', '''Smooth''' and '''Restore'''. The modifiers {{Key press|Alt}} and {{Key press|Ctrl}} can be held during the Height Choosing phase of the '''Level''' and '''Raise''' commands for more height choosing control.

=== Level ===

http://licho.eu/alba/terraform/level.sized.jpg

'''Level''' will move the terrain in the area to exactly the same height, the result terrain will be flat. For example a hill could be flattened.

* Hold {{Key press|Alt}} to snap to either the starting height, just below water level (so that ships can't pass) or the level just below water level that land units cannot pass (23 deep).

* Hold {{Key press|Ctrl}} and move the mouse to select the height to be levelled to from terrain by mousing over the terrain.

* Tap {{Key press|Space}} to cycle through only raise or only level. This limits the terraform to either take away or add terrain instead of a mix of both. Can be toggled during Lasso stage.

=== Raise ===

http://licho.eu/alba/terraform/raise.sized.jpg

'''Raise''' raises or lowers the terrain in the area by the same amount, the relative height of the terrain within the area is not changed.

* Hold {{Key press|Alt}} to snap to heights by steps of 15. A 15 high (or deep) wall (or trench) will be impassable to vehicles but passable to bots. A 18 high wall will be impassable to most common bots. A 30 high wall will be impassable to everything except spiders.

* Press {{Key press|Ctrl}} to reset the height to 0.

=== Smooth ===

<img src="http://licho.eu/alba/terraform/smooth1.sized.jpg" width="360"/><img src="http://licho.eu/alba/terraform/smooth2.sized.jpg" width="360"/>

'''Smooth''' smooths the terrain, cliffs become less sharp.

=== Restore ===

<img src="http://licho.eu/alba/terraform/restore1.sized.jpg" width="360"/><img src="http://licho.eu/alba/terraform/restore2.sized.jpg" width="360"/>

'''Restore''' reverts the height of the terrain to what it was at the start of the game.

* Tap {{Key press|Space}} to cycle through only raise or only level. This limits the terraform to either take away or add terrain instead of a mix of both. Toggle during Lasso stage.

== Advanced Area Selection ==

For easier terraforming, {{Key press|Alt}} and/or {{Key press|Ctrl}} can be used to modify the way the lasso command is given.

* Hold {{Key press|Alt}} while clicking to terraform a rectangular area.

http://licho.eu/alba/terraform/square.jpg

* Hold {{Key press|Alt}} and click on a building or unit to create a wall around that unit.

http://licho.eu/alba/terraform/autowall.sized.jpg

* Hold {{Key press|Alt}} + {{Key press|Ctrl}} while clicking to create a hollow rectangle of terraform.

http://licho.eu/alba/terraform/ring.sized.jpg

* Hold {{Key press|Ctrl}} at any time during line drawing to create a straight section of line. Straight and non-straight lines can be mixed by pressing and releasing {{Key press|Ctrl}}.

http://licho.eu/alba/terraform/loopy.sized.jpg

== Terraforming Under Buildings In One Click ==

The default option of terraforming the ground under buildings is to press the {{Key press|B}} key after choosing the structure, changing the height of the project with {{Key press|C}} and {{Key press|V}} afterwards. By far the simplest way to use this kind of terraforming is to press {{Key press|Alt}} key while placing a structure and adjust the height of the structure by scrolling with the mouse wheel, but this option should first be enabled in the settings.

[[File:terraform_structure.gif]]

Structure terrforming controls can be changed in the menu: <code>Settings > Interface > Building placement</code>. Tick the <code>Alt mouse wheel to set height</code> to enable the easier construction option.

See [[Structure Placement]] for more information on structure terraforming.
== Ramp ==

The ramp command interface is different from that of the other terraform commands.

First select the '''Ramp''' command from the command menu.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/ramp.png

=== Simple Ramp ===
This is a simple way to make a ramp between 2 points on the ground. It uses exactly the same interface as advanced ramp but it can be unclear how to make a simple ramp just from the explanation of the full features of advanced ramp.

In short:
* {{Key press|Left Click}} the start of the ramp
* {{Key press|Left Click}} the end of the ramp
* {{Key press|Left Click}} again

==== Advanced Ramp ====
Using the full ramp interface you can make a ramp between any 2 arbitrary points above or below the terrain and chose the width of this ramp.

{{Key press|Left Click}} on the ground to set the start of the ramp. '''If''' you want to choose the height of the start of the ramp hold the click and move the mouse up or down. A little green line will appear out of the ground to indicate the height. The default height is the ground height, release the mouse to select the height.

* Hold {{Key press|Alt}} when choosing the start height to snap to the original ground height or just below water level(helpful for getting hovers out of the water).

<img src="http://licho.eu/alba/terraform/ramp1.sized.jpg" width="480"/>

* {{Key press|Left Click}} on the ground to set the end of the ramp. As with the start of the ramp, you can hold the mouse and move to choose the height.

* Hold {{Key press|Alt}} when choosing the end height to snap the gradient of the ramp to either upwards bot pathable, upwards vehicle pathable, flat, downwards vehicle pathable, downwards bot pathable, the original ground height or just below water level.

<img src="http://licho.eu/alba/terraform/ramp2.sized.jpg" width="480"/>

* Move the mouse up/down (not held down) and click to set the width of the ramp. Then {{Key press|Left Click}} to build it.

<img src="http://licho.eu/alba/terraform/ramp3.sized.jpg" width="480"/>

The ramp colour indicates whether all units will be able to use it, if vehicles/tanks will not be able to use it and if only spiders can use it.

<img src="http://licho.eu/alba/terraform/ramp_green.jpg" width="240"/><img src="http://licho.eu/alba/terraform/ramp_yellow.jpg" width="240"/><img src="http://licho.eu/alba/terraform/ramp_red.jpg" width="240"/>

Optional: Tap {{Key press|Space}} to cycle through only raise or only level. This limits the terraform to either take away or add terrain instead of a mix of both. Can be toggled at any stage during the ramp command.

== Cost ==

Terraform by default costs 1 metal, energy and build power to raise or lower 1 heightmap grid, each vertex of the blue grid maps onto a point on the heightmap grid. Due to the sloped sides it will be costly to make a very high spire. Equal volumes of terraform will have the same cost regardless of shape. Cost can be changed with the "terraform cost multiplier" [[Setting_Up_a_Game#Advanced_Options|ModOption]].

As a general guideline, assuming the base value for terraforming cost, creating a 15 deep wall (or trench) will cost roughly 19 resources per 'segment'.

Building a "skydust" (i.e. [[Stardust]] on a pillar) costs about 50 resources for a 50 height pillar, or 85 resources for 100 height.

== Terraform blocking ==

By placing troops or structures near the terraforming projects of your opponent you can deny their construction indefinitely. Use this to stop the enemy from building mountain ranges in your backyard or to defend your own creations from being deconstructed by enemy builders.

[[Image:Tera_block.png]]

== Tips ==

You can protect non-combat structures not sensitive to terrain such as [[Cornea|cloak]]/[[Aegis|shield generators]], [[Caretaker|nanoturrets]], [[Gunship Plant]]s and [[Missile Silo]]s with walls or holes.

Buildings cannot be moved vertically once placed. If you want to put a [[Fusion Reactor|Fusion]] in a hole for safety the hole will have to be built before the Fusion.

[[Big Bertha]]s, [[Crab]]s and [[Ogre]]s are very good at knocking down walls. [[Quake]] missiles are the ultimate solution against landscape designers.

http://licho.eu/alba/terraform/crabesmooth.sized.jpg

You can use terraforming to make a trench or wall underwater to stop amphibious bots.

[[Lobster|Lobsters]] can throw units over low walls.

Terraform ramp can be used with [[Newton]]s [[Newton_Firezones|to fire units at the enemy]]!

http://licho.eu/alba/terraform/newtonramp.sized.jpg

To set hotkeys for terraform commands, navigate into the game menu and look under hotkeys for <code>Levelground</code>, <code>Raiseground</code>, <code>Rampground</code>, <code>Smoothground</code> and <code>Restoreground</code>.

{{Navbox manual}}

Kodachi

2021-02-22T17:28:52Z

Legomenon: Update Kodachi tactics

The '''{{PAGENAME}}''' is a [[Unit_classes#raider|raider]] tank from the [[Tank Foundry]].{{ Infobox zkunit
| name = Kodachi
| defname = tankraid
| description = Raider Tank
| image = http://manual.zero-k.info/unitpics/tankraid.png
| icontype = tankscout
| cost = 180
| hitpoints = 670
| movespeed = 108
| turnrate = 190
| sight = 600
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Flame Bomb
| type = Cannon
| damage = 40
| reloadtime = 0.50
| dps = 80
| afterburn = 1
| range = 215
| aoe = 48
| customlabel1 = Ground Burn DPS
| customdata1 = 43
| customlabel2 = Ground Burn radius (elmo)
| customdata2 = 54
| customlabel3 = Ground Burn duration (s)
| customdata3 = 1.60
| projectilespeed = 520
}}
| abilities =
{{ Infobox zkability regen
| idleregen = 5
| timetoenable = 10.0
}}
{{ Infobox zkability line
| customdata1 = Immunity to afterburn
}}
}}==Description==
The Kodachi is a unique raider. Its small yet agile chassis has enough armor and speed to get it close enough to fire its weapon, a napalm bomb. The Kodachi should run in, get a few shots off, and withdraw before it takes significant damage. Damaged Kodachis regenerate out of combat.

== Tactics and Strategy ==
Using the Kodachi, like with other [[Tank Foundry]] units, requires a bit more finesse compared to other [[Unit classes#Raider|raiders]]. The Kodachi is slower, its weapon is mediocre at face-to-face engagements, and it will generally find itself outnumbered. The key lies in constant movement. While it can be quite a bit slower than its raider peers, Kodachi's flame bombs have respectable range, AOE, and are very damaging when trying to catch up to a Kodachi. Maneuver around laying fire at the path of enemy units but never directly engage into a fair fight, and retreat as soon as the enemy units give chase, shooting at them in near impunity.

Be careful about using the Kodachi alongside other units, especially other raiders like [[Blitz]]es. If you aren't careful, you could end up harming your own units with the Kodachi's napalm bombs, which set units on fire and leave behind puddles of napalm that burn for short periods of time.

The flame bomb ground burn does very adequate damage to buildings, but they inflict very little afterburn, unlike [[Pyro]]. This means the Kodachi has to stick around and destroy the building fully before being able to run away. It can still devastate enemy economy by destroying poorly defended [[Metal Extractor|metal extractors]] and [[energy]] sources in a few seconds, which makes it especially dangerous in the early game before sufficient defenses can be set up, or even later in the game when Kodachis return in larger numbers that allow them to dive past light static defenses.

While dealing with the Kodachi yourself remember its main flaws. Early radar detection will allow you to mount up proper defenses, as you never want it roaming around freely behind your lines. Form a wide formation with your units as to not get hit with AOE flames and encircle the Kodachi if you have fast raiders, or use the better range of your own raiders to kite it otherwise and prevent it from advancing further. One or two [[Lotus]]es may be helpful to corral the Kodachi towards less vulnerable areas of your territory, or even an [[Imp]] to bait the Kodachis into a trap. Try to not let it get away, since it will eventually regenerate back to full health.

{{Navbox units}}

Venom

2021-02-22T17:08:54Z

Legomenon: Try to update Venom tactics

The '''{{PAGENAME}}''' is a lightning riot spider from the [[Spider Factory]].{{ Infobox zkunit
| name = Venom
| defname = spideremp
| description = Lightning Riot Spider
| image = http://manual.zero-k.info/unitpics/spideremp.png
| icontype = spiderriotspecial
| cost = 200
| hitpoints = 740
| movespeed = 84
| turnrate = 316
| sight = 440
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Electro-Stunner
| type = LightningCannon
| damage = 65
| reloadtime = 1.10
| dps = 59
| empdamage = 400
| empdps = 364
| stuntime = 1
| range = 240
| aoe = 64
| special1 = Instantly hits
}}
}}==Description==
The Venom is an all-terrain unit designed to paralyze enemies so other units can easily destroy them. It moves particularly fast for a riot unit and in addition to the paralysis from its [[Weapon_classes#EMP|EMP]] weapon it does a respectable amount of damage. Works well in tandem with the Recluse to keep enemies from closing range with the fragile skirmisher.

==Strategy and Tactics==
The Venom's stun is very powerful, a single Venom will render an enemy almost helpless already, and two Venoms will stunlock it perfectly if they overlay their shots at all. Because of the stun, a few Venoms can leave many enemy units defenseless against any attacks. Hard-hitting assaults like the [[Hermit]] or skirmishers like the [[Recluse]], which fire projectiles that move too slowly to reliably hit agile enemies, can benefit greatly from the Venom's ability to disable enemies.

Aim for clusters of enemies, as the small splash radius can be exploited better, stunning many enemy units. When facing faster raiders, keep walking your Venoms towards the enemy so that they do not have any chance to escape in the small gaps between the Venom shots. Ensure that you don't stun your own Venoms.

The Venom is fast enough to close range on skirmishers. The speed also makes them a potent threat in small groups to lone, heavy units that cannot fend off raiders. Venoms deal EMP very quickly and can achieve stunlock in a matter of seconds against anything short of a [[Paladin]], this can be a brute force substitute for [[Widow]] when stealth is not necessary.

{{Navbox units}}

Gauss

2021-02-14T19:46:32Z

Legomenon: Gauss slight DPS nerf as of 1.9.2.0

The '''{{PAGENAME}}''' is a hardened artillery gauss turret designed to be difficult to dislodge with artillery. {{ Infobox zkunit
| name = Gauss
| defname = turretgauss
| description = Gauss Turret, 10 health/s when closed
| image = http://manual.zero-k.info/unitpics/turretgauss.png
| icontype = defense
| cost = 400
| hitpoints = 3000
| sight = 664
| weapons =
{{ Infobox zkweapon
| name = Light Gauss Cannon
| type = Cannon
| damage = 200
| reloadtime = 2.1
| dps = 95
| shielddamage = 150
| range = 560
| projectilespeed = 1200
| special1 = Water capable
| special2 = Piercing
}}
| abilities =
{{ Infobox zkability regen
| customlabel1 = Closed regen (HP/s)
| customdata1 = 10
}}
{{ Infobox zkability armored
| reduction = 75%
}}
}}==Description==
The Gauss is a compact, resilient turret with a medium-range gauss cannon. When popped down, it receives a quarter of incoming damage as well as small amount of health regeneration. It can also attack underwater targets.

==Tactics and Strategy==
Gauss has a similar role to Stinger, aka, it excels at exerting control over an area and generally putting a stop to enemy assaults. Its not quite as effective as Stinger in this role, but its dramatic damage reduction when closed tends to make it the superior option when enemy artillery is making itself a problem.

Gauss also has piercing shots and a greater fire rate, both of which make it significantly less vulnerable to swarms than Stinger. Its still not a riot turret though, and if the enemy has a significant raider presence you should consider supporting your Gauss with an anti-swarm turret. Faraday tends to be a good option because, like Gauss, it is armored and therefore artillery-resistant when not firing.

Gauss has a second life in the sea: it can shot underwater targets as well, and therefore can serve as a heavier turret option for sea than Urchin, as well as an artillery-resistant option.

There is a problem however: Gauss cannot be built on sea by default. You will have to place your sea Gauss in a convenient beach or island. Depending on depth and on how much you want the turret, terraforming a small earth pillar out of the sea may be viable. The upside is that since your sea Gauss will always be on solid ground, it will never be vulnerable to exclusively aquatic weapons, which makes it much harder for many waterborne units to take them out.

{{Navbox buildings}}

Viper

2021-02-14T19:44:35Z

Legomenon: Guardian only gets one single Viper as of 1.9.2.0

The '''{{PAGENAME}}''' is an advanced battle drone.{{ Infobox zkunit
| name = Viper
| defname = droneheavyslow
| description = Advanced Battle Drone
| image = http://manual.zero-k.info/unitpics/droneheavyslow.png
| icontype = gunship
| cost = 35
| hitpoints = 430
| movespeed = 150
| turnrate = 131
| sight = 500
| weapons =
{{ Infobox zkweapon
| name = Disruptor Pulse Beam
| type = BeamLaser
| damage = 200
| reloadtime = 2
| dps = 100
| slowdamage = 400
| slowdps = 200
| range = 200
| special1 = Instantly hits
}}
| abilities =
{{ Infobox zkability regen
| idleregen = 10
| timetoenable = 10.0
}}
}}==Description==
The Viper is an advanced battle drone similar to the Firefly but equipped with a Disruptor Pulse Beam, slowing its targets more with each hit.

A Viper can be created by adding the Battle Drone module to a [[Commander]].

The Guardian Commander can spawn in one Viper for free at level 5.

{{Navbox units}}

Firefly

2021-02-14T19:44:02Z

Legomenon: Update drone level gain for 1.9.2.0

The '''{{PAGENAME}}''' is an attack drone.{{ Infobox zkunit
| name = Firefly
| defname = dronelight
| description = Attack Drone
| image = http://manual.zero-k.info/unitpics/dronelight.png
| icontype = fighter
| cost = 20
| hitpoints = 180
| movespeed = 210
| turnrate = 131
| sight = 500
| weapons =
{{ Infobox zkweapon
| name = Light Particle Beam
| type = BeamLaser
| damage = 32
| reloadtime = 0.80
| dps = 40
| range = 150
| special1 = Instantly hits
}}
| abilities =
{{ Infobox zkability regen
| idleregen = 10
| timetoenable = 10.0
}}
}}==Description==
The Firefly is an attack drone with a weak high precision pulse laser. They can protect their parent unit from light enemy units. They do not share stealth with it though, so they can also betray the presence of a cloaked commander.

A Firefly can be created by adding the Companion Drone module to a [[Commander]].

The Guardian Commander can spawn in one Firefly for free at level 1, and gains an additional Firefly at levels 3 and 6.

{{Navbox units}}

Badger

2021-02-14T19:42:32Z

Legomenon: Update Badger damage breakdown for 1.9.2.0

The '''{{PAGENAME}}''' is an artillery minelayer rover from the [[Rover Assembly]].{{ Infobox zkunit
| name = Badger
| defname = veharty
| description = Artillery Minelayer Rover
| image = http://manual.zero-k.info/unitpics/veharty.png
| icontype = vehiclearty
| cost = 260
| hitpoints = 450
| movespeed = 68
| turnrate = 105
| sight = 660
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Light Mine Artillery
| type = Cannon
| damage = 190
| reloadtime = 5.5
| dps = 34
| range = 750
| aoe = 48
| customlabel1 = Spawns Unit
| customdata1 = [[Claw]]
| customlabel2 = Spawn Life (s)
| customdata2 = 60
| projectilespeed = 500
| special1 = High trajectory
}}
}}==Description==
The Badger lays mines which are fairly effective but have a limited lifespan from a distance (rather haphazardly). The Badger outranges most defenses comfortably, but is lightly armored and cannot flee easily so keep it screened with friendly units, possibly assisted by your own mines.

= Tactics and Strategy =
The Badger is generally too weak and inaccurate to effectively counter more robust enemy defenses like [[Stardust]] or [[Stinger]]s (which would be better countered with [[Impaler]]s). However, the Badger is useful in an area denial role (similar to the [[Firewalker]]), where its mines, while not particularly damaging to enemy assault units, can stop enemy raiders, skirmishers, and even cloaked units (like [[Scythe]]s, [[Widow]]s, and [[Ultimatum]]s) dead in their tracks.

The bulk of the damage of Badger is done via the mines it spawns, not its projectile. The Badger projectile only does 20 damage (with a respectable AoE), and spawns a mine that will explode into 5 bomblets inflicting 34 damage each to a single target, for 190 damage total per shot (and very little AoE). The full 190 damage will also be done if the projectile hits a shield directly.

The Badger's mines stay active for a single minute, so a single Badger that force-fires on the ground can prepare a minefield consisting of 11 mines in a minute, which it can maintain indefinitely as long as it keeps firing.

To quickly order multiple Badgers to create a minefield that stretches from place to place, hold down the Alt key, and drag a line from one spot to another, while giving the Badgers a force-fire order.

{{Navbox units}}

Funnelweb

2021-02-13T20:14:27Z

Legomenon: Mention Funnelweb shield recharge delay more explicitly

The '''{{PAGENAME}}''' is a shield support strider from the [[Strider Hub]].{{ Infobox zkunit
| name = Funnelweb
| defname = striderfunnelweb
| description = Shield Support Strider
| image = http://manual.zero-k.info/unitpics/striderfunnelweb.png
| icontype = t3special
| cost = 4000
| hitpoints = 4500
| movespeed = 41
| turnrate = 103
| sight = 650
| transportable = Heavy
| abilities =
{{ Infobox zkability construction
| buildpower = 40
}}
{{ Infobox zkability shield
| name = Energy Shield
| strength = 19400
| regen = 300
| regencost = 48
| radius = 550
}}
{{ Infobox zkability intel
| radar = 1400
}}
}}

==Description==
The slow all-terrain Funnelweb features an extremely powerful wide-area shield and high nano power for post-battle utility. It is otherwise unarmed.

== Tactics and Strategy ==
Use the Funnelweb as combat support. The shield and buildpower it offers is a force multiplier. Putting a solid force within its shield is a recipe for a base killing army. The Funnelweb's shield recharges quickly outside of combat, and the strength of its shield does not affect the shield strength of any nearby shielded units. The shield will only begin regenerating if it has taken no damage in the last 10 seconds, so harassing the Funnelweb with light repeated attacks can be a good tactic to drain and keep the shield health low.

Always, always, always give a Funnelweb an escort. It is not armed, and in cannot defend itself against anything. Seriously, a lone raider could destroy it. Bringing a mixed bag of riots, skirmishers, and raiders is usually a good idea.

{{Navbox units}}

Jack

2021-02-12T02:58:46Z

Legomenon: Fix typo

The '''{{PAGENAME}}''' is a melee assault jumper from the [[Jumpbot Factory]].{{ Infobox zkunit
| name = Jack
| defname = jumpassault
| description = Melee Assault Jumper
| image = http://manual.zero-k.info/unitpics/jumpassault.png
| icontype = jumpjetassault
| cost = 600
| hitpoints = 6000
| movespeed = 54
| turnrate = 237
| sight = 350
| transportable = Heavy
| weapons =
{{ Infobox zkweapon
| name = Spike
| type = BeamLaser
| damage = 300
| reloadtime = 1.0
| dps = 300
| range = 125
| special1 = Instantly hits
| special2 = Ignores shields
| special3 = Water capable
}}
| abilities =
{{ Infobox zkability jump
| range = 400
| reload = 10
| speed = 120
| midairjump = Yes
}}
}}==Description==
The Jack is a melee assault walker with jumpjets. A few Jacks can easily level most fortification lines. Its small range and very low speed make it very vulnerable to skirmishers.

== Tactics and Strategy ==
The Jack is another one of multi-use units in [[Jumpbot Factory]] rooster. Jacks are both tanks, damage dealers and sometimes even raiders in their own right.

The Jack can take quite a punishment, allowing them to tank in front of less sturdy units like [[Moderator]]s or [[Firewalker]]s. Their large healthpool and their jump ability also allows them to cross defence lines with ease, making it easy to send several Jacks behind enemy lines to wreak havoc.

The Jack has a surprisingly strong damage, mainly coming from its fast attack rate. You always want to outrange and outrun them in a fight. The best way of dealing with them are disabling methods. Units such as [[Venom]], [[Bolas]] or [[Gnat]] will give your army a window to dispose of Jacks.

Jacks can also be utilized in a very specific tactic using [[Newton]] turrets and their [[Newton Firezones]] command. It can allow your opponent to quickly overrun your base of operations, so keep an eye out for that.
{{Navbox units}}

Badger

2021-02-12T02:49:59Z

Legomenon: Fix Badger damage description read comprehension failure check

The '''{{PAGENAME}}''' is an artillery minelayer rover from the [[Rover Assembly]].{{ Infobox zkunit
| name = Badger
| defname = veharty
| description = Artillery Minelayer Rover
| image = http://manual.zero-k.info/unitpics/veharty.png
| icontype = vehiclearty
| cost = 260
| hitpoints = 450
| movespeed = 68
| turnrate = 105
| sight = 660
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Light Mine Artillery
| type = Cannon
| damage = 220
| reloadtime = 5.5
| dps = 40
| range = 750
| aoe = 48
| customlabel1 = Spawns Unit
| customdata1 = [[Claw]]
| customlabel2 = Spawn Life (s)
| customdata2 = 60
| projectilespeed = 500
| special1 = High trajectory
}}
}}==Description==
The Badger lays mines which are fairly effective but have a limited lifespan from a distance (rather haphazardly). The Badger outranges most defenses comfortably, but is lightly armored and cannot flee easily so keep it screened with friendly units, possibly assisted by your own mines.

= Tactics and Strategy =
The Badger is generally too weak and inaccurate to effectively counter more robust enemy defenses like [[Stardust]] or [[Stinger]]s (which would be better countered with [[Impaler]]s). However, the Badger is useful in an area denial role (similar to the [[Firewalker]]), where its mines, while not particularly damaging to enemy assault units, can stop enemy raiders, skirmishers, and even cloaked units (like [[Scythe]]s, [[Widow]]s, and [[Ultimatum]]s) dead in their tracks.

The bulk of the damage of Badger is done via the mines it spawns, not its projectile. The Badger projectile only does 20 damage (with a respectable AoE), and spawns a mine that will explode into 5 bomblets inflicting 40 damage each to a single target, for 220 damage total per shot (and very little AoE). The full 220 damage will also be done if the projectile hits a shield directly.

The Badger's mines stay active for a single minute, so a single Badger that force-fires on the ground can prepare a minefield consisting of 11 mines in a minute, which it can maintain indefinitely as long as it keeps firing.

To quickly order multiple Badgers to create a minefield that stretches from place to place, hold down the Alt key, and drag a line from one spot to another, while giving the Badgers a force-fire order.

{{Navbox units}}

Lance

2021-02-12T02:32:27Z

Legomenon: Lance formatting fix

The '''{{PAGENAME}}''' is an anti-heavy artillery hovercraft from the [[Hovercraft Platform]].{{ Infobox zkunit
| name = Lance
| defname = hoverarty
| description = Anti-Heavy Artillery Hovercraft
| image = http://manual.zero-k.info/unitpics/hoverarty.png
| icontype = mobiletachyon
| cost = 1000
| hitpoints = 1000
| movespeed = 53
| turnrate = 76
| sight = 660
| sonar = 660
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Tachyon Accelerator
| type = BeamLaser
| damage = 3000
| reloadtime = 20
| dps = 150
| range = 1000
| special1 = Instantly hits
}}
| abilities =
{{ Infobox zkability line
| customdata1 = Can ignore unidentified targets
}}
}}==Description==
The Lance's weapon, nicknamed 'the Blue Laser of Death', has the power and accuracy to skewer most units with a single shot. Use it against high armor units, but keep it behind the front lines - it has light armor and can't run from danger.

== Tactics and Strategy ==
Since Lances have such a low rate-of-fire, and very high damage-per-shot, it is good to set them to hold fire mode (or return fire mode) to conserve their shots for use against enemy striders and assault units. Moreover, setting them to hold fire against unidentified radar targets should help ensure that their shots hit more often (since targeting unidentified radar targets imposes accuracy penalties in general), though do keep in mind that, when used in conjunction with attack move orders, it might also result in the Lances stopping in front of unidentified targets. It is good to spread out your lances, as there is a tendency for Lances to sometimes hit each other when moving around and firing.

Note that Lance does not deal all of its damage instantly (it instead does 100 damage 30 times over the course of a second). This means it cannot pierce through a shield as easily as it might appear, though Lance remains useful to slowly drain enemy shields at a very safe range. On the plus side, this means a Lance beam can pierce through multiple enemy units, thus reducing its overkill potential when used in a target rich environment.

{{Navbox units}}

Venom

2021-02-12T02:30:58Z

Legomenon: Venom no longer does "a small amount of damage", stunlock cap is even higher now

The '''{{PAGENAME}}''' is a lightning riot spider from the [[Spider Factory]].{{ Infobox zkunit
| name = Venom
| defname = spideremp
| description = Lightning Riot Spider
| image = http://manual.zero-k.info/unitpics/spideremp.png
| icontype = spiderriotspecial
| cost = 200
| hitpoints = 750
| movespeed = 84
| turnrate = 316
| sight = 440
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Electro-Stunner
| type = LightningCannon
| damage = 65
| reloadtime = 1.10
| dps = 59
| empdamage = 400
| empdps = 364
| stuntime = 1
| range = 245
| aoe = 64
| special1 = Instantly hits
}}
}}==Description==
The Venom is an all-terrain unit designed to paralyze enemies so other units can easily destroy them. It moves particularly fast for a riot unit and in addition to the paralysis from its [[Weapon_classes#EMP|EMP]] weapon it does a respectable amount of damage. Works well in tandem with the Recluse to keep enemies from closing range with the fragile skirmisher.

==Strategy and Tactics==
The Venom's stun is very powerful, and can keep units stunlocked very effectively, which makes it a powerful addition to any spiderball. Because of the stun, a few Venoms can leave many enemy units defenseless against any attacks. Hard-hitting assaults like the [[Hermit]] or skirmishers like the [[Recluse]], which fire projectiles that move too slowly to reliably hit agile enemies, can benefit greatly from the Venom's ability to stunlock enemies.

Aim for clusters of enemies, as the small splash radius can be exploited better, stunning many enemy units. Ensure that you don't stun your own Venoms.

The Venom is fast enough to close range on skirmishers.

Given enough time, a Venom can stunlock even a [[Jugglenaut]].

{{Navbox units}}

Lance

2021-02-12T02:19:56Z

Legomenon: Add remark on Lance beam not being instant

The '''{{PAGENAME}}''' is an anti-heavy artillery hovercraft from the [[Hovercraft Platform]].{{ Infobox zkunit
| name = Lance
| defname = hoverarty
| description = Anti-Heavy Artillery Hovercraft
| image = http://manual.zero-k.info/unitpics/hoverarty.png
| icontype = mobiletachyon
| cost = 1000
| hitpoints = 1000
| movespeed = 53
| turnrate = 76
| sight = 660
| sonar = 660
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Tachyon Accelerator
| type = BeamLaser
| damage = 3000
| reloadtime = 20
| dps = 150
| range = 1000
| special1 = Instantly hits
}}
| abilities =
{{ Infobox zkability line
| customdata1 = Can ignore unidentified targets
}}
}}==Description==
The Lance's weapon, nicknamed 'the Blue Laser of Death', has the power and accuracy to skewer most units with a single shot. Use it against high armor units, but keep it behind the front lines - it has light armor and can't run from danger.

== Tactics and Strategy ==
Since Lances have such a low rate-of-fire, and very high damage-per-shot, it is good to set them to hold fire mode (or return fire mode) to conserve their shots for use against enemy striders and assault units. Moreover, setting them to hold fire against unidentified radar targets should help ensure that their shots hit more often (since targeting unidentified radar targets imposes accuracy penalties in general), though do keep in mind that, when used in conjunction with attack move orders, it might also result in the Lances stopping in front of unidentified targets. It is good to spread out your lances, as there is a tendency for Lances to sometimes hit each other when moving around and firing.

Note that Lance does not deal all of its damage instantly but instead does 100 damage 30 times over the course of a second. This means it cannot pierce through a shield as easily as it might appear, though Lance remains useful to slowly drain enemy shields at a very safe range. On the plus side, this means a Lance beam can pierce through multiple enemy units, thus reducing its overkill potential when used in a target rich environment.

{{Navbox units}}

Scorcher

2021-02-12T02:09:48Z

Legomenon: Mention Scorcher hit and run tactic

The '''{{PAGENAME}}''' is a raider rover from the [[Rover Assembly]].{{ Infobox zkunit
| name = Scorcher
| defname = vehraid
| description = Raider Rover
| image = http://manual.zero-k.info/unitpics/vehraid.png
| icontype = vehicleraider
| cost = 125
| hitpoints = 480
| movespeed = 111
| turnrate = 185
| sight = 560
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Heat Ray
| type = LaserCannon
| damage = 30
| reloadtime = 0.10
| dps = 300
| range = 270
| projectilespeed = 500
| special1 = Damage falls off with range
}}
}}==Description==
Capable of taking damage and dishing it out, the Scorcher is a versatile unit that remains very useful for more than just raiding, though it pays the price in manueverability and in cost. Though able to hold its own in combat, it is no match for anti-swarm and riot units or defenses. The Scorcher's heatray deals more damage up close.

Retreating from enemy raiders can allow the Scorcher to deal damage safely since it outranges and outspeeds most of its peers. The heatray damage is normally very poor at maximum range, but the projectile does not have to travel as far if an enemy unit is chasing the Scorcher, resulting in a much higher amount of damage being dealt. This can allow a group of Scorchers to harass enemy units that they cannot engage into directly so long as they make sure they can always retreat before the enemy closes in.

{{Navbox units}}

Sling

2021-02-12T02:00:32Z

Legomenon: Upsell Sling since it's much cheaper than it's ever been

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 = 100
| hitpoints = 350
| movespeed = 48
| turnrate = 297
| sight = 660
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Light Plasma Cannon
| type = Cannon
| damage = 150
| reloadtime = 6
| dps = 25
| range = 860
| projectilespeed = 270
}}
}}==Description==
The Sling has a long range plasma cannon that allows indirect fire over obstacles, and outranges static defenses up to heavy laser towers. Slings are ineffective against most mobile units and should be guarded in order to prevent raiders and other fast units from closing range.

= Tactics and Strategy =
Slings are by far the cheapest artillery in the game, which is both a strength and a weakness. On the one hand, this means you may need lots of them to accomplish the same task as a single [[Impaler]] or [[Lance]]. On the other hand, Slings are far better suited to combating light static defences like [[Picket|Pickets]], against which the relatively fragile Cloakbots are vulnerable and where heavier artillery units would be overkill. Building a few Slings for this task is often a good idea - being low cost allows them to be used with more granularity and earlier in the game than most other artillery. 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.

While Slings are not effective against most mobile units due to the low velocity of their projectile, they can still hit large targets such as shields or slow moving groups of enemy skirmishers. This makes them a useful soft counter to small quantities of shield bot units, particularly the relatively fragile and dangerous Felon. However, when encountered in larger groups linked Shield bot regeneration will be too high to overcome and the Slings will likely become ineffective.

A common employment of Slings is to station one or two within your own front line defences to prevent opponents from building defences and metal extractors of their own nearby.

Slings have excellent damage per cost compared to other artillery but have relatively low range so will take losses from heavier artillery such as [[Emissary]] or [[Firewalker]] as the game progresses and unit density increases. Slings will likely need protection so they can remain near the frontline, or support from other, longer range artillery to act as suppression fire.

{{Navbox units}}

Badger

2021-02-12T01:48:41Z

Legomenon: Attempt to explain Badger damage mechanics since the wiki stats can induce errors

The '''{{PAGENAME}}''' is an artillery minelayer rover from the [[Rover Assembly]].{{ Infobox zkunit
| name = Badger
| defname = veharty
| description = Artillery Minelayer Rover
| image = http://manual.zero-k.info/unitpics/veharty.png
| icontype = vehiclearty
| cost = 260
| hitpoints = 450
| movespeed = 68
| turnrate = 105
| sight = 660
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Light Mine Artillery
| type = Cannon
| damage = 220
| reloadtime = 5.5
| dps = 40
| range = 750
| aoe = 48
| customlabel1 = Spawns Unit
| customdata1 = [[Claw]]
| customlabel2 = Spawn Life (s)
| customdata2 = 60
| projectilespeed = 500
| special1 = High trajectory
}}
}}==Description==
The Badger lays mines which are fairly effective but have a limited lifespan from a distance (rather haphazardly). The Badger outranges most defenses comfortably, but is lightly armored and cannot flee easily so keep it screened with friendly units, possibly assisted by your own mines.

= Tactics and Strategy =
The Badger is generally too weak and inaccurate to effectively counter more robust enemy defenses like [[Stardust]] or [[Stinger]]s (which would be better countered with [[Impaler]]s). However, the Badger is useful in an area denial role (similar to the [[Firewalker]]), where its mines, while not particularly damaging to enemy assault units, can stop enemy raiders, skirmishers, and even cloaked units (like [[Scythe]]s, [[Widow]]s, and [[Ultimatum]]s) dead in their tracks.

The bulk of the damage of Badger is done via the mines it spawns, not its projectile. The Badger projectile only does 20 damage with a respectable AoE, but spawns 5 mines that will do 40 damage each to a single target, for 220 damage total per shot (and very little AoE). The full 220 damage will also be done if the projectile hits a shield directly.

The Badger's mines stay active for a single minute, so a single Badger that force-fires on the ground can prepare a minefield consisting of 11 mines in a minute, which it can maintain indefinitely as long as it keeps firing.

To quickly order multiple Badgers to create a minefield that stretches from place to place, hold down the Alt key, and drag a line from one spot to another, while giving the Badgers a force-fire order.

{{Navbox units}}

Morph Command

2021-02-12T01:43:35Z

Legomenon: Add reference to Djinn and Sparrow morph paths

The '''Morph''' command refers to the upgrade of [[Geothermal Generator]] into [[Advanced Geothermal]] power plant or transformation of buildings into mobile units, like [[Aegis]] into [[Aspis]] and [[Cornea]] into [[Iris]] (also the other way around). Other useful morphs are the spying plane [[Sparrow]] morphed from a [[Radar Tower]], and [[Djinn]] from a [[Conch]] constructor. Sometimes players also refer to [[Commander|commander upgrades]] as "morphing".

*Upgrading your [[Geothermal Generator|geo]], while beneficial, will render it disabled for the duration of the upgrade, and will require a fee in energy. The same is true for transformations.

{{Navbox commands}}
[[Category: Commands]]

Zero-K:Developing

2021-02-12T01:39:57Z

Legomenon: Add workaround pointer for running infra on a separate local network instance

New developers should read this before touching the source.

== ZK's Devving Philosophy (social rules) ==
* "War is a product of anticommunication"
** Communicate with other devs about your changes/fixes, let them understand the issue. Do not make 'random' changes.
* "Do not create work for other people."
** Have responsibility for your changes/commit. Do not leave bugs that require other people to fix.
* "Readability & performance are equally important."
** Optimize code but not to the point of unreadability. [http://c2.com/cgi/wiki?RulesOfOptimization Remember the rules of optimization]:
*** Don't.
*** Don't (yet).
*** Profile before doing it.
* "If it ain't broke, don't fix it."
** Don't code fixes that nobody wants to problems that don't exist.

== What is in source codes ==
* [https://github.com/ZeroK-RTS/Zero-K Zero-K] contains the game proper
** units folder contains unit definition files
*** You can read the wiki about game development for [http://springrts.com/wiki/Main_Page Spring Engine]
* [https://github.com/ZeroK-RTS/Zero-K-Infrastructure Zero-K-Infrastructure]
** Zero-K.info: Website sources
** ZkLobbyServer: Lobby server (for MP)
** ZkData: Website/server database structure
* [https://github.com/ZeroK-RTS/Chobby Chobby] contains the lobby client
* [https://github.com/ZeroK-RTS/Zero-K-Artwork Zero-K-Artwork] contains sources for 2D art, 3D art and sounds
* [https://github.com/ZeroK-RTS/SpringRTS-Tools SpringRTS-tools] contains various dev tools
** Upspring - required to edit the .3do and .s3o model files used in the game
** MapIconBuilder - unit map icon sources are here
* [https://github.com/ZeroK-RTS/Zero-K-Missions Zero-K-Missions] contains source files for official ZK missions

=== Style Guide===
The lua in the menu (chobby) and game proper should use the following whitespace:
* Indent with tabs.
* A tab may only follow a newline or another tab.
* If the text across two lines is being aligned (such as for a long function) then the two lines must have the same number of tabs.
* Don't try stack flow of control into one line. For example, put newlines after <code>then</code> and <code>else</code>.
* End files with a newline.
* Commas should be followed by whitespace. Relations (=, <, <=, >=, ==, ~=) should have whitespace on each side.
* if a conditional is to take up multiple lines, double indent the extra lines and end the line with a conjunction (See Gallery below)
These guidelines are not necessarily followed in old files so updating them with a separate commit is a good idea prior to making large changes. Also, unitdefs use two-space indentation instead of tabs.

There are a few guildines for dealing with Spring functions.
* Localisation of Spring.Function should be named spFunction.
* Localisation of Spring.MoveCtrl.Function should be named spMoveCtrlFunction.
* Spring.GetCommandQueue should be used rather than Spring.GetUnitCommands (it's an alias, we just picked one).

<gallery>
Styleguide-if-example.JPG|Proper multiline if statement
Styleguide-stackflow.JPG|Example of stacked flow control
</gallery>

== Getting sources ==
This is a guide to downloading Zero-K sources from [https://github.com/ GitHub] using [https://tortoisegit.org/ TortoiseGit]. The game sources are used as an example, however this method applies to other subprojects as well.
* Install [https://tortoisegit.org/download/ TortoiseGit].
* Create a [https://github.com/ GitHub] account.
[[File:ForkZK.jpg]]
* Log in to GitHub and [https://github.com/ZeroK-RTS Locate] the repository you want to edit.
* Click the "Fork" button on the GitHub website to create your own copy on GitHub.
[[File:ZKCloneCopy.png|1103px]]
* Locate your fork on GitHub and click "Code".
* Copy the web URL to your clipboard.
[[File:localCloneZK.jpg]]
* Create a folder called 'zk.sdd' in your Zero-K install under games.
* Right click on 'zk.sdd' and select 'Git Clone...' from the context menu.
[[File:cloneUIZK.jpg]]
* Copy the web URL into the 'URL:' field of the clone interface.
* Ensure that the 'Directory:' field ends in 'zk.sdd'. It is likely to automatically contain the path '...\Zero-K\games\zk.sdd\Zero-K' so be sure to delete the '\Zero-K' at the end.
[[File:cloneSuccess.jpg]]
* Wait for the sources to download.
* Your 'zk.sdd' folder should look something like the image above.

== Updating sources ==
Keep your sources up to date by periodically syncing your fork to the original repository (using 'compare', see: https://github.com/KirstieJane/STEMMRoleModels/wiki/Syncing-your-fork-to-the-original-repository-via-the-browser, then do "rebase and merge" instead of "merge") and doing TortoiseGit -> Pull on your repository folder to take the changes from GitHub to your local files.

== Modifying the game ==
:''For personal modding, see [[Mod Creation]]''
Follow the instructions in 'Getting sources' the download the Zero-K game sources. Feel free to inspect and edit the game files. Most developers using Windows edit lua files with [https://notepad-plus-plus.org/download/v7.6.6.html Notepad++].

To test your changes:
* (If using Windows make sure your file explorer has file name extensions enabled; for example the chobby_wrapper_port file should have a .txt on the end of its name.)
* Create an empty text file named 'devmode.txt' in the same directory as Zero-K.exe.
* Launch Zero-K.exe.
[[File:enableDevMode.jpg]]
* Select 'Zero-K Dev' in Settings -> Developer -> Singleplayer (you may need to scroll down).
[[File:startTest.jpg]]
* From the main menu select Singleplayer -> Skirmish -> Advanced -> Start to launch a test game. Note that the game type should be automatically set to 'Zero-K $VERSION'.
* In the game, press F8 to open debug console. It'll display errors and output to the log.

To test game changes in multiplayer:
* Make sure all players have a zk.sdd folder with the same exact files on their local Zero-K installation, or the game will desync.
* Launch Zero-K and create a passworded multiplayer lobby.
* Set the room type to Custom.
* Type <code>!game zk:dev</code> to set the game type to 'Zero-K $VERSION'.
* Launch the game normally once the other testers have joined.

== Modifying the lobby menu ==
Follow the instructions in 'Getting sources' with the following adjustments:
* The repository that you want to edit is https://github.com/ZeroK-RTS/Chobby.
* It is best to call the folder something like 'zkmenu.sdd', to avoid confusion.
Make sure that the 'Directory:' field ends in '.sdd'. You should end up with something like this:

[[File:zkmenufolder.jpg]]

To test your changes launch Zero-K.exe with the <tt>dev</tt> arg (i.e. <code>Zero-K.exe dev</code>). On windows this is best done by creating a shortcut and changing the target, as shown below.
[[File:targetZK.jpg]]

== Submitting changes ==
Git provides a systematic way to review and merge changes into the main repositories. The main game repository is used as example, but this method works for other repositories as well.

The simple way to commit changes is as follows.
* Make some changes to your local files.
* Right click on 'zk.sdd' and select 'Git Commit'.
* Write a description of the changes and click 'Commit'.
* Right click on 'zk.sdd' and select TortiseGit -> Push.
* Enter your GitHub login and password when prompted. The changes should now appear on your fork in GitHub.
* Navigate to https://github.com/ZeroK-RTS/Zero-K/pulls and click "New Pull Request".
* Click "compare across forks" to make your fork visible.
* Set your fork to be the head repository.
* Write a title and description of the changes, then create the pull request.
This creates a proposal to apply your changes to the main game. Be sure to check up on it and respond to comments.

A more advanced method involves creating branches locally with TortiseGit -> Create Branch and committing blocks of related changes to a single branch. You are then able to make pull requests from branches. This allows branches to be smaller and more focused, which is desirable when merging.

Make sure to keep your repository up to date to make merges less difficult.

== Zero-K.exe launch flags ==
<pre>Zero-K.exe [rapid tag] [engine version]</pre>
Note that the engine specified in arg won't automatically use the main Zero-K folder as its datadir. Add a <tt>springsettings.cfg</tt> file to the engine version's folder with the tag <code>SpringData = path_to_Zero-K_folder</code>

== Modifying infrastructure/tools ==
* Install [https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx Visual Studio Community edition]
* Install the developer or express edition, whichever works best for [https://www.microsoft.com/en-us/sql-server/sql-server-downloads SQL Server express]
* Recommended but perhaps not strictly necessary: Install [https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15 SQL Server Management Studio]
* Clone to desktop [https://github.com/ZeroK-RTS/Zero-K-Infrastructure Zero-K infrastructure]
* Test by opening Zero-K.sln in Visual Studio
* Infra overview/structure [[Zero-K Infra Guide]] (Incomplete/WIP)

=== Initializing Website Database ===
You may need to setup the database connection for the website. In order to do that: Open Visual Studio, open the Server Explorer panel (under the View menu), right click Data Connections -> Add Connection -> Sql Server. Enter <code>(localdb)\mssqllocaldb</code> in the Server Name field, after which zero-k_local will appear in the dropdown list of databases.

(If zero-k_local does not appear, type it in the text box and press OK; Visual Studio will ask whether you would like to create the database. This may require you to have administrator rights on the computer.)

[[File:zk-database-setup.png]]

=== Debugging infrastructure ===
* To run a project right click it, choose "set as startup project" and hit F5 to run using debugger.
* You can enable multiple startup projects to test entire infrastructure locally (game servers, lobby etc). Enable asp.net, springie and ZeroKLobby projects to test it all together. [http://i.imgur.com/2mgizUJ.png Setup]
* To run asp.net:
** It's required that you install MS SQL Server on your local PC.
*** You can get SQL Server 2019 (For Windows 10) [https://www.microsoft.com/en-us/sql-server/sql-server-downloads here] or SQL Server 2017 (for Windows 8 and later) [https://www.microsoft.com/en-us/sql-server/sql-server-2017 here] or SQL Server 2014 (for Windows 7) [https://www.microsoft.com/en-ie/download/details.aspx?id=42299 here]. For SQL Server 2014, the file you will need is called SQLEXPR_x64_ENU or SQLEXPR_x86_ENU. Make sure you install version that matches your version of Windows (i.e. x86 vs x64).
*** During the installation, set collation to <code>SQL_Latin1_General_CP1_CI_AS</code>. Leave all the parameters default except that I changed server name to SQLSERVER in one of the first steps of wizard.
[[File:SQL server collation.png|405px]]
** Right click asp.net -> properties -> web -> check "Specific Page" and leave it blank. Otherwise you get errors when trying to host locally.
** Make sure SQL Server is running (check the Sql Server Configuration Manager in the Start Menu). If you can't connect, edit the data source for <code>ModeType.Local</code> in <code>GlobalConst.cs</code> (currently line 46) to say something like: <code>Data Source=<hostname (usually your computer name)>\SQLSERVER</code>
** To make things run smoothly the following changes might also be a good idea: In <code>Shared/PlasmaShared/GlobalConst.cs</code> (currently line 137) replace the DefaultEngineOverride with whatever engine version is current. Comment out lines 190 and 238-298 of <code>Zero-K.info/AppCode/PlasmaServer.cs</code> unless somebody can supply instructions on how to make the torrent errors go away.

TODO: add download links for sample database tables here. Users and clans are probably easier to make yourself for most purposes. For now, if you need this ask Licho, Histidine, DeinFreund or Anarchid. Aquanim has sample tables for maps and Planetwars structures, if that is all that you need.

=== Testing ===
* When you run the server locally a browser window with the website should appear. You can connect to your local server with the normal lobby by going to Settings and setting the target to "localhost" rather than "zero-k.info".
* Once you have created an account you can make it an admin account by editing the database with SQL Server Management Studio. Open the list of databases in the tree on the left, open the Zero-K database, then in the Tables folder right-click on dbo.Accounts and select "Edit Top 200 Rows". Set the "AdminLevel" of your account to 2 for full admin powers.

If you are running Zero-K infrastructure on a separate machine on your local network, you will likely get a 400 Bad Hostname error on connecting to the website or the lobby. This is an issue with port opening and a likely fix is [https://stackoverflow.com/a/42989832 here].

=== Modifying The Database Structure ===
* Modify the appropriate files in ./ZkData/Ef/... and elsewhere ( [https://github.com/ZeroK-RTS/Zero-K-Infrastructure/commit/61addee11e74b09dd5dd73e12d31a28030d84e81 this commit] should be a reasonable guide; don't worry about the migration files, they are created later )
* In Visual Studio open Tools > NuGet Package Manager > Package Manager Console
* At the top of the window which appears, there is a "Default project" dropdown box. Set this to ZkData.
* Type the command <code>Add-Migration [description-of-change-here]</code> into the package manager console. This should create some migration files with your description and a timestamp in the name in the Migrations folder of ZkData.
* In some cases you may now need to manually edit the created migration files to set defaults and the like?
* Type the command <code>Update-Database</code> into the package manager console. This should update the database structure.
* To revert a migration that has not yet been pushed to the main repository, run <code>Update-Database –TargetMigration: TheLastGoodMigration</code> then delete your bad migration files.

== Artwork ==
See [http://zero-k.info/Wiki/Development_Artwork Development Artwork] (outdated)

[[Blender_To_Zero-K|Blender To Zero-K]]

== Missions ==
=== Campaign ===
Campaign planets/missions are defined in [//github.com/ZeroK-RTS/Chobby/tree/master/campaign/sample Chobby/campaign/sample]

=== Standalone missions ===
See [[Mission Editor|Mission Editor start page]]

== Updating PlanetWars for new round ==
:''TODO''
Changing faction:
* Faction ID, name, color in dbo.Faction
* Faction blurb <tt>Faction<Name></tt> on sitewiki
* Add/change icons if needed
** Site: img/factions/<name>.png
** Game: LuaUI/Configs/Factions
** Chobby: LuaMenu/Images/Factions
** Does chobby download them automatically? Presumably not

Using [https://zero-k.info/PlanetwarsAdmin Planetwars admin interface]: Change to a different galaxy if desired, reset PW

== Wiki ==
See [[Editing Help]]

=== Making/Editing a unit ===
See the Blender to Zero-K page for a comprehensive guide on modelling, texturing, and baking aoplates for Zero-K units: [https://zero-k.info/mediawiki/index.php?title=Blender_To_Zero-K Blender to Zero-K Page]

=== Unit pages ===
Part of each unit page is autogenerated by the [//github.com/ZeroK-RTS/SpringRTS-Tools/tree/master/unitguide Unit Guide tool], and uploaded by the [//github.com/ZeroK-RTS/Zero-K-Infrastructure/blob/master/Fixer/WikiPortingMW.cs Wiki bot].

Run <code>export_unit_templates.sh</code> to generate wiki templates for each unit (see <code>export_unit_templates.lua</code> for some configuration options), then have the bot read the generated text files and edit the unit pages accordingly (requires Visual Studio setup as detailed above). The text output can also be used to manually edit pages.

Unit buildicons and radar icons should be uploaded by FTP to manual.zero-k.info (<code>zero-k.info/zkmanual/www/unitpics</code> and <code>/icons</code> respectively). Contact Licho or Histidine for login details.

== itch.io builds ==
Instructions for updating the portable build on [https://itch.io/ itch.io]:

* Download latest Zero-K portable from https://zerok.itch.io/zero-k, extract to a folder
* Download butler (see guide at https://itch.io/docs/butler/)
* Modify extracted portable folder so that its contents are the same as what the user will download
* Run butler with command: <code>butler push <portable folder> zerok/zero-k:portable</code>

== Engine ==
See [https://springrts.com/wiki/Development:Getting_Started Spring Engine Development]

== Releasing Zero-K on steam safely ==

* Force push to stable branch
* In TeamCity click on Deploy LIVE Zero-K Lobby - this will build Zero-K.exe chobby wrapper
* Download the Zero-K.exe to your local machine from https://zero-k.info/lobby/Zero-K.exe
* Verify anti-virus status and upload to windows defender as false detection here: https://www.microsoft.com/en-us/wdsi/filesubmission
* In TeamCity click on Deploy LIVE website - this will deploy website and rebuild steam.
* If steam deployment fails, in list of builds click "rebuild steam"

Note that steps 2,3,4 are only needed if we are changing Zero-K.exe wrapper.

[[Category:Development]]

Kodachi

2021-02-01T05:07:20Z

Legomenon: v1.9.1.0 Kodachi speed nerf

The '''{{PAGENAME}}''' is a [[Unit_classes#raider|raider]] tank from the [[Tank Foundry]].{{ Infobox zkunit
| name = Kodachi
| defname = tankraid
| description = Raider Tank
| image = http://manual.zero-k.info/unitpics/tankraid.png
| icontype = tankscout
| cost = 180
| hitpoints = 670
| movespeed = 108
| turnrate = 190
| sight = 600
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Flame Bomb
| type = Cannon
| damage = 40
| reloadtime = 0.50
| dps = 80
| afterburn = 1
| range = 215
| aoe = 48
| customlabel1 = Ground Burn DPS
| customdata1 = 43
| customlabel2 = Ground Burn radius (elmo)
| customdata2 = 54
| customlabel3 = Ground Burn duration (s)
| customdata3 = 1.60
| projectilespeed = 520
}}
| abilities =
{{ Infobox zkability regen
| idleregen = 5
| timetoenable = 10.0
}}
{{ Infobox zkability line
| customdata1 = Immunity to afterburn
}}
}}==Description==
The Kodachi is a unique raider. Its small yet agile chassis has enough armor and speed to get it close enough to fire its weapon, a napalm bomb. The Kodachi should run in, get a few shots off, and withdraw before it takes significant damage. Damaged Kodachis regenerate out of combat.

== Tactics and Strategy ==
Using the Kodachi, like with other [[Tank Foundry]] units, requires a bit more finesse compared to other [[Unit classes#Raider|raiders]]. The Kodachi is slower, its weapon is mediocre at face-to-face engagements, and it will generally find itself outnumbered. The key lies in constant movement. While it can be quite a bit slower than its raider peers, Kodachi's flame bombs and regeneration allow it to outmaneuver its opponents. Remember to keep it on fire-at-will and maneuver around laying fire at the path of an enemy units.

Be careful about using the Kodachi alongside other units, especially other raiders like [[Blitz]]es. If you aren't careful, you could end up harming your own units with the Kodachi's napalm bombs, which set units on fire and leave behind puddles of napalm that burn for short periods of time.

Main prey of the Kodachi however is not units, but buildings. Remember that afterburn damage allows you even more mobility, as this unit doesn't need to stick around for burn damage to destroy the construction. The Kodachi can devastate enemy economy by quickly destroying poorly defended [[Metal Extractor|metal extractors]] and [[energy]] sources, which makes it especially dangerous in early game, or even later when it has greater numbers.

While dealing with the Kodachi yourself remember its main flaws. Early radar detection will allow you to mount up proper defenses, as you never want it roaming around freely behind your lines. Form a wide formation with your units as to not get hit with AOE flames and encircle the Kodachi. Try to not let it get away, since it will regenerate taken damage.

{{Navbox units}}

Weapons

2021-02-01T04:57:02Z

Legomenon: Clarify that disarm shuts down almost everything, including passive abilities

This is a list of some of the commonly found '''weapons''' in Zero-K and their unique characteristics.<div style="float:right;">__TOC__</div>

==Overview==

{| class="wikitable sortable"
! Name !! Range Type !! Notes
|-
| Plasma Cannons || Ballistic || -
|-
| EMG || Ballistic || High damage, short range
|-
| Lasers || Spherical || Instant hit, straight line
|-
| Missiles || Cylindrical || Tracking
|-
| Rockets || Cylindrical || Doesn't track
|-
| Gauss || Ballistic || Penetrates
|-
| Heatray || Spherical || Damage falls off with range
|-
| Fire || Cylindrical || Penetrates, puts units on fire
|-
| EMP || || No damage, temporarily disables unit
|-
| Lightning || Spherical || Inaccurate, temporarily disables unit
|-
| Slow || || Temporarily slows units
|}

==Plasma Cannons==
Plasma shells are a standard weapon for many units. Plasma Cannons are mostly fairly accurate with the exception of high trajectory plasma artillery. Plasma shells move relatively slowly and are affected by gravity which gives them a ballistic trajectory significantly increasing their range downhill while decreasing range uphill. The trajectory also means they can often shoot over friendly units. Their slow projectile speed means most plasma weapons are good against large, slow-moving, or stationary targets, but generally are not as good against fast moving targets or airborne units.

[[File:Weapon cannon.jpg]]

==EMG==
EMG's are fast rapid firing weapons that shoot numerous small plasma bullets. They are effective against any land targets and also against air targets that get in range. They have high damage output but short range. They have a ballistic trajectory like the plasma cannon that makes them signifincantly better at fighting downhill. Additionally, bullets from "Heavy EMG"s burst on impact, doing damage in an area of effect.

[[File:Weapon EMG.jpg]]

==Lasers==
Laser are accurate weapons that require a direct path between the weapon and target. They have no area of effect with the exception of the Starlight superweapon. Laser thickness is a good indicator of how much damage it does. They have spherical range and thus have their maximum 2D range against units at the same height as them. Lasers instantly hit which makes the constant fire lasers good against fast ground units and air, burst fire lasers can still hit fast units but are not good against them. If the target of a burst laser dies the laser can continue on and deal the remaining damage to units behind the target.

[[File:Weapon laser.jpg]]

==Missiles==
Missiles are projectiles that track their targets. Missiles have yellow exhaust and white smoke. All missiles will attack air, and most missiles will attack ground, except the missiles of dedicated anti-air units (which have blue exhaust). Missile range is not affected by terrain giving them a cylindrical target shape. This is useful as with a large enough height difference missiles will outrange lasers that they would not normally outrange.

[[File:Weapon missile.jpg]]

==Rockets==
Rockets are projectiles that do not track, but continue along their trajectory until impact. Rockets have red exhaust and black smoke. Rocket range, like missile, is not affected by terrain. Some rockets require a direct line to fire which makes them more likely to hit enemies other than their target if they miss. Other rockets have an arcing trajectory that makes them very good at shooting over allies so they can be quite powerful in groups. Rockets are slow so almost never hit air and are poor at hitting fast units.

[[File:Weapon rocket.jpg]]

==Gauss==
Like fire, gauss is also a penetrating weapon that moves through units. It moves fast, so will only rarely do additional damage to the same unit. It is ballistic like a plasma cannon which increases its range downhill. The faster projectile makes it able to often hit air and fast units, though it can miss.

[[File:Weapon gauss.jpg]]

==Heatray==
Heatrays, similar to lasers, require a direct path of fire between the weapon and target. Unlike lasers, the damage falls off with range, so the more distant the target the less damage is done. Close the distance to your target for more damage. Like lasers, they have spherical range.

[[File:Weapon heatray.jpg]]

==[[Fire]]==
[[Fire]] is a penetrating weapon with cylindrical range. It will do damage to all units in its firing line. Units hit by [[fire]] weapons also catch on [[fire]] and will continue to take damage for some time. This is useful for disabling cloak and repair. It can hit fast units and aircraft.

[[File:Weapon fire.jpg]]

==EMP==
Unlike most other weapons, EMP does not directly damage the enemy. Instead it fills up a separate EMP bar on the enemy. The size of a unit's "EMP health" is its ''current'' health so damaged units are easier to EMP. When 100% EMP damage is reached (emp damage exceeds current health) a unit is completely disabled and cannot move or return fire. Damage above 100% increases EMP time by 1 second per 2.5% up to a maximum EMP time that is different for each weapon. EMP heals automatically and a unit will be re-enabled once the EMP bar drops below 100% again. Against shields EMP will deal 1/3 of its damage. EMP is yellow, or in the case of the self-destructing [[Imp]], blue.

'''Disarm''' is a particular type of EMP that will leave the afflicted units able to move, but unable to use any weapons or special abilities (this includes jumping, using build power, regeneration or receiving income from the commander's Vanguard economy module). Disarmed units flash yellow instead of blue. '''Disarm''' has a separate bar.

[[File:Weapon EMP.jpg]]

==Lightning==
Lightning is direct-fire and carries EMP stun along with its damage. It has spherical range. Lightning weapons usually disable their targets before killing them, allowing them to be finished off with no fear of retaliation. Lightning is always blue. Lighting is somewhat inaccurate but should reliably hit any large unit.

[[File:Weapon lightning.jpg]]

==Slow==
Slow damage, similar to EMP, does not reduce enemy hitpoints. Instead it gradually decreases the move speed and rate of fire of enemy units. Like EMP the slow health of a unit is the current health of the unit. The reduction is the slow damage taken divided by the max health of the unit. Slow damage maxes out at 50% and cannot be increased past that point. Like EMP damage, slow damage also deals 1/3 of its damage against shields and automatically heals by 4% of the unit's current health per second once it has stopped taking further slow damage. Weapons with slow ability are purple.

Many slowing weapons are actually ''disruptors'', represented as purple projectiles or beams with a white core. These do both normal and slow damage.

[[File: Weapon slow.jpg]]

==Conclusion==
While this guide covers many of the more common types of weapons, there is still a wide variety of interesting devices at your disposal. The best way to learn them all is to have fun experimenting with them!

{{Navbox manual}}

Weapons

2021-02-01T04:42:39Z

Legomenon: Add specific rate for slow damage decay

This is a list of some of the commonly found '''weapons''' in Zero-K and their unique characteristics.<div style="float:right;">__TOC__</div>

==Overview==

{| class="wikitable sortable"
! Name !! Range Type !! Notes
|-
| Plasma Cannons || Ballistic || -
|-
| EMG || Ballistic || High damage, short range
|-
| Lasers || Spherical || Instant hit, straight line
|-
| Missiles || Cylindrical || Tracking
|-
| Rockets || Cylindrical || Doesn't track
|-
| Gauss || Ballistic || Penetrates
|-
| Heatray || Spherical || Damage falls off with range
|-
| Fire || Cylindrical || Penetrates, puts units on fire
|-
| EMP || || No damage, temporarily disables unit
|-
| Lightning || Spherical || Inaccurate, temporarily disables unit
|-
| Slow || || Temporarily slows units
|}

==Plasma Cannons==
Plasma shells are a standard weapon for many units. Plasma Cannons are mostly fairly accurate with the exception of high trajectory plasma artillery. Plasma shells move relatively slowly and are affected by gravity which gives them a ballistic trajectory significantly increasing their range downhill while decreasing range uphill. The trajectory also means they can often shoot over friendly units. Their slow projectile speed means most plasma weapons are good against large, slow-moving, or stationary targets, but generally are not as good against fast moving targets or airborne units.

[[File:Weapon cannon.jpg]]

==EMG==
EMG's are fast rapid firing weapons that shoot numerous small plasma bullets. They are effective against any land targets and also against air targets that get in range. They have high damage output but short range. They have a ballistic trajectory like the plasma cannon that makes them signifincantly better at fighting downhill. Additionally, bullets from "Heavy EMG"s burst on impact, doing damage in an area of effect.

[[File:Weapon EMG.jpg]]

==Lasers==
Laser are accurate weapons that require a direct path between the weapon and target. They have no area of effect with the exception of the Starlight superweapon. Laser thickness is a good indicator of how much damage it does. They have spherical range and thus have their maximum 2D range against units at the same height as them. Lasers instantly hit which makes the constant fire lasers good against fast ground units and air, burst fire lasers can still hit fast units but are not good against them. If the target of a burst laser dies the laser can continue on and deal the remaining damage to units behind the target.

[[File:Weapon laser.jpg]]

==Missiles==
Missiles are projectiles that track their targets. Missiles have yellow exhaust and white smoke. All missiles will attack air, and most missiles will attack ground, except the missiles of dedicated anti-air units (which have blue exhaust). Missile range is not affected by terrain giving them a cylindrical target shape. This is useful as with a large enough height difference missiles will outrange lasers that they would not normally outrange.

[[File:Weapon missile.jpg]]

==Rockets==
Rockets are projectiles that do not track, but continue along their trajectory until impact. Rockets have red exhaust and black smoke. Rocket range, like missile, is not affected by terrain. Some rockets require a direct line to fire which makes them more likely to hit enemies other than their target if they miss. Other rockets have an arcing trajectory that makes them very good at shooting over allies so they can be quite powerful in groups. Rockets are slow so almost never hit air and are poor at hitting fast units.

[[File:Weapon rocket.jpg]]

==Gauss==
Like fire, gauss is also a penetrating weapon that moves through units. It moves fast, so will only rarely do additional damage to the same unit. It is ballistic like a plasma cannon which increases its range downhill. The faster projectile makes it able to often hit air and fast units, though it can miss.

[[File:Weapon gauss.jpg]]

==Heatray==
Heatrays, similar to lasers, require a direct path of fire between the weapon and target. Unlike lasers, the damage falls off with range, so the more distant the target the less damage is done. Close the distance to your target for more damage. Like lasers, they have spherical range.

[[File:Weapon heatray.jpg]]

==[[Fire]]==
[[Fire]] is a penetrating weapon with cylindrical range. It will do damage to all units in its firing line. Units hit by [[fire]] weapons also catch on [[fire]] and will continue to take damage for some time. This is useful for disabling cloak and repair. It can hit fast units and aircraft.

[[File:Weapon fire.jpg]]

==EMP==
Unlike most other weapons, EMP does not directly damage the enemy. Instead it fills up a separate EMP bar on the enemy. The size of a unit's "EMP health" is its ''current'' health so damaged units are easier to EMP. When 100% EMP damage is reached (emp damage exceeds current health) a unit is completely disabled and cannot move or return fire. Damage above 100% increases EMP time by 1 second per 2.5% up to a maximum EMP time that is different for each weapon. EMP heals automatically and a unit will be re-enabled once the EMP bar drops below 100% again. Against shields EMP will deal 1/3 of its damage. EMP is yellow, or in the case of the self-destructing [[Imp]], blue.

'''Disarm''' is a particular type of EMP that will leave the afflicted units able to move, but unable to use any weapons or special abilities. Disarmed units flash yellow instead of blue. '''Disarm''' has a separate bar.

[[File:Weapon EMP.jpg]]

==Lightning==
Lightning is direct-fire and carries EMP stun along with its damage. It has spherical range. Lightning weapons usually disable their targets before killing them, allowing them to be finished off with no fear of retaliation. Lightning is always blue. Lighting is somewhat inaccurate but should reliably hit any large unit.

[[File:Weapon lightning.jpg]]

==Slow==
Slow damage, similar to EMP, does not reduce enemy hitpoints. Instead it gradually decreases the move speed and rate of fire of enemy units. Like EMP the slow health of a unit is the current health of the unit. The reduction is the slow damage taken divided by the max health of the unit. Slow damage maxes out at 50% and cannot be increased past that point. Like EMP damage, slow damage also deals 1/3 of its damage against shields and automatically heals by 4% of the unit's current health per second once it has stopped taking further slow damage. Weapons with slow ability are purple.

Many slowing weapons are actually ''disruptors'', represented as purple projectiles or beams with a white core. These do both normal and slow damage.

[[File: Weapon slow.jpg]]

==Conclusion==
While this guide covers many of the more common types of weapons, there is still a wide variety of interesting devices at your disposal. The best way to learn them all is to have fun experimenting with them!

{{Navbox manual}}

Zero-K:Developing

2021-01-30T02:23:30Z

Legomenon: Add instructions to test game mod in multiplayer

New developers should read this before touching the source.

== ZK's Devving Philosophy (social rules) ==
* "War is a product of anticommunication"
** Communicate with other devs about your changes/fixes, let them understand the issue. Do not make 'random' changes.
* "Do not create work for other people."
** Have responsibility for your changes/commit. Do not leave bugs that require other people to fix.
* "Readability & performance are equally important."
** Optimize code but not to the point of unreadability. [http://c2.com/cgi/wiki?RulesOfOptimization Remember the rules of optimization]:
*** Don't.
*** Don't (yet).
*** Profile before doing it.
* "If it ain't broke, don't fix it."
** Don't code fixes that nobody wants to problems that don't exist.

== What is in source codes ==
* [https://github.com/ZeroK-RTS/Zero-K Zero-K] contains the game proper
** units folder contains unit definition files
*** You can read the wiki about game development for [http://springrts.com/wiki/Main_Page Spring Engine]
* [https://github.com/ZeroK-RTS/Zero-K-Infrastructure Zero-K-Infrastructure]
** Zero-K.info: Website sources
** ZkLobbyServer: Lobby server (for MP)
** ZkData: Website/server database structure
* [https://github.com/ZeroK-RTS/Chobby Chobby] contains the lobby client
* [https://github.com/ZeroK-RTS/Zero-K-Artwork Zero-K-Artwork] contains sources for 2D art, 3D art and sounds
* [https://github.com/ZeroK-RTS/SpringRTS-Tools SpringRTS-tools] contains various dev tools
** Upspring - required to edit the .3do and .s3o model files used in the game
** MapIconBuilder - unit map icon sources are here
* [https://github.com/ZeroK-RTS/Zero-K-Missions Zero-K-Missions] contains source files for official ZK missions

=== Style Guide===
The lua in the menu (chobby) and game proper should use the following whitespace:
* Indent with tabs.
* A tab may only follow a newline or another tab.
* If the text across two lines is being aligned (such as for a long function) then the two lines must have the same number of tabs.
* Don't try stack flow of control into one line. For example, put newlines after <code>then</code> and <code>else</code>.
* End files with a newline.
* Commas should be followed by whitespace. Relations (=, <, <=, >=, ==, ~=) should have whitespace on each side.
* if a conditional is to take up multiple lines, double indent the extra lines and end the line with a conjunction (See Gallery below)
These guidelines are not necessarily followed in old files so updating them with a separate commit is a good idea prior to making large changes. Also, unitdefs use two-space indentation instead of tabs.

There are a few guildines for dealing with Spring functions.
* Localisation of Spring.Function should be named spFunction.
* Localisation of Spring.MoveCtrl.Function should be named spMoveCtrlFunction.
* Spring.GetCommandQueue should be used rather than Spring.GetUnitCommands (it's an alias, we just picked one).

<gallery>
Styleguide-if-example.JPG|Proper multiline if statement
Styleguide-stackflow.JPG|Example of stacked flow control
</gallery>

== Getting sources ==
This is a guide to downloading Zero-K sources from [https://github.com/ GitHub] using [https://tortoisegit.org/ TortoiseGit]. The game sources are used as an example, however this method applies to other subprojects as well.
* Install [https://tortoisegit.org/download/ TortoiseGit].
* Create a [https://github.com/ GitHub] account.
[[File:ForkZK.jpg]]
* Log in to GitHub and [https://github.com/ZeroK-RTS Locate] the repository you want to edit.
* Click the "Fork" button on the GitHub website to create your own copy on GitHub.
[[File:ZKCloneCopy.png|1103px]]
* Locate your fork on GitHub and click "Code".
* Copy the web URL to your clipboard.
[[File:localCloneZK.jpg]]
* Create a folder called 'zk.sdd' in your Zero-K install under games.
* Right click on 'zk.sdd' and select 'Git Clone...' from the context menu.
[[File:cloneUIZK.jpg]]
* Copy the web URL into the 'URL:' field of the clone interface.
* Ensure that the 'Directory:' field ends in 'zk.sdd'. It is likely to automatically contain the path '...\Zero-K\games\zk.sdd\Zero-K' so be sure to delete the '\Zero-K' at the end.
[[File:cloneSuccess.jpg]]
* Wait for the sources to download.
* Your 'zk.sdd' folder should look something like the image above.

== Updating sources ==
Keep your sources up to date by periodically syncing your fork to the original repository (using 'compare', see: https://github.com/KirstieJane/STEMMRoleModels/wiki/Syncing-your-fork-to-the-original-repository-via-the-browser, then do "rebase and merge" instead of "merge") and doing TortoiseGit -> Pull on your repository folder to take the changes from GitHub to your local files.

== Modifying the game ==
:''For personal modding, see [[Mod Creation]]''
Follow the instructions in 'Getting sources' the download the Zero-K game sources. Feel free to inspect and edit the game files. Most developers using Windows edit lua files with [https://notepad-plus-plus.org/download/v7.6.6.html Notepad++].

To test your changes:
* (If using Windows make sure your file explorer has file name extensions enabled; for example the chobby_wrapper_port file should have a .txt on the end of its name.)
* Create an empty text file named 'devmode.txt' in the same directory as Zero-K.exe.
* Launch Zero-K.exe.
[[File:enableDevMode.jpg]]
* Select 'Zero-K Dev' in Settings -> Developer -> Singleplayer (you may need to scroll down).
[[File:startTest.jpg]]
* From the main menu select Singleplayer -> Skirmish -> Advanced -> Start to launch a test game. Note that the game type should be automatically set to 'Zero-K $VERSION'.
* In the game, press F8 to open debug console. It'll display errors and output to the log.

To test game changes in multiplayer:
* Make sure all players have a zk.sdd folder with the same exact files on their local Zero-K installation, or the game will desync.
* Launch Zero-K and create a passworded multiplayer lobby.
* Set the room type to Custom.
* Type <code>!game zk:dev</code> to set the game type to 'Zero-K $VERSION'.
* Launch the game normally once the other testers have joined.

== Modifying the lobby menu ==
Follow the instructions in 'Getting sources' with the following adjustments:
* The repository that you want to edit is https://github.com/ZeroK-RTS/Chobby.
* It is best to call the folder something like 'zkmenu.sdd', to avoid confusion.
Make sure that the 'Directory:' field ends in '.sdd'. You should end up with something like this:

[[File:zkmenufolder.jpg]]

To test your changes launch Zero-K.exe with the <tt>dev</tt> arg (i.e. <code>Zero-K.exe dev</code>). On windows this is best done by creating a shortcut and changing the target, as shown below.
[[File:targetZK.jpg]]

== Submitting changes ==
Git provides a systematic way to review and merge changes into the main repositories. The main game repository is used as example, but this method works for other repositories as well.

The simple way to commit changes is as follows.
* Make some changes to your local files.
* Right click on 'zk.sdd' and select 'Git Commit'.
* Write a description of the changes and click 'Commit'.
* Right click on 'zk.sdd' and select TortiseGit -> Push.
* Enter your GitHub login and password when prompted. The changes should now appear on your fork in GitHub.
* Navigate to https://github.com/ZeroK-RTS/Zero-K/pulls and click "New Pull Request".
* Click "compare across forks" to make your fork visible.
* Set your fork to be the head repository.
* Write a title and description of the changes, then create the pull request.
This creates a proposal to apply your changes to the main game. Be sure to check up on it and respond to comments.

A more advanced method involves creating branches locally with TortiseGit -> Create Branch and committing blocks of related changes to a single branch. You are then able to make pull requests from branches. This allows branches to be smaller and more focused, which is desirable when merging.

Make sure to keep your repository up to date to make merges less difficult.

== Zero-K.exe launch flags ==
<pre>Zero-K.exe [rapid tag] [engine version]</pre>
Note that the engine specified in arg won't automatically use the main Zero-K folder as its datadir. Add a <tt>springsettings.cfg</tt> file to the engine version's folder with the tag <code>SpringData = path_to_Zero-K_folder</code>

== Modifying infrastructure/tools ==
* Install [https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx Visual Studio Community edition]
* Install the developer or express edition, whichever works best for [https://www.microsoft.com/en-us/sql-server/sql-server-downloads SQL Server express]
* Recommended but perhaps not strictly necessary: Install [https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15 SQL Server Management Studio]
* Clone to desktop [https://github.com/ZeroK-RTS/Zero-K-Infrastructure Zero-K infrastructure]
* Test by opening Zero-K.sln in Visual Studio
* Infra overview/structure [[Zero-K Infra Guide]] (Incomplete/WIP)

=== Initializing Website Database ===
You may need to setup the database connection for the website. In order to do that: Open Visual Studio, open the Server Explorer panel (under the View menu), right click Data Connections -> Add Connection -> Sql Server. Enter <code>(localdb)\mssqllocaldb</code> in the Server Name field, after which zero-k_local will appear in the dropdown list of databases.

(If zero-k_local does not appear, type it in the text box and press OK; Visual Studio will ask whether you would like to create the database. This may require you to have administrator rights on the computer.)

[[File:zk-database-setup.png]]

=== Debugging infrastructure ===
* To run a project right click it, choose "set as startup project" and hit F5 to run using debugger.
* You can enable multiple startup projects to test entire infrastructure locally (game servers, lobby etc). Enable asp.net, springie and ZeroKLobby projects to test it all together. [http://i.imgur.com/2mgizUJ.png Setup]
* To run asp.net:
** It's required that you install MS SQL Server on your local PC.
*** You can get SQL Server 2019 (For Windows 10) [https://www.microsoft.com/en-us/sql-server/sql-server-downloads here] or SQL Server 2017 (for Windows 8 and later) [https://www.microsoft.com/en-us/sql-server/sql-server-2017 here] or SQL Server 2014 (for Windows 7) [https://www.microsoft.com/en-ie/download/details.aspx?id=42299 here]. For SQL Server 2014, the file you will need is called SQLEXPR_x64_ENU or SQLEXPR_x86_ENU. Make sure you install version that matches your version of Windows (i.e. x86 vs x64).
*** During the installation, set collation to <code>SQL_Latin1_General_CP1_CI_AS</code>. Leave all the parameters default except that I changed server name to SQLSERVER in one of the first steps of wizard.
[[File:SQL server collation.png|405px]]
** Right click asp.net -> properties -> web -> check "Specific Page" and leave it blank. Otherwise you get errors when trying to host locally.
** Make sure SQL Server is running (check the Sql Server Configuration Manager in the Start Menu). If you can't connect, edit the data source for <code>ModeType.Local</code> in <code>GlobalConst.cs</code> (currently line 46) to say something like: <code>Data Source=<hostname (usually your computer name)>\SQLSERVER</code>
** To make things run smoothly the following changes might also be a good idea: In <code>Shared/PlasmaShared/GlobalConst.cs</code> (currently line 137) replace the DefaultEngineOverride with whatever engine version is current. Comment out lines 190 and 238-298 of <code>Zero-K.info/AppCode/PlasmaServer.cs</code> unless somebody can supply instructions on how to make the torrent errors go away.

TODO: add download links for sample database tables here. Users and clans are probably easier to make yourself for most purposes. For now, if you need this ask Licho, Histidine, DeinFreund or Anarchid. Aquanim has sample tables for maps and Planetwars structures, if that is all that you need.

=== Testing ===
* When you run the server locally a browser window with the website should appear. You can connect to your local server with the normal lobby by going to Settings and setting the target to "localhost" rather than "zero-k.info".
* Once you have created an account you can make it an admin account by editing the database with SQL Server Management Studio. Open the list of databases in the tree on the left, open the Zero-K database, then in the Tables folder right-click on dbo.Accounts and select "Edit Top 200 Rows". Set the "AdminLevel" of your account to 2 for full admin powers.

=== Modifying The Database Structure ===
* Modify the appropriate files in ./ZkData/Ef/... and elsewhere ( [https://github.com/ZeroK-RTS/Zero-K-Infrastructure/commit/61addee11e74b09dd5dd73e12d31a28030d84e81 this commit] should be a reasonable guide; don't worry about the migration files, they are created later )
* In Visual Studio open Tools > NuGet Package Manager > Package Manager Console
* At the top of the window which appears, there is a "Default project" dropdown box. Set this to ZkData.
* Type the command <code>Add-Migration [description-of-change-here]</code> into the package manager console. This should create some migration files with your description and a timestamp in the name in the Migrations folder of ZkData.
* In some cases you may now need to manually edit the created migration files to set defaults and the like?
* Type the command <code>Update-Database</code> into the package manager console. This should update the database structure.
* To revert a migration that has not yet been pushed to the main repository, run <code>Update-Database –TargetMigration: TheLastGoodMigration</code> then delete your bad migration files.

== Artwork ==
See [http://zero-k.info/Wiki/Development_Artwork Development Artwork] (outdated)

[[Blender_To_Zero-K|Blender To Zero-K]]

== Missions ==
=== Campaign ===
Campaign planets/missions are defined in [//github.com/ZeroK-RTS/Chobby/tree/master/campaign/sample Chobby/campaign/sample]

=== Standalone missions ===
See [[Mission Editor|Mission Editor start page]]

== Updating PlanetWars for new round ==
:''TODO''
Changing faction:
* Faction ID, name, color in dbo.Faction
* Faction blurb <tt>Faction<Name></tt> on sitewiki
* Add/change icons if needed
** Site: img/factions/<name>.png
** Game: LuaUI/Configs/Factions
** Chobby: LuaMenu/Images/Factions
** Does chobby download them automatically? Presumably not

Using [https://zero-k.info/PlanetwarsAdmin Planetwars admin interface]: Change to a different galaxy if desired, reset PW

== Wiki ==
See [[Editing Help]]

=== Making/Editing a unit ===
See the Blender to Zero-K page for a comprehensive guide on modelling, texturing, and baking aoplates for Zero-K units: [https://zero-k.info/mediawiki/index.php?title=Blender_To_Zero-K Blender to Zero-K Page]

=== Unit pages ===
Part of each unit page is autogenerated by the [//github.com/ZeroK-RTS/SpringRTS-Tools/tree/master/unitguide Unit Guide tool], and uploaded by the [//github.com/ZeroK-RTS/Zero-K-Infrastructure/blob/master/Fixer/WikiPortingMW.cs Wiki bot].

Run <code>export_unit_templates.sh</code> to generate wiki templates for each unit (see <code>export_unit_templates.lua</code> for some configuration options), then have the bot read the generated text files and edit the unit pages accordingly (requires Visual Studio setup as detailed above). The text output can also be used to manually edit pages.

Unit buildicons and radar icons should be uploaded by FTP to manual.zero-k.info (<code>zero-k.info/zkmanual/www/unitpics</code> and <code>/icons</code> respectively). Contact Licho or Histidine for login details.

== itch.io builds ==
Instructions for updating the portable build on [https://itch.io/ itch.io]:

* Download latest Zero-K portable from https://zerok.itch.io/zero-k, extract to a folder
* Download butler (see guide at https://itch.io/docs/butler/)
* Modify extracted portable folder so that its contents are the same as what the user will download
* Run butler with command: <code>butler push <portable folder> zerok/zero-k:portable</code>

== Engine ==
See [https://springrts.com/wiki/Development:Getting_Started Spring Engine Development]

[[Category:Development]]

Commander

2020-05-09T04:50:15Z

Legomenon: 1.8.3.2 speed modifier changes

<div style="float:right;">__TOC__</div>
= Commander intro =

At the start of a match, you are given the option to select a [[#Commander Chassis|Commander Chassis]].

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commstrike.png">
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commassault.png">
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commrecon.png">
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commsupport.png">

Your desired playstyle will determine which of the commanders would suit you best, which are summarized in the following table:
{| class="wikitable"
! || HP || Speed || Can Jump || Build Power || Modules
|-
| '''Strike''' || High || Fast|| No || Normal || Versatile
|-
| '''Guardian''' || Excellent || Medium || No || Normal || Powerful
|-
| '''Recon''' || Low || Fast || Yes || Lower || Light
|-
| '''Engineer''' || Medium || Slow || No || Improved || Support
|-
|}

Your commander can be configured with a variety of [[#Module types|Modules]] to better suit your playstyle. A commander can be made more powerful in the middle of a round by using the 'Morph' command to gain levels. Each time you morph to a higher Commander Level you are given the option to spend metal to attach new modules.

Modules can have different costs. Morphs to a new Level have a base cost and additional cost for each module selected.

Commanders start at Level 1 with a Beam Laser and a radar module attached.

At Commander Level 2, it is possible to replace your starting [[#Weapon types|Weapon]].

At Commander Level 4, a second weapon (or a [[#Weapon types|Special Weapon]]) can be added. Some weapons at this level require the use of both hands. If the weapon upgrade slot is left empty, your commander is given a second Beam Laser for free.

Each added level past level 2 gives the commander a health boost. Commanders can morph an unlimited number of times until all possible modules are attached. Engineer commanders will also gain additional build power with each level.

Favorite loadouts can be created and saved (up to Commander Level 6) for online play.

= 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 !! +
|-
| Base [[File:Ibeam.png|20px]] cost || -     ||25 || 100 || 600 || 200 || +100
|-
| Base time || - || 2 || 6 || 30 || 8 || ++
|-
| Total Weapon slots || 0 || 1 || 1 || 2 || 2 || +0
|-
| Total Module slots || 0 || 1 || 3 || 5 || 8 || +3
|-
|}

Equipping weapons and modules costs additional metal. Morph time is partly dependant on the metal cost.

== 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 be stacked up to 8 times. Stacking them repeatedly will create a powerful commander, even though their bonuses as quite minor. 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.

{| class="wikitable sortable" style="text-align: center"
! Name
! scope="col" class="unsortable" | Description
! Cost
! Strike !! Guardian !! Recon !! Engineer
|-
! Advanced targeting system
| +7.5% range for all weapons. -1 speed.
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Damage booster
| +10% damage for all weapons. -1 speed.
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! High density plating
| +1600 HP,-3 speed. Requires Ablative armor plates.
| 400
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Ablative armor plates
| +600 HP
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Companion drone
| +1 [[Firefly|Weak attack drone]]
| 300
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Battle drone
| +1 [[Viper|Drone with slowing laser]], requires Companion drone.
| 500
| style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: green;" | ✔
|-
! Carrepairer's nanolathe
| +4 Buildpower
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! High power servos
| +3 speed
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Autorepair system
| +10 HP/sec, -100 HP
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
|}

=== 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 cloaking field. These are cyan as well.

{| class="wikitable sortable" style="text-align: center"
! Name
! scope="col" class="unsortable" | Description
! Cost
! Req. level
! Strike !! Guardian !! Recon !! Engineer
|-
! Area shield conversion
| Upgrades Personal shield. Larger shield (same as [[Aspis]]) Prevents commander from cloaking
| 250
| 3
| style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: green;" | ✔
|-
! Cloaking field
| Upgrades Radar jammer. Cloaks friendly units within 350 elmo similar to [[Iris]] 15 E/s upkeep
| 600
| 3
| style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: green;" | ✔
|-
! Field radar
| Basic radar with 1800 elmo range
| 75
| 1 (Free)
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Lazarus device
| Commander can resurrect wrecks same as [[Athena]]
| 400
| 2
| style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: green;" | ✔
|-
! Personal cloak
| Cloaks the commander Does not work with shields and slows down commander by -8 speed
| 400
| 2
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Personal shield
| Small shield with 1250 HP, no upkeep Prevents commander from cloaking
| 300
| 2
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Radar jammer
| 500 elmo range
| 200
| 2
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
|}

=== 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 require a level 2 commander. They are a space effective way to spend a module slot but make sure you have the weapon that they affect. They are purple.

{| class="wikitable sortable" style="text-align: center"
! Name
! scope="col" class="unsortable" | Description
! Cost
! Weapon
! Strike !! Guardian !! Recon !! Engineer
|-
! Disruptor ammo
| Reduced direct damage by 25%. Add slow damage equal to 2X damage.
| 300
| Shotgun Machine gun Light/Heavy particle beam
| style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Flux amplifier
| Improves stun duration and EMP damage.
| 300
| Lightning rifle Multi stunner
| style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Napalm warhead
| Set targets on fire. Reduced direct damage.
| 350
| Riot cannon Rocket launcher
| style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: red;" | ✘
|-
|}

== 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.

{| class="wikitable sortable" style="text-align: center"
! Name
! Range
! Reload time
! Damage
! DPS
! Strike !! Guardian !! Recon !! Engineer
! scope="col" class="unsortable" | Notes
|-
!Beam Laser
| 330 || || || 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
| Constant beam
|-
! Flame thrower
| 270 || 0.17 || 11 || 66
| style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: red;" | ✘
| Sets units on fire for 15s(15 DPS) Pierces units Does more damage against larger units
|-
! Heatray
| 300 || 0.1 || 0 - 45 ||0 - 450
| style="color: red;" |✘ || style="color: green;" |✔ || style="color: red;" | ✘ || style="color: red;" | ✘
| Damage falls off linearly with range
|-
! Heavy particle beam
| 390 || 3.1 || 800 || 258
| style="color: red;" |✘ || style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: green;" | ✔
| Replaces all other weapons Mounted on second weapon slot
|-
! Light particle beam
| 300 || 0.33 || 70 || 210
| style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: green;" | ✔
|
|-
! Lightning Rifle
| 300 || 1.83 || 220+550 || 120+300
| style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: green;" | ✔
| [[Weapon_classes#EMP|EMP]] duration: 1s
|-
! Machine Gun
| 285 || 0.17 || 30 || 180
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: red;" | ✘
|
|-
! Missile launcher
| 415 || 1 || 80 || 80
| style="color: green;" | ✔ || style="color: red;" |✘ || style="color: red;" |✘ || style="color: green;" | ✔
| Homing
|-
! Pea Shooter
| 300 || 0.1 || 12 || 120
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|
|-
! Riot cannon
| 275 || 1.63 || 220 || 135
|style="color: red;" |✘ || style="color: green;" |✔ || style="color: red;" |✘ || style="color: red;" |✘
| AoE
|-
! Rocket launcher
| 430 || 3 || 360 || 120
| style="color: red;" |✘ || style="color: green;" | ✔ || style="color: red;" |✘ || style="color: red;" |✘
| Not Homing
|-
! Shock Rifle
| 600 || 12 || 1512 || 125
| style="color: red;" |✘ || style="color: red;" |✘ || style="color: red;" |✘ || style="color: green;" | ✔
| Replaces all other weapons Mounted on second weapon slot
|-
! Shotgun
| 290 || 2 || 32x12 (384) || 192
| style="color: green;" | ✔ || style="color: red;" |✘ || style="color: green;" | ✔ || style="color: green;" | ✔
|
|-
|}

=== 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.

{| class="wikitable sortable" style="text-align: center"
! Name
! Range
! Reload time
! Damage
! DPS
! Strike !! Guardian !! Recon !! Engineer
! scope="col" class="unsortable" | Special Notes
|-
! Cluster bomb
| 360 || 30 || 300x8 (2400)|| 80
| style="color: red;" |✘ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: red;" |✘
| Bomblets spread (like a shotgun)
|-
! Concussion shell
| 450 || 25 ||750 || 30
| style="color: red;" |✘ || style="color: red;" |✘ || style="color: green;" | ✔ || style="color: red;" |✘
| Has Impulse (Tosses some units)
|-
! Disintegrator
| 200 ||30 ||2000 || 46.67
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: red;" |✘ || style="color: red;" |✘
| Directed burst of energy Damage varies on unit size
|-
! Disruptor bomb
| 450 ||25 ||350+2100 || 14+84
| style="color: green;" | ✔ || style="color: red;" |✘ || style="color: green;" | ✔ || style="color: green;" | ✔
| [[Weapon_classes#Slow|Slow Effect]], Has large AOE (512)
|-
! Hellfire grenade
| 450 || 25||200 || 8
| style="color: red;" |✘ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: red;" |✘
| Sets an area on fire (45s,40dps+3s burning)
|-
! Multistunner
| 360 || 25||550/800 x 16 (8800/12800) ||352/512
| style="color: green;" | ✔ || style="color: red;" |✘ || style="color: green;" | ✔ || style="color: green;" | ✔
| Affected by flux amplifier. Max [[Weapon_classes#EMP|EMP]] time: 8s [upgraded: 10s]
|-
! SLAM
| 700 ||30 || 1512|| 50.4
| style="color: red;" |✘ || style="color: green;" | ✔ || style="color: red;" |✘ || style="color: red;" |✘
| Tactical Missile with high vertical arc
|-
|}
Key: EMP Damage, Slow Damage

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

You can configure custom commanders based on these chassis on your user page; you must be logged in to the Zero-K website and go to: https://zero-k.info/My/Commanders. These custom commanders may be selected at the beginning of the game in multiplayer matches. You will still need to upgrade them as usual, but the upgrade options are filled in to your preferences.

== Common attributes ==
{|
| '''Metal Production''' || 4 / s ||    || '''Energy Production''' || 6 / s
|-
| '''Beam Range''' || 330 ||    || '''HP Regen''' || 5 / s
|-
| '''Sight Distance'''|| 500 ||    || '''Sonar Distance''' || 500
|-
| '''Build Power''' || 10 ||    || '''Build Power (Engineer)''' || 10+
|-
| '''Build Range''' || 144 ||    || '''Build Range (Engineer)''' || 220+
|-
|}

Metal and energy production come from a unique '''Vanguard economy module'''. Any resurrected commanders will have lost this module and produce no resources. Engineer commanders gain additional build power and range with levels.

== 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
* Good health and highest speed (43.5)
* Can use the most weapon types
* Combat regen bonus

{|
! Level 1 !! Level 2 !! Level 3 !! Level 4 !! Level 5 !! Level 6
|-
|HP: 4200 || HP: 4200 || HP: 4600 Bonus regen: 10 || HP: 5200 Bonus Regen: 16|| HP: 5800 Bonus regen: 25||HP: 6400 Bonus regen: 35
|-
|}

=== Guardian Commander ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commassault.png 
* Best HP
* Medium speed (40)
* Gains more HP from increased levels than other chassis do
* Able to use most non-exotic weapons
* Gains free companion and battle drones with levels

{|
! Level 1 !! Level 2 !! Level 3 !! Level 4 !! Level 5 !! Level 6
|-
|HP: 4400 Light Drones: 1||HP: 4400 Light Drones: 1||HP: 5000 Light Drones: 2||HP: 5700 Light Drones: 2 Heavy Drones: 1||HP: 6600 Light Drones: 3 Heavy Drones: 1||HP: 7600 Light Drones: 3 Heavy Drones: 2
|-
|}

=== Recon Commander ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commrecon.png 
* Lowest HP
* Highest Speed (43.5)
* Can Jump
* Uses light weapons
* Has lowest buildpower (8 instead of 10)

{|
! Level 1 !! Level 2 !! Level 3 !! Level 4 !! Level 5 !! Level 6
|-
|HP: 3250||HP: 3250||HP: 3400||HP: 3600||HP: 3800||HP: 4000
|-
|}

=== Engineer Commander ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commsupport.png 
* Lowest speed (39)
* Low HP
* Gains buildpower and small amount of build range with levels
* Increased build range (220 + 12/level, up to 280, compared to 144 for others)
* Fewer direct damage weapons

{|
! Level 1 !! Level 2 !! Level 3 !! Level 4 !! Level 5 !! Level 6
|-
|HP: 3800 Buildpower: 12||HP: 3800 Buildpower: 14||HP: 4000 Buildpower: 16||HP: 4300 Buildpower: 18||HP: 4600 Buildpower: 21||HP: 5000 Buildpower: 24
|-
|}

= 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% damage modules multiply a commander's damage 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}}

Commander

2020-05-09T04:45:31Z

Legomenon: 1.8.3.2 commander changes

<div style="float:right;">__TOC__</div>
= Commander intro =

At the start of a match, you are given the option to select a [[#Commander Chassis|Commander Chassis]].

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commstrike.png">
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commassault.png">
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commrecon.png">
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commsupport.png">

Your desired playstyle will determine which of the commanders would suit you best, which are summarized in the following table:
{| class="wikitable"
! || HP || Speed || Can Jump || Build Power || Modules
|-
| '''Strike''' || High || Fast|| No || Normal || Versatile
|-
| '''Guardian''' || Excellent || Medium || No || Normal || Powerful
|-
| '''Recon''' || Low || Fast || Yes || Lower || Light
|-
| '''Engineer''' || Medium || Slow || No || Improved || Support
|-
|}

Your commander can be configured with a variety of [[#Module types|Modules]] to better suit your playstyle. A commander can be made more powerful in the middle of a round by using the 'Morph' command to gain levels. Each time you morph to a higher Commander Level you are given the option to spend metal to attach new modules.

Modules can have different costs. Morphs to a new Level have a base cost and additional cost for each module selected.

Commanders start at Level 1 with a Beam Laser and a radar module attached.

At Commander Level 2, it is possible to replace your starting [[#Weapon types|Weapon]].

At Commander Level 4, a second weapon (or a [[#Weapon types|Special Weapon]]) can be added. Some weapons at this level require the use of both hands. If the weapon upgrade slot is left empty, your commander is given a second Beam Laser for free.

Each added level past level 2 gives the commander a health boost. Commanders can morph an unlimited number of times until all possible modules are attached. Engineer commanders will also gain additional build power with each level.

Favorite loadouts can be created and saved (up to Commander Level 6) for online play.

= 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 !! +
|-
| Base [[File:Ibeam.png|20px]] cost || -     ||25 || 100 || 600 || 200 || +100
|-
| Base time || - || 2 || 6 || 30 || 8 || ++
|-
| Total Weapon slots || 0 || 1 || 1 || 2 || 2 || +0
|-
| Total Module slots || 0 || 1 || 3 || 5 || 8 || +3
|-
|}

Equipping weapons and modules costs additional metal. Morph time is partly dependant on the metal cost.

== 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 be stacked up to 8 times. Stacking them repeatedly will create a powerful commander, even though their bonuses as quite minor. 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.

{| class="wikitable sortable" style="text-align: center"
! Name
! scope="col" class="unsortable" | Description
! Cost
! Strike !! Guardian !! Recon !! Engineer
|-
! Advanced targeting system
| +7.5% range for all weapons. -2.5% speed.
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Damage booster
| +10% damage for all weapons. -2.5% speed.
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! High density plating
| +1600 HP,-10% speed. Requires Ablative armor plates.
| 400
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Ablative armor plates
| +600 HP
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Companion drone
| +1 [[Firefly|Weak attack drone]]
| 300
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Battle drone
| +1 [[Viper|Drone with slowing laser]], requires Companion drone.
| 500
| style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: green;" | ✔
|-
! Carrepairer's nanolathe
| +4 Buildpower
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! High power servos
| +8% speed
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Autorepair system
| +10 HP/sec, -100 HP
| 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
|}

=== 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 cloaking field. These are cyan as well.

{| class="wikitable sortable" style="text-align: center"
! Name
! scope="col" class="unsortable" | Description
! Cost
! Req. level
! Strike !! Guardian !! Recon !! Engineer
|-
! Area shield conversion
| Upgrades Personal shield. Larger shield (same as [[Aspis]]) Prevents commander from cloaking
| 250
| 3
| style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: green;" | ✔
|-
! Cloaking field
| Upgrades Radar jammer. Cloaks friendly units within 350 elmo similar to [[Iris]] 15 E/s upkeep
| 600
| 3
| style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: green;" | ✔
|-
! Field radar
| Basic radar with 1800 elmo range
| 75
| 1 (Free)
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Lazarus device
| Commander can resurrect wrecks same as [[Athena]]
| 400
| 2
| style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: green;" | ✔
|-
! Personal cloak
| Cloaks the commander Does not work with shields
| 400
| 2
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Personal shield
| Small shield with 1250 HP, no upkeep Prevents commander from cloaking
| 300
| 2
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Radar jammer
| 500 elmo range
| 200
| 2
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
|}

=== 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 require a level 2 commander. They are a space effective way to spend a module slot but make sure you have the weapon that they affect. They are purple.

{| class="wikitable sortable" style="text-align: center"
! Name
! scope="col" class="unsortable" | Description
! Cost
! Weapon
! Strike !! Guardian !! Recon !! Engineer
|-
! Disruptor ammo
| Reduced direct damage by 25%. Add slow damage equal to 2X damage.
| 300
| Shotgun Machine gun Light/Heavy particle beam
| style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Flux amplifier
| Improves stun duration and EMP damage.
| 300
| Lightning rifle Multi stunner
| style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: green;" | ✔
|-
! Napalm warhead
| Set targets on fire. Reduced direct damage.
| 350
| Riot cannon Rocket launcher
| style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: red;" | ✘
|-
|}

== 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.

{| class="wikitable sortable" style="text-align: center"
! Name
! Range
! Reload time
! Damage
! DPS
! Strike !! Guardian !! Recon !! Engineer
! scope="col" class="unsortable" | Notes
|-
!Beam Laser
| 330 || || || 150
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
| Constant beam
|-
! Flame thrower
| 270 || 0.17 || 11 || 66
| style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: red;" | ✘
| Sets units on fire for 15s(15 DPS) Pierces units Does more damage against larger units
|-
! Heatray
| 300 || 0.1 || 0 - 45 ||0 - 450
| style="color: red;" |✘ || style="color: green;" |✔ || style="color: red;" | ✘ || style="color: red;" | ✘
| Damage falls off linearly with range
|-
! Heavy particle beam
| 390 || 3.1 || 800 || 258
| style="color: red;" |✘ || style="color: red;" | ✘ || style="color: red;" | ✘ || style="color: green;" | ✔
| Replaces all other weapons Mounted on second weapon slot
|-
! Light particle beam
| 300 || 0.33 || 70 || 210
| style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: green;" | ✔
|
|-
! Lightning Rifle
| 300 || 1.83 || 220+550 || 120+300
| style="color: green;" | ✔ || style="color: red;" | ✘ || style="color: green;" | ✔ || style="color: green;" | ✔
| [[Weapon_classes#EMP|EMP]] duration: 1s
|-
! Machine Gun
| 285 || 0.17 || 30 || 180
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: red;" | ✘
|
|-
! Missile launcher
| 415 || 1 || 80 || 80
| style="color: green;" | ✔ || style="color: red;" |✘ || style="color: red;" |✘ || style="color: green;" | ✔
| Homing
|-
! Pea Shooter
| 300 || 0.1 || 12 || 120
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: green;" | ✔
|
|-
! Riot cannon
| 275 || 1.63 || 220 || 135
|style="color: red;" |✘ || style="color: green;" |✔ || style="color: red;" |✘ || style="color: red;" |✘
| AoE
|-
! Rocket launcher
| 430 || 3 || 360 || 120
| style="color: red;" |✘ || style="color: green;" | ✔ || style="color: red;" |✘ || style="color: red;" |✘
| Not Homing
|-
! Shock Rifle
| 600 || 12 || 1512 || 125
| style="color: red;" |✘ || style="color: red;" |✘ || style="color: red;" |✘ || style="color: green;" | ✔
| Replaces all other weapons Mounted on second weapon slot
|-
! Shotgun
| 290 || 2 || 32x12 (384) || 192
| style="color: green;" | ✔ || style="color: red;" |✘ || style="color: green;" | ✔ || style="color: green;" | ✔
|
|-
|}

=== 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.

{| class="wikitable sortable" style="text-align: center"
! Name
! Range
! Reload time
! Damage
! DPS
! Strike !! Guardian !! Recon !! Engineer
! scope="col" class="unsortable" | Special Notes
|-
! Cluster bomb
| 360 || 30 || 300x8 (2400)|| 80
| style="color: red;" |✘ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: red;" |✘
| Bomblets spread (like a shotgun)
|-
! Concussion shell
| 450 || 25 ||750 || 30
| style="color: red;" |✘ || style="color: red;" |✘ || style="color: green;" | ✔ || style="color: red;" |✘
| Has Impulse (Tosses some units)
|-
! Disintegrator
| 200 ||30 ||2000 || 46.67
| style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: red;" |✘ || style="color: red;" |✘
| Directed burst of energy Damage varies on unit size
|-
! Disruptor bomb
| 450 ||25 ||350+2100 || 14+84
| style="color: green;" | ✔ || style="color: red;" |✘ || style="color: green;" | ✔ || style="color: green;" | ✔
| [[Weapon_classes#Slow|Slow Effect]], Has large AOE (512)
|-
! Hellfire grenade
| 450 || 25||200 || 8
| style="color: red;" |✘ || style="color: green;" | ✔ || style="color: green;" | ✔ || style="color: red;" |✘
| Sets an area on fire (45s,40dps+3s burning)
|-
! Multistunner
| 360 || 25||550/800 x 16 (8800/12800) ||352/512
| style="color: green;" | ✔ || style="color: red;" |✘ || style="color: green;" | ✔ || style="color: green;" | ✔
| Affected by flux amplifier. Max [[Weapon_classes#EMP|EMP]] time: 8s [upgraded: 10s]
|-
! SLAM
| 700 ||30 || 1512|| 50.4
| style="color: red;" |✘ || style="color: green;" | ✔ || style="color: red;" |✘ || style="color: red;" |✘
| Tactical Missile with high vertical arc
|-
|}
Key: EMP Damage, Slow Damage

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

You can configure custom commanders based on these chassis on your user page; you must be logged in to the Zero-K website and go to: https://zero-k.info/My/Commanders. These custom commanders may be selected at the beginning of the game in multiplayer matches. You will still need to upgrade them as usual, but the upgrade options are filled in to your preferences.

== Common attributes ==
{|
| '''Metal Production''' || 4 / s ||    || '''Energy Production''' || 6 / s
|-
| '''Beam Range''' || 330 ||    || '''HP Regen''' || 5 / s
|-
| '''Sight Distance'''|| 500 ||    || '''Sonar Distance''' || 500
|-
| '''Build Power''' || 10 ||    || '''Build Power (Engineer)''' || 10+
|-
| '''Build Range''' || 144 ||    || '''Build Range (Engineer)''' || 220+
|-
|}

Metal and energy production come from a unique '''Vanguard economy module'''. Any resurrected commanders will have lost this module and produce no resources. Engineer commanders gain additional build power and range with levels.

== 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
* Good health and highest speed (43.5)
* Can use the most weapon types
* Combat regen bonus

{|
! Level 1 !! Level 2 !! Level 3 !! Level 4 !! Level 5 !! Level 6
|-
|HP: 4200 || HP: 4200 || HP: 4600 Bonus regen: 10 || HP: 5200 Bonus Regen: 16|| HP: 5800 Bonus regen: 25||HP: 6400 Bonus regen: 35
|-
|}

=== Guardian Commander ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commassault.png 
* Best HP
* Medium speed (40)
* Gains more HP from increased levels than other chassis do
* Able to use most non-exotic weapons
* Gains free companion and battle drones with levels

{|
! Level 1 !! Level 2 !! Level 3 !! Level 4 !! Level 5 !! Level 6
|-
|HP: 4400 Light Drones: 1||HP: 4400 Light Drones: 1||HP: 5000 Light Drones: 2||HP: 5700 Light Drones: 2 Heavy Drones: 1||HP: 6600 Light Drones: 3 Heavy Drones: 1||HP: 7600 Light Drones: 3 Heavy Drones: 2
|-
|}

=== Recon Commander ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commrecon.png 
* Lowest HP
* Highest Speed (43.5)
* Can Jump
* Uses light weapons
* Has lowest buildpower (8 instead of 10)

{|
! Level 1 !! Level 2 !! Level 3 !! Level 4 !! Level 5 !! Level 6
|-
|HP: 3250||HP: 3250||HP: 3400||HP: 3600||HP: 3800||HP: 4000
|-
|}

=== Engineer Commander ===
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commsupport.png 
* Lowest speed (39)
* Low HP
* Gains buildpower and small amount of build range with levels
* Increased build range (220 + 12/level, up to 280, compared to 144 for others)
* Fewer direct damage weapons

{|
! Level 1 !! Level 2 !! Level 3 !! Level 4 !! Level 5 !! Level 6
|-
|HP: 3800 Buildpower: 12||HP: 3800 Buildpower: 14||HP: 4000 Buildpower: 16||HP: 4300 Buildpower: 18||HP: 4600 Buildpower: 21||HP: 5000 Buildpower: 24
|-
|}

= 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}}

Dominatrix

2020-05-05T04:48:06Z

Legomenon: Fix typo

The '''{{PAGENAME}}''' is a capture rover from the [[Rover Assembly]].{{ Infobox zkunit
| name = Dominatrix
| defname = vehcapture
| description = Capture Rover
| image = http://manual.zero-k.info/unitpics/vehcapture.png
| icontype = vehiclespecial
| cost = 420
| hitpoints = 820
| movespeed = 59
| turnrate = 111
| sight = 550
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Capture Ray
| type = BeamLaser
| damage = 11.1
| reloadtime = 0.03
| dps = 333
| range = 450
| special1 = Instantly hits
| special2 = Ignores shields
| special3 = Water capable
}}
}}==Description==
The Dominatrix [[capture]]s enemies, turning them against their former allies. Multiple Dominatrix can capture a single target faster, although only one becomes the controller. After taking control of a unit the Dominatrix cannot fire for 12 seconds. If a Dominatrix is destroyed all units it controls are freed.

= Tactics and Strategy =
Note that the Dominatrix's capture dps is pitted against the target's HP. This means that, for example, a single Dominatrix (which has a capture dps of 333) takes about 20.5 seconds to capture an enemy [[Minotaur]] (which has 6800 HP). Also note that damaged units will be captured faster and that capture damage does not ignore unit armor. Capture damage decays quickly if the target escapes range, so partial damage will most likely go to waste.

To prolong the life span of your frail Dominatrices, try escorting them with at least 1 [[Aspis]], along with an [[Iris]] to help keep enemy artillery from skirmishing your Dominatrices to death. Be warned that, like with other shield balls, such a combination is asking to be countered with [[Firewalker]]s, [[Imp]]s, [[Snitch]]es, [[Thunderbird]]s, or [[Likho]]s to name a few.

==Best uses for Dominatrix==

1) Countering rushes of nasty heavyweight riots: Mace, Ogre, Redback. For an equal price to the rush unit, you get the Dominatrix which stops the rush unit - and you also get the rush unit. Typically, the rushing player resigns after realising that they've spent most of their economy on giving you one of these units.

2) Defeating medium-heavy assault units. Minotaur and Jack in particular are very difficult for Rover to counter without a Domi, but this will require a critical mass of Domis to have sufficient DPS to actually complete the capture.

3) Killing enemy commanders. Now, Rover doesn't lack in commander-killing options, with Scorchers and Ravagers also being quite good at the job. But a Dominatrix outruns and outranges non-trollcom commanders, so an unassisted com caught in the wild against a Domi will soon encounter a fate worse than death, creating a massive 8 metal per second differential for the capturer.

If your enemy is inattentive, you may even get this almost for free, because the dominatrix capture ray does not trigger the "commander under attack" alarm.

==Countering Dominatrix==

Countering Dominatrix as hover, your two choice units are Halberd and Lance. Ideally, both!

1) Halberd costs less than the dominatrix and takes little capture damage while armored. You will need at least 3 halberd per enemy 2 dominatrix, but halberds are fast enough to catch up with the domis, and more importantly, they are very hard to stop and they are *very bad at killing each other*. So when they get turned, Dominatrices don't get any bonus kills from the freshly acquired slaves; instead, once the remaining Halberds kill one of the slave-owning Domis, you get your slightly dented Halberds back.

2) Lance has the range and alpha to kill dominatrices with impunity. It might not be effective if shooting by radar though, but that's where Halberds come in handy.

3) Scalpel if you want to fight dirty. A Scalpel/Mace force fights very favorably with almost every Rover composition, barring things like heavy Badger - at least, until Thunderbirds come out. The Scalpel/Mace build also trades equally with Dominatrix - remember that you get two Scalpel for one Domi, and while a Domi outranges the Scalpel slightly, it's not a big enough margin to prevent return fire. It takes two scalpel salvos to kill a domi, and if you succeed, you more or less erase all the damage the Domi did. A good trick here is to manually target them, otherwise the first captures will waste shots for most of your army.

== Other counters ==

Once the enemy has fielded five or more dominatrix, you may consider further asymmetric options:

Aggressive porcing - Dominatrix is quite bad against Stinger. Extra good if your artillery is an anti-mobile kind, which is literally any artillery unit except Sling and Impaler - then you can also bombard the enemy units from your porc forest!

Air bombing - but start with a Thunderbird because unassisted Ravens will probably be captured. A Dominatrix takes two Raven bombs to die, too.

Cloaked snitches - remember, 5 dominatrix is over 2k metal. You get to facswitch to shield (800m), an area cloaker (500-ish), and four-five Snitches for this price.

Phantoms - just bring something to keep the Darts away.

Emissary. Outruns, outranges, and outguns Dominatrix. Kind of mandatory late game.

{{Navbox units}}

Dominatrix

2020-05-05T04:44:38Z

Legomenon: Update Dominatrix tactics for Metal -> HP capture damage change

The '''{{PAGENAME}}''' is a capture rover from the [[Rover Assembly]].{{ Infobox zkunit
| name = Dominatrix
| defname = vehcapture
| description = Capture Rover
| image = http://manual.zero-k.info/unitpics/vehcapture.png
| icontype = vehiclespecial
| cost = 420
| hitpoints = 820
| movespeed = 59
| turnrate = 111
| sight = 550
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Capture Ray
| type = BeamLaser
| damage = 11.1
| reloadtime = 0.03
| dps = 333
| range = 450
| special1 = Instantly hits
| special2 = Ignores shields
| special3 = Water capable
}}
}}==Description==
The Dominatrix [[capture]]s enemies, turning them against their former allies. Multiple Dominatrix can capture a single target faster, although only one becomes the controller. After taking control of a unit the Dominatrix cannot fire for 12 seconds. If a Dominatrix is destroyed all units it controls are freed.

= Tactics and Strategy =
Note that the Dominatrix's capture dps is pitted against the target's HP. This means that, for example, a single Dominatrix (which has a capture dps of 333) takes about 20.5 seconds to capture an enemy [[Minotaur]] (which has 6800 HP). Also note that damaged units will be captured faster and that capture damage does not ignore unit armor. Capture damage decays quickly if the target escapes range, so partial damage will most likely go to waste.

To prolong the life span of your frail Dominatrices, try escorting them with at least 1 [[Aspis]], along with an [[Iris]] to help keep enemy artillery from skirmishing your Dominatrices to death. Be warned that, like with other shield balls, such a combination is asking to be countered with [[Firewalker]]s, [[Imp]]s, [[Snitch]]es, [[Thunderbird]]s, or [[Likho]]s to name a few.

==Best uses for Dominatrix==

1) Countering rushes of nasty heavyweight riots: Mace, Ogre, Redback. For an equal price to the rush unit, you get the Dominatrix which stops the rush unit - and you also get the rush unit. Typically, the rushing player resigns after realising that they've spent most of their economy on giving you one of these units.

2) Defeating medium-heavy assault units. Minotaur and Jack in particular are very difficult for Rover to counter without a Domi, but this will require a critical mass of Domis to have sufficient DPS to actually complete the capture.

3) Killing enemy commanders. Now, Rover doesn't lack in commander-killing options, with Scorchers and Ravagers also being quite good at the job. But a Dominatrix outruns and outranges non-trollcom commanders, so an unassisted com caught in the wild against a Domi will soon encounter a fate worse than death, creating a massive 8 metal per second differential for the capturer.

If your enemy is inattentive, you may even get this almost for free, because the dominatrix capture ray does not trigger the "commander under attack" alarm.

==Countering Dominatrix==

Countering Dominatrix as hover, your two choice units are Halberd and Lance. Ideally, both!

1) Halberd costs less than the dominatrix and takes little capture damage while armored. You will need at least 3 halberd per enemy 2 dominatrix, but halberds are fast enough to catch up with the domis, and more importantly, they are very hard to stop and they are *very bad at killing each other*. So when they get turned, Dominatrices don't get any bonus kills from the freshly acquired slaves; instead, once the remaining Halberds kill one of the slave-owning Domis, you get your slightly dented Halberds back.

2) Lance has the range and alpha to kill dominatrices with impunity. It might not be effective if shooting by radar though, but that's where Halberds come in handy.

3) Scalpel if you want to fight dirty. A Scalpel/Mace force fights very favorable with almost every Rover composition, barring things like heavy Badger - at least, until Thunderbirds come out. The Scalpel/Mace build also trades equally with Dominatrix - remember that you get two Scalpel for one Domi, and while a Domi outranges the Scalpel slightly, it's not a big enough margin to prevent return fire. It takes two scalpel salvos to kill a domi, and if you succeed, you more or less erase all the damage the Domi did. A good trick here is to manually target them, otherwise the first captures will waste shots for most of your army.

== Other counters ==

Once the enemy has fielded five or more dominatrix, you may consider further asymmetric options:

Aggressive porcing - Dominatrix is quite bad against Stinger. Extra good if your artillery is an anti-mobile kind, which is literally any artillery unit except Sling and Impaler - then you can also bombard the enemy units from your porc forest!

Air bombing - but start with a Thunderbird because unassisted Ravens will probably be captured. A Dominatrix takes two Raven bombs to die, too.

Cloaked snitches - remember, 5 dominatrix is over 2k metal. You get to facswitch to shield (800m), an area cloaker (500-ish), and four-five Snitches for this price.

Phantoms - just bring something to keep the Darts away.

Emissary. Outruns, outranges, and outguns Dominatrix. Kind of mandatory late game.

{{Navbox units}}