Zero-K - User contributions [en]

Template:Command Panel UI Button

2025-08-13T04:59:17Z

RandomX: 53 - 2px margin on either side...

<div style="width:53px;height:49px;border:#356 solid 2px;border-radius:4px;background-color:#233;padding:0;margin:0;position:relative"><img src="//raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/nested_buildmenu/frame_{{{frame|Mobile}}}.png" style="width:53px;height:{{#if:{{{price|}}}|40|47}}px;margin:0;border:none;position:absolute;top:0;left:0" alt="({{{frame|Mobile}}}) "><img src="//manual.zero-k.info/unitpics/{{{unitpic|cloakraid}}}.png" style="width:53px;height:{{#if:{{{price|}}}|40|47}}px;margin:0;border:none;position:absolute;top:0;left:0" alt="{{{name|{{{1|{{UnitData getData|{{{unitpic|cloakraid}}}|name}}}}}}}}" title="{{{name|{{{1|{{UnitData getData|{{{unitpic|cloakraid}}}|name}}}}}}}}">
{{#if:{{{price|}}}|<div style="line-height:19px;color:#0f0;text-shadow:1px 1px 2px #000;position:absolute;top:0;left:5px;font-family:FreeSans,Arial,sans-serif;font-weight:bold;font-size:11px">{{{hotkey|W}}}</div>
<div style="line-height:22px;color:#eee;text-shadow:1px 1px 2px #000;position:absolute;top:33px;left:5px;font-family:FreeSans,Arial,sans-serif;font-weight:bold;font-size:12px">{{{price|{{UnitData getData|{{{unitpic|cloakraid}}}|cost}}}}}</div>
}}
{{#if:{{{queued|{{{2|}}}}}}|<div style="line-height:26px;color:#fff;text-shadow:1px 1px 2px #000;position:absolute;top:25px;left:0;width:47px;font-family:FreeSans,Arial,sans-serif;font-weight:bold;font-size:15px;text-align:right">{{{queued|{{{2|0}}}}}}</div>
{{#if:{{{progress|{{{3|}}}}}}|<div style="width:{{#expr:{{{progress|{{{3|0}}}}}}*0.49}}px;height:43px;margin:0;border:none;position:absolute;top:2px;left:2px;background:rgba(192, 192, 96, 0.55)"></div>}}}}
</div><noinclude>{{Documentation}}</noinclude>

Template:Command Panel UI Button

2025-08-13T04:45:27Z

RandomX:

<div style="width:53px;height:49px;border:#356 solid 2px;border-radius:4px;background-color:#233;padding:0;margin:0;position:relative"><img src="//raw.githubusercontent.com/ZeroK-RTS/Zero-K/master/LuaUI/Images/nested_buildmenu/frame_{{{frame|Mobile}}}.png" style="width:53px;height:{{#if:{{{price|}}}|40|47}}px;margin:0;border:none;position:absolute;top:0;left:0" alt="({{{frame|Mobile}}}) "><img src="//manual.zero-k.info/unitpics/{{{unitpic|cloakraid}}}.png" style="width:53px;height:{{#if:{{{price|}}}|40|47}}px;margin:0;border:none;position:absolute;top:0;left:0" alt="{{{name|{{{1|{{UnitData getData|{{{unitpic|cloakraid}}}|name}}}}}}}}" title="{{{name|{{{1|{{UnitData getData|{{{unitpic|cloakraid}}}|name}}}}}}}}">
{{#if:{{{price|}}}|<div style="line-height:19px;color:#0f0;text-shadow:1px 1px 2px #000;position:absolute;top:0;left:5px;font-family:FreeSans,Arial,sans-serif;font-weight:bold;font-size:11px">{{{hotkey|W}}}</div>
<div style="line-height:22px;color:#eee;text-shadow:1px 1px 2px #000;position:absolute;top:33px;left:5px;font-family:FreeSans,Arial,sans-serif;font-weight:bold;font-size:12px">{{{price|{{UnitData getData|{{{unitpic|cloakraid}}}|cost}}}}}</div>
}}
{{#if:{{{queued|{{{2|}}}}}}|<div style="line-height:26px;color:#fff;text-shadow:1px 1px 2px #000;position:absolute;top:25px;left:0;width:47px;font-family:FreeSans,Arial,sans-serif;font-weight:bold;font-size:15px;text-align:right">{{{queued|{{{2|0}}}}}}</div>
{{#if:{{{progress|{{{3|}}}}}}|<div style="width:{{#expr:{{{progress|{{{3|0}}}}}}*0.53}}px;height:43px;margin:0;border:none;position:absolute;top:2px;left:2px;background:rgba(192, 192, 96, 0.55)"></div>}}}}
</div><noinclude>{{Documentation}}</noinclude>

Template:Navbox

2024-11-20T02:26:26Z

RandomX: Make it possible to temporarily fix any page that has a navbox... even if this makes the warning appear multiple times.

<includeonly>{{Purge}}{{#invoke:Navbox|navbox}}</includeonly><noinclude>
{{Documentation}}
</noinclude>

Template:Navbox manual

2024-11-20T02:23:14Z

RandomX:

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

| group1 = Basics
| list1 = {{:Manual/Getting Started}}

| group2 = Units
| list2 = {{:Manual/Unit References}}

| group3 = Unit abilities and features
| list3 = {{:Manual/Unit Abilities}}
{{:Manual/Unit Features}}

| group4 = Other features
| list4 = {{:Manual/General Features}}

| group5 = Other information
| list5 = {{:Manual/Other Info|none}}

| group6 = Strategy
| list6 = {{:Manual/Strategy|none}}

| group7 = Development/Modding
| list7 = {{:Manual/Coding}}
}}

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

V1.8.8.2

2024-11-03T04:28:46Z

RandomX:

{{TOC right}}[[File:Multiple Factories.png]]
== Construction Plates and Archer Rework ==
:[//zero-k.info/Forum/Thread/31937 Forum thread ''Zero-K v1.8.8.2 - Construction Plates and Archer Rework'']

Some players like parallel build queues, some want more ways to optimise production, and some just think a base with lots of factories looks cool. All these desires are satisfied in this update with the introduction of construction plates - efficient mini-factories that must be placed near a main factory to function. They can be used in the campaign and teamgames to take advantage of allied tech, while in 1v1 they should make it easier for factories access their heavy units.

The rest of the update focuses on the balance of three area; Kodachi, Amph, and dense team games. Kodachi has received nerfs to rein in the range bestowed by the fire prediction AI from v1.8.5.0. Archer takes over the role of sea riot from Scallop, with Archer gaining a sonic blaster and Scallop losing torpedo power. Funnelweb, Lance, Gauss and Big Bertha have various nerfs to open up the options in dense team games.

In other news, there is a 1v1 tournament this weekend. [//zero-k.info/Forum/Thread/31918 Click here] for details and post to sign up.

=== Balance ===
<dfn style="font-weight:bold">Construction Plates</dfn> are parallel build queues that offer an alternate method of increasing production. Hover a factory blueprint within 420 elmos of a factory of the same type to place a construction plate.
* Cost 150
* Health 1000 (1500 for Ship)
* Build Power 10

'''Scorcher''' regains some of its damage.
* DPS increased by 5.6%

'''Bolas''' has slightly more range to help it against Kodachi.
* Range 225 → 230

'''Kodachi''' has a nerf to take fire prediction into account.
* Cost 170 → 180
* Range 230 → 215
* Reload Time 0.466s → 0.5s
* Moved 13% of on-hit damage to groundburn damage.
* Projectile Velocity increased by 117% (reduces prediction overshoot).

'''Welder''' is more vulnerable to raids.
* Health 2000 → 1800

'''Scallop''' torpedoes are relegated to sidearm status.
* Range 260 → 270 (both weapons)
* Can fire torpedoes from underwater.
* Torpedo DPS reduced by 60%
* Torpedo AoE reduced by 62%

'''Archer''' takes on the role of sea riot.
* Replaced Water Cannon with Sonic Blaster.
* Can fire into water, must float to fire.
* Reduced Speed and increased DPS.

'''Lance''' is easier to catch.
* Speed 55.5 → 52.5
* Turn Rate reduced by 9.4%
* Range 1020 → 1000

'''Funnelweb''' takes on a tankyness more appropriate for a constructor.
* Cost 3000 → 3500
* Health 6500 → 4500

'''Gauss''' is worse at tying up artillery.
* Bunker Regen 20hp/s → 10hp/s

'''Big Bertha''' is less generically powerful in dense team games.
* Cost 5000 → 6000
* Reload 7s → 8s
* AoE reduced by 8.3%
* Projectile speed reduced by 4.5%

=== Fixes ===
* Scouted Caretakers and Strider Hubs no longer radar wobble.
* Fixed metal reserve erroneously disabling repair.
* Fix commander speed when walking in formation.
* Various fixes to shared unit control mode.
* Disabled shift append to groups by default.
* Change disambiguation of space+click context menu.
* Likho is better at avoiding obstructions when aiming.
* Fix Grizzly float-to-fire AI in some edge-of-range cases.
* Fixed manual queuing with Auto Reclaim/Heal/Assist widget.
* Fixed an issue with auto-retreat for planes.
* Fixed repeated screen resolution changes causing some UI widgets to be lost under the minimap.
* Fixed zero volume music logic.
* Fixed rare spectator panels crash.

{{Navbox changelog}}

V1.11.6.2

2024-11-03T04:27:40Z

RandomX:

{{TOC right}}[[File:Allied indicators.png|Allied indicators.png]]
== Don't Nuke Your Allies ==
:[//zero-k.info/Forum/Thread/36520 Forum thread ''Zero-K v1.11.6.2 - Don't Nuke Your Allies'']

The 3v3 tournament finished earlier today with an excellent turnout of 19 teams. The results and videos will be posted in [https://zero-k.info/Forum/Thread/36455 this thread] in the coming days. The upshot for this patch is that we are free to make a few balance changes. The aim of these changes is to work on a few of the more maligned units, while nerfing some of the most prevalent strategies. This mostly means buffs for Gunships and nerfs for Lance and cloaked Snitch.

The update also has some exciting features. A big one for team games is that allied nukes and missiles now automatically show where they were aimed, which should halve the number of people that panic when a nuke is fired. Another is the ability to watch any game while waiting for a different one to start without missing out on the chat, as chat from non-started lobbies is now sent ingame. Superintendent has also added a few more tracks to his alternate soundtrack.

=== Balance ===
'''Snitch''' is slower to nerf its use with cloaker, without making it worse as a pure ambusher.
* Speed 117 → 108

'''Iris''' is a bit easier to find and its area cloak radius now matches area shield radius.
* Speed 57 → 54
* Decloak range 180 → 210
* Cloaker radius 360 → 350

'''Lance''' is less effective when set to fire at will.
* Reload time 20s → 23s

'''Scallop''' is still the slowest riot but is a bit tankier than average.
* Health 1100 → 1200
* Speed 48 → 51

'''Emissary''' can afford to be fast since it takes so long to pack up.
* Speed 60 → 63
* Range 1120 → 1150

'''Blastwing''' takes less time to deal its damage and deals slightly more.
* AoE 128 → 144
* Fire DPS 25 → 32
* Fire linger 25s → 20s

'''Gnat''' needs more health to survive long enough to stun the juiciest target.
* Cost 90 → 85
* Health 370 → 440

'''Revenant''' can be brought back now that commanders are more resilient.
* Health 3600 → 4200
* Missiles 8 → 9
* Reduced missile wobble by 6.7%

'''Stardust''' has a small buff to its damage output but might still need a larger change later.
* Heat per shot 3.8 → 3.5

'''Lucifer''' can see as far as it can shoot (thanks Majo).
* Sight range 780 → 1280

=== Game Features ===
* Added predicted impact time and location for allied nukes and stockpiled missiles (thanks esainane).
* Added a new Superintendent music track.
* Hovering a unit with the mouse now highlights it slightly. This can be configured under 'Settings/Graphics/Unit Visibility'.
* Alt+N terraform preset is slightly higher to block Phantoms firing at Engineer Commander.
* Added Set Target (instead of Force Fire) on Right Click option under 'Settings/Unit Behaviour'.
* Added time and space leeway settings to make selection easier, under 'Settings/Interface/Selection'.
* Added an explanation of selection rank to 'Settings/Interface/Selection' as people find fiddling with it surprisingly useful.
* Embiggened cursor hitboxes of Grizzly, Jugglenaut, Cyclops, Shield Factory and Cloak Factory.
* Singularity Reactor size now fluctuates.
* Impaler fire sound is slightly fainter and only five can play at once.
* Added Base Extraction graph to the endgame stats that tracks cumulative metal from extractors before overdrive.

=== Lobby Features ===
* Battles can now be watched by right clicking on them in the battle list and selecting 'Watch'.
* Chat from any lobby you are in is sent ingame if the lobby is not running.
* Added a new Superintendent track that plays when the lobby opens.
* Mention Imp burrow in the tips for the Imp campaign mission.
* Added a game option to override the names of teams for tournaments.
* Added a game option (under Experimental) called Notes that just writes text to a window at the start of the game. Use it to explain unit tweaks or other complicated set of options.

=== Fixes ===
* Preselection highlight (when hovering over units) now highlights units correctly in edge cases.
* Fixed the player count in the battle lobby status box updating slowly.
* Fixed units set to avoid radar wobble not firing at identified structure dots that left radar.
* Fixed Advanced Geo aim point (thanks dyth68).
* Fixed Mariner special build icon size.
* Healthbars and Build ETA now draw in front of unit outlines.
* Fixed an error that could occur when destroying all the units of the losing team.
* Phoenix gibs no longer include a near-complete copy of its fuselage.

{{Navbox changelog}}

V1.8.8.2

2024-11-03T04:26:33Z

RandomX: Created page with "{{TOC right}}File:Multiple Factories.png == Construction Plates and Archer Rework == :[//zero-k.info/Forum/Thread/31937 Forum thread ''Zero-K v1.8.8.2 - Construction Plate..."

{{TOC right}}[[File:Multiple Factories.png]]
== Construction Plates and Archer Rework ==
:[//zero-k.info/Forum/Thread/31937 Forum thread ''Zero-K v1.8.8.2 - Construction Plates and Archer Rework'']

Some players like parallel build queues, some want more ways to optimise production, and some just think a base with lots of factories looks cool. All these desires are satisfied in this update with the introduction of construction plates - efficient mini-factories that must be placed near a main factory to function. They can be used in the campaign and teamgames to take advantage of allied tech, while in 1v1 they should make it easier for factories access their heavy units.

The rest of the update focuses on the balance of three area; Kodachi, Amph, and dense team games. Kodachi has received nerfs to rein in the range bestowed by the fire prediction AI from v1.8.5.0. Archer takes over the role of sea riot from Scallop, with Archer gaining a sonic blaster and Scallop losing torpedo power. Funnelweb, Lance, Gauss and Big Bertha have various nerfs to open up the options in dense team games.

In other news, there is a 1v1 tournament this weekend. [//zero-k.info/Forum/Thread/31918 Click here] for details and post to sign up.

=== Balance ===
<dfn style="font-weight:bold">Construction Plates</dfn> are parallel build queues that offer an alternate method of increasing production. Hover a factory blueprint within 420 elmos of a factory of the same type to place a construction plate.
* Cost 150
* Health 1000 (1500 for Ship)
* Build Power 10

'''Scorcher''' regains some of its damage.
* DPS increased by 5.6%

'''Bolas''' has slightly more range to help it against Kodachi.
* Range 225 -> 230

'''Kodachi''' has a nerf to take fire prediction into account.
* Cost 170 -> 180
* Range 230 -> 215
* Reload Time 0.466s -> 0.5s
* Moved 13% of on-hit damage to groundburn damage.
* Projectile Velocity increased by 117% (reduces prediction overshoot).

'''Welder''' is more vulnerable to raids.
* Health 2000 -> 1800

'''Scallop''' torpedoes are relegated to sidearm status.
* Range 260 -> 270 (both weapons)
* Can fire torpedoes from underwater.
* Torpedo DPS reduced by 60%
* Torpedo AoE reduced by 62%

'''Archer''' takes on the role of sea riot.
* Replaced Water Cannon with Sonic Blaster.
* Can fire into water, must float to fire.
* Reduced Speed and increased DPS.

'''Lance''' is easier to catch.
* Speed 55.5 -> 52.5
* Turn Rate reduced by 9.4%
* Range 1020 -> 1000

'''Funnelweb''' takes on a tankyness more appropriate for a constructor.
* Cost 3000 -> 3500
* Health 6500 -> 4500

'''Gauss''' is worse at tying up artillery.
* Bunker Regen 20hp/s -> 10hp/s

'''Big Bertha''' is less generically powerful in dense team games.
* Cost 5000 -> 6000
* Reload 7s -> 8s
* AoE reduced by 8.3%
* Projectile speed reduced by 4.5%

=== Fixes ===
* Scouted Caretakers and Strider Hubs no longer radar wobble.
* Fixed metal reserve erroneously disabling repair.
* Fix commander speed when walking in formation.
* Various fixes to shared unit control mode.
* Disabled shift append to groups by default.
* Change disambiguation of space+click context menu.
* Likho is better at avoiding obstructions when aiming.
* Fix Grizzly float-to-fire AI in some edge-of-range cases.
* Fixed manual queuing with Auto Reclaim/Heal/Assist widget.
* Fixed an issue with auto-retreat for planes.
* Fixed repeated screen resolution changes causing some UI widgets to be lost under the minimap.
* Fixed zero volume music logic.
* Fixed rare spectator panels crash.

{{Navbox changelog}}

V1.11.6.2

2024-11-03T04:10:30Z

RandomX: Created page with "{{TOC right}}File:Allied indicators.png| == Don't Nuke Your Allies == :[//zero-k.info/Forum/Thread/36520 Forum thread ''Zero-K v1.11.6.2 - Don't Nuke Your Allies''] The 3..."

{{TOC right}}[[File:Allied indicators.png|Allied indicators.png]]
== Don't Nuke Your Allies ==
:[//zero-k.info/Forum/Thread/36520 Forum thread ''Zero-K v1.11.6.2 - Don't Nuke Your Allies'']

The 3v3 tournament finished earlier today with an excellent turnout of 19 teams. The results and videos will be posted in [https://zero-k.info/Forum/Thread/36455 this thread] in the coming days. The upshot for this patch is that we are free to make a few balance changes. The aim of these changes is to work on a few of the more maligned units, while nerfing some of the most prevalent strategies. This mostly means buffs for Gunships and nerfs for Lance and cloaked Snitch.

The update also has some exciting features. A big one for team games is that allied nukes and missiles now automatically show where they were aimed, which should halve the number of people that panic when a nuke is fired. Another is the ability to watch any game while waiting for a different one to start without missing out on the chat, as chat from non-started lobbies is now sent ingame. Superintendent has also added a few more tracks to his alternate soundtrack.

== Balance ==
'''Snitch''' is slower to nerf its use with cloaker, without making it worse as a pure ambusher.
* Speed 117 → 108

'''Iris''' is a bit easier to find and its area cloak radius now matches area shield radius.
* Speed 57 → 54
* Decloak range 180 → 210
* Cloaker radius 360 → 350

'''Lance''' is less effective when set to fire at will.
* Reload time 20s → 23s

'''Scallop''' is still the slowest riot but is a bit tankier than average.
* Health 1100 → 1200
* Speed 48 → 51

'''Emissary''' can afford to be fast since it takes so long to pack up.
* Speed 60 → 63
* Range 1120 → 1150

'''Blastwing''' takes less time to deal its damage and deals slightly more.
* AoE 128 → 144
* Fire DPS 25 → 32
* Fire linger 25s → 20s

'''Gnat''' needs more health to survive long enough to stun the juiciest target.
* Cost 90 → 85
* Health 370 → 440

'''Revenant''' can be brought back now that commanders are more resilient.
* Health 3600 → 4200
* Missiles 8 → 9
* Reduced missile wobble by 6.7%

'''Stardust''' has a small buff to its damage output but might still need a larger change later.
* Heat per shot 3.8 → 3.5

'''Lucifer''' can see as far as it can shoot (thanks Majo).
* Sight range 780 → 1280

== Game Features ==
* Added predicted impact time and location for allied nukes and stockpiled missiles (thanks esainane).
* Added a new Superintendent music track.
* Hovering a unit with the mouse now highlights it slightly. This can be configured under 'Settings/Graphics/Unit Visibility'.
* Alt+N terraform preset is slightly higher to block Phantoms firing at Engineer Commander.
* Added Set Target (instead of Force Fire) on Right Click option under 'Settings/Unit Behaviour'.
* Added time and space leeway settings to make selection easier, under 'Settings/Interface/Selection'.
* Added an explanation of selection rank to 'Settings/Interface/Selection' as people find fiddling with it surprisingly useful.
* Embiggened cursor hitboxes of Grizzly, Jugglenaut, Cyclops, Shield Factory and Cloak Factory.
* Singularity Reactor size now fluctuates.
* Impaler fire sound is slightly fainter and only five can play at once.
* Added Base Extraction graph to the endgame stats that tracks cumulative metal from extractors before overdrive.

== Lobby Features ==
* Battles can now be watched by right clicking on them in the battle list and selecting 'Watch'.
* Chat from any lobby you are in is sent ingame if the lobby is not running.
* Added a new Superintendent track that plays when the lobby opens.
* Mention Imp burrow in the tips for the Imp campaign mission.
* Added a game option to override the names of teams for tournaments.
* Added a game option (under Experimental) called Notes that just writes text to a window at the start of the game. Use it to explain unit tweaks or other complicated set of options.

== Fixes ==
* Preselection highlight (when hovering over units) now highlights units correctly in edge cases.
* Fixed the player count in the battle lobby status box updating slowly.
* Fixed units set to avoid radar wobble not firing at identified structure dots that left radar.
* Fixed Advanced Geo aim point (thanks dyth68).
* Fixed Mariner special build icon size.
* Healthbars and Build ETA now draw in front of unit outlines.
* Fixed an error that could occur when destroying all the units of the losing team.
* Phoenix gibs no longer include a near-complete copy of its fuselage.

{{Navbox changelog}}

Template:Navbox commands

2024-11-01T04:58:37Z

RandomX: A little more consistency to spacing.

{{Navbox
| name = Navbox commands
| title = [[Unit_commands|Commands]]
| state = {{{state|}}}
| listclass = hlist

| group1 = Targeted
| list1 = *[[File:Move.png|16px|link=]] [[Move Command|Move]]
*[[File:Fight.png|16px|link=]] [[Attack Move Command|Attack Move]]
*[[File:Jump.png|16px|link=]] [[Jump Command|Jump]]
*[[File:Attack.png|16px|link=]] [[Force Fire Command|Force Fire]]
*[[File:Settarget.png|16px|link=]] [[Set Target Command|Set Target]]
*[[File:Cmd_dgun.png|16px|link=]] [[Fire Special Weapon Command|Fire Special Weapon]]
*[[File:Areaattack.png|16px|link=]] [[Area Attack Command|Area Attack]]
*[[File:Guard.png|16px|link=]] [[Guard Command|Guard]]
*[[File:Patrol.png|16px|link=]] [[Patrol Command|Patrol]]

| group2 = Economic
| list2 = *[[File:Repair.png|16px|link=]] [[Repair Command|Repair]]
*[[File:Reclaim.png|16px|link=]] [[Reclaim Command|Reclaim]]
*[[File:Resurrect.png|16px|link=]] [[Resurrect Command|Resurrect]]
*[[File:Mex.png|16px|link=]] [[Area Mex Command|Area Mex]]
*[[Buildings#Building_placement_and_construction|Building placement]]
*[[File:Factory.png|16px|link=]] [[Factory Production]]

| group3 = Instant
| list3 = *[[File:Cancel.png|16px|link=]] [[Stop Command|Stop]]
*[[File:Wait.png|16px|link=]] [[Wait Command|Wait]]
*[[File:Detonate.png|16px|link=]] [[Detonate Command|Detonate]]
*[[File:Wait_death.png|16px|link=]] [[Self Destruct Command|Self Destruct]]
*[[File:Canceltarget.png|16px|link=]] [[Set Target Command|Cancel Target]]
*[[File:Rearm.png|16px|link=]] [[Resupply Command|Resupply]]
*[[File:Recall_drones_new.png|16px|link=]] [[Recall Drones Command|Recall Drones]]
*[[File:Stopbuild.png|16px|link=]] [[Clear Production Queue]]
*[[File:Nuke.png|16x10px|link=]] [[Stockpile Command|Stockpile]]

| group4 = Transport
| list4 = *[[File:Load.png|16px|link=]] [[Load Command|Load]]
*[[File:Unload.png|16px|link=]] [[Unload Command|Unload]]
*[[File:Action.png|16px|link=]] [[Eject Cargo Command|Eject Cargo]]
*[[File:Embark.png|16px|link=]] [[Embark Command|Embark]]
*[[File:Disembark.png|16px|link=]] [[Disembark Command|Disembark]]

| group5 = Unusual
| list5 = *[[File:Capture.png|16px|link=]] [[Newton Firezones|Newton firezone commands]]
*[[Morph Command|Morph]]
*[[File:Upgrade.png|16px|link=]] [[Commander|Upgrade Commander]]
*[[File:Cancelupgrade.png|16px|link=]] [[Commander|Stop Commander Upgrade]]
*[[File:Cmd_bomb.png|16px|link=]] [[Unique Commands#Drop Bombs|Drop Bombs]]
*[[File:Cmd_bomb.png|16px|link=]] [[Unique Commands#Unleash Lightning|Unleash Lightning]]
*[[File:Cmd_drop_beacon.png|16px|link=]] [[Unique Commands#Teleport Beacon|Teleport Beacon]]
*[[File:Cmd_sprint.png|16px|link=]] [[Unique Commands#Speed Boost|Speed Boost]]
*[[File:Cmd_drop_beacon.png|16px|link=]] [[Evacuate Command|Evacuate]]

| group6 = Global
| list6 = *[[File:Ferry.png|16px|link=]] [[Ferry Command|Ferry]]
*[[File:Retreat.png|16px|link=]] [[Retreat|Retreat]]
*[[File:Storage.png|16px|link=]] [[Economy_Guide#Reserving_resources|Reserve]]

| group7 = Historical
| list7 = *[[File:Cmd_dgun.png|16px|link=]] [[Historical Commands#Drop Depthcharge|Drop Depthcharge]]

| below = [[Unit states]]

}}

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

Newton Firezones

2024-11-01T04:53:27Z

RandomX: Brought over Newton videos so they don't get lost when imgur kills them. Added navbox.

'''Set a Newton firezone''' command is used by [[Newton]] turrets to target a specific area. Setting a fire zone won't stop a turret set to fire at will from firing at enemies entering its range. It will realign to aim at the fire zone while idle. As a confirmation of fire zone setup, turrets will fire once at the center of chosen area. If a turret fails to do so, it might mean that the fire zone is obscured or unreachable. Any units entering a fire zone, ''including friendlies'', will be targeted.

[[File:Newton FZ setup.mp4|upright=2]]

This command can be used to set up your turrets to target only a specific area of terrain (such as cliffs or edges of islands).

== Ramp launchers ==
The main usage is the creation of ramp launchers. The strategy includes setting up a ramp using [[terraform]]ing, and using a bunch of Newton turrets to launch your units behind enemy lines.

[[File:Newton ramp setup.mp4|upright=2]]

Depending on the unit's mass, it might require more or fewer Newton turrets to send it the same distance. Not all units will be eligible to be "delivered" this way, as most will die from fall damage. The usual choice are [[Jumpbot Factory]] units, as some of them can negate fall damage by engaging their jump jets before landing. Lead units in one by one, as otherwise they may be launched either by not every turret at once (providing insufficient force), or from a wrong location (and be launched into the wrong direction, respectively).

{{Navbox commands}}

Main Page

2024-11-01T04:52:15Z

RandomX: Add some space at the bottom of the page.

[[File:zk_logo.png|center|link=]]
<div style="font-size:200%;text-align:center;margin:auto">Welcome to the Zero-K Wiki</div>
----

{{TOC right}}

This is the official wiki for the free open-source <abbr title="real-time strategy">RTS</abbr> game '''[//zero-k.info Zero-K]'''.
* If you're new to the game, consult the '''[[Manual]]''' for helpful information on how to get started.
* There is a [https://discord.gg/aab63Vt Discord server] which is linked to the game chat.
* You can log in to the wiki using your Zero-K account and password, or your Steam account. (Please use your Zero-K username if logging in with Steam, to avoid naming conflicts.)
* The wiki is still a work in progress. Some articles may not be up to date. Find out how you can help [[Editing Help|here]]!

== Overview ==
{| style="margin:auto"

|
; Game info
: [[Manual]]
: [[Units]]
: [[Buildings]]
: [[Commander]]
: [[Unit commands|Unit Commands]]

|
; Community
: [https://discord.gg/aab63Vt Discord]
: [https://zero-k.info/Forum Forum]
: [https://zero-k.info/Ladders Ladders]
: [https://steamcommunity.com/app/334920 Steam]
: [https://www.twitch.tv/directory/game/Zero-K Twitch]

|}

=== Manual ===
{{Navbox manual}}

=== Units ===
{{Navbox units}}

=== Buildings ===
{{Navbox buildings}}

=== Commands ===
{{Navbox commands}}

=== Planet Wars ===
{{Navbox planetwars}}

{{clear}}
[[Category:Manual|#]][[Category:Units|#]][[Category:Buildings|#]][[Category:Commands|#]]

Main Page

2024-11-01T04:47:57Z

RandomX:

[[File:zk_logo.png|center|link=]]
<div style="font-size:200%;text-align:center;margin:auto">Welcome to the Zero-K Wiki</div>
----

{{TOC right}}

This is the official wiki for the free open-source <abbr title="real-time strategy">RTS</abbr> game '''[//zero-k.info Zero-K]'''.
* If you're new to the game, consult the '''[[Manual]]''' for helpful information on how to get started.
* There is a [https://discord.gg/aab63Vt Discord server] which is linked to the game chat.
* You can log in to the wiki using your Zero-K account and password, or your Steam account. (Please use your Zero-K username if logging in with Steam, to avoid naming conflicts.)
* The wiki is still a work in progress. Some articles may not be up to date. Find out how you can help [[Editing Help|here]]!

== Overview ==
{| style="margin:auto"

|
; Game info
: [[Manual]]
: [[Units]]
: [[Buildings]]
: [[Commander]]
: [[Unit commands|Unit Commands]]

|
; Community
: [https://discord.gg/aab63Vt Discord]
: [https://zero-k.info/Forum Forum]
: [https://zero-k.info/Ladders Ladders]
: [https://steamcommunity.com/app/334920 Steam]
: [https://www.twitch.tv/directory/game/Zero-K Twitch]

|}

=== Manual ===
{{Navbox manual}}

=== Units ===
{{Navbox units}}

=== Buildings ===
{{Navbox buildings}}

=== Commands ===
{{Navbox commands}}

=== Planet Wars ===
{{Navbox planetwars}}

[[:Category:Manual|#]][[:Category:Units|#]][[:Category:Buildings|#]][[:Category:Commands|#]]

Main Page

2024-11-01T04:46:49Z

RandomX:

[[File:zk_logo.png|center|link=]]
<div style="font-size:200%;text-align:center;margin:auto">Welcome to the Zero-K Wiki</div>
----

{{TOC right}}

This is the official wiki for the free open-source <abbr title="real-time strategy">RTS</abbr> game '''[//zero-k.info Zero-K]'''.
* If you're new to the game, consult the '''[[Manual]]''' for helpful information on how to get started.
* There is a [https://discord.gg/aab63Vt Discord server] which is linked to the game chat.
* You can log in to the wiki using your Zero-K account and password, or your Steam account. (Please use your Zero-K username if logging in with Steam, to avoid naming conflicts.)
* The wiki is still a work in progress. Some articles may not be up to date. Find out how you can help [[Editing Help|here]]!

== Overview ==
{| style="margin:auto"

|
; Game info
: [[Manual]]
: [[Units]]
: [[Buildings]]
: [[Commander]]
: [[Unit commands|Unit Commands]]

|
; Community
: [https://discord.gg/aab63Vt Discord]
: [https://zero-k.info/Forum Forum]
: [https://zero-k.info/Ladders Ladders]
: [https://steamcommunity.com/app/334920 Steam]
: [https://www.twitch.tv/directory/game/Zero-K Twitch]

|}

=== Manual ===
{{Navbox manual}}

=== Units ===
{{Navbox units}}

=== Buildings ===
{{Navbox buildings}}

=== Commands ===
{{Navbox commands}}

=== Planet Wars ===
{{Navbox planetwars}}

[[Category:Units|#]][[Category:Buildings|#]][[Category:Commands|#]]

Main Page

2024-11-01T04:46:13Z

RandomX:

[[File:zk_logo.png|center|link=]]
<div style="font-size:200%;text-align:center;margin:auto">Welcome to the Zero-K Wiki</div>
----

{{TOC right}}

This is the official wiki for the free open-source <abbr title="real-time strategy">RTS</abbr> game '''[//zero-k.info Zero-K]'''.
* If you're new to the game, consult the '''[[Manual]]''' for helpful information on how to get started.
* There is a [https://discord.gg/aab63Vt Discord server] which is linked to the game chat.
* You can log in to the wiki using your Zero-K account and password, or your Steam account. (Please use your Zero-K username if logging in with Steam, to avoid naming conflicts.)
* The wiki is still a work in progress. Some articles may not be up to date. Find out how you can help [[Editing Help|here]]!

== Overview ==
{| style="margin:auto"

|
; Game info
: [[Manual]]
: [[Units]]
: [[Buildings]]
: [[Commander]]
: [[Unit commands|Unit Commands]]

|
; Community
: [https://discord.gg/aab63Vt Discord]
: [https://zero-k.info/Forum Forum]
: [https://zero-k.info/Ladders Ladders]
: [https://steamcommunity.com/app/334920 Steam]
: [https://www.twitch.tv/directory/game/Zero-K Twitch]

|}

=== Manual ===
{{Navbox manual}}

=== Units ===
{{Navbox units}}

=== Buildings ===
{{Navbox buildings}}

=== Commands ===
{{Navbox commands}}

=== Planet Wars ===
{{Navbox planetwars}}

[[:Category:Units|#]][[:Category:Buildings|#]][[:Category:Commands|#]]

File:Newton ramp setup.mp4

2024-11-01T04:30:38Z

RandomX: Re-compressed to meet the size limit and imported from https://imgur.com/fUUckMe Hopefully, someone will fix the text in the video and reupload at some point.

== Summary ==
Re-compressed to meet the size limit and imported from https://imgur.com/fUUckMe

Hopefully, someone will fix the text in the video and reupload at some point.
== Licensing ==
{{Zero-K screenshot}}

File:Newton FZ setup.mp4

2024-11-01T04:28:36Z

RandomX: Re-compressed and imported from https://imgur.com/f8LH3dS

== Summary ==
Re-compressed and imported from https://imgur.com/f8LH3dS
== Licensing ==
{{Zero-K screenshot}}

Transportation

2024-10-30T18:10:05Z

RandomX: Brought videos to the wiki so they don't get lost when imgur decides to retire them. A few minor text changes.

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. 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 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 ([[File:Bulb on.png|18px|alt=light bulb]]) 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. Transports called by the ''Embark'' command will return to the spot where they took the unit using the same path.
*'''Disembark'''—safely exit 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, while 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 is nearby, it will pick them up, drop them off, and the units 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, and transports will carry them to enemy base.
; Select Dantes, give them move commands across 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 and 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]]).

[[File:Route set up.mp4|right|upright=1.3]] 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.

[[File:Route edit.mp4|left|upright=1.3]] 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.{{clear}}

[[File:Route del.mp4|left|upright=1.3]] To remove a ferry route, click the ferry route button and left-click a start location.{{clear}}

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 to 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 {{key press|Shift}}-queue commands for the unit, and it will follow the commands after arrival at the destination.

[[File:Route exec.mp4|upright=2]]

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.

Although the ferry routes are automated, they still require regular oversight. Under certain circumstances, a unit may end up waiting to be transported forever. Also, units waiting for transports may enter the [[Wait Command|Wait]] state, denoted by an hourglass icon above the unit, which will prevent them from defending themselves.



{{Navbox manual}}

File:Route exec.mp4

2024-10-30T17:41:03Z

RandomX: Imported and re-compressed, original at https://imgur.com/XHY0vP7

== Summary ==
Imported and re-compressed, original at https://imgur.com/XHY0vP7
== Licensing ==
{{Zero-K screenshot}}

File:Route set up.mp4

2024-10-30T17:34:35Z

RandomX: Imported from https://imgur.com/XHY0vP7

== Summary ==
Imported from https://imgur.com/XHY0vP7
== Licensing ==
{{Zero-K screenshot}}

File:Route edit.mp4

2024-10-30T17:33:45Z

RandomX: Imported from https://i.imgur.com/WC2qb03.mp4

== Summary ==
Imported from https://i.imgur.com/WC2qb03.mp4
== Licensing ==
{{Zero-K screenshot}}

File:Route del.mp4

2024-10-30T17:32:32Z

RandomX: Imported from https://imgur.com/SHFhe68

== Summary ==
Imported from https://imgur.com/SHFhe68
== Licensing ==
{{Zero-K screenshot}}

Template:Ratio/doc

2024-10-30T03:58:19Z

RandomX: Initial doc

Put a ratio like 1:1 into this template, and the colon will be replaced with the proper ratio symbol, like so: {{{{BASEPAGENAME}}|1:1}}. Depending on the font, this change may not even be obvious (and some systems may not be able to show it at all due to missing glyph, but there's no fallback for now).

More importantly, though, the entire ratio will be treated as a unit (won't break) at the end of a line.

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

Template:Sqrt

2024-10-30T03:40:54Z

RandomX: Slightly better (maybe) connection between radical and vinculum.

<span style="font-size-adjust:ex-height .66;line-height:100%">√</span><span style="text-decoration:overline">{{expr|{{{1|<var>radicand</var>}}}}}</span><noinclude>
{{Documentation}}</noinclude>

Manual

2024-10-30T03:04:12Z

RandomX: Moved purge template to the navbox...

Welcome to the Zero-K manual! This manual includes game documentation, gameplay guides, modding resources and other relevant information.

<div style="columns:auto 30em;column-rule:thin dashed gray">
<div style="break-inside:avoid">
== Getting Started ==
{{:{{PAGENAME}}/Getting Started}}

</div><div style="break-inside:avoid">
== Units ==
=== Unit References ===
{{:{{PAGENAME}}/Unit References}}

=== Unit Abilities ===
{{:{{PAGENAME}}/Unit Abilities}}

=== Unit Features ===
{{:{{PAGENAME}}/Unit Features}}
* [[File:robot2.png|link=]] [[Unit Management|Effective unit usage guide]]

</div><div style="break-inside:avoid">
== General Features ==
{{:{{PAGENAME}}/General Features}}

</div><div style="break-inside:avoid">
== Further Game Info ==
{{:{{PAGENAME}}/Other Info|inline}}
* [[Configuration Files|Transfer settings to Steam]]
* [[4k help|Running Zero-K on a 4k monitor]]

</div><div style="break-inside:avoid">
== Development and Modding ==
{{:{{PAGENAME}}/Coding}}
* [[Lua Architecture]]
* [[Reporting Bugs]]

</div><div style="break-inside:avoid">
== Strategy Guides ==
{{:{{PAGENAME}}/Strategy|inline}}
* [[File:factory.png|x16px|link=]] [[Optimal rover squads guide]]

</div><div style="break-inside:avoid">

== Tournament Info ==
* [[File:tropy_gold.png|x16px|link=]] [[Tournaments]]
* [https://zero-k.info/Forum/Thread/20258 Archive of Past Tournaments]

</div><div style="break-inside:avoid">
== Planetwars ==
* [[PlanetWars attack|Attacking]]
* [[PlanetWars influence|Influence]]
* [[PlanetWars planets|Planets]]

== Planetwars (old) ==
* [[PlanetWars|Introduction to Planetwars]]
* [[PlanetWars attack|Attacking]]
* [[PlanetWars initiative|Initiative]]
* [[PlanetWars ships|Ships]]
* [[PlanetWars structures|Structures]]
* [[PlanetWars economy|Economy]]
* [[PlanetWars faction roles|Faction Roles]]
* [[PlanetWars events|Events]]
* [[PlanetWars factions|History]]
</div>
</div>

{{Navbox manual}}

Template:Navbox manual

2024-10-30T03:03:49Z

RandomX: Added purge template....

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

| group1 = Basics
| list1 = {{:Manual/Getting Started}}

| group2 = Units
| list2 = {{:Manual/Unit References}}

| group3 = Unit abilities and features
| list3 = {{:Manual/Unit Abilities}}
{{:Manual/Unit Features}}

| group4 = Other features
| list4 = {{:Manual/General Features}}

| group5 = Other information
| list5 = {{:Manual/Other Info|none}}

| group6 = Strategy
| list6 = {{:Manual/Strategy|none}}

| group7 = Development/Modding
| list7 = {{:Manual/Coding}}
}}

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

Cold Takes

2024-10-25T20:39:19Z

RandomX: Added 20.

Cold Takes is a series of design blog posts started by GoogleFrog in December 2023. A new one is released every second Sunday. Links are below, but someone should probably copy them to the wiki before Steam reorganises itself (hint hint).

* {{blog post link|//store.steampowered.com/news/app/334920/view/3868091084290486602|Cold Take|1 - Why Zero-K}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/3875973926280115016|Cold Take|2 - Quant's Rule}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/3887234011192023190|Cold Take|3 - Fight your opponent, not the UI}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/3887234011247278813|Cold Take|4 - Factories as Factions}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/3990819338898810107|Cold Take|5 - Making Metal}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/3958168875487633267|Cold Take|6 - Physics vs. Formulas}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/6001679204174153483|Cold Take|7 - Jumpjets and Jumplegs}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4102287868180887053|Cold Take|8 - Smoothly Flowing Economy}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/5969030636156442045|Cold Take|9 - Energy as Supply}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4205874461249023268|Cold Take|10 - The Smartest Unit in Zero-K}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4202498029349040781|Cold Take|11 - The Atomic Solution to Monospam}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/6398004206839876250|Cold Take|12 - Mighty Morphing}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4155212770698415116|Cold Take|13 - Pro-Simplicity, Anti-Nuke}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4268931197552327328|Cold Take|14 - Free Factories For All}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4356753927297880954|Cold Take|15 - Experiences With Veterancy}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4356753927297594043|Cold Take|16 - Aim and Fire}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4268936271617655343|Cold Take|17 - Tactical and Strategic Cloaking}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4577434114386644037|Cold Take|18 - Terrain Matters}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4683271241468857961|Cold Take|19 - Game Jams}}
* {{blog post link|//store.steampowered.com/news/app/334920/view/4518891123292895731|Cold Take|20 - Teamwork By Default}}

[[Category:Cold Takes|#]]

Cold Takes/20 - Teamwork By Default

2024-10-25T20:38:15Z

RandomX: Initial transfer.

{{blog post||19 Oct 2024}}

Zero-K pushes the limit of team games in RTS, supporting up to 16 players per side - something that sounds impossible. Your average RTS caps out at 4v4, with a few going as high as 6v6. In Zero-K players regularly play games three times this size, and while such large games are not for everyone, I suggest trying them out just for the experience. There is a real sense of scale in a game with so many players, taking so many actions, in which you can only really zoom in and understand a relatively small part. But it is surprising that such games work at all, so in this article we are going to dive into the design that makes them possible.

[[File:World map with icons.png]]

The weirdest part of the story is that, for the most part, support for large team games came about accidentally. The rest of the Zero-K design philosophy just happens to inherently let teams have a large number of players. From time to time we added features aimed at large games, but most of the work is done by principles covered in [[Cold Takes|previous cold takes]]. We could have deliberately removed large teams, but the attempt would warp the rest of the design, and it is not like they are hurting other game modes. Small games, down to 1v1 and 2v2, work fine, and the way I see it, supporting more game modes is good.

The bulk of the work is done by [[Cold Takes/3 - Fight your opponent, not the UI|''Fight your opponent, not the UI'']], plus the realisation that players coordinate with their team via the user interface. Essentially, cooperation within a team should be free of artificial limitations or hoops to jump through, in much the same way as any other action in the game. Zero-K contains simple examples of cooperation UI, such as the [[v1.11.6.2|nuke indicator]] that tells players where an allied nuke is expected to land, but not fighting the UI goes deeper than that.

[[File:Allied indicators.png]]

Zero-K is the game that [[Cold Takes/10 - The Smartest Unit in Zero-K|designs the stupidity out of units]] and uses [[Cold Takes/16 - Aim and Fire|designs weapons using unattainable ideals]], and we take the same approach to cooperation. Like units, players have abilities that influence the game, and we consider it a failure if the mechanics of the game force players down the route of boring and arduous use of the UI. So while most games would happily add a nuke indicator, few would go the extra step of excising fundamentally anti-cooperative mechanics to the extent that we do.

We inherited key player abilities, namely the ability to freely share units and resources, from [[Cold Takes/1 - Why Zero-K|Total Annihilation]]. This is a fairly standard function for RTS games, but the implications are far-reaching, and Zero-K has a penchant for taking ideas to the extreme and biting the resulting bullets. The issue with sharing is that sharing UIs are invariably some of the worst found in RTS. They tend to resemble big spreadsheets of fiddly buttons or sliders, which is not what we want in an RTS. So contact with this UI should be minimised, which relegates sharing to an almost "theoretical" ability, one that the game is designed around, but which players should rarely manually invoke. This generalises to the principle of the <dfn style="font-style:italic">irrelevance of ownership</dfn>:

:'''Nothing in the mechanics of the game world is permitted to depend on the details of ownership within a team, because then players would be incentivised to touch the unit sharing UI to gain an advantage.'''

Few games use this principle, since it is automatically violated by player-specific upgrades. Even within the TA-lineage, Supreme Commander lets units of the same player shoot through each other, but not through allies. Even Zero-K violates the principle, since unidentified radar dots reveal team colour, which can let the enemy guess the identity of unseen units. This is something I have wanted to be able to turn off, but it requires engine work, and to walk back the extremism a bit, dot colour may well improve the game.

The principle of irrelevance of ownership sounds restrictive, but it is also quite freeing, and we were not going to add global upgrades regardless. A key implication of the principle is that resource income can be distributed arbitrarily within a team, without any theoretical impact on in-world game balance. In practise this let us fiddle with income sharing to "simulate" cooperation among strangers on the internet, which is part of what allows such large team games to work. For example, income from metal extractors is shared evenly between everyone on the team, which was called communism mode in early [[Cold Takes/1 - Why Zero-K|Complete Annihilation]]. Communism evolved alongside the rest of the game, and quickly became integrated with [[Cold Takes/5 - Making Metal|overdrive]], since the overdrive formula benefits from shared resources.

[[File:Commie mode.jpg]]

The theoretical justification for communism is that securing territory is a shared effort, and much harder than merely building a metal extractor, so the team shares the benefit. The practical justification was more important at the time though, since we all had experience with people arguing over metal spots in [[Cold Takes/1 - Why Zero-K|Balanced Annihilation]], which could escalate to teamkilling. A secondary effect in BA was the limited map pool; players tended to play a small set of maps, where everyone understood the meta of spot ownership, in part to lessen the potential for arguments over resources.

It is worth mentioning that I snuck an assumption into communism: that players want to cooperate. What if people want to keep their income to themselves? This gets at the core of the design: we assume that the team wants to cooperate, teamwork is the default. If players want to argue and destroy each other's buildings, then they might not find support for these actions in the UI. There is also a bit of a paradox here, as anyone who has played a team game with a range of skill levels can tell you: who owns what is actually very important. But instead of trying to judge the worth of each player, we opted to make a game where part of the skill is in being a good teammate, rather than rolling over the weaker members on your team as you grow your own personal empire.

Communism solved the metal spot arguments and opened up the map pool, but it suffered from the free rider problem. Some players would skip building metal extractors all together, hoping that their teammates would pick up the slack. Full communism was also not great at incentivising overdrive, even when it would significantly benefit the team. So we added rebates. For example, metal extractors refund 80% of their cost to the player(s) that built them, over a few minutes, in the form of a slightly increased share of the income. [[Cold Takes/9 - Energy as Supply|Energy structures]] offer a similar refund of 60% from their increased [[Cold Takes/5 - Making Metal|metal overdrive income]]. The numbers have been tweaked over the years, since a higher payback percentage can lead to perceptions of selfishness by energy spammers. We even recently introduced payback for the first few Antinukes built by a team, as a social way to nerf nukes in low-cooperation situations.

[[File:Rotationally symmetric.png]]

Shared metal extractors also helped with the "Tabula Problem" caused by some rotationally symmetric maps. Tabula has high terrain on its North and South, that is easier to take and defend from the North-West and South-East respectively. Before communism, Tabula was typically won by the team that invaded the weak low ground from the strong high ground, before their opponent did the same on the other side of the map. The low ground just lacked the metal income required to mount a defense, without players manually sharing units or metal extractors. Tabula continued to play a bit like this since communism, the low ground still has poor terrain, but the extra income makes the defense fairer and more interesting.

Income sharing alone is not enough to make large games fun. For that we need the rest of Zero-K, primarily its unit and faction design. Our large number of [[Cold Takes/4 - Factories as Factions|faction-like factories]] lets players carve out a distinct role and set of units within the team, and [[Cold Takes/14 - Free Factories For All|factory plop]] lets everyone build a factory without "wasting" resources. There was concern that the recent addition of [[v1.8.8.2|factory plates]] would destroy this sense of having a role within a team, but the fear has not come to pass. If anything they seem to have improved team games by letting players take on a role they are not sure of, with the safety of being able to switch out of it cheaply.

[[File:Multiple Factories.png]]

The coordination feature that came closest to breaking the game was shared control mode, where players own and control the same set of units. The campaign has shared control, but it can also be enabled in team games via an invite system. The danger with shared unit control is that it can be powerful, but it is also quite annoying when someone else accidentally uses "your" units. This is the dreaded trade-off, power at the cost of fighting the UI, but the mode is barely used in public games. Tournament and campaign games are different, since people can communicate enough to avoid the downsides, and in these contexts it is a great feature.

As with many automation-type features, it is worth asking whether cooperation has been automated away. I think we are fine on this front; teammates send messages, flank, and otherwise help each other out. People still share the occasional unit to augment fronts that really need it. Mostly we have removed the excess UI interactions, and set a baseline level of cooperation so players can expand as much as they want without worrying about "stealing" metal spots. Perhaps the greatest benefit is too the map pool, as any map can be played with any number of players, for a really wide range of experiences.

This marks the end of the first series of cold takes. Twenty is a nice round number and it is time for a short break. Look forward to the next series starting in January next year.

File:20 - Teamwork By Default.jpg

2024-10-25T20:37:57Z

RandomX:

== Licensing ==
{{Zero-K screenshot}}

File:Rotationally symmetric.png

2024-10-25T20:35:29Z

RandomX:

== Licensing ==
{{Zero-K screenshot}}

File:Commie mode.jpg

2024-10-25T20:34:51Z

RandomX:

File:Allied indicators.png

2024-10-25T20:34:34Z

RandomX:

== Licensing ==
{{Zero-K screenshot}}

File:World map with icons.png

2024-10-25T20:34:09Z

RandomX:

== Licensing ==
{{Zero-K screenshot}}

Module:Lua banner

2024-10-24T03:11:12Z

RandomX:

-- This module implements the {{lua}} template.

local yesno = require('Module:Yesno')
local mList = require('Module:List')
local mTableTools = require('Module:TableTools')
local mMessageBox = require('Module:Message box')

local p = {}

function p.main(frame)
local origArgs = frame:getParent().args
local args = {}
for k, v in pairs(origArgs) do
v = v:match('^%s*(.-)%s*$')
if v ~= '' then
args[k] = v
end
end
return p._main(args)
end

function p._main(args)
local modules = mTableTools.compressSparseArray(args)
local box = p.renderBox(modules)
local trackingCategories = p.renderTrackingCategories(args, modules)
return box .. trackingCategories
end

function p.renderBox(modules)
local boxArgs = {}
if #modules < 1 then
boxArgs.text = '<strong class="error">Error: no modules specified</strong>'
else
local moduleLinks = {}
for i, module in ipairs(modules) do
moduleLinks[i] = string.format('[[:%s]]', module)
end
local moduleList = mList.makeList('bulleted', moduleLinks)
boxArgs.text = 'Uses [[Wikipedia:Lua (programming language)|Lua]]:\n' .. moduleList
end
boxArgs.type = 'notice'
boxArgs.small = true
boxArgs.image = '[[File:Lua-logo-nolabel.svg|30px|alt=Lua logo|link=Wikipedia:Lua (programming language)]]'
return mMessageBox.main('mbox', boxArgs)
end

function p.renderTrackingCategories(args, modules, titleObj)
if yesno(args.nocat) then
return ''
end

local cats = {}

-- Error category
if #modules < 1 then
cats[#cats + 1] = 'Lua templates with errors'
end

-- Lua templates category
titleObj = titleObj or mw.title.getCurrentTitle()
local subpageBlacklist = {
doc = true,
sandbox = true,
sandbox2 = true,
testcases = true
}
if titleObj.namespace == 10
and not subpageBlacklist[titleObj.subpageText]
then
local category = args.category
if not category then
local categories = {
['Module:String'] = 'Lua String-based templates',
['Module:Math'] = 'Templates based on the Math Lua module',
['Module:BaseConvert'] = 'Templates based on the BaseConvert Lua module',
['Module:Citation'] = 'Lua-based citation templates'
}
categories['Module:Citation/CS1'] = categories['Module:Citation']
category = modules[1] and categories[modules[1]]
category = category or 'Lua-based templates'
end
cats[#cats + 1] = category
end

for i, cat in ipairs(cats) do
cats[i] = string.format('[[Category:%s]]', cat)
end
return table.concat(cats)
end

return p

Module:Lua banner

2024-10-24T03:09:48Z

RandomX: A more direct link to the Lua page on w:

-- This module implements the {{lua}} template.

local yesno = require('Module:Yesno')
local mList = require('Module:List')
local mTableTools = require('Module:TableTools')
local mMessageBox = require('Module:Message box')

local p = {}

function p.main(frame)
local origArgs = frame:getParent().args
local args = {}
for k, v in pairs(origArgs) do
v = v:match('^%s*(.-)%s*$')
if v ~= '' then
args[k] = v
end
end
return p._main(args)
end

function p._main(args)
local modules = mTableTools.compressSparseArray(args)
local box = p.renderBox(modules)
local trackingCategories = p.renderTrackingCategories(args, modules)
return box .. trackingCategories
end

function p.renderBox(modules)
local boxArgs = {}
if #modules < 1 then
boxArgs.text = '<strong class="error">Error: no modules specified</strong>'
else
local moduleLinks = {}
for i, module in ipairs(modules) do
moduleLinks[i] = string.format('[[:%s]]', module)
end
local moduleList = mList.makeList('bulleted', moduleLinks)
boxArgs.text = 'Uses [[Wikipedia:Lua (programming language)|]]:\n' .. moduleList
end
boxArgs.type = 'notice'
boxArgs.small = true
boxArgs.image = '[[File:Lua-logo-nolabel.svg|30px|alt=Lua logo|link=Wikipedia:Lua (programming language)]]'
return mMessageBox.main('mbox', boxArgs)
end

function p.renderTrackingCategories(args, modules, titleObj)
if yesno(args.nocat) then
return ''
end

local cats = {}

-- Error category
if #modules < 1 then
cats[#cats + 1] = 'Lua templates with errors'
end

-- Lua templates category
titleObj = titleObj or mw.title.getCurrentTitle()
local subpageBlacklist = {
doc = true,
sandbox = true,
sandbox2 = true,
testcases = true
}
if titleObj.namespace == 10
and not subpageBlacklist[titleObj.subpageText]
then
local category = args.category
if not category then
local categories = {
['Module:String'] = 'Lua String-based templates',
['Module:Math'] = 'Templates based on the Math Lua module',
['Module:BaseConvert'] = 'Templates based on the BaseConvert Lua module',
['Module:Citation'] = 'Lua-based citation templates'
}
categories['Module:Citation/CS1'] = categories['Module:Citation']
category = modules[1] and categories[modules[1]]
category = category or 'Lua-based templates'
end
cats[#cats + 1] = category
end

for i, cat in ipairs(cats) do
cats[i] = string.format('[[Category:%s]]', cat)
end
return table.concat(cats)
end

return p

Cold Takes/7 - Jumpjets and Jumplegs

2024-10-24T03:05:08Z

RandomX: Pretty sure that's the right xponen... but feel free to correct if this is wrong.

{{blog post||24 Feb 2024}}{{TOC right}}

Jumping is old, going back to the early days of [[Cold Takes/1 - Why Zero-K|Complete Annihilation]], which predates Zero-K. It is also a very stable mechanic, to the point where a player from 15 years ago would not see the difference just from using it. In part this is due to its simplicity: just give a unit which can jump a jump order, and it will jump to the location once it is in range. But it is also because surprisingly little has changed.

So why write an article about jumping? Well, while there have been a few changes, each one reveals a further refinement in the design of Zero-K. Even more revealing are the ways that jumping has deliberately stayed the same, in the face of potential changes. So here are four mini-articles on the how, what, where, and legs(?) of jumping.

[[File:Jumping Pyro.gif]]

==Which units jump?==
Perhaps the most important aspect of any ability is the types of units that can use it. Jump is one of the many abilities associated with a particular factory, in this case the Jumpbot factory, but in an unusual way. Other factories with a unique movement ability, such as the Hovercraft Platform or Spider Factory, have that ability on all of their units, whereas only about half the Jumpbots jump. This makes Jumpbots more like Cloakbots or Shieldbots, which each only have a few cloaked or shielded units. Furthermore, the Shieldbots' Dirtbag jumps, as well as the Recon Commander, and the largest unit in the game - the Detriment. This smattering of jumping is also similar to cloaking and shields.

To see why Jumpbots ended up like this we have to go back to CA, since only commanders and Detriment have gained jumping since then. Jump was an ability exclusive to the Core faction, to mirror Arm's exclusive access to all-terrain spiders. Each faction had two tiers of bot factories, with a few all-terrain options in the higher tier factory. Placeholder and Firewalker, two non-jumping Jumpbots, did not exist at the time, and Moderator existed in the skirmisher role, but with a different weapon. Technically we could have let Moderator jump, its role stopped us.

[[File:Jumping Moderator.png]]

Jumping is not just a way to move around the map, it is also a tactical ability that bestows a burst of speed. So a jumping skirmisher violates [[Cold Takes/2 - Quant's Rule|Quant's Rule]], since skirmishers are meant to be weak to fast units that negate their range advantage. Jumping is an excellent escape tool that negates this weakness, so Moderator was not given the ability to jump. Firewalker is non-jumping for the same reason, and also because dislodging artillery from awkward cliffs sounds very annoying. Spiderbots lack true artillery for the same reason.

In addition to violating Quant's Rule, using jumping skirmishers also sounds tedious. Jumping with a short ranged unit is a game of risk, reward, and sudden retreats, while jumping with a skirmisher sounds like game of routinely retreating when enemies get too near. Such a thing feels like it could be automated, which also comes into conflict with the idea of [[Cold Takes/3 - Fight your opponent, not the UI|fighting your opponent, not the UI]].

We considered creating a combined jump and spider factory while CA was being [[Cold Takes/4 - Factories as Factions|merged into one faction to create Zero-K]]. The goal was to create a fleshed-out all-terrain factory, and on paper it worked quite well. The only spiders at the time were Flea, Venom, Recluse and Crab, which fill the scout, riot and skirmisher roles, which leaves the raider, assault and anti-heavy roles to be filled by Pyro, Jack and Skuttle. However, this idea did not make it beyond prototyping, and instead we settled on the Jumpbot and Spiderbot factories we have today. I do not recall the exact process behind the decision, but here are some likely factors.
*Jumping is a sudden bursts of speed, while spiders can constantly dance around cliffs. These are distinct styles so should be in different factories to let the distinctiveness flourish.
*The combined factory would be too full, and too flexible, with all the units it could contain.
*It would be tricky to find new homes for all the non-jumpers and non-spiders that we wanted to keep from the rest of the bot factories.
*Having two factions that can play very hilly maps, or areas of maps, seems much better for diversity.
*Jugglenaut and Crab would fight over the role of the factory's signature unit.

The solution was to add Hermit and Tarantula to flesh out the spiders, and make Widow all-terrain. Redback was added later to let Venom move more towards a raider role. As for the Jumpbots, they are essentially the old CA tier 2 Core bot factory, with a few new units added later.

As for why there are no new jumping units, that goes back to the Zero-K approach to uniqueness. Many sci-fi strategy games use a weapon-chassis approach to unit design, where units can be boiled down to a combination of weapon and movement types. Sometimes there is even an in-game unit designer to make this breakdown explicit. Zero-K ''can'' be viewed through the lens of chassis and weapons, but there are so many holes in the matrix, and extra subtleties on top, that doing so is of limited use. Zero-K units aim to be more distinctive than combinations of weapon and chassis, and adding more jumping units for existing roles would work against that. Besides, jumping is primarilly a Jumpbot feature, and there are plenty of mechanics to build other factories around.

[[File:Jump fac units.png]]

==Jump physics==
Jumping is surprisingly [[Cold Takes/6 - Physics vs. Formulas|non-physical]] for a game with unit launchers and Lobsters. A jumping unit follows a set trajectory until it either dies or lands on a building, so unless that happens, it is guaranteed to end up safely on the ground. Its trajectory is calculated at the start of the jump, although the jump will be blocked if it would pass through terrain. This is all very deliberate, to the point where an impulse-based alternative written by the developer [//github.com/xponen xponen] was not adopted. This new system used dynamically scripted physical forces to launch and guide units through the air, then slow them down at the other end to avoid taking fall damage. It was essentially a simplified and automated Kerbal Space Program.

The impulse-based system was rejected for the unreliability inherent in its design. The goal of the system was to give units full physics while jumping, which meant that sufficient incoming fire could knock them off-course. Jumping multiple units was particularly risky since they would bump into each other mid-air, and even a slight course adjustment could lead to a unit bouncing away, down a cliff, and into a puddle. But how is this distinct from Lobster lob, which was added much later? Lobster picks up units and physically throws them in a direction, with the only nod to safety being temporary fall damage immunity.

[[File:Lobbed units.png]]

The difference between Lobster and jumping lies in their centrality. Lobster is a somewhat niche midgame support unit, while many jumping units, particularly Pyro and Constable, are built from the very start of the game. As such, jumping has to be much more reliable. A Lobster causing part of an army to bounce down a cliff is recoverable, and to some extent it is the price of using Lobster. Armies are large enough by that point for things to average out. An early Pyro failing to jump up a cliff, or a constructor becoming stuck, would feel really bad and could be game deciding.

The general principle here is that, if you want to build a faction around a mechanic, it had better be reliable. People have to be able to trust their units' basic abilities, since taking even a slim risk of complete failure into account is too taxing. On the other hand, tactics that appear later in the game can afford to have a bit more risk. There are more options later in the game, so using any particular one is more opt-in, and there are more ways to mitigate risk.

As for the unused impulse-based jump code, there is a happy ending. Amphibious floating was originally implemented in the same way as jumping, with a set trajectory. This leaves a lot to be desired, and I could see xponen trying to get more physics into the game, so I suggested that the impulse jump tech be used for floating. This worked great since units bobbing around and bouncing off each other is a great feature for floating, and it cannot fail in the same ways as jumping. Floating is much better for it, and the impulse jump code still exists in the repository, so a modder could even pick it up for use in a game with a different set of goals.

[[File:Impulse floaters.png]]

==What are jumplegs?==
The lack of interaction between jumping and the rest of physics has a few weird effects. Units can jump from anywhere to anywhere, provided it is in 2D range, which includes while flying through the sky after being launched from a unit cannon. Jumping just follows a calculated trajectory, which causes launched units to turn sharply and float towards the ground when they jump. I remember launching Pyros across Victoria Crater almost as soon as Newton was implemented. However, there have been a few problems.

Skuttle is a cloaking, jumping, bomb, which made it a particularly powerful unit to launch. Imagine the Sky Jacks of today, except they are cloaked and 1-shot their target. The best theoretical counter was positioning Hercules, or any other high-flying gunship, above anything important to decloak the Skuttle, and spamming Pickets. This was far too expensive, arduous, and silly, so we considered ways to nerf the tactic. Removing cloak was not an option since Skuttle needs to cloak while jumping for its mundane uses, so instead we removed its ability to jump mid-air. Thus the distinction between jumplegs and jumpjets was born.

[[File:Jumping Skuttle.png]]

A unit with jumplegs can jump, but not from mid-air. Skuttle was given jumplegs, along with some other units that looked like they use legs to jump. Notably, Pyro and Jack were given jumpjets, so retained their utility in unit launchers. This reflects the broader design philosophy of trying to retain as many of the creative combinations of mechanics as possible. It would have been easy to remove mid-air jumping entirely, but instead we surgically patched out the bits that would clearly break the game. Besides, jumping from anywhere has synergy with Placeholder, and saving units that are knocked off cliffs by enemy fire is cool.

Splitting jets and legs also let us make jet break cloaking. This had to happen eventually, but was blocked by Skuttle needing to cloak, since the smoke and fire emitted by jumpjets ignore cloaking. Effects like these can be seen by players, but not their units, which gives players extra information. This leads to a form of fighting the UI where players want to tell their units to shoot at the mysterious smoke, but cannot. In these cases we either remove the effect while cloaking, or make the effect decloak, to bring player knowledge in line with unit knowledge. The former is applied to damaged-unit smoke, which is suppressed for cloaked units for this very reason, but would look silly when applied to jets. The latter, decloaking the unit, was initially why units decloak when they take damage, since projectiles exploding mid-air is suspicious.

[[File:Legs and jets.png]]

The existing jumpers were split into jets and legs on aesthetic ground. Basically, if a unit already had leg animations, then it was given leg mechanics. This was particularly good for units with a wind-up animation, since the animation caused them to actually stop mid-air to do their animation, which was too cartoony even for Zero-K. Detriment jump, which was added later, has a wind-up animation and a rocket jet, so mechanically it has jets and legs. It decloaks when it jumps and cannot jump mid-air.

Recon Commanders was hit the hardest by the addition of jumpjet decloaking, since it can equip a personal cloak module. I recall this being a desirable change at the time though, as cloak made the commanders a bit too slippery. Jugglenaut and Detriment also decloak when they land, since their impacts create a visible explosion.

[[File:Jumping Jugglenauts.png]]

==Where can units jump?==
The question of where units should be able to jump is a tricky one, since both extremes lead to frustration. Highly restrictive jumping will cause units to annoyingly refuse orders that it "should" be able to carry out, while unrestricted jumping results in players unintentionally ordering their units to become stuck on impassible terrain. The current system is as follows.
*Units cannot jump onto terrain that is too steep, since they would become stuck.
*Units can jump onto structures, however, the jump ends when they hit the structure.
*Units can jump into water, provided the terrain under the water is not too steep.
*Units cannot jump out of the water, except Detriment and commanders, since they are amphibious.

These rules work surprisingly well, and have been tweaked over the years. Originally units could jump out of water but not onto structures.

Jumping onto structures used to be impossible. The issue with allowing it is that a jump trajectory would let units clip completely into structures, making them impervious to enemy fire. However, this had to be solved, since being unable to jump at structures felt like too much of an arbitrary limitation. Jacks were looking silly milling around the bases of terraformed turrets, and a Singularity Reactor in a hole should be more vulnerable to jumpers, not less. So we let jump target structures, but interrupt it as soon as the unit hits the structure. This lets Jacks jump up to get a few hits on a turret on a spire before bouncing back down, limiting its damage output by its jump recharge.

Interrupting a jump when it hits a structure leaves units at the mercy of physics, so they could bounce off the structure and fall down a cliff, but I do not recall any complaints. Perhaps it is because such a jump is a deliberate decision, and one that rarely has to be taken early in the game. People naturally give jump orders on open terrain, when it is available. The bouncing is also much more restrained than full impulse-based jump, since the jump is always interrupted very close to the destination.

It also used to be possible to jump out of the water, and there was even the idea of making jumping units fully amphibious. Jack could already be used amphibiously since melee weapons fire underwater. However, the idea of giving jump a small amount of underwater utility was dropped because it was too tedious. Babysitting units across the sea by chaining jump was a form of fighting the UI, which we resolved by removing the possibility. The idea of full amphibious movement was dropped because jump already bypasses cliffs, so if it bypassed large bodies of water, then there would be too few ways to make a hard barrier against it.

[[File:Jumping Jack.png]]

Units can jump into water because it seems like something they should be able to do, and there are more upsides than downsides. Sometimes it is worth saving a Jack or Jugglenaut by telling it to jump into the sea. Rescuing such units is just a matter of a little terraform, to give them a small platform of dry land to jump from. In theory these units can jump in any direction, so it stands to reason that they should jump into the sea if it is to their advantage to spend some time stuck underwater. Jumping into the water accidentally is bad, but water is visually distinct enough to make this very rare.

There would be times when units would want to jump onto terrain that is too steep, where they would be stuck until they jump out again. However, terrain steepness is harder to make out than water, no matter how clearly it is shown, and there are far fewer advantages, since the main purpose of water is to block projectiles. Ability restrictions are about balancing the feel of units being able to freely use their abilities against the risks of each application. A niche use for an ability that has a high risk of being accidentally misused is not worth allowing.

[[File:Jumper chaos.png]]

==Distilling some principles==
Hopefully that was a useful insight into some aspects of jump design. Most of these articles involve dredging the principles out of my subconscious, which means at the outset I am not entirely sure how the concepts will be carved up. So I would like to take a moment to summarise a few of the new ones we saw.
*'''Jank Escalation''' - Mechanics that are central to some core set of units need to be reliable, so players can trust them. More niche mechanics, or those that show up later in the game, can have more risk involved. So jumping is reliable while Lobster is not.
*'''Disciplined Physics''' - Physics is great, but it should not be used at the expense of other considerations. Zero-K does not set out to apply the maximum level of physical simulation so usability often takes precedence, as mentioned in [[Cold Takes/6 - Physics vs. Formulas|Physics vs. Formulas]].
*'''Surgical Excision''' - Interactions that would break the game should be removed without affecting related mechanics that have not yet been shown to be broken. Doing so would hinder the creative toolbox feel of the systems. So Pyro can still jump mid-air.
*'''Practical Verisimilitude''' - Units should feel like they are free to use their abilities in ways that make sense within the game world as it is presented. But units with no restrictions can be told to do very stupid things, so applications with low utility and a high risk of misuse are restricted. So units can jump into the sea, but not onto steep terrain.

Of course, we also saw a few ways to use Quant's Rule and Not Fighting The UI, but they are going to show up everywhere and already have their own articles. Perhaps it is time to start a glossary.

Cold Takes/16 - Aim and Fire

2024-10-24T02:58:43Z

RandomX: Removed paragraph from of list.

{{blog post||10 Aug 2024}}

It is finally time to talk about weapons, starting with how they are fired. The weapon design space is huge, thanks to [[Cold Takes/6 - Physics vs. Formulas|projectile physics]], and we put it to good use. But such freedom is a double-edged sword, since much of the full design space contains frustrating or incomprehensible mechanics. There are interesting games in this space, but Zero-K is first and foremost a strategy game, which means it needs to be stable and predictable enough to reward planning. So, to combat the full freedom of physics, we installed a few guard rails around weapon design; a loose set of rules that, if followed, limit how badly a weapon can break the game.

There are rules for many aspects of weapon design, but those around aiming and firing are some of the most important. The rules consider the following three aspects of our design goals.
*'''Intelligence''' - Aiming and firing are just abilities, and units should be good at [[Cold Takes/10 - The Smartest Unit in Zero-K|using their abilities]].
*'''Predictability''' - Players should be able to learn how units aim and what causes them to fire.
*'''Verisimilitude''' - Weapons should feel like they can be used in ways that make sense within the observable fiction of the game world, rather than just being a bundle of arbitrary mechanics.
As you might have guessed, projectile physics causes most of the conflicts between these goals. This specific set of problems is mostly limited to [[Cold Takes/1 - Why Zero-K|descendants of Total Annihilation]], since projectiles have a minor role in other types of games. The standard RTS projectile is a animation and a short delay between firing and dealing damage, since they are guaranteed to hit their target, and only their target (unless something unusual happens, such as death or teleportation). This limits just how stupidly units might misuse a weapon, and it allows weapon fire to be quite predictable.

[[File:TA vs SC firing.png]]

Total Annihilation probably used projectile physics to enhance verisimilitude, but I would disagree that this means other games inherently lack it. Every RTS simplifies many aspects of reality, and simplified projectiles are quite popular. How closely a simulation hews to reality is only loosely related to the experience of a reasonably consistent and believable game world. There are, of course, many players that seek out strict realism, but Zero-K does not simulate projectiles to be realistic. We use physics to make intricate, yet fundamentally simple, mechanics that reward intuition and creativity. But I digress, physics generally seems to cause problems for the goals above, rather than solve them.

Physical projectiles are hard to use. You shoot at the enemy, but then the enemy moves and the projectile hits empty ground. So you shoot where the enemy is going to be, but they dodge the other way, or you miss due to innate weapon spread. Units do a decent job at leading their shots, but many still miss. This makes deciding when to shoot of utmost importance, but this decision has to be quick, which risks making it unpredictable.

[[File:UI Design Units Using Abilities.png|thumb|upright=2]]

To make matters worse, the sense of verisimilitude subscribed to by Zero-K says that, ideally, weapons only provide two [[Cold Takes/3 - Fight your opponent, not the UI|in-world abilities]]:
*Change where the weapon is aiming.
*Fire the weapon.
In other words, we think of units as having the same basic abilities as a player in a first person shooter. In practice the implementation does not go that far, but we do at least let units blindly fire at the ground, since a cloaked bomb might be there. But even this limited ability means that, in theory, players could manually control every shot, which raises the spectre of [[Cold Takes/3 - Fight your opponent, not the UI|fighting the UI]]. So units have to be smart enough for players to not need to resort to manual control.

We could write some whizz-bang first person shooter-level AI, but then battles would amount to little more than watching units careen around the screen. This brings us back to predictability, so perhaps intelligence and predictability are fundamentally opposed. Worry not, the deadlock can be broken by imposing limitations upon weapons that are designed to make them simpler, so that units can be reasonably smart without breaking the "intelligence budget" of predictability. These limitations tend to be quite gamey, beyond the realm of pure physics, which causes trade-offs with verisimilitude.

[[File:ZK FPS.png]]

Consider the ubiquitous range ring and its implications for homing missiles. A Fencer can only fire missiles at enemies within a circle around itself, but an enemy that dances just out of this circle will still be hit, which is a bit weird. What happens if we let just the goals argue it out?

;Verisimilitude:
:That's ridiculous! The missile can demonstrably hit units beyond its arbitrary "range". Fencer should be firing in more situations, at everything that it can physically hit.
;Intelligence:
:Hmm... sounds exploitable, we don't want to fire at things barely within physical range. Borderline targets could (and should) just step back and let the missile run out of fuel before impact.
;Predictability:
:We could just only let missiles fire at structures, not units. Those are sure to stay still.
;Verisimilitude:
:That's super arbitrary!
;Intelligence:
:How about we use the target's max speed, accounting for slow and EMP, hill climbing, facing, angular velocity....
;Performance:
:uhh...
;Predictability:
:And how is anyone meant to know which combination of factors will or will not result in a Fencer firing a missile?

At this point we might placate verisimilitude with some mumbling about "missile lock range", but background lore is no match for what players can observe ingame. Besides, we have many ballistic weapons that could also shoot a bit beyond their range ring, and this cannot be explained by any sort of "missile lock". So the the fact is that verisimilitude lost this battle, and the best we can do is make these situations as simple and consistent as possible.

[[File:Fencers long range.png]]

The verisimilitude of Zero-K demands that units can do everything that they look like they are capable of, predictability demands whatever is simplest to communicate to players, and intelligence only cares that the resulting ability is hard to screw up. Designing a weapon with these constraints in mind looks a bit like this:
*Imagine the ideal form of the weapon, packed full of verisimilitude. A Glaive holds a gun in its hands. It can actuate its arms in any direction and pull the trigger at any time. It is a real robot.
*Next consider the proper use of the weapon. Should Glaives spend their time shooting wildly into the sky? Probably not, unless an enemy is flying overhead.
*Then impose as many behavioural or mechanical limitations as you like, provided that you only cull the stupid or pointless ways that the ideal weapon might have been used. These should help the unit [[Cold Takes/10 - The Smartest Unit in Zero-K|avoid being stupid]]. Shooting into the sky is almost always pointless, so Glaives only do it when there is an enemy flying overhead.
*Finally, add a small set of standard limitations, such as range rings. Consistency is key here, since the goal is predictability, and arbitrary limitations hurt verisimilitude the most.

In practise, the process is not as simple as working through four steps. Most limitations affects all three aspects simultaneously, and sometimes you need to revise the ideal version of the weapon to make the downstream implementation workable. It is also possible to start at the implementation, then work backwards to figure out what sort of ideal weapon would result in it.

One of the most important corollaries of the process is that weapon behaviour cannot depend on the existence of a target. This is known as the No Void Ray rule, as it was developed back when Starcraft 2 had a unit that gained damage the longer it fired. The unit was redesigned in the first expansion, probably because shooting your own stuff is allowed in Starcraft, but incentivising players to do it looked a bit silly. In any case, Void Ray would not even make it into Zero-K, since there would be nothing stopping it shooting into the sky when idle. Maintaining its damage bonus is smart, so we could not in good conscience prevent it from doing so. This would make the mechanic pointless, so we would avoid adding it in the first place.

[[File:Smarter Mace.png]]

The same rule applies to lock-on mechanics, or mechanics that penalise a unit for switching targets. A weapon shooting down a line of enemies should not care which unit is "aiming at", since it all involves aiming in the same direction. Any mechanical distinction would drag the interface abstraction of "targeting" into the realm of the game world. There should be no "best command" among those that cause the unit to aim and fire in the same direction. Commands are meant to help the player manipulate the game world, not be themselves be something that require optimisation.

There are ways around the No Void Ray rule. For example, the weapon could apply an escalating status effect on the target that causes the target to take more damage from that type of weapon. This would look a bit like a Void Ray, and even solves the problem of charging by shooting at your own stuff. However, this particular mechanic would be discouraged by [[Cold Takes/6 - Physics vs. Formulas|Physics vs. Formulas]], but in general there are often ways to make a design work within the weapon design guidelines.

Perhaps it is best to think of the weapon design rules as a set of guarantees, rather than a set of restrictions. Working within the rules keeps Zero-K consistent and delineates a relatively safe part of design space. These restrictions can aid creativity, and not only via the usual refrain, but because the safety guarantees free up brainpower that would otherwise be spent making sure that an idea does not completely break the game. For example, the rules inherently disallow designs that incentivises players to shoot at their own base. So the rules can be bent, but more care is required, because the rest of the game is built on their assumptions.

[[File:Picky AA.png|center]]

Anti-air weapons are the most blatant violators of idea that weapons can be fired in any direction. Being so blatant is great actually, since a large and well-defined exception feels much less arbitrary. Every weapon falls into one of the following categories.
*Weapons that can only shoot at aicraft. Units with these weapons have "Anti-Air" in their two-word role description.
*All other weapons. These weapons shoot at aircraft if they have a decent chance of hitting. Melee weapons can and do hit planes, when the wielder is thrown high enough.

We could have avoided creating the special Anti-Air category. One approach would be to make aircraft significantly slower or flimsier, to allow their best counters to be weak enough to hit ground as well. Unfortunately this would make air units more like ground units, or just weaker overall, violating [[Cold Takes/2 - Quant's Rule|Quant's Rule]]. We also considered giving anti-air weapons upwards-facing firing arcs, to allow them to shoot into the sky without hitting the ground. This has poor implications for predictability, as an inverted cone would give anti-air variable range depending on terrain and cruise altitude, as well as make for great artillery against cliffs. An inverted cone also just kick the can down the road, as it raises the question of why this amazing weapon cannot be built at an angle.

None of the alternatives to Anti-Air were as good as defining a simple category that gives air the freedom to be powerful and different. That said, most games with air have Anti-Air, so perhaps the more interesting part of Zero-K is the lack of strict Anti-Ground. This choice is a type of design minimalism, we started with projectile physics and then added as few mechanics on top as seemed necessary. We could have widespread Anti-Ground, either as a targeting category, or just by making planes fly so fast and high that nothing but Anti-Air could hit them, but the game works fine as-is.

Truth be told, ground units shooting at planes is a feature, not a bug. The goal is not realism, the goal is the feeling of a fairly consistent world, and we like the extra interactions between different parts of the game. In a sense we picked our flavour of verisimilitude <em>because</em> we like where we end up when taken to its logical conclusion. But now it feels like this article is about to fold back on on itself. Just remember, for future articles or discussion, that Zero-K units are generally allowed to aim their weapons and fire at whatever they want, provided they agree to avoid using this freedom to do anything too pointless or stupid.

Factory Production

2024-10-17T01:55:23Z

RandomX:

== Unit Queue ==
Factories produce units in a queue. When clicking on units, they are normally added to the end of the queue. They can be set to loop production with the [[Unit states#Repeat|Repeat Command]]. This will cause the factory to produce the same queue endlessly.

== Production Modifiers ==
{|
|{{Command Panel UI Button|unitpic=cloakcon|Conjurer
|frame=Fac
|hotkey=Q
|price=120
|queued=1}}
|{{Command Panel UI Button|unitpic=cloakraid|Glaive
|frame=Mobile
|hotkey=W
|price=65
|queued=20}}
|{{Command Panel UI Button|unitpic=cloakskirm|Ronin
|frame=Mobile
|hotkey=E
|price=90
|queued=15}}
|}
Left-clicking (or using the unit's hotkey) will add one unit to the queue, and right-clicking will remove one unit.

Hold {{key press|Shift}} to add/remove 5 units to the queue.

Hold {{key press|Ctrl}} to add/remove 20 units to the queue.

Hold {{key combo|Shift|Ctrl}} to add/remove 100 units to the queue.

Hold {{key press|Alt}} to place the clicked unit next in the queue. Factories in loop production mode do not repeat production of units queued with {{key press|Alt}}.

== Queue Manipulation ==
{|
|{{Command Panel UI Button|unitpic=cloakraid|Glaive
|frame=Mobile
|queued=1
|progress=50}}
|{{Command Panel UI Button|unitpic=cloakskirm|Ronin
|frame=Mobile
|queued=3
}}
|{{Command Panel UI Button|unitpic=cloakcon|Conjurer
|frame=Fac
|queued=5
}}
|{{Command Panel UI Button|unitpic=cloakjammer|Iris
|frame=Misc
|queued=1
}}
|}
The production queue is shown in the third row of the factory Units tab. Each item in the queue is a block of units of the same type.

Blocks can be modified by clicking on them with the above-mentioned modifier keys to adjust the number of units in the block.

Blocks can be left-clicked and dragged to change their position in the queue.

{{key press|Alt}}-click a block to move it to the front of the queue. Any metal/energy used on whatever was being produced prior to the click will be lost.

{{Navbox commands}}

[[Category:Commands|#]]

Buildings

2024-10-17T01:52:37Z

RandomX:

The '''Buildings''' of Zero-K are the backbone of your strategy. Build [[Metal Extractor|Metal Extractors]] and [[Energy]] producers to propel your economy, build [[Factory Production|Factories]] and [[Caretaker]]s to produce an army, build defensive and intel structures to protect yourself from your opponents' armies, and build superweapons to end the game in spectacular fashion.

Properties shared by most or all buildings in Zero-K include:
* They cost the same amount of [[Metal]] and [[Energy]].
* Once a [[#Placing Nanoframes|nanoframe]] is placed, the ground beneath the building cannot be [[terraform]]ed until the building is destroyed.

== Building placement and construction ==
After selecting a building from the build menu, instead of simply left-clicking to place it, some modifiers can be used during building placement for additional control.

=== Command queuing ===
The normal command queuing options apply:
* Hold {{key press|Shift}} to append orders to the end of the queue.
* Hold {{key press|Space}} to insert orders at the front of the queue. This will come before the current task if there is one.
* Hold {{key combo|Shift|Space}} to insert orders between existing orders. The order will try to be inserted between two nearby orders such that the constructor will minimize the added movement distance.

=== Build Facing ===
When placing factories or other structures, their orientation can be selected by clicking and dragging, rotated in 90 degree steps using {{key press|[}} and {{key press|]}}, or rotated clockwise in 90 degree steps by pressing the {{key press|R}} key.

=== Terraforming ===
{{See|Terraform#Level{{!}}Level Commands}}
[[Terraform#Terraform Types|Terraforming]] can be queued before construction to put a structure on a spire or in a hole. There are various ways to issue this command depending on your advanced settings in [[Ingame Menu#Interface|<samp>Interface</samp>]] → [[Ingame Menu#Building Placement|<samp>Building Placement</samp>]].

Height selection mode can be entered as follows:
* By holding {{key press|Alt}} and using the mouse wheel during structure placement.
* By pressing {{key press|B}} during structure placement. Press {{key press|C}} or {{key press|V}} to adjust the height.
* If you have enabled '''Terraform by holding mouse click''' in your settings, by holding down the '''left mouse button''' during placement (keeping the cursor stationary). Once the terraform mode has been entered, the mouse can be moved up and down to adjust the elevation. Another left click finalizes the command.

After choosing the terraform height, click to place the structure as usual to issue the terraform and construction command. Structure terraform does not support multiple structure placement, but it does support queuing and insertion with {{key press|Space}} and {{key press|Shift}}.

An existing building can be surrounded by a terraformed wall by selecting the terraform command from the Special tab (hotkeys {{key press|V}}, then {{key press|X}}), then holding down {{key press|Ctrl}} and clicking on the building. Release {{key press|Ctrl}} and move the mouse upwards to set the height of the wall.

=== Line and Rectangular Grid ===
* Hold {{key press|Shift}} while dragging the mouse to place a line of structures.
* Hold {{key combo|Shift|Ctrl}} to drag a line of structures in the 4 cardinal directions. If holding the mouse over a building, it will surround that building with the selected structure.
* Hold {{key combo|Shift|Alt}} to drag a rectangular grid of structures.
* Hold {{key combo|Shift|Ctrl|Alt}} to drag a hollow box of structures.

The spacing between the individual buildings can be adjusted by pressing {{key press|X}} or {{key press|Z}}.

=== Surrounding an existing building ===
By holding {{key combo|Ctrl|Shift}} during placement, an existing building can be surrounded with the selected building. For example, a fragile and expensive [[Fusion Reactor]] can be surrounded by sturdy and cheap [[Solar Collector]]s by first building the Fusion Reactor, then selecting the Solar Collector from the build menu, holding down {{key combo|Ctrl|Shift}} and clicking on the Fusion Reactor.

=== Placing Nanoframes ===
Holding {{key press|Q}} while placing structures will place only the framework ''(nanoframe)'', which will let the structure be completed later. This is often used when there are Caretakers nearby that can finish the construction on their own.

=== Metal Extractors ===
There is a specialized [[Area Mex Command]] to place Metal Extractors in an area and optionally surround them with power generators at the same time.

{{Navbox buildings}}

[[Category:Buildings|#]]

Main Page

2024-10-17T01:47:43Z

RandomX:

[[File:zk_logo.png|center|link=]]
<div style="font-size:200%;text-align:center;margin:auto">Welcome to the Zero-K Wiki</div>
----

{{TOC right}}

This is the official wiki for the free open-source <abbr title="real-time strategy">RTS</abbr> game '''[//zero-k.info Zero-K]'''.
* If you're new to the game, consult the '''[[Manual]]''' for helpful information on how to get started.
* There is a [https://discord.gg/aab63Vt Discord server] which is linked to the game chat.
* You can log in to the wiki using your Zero-K account and password, or your Steam account. (Please use your Zero-K username if logging in with Steam, to avoid naming conflicts.)
* The wiki is still a work in progress. Some articles may not be up to date. Find out how you can help [[Editing Help|here]]!

== Overview ==
{| style="margin:auto"

|
; Game info
: [[Manual]]
: [[Units]]
: [[Buildings]]
: [[Commander]]
: [[Unit commands|Unit Commands]]

|
; Community
: [https://discord.gg/aab63Vt Discord]
: [https://zero-k.info/Forum Forum]
: [https://zero-k.info/Ladders Ladders]
: [https://steamcommunity.com/app/334920 Steam]
: [https://www.twitch.tv/directory/game/Zero-K Twitch]

|}

=== Manual ===
{{Navbox manual}}

=== Units ===
{{Navbox units}}

=== Buildings ===
{{Navbox buildings}}

=== Commands ===
{{Navbox commands}}

=== Planet Wars ===
{{Navbox planetwars}}

[[Category:Units|#]][[Category:Buildings|#]][[Category:Commands|#]]

Units

2024-10-17T01:46:42Z

RandomX:

The '''Units''' of Zero-K are the tools you will use to execute your strategies and defeat your opponents.

Use your [[Commander]] and [[Unit classes#Constructor|Constructors]] to build up your base and economy, [[Unit classes#Raider|Raider]] and [[Unit classes#Assault|Assault]] units to attack at close range, [[Unit classes#Skirmisher|Skirmishers]] and [[Unit classes#Artillery|Artillery]] to engage at long range, and [[Unit classes#Riot|Riots]] to defend in close quarters.

{| class="wikitable"
! style="text-align: center;" | [[Cloakbot Factory|{{unit image|factorycloak|Cloakbot Factory}}<br>Cloakbots]]
! style="text-align: center;" | [[Shieldbot Factory|{{unit image|factoryshield|Shieldbot Factory}}<br>Shieldbots]]
! style="text-align: center;" | [[Rover Assembly|{{unit image|factoryveh|Rover Assembly}}<br>Rovers]]
! style="text-align: center;" | [[Hovercraft Platform|{{unit image|factoryhover|Hovercraft Platform}}<br>Hovercraft]]
! style="text-align: center;" | [[Gunship Plant|{{unit image|factorygunship|Gunship Plant}}<br>Gunships]]
! style="text-align: center;" | [[Airplane Plant|{{unit image|factoryplane|Airplane Plant}}<br>Airplanes]]
|-
| style="text-align: center; font-weight:bold;" | [[Spider Factory|{{unit image|factoryspider|Spider Factory}}<br>Spiders]]
| style="text-align: center; font-weight:bold;" | [[Jumpbot Factory|{{unit image|factoryjump|Jumpbot Factory}}<br>Jumpbots]]
| style="text-align: center; font-weight:bold;" | [[Tank Foundry|{{unit image|factorytank|Tank Foundry}}<br>Tanks]]
| style="text-align: center; font-weight:bold;" | [[Amphbot Factory|{{unit image|factoryamph|Amphbot Factory}}<br>Amphbots]]
| style="text-align: center; font-weight:bold;" | [[Shipyard|{{unit image|factoryship|Shipyard}}<br>Ships]]
| style="text-align: center; font-weight:bold;" | [[Strider Hub|{{unit image|striderhub|Strider Hub}}<br>Striders]]
|}

Properties shared by most or all units in Zero-K include:

* They cost the same amount of [[Metal]] and [[Energy]].
* Most units are produced by a factory, and autonomous Drones are built by their parent.

Useful information on units:
* [[Unit classes]]
* [[Map icons|Unit map icons]]
* [[Weapon classes]]
* [[Internal unit names]]

==Unit chassis movement traits==

The movement traits of different unit chassis can be a very important factor when choosing which factory to build at the start of a game. Factors such as the terrain of the map as well as the map size can influence this decision. For instance, lots of deep water may call for a factory with lots of amphibious or airborne options, while a map with mostly somewhat steep terrain may call for bots, spiders or airborne options.

===Brief overview===

;Legged chassis
:<div style="float:left;padding-right:0.5em;margin:0">{{unit image|cloakraid}}[[File:Angle_54.png|64px|link=]]</div> ''Bots:'' Non-climbing legged units (generally having two or four legs) tend to have great turn rates and can typically traverse somewhat steep terrain. Some bots are [[Submersion|amphibious]], notably [[Amphbot Factory|amphbots]] and certain [[Strider Hub|strider bots]]. Many of the bots from the [[Jumpbot Factory]] and a few other bots can [[Jump Command|jump]], which can be useful for traversing terrain as well as in combat.{{clear}}
:<div style="float:left;padding-right:0.5em;margin:0">{{unit image|cloakbomb}}[[File:Angle_90.png|64px|link=]]</div>''All-terrain:'' Climbing legged units (generally having four or more legs) can climb and traverse any land terrain, including practically vertical hills and cliffs, but tend to have poor speed. They include [[Spider Factory|all spider factory units]] and various other units such as the [[Scorpion|Scorpion strider]].{{clear}}
;Wheeled, tracked and hovercraft chassis
:<div style="float:left;padding-right:0.5em;margin:0">{{unit image|vehraid}}[[File:Angle_27.png|64px|link=]]</div> [[Rover Assembly|Rovers]] tend to have good or great speed, medium or poor turn rates, and prefer flat terrain (slightly steep terrain slows them).{{clear}}
:<div style="float:left;padding-right:0.5em;margin:0">{{unit image|tankassault}}[[File:Angle_27.png|64px|link=]]</div> [[Tank Foundry|Tanks]] are like rovers, except their speed and turn rates are typically worse.{{clear}}
:<div style="float:left;padding-right:0.5em;margin:0">{{unit image|hoverraid}}[[File:Angle_27.png|64px|link=]]</div> [[Hovercraft Platform|Hovercraft]] are like rovers, except they can traverse water easily.{{clear}}
;Airborne chassis
:{{unit image|bomberriot|style=float:left;padding-right:0.5em}} Airplanes fly and tend to have excellent speed. Their movement resembles real-life planes.{{clear}}
:{{unit image|gunshipraid|style=float:left;padding-right:0.5em}} Gunships hover above the ground; their movement resembles helicopters.{{clear}}
;Naval chassis
:{{unit image|shipscout|style=float:left;padding-right:0.5em}} Ships float on the sea surface. Smaller ships are built in the [[Shipyard]], while carriers and battleships are built at the [[Strider Hub]].{{clear}}
:{{unit image|subraider|style=float:left;padding-right:0.5em}} Submarines [[Submersion|dive underwater]], which gives them protection from radar and weaponry (but they cannot surface).{{clear}}

There are also various kinds of indirect movement, such as [[Transportation|transport gunships]], [[Teleportation|teleportation]], throwing, gravity projection, etc. And terrain can be [[Terraform|terraformed]] by construction units, or flattened by attacking with certain units such as the [[Tremor]] artillery unit, which can help enable units such as tanks to cross terrain that would otherwise be impassable for them.

The [[Newbie Guide#Map views|pathing map overlay]] when a unit is selected is useful for viewing where a selected unit can and cannot go.

{{Navbox units}}

{{Navbox buildings}}

[[Category:Units|#]][[Category:Buildings|#]]

Unit commands

2024-10-16T17:53:59Z

RandomX: Using local images in the table.

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) [[File:Move.png|none|32px|link=Move Command]]
|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) [[File:Fight.png|none|32px|link=Attack Move Command]]
|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) [[File:Patrol.png|none|32px|link=Patrol Command]]
|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) [[File:Attack.png|none|32px|link=Force Fire Command]]
|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) [[File:Settarget.png|none|32px|link=Set Target Command]]
|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) [[File:Guard.png|none|32px|link=Guard Command]]
|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) [[File:Repair.png|none|32px|link=Repair Command]]
|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).
|For area only. Persist the area even when no valid targets inside while only repairing live units.
|-
|[[Area Mex Command|Area Mex]] (W) [[File:mex.png|none|32px|link=Area Mex Command]]
|Build a mex at given spot||Queue mexes across the area.
|Surround each mex in the area with 2 solars. Works on already-built mexes. If a mex is underwater, 2 Tidal Generators are built instead. If on land and flat space is limited, a Wind Generator will be substituted where a Solar does not fit.
|As with +CTRL, except with only one generator per mex, chosen as appropriate.
|As with +CTRL, except with four generators per mex, chosen as appropriate, one on each side.
|
|-
|[[Reclaim Command|Reclaim]] (E) [[File:Reclaim.png|none|32px|link=Reclaim Command]]
|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.
|Area only. Persist the command even when no features are in the area while ignoring(or not, depending on setting) metal-less features
|-
|[[Resurrect Command|Resurrect]] (T) [[File:Resurrect.png|none|32px|link=Resurrect Command]]
|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. Ignores partially reclaimed wrecks.
|Area only. Persist the command even when no resurrectables are in the area. Resurrects partially reclaimed wrecks.
|-
|}

== 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]]
* [[Economy Guide#Reserving resources|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}}

[[Category:Commands|#]]

Main Page

2024-10-16T16:35:31Z

RandomX: fix spacing

Main Page

2024-10-16T16:22:05Z

RandomX: Attempt to move this page to the top of units and commands category list.

[[File:zk_logo.png|center|link=]]
<div style="font-size:200%;text-align:center;margin:auto">Welcome to the Zero-K Wiki</div>
----

{{TOC right}}

This is the official wiki for the free open-source <abbr title="real-time strategy">RTS</abbr> game '''[//zero-k.info Zero-K]'''.
* If you're new to the game, consult the '''[[Manual]]''' for helpful information on how to get started.
* There is a [https://discord.gg/aab63Vt Discord server] which is linked to the game chat.
* You can log in to the wiki using your Zero-K account and password, or your Steam account. (Please use your Zero-K username if logging in with Steam, to avoid naming conflicts.)
* The wiki is still a work in progress. Some articles may not be up to date. Find out how you can help [[Editing Help|here]]!

== Overview ==
{| style="margin:auto"

|
; Game info
: [[Manual]]
: [[Units]]
: [[Buildings]]
: [[Commander]]
: [[Unit commands|Unit Commands]]

|
; Community
: [https://discord.gg/aab63Vt Discord]
: [https://zero-k.info/Forum Forum]
: [https://zero-k.info/Ladders Ladders]
: [https://steamcommunity.com/app/334920 Steam]
: [https://www.twitch.tv/directory/game/Zero-K Twitch]

|}

=== Manual ===
{{Navbox manual}}

=== Units ===
{{Navbox units}}[[Category:Units|#]]

=== Buildings ===
{{Navbox buildings}}

=== Commands ===
{{Navbox commands}}[[Category:Commands|#]]

=== Planet Wars ===
{{Navbox planetwars}}

Units

2024-10-16T16:15:56Z

RandomX: Sort ahead of actual units.

Badger

2024-10-16T15:19:47Z

RandomX: Added Claw link to the text + some minor text fixing.

The '''{{PAGENAME}}''' is an artillery minelayer rover from the [[Rover Assembly]].{{Autoinfobox zkunit
| defname = veharty
}}==Description==
The {{PAGENAME}} lays mines—which are fairly effective, but have a limited lifespan—from a distance (rather haphazardly). The {{PAGENAME}} outranges most defenses comfortably, but is lightly armored and cannot flee easily, so keep it screened with friendly units, possibly assisted by its own mines.

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

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

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

To quickly order multiple {{PAGENAME}}s to create a minefield that stretches from place to place, hold down the {{key press|Alt}} key and drag a line from one spot to the other while giving the {{PAGENAME}}s a force-fire order.

{{Navbox units}}

Template:Infobox zkweapon

2024-10-16T14:58:03Z

RandomX: I don't think Shield Damage is in %. Revert if this is wrong.

<noinclude>[[Category:ZK Infoboxes]]</noinclude>
{{ infobox | subbox = yes
| abovestyle = background:#bbb; color:#000
| above =
| headerstyle = color:#000; {{#if: {{{specialheadercolour|}}} | {{{specialheadercolour|}}} | {{#if: {{{empdamage|}}} | background:#bbf; | {{#if: {{{slowdamage|}}} | background:#fbf; | {{#if: {{{disarmdamage|}}} | background:#ffb; | {{#if: {{{afterburn|}}} | background:#fbb; | background:#bbb; }} }} }} }} }} {{#if: {{{manualfire|}}} | border: 2px solid red; | }} {{#if: {{{antiair|}}} | border: 2px dashed #44b; | }} {{#if: {{{wateronly|}}} | border: 2px solid blue; | }}
| labelstyle =
| datastyle = text-align: center;

| header1 = {{{name}}}

| label11 = Damage
| data11 = {{{damage|0}}}
| label12 = <span style="color: #bbf">EMP Damage</span>
| data12 = {{#if: {{{empdamage|}}} | <span style="color: #bbf">{{{empdamage|}}}</span> | }}
| label13 = <span style="color: #fbf">Slow Damage</span>
| data13 = {{#if: {{{slowdamage|}}} | <span style="color: #fbf">{{{slowdamage|}}}</span> | }}
| label14 = <span style="color: #ffb">Disarm Damage</span>
| data14 = {{#if: {{{disarmdamage|}}} | <span style="color: #ffb">{{{disarmdamage|}}}</span> | }}

| label21 = Reload Time (s)
| data21 = {{{reloadtime|}}}
| label22 = Damage per Second
| data22 = {{ #if: {{{dps|}}}{{{empdps|}}}{{{slowdps|}}}{{{disarmdps|}}} | {{{dps|0}}} | }} {{#if: {{{empdps|}}} | + <span style="color: #bbf">{{{empdps|}}}</span> | }} {{#if: {{{slowdps|}}} | + <span style="color: #fbf">{{{slowdps|}}}</span> | }} {{#if: {{{disarmdps|}}} | + <span style="color: #ffb">{{{disarmdps|}}}</span> | }}
| label23 = Shield Damage
| data23 = {{{shielddamage|}}}
| label24 = <span style="color: #fbb">Afterburn (s)</span>
| data24 = {{ #if: {{{afterburn|}}} | <span style="color: #fbb">{{{afterburn|}}} ({{{afterburndps|15}}} DPS)</span> | }}
| label25 = Max Stun Time (s)
| data25 = {{{stuntime|}}}
| label26 = Range (elmo)
| data26 = {{{range|}}}
| label27 = Area of Effect (elmo)
| data27 = {{{aoe|}}}
| label28 = Projectile Speed (elmo/s)
| data28 = {{{projectilespeed|}}}

| label41 = Inaccuracy (deg)
| data41 = {{{inaccuracy|}}}

| label42 = Homing (deg/s)
| data42 = {{{homing|}}}
| label43 = Wobbly (maximum, deg/s)
| data43 = {{{wobbly|}}}
| label44 = Arcing shot (deg)
| data44 = {{{arcing|}}}
| label45 = Firing arc (deg)
| data45 = {{{firearc|}}}

| label46 = Burst Time (s)
| data46 = {{{bursttime|}}}

| label81 = {{{customlabel1|}}}
| data81 = {{{customdata1|}}}
| label82 = {{{customlabel2|}}}
| data82 = {{{customdata2|}}}
| label83 = {{{customlabel3|}}}
| data83 = {{{customdata3|}}}
| label84 = {{{customlabel4|}}}
| data84 = {{{customdata4|}}}
| label85 = {{{customlabel5|}}}
| data85 = {{{customdata5|}}}
| label86 = {{{customlabel6|}}}
| data86 = {{{customdata6|}}}
| label87 = {{{customlabel7|}}}
| data87 = {{{customdata7|}}}
| label88 = {{{customlabel8|}}}
| data88 = {{{customdata8|}}}
| label89 = {{{customlabel9|}}}
| data89 = {{{customdata9|}}}

| data91 = {{{special1|}}}
| data92 = {{{special2|}}}
| data93 = {{{special3|}}}
| data94 = {{{special4|}}}
| data95 = {{{special5|}}}
| data96 = {{{special6|}}}
| data97 = {{{special7|}}}
| data98 = {{{special8|}}}
| data99 = {{{special9|}}}
}}
<noinclude>
{{Documentation}}

</noinclude>

Template:Purge

2024-10-16T03:31:16Z

RandomX: oops...

{{#ifeq:{{#invoke:String|find|{{filepath:Selection.png}}|test.zero}}|0||
{{ombox|type=content|text=The images and links on this page may be broken at the moment. The cache on this page points to the '''test wiki'''.

Please [{{#invoke:String|replace|{{canonicalurl:{{PAGENAME}}|action=purge}}|test.||1}} purge the cache] to try to restore images and fix those links.
<small>This will work ''only if'' the page is '''not''' on the test server (where this box should appear for now even when cache purging is not needed), which may lack the actual images. This page ''thinks'' that it resides on '''{{SERVERNAME}}''' right now.<small>
}}
|}}<noinclude>
{{documentation}}

</noinclude>

Template:Purge

2024-10-16T03:29:53Z

RandomX: It's worse. Need to manually remove "test." from the url.

{{#ifeq:{{#invoke:String|find|{{filepath:Selection.png}}|test.zero}}|0||
{{ombox|type=content|text=The images and links on this page may be broken at the moment. The cache on this page points to the '''test wiki'''.

Please [{{#invoke:String|replace|{{canonicalurl:{{PAGENAME}}|action=purge}}|test.|1}} purge the cache] to try to restore images and fix those links.
<small>This will work ''only if'' the page is '''not''' on the test server (where this box should appear for now even when cache purging is not needed), which may lack the actual images. This page ''thinks'' that it resides on '''{{SERVERNAME}}''' right now.<small>
}}
|}}<noinclude>
{{documentation}}

</noinclude>

Template:Purge

2024-10-16T03:20:38Z

RandomX: Use an image that actually exists on the test wiki. Break the test server a little. Eventually this will need to be fixed, but it's the best I can do for now. A little debug/explanation text in small print...

{{#ifeq:{{#invoke:String|find|{{filepath:Selection.png}}|test.zero}}|0||
{{ombox|type=content|text=The images and links on this page may be broken at the moment. The cache on this page points to the '''test wiki'''.

Please [{{canonicalurl:{{PAGENAME}}|action=purge}} purge the cache] to try to restore images and fix those links.
<small>This will work only if the page is not on the test server (where this box should appear for now even when cache purging is not needed), which may lack the actual images. This page ''thinks'' that it resides on '''{{SERVERNAME}}''' right now.<small>
}}
|}}<noinclude>
{{documentation}}

</noinclude>

Template:Blog post

2024-10-15T05:56:46Z

RandomX: Added purge tempate. Temporarily, hopefully.

{{Purge}}{{#ifexist:File:{{#titleparts:{{PAGENAME}}|1|-1}}.jpg|
<div style="position:relative;overflow:hidden;padding-top:24vw">
<div style="position:absolute;right:0;top:0;z-index:-1;width:100%;height:100%;overflow:hidden"><img alt="" src="{{filepath:{{#titleparts:{{PAGENAME}}|1|-1}}.jpg}}" style="height:auto;width:auto;max-height:100%;max-width:100%;border:thin solid transparent;border-radius:1em"></div>
}}<div style="text-shadow:1px 1px 5px #666,1px 1px 1px #333,-1px -1px 1px #993">
={{#if:{{{1|}}}|{{{1}}}|{{padright:|{{#expr:{{#invoke:String|len|{{#titleparts:{{PAGENAME}}|1|-2}}}} - 1}}|{{#titleparts:{{PAGENAME}}|1|-2}} }} #{{#titleparts:{{PAGENAME}}|1|-1}} }}=
{{DISPLAYTITLE:<span style="position:absolute;clip:rect(1px 1px 1px 1px);clip:rect(1px, 1px, 1px, 1px)">{{FULLPAGENAME}}</span>}}
{{#if:{{{2|}}}|
Posted {{#formatdate:{{{2|{{#timel:d M Y|now}}}}}|mdy}}
|♥
}}
{{#ifexist:File:{{#titleparts:{{PAGENAME}}|1|-1}}.jpg|
<div style="visibility:hidden;padding:0;margin:0;border:0;position:absolute;top:0;left:0;z-index:-2">[[File:{{#invoke:String|replace|{{#titleparts:{{PAGENAME}}|1|-1}}|%2C|,}}.jpg|1px|alt=|link=]]</div></div>
}}</div>

{{clear}}
__NOEDITSECTION__
[[Category:{{{3|{{#titleparts:{{PAGENAME}}|1|-2}}}}}|C{{padleft:{{#invoke:String|len|{{#invoke:String|match|{{#titleparts:{{PAGENAME}}|1|-1}}|%d+|plain=false|nomatch=0|ignore_errors=true}}}}|3}}]]