Zero-K - User contributions [en]

Interface

2019-01-06T11:56:17Z

DeinFreund:

For information on the game lobby interface, see [[Game_Lobby|game lobby]]

== In-game Interface ==

The Zero-K ingame interface is simply structured. See the image below and the related text to understand the basic interface view.

The interface elements can be moved, resized and tweaked with '''CTRL+F11''', or by the ingame menu via Settings>HUD Panels>Extras.

[[File:Interface_screenshot.jpg]]

# Idle Constructors, Commander, and your factories production queue. If some of your constructors are idle the "M" will turn to yellow.
# Orders Panel. Includes Move, Attack Move, Fire etc. This panel has 5 extra tabs for constructors, allowing you to build factories, Economic structures, Defenses, etc. The right side of this panel shows current unit states.
# Info Panel. Shows information about the selected unit (like health, build power etc).
# Minimap. Units in combat will glow yellow, dying units red. You can issue orders here just as on the main screen. The buttons allow you to change the view (metal view, height view, etc).
# Player List. An overview of all participants in the game, also spectators. CPU load, Ping and alliance state are shown. Hovering over the list will show current spectators.
# Messages including chat and notifications.
# Buttons to toggle map overlays, show team colors, and zoom to the last message. Can also place retreat and ferry zones. Not shown, there is also a button to show graphs showing gameplay stats. All these buttons have hotkeys which can be re-bound.
# Metal (blue) and Energy (yellow) economy bars. The numbers are: current storage, +income, -expenditure. The current amount of storage used compared with total storage is shown by how full the bar is. The >>> symbols show how quickly the storage is being filled or depleted. More economic information is avaible when hovering the cursor over the metal/energy icons.
# Buttons to go to the main in-game [[Ingame_Menu|'''F10''' or '''ESC''' menu]], and toggle the main game lobby. There are also controls for sound and music volume.
# This is the main playing area. Here you see a construction queue made with '''SHIFT'''.
# This is an info panel that the cursor is hovering over. More information about the unit can be brought up with '''SPACE+click'''.

== Sharing Resources ==

When playing a team game, you can donate metal and energy to your allies, as well as selected units. By default, you also donate excess metal and energy to your team automatically. Hold '''TAB''' to display the following menu.

[[file:TabMenu_Sharing.jpg]]

# Metal and Energy bars, showing current storage and income.
# Current defensive power per player, gained by building static defenses.
# Current offensive power per player, gained by building factories and combat units.
# Donate energy to this player. The amount is determined by holding SHIFT, CTRL and ALT.
# Donate metal to this player. The amount is determined by holding SHIFT, CTRL and ALT.
# Donate the units you currently have selected to the player.

== Changing the in-game language ==
While in-game, click on the flag at the top right to select the language.

[[file:LanguageBar.png]]

{{Navbox manual}}

File:LanguageBar.png

2019-01-06T11:53:47Z

DeinFreund: Menu to choose in-game language

== Summary ==
Menu to choose in-game language
== Licensing ==
{{Zero-K screenshot}}

Commshare

2018-08-22T09:18:28Z

DeinFreund: How to turn on commshare

[[Category:Manual]]

== Overview ==
Commshare (or Command Share) is an alpha feature. Players who engage in Commsharing are assigned to a squad, which functions as if all the members of the squad were one player. Each member assigned to a squad adds their income and [[units]] to the squad.

Enable Commshare by holding '''Tab''' to open the player list, then pressing the <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/Commshare.png" height='16' alighn="center"/> Commshare Icon to invite a player into your squad or to accept the player's invitation into their squad.

= Overview of modes =
Commshare has three modes of operation:

* All mode
All players are merged at game start (specifically ~166ms into the game). Nobody may unmerge or kick anyone at any time.

* Invite mode (Default)
To merge with another player, you must first both agree to it. The player who invites the other first becomes the 'squad leader' who acts as the representative of the squad. Squad leaders can kick anyone for any reason at any time. They will receive their units back upon getting kicked, however. You may also leave a squad at any time as well. Issuing an invite is simple: Press H then click on the half teal/half green commander.

* None
No commsharing is allowed. No commshare commands will be responded to.

= Privileges =

All members may accept, decline, or issue invites. Only the squad leader may kick anyone.

= Developing =

Commands to commshare should be issued using SendLuaRulesMsg with the following string:
sharemode <command> <param>
This is not case sensitive. The following are valid commands:
{|
!Command:!!Param:!!Purpose:
|-
|Accept || playerID || Accepts an invite from playerID.
|-
|Decline || playerID || Declines an invite from playerID.
|-
|Invite || playerID || Issues an invite to playerID.
|-
|Kick || playerID || Forces playerID to unmerge, requires teamleader.
|-
|Remerge || None || Causes you to remerge, if you were disconnected/kick from game.
|-
|Unmerge || None || Causes you to unmerge.
|}

== TeamRulesParam: Getting invites ==
Invites are stored in TeamRulesParam as private data. It is stored as if it was an ordered table.
{|
!Param:!!Info:!!Notes:
|-
|commshare_invitecount || # of invites || Get this first, then do a for i=1,commshare_invitecount loop.
|-
|"commshare_invite_" .. i .."_id" || ID of the player who sent the invite ||
|-
|"commshare_invite_" .. i .."_timeleft" || Time remaining on this invite || You must check if this is different than last second's count to see if it's dead.
|}

{{Navbox manual}}

Template:Navbox manual

2018-08-22T09:15:31Z

DeinFreund: add commshare

{{Navbox
| name = Navbox manual
| title = [[Manual]]
| state = {{{state|}}}
| listclass = hlist

| group1 = Basics
| list1 = * [[Newbie Guide]]
* [[FAQ]]
* [[Interface]]
* [[Economy Guide|Basic Economy Guide]]
* [[Help for other RTS players|Help for Other RTS Players]]
* [[Gameplay dos and don'ts|Dos and Dont's]]
* [[Video tutorials|Video Tutorials]]
* [[Offsite Resources]]

| group2 = Units
| list2 = * <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/epicmenu/robot2.png" height='16' align="center" /> [[Units]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/advplayerslist/units.png" height='16' align="center" /> [[Unit classes|Unit Classes]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/advplayerslist/war.png" height='16' align="center" /> [[Weapon classes|Weapon Classes]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/stealth_on.png" height='16' align="center" /> [[Map icons|Unit Radar Icons]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/module_areashield.png" height='16' align="center" /> [[Commander]]s

| group3 = Unit abilities and features
| list3 = * <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/capture.png" height='16' align="center" /> [[Capture]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/cloak_on.png" width='16' align="center" /> [[Cloak]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaRules/Images/awards/trophy_fire.png" height='16' align="center" /> [[Fire]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/embark.png" height='16' align="center" /> [[Transportation]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/repair.png" height='16' align="center" /> [[Repair]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/health.png" height='16' align="center" /> [[Shield]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/ramp.png" height='16' align="center" /> [[Terraform]]ing
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/move.png" height='16' align="center" /> [[Unit commands|Unit Commands]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/on.png" height='16' align="center" /> [[Unit states|Unit States]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bulb_on.png" height='16' align="center" /> [[Unit AI]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/retreat_90.png" height='16' align="center" /> [[Retreat|Retreat Command]]

| group4 = Other features
| list4 = * <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/mex.png" height='16' align="center"/> [[Overdrive|Overdrive System]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/advplayerslist/diplomacy.png" height='16' align="center"/> [[Ceasefire]]s
* <img src="http://manual.zero-k.info/unitpics/chicken.png" height='16' align="center"/> [[Chicken Defense]]
* <img src="http://zero-k.info/img/news/2213.png" height='16' align="center"/> [[User Page]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/draggrip.png" height='16' alighn="center"/> [[Customizing the User Interface]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/Commshare.png" height='16' alighn="center"/> [[Commshare|Unit control sharing]]

| group5 = Other information
| list5 = * <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/epicmenu/control_panel.png" height='16' align="center"/> [[Hotkeys|Customizing Hotkeys]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/epicmenu/questionmark.png" height='16' align="center"/> [[Abbreviations]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/advplayerslist/Ranks/rank5.png" height='16' align="center"/> [[Award]]s
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/epicmenu/game.png" height='16' align="center"/>[[Cheats]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/build.png" height='16' align="center"/> [http://springrts.com/wiki/UI_commands Engine commands]
* [[File:Soldier.png]] [[Matchmaking]]
* <img src="http://zero-k.info/img/conduct.png" height='16' align="center"/>[[Zero-K:Code of Conduct |Code of Conduct]]
* [[Performance Optimizations]]

| group6 = Strategy
| list6 = * <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/energy.png" height='16' align="center"/> [[Wind Farm Guide|Wind Farming]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/factory.png" height='16' align="center"/> [[Factory tips|Factory Tips]]
* <img src="http://manual.zero-k.info/icons/cruisemissilesmall.png" height='16' align="center"/> [[Missile Silo Tutorial]]

| group7 = Development/Modding
| list7 = * [[Developing]]
* [[Widget Configuration]]
* [[Map Creation]]
* [[Mod Creation]]
* [[Animator GUI]]
* [[Startbox API]]
}}

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

Commshare

2018-08-22T09:13:46Z

DeinFreund: add navbox

[[Category:Manual]]

== Overview ==
Commshare (or Command Share) is an alpha feature. Players who engage in Commsharing are assigned to a squad, which functions as if all the members of the squad were one player. Each member assigned to a squad adds their income and [[units]] to the squad.

= Overview of modes =
Commshare has three modes of operation:

* All mode
All players are merged at game start (specifically ~166ms into the game). Nobody may unmerge or kick anyone at any time.

* Invite mode (Default)
To merge with another player, you must first both agree to it. The player who invites the other first becomes the 'squad leader' who acts as the representative of the squad. Squad leaders can kick anyone for any reason at any time. They will receive their units back upon getting kicked, however. You may also leave a squad at any time as well. Issuing an invite is simple: Press H then click on the half teal/half green commander.

* None
No commsharing is allowed. No commshare commands will be responded to.

= Privileges =

All members may accept, decline, or issue invites. Only the squad leader may kick anyone.

= Developing =

Commands to commshare should be issued using SendLuaRulesMsg with the following string:
sharemode <command> <param>
This is not case sensitive. The following are valid commands:
{|
!Command:!!Param:!!Purpose:
|-
|Accept || playerID || Accepts an invite from playerID.
|-
|Decline || playerID || Declines an invite from playerID.
|-
|Invite || playerID || Issues an invite to playerID.
|-
|Kick || playerID || Forces playerID to unmerge, requires teamleader.
|-
|Remerge || None || Causes you to remerge, if you were disconnected/kick from game.
|-
|Unmerge || None || Causes you to unmerge.
|}

== TeamRulesParam: Getting invites ==
Invites are stored in TeamRulesParam as private data. It is stored as if it was an ordered table.
{|
!Param:!!Info:!!Notes:
|-
|commshare_invitecount || # of invites || Get this first, then do a for i=1,commshare_invitecount loop.
|-
|"commshare_invite_" .. i .."_id" || ID of the player who sent the invite ||
|-
|"commshare_invite_" .. i .."_timeleft" || Time remaining on this invite || You must check if this is different than last second's count to see if it's dead.
|}

{{Navbox manual}}

Commshare

2018-08-22T09:12:21Z

DeinFreund: this page should have more links

[[Category:Manual]]

== Overview ==
Commshare (or Command Share) is an alpha feature. Players who engage in Commsharing are assigned to a squad, which functions as if all the members of the squad were one player. Each member assigned to a squad adds their income and [[units]] to the squad.

= Overview of modes =
Commshare has three modes of operation:

* All mode
All players are merged at game start (specifically ~166ms into the game). Nobody may unmerge or kick anyone at any time.

* Invite mode (Default)
To merge with another player, you must first both agree to it. The player who invites the other first becomes the 'squad leader' who acts as the representative of the squad. Squad leaders can kick anyone for any reason at any time. They will receive their units back upon getting kicked, however. You may also leave a squad at any time as well. Issuing an invite is simple: Press H then click on the half teal/half green commander.

* None
No commsharing is allowed. No commshare commands will be responded to.

= Privileges =

All members may accept, decline, or issue invites. Only the squad leader may kick anyone.

= Developing =

Commands to commshare should be issued using SendLuaRulesMsg with the following string:
sharemode <command> <param>
This is not case sensitive. The following are valid commands:
{|
!Command:!!Param:!!Purpose:
|-
|Accept || playerID || Accepts an invite from playerID.
|-
|Decline || playerID || Declines an invite from playerID.
|-
|Invite || playerID || Issues an invite to playerID.
|-
|Kick || playerID || Forces playerID to unmerge, requires teamleader.
|-
|Remerge || None || Causes you to remerge, if you were disconnected/kick from game.
|-
|Unmerge || None || Causes you to unmerge.
|}

== TeamRulesParam: Getting invites ==
Invites are stored in TeamRulesParam as private data. It is stored as if it was an ordered table.
{|
!Param:!!Info:!!Notes:
|-
|commshare_invitecount || # of invites || Get this first, then do a for i=1,commshare_invitecount loop.
|-
|"commshare_invite_" .. i .."_id" || ID of the player who sent the invite ||
|-
|"commshare_invite_" .. i .."_timeleft" || Time remaining on this invite || You must check if this is different than last second's count to see if it's dead.
|}

Cheese

2018-08-22T09:07:04Z

DeinFreund: basic links

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

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

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

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

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

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

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

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

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

Modifier Reference

2018-08-22T09:01:07Z

DeinFreund: Redirected page to Unit commands#Most Common Commands and Modifiers

#REDIRECT [[Unit_commands#Most_Common_Commands_and_Modifiers]]

Unit commands

2018-08-22T09:00:29Z

DeinFreund: /* Modifiers */

Commands are the orders or directions that players issue to their units throughout a game of Zero-K. Most of the actions and decisions that players make throughout a game are implemented via issuing various types of commands. This page lists and categorizes all the commands with links for details on specific commands.

== Command Types ==
There are three main types of command: targeted commands, instant commands and state toggles.
* '''Targeted commands''' are issued with a target. Targets can include units and map features (rocks, trees, wrecks) as well as positions, areas and lines drawn that you draw on the map when the command is issued. Targeting lines, areas or multiple units or features is commonly achieved by clicking an dragging.
* '''Instant commands''' activate unit abilities that require no target.
* '''State toggles''' are standing orders that modify behaviour or toggle certain abilities.

== Giving Commands ==
Instant commands and state toggles can be issued by clicking their button in the command panel or pressing their hotkey. Right clicking a state toggle cycles the toggle backwards or reset it to a deactivated state, depending on the command. Hotkeys to set a state toggle to a particular state can be bound in the hotkeys menu.

Targeted commands can be issued with either the left or right mouse buttons.
* Click the '''right mouse button''' to issue a context sensitive command. The command that will be issued is indicated by the mouse cursor and depends on both your unit selection and the target of the command. Common examples are [[Force Fire Command|force fire]] when the target is an enemy unit and [[Move Command|move]] when the the target is empty ground.
* Click the '''left mouse button''' to issue a command selected. To select a command click on its button in the command panel or press its hotkey. The selected command is indicated by the mouse cursor and a highlighted command button. Issue the command (without holding Shift) or right click to deselect the command.

Targeted commands can be modified in many ways.
* '''Click and drag''' to draw a circle or a line. Most commands support either line or circle drawing and some support both depending on other modifers.
* Many commands are modified by holding '''Alt''' or '''Ctrl''' while clicking to issue the command.
* Some commands change depending on whether they are targeted on a unit or the ground.

== Queuing and Inserting Commands ==
Units maintain a list of commands, known as their command queue, that are executed in order as each command is completed. Most targeted and instant commands can be added to the end of the queue or inserted or inserted into the queue. State toggles cannot be added to the queue and always take effect instantly.
* Hold '''SHIFT''' while issuing a targeted or instant command to add it to the end of the command queue.
* Hold '''SPACE''' while issuing a targeted command to add it to the start of the command queue, pushing the current command to the second spot in the queue.
* Hold '''SHIFT+SPACE''' while issuing a targeted command to insert it at the point in the command queue that would result in the least extra travel time.

A targeted command that is issued without holding Shift or Space cancels the entire command queue, replacing it with the newly issued command. An instant command that is issued without holding Shift or Space immediately executes the command without affecting the rest of the queue. Nobody knows what happens if an instant command is issued with Space held.

== Factory Production Commands ==
Factories can make use of unit commands to make produced units take specific actions when leaving the factory. For example, units can be set to move to a point or patrol as soon as they are produced.

Unit commands given to factories can also be queued and modified, as above.

== Most Common Commands and Modifiers ==
Commands can have their behaviour modified using ALT and CTRL, and can be combined with SHIFT and SPACE to queue commands. Some commands also change their behaviour when targeted on a unit or the ground. See each command's page for details.

{|
!style="width: 10%"|Command
!style="width: 10%"|Click+drag behaviour
!style="width: 20%"|Drag behaviour
!style="width: 20%"|+CTRL
!style="width: 20%"|+ALT
!style="width: 20%"|+CTRL+ALT
|-
|[[Move_Command|Move]](M) <img src="http://zero-k.info/mediawiki/images/d/de/Move.png" width="32" height="32"/>
|Move units to a point.
|Move units into a line.
|Move, maintaining current formation.
|When dragging, move along a line.
|When dragging, move along a line in formation.
|-
|[[Attack_Move_Command|Attack move]](A) <img src="http://zero-k.info/mediawiki/images/f/f8/Fight.png" width="32" height="32"/>
|Move to a point, using unit AI while moving.
|Same as move, using AI.
|Same as move, using AI.
|Same as move, using AI.
|Same as move, using AI.
|-
|[[Patrol_Command|Patrol]](P) <img src="http://zero-k.info/mediawiki/images/f/fd/Patrol.png" width="32" height="32"/>
|Move back and forth between current position and a point, using unit AI while moving.
|Same as move, using AI.
|Same as move, using AI.
|Same as move, using AI.
|Same as move, using AI.
|-
|[[Force_Fire_Command|Force Fire]](F) <img src="http://zero-k.info/mediawiki/images/0/00/Attack.png" width="32" height="32"/>
|Fire at a point
|Fire at all targets in an area, in a queue.
|When dragging, fire at all targets in an area, splitting fire.
|When dragging, fire along a line.
|
|-
|[[Set_Target_Command|Set Target]](T) <img src="http://zero-k.info/mediawiki/images/5/58/Settarget.png" width="32" height="32"/>
|Target a unit or point, without moving. Fire at target if in range. Fire normally if out of range.
|Target the nearest enemy in the circle.
|Target all enemies in the circle, splitting targets.
|Target the ground along a line, firing if in range.
|
|-
|[[Guard_Command|Guard]](G) <img src="http://zero-k.info/mediawiki/images/7/74/Guard.png" width="32" height="32"/>
|Protect, repair, and assist a unit.
|On unit: guard in circle formation.
On ground: guard all units in the circle.
|For circle formation: guard in a specific direction.
|For circle formation: guard in a direction relative to unit facing.
|For circle formation: do not match guarding unit speeds/positions.
|-
|[[Repair_Command|Repair]](R) <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/Anims/cursorrepair_0.png"/>
|Repair a live unit; Assist construction.
|Area command. Applies the click command to valid targets in the area, as long as there are any.
|Only repair live units, do not assist construction.
|For area only. Persist the area even when no valid targets inside (continue if any new show up).
|
|-
|[[Area_Mex_Command|Area Mex]](W) <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/mex.png" width="32" height="32"/>
|Build a mex at given spot||Queue mexes across the area.
|Surround each mex in the area with 4 solars. Works on already-built mexes.
|
|
|
|-
|[[Reclaim_Command|Reclaim]](E) <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/Anims/cursorreclamate_0.png"/>
|Reclaim target (unit or feature).
|Reclaim features across the area.
|Area only. If centered on a live unit, reclaim all units of this type in the area. Else, ignore metal-less features, such as trees. There is a menu option to do this by default, in which case trees can be reclaimed either with CTRL or by centering the area on a tree.
|Area only. Persist the command even when no features are in the area.
|
|-
|[[Resurrect_Command|Resurrect]] <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/Anims/cursorrevive_0.png"/>
|Resurrect target wreck||Area version. Resurrect wrecks in given area as long as there are any; ignore ones that are partially reclaimed.
|Area only. Resurrect even partially reclaimed wrecks (but still not those actively being reclaimed - this requires single target command).
|Area only. Persist the command even when no resurrectables are in the area.
|
|-
|}

== Full List of Commands ==
=== Common targeted commands ===
* [[Move Command|Move]]
* [[Attack Move Command|Attack Move]]
* [[Jump Command|Jump]]
* [[Force Fire Command|Force Fire]]
* [[Set Target Command|Set Target]]
* [[Fire Special Weapon Command|Fire Special Weapon]]
* [[Area Attack Command|Area Attack]]
* [[Guard Command|Guard]]
* [[Patrol Command|Patrol]]

=== Common economic commands ===
* [[Repair Command|Repair]]
* [[Reclaim Command|Reclaim]]
* [[Resurrect Command|Resurrect]]
* [[Area Mex Command|Area Mex]]
* [[Structure Placement|Structure placement commands]]
* [[Factory Production|Unit construction commands]]
* [[Terraform|Terraforming commands]]

=== Instant commands ===
* [[Stop Command|Stop]]
* [[Wait Command|Wait]]
* [[Detonate Command|Detonate]]
* [[Self Destruct Command|Self Destruct]]
* [[Cancel Target Command|Cancel Target]]
* [[Return to Airbase Command|Return to Airbase]]
* [[Recall Drones Command|Recall Drones]]
* [[Clear Production Queue Command|Clear Production Queue]]
* [[Stockpile Command|Stockpile]]

=== Transport commands ===
* [[Load Command|Load]]
* [[Unload Command|Unload]]
* [[Load Command#Load Selected Units|Load Selected Units]]
* [[Eject Cargo Command|Eject Cargo]]
* [[Transport AI#Embark and Disembark|Embark]]
* [[Transport AI#Embark and Disembark|Disembark]]

=== Unusual commands ===
* [[Newton Firezones|Newton firezone commands]]
* [[Morph Command|Morph]]
* [[Commander|Upgrade Commander]]
* [[Commander|Stop Commander Upgrade]]
* [[Unique Commands#Drop Bombs|Drop Bombs]]
* [[Unique Commands#Unleash Lightning|Unleash Lightning]]
* [[Unique Commands#Teleport Beacon|Teleport Beacon]]
* [[Unique Commands#Drop Depthcharge|Drop Depthcharge]]
* [[Unique Commands#Speed Boost|Speed Boost]]
* [[Evacuate Command|Evacuate]]

=== Global commands ===
* [[Ferry Command|Ferry]]
* [[Retreat|Retreat]]
* [[Resources Reserve|Reserve]]

=== State commands ===
* [[Unit states#Fire State|Fire State]]
* [[Unit states#Move State|Move State]]
* [[Unit states#Repeat|Repeat]]
* [[Unit states#Overkill Prevention|Overkill Prevention]]
* [[Unit states#Retreat|Retreat]]
* [[Unit states#Build Priority|Build Priority]]
* [[Unit states#Misc Priority|Build Misc]]
* [[Unit states#Factory Assist|Factory Assist]]
* [[Unit states#Cloak|Cloak]]
* [[Unit states#Unit AI|Unit AI]]
* [[Unit states#On/Off|On/Off]]
* [[Unit states#Idle State|Idle State]]
* [[Unit states#Float State|Float State]]
* [[Unit states#Trajectory|Trajectory]]
* [[Unit states#Fire at Radar|Fire at Radar]]
* [[Unit states#Dive State|Dive State]]
* [[Unit states#Area Cloak|Area Cloak]]
* [[Unit states#Gunship Strafe|Gunship Strafe]]
* [[Unit states#Kill Captured|Kill Captured]]
* [[Unit states#Drone Construction|Drone Construction]]
* [[Unit states#Impulse Mode|Impulse Mode]]

{{Navbox commands}}
{{Navbox manual}}

Modifier Reference

2018-08-22T08:59:34Z

DeinFreund: Integrated this nice overview directly into commands page, it is a little small and hard to find otherwise

#REDIRECT [[Unit_commands#Modifiers]]

Template:Navbox manual

2018-08-22T08:49:25Z

DeinFreund: add link to performance optimizations

{{Navbox
| name = Navbox manual
| title = [[Manual]]
| state = {{{state|}}}
| listclass = hlist

| group1 = Basics
| list1 = * [[Newbie Guide]]
* [[FAQ]]
* [[Interface]]
* [[Economy Guide|Basic Economy Guide]]
* [[Help for other RTS players|Help for Other RTS Players]]
* [[Gameplay dos and don'ts|Dos and Dont's]]
* [[Video tutorials|Video Tutorials]]
* [[Offsite Resources]]

| group2 = Units
| list2 = * <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/epicmenu/robot2.png" height='16' align="center" /> [[Units]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/advplayerslist/units.png" height='16' align="center" /> [[Unit classes|Unit Classes]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/advplayerslist/war.png" height='16' align="center" /> [[Weapon classes|Weapon Classes]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/stealth_on.png" height='16' align="center" /> [[Map icons|Unit Radar Icons]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/unitpics/module_areashield.png" height='16' align="center" /> [[Commander]]s

| group3 = Unit abilities and features
| list3 = * <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/capture.png" height='16' align="center" /> [[Capture]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/cloak_on.png" width='16' align="center" /> [[Cloak]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaRules/Images/awards/trophy_fire.png" height='16' align="center" /> [[Fire]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/embark.png" height='16' align="center" /> [[Transportation]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/repair.png" height='16' align="center" /> [[Repair]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/health.png" height='16' align="center" /> [[Shield]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/ramp.png" height='16' align="center" /> [[Terraform]]ing
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/move.png" height='16' align="center" /> [[Unit commands|Unit Commands]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/on.png" height='16' align="center" /> [[Unit states|Unit States]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/bulb_on.png" height='16' align="center" /> [[Unit AI]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/states/retreat_90.png" height='16' align="center" /> [[Retreat|Retreat Command]]

| group4 = Other features
| list4 = * <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/mex.png" height='16' align="center"/> [[Overdrive|Overdrive System]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/advplayerslist/diplomacy.png" height='16' align="center"/> [[Ceasefire]]s
* <img src="http://manual.zero-k.info/unitpics/chicken.png" height='16' align="center"/> [[Chicken Defense]]
* <img src="http://zero-k.info/img/news/2213.png" height='16' align="center"/> [[User Page]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/draggrip.png" height='16' alighn="center"/> [[Customizing the User Interface]]

| group5 = Other information
| list5 = * <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/epicmenu/control_panel.png" height='16' align="center"/> [[Hotkeys|Customizing Hotkeys]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/epicmenu/questionmark.png" height='16' align="center"/> [[Abbreviations]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/advplayerslist/Ranks/rank5.png" height='16' align="center"/> [[Award]]s
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/epicmenu/game.png" height='16' align="center"/>[[Cheats]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/commands/Bold/build.png" height='16' align="center"/> [http://springrts.com/wiki/UI_commands Engine commands]
* [[File:Soldier.png]] [[Matchmaking]]
* <img src="http://zero-k.info/img/conduct.png" height='16' align="center"/>[[Zero-K:Code of Conduct |Code of Conduct]]
* [[Performance Optimizations]]

| group6 = Strategy
| list6 = * <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/energy.png" height='16' align="center"/> [[Wind Farm Guide|Wind Farming]]
* <img src="https://raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/factory.png" height='16' align="center"/> [[Factory tips|Factory Tips]]
* <img src="http://manual.zero-k.info/icons/cruisemissilesmall.png" height='16' align="center"/> [[Missile Silo Tutorial]]

| group7 = Development/Modding
| list7 = * [[Developing]]
* [[Widget Configuration]]
* [[Map Creation]]
* [[Mod Creation]]
* [[Animator GUI]]
* [[Startbox API]]
}}

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

Performance Optimizations

2018-08-22T08:48:35Z

DeinFreund: add manual navbox

== In-game Overlay ==
When using Steam or Discord, the in-game overlay should be disabled for maximum performance. It can lead to anything from increased lag to a completely unresponsive user [[interface]].

=== Disabling the Steam Overlay ===
* Right click on Zero-K in your Steam library.
* Select 'Properties' from the dropdown menu.
* Untick "Enable the Steam Overlay while in-game" in General.

=== Disabling the Discord Overlay ===
* In Discord, go to Settings -> Games
* Look for Zero-K and click the button on the right to "Toggle Overlay". It should turn red.

== Linux Graphics Driver Optimizations ==
===Graphics Check===
<pre>glxinfo | grep "Max core profile version"</pre>
It needs to show a number 4.1 or greater otherwise graphically demanding games such as Zero-K won't run correctly.
If it doesn't you need to do the following.

Do a backup before preceding. These instructions written for Debian 9 but will likely work on other distributions with little modification.

===Backport libdrm from sid===
<pre>
apt-get build-dep libdrm
apt-get source libdrm -t sid
debuild -b -uc -us libdrm
dpkg install libdrm
</pre>

===Build New Mesa3d===
<pre>
apt-get install llvm-3.9-dev
ln -sf /usr/bin/llvm-config-3.9 /usr/bin/llvm-config
git clone git://anongit.freedesktop.org/git/mesa/mesa
cd mesa
./autogen.sh
./configure --prefix=/opt/mesa --enable-texture-float --with-gallium-drivers=radeonsi,swrast --with-platforms=drm,x11 --enable-glx-tls --enable-shared-glapi --enable-glx --enable-driglx-direct --enable-gles1 --enable-gles2 --enable-gbm --enable-openmax --enable-xa --enable-osmesa --with-radeonsi-llvm-compiler --enable-sysfs --enable-vdpau --enable-xvmc --enable-openmax --enable-nine
make -j 4
checkinstall
</pre>

You will have to configure via the checkinstall menu to build and install a valid package.

<pre>
This package will be built according to these values:

0 - Maintainer: [ your@email ]
1 - Summary: [ open source 3D computer graphics library ]
2 - Name: [ mesa ]
3 - Version: [ version number from git ]
4 - Release: [ 1 ]
5 - License: [ MIT ]
6 - Group: [ checkinstall ]
7 - Architecture: [ amd64 ]
8 - Source location: [ mesa ]
9 - Alternate source location: [ ]
10 - Requires: [ ]
11 - Provides: [ mesa ]
12 - Conflicts: [ ]
13 - Replaces: [ ]
</pre>

===Configure Xorg===
<pre>
Xorg -configure
cp xorg.conf.new /etc/X11/xorg.conf
</pre>

Next restart your display manager.

<pre>
systemctl restart lightdm.service
</pre>

{{Navbox manual}}

Performance Optimizations

2018-08-22T08:46:30Z

DeinFreund: disabling overlays

Performance Optimizations

2018-08-22T08:37:07Z

DeinFreund: DeinFreund moved page Optimized Graphics Linux to Performance Optimizations: generalize page for all OS

==Graphics Check==
<pre>glxinfo | grep "Max core profile version"</pre>
It needs to show a number 4.1 or greater otherwise graphically demanding games such as Zero-K won't run correctly.
If it doesn't you need to do the following.

Do a backup before preceding. These instructions written for Debian 9 but will likely work on other distributions with little modification.

==Backport libdrm from sid==
<pre>
apt-get build-dep libdrm
apt-get source libdrm -t sid
debuild -b -uc -us libdrm
dpkg install libdrm
</pre>

==Build New Mesa3d==
<pre>
apt-get install llvm-3.9-dev
ln -sf /usr/bin/llvm-config-3.9 /usr/bin/llvm-config
git clone git://anongit.freedesktop.org/git/mesa/mesa
cd mesa
./autogen.sh
./configure --prefix=/opt/mesa --enable-texture-float --with-gallium-drivers=radeonsi,swrast --with-platforms=drm,x11 --enable-glx-tls --enable-shared-glapi --enable-glx --enable-driglx-direct --enable-gles1 --enable-gles2 --enable-gbm --enable-openmax --enable-xa --enable-osmesa --with-radeonsi-llvm-compiler --enable-sysfs --enable-vdpau --enable-xvmc --enable-openmax --enable-nine
make -j 4
checkinstall
</pre>

You will have to configure via the checkinstall menu to build and install a valid package.

<pre>
This package will be built according to these values:

0 - Maintainer: [ your@email ]
1 - Summary: [ open source 3D computer graphics library ]
2 - Name: [ mesa ]
3 - Version: [ version number from git ]
4 - Release: [ 1 ]
5 - License: [ MIT ]
6 - Group: [ checkinstall ]
7 - Architecture: [ amd64 ]
8 - Source location: [ mesa ]
9 - Alternate source location: [ ]
10 - Requires: [ ]
11 - Provides: [ mesa ]
12 - Conflicts: [ ]
13 - Replaces: [ ]
</pre>

==Configure Xorg==
<pre>
Xorg -configure
cp xorg.conf.new /etc/X11/xorg.conf
</pre>

Next restart your display manager.

<pre>
systemctl restart lightdm.service
</pre>

Optimized Graphics Linux

2018-08-22T08:37:07Z

DeinFreund: DeinFreund moved page Optimized Graphics Linux to Performance Optimizations: generalize page for all OS

#REDIRECT [[Performance Optimizations]]

FAQ

2018-08-10T09:55:15Z

DeinFreund: replace link to fanart/media page by nicer and more up to date presskit page.

'''Frequently Asked Questions''' - Zero-K
(still under construction)

==I'm new to Zero-K. Where should I start?==
First you should read the [[Newbie Guide]] and try some practice games against the AI.
Some missions are designed for new players to get to know the interface and some basic gameplay ideas (e.g. [http://zero-k.info/Missions/Detail/97 Sandbox] and [http://zero-k.info/Missions/Detail/100 2v1]). You can also access them from Zero-K lobby directly.

You can also spectate some online games to see which things are significant.

==How can I unlock commander modules?==
You have to visit the [http://www.zero-k.info Zero-K Homepage] and log in with your account. You can easily reach this page from the lobby through the "Home" tab. From here, scroll down until you see "You can unlock technology" and click on this link. Alternatively you can [http://zero-k.info/My/UnlockList click here] if you're logged in. Note that you do not have to unlock anything from this page; all modules are currently unlocked in-game for all players. Unlocking these just makes them available for preconfigured commanders.

==How do I gain rating? ==
You can gain rating if you're winning multiplayer games. Based on you enemies' skill you will gain/lose more or less rating.

Instead of relying on fixed rating thresholds, rating colors are defined by your gaming skills (calculated by a specific algorithm called WHR, similar to ELO) expressed as a percentiles of the playerbase. Rating colors can only be gained or lost after holding one's position in the new percentile for multiple games.

Here is a list of the rating colors:

{|
! Icon !! Color !! Theme !! Percentile
|-
|<img src="http://zero-k.info/img/ranks/0_7.png"/> <img src="http://zero-k.info/img/ranks/2_7.png"/> <img src="http://zero-k.info/img/ranks/6_7.png"/> || Gamma ray || Singularity|| Top 1%
|-
|<img src="http://zero-k.info/img/ranks/0_6.png"/> <img src="http://zero-k.info/img/ranks/2_6.png"/> <img src="http://zero-k.info/img/ranks/6_6.png"/> || X ray || Neutron star|| Top 5%
|-
|<img src="http://zero-k.info/img/ranks/0_5.png"/> <img src="http://zero-k.info/img/ranks/2_5.png"/> <img src="http://zero-k.info/img/ranks/6_5.png"/> || Blue white || Supergiant|| Top 10%
|-
|<img src="http://zero-k.info/img/ranks/0_4.png"/> <img src="http://zero-k.info/img/ranks/2_4.png"/> <img src="http://zero-k.info/img/ranks/6_4.png"/> || Bright yellow || Giant|| Top 20%
|-
|<img src="http://zero-k.info/img/ranks/0_3.png"/> <img src="http://zero-k.info/img/ranks/2_3.png"/> <img src="http://zero-k.info/img/ranks/6_3.png"/> || Orange || Subgiant|| Top 40%
|-
|<img src="http://zero-k.info/img/ranks/0_2.png"/> <img src="http://zero-k.info/img/ranks/2_2.png"/> <img src="http://zero-k.info/img/ranks/6_2.png"/> || Red|| Red dwarf|| Top 60%
|-
|<img src="http://zero-k.info/img/ranks/0_1.png"/> <img src="http://zero-k.info/img/ranks/2_1.png"/> <img src="http://zero-k.info/img/ranks/6_1.png"/> || Dark red|| Brown dwarf|| Top 80%
|-
|<img src="http://zero-k.info/img/ranks/0_0.png"/> <img src="http://zero-k.info/img/ranks/2_0.png"/> <img src="http://zero-k.info/img/ranks/6_0.png"/> || Infrared|| Nebula|| Everyone
|}

The rank level itself is defined by the cumulated total time spent ingame.

Here is a list of the ranks, with color Infrared:

<img src="http://zero-k.info/img/ranks/0_0.png"/>
<img src="http://zero-k.info/img/ranks/1_0.png"/>
<img src="http://zero-k.info/img/ranks/2_0.png"/>
<img src="http://zero-k.info/img/ranks/3_0.png"/>
<img src="http://zero-k.info/img/ranks/4_0.png"/>
<img src="http://zero-k.info/img/ranks/5_0.png"/>
<img src="http://zero-k.info/img/ranks/6_0.png"/>
<img src="http://zero-k.info/img/ranks/7_0.png"/>

The progress bar "Level XXX" shows your rank level (i.e. dependent on total time spent ingame).

The progress bar below it shows your position in respect to the next cosmic object (in other words, how far you are to the next color, dependent on your gaming skills).

==How much XP do I need to reach the next level?==
Mouse over the XP bar on the home page; the XP needed is displayed in the tooltip.

==My FPS is low after some time have passed ingame. What can I do?==
Try to reduce your graphics settings. To do so, go to the Settings Tab on Zero-K Lobby and click Graphics Settings -> Run SpringSettings. Some system-intensive elements that you could tone down/disable are shadows and water type. Try a new game and probably change some settings again.

If you're playing on Steam, disable the Steam Overlay as it negatively affects performance:
* Right click on Zero-K in your Steam library.
* Select 'Properties' from the dropdown menu.
* Untick "Enable the Steam Overlay while in-game" in General.

==I get ugly bubbles in the minimap/the whole screen flashbangs.==
Do you get bubbles like this?

http://zero-k.info/img/clans/FAQ_bg.png

This is a bug somewhere in Lua drawing with ATI/AMD and OpenGL.
Disable widgets that draw via F11 menu to find the problematic widget.
This should largely be fixed, if it still happens make a bugreport please.

==I have some game ideas. Where can I post them?==
Visit the [http://zero-k.info/Forum Zero-K forum] and pose your ideas in one of the sections.
Furthermore, you can create a new issue on our development site: https://github.com/ZeroK-RTS/Zero-K/issues

==What do all the ingame abbreviations mean?==
You can look up some abbreviations used ingame [[Abbreviations|here in this list]]. Some abbreviations unrelated to the game can be looked up on [http://en.wiktionary.org/wiki/Appendix:Internet_slang this page]. Another way is to ask players ingame.

==How can I support the game? Donations?==
On the one hand you can [http://zero-k.info/Contributions donate some coins] so we can pay the server costs. On the other hand you can support us by simply playing the game and spreading the word. Feel free to use our [http://presskit.zero-k.info/ advertisement material] on your site. Thanks a lot! :-)

==How do I change my password? ==
On your home/account page, click ''Account maintenance'' and enter your new password.

==I forgot my password / username. Help me pls!==
If you forgot your password / username please contact one of the server admins to receive your password / username. They will reset it to something and pm it to you.

==My game crashes/has graphical glitches. How do I fix it? ==
First check the [http://springrts.com/wiki/FAQ:trouble troubleshooting FAQ] on the Spring engine wiki and see if your issue is covered there. If you can't find a solution to the problem, you can file a bug report on our forum or [https://github.com/ZeroK-RTS Github development site].

==I have a bug report!==
You can post in the [http://zero-k.info/Forum?categoryID=3 Help & Bugs subforum] or make an issue report on [https://github.com/ZeroK-RTS Github] (more technical).

Please include diagnostic logs as appropriate. You can automatically upload the log from ingame through ''Main Menu'' -> ''Help'' -> ''Report a Bug''.

Otherwise, look for infolog_full.txt in your installation folder. Be sure to [http://www.pastebin.com pastebin] your infolog and give the link instead of posting the whole thing on the forum or github.

==My question isn't answered here. Where can I ask my question?==
As above you can visit the [http://zero-k.info/Forum forum] and ask your question in one of the listed sections. 
You can also ask players ingame to get help.

{{Navbox manual}}

Unit commands

2018-08-05T18:03:32Z

DeinFreund: Undo revision 4438 by 93.210.155.122 (talk) (Vandalism)

User:DeinFreund/vector.css

2016-09-17T20:49:46Z

DeinFreund: Blanked the page

Matchmaking

2016-09-16T15:59:43Z

DeinFreund: algorithm corrections

The Zero-K Matchmaker allows players to automatically find a game with other similarly skilled players to participate in. This solves the problem of highly rated individuals being disappointed by having to fight with newbies on their team.

= Introduction =
The Matchmaker can be found in the Multiplayer tab of most lobbies. You will be presented with a list of possible game types to play, as well as a short description of these.

[[File:MMQueues.png]]

After selecting the preferred gametype(s), you can freely join rooms or spectate battles until a game is found. If you decide to play in a custom battle, you will simply be removed from the Matchmaking queue without any further penalties.

[[File:AreYouReady.png]]

Once a match has been found, you will be informed both visually and audibly by a pop-up, asking you to confirm that you are ready to play the game. Once the match has been accepted by all players, the game will be started on a randomly selected map from the game type specific map pool. Should one of the other players not accept the game, you will be put back into the Matchmaking queue until another game is found.

If no response is made within 30 seconds or the request is denied, you will be removed from the queue. If you ignore or deny a found match, you will be unable to join the Matchmaking queue again for five minutes.

= Algorithm =
Once you have joined a queue, the Matchmaker will continuously look for other players to pair you with. Each player is assigned a maximum rating span, and the difference between maximum rating and minimum rating in a game must not be greater than the maximum rating span of all players. This span is progressively widened as the player is waiting, up to a maximum width. The matchmaker will always prioritize the players which have waited the longest. I.e. it will rather make a game with a big rating difference to accommodate a player that has waited long than make a game with a small rating difference containing players that have just joined the queue.

If there are enough players within rating range, the Matchmaker will choose the nearest ones and ask them to accept the match. If all chosen players accept, they will be assigned a map and a room and removed from all queues. Otherwise the Matchmaker will continue to look for possible games after the declining players have been removed from the queue.

= Parties =
In the future, players will be able to group up with their friends to join a game in the same team. This system is not yet implemented.

Matchmaking

2016-09-15T15:14:09Z

DeinFreund: Addressing players, not readers

The Zero-K Matchmaker allows players to automatically find a game with other similarly skilled players to participate in. This solves the problem of highly rated individuals being disappointed by having to fight with newbies on their team.

= Introduction =
The Matchmaker can be found in the Multiplayer tab of most lobbies. The player will be presented with a list of possible game types to play, as well as a short description of these.

[[File:MMQueues.png]]

After selecting the preferred gametype(s), the player can freely join rooms or spectate battles until a game is found. If he decides to play in a custom battle, he will simply be removed from the Matchmaking queue without any further penalties.

[[File:AreYouReady.png]]

Once a match has been found, the player will be informed both visually and audibly by a pop-up, asking him to confirm that he is going to play this game. Once the match has been accepted by all players, the game will be started on a randomly selected map from the game type specific map pool. Should one of the other players not accept the game, the searching player will be put back into the Matchmaking, until another game is found. If no response is made within 30 seconds or the request is denied, the player will be removed from the queue. Furthermore, ignored or denied requests will lead to a five minute exclusion from Matchmaking.

= Algorithm =
Once a player has joined a queue, the Matchmaker will continuously look for other players to pair him with. Each player is assigned a maximum rating span within which both his teammates and opponents have to lie. This span is progressively widened while the player is waiting, up to a maximum width. If there are enough players within rating range, the Matchmaker will choose the nearest ones and ask them to accept the match. If all players accepted, they will be assigned a map and a room and removed from all queues. Otherwise the Matchmaker will continue to look for possible games after the declining players have been removed from the queue.

= Parties =
In the future, players will be able to group up with their friends to join a game in the same team. This system is not yet implemented.

Matchmaking

2016-09-15T12:12:51Z

DeinFreund:

The Zero-K Matchmaker allows players to automatically find a game with other similarly skilled players to participate in. This solves the problem of highly rated individuals being disappointed by having to fight with newbies on their team.

= Introduction =
The Matchmaker can be found in the Multiplayer tab of most lobbies. The player will be presented with a list of possible game types to play, as well as a short description of these.

[[File:MMQueues.png]]

After selecting the preferred gametype(s), the player can freely join rooms or spectate battles until a game is found. If he decides to play in a custom battle, he will simply be removed from the Matchmaking queue without any further penalties.

[[File:AreYouReady.png]]

Once a match has been found, the player will be informed both visually and audibly by a pop-up, asking him to confirm that he is going to play this game. Once the match has been accepted by all players, the game will be started on a randomly selected map from the game type specific map pool. Should one of the other players not accept the game, the searching player will be put back into the Matchmaking, until another game is found. If no response is made within 30 seconds or the request is denied, the player will be removed from the queue. Furthermore, ignored or denied requests will lead to a five minute exclusion from Matchmaking.

= Algorithm =
Once a player has joined a queue, the Matchmaker will continuously look for other players to pair him with. Each player is assigned a maximum rating span within which both his teammates and opponents have to lie. This span is progressively widened while the player is waiting, up to a maximum width. If there are enough players within rating range, the Matchmaker will choose the nearest ones and ask them to accept the match. If all players accepted, they will be assigned a map and a room and removed from all queues. Otherwise the Matchmaker will continue to look for possible games after the declining players have been removed from the queue.

= Parties =
Players can group up with your friends to join a game in the same team. This system is not yet implemented.

Matchmaking

2016-09-14T22:05:04Z

DeinFreund: How2Matchmake

The Zero-K Matchmaker allows players to automatically find a game with other similarly skilled players to participate in. This solves the problem of highly rated individuals being disappointed by having to fight with newbies on their team.

= Introduction =
The Matchmaker can be found in the Multiplayer tab of most lobbies. The player will be presented with a list of possible game types to play, as well as a short description of these.

[[File:MMQueues.png]]

After selecting the preferred gametype(s), the player can freely join rooms or spectate battles until a game is found. If he decides to play in a custom battle, he will simply be removed from the Matchmaking queue without any further penalties.

[[File:AreYouReady.png]]

Once a match has been found, the player will be informed both visually and audibly by a pop-up, asking him to confirm that he is going to play this game. Once the match has been accepted by all players, the game will be started on a randomly selected map from the game type specific map pool. Should one of the other players not accept the game, the searching player will be put back into the Matchmaking, until another game is found. If no response is made within 30 seconds or the request is denied, the player will be removed from the queue. Furthermore, ignored or denied requests will lead to a five minute exclusion from Matchmaking.

= Algorithm =
Once a player has joined a queue, the Matchmaker will continuously look for other players to pair him with. Each player is assigned a maximum rating span within which both his teammates and opponents have to lie. This span is progressively widened while the player is waiting, up to a maximum width. If there are enough players within rating range, the Matchmaker will choose the nearest ones and ask them to accept the match. If all players accepted, they will be assigned a map and a room and removed from all queues. Otherwise the Matchmaker will continue to look for possible games after the declining players have been removed from the queue.

= Parties =
You can group up with your friends to join a game in the same team. This system is not yet implemented.

File:AreYouReady.png

2016-09-14T21:46:51Z

DeinFreund:

File:MMQueues.png

2016-09-14T21:37:37Z

DeinFreund: Shows Matchmaker Queues.

Shows Matchmaker Queues.

Template talk:Navbox units

2016-07-26T18:55:26Z

DeinFreund: Created page with "= Non buildable units = I'd restrict the units to actual units that you encounter in the "standard" zk game. Nebula doesn't seem to fit there. Alternatively, a section for hid..."

= Non buildable units =
I'd restrict the units to actual units that you encounter in the "standard" zk game. Nebula doesn't seem to fit there. Alternatively, a section for hidden units could be made.
[[User:DeinFreund|DeinFreund]] ([[User talk:DeinFreund|talk]]) 21:55, 26 July 2016 (AST)

Talk:Missile Silo Tutorial

2016-07-25T18:09:08Z

DeinFreund: /* Inferno damage */

= Inferno damage =
How do you calculate the total damage it deals to a specific unit? Would be nice to add that to the Damage section.
[[User:DeinFreund|DeinFreund]] ([[User talk:DeinFreund|talk]]) 21:56, 23 July 2016 (AST)

Some empirical testing indicates that the Inferno deals around 30 dps to anything standing in its flames. There's also the ~150 on impact and about 50 in afterburn after leaving the flames, or after the flames die out. There may be some randomness involved. [[User:Aquanim|Aquanim]] ([[User talk:Aquanim|talk]]) 19:10, 24 July 2016 (AST)

> So you you would rate Inferno as 1500 guaranteed damage? [[User:DeinFreund|DeinFreund]] ([[User talk:DeinFreund|talk]]) 21:09, 25 July 2016 (AST)

2016-06-26T03:29:32Z

DeinFreund: /* THE */

'''PRESS''' ''ALL'' [[OF]]
== THE ==
<nowiki>--~~~~loblob
----
</nowiki>

== !resign ==

Test

MediaWiki talk:Vector.css

2016-06-26T02:54:32Z

DeinFreund: /* Colors */