Zero-K - User contributions [en]

Repair

2025-12-07T07:14:01Z

Mach56: /* Active repair */ Explicitly define the in-combat penalty instead of implicitly

== 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.
* Units that have taken damage in the last 10 seconds suffer an "in-combat penalty" and are repaired at 25% of the normal repair speed (i.e. 3 times slower than construction).
* Energy drain per second is equal to buildpower, except with the in-combat penalty in which case it is 25% of buildpower.
* Health regained per buildpower is proportional to the unit's health/cost.
* 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 {{UnitData getData|turretgauss|armoredRegen}} HP/s.

= Lists of units with passive regeneration =

=== Idle regeneration ===
{|
!Name!!Regen [HP/s]!!Timer [s]
|-
||[[Glaive]]||{{UnitData getData|cloakraid|idleRegen}}||{{UnitData getData|cloakraid|idleRegenTime}}
|-
||[[Locust]]||{{UnitData getData|gunshipraid|idleRegen}}||{{UnitData getData|gunshipraid|idleRegenTime}}
|-
||[[Kodachi]]||{{UnitData getData|tankraid|idleRegen}}||{{UnitData getData|tankraid|idleRegenTime}}
|-
||[[Reaver]]||{{UnitData getData|cloakriot|idleRegen}}||{{UnitData getData|cloakriot|idleRegenTime}}
|-
||[[Scythe]]||{{UnitData getData|cloakheavyraid|idleRegen}}||{{UnitData getData|cloakheavyraid|idleRegenTime}}
|-
||[[Claw]]||{{UnitData getData|wolverine_mine|idleRegen}}||{{UnitData getData|wolverine_mine|idleRegenTime}}
|-
||[[Chicken]]s||{{UnitData getData|chickens|idleRegen}}||{{UnitData getData|chickens|idleRegenTime}}
|-
||Other units||5||60
|}

=== Combat regeneration ===
{|
!Name!!Regen [HP/s]
|-
|[[Ultimatum]]||{{UnitData getData|striderantiheavy|combatRegen}}
|-
|[[Athena]]||{{UnitData getData|athena|combatRegen}}
|-
|[[Paladin]]||{{UnitData getData|striderbantha|combatRegen}}
|-
|[[Detriment]]||{{UnitData getData|striderdetriment|combatRegen}}
|-
|[[Commander|Strike Commander level 1<br/>Strike Commander level 2<br/>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]]||{{UnitData getData|amphcon|waterRegen}}||{{UnitData getData|amphcon|waterRegenDepth}}
|-
|[[Duck]]||{{UnitData getData|amphraid|waterRegen}}||{{UnitData getData|amphraid|waterRegenDepth}}
|-
|[[Archer]]||{{UnitData getData|amphimpulse|waterRegen}}||{{UnitData getData|amphimpulse|waterRegenDepth}}
|-
|[[Bulkhead]]||{{UnitData getData|amphsupport|waterRegen}}||{{UnitData getData|amphsupport|waterRegenDepth}}
|-
|[[Buoy]]||{{UnitData getData|amphfloater|waterRegen}}||{{UnitData getData|amphfloater|waterRegenDepth}}
|-
|[[Scallop]]||{{UnitData getData|amphriot|waterRegen}}||{{UnitData getData|amphriot|waterRegenDepth}}
|-
|[[Grizzly]]||{{UnitData getData|amphassault|waterRegen}}||{{UnitData getData|amphassault|waterRegenDepth}}
|-
|[[Angler]]||{{UnitData getData|amphaa|waterRegen}}||{{UnitData getData|amphaa|waterRegenDepth}}
|-
|[[Limpet]]||{{UnitData getData|amphbomb|waterRegen}}||{{UnitData getData|amphbomb|waterRegenDepth}}
|-
|[[Lobster]]||{{UnitData getData|amphlaunch|waterRegen}}||{{UnitData getData|amphlaunch|waterRegenDepth}}
|-
|[[Djinn]]||{{UnitData getData|amphtele|waterRegen}}||{{UnitData getData|amphtele|waterRegenDepth}}
|-
|}

{{Navbox manual}}

Model Guidelines

2025-11-24T11:53:08Z

Mach56: Add navbox

Here are some things to be aware of when creating new models for ZK.

== General Guidelines ==

* Aim for some consistency with the best models of a given class. Eg among units of a factory, or the set of turrets. A remodel of multiple things at once can get around this, but that is not where people tend to start.
* Try to maintain a consistent sense of scale. This is by no means uniform across ZK, but there is a rough absolute scale for things like flat plates, body molding, and greebles. The complexity of the model should try to match its contemporaries.
* Weapons should be large. Weapon orientation is the primary information and source of dynamism for a model. Units are viewed from a distance so even weapons that look too large close up in modelling software are probably fine.
* When creating a new model, consider the position of its weapons. Horizontally offset weapons can be tricky and end up firing at allies (eg Chainsaw).
* Ground cannot be wider or longer than Cyclops, which is why Striders mostly extend upwards.
* Structure footprints are rectangular. This should be accepted and even communicated to the player, but it can be communicated subtly. Eg Disco Rave Party is mostly round but has an octagonal base. Models should not hide the underlying mechanics.
* Fast units look fast, high health:cost units look tough, etc...

== Remake Guidelines ==

Be aware that models have a direct impact on game balance. We are not looking to rebalance Zero-K around new models at this point, so it can be good to ask around about a unit to determine its important characteristics. More care has to be taken for cheaper units as their balance tends to be tighter. Striders have quite a bit of room to move.
* The collision box of the model determines how easy it is to hit, so a remodel should be approximately the same size and shape.
* The footprint of a structure impacts how well raiders can dance around it, as well as how expensive it is to wall or put on a platform.
* Projectiles really come from the weapons they are fired from. The height and offset from which a weapon fires can be quite important.
* Aiming is a physical process that involves turning the model. It is safest to stick to he same skeleton if possible.
* If a unit has a special ability, such as gaining armour, then this should be reflected on the model.
* Don't add things to a unit that implies the existence of a non-existent special ability.

Models also imply things about the character of units. This is also good to maintain as balance shifts towards the visuals of the previous model to some degree.
* Healthy units are usually bulky.
* Units that turn or aim slowly should look cumbersome.

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

Zero-K:Developing

2025-11-24T11:53:01Z

Mach56: Add navbox

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. [//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 as shown: <gallery widths="329px">
Styleguide-if-example.JPG|Proper multiline if statement
Styleguide-stackflow.JPG|Example of stacked flow control
</gallery>
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).

== 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 [//notepad-plus-plus.org/download/ 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.

== Returning to default settings ==
Personalized config changes and widgets in-use can be reset for both the game and lobby.
* For the lobby, rename or remove the 'luamenu' folder from the base directory.
* To set in-game widgets and settings to default, rename or remove the 'luaui' folder from the base directory.

== 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.
*[[File:Startup projects.png|thumb|Startup projects setup.]] 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.
* 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|none]]
** 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:<br/><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.
**(As of June 2023) a few extra steps: in Visual Studio open Tools - Options - Projects and Solutions - Web Projects and tick "Use the 64 bit version of IIS Express...". In <code>ZkLobbyServer/ZkLobbyServer.cs</code> you may need to comment out the line <code>Task.Factory.StartNew(()=>ReplayStorage.Instance.MigrateReplays(), TaskCreationOptions.LongRunning);</code> currently on line 104.

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 ===
Unit infoboxes can now be automatically kept up to date using [[Template:Autoinfobox zkunit]]. See the template page and [[Module:UnitData]] for more information.

Unit buildicons and radar icons require manual uploading to the Zero-K website. (<code>zero-k.info/zkmanual/www/unitpics</code> and <code>/icons</code> respectively). If an icon is missing, poke Licho or Histidine to fix it. Alternatively, buildicons can be obtained directly from the GitHub CDN.

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

* Force push master to stable branch
* Go to zero-k.info engine list, click rebuild steam on current engine version

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

Manual/Coding

2025-11-24T11:52:01Z

Mach56:

* [[Cold Takes]] (design blog)
* [[Developing]]
* [[Animator GUI]]
* [[Widget Configuration]]
* [[Map Creation]]
* [[Model Guidelines]]
* [[ZK Map Making Guide]]
* [[Startbox API]]
* [[Mod Creation]]
* [[Custom Modes]]
* [[How To Play Mods]]
* [[Quick Stat Tweaks]]

Unit classes

2023-05-03T01:10:29Z

Mach56: Dagger has the scout icon now, so it doesn't fit in with the rest of the raiders.

Combat units in ZK generally fall into one of several classes. Understanding these roles and knowing how best to use and combine them for maximum effect is the cornerstone of a victorious battle in Zero-K.
{{TOC right}}

''Icons under titles indicate the role mapicon of that class. For further details, consult the [[Icons|Icon Guide]].''

== Raider ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/raider.png" height="64" width="64">

The raider emphasizes speed. They personify blitzkrieg tactics—sheer firepower and the speed needed to get it into the enemy's heartland. Raiders generally have a high DPS for their cost, but they also have poor armor and range. The primary uses for raiders are harassment attacks to interfere with an enemy's economy, brute-forcing a particularly weak point in the enemy's lines, and taking out inaccurate units such as artillery which cannot hit them. They also come in handy for scouting, although a dedicated scout is better for the task.

''Pro tip:'' The Unit AI can automatically micro your raiders to jink enemy shots if you give them an Attack Move order.

{|
!Use for:!!Counter with:
|-
|
*Early game rush
*Armed reconnaissance
*Flanking skirmisher/artillery/support units
*Rushing through breaches in defense
*Fast response vs. other raiders
|
*LLTs
*Antiswarm/riot units
*Area bombers
|}

'''Common examples''': [[Glaive]], [[Bandit]], [[Scorcher]], [[Pyro]], [[Blitz]], [[Duck]]

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/cloakraid.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/shieldraid.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/vehraid.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/jumpraid.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/tankheavyraid.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/amphraid.png

== Assault ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/assault.png" height="64" width="64">

Assault units rely on their high armor to tank damage. A useful mainline unit, the assault class is favored for its staying power and ease of use. They usually have fairly slow turrets and projectiles, making them better against slow, large, or static enemies than fast moving raiders or gunships. As its name suggests, the assault class excels at attacking enemy strong points.

{|
!Use for:!!Counter with:
|-
|
*Frontal assault
*Screening allied units
*Pushing in the field
*General confrontations
|
*Raiders(when unsupported)
*Skirmishers
*Bombers
*Gunships
*Crawling bombs
|}

'''Common examples''': [[Knight]], [[Thug]], [[Ravager]], [[Hermit]], [[Minotaur]]

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/cloakassault.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/shieldassault.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/vehassault.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/spiderassault.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/tankassault.png

== Skirmisher ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/skirm.png" height="64" width="64">

Skirmishers emphasize range. They support your forces by picking off enemies at a distance, before they can do damage. Skirms have light armor, and rely on their speed and range (as well as the protection of nearby friendlies) for defense. The strength of the skirmisher lies in its ability to shoot without fear of retaliation—always maximize this advantage by using the technique known as kiting (moving away as shorter-ranged enemies attempt to close the distance).

''Pro tip:'' Giving an Attack Move order to your skirmishers will have the Unit AI kite enemies automatically as needed.

{|
!Use for:!!Counter with:
|-
|
*Countering assaults
*Harassing enemy forward positions
*Countering Riots
*Picking off short-ranged turrets
|
*Raiders
*Crawling bombs (depends on skirm type)
*Gunships, area bombers
*Defenses that can outrange skirms
*Defend on high ground
|}

'''Common examples''': [[Ronin]], [[Rogue]], [[Recluse]], [[Moderator]], [[Scalpel]], [[Buoy]]

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/cloakskirm.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/shieldskirm.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/spiderskirm.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/jumpskirm.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/hoverskirm.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/amphfloater.png

== Riot ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/riot.png" height="64" width="64">

Riot units emphasize damage. They excel at crowd control, slaying huge amounts of lighter units such as raiders. Units of this class will either have a high rate of fire or a large AoE, sometimes both. On the flip side, riot units are slow and short-ranged, and are poorly suited for assaulting defenses (which get in a lot of free shots as the slow riot unit attempts to get close enough to fire) or fighting skirmisher groups (which will simply kite them).

Due to their high-velocity projectiles, some riot units can also pose a significant threat to attacking gunships.

{|
!Use for:!!Counter with:
|-
|
*Countering raider swarms
*Protecting ranged units
*Secondary AA (against gunships)
|
*Skirmishers
*Static defense
*Outmaneuvering/bypassing them
*Assaults(sometimes)
|}

'''Common examples''': [[Reaver]], [[Outlaw]], [[Ripper]], [[Mace]], [[Scallop]]

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/cloakriot.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/shieldriot.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/vehriot.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/hoverriot.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/amphriot.png

== Artillery ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/LRarty.png" height="64" width="64">

Artillery units are generally used to pick off enemy structures from a safe distance. Easily outranging static defenses, artillery can destroy them with impunity. Mobile units can usually dodge the fire of most (but not all) artillery, and artillery units tend to be completely helpless when attacked directly.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/arty.png" height="64" width="64">

The alternate artillery icon is used when a factory has 2 artillery pieces that need separate icons. The heavier artillery will use the vertical icon.
{|
|-
!Use for:!!Counter with:
|-
|
*Killing defenses
*Causing attrition at range
|
*Most other ground and air units
|}

'''Common examples''': [[Sling]], [[Badger]], [[Impaler]], [[Firewalker]], [[Emissary]], [[Tremor]]

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/cloakarty.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/veharty.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/vehheavyarty.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/jumparty.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/tankarty.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/tankheavyarty.png

== Scout ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/scout.png" height="64" width="64">

Scout units emphasize speed. They have extreme speed and good visual range, and their dirt-cheap cost makes them expendable—just as well considering that they have no armor to speak of whatsoever. Scouts tend to be only very lightly armed, but they can still kill undefended economy structures and support units if the enemy isn't careful. Scouts are very similar to raiders in their role.
{|
!Use for:!!Counter with:
|-
|
*Checking enemy unit composition
*Finding cloakers
*Killing undefended expansion
|
*Raiders
*Riots
*Light defense
|}

'''Common examples''': [[Flea]], [[Dart]], [[Puppy]]

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/spiderscout.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/vehscout.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/jumpscout.png

== Anti-Air ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/aa.png" height="64" width="64">

Anti-air units exist for one purpose—defend your army from aircraft. Their high firepower and range allows them to destroy enemy aircraft before they can damage your forces, but they are of course useless against any other target.
{|
!Use for:!!Counter with:
|-
|
*Countering aircraft
|
*Ground combat units
|}

'''Common examples''': [[Gremlin]], [[Vandal]], [[Crasher]], [[Toad]], [[Tarantula]], [[Ettin]], [[Flail]], [[Angler]]

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/cloakaa.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/shieldaa.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/vehaa.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/jumpaa.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/spideraa.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/tankaa.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/hoveraa.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/amphaa.png

== Support ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/support.png" height="64" width="64">

Support units provide long ranged fire support but for some reason or another do not fit into the skirmisher role. They generally have low DPS. The actual roles of these units are too diverse to fit in a little table. There are three units that are labeled as support: [[Fencer]], [[Lance]] and [[Felon]]. The Fencer is very accurate but must stop to fire, so it is easily beaten by assaults. The Lance has massive long-range burst damage so it is effective against high cost units. The Felon discharges its shield as energy bolts and works best when linked to other shields.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/vehsupport.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/hoverarty.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/shieldfelon.png

== Constructor ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/builder.png" height="64" width="64">

Produces structures to improve your economy, provide your base with defense, and to expand. Constructors can provide an edge in battle by repairing damaged units, and reclaiming metal-filled wrecks to recover up to 40% of a unit's original value. Constructors can also assist other builders with construction. Maps may also have metal-filled features such as rocks available to reclaim that can boost your economy.
{|
!Use for:!!Counter with:
|-
|
*Building economy and defenses
*Reclaiming and denying reclaim
*Repair support for armies
*Building forward bases
|
*Raiders when undefended
*Small groups of scouts
|}
'''Common examples''': [[Conjurer]], [[Convict]], [[Mason]]

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/cloakcon.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/shieldcon.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/vehcon.png

== Mobile Bombs ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/special.png" height="64" width="64">

Mobile bombs move up to enemy units and explode causing massive damage. They do well against inaccurate units in clumps. Raiders can beat mobile bombs because while the raider will die, the bomb often costs more than the raider. Mobile bombs are particularly effective when combined with a cloaker.

''Pro tip:'' The Unit AI can automatically micro your bombs to jink enemy shots if you give them an Attack Move order.

''Note:'' The star icon is also used for some special abilities.
{|
!Use for:!!Counter with:
|-
|
*Countering Skirmishers
*Countering Assaults
*Countering clusters of units
|
*Raiders
*Scouts
*Accurate units
*[[Picket]]s
|}

'''Common examples''': [[Imp]], [[Snitch]], [[Skuttle]]

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/cloakbomb.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/shieldbomb.png
https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/jumpbomb.png

== Shield ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/shield.png" height="64" width="64">

[[Shields]] provide a defensive bubble that blocks enemy projectiles. Shields are good at blocking (limited) burst damage or low DPS sustained attacks. They will fall to focus from artillery.
{|
!Use for:!!Counter with:
|-
|
*Protecting advancing units
*Protection against bombers
*Protection against [[Big Bertha]]s
*Some breathing room against artillery
|
*Raiders (get inside the shield)
*High DPS/Burst damage units
*Focus fire from artillery
*EMP/Disarm
|}

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/shieldshield.png

== Cloaker ==
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/jammer.png" height="64" width="64">

Cloakers hide your units from the enemy, see [[Cloak]] for more details. Cloaked units will decloak if collided with or if they fire, this makes cheap expendable units ideal for finding cloakers. Cloaked units also decloak if they are damaged which makes units with large AOE very effective at finding them. The [[Firewalker]] is particularly effective as the fire persists preventing units from recloaking. If you think you know where an enemy cloaker is Pro tip to force fire your artillery at that location.
{|
!Use for:!!Counter with:
|-
|
*Sneaking into bases
*Closing the range against defenses for low range units
*Hiding economy (only works until it's scouted)
*Hiding defenses(only works until they fire)
|
*Raiders
*Scouts
*AOE artillery (e.g.: Firewalker or [[Tremor]])
|}

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/cloakjammer.png

----

These classes are generalized; specific units will often have different properties that cause their behavior to deviate significantly from the general archetype!
That said, it is generally a good idea to have a pack of units of EACH major class on the battlefield. Typically, at least skirmishers and riot should be present. A small pack of raiders (about 10) can come in handy to rush through openings in enemy lines or shock an enemy skirmisher/artillery group. Since they are the cheapest units it will typically be quite effective, because your enemy might not expect you to get through really fast.

{{Navbox manual}}

Airplane Plant

2022-11-17T11:27:32Z

Mach56: /* Bombing Mechanics */ Raven no longer dives.

The '''{{PAGENAME}}''' is a factory that produces airplanes.{{ Infobox zkunit
| name = Airplane Plant
| defname = factoryplane
| description = Produces Airplanes
| image = http://manual.zero-k.info/unitpics/factoryplane.png
| icontype = facair
| cost = 700
| hitpoints = 4000
| sight = 273
| abilities =
{{ Infobox zkability construction
| buildpower = 10
}}
}}==Description==
The Airplane Plant offers a variety of fixed-wing aircraft to suit your needs. Choose between multi-role fighters that can double as light attackers or specialized interceptors, and between precision bombers for taking down specific targets or their saturation counterparts for destroying swarms. The plant also comes bundled with one rearm pad.

The Airplane Plant builds:<dl>
{{icon unit def|planecon|Crane|Construction Aircraft}}
{{icon unit def|fighter|Swift|Multi-role Fighter}}
{{icon unit def|planeheavyfighter|Raptor|Air Superiority Fighter}}
{{icon unit def|bomberprec|Raven|Precision Bomber}}
{{icon unit def|bomberriot|Phoenix|Saturation Napalm Bomber}}
{{icon unit def|bomberdisarm|Thunderbird|Disarming Lightning Bomber}}
{{icon unit def|bomberheavy|Likho|Singularity Bomber}}
{{icon unit def|planescout|Owl|Radar/Sonar Plane}}
{{icon unit def|planelightscout|Sparrow|Light Scout Plane}}
</dl>{{clear}}
==Tactics and Strategy==

The Airplane Plant provides the most unique array of units of any factory in Zero-K; the Planes are more like a support force, as opposed to combat units. Both the speed of the Planes and their first-strike capability is unparalleled. The Swift is the Planes' main air-to-air option, while the Raven, Thunderbird and Likho bombers punish any poorly-covered ground forces.

In contrast to the Gunships, the Airplane bombers deliver their damage in a very short period of time, so anti-air which relies on prolonged engagements is less effective against them. On the other hand, the bombers have to return to base and rearm before making another run. The Swift fighter relies on similar hit-and-run tactics against enemy air forces.

=== Example Unit Combinations ===

Once your fleet of Swifts is large enough, add a few Raptors for more sustained damage. Make sure your Swifts are in position to protect the Raptors' flank and rear.

Fly a Swift or two over enemy territory before a bombing run to soak up a few missiles and scout for an unexpected concentration of anti-air. Losing a Swift or two is far less painful than losing a Likho.

Follow up a Thunderbird strike with swift ground units such as the [[Glaive]] or [[Scorcher]] to capitalise while the enemy is disarmed.

Use Owls to scout for your artillery pieces like the [[Sling]], [[Emissary]] or [[Lance]].

Owls jam enemy radar in an area around and below them. Order a line of Owls to fly circles behind your team's front lines to provide radar, line of sight, and to hide your allies from enemy radar.

=== Bombing Mechanics ===

The Airplane Plant provides its owner with access to four bombers, being the [[Raven]], [[Phoenix]], [[Thunderbird]], and [[Likho]]. Upon attacking they will drop their payload, which differs between the different types of bomber.

*The [[Raven]] will drop a single gliding bomb, dealing 800 damage.
*The [[Phoenix]] will drop 15 napalm bomblets, each doing 25 damage on impact and another 150 damage per unit hit as it burns. The bomblets are dropped over a wide area, which means small units may dodge the majority of bomblets, whereas large groups may be hit multiple times.
*The [[Thunderbird]] releases disarming lightning from its belly towards the ground in a line, with the center of the line at the ordered point of attack or target unit. The Thunderbird is free to change direction while firing, and can be manually fired (default 'D').
*The [[Likho]] drops a single homing implosion bomb dealing approximately 2000 damage.

The four different bombers will move differently during their payload release. As mentioned above, [[Thunderbird]]s will happily continue flying in a straight line unless ordered not to. The [[Phoenix]] is the exact opposite, and will prefer to drop its payload in a J-shape unless given a move order to continue on in the direction it came from. The [[Likho]] launches its bomb at 500 range before turning around immediately. The [[Raven]] will simply drop its bomb and turn around.

After releasing their payload, bombers will seek out the closest [[Airpad]], Airplane Plant, or [[Reef]] aircraft carrier to rearm. If they are given a move order after attacking, either by putting a move order into their command queue or by manually ordering them to move, they will first complete their move order before proceeding to a repair pad. If they are instead given a second attack order, they will first return to a repair pad to rearm before executing this attack.

=== Bombing Strategy and Tactics ===

====General tips:====

*When selecting Ravens and Likhos, a line on the right of the selection panel will inform you about how much damage your total selection can perform in one run (Burst Damage). Use this to gauge whether your currently selected bomber wing can destroy the high value target of your choosing (A default strike commander, for example, takes 4 Ravens).
*Use move orders after bombing to make your bombers take the shortest way out of enemy anti-air coverage. Often it is safer to make a 90 degree turn and fly out to the side than to turn the full 180 degrees inside enemy anti-air cover.
*Raven bombs will pass through water surfaces, allowing you to bomb submerged units. Phoenix bomblets explode on the surface.
*Owls provide sonar coverage as well as radar, making them invaluable for spotting submerged units.
*Be careful bombing around EMP units such as [[Venom]]s or [[Faraday]]s! Stunned planes will slowly drift down to the ground, where they can be shot to pieces by any old unit that happens by.
*Using the 'Force fire' command (Default {{key press|F}}), and holding down the left mouse button allows you to draw a circle. Release to order your bombers to attack enemy units inside this circle in turn.
*Hold down {{key press|Ctrl}} while issuing the above command to tell your bombers to pick a unit inside the circle to bomb. This distributes your bombers between units. It is especially useful against [[Lotus]]es, [[Picket]]s, or light mobile units which all do not warrant multiple [[Raven]] bombs. Consider using this with [[Phoenix]]es to spread them over a larger mass of enemy units.
*Use the Area Attack command (Default {{key combo|Alt|A}}) to designate an area in which to bomb. When enemy units enter this area, they will be bombed by your bombers. When there are no enemy units to be found, your bombers will bomb random points of terrain in the area. Consider combining with [[Phoenix]]es to hunt down suspected cloaked units.

==== Raven tips: ====

[[Raven]]s are the workhorse of the Airplane Plant. They're the cheapest bombers, they deal a lot of damage, and have the most hit points for their cost.
*Sometimes it's worth it to channel your inner World War 2 British bomber command officer and sacrifice some of your Ravens to take out an important enemy target. With five ravens you can bomb a [[Razor]] anti air turret to pave the way for more bombers to follow them. Or you can strike at a [[Singularity Reactor]] deep within enemy territory. If five of your bombers make it through, you will cripple your enemy's economy and perhaps take out a large portion of their base. Or if your allies are facing a particularly deadly unit, like a [[Dante]], you could turn the tide in favour of your allies with a well-timed bomb run.
*If your enemy pushes out from under their AA cover, a quick wing of Ravens using the spread attack command (Default {{key combo|Ctrl|A}}) can quickly soften the enemy units up for a follow-up by ground forces, or take care of the units on their own if used in sufficient numbers.

==== Phoenix tips: ====

[[Phoenix]]es are more vulnerable than other bombers. They are also more dangerous to vulnerable units.
*While the low initial damage of the Phoenix is underwhelming, the 10-second burn can make quick work of lighter units like [[Dart]]s even when they dodge most initial damage.
*Burn damage will reset the countdown for units with regenerative abilities like [[Glaive]]s or [[Reaver]]s, as well as keep units with a cloak from disappearing from sight.
*Be careful when using Phoenixes around allied units, as the same properties that make them useful against enemy hordes make them a liability in a chaotic front line.

==== Thunderbird tips: ====

[[Thunderbird]]s do not deal damage themselves, but provide utility on the battlefield that can make the difference between a successful assault or a complete catastrophe.
* If you can spare the time to micro, it is often much more effective to manually give your Thunderbird move orders and to deploy its lightning attack (Default {{key press|D}}) when it is going to be most effective.
* Do not hesitate to inform your team that you're about to disarm the units they're fighting, so they can rush them just as you finish your attack run.
* Be careful not to fly over allied units on your attack run. There's not much point to disarming your enemies if your allies are also disarmed. Though sometimes it can be worth it just to buy your team some time to react.

==== Likho tips: ====

The [[Likho]] is your heavy-duty end-game bomber. It can survive enemy fire that would destroy two [[Raven]]s, but costs as much as 6.5 of them. Depending on what you find yourself having to deal with, you may be better off with more Ravens!

*The Likho is especially useful against units that like to clump together into balls, like units from the [[Shieldbot Factory]], [[Ravager]]s, and [[Blitz]]es.
*The Likho's large cost means that it's a prime target for reclamation if you do lose it. Try not to lose it over enemy territory! If possible, lose it as close to your own front lines as you can! Better still, do not lose it at all.
*The homing bomb of the Likho means it's much less likely to miss moving targets than the bombs the Raven drops. This also means it doesn't have to get so close to the enemy and can be more safely used against units with low range but high damage like [[Reaver]]s, [[Mace]]s, or [[Ogre]]s.

=== Beating Airplanes ===

Anti-air units or structures which deliver high burst damage are generally more effective against Planes than those with sustained damage. The [[Picket]] is generally preferred over the [[Hacksaw]] due to its larger range and flexibility to engage ground targets. The range of the [[Chainsaw]] and [[Artemis]] makes them effective against any air threat, though they are more expensive.

You'll generally need a few mobile anti-air units to shoot down bombers, although the [[Flail]], [[Crasher]], [[Vandal]] and [[Angler]]'s high burst damage is helpful here.

The most important thing to keep in mind when playing against Planes is not to over-extend. Valuable units may be sniped by Ravens, and if you move a large raiding group or army beyond the range of your anti-air it will likely be disarmed by a Thunderbird and destroyed. Don't stick anything outside anti-air range unless you're prepared to lose it. The best defence against bombers is to have your own Swift planes, since they are fast enough to defend you anywhere on the map.

If you are using Gunships against a player with Planes, don't move your anti-ground gunships away from anti-air protection unless you're prepared to lose them. Try to make the Airplane player engage you in a direct fight, since your air-to-air units are tougher than theirs.

If you are playing the Airplane mirror match-up, try to have more Swifts than they do, while still making things happen in the ground war using the cheaper bombers if you can (Raven, Phoenix and Thunderbird). Hold your Swift boost in reserve as long as possible to counter enemy bombing runs or to escape from a losing fighter battle.

{{Navbox buildings}}

Map icons

2022-11-17T11:10:45Z

Mach56: /* Other units */ The Lance no longer uses that icon.

ZK uses a unique '''icon''' system, assigning each unit class and chassis a specific map icon. You can see these icons when you zoom out enough.
{{TOC right}}[[File:mapicons.jpg]]

Needless to say, these icons can be rather confusing, even intimidating, to the new user. Fortunately, they're actually very simple, and this guide will explain them to you.

== General ==
The icon system is mostly modular; an icon indicating a unit role is superimposed on an icon representing a chassis type (bot, vehicle, etc.)

Thus a raider rover is
<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/vehicleraider.png" height="64" width="64">
and an artillery tank is
<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/tankarty.png" height="64" width="64">

{|
! Chassis icon !! Type !! Chassis icon !! Type
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/kbot.png" height="64" width="64"> || Cloakbot ||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/vehicle.png" height="64" width="64"> ||Rover
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/walker.png" height="64" width="64"> ||Shieldbot ||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/tank.png" height="64" width="64"> ||Tank
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/jumpjet.png" height="64" width="64"> ||Jumpjet ||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/spider.png" height="64" width="64"> ||Spider
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/ship.png" height="64" width="64"> ||Ship ||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/hover.png" height="64" width="64"> ||Hover
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/hover2.png" height="64" width="64"> ||Amph || <img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/air.png" height="48" width="48"> ||Aircraft
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/t3.png" height="64" width="64"> ||Strider||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/gunship.png" height="64" width="64">||Gunship
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/defense.png" height="64" width="64"> ||Defense ||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/static.png" height="48" width="48"> ||Static
|}

{|
! Role icon !! Type !! Role icon !! Type
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/raider.png" height="64" width="64"> ||Raider ||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/assault.png" height="64" width="64"> ||Assault
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/skirm.png" height="64" width="64"> ||Skirmisher ||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/riot.png" height="64" width="64"> ||Riot
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/arty.png" height="64" width="64"> ||Artillery ||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/aa.png" height="64" width="64"> ||Anti-air
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/scout.png" height="64" width="64"> ||Scout ||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/LRarty.png" height="64" width="64"> ||Long range arty
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/radar.png" height="64" width="64"> ||Radar || <img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/bomb.png" height="64" width="64"> ||Bomb/special
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/jammer.png" height="64" width="64"> ||Jammer|| <img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/shield.png" height="64" width="64"> ||Shield
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/support.png" height="64" width="64"> ||Ranged Support||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master/MapIconBuilder/MapIcons/2_Class/transport.png" height="64" width="64"> ||Transport
|-
| <img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/antinuke.png" height="64" width="64"> ||Anti-Nuke|| ||
|}

== Static Defense ==
Static defenses use the normal icon system, though the roles don't correspond exactly. The exception is the Heavy SAM icon used by the long-ranged missile tower, the Artemis.

{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseraider.png" height="64" width="64">||[[Lotus]] (LLT)||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseassault.png" height="64" width="64">||[[Stinger]] (HLT)
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseskirm.png" height="64" width="64">||[[Picket]]||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseriot.png" height="64" width="64">||[[Stardust]]
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defensespecial.png" height="64" width="64">||[[Faraday]]<br/>[[Newton]]||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseaa.png" height="64" width="64">||[[Razor]]
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/staticaa.png" height="64" width="64">||[[Thresher]] (flak)||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/heavysam.png" height="64" width="64">||[[Artemis]]
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/fixedtachyon.png">||[[Lucifer]]||<img src=//raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/icons/staticassaultriot.png height="64" width="64">||[[Desolator]]
|}

== Factories ==
Factories use the chassis icon of the units they build superimposed on the static building icon.

{|
! Icon !! Class !! Icon !! Class
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statickbot.png" height="64" width="64">||Cloakbot||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticvehicle.png" height="64" width="64">||Rover
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticwalker.png" height="64" width="64">||Shieldbot||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statictank.png" height="64" width="64">||Tank
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticjumpjet.png" height="64" width="64">||Jumper||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticspider.png" height="64" width="64">||Spider
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticair.png" height="64" width="64">||Airplane||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/facgunship.png">||Gunship
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statichover.png" height="64" width="64">||Hover||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticship.png" height="64" width="64">||Ship
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statichover2.png" height="64" width="64">||Amph||||
|}

Usually, however, the factory's icon will be obscured by the icon of whatever it's building.

== Econ Buildings ==

{|
! Icon !! Unit
|-
|style = "text-align:center;" | <img src="//manual.zero-k.info/icons/mex.png" height="48" width="48"/> ||[[Metal Extractor]]
|-
|style = "text-align:center;" | <img src="//manual.zero-k.info/icons/energywind.png" height="64" width="64"/>||[[Wind/Tidal Generator]]
|-
|<img src="//manual.zero-k.info/icons/energy_med.png" height="64" width="64"/>||[[Solar Collector]]
|-
|<img src="//manual.zero-k.info/icons/energygeo.png" height="64" width="64"/>||[[Geothermal Generator]]
|-
|<img src="//manual.zero-k.info/icons/energyfusion.png">||[[Fusion Reactor]]
|-
|<img src="//manual.zero-k.info/icons/energyheavygeo.png" height="64" width="64"/>||[[Advanced Geothermal]]
|-
|<img src="//manual.zero-k.info/icons/energysingu.png">||[[Singularity Reactor]]
|-
|<img src="//manual.zero-k.info/icons/pylon.png">||[[Energy Pylon]]
|}

== Aircraft ==
Although aircraft do have a chassis icon, they generally use pictographic icons, as below:

{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/fighter.png">||Multirole fighter||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/stealthfighter.png" height="64" width="64">||Dedicated fighter
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bomberassault.png">||Precision bomber||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bomberraider.png">||Napalm bomber
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bomberriot.png">||EMP bomber||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bombernuke.png">||Implosion bomber
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/radarplane.png">||Radar plane|| ||
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/gunship.png">||Light gunship||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/heavygunship.png">||Heavy gunship
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/airbomb.png">||Blastwing|| ||
|}

== Ships ==
Like aircraft, ships use pictographic icons.
{|
! Icon !! Unit
! Icon !! Unit
! Icon !! Unit
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/scoutboat.png" height="64" width="64">||[[Cutter]]
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/hunter.png" height="80" width="80">||[[Hunter]]
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/corvette.png" height="80" width="80">||[[Corsair]]
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/enforcer.png" height="80" width="80">||[[Mistral]]
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/aaboat.png" height="80" width="80">||[[Zephyr]]
|<img src="//manual.zero-k.info/icons/shipassault.png" height="80" width="80">||[[Siren]]
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/destroyer.png" height="80" width="80">||[[Envoy]]
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/carrier.png" height="96" width="96">||[[Reef]]
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/battleship.png" height="96" width="96">||[[Shogun]]
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/submarine.png" height="80" width="80">||[[Seawolf]]
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/missilesub.png" height="80" width="80">||[[Scylla]]
| ||
|}

== Misc. Units ==
Many units have specific icons that reflect their unique roles, particularly superweapons such as Big Berthas and Trinities.

=== Superweapons ===
{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/cruisemissile.png">||Cruise missile||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/lrpc.png">||[[Big Bertha]]
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/nuke.png">||[[Trinity]]||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/mahlazer.png">||[[Starlight]]
[[Zenith]]

[[Disco Rave Party]]
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/krogoth.png">||[[Detriment]]||||
|}

=== Other units ===
{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/builder.png">||Constructor||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/builderair.png">||Aircon
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/icons/clogger.png" height="64" width="64"/>||[[Dirtbag]]||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/mine.png">||[[Claw|Mine]]
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/sniper.png">||[[Phantom]]||<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/armcommander.png">||[[Commander]]
|-
|<img src="//raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/chickenq.png">||[[Chicken Queen]]||||
|}

{{Navbox manual}}

Template talk:Navbox changelog

2022-07-20T08:37:46Z

Mach56:

TO DO:
* Add dates of release to each page.
* Make navbox in chronological order. This out of order navbox is annoying me.
* Possibly make a [[changelog]] page OR a little infobox on the side of the page that gives a quick summery/goal of major changes in each patch. ("This patch tried to balance hovers", "Bug fix patch", etc)
* '''ENSURE ALL PAGES ACTUALLY CONTAIN THE NAVBOX''' (I've caught a few of them that lacked it)
* Update patch notes to new editing style (See [[v1.2.12.0]] for example)
** Forum post tags are ugly.

--[[User:Shaman|Shaman]] ([[User talk:Shaman|talk]]) 13:12, 8 January 2019 (CET)

== Section numbering ==

Would there be any negative side effects from making 2013 the first section and just adding a new one every year (as opposed to renumbering all of them every year)? —[[User:RandomX|RandomX]] ([[User talk:RandomX|talk]]) 20:46, 9 July 2022 (PDT)

:I don't think so. Might be a good idea to ask one of the admins/mods first if that is what would be preferred. --[[User:Mach56|Mach56]] ([[User talk:Mach56|talk]]) 01:17, 20 July 2022 (PDT)

== Bundling patches together ==

Should we just bundle all the .Y.XX versions together onto a single page? Some earlier ones seem to be single line changes, no reason for each of those to have its own page. The more filled out ones will create a large page, but I think that's a fair price to pay to not have 20 pages for all the 1.6.1.XX versions.

Template:Navbox changelog

2022-07-20T08:33:25Z

Mach56: Slightly more exhaustive search for missing changes by searching for "VERISON{1" on github instead of checking the titles of forum posts. Was only on the game repo and not the others, only went to 2018, there's still more.

{{Navbox
| name = Navbox changelog
| title = Changelog
| state = uncollapsed
| listclass = hlist

| group1 = 2022
| list1 =
* [[v1.10.1.0]]
* [[v1.10.1.1]]
* [[v1.10.1.3]]
* [[v1.10.1.4]]
* [[v1.10.1.5]]
* [[v1.10.1.6]]
* [[v1.10.1.7]]
* [[v1.10.4.0]]
* [[v1.10.4.1]]
* [[v1.10.5.0]]
* [[v1.10.6.0]]
* [[v1.10.7.0]]

| group2 = 2021
| list2 =
* [[v1.9.1.0]]
* [[v1.9.1.1]]
* [[v1.9.2.0]]
* [[v1.9.3.0]]
* [[v1.9.3.1]]
* [[v1.9.4.1]]
* [[v1.9.6.0]]
* [[v1.9.6.1]]
* [[v1.9.6.5]]
* [[v1.9.8.0]]
* [[v1.9.9.0]]
* [[v1.9.9.1]]
* [[v1.9.11.0]]
* [[v1.9.11.1]]
* [[v1.9.12.0]]

| group3 = 2020
| list3 =
* [[v1.8.2.1]]
* [[v1.8.2.3]]
* [[v1.8.3.0]]
* [[v1.8.3.1]]
* [[v1.8.3.2]]
* [[v1.8.4.0]]
* [[v1.8.4.1]]
* [[v1.8.4.2]]
* [[v1.8.4.3]]
* [[v1.8.4.4]]
* [[v1.8.4.5]]
* [[v1.8.5.0]]
* [[v1.8.5.1]]
* [[v1.8.5.3]]
* [[v1.8.7.0]]
* [[v1.8.7.1]]
* [[v1.8.8.1]]
* [[v1.8.8.2]]
* [[v1.8.9.1]]
* [[v1.8.9.4]]
* [[v1.8.10.0]]
* [[v1.8.11.1]]
* [[v1.8.11.3]]
* [[v1.8.12.0]]
* [[v1.8.12.1]]

| group4 = 2019
| list4 =
* [[v1.7.2.0]]
* [[v1.7.2.1]]
* [[v1.7.3.1]]
* [[v1.7.3.4]]
* [[v1.7.3.5]]
* [[v1.7.3.8]]
* [[v1.7.4.1]]
* [[v1.7.5.1]]
* [[v1.7.6.0]]
* [[v1.7.6.1]]
* [[v1.7.7.0]]
* [[v1.7.8.1]]
* [[v1.7.8.2]]
* [[v1.7.9.0]]
* [[v1.7.9.1]]
* [[v1.7.10.0]]
* [[v1.7.11.0]]
* [[v1.7.11.1]]
* [[v1.7.11.4]]

| group5 = 2018
| list5 =
* [[v1.6.1.0]]
* [[v1.6.1.1]]
* [[v1.6.1.2]]
* [[v1.6.1.3]]
* [[v1.6.1.4]]
* [[v1.6.1.5]]
* [[v1.6.1.6]]
* [[v1.6.1.7]]
* [[v1.6.1.8]]
* [[v1.6.1.9]]
* [[v1.6.1.10]]
* [[v1.6.1.11]]
* [[v1.6.1.12]]
* [[v1.6.1.13]]
* [[v1.6.1.14]]
* [[v1.6.1.15]]
* [[v1.6.1.16]]
* [[v1.6.1.17]]
* [[v1.6.1.18]]
* [[v1.6.1.19]]
* [[v1.6.2.1]]
* [[v1.6.2.3]]
* [[v1.6.2.9]]
* [[v1.6.2.10]]
* [[v1.6.2.14]]
* [[v1.6.3.1]]
* [[v1.6.3.2]]
* [[v1.6.3.5]]
* [[v1.6.4.1]]
* [[v1.6.5.0]]
* [[v1.6.5.1]]
* [[v1.6.5.2]]
* [[v1.6.5.5]]
* [[V1.6.5.6]]
* [[v1.6.7.0]]
* [[v1.6.7.1]]
* [[v1.6.7.2]]
* [[v1.6.7.3]]
* [[v1.6.9.0]]
* [[v1.6.10.0]]
* [[v1.6.11.1]]
* [[v1.6.11.3]]
* [[V1.6.12.0]]

| group6 = 2017
| list6 =
* [[v1.5.1.5]]
* [[v1.5.1.11]]
* [[v1.5.2.5]]
* [[v1.5.2.20]]
* [[v1.5.2.24]]
* [[v1.5.3.2]]
* [[v1.5.3.4]]
* [[v1.5.4.0]]
* [[v1.5.4.4]]
* [[v1.5.4.11]]
* [[v1.5.5.0]]
* [[v1.5.6.0]]
* [[v1.5.7.1]]
* [[v1.5.7.8]]
* [[v1.5.8.2]]
* [[v1.5.9.3]]
* [[v1.5.10.2]]
* [[v1.5.11.1]]
* [[v1.5.11.6]]
* [[v1.5.11.9]]

| group7 = 2016
| list7 =
* [[v1.4.2.5]]
* [[v1.4.2.8]]
* [[v1.4.2.14]]
* [[v1.4.3.3]]
* [[v1.4.4.0]]
* [[v1.4.5.0]]
* [[v1.4.6.0]]
* [[v1.4.7.0]]
* [[v1.4.9.2]]
* [[v1.4.11.0]]
* [[v1.4.11.15]]
* [[v1.4.12.7]]
* [[v1.4.12.15]]

| group8 = 2015
| list8 =
* [[v1.3.1.1]]
* [[v1.3.1.5]]
* [[v1.3.1.8]]
* [[v1.3.1.12]]
* [[v1.3.1.15]]
* [[v1.3.1.17]]
* [[v1.3.4.1]]
* [[v1.3.5.1]]
* [[v1.3.6.0]]
* [[v1.3.6.1]]
* [[v1.3.7.1]]
* [[v1.3.8.5]]
* [[v1.3.8.7]]
* [[v1.3.8.12]]
* [[v1.3.9.0]]
* [[v1.3.10.0]]
* [[v1.3.11.3]]
* [[v1.3.12.1]]

| group9 = 2013
| list9 =
* [[v1.2.1.0]]
* [[v1.2.1.1]]
* [[v1.2.2.9]]
* [[v1.2.3.0]]
* [[v1.2.3.7]]
* [[v1.2.4.0]]
* [[v1.2.4.9]]
* [[v1.2.6.0]]
* [[v1.2.7.0]]
* [[v1.2.9.0]]
* [[v1.2.11.0]]
* [[v1.2.12.0]]

}}

Template:Navbox changelog

2022-07-20T08:19:08Z

Mach56: 1.10.7.0 happened, but it wasn't posted on the forum

{{Navbox
| name = Navbox changelog
| title = Changelog
| state = uncollapsed
| listclass = hlist

| group1 = 2022
| list1 =
* [[v1.10.1.0]]
* [[v1.10.1.5]]
* [[v1.10.4.0]]
* [[v1.10.5.0]]
* [[v1.10.6.0]]
* [[v1.10.7.0]]

| group2 = 2021
| list2 =
* [[v1.9.1.0]]
* [[v1.9.2.0]]
* [[v1.9.3.0]]
* [[v1.9.4.1]]
* [[v1.9.6.0]]
* [[v1.9.6.5]]
* [[v1.9.8.0]]
* [[v1.9.9.0]]
* [[v1.9.9.1]]
* [[v1.9.11.0]]
* [[v1.9.12.0]]

| group3 = 2020
| list3 =
* [[v1.8.2.3]]
* [[v1.8.3.0]]
* [[v1.8.3.1]]
* [[v1.8.3.2]]
* [[v1.8.4.0]]
* [[v1.8.4.4]]
* [[v1.8.4.5]]
* [[v1.8.5.0]]
* [[v1.8.7.0]]
* [[v1.8.8.2]]
* [[v1.8.9.1]]
* [[v1.8.9.4]]
* [[v1.8.10.0]]
* [[v1.8.11.1]]
* [[v1.8.11.3]]
* [[v1.8.12.0]]
* [[v1.8.12.1]]

| group4 = 2019
| list4 =
* [[v1.7.2.0]]
* [[v1.7.3.1]]
* [[v1.7.3.4]]
* [[v1.7.3.5]]
* [[v1.7.3.8]]
* [[v1.7.6.0]]
* [[v1.7.7.0]]
* [[v1.7.8.2]]
* [[v1.7.9.0]]
* [[v1.7.10.0]]
* [[v1.7.11.0]]
* [[v1.7.11.4]]

| group5 = 2018
| list5 =
* [[v1.6.1.6]]
* [[v1.6.2.3]]
* [[v1.6.2.9]]
* [[v1.6.2.10]]
* [[v1.6.2.14]]
* [[v1.6.3.2]]
* [[v1.6.3.5]]
* [[v1.6.5.0]]
* [[v1.6.5.1]]
* [[v1.6.5.2]]
* [[v1.6.5.5]]
* [[V1.6.5.6]]
* [[v1.6.7.3]]
* [[v1.6.9.0]]
* [[v1.6.10.0]]
* [[v1.6.11.3]]
* [[V1.6.12.0]]

| group6 = 2017
| list6 =
* [[v1.5.1.5]]
* [[v1.5.1.11]]
* [[v1.5.2.5]]
* [[v1.5.2.20]]
* [[v1.5.2.24]]
* [[v1.5.3.2]]
* [[v1.5.3.4]]
* [[v1.5.4.0]]
* [[v1.5.4.4]]
* [[v1.5.4.11]]
* [[v1.5.5.0]]
* [[v1.5.6.0]]
* [[v1.5.7.1]]
* [[v1.5.7.8]]
* [[v1.5.8.2]]
* [[v1.5.9.3]]
* [[v1.5.10.2]]
* [[v1.5.11.1]]
* [[v1.5.11.6]]
* [[v1.5.11.9]]

| group7 = 2016
| list7 =
* [[v1.4.2.5]]
* [[v1.4.2.8]]
* [[v1.4.2.14]]
* [[v1.4.3.3]]
* [[v1.4.4.0]]
* [[v1.4.5.0]]
* [[v1.4.6.0]]
* [[v1.4.7.0]]
* [[v1.4.9.2]]
* [[v1.4.11.0]]
* [[v1.4.11.15]]
* [[v1.4.12.7]]
* [[v1.4.12.15]]

| group8 = 2015
| list8 =
* [[v1.3.1.1]]
* [[v1.3.1.5]]
* [[v1.3.1.8]]
* [[v1.3.1.12]]
* [[v1.3.1.15]]
* [[v1.3.1.17]]
* [[v1.3.4.1]]
* [[v1.3.5.1]]
* [[v1.3.6.0]]
* [[v1.3.6.1]]
* [[v1.3.7.1]]
* [[v1.3.8.5]]
* [[v1.3.8.7]]
* [[v1.3.8.12]]
* [[v1.3.9.0]]
* [[v1.3.10.0]]
* [[v1.3.11.3]]
* [[v1.3.12.1]]

| group9 = 2013
| list9 =
* [[v1.2.1.0]]
* [[v1.2.1.1]]
* [[v1.2.2.9]]
* [[v1.2.3.0]]
* [[v1.2.3.7]]
* [[v1.2.4.0]]
* [[v1.2.4.9]]
* [[v1.2.6.0]]
* [[v1.2.7.0]]
* [[v1.2.9.0]]
* [[v1.2.11.0]]
* [[v1.2.12.0]]

}}

Template talk:Navbox changelog

2022-07-20T08:17:20Z

Mach56: /* Section numbering */

Template:Navbox changelog

2022-07-09T01:29:25Z

Mach56: Add more missing changelogs

{{Navbox
| name = Navbox changelog
| title = Changelog
| state = uncollapsed
| listclass = hlist

| group1 = 2022
| list1 =
* [[v1.10.1.0]]
* [[v1.10.1.5]]
* [[v1.10.4.0]]
* [[v1.10.5.0]]
* [[v1.10.6.0]]

| group2 = 2021
| list2 =
* [[v1.9.1.0]]
* [[v1.9.2.0]]
* [[v1.9.3.0]]
* [[v1.9.4.1]]
* [[v1.9.6.0]]
* [[v1.9.6.5]]
* [[v1.9.8.0]]
* [[v1.9.9.0]]
* [[v1.9.9.1]]
* [[v1.9.11.0]]
* [[v1.9.12.0]]

| group3 = 2020
| list3 =
* [[v1.8.2.3]]
* [[v1.8.3.0]]
* [[v1.8.3.1]]
* [[v1.8.3.2]]
* [[v1.8.4.0]]
* [[v1.8.4.4]]
* [[v1.8.4.5]]
* [[v1.8.5.0]]
* [[v1.8.7.0]]
* [[v1.8.8.2]]
* [[v1.8.9.1]]
* [[v1.8.9.4]]
* [[v1.8.10.0]]
* [[v1.8.11.1]]
* [[v1.8.11.3]]
* [[v1.8.12.0]]
* [[v1.8.12.1]]

| group4 = 2019
| list4 =
* [[v1.7.2.0]]
* [[v1.7.3.1]]
* [[v1.7.3.4]]
* [[v1.7.3.5]]
* [[v1.7.3.8]]
* [[v1.7.6.0]]
* [[v1.7.7.0]]
* [[v1.7.8.2]]
* [[v1.7.9.0]]
* [[v1.7.10.0]]
* [[v1.7.11.0]]
* [[v1.7.11.4]]

| group5 = 2018
| list5 =
* [[v1.6.1.6]]
* [[v1.6.2.3]]
* [[v1.6.2.9]]
* [[v1.6.2.10]]
* [[v1.6.2.14]]
* [[v1.6.3.2]]
* [[v1.6.3.5]]
* [[v1.6.5.0]]
* [[v1.6.5.1]]
* [[v1.6.5.2]]
* [[v1.6.5.5]]
* [[V1.6.5.6]]
* [[v1.6.7.3]]
* [[v1.6.9.0]]
* [[v1.6.10.0]]
* [[v1.6.11.3]]
* [[V1.6.12.0]]

| group6 = 2017
| list6 =
* [[v1.5.1.5]]
* [[v1.5.1.11]]
* [[v1.5.2.5]]
* [[v1.5.2.20]]
* [[v1.5.2.24]]
* [[v1.5.3.2]]
* [[v1.5.3.4]]
* [[v1.5.4.0]]
* [[v1.5.4.4]]
* [[v1.5.4.11]]
* [[v1.5.5.0]]
* [[v1.5.6.0]]
* [[v1.5.7.1]]
* [[v1.5.7.8]]
* [[v1.5.8.2]]
* [[v1.5.9.3]]
* [[v1.5.10.2]]
* [[v1.5.11.1]]
* [[v1.5.11.6]]
* [[v1.5.11.9]]

| group7 = 2016
| list7 =
* [[v1.4.2.5]]
* [[v1.4.2.8]]
* [[v1.4.2.14]]
* [[v1.4.3.3]]
* [[v1.4.4.0]]
* [[v1.4.5.0]]
* [[v1.4.6.0]]
* [[v1.4.7.0]]
* [[v1.4.9.2]]
* [[v1.4.11.0]]
* [[v1.4.11.15]]
* [[v1.4.12.7]]
* [[v1.4.12.15]]

| group8 = 2015
| list8 =
* [[v1.3.1.1]]
* [[v1.3.1.5]]
* [[v1.3.1.8]]
* [[v1.3.1.12]]
* [[v1.3.1.15]]
* [[v1.3.1.17]]
* [[v1.3.4.1]]
* [[v1.3.5.1]]
* [[v1.3.6.0]]
* [[v1.3.6.1]]
* [[v1.3.7.1]]
* [[v1.3.8.5]]
* [[v1.3.8.7]]
* [[v1.3.8.12]]
* [[v1.3.9.0]]
* [[v1.3.10.0]]
* [[v1.3.11.3]]
* [[v1.3.12.1]]

| group9 = 2013
| list9 =
* [[v1.2.1.0]]
* [[v1.2.1.1]]
* [[v1.2.2.9]]
* [[v1.2.3.0]]
* [[v1.2.3.7]]
* [[v1.2.4.0]]
* [[v1.2.4.9]]
* [[v1.2.6.0]]
* [[v1.2.7.0]]
* [[v1.2.9.0]]
* [[v1.2.11.0]]
* [[v1.2.12.0]]

}}

Talk:Units

2022-07-09T01:24:32Z

Mach56: /* Unit reference/comparison table? */

== Unit summaries ==
I think a very brief summary of each factory could be very helpful, like:

* Cloakbots: High DPS, fragile, relatively shorter-ranged. Several units are cloaked or have area cloaking.
* Shieldbots: Tough, low DPS. Several units have shields and shield-related abilities such as turning shields into damage.

Etc. I would do it myself, but I know far too little of the different factories to be able to give good brief summaries.

In addition, it might be nice to automatically generate and show (similar to this script: https://github.com/ZeroK-RTS/SpringRTS-Tools/blob/master/unitguide/export_unit_templates.lua , which is some really nice functionality, kudos to Histidine91) a box plot for each of some different main statistics, such as "DPS/cost", "Hit Points/cost", "Movement Speed", "Range", "Weapon AOE". The units of each factory would then be depicted with one box in each box plot. That by itself could give an easy way to get a quick and superficial impression of how each factory compares to other factories. That said, lots of units have special abilities or special weapons, and even regular statistics can have major importance (which I think is a really nice part of Zero-K), so for at least some of those statistics, the plots might be both difficult and laboursome to automatically generate as well as possibly be very misleading, which might be worse than no impression. So this may not be a good idea and not at all worth the time or effort.
— unsigned comment by [[Special:Contributions/109.57.58.139|109.57.58.139]]
:Reg. the latter part, I think statistics such as "log2(Hit Points)" (illustrating force concentration, which is relevant for striders and tanks) and "log2(cost)", and maybe "log2(Range)" instead of "Range", might be useful. — unsigned comment by [[Special:Contributions/109.57.58.139|109.57.58.139]]

== Too much html+css ==

Our players are already intimidated when it comes to editing the Wiki. This page has enough HTML and CSS now to scare off anyone who wants to edit it and doesn't know how to read HTML. I suggest that the page be converted to Wiki syntax and kept that way. —[[User:RandomX|RandomX]] ([[User talk:RandomX|talk]]) 02:49, 27 July 2020 (CEST)

That's a fair point that I didn't consider, I hoped to keep that amount down, but I didn't succeed without sacrificing the formatting I hoped for. I will cut down the amount of HTML and CSS. I think it would be OK to keep the image links that are also present in the different factory pages, since they should be decently simple, and I don't know whether those images can be included as is using only MediaWiki syntax (if anyone knows how to do that, please do mention it and I will use MediaWiki syntax for the images). --[[User:Someoneelsewhere|Someoneelsewhere]] ([[User talk:Someoneelsewhere|talk]]) 03:20, 27 July 2020 (CEST)

I have greatly decreased the usage of HTML and CSS. It looks "noisier" now, however. Does anyone have any proposals or suggestions for making it less "noisy" while keeping it to MediaWiki syntax? I must also apologize, for it seems that it is really simple to include images as is, having just the raw link works when you are just including the image, not using it as part of a link or similar. --[[User:Someoneelsewhere|Someoneelsewhere]] ([[User talk:Someoneelsewhere|talk]]) 04:33, 27 July 2020 (CEST)

Dear RandomX, I have partially reverted to using a bit of HTML and CSS again, and it is now not anywhere near as noisy before, however, it still does not seem quite as good as the original version. Given that you are definitely beyond any doubt much more experienced reg. this Wiki than me, would it be possible for you to improve and fix that, maybe such that the text is placed to the right of the image instead of below it, and thus increase visual coherence and decrease space wasted? I believe that could be very helpful to the section. Thank you very much in advance and best regards. --[[User:Someoneelsewhere|Someoneelsewhere]] ([[User talk:Someoneelsewhere|talk]]) 06:06, 27 July 2020 (CEST)

I don't pretend to know more than I do. ...But making things easier for others is always good. I think I achieved what you were trying to do, but at the cost of having to use {{tl|clear}}, which is hardly optimal. While I'm not happy about the image tags (''you'' did it right!), wiki software severely limits what you can do with images when they are linked the correct way. The html is here only because we really should have all the images uploaded here, but that's for someone with admin rights to do. Or someone very-VERY patient. These are all only suggestions anyway. If you feel that I really broke your layout, feel free to revert everything to the pre-me condition. —[[User:RandomX|RandomX]] ([[User talk:RandomX|talk]]) 01:00, 28 July 2020 (CEST)

Dear RandomX, thank you very, very much, it looks really good now, (much) better than my attempt, and it is very clear and concise. And I only did it right reg. images after you mentioned that such would be possible :) . I think you are right about the images, I believe there are some places here and there where the images can be converted as is, I will look at converting a few of those pages. Best regards and again, thank you very, very much :) . --[[User:Someoneelsewhere|Someoneelsewhere]] ([[User talk:Someoneelsewhere|talk]]) 01:28, 28 July 2020 (CEST)

== Unit reference/comparison table? ==

Is there any interest in one big table of all the units in the game, with their factory, cost, designation, dps and so on? Wiki code permitting it could be sortable by column.

I'm new to the game, and this sort of thing would help enormously in getting to know the relative strengths of the different units.

I tend to make a similar spreadsheet for my own use whenever I start playing a new game, and I thought maybe other people might be interested as well.

: I'm not sure a big table with all the units would be a good idea, but a table for each category (e.g. constructor, factory, combat unit (maybe split this into roles too?) etc.) might be a better idea. You'd probably rather compare like-to-like rather than have a bunch of unrelated units in there as well. --[[User:Mach56|Mach56]] ([[User talk:Mach56|talk]]) 18:24, 8 July 2022 (PDT)

Balancing Guidelines

2022-07-09T01:10:10Z

Mach56: /* Maths and Stats */ Update old unit names

==Game Design==
Balance in Zero-K should always be approached holistically, in respect to its design. It is a complex network of niches, counter mechanics and roles. These can be unit-unit counters, or situational dynamics such as terrain. When approaching units balance, determine first that you understand what a unit is meant to:
* Be good at
* Be bad at
* Beat
* Be beaten by

And how it is meant to be used. Change a unit to stay within its role. Sometimes, it is the role which is too broad, and a new weakness needs to be introduced. A narrow role is better than a broad one, as long as a unit is very good at what it does. Always make sure units do not overlap identically in role, otherwise one or the other will always be preferable. More than balance, be conscious of how a unit makes the game actually play. Modifying a unit stats can totally change how the game plays, and even if something seems UP or OP, changing it would make the game play worse.

<CarRepairer> it's simple really. unit cost = (pwn - fail) * baw

Once you are sure you understand a unit's role, there are three areas you should test and gather information in.

==Ingame experience==
This is the most important. If a unit cannot be used effectively in game, then it isn't OP (yet) and if everyone uses it then it isn't UP (yet). However, beware the culture of balance. Often a unit will go for weeks without anyone using it, and then someone discovers and exploits it. Soon everyone is using it, and it goes from being 'useless' to being OP. Be careful not to repeatedly buff an unpopular unit, it can take a long time before people come back to an unpopular unit and give it another shot. Don't be too hasty to nerf a popular unit- perhaps this is a 'fad', perhaps someone will find a counter. If you do nerf it, be conservative- don't try and over-nerf it just to ensure people stop using it because then its useless and will get buffed again.

Balance based on what good players do. This does not mean that you should balance the game entirely around the high-micro, hard to use 'pro' units or balance so that the game is only viable at a high level. However, good or inventive players can totally change the face of the way the game is played by effectively exploiting an underused unit. There are many units which an average player will not understand the use for until they have seen it used well.

Don't balance based on one game. Consult other players on their experiences too. You should test exhaustively, on several maps, with varying skill levels between the players. It is useful if testing a strategy to try it out vs someone, then get them to try it out vs you, both trying to counter.

1v1 is the most pure testing ground for a strategy. Team games often have different requirements but the various factors in play in team games make it very hard to get an impartial judgement, there are too many stray variables.

A good way to get impartial data on the use of units is through real game statistics. Statistical abnormalities are excellent candidates for trying to exploit ingame. Remember however that what causes the most cost in damage in a game isn't necessarily what decided the outcome- It might just be the mop-up crew, the victory may be economic, and a units effectiveness depends entirely on the skill of player using it. Keep Lancaster's square law in mind, masses of even a bad unit will be cost effective vs small numbers of a good unit.

==Closed testing==
Do for-cost tests of units. /spectator /godmode is your friend here! Micro both sides in various circumstances. This can help to nullify a whole range of factors that may be skewing your assessment, like economic differences and terrain. Note however that those factors are often precisely why those units are op, and that you wont really know how a unit works out ingame unless you use it in real situations.

==Maths and Stats==
Look at the actual stats of a unit. Compare it to similiar units. Sometimes one unit will appear to be OP when another one is actually far better. This is an incredibly useful tool in determining where the problem in a unit might lay, as often the problem will stand out immediately. Other times, it is something very subtle. Remember there are a huge range of values besides hp/dps. Range, speed, manoeuvrability, and even variables in the script like turret turnrate.

Think about everything in terms of cost. Knowing how much damage or HP something has is an abstract figure, what is important is its cost/damage cost/hp. Weight class (IE the cost, irrespective of cost-effectiveness) can also be very important, as a large unit has full DPS until it dies, while a mass of units of the same cost loses DPS as they die.

The use of a unit is not always determined by good stats, but often by the right combination and values. There is a huge difference between just out-ranging an LLT, and having the same range as an LLT. Try to think more in terms of unit relationships than pure numbers. When balancing a unit, try and think of other areas that can be changed to make it useful, rather than just its hp/dps. What specifically is holding it back/making it too strong ingame? Also remember knock-on effects. If you nerf something, another unit which it has until now effectively countered may suddenly be OP.

Be aware of what your values mean in relation to other units. Buffing a units HP by 5% might not actually do anything, because all the weapons that can shoot it still take just as many shots to kill it, or it might put it over a threshold which means it takes an extra shot to kill, for much more than a 5% difference. This matters particularly for Air vs AA, Subs vs Anti-sub, Pickets vs Raiders, and low RoF units like Lances, Skuttles and Widows.

Keep Quant's rule in mind, buff strengths, nerf weaknesses, otherwise all units tend over time towards the average and unit difference is lost. Ultimately though how it fits within the game design and how it can better fulfill its role is the most important factor though, and one of its strengths or weaknesses may in fact be preventing it from fulfilling that role.

= Further reading =
[http://springrts.com/phpbb/viewtopic.php?p=177771#p177771 Issac's essay on balance design]

[[Category:Development]]

Lobster

2022-06-10T15:04:17Z

Mach56: Undo revision 8455 by 50.100.92.172 (talk)

The '''{{PAGENAME}}''' is a launcher bot from the [[Amphbot Factory]].{{ Infobox zkunit
| name = Lobster
| defname = amphlaunch
| description = Amphibious Launcher Bot
| image = http://manual.zero-k.info/unitpics/amphlaunch.png
| icontype = ampharty
| cost = 340
| hitpoints = 960
| movespeed = 54
| turnrate = 356
| sight = 500
| sonar = 500
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Unit Launcher
| type = Cannon
| damage = 0
| reloadtime = 12
| range = 620
| aoe = 112
| projectilespeed = 350
| special1 = High trajectory
| special2 = Water capable
}}
| abilities =
{{ Infobox zkability regen
| waterregen = 10
| atdepth = 40
}}
}}==Description==
Lacking armaments of its own, the Lobster's response to threats is to throw other units at the problem. Though originally intended for rapid coastline deployment, the Lobster has a variety of uses and can even offensively throw enemies units.

== Tactics and Strategy ==
While at first seeming as an afterthought unit, the Lobster is an ace in [[Amphbot Factory]]'s arsenal, allowing it a much-needed mobility boost and opening strategies for both sea and land warfare. You'll find that using Lobsters greatly improves performance from other units of this factory, while not requiring a lot of investment, as even one is usually sufficient.

The Lobster launches units to great heights, allowing for both fast terrain traversal and access to otherwise unreachable terrain, while not causing any fall damage. It also ignores the unit's mass, launching anything from [[Flea]] to [[Detriment]] (and being the fastest of transport methods for the latter).

While using the Lobster, always mind its "grab", represented by thin green lines, as any unit in its reach will be launched alongside the desired ones.

Some of the possible strategies include:
* Landing your troops on cliffs and from unexpected angles on island maps.
* Launching your [[Limpet]]s, giving you an arc-artillery previously missing and a potent disabling method.
* Using Lobsters in stealth to launch enemy into traps.
* Making a chain of Lobsters, launching one with the other, effectively allowing you to get your army across the map in moments.
* Tossing a lobster into enemy lines and tossing enemies out of position into your riots.

{{Navbox units}}

Gunship Plant

2022-06-10T15:02:34Z

Mach56: /* Beating Gunships */ Update names and minor grammar fixes

The '''{{PAGENAME}}''' is a factory that produces gunships.{{ Infobox zkunit
| name = Gunship Plant
| defname = factorygunship
| description = Produces Gunships
| image = http://manual.zero-k.info/unitpics/factorygunship.png
| icontype = facgunship
| cost = 700
| hitpoints = 4000
| sight = 273
| abilities =
{{ Infobox zkability construction
| buildpower = 10
}}
}}==Description==
The Gunship Plant is designed for close air support. It includes a selection of transports for hauling land units around, and combat gunships which can perform a variety of offensive or defensive roles.

The Gunship Plant builds:
* http://manual.zero-k.info/unitpics/gunshipcon.png [[Wasp]]   Heavy Gunship Constructor
* http://manual.zero-k.info/unitpics/gunshipbomb.png [[Blastwing]]   Flying Bomb
* http://manual.zero-k.info/unitpics/gunshipemp.png [[Gnat]]   Anti-Heavy EMP Drone
* http://manual.zero-k.info/unitpics/gunshipraid.png [[Locust]]   Raider Gunship
* http://manual.zero-k.info/unitpics/gunshipskirm.png [[Harpy]]   Multi-Role Support Gunship
* http://manual.zero-k.info/unitpics/gunshipheavyskirm.png [[Nimbus]]   Fire Support Gunship
* http://manual.zero-k.info/unitpics/gunshipassault.png [[Revenant]]   Heavy Raider/Assault Gunship
* http://manual.zero-k.info/unitpics/gunshipkrow.png [[Krow]]   Flying Fortress
* http://manual.zero-k.info/unitpics/gunshipaa.png [[Trident]]   Anti-Air Gunship
* http://manual.zero-k.info/unitpics/gunshiptrans.png [[Charon]]   Air Transport
* http://manual.zero-k.info/unitpics/gunshipheavytrans.png [[Hercules]]   Armed Heavy Air Transport

==Tactics and Strategy==

The principle of Gunships is to assault the enemy from the air, at any time, and in any place. To this end, the Locust and Harpy are quick and capable of engaging enemy forces directly, while the Charon and Hercules can transport friendly land forces to the places they will be most effective. As a finishing blow, the super-heavy Krow gunship is without equal against opponents with poor anti-air coverage.

In contrast to Airplanes, Gunships never have to rearm, so they can stick around an enemy base or army and keep dealing damage. On the other hand, they are slower and require more time to deal the same amount of damage that a bombing run would. Similarly, the Trident and Harpy are favoured in a head-on, prolonged engagement against the [[Swift]] and [[Raptor]] airplane fighters, but they are slower and less able to react to air-to-ground threats presented by the enemy.

=== Example Unit Combinations ===

As a raiding force, use Blastwings to set an enemy factory on fire and halt production, then use Locusts to take out enemy infrastructure.

Tridents and Harpies together present some danger to ground units while being almost impervious to attack from enemy air forces.

Where possible, protect your dedicated anti-ground gunships like the Nimbus, Revenant and Krow from air-to-air threats with Tridents.

Use Charons to drop slow, high-damage riot units like the [[Reaver]] or [[Scallop]] close to enemy buildings or units which they could not otherwise reach. You can assist your dropped forces with Gnats to disable enemy threats.

Similar drop tactics may be pursued by transporting a heavier unit like the [[Dante]] with a Hercules. If you don't want to lose the units you're dropping, retrieve them with transports or a [[Djinn]] beacon.

More esoteric uses of transports include dropping bombs like the [[Snitch]] or [[Skuttle]] on enemy targets, or stunning a high-value target like a [[Crabe]], [[Grizzly]] or [[Commander]] with Gnats then abducting it with a Hercules.

=== Beating Gunships ===

Anti-air units or structures which deliver high sustained damage-per-second are generally more effective against Gunships than those with high burst damage. The [[Razor]] is pretty cheap and very tough, though you will need more than one to deal enough damage to a large Gunship fleet. The [[Thresher]] is more expensive, but its flak cannon inflicts area-of-effect damage. The range of the [[Chainsaw]] and [[Artemis]] makes them effective against any air threat, though they are more expensive.

In terms of mobile anti-air, the [[Ettin]] and [[Toad]] are most effective against Gunships. In permissive terrain, the speed of the [[Crasher]] and [[Flail]] gives them an edge despite being burst-damage based AA. The [[Gremlin]] is effective in bulk if their passive cloak is abused to set traps for enemy Gunships.

Your first priority against Gunships is to fend off the initial raids by Locusts and Blastwings, while continuing to expand and pressure them in return. Locusts fly quite low so unlike most air units they are quite vulnerable to the [[Lotus]], and [[Picket]] are also effective in larger numbers. You might also need mobile anti-air to protect your constructors.

If you are using Airplanes against a player with Gunships, avoid a direct fight unless you have a substantial numerical advantage - Tridents are very strong against your fighters. They can't move fast enough to deal with bombing threats on multiple fronts, so focus on supporting your ground forces with bombing runs. You should still keep some fighters to contest the skies if the gunships enter your territory.

If you are playing the Gunship mirror matchup, try to have more Tridents than they do, while still making things happen in the ground war using Locust raids and the like.

{{Navbox buildings}}

Halberd

2022-03-07T11:39:39Z

Mach56: Update Halberd hp 1600->1450

The '''{{PAGENAME}}''' is a blockade runner hover from the [[Hovercraft Platform]].{{ Infobox zkunit
| name = Halberd
| defname = hoverassault
| description = Blockade Runner Hover
| image = http://manual.zero-k.info/unitpics/hoverassault.png
| icontype = hoverassault
| cost = 210
| hitpoints = 1450
| movespeed = 96
| turnrate = 162
| sight = 385
| sonar = 385
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Direct Energy Weapon
| type = LaserCannon
| damage = 160
| reloadtime = 1.20
| dps = 133
| range = 200
| projectilespeed = 200
}}
| abilities =
{{ Infobox zkability armored
| reduction = 67%
}}
}}==Description==
The Halberd buttons down into its armored hull when not firing, offering 4x damage resistance. Its slow, short-ranged weapon is unsuitable for use against highly mobile targets.

== Tactics and Strategy ==
Set the Halberd's fire state to "hold fire mode" to keep it from opening up its protective hull to fire at enemies, thus keeping its damage reduction capabilities active (for, say, when it needs to speed past some modest defenses).

{{Navbox units}}

Map icons

2022-02-10T23:21:32Z

Mach56: /* General */ Add transport icon

ZK uses a unique '''icon''' system, assigning each unit class and chassis a specific map icon. You can see these icons when you zoom out enough.<div style="float:right;">__TOC__</div>

http://licho.eu/alba/Zero-K_Manual/mapicons.jpg

Needless to say, these icons can be rather confusing, even intimidating, to the new user. Fortunately, they're actually very simple, and this guide will explain them to you.

== General ==
The icon system is mostly modular; an icon indicating a unit role is superimposed on an icon representing a chassis type (bot, vehicle, etc.)

Thus a raider rover is
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/vehicleraider.png" height="64" width="64" />
and an artillery tank is
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/tankarty.png" height="64" width="64" />

{|
! Chassis icon !! Type !! Chassis icon !! Type
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/kbot.png" height="64" width="64" /> || Cloakbot ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/vehicle.png" height="64" width="64" /> ||Rover
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/walker.png" height="64" width="64" /> ||Shieldbot ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/tank.png" height="64" width="64" /> ||Tank
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/jumpjet.png" height="64" width="64" /> ||Jumpjet ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/spider.png" height="64" width="64" /> ||Spider
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/ship.png" height="64" width="64" /> ||Ship ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/hover.png" height="64" width="64" /> ||Hover
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/hover2.png" height="64" width="64" /> ||Amph || <img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/air.png" height="48" width="48" /> ||Aircraft
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/t3.png" height="64" width="64" /> ||Strider||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/gunship.png" height="64" width="64" />||Gunship
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/defense.png" height="64" width="64" /> ||Defense ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/static.png" height="48" width="48" /> ||Static
|}

{|
! Role icon !! Type !! Role icon !! Type
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/raider.png" height="64" width="64" /> ||Raider ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/assault.png" height="64" width="64" /> ||Assault
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/skirm.png" height="64" width="64" /> ||Skirmisher ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/riot.png" height="64" width="64" /> ||Riot
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/arty.png" height="64" width="64" /> ||Artillery ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/aa.png" height="64" width="64" /> ||Anti-air
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/scout.png" height="64" width="64" /> ||Scout ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/LRarty.png" height="64" width="64" /> ||Long range arty
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/radar.png" height="64" width="64" /> ||Radar || <img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/bomb.png" height="64" width="64" /> ||Bomb/special
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/jammer.png" height="64" width="64" /> ||Jammer|| <img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/shield.png" height="64" width="64" /> ||Shield
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/support.png" height="64" width="64" /> ||Ranged Support||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master/MapIconBuilder/MapIcons/2_Class/transport.png" height="64" width="64" /> ||Transport
|-
| <img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/antinuke.png" height="64" width="64" /> ||Anti-Nuke|| ||
|}

== Static Defense ==
Static defenses use the normal icon system, though the roles don't correspond exactly. The exception is the Heavy SAM icon used by the long-ranged missile tower, the Artemis.

{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseraider.png" height="64" width="64" />||[[Lotus]] (LLT)||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseassault.png" height="64" width="64" />||[[Stinger]] (HLT)
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseskirm.png" height="64" width="64" />||[[Picket]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseriot.png" height="64" width="64" />||[[Stardust]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defensespecial.png" height="64" width="64" />||[[Faraday]]<br/>[[Newton]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseaa.png" height="64" width="64" />||[[Razor]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/staticaa.png" height="64" width="64" />||[[Thresher]] (flak)||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/heavysam.png" height="64" width="64" />||[[Artemis]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/fixedtachyon.png" />||[[Lucifer]]||<img src=https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/icons/staticassaultriot.png height="64" width="64" />||[[Desolator]]
|}

== Factories ==
Factories use the chassis icon of the units they build superimposed on the static building icon.

{|
! Icon !! Class !! Icon !! Class
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statickbot.png" height="64" width="64" />||Cloakbot||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticvehicle.png" height="64" width="64" />||Rover
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticwalker.png" height="64" width="64" />||Shieldbot||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statictank.png" height="64" width="64" />||Tank
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticjumpjet.png" height="64" width="64" />||Jumper||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticspider.png" height="64" width="64" />||Spider
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticair.png" height="64" width="64" />||Airplane||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/facgunship.png" />||Gunship
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statichover.png" height="64" width="64" />||Hover||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticship.png" height="64" width="64" />||Ship
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statichover2.png" height="64" width="64" />||Amph||||
|}

Usually, however, the factory's icon will be obscured by the icon of whatever it's building.

== Econ Buildings ==

{|
! Icon !! Unit
|-
|style = "text-align:center;" | <img src="http://manual.zero-k.info/icons/mex.png" height="48" width="48"/> ||[[Metal Extractor]]
|-
|style = "text-align:center;" | <img src="http://manual.zero-k.info/icons/energywind.png" height="64" width="64"/>||[[Wind/Tidal Generator]]
|-
|<img src="http://manual.zero-k.info/icons/energy_med.png" height="64" width="64"/>||[[Solar Collector]]
|-
|<img src="http://manual.zero-k.info/icons/energygeo.png" height="64" width="64"/>||[[Geothermal Generator]]
|-
|<img src="http://manual.zero-k.info/icons/energyfusion.png" />||[[Fusion Reactor]]
|-
|<img src="http://manual.zero-k.info/icons/energyheavygeo.png" height="64" width="64"/>||[[Advanced Geothermal]]
|-
|<img src="http://manual.zero-k.info/icons/energysingu.png" />||[[Singularity Reactor]]
|-
|<img src="http://manual.zero-k.info/icons/pylon.png" />||[[Energy Pylon]]
|}

== Aircraft ==
Although aircraft do have a chassis icon, they generally use pictographic icons, as below:

{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/fighter.png" />||Multirole fighter||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/stealthfighter.png" height="64" width="64" />||Dedicated fighter
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bomberassault.png" />||Precision bomber||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bomberraider.png" />||Napalm bomber
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bomberriot.png" />||EMP bomber||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bombernuke.png" />||Implosion bomber
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/radarplane.png" />||Radar plane|| ||
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/gunship.png" />||Light gunship||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/heavygunship.png" />||Heavy gunship
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/airbomb.png" />||Blastwing|| ||
|}

== Ships ==
Like aircraft, ships use pictographic icons.
{|
! Icon !! Unit
! Icon !! Unit
! Icon !! Unit
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/scoutboat.png" height="64" width="64" />||[[Cutter]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/hunter.png" height="80" width="80" />||[[Hunter]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/corvette.png" height="80" width="80" />||[[Corsair]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/enforcer.png" height="80" width="80" />||[[Mistral]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/aaboat.png" height="80" width="80" />||[[Zephyr]]
|<img src="http://manual.zero-k.info/icons/shipassault.png" height="80" width="80" />||[[Siren]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/destroyer.png" height="80" width="80" />||[[Envoy]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/carrier.png" height="96" width="96" />||[[Reef]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/battleship.png" height="96" width="96" />||[[Shogun]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/submarine.png" height="80" width="80" />||[[Seawolf]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/missilesub.png" height="80" width="80" />||[[Scylla]]
| ||
|}

== Misc. Units ==
Many units have specific icons that reflect their unique roles, particularly superweapons such as Big Berthas and Trinities.

=== Superweapons ===
{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/cruisemissile.png" />||Cruise missile||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/lrpc.png" />||[[Big Bertha]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/nuke.png" />||[[Trinity]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/mahlazer.png" />||[[Starlight]]
[[Zenith]]

[[Disco Rave Party]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/krogoth.png" />||[[Detriment]]||||
|}

=== Other units ===
{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/builder.png" />||Constructor||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/builderair.png" />||Aircon
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/icons/clogger.png" height="64" width="64"/>||[[Dirtbag]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/mine.png" />||[[Claw|Mine]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/mobiletachyon.png" />||[[Lance]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/sniper.png" />||[[Phantom]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/armcommander.png" />||[[Commander]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/chickenq.png" />||[[Chicken Queen]]
|}

{{Navbox manual}}

Map icons

2022-02-10T23:17:16Z

Mach56: /* Aircraft */ Transport icon depicted isn't used. The one used is like the raider/riot/skirm etc role icons, not a unique one.

ZK uses a unique '''icon''' system, assigning each unit class and chassis a specific map icon. You can see these icons when you zoom out enough.<div style="float:right;">__TOC__</div>

http://licho.eu/alba/Zero-K_Manual/mapicons.jpg

Needless to say, these icons can be rather confusing, even intimidating, to the new user. Fortunately, they're actually very simple, and this guide will explain them to you.

== General ==
The icon system is mostly modular; an icon indicating a unit role is superimposed on an icon representing a chassis type (bot, vehicle, etc.)

Thus a raider rover is
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/vehicleraider.png" height="64" width="64" />
and an artillery tank is
<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/tankarty.png" height="64" width="64" />

{|
! Chassis icon !! Type !! Chassis icon !! Type
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/kbot.png" height="64" width="64" /> || Cloakbot ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/vehicle.png" height="64" width="64" /> ||Rover
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/walker.png" height="64" width="64" /> ||Shieldbot ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/tank.png" height="64" width="64" /> ||Tank
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/jumpjet.png" height="64" width="64" /> ||Jumpjet ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/spider.png" height="64" width="64" /> ||Spider
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/ship.png" height="64" width="64" /> ||Ship ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/hover.png" height="64" width="64" /> ||Hover
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/hover2.png" height="64" width="64" /> ||Amph || <img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/air.png" height="48" width="48" /> ||Aircraft
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/t3.png" height="64" width="64" /> ||Strider||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/gunship.png" height="64" width="64" />||Gunship
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/defense.png" height="64" width="64" /> ||Defense ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/1_Movetype/static.png" height="48" width="48" /> ||Static
|}

{|
! Role icon !! Type !! Role icon !! Type
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/raider.png" height="64" width="64" /> ||Raider ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/assault.png" height="64" width="64" /> ||Assault
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/skirm.png" height="64" width="64" /> ||Skirmisher ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/riot.png" height="64" width="64" /> ||Riot
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/arty.png" height="64" width="64" /> ||Artillery ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/aa.png" height="64" width="64" /> ||Anti-air
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/scout.png" height="64" width="64" /> ||Scout ||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/LRarty.png" height="64" width="64" /> ||Long range arty
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/radar.png" height="64" width="64" /> ||Radar || <img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/bomb.png" height="64" width="64" /> ||Bomb/special
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/jammer.png" height="64" width="64" /> ||Jammer|| <img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/shield.png" height="64" width="64" /> ||Shield
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/support.png" height="64" width="64" /> ||Ranged Support|| <img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/2_Class/antinuke.png" height="64" width="64" /> ||Anti-Nuke
|}

== Static Defense ==
Static defenses use the normal icon system, though the roles don't correspond exactly. The exception is the Heavy SAM icon used by the long-ranged missile tower, the Artemis.

{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseraider.png" height="64" width="64" />||[[Lotus]] (LLT)||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseassault.png" height="64" width="64" />||[[Stinger]] (HLT)
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseskirm.png" height="64" width="64" />||[[Picket]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseriot.png" height="64" width="64" />||[[Stardust]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defensespecial.png" height="64" width="64" />||[[Faraday]]<br/>[[Newton]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/defenseaa.png" height="64" width="64" />||[[Razor]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIcons/staticaa.png" height="64" width="64" />||[[Thresher]] (flak)||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/heavysam.png" height="64" width="64" />||[[Artemis]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/fixedtachyon.png" />||[[Lucifer]]||<img src=https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/icons/staticassaultriot.png height="64" width="64" />||[[Desolator]]
|}

== Factories ==
Factories use the chassis icon of the units they build superimposed on the static building icon.

{|
! Icon !! Class !! Icon !! Class
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statickbot.png" height="64" width="64" />||Cloakbot||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticvehicle.png" height="64" width="64" />||Rover
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticwalker.png" height="64" width="64" />||Shieldbot||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statictank.png" height="64" width="64" />||Tank
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticjumpjet.png" height="64" width="64" />||Jumper||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticspider.png" height="64" width="64" />||Spider
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticair.png" height="64" width="64" />||Airplane||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/facgunship.png" />||Gunship
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statichover.png" height="64" width="64" />||Hover||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/staticship.png" height="64" width="64" />||Ship
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MapIconFactories/statichover2.png" height="64" width="64" />||Amph||||
|}

Usually, however, the factory's icon will be obscured by the icon of whatever it's building.

== Econ Buildings ==

{|
! Icon !! Unit
|-
|style = "text-align:center;" | <img src="http://manual.zero-k.info/icons/mex.png" height="48" width="48"/> ||[[Metal Extractor]]
|-
|style = "text-align:center;" | <img src="http://manual.zero-k.info/icons/energywind.png" height="64" width="64"/>||[[Wind/Tidal Generator]]
|-
|<img src="http://manual.zero-k.info/icons/energy_med.png" height="64" width="64"/>||[[Solar Collector]]
|-
|<img src="http://manual.zero-k.info/icons/energygeo.png" height="64" width="64"/>||[[Geothermal Generator]]
|-
|<img src="http://manual.zero-k.info/icons/energyfusion.png" />||[[Fusion Reactor]]
|-
|<img src="http://manual.zero-k.info/icons/energyheavygeo.png" height="64" width="64"/>||[[Advanced Geothermal]]
|-
|<img src="http://manual.zero-k.info/icons/energysingu.png" />||[[Singularity Reactor]]
|-
|<img src="http://manual.zero-k.info/icons/pylon.png" />||[[Energy Pylon]]
|}

== Aircraft ==
Although aircraft do have a chassis icon, they generally use pictographic icons, as below:

{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/fighter.png" />||Multirole fighter||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/stealthfighter.png" height="64" width="64" />||Dedicated fighter
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bomberassault.png" />||Precision bomber||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bomberraider.png" />||Napalm bomber
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bomberriot.png" />||EMP bomber||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/bombernuke.png" />||Implosion bomber
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/radarplane.png" />||Radar plane|| ||
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/gunship.png" />||Light gunship||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/heavygunship.png" />||Heavy gunship
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/airbomb.png" />||Blastwing|| ||
|}

== Ships ==
Like aircraft, ships use pictographic icons.
{|
! Icon !! Unit
! Icon !! Unit
! Icon !! Unit
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/scoutboat.png" height="64" width="64" />||[[Cutter]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/hunter.png" height="80" width="80" />||[[Hunter]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/corvette.png" height="80" width="80" />||[[Corsair]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/enforcer.png" height="80" width="80" />||[[Mistral]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/aaboat.png" height="80" width="80" />||[[Zephyr]]
|<img src="http://manual.zero-k.info/icons/shipassault.png" height="80" width="80" />||[[Siren]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/destroyer.png" height="80" width="80" />||[[Envoy]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/carrier.png" height="96" width="96" />||[[Reef]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/battleship.png" height="96" width="96" />||[[Shogun]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/submarine.png" height="80" width="80" />||[[Seawolf]]
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/newships/missilesub.png" height="80" width="80" />||[[Scylla]]
| ||
|}

== Misc. Units ==
Many units have specific icons that reflect their unique roles, particularly superweapons such as Big Berthas and Trinities.

=== Superweapons ===
{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/cruisemissile.png" />||Cruise missile||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/lrpc.png" />||[[Big Bertha]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/nuke.png" />||[[Trinity]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/mahlazer.png" />||[[Starlight]]
[[Zenith]]

[[Disco Rave Party]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/krogoth.png" />||[[Detriment]]||||
|}

=== Other units ===
{|
! Icon !! Unit !! Icon !! Unit
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/builder.png" />||Constructor||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/builderair.png" />||Aircon
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/icons/clogger.png" height="64" width="64"/>||[[Dirtbag]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/mine.png" />||[[Claw|Mine]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/mobiletachyon.png" />||[[Lance]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/sniper.png" />||[[Phantom]]
|-
|<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/armcommander.png" />||[[Commander]]||<img src="https://raw.githubusercontent.com/ZeroK-RTS/SpringRTS-Tools/master//MapIconBuilder/MiscSources/chickenq.png" />||[[Chicken Queen]]
|}

{{Navbox manual}}

Disco Rave Party

2022-02-02T02:24:59Z

Mach56: add grid range

The '''{{PAGENAME}}''' is a destructive rainbow projector firing multi-colored super shots.{{ Infobox zkunit
| name = Disco Rave Party
| defname = raveparty
| description = Destructive Rainbow Projector
| image = http://manual.zero-k.info/unitpics/raveparty.png
| icontype = mahlazer
| cost = 36000
| hitpoints = 16000
| sight = 660
| gridlink = 150
| weapons =
{{ Infobox zkweapon
| name = Red Killer
| type = Cannon
| damage = 3002
| reloadtime = 6
| dps = 500
| range = 7500
| aoe = 96
| projectilespeed = 1100
| special1 = Trajectory toggle
}}
{{ Infobox zkweapon
| name = Orange Roaster
| type = Cannon
| damage = 301
| reloadtime = 6
| dps = 50
| afterburn = 8
| range = 7500
| aoe = 320
| customlabel1 = Ground Burn DPS
| customdata1 = 40
| customlabel2 = Ground Burn radius (elmo)
| customdata2 = 320
| customlabel3 = Ground Burn duration (s)
| customdata3 = 15
| projectilespeed = 1100
| special1 = Trajectory toggle
}}
{{ Infobox zkweapon
| name = Yellow Slammer
| type = Cannon
| damage = 801
| reloadtime = 6
| dps = 134
| range = 7500
| aoe = 192
| projectilespeed = 1100
| special1 = Trajectory toggle
}}
{{ Infobox zkweapon
| name = Green Stamper
| type = Cannon
| damage = 401
| reloadtime = 6
| dps = 67
| range = 7500
| aoe = 192
| projectilespeed = 1100
| special1 = Smooths ground
| special2 = Trajectory toggle
}}
{{ Infobox zkweapon
| name = Blue Shocker
| type = Cannon
| damage = 0
| reloadtime = 6
| empdamage = 30000
| empdps = 5000
| stuntime = 25
| range = 7500
| aoe = 160
| projectilespeed = 1100
| special1 = Trajectory toggle
}}
{{ Infobox zkweapon
| name = Violet Slugger
| type = Cannon
| damage = 450
| reloadtime = 6
| dps = 75
| slowdamage = 4501
| slowdps = 750
| range = 7500
| aoe = 360
| projectilespeed = 1100
| special1 = Trajectory toggle
| special2 = No friendly fire
}}
}}==Description==
The Disco Rave Party throws six different party shots at your enemy for a different surprise each time. Fun for the whole family!

==Trivia==
* The weapon names are inspired by a boss in [http://www.hardcoregaming101.net/gunstarheroes/gunstarheroes.htm Gunstar Heroes].

{{Navbox buildings}}

Starlight

2022-02-02T02:24:57Z

Mach56: add grid range

The '''{{PAGENAME}}''' is a superweapon firing a powerful beam laser from the sky.{{ Infobox zkunit
| name = Starlight
| defname = mahlazer
| description = Planetary Energy Chisel
| image = http://manual.zero-k.info/unitpics/mahlazer.png
| icontype = mahlazer
| cost = 45000
| hitpoints = 10000
| sight = 660
| gridlink = 200
| weapons =
{{ Infobox zkweapon
| name = Craterpuncher
| type = BeamLaser
| damage = 18000
| reloadtime = 20
| dps = 900
| range = 10000
| aoe = 70
| special1 = Instantly hits
| special2 = Water capable
}}
{{ Infobox zkweapon
| name = Cutter
| type = BeamLaser
| damage = 150
| reloadtime = 0.03
| dps = 4500
| range = 10000
| aoe = 70
| special1 = Instantly hits
| special2 = Water capable
}}
}}==Description==
This large-scale tool is used to shape terrain for terraforming projects. Also useful as a cleanser of obstacles such as pesky enemy units and bases.

==Tactics and Strategy==
The Starlight creates a MASSIVE beam that shakes the land it hits. This beam will "Walk" to a target... but watch out for friendly fire! Especially if you build it deep in your base!

Few things, if any, can hope to withstand a Starlight's direct onslaught for long. Even a Detriment will melt within mere seconds.

==Additional Details==
On its own, {{PAGENAME}} is able to shoot its beam only upwards. Then the beam needs to be reflected by [[Glint]], a satellite that allows it to be aimed at ground targets. The satellite is deployed from the top of the {{PAGENAME}}.

{{Navbox buildings}}

Zenith

2022-02-02T02:24:56Z

Mach56: add grid range

The '''{{PAGENAME}}''' is a superweapon that gathers meteors and throws them at the enemy.{{ Infobox zkunit
| name = Zenith
| defname = zenith
| description = Meteor Controller
| image = http://manual.zero-k.info/unitpics/zenith.png
| icontype = mahlazer
| cost = 40000
| hitpoints = 12000
| sight = 660
| gridlink = 150
| weapons =
{{ Infobox zkweapon
| name = Meteor
| type = MissileLauncher
| damage = 1600
| reloadtime = 1
| dps = 1600
| range = 9000
| aoe = 120
| wobbly = 30
| projectilespeed = 1600
| special1 = Potential friendly fire
}}
}}==Description==
The Zenith collects meteorites from the sky (up to 300), which it can send anywhere to break things or provide a small reclaimable source of metal.

==Tactics and Strategy==
Set the Zenith to hold-fire mode to allow it to collect meteors instead of raining down small unreliable meteor swarms at any enemies within its massively-long range (which could not only miss the targeted enemy, but also hurt your own units by accident). Giving it an attack order will send all collected meteors at once, effectively dealing high-burst damage if they are in high numbers (and quite capable of taking down approaching Striders like the Paladin). However, if the Zenith reaches full capacity, any newly collected meteors will be dropped around and on the Zenith's location, dealing damage to buildings and units.

{{Navbox buildings}}

Jack

2022-01-09T12:39:56Z

Mach56: /* Tactics and Strategy */ Added a how-to-Jack Drop guide.

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 = Medium
| weapons =
{{ Infobox zkweapon
| name = Spike
| type = BeamLaser
| damage = 300
| reloadtime = 1
| 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]] roster. 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.

===Jack Drops===

This strategy requires the [[Gunship Plant]] to be performed. Queue some Jacks and an equal number of [[Charon]]s from the Gunship fac, the earlier the better, though late-game Jack drops can still be quite dangerous. Load the Jacks into the Charon and fly them to the enemy base, avoiding AA if relevant. The Charons can take the Jacks into the base of the enemy and kill a factory, intercept an exposed frontline commander and chase it down and kill it (Jacks are faster than all commanders, barring any speed morphs, so it's possible to chase them down), or target another high priority target. It may be prudent to queue a return trip for the Charons so they may be reused, or alternatively attempt to pick-up and return the Jacks to restock for another drop.

====Defending against it====

Unless the Charons are intercepted before they arrive with [[Swift]]s, [[Raptor]]s or anti-air defences, it's likely that the Jacks will get to their target. Normal methods of dealing with Jacks (like the aforementioned Venom, Bolas, or Gnat) be used once they have landed.
{{Navbox units}}

Unit states

2022-01-09T11:31:31Z

Mach56: /* Avoid Bad Targets */ Specify what "light drones" are

{{TOC right}}
Most units and buildings have ''behavior states'' that can be set by the player to modify unit behavior on the fly. The state settings are set per unit to allow different behavior of the same unit types.

Some unit states are hidden by default. You can display them under [[Ingame Menu#Commands|Settings/Interface/Commands]].

[[File:Factory commands.png]]

The right side of the menu displays the settings of the selected units. This display is used to edit the settings. Clicking on a state toggles it. Most states with more than two settings can be toggled backwards with right click.

There is a subtlety in the use of this display: When multiple units in the selection have the same settings different states the display only shows one of the states. A displayed state does not guarantee all units in the selection have that state. Clicking on a state guarantees that every selected unit has the setting displayed after clicking.

== Factory States ==
Factories have many states that usually make no sense for an unarmed structure. Units produced by a factory inherit most of the factory's states if the units have no other default.

== Default States ==
Units can be set to adopt a particular state upon creation from the menu (under Settings/Unit Behaviour/Default). For instance, an artillery unit could be set to Hold Position by default.

== State List ==
Following is a list that explains each state and its settings.

=== Fire State ===
Firestate controls a unit's automatic targeting behaviour. This state is available for all armed units and structures. Player given commands and guard retaliation overrides firestate. As in a unit set to Hold Fire will still fire if it is given a direct order to attack. Units do not lose their current target when firestate changes.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/fire_atwill.png" height="24" width="24"/> '''Fire at Will''' — Fire at any/all enemies within range.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/fire_return.png" height="24" width="24"/> '''Return fire''' — Fire back at enemies that hurt the unit.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/fire_hold.png" height="24" width="24"/> '''Hold Fire''' — Will not fire unless ordered to.

=== Move State ===
Movestate controls how freely a unit can move in pursuit of its target. All mobile units have movestate.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/move_roam.png" height="24" width="24"/> '''Roam''' — The unit will move to attack nearby targets and chase them if they run away. Constructors will only assist ally construction if set to Roam.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/move_engage.png" height="24" width="24"/> '''Maneuver''' — This behaves similarly to Roam, but with a shorter "leash".

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/move_hold.png" height="24" width="24"/> '''Hold Position''' — Unit will not automatically chase enemies or use unit AI. Units will chase with an attack command and use unit AI if they have an Attack Move command.

=== Repeat ===
Repeat causes a unit's order queue to loop. Upon completing an order the order is added to the end of the queue. This is particularly useful for factories because a production queue can be repeated.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/repeat_on.png" height="24" width="24"/> '''Repeat On'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/repeat_off.png" height="24" width="24"/> '''Repeat Off'''

=== Overkill Prevention ===
Some units have ''overkill prevention'' (OKP), such that if only one unit needs to fire to kill the target, other units will try to find a different target instead. This reduces wasted shots, useful for long-reload units such as [[Scalpel]]s.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/overkill_on.png" height="24" width="24"/> '''Overkill Prevention On'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/overkill_off.png" height="24" width="24"/> '''Overkill Prevention Off'''

=== Retreat ===

Sets the retreat level. See [[Retreat]].

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/retreat_90.png" height="24" width="24"/> '''Max Retreat''' — Unit retreats to the closest retreat position when health drops below 99%.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/retreat_60.png" height="24" width="24"/> '''2/3 Retreat''' — Unit retreats to the closest retreat position when health drops below 65%.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/retreat_30.png" height="24" width="24"/> '''1/3 Retreat''' — Unit retreats to the closest retreat position when health drops below 30%.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/retreat_off.png" height="24" width="24"/> '''No Retreat''' — Unit does not auto-retreat.

=== Selection Rank ===
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/selection_rank_0.png" height="24" width="24"/>
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/selection_rank_1.png" height="24" width="24"/>
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/selection_rank_2.png" height="24" width="24"/>
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/selection_rank_3.png" height="24" width="24"/>

See [[Selection#Selection_Rank|Selection Rank]]

=== Build Priority ===

Priority lets you control resource spending more accurately when spending exceeds income. See [[Economy_Guide#Priority |Economy Guide Priority]]

See also [[Resources Reserve]]

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_high.png" height="24" width="24"/> '''High Priority''' — Constructors are always funded.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_med.png" height="24" width="24"/> '''Normal Priority''' — This is the default. Constructors with this set have their priority overridden by the nanoframe they are constructing.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_low.png" height="24" width="24"/> '''Low Priority''' — Constructors use any resources left over to construct.

==== Misc Priority ====
Misc. priority is used for the unit's personal, non-construction resource consumption, i.e. from abilities like [[commander]] upgrades or [[Trinity]] stockpiling.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_high_other.png" height="24" width="24"/> '''High Priority'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_med_other.png" height="24" width="24"/> '''Normal Priority'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_low_other.png" height="24" width="24"/> '''Low Priority'''

=== Factory Assist ===

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/autoassist_on.png" height="24" width="24"/> '''Auto-assist Factory''' — Constructor do not follow the factory rally point. Instead they assist the factory that created them.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/autoassist_off.png" height="24" width="24"/> '''Default Behaviour''' — Constructor will continue to rally point when exiting factory.

=== Cloak ===

Toggles unit cloak. See [[Cloak]]

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/cloak_on.png" height="24" width="24"/> '''Enable Cloak'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/cloak_off.png" height="24" width="24"/> '''Disable Cloak'''

=== Unit AI ===

Toggles smart AI for the unit. See [[Unit AI]]

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bulb_on.png" height="24" width="24"/> '''Unit AI ON''' — Turn ON the game's default unit AI for this unit (skirm, skirmish, and/or Anti-Air AI).

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bulb_off.png" height="24" width="24"/> '''Unit AI OFF''' — Turn OFF the game's default unit AI for this unit.

=== On/Off ===
On/Off controls various miscellaneous unit states. It is used to toggle activation on radar, sonar and cloakers. It also toggles the armour ability of the [[Solar Collector]], [[Lucifer]] and [[Desolator]].

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/on.png" height="24" width="24"/> '''On'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/off.png" height="24" width="24"/> ''' Off'''

=== Idle State ===

Aircraft can be told to fly in a holding pattern or land when idle.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/fly_on.png" height="24" width="24"/> '''Free Flying''' — Unit continues flying when idle.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/fly_off.png" height="24" width="24"/> '''Land on Idle''' — Unit lands when idle.

=== Float State ===

Some amphibious units can float to the surface of the ocean to fire their weapons. They are immobile when floating

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/amph_float.png" height="24" width="24"/> '''Always Float''' — Unit automatically floats when idle.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/amph_attack.png" height="24" width="24"/> '''Float to Fire''' — Unit automatically floats if an enemy is in range and sinks otherwise. Units with long reload time sink between shots.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/amph_sink.png" height="24" width="24"/> '''Always Sink''' — Unit does not float.

=== Trajectory ===

Certain long range artillery units can be toggled between high and low trajectory firing.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/traj_high.png" height="24" width="24"/> '''High Trajectory''' — Shoot with a high arcing shot. This is useful for shooting over terrain that blocks direct line of sight, though it does moderately reduce accuracy.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/traj_low.png" height="24" width="24"/> '''Low Trajectory''' — Unit fire directly toward the enemy. This can be useful because directly fired projectiles are more accurate and spend less time in flight.

=== Fire at Radar ===
Some units with long-range precision weapons, like the Phantom and Lance, can be ordered not to fire on radar dots (i.e. targets inside radar range but outside visual range). These units will still fire on buildings outside line of sight if the target position is known precisely (indicated by the "ghost" building).

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/stealth_on.png" height="24" width="24"/> '''Fire at Radar Dots'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/stealth_off.png" height="24" width="24"/> '''Don't Fire at Radar Dots'''

=== Dive State ===

[[Raven]] by default dive bombs to attack units under area shields, and moving targets. It can also dive bomb normally or constantly fly at a lower altitude.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/divebomb_shield.png" height="24" width="24"/> '''Dive Bomb Shield or Mobile'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/divebomb_attack.png" height="24" width="24"/> '''Dive Bomb Mobile'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/divebomb_always.png" height="24" width="24"/> '''Always Fly Low''' — This causes it to fly at a lowered altitude all the time. It is weak to ground units in this state.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/divebomb_off.png" height="24" width="24"/> '''Always Fly High''' — Will not use dive bomb. This can make it difficult to hit moving or shielded targets.

=== Area Cloak ===

Toggles an area cloaker. Area cloak is also disabled if the unit's On/Off state is set to Off. See [[Cloak]]

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/areacloak_on.png" height="24" width="24"/> '''Activate Cloaking Field''' — Cloak all allied units within cloaking field radius.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/areacloak_off.png" height="24" width="24"/> '''Disengage Cloaking Field''' — Do not emit cloaking field.

=== Gunship Strafe ===
Most gunships can circle-strafe their target when attacking.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/strafe_on.png" height="24" width="24"/> '''Strafe''' — Dodge ground projectiles by circling over the targeted enemy.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/strafe_off.png" height="24" width="24"/> '''No Strafe''' — Deactivate strafing for gunships. Use this to keep out of range of static AA.

=== Kill Captured ===

[[Dominatrix]] can be set to automatically destroy units that it captures.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/capturekill_on.png" height="24" width="24"/> '''Auto-Self Destruct''' — Immediately self-destruct the captured units.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/capturekill_off.png" height="24" width="24"/> '''No Self Destruct''' — Maintain normal control over captured units, no self-destruct.

=== Drone Construction ===
Units capable of drone production can switch it on or off.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/drones_on.png" height="24" width="24"/> '''Production of drones is ongoing'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/drones_off.png" height="24" width="24"/> '''Production of drones is stopped'''

=== Impulse Mode ===
[[Newton]] and [[Jugglenaut]] can be set to push or pull units with their gravity guns.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/push_alt.png" height="24" width="24"/> '''Push'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/pull_alt.png" height="24" width="24"/> '''Pull'''

=== Ward Fire ===
Shoot at the shields of Thugs, Felons and Convicts when nothing else is in range.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/ward_on.png" height="24" width="24"/> '''Ward Fire Enabled'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/ward_off.png" height="24" width="24"/> '''Ward Fire Disabled'''

=== Allow Attack Commands ===
State for [[Lobster]] to ignore attack commands and only respond to [[Fire_Special_Weapon_Command |'D' commands]].

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/disableattack_off.png" height="24" width="24"/> '''Disable Attack Off'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/disableattack_on.png" height="24" width="24"/> '''Disable Attack On'''

=== Fire Towards Enemies ===
Shoots towards enemies when there are no other targets.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/shoot_towards_off.png" height="24" width="24"/> '''Disabled'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/shoot_towards_on.png" height="24" width="24"/> '''Enabled'''

=== Avoid Bad Targets ===
Added in the [https://zero-k.info/Forum/Post/236870#236870 Anti-Bait update] , this state prevents a unit from automatically firing a long reload weapon at unit classes identified by metal cost.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bait_off_alternate.png" height="24" width="24"/> '''Disabled'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bait_1.png" height="24" width="24"/> '''Free''' — Avoid light drones ([[Firefly]] and [[Gull]]), [[Wind/Tidal Generator|Wind]], [[Solar Collector|Solar]], [[Claw]], [[Dirtbag]], nanoframes up to 50 metal and armoured targets (except [[Crab]]).

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bait_2.png" height="24" width="24"/> '''Light''' — As above, as well as units costing less than 90, [[Razor]], [[Sparrow]] and unidentified radar dots.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bait_3.png" height="24" width="24"/> '''Medium''' — As above, as well as units costing less than 240, except [[Stardust]], with the addition of [[Raptor]].

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bait_4.png" height="24" width="24"/> '''Heavy''' — As above, as well as units costing less than 420.

=== Puppy Replication ===
Set whether Puppies use nearby wrecks to make more Puppies.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/goo_on.png" height="24" width="24"/> '''On Except When Cloaked'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/goo_cloak.png" height="24" width="24"/> '''Always On'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/goo_off.png" height="24" width="24"/> '''Off'''

{{Navbox manual}}

Unit states

2022-01-09T11:26:46Z

Mach56: /* Avoid Bad Targets */ Add descriptions

{{TOC right}}
Most units and buildings have ''behavior states'' that can be set by the player to modify unit behavior on the fly. The state settings are set per unit to allow different behavior of the same unit types.

Some unit states are hidden by default. You can display them under [[Ingame Menu#Commands|Settings/Interface/Commands]].

[[File:Factory commands.png]]

The right side of the menu displays the settings of the selected units. This display is used to edit the settings. Clicking on a state toggles it. Most states with more than two settings can be toggled backwards with right click.

There is a subtlety in the use of this display: When multiple units in the selection have the same settings different states the display only shows one of the states. A displayed state does not guarantee all units in the selection have that state. Clicking on a state guarantees that every selected unit has the setting displayed after clicking.

== Factory States ==
Factories have many states that usually make no sense for an unarmed structure. Units produced by a factory inherit most of the factory's states if the units have no other default.

== Default States ==
Units can be set to adopt a particular state upon creation from the menu (under Settings/Unit Behaviour/Default). For instance, an artillery unit could be set to Hold Position by default.

== State List ==
Following is a list that explains each state and its settings.

=== Fire State ===
Firestate controls a unit's automatic targeting behaviour. This state is available for all armed units and structures. Player given commands and guard retaliation overrides firestate. As in a unit set to Hold Fire will still fire if it is given a direct order to attack. Units do not lose their current target when firestate changes.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/fire_atwill.png" height="24" width="24"/> '''Fire at Will''' — Fire at any/all enemies within range.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/fire_return.png" height="24" width="24"/> '''Return fire''' — Fire back at enemies that hurt the unit.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/fire_hold.png" height="24" width="24"/> '''Hold Fire''' — Will not fire unless ordered to.

=== Move State ===
Movestate controls how freely a unit can move in pursuit of its target. All mobile units have movestate.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/move_roam.png" height="24" width="24"/> '''Roam''' — The unit will move to attack nearby targets and chase them if they run away. Constructors will only assist ally construction if set to Roam.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/move_engage.png" height="24" width="24"/> '''Maneuver''' — This behaves similarly to Roam, but with a shorter "leash".

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/move_hold.png" height="24" width="24"/> '''Hold Position''' — Unit will not automatically chase enemies or use unit AI. Units will chase with an attack command and use unit AI if they have an Attack Move command.

=== Repeat ===
Repeat causes a unit's order queue to loop. Upon completing an order the order is added to the end of the queue. This is particularly useful for factories because a production queue can be repeated.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/repeat_on.png" height="24" width="24"/> '''Repeat On'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/repeat_off.png" height="24" width="24"/> '''Repeat Off'''

=== Overkill Prevention ===
Some units have ''overkill prevention'' (OKP), such that if only one unit needs to fire to kill the target, other units will try to find a different target instead. This reduces wasted shots, useful for long-reload units such as [[Scalpel]]s.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/overkill_on.png" height="24" width="24"/> '''Overkill Prevention On'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/overkill_off.png" height="24" width="24"/> '''Overkill Prevention Off'''

=== Retreat ===

Sets the retreat level. See [[Retreat]].

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/retreat_90.png" height="24" width="24"/> '''Max Retreat''' — Unit retreats to the closest retreat position when health drops below 99%.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/retreat_60.png" height="24" width="24"/> '''2/3 Retreat''' — Unit retreats to the closest retreat position when health drops below 65%.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/retreat_30.png" height="24" width="24"/> '''1/3 Retreat''' — Unit retreats to the closest retreat position when health drops below 30%.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/retreat_off.png" height="24" width="24"/> '''No Retreat''' — Unit does not auto-retreat.

=== Selection Rank ===
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/selection_rank_0.png" height="24" width="24"/>
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/selection_rank_1.png" height="24" width="24"/>
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/selection_rank_2.png" height="24" width="24"/>
<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/selection_rank_3.png" height="24" width="24"/>

See [[Selection#Selection_Rank|Selection Rank]]

=== Build Priority ===

Priority lets you control resource spending more accurately when spending exceeds income. See [[Economy_Guide#Priority |Economy Guide Priority]]

See also [[Resources Reserve]]

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_high.png" height="24" width="24"/> '''High Priority''' — Constructors are always funded.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_med.png" height="24" width="24"/> '''Normal Priority''' — This is the default. Constructors with this set have their priority overridden by the nanoframe they are constructing.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_low.png" height="24" width="24"/> '''Low Priority''' — Constructors use any resources left over to construct.

==== Misc Priority ====
Misc. priority is used for the unit's personal, non-construction resource consumption, i.e. from abilities like [[commander]] upgrades or [[Trinity]] stockpiling.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_high_other.png" height="24" width="24"/> '''High Priority'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_med_other.png" height="24" width="24"/> '''Normal Priority'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/wrench_low_other.png" height="24" width="24"/> '''Low Priority'''

=== Factory Assist ===

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/autoassist_on.png" height="24" width="24"/> '''Auto-assist Factory''' — Constructor do not follow the factory rally point. Instead they assist the factory that created them.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/autoassist_off.png" height="24" width="24"/> '''Default Behaviour''' — Constructor will continue to rally point when exiting factory.

=== Cloak ===

Toggles unit cloak. See [[Cloak]]

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/cloak_on.png" height="24" width="24"/> '''Enable Cloak'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/cloak_off.png" height="24" width="24"/> '''Disable Cloak'''

=== Unit AI ===

Toggles smart AI for the unit. See [[Unit AI]]

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bulb_on.png" height="24" width="24"/> '''Unit AI ON''' — Turn ON the game's default unit AI for this unit (skirm, skirmish, and/or Anti-Air AI).

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bulb_off.png" height="24" width="24"/> '''Unit AI OFF''' — Turn OFF the game's default unit AI for this unit.

=== On/Off ===
On/Off controls various miscellaneous unit states. It is used to toggle activation on radar, sonar and cloakers. It also toggles the armour ability of the [[Solar Collector]], [[Lucifer]] and [[Desolator]].

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/on.png" height="24" width="24"/> '''On'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/off.png" height="24" width="24"/> ''' Off'''

=== Idle State ===

Aircraft can be told to fly in a holding pattern or land when idle.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/fly_on.png" height="24" width="24"/> '''Free Flying''' — Unit continues flying when idle.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/fly_off.png" height="24" width="24"/> '''Land on Idle''' — Unit lands when idle.

=== Float State ===

Some amphibious units can float to the surface of the ocean to fire their weapons. They are immobile when floating

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/amph_float.png" height="24" width="24"/> '''Always Float''' — Unit automatically floats when idle.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/amph_attack.png" height="24" width="24"/> '''Float to Fire''' — Unit automatically floats if an enemy is in range and sinks otherwise. Units with long reload time sink between shots.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/amph_sink.png" height="24" width="24"/> '''Always Sink''' — Unit does not float.

=== Trajectory ===

Certain long range artillery units can be toggled between high and low trajectory firing.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/traj_high.png" height="24" width="24"/> '''High Trajectory''' — Shoot with a high arcing shot. This is useful for shooting over terrain that blocks direct line of sight, though it does moderately reduce accuracy.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/traj_low.png" height="24" width="24"/> '''Low Trajectory''' — Unit fire directly toward the enemy. This can be useful because directly fired projectiles are more accurate and spend less time in flight.

=== Fire at Radar ===
Some units with long-range precision weapons, like the Phantom and Lance, can be ordered not to fire on radar dots (i.e. targets inside radar range but outside visual range). These units will still fire on buildings outside line of sight if the target position is known precisely (indicated by the "ghost" building).

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/stealth_on.png" height="24" width="24"/> '''Fire at Radar Dots'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/stealth_off.png" height="24" width="24"/> '''Don't Fire at Radar Dots'''

=== Dive State ===

[[Raven]] by default dive bombs to attack units under area shields, and moving targets. It can also dive bomb normally or constantly fly at a lower altitude.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/divebomb_shield.png" height="24" width="24"/> '''Dive Bomb Shield or Mobile'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/divebomb_attack.png" height="24" width="24"/> '''Dive Bomb Mobile'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/divebomb_always.png" height="24" width="24"/> '''Always Fly Low''' — This causes it to fly at a lowered altitude all the time. It is weak to ground units in this state.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/divebomb_off.png" height="24" width="24"/> '''Always Fly High''' — Will not use dive bomb. This can make it difficult to hit moving or shielded targets.

=== Area Cloak ===

Toggles an area cloaker. Area cloak is also disabled if the unit's On/Off state is set to Off. See [[Cloak]]

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/areacloak_on.png" height="24" width="24"/> '''Activate Cloaking Field''' — Cloak all allied units within cloaking field radius.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/areacloak_off.png" height="24" width="24"/> '''Disengage Cloaking Field''' — Do not emit cloaking field.

=== Gunship Strafe ===
Most gunships can circle-strafe their target when attacking.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/strafe_on.png" height="24" width="24"/> '''Strafe''' — Dodge ground projectiles by circling over the targeted enemy.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/strafe_off.png" height="24" width="24"/> '''No Strafe''' — Deactivate strafing for gunships. Use this to keep out of range of static AA.

=== Kill Captured ===

[[Dominatrix]] can be set to automatically destroy units that it captures.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/capturekill_on.png" height="24" width="24"/> '''Auto-Self Destruct''' — Immediately self-destruct the captured units.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/capturekill_off.png" height="24" width="24"/> '''No Self Destruct''' — Maintain normal control over captured units, no self-destruct.

=== Drone Construction ===
Units capable of drone production can switch it on or off.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/drones_on.png" height="24" width="24"/> '''Production of drones is ongoing'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/drones_off.png" height="24" width="24"/> '''Production of drones is stopped'''

=== Impulse Mode ===
[[Newton]] and [[Jugglenaut]] can be set to push or pull units with their gravity guns.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/push_alt.png" height="24" width="24"/> '''Push'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/pull_alt.png" height="24" width="24"/> '''Pull'''

=== Ward Fire ===
Shoot at the shields of Thugs, Felons and Convicts when nothing else is in range.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/ward_on.png" height="24" width="24"/> '''Ward Fire Enabled'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/ward_off.png" height="24" width="24"/> '''Ward Fire Disabled'''

=== Allow Attack Commands ===
State for [[Lobster]] to ignore attack commands and only respond to [[Fire_Special_Weapon_Command |'D' commands]].

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/disableattack_off.png" height="24" width="24"/> '''Disable Attack Off'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/disableattack_on.png" height="24" width="24"/> '''Disable Attack On'''

=== Fire Towards Enemies ===
Shoots towards enemies when there are no other targets.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/shoot_towards_off.png" height="24" width="24"/> '''Disabled'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/shoot_towards_on.png" height="24" width="24"/> '''Enabled'''

=== Avoid Bad Targets ===
Added in the [https://zero-k.info/Forum/Post/236870#236870 Anti-Bait update] , this state prevents a unit from automatically firing a long reload weapon at unit classes identified by metal cost.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bait_off_alternate.png" height="24" width="24"/> '''Disabled'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bait_1.png" height="24" width="24"/> '''Free''' — Avoid light drones, [[Wind/Tidal Generator|Wind]], [[Solar Collector|Solar]], [[Claw]], [[Dirtbag]], nanoframes up to 50 metal and armoured targets (except [[Crab]]).

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bait_2.png" height="24" width="24"/> '''Light''' — As above, as well as units costing less than 90, [[Razor]], [[Sparrow]] and unidentified radar dots.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bait_3.png" height="24" width="24"/> '''Medium''' — As above, as well as units costing less than 240, except [[Stardust]], with the addition of [[Raptor]].

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bait_4.png" height="24" width="24"/> '''Heavy''' — As above, as well as units costing less than 420.

=== Puppy Replication ===
Set whether Puppies use nearby wrecks to make more Puppies.

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/goo_on.png" height="24" width="24"/> '''On Except When Cloaked'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/goo_cloak.png" height="24" width="24"/> '''Always On'''

<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/goo_off.png" height="24" width="24"/> '''Off'''

{{Navbox manual}}

Talk:Shogun

2021-12-06T03:57:36Z

Mach56:

nitpick: I'm not sure you can call it a psychological effect if the lore is that these are mecha/ai consider removing the word psychology.
: That's the ingame description, you'll want to make a ticket about it or post on discord/forums if you want it changed. [[User:Mach56|Mach56]] ([[User talk:Mach56|talk]]) 04:57, 6 December 2021 (CET)

Dirtbag

2021-11-23T07:39:43Z

Mach56: /* Tactics and Strategy */ spelling and adding the rover fac to affected players.

The '''{{PAGENAME}}''' is a light scout and obstruction unit from the [[Shieldbot Factory]].{{ Infobox zkunit
| name = Dirtbag
| defname = shieldscout
| description = Box of Dirt
| image = http://manual.zero-k.info/unitpics/shieldscout.png
| icontype = clogger
| cost = 30
| hitpoints = 600
| movespeed = 84
| turnrate = 396
| sight = 600
| transportable = Light
| weapons =
{{ Infobox zkweapon
| name = Headbutt
| type = BeamLaser
| damage = 55
| reloadtime = 1.90
| dps = 29
| range = 50
| special1 = Instantly hits
| special2 = Ignores shields
| special3 = Water capable
| special4 = Passes through ground
}}
| abilities =
{{ Infobox zkability jump
| range = 400
| reload = 10
| speed = 180
| midairjump = No
}}
{{ Infobox zkability line
| customdata1 = Instant self-destruction
}}
}}==Description==
The Dirtbag exists to block enemy movement and generally get in the way. They are so dedicated to this task that they release their dirt payload upon death to form [[Terraform|little annoying mounds]]. While waiting for their fate Dirtbags enjoy headbutting and scouting.

= Tactics and Strategy =
Highly utilitarian, literally dirt-cheap. Annoying. The Dirtbag can serve in a number of ways and sometimes turns out to be a game-changing unit.

While a bit slower then a [[Bandit]], Dirtbags are also twice as cheap, and have an ability to jump, which, combined with having the same vision radius, turns them into a great scout early game. As a last-ditch effort, Dirtbag can try to self-detonate on enemy metal spots, restricting the [[mex]] construction. Kind of annoying.

As such, Dirtbags also serve as excellent screens against units such as [[Widow]]s or [[Phantom]]s, but they will require some fire support to completely drive off the enemy. They also one-shot [[Flea]]s. Irritating, huh?

The Dirtbag can turn game for [[Rover Assembly]], [[Hovercraft Platform]], and [[Tank Foundry]] players into a clumsy mess. After death, Dirtbags spawn a [[Terraform|little ugly mound]], about the height of their legs. In mass, this can turn the battlefield into a claustrophobic unreadable horror of a terrain, providing you with a cheap terraforming option, and a huge advantage if you or your allies switch into [[Spider Factory]]. Beware, that the mounds will form wherever the Dirtbag dies, and will potentially restrict your [[Radar Tower|radar]] vision. Pesky little things.

Finally, Dirtbags can draw fire, helping during charges on [[Stinger]]s and other defences alike, being a target for [[Lance]]s, clog up [[Jugglenaut]]s in pull mode, draw out [[Imp]]s and much more. When someone hits you, try throwing some dirt in their face, turns out it might just help.
{{Navbox units}}

Factory Plates

2021-11-14T02:41:21Z

Mach56: Grammar

'''{{PAGENAME}}''' are an alternate method of increasing production. Instead of boosting a single factory with [[Caretaker]]s or constructors, a factory plate is a cheap way to double a factory's throughput. A factory plate requires a factory of the same type within a short distance (seen as a circle surrounding the factory) to work. When selecting a factory to place should there be another factory of the same type already placed and friendly there will be a line drawn to it. Moving the factory ghost into the circle will automatically convert it into a plate.
==Tips and Strategy==
A factory plate is cheaper than a Caretaker, another factory, or any 2 constructors, so consider building one as an alternative to a Caretaker for increased production.

Factory plates are very useful in team games, as each player can choose a different factory at the start, and a player can build a plate at someone else's factory should they want that factory's units.

However, for expensive units such as the [[Grizzly]] or [[Jugglenaut]], consider building Caretakers instead, as factory plates cannot help the main factory or other plates with creating units. Though should there be a sudden, urgent need for smaller units, a plate will allow the continued production of the expensive unit while the smaller ones are being produced, instead of having to cancel the large unit and switch to the smaller ones.

{{navbox manual}}

Transportation

2021-11-08T11:03:26Z

Mach56: /* Mass and Capacity */ A unit's mass is not equal to its cost, it is arbitrary.

Transports are used to rapidly move ground and sea forces around the battlefield. There are two transports: [[Charon]] and [[Hercules]]. Both are constructed at the [[Gunship Plant]].

[[Teleportation]] is an alternative means of transportation.

== Basic Commands and Abilities ==

=== Mass and Capacity ===
Transports can pick up and carry a single unit at a time.

[[Charon]] can carry '''light''' and '''medium''' units while [[Hercules]] can carry any transportable unit. Transports cannot carry air units or the ship Striders [[Shogun]] and [[Reef]]. A unit's transportability depends on its metal cost. Light units are units below or equal to 500 metal, medium units are between 501 and 1000 metal, and heavy units are everything else. A unit's transportability and mass can be viewed in an information window by {{key press|Space}}-clicking on the unit.

Laden transports have a speed penalty depending on the mass of their cargo. Transports receive no additional speed penalty for transporting units up to their own mass, otherwise, they have a speed modifier of {{frac|2 × <var>selfMass</var>|{{expr|<var>selfMass</var> + <var>cargoMass</var>}}}}.

=== Loading ===
Transports can pick up any valid <em>stationary</em> unit, including stunned enemies. They have to physically lower themselves onto a unit to pick it up. This process can take a few seconds, depending on the target. There are two ways to load units:
# Issue the [[Load Command|'''Load''']] command (hotkey {{key press|L}}) to a transport to load the target unit. This command is generally available as a right-click context command. Issue an area command with by clicking and dragging to tell multiple transports to load a group of units.
# Select a mixed selection of transports and ground units and issue the '''Load Selected Units''' command (double-tap {{key press|L}}) to have the transports load the selected units. Idle units will be loaded into the transports while units with orders will be loaded and transported to the end of their order queue.

=== Unloading ===
Transports can either carefully place their cargo on the ground, or they can eject it in-flight.
* Use the [[Unload Command|'''Unload''']] command (hotkey {{key press|U}}) to unload carefully. This command can be issued in an area selected by clicking and dragging or along a line by {{key press|Alt}}-clicking and dragging.
* Use the [[Eject Cargo Command|'''Eject Cargo''']] command (hotkey {{key press|D}}) to drop transported units. This may damage the dropped units. Transports carrying bombs draw a target where the bomb is going to hit on the ground based on their velocity.

== Transport AI ==
'''Transport AI''' can be toggled with the unit AI state toggle (<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bulb_on.png" height="18">) on transports.

Transports can be set to [[Guard Command|guard]] a factory to automatically pick up newly created units and drop them off at the end of the rally queue.

There are two queueable commands: ''Embark'' [[File:Embark.png|18px]] and ''Disembark'' [[File:Disembark.png|18px]]—these commands appear on transportable land units and factories when you build your first air transport.
*'''Embark'''—wait for transport to pick me up. Transportes called by the ''Embark'' command will return to the spot where they took the unit using the same path.
*'''Disembark'''—safely exit and from the transport.

=== Benefit ===
A transport might skip some units because it finds it pointless to transport them. It takes several things into account—distance of transport from unit, planned unit path, unit speed, transport speed, transport land times, terrain height differences—all of this is used to estimate the "benefit" of transporting a given unit with the air transport.

'''Benefit''' is the number of seconds saved by using a transport. It transports units only if benefit is greater than five seconds and in the order of benefit (slowest units will be transported first, fast units might be ignored completely). The exception to this is the ''Embark'' command, which serves as "priority" transport—units waiting with the ''Embark'' command will be served first.

=== Possible uses ===
# Give bot factory waypoints through safe area next to the current battlefield.
#* Result: Units walk along these waypoints and if there are idle transports they will pick them up and transport them to their destination.
# Give factory waypoint to ally's base entrance followed by [[Patrol Command|patrol]].
#* Result: Units walk there and if transport nearby it will pick it up, drop it off and the unit will start patrolling.
# Give factory a move order near your base, ''Embark'', then move to an impassable mountain.
#* Result: Units will emerge from factory and enter ''Embark'' mode—they will stand there and wait for transport to get them to the mountain.
# Select crawling bombs, click to move to enemy base then click ''Embark''.
#* Result: Bombs will stop and wait for transports, transports will carry them to enemy base.
# Select Dantes, give them move commands across air safe areas, followed by disembark from behind the base spot and move to enemy base. Then click ''Embark''.
#* Result: Dantes will stop and wait for transports. Transport will carry them along the waypoints to back of enemy base, unload them. From there Dantes will continue on foot.

== Ferry routes ==
Ferry routes automate transports to travel units across a set path to a destination. The <abbr title="user interface">UI</abbr> for creating ferry routes is (by default) in the upper left corner bar next to ''retreat and repair''. The symbol is a red circle with a ray pointing out of it to the right ([[File:Ferry.png|18px]]). To create a ferry route, first left-click the ferry route button, next left-click the start location of your ferry route, then left-click the destination. A ferry route does not have to be just a straight line. The path to take can twist and turn all you like by holding {{key press|Shift}} and left-clicking between the starting area and destination. Your ferry route will appear as a hard red circle indicating the start and a line directing out of that circle towards the destination.

Transports return to the spot where they took a unit using the same path.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/XHY0vP7.mp4" controls="true"></htmltag>

You can even edit your ferry route by clicking the ferry route button, holding {{key press|Shift}} and clicking where you placed a start, end, or corner to select it, and then clicking where you want that point to be.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/WC2qb03.mp4" controls="true"></htmltag>

To remove a ferry route, click the ferry route button and left-click a start location.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/SHFhe68.mp4" controls="true"></htmltag>

Now that you have your ferry route, it's time to put it to use! Assign transports to the ferry route by issuing a move command into the start circle. The transports will now stay within a short distance of the start, even if you try and move them away, waiting for units. Take a unit you want to ferry and issue a move order into the circle. Once the unit is in the circle, it will wait for a transport to pick it up and move it to the end of the ferry route. You can shift queue commands for the unit, and it will follow the commands after arrival at the destination.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/No0wGkg.mp4" controls="true"></htmltag>

Potential uses for ferry routes:
*To move a large army around static anti-air cover to far locations, as the transports will follow the route both to and from the location.
*You can set your factory's waypoint to the ferry route start, and units will wait for transports to ferry them.

There are a few bugs with the system, such as if you assign a transport to a ferry route one time it may be unable to ever be assigned to a different ferry route, sometimes units won't seen to call for transports when they are in the start circle. if you have a gunship plant's rally point in a ferry route, the transports will wait for transport instead of being added to the ferry route, so you need to manually move them into the circle. There seem to be cases where there are both units and transports at the start location, but the units wait for a transport that is already off on it's ferry mission to come back and pick them up, which is undesired. Somehow, units seem to wait for a transport outside the circle, and thus never get a transport to pick them up. If a unit is waiting and not picked up, it will never get assigned a wait command when issuing a move command into the circle, and if you want it to be ferried, you must manually issue a wait command on the unit while it is inside the ferry circle. If the <abbr title="landing zone">LZ</abbr> is cluttered with units at the end of the ferry, transports will get stuck and not place units down, instead just holding them hostage over the end point. All in all, while automated, ferry routes require periodical check-ups.

{{Navbox manual}}

Transportation

2021-10-30T12:51:22Z

Mach56: /* Mass and Capacity */ Changed metal cost back to mass, and added a note that mass is equal to metal cost.

Transports are used to rapidly move ground and sea forces around the battlefield. There are two transports: [[Charon]] and [[Hercules]]. Both are constructed at the [[Gunship Plant]]. This page is about their uses and abilities. See a different page for [[teleportation]].

= '''Basic Commands and Abilities''' =

=== Mass and Capacity ===
Transports can pick up and carry a single unit at a time. A unit's mass is equal to its cost, so more expensive units are also heavier.

[[Charon]] can carry '''light''' and '''medium''' units while [[Hercules]] can carry any transportable unit. Transports cannot carry air units or the ship Striders: [[Shogun]] and [[Reef]]. Light units are units below or equal to 500 mass, medium units are between 501 and 1000 mass, and heavy units are everything else. A unit's transportability and mass can be viewed in an information window by Space+Clicking on the unit.

Laden transports have a speed penalty depending on the mass of their cargo. Transports receive no additional speed penalty for transporting units up to their own mass, otherwise, they have a speed modifier of <code>2*selfMass / (selfMass + cargoMass)</code>.

=== Loading ===
Transports can pick up any valid stationary unit, including stunned enemies. Transports have to physically lower themselves onto a unit to pick it up. This process can take a few seconds, depending on the target. Here are two ways to load units:
* Issue the [[Load Command|'''Load''']] command (hotkey '''L''') to a transport to load the target unit. This command is generally available as a right-click context command. Issue an area command with Click+Drag to tell multiple transports to load a group of units
* Select a mixed selection of transports and ground units and issue the '''Load Selected Units''' command (double tap '''L''') to have the transports load the selected units. Idle units will be loaded into the transports while units with orders will be loaded and transported to the end of their order queue.

=== Unloading ===
Transports can either carefully place their cargo on the ground or they can eject it in-flight.
* Use the [[Unload Command|'''Unload''']] command (hotkey '''U''') to unload carefully. This command can be issued in an area with Click+Drag or along a line with Alt+Click+Drag.
* Use the [[Eject Cargo Command|'''Eject Cargo''']] command (hotkey '''D''') to drop transported units. This may damage the dropped units. Transports carrying bombs draw a target on the ground based on their velocity.

= '''Transport AI''' =
[[Transport AI|'''Transport AI''']] can be toggled with the unit AI state toggle (<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bulb_on.png" height='18' align="center" />) on transports. It has a few different aspects:
* Transports can be set to [[Guard Command|guard]] a factory to automatically pick up newly created units and drop them off at the end of the rally queue.
* Two queueable commands: ''Embark'' [[File:Embark.png|18px]] and ''Disembark'' [[File:Disembark.png|18px]] - these commands appear on transportable land units and factories when you build your first air transport. '''Embark''' — wait for transport to pick me up. '''Disembark''' — disembark from transport.

=== Possible uses ===
# Give bot factory waypoints through safe area next to the current battlefield.
#* Result: Units walk along these waypoints and if there are idle transports they will pick them up and transport them to their destination.
# Give factory waypoint to ally's base entrance followed by [[Patrol Command|patrol]].
#* Result: Units walk there and if transport nearby it will pick it up, drop it off and the unit will start patrolling.
# Give factory a move order near your base, ''Embark'', then move to an impassable mountain.
#* Result: Units will emerge from factory and enter ''Embark'' mode - they will stand there and wait for transport to get them to the mountain.
# Select crawling bombs, click to move to enemy base then click ''Embark''.
#* Result: Bombs will stop and wait for transports, transports will carry them to enemy base.
# Select Dantes, give them move commands across air safe areas, followed by disembark from behind the base spot and move to enemy base. Then click ''Embark''.
#* Result: Dantes will stop and wait for transports. Transport will carry them along the waypoints to back of enemy base, unload them. From there Dantes will continue on foot.

=== Notes and details ===
* Transported called by the '''Embark''' command will return to the spot where they took unit using the same path.
* Transports might skip some units because it finds it useless to transport them. It takes several things into account - distance of transport from unit, planned unit path, unit speed, transport speed, transport land times, terrain height differences - all of this is used to estimate the "benefit" of transporting given unit with air transport. Benefit = number of seconds saved by using transporter. It only transports units if benefit is higher than 5 seconds and in order of benefit (slowest units will be transported first, fast units might be ignored completely). Exception to this is the ''Embark'' command which serves as "priority" transport - units waiting with the ''Embark'' command will be served first.

= '''Ferry routes''' =
Ferry routes automate transports to travel units across a set path to a destination. The UI for creating ferry routes is (by default) in the upper left corner bar next to retreat and repair. The symbol is a red circle with a ray pointing out of it to the right ([[File:Ferry.png|18px]]). To create a ferry route, first left click the ferry route button, next left click the start location of your ferry route, then left click the destination. A ferry route does not have to be just a straight line, the path to take can twist and turn all you like by holding shift and left clicking between setting the start and destination. Your ferry route will appear as a hard red circle indicating the start and a line directing out of that circle towards the end.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/XHY0vP7.mp4" controls="true"></htmltag>

You can even edit your ferry route, by clicking the ferry route button, hold shift and click on anyplace you placed a start, end, or corner to select it, and then click where you want that point to be.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/WC2qb03.mp4" controls="true"></htmltag>

To remove a ferry route, click the ferry route button and left click a start location.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/SHFhe68.mp4" controls="true"></htmltag>

Now that you have your ferry route, it's time to put it to use! Assign transports to the ferry route by issuing a move command into the start circle. The transtports will now stay within a short distance of the start, even if you try and move them away, waiting for units. take a unit you want to ferry, and issue a move order into the circle. Once the unit is in the circle, it will wait for a transport to pick it up and move it to the end of the ferry route. you can shift queue commands for the unit and it will follow the commands after the transport.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/No0wGkg.mp4" controls="true"></htmltag>

Potential uses for ferry routes are to move a large army around static anti-air cover to far locations, as the transports will follow the route both to and from the location. You can set your factory's way-point to the ferry route start, and units will wait for transports to ferry them.

There are a few bugs with the system, such as if you assign a transport to a ferry route one time it may be unable to ever be assigned to a different ferry route, sometimes units won't seen to call for transports when they are in the start circle. if you have a gunship plant's rally point in a ferry route, the transports will wait for transport instead of being added to the ferry route, so you need to manually move them into the circle. There seem to be cases where there are both units and transports at the start location, but the units wait for a transport that is already off on it's ferry mission to come back and pick them up, which is undesired. Somehow, units seem to wait for a transport outside the circle, and thus never get a transport to pick them up.If a unit is waiting and not picked up, it will never get assigned a wait command when issuing a move command into the circle, and if you want it to be ferried, you must manually issue a wait command on the unit while it is inside the ferry circle. If the LZ is cluttered with units at the end of the ferry, transports will get stuck and not place units down, instead just holding them hostage over the end point. All in all, while automated, ferry routes require periodical check-ups.

=== Notes and details ===
* In all of these cases transports return to the spot where they took unit using the same path.

{{Navbox manual}}

Transportation

2021-10-30T12:46:45Z

Mach56: /* Mass and Capacity */

Transports are used to rapidly move ground and sea forces around the battlefield. There are two transports: [[Charon]] and [[Hercules]]. Both are constructed at the [[Gunship Plant]]. This page is about their uses and abilities. See a different page for [[teleportation]].

= '''Basic Commands and Abilities''' =

=== Mass and Capacity ===
Transports can pick up and carry a single unit at a time.

[[Charon]] can carry '''light''' and '''medium''' units while [[Hercules]] can carry any transportable unit. Transports cannot carry air units or the ship Striders: [[Shogun]] and [[Reef]]. Light units are units below or equal to 500 metal, medium units are between 501 and 1000 metal, and heavy units are everything else. A unit's transportability and mass can be viewed in an information window by Space+Clicking on the unit.

Laden transports have a speed penalty depending on the metal cost of their cargo. Transports receive no additonal speed penalty for transporting units up to their own mass, otherwise, they have a speed modifier of <code>2*selfMass / (selfMass + cargoMass)</code>.

=== Loading ===
Transports can pick up any valid stationary unit, including stunned enemies. Transports have to physically lower themselves onto a unit to pick it up. This process can take a few seconds, depending on the target. Here are two ways to load units:
* Issue the [[Load Command|'''Load''']] command (hotkey '''L''') to a transport to load the target unit. This command is generally available as a right-click context command. Issue an area command with Click+Drag to tell multiple transports to load a group of units
* Select a mixed selection of transports and ground units and issue the '''Load Selected Units''' command (double tap '''L''') to have the transports load the selected units. Idle units will be loaded into the transports while units with orders will be loaded and transported to the end of their order queue.

=== Unloading ===
Transports can either carefully place their cargo on the ground or they can eject it in-flight.
* Use the [[Unload Command|'''Unload''']] command (hotkey '''U''') to unload carefully. This command can be issued in an area with Click+Drag or along a line with Alt+Click+Drag.
* Use the [[Eject Cargo Command|'''Eject Cargo''']] command (hotkey '''D''') to drop transported units. This may damage the dropped units. Transports carrying bombs draw a target on the ground based on their velocity.

= '''Transport AI''' =
[[Transport AI|'''Transport AI''']] can be toggled with the unit AI state toggle (<img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bulb_on.png" height='18' align="center" />) on transports. It has a few different aspects:
* Transports can be set to [[Guard Command|guard]] a factory to automatically pick up newly created units and drop them off at the end of the rally queue.
* Two queueable commands: ''Embark'' [[File:Embark.png|18px]] and ''Disembark'' [[File:Disembark.png|18px]] - these commands appear on transportable land units and factories when you build your first air transport. '''Embark''' — wait for transport to pick me up. '''Disembark''' — disembark from transport.

=== Possible uses ===
# Give bot factory waypoints through safe area next to the current battlefield.
#* Result: Units walk along these waypoints and if there are idle transports they will pick them up and transport them to their destination.
# Give factory waypoint to ally's base entrance followed by [[Patrol Command|patrol]].
#* Result: Units walk there and if transport nearby it will pick it up, drop it off and the unit will start patrolling.
# Give factory a move order near your base, ''Embark'', then move to an impassable mountain.
#* Result: Units will emerge from factory and enter ''Embark'' mode - they will stand there and wait for transport to get them to the mountain.
# Select crawling bombs, click to move to enemy base then click ''Embark''.
#* Result: Bombs will stop and wait for transports, transports will carry them to enemy base.
# Select Dantes, give them move commands across air safe areas, followed by disembark from behind the base spot and move to enemy base. Then click ''Embark''.
#* Result: Dantes will stop and wait for transports. Transport will carry them along the waypoints to back of enemy base, unload them. From there Dantes will continue on foot.

=== Notes and details ===
* Transported called by the '''Embark''' command will return to the spot where they took unit using the same path.
* Transports might skip some units because it finds it useless to transport them. It takes several things into account - distance of transport from unit, planned unit path, unit speed, transport speed, transport land times, terrain height differences - all of this is used to estimate the "benefit" of transporting given unit with air transport. Benefit = number of seconds saved by using transporter. It only transports units if benefit is higher than 5 seconds and in order of benefit (slowest units will be transported first, fast units might be ignored completely). Exception to this is the ''Embark'' command which serves as "priority" transport - units waiting with the ''Embark'' command will be served first.

= '''Ferry routes''' =
Ferry routes automate transports to travel units across a set path to a destination. The UI for creating ferry routes is (by default) in the upper left corner bar next to retreat and repair. The symbol is a red circle with a ray pointing out of it to the right ([[File:Ferry.png|18px]]). To create a ferry route, first left click the ferry route button, next left click the start location of your ferry route, then left click the destination. A ferry route does not have to be just a straight line, the path to take can twist and turn all you like by holding shift and left clicking between setting the start and destination. Your ferry route will appear as a hard red circle indicating the start and a line directing out of that circle towards the end.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/XHY0vP7.mp4" controls="true"></htmltag>

You can even edit your ferry route, by clicking the ferry route button, hold shift and click on anyplace you placed a start, end, or corner to select it, and then click where you want that point to be.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/WC2qb03.mp4" controls="true"></htmltag>

To remove a ferry route, click the ferry route button and left click a start location.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/SHFhe68.mp4" controls="true"></htmltag>

Now that you have your ferry route, it's time to put it to use! Assign transports to the ferry route by issuing a move command into the start circle. The transtports will now stay within a short distance of the start, even if you try and move them away, waiting for units. take a unit you want to ferry, and issue a move order into the circle. Once the unit is in the circle, it will wait for a transport to pick it up and move it to the end of the ferry route. you can shift queue commands for the unit and it will follow the commands after the transport.

<htmltag tagname="video" width="560" height="320" loop="true" autoplay="true" src="https://i.imgur.com/No0wGkg.mp4" controls="true"></htmltag>

Potential uses for ferry routes are to move a large army around static anti-air cover to far locations, as the transports will follow the route both to and from the location. You can set your factory's way-point to the ferry route start, and units will wait for transports to ferry them.

There are a few bugs with the system, such as if you assign a transport to a ferry route one time it may be unable to ever be assigned to a different ferry route, sometimes units won't seen to call for transports when they are in the start circle. if you have a gunship plant's rally point in a ferry route, the transports will wait for transport instead of being added to the ferry route, so you need to manually move them into the circle. There seem to be cases where there are both units and transports at the start location, but the units wait for a transport that is already off on it's ferry mission to come back and pick them up, which is undesired. Somehow, units seem to wait for a transport outside the circle, and thus never get a transport to pick them up.If a unit is waiting and not picked up, it will never get assigned a wait command when issuing a move command into the circle, and if you want it to be ferried, you must manually issue a wait command on the unit while it is inside the ferry circle. If the LZ is cluttered with units at the end of the ferry, transports will get stuck and not place units down, instead just holding them hostage over the end point. All in all, while automated, ferry routes require periodical check-ups.

=== Notes and details ===
* In all of these cases transports return to the spot where they took unit using the same path.

{{Navbox manual}}

Unique Commands

2021-10-19T12:32:23Z

Mach56: /* Speed Boost */ Spelling

Several units have special abilities that are activated with '''unique commands'''. These are bound to the {{key press|D}} key by default (similar to [[Fire Special Weapon Command|Special Weapons]]).

== Speed Boost ==
http://manual.zero-k.info/unitpics/planefighter.png [[File:Cmd sprint.png]]

The [[Swift]] multirole fighter has an ability to temporarily receive a massive boost to its flight speed through he use of the '''Speed Boost''' instant command. This is extremely useful to dodge missiles, avoid losing engagements, or quickly intercept incoming enemy bombers. While most of the uses of Speed Boost are manual, this ability will be automatically used when [[retreat]]ing.

== Teleport Beacon ==
http://manual.zero-k.info/unitpics/amphtele.png [[File:Cmd drop beacon.png]]

The [[Djinn]] amphibious teleporter works by warping the units from its Lamp teleport beacon to its present deployed location. It can relocate the Lamp entry point by using the '''Teleport Beacon''' ability on any desired point on the map, as long as it's not blocked by an occupying structure or impassable terrain. For more information on teleportation refer to [[teleportation|this]] page.

== Drop Bombs ==
http://manual.zero-k.info/unitpics/gunshipkrow.png [[File:Cmd bomb.png]]

The [[Krow]] flying fortress has a special weapon that is only activated by the instant '''Drop Bombs''' command. Immediately upon command activation, the unit unleashes a salvo of bomblets directly beneath it, lasting several seconds.

The Krow has a significantly lowered acceleration and turn rate during the bombing run.

== Unleash Lightning ==
http://manual.zero-k.info/unitpics/bomberdisarm.png [[File:Cmd bomb.png]]

The [[Thunderbird]] disarm bomber has only one weapon and will use it automatically upon designated targets. However, it is also possible to activate the lightning weapon immediately by the manual '''Unleash Lightning''' command - usually in response to unexpected maneuvers by the targeted enemies.

== See also ==
{{See|Self Destruct Command}}
[[Unit classes#Mobile Bombs|Bombs]] have a command that allows them to quickly detonate.

{{Navbox commands}}

Fire Special Weapon Command

2021-09-29T00:48:44Z

Mach56: /* Commander's Special */ spell "cannon" correctly

Unique weapons, activated separately and manually by pressing {{key press|D}} by default. Unlike [[Unique Commands]] arsenal, those weapons function more like already existing ones in overclock mode.

== Multi-Stunner ==

http://manual.zero-k.info/unitpics/striderscorpion.png [[File:Cmd dgun.png]]

The [[Scorpion]] infiltrator has a medium range (about most skirmishers' reach) multiple-hit stunner. Upon activation, it strikes in a small arc, completely disabling anything in its path (including friendlies). Combined with Scorpion's inherent [[cloak|personal cloak]], the unit gains large tactical usage, as it is capable of both stealthily approaching and disabling large chunks of tightly grouped armies and high-priority units, or even helping to stage its own escape.

== Napalm Rocket Salvo ==

http://manual.zero-k.info/unitpics/striderdante.png [[File:Cmd dgun.png]]

The [[Dante]] assault/riot strider has a medium to long range napalm rocket salvo. When activated, the strider launches a barrage of 20 missiles, each dealing low damage, but leaving a strong napalm concoction behind. This weapon allows Dante reach over its intended (and expected by your enemies) range, even allowing it to go past the salvo's range itself, as missiles can fly way past their maximum launch radius. Rocket salvo can be used to dispatch bunched up light enemy units, deter skirmishers which can put pressure on this strider due to range advantage, or even punish air force fleets of your enemies.

== Disarm Missile ==

http://manual.zero-k.info/unitpics/shipcarrier.png [[File:Cmd dgun.png]]

The [[Reef]] aircraft carrier has a long range disarm missile. When used, it disarms any unit or structure in a large radius. While Reef is able to stock up on those missiles, allowing for rapid fire, they're also quite costly (150 [[metal]] apiece), and their production consumes 5 metal each second.

== EMP Missiles ==

http://manual.zero-k.info/unitpics/striderbantha.png [[File:Cmd dgun.png]]

The [[Paladin]] support strider carries EMP missiles. This allows it to launch salvos of 12 such armaments, providing complete disabling effect over a large area. Firing this weapon at farther targets sharply decreases its accuracy. This, in combination with Paladin's long range and lightning cannons allows this strider to contain large portions of enemy army, offer support during attacks and more.

== Obliteration Blaster ==

http://manual.zero-k.info/unitpics/striderdetriment.png [[File:Cmd dgun.png]]

The [[Detriment]] ultimate assault strider has a powerful obliteration blaster. The weapon fires ten powerful shots in quick succession, dealing heavy damage. Use mainly against enemy striders or other heavy units, as a single volley can kill any unit from full health except a Paladin or another Detriment.

== Commander's Special ==

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commstrike.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commassault.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commrecon.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commsupport.png [[File:Cmd dgun.png]]

Once [[Commander]]s upgrade to level 4, you can choose to forgo a second normal weapon to gain a special weapon. There are several options, depending on the starting chassis. These include:

https://zero-k.info/img/avatars/commweapon_clusterbomb.png Cluster bomb — available for Guardian and Recon — lets out a close-range shotgun-like blast of 8 high-damage pellets. Comparable to rocket salvos of [[Revenant]].

https://zero-k.info/img/avatars/commweapon_concussion.png Concussion shell — available for Recon — fires one short impulse with medium damage and strong toss effect.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_sunburst.png Disintegrator — available for Guardian and Strike — directed beam of energy with an extremely high alpha damage potential, functions like [[Ultimatum]]'s cannon.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_disruptorbomb.png Disruptor bomb — available for Strike, Recon and Engineer — launches a single bomb with large AOE blast inflicting slow effect on targets. Think of it as of a larger area [[Limpet]] on request.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_napalmgrenade.png Hellfire grenade — available for Guardian and Recon — launches a single bomb with large AOE blast inflicting low damage and leaving a strong napalm concoction behind. An [[Inferno]]-like deterrent.

https://zero-k.info/img/avatars/commweapon_multistunner.png Multi-stunner — available for Strike, Recon and Engineer — strikes in a small arc, completely disabling anything in its path (including friendlies). Somewhat weaker equivalent of Scorpion's special weapon.

https://zero-k.info/img/avatars/commweapon_slamrocket.png S.L.A.M. — available for Guardian — launches a tactical nuclear missile with high vertical arc-like trajectory. Functions as a somewhat weaker equivalent of [[Eos]].

{{Navbox commands}}

Fire Special Weapon Command

2021-09-29T00:47:07Z

Mach56: /* Obliteration Blaster */ State how many shots are fired

Unique weapons, activated separately and manually by pressing {{key press|D}} by default. Unlike [[Unique Commands]] arsenal, those weapons function more like already existing ones in overclock mode.

== Multi-Stunner ==

http://manual.zero-k.info/unitpics/striderscorpion.png [[File:Cmd dgun.png]]

The [[Scorpion]] infiltrator has a medium range (about most skirmishers' reach) multiple-hit stunner. Upon activation, it strikes in a small arc, completely disabling anything in its path (including friendlies). Combined with Scorpion's inherent [[cloak|personal cloak]], the unit gains large tactical usage, as it is capable of both stealthily approaching and disabling large chunks of tightly grouped armies and high-priority units, or even helping to stage its own escape.

== Napalm Rocket Salvo ==

http://manual.zero-k.info/unitpics/striderdante.png [[File:Cmd dgun.png]]

The [[Dante]] assault/riot strider has a medium to long range napalm rocket salvo. When activated, the strider launches a barrage of 20 missiles, each dealing low damage, but leaving a strong napalm concoction behind. This weapon allows Dante reach over its intended (and expected by your enemies) range, even allowing it to go past the salvo's range itself, as missiles can fly way past their maximum launch radius. Rocket salvo can be used to dispatch bunched up light enemy units, deter skirmishers which can put pressure on this strider due to range advantage, or even punish air force fleets of your enemies.

== Disarm Missile ==

http://manual.zero-k.info/unitpics/shipcarrier.png [[File:Cmd dgun.png]]

The [[Reef]] aircraft carrier has a long range disarm missile. When used, it disarms any unit or structure in a large radius. While Reef is able to stock up on those missiles, allowing for rapid fire, they're also quite costly (150 [[metal]] apiece), and their production consumes 5 metal each second.

== EMP Missiles ==

http://manual.zero-k.info/unitpics/striderbantha.png [[File:Cmd dgun.png]]

The [[Paladin]] support strider carries EMP missiles. This allows it to launch salvos of 12 such armaments, providing complete disabling effect over a large area. Firing this weapon at farther targets sharply decreases its accuracy. This, in combination with Paladin's long range and lightning cannons allows this strider to contain large portions of enemy army, offer support during attacks and more.

== Obliteration Blaster ==

http://manual.zero-k.info/unitpics/striderdetriment.png [[File:Cmd dgun.png]]

The [[Detriment]] ultimate assault strider has a powerful obliteration blaster. The weapon fires ten powerful shots in quick succession, dealing heavy damage. Use mainly against enemy striders or other heavy units, as a single volley can kill any unit from full health except a Paladin or another Detriment.

== Commander's Special ==

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commstrike.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commassault.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commrecon.png https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commsupport.png [[File:Cmd dgun.png]]

Once [[Commander]]s upgrade to level 4, you can choose to forgo a second normal weapon to gain a special weapon. There are several options, depending on the starting chassis. These include:

https://zero-k.info/img/avatars/commweapon_clusterbomb.png Cluster bomb — available for Guardian and Recon — lets out a close-range shotgun-like blast of 8 high-damage pellets. Comparable to rocket salvos of [[Revenant]].

https://zero-k.info/img/avatars/commweapon_concussion.png Concussion shell — available for Recon — fires one short impulse with medium damage and strong toss effect.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_sunburst.png Disintegrator — available for Guardian and Strike — directed beam of energy with an extremely high alpha damage potential, functions like [[Ultimatum]]'s canon.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_disruptorbomb.png Disruptor bomb — available for Strike, Recon and Engineer — launches a single bomb with large AOE blast inflicting slow effect on targets. Think of it as of a larger area [[Limpet]] on request.

https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/commweapon_napalmgrenade.png Hellfire grenade — available for Guardian and Recon — launches a single bomb with large AOE blast inflicting low damage and leaving a strong napalm concoction behind. An [[Inferno]]-like deterrent.

https://zero-k.info/img/avatars/commweapon_multistunner.png Multi-stunner — available for Strike, Recon and Engineer — strikes in a small arc, completely disabling anything in its path (including friendlies). Somewhat weaker equivalent of Scorpion's special weapon.

https://zero-k.info/img/avatars/commweapon_slamrocket.png S.L.A.M. — available for Guardian — launches a tactical nuclear missile with high vertical arc-like trajectory. Functions as a somewhat weaker equivalent of [[Eos]].

{{Navbox commands}}

Charon

2021-09-28T06:05:33Z

Mach56: Add medium unit transport stats to charon

The '''{{PAGENAME}}''' is an air transport from the [[Gunship Plant]].{{ Infobox zkunit
| name = Charon
| defname = gunshiptrans
| description = Air Transport
| image = http://manual.zero-k.info/unitpics/gunshiptrans.png
| icontype = gunshiptransport
| cost = 100
| hitpoints = 300
| movespeed = 345
| turnrate = 91
| sight = 300
| abilities =
{{ Infobox zkability intel
| name = Transporting
| special1 = Transports light units at 70% speed
| special2 = Transports medium units at 50% speed
}}
}}==Description==
The Charon is the basic air transport. It is ideal to ferry units to the front or make a drop deep behind enemy lines, but should not be used to land in areas with any kind of AA cover. It can only transport 'Light' or 'Medium' units, that is, units that cost 1000 metal or less.

==Tactics and Strategy==
The Charon can be used offensively by manually [[Load Command|load]]ing an enemy worker while they build, then flying them to allies to destroy or [[Eject Cargo Command|dropping]] them into an area that could damage them or leave them useless.

{{Navbox units}}

Hercules

2021-09-28T06:04:25Z

Mach56: Add medium unit transport stats

The '''{{PAGENAME}}''' is an armed heavy air transport from the [[Gunship Plant]].{{ Infobox zkunit
| name = Hercules
| defname = gunshipheavytrans
| description = Armed Heavy Air Transport
| image = http://manual.zero-k.info/unitpics/gunshipheavytrans.png
| icontype = heavygunshiptransport
| cost = 750
| hitpoints = 1800
| movespeed = 270
| turnrate = 69
| sight = 660
| weapons =
{{ Infobox zkweapon
| name = Light Laser Blaster × 2
| type = LaserCannon
| damage = 10
| reloadtime = 0.20
| dps = 50
| range = 320
| projectilespeed = 2400
}}
{{ Infobox zkweapon
| name = Anti-Air Laser
| type = BeamLaser
| damage = 20
| reloadtime = 0.40
| dps = 50
| range = 450
| antiair = Yes
| special1 = Instantly hits
}}
| abilities =
{{ Infobox zkability intel
| name = Transporting
| special1 = Transports light units at 75% speed
| special2 = Transports medium units at 65% speed
| special3 = Transports heavy units at 50% speed
}}
}}==Description==
The Hercules can haul any land unit in the game. Its twin laser guns and automated cargo ejection system make it ideal for drops into hot LZs.

==Tactics And Strategy==
Heavy enemy units can be disabled using [[Shockley]] missiles, [[Gnat]]s or other EMP units, leaving them defenseless. A Hercules then can then fly in and manually [[Load Command|load]] it, leaving it disabled while carried and able to be moved to any location, continuing to take damage in the air.

A Hercules can also pickup any stationary unit and destroy them using their lasers or [[Eject Cargo Command|dropping]] them from a large height or out of bounds.

{{Navbox units}}

Charon

2021-09-28T06:02:18Z

Mach56: Add medium units to Charon's transport capabilities.

The '''{{PAGENAME}}''' is an air transport from the [[Gunship Plant]].{{ Infobox zkunit
| name = Charon
| defname = gunshiptrans
| description = Air Transport
| image = http://manual.zero-k.info/unitpics/gunshiptrans.png
| icontype = gunshiptransport
| cost = 100
| hitpoints = 300
| movespeed = 345
| turnrate = 91
| sight = 300
| abilities =
{{ Infobox zkability intel
| name = Transporting
| special1 = Transports at 70% speed
}}
}}==Description==
The Charon is the basic air transport. It is ideal to ferry units to the front or make a drop deep behind enemy lines, but should not be used to land in areas with any kind of AA cover. It can only transport 'Light' or 'Medium' units, that is, units that cost 1000 metal or less.

==Tactics and Strategy==
The Charon can be used offensively by manually [[Load Command|load]]ing an enemy worker while they build, then flying them to allies to destroy or [[Eject Cargo Command|dropping]] them into an area that could damage them or leave them useless.

{{Navbox units}}

Djinn

2021-09-28T05:55:19Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is an amphibious teleport bridge from the [[Amphbot Factory]].{{ Infobox zkunit
| name = Djinn
| defname = amphtele
| description = Amphibious Teleport Bridge
| image = http://manual.zero-k.info/unitpics/amphtele.png
| icontype = amphtransport
| cost = 750
| hitpoints = 2500
| movespeed = 75
| turnrate = 138
| sight = 300
| sonar = 300
| transportable = Medium
| abilities =
{{ Infobox zkability regen
| waterregen = 30
| atdepth = 40
}}
}}==Description==
Djinn excels at moving large land based armies across bodies of water. It can place a [[Lamp]] at remote locations with its special ability to teleport units. The [[teleportation]] is one-way, moving units from the Lamp to the Djinn, so ensure the destination is safe.

=Tactics And Strategy=

Djinn is an expensive unit, so it's best built to move expensive armies, like striders, a dozen Scallops, or a couple Grizzlies.

Djinn is faster than many heavy and assault-class units, and outspeeds most of the amph bot factory unit set. Move it ahead of your assault force to close the distance faster.

The specops engineer [[Athena]] can fly undetected behind enemy lines to build Djinn. If walking is not an option, flying can be.

Djinn can be used for unit retrieval. Keep the Djinn safe in base, and create a lamp cross-map near your exposed units. Teleport them back to safety for [[Repair]]s and to join the next assault.

{{Navbox units}}

Iris

2021-09-28T05:55:15Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is an area cloaker/jammer walker from the [[Cloakbot Factory]].{{ Infobox zkunit
| name = Iris
| defname = cloakjammer
| description = Area Cloaker/Jammer Walker
| image = http://manual.zero-k.info/unitpics/cloakjammer.png
| icontype = kbotjammer
| cost = 600
| hitpoints = 600
| movespeed = 57
| turnrate = 415
| energy = -1.5
| sight = 400
| transportable = Medium
| abilities =
{{ Infobox zkability intel
| name = Radar Jammer
| jam = 400
}}
{{ Infobox zkability cloak
| name = Area Cloak
| radius = 400
| upkeep = 15
}}
{{ Infobox zkability morph
| to = [[Cornea]]
| cost = 0
| time = 30
| disabled = Yes
}}
}}==Description==
The Iris has a jamming device to conceal your units' radar returns. It also has a small [[Cloak|area cloaker]] to hide friendly nearby units from enemy sight. It hides units in a smaller range and uses more energy than its stationary cousin, the [[Cornea]], and is able to transform into a Cornea at no additional cost.

= Tactics and Strategy =

Having no weapons of its own, the Iris acts as a force multiplier for your other units, cloaking them from enemy view. This makes the Iris especially helpful at dealing with enemy skirmishers (such as [[Ronin]]s or [[Fencer]]s), artillery (such as [[Firewalker]]s or [[Merlin]]s), anti-heavy sniper units (such as [[Phantom]]s or [[Lance]]s), and even static defenses (such as [[Picket]]s, [[Stinger]]s, or even [[Cerberus]]) which normally won't fire at cloaked targets until they're revealed. As a result, the Iris effectively prevents longer-ranged enemy units from skirmishing any of your slower, shorter-ranged assaults (such as [[Knight]]s), riots (such as [[Reaver]]s), and even striders (such as [[Dante]]s or even [[Detriment]]s), allowing them to sneakily close the distance towards the enemy's units before coming under fire, so long as your units remain under the Iris's cloaking field, and so long as they don't shoot or take damage.

Note that the Iris itself is very fragile, and if it is killed, you may find your units in dangerous positions outside the safety of your lines.

In addition to its traditional role, the Iris can also be used to deliver bombs (such as [[Imp]]s and [[Snitch]]es) to the heart of enemy unit clusters. When used correctly, this can be a very efficient counter to [[Shieldbot_Factory#Tactics_and_Strategy|shield balls]].

Remember that the Iris (along with the [[Aspis]]) is amphibious, so it can be used to cloak friendly [[Shipyard|ships]], [[Amphbot Factory|amphbots]], [[Hovercraft Platform|hovercraft]], [[Reef]]s, [[Shogun]]s, and even [[Detriment]]s. Also remember that the [[Athena]] can build Irises (along with Aspis), so there's always an opportunity to build them without needing a [[Cloakbot Factory]], even if the battle takes place at sea (though you may need to terraform some dry land in order to build Athenas at sea if your Strider Hub is built far from dry land).

{{Navbox units}}

Aspis

2021-09-28T05:55:13Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is an area [[Shield]] walker from the [[Shieldbot Factory]].{{ Infobox zkunit
| name = Aspis
| defname = shieldshield
| description = Area Shield Walker
| image = http://manual.zero-k.info/unitpics/shieldshield.png
| icontype = walkershield
| cost = 600
| hitpoints = 700
| movespeed = 62
| turnrate = 415
| sight = 300
| transportable = Medium
| abilities =
{{ Infobox zkability shield
| name = Energy Shield
| strength = 3600
| regen = 50
| regencost = 12
| radius = 350
}}
{{ Infobox zkability morph
| to = [[Aegis]]
| cost = 0
| time = 30
| disabled = Yes
}}
}}==Description==
The Aspis protects surrounding units with its area shield by destroying enemy projectiles and will automatically connect to other shield-equipped units to share charge. The area shield will not stop units and only intercepts projectiles on its perimeter, so enemies can get under the shield and shoot at the units inside. Recharging and maintaining area shields costs energy.

[[File:Shield2.jpg|900px]]

=Tactics and Strategy=

Remember that the Aspis (along with the [[Iris]]) is amphibious, so it can be used to shield friendly [[Shipyard|ships]], [[Amphbot Factory|amphbots]], [[Hovercraft Platform|hovercraft]], [[Reef|Reefs]], [[Shogun|Shoguns]], and even [[Detriment|Detriments]] alongside land units. Also remember that the [[Athena]] can build Aspis (along with [[Iris|Irises]]), so there's always an opportunity to build them without needing a [[Shieldbot Factory]], even if the battle takes place at sea (though you may need to terraform some dry land in order to build Athenas at sea if your Strider Hub is built far from dry land).

{{Navbox units}}

Envoy

2021-09-28T05:55:10Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is a cruiser (artillery) from the [[Shipyard]].{{ Infobox zkunit
| name = Envoy
| defname = shiparty
| description = Cruiser (Artillery)
| image = http://manual.zero-k.info/unitpics/shiparty.png
| icontype = shiparty
| cost = 850
| hitpoints = 2000
| movespeed = 51
| turnrate = 92
| sight = 660
| sonar = 660
| transportable = Medium
| weapons =
{{ Infobox zkweapon
| name = Plasma Cannon
| type = Cannon
| damage = 601
| reloadtime = 5
| dps = 120
| range = 1200
| aoe = 48
| projectilespeed = 350
}}
}}==Description==
This Cruiser packs a powerful, long-range artillery cannon, useful for bombarding fixed emplacements and shore targets. Beware of aircraft, submarines and raider ships.

{{Navbox units}}

Siren

2021-09-28T05:55:09Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is a destroyer (riot/assault) from the [[Shipyard]].{{ Infobox zkunit
| name = Siren
| defname = shipassault
| description = Destroyer (Riot/Assault)
| image = http://manual.zero-k.info/unitpics/shipassault.png
| icontype = shipassault
| cost = 600
| hitpoints = 5200
| movespeed = 60
| turnrate = 63
| sight = 440
| sonar = 440
| transportable = Medium
| weapons =
{{ Infobox zkweapon
| name = Sonic Blaster
| type = Cannon
| damage = 280
| reloadtime = 1.70
| dps = 165
| range = 270
| aoe = 95
| projectilespeed = 700
| special1 = Water capable
}}
{{ Infobox zkweapon
| name = Destroyer Missiles
| type = StarburstLauncher
| damage = 400
| reloadtime = 16
| dps = 25
| range = 800
| aoe = 24
| projectilespeed = 1800
}}
}}==Description==
This Destroyer is a general-purpose combat vessel, combining a strong area-of-effect sonic cannon, a medium-range vertical launch missile, and strong armor. Use its sonic gun against smaller opponents above and below the water, and its missile against static targets.

{{Navbox units}}

Impaler

2021-09-28T05:55:07Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is a precision artillery rover from the [[Rover Assembly]].{{ Infobox zkunit
| name = Impaler
| defname = vehheavyarty
| description = Precision Artillery Rover
| image = http://manual.zero-k.info/unitpics/vehheavyarty.png
| icontype = vehiclelrarty
| cost = 700
| hitpoints = 1100
| movespeed = 60
| turnrate = 121
| sight = 660
| transportable = Medium
| weapons =
{{ Infobox zkweapon
| name = Kinetic Missile
| type = StarburstLauncher
| damage = 800
| reloadtime = 10
| dps = 80
| range = 1500
| projectilespeed = 8000
}}
| abilities =
{{ Infobox zkability line
| customdata1 = Can ignore unidentified targets
}}
}}==Description==
The Impaler fires vertically a high damage, high accuracy kinetic missile at long range. Its high arc makes it able to fire over any obstacle, however that makes the flight time so high that it's useless against moving targets. Use the Impaler to kill specific buildings.

{{Navbox units}}

Lance

2021-09-28T05:55:05Z

Mach56: Now medium weight

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

Emissary

2021-09-28T05:55:03Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is a general-purpose artillery from the [[Tank Foundry]].{{ Infobox zkunit
| name = Emissary
| defname = tankarty
| description = General-Purpose Artillery
| image = http://manual.zero-k.info/unitpics/tankarty.png
| icontype = tankarty
| cost = 700
| hitpoints = 840
| movespeed = 60
| turnrate = 105
| sight = 660
| transportable = Medium
| weapons =
{{ Infobox zkweapon
| name = Plasma Artillery
| type = Cannon
| damage = 601
| reloadtime = 7
| dps = 86
| range = 1120
| aoe = 42
| projectilespeed = 315
}}
}}==Description==
The heavy, long-ranging gun of the Emissary makes it the unit of choice for standoff shelling of enemy mobiles or structures. As always, it should be wary of anything that gets close to it.

==Tactics and Strategy==
The emissary has a fast projectile for an artillery unit, and even has a bit of AoE. These characteristics make this unit also quite effective against mobile units; effectively functioning as a long range fire support unit. If you are struggling to deal with skirmishers as tanks, try making some of these.

{{Navbox units}}

Minotaur

2021-09-28T05:55:01Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is an assault tank from the [[Tank Foundry]].{{ Infobox zkunit
| name = Minotaur
| defname = tankassault
| description = Assault Tank
| image = http://manual.zero-k.info/unitpics/tankassault.png
| icontype = tankassault
| cost = 850
| hitpoints = 6800
| movespeed = 74
| turnrate = 96
| sight = 506
| transportable = Medium
| weapons =
{{ Infobox zkweapon
| name = Medium Plasma Cannon
| type = Cannon
| damage = 320.1 × 2
| reloadtime = 4
| dps = 160
| range = 360
| aoe = 16
| projectilespeed = 255
}}
}}==Description==
A heavy duty battle tank. The Minotaur excels at absorbing damage in pitched battles, but its low rate of fire means it is not so good at dealing with swarms, and its heavy armor comes at the price of maneuverability.

== Tactics and Strategy ==
A combination of exceptionally high health with above average top speed means Minotaurs excel at surviving battle if you bother to pull them back when their health is low. This gives you the opportunity to repair them and send them back to the front brand new. Its easy to see how this can give you the upper hand in the battle of attrition over time.

Minotaurs parked in the frontlines should have supporting riot units handy, least the enemy raid or "crawling"/mobile bomb them, as their cannons are quite terrible at killing anything fast or numerous.

{{Navbox units}}

Phantom

2021-09-28T05:54:42Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is a cloaked skirmish/anti-heavy artillery bot from the [[Cloakbot Factory]].{{ Infobox zkunit
| name = Phantom
| defname = cloaksnipe
| description = Cloaked Skirmish/Anti-Heavy Artillery Bot
| image = http://manual.zero-k.info/unitpics/cloaksnipe.png
| icontype = sniper
| cost = 750
| hitpoints = 560
| movespeed = 42
| turnrate = 412
| sight = 400
| transportable = Medium
| weapons =
{{ Infobox zkweapon
| name = Pulsed Particle Projector
| type = Cannon
| damage = 1500
| reloadtime = 17
| dps = 88
| range = 700
| projectilespeed = 850
}}
| abilities =
{{ Infobox zkability cloak
| upkeepidle = 1
| upkeepmobile = 5
| decloakradius = 155
}}
{{ Infobox zkability line
| customdata1 = Can ignore unidentified targets
}}
}}==Description==
The Phantom's energy rifle inflicts heavy damage to a single target. It can fire while cloaked; however the shaped explosion of its projectile betrays the direction from which a shot was made. It requires quite a bit of energy to keep cloaked, especially when moving. The best way to locate a Phantom is by sweeping the area with many cheap units.

= Tactics and Strategy =
The Phantom has low damage-per-second compared to its cost, but since it remains cloaked even while firing it can deliver its damage very safely. Try to kill enemies with a single attack (from more than one Phantom, if necessary) to deny your opponent the opportunity to repair their unit. The enemy can still decloak and kill your Phantom by bringing a unit nearby (such as a [[Flea]] or [[Glaive]]), so make sure you have forces ready to protect your Phantoms' retreat if necessary.

Since Phantoms have a low rate of fire and high damage per shot, you might want to set them to hold fire mode (or return fire mode) if you want 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 Phantoms stopping in front of unidentified targets.

{{Navbox units}}

Felon

2021-09-28T05:54:40Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is a shielded riot/skirmisher bot from the [[Shieldbot Factory]].{{ Infobox zkunit
| name = Felon
| defname = shieldfelon
| description = Shielded Riot/Skirmisher Bot
| image = http://manual.zero-k.info/unitpics/shieldfelon.png
| icontype = walkersupport
| cost = 620
| hitpoints = 1600
| movespeed = 45
| turnrate = 198
| sight = 520
| transportable = Medium
| weapons =
{{ Infobox zkweapon
| name = Shield Gun
| type = LightningCannon
| damage = 94
| reloadtime = 0.13
| dps = 707
| range = 435
| customlabel1 = Shield drain (HP/shot)
| customdata1 = 75
| special1 = Instantly hits
}}
| abilities =
{{ Infobox zkability shield
| name = Energy Shield
| strength = 1800
| regen = 21
| regencost = 0
| radius = 120
}}
{{ Infobox zkability line
| customdata1 = Can ignore unidentified targets
}}
}}==Description==
The Felon draws energy from its shield, discharging it in accurate bursts. Link it to other shields to increase its rate of fire.

=Tactics And Strategy=
Use Felons with Thugs so the Thugs can tank damage for the Felon while also helping the Felon recharge its shields.

Felons are good anti-skirmishers due to the Felon's instant hit projectiles, so letting a Felon get close enough to discharge itself onto the enemy skirmishers is a good tactic.

Felons are the single strongest unit in the Shieldbot factory in terms of damage and HP. However, they are also the most expensive, meaning that the Felon must be defended.

Beware if the enemy sends swarms of high health but cheap units towards the Felon; the Felon will drain its shields and be an easy target and because the Felon drains its own shield whilst firing means that the Felon will be unable to fire consistently, drastically reducing the amount of damage a shieldball can do.

{{Navbox units}}

Skuttle

2021-09-28T05:54:37Z

Mach56: Now medium weight

The '''{{PAGENAME}}''' is a cloaked jumping anti-heavy bomb from the [[Jumpbot Factory]].{{ Infobox zkunit
| name = Skuttle
| defname = jumpbomb
| description = Cloaked Jumping Anti-Heavy Bomb
| image = http://manual.zero-k.info/unitpics/jumpbomb.png
| icontype = jumpjetbomb
| cost = 550
| hitpoints = 250
| movespeed = 46
| turnrate = 396
| sight = 280
| transportable = Medium
| weapons =
{{ Infobox zkweapon
| name = Explosion
| damage = 8002
| aoe = 90
}}
| abilities =
{{ Infobox zkability cloak
| upkeepidle = 5
| upkeepmobile = 15
| decloakradius = 180
}}
{{ Infobox zkability jump
| range = 400
| reload = 10
| speed = 180
| midairjump = No
}}
{{ Infobox zkability line
| customdata1 = Instant self-destruction
}}
}}==Description==
This slow-moving, expensive cloaked unit can jump onto enemy units and blast even a heavy tank straight to hell. Counter with swarms of cheap screening units. Be careful of its very small explosion radius when using it.

== Tactics and Strategy ==
Expensive, slow and unwieldy in comparison to its other [[Unit classes#Mobile Bombs|explosive brothers]], the {{PAGENAME}} is a niche unit, primarily used to devastate enemy with pinpoint strikes at expensive units, heavy structures, commanders and other high priority targets.

While using the {{PAGENAME}}, beware of its large decloak radius, as it boasts low hitpoints and can be destroyed in seconds. Always have your {{PAGENAME}}s go separately from your main force to avoid possible explosions in the midst of your own units.

Using the {{PAGENAME}} effectively requires knowledge of your target, its defenses, and enemy roster. Area jammers like [[Cornea]] and cheap scouts in big numbers, such as [[Flea]]s or [[Dart]]s, quickly diminish the chance of success. Mind your energy income and reserves, so as to not find your bomb decloaking in the group of enemies. Final stretch should be cut with the jump, which also allows {{PAGENAME}}s to ignore elevation by terraforming , enemies in the way, or even to reach flying units. Remember that {{PAGENAME}} decloaks when jumping, and it can be shot down before reaching the target. Because of the small explosion range, always try to get as close as possible, as its damage drops sharply with range.

===Multiple {{PAGENAME}}s===
Some units and structures are tough enough to withstand one {{PAGENAME}}, so you might need to consider other options, or just throw more of them at the enemy until there's nothing left.

{| class="wikitable sortable"
|+
Small table to help with numbers game for some of the usual targets.
!Enemy unit/structure!!Required number of {{PAGENAME}}s
|-
|http://manual.zero-k.info/unitpics/spidercrabe.png [[Crab]]||style="text-align:center"|1 for moving, 2 for stationary
|-
|http://manual.zero-k.info/unitpics/tankheavyassault.png [[Cyclops]]||style="text-align:center"|2
|-
|http://manual.zero-k.info/unitpics/amphassault.png [[Grizzly]]||style="text-align:center"|2
|-
|http://manual.zero-k.info/unitpics/gunshipkrow.png [[Krow]]||style="text-align:center"|2
|-
|http://manual.zero-k.info/unitpics/striderdante.png [[Dante]]||style="text-align:center"|2
|-
|http://manual.zero-k.info/unitpics/striderbantha.png [[Paladin]]||style="text-align:center"|4
|-
|http://manual.zero-k.info/unitpics/staticarty.png [[Cerberus]]||style="text-align:center"|1
|-
|http://manual.zero-k.info/unitpics/turretantiheavy.png [[Lucifer]]||style="text-align:center"|1
|}

The damage is considered to be dealt point-blank (maximum) to a full-health enemy.

All of these exchanges are cost-effective, but beware of the reclaim left after the unit's demise.

{{Navbox units}}

Jack

2021-09-28T05:51:50Z

Mach56: Now medium weight