Commander Wars - User contributions [en]

Main Page

2025-09-24T18:14:36Z

MrDuck557: Added Modded CO List to main page

<strong>Welcome to Commander Wars Wiki</strong>

The project is separated in three parts.

*The core engine written in C++ using oxygine as a render and input engine and qt as an interpreter, language support etc. framework
*The resources folder containing the javascript default data and images and sounds or music
*The mods folder containing mods for the core engine

Consult the [https://github.com/Robosturm/Commander_Wars Github page] for bug reports, feedback and feature requests.

The releases page of the game can be found [https://github.com/Robosturm/Commander_Wars/releases here] .

This is the [[F.A.Q.]]

Join the [https://discord.gg/WKXFcXPmxz Discord Server] to discuss the game, and get more scripting help.
==Showcasing of the game==
This is a demonstration of the game capabilities, the CO powers of the [[Xanari Crew]] mod, by XnKradst<br/>
<youtube>https://www.youtube.com/watch?v=j8M-SqqOQOA </youtube>

== A custom CO card generator ==
This simple tool was created to help you [https://www.commanderwars.com/front.php generate your CO]

==Recent Pages==
{{Special:Newestpages/-/5}}

== Content Categories ==
[[:Category:Modding_tutorials|Modding tutorials]] contain scripting reference for custom COs and Units.

[[:Category:Technical| Technical guides]] contain guides intended for developers, they are technical in nature.

[[:Category:Gameplay| Gameplay]] articles are intended to help players understand the game.

[[List of Modded COs|Modded CO List]] List of custom COs created by COW Discord Community

[[:Category:Mods| Mod list]] List of Mod created by COW Discord community

[[:Category:Community Maps| Map list]] List of Map created by COW Discord community

List of Modded COs

2024-04-19T02:18:39Z

MrDuck557: Added descriptions for Balsam, Osprey, and Seargent Quackers

==List of Modded and Playable Custom COs for Commander Wars==
Last Updated: April 18th, 2024
{| class="wikitable sortable"
! scope="col" | Mod name || scope="col" | Mod Link || scope="col" | Image / Dossier
!Description|| scope="col" | Creator(s) || scope="col" |Last Updated
|-
| Aaron || [https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| || KesalahanTeknis, Marmalad || April 23rd, 2022
|-
| Agnes || [https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| || KesalahanTeknis || December 18th, 2022
|-
| Alek || [https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| || KesalahanTeknis || December 18th, 2022
|-
| Alice || [https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
| Alps|| [https://drive.google.com/file/d/1YE6nmvXAw5c7RIDWG_dLRryplgUInFtv/view?usp=sharing Standalone release]||[https://i.imgur.com/3eD8iUW.png Image]
| ||Nanoka||December 22nd, 2022
|-
|Ambrose||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
| Amy||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]|| [https://i.imgur.com/aY3v126.png Image]
| ||F.C.M.C Memories 54||February 5th, 2024
|-
|└──||[https://drive.google.com/file/d/1hYzWbfrMebRIAZQYNZWYdb8ydmmGzCIG/view?usp=sharing Standalone version]||[https://i.imgur.com/BWdMnQx.jpg Image]
| ||F.C.M.C Memories 54||October 9th, 2022
|-
|Andrea||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Aoi Kaze||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/mnRy6qu.png Image]
| || ruigio||February 5th, 2024
|-
|└──|| [https://drive.google.com/file/d/1C-1LKLSCQUxcFLx1UdISgL6OSbKdH5L4/view?usp=sharing Standalone version]||[https://i.imgur.com/KSpp2PD.png Image]
| ||ruigio || January 15th, 2023
|-
| Apothema||[https://drive.google.com/file/d/1uOPewGS05etwCSMwaDwvWUp-89289n9q/view?usp=sharing Silver Horizon (Older version)]||
| ||ChemAtDark||July 2nd, 2022
|-
| Argent||[https://drive.google.com/file/d/1xL2u2VocZoDOjKP7y8ryH8cfC632WmKo/view?usp=sharing Battalion CoW]||
| ||Hamplmann||June 20th, 2023
|-
|Bally||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis || December 18th, 2022
|-
|Balsam||[https://drive.google.com/file/d/11gROTiA0SxNHiPIGzWLcClgjS3xJfOPO/view?usp=sharing Standalone release]||
| CO with a focus on ground vehicles and movement. Perfect movement in zone and canto ensure that not a single move point is wasted. Powers convert mobility into raw power, with COP giving more attack for each tile moved and SCOP allowing units to move and attack through multiple enemies.||MrDuck557|| April 18th, 2024
|-
|Bawke||[https://drive.google.com/file/d/18-FUmQxbaMsIuzZJONUT9McDoMsBFJCh/view?usp=sharing Standalone release]||
| ||Hog||June 24th, 2023
|-
|Bernstein||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Big Derp||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Ridiculously high firepower and defense that go down as his power meter (of 15 stars) charges, and it charges at a very fast rate. Superpower dealt 5 HP of damage to all of his own units. No regular CO power.||XnKradst||March 18th, 2022
|-
|Blaze
| [https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/UTJZRcz.png Image]
| Indirect units have no minimum range, direct units can attack indirectly with powers.||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above but without the minimum range for indirect units.|| XnKradst || March 18th, 2022
|-
|Bill||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/Ozb01FD.png Image]
| || Niklas||February 5th, 2024
|-
|└──||[https://drive.google.com/file/d/1sLR2yLvN8HJKK7Snt_1fDZBvJayjzTYw/view?usp=sharing Standalone version]||[https://i.imgur.com/DS81Ryy.png Image]
| || Niklas||October 9th, 2022
|-
|Billy Gates||[https://drive.google.com/file/d/1eY3GLJqeHOBHXWcEaSEFkgXLpct_Lthq/view?usp=sharing Standalone release]||
| || K'Braid ||October 12th, 2022
|-
|Billy Gates||[https://drive.google.com/file/d/1iIAVQiJFMukT06flThtfR7aOzhZECE-J/view?usp=sharing SFW COs]||
| ||Creed||October 14th, 2022
|-
|Binah||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Boris||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Air units can pass through enemy units at all times. Powers allow them to also damage the enemy units being passed through.||XnKradst||March 18th, 2022
|-
| Braid||[https://drive.google.com/file/d/1zirDJbTfrTRJJQvHRfIU7BIeOV1lPtlR/view K'Braid's COs]||
| ||K'Braid|| March 19th, 2022
|-
|Brashim||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/2h90Eys.png Image]
| ||brasmak||February 5th, 2024
|-
|BunBun||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
| BVin||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad|| April 23rd, 2022
|-
|Cadenza||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]|| [https://i.imgur.com/wbSpiM8.png Image]
| ||MegaTank||February 5th, 2024
|-
|└──||[https://drive.google.com/file/d/1gCpDqFjIvvnbypaZDIuJ_-cMcR97zJwz/view?usp=sharing Standalone version]||[https://i.imgur.com/wqBbZfx.png Image]
| ||MegaTank || August 8th, 2022
|-
|Camber||[https://drive.google.com/file/d/1CQnuR6nRaM6wo82Ic9CroTStYxyeuhqt/view?usp=sharing Chinese Kanbei]||[https://i.imgur.com/3MA6rTx.png Image]
| ||Nin10doGMod|| October 25th, 2023
|-
|Caroline||[https://drive.google.com/file/d/1iIAVQiJFMukT06flThtfR7aOzhZECE-J/view?usp=sharing SFW COs]||
| || Creed||October 14th, 2022
|-
|Cassandra||[https://drive.google.com/file/d/1jsQbZpdcurtbJnAPRAwOVTP7S3ZpURgQ/view?usp=sharing BattleTanx COs]||
| ||Ellie|| January 30th, 2023
|-
|Cattleya||[https://drive.google.com/file/d/1Gamo6lgKgskdknL8pzU0WZCNFCjeKdVE/view?usp=sharing Standalone release]||[https://i.imgur.com/vzUC0KV.png Image]
| ||Nanoka||October 17th, 2023
|-
|Cheibriados || [https://drive.google.com/file/d/1W3fCF2HQfL0MoUk-5I4eXPWVTOhH8E14/view?usp=sharing Standalone release]||
| ||Brilliand||October 26th, 2023
|-
| Chelsen
| [https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/lCEgZYD.png Image]
| Units gain a firepower buff and a defense debuff, or the other way around, depending on their map position's "parity" (think checkerboard pattern).||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above, but with slightly different CO powers and no visual indicators.||XnKradst||March 18th, 2022
|-
|Chesed||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis || December 18th, 2022
|-
|Chris||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Cindee
| [https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/xMI9hSl.png Image]
| Units gain both firepower and defense the closer they are to her buildings. If near multiple buildings, the bonuses stack.||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Units gain firepower and defense if within 10 spaces of her HQ(s), gaining more bonuses the closer they are to the HQ(s).||XnKradst||March 18th, 2022
|-
|Clone Andy||[https://www.mediafire.com/file/li8lzzekdrobf5g/Clone_Andy.zip/file Standalone release]||[https://i.imgur.com/Ich0y1F.png Image]
| ||Nin10doGMod||September 10th, 2023
|-
|Contessa
|[https://drive.google.com/file/d/1c4-WkTxJowPlfL_4dLzddqyxi4nUA50Q/view?usp=sharing Standalone release]
|
|
|Brilliand
|April 18th, 2024
|-
|Cyphir
| [https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/wjFRlCg.png Image]
| All units can capture properties, but non-foot soldiers capture at a slower pace. Non-foot soldiers also lose defense when capturing.||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above, but with slightly different CO powers and penalties.||XnKradst||March 18th, 2022
|-
|Cyrus||[https://drive.google.com/file/d/1e5EX9cO_6rj9_8dP4F-Mz7LCSEFaKxec/view?usp=sharing Standalone release]||
| ||K'Braid||February 12th, 2022
|-
|Daehyun||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Damaskas||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis ||December 18th, 2022
|-
|Damond||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Danial||[https://drive.google.com/file/d/1zirDJbTfrTRJJQvHRfIU7BIeOV1lPtlR/view K'Braid's COs]||
| ||K'Braid||March 19th, 2022
|-
|Darjeeling||[https://drive.google.com/file/d/16BN7eoXjXVCY0gnBXAwTibinXg2TIf4V/view?usp=sharing Standalone release]||[https://i.imgur.com/1xEFvh8.png Image]
| || Namelessone|| September 15th, 2022
|-
|Dark Despair||[https://drive.google.com/file/d/1N1nU6U1g9KxFirZKBaklXCDXmgOZ_tRa/view?usp=sharing Imperial COs]||
| ||DarkDespair||December 7th, 2021
|-
|DarkusRelling||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Deckard||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Dekkar
| [https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/LfaM7ib.png Image]
| The fewer (other) units surrounding his units, the more defense they have. The fewer units surrounding the target, the more damage his units deal to them.||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Units have high firepower and defense if they are "isolated" from his other units (at least two tiles away).|| XnKradst||March 18th, 2022
|-
|Dekks||[https://drive.google.com/file/d/1yyph-Y52ByCoY3iAnkMZsv1YLhRvnMmm/view?usp=sharing Gin Co Mod]||[https://i.imgur.com/uLULGwb.png Image]
| ||gin_san ||October 24th, 2023
|-
|Dekks(Young version)||[https://drive.google.com/file/d/1yyph-Y52ByCoY3iAnkMZsv1YLhRvnMmm/view?usp=sharing Gin Co Mod]||[https://i.imgur.com/gEqgImg.png Image]
| ||gin_san||October 24th, 2023
|-
|Destin||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| All bases can build air units as long as he owns an airport somewhere on the map. Overpowered CO powers where with every attack, all enemy units of the same exact type (also belonging to the same opponent) as the target suffer collateral damage.||XnKradst||March 18th, 2022
|-
|Drac
| [https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/PhI4yi8.png Image]
| Units gain firepower for each round of ammunition and every 5 points of fuel missing from the target.||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Units start weak, but gain firepower and defense over time, capping at Day 45.||XnKradst|| March 18th, 2022
|-
|Drake / Drayke
| [https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/IVfQdD1.png Image]
| Direct units deal more damage if they attack without moving. CO powers either allow direct units to attack again after attacking (only in the same position) or drop temporary Mechs that can immediately attack without moving.||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above, but with entirely different CO powers: units with low HP deal massive damage.||XnKradst||March 18th, 2022
|-
|Dread||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Foot soldiers are unhindered by mountains and rivers. CO powers reshuffle enemy positions in a meteor-like radius, and reduces enemy vision.||XnKradst ||March 18th, 2022
|-
|Duke || [https://drive.google.com/file/d/1CJeoPcZCeckhOecs5bX6dArgVytlsR_Q/view?usp=sharing AW Air Force Mod]||
| ||Tesla_Trooper||August 21st, 2023
|-
|Durand||[https://drive.google.com/file/d/1xL2u2VocZoDOjKP7y8ryH8cfC632WmKo/view?usp=sharing Battalion CoW]||
| ||Hamplmann||June 20th, 2023
|-
|Durand (Boss)||[https://drive.google.com/file/d/1xL2u2VocZoDOjKP7y8ryH8cfC632WmKo/view?usp=sharing Battalion CoW]||
| || Hamplmann||June 20th, 2023
|-
|Eili||[https://drive.google.com/file/d/1zirDJbTfrTRJJQvHRfIU7BIeOV1lPtlR/view K'Braid's COs]||
| || K'Braid ||March 19th, 2022
|-
|Elana||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/gAhIMa5.png Image]
| ||Captain Trek, Niklas||August 4th, 2023
|-
|Embrie
| [https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/P3OMiVM.png Image]
| Each consecutive/repeated attack against the same enemy unit on the same turn has more firepower than the last.||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above, only with slight differences.||XnKradst||March 18th, 2022
|-
|Emilie||[https://drive.google.com/file/d/1dHk6qLYlQ-w5VWV1ZAXe1jghbaCx0T7v/view?usp=sharing Standalone release]||[https://i.imgur.com/hz5lHTY.png Image]
| ||Nanoka||October 11th, 2022
|-
|Enigma||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as below, but without a CO zone.|| XnKradst||March 18th, 2022
|-
|└──||[https://drive.google.com/file/d/1c1WMRrxyFV-MbQcW9di8D-7cWuyTxmto/view?usp=sharing Standalone version]|| [https://i.imgur.com/dNMezTV.png Image]
| Changes stats and powers to a randomly chosen CO out of the 28 AW trilogy COs at the start of every turn.||XnKradst||April 2nd, 2022
|-
|Eph ||[https://drive.google.com/file/d/16GSGcaVzW-YByqO77BnqNyhEFJUJ8qtQ/view?usp=sharing Advance Wars Whatever Mod]||
| ||bajing_jalan_jalan||August 31st, 2022
|-
| Eric Andre||[https://drive.google.com/file/d/1t-05kD2INgKtjZHj1TsDQdga0FFa6nkF/view?usp=sharing Standalone release]||[https://i.imgur.com/A13joqT.png Image]
| ||Thunderdoughnut||January 27th, 2024
|-
|Error||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Old version of Xanderbot (see below).
Changes stats and powers to a randomly chosen CO out of the 38 Xanari Crew COs (from the original mod) at the start of every turn.
|XnKradst||March 18th, 2022
|-
|Eva||[https://drive.google.com/file/d/1zirDJbTfrTRJJQvHRfIU7BIeOV1lPtlR/view K'Braid's COs]||
| ||K'Braid||March 19th, 2022
|-
|Evan||[https://drive.google.com/file/d/16GSGcaVzW-YByqO77BnqNyhEFJUJ8qtQ/view?usp=sharing Advance Wars Whatever Mod]||
| ||bajing_jalan_jalan||August 31st, 2022
|-
|Excella||[https://drive.google.com/file/d/1MPU0c59TjZ8naMvREE5gBBR4bW82OwYN/view?usp=sharing Standalone release]||
| ||TheUberHunter||September 29th, 2023
|-
|Fioretto|| [https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/Wim0ByI.png Image]
| ||Hamplmann||February 5th, 2024
|-
|Frazone||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/ZwPR3w7.png Image]
| ||Captain Trek, Frazone ||August 4th, 2023
|-
|Frud||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Futo||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222 ||September 27th, 2022
|-
|Ganyu||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Gebura||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Gerald||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Gina||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/VxCjKiW.png Image]
| ||Nanoka||February 5th, 2024
|-
|└──||[https://drive.google.com/file/d/1onEmoGsmOqzTZOtgDAJXL5f2YSRhWlfZ/view?usp=sharing Standalone version]||[https://i.imgur.com/gKvLn72.png Image]
| ||Nanoka||October 5th, 2022
|-
|Goomba Tower||[https://drive.google.com/file/d/1ZjOuRGNVhfrtKHA2joYBBkmEfpt49Atu/view?usp=sharing Standalone release]||[https://i.imgur.com/9Wvh9md.png Image]
| Infantry can "stack" onto each other by loading into each other. The more units an infantry unit is carrying, the more damage it deals and the less damage it receives.||XnKradst||December 12th, 2023
|-
|Great Minds
|[https://drive.google.com/file/d/13hGRsfP8NkT0y84uszDYt2uvdpFFt5j7/view?usp=sharing Standalone release]
|
|
|Brilliand
|April 18th, 2024
|-
|Grendelle||[https://drive.google.com/file/d/1q6lLTyPJMBl5ztVp6k8At1UM-aunz1rJ/view?usp=sharing Standalone release]||[https://i.imgur.com/9Wvh9md.png Image]
| ||Nanoka||June 10th, 2023
|-
|Griffin Spade||[https://drive.google.com/file/d/1jsQbZpdcurtbJnAPRAwOVTP7S3ZpURgQ/view?usp=sharing BattleTanx COs]||
| ||Ellie||January 30th, 2023
|-
|Grigori||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/nSS2XSz.png Image]
| Units deal more damage if they start in a position not covered by the entire enemy army's vision (even outside Fog of War). CO powers allow indirect units to fire multiple times without moving.|| XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above but with slight balance changes, and the superpower also dealt splash damage to everything in an indirect unit's fire range.||XnKradst||March 18th, 2022
|-
|Gunter||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Haman||[https://drive.google.com/file/d/1L6-JmgLCmqCyrymFjXbJ4sWYoWpGLf9y/view?usp=sharing Standalone release]||[https://i.imgur.com/iH70UEY.png Image]
| ||Jsonic3000||February 14th, 2023
|-
|Hanabi||[https://drive.google.com/file/d/1mGnHtI4VpAf-RZ9j4u9_EMlaidYKnpyn/view?usp=sharing Standalone release]||[https://i.imgur.com/GSb1fye.png Image]
| ||Nanoka||November 3rd, 2023
|-
|Harbinger|| [https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/6uAJSNC.png Image]
| ||StarFlash||February 5th, 2024
|-
|Heck You||[https://drive.google.com/file/d/1P80UjX_z7TgHlNud31HKBXWAtkR63Gku/view?usp=sharing Heck You]||[https://i.imgur.com/A1txdBq.png Image]
| ||MrDuck557||December 23rd, 2023
|-
|Helena||[https://drive.google.com/file/d/1p6XBx2XTwatkX23QcEiUSoN3VwkG7gb9/view?usp=sharing Standalone release]||[https://i.imgur.com/BFUj5Pl.png Image]
| ||Nanoka||September 6th, 2023
|-
|Hibana ||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/mY35Yvu.png Image]
| ||Captain Trek, TenesCross||August 4th, 2023
|-
|Hijiri||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Hod||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Hokma||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Huang ||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/4YCZCB7.png Image]
| ||Captain Trek, Lady Braixen||August 4th, 2023
|-
|Hughes||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/C6X2Syy.png Image]
| ||Captain Trek, ???||August 4th, 2023
|-
|Hutao||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Iyala ||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Each time she kills an enemy unit, the enemy loses power charge (unless they already have a portion of the power filled, so she cannot thwart CO powers). CO powers heal or damage every unit on the map depending on their remaining HP.||XnKradst ||March 18th, 2022
|-
|Izzy||[https://drive.google.com/file/d/1zmYetlek4O-j6Noe7F_hNsOjSBzhWeNp/view?usp=sharing Nanoka AW2 COs]||
| ||Nanoka|| January 26th, 2022
|-
|Jaime||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
| Jessabelle ||[https://drive.google.com/file/d/1tbK1ypKQ-wXrtClOonw9OpHP46La3wPV/view?usp=sharing Standalone release]||[https://i.imgur.com/7DHhr1R.png Image]
| ||Nanoka||December 3rd, 2023
|-
|Jiffy||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/WsHbgtj.png Image]
| ||Captain Trek, Tanman||August 4th, 2023
|-
|Jill||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/HbC3Rtj.png Image]
| All (directs and indirects alike) units gain firepower for each tile between its starting position and the target. CO powers either boost movement and fire range, or allow indirect units to move and fire on the same turn.|| XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above with slight mechanic changes, and both powers allow indirect units to fire and move on the same turn.||XnKradst || March 18th, 2022
|-
|Joyce||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Jun||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| || KesalahanTeknis, Marmalad||April 23rd, 2022
|-
| June||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/9adXZCr.png Image]
| Indirect units can counter enemy indirect attacks. Super CO power grants indirect units extra range depending on their terrain stars.||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Indirect units deal more damage the further away the target is.||XnKradst||March 18th, 2022
|-
|Kaga||[https://drive.google.com/file/d/15gwVMSd5_VTqXTB_DDwlT8Qho1CBsKU9/view?usp=sharing Standalone release]||[https://i.imgur.com/fMtVVrA.png Image]
| ||Nanoka||August 18th, 2022
|-
| Kairo||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/pAhw7Hi.png Image]
| Units deal more damage if they have more terrain stars than the target. Regular CO power causes enemy units to not benefit from terrain stars for a turn.||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above, but with different CO powers; the superpower makes his units deal extra damage based on the enemy's terrain stars.||XnKradst ||March 18th, 2022
|-
|Katty ||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Keith||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Kidd||[https://drive.google.com/file/d/1zirDJbTfrTRJJQvHRfIU7BIeOV1lPtlR/view K'Braid's COs]||
| ||K'Braid||March 19th, 2022
|-
|Kit||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Units cannot be killed in one hit. If a 10 HP unit suffers a one-hit kill, it instead survives with 1 HP left.||XnKradst||March 18th, 2022
|-
|Koishi||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Kylie||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis|| December 18th, 2022
|-
|Kyusoku||[https://drive.google.com/file/d/1uOPewGS05etwCSMwaDwvWUp-89289n9q/view?usp=sharing Silver Horizon (Older version)]||
| ||ChemAtDark||July 2nd, 2022
|-
|Lazure||[https://drive.google.com/file/d/1GBSws0J81NuuzTNIQ6EcRfEMES--AG0W/view?usp=sharing Silver Horizon]||[https://i.imgur.com/QO9OJFD.png Image]
| ||ChemAtDark||May 5th, 2023
|-
|Lee||[https://drive.google.com/file/d/1PcJkcvQwUOCrChR35enwqxG7ufKCXVyI/view?usp=sharing Standalone release]
|
| ||Brilliand||October 12th, 2022
|-
| Leona||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/YMOo2Mu.png Image]
| Damaged units deal 20% true damage if they have the same HP as the target, or they have exactly 7 HP left. If both conditions are met, deal 40% true damage.
CO powers hide her units' HP for a turn, and also generally affects unit HP.
| XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Extremely high luck and misfortune, sometimes even healing the enemy when attacking. CO powers randomize all enemy units' fuel, ammo and HP, the last of which is superpower-only.||XnKradst||March 18th, 2022
|-
|Leopold||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/wuBRviU.png Image]
| ||Captain Trek||August 4th, 2023
|-
|Lio||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/4DDPS0b.png Image]
| When an enemy unit destroys her units, that enemy unit is tagged with a special icon. All units deal more damage against tagged enemy units.|| XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above, but with different CO powers, and attacking a tagged unit untags them.||XnKradst||March 18th, 2022
|-
|Lloyd Banning
|[https://drive.google.com/file/d/1jc8rITT_nQFrms4jNN2cpOXX8ndfFz93/view?usp=sharing Standalone release]
|[https://i.imgur.com/8ksuk3M.png Image]
|
|MrDuck557, ZERGRUSHER228
|Marth 27th 2024
|-
|Luce||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Luke||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Lumi||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/Y79zD2w.png Image]
| Naval units, and everything else covered by their vision range, have increased firepower and defense. CO power spawns damaged submarines on her ports.
Naval units can also act immediately when built (one per port).
| XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Naval units can act immediately when built (one per port), but they have low firepower and defense. They are also cheaper.||XnKradst||March 18th, 2022
|-
|Maelis||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Malkuth||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Manöver||[https://drive.google.com/file/d/19bFp6UILiKDiZLY2725o69xRY7xeAZ2-/view?usp=sharing Epsilon COs]||
| ||Eldritch||December 29th, 2021
|-
|Marie|| [https://drive.google.com/file/d/1fD7f_KHP8yAWGysd-J_23R41asgDPS4o/view?usp=sharing Standalone release]||
| ||Brilliand ||December 13th, 2022
|-
|Mario in a Kart||[https://drive.google.com/file/d/111SSJNKPbV-FuosKT31wZcdrr1N8tlKK/view?usp=sharing Mario Kart: The CO]||[https://i.imgur.com/XFGvHOZ.png Image]
| Based on Mario Kart. All units gain a random "item" at the start of his turn, which grants a variety of stats and effects.||XnKradst ||April 8th, 2023
|-
|Marisa ||[https://drive.google.com/file/d/1fr_dTx7f5P6Q7VCHwiCWOBwU5g4UZQTz/view?usp=sharing Standalone release]||
| ||Nanoka||November 4th, 2022
|-
|Maru||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Marysa L.||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/whxfxiG.png Image]
| ||SaMantaUwU||February 5th, 2024
|-
|└──
|[https://drive.google.com/file/d/1JoYiTkUCI0dKvLqMQ40na9k0mSQ-Ao-C/view?usp=sharing Standalone version]||[https://i.imgur.com/yHfCEl1.png Image]
| ||SaMantaUwU||January 28th, 2023
|-
|Mayden||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Units can over-promote to a fourth rank, granting 50% firepower and defense. CO zone and powers also promote her own units.||XnKradst||March 18th, 2022
|-
|Mengsk||[https://drive.google.com/file/d/1jxGvpKJaJS1GAyWStFnBSWYvLajme6Ha/view?usp=sharing Standalone release]||[https://i.imgur.com/iKwCZvn.png Image]
| ||Nanoka||April 4th, 2023
|-
|Mia||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Units have infinite ammo, but reduced fuel. Powers allow units to move again after attacking, but they cannot attack again.||XnKradst||March 18th, 2022
|-
|Miho Nishizumi||[https://drive.google.com/file/d/1e-gkeDi26SXbqiXlz87byNqQl_HQQYXA/view?usp=sharing Standalone release]||[https://i.imgur.com/ClNMpLR.png Image]
| ||Nanoka||November 10th, 2023
|-
|Mina||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/UwUAvfS.png Image]
| ||Sourdreemurr||February 5th, 2024
|-
|└──||[https://drive.google.com/file/d/1_qS0TaGyws59_o-twJLR_ZhKnKOhLdxn/view?usp=sharing Standalone version]||[https://i.imgur.com/OJAsIK6.jpg Image]
| ||Sourdreemurr||August 2nd, 2022
|-
|Mizer||[https://drive.google.com/file/d/15dJwaSCzHO0XHVOcNbBlyT9T9s7a37A-/view?usp=sharing Standalone release]||[https://i.imgur.com/HqM6lkF.png Image]
| ||Nanoka||November 16th, 2022
|-
|Monarch||[https://drive.google.com/file/d/19bFp6UILiKDiZLY2725o69xRY7xeAZ2-/view?usp=sharing Epsilon COs]||
| ||Eldritch||December 29th, 2021
|-
|Mr. Krabs||[https://drive.google.com/file/d/1nmLFvlR0ueWdrKXQnM-Zt37rE9tlX35W/view?usp=sharing Standalone release]||[https://i.imgur.com/sfGd5Ag.png Image]
| ||Hog||September 25th, 2023
|-
|Mr. Yamamoto||[https://drive.google.com/file/d/1iIAVQiJFMukT06flThtfR7aOzhZECE-J/view?usp=sharing SFW COs]||
| ||Creed||October 14th, 2022
|-
|Multiplier||[https://drive.google.com/file/d/18-FUmQxbaMsIuzZJONUT9McDoMsBFJCh/view?usp=sharing Standalone release]||[https://i.imgur.com/ylGOZlL.png Image]
| ||Hog ||June 24th, 2023
|-
|Myo||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Nadiyah||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/C81aG0I.png Image]
| ||Thae||February 5th, 2024
|-
|└──||[https://drive.google.com/file/d/1BS6s4eH_ni3tklWiMRBdpZgUXxslZs5H/view?usp=sharing Standalone version]||[https://i.imgur.com/TjBHXDX.png Image]
| ||Thae||October 5th, 2022
|-
|Naked Squid||[https://drive.google.com/file/d/1z3ay_9mhM75RJi_Bf4rnEkhye3kcHvmb/view?usp=sharing Standalone release]||[https://i.imgur.com/2VXygOF.png Image]
| ||Nanoka||April 2nd, 2023
|-
|Nana||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/9yNe7Il.png Image]
| Units paralyze the enemy if they are killed by counterattack. CO powers shot lasers from her buildings, which will paralyze the first enemy unit hit in each direction.||XnKradst||January 28th, 2024
|-
|└── ||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above, but can only paralyze enemy units if inside her CO zone. Powers are stronger.||XnKradst||March 18th, 2022
|-
|Nanami||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Nanoca||[https://drive.google.com/file/d/1BMizP-Vzs2jKlTe41UULV0qoL8S86N_y/view?usp=sharing Standalone release]||[https://i.imgur.com/PjvVhK1.png Image]
| ||Nanoka||January 12th, 2024
|-
|Nazrin||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Netzach||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Night||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Nue||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Nuki||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Oblivian Litleo ||[https://drive.google.com/file/d/1N1nU6U1g9KxFirZKBaklXCDXmgOZ_tRa/view?usp=sharing Imperial COs]||
| ||DarkDespair ||December 7th, 2021
|-
|The Onceler||[https://drive.google.com/file/d/10cHtcD6ba71-X3iFOoCsani-c661p2Gp/view?usp=sharing Standalone release]||
| || Brilliand||December 13th, 2022
|-
|Ophthalmia||[https://drive.google.com/file/d/1wuuXwiC68_yslNPwWsyTJ-Eld5kgc2Xv/view?usp=sharing The others Co mod]||
| ||michale modelcitizen||March 18th, 2022
|-
|Osprey||[https://drive.google.com/file/d/1QY0UJ1M71E97yEfnLrLg56EFefAeof3L/view?usp=sharing Standalone release]||[https://i.imgur.com/y6ZklNb.png Image]
| All air units are equipped with long-range missiles, giving them +1 range. COP gives a nice ball of stats to allow for an early push, or you can opt for the SCOP to refresh units when they get a kill.|| MrDuck557||March 30th, 2024
|-
|Panavia||[https://drive.google.com/file/d/1yR-cdufPtctJan2UElGEHwTY7xDrKp4M/view?usp=sharing Tristia COs]||
| ||Nanoka||October 19th, 2021
|-
|Pawke||[https://drive.google.com/file/d/1xT1vFusnoaEDhwZN47_wJF_0jKhn2wmn/view?usp=sharing Standalone release]||[https://i.imgur.com/IeQjn9a.png Image]
| ||FruityGum, MrDuck557||February 27th, 2024
|-
|Pearl ||[https://drive.google.com/file/d/1Q1HAjnSnXJ0NI5900qNF2nEj5Sz_NZqP/view?usp=sharing Standalone release]||[https://i.imgur.com/lDIlQtH.png Image]
| ||Namelessone||February 1st, 2023
|-
|Pearl||[https://drive.google.com/file/d/1xL2u2VocZoDOjKP7y8ryH8cfC632WmKo/view?usp=sharing Battalion CoW]||
| ||Hamplmann||June 20th, 2023
|-
|PenPen||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/QkmHRKz.png Image]
| || Go7||February 5th, 2024
|-
|Perses||[https://drive.google.com/file/d/1uOPewGS05etwCSMwaDwvWUp-89289n9q/view?usp=sharing Silver Horizon (Older version)]||
| ||ChemAtDark||July 2nd, 2022
|-
|Phoenix||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis ||December 18th, 2022
|-
|Pierce||[https://drive.google.com/file/d/1b_rMzpyoh-FEF-xTReUCv3aNdaSZxc6L/view?usp=sharing Anglo Isles CO mod]||
| ||michale modelcitizen||April 4th, 2022
|-
|Polish ||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/00UwOvm.png Image]
| ||Captain Trek, ???|| August 4th, 2023
|-
|Quinton||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Buildings damage enemy units at the start of his turns, but at the cost of the building's durability (if being captured).||XnKradst||March 18th, 2022
|-
|Ralph||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/7rfOP11.png Image]
| ||Captain Trek||February 5th, 2024
|-
|└──||[https://drive.google.com/file/d/1BKQyqIoZCrIhhggPnxjXgN_tW-wZ42uZ/view?usp=sharing Standalone version]||[https://i.imgur.com/8eBU4Bl.png Image]
| ||Captain Trek||August 26th, 2022
|-
|Rance ||[https://drive.google.com/file/d/1N1quhph_bCLJMAOIJa99xaGTvVpE19Na/view?usp=sharing Standalone release]||[https://i.imgur.com/z6uEozJ.png Image]
| ||Nanoka||December 29th, 2023
|-
|Rapid||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Rashelle ||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/ii4IX8U.png Image]
| ||Captain Trek, ???||August 4th, 2023
|-
|Rayane||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Rean Schwarzer||[https://drive.google.com/file/d/1HsazQ5CQf2-f4GKO_qKhZU7RJkQpg3D8/view?usp=sharing Standalone release]||
| ||Hog, ZERGRUSHER228||February 11th, 2024
|-
|Rick||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/5WXHzq0.png Image]
| Lower defense, but heals 1 HP to all of his units at the start of every turn.||XnKradst|| January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| More or less the same as above, only with slight number changes.||XnKradst||March 18th, 2022
|-
|Rick Harrison ||[https://drive.google.com/file/d/1LIBEiKQc2asFQG3EGiyBVuB4fAv4XjSs/view?usp=sharing Standalone release]||[https://i.imgur.com/ptalref.png Image]
| ||Thunderdoughnut|| January 27th, 2024
|-
|Riki|| [https://drive.google.com/file/d/16GSGcaVzW-YByqO77BnqNyhEFJUJ8qtQ/view?usp=sharing Advance Wars Whatever Mod]||
| ||bajing_jalan_jalan||August 31st, 2022
|-
|Rina||[https://drive.google.com/file/d/10OYQ5y3uP4JEWEuLJdpq91DlFvWRDRMI/view?usp=sharing Standalone release]||[https://i.imgur.com/wJUFwPI.png Image]
| ||Nanoka||April 29th, 2023
|-
|Rocky||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/WJtKA2o.png Image]
| High defense, but faster units have one less movement point.||XnKradst|| January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Mostly the same as above, but with a gimmicky superpower that converts all of his cities into custom "fortified" variants that only his own units can cross. They must be destroyed to be reverted to a normal town.|| XnKradst||March 18th, 2022
|-
|Rodger||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/Z0mkX53.png Image]
| ||Captain Trek, Niklas||August 4th, 2023
|-
|Rooke||[https://drive.google.com/file/d/1L6rNvsFL96TRjzSPHSXqaHDraWOILp2A/view?usp=sharing Commander Wars - 1st CO Contest]||[https://i.imgur.com/DJp4RWz.png Image]
| ||Λvalon||February 5th, 2024
|-
|└──||[https://drive.google.com/file/d/1QmFa3xRd9by9J3vfItkLAdV8yI0ge7JQ/view?usp=sharing Standalone version]||[https://i.imgur.com/1Crd7xU.png Image]
| ||Λvalon||September 7th, 2022
|-
|Rose ||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Sabrina||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
| Sakura||[https://drive.google.com/file/d/16GSGcaVzW-YByqO77BnqNyhEFJUJ8qtQ/view?usp=sharing Advance Wars Whatever Mod]||
| ||bajing_jalan_jalan|| August 31st, 2022
|-
|Sally||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/dNvQc4v.png Image]
| Units ignore damage below a certain threshold (chip damage). Super CO power renders all units invincible to everything except killing blows.||XnKradst||January 28th, 2024
|-
| └──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Repairs cost half the price, and powers allowed her to gain funds from damage received. She still has the above version's super CO power.||XnKradst||March 18th, 2022
|-
|Santa Sturm||[https://drive.google.com/file/d/11iM-LjYWCy946iQM0OmIzvlOUxelZH5p/view?usp=sharing Standalone release]||
| ||Tesla_Trooper||December 24th, 2022
|-
|Scroid||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Bases can deploy Oozium and a custom Parasite unit. Those units also have 1 more movement than normal. CO powers either buff or spawn more of those units.||XnKradst||March 18th, 2022
|-
|Seargent Quackers
|[https://drive.google.com/file/d/1OyjrJ7GpjVXwqPVHQhfM8vBXYAmt1Snn/view?usp=sharing Standalone release]||[https://i.imgur.com/NtwWlGn.png Image]
| A duck that repairs. All you need to know.
Infantry and APCs can repair, and Black Boats repair 2hp instead of one. All repairs are half cost. COP makes all repairs more potent and free, and SCOP gives a refresh on top of that.
|MrDuck557||March 30th, 2024
|-
|Serena||[https://drive.google.com/file/d/1K26DVCK5EiIODwaOFUjwQROpOLs74raG/view?usp=sharing Standalone release]||
| ||TheUberHunter||October 4th, 2023
|-
|Serg||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Snipers can pierce the armor of enemy vehicles, including helicopters.||XnKradst||March 18th, 2022
|-
|Shaltear||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis
|December 18th, 2022
|-
|Sheren||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis, Marmalad||December 18th, 2022
|-
|Sidney||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Killing enemy units reduces the enemy player's funds, which can drop below 0 to the negatives (putting them in debt).||XnKradst ||March 18th, 2022
|-
|Silbergeist||[https://drive.google.com/file/d/1uOPewGS05etwCSMwaDwvWUp-89289n9q/view?usp=sharing Silver Horizon (Older version)]||
| ||ChemAtDark||July 2nd, 2022
|-
|SKrlett||[https://drive.google.com/file/d/1cxYLlWCmvNLGPMsMtIPbJhxG6U8Nk81u/view?usp=sharing KTeknis Projects (Older version)]||
| ||KesalahanTeknis, Marmalad||April 23rd, 2022
|-
|Sol||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Slightly stronger during sunny weather, slightly weaker otherwise. CO powers grant several major stat boosts at once (firepower, defense, movement, fire range, vision, capture points, unit discounts).||XnKradst||March 18th, 2022
|-
|Sonny||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/3Yfp9ku.png Image]
| Attacks heal the allied unit behind the attacker. CO powers make his attacks deal collateral damage to all enemy units behind the target in a straight line, range depending on power.||XnKradst||January 28th, 2024
|-
| └──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as the above, but CO powers deal more damage at the cost of losing terrain stars on most terrain.||XnKradst||March 18th, 2022
|-
|Sophia||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/lLYODSP.png Image]
| ||Captain Trek, Quentcat||August 4th, 2023
|-
|Soraya||[https://drive.google.com/file/d/11UUWFRcv2DwEt4TwUdwZeP5uJ_J0jQQm/view?usp=sharing Standalone release]||[https://i.imgur.com/qNlDB6l.png Image]
| || ruigio||October 27th, 2023
|-
|Splitting Slime||[https://drive.google.com/file/d/1TlpgIC5hZ2eCyVLRs10SK-1moFyNvw9M/view?usp=sharing Standalone release]||
| ||Brilliand||October 29th, 2022
|-
|Surge ||[https://drive.google.com/file/d/1fMb8YTsvbk6BlFrH3tm4zA_VIli2aUON/view?usp=sharing Standalone release]||
| ||Brilliand, I_Am_Jarvis|| October 30th, 2022
|-
|Syrene||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis|| December 18th, 2022
|-
|Talas||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis, Marmalad||December 18th, 2022
|-
|Tapper||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]
|[https://i.imgur.com/OuXt63s.png Image]
| ||Captain Trek, Shaw Fujikawa||August 4th, 2023
|-
|Tara||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/3DAmMnv.png Image]
| ||Captain Trek, ???||August 4th, 2023
|-
|TCM
|[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Teki|| [https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Tempest||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis, Marmalad||December 18th, 2022
|-
|Tenshi||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Tepho||[https://drive.google.com/file/d/1H1hzw10AnLkwm-g0NfVT4SCMHVWEK5lQ/view?usp=sharing Standalone release]||
| ||MrDuck557, ZERGRUSHER228||January 21st, 2024
|-
|Tesla||[https://drive.google.com/file/d/18pDeNt4g6Stzdl86ZTvIQwBBxvdcUEQw/view?usp=sharing Standalone release]||[https://i.imgur.com/vIEEDhF.png Image]
| ||Nanoka, MrDuck557||January 24th, 2024
|-
|Tiphereth
|[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Tomasu||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/cnFjRdQ.png Image]
| Start every turn with firepower slightly below average. Every time a unit is ordered to wait, his firepower rises. Every time a unit attacks, his firepower resets (after the attack).||XnKradst||January 28th, 2024
|-
| └──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Stealth units cost less and are stronger, but foot soldiers are weaker. CO powers grant movement to all units and allow them to pass enemy units.||XnKradst||March 18th, 2022
|-
| Tondra||[https://drive.google.com/file/d/1QS0OGCeMcONR9k9Nd7e60XDRmqpcmcTI/view?usp=sharing Standalone release]||
| ||Nanoka, Omega||March 30th, 2022
|-
|Troy||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/49d4slF.png Image]
| Has the ability to trick the enemy by deploying "decoy" variants of some units (light tank, artillery, anti-air and battle copter), all at the price of 3000. These decoys move slower, cannot attack and are destroyed in one hit. CO powers either allow more decoy deployments, or convert decoys into real units.||XnKradst||January 28th, 2024
|-
| └──
|[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Has the ability to deploy "Spy" units, which are infantry that can use stealth, but weaker in combat. CO powers spawn more spies in random places.||XnKradst||March 18th, 2022
|-
|Tucker||[https://drive.google.com/file/d/1xL2u2VocZoDOjKP7y8ryH8cfC632WmKo/view?usp=sharing Battalion CoW]||
| ||Hamplmann||June 20th, 2023
|-
|Tyke||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Tynia||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/USHDqrl.png Image]
| Ground units (except foot soldiers) have an extra movement point if starting on a production facility or road tile. CO powers make her units deal more damage per terrain star traversed before attacking.||XnKradst||January 28th, 2024
|-
|└──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| All ground vehicles including motorbikes have improved firepower and movement across all terrain. Super CO power kills the enemy's most expensive unit instantly.||XnKradst||March 18th, 2022
|-
| Umi||[https://drive.google.com/file/d/1frd3DlcRmIyirjj9GdqKlhfjaVoyWxx9/view?usp=sharing Standalone release]||[https://i.imgur.com/lYOtTmv.png Image]
| ||Nanoka||March 1st, 2023
|-
|Visor||[https://drive.google.com/file/d/1XJ9qpPpj4ucHjtCryFmTD5irFQbShEUz/view?usp=sharing The Overlooked Ones]||[https://i.imgur.com/6BF4oUH.png Image]
| ||Captain Trek, boiyouthought98||August 4th, 2023
|-
|Walder||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Windsor|| [https://drive.google.com/file/d/1b_rMzpyoh-FEF-xTReUCv3aNdaSZxc6L/view?usp=sharing Anglo Isles CO mod]||
| ||michale modelcitizen||April 4th, 2022
|-
|Xander||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/613P1vb.png Image]
| Deployed units can immediately act, allowing the same base to deploy as many units as he can afford. All units have more firepower but significantly less defense.
CO powers reduce deployment costs.
|XnKradst||January 28th, 2024
|-
| └──||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above, but with more ridiculously overpowered stats.||XnKradst||March 18th, 2022
|-
|Xanderbot||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/BPDgAkj.png Image]
| New version of Error (see above).
Changes stats and powers to a randomly chosen CO out of the 26 Xanari Crew COs (from the remake) at the start of every turn.
| XnKradst||January 28th, 2024
|-
|Xiao||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Xingqiu||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Yesod||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| ||KesalahanTeknis||December 18th, 2022
|-
|Youmu||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Yune||[https://drive.google.com/file/d/1guC8D2-C8hfl4hvNYTEYa6U5HOQfND2W/view KTeknis Projects]||
| || KesalahanTeknis||December 18th, 2022
|-
|Zaiu||[https://drive.google.com/file/d/1n33aVqoy9uVDC7nR-to8dQa35Y98Dly7/view?usp=sharing Xanari Crew (Remake/AW2)]||[https://i.imgur.com/9ufaR6Z.png Image]
| Perfect vision at the cost of slightly lower vision range. CO powers grant him temporary control of enemy units.||XnKradst|| January 28th, 2024
|-
|└──
|[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| Same as above, but powers gain permanent control of enemy units.||XnKradst||March 18th, 2022
|-
|Zhongli||[https://mega.nz/file/pwoxXL4Y#oy79ceCRPQur_Hr4Fn4HyGSS8yCl8u1EkxfBDS3Mzxg Tsubaki mods]||
| ||shirone222||September 27th, 2022
|-
|Zuza||[https://www.mediafire.com/file/czr387mrs7w7d0l/CoW_Xanari_Crew_ver12_1.zip/file Xanari Crew (Original)]||
| If units die in one hit, 75% of the funds spent deploying them is refunded. CO powers make all living units generate more money.||XnKradst||March 18th, 2022
|}

==List of KnightLord COs created for Commander Wars==
Last Updated: April 12th, 2024
{| class="wikitable"
!Name (Non OCs/OCs)!!Mod!!Image / Dossier
!Description!!Creator(s)!!Last Updated
|-
|Aaron (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Abby (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
| April 12th, 2024
|-
|Admiral Wiler (Langrisser 4 & 5)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Adon (Choi Aniki & Langrisser series)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2] ||
| ||Knightlord07||October 9th, 2023
|-
|Agana (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
| Knightlord07
|January 31st, 2024
|-
| Agent #7 (Tsukihime 2000 & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
| April 1st, 2024
|-
|Agnes (Trails Through Daybreak)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Ainz (OverLord Anime)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Airi (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th 2024
|-
|Akatsuki (UNIB & Akatsuki Blitzkampf)|| [https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| || Knightlord07||November 15th, 2023
|-
|Akiha (Tsukihime & Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Akihiko (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
| Akuhei (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Akira (OC)|| [https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Albedo (Overlord Anime)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Albert (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Alfred (Langrisser 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Alicia (Valkyria Chronicles)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs] ||
| ||Knightlord07||October 9th, 2023
|-
|Alina (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Alma (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
| January 31st, 2024
|-
|Altemuller (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Altera (Fate/Grand Order)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Altina (Trails Cold Steel series)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Alustriel (Langrisser Mobile)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Ami (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| || Knightlord07||November 15th, 2023
|-
|Amenozako (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Ange (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Angelica (Langrisser Mobile) ||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3] ||
| ||Knightlord07||October 9th, 2023
|-
|Angelina (Langrisser 4 & 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
| Anna (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07|| October 9th, 2023
|-
|Ansel (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07 || December 9th, 2023
|-
|Aoko (Tsukihime & Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse] ||
| ||Knightlord07||October 31st, 2023
|-
|Aoi (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
| January 31st, 2024
|-
|Arcueid (Tsukihime & Melty Blood)|| [https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Arcueid wearing neko suit (Tsukihime 2000 & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
| April 1st, 2024
|-
|Archetype: Earth (Tsukihime & Melty Blood)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Ares (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Arianrhod (Trails series)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07 ||October 9th, 2023
|-
|Artoria Alter (Fate/Stay Night: Heaven Feel)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Artoria Lily (Fate/Unlimited Code)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Artoria Pendragon (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Asa (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Ashram (Record of Lodoss War)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Asne (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Asuka (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
| January 31st, 2024
|-
|Asuna (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Autokrato IV (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07|| October 9th, 2023
|-
|Ayako
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Ayami
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Ayla (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
| January 31st, 2024
|-
| Ayuka (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Battler (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Bazett (Fate/Hollow Atarxia)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Belne (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
| Bernhardt (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07 ||October 9th, 2023
|-
|Betty (Langrisser 1 Remake)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
| Bianca (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Big Nobu (Fate/Grand Order & Joke)
| [https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Blood Cougher Okita Souji (Fate/Grand Order & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
| April 1st, 2024
|-
|Borys (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Boris (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
| January 31st, 2024
|-
|Bozel (Langrisser series)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Brainwash Detective Hisui (Tsukihime 2000 & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Brenda (Langrisser 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1] ||
| ||Knightlord07||October 9th, 2023
|-
|Bukko (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Byakuya (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Calista (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Camille (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
| Camu (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Caren (Fate/Hollow Atarxia) ||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Carmine (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Carol (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Chad Sanshiro (Project X Zone 2 & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Cherie (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Chie (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Chika (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Chinatsu (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Chiyo (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Chris (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Christiane (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Ciel (Tsukihime & Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07 ||October 31st, 2023
|-
|Clarett (Langrisser 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
| Claire (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Constanta (Langrisser Re:Incarnation Tensei)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Cu Chulainn (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Culture Spreader Oda Nobunaga (Fate/Grand Order & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Dae (OC)
| [https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Dai (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Danta (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|Firepower & defense per tiles moved
|Knightlord07
| April 12th, 2024
|-
|Dark Sakura (Fate/Stay Night: Heaven Feel)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
| April 12th, 2024
|-
|Deedlit (Record of Lodoss War)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Diarmuid (Fate/Umlimited Code & Fate/Zero)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Diego (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
| Dieharte (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Digos (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
| Dios (Langrisser 3) ||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07 ||October 9th, 2023
|-
|Do Kahni (Langrisser 3)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Dust (Melty Blood Actress Again)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
| Edward (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Egbert (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Elaine (Trails through Daybreak)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Elizabeth (OC)|| [https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Elma (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2] ||
| ||Knightlord07||October 9th, 2023
|-
|Eltnum (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| || Knightlord07||November 15th, 2023
|-
|Elwin (Langrisser 2) ||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Emerick (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Emi (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07|| December 9th, 2023
|-
|Emika (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Emiko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Emma (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Enkidu (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Eri (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv%20Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
| Eriko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Eric (OC)
| [https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
| Est (Langrisser 2) ||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Estelle (Trails series)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Eva (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Excella (Shining Resonance)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Fauvel (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Featuring Dante From Devil May Cry (Devil May Cry series & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Fen (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Feraquea (Langrisser 3 & 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Finn (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
| January 31st, 2024
|-
|Florentia (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Freya (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Fuji (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Futaba (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Fuyuko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Gawain (Fate/Extra)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Geese Howard (KOF series)||[https://drive.google.com/file/d/1BE4n71tmlYvtL78EwbJkRRIvXModKZ62/view?usp=sharing Standalone release]||[https://i.imgur.com/beKGSQs.png Image]
| ||Knightlord07||April 12th, 2023
|-
|Gerold & Layla (Langrisser Mobile & Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07 || October 9th, 2023
|-
|Gilbert (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Gilgamesh (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Ginko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Gintoki (Gintama)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07|| October 9th, 2023
|-
|Gizarof (Langrisser 4 & 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Gordeau (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Greta (OC)
| [https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
| Knightlord07
|April 12th, 2024
|-
|Gudako (Learning FGO Manga & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Gunther (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Gustaf (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Hae (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Hammer (Castlevania: Aria & Dawn of Sorrow)||[https://drive.google.com/file/d/1dprfKbgHEOQ__jQe3eAWZtjx6K-zMadV/view?usp=sharing Standalone release]||[https://i.imgur.com/H59xMzc.png Image]
| ||Knightlord07|| May 13th, 2023
|-
|Haruhi (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
| Haruka (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Haruyi (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Haunted Astolfo Plushie (Meme)
| [https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Hawking (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
| Hein (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Helena (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix] ||
| ||Knightlord07||December 9th, 2023
|-
| Heracles (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
| Hisae (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Hiei (Yu Yu Hakusho)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Hilda (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Hilda (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Himiko (Mashin Hero Wataru)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Hinako (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Hisui (Tsukihime & Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Hiyori (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
| Honoka (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
| Hotaru (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Hyde (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Ichika (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|IIIyasviel (Fate/Stay Night)|| [https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| || Knightlord07||October 31st, 2023
|-
|Imelda (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Iori (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Iris (Sakura Wars)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs] ||
| ||Knightlord07||October 9th, 2023
|-
|Isara (Valkyria Chronicles)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs] ||
| ||Knightlord07||October 9th, 2023
|-
|Iseul (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
| Ivar (Langrisser 4)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1] ||
| ||Knightlord07||October 9th, 2023
|-
|Ixqui (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Jeanne (Fate/Apocrypha & Fate series) ||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Jessica (Umineko) ||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07 ||December 9th, 2023
|-
|Jessica (Langrisser series)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Jill (OC)
| [https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Joa (Langrisser Re:Incarnation)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
| Johnny (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Joshua (Trails series)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Jugler (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Julian (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
| Juri (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|JuWon (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07|| November 15th, 2023
|-
| Kagura (Gintama)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Kako (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
| Kalina (Girls' Frontline & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Kana (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Karl (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Karin (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
| Kasumi (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
| January 31st, 2024
|-
|Katsuko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Kawai (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
| Kayura (Legendary Armor Samurai Trooper)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| || Knightlord07||October 9th, 2023
|-
|Kazuma (Yu Yu Hakusho)|| [https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs] ||
| ||Knightlord07||October 9th, 2023
|-
|Kei (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs] ||
| ||Knightlord07||November 15th, 2023
|-
|Keiko (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Keith (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Kertesz (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Ki (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Kirei (Fate/Stay Night) ||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse] ||
| ||Knightlord07||October 31st, 2023
|-
|Kirika (Shining Resonance)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07 ||October 9th, 2023
|-
|Kirikaze (Langrisser 3) ||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Kishyami (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Kiyoko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Klose (Trails series)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Knight of Mystery (Langrisser Mobile & Langrisser 4 & 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Knightlord07 (Discord member)||[https://drive.google.com/file/d/1UjrgeGmJX7wUTWKg4Xwa2kPc9gKbHk6W/view?usp=sharing Standalone release]||[https://i.imgur.com/N0t7BrO.png Image]
| || Knightlord07||October 31st, 2023
|-
| Kohaku (Tsukihime & Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Koharu (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Komako (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Konomi (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
| April 12th, 2024
|-
|Kouma (Kagetsu Tohya & Melty Blood)|| [https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| || Knightlord07||October 31st, 2023
|-
|Kruger (Langrisser 4)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Kunio (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Kuon (UNIB) ||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Kurama (Yu Yu Hakasho)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
| Kurami (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Kwan (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Kyle (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Kyoko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Kyrie (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Laetitia (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Laias (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
| Lainforce (Langrisser 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Laird (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Lambda (Langrisser 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
| Lana (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07 ||October 9th, 2023
|-
|Lance (Langrisser 1) ||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Landius (Langrisser 4 & 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Ledin (Langrisser 1 & 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Leion (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07|| December 9th, 2023
|-
|Len (Kagetsu Tohya & Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Lenon (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Leon (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07|| October 9th, 2023
|-
|Leonhardt (Trails of the Sky series)
|[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Leopold Goenitz (KOF series)||[https://drive.google.com/file/d/1ZvoEp6txHrxWzOhiqHg-MdyWmaPzixdU/view?usp=sharing Standalone release]||[https://i.imgur.com/ZKWPp2j.png Image]
| ||Knightlord07 ||September 3rd, 2023
|-
|Lester (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Letitia (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Lewin (Langrisser 3) ||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
| Leysritt (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Liana (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Liang (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Licorice (Langrisser Re:Incarnation)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| || Knightlord07||October 9th, 2023
|-
|Liffany (Langrisser 3) ||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Light of Genesis (Langrisser Mobile & Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Lina (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix] ||
| ||Knightlord07||December 9th, 2023
|-
|Linne (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Listell (Langrisser 4)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Londrekia (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| || Knightlord07||November 15th, 2023
|-
|Lucia (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07 ||December 9th, 2023
|-
|Lucretia (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Lucy (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix] ||
| ||Knightlord07||December 9th, 2023
|-
|Lufu (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Lugner (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
| Luna (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Lunon (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07|| December 9th, 2023
|-
|Luviagelita (Fate/Hollow Atarxia)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Maaya (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Madoka (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Magical Amber (Fate/Tiger Colosseum Upper, Tsukhime & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Mai (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Maiya (Langrisser Re:Incarnation)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Makoto (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Manon (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| || Knightlord07||December 9th, 2023
|-
|Marcus (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix] ||
| ||Knightlord07||December 9th, 2023
|-
|Mari (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Mariel (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07 ||October 9th, 2023
|-
| Mash (Fate/Grand Order)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
| Masuyo (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
| April 12th, 2024
|-
|McClaine (Langrisser 4 & 5)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| || Knightlord07|| October 9th, 2023
|-
|Mecha Hisui (Melty Blood)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Medea (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Medusa (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Merkava (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Michael (Tsukihime & Melty Blood)|| [https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Michel (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Michie (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Mika (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Mina (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Minako (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Mini Nobu (Fate/Grand Order & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Mio (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Mion (Higurashi)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| || Knightlord07||December 9th, 2023
|-
|Misako (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Miyako (Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Mizuki (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
| Mizuko (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Momoko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Mutsumi (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Nagya (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07 ||October 9th, 2023
|-
|Naoko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
| Narm (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1] ||
| ||Knightlord07||October 9th, 2023
|-
|Nasase (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| || Knightlord07||November 15th, 2023
|-
|Natsuhi (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Neco Arc (Tsukihime & Melty Blood) ||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Neco Arc Chaos (Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Nero (Fate/Extra)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07 ||December 9th, 2023
|-
|Newspaper Miyako (Melty Blood & Joke)
| [https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Nicolis (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|No Name (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Noel
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Noemi (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| || Knightlord07||October 9th, 2023
|-
|Nrvnqsr (Tsukihime & Melty Blood)|| [https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
| Null (Langrisser 4)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Odilon (Langrisser Re:incarnation Tensei)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Oiwa (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Olivier (Trails series)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Omega (Langrisser 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Ophelia (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|OP Vergil (Devil May Cry series & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
| Orie (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| Hordes||Knightlord07||November 15th, 2023
|-
|Ost (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Padoru (Fate/Extra)||[https://drive.google.com/file/d/1uat2yf00ZvXfT_55kaWuF9uIRLunZePg/view?usp=sharing Standalone release]||
| ||Knightlord07||December 9th, 2023
|-
|Parn (Record of Lodoss War)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Patsyr (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Pierre (Langrisser 3)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Pilk Seller Neco Arc (Tsukihime & Melty Blood Remake & Joke)
| [https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
| April 1st, 2024
|-
|Pirotess (Record of Lodoss War)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Polyal (Langrisser Re:Incarnation Tensei)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Power Ciel (Tsukihime & Melty Blood)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
| Knightlord07
|January 31st, 2024
|-
|Rachel (Langrisser 4)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Rakumei (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Ranford (Langrisser 4 & 5)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Red Arcueid (Melty Blood)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Rean (Trails of the Cold Steel Series)|| [https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Rei (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Reina (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Rena (Higurashi)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Renata (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Renne (Trails series)|| [https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Rie (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Ricky (Langrisser 4) ||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Riesbyfe (Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Rika (Higurashi)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Rinko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
| Knightlord07
|April 12th, 2024
|-
|Rin (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Rin Tohsaka on a Pink Car (Fate/Stay Night & Joke)
| [https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Robo Colonel Sander (Langrisser Mobile & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Rohga (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Rona (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Rosa (Umineko) ||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix] ||
| ||Knightlord07||December 9th, 2023
|-
|Rosetta (OC) ||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Rozalia (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
| Rozenciel (Langrisser Mobile & Langrisser 4 & 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Ryo (Legendary Armor Samurai Troopers)|| [https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Ryo (OC)
| [https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Ryu (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Ryuji (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Sacchin but isn't it sad Sacchin (Tsukihime & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
| April 1st, 2024
|-
|Sakura (Sakura Wars)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Sakura (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Sam (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Samson (Choi Aniki & Langrisser series)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2] ||
| ||Knightlord07||October 9th, 2023
|-
|Sanae (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Sanon (Umineko)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Sasaki (Fate/Stay Night)|| [https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07|| October 31st, 2023
|-
|Satsuki (Tsukihime & Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Scathach (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07 ||November 15th, 2023
|-
|Scathach (Fate/Grand Order)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Scott (Langrisser 2)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07
|October 9th, 2023
|-
|Seiba Lion (Fate/Tiger Colosseum & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Seiba on a Lion (Fate/Stay Night & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
| Seikyo (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
| Seishi (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Senpai food lover Sakura (Fate/Stay Night & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
| Sensei Ciel Curry Maker (Tsukihime & Melty Blood Remake & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Seo (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Selvaria (Valkyria Chornicle)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Serena (Langrisser 4)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
| Serena (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Seth (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
| Setsuko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Setsuna (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Shalltear (Overlord Anime)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Shannon (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07|| November 15th, 2023
|-
|Shelfaniel (Langrisser 4 & 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Shibaraku (Mashin Hero Wataru)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs] ||
| ||Knightlord07||October 9th, 2023
|-
|Shigo (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Shiin (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Shilinka (Langrisser Mobile)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Shiki (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07 ||November 15th, 2023
|-
|Shiki Nanaya (Kagetsu Tohya & Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Shiki Ryougi (Melty Blood Actress Again)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Shiki Tohno (Tsukihime & Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Shinji (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Shinpachi (Gintama)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Shion (Higurashi)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Shiori (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Shirou (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
| Shoten (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Sieghart (Langrisser 3 & 2)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Sigma (Langrisser 5)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07|| October 9th, 2023
|-
|Silver Wolf (Langrisser 3)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Sion (Melty Blood)|| [https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| || Knightlord07||October 31st, 2023
|-
|Sion TATARI (Melty Blood)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Sissi White (Langrisser Mobile)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Sokushi (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Sonia (Shining Resonance)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07 ||October 9th, 2023
|-
|Sonia (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Sonya (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Sophia (Langrisser 3)
|[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Sora (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07||December 9th, 2023
|-
|Souichirou (Fate/Stay Night)|| [https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07||October 31st, 2023
|-
|Strange Foreigner (Street Fighter 2 & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
| Sunako (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Super Smart Eltnam (Melty Blood & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Sumire (Sakura Wars)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Suzette (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Taiga (Fate/Stay Night)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse]||
| ||Knightlord07|| October 31st, 2023
|-
|Taiga on a Tiger Tank (Fate/Stay Night & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
| Takeru (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
| Knightlord07
|January 31st, 2024
|-
|Taylor (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Theresa Apocalypse (Honkai Impact 3rd & Joke)||[https://drive.google.com/file/d/1fJ2PcK301so_MOuHc-aLShhQ8Iu-cQdn/view?usp=sharing Standalone release]||[https://i.imgur.com/prekBzv.png Image]
| ||Knightlord07||April 13th, 2023
|-
|Thorn (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Thumb Down Akiha (Tsukihime 200 & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Tiaris (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| || Knightlord07||October 9th, 2023
|-
|Toguro (Yu Yu Hakusho)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Toma (Legendary Armor Samurai Troopers)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Towa (Langrisser Re:Incarnation Tensei) ||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07|| October 9th, 2023
|-
|Tsundere Jalter (Fate/Grand Order & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
| Tsubaki (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
| Tsubasa (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|Naval units into land tiles
|Knightlord07
|April 12th, 2024
|-
|Tsubame (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|Tsurugi (UNIB) ||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Ultimate Fumo (Touhou & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Valan (Langrisser series)|| [https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07|| October 9th, 2023
|-
|Van (Trails through Daybreak)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Vanessa (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
| Knightlord07
|January 31st, 2024
|-
|Vargas (Langrisser 2)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Varna (Langrisser 3)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1]||
| ||Knightlord07||October 9th, 2023
|-
|Vatista (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Vera (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07 ||November 15th, 2023
|-
|Virash (Langrisser 5)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Vermillion Akiha (Melty Blood)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Volkoff (Langrisser 1)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 1] ||
| ||Knightlord07||October 9th, 2023
|-
|Wagner (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Waldstein (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
| Wanna play some KOF (KOF & Joke)
|[https://drive.google.com/file/d/1_dLZPct3ns8jeGuf5DDyYpQ167JiR4Fc/view April Fool's]
|
|
|Knightlord07
|April 1st, 2024
|-
|Warui (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Wataru (Mashin Hero Wataru)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Werner (Langrisser Re:Incarnation Tensei)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 2]||
| ||Knightlord07||October 9th, 2023
|-
|White Len (Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse] ||
| ||Knightlord07||October 31st, 2023
|-
|Wilhelm (OC)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|William (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Yami (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Yoshiko (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs] ||
| ||Knightlord07||November 15th, 2023
|-
|Yui (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Yuna (OC)
|[https://drive.google.com/file/d/1zM0ybz8E7J4nvpOLMJ3p6j2jxWtWlm7j/view KL07's Main Mods Overhaul]
|
|
|Knightlord07
|January 31st, 2024
|-
|Yuki (OC)||[https://drive.google.com/file/d/1u4dedGsx0JWVbLEmmEkGBVRftqBpvUHh/view KL07's Origin Mix]||
| ||Knightlord07|| December 9th, 2023
|-
|Yulia (Langrisser Mobile)||[https://drive.google.com/file/d/1fm69FaPuCDTxpzS9KvuHNewer_sY20iX/view Langrisser Vol. 3]||
| ||Knightlord07||October 9th, 2023
|-
|Yuri (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|Convert units
|Knightlord07
|April 12th, 2024
|-
|Yuriko (OC)
|[https://drive.google.com/file/d/1F3ZAoyXkCNTEjghfPv+Ly55ptvnJXKZM/view OCs Rival]
|
|
|Knightlord07
|April 12th, 2024
|-
|Yusuke (Yu YU Hakusho)||[https://drive.google.com/file/d/1Gzo3tLo8RH_9f7uA7VRZqQjjWg5-rxrg/view Langrisser Mobile Collabs]||
| ||Knightlord07||October 9th, 2023
|-
|Yuzuriha (UNIB)||[https://drive.google.com/file/d/1g67JGlWUtauia1lehRFGurKyVmrbs03f/view KL07's OCs]||
| ||Knightlord07||November 15th, 2023
|-
|Zepia (Melty Blood)||[https://drive.google.com/file/d/1i1bSSqae7Gg7GVobJgascbuXI7sbGHni/view Nasuverse] ||
| ||Knightlord07|| October 31st, 2023
|}Link to those cos in these page
* [[Langrisser Vol1|Langrisser Vol 1]] (Advancegrisser)
*[[Langrisser Vol2|Langrisser Vol 2]] (Advancegrisser)
*[[Langrisser Vol3|Langrisser Vol 3]] (Advancegrisser)
*[[Langrisser Mobile Collabs|Langrisser Collab]]
*[[Nasuverse]] (Type Moon)
*[[KL07's OCs]]
*[[KL07's Origin Mix]]
*[[KL07's Final OCs|KL07's Final]]
*[[KL07's April Fools|April Fools]]
*[[KL07's OCS Rival Cos|OCs Rivals]]
[[Category:Mods]]

[[Category:Mods]]

Andy Breakdown

2023-12-31T16:12:42Z

MrDuck557: Links go to master branch now

'''Notice: Modding tutorials assume you know at least the basics of coding or scripting. Commander Wars uses Javascript as the Scripting Language.''' In case you want to learn more about Javascript, you can check the tutorial here: Derek Banas' Javascript tutorial , purchase O'Reilly's excellent book on the subject JavaScript: The Definitive Guide, or check out W3 Schools Interactive Tutorials

'''This tutorial references https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_andy.js, the source code of the actual vanilla Andy in COW.'''

== Small Disclaimer ==
This will only go through vanilla Andy's js code, and not any other files. This is intended for newer players to understand the workings of what the code they're copy-pasting actually does. If you want to make a brand new CO in a mod, a good starting point is [[Custom CO]]. Alternatively, download a mod and edit to suit your needs.

Also I refer to normal CO powers as COP and super CO powers as SCOP, just clearing that up

== Some stuff in the header ==
<syntaxhighlight lang="javascript" line="1" start="1">
var Constructor = function()
{
</syntaxhighlight>The very first line (or two) of code. This defines a variable called Constructor to be a function. What does the function do? It's defined in the curly brackets {} following it. Notice how only the opening bracket is present. This is a long function (the whole CO).<syntaxhighlight lang="javascript" line="1" start="3">
this.getCOStyles = function()
{
return ["+alt", "+alt2", "+alt3"];
};
</syntaxhighlight>Due to some js... weirdness, we treat functions as objects that you can define properties of. If we called Constructor.getCOStyles() after finishing the Constructor function, we would get this. Specifically it would return ["+alt", "+alt2", "+alt3"]. This is telling the game to look for alternate CO images labeled "andy+alt", "andy+alt2", and "andy+alt3" as well as simply "andy". If you look in the corresponding images folder ([https://github.com/Robosturm/Commander_Wars/tree/master/resources/images/co/os]), we do actually find said images. This is Commander Wars's way to get CO styles, so if you want to have extra costumes for your CO, this is how you do it.<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
}
};
</syntaxhighlight>This is a custom function for the AI behavior of Andy. If it looks scary, that's because <s>it kinda is</s> there's just a bunch of variables and if statements flying around. Let's break this down further<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{

</syntaxhighlight>Again, a function definition. But this time, with words inside the function() brackets. Those are called parameters, and how you can pass data into a function. Here, the game is passing in:

* The CO (co) (specifically the player's instance of a CO, in an andy mirror match both andys are actually considered different COs)
* The power charge more than what the COP needs (powerSurplus)
* The count of all owned units on the field (unitCount)
* Count of all units less than 10hp (repairUnits)
* Count of all units that can shoot at more than 1 range (indirectUnits)
* Count of all units not an indirect unit (directUnits)
* The number of enemy units
* The turn mode of the AI, set to start of day, during the day, and end of day.

The vast majority of the time, a significant portion of these will not be used (for example, Andy doesn't really care if his units are direct or indirect, so long as they're repaired)<syntaxhighlight lang="javascript" line="1" start="10">
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{

</syntaxhighlight>This checks that the turn mode is start of day. This makes sure that Andy only ever uses his power at the start of each day.<syntaxhighlight lang="javascript" line="1" start="12">
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
</syntaxhighlight>If Andy can use his SCOP of course he uses his SCOP<syntaxhighlight>
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
</syntaxhighlight>If Andy has at most 0.5 stars more than his COP (and if he can use his COP in the first place), return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);?

Referencing CO.getAiUsePowerAtUnitCount, it first checks if turnMode is equal to start of day, and also if repairUnits (in Andy's getAiUsePower at least, the name is changed during the function call to unitCount) is at least 5.

If either of these conditions are not fulfilled, don't use any power.

If both of these conditions are fulfilled, use SCOP is possible, and use COP if powerSurplus <= 0.5 (and if COP is usable in the first place)

So essentially, Andy doesn't want to Hyper Repair unless he has just enough power charge and if he can repair at least 5 units.<syntaxhighlight lang="javascript" line="1" start="21">
}
};
</syntaxhighlight>Closing brackets you always need those

You may be put off at the lack of a return statement here. Won't the code break if the function doesn't return anything?

I'm put off too.

Also the semicolon at the end? This is because we're actually defining a variable (getAiUsePower) as this function. Defining a variable is a code statement. We need semicolons after each code statement so the computer knows where to end each block of code. This is a property of c++ and java as well as javascript.

Next segment!

== Power stuff ==
<syntaxhighlight lang="javascript" line="1" start="24">
this.init = function(co, map)
{
co.setPowerStars(3);
co.setSuperpowerStars(3);
};
</syntaxhighlight>init() is generally a function called to make sure that something is ready and to set up any needed variables. In this case, the only things that are done are setting COP stars to 3 and setting SCOP stars to 3. Note how the SCOP does not cost 3 stars, rather this is 3 stars on top of the COP cost of 3 stars, for a total of 6 stars.

Since the next function probably won't fit on the screen all at once, I'll just break it down now.<syntaxhighlight lang="javascript" line="1" start="30">
this.activatePower = function(co, map)
{
var dialogAnimation = co.createPowerSentence();
var powerNameAnimation = co.createPowerScreen(GameEnums.PowerMode_Power);
dialogAnimation.queueAnimation(powerNameAnimation);
</syntaxhighlight>The function is called activatePower, which is used when you activate power (COP specifically)

dialogAnimation and powerNameAnimation are used for the flashy effects whenever you use a power, the ones that appear, fill the screen with the power name, and disappear before your units get sparkles on them.

.queueAnimation is used to make sure that the whole screen is filled after the dialog finishes.<syntaxhighlight lang="javascript" line="1" start="36">
var units = co.getOwner().getUnits();
var animations = [];
var counter = 0;
units.randomize();
</syntaxhighlight>To go through all the units and make animations, we'll need to get all the units and have a place to store all the animations. counter is set to 0 and will correspond to animations's size (incidentally both are 0 right now)

units.randomize() makes sure that the units will be considered in a random order. Since animations happen in the same order, the animations are randomized as well.<syntaxhighlight lang="javascript" line="1" start="40">
for (var i = 0; i < units.size(); i++)
{
var unit = units.at(i);
</syntaxhighlight>The for loop will iterate through the units, with i being the index and unit being the current unit. This is randomized because units was randomized beforehand.<syntaxhighlight lang="javascript" line="1" start="44">
var animation = GameAnimationFactory.createAnimation(map, unit.getX(), unit.getY());
animation.writeDataInt32(unit.getX());
animation.writeDataInt32(unit.getY());
animation.writeDataInt32(CO_ANDY.powerHeal);
animation.setEndOfAnimationCall("ANIMATION", "postAnimationHeal");
</syntaxhighlight>Here the animation is set up. The animation is created on the map at the unit's position in createAnimation. Then the unit's position is written to the animation and CO_ANDY.powerHeal. powerHeal is an integer specifying the COP healing, in this case 2. The variable is useful to avoid "magic numbers", constant values that are typed in directly. If you want to change a magic number, you have to manually go into the code and edit every instance of that magic number. Keeping your constants in variables like CO_ANDY.powerHeal allows you to change the value quickly and easily from one place. You'll see variables like this later in the code.

Note: CO_<co name> is standard convention for CO variables. Often, you'll store important variables for your CO on CO_<co name> like CO_ANDY.powerHeal. CO_<co name> is how other scripts are going to access your CO, and how your own script accesses your CO.

At the end of the animation, the units will be healed for 2 hp. postAnimationHeal uses the prior three values to know what position to heal as well as how much to heal. setEndOfAnimationCall tells the animation engine to call a function (in this case postAnimationHeal) from an object (ANIMATION) at the end of the animation. Here's the actual postAnimationHeal if you're curious. [https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/general/animation.js]

Before going any further into the animation code, I want to go into the big picture of what is actually happening.

So first of all, when an animation is created, it's going to be handled by the Commander Wars engine no matter what. It doesn't matter if no variable in your script points to it, it's going to be saved in the core game and the core game will handle it.

The power animation for the units goes something like this: make an animation for every unit in a random order, but don't have more than 5 animations going on at the same time.

With that out of the way, here's the rest of the code<syntaxhighlight lang="javascript" line="1" start="49">
var delay = globals.randInt(135, 265);
if (animations.length < 5)
{
delay *= i;
}
animation.setSound("power0.wav", 1, delay);
</syntaxhighlight>delay is set to some random number between 135 and 265. Then, if the animation queue isn't filled (length is 5), multiply the delay by i.

What delay *= i will do is approximately make sure that the animations are in order. Say we happen to roll 200 3 times, the delays would be 200 (start at 200), 400, and 600. This will make the animations appear one after the other, kind of like how it works in the original advance wars. I'll explain what happens if the delay isn't multiplied later.

animation.setSound("power0.wav", 1, delay) sets the sound of the animation. power0.wav is the filename of the sound, 1 is the number of times to repeat (1 means 1 play) and delay is how delayed it is. If you want, I believe you can add another number for volume and also set if the oldest sound should be stopped. (animation.setSound("filename", repeats, delay, volume, stopOldestSound))<syntaxhighlight lang="javascript" line="1" start="55">
if (animations.length < 5)
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
powerNameAnimation.queueAnimation(animation);
animations.push(animation);
}
</syntaxhighlight>animations.length < 5 means the animation queue isn't full. It then adds a sprite (power0) and positions it accordingly.

Looking at the source of addSprite [https://github.com/Robosturm/Commander_Wars/blob/master/game/gameanimation/gameanimation.cpp], it offsets the image so that the unit is in the center (-map.getImageSize()*1.27) (both of them), sets sleepAfterFinish (0 is no I think), sets the scale (2) and adds delay (delay). There's another parameter for loops, which would probably set repeats if you want the image to show up more than once.

powerNameAnimation.queueAnimation(animation) sets the current animation to fire right after powerNameAnimation (the screen fill with your power name). But while the animation starts right away internally, the sound and image are delayed (thanks to delay) so what you see and hear on screen actually starts a bit later (which is probably what you want). queueAnimation() is a function attached to the animation class in general, so don't be confused if you see a different animation object using this function.

animations.push(animation) sticks the current animation at the end of the animations list. This will become very relevant shortly.<syntaxhighlight lang="javascript" line="1" start="61">
else
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
animations[counter].queueAnimation(animation);
animations[counter] = animation;
counter++;
if (counter >= animations.length)
{
counter = 0;
}
}
</syntaxhighlight>else is for if the statement in the if block isn't true (in this case animations.length < 5). This would mean that the animation queue is full.

Just to recap, delay has not been multiplied by i, counter is the index of some animation in animation, and animations is full of animations.

We've seen the addSprite method before. What's different is animations[counter].queueAnimation(animation). Here, the current animation is set to fire right after animations[counter] finishes. Then the current animation replaces the old animation, and counter increases by 1. (++ does that) If counter >= animations.length (animations[counter] would throw an error), just set it back to 0.

Was that confusing? Here's a step by step diagram.

Right before the first instance of this, animations is filled with [0,1,2,3,4]. (not actually those numbers, just animations 0, 1, 2, 3, and 4)

On the first iteration of this else statement, counter is 0, so animation 0 will set 5 to fire right after it, then 5 takes 0's place. counter increases by 1.

The list looks like this: [5,1,2,3,4], and counter is 1 now.

Next iteration: [5,6,2,3,4] (6 is queued after 1, counter is 2)

Skip forwards a bit: [5,6,7,8,4] (7 after 2, 8 after 3, counter is 4)

Now the animations will do their dance [5,6,7,8,9], and counter increases by 1 to 5.

But animations[5] is not valid (remember 0 indexing), so counter is set back to 0, and the cycle repeats.

The delay works here, because we have 0,5,10,15 going "1 delay" after each other, 1,6,11,16 going "1 delay" after each other (but 1 is delayed by "1 delay" relative to 0) and the rest is similar. If you don't think this is good, feel free to mess around with the code and see what happens.<syntaxhighlight lang="javascript" line="1" start="72">
}
};
</syntaxhighlight>And that's that function done.

activateSuperpower is actually pretty similar, using much of the same mechanics to do basically the same thing.

Notable changes:<syntaxhighlight lang="javascript" line="1" start="92">
animation.writeDataInt32(CO_ANDY.superPowerHeal);
</syntaxhighlight>When using the SCOP, we use the superPowerHeal rather than the regular power heal.<syntaxhighlight lang="javascript" line="1" start="95">
if (animations.length < 7)
</syntaxhighlight>bigger queue, more animations at once<syntaxhighlight lang="javascript" line="1" start="99">
if (i % 2 === 0)
{
animation.setSound("power12_1.wav", 1, delay);
}
else
{
animation.setSound("power12_2.wav", 1, delay);
}

</syntaxhighlight>We have two sounds! i%2===0 will be true every other iteration, so we alternate between the two sounds.<syntaxhighlight lang="javascript" line="1" start="109">
animation.addSprite("power12", -map.getImageSize() * 2, -map.getImageSize() * 2, 0, 2, delay);
</syntaxhighlight>Different image, and the offset is bigger (because the image is bigger)

Again, it was basically the same thing, but with SCOP stuff.

You're asking how long the next functions are going to be?

Not very long actually, they're far simpler and mostly just for returning numbers.

== Music and Modifiers ==
Most of these functions will return a value. Not much logic in these.<syntaxhighlight lang="javascript" line="1" start="127">
this.loadCOMusic = function(co, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Power:
audio.addMusic("resources/music/cos/power.mp3", 992, 45321);
break;
case GameEnums.PowerMode_Superpower:
audio.addMusic("resources/music/cos/superpower.mp3", 1505, 49515);
break;
case GameEnums.PowerMode_Tagpower:
audio.addMusic("resources/music/cos/tagpower.mp3", 14611, 65538);
break;
default:
audio.addMusic("resources/music/cos/andy.mp3", 4466, 74972);
break;
}
}
};
</syntaxhighlight>co.getPowerMode() returns something based on what power is activated.

switch statements execute different code based on the input value. In this case that would be the power mode.

This format (a switch statement using the power mode) is actually the standard way of doing different things if your power is active or not. You don't have to memorize it, just copy-paste it a bunch.

audio.addMusic plays the music (in a loop presumably) from startTime (in milliseconds) to endTime (in milliseconds).

The break statements prevent the code from considering other cases once one case has been run.<syntaxhighlight lang="javascript" line="1" start="149">
this.getCOUnitRange = function(co, map)
{
return 3;
};
this.getCOArmy = function()
{
return "OS";
};
</syntaxhighlight>getCOUnitRange should return the CO zone range, in this case 3.

getCOArmy should return a string corresponding to the co's country. In this case Andy is from Orange Star, so this function returns "OS". You can check other COs for their country's strings. <syntaxhighlight lang="javascript" line="1" start="158">
this.superPowerHeal = 5;
this.superPowerOffBonus = 30;
this.superPowerMovementBonus = 1;

this.powerDefBonus = 20;
this.powerOffBonus = 20;
this.powerHeal = 2;

this.d2dCoZoneOffBonus = 20;
this.d2dCoZoneDefBonus = 20;
</syntaxhighlight>These are variables for easy modification of Andy's numbers. If you check the in-game wiki, these numbers should line up with what you see there. As stated above, these variables make sure you don't accidentally change the numbers in one place but not another.<syntaxhighlight lang="javascript" line="1" start="169">
this.getOffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isDefender, action, luckmode, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Tagpower:
case GameEnums.PowerMode_Superpower:
return CO_ANDY.superPowerOffBonus;
case GameEnums.PowerMode_Power:
return CO_ANDY.powerOffBonus;
default:
if (co.inCORange(Qt.point(atkPosX, atkPosY), attacker))
{
return CO_ANDY.d2dCoZoneOffBonus;
}
break;
}
}
return 0;
};
</syntaxhighlight>getOffensiveBonus is called when you want to find the offensive bonus of a specific unit. There are a lot of parameters for this function, but honestly most of them are pretty self-explanatory (what do you expect defender to be).

if (CO.isActive(co)) just makes sure your CO is actually active and should be used.

The switch statement is explained above. In this case, it changes the offensive bonus depending on if the power is active or not.

Note the co.inCORange() function. This is a very easy way to check if a unit is in the CO zone or not. You may be curious why this check isn't in any other case. In the original AW DoR, where CO zones were first introduced, CO zones became global while using powers. This is carried over to COW, so not only would the check be redundant (you can be sure your unit is in the map-wide zone), it may not even work (sometimes when a CO unit is moved during powers, the zone shows up as range 0).

Also the break statement at the end. This is best practice in switch statements, as it ensures you get out of the switch right away and not accidentally fall into other cases. You don't need to do this after a return statement, because return sends you out of the function as well as the switch.<syntaxhighlight lang="javascript" line="1" start="191">
this.getDeffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isAttacker, action, luckmode, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() > GameEnums.PowerMode_Off)
{
return CO_ANDY.powerDefBonus;
}
else if (co.inCORange(Qt.point(defPosX, defPosY), defender))
{
return CO_ANDY.d2dCoZoneDefBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, except for one thing.

A funny thing about enums, they're actually numbers.

This allows for funky stuff like co.getPowerMode() > GameEnums.PowerMode_Off. This will be true if either CO power is active.

I don't personally use this, but this is an alternative to a switch statement.<syntaxhighlight lang="javascript" line="1" start="207">
this.getMovementpointModifier = function(co, unit, posX, posY, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() === GameEnums.PowerMode_Superpower ||
co.getPowerMode() === GameEnums.PowerMode_Tagpower)
{
return CO_ANDY.superPowerMovementBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, again

Since movement takes place outside of combat, you don't have attacker, attackerX, defender, and defenderY (some variables skipped for brevity). Instead you just have the unit you're moving. This shouldn't be too relevant, but beware accidentally copying attacker and not replacing it with unit.<syntaxhighlight lang="javascript" line="1" start="220">
this.getCOUnits = function(co, building, map)
{
if (CO.isActive(co))
{
var buildingId = building.getBuildingID();
if (buildingId === "FACTORY" ||
buildingId === "TOWN" ||
BUILDING.isHq(building))
{
return ["ZCOUNIT_REPAIR_TANK"];
}
}
return [];
};
</syntaxhighlight>This function gets your exclusive CO units. In Andy's case, we have repair tanks (internal ID ZCOUNIT_REPAIR_TANK). But since it's a land unit, we don't want to build it out of any building (as much as I think Andy forgetting what an airport is supposed to do is funny).

So we check the buildingId. For compatibility with Hachi and Hachi's soul, we also add the repair tank to the build lists of towns and hqs, even though they can't build anything.<syntaxhighlight lang="javascript" line="1" start="234">
this.getAiCoUnitBonus = function(co, unit, map)
{
return 1;
};
</syntaxhighlight>I actually had to look up what this does. If we step away from Andy for a bit and go to Sami's code [https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_sami.js#L305]:<syntaxhighlight lang="javascript" line="1" start="305">
this.getAiCoUnitBonus = function(co, unit, map)
{
if (unit.getUnitID() !== "INFANTRY")
{
if (unit.getUnitType() === GameEnums.UnitType_Infantry)
{
return 8;
}
else if (unit.getBaseMaxRange() === 1)
{
return -1;
}
}
return 2;
};
</syntaxhighlight>It quickly becomes apparent what this method is used for. If the unit is an infantry, skip the if statement and return 2. If the unit is of type infantry (but not the 1k infantry, something like a commando), return 8. If it's a direct unit, return -1. And if it's an indirect, you go outside of the if statement and return 2.

In short, Sami prefers infantry type over infantry and indirects, and those over direct units (for CO units) (Thanks Sami!)

Andy returns 1 no matter what, so no preference.

What a long winded way of explaining 4 lines of code.

== Bio, Description, and Details ==
<syntaxhighlight lang="javascript" line="1" start="239">
// CO - Intel
this.getBio = function(co)
{
return qsTr("A whiz with a wrench, this mechanical boy wonder earned fame as the hero who saved Macro Land in the last great war.");
};
</syntaxhighlight>Now we get to the CO information. This just returns a string. What's interesting is the use of the function qsTr. This converts the string into a format that's easier to display, so just put it around the test you're displaying and you're good to go.<syntaxhighlight lang="javascript" line="1" start="244">
this.getHits = function(co)
{
return qsTr("Mechanics");
};
this.getMiss = function(co)
{
return qsTr("Waking up too early");
};
this.getCODescription = function(co)
{
return qsTr("No real weaknesses or strengths. Ready to fight wherever and whenever.");
};
</syntaxhighlight>More bio.

getCODescription is where you'll put a short description of your CO. Nothing long and no numbers, just tell the user the basics. Also useful for more flavor text.<syntaxhighlight lang="javascript" line="1" start="256">
this.getLongCODescription = function()
{
var text = qsTr("\nSpecial Unit:\nRepair Tanks\n") +
qsTr("\nGlobal Effect: \nNone.") +
qsTr("\n\nCO Zone Effect: \nAndy's units gain +%0% firepower and +%1% defence.");
text = replaceTextArgs(text, [CO_ANDY.d2dCoZoneOffBonus, CO_ANDY.d2dCoZoneDefBonus]);
return text;
};
</syntaxhighlight>Predictably, the long CO description, but this time with numbers!

var text is just a temporary placeholder, the name isn't important

You can join strings to each other with the + operator. You don't have to do this, but here it makes the text easier to read (code-side, there should be no difference on screen). \n is the newline symbol, which makes a newline. You can get more info on strings on google.

What's the %0% doing in the string? It's used by the replaceTextArgs to substitute the proper bonus numbers into the description. Specifically, %0% says "insert the thing in index 0 of the list of objects here". In this case, it's easy to see that CO_ANDY.d2dCoZoneOffBonus is the first object in the list. Similar idea with %1%.

Doing this rather than hardcoding the numbers into the string makes it easier to change the stats of the CO without messing up the description. You can hardcode the numbers if you like, just remember they're there.<syntaxhighlight lang="javascript" line="1" start="264">
this.getPowerDescription = function(co)
{
var text = qsTr("Restores +%0 HP to all of Andy's units. His units gain +%1% firepower and +%2% defence.");
text = replaceTextArgs(text, [CO_ANDY.powerHeal, CO_ANDY.powerOffBonus, CO_ANDY.powerDefBonus]);
return text;
};
this.getPowerName = function(co)
{
return qsTr("Hyper Repair");
};
</syntaxhighlight>Power description and power name. What else is there to say.<syntaxhighlight lang="javascript" line="1" start="274">
this.getSuperPowerDescription = function(co)
{
var text = qsTr("Restores +%0 HP to all of Andy's units. His units gain +%2 movement, +%1% firepower, and +%3% defence.");
text = replaceTextArgs(text, [CO_ANDY.superPowerHeal, CO_ANDY.superPowerOffBonus, CO_ANDY.superPowerMovementBonus, CO_ANDY.powerDefBonus]);
return text;
};
this.getSuperPowerName = function(co)
{
return qsTr("Hyper Upgrade");
};
</syntaxhighlight>The super power. Spicy I know<syntaxhighlight lang="javascript" line="1" start="284">
this.getPowerSentences = function(co)
{
return [qsTr("I've got parts to spare!"),
qsTr("I'm not giving up!"),
qsTr("Time to roll up my sleeves!"),
qsTr("I haven't even cranked the engine yet!"),
qsTr("Pass me my wrench!"),
qsTr("It's time for a tune-up!"),
qsTr("Never give up, and never lose! I'm on my way!"),
qsTr("I'm not worried! I can fix anything!")];
};
</syntaxhighlight>When you use a power, the CO says something before actually using it. What that something is comes from here.

Just return a list of strings (using []), the hard part is thinking of what to say.<syntaxhighlight lang="javascript" line="1" start="295">
this.getVictorySentences = function(co)
{
return [qsTr("We won! Woohoo!"),
qsTr("I can fix anything!"),
qsTr("I did it! Did you see that!?")];
};
this.getDefeatSentences = function(co)
{
return [qsTr("Oh, come on!"),
qsTr("Next time I see you, you're in trouble!")];
};
</syntaxhighlight>There are a surprising number of words that go into making a CO aren't there?<syntaxhighlight lang="javascript" line="1" start="306">
this.getName = function()
{
return qsTr("Andy");
};
}
</syntaxhighlight>Just to confirm, we are in fact looking at Andy's code.

Also the closing bracket of the original Constructor function. How long ago was that?

== Footer ==
Now for two vital lines of code:<syntaxhighlight lang="javascript" line="1" start="312">
Constructor.prototype = CO;
var CO_ANDY = new Constructor();
</syntaxhighlight>We set the type of constructor to CO. This tells COW that this is a CO and not some weirdly shaped unit.

Then we set the var CO_ANDY to a new instance of Constructor. This makes CO_ANDY and actual CO object, and not just the blueprints of how to make Andy. CO_ANDY is where COW (and other scripts) will reference your CO from now on.

And with those two lines, we are finished!

== Endnote ==
If you made it to the end, congrats! You now know the details of how Andy's code works and (hopefully) how to make your own.

What's that? You don't know how to make stuff affect different kinds of units?

Uh...

Maybe I should do this for Max as well.

Anyways, that's it for this guide. Have a nice day!
[[Category:Modding tutorials]]

Andy Breakdown

2023-12-31T13:17:01Z

MrDuck557: Sami's code incorrect, fixed

'''Notice: Modding tutorials assume you know at least the basics of coding or scripting. Commander Wars uses Javascript as the Scripting Language.''' In case you want to learn more about Javascript, you can check the tutorial here: Derek Banas' Javascript tutorial , purchase O'Reilly's excellent book on the subject JavaScript: The Definitive Guide, or check out W3 Schools Interactive Tutorials

'''This tutorial references https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_andy.js, the source code of the actual vanilla Andy in COW.'''

== Small Disclaimer ==
This will only go through vanilla Andy's js code, and not any other files. This is intended for newer players to understand the workings of what the code they're copy-pasting actually does. If you want to make a brand new CO in a mod, a good starting point is [[Custom CO]]. Alternatively, download a mod and edit to suit your needs.

Also I refer to normal CO powers as COP and super CO powers as SCOP, just clearing that up

== Some stuff in the header ==
<syntaxhighlight lang="javascript" line="1" start="1">
var Constructor = function()
{
</syntaxhighlight>The very first line (or two) of code. This defines a variable called Constructor to be a function. What does the function do? It's defined in the curly brackets {} following it. Notice how only the opening bracket is present. This is a long function (the whole CO).<syntaxhighlight lang="javascript" line="1" start="3">
this.getCOStyles = function()
{
return ["+alt", "+alt2", "+alt3"];
};
</syntaxhighlight>Due to some js... weirdness, we treat functions as objects that you can define properties of. If we called Constructor.getCOStyles() after finishing the Constructor function, we would get this. Specifically it would return ["+alt", "+alt2", "+alt3"]. This is telling the game to look for alternate CO images labeled "andy+alt", "andy+alt2", and "andy+alt3" as well as simply "andy". If you look in the corresponding images folder ([https://github.com/Robosturm/Commander_Wars/tree/master/resources/images/co/os]), we do actually find said images. This is Commander Wars's way to get CO styles, so if you want to have extra costumes for your CO, this is how you do it.<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
}
};
</syntaxhighlight>This is a custom function for the AI behavior of Andy. If it looks scary, that's because <s>it kinda is</s> there's just a bunch of variables and if statements flying around. Let's break this down further<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{

</syntaxhighlight>Again, a function definition. But this time, with words inside the function() brackets. Those are called parameters, and how you can pass data into a function. Here, the game is passing in:

* The CO (co) (specifically the player's instance of a CO, in an andy mirror match both andys are actually considered different COs)
* The power charge more than what the COP needs (powerSurplus)
* The count of all owned units on the field (unitCount)
* Count of all units less than 10hp (repairUnits)
* Count of all units that can shoot at more than 1 range (indirectUnits)
* Count of all units not an indirect unit (directUnits)
* The number of enemy units
* The turn mode of the AI, set to start of day, during the day, and end of day.

The vast majority of the time, a significant portion of these will not be used (for example, Andy doesn't really care if his units are direct or indirect, so long as they're repaired)<syntaxhighlight lang="javascript" line="1" start="10">
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{

</syntaxhighlight>This checks that the turn mode is start of day. This makes sure that Andy only ever uses his power at the start of each day.<syntaxhighlight lang="javascript" line="1" start="12">
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
</syntaxhighlight>If Andy can use his SCOP of course he uses his SCOP<syntaxhighlight>
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
</syntaxhighlight>If Andy has at most 0.5 stars more than his COP (and if he can use his COP in the first place), return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);?

Referencing CO.getAiUsePowerAtUnitCount, it first checks if turnMode is equal to start of day, and also if repairUnits (in Andy's getAiUsePower at least, the name is changed during the function call to unitCount) is at least 5.

If either of these conditions are not fulfilled, don't use any power.

If both of these conditions are fulfilled, use SCOP is possible, and use COP if powerSurplus <= 0.5 (and if COP is usable in the first place)

So essentially, Andy doesn't want to Hyper Repair unless he has just enough power charge and if he can repair at least 5 units.<syntaxhighlight lang="javascript" line="1" start="21">
}
};
</syntaxhighlight>Closing brackets you always need those

You may be put off at the lack of a return statement here. Won't the code break if the function doesn't return anything?

I'm put off too.

Also the semicolon at the end? This is because we're actually defining a variable (getAiUsePower) as this function. Defining a variable is a code statement. We need semicolons after each code statement so the computer knows where to end each block of code. This is a property of c++ and java as well as javascript.

Next segment!

== Power stuff ==
<syntaxhighlight lang="javascript" line="1" start="24">
this.init = function(co, map)
{
co.setPowerStars(3);
co.setSuperpowerStars(3);
};
</syntaxhighlight>init() is generally a function called to make sure that something is ready and to set up any needed variables. In this case, the only things that are done are setting COP stars to 3 and setting SCOP stars to 3. Note how the SCOP does not cost 3 stars, rather this is 3 stars on top of the COP cost of 3 stars, for a total of 6 stars.

Since the next function probably won't fit on the screen all at once, I'll just break it down now.<syntaxhighlight lang="javascript" line="1" start="30">
this.activatePower = function(co, map)
{
var dialogAnimation = co.createPowerSentence();
var powerNameAnimation = co.createPowerScreen(GameEnums.PowerMode_Power);
dialogAnimation.queueAnimation(powerNameAnimation);
</syntaxhighlight>The function is called activatePower, which is used when you activate power (COP specifically)

dialogAnimation and powerNameAnimation are used for the flashy effects whenever you use a power, the ones that appear, fill the screen with the power name, and disappear before your units get sparkles on them.

.queueAnimation is used to make sure that the whole screen is filled after the dialog finishes.<syntaxhighlight lang="javascript" line="1" start="36">
var units = co.getOwner().getUnits();
var animations = [];
var counter = 0;
units.randomize();
</syntaxhighlight>To go through all the units and make animations, we'll need to get all the units and have a place to store all the animations. counter is set to 0 and will correspond to animations's size (incidentally both are 0 right now)

units.randomize() makes sure that the units will be considered in a random order. Since animations happen in the same order, the animations are randomized as well.<syntaxhighlight lang="javascript" line="1" start="40">
for (var i = 0; i < units.size(); i++)
{
var unit = units.at(i);
</syntaxhighlight>The for loop will iterate through the units, with i being the index and unit being the current unit. This is randomized because units was randomized beforehand.<syntaxhighlight lang="javascript" line="1" start="44">
var animation = GameAnimationFactory.createAnimation(map, unit.getX(), unit.getY());
animation.writeDataInt32(unit.getX());
animation.writeDataInt32(unit.getY());
animation.writeDataInt32(CO_ANDY.powerHeal);
animation.setEndOfAnimationCall("ANIMATION", "postAnimationHeal");
</syntaxhighlight>Here the animation is set up. The animation is created on the map at the unit's position in createAnimation. Then the unit's position is written to the animation and CO_ANDY.powerHeal. powerHeal is an integer specifying the COP healing, in this case 2. The variable is useful to avoid "magic numbers", constant values that are typed in directly. If you want to change a magic number, you have to manually go into the code and edit every instance of that magic number. Keeping your constants in variables like CO_ANDY.powerHeal allows you to change the value quickly and easily from one place. You'll see variables like this later in the code.

Note: CO_<co name> is standard convention for CO variables. Often, you'll store important variables for your CO on CO_<co name> like CO_ANDY.powerHeal. CO_<co name> is how other scripts are going to access your CO, and how your own script accesses your CO.

At the end of the animation, the units will be healed for 2 hp. postAnimationHeal uses the prior three values to know what position to heal as well as how much to heal. setEndOfAnimationCall tells the animation engine to call a function (in this case postAnimationHeal) from an object (ANIMATION) at the end of the animation. Here's the actual postAnimationHeal if you're curious. [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/resources/scripts/general/animation.js#L4]

Before going any further into the animation code, I want to go into the big picture of what is actually happening.

So first of all, when an animation is created, it's going to be handled by the Commander Wars engine no matter what. It doesn't matter if no variable in your script points to it, it's going to be saved in the core game and the core game will handle it.

The power animation for the units goes something like this: make an animation for every unit in a random order, but don't have more than 5 animations going on at the same time.

With that out of the way, here's the rest of the code<syntaxhighlight lang="javascript" line="1" start="49">
var delay = globals.randInt(135, 265);
if (animations.length < 5)
{
delay *= i;
}
animation.setSound("power0.wav", 1, delay);
</syntaxhighlight>delay is set to some random number between 135 and 265. Then, if the animation queue isn't filled (length is 5), multiply the delay by i.

What delay *= i will do is approximately make sure that the animations are in order. Say we happen to roll 200 3 times, the delays would be 200 (start at 200), 400, and 600. This will make the animations appear one after the other, kind of like how it works in the original advance wars. I'll explain what happens if the delay isn't multiplied later.

animation.setSound("power0.wav", 1, delay) sets the sound of the animation. power0.wav is the filename of the sound, 1 is the number of times to repeat (1 means 1 play) and delay is how delayed it is. If you want, I believe you can add another number for volume and also set if the oldest sound should be stopped. (animation.setSound("filename", repeats, delay, volume, stopOldestSound))<syntaxhighlight lang="javascript" line="1" start="55">
if (animations.length < 5)
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
powerNameAnimation.queueAnimation(animation);
animations.push(animation);
}
</syntaxhighlight>animations.length < 5 means the animation queue isn't full. It then adds a sprite (power0) and positions it accordingly.

Looking at the source of addSprite [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/game/gameanimation/gameanimation.cpp], it offsets the image so that the unit is in the center (-map.getImageSize()*1.27) (both of them), sets sleepAfterFinish (0 is no I think), sets the scale (2) and adds delay (delay). There's another parameter for loops, which would probably set repeats if you want the image to show up more than once.

powerNameAnimation.queueAnimation(animation) sets the current animation to fire right after powerNameAnimation (the screen fill with your power name). But while the animation starts right away internally, the sound and image are delayed (thanks to delay) so what you see and hear on screen actually starts a bit later (which is probably what you want). queueAnimation() is a function attached to the animation class in general, so don't be confused if you see a different animation object using this function.

animations.push(animation) sticks the current animation at the end of the animations list. This will become very relevant shortly.<syntaxhighlight lang="javascript" line="1" start="61">
else
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
animations[counter].queueAnimation(animation);
animations[counter] = animation;
counter++;
if (counter >= animations.length)
{
counter = 0;
}
}
</syntaxhighlight>else is for if the statement in the if block isn't true (in this case animations.length < 5). This would mean that the animation queue is full.

Just to recap, delay has not been multiplied by i, counter is the index of some animation in animation, and animations is full of animations.

We've seen the addSprite method before. What's different is animations[counter].queueAnimation(animation). Here, the current animation is set to fire right after animations[counter] finishes. Then the current animation replaces the old animation, and counter increases by 1. (++ does that) If counter >= animations.length (animations[counter] would throw an error), just set it back to 0.

Was that confusing? Here's a step by step diagram.

Right before the first instance of this, animations is filled with [0,1,2,3,4]. (not actually those numbers, just animations 0, 1, 2, 3, and 4)

On the first iteration of this else statement, counter is 0, so animation 0 will set 5 to fire right after it, then 5 takes 0's place. counter increases by 1.

The list looks like this: [5,1,2,3,4], and counter is 1 now.

Next iteration: [5,6,2,3,4] (6 is queued after 1, counter is 2)

Skip forwards a bit: [5,6,7,8,4] (7 after 2, 8 after 3, counter is 4)

Now the animations will do their dance [5,6,7,8,9], and counter increases by 1 to 5.

But animations[5] is not valid (remember 0 indexing), so counter is set back to 0, and the cycle repeats.

The delay works here, because we have 0,5,10,15 going "1 delay" after each other, 1,6,11,16 going "1 delay" after each other (but 1 is delayed by "1 delay" relative to 0) and the rest is similar. If you don't think this is good, feel free to mess around with the code and see what happens.<syntaxhighlight lang="javascript" line="1" start="72">
}
};
</syntaxhighlight>And that's that function done.

activateSuperpower is actually pretty similar, using much of the same mechanics to do basically the same thing.

Notable changes:<syntaxhighlight lang="javascript" line="1" start="92">
animation.writeDataInt32(CO_ANDY.superPowerHeal);
</syntaxhighlight>When using the SCOP, we use the superPowerHeal rather than the regular power heal.<syntaxhighlight lang="javascript" line="1" start="95">
if (animations.length < 7)
</syntaxhighlight>bigger queue, more animations at once<syntaxhighlight lang="javascript" line="1" start="99">
if (i % 2 === 0)
{
animation.setSound("power12_1.wav", 1, delay);
}
else
{
animation.setSound("power12_2.wav", 1, delay);
}

</syntaxhighlight>We have two sounds! i%2===0 will be true every other iteration, so we alternate between the two sounds.<syntaxhighlight lang="javascript" line="1" start="109">
animation.addSprite("power12", -map.getImageSize() * 2, -map.getImageSize() * 2, 0, 2, delay);
</syntaxhighlight>Different image, and the offset is bigger (because the image is bigger)

Again, it was basically the same thing, but with SCOP stuff.

You're asking how long the next functions are going to be?

Not very long actually, they're far simpler and mostly just for returning numbers.

== Music and Modifiers ==
Most of these functions will return a value. Not much logic in these.<syntaxhighlight lang="javascript" line="1" start="127">
this.loadCOMusic = function(co, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Power:
audio.addMusic("resources/music/cos/power.mp3", 992, 45321);
break;
case GameEnums.PowerMode_Superpower:
audio.addMusic("resources/music/cos/superpower.mp3", 1505, 49515);
break;
case GameEnums.PowerMode_Tagpower:
audio.addMusic("resources/music/cos/tagpower.mp3", 14611, 65538);
break;
default:
audio.addMusic("resources/music/cos/andy.mp3", 4466, 74972);
break;
}
}
};
</syntaxhighlight>co.getPowerMode() returns something based on what power is activated.

switch statements execute different code based on the input value. In this case that would be the power mode.

This format (a switch statement using the power mode) is actually the standard way of doing different things if your power is active or not. You don't have to memorize it, just copy-paste it a bunch.

audio.addMusic plays the music (in a loop presumably) from startTime (in milliseconds) to endTime (in milliseconds).

The break statements prevent the code from considering other cases once one case has been run.<syntaxhighlight lang="javascript" line="1" start="149">
this.getCOUnitRange = function(co, map)
{
return 3;
};
this.getCOArmy = function()
{
return "OS";
};
</syntaxhighlight>getCOUnitRange should return the CO zone range, in this case 3.

getCOArmy should return a string corresponding to the co's country. In this case Andy is from Orange Star, so this function returns "OS". You can check other COs for their country's strings. <syntaxhighlight lang="javascript" line="1" start="158">
this.superPowerHeal = 5;
this.superPowerOffBonus = 30;
this.superPowerMovementBonus = 1;

this.powerDefBonus = 20;
this.powerOffBonus = 20;
this.powerHeal = 2;

this.d2dCoZoneOffBonus = 20;
this.d2dCoZoneDefBonus = 20;
</syntaxhighlight>These are variables for easy modification of Andy's numbers. If you check the in-game wiki, these numbers should line up with what you see there. As stated above, these variables make sure you don't accidentally change the numbers in one place but not another.<syntaxhighlight lang="javascript" line="1" start="169">
this.getOffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isDefender, action, luckmode, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Tagpower:
case GameEnums.PowerMode_Superpower:
return CO_ANDY.superPowerOffBonus;
case GameEnums.PowerMode_Power:
return CO_ANDY.powerOffBonus;
default:
if (co.inCORange(Qt.point(atkPosX, atkPosY), attacker))
{
return CO_ANDY.d2dCoZoneOffBonus;
}
break;
}
}
return 0;
};
</syntaxhighlight>getOffensiveBonus is called when you want to find the offensive bonus of a specific unit. There are a lot of parameters for this function, but honestly most of them are pretty self-explanatory (what do you expect defender to be).

if (CO.isActive(co)) just makes sure your CO is actually active and should be used.

The switch statement is explained above. In this case, it changes the offensive bonus depending on if the power is active or not.

Note the co.inCORange() function. This is a very easy way to check if a unit is in the CO zone or not. You may be curious why this check isn't in any other case. In the original AW DoR, where CO zones were first introduced, CO zones became global while using powers. This is carried over to COW, so not only would the check be redundant (you can be sure your unit is in the map-wide zone), it may not even work (sometimes when a CO unit is moved during powers, the zone shows up as range 0).

Also the break statement at the end. This is best practice in switch statements, as it ensures you get out of the switch right away and not accidentally fall into other cases. You don't need to do this after a return statement, because return sends you out of the function as well as the switch.<syntaxhighlight lang="javascript" line="1" start="191">
this.getDeffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isAttacker, action, luckmode, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() > GameEnums.PowerMode_Off)
{
return CO_ANDY.powerDefBonus;
}
else if (co.inCORange(Qt.point(defPosX, defPosY), defender))
{
return CO_ANDY.d2dCoZoneDefBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, except for one thing.

A funny thing about enums, they're actually numbers.

This allows for funky stuff like co.getPowerMode() > GameEnums.PowerMode_Off. This will be true if either CO power is active.

I don't personally use this, but this is an alternative to a switch statement.<syntaxhighlight lang="javascript" line="1" start="207">
this.getMovementpointModifier = function(co, unit, posX, posY, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() === GameEnums.PowerMode_Superpower ||
co.getPowerMode() === GameEnums.PowerMode_Tagpower)
{
return CO_ANDY.superPowerMovementBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, again

Since movement takes place outside of combat, you don't have attacker, attackerX, defender, and defenderY (some variables skipped for brevity). Instead you just have the unit you're moving. This shouldn't be too relevant, but beware accidentally copying attacker and not replacing it with unit.<syntaxhighlight lang="javascript" line="1" start="220">
this.getCOUnits = function(co, building, map)
{
if (CO.isActive(co))
{
var buildingId = building.getBuildingID();
if (buildingId === "FACTORY" ||
buildingId === "TOWN" ||
BUILDING.isHq(building))
{
return ["ZCOUNIT_REPAIR_TANK"];
}
}
return [];
};
</syntaxhighlight>This function gets your exclusive CO units. In Andy's case, we have repair tanks (internal ID ZCOUNIT_REPAIR_TANK). But since it's a land unit, we don't want to build it out of any building (as much as I think Andy forgetting what an airport is supposed to do is funny).

So we check the buildingId. For compatibility with Hachi and Hachi's soul, we also add the repair tank to the build lists of towns and hqs, even though they can't build anything.<syntaxhighlight lang="javascript" line="1" start="234">
this.getAiCoUnitBonus = function(co, unit, map)
{
return 1;
};
</syntaxhighlight>I actually had to look up what this does. If we step away from Andy for a bit and go to Sami's code [https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_sami.js#L305]:<syntaxhighlight lang="javascript" line="1" start="305">
this.getAiCoUnitBonus = function(co, unit, map)
{
if (unit.getUnitID() !== "INFANTRY")
{
if (unit.getUnitType() === GameEnums.UnitType_Infantry)
{
return 8;
}
else if (unit.getBaseMaxRange() === 1)
{
return -1;
}
}
return 2;
};
</syntaxhighlight>It quickly becomes apparent what this method is used for. If the unit is an infantry, skip the if statement and return 2. If the unit is of type infantry (but not the 1k infantry, something like a commando), return 8. If it's a direct unit, return -1. And if it's an indirect, you go outside of the if statement and return 2.

In short, Sami prefers infantry type over infantry and indirects, and those over direct units (for CO units) (Thanks Sami!)

Andy returns 1 no matter what, so no preference.

What a long winded way of explaining 4 lines of code.

== Bio, Description, and Details ==
<syntaxhighlight lang="javascript" line="1" start="239">
// CO - Intel
this.getBio = function(co)
{
return qsTr("A whiz with a wrench, this mechanical boy wonder earned fame as the hero who saved Macro Land in the last great war.");
};
</syntaxhighlight>Now we get to the CO information. This just returns a string. What's interesting is the use of the function qsTr. This converts the string into a format that's easier to display, so just put it around the test you're displaying and you're good to go.<syntaxhighlight lang="javascript" line="1" start="244">
this.getHits = function(co)
{
return qsTr("Mechanics");
};
this.getMiss = function(co)
{
return qsTr("Waking up too early");
};
this.getCODescription = function(co)
{
return qsTr("No real weaknesses or strengths. Ready to fight wherever and whenever.");
};
</syntaxhighlight>More bio.

getCODescription is where you'll put a short description of your CO. Nothing long and no numbers, just tell the user the basics. Also useful for more flavor text.<syntaxhighlight lang="javascript" line="1" start="256">
this.getLongCODescription = function()
{
var text = qsTr("\nSpecial Unit:\nRepair Tanks\n") +
qsTr("\nGlobal Effect: \nNone.") +
qsTr("\n\nCO Zone Effect: \nAndy's units gain +%0% firepower and +%1% defence.");
text = replaceTextArgs(text, [CO_ANDY.d2dCoZoneOffBonus, CO_ANDY.d2dCoZoneDefBonus]);
return text;
};
</syntaxhighlight>Predictably, the long CO description, but this time with numbers!

var text is just a temporary placeholder, the name isn't important

You can join strings to each other with the + operator. You don't have to do this, but here it makes the text easier to read (code-side, there should be no difference on screen). \n is the newline symbol, which makes a newline. You can get more info on strings on google.

What's the %0% doing in the string? It's used by the replaceTextArgs to substitute the proper bonus numbers into the description. Specifically, %0% says "insert the thing in index 0 of the list of objects here". In this case, it's easy to see that CO_ANDY.d2dCoZoneOffBonus is the first object in the list. Similar idea with %1%.

Doing this rather than hardcoding the numbers into the string makes it easier to change the stats of the CO without messing up the description. You can hardcode the numbers if you like, just remember they're there.<syntaxhighlight lang="javascript" line="1" start="264">
this.getPowerDescription = function(co)
{
var text = qsTr("Restores +%0 HP to all of Andy's units. His units gain +%1% firepower and +%2% defence.");
text = replaceTextArgs(text, [CO_ANDY.powerHeal, CO_ANDY.powerOffBonus, CO_ANDY.powerDefBonus]);
return text;
};
this.getPowerName = function(co)
{
return qsTr("Hyper Repair");
};
</syntaxhighlight>Power description and power name. What else is there to say.<syntaxhighlight lang="javascript" line="1" start="274">
this.getSuperPowerDescription = function(co)
{
var text = qsTr("Restores +%0 HP to all of Andy's units. His units gain +%2 movement, +%1% firepower, and +%3% defence.");
text = replaceTextArgs(text, [CO_ANDY.superPowerHeal, CO_ANDY.superPowerOffBonus, CO_ANDY.superPowerMovementBonus, CO_ANDY.powerDefBonus]);
return text;
};
this.getSuperPowerName = function(co)
{
return qsTr("Hyper Upgrade");
};
</syntaxhighlight>The super power. Spicy I know<syntaxhighlight lang="javascript" line="1" start="284">
this.getPowerSentences = function(co)
{
return [qsTr("I've got parts to spare!"),
qsTr("I'm not giving up!"),
qsTr("Time to roll up my sleeves!"),
qsTr("I haven't even cranked the engine yet!"),
qsTr("Pass me my wrench!"),
qsTr("It's time for a tune-up!"),
qsTr("Never give up, and never lose! I'm on my way!"),
qsTr("I'm not worried! I can fix anything!")];
};
</syntaxhighlight>When you use a power, the CO says something before actually using it. What that something is comes from here.

Just return a list of strings (using []), the hard part is thinking of what to say.<syntaxhighlight lang="javascript" line="1" start="295">
this.getVictorySentences = function(co)
{
return [qsTr("We won! Woohoo!"),
qsTr("I can fix anything!"),
qsTr("I did it! Did you see that!?")];
};
this.getDefeatSentences = function(co)
{
return [qsTr("Oh, come on!"),
qsTr("Next time I see you, you're in trouble!")];
};
</syntaxhighlight>There are a surprising number of words that go into making a CO aren't there?<syntaxhighlight lang="javascript" line="1" start="306">
this.getName = function()
{
return qsTr("Andy");
};
}
</syntaxhighlight>Just to confirm, we are in fact looking at Andy's code.

Also the closing bracket of the original Constructor function. How long ago was that?

== Footer ==
Now for two vital lines of code:<syntaxhighlight lang="javascript" line="1" start="312">
Constructor.prototype = CO;
var CO_ANDY = new Constructor();
</syntaxhighlight>We set the type of constructor to CO. This tells COW that this is a CO and not some weirdly shaped unit.

Then we set the var CO_ANDY to a new instance of Constructor. This makes CO_ANDY and actual CO object, and not just the blueprints of how to make Andy. CO_ANDY is where COW (and other scripts) will reference your CO from now on.

And with those two lines, we are finished!

== Endnote ==
If you made it to the end, congrats! You now know the details of how Andy's code works and (hopefully) how to make your own.

What's that? You don't know how to make stuff affect different kinds of units?

Uh...

Maybe I should do this for Max as well.

Anyways, that's it for this guide. Have a nice day!
[[Category:Modding tutorials]]

Andy Breakdown

2023-12-30T20:03:03Z

MrDuck557: Endnote and removed unfinished notice

'''Notice: Modding tutorials assume you know at least the basics of coding or scripting. Commander Wars uses Javascript as the Scripting Language.''' In case you want to learn more about Javascript, you can check the tutorial here: Derek Banas' Javascript tutorial , purchase O'Reilly's excellent book on the subject JavaScript: The Definitive Guide, or check out W3 Schools Interactive Tutorials

'''This tutorial references https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_andy.js, the source code of the actual vanilla Andy in COW.'''

== Small Disclaimer ==
This will only go through vanilla Andy's js code, and not any other files. This is intended for newer players to understand the workings of what the code they're copy-pasting actually does. If you want to make a brand new CO in a mod, a good starting point is [[Custom CO]]. Alternatively, download a mod and edit to suit your needs.

Also I refer to normal CO powers as COP and super CO powers as SCOP, just clearing that up

== Some stuff in the header ==
<syntaxhighlight lang="javascript" line="1" start="1">
var Constructor = function()
{
</syntaxhighlight>The very first line (or two) of code. This defines a variable called Constructor to be a function. What does the function do? It's defined in the curly brackets {} following it. Notice how only the opening bracket is present. This is a long function (the whole CO).<syntaxhighlight lang="javascript" line="1" start="3">
this.getCOStyles = function()
{
return ["+alt", "+alt2", "+alt3"];
};
</syntaxhighlight>Due to some js... weirdness, we treat functions as objects that you can define properties of. If we called Constructor.getCOStyles() after finishing the Constructor function, we would get this. Specifically it would return ["+alt", "+alt2", "+alt3"]. This is telling the game to look for alternate CO images labeled "andy+alt", "andy+alt2", and "andy+alt3" as well as simply "andy". If you look in the corresponding images folder ([https://github.com/Robosturm/Commander_Wars/tree/master/resources/images/co/os]), we do actually find said images. This is Commander Wars's way to get CO styles, so if you want to have extra costumes for your CO, this is how you do it.<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
}
};
</syntaxhighlight>This is a custom function for the AI behavior of Andy. If it looks scary, that's because <s>it kinda is</s> there's just a bunch of variables and if statements flying around. Let's break this down further<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{

</syntaxhighlight>Again, a function definition. But this time, with words inside the function() brackets. Those are called parameters, and how you can pass data into a function. Here, the game is passing in:

* The CO (co) (specifically the player's instance of a CO, in an andy mirror match both andys are actually considered different COs)
* The power charge more than what the COP needs (powerSurplus)
* The count of all owned units on the field (unitCount)
* Count of all units less than 10hp (repairUnits)
* Count of all units that can shoot at more than 1 range (indirectUnits)
* Count of all units not an indirect unit (directUnits)
* The number of enemy units
* The turn mode of the AI, set to start of day, during the day, and end of day.

The vast majority of the time, a significant portion of these will not be used (for example, Andy doesn't really care if his units are direct or indirect, so long as they're repaired)<syntaxhighlight lang="javascript" line="1" start="10">
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{

</syntaxhighlight>This checks that the turn mode is start of day. This makes sure that Andy only ever uses his power at the start of each day.<syntaxhighlight lang="javascript" line="1" start="12">
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
</syntaxhighlight>If Andy can use his SCOP of course he uses his SCOP<syntaxhighlight>
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
</syntaxhighlight>If Andy has at most 0.5 stars more than his COP (and if he can use his COP in the first place), return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);?

Referencing CO.getAiUsePowerAtUnitCount, it first checks if turnMode is equal to start of day, and also if repairUnits (in Andy's getAiUsePower at least, the name is changed during the function call to unitCount) is at least 5.

If either of these conditions are not fulfilled, don't use any power.

If both of these conditions are fulfilled, use SCOP is possible, and use COP if powerSurplus <= 0.5 (and if COP is usable in the first place)

So essentially, Andy doesn't want to Hyper Repair unless he has just enough power charge and if he can repair at least 5 units.<syntaxhighlight lang="javascript" line="1" start="21">
}
};
</syntaxhighlight>Closing brackets you always need those

You may be put off at the lack of a return statement here. Won't the code break if the function doesn't return anything?

I'm put off too.

Also the semicolon at the end? This is because we're actually defining a variable (getAiUsePower) as this function. Defining a variable is a code statement. We need semicolons after each code statement so the computer knows where to end each block of code. This is a property of c++ and java as well as javascript.

Next segment!

== Power stuff ==
<syntaxhighlight lang="javascript" line="1" start="24">
this.init = function(co, map)
{
co.setPowerStars(3);
co.setSuperpowerStars(3);
};
</syntaxhighlight>init() is generally a function called to make sure that something is ready and to set up any needed variables. In this case, the only things that are done are setting COP stars to 3 and setting SCOP stars to 3. Note how the SCOP does not cost 3 stars, rather this is 3 stars on top of the COP cost of 3 stars, for a total of 6 stars.

Since the next function probably won't fit on the screen all at once, I'll just break it down now.<syntaxhighlight lang="javascript" line="1" start="30">
this.activatePower = function(co, map)
{
var dialogAnimation = co.createPowerSentence();
var powerNameAnimation = co.createPowerScreen(GameEnums.PowerMode_Power);
dialogAnimation.queueAnimation(powerNameAnimation);
</syntaxhighlight>The function is called activatePower, which is used when you activate power (COP specifically)

dialogAnimation and powerNameAnimation are used for the flashy effects whenever you use a power, the ones that appear, fill the screen with the power name, and disappear before your units get sparkles on them.

.queueAnimation is used to make sure that the whole screen is filled after the dialog finishes.<syntaxhighlight lang="javascript" line="1" start="36">
var units = co.getOwner().getUnits();
var animations = [];
var counter = 0;
units.randomize();
</syntaxhighlight>To go through all the units and make animations, we'll need to get all the units and have a place to store all the animations. counter is set to 0 and will correspond to animations's size (incidentally both are 0 right now)

units.randomize() makes sure that the units will be considered in a random order. Since animations happen in the same order, the animations are randomized as well.<syntaxhighlight lang="javascript" line="1" start="40">
for (var i = 0; i < units.size(); i++)
{
var unit = units.at(i);
</syntaxhighlight>The for loop will iterate through the units, with i being the index and unit being the current unit. This is randomized because units was randomized beforehand.<syntaxhighlight lang="javascript" line="1" start="44">
var animation = GameAnimationFactory.createAnimation(map, unit.getX(), unit.getY());
animation.writeDataInt32(unit.getX());
animation.writeDataInt32(unit.getY());
animation.writeDataInt32(CO_ANDY.powerHeal);
animation.setEndOfAnimationCall("ANIMATION", "postAnimationHeal");
</syntaxhighlight>Here the animation is set up. The animation is created on the map at the unit's position in createAnimation. Then the unit's position is written to the animation and CO_ANDY.powerHeal. powerHeal is an integer specifying the COP healing, in this case 2. The variable is useful to avoid "magic numbers", constant values that are typed in directly. If you want to change a magic number, you have to manually go into the code and edit every instance of that magic number. Keeping your constants in variables like CO_ANDY.powerHeal allows you to change the value quickly and easily from one place. You'll see variables like this later in the code.

Note: CO_<co name> is standard convention for CO variables. Often, you'll store important variables for your CO on CO_<co name> like CO_ANDY.powerHeal. CO_<co name> is how other scripts are going to access your CO, and how your own script accesses your CO.

At the end of the animation, the units will be healed for 2 hp. postAnimationHeal uses the prior three values to know what position to heal as well as how much to heal. setEndOfAnimationCall tells the animation engine to call a function (in this case postAnimationHeal) from an object (ANIMATION) at the end of the animation. Here's the actual postAnimationHeal if you're curious. [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/resources/scripts/general/animation.js#L4]

Before going any further into the animation code, I want to go into the big picture of what is actually happening.

So first of all, when an animation is created, it's going to be handled by the Commander Wars engine no matter what. It doesn't matter if no variable in your script points to it, it's going to be saved in the core game and the core game will handle it.

The power animation for the units goes something like this: make an animation for every unit in a random order, but don't have more than 5 animations going on at the same time.

With that out of the way, here's the rest of the code<syntaxhighlight lang="javascript" line="1" start="49">
var delay = globals.randInt(135, 265);
if (animations.length < 5)
{
delay *= i;
}
animation.setSound("power0.wav", 1, delay);
</syntaxhighlight>delay is set to some random number between 135 and 265. Then, if the animation queue isn't filled (length is 5), multiply the delay by i.

What delay *= i will do is approximately make sure that the animations are in order. Say we happen to roll 200 3 times, the delays would be 200 (start at 200), 400, and 600. This will make the animations appear one after the other, kind of like how it works in the original advance wars. I'll explain what happens if the delay isn't multiplied later.

animation.setSound("power0.wav", 1, delay) sets the sound of the animation. power0.wav is the filename of the sound, 1 is the number of times to repeat (1 means 1 play) and delay is how delayed it is. If you want, I believe you can add another number for volume and also set if the oldest sound should be stopped. (animation.setSound("filename", repeats, delay, volume, stopOldestSound))<syntaxhighlight lang="javascript" line="1" start="55">
if (animations.length < 5)
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
powerNameAnimation.queueAnimation(animation);
animations.push(animation);
}
</syntaxhighlight>animations.length < 5 means the animation queue isn't full. It then adds a sprite (power0) and positions it accordingly.

Looking at the source of addSprite [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/game/gameanimation/gameanimation.cpp], it offsets the image so that the unit is in the center (-map.getImageSize()*1.27) (both of them), sets sleepAfterFinish (0 is no I think), sets the scale (2) and adds delay (delay). There's another parameter for loops, which would probably set repeats if you want the image to show up more than once.

powerNameAnimation.queueAnimation(animation) sets the current animation to fire right after powerNameAnimation (the screen fill with your power name). But while the animation starts right away internally, the sound and image are delayed (thanks to delay) so what you see and hear on screen actually starts a bit later (which is probably what you want). queueAnimation() is a function attached to the animation class in general, so don't be confused if you see a different animation object using this function.

animations.push(animation) sticks the current animation at the end of the animations list. This will become very relevant shortly.<syntaxhighlight lang="javascript" line="1" start="61">
else
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
animations[counter].queueAnimation(animation);
animations[counter] = animation;
counter++;
if (counter >= animations.length)
{
counter = 0;
}
}
</syntaxhighlight>else is for if the statement in the if block isn't true (in this case animations.length < 5). This would mean that the animation queue is full.

Just to recap, delay has not been multiplied by i, counter is the index of some animation in animation, and animations is full of animations.

We've seen the addSprite method before. What's different is animations[counter].queueAnimation(animation). Here, the current animation is set to fire right after animations[counter] finishes. Then the current animation replaces the old animation, and counter increases by 1. (++ does that) If counter >= animations.length (animations[counter] would throw an error), just set it back to 0.

Was that confusing? Here's a step by step diagram.

Right before the first instance of this, animations is filled with [0,1,2,3,4]. (not actually those numbers, just animations 0, 1, 2, 3, and 4)

On the first iteration of this else statement, counter is 0, so animation 0 will set 5 to fire right after it, then 5 takes 0's place. counter increases by 1.

The list looks like this: [5,1,2,3,4], and counter is 1 now.

Next iteration: [5,6,2,3,4] (6 is queued after 1, counter is 2)

Skip forwards a bit: [5,6,7,8,4] (7 after 2, 8 after 3, counter is 4)

Now the animations will do their dance [5,6,7,8,9], and counter increases by 1 to 5.

But animations[5] is not valid (remember 0 indexing), so counter is set back to 0, and the cycle repeats.

The delay works here, because we have 0,5,10,15 going "1 delay" after each other, 1,6,11,16 going "1 delay" after each other (but 1 is delayed by "1 delay" relative to 0) and the rest is similar. If you don't think this is good, feel free to mess around with the code and see what happens.<syntaxhighlight lang="javascript" line="1" start="72">
}
};
</syntaxhighlight>And that's that function done.

activateSuperpower is actually pretty similar, using much of the same mechanics to do basically the same thing.

Notable changes:<syntaxhighlight lang="javascript" line="1" start="92">
animation.writeDataInt32(CO_ANDY.superPowerHeal);
</syntaxhighlight>When using the SCOP, we use the superPowerHeal rather than the regular power heal.<syntaxhighlight lang="javascript" line="1" start="95">
if (animations.length < 7)
</syntaxhighlight>bigger queue, more animations at once<syntaxhighlight lang="javascript" line="1" start="99">
if (i % 2 === 0)
{
animation.setSound("power12_1.wav", 1, delay);
}
else
{
animation.setSound("power12_2.wav", 1, delay);
}

</syntaxhighlight>We have two sounds! i%2===0 will be true every other iteration, so we alternate between the two sounds.<syntaxhighlight lang="javascript" line="1" start="109">
animation.addSprite("power12", -map.getImageSize() * 2, -map.getImageSize() * 2, 0, 2, delay);
</syntaxhighlight>Different image, and the offset is bigger (because the image is bigger)

Again, it was basically the same thing, but with SCOP stuff.

You're asking how long the next functions are going to be?

Not very long actually, they're far simpler and mostly just for returning numbers.

== Music and Modifiers ==
Most of these functions will return a value. Not much logic in these.<syntaxhighlight lang="javascript" line="1" start="127">
this.loadCOMusic = function(co, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Power:
audio.addMusic("resources/music/cos/power.mp3", 992, 45321);
break;
case GameEnums.PowerMode_Superpower:
audio.addMusic("resources/music/cos/superpower.mp3", 1505, 49515);
break;
case GameEnums.PowerMode_Tagpower:
audio.addMusic("resources/music/cos/tagpower.mp3", 14611, 65538);
break;
default:
audio.addMusic("resources/music/cos/andy.mp3", 4466, 74972);
break;
}
}
};
</syntaxhighlight>co.getPowerMode() returns something based on what power is activated.

switch statements execute different code based on the input value. In this case that would be the power mode.

This format (a switch statement using the power mode) is actually the standard way of doing different things if your power is active or not. You don't have to memorize it, just copy-paste it a bunch.

audio.addMusic plays the music (in a loop presumably) from startTime (in milliseconds) to endTime (in milliseconds).

The break statements prevent the code from considering other cases once one case has been run.<syntaxhighlight lang="javascript" line="1" start="149">
this.getCOUnitRange = function(co, map)
{
return 3;
};
this.getCOArmy = function()
{
return "OS";
};
</syntaxhighlight>getCOUnitRange should return the CO zone range, in this case 3.

getCOArmy should return a string corresponding to the co's country. In this case Andy is from Orange Star, so this function returns "OS". You can check other COs for their country's strings. <syntaxhighlight lang="javascript" line="1" start="158">
this.superPowerHeal = 5;
this.superPowerOffBonus = 30;
this.superPowerMovementBonus = 1;

this.powerDefBonus = 20;
this.powerOffBonus = 20;
this.powerHeal = 2;

this.d2dCoZoneOffBonus = 20;
this.d2dCoZoneDefBonus = 20;
</syntaxhighlight>These are variables for easy modification of Andy's numbers. If you check the in-game wiki, these numbers should line up with what you see there. As stated above, these variables make sure you don't accidentally change the numbers in one place but not another.<syntaxhighlight lang="javascript" line="1" start="169">
this.getOffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isDefender, action, luckmode, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Tagpower:
case GameEnums.PowerMode_Superpower:
return CO_ANDY.superPowerOffBonus;
case GameEnums.PowerMode_Power:
return CO_ANDY.powerOffBonus;
default:
if (co.inCORange(Qt.point(atkPosX, atkPosY), attacker))
{
return CO_ANDY.d2dCoZoneOffBonus;
}
break;
}
}
return 0;
};
</syntaxhighlight>getOffensiveBonus is called when you want to find the offensive bonus of a specific unit. There are a lot of parameters for this function, but honestly most of them are pretty self-explanatory (what do you expect defender to be).

if (CO.isActive(co)) just makes sure your CO is actually active and should be used.

The switch statement is explained above. In this case, it changes the offensive bonus depending on if the power is active or not.

Note the co.inCORange() function. This is a very easy way to check if a unit is in the CO zone or not. You may be curious why this check isn't in any other case. In the original AW DoR, where CO zones were first introduced, CO zones became global while using powers. This is carried over to COW, so not only would the check be redundant (you can be sure your unit is in the map-wide zone), it may not even work (sometimes when a CO unit is moved during powers, the zone shows up as range 0).

Also the break statement at the end. This is best practice in switch statements, as it ensures you get out of the switch right away and not accidentally fall into other cases. You don't need to do this after a return statement, because return sends you out of the function as well as the switch.<syntaxhighlight lang="javascript" line="1" start="191">
this.getDeffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isAttacker, action, luckmode, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() > GameEnums.PowerMode_Off)
{
return CO_ANDY.powerDefBonus;
}
else if (co.inCORange(Qt.point(defPosX, defPosY), defender))
{
return CO_ANDY.d2dCoZoneDefBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, except for one thing.

A funny thing about enums, they're actually numbers.

This allows for funky stuff like co.getPowerMode() > GameEnums.PowerMode_Off. This will be true if either CO power is active.

I don't personally use this, but this is an alternative to a switch statement.<syntaxhighlight lang="javascript" line="1" start="207">
this.getMovementpointModifier = function(co, unit, posX, posY, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() === GameEnums.PowerMode_Superpower ||
co.getPowerMode() === GameEnums.PowerMode_Tagpower)
{
return CO_ANDY.superPowerMovementBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, again

Since movement takes place outside of combat, you don't have attacker, attackerX, defender, and defenderY (some variables skipped for brevity). Instead you just have the unit you're moving. This shouldn't be too relevant, but beware accidentally copying attacker and not replacing it with unit.<syntaxhighlight lang="javascript" line="1" start="220">
this.getCOUnits = function(co, building, map)
{
if (CO.isActive(co))
{
var buildingId = building.getBuildingID();
if (buildingId === "FACTORY" ||
buildingId === "TOWN" ||
BUILDING.isHq(building))
{
return ["ZCOUNIT_REPAIR_TANK"];
}
}
return [];
};
</syntaxhighlight>This function gets your exclusive CO units. In Andy's case, we have repair tanks (internal ID ZCOUNIT_REPAIR_TANK). But since it's a land unit, we don't want to build it out of any building (as much as I think Andy forgetting what an airport is supposed to do is funny).

So we check the buildingId. For compatibility with Hachi and Hachi's soul, we also add the repair tank to the build lists of towns and hqs, even though they can't build anything.<syntaxhighlight lang="javascript" line="1" start="234">
this.getAiCoUnitBonus = function(co, unit, map)
{
return 1;
};
</syntaxhighlight>I actually had to look up what this does. If we step away from Andy for a bit and go to Sami's code [https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_sami.js#L305]:<syntaxhighlight lang="javascript" line="1" start="305">
this.getAiCoUnitBonus = function(co, unit, map)
{
if (unit.getUnitID !== "INFANTRY")
{
if (unit.getUnitType() === GameEnums.UnitType_Infantry)
{
return 8;
}
else if (unit.getBaseMaxRange() === 1)
{
return -1;
}
}
return 2;
};
</syntaxhighlight>It quickly becomes apparent what this method is used for. If the unit is an infantry, skip the if statement and return 2. If the unit is of type infantry (but not the 1k infantry, something like a commando), return 8. If it's a direct unit, return -1. And if it's an indirect, you go outside of the if statement and return 2.

In short, Sami prefers infantry type over infantry and indirects, and those over direct units (for CO units) (Thanks Sami!)

Andy returns 1 no matter what, so no preference.

What a long winded way of explaining 4 lines of code.

== Bio, Description, and Details ==
<syntaxhighlight lang="javascript" line="1" start="239">
// CO - Intel
this.getBio = function(co)
{
return qsTr("A whiz with a wrench, this mechanical boy wonder earned fame as the hero who saved Macro Land in the last great war.");
};
</syntaxhighlight>Now we get to the CO information. This just returns a string. What's interesting is the use of the function qsTr. This converts the string into a format that's easier to display, so just put it around the test you're displaying and you're good to go.<syntaxhighlight lang="javascript" line="1" start="244">
this.getHits = function(co)
{
return qsTr("Mechanics");
};
this.getMiss = function(co)
{
return qsTr("Waking up too early");
};
this.getCODescription = function(co)
{
return qsTr("No real weaknesses or strengths. Ready to fight wherever and whenever.");
};
</syntaxhighlight>More bio.

getCODescription is where you'll put a short description of your CO. Nothing long and no numbers, just tell the user the basics. Also useful for more flavor text.<syntaxhighlight lang="javascript" line="1" start="256">
this.getLongCODescription = function()
{
var text = qsTr("\nSpecial Unit:\nRepair Tanks\n") +
qsTr("\nGlobal Effect: \nNone.") +
qsTr("\n\nCO Zone Effect: \nAndy's units gain +%0% firepower and +%1% defence.");
text = replaceTextArgs(text, [CO_ANDY.d2dCoZoneOffBonus, CO_ANDY.d2dCoZoneDefBonus]);
return text;
};
</syntaxhighlight>Predictably, the long CO description, but this time with numbers!

var text is just a temporary placeholder, the name isn't important

You can join strings to each other with the + operator. You don't have to do this, but here it makes the text easier to read (code-side, there should be no difference on screen). \n is the newline symbol, which makes a newline. You can get more info on strings on google.

What's the %0% doing in the string? It's used by the replaceTextArgs to substitute the proper bonus numbers into the description. Specifically, %0% says "insert the thing in index 0 of the list of objects here". In this case, it's easy to see that CO_ANDY.d2dCoZoneOffBonus is the first object in the list. Similar idea with %1%.

Doing this rather than hardcoding the numbers into the string makes it easier to change the stats of the CO without messing up the description. You can hardcode the numbers if you like, just remember they're there.<syntaxhighlight lang="javascript" line="1" start="264">
this.getPowerDescription = function(co)
{
var text = qsTr("Restores +%0 HP to all of Andy's units. His units gain +%1% firepower and +%2% defence.");
text = replaceTextArgs(text, [CO_ANDY.powerHeal, CO_ANDY.powerOffBonus, CO_ANDY.powerDefBonus]);
return text;
};
this.getPowerName = function(co)
{
return qsTr("Hyper Repair");
};
</syntaxhighlight>Power description and power name. What else is there to say.<syntaxhighlight lang="javascript" line="1" start="274">
this.getSuperPowerDescription = function(co)
{
var text = qsTr("Restores +%0 HP to all of Andy's units. His units gain +%2 movement, +%1% firepower, and +%3% defence.");
text = replaceTextArgs(text, [CO_ANDY.superPowerHeal, CO_ANDY.superPowerOffBonus, CO_ANDY.superPowerMovementBonus, CO_ANDY.powerDefBonus]);
return text;
};
this.getSuperPowerName = function(co)
{
return qsTr("Hyper Upgrade");
};
</syntaxhighlight>The super power. Spicy I know<syntaxhighlight lang="javascript" line="1" start="284">
this.getPowerSentences = function(co)
{
return [qsTr("I've got parts to spare!"),
qsTr("I'm not giving up!"),
qsTr("Time to roll up my sleeves!"),
qsTr("I haven't even cranked the engine yet!"),
qsTr("Pass me my wrench!"),
qsTr("It's time for a tune-up!"),
qsTr("Never give up, and never lose! I'm on my way!"),
qsTr("I'm not worried! I can fix anything!")];
};
</syntaxhighlight>When you use a power, the CO says something before actually using it. What that something is comes from here.

Just return a list of strings (using []), the hard part is thinking of what to say.<syntaxhighlight lang="javascript" line="1" start="295">
this.getVictorySentences = function(co)
{
return [qsTr("We won! Woohoo!"),
qsTr("I can fix anything!"),
qsTr("I did it! Did you see that!?")];
};
this.getDefeatSentences = function(co)
{
return [qsTr("Oh, come on!"),
qsTr("Next time I see you, you're in trouble!")];
};
</syntaxhighlight>There are a surprising number of words that go into making a CO aren't there?<syntaxhighlight lang="javascript" line="1" start="306">
this.getName = function()
{
return qsTr("Andy");
};
}
</syntaxhighlight>Just to confirm, we are in fact looking at Andy's code.

Also the closing bracket of the original Constructor function. How long ago was that?

== Footer ==
Now for two vital lines of code:<syntaxhighlight lang="javascript" line="1" start="312">
Constructor.prototype = CO;
var CO_ANDY = new Constructor();
</syntaxhighlight>We set the type of constructor to CO. This tells COW that this is a CO and not some weirdly shaped unit.

Then we set the var CO_ANDY to a new instance of Constructor. This makes CO_ANDY and actual CO object, and not just the blueprints of how to make Andy. CO_ANDY is where COW (and other scripts) will reference your CO from now on.

And with those two lines, we are finished!

== Endnote ==
If you made it to the end, congrats! You now know the details of how Andy's code works and (hopefully) how to make your own.

What's that? You don't know how to make stuff affect different kinds of units?

Uh...

Maybe I should do this for Max as well.

Anyways, that's it for this guide. Have a nice day!
[[Category:Modding tutorials]]

Andy Breakdown

2023-12-30T20:00:41Z

MrDuck557: Finished descriptions and footer

'''Notice: Modding tutorials assume you know at least the basics of coding or scripting. Commander Wars uses Javascript as the Scripting Language.''' In case you want to learn more about Javascript, you can check the tutorial here: Derek Banas' Javascript tutorial , purchase O'Reilly's excellent book on the subject JavaScript: The Definitive Guide, or check out W3 Schools Interactive Tutorials

'''This tutorial references https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_andy.js, the source code of the actual vanilla Andy in COW.'''

'''THIS IS UNFINISHED DO NOT COMPLAIN ABOUT MISSING SECTIONS'''

== Small Disclaimer ==
This will only go through vanilla Andy's js code, and not any other files. This is intended for newer players to understand the workings of what the code they're copy-pasting actually does. If you want to make a brand new CO in a mod, a good starting point is [[Custom CO]]. Alternatively, download a mod and edit to suit your needs.

Also I refer to normal CO powers as COP and super CO powers as SCOP, just clearing that up

== Some stuff in the header ==
<syntaxhighlight lang="javascript" line="1" start="1">
var Constructor = function()
{
</syntaxhighlight>The very first line (or two) of code. This defines a variable called Constructor to be a function. What does the function do? It's defined in the curly brackets {} following it. Notice how only the opening bracket is present. This is a long function (the whole CO).<syntaxhighlight lang="javascript" line="1" start="3">
this.getCOStyles = function()
{
return ["+alt", "+alt2", "+alt3"];
};
</syntaxhighlight>Due to some js... weirdness, we treat functions as objects that you can define properties of. If we called Constructor.getCOStyles() after finishing the Constructor function, we would get this. Specifically it would return ["+alt", "+alt2", "+alt3"]. This is telling the game to look for alternate CO images labeled "andy+alt", "andy+alt2", and "andy+alt3" as well as simply "andy". If you look in the corresponding images folder ([https://github.com/Robosturm/Commander_Wars/tree/master/resources/images/co/os]), we do actually find said images. This is Commander Wars's way to get CO styles, so if you want to have extra costumes for your CO, this is how you do it.<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
}
};
</syntaxhighlight>This is a custom function for the AI behavior of Andy. If it looks scary, that's because <s>it kinda is</s> there's just a bunch of variables and if statements flying around. Let's break this down further<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{

</syntaxhighlight>Again, a function definition. But this time, with words inside the function() brackets. Those are called parameters, and how you can pass data into a function. Here, the game is passing in:

* The CO (co) (specifically the player's instance of a CO, in an andy mirror match both andys are actually considered different COs)
* The power charge more than what the COP needs (powerSurplus)
* The count of all owned units on the field (unitCount)
* Count of all units less than 10hp (repairUnits)
* Count of all units that can shoot at more than 1 range (indirectUnits)
* Count of all units not an indirect unit (directUnits)
* The number of enemy units
* The turn mode of the AI, set to start of day, during the day, and end of day.

The vast majority of the time, a significant portion of these will not be used (for example, Andy doesn't really care if his units are direct or indirect, so long as they're repaired)<syntaxhighlight lang="javascript" line="1" start="10">
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{

</syntaxhighlight>This checks that the turn mode is start of day. This makes sure that Andy only ever uses his power at the start of each day.<syntaxhighlight lang="javascript" line="1" start="12">
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
</syntaxhighlight>If Andy can use his SCOP of course he uses his SCOP<syntaxhighlight>
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
</syntaxhighlight>If Andy has at most 0.5 stars more than his COP (and if he can use his COP in the first place), return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);?

Referencing CO.getAiUsePowerAtUnitCount, it first checks if turnMode is equal to start of day, and also if repairUnits (in Andy's getAiUsePower at least, the name is changed during the function call to unitCount) is at least 5.

If either of these conditions are not fulfilled, don't use any power.

If both of these conditions are fulfilled, use SCOP is possible, and use COP if powerSurplus <= 0.5 (and if COP is usable in the first place)

So essentially, Andy doesn't want to Hyper Repair unless he has just enough power charge and if he can repair at least 5 units.<syntaxhighlight lang="javascript" line="1" start="21">
}
};
</syntaxhighlight>Closing brackets you always need those

You may be put off at the lack of a return statement here. Won't the code break if the function doesn't return anything?

I'm put off too.

Also the semicolon at the end? This is because we're actually defining a variable (getAiUsePower) as this function. Defining a variable is a code statement. We need semicolons after each code statement so the computer knows where to end each block of code. This is a property of c++ and java as well as javascript.

Next segment!

== Power stuff ==
<syntaxhighlight lang="javascript" line="1" start="24">
this.init = function(co, map)
{
co.setPowerStars(3);
co.setSuperpowerStars(3);
};
</syntaxhighlight>init() is generally a function called to make sure that something is ready and to set up any needed variables. In this case, the only things that are done are setting COP stars to 3 and setting SCOP stars to 3. Note how the SCOP does not cost 3 stars, rather this is 3 stars on top of the COP cost of 3 stars, for a total of 6 stars.

Since the next function probably won't fit on the screen all at once, I'll just break it down now.<syntaxhighlight lang="javascript" line="1" start="30">
this.activatePower = function(co, map)
{
var dialogAnimation = co.createPowerSentence();
var powerNameAnimation = co.createPowerScreen(GameEnums.PowerMode_Power);
dialogAnimation.queueAnimation(powerNameAnimation);
</syntaxhighlight>The function is called activatePower, which is used when you activate power (COP specifically)

dialogAnimation and powerNameAnimation are used for the flashy effects whenever you use a power, the ones that appear, fill the screen with the power name, and disappear before your units get sparkles on them.

.queueAnimation is used to make sure that the whole screen is filled after the dialog finishes.<syntaxhighlight lang="javascript" line="1" start="36">
var units = co.getOwner().getUnits();
var animations = [];
var counter = 0;
units.randomize();
</syntaxhighlight>To go through all the units and make animations, we'll need to get all the units and have a place to store all the animations. counter is set to 0 and will correspond to animations's size (incidentally both are 0 right now)

units.randomize() makes sure that the units will be considered in a random order. Since animations happen in the same order, the animations are randomized as well.<syntaxhighlight lang="javascript" line="1" start="40">
for (var i = 0; i < units.size(); i++)
{
var unit = units.at(i);
</syntaxhighlight>The for loop will iterate through the units, with i being the index and unit being the current unit. This is randomized because units was randomized beforehand.<syntaxhighlight lang="javascript" line="1" start="44">
var animation = GameAnimationFactory.createAnimation(map, unit.getX(), unit.getY());
animation.writeDataInt32(unit.getX());
animation.writeDataInt32(unit.getY());
animation.writeDataInt32(CO_ANDY.powerHeal);
animation.setEndOfAnimationCall("ANIMATION", "postAnimationHeal");
</syntaxhighlight>Here the animation is set up. The animation is created on the map at the unit's position in createAnimation. Then the unit's position is written to the animation and CO_ANDY.powerHeal. powerHeal is an integer specifying the COP healing, in this case 2. The variable is useful to avoid "magic numbers", constant values that are typed in directly. If you want to change a magic number, you have to manually go into the code and edit every instance of that magic number. Keeping your constants in variables like CO_ANDY.powerHeal allows you to change the value quickly and easily from one place. You'll see variables like this later in the code.

Note: CO_<co name> is standard convention for CO variables. Often, you'll store important variables for your CO on CO_<co name> like CO_ANDY.powerHeal. CO_<co name> is how other scripts are going to access your CO, and how your own script accesses your CO.

At the end of the animation, the units will be healed for 2 hp. postAnimationHeal uses the prior three values to know what position to heal as well as how much to heal. setEndOfAnimationCall tells the animation engine to call a function (in this case postAnimationHeal) from an object (ANIMATION) at the end of the animation. Here's the actual postAnimationHeal if you're curious. [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/resources/scripts/general/animation.js#L4]

Before going any further into the animation code, I want to go into the big picture of what is actually happening.

So first of all, when an animation is created, it's going to be handled by the Commander Wars engine no matter what. It doesn't matter if no variable in your script points to it, it's going to be saved in the core game and the core game will handle it.

The power animation for the units goes something like this: make an animation for every unit in a random order, but don't have more than 5 animations going on at the same time.

With that out of the way, here's the rest of the code<syntaxhighlight lang="javascript" line="1" start="49">
var delay = globals.randInt(135, 265);
if (animations.length < 5)
{
delay *= i;
}
animation.setSound("power0.wav", 1, delay);
</syntaxhighlight>delay is set to some random number between 135 and 265. Then, if the animation queue isn't filled (length is 5), multiply the delay by i.

What delay *= i will do is approximately make sure that the animations are in order. Say we happen to roll 200 3 times, the delays would be 200 (start at 200), 400, and 600. This will make the animations appear one after the other, kind of like how it works in the original advance wars. I'll explain what happens if the delay isn't multiplied later.

animation.setSound("power0.wav", 1, delay) sets the sound of the animation. power0.wav is the filename of the sound, 1 is the number of times to repeat (1 means 1 play) and delay is how delayed it is. If you want, I believe you can add another number for volume and also set if the oldest sound should be stopped. (animation.setSound("filename", repeats, delay, volume, stopOldestSound))<syntaxhighlight lang="javascript" line="1" start="55">
if (animations.length < 5)
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
powerNameAnimation.queueAnimation(animation);
animations.push(animation);
}
</syntaxhighlight>animations.length < 5 means the animation queue isn't full. It then adds a sprite (power0) and positions it accordingly.

Looking at the source of addSprite [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/game/gameanimation/gameanimation.cpp], it offsets the image so that the unit is in the center (-map.getImageSize()*1.27) (both of them), sets sleepAfterFinish (0 is no I think), sets the scale (2) and adds delay (delay). There's another parameter for loops, which would probably set repeats if you want the image to show up more than once.

powerNameAnimation.queueAnimation(animation) sets the current animation to fire right after powerNameAnimation (the screen fill with your power name). But while the animation starts right away internally, the sound and image are delayed (thanks to delay) so what you see and hear on screen actually starts a bit later (which is probably what you want). queueAnimation() is a function attached to the animation class in general, so don't be confused if you see a different animation object using this function.

animations.push(animation) sticks the current animation at the end of the animations list. This will become very relevant shortly.<syntaxhighlight lang="javascript" line="1" start="61">
else
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
animations[counter].queueAnimation(animation);
animations[counter] = animation;
counter++;
if (counter >= animations.length)
{
counter = 0;
}
}
</syntaxhighlight>else is for if the statement in the if block isn't true (in this case animations.length < 5). This would mean that the animation queue is full.

Just to recap, delay has not been multiplied by i, counter is the index of some animation in animation, and animations is full of animations.

We've seen the addSprite method before. What's different is animations[counter].queueAnimation(animation). Here, the current animation is set to fire right after animations[counter] finishes. Then the current animation replaces the old animation, and counter increases by 1. (++ does that) If counter >= animations.length (animations[counter] would throw an error), just set it back to 0.

Was that confusing? Here's a step by step diagram.

Right before the first instance of this, animations is filled with [0,1,2,3,4]. (not actually those numbers, just animations 0, 1, 2, 3, and 4)

On the first iteration of this else statement, counter is 0, so animation 0 will set 5 to fire right after it, then 5 takes 0's place. counter increases by 1.

The list looks like this: [5,1,2,3,4], and counter is 1 now.

Next iteration: [5,6,2,3,4] (6 is queued after 1, counter is 2)

Skip forwards a bit: [5,6,7,8,4] (7 after 2, 8 after 3, counter is 4)

Now the animations will do their dance [5,6,7,8,9], and counter increases by 1 to 5.

But animations[5] is not valid (remember 0 indexing), so counter is set back to 0, and the cycle repeats.

The delay works here, because we have 0,5,10,15 going "1 delay" after each other, 1,6,11,16 going "1 delay" after each other (but 1 is delayed by "1 delay" relative to 0) and the rest is similar. If you don't think this is good, feel free to mess around with the code and see what happens.<syntaxhighlight lang="javascript" line="1" start="72">
}
};
</syntaxhighlight>And that's that function done.

activateSuperpower is actually pretty similar, using much of the same mechanics to do basically the same thing.

Notable changes:<syntaxhighlight lang="javascript" line="1" start="92">
animation.writeDataInt32(CO_ANDY.superPowerHeal);
</syntaxhighlight>When using the SCOP, we use the superPowerHeal rather than the regular power heal.<syntaxhighlight lang="javascript" line="1" start="95">
if (animations.length < 7)
</syntaxhighlight>bigger queue, more animations at once<syntaxhighlight lang="javascript" line="1" start="99">
if (i % 2 === 0)
{
animation.setSound("power12_1.wav", 1, delay);
}
else
{
animation.setSound("power12_2.wav", 1, delay);
}

</syntaxhighlight>We have two sounds! i%2===0 will be true every other iteration, so we alternate between the two sounds.<syntaxhighlight lang="javascript" line="1" start="109">
animation.addSprite("power12", -map.getImageSize() * 2, -map.getImageSize() * 2, 0, 2, delay);
</syntaxhighlight>Different image, and the offset is bigger (because the image is bigger)

Again, it was basically the same thing, but with SCOP stuff.

You're asking how long the next functions are going to be?

Not very long actually, they're far simpler and mostly just for returning numbers.

== Music and Modifiers ==
Most of these functions will return a value. Not much logic in these.<syntaxhighlight lang="javascript" line="1" start="127">
this.loadCOMusic = function(co, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Power:
audio.addMusic("resources/music/cos/power.mp3", 992, 45321);
break;
case GameEnums.PowerMode_Superpower:
audio.addMusic("resources/music/cos/superpower.mp3", 1505, 49515);
break;
case GameEnums.PowerMode_Tagpower:
audio.addMusic("resources/music/cos/tagpower.mp3", 14611, 65538);
break;
default:
audio.addMusic("resources/music/cos/andy.mp3", 4466, 74972);
break;
}
}
};
</syntaxhighlight>co.getPowerMode() returns something based on what power is activated.

switch statements execute different code based on the input value. In this case that would be the power mode.

This format (a switch statement using the power mode) is actually the standard way of doing different things if your power is active or not. You don't have to memorize it, just copy-paste it a bunch.

audio.addMusic plays the music (in a loop presumably) from startTime (in milliseconds) to endTime (in milliseconds).

The break statements prevent the code from considering other cases once one case has been run.<syntaxhighlight lang="javascript" line="1" start="149">
this.getCOUnitRange = function(co, map)
{
return 3;
};
this.getCOArmy = function()
{
return "OS";
};
</syntaxhighlight>getCOUnitRange should return the CO zone range, in this case 3.

getCOArmy should return a string corresponding to the co's country. In this case Andy is from Orange Star, so this function returns "OS". You can check other COs for their country's strings. <syntaxhighlight lang="javascript" line="1" start="158">
this.superPowerHeal = 5;
this.superPowerOffBonus = 30;
this.superPowerMovementBonus = 1;

this.powerDefBonus = 20;
this.powerOffBonus = 20;
this.powerHeal = 2;

this.d2dCoZoneOffBonus = 20;
this.d2dCoZoneDefBonus = 20;
</syntaxhighlight>These are variables for easy modification of Andy's numbers. If you check the in-game wiki, these numbers should line up with what you see there. As stated above, these variables make sure you don't accidentally change the numbers in one place but not another.<syntaxhighlight lang="javascript" line="1" start="169">
this.getOffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isDefender, action, luckmode, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Tagpower:
case GameEnums.PowerMode_Superpower:
return CO_ANDY.superPowerOffBonus;
case GameEnums.PowerMode_Power:
return CO_ANDY.powerOffBonus;
default:
if (co.inCORange(Qt.point(atkPosX, atkPosY), attacker))
{
return CO_ANDY.d2dCoZoneOffBonus;
}
break;
}
}
return 0;
};
</syntaxhighlight>getOffensiveBonus is called when you want to find the offensive bonus of a specific unit. There are a lot of parameters for this function, but honestly most of them are pretty self-explanatory (what do you expect defender to be).

if (CO.isActive(co)) just makes sure your CO is actually active and should be used.

The switch statement is explained above. In this case, it changes the offensive bonus depending on if the power is active or not.

Note the co.inCORange() function. This is a very easy way to check if a unit is in the CO zone or not. You may be curious why this check isn't in any other case. In the original AW DoR, where CO zones were first introduced, CO zones became global while using powers. This is carried over to COW, so not only would the check be redundant (you can be sure your unit is in the map-wide zone), it may not even work (sometimes when a CO unit is moved during powers, the zone shows up as range 0).

Also the break statement at the end. This is best practice in switch statements, as it ensures you get out of the switch right away and not accidentally fall into other cases. You don't need to do this after a return statement, because return sends you out of the function as well as the switch.<syntaxhighlight lang="javascript" line="1" start="191">
this.getDeffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isAttacker, action, luckmode, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() > GameEnums.PowerMode_Off)
{
return CO_ANDY.powerDefBonus;
}
else if (co.inCORange(Qt.point(defPosX, defPosY), defender))
{
return CO_ANDY.d2dCoZoneDefBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, except for one thing.

A funny thing about enums, they're actually numbers.

This allows for funky stuff like co.getPowerMode() > GameEnums.PowerMode_Off. This will be true if either CO power is active.

I don't personally use this, but this is an alternative to a switch statement.<syntaxhighlight lang="javascript" line="1" start="207">
this.getMovementpointModifier = function(co, unit, posX, posY, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() === GameEnums.PowerMode_Superpower ||
co.getPowerMode() === GameEnums.PowerMode_Tagpower)
{
return CO_ANDY.superPowerMovementBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, again

Since movement takes place outside of combat, you don't have attacker, attackerX, defender, and defenderY (some variables skipped for brevity). Instead you just have the unit you're moving. This shouldn't be too relevant, but beware accidentally copying attacker and not replacing it with unit.<syntaxhighlight lang="javascript" line="1" start="220">
this.getCOUnits = function(co, building, map)
{
if (CO.isActive(co))
{
var buildingId = building.getBuildingID();
if (buildingId === "FACTORY" ||
buildingId === "TOWN" ||
BUILDING.isHq(building))
{
return ["ZCOUNIT_REPAIR_TANK"];
}
}
return [];
};
</syntaxhighlight>This function gets your exclusive CO units. In Andy's case, we have repair tanks (internal ID ZCOUNIT_REPAIR_TANK). But since it's a land unit, we don't want to build it out of any building (as much as I think Andy forgetting what an airport is supposed to do is funny).

So we check the buildingId. For compatibility with Hachi and Hachi's soul, we also add the repair tank to the build lists of towns and hqs, even though they can't build anything.<syntaxhighlight lang="javascript" line="1" start="234">
this.getAiCoUnitBonus = function(co, unit, map)
{
return 1;
};
</syntaxhighlight>I actually had to look up what this does. If we step away from Andy for a bit and go to Sami's code [https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_sami.js#L305]:<syntaxhighlight lang="javascript" line="1" start="305">
this.getAiCoUnitBonus = function(co, unit, map)
{
if (unit.getUnitID !== "INFANTRY")
{
if (unit.getUnitType() === GameEnums.UnitType_Infantry)
{
return 8;
}
else if (unit.getBaseMaxRange() === 1)
{
return -1;
}
}
return 2;
};
</syntaxhighlight>It quickly becomes apparent what this method is used for. If the unit is an infantry, skip the if statement and return 2. If the unit is of type infantry (but not the 1k infantry, something like a commando), return 8. If it's a direct unit, return -1. And if it's an indirect, you go outside of the if statement and return 2.

In short, Sami prefers infantry type over infantry and indirects, and those over direct units (for CO units) (Thanks Sami!)

Andy returns 1 no matter what, so no preference.

What a long winded way of explaining 4 lines of code.

== Bio, Description, and Details ==
<syntaxhighlight lang="javascript" line="1" start="239">
// CO - Intel
this.getBio = function(co)
{
return qsTr("A whiz with a wrench, this mechanical boy wonder earned fame as the hero who saved Macro Land in the last great war.");
};
</syntaxhighlight>Now we get to the CO information. This just returns a string. What's interesting is the use of the function qsTr. This converts the string into a format that's easier to display, so just put it around the test you're displaying and you're good to go.<syntaxhighlight lang="javascript" line="1" start="244">
this.getHits = function(co)
{
return qsTr("Mechanics");
};
this.getMiss = function(co)
{
return qsTr("Waking up too early");
};
this.getCODescription = function(co)
{
return qsTr("No real weaknesses or strengths. Ready to fight wherever and whenever.");
};
</syntaxhighlight>More bio.

getCODescription is where you'll put a short description of your CO. Nothing long and no numbers, just tell the user the basics. Also useful for more flavor text.<syntaxhighlight lang="javascript" line="1" start="256">
this.getLongCODescription = function()
{
var text = qsTr("\nSpecial Unit:\nRepair Tanks\n") +
qsTr("\nGlobal Effect: \nNone.") +
qsTr("\n\nCO Zone Effect: \nAndy's units gain +%0% firepower and +%1% defence.");
text = replaceTextArgs(text, [CO_ANDY.d2dCoZoneOffBonus, CO_ANDY.d2dCoZoneDefBonus]);
return text;
};
</syntaxhighlight>Predictably, the long CO description, but this time with numbers!

var text is just a temporary placeholder, the name isn't important

You can join strings to each other with the + operator. You don't have to do this, but here it makes the text easier to read (code-side, there should be no difference on screen). \n is the newline symbol, which makes a newline. You can get more info on strings on google.

What's the %0% doing in the string? It's used by the replaceTextArgs to substitute the proper bonus numbers into the description. Specifically, %0% says "insert the thing in index 0 of the list of objects here". In this case, it's easy to see that CO_ANDY.d2dCoZoneOffBonus is the first object in the list. Similar idea with %1%.

Doing this rather than hardcoding the numbers into the string makes it easier to change the stats of the CO without messing up the description. You can hardcode the numbers if you like, just remember they're there.<syntaxhighlight lang="javascript" line="1" start="264">
this.getPowerDescription = function(co)
{
var text = qsTr("Restores +%0 HP to all of Andy's units. His units gain +%1% firepower and +%2% defence.");
text = replaceTextArgs(text, [CO_ANDY.powerHeal, CO_ANDY.powerOffBonus, CO_ANDY.powerDefBonus]);
return text;
};
this.getPowerName = function(co)
{
return qsTr("Hyper Repair");
};
</syntaxhighlight>Power description and power name. What else is there to say.<syntaxhighlight lang="javascript" line="1" start="274">
this.getSuperPowerDescription = function(co)
{
var text = qsTr("Restores +%0 HP to all of Andy's units. His units gain +%2 movement, +%1% firepower, and +%3% defence.");
text = replaceTextArgs(text, [CO_ANDY.superPowerHeal, CO_ANDY.superPowerOffBonus, CO_ANDY.superPowerMovementBonus, CO_ANDY.powerDefBonus]);
return text;
};
this.getSuperPowerName = function(co)
{
return qsTr("Hyper Upgrade");
};
</syntaxhighlight>The super power. Spicy I know<syntaxhighlight lang="javascript" line="1" start="284">
this.getPowerSentences = function(co)
{
return [qsTr("I've got parts to spare!"),
qsTr("I'm not giving up!"),
qsTr("Time to roll up my sleeves!"),
qsTr("I haven't even cranked the engine yet!"),
qsTr("Pass me my wrench!"),
qsTr("It's time for a tune-up!"),
qsTr("Never give up, and never lose! I'm on my way!"),
qsTr("I'm not worried! I can fix anything!")];
};
</syntaxhighlight>When you use a power, the CO says something before actually using it. What that something is comes from here.

Just return a list of strings (using []), the hard part is thinking of what to say.<syntaxhighlight lang="javascript" line="1" start="295">
this.getVictorySentences = function(co)
{
return [qsTr("We won! Woohoo!"),
qsTr("I can fix anything!"),
qsTr("I did it! Did you see that!?")];
};
this.getDefeatSentences = function(co)
{
return [qsTr("Oh, come on!"),
qsTr("Next time I see you, you're in trouble!")];
};
</syntaxhighlight>There are a surprising number of words that go into making a CO aren't there?<syntaxhighlight lang="javascript" line="1" start="306">
this.getName = function()
{
return qsTr("Andy");
};
}
</syntaxhighlight>Just to confirm, we are in fact looking at Andy's code.

Also the closing bracket of the original Constructor function. How long ago was that?

== Footer ==
Now for two vital lines of code:<syntaxhighlight lang="javascript" line="1" start="312">
Constructor.prototype = CO;
var CO_ANDY = new Constructor();
</syntaxhighlight>We set the type of constructor to CO. This tells COW that this is a CO and not some weirdly shaped unit.

Then we set the var CO_ANDY to a new instance of Constructor. This makes CO_ANDY and actual CO object, and not just the blueprints of how to make Andy. CO_ANDY is where COW (and other scripts) will reference your CO from now on.

And with those two lines, we are finished!
[[Category:Modding tutorials]]

Andy Breakdown

2023-12-30T16:54:56Z

MrDuck557: Right category

'''Notice: Modding tutorials assume you know at least the basics of coding or scripting. Commander Wars uses Javascript as the Scripting Language.''' In case you want to learn more about Javascript, you can check the tutorial here: Derek Banas' Javascript tutorial , purchase O'Reilly's excellent book on the subject JavaScript: The Definitive Guide, or check out W3 Schools Interactive Tutorials

'''This tutorial references https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_andy.js, the source code of the actual vanilla Andy in COW.'''

'''THIS IS UNFINISHED DO NOT COMPLAIN ABOUT MISSING SECTIONS'''

== Small Disclaimer ==
This will only go through vanilla Andy's js code, and not any other files. This is intended for newer players to understand the workings of what the code they're copy-pasting actually does. If you want to make a brand new CO in a mod, a good starting point is [[Custom CO]]. Alternatively, download a mod and edit to suit your needs.

Also I refer to normal CO powers as COP and super CO powers as SCOP, just clearing that up

== Some stuff in the header ==
<syntaxhighlight lang="javascript" line="1" start="1">
var Constructor = function()
{
</syntaxhighlight>The very first line (or two) of code. This defines a variable called Constructor to be a function. What does the function do? It's defined in the curly brackets {} following it. Notice how only the opening bracket is present. This is a long function (the whole CO).<syntaxhighlight lang="javascript" line="1" start="3">
this.getCOStyles = function()
{
return ["+alt", "+alt2", "+alt3"];
};
</syntaxhighlight>Due to some js... weirdness, we treat functions as objects that you can define properties of. If we called Constructor.getCOStyles() after finishing the Constructor function, we would get this. Specifically it would return ["+alt", "+alt2", "+alt3"]. This is telling the game to look for alternate CO images labeled "andy+alt", "andy+alt2", and "andy+alt3" as well as simply "andy". If you look in the corresponding images folder ([https://github.com/Robosturm/Commander_Wars/tree/master/resources/images/co/os]), we do actually find said images. This is Commander Wars's way to get CO styles, so if you want to have extra costumes for your CO, this is how you do it.<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
}
};
</syntaxhighlight>This is a custom function for the AI behavior of Andy. If it looks scary, that's because <s>it kinda is</s> there's just a bunch of variables and if statements flying around. Let's break this down further<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{

</syntaxhighlight>Again, a function definition. But this time, with words inside the function() brackets. Those are called parameters, and how you can pass data into a function. Here, the game is passing in:

* The CO (co) (specifically the player's instance of a CO, in an andy mirror match both andys are actually considered different COs)
* The power charge more than what the COP needs (powerSurplus)
* The count of all owned units on the field (unitCount)
* Count of all units less than 10hp (repairUnits)
* Count of all units that can shoot at more than 1 range (indirectUnits)
* Count of all units not an indirect unit (directUnits)
* The number of enemy units
* The turn mode of the AI, set to start of day, during the day, and end of day.

The vast majority of the time, a significant portion of these will not be used (for example, Andy doesn't really care if his units are direct or indirect, so long as they're repaired)<syntaxhighlight lang="javascript" line="1" start="10">
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{

</syntaxhighlight>This checks that the turn mode is start of day. This makes sure that Andy only ever uses his power at the start of each day.<syntaxhighlight lang="javascript" line="1" start="12">
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
</syntaxhighlight>If Andy can use his SCOP of course he uses his SCOP<syntaxhighlight>
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
</syntaxhighlight>If Andy has at most 0.5 stars more than his COP (and if he can use his COP in the first place), return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);?

Referencing CO.getAiUsePowerAtUnitCount, it first checks if turnMode is equal to start of day, and also if repairUnits (in Andy's getAiUsePower at least, the name is changed during the function call to unitCount) is at least 5.

If either of these conditions are not fulfilled, don't use any power.

If both of these conditions are fulfilled, use SCOP is possible, and use COP if powerSurplus <= 0.5 (and if COP is usable in the first place)

So essentially, Andy doesn't want to Hyper Repair unless he has just enough power charge and if he can repair at least 5 units.<syntaxhighlight lang="javascript" line="1" start="21">
}
};
</syntaxhighlight>Closing brackets you always need those

You may be put off at the lack of a return statement here. Won't the code break if the function doesn't return anything?

I'm put off too.

Also the semicolon at the end? This is because we're actually defining a variable (getAiUsePower) as this function. Defining a variable is a code statement. We need semicolons after each code statement so the computer knows where to end each block of code. This is a property of c++ and java as well as javascript.

Next segment!

== Power stuff ==
<syntaxhighlight lang="javascript" line="1" start="24">
this.init = function(co, map)
{
co.setPowerStars(3);
co.setSuperpowerStars(3);
};
</syntaxhighlight>init() is generally a function called to make sure that something is ready and to set up any needed variables. In this case, the only things that are done are setting COP stars to 3 and setting SCOP stars to 3. Note how the SCOP does not cost 3 stars, rather this is 3 stars on top of the COP cost of 3 stars, for a total of 6 stars.

Since the next function probably won't fit on the screen all at once, I'll just break it down now.<syntaxhighlight lang="javascript" line="1" start="30">
this.activatePower = function(co, map)
{
var dialogAnimation = co.createPowerSentence();
var powerNameAnimation = co.createPowerScreen(GameEnums.PowerMode_Power);
dialogAnimation.queueAnimation(powerNameAnimation);
</syntaxhighlight>The function is called activatePower, which is used when you activate power (COP specifically)

dialogAnimation and powerNameAnimation are used for the flashy effects whenever you use a power, the ones that appear, fill the screen with the power name, and disappear before your units get sparkles on them.

.queueAnimation is used to make sure that the whole screen is filled after the dialog finishes.<syntaxhighlight lang="javascript" line="1" start="36">
var units = co.getOwner().getUnits();
var animations = [];
var counter = 0;
units.randomize();
</syntaxhighlight>To go through all the units and make animations, we'll need to get all the units and have a place to store all the animations. counter is set to 0 and will correspond to animations's size (incidentally both are 0 right now)

units.randomize() makes sure that the units will be considered in a random order. Since animations happen in the same order, the animations are randomized as well.<syntaxhighlight lang="javascript" line="1" start="40">
for (var i = 0; i < units.size(); i++)
{
var unit = units.at(i);
</syntaxhighlight>The for loop will iterate through the units, with i being the index and unit being the current unit. This is randomized because units was randomized beforehand.<syntaxhighlight lang="javascript" line="1" start="44">
var animation = GameAnimationFactory.createAnimation(map, unit.getX(), unit.getY());
animation.writeDataInt32(unit.getX());
animation.writeDataInt32(unit.getY());
animation.writeDataInt32(CO_ANDY.powerHeal);
animation.setEndOfAnimationCall("ANIMATION", "postAnimationHeal");
</syntaxhighlight>Here the animation is set up. The animation is created on the map at the unit's position in createAnimation. Then the unit's position is written to the animation and CO_ANDY.powerHeal. powerHeal is an integer specifying the COP healing, in this case 2. The variable is useful to avoid "magic numbers", constant values that are typed in directly. If you want to change a magic number, you have to manually go into the code and edit every instance of that magic number. Keeping your constants in variables like CO_ANDY.powerHeal allows you to change the value quickly and easily from one place. You'll see variables like this later in the code.

Note: CO_<co name> is standard convention for CO variables. Often, you'll store important variables for your CO on CO_<co name> like CO_ANDY.powerHeal. CO_<co name> is how other scripts are going to access your CO, and how your own script accesses your CO.

At the end of the animation, the units will be healed for 2 hp. postAnimationHeal uses the prior three values to know what position to heal as well as how much to heal. setEndOfAnimationCall tells the animation engine to call a function (in this case postAnimationHeal) from an object (ANIMATION) at the end of the animation. Here's the actual postAnimationHeal if you're curious. [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/resources/scripts/general/animation.js#L4]

Before going any further into the animation code, I want to go into the big picture of what is actually happening.

So first of all, when an animation is created, it's going to be handled by the Commander Wars engine no matter what. It doesn't matter if no variable in your script points to it, it's going to be saved in the core game and the core game will handle it.

The power animation for the units goes something like this: make an animation for every unit in a random order, but don't have more than 5 animations going on at the same time.

With that out of the way, here's the rest of the code<syntaxhighlight lang="javascript" line="1" start="49">
var delay = globals.randInt(135, 265);
if (animations.length < 5)
{
delay *= i;
}
animation.setSound("power0.wav", 1, delay);
</syntaxhighlight>delay is set to some random number between 135 and 265. Then, if the animation queue isn't filled (length is 5), multiply the delay by i.

What delay *= i will do is approximately make sure that the animations are in order. Say we happen to roll 200 3 times, the delays would be 200 (start at 200), 400, and 600. This will make the animations appear one after the other, kind of like how it works in the original advance wars. I'll explain what happens if the delay isn't multiplied later.

animation.setSound("power0.wav", 1, delay) sets the sound of the animation. power0.wav is the filename of the sound, 1 is the number of times to repeat (1 means 1 play) and delay is how delayed it is. If you want, I believe you can add another number for volume and also set if the oldest sound should be stopped. (animation.setSound("filename", repeats, delay, volume, stopOldestSound))<syntaxhighlight lang="javascript" line="1" start="55">
if (animations.length < 5)
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
powerNameAnimation.queueAnimation(animation);
animations.push(animation);
}
</syntaxhighlight>animations.length < 5 means the animation queue isn't full. It then adds a sprite (power0) and positions it accordingly.

Looking at the source of addSprite [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/game/gameanimation/gameanimation.cpp], it offsets the image so that the unit is in the center (-map.getImageSize()*1.27) (both of them), sets sleepAfterFinish (0 is no I think), sets the scale (2) and adds delay (delay). There's another parameter for loops, which would probably set repeats if you want the image to show up more than once.

powerNameAnimation.queueAnimation(animation) sets the current animation to fire right after powerNameAnimation (the screen fill with your power name). But while the animation starts right away internally, the sound and image are delayed (thanks to delay) so what you see and hear on screen actually starts a bit later (which is probably what you want). queueAnimation() is a function attached to the animation class in general, so don't be confused if you see a different animation object using this function.

animations.push(animation) sticks the current animation at the end of the animations list. This will become very relevant shortly.<syntaxhighlight lang="javascript" line="1" start="61">
else
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
animations[counter].queueAnimation(animation);
animations[counter] = animation;
counter++;
if (counter >= animations.length)
{
counter = 0;
}
}
</syntaxhighlight>else is for if the statement in the if block isn't true (in this case animations.length < 5). This would mean that the animation queue is full.

Just to recap, delay has not been multiplied by i, counter is the index of some animation in animation, and animations is full of animations.

We've seen the addSprite method before. What's different is animations[counter].queueAnimation(animation). Here, the current animation is set to fire right after animations[counter] finishes. Then the current animation replaces the old animation, and counter increases by 1. (++ does that) If counter >= animations.length (animations[counter] would throw an error), just set it back to 0.

Was that confusing? Here's a step by step diagram.

Right before the first instance of this, animations is filled with [0,1,2,3,4]. (not actually those numbers, just animations 0, 1, 2, 3, and 4)

On the first iteration of this else statement, counter is 0, so animation 0 will set 5 to fire right after it, then 5 takes 0's place. counter increases by 1.

The list looks like this: [5,1,2,3,4], and counter is 1 now.

Next iteration: [5,6,2,3,4] (6 is queued after 1, counter is 2)

Skip forwards a bit: [5,6,7,8,4] (7 after 2, 8 after 3, counter is 4)

Now the animations will do their dance [5,6,7,8,9], and counter increases by 1 to 5.

But animations[5] is not valid (remember 0 indexing), so counter is set back to 0, and the cycle repeats.

The delay works here, because we have 0,5,10,15 going "1 delay" after each other, 1,6,11,16 going "1 delay" after each other (but 1 is delayed by "1 delay" relative to 0) and the rest is similar. If you don't think this is good, feel free to mess around with the code and see what happens.<syntaxhighlight lang="javascript" line="1" start="72">
}
};
</syntaxhighlight>And that's that function done.

activateSuperpower is actually pretty similar, using much of the same mechanics to do basically the same thing.

Notable changes:<syntaxhighlight lang="javascript" line="1" start="92">
animation.writeDataInt32(CO_ANDY.superPowerHeal);
</syntaxhighlight>When using the SCOP, we use the superPowerHeal rather than the regular power heal.<syntaxhighlight lang="javascript" line="1" start="95">
if (animations.length < 7)
</syntaxhighlight>bigger queue, more animations at once<syntaxhighlight lang="javascript" line="1" start="99">
if (i % 2 === 0)
{
animation.setSound("power12_1.wav", 1, delay);
}
else
{
animation.setSound("power12_2.wav", 1, delay);
}

</syntaxhighlight>We have two sounds! i%2===0 will be true every other iteration, so we alternate between the two sounds.<syntaxhighlight lang="javascript" line="1" start="109">
animation.addSprite("power12", -map.getImageSize() * 2, -map.getImageSize() * 2, 0, 2, delay);
</syntaxhighlight>Different image, and the offset is bigger (because the image is bigger)

Again, it was basically the same thing, but with SCOP stuff.

You're asking how long the next functions are going to be?

Not very long actually, they're far simpler and mostly just for returning numbers.

== Music and Modifiers ==
Most of these functions will return a value. Not much logic in these.<syntaxhighlight lang="javascript" line="1" start="127">
this.loadCOMusic = function(co, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Power:
audio.addMusic("resources/music/cos/power.mp3", 992, 45321);
break;
case GameEnums.PowerMode_Superpower:
audio.addMusic("resources/music/cos/superpower.mp3", 1505, 49515);
break;
case GameEnums.PowerMode_Tagpower:
audio.addMusic("resources/music/cos/tagpower.mp3", 14611, 65538);
break;
default:
audio.addMusic("resources/music/cos/andy.mp3", 4466, 74972);
break;
}
}
};
</syntaxhighlight>co.getPowerMode() returns something based on what power is activated.

switch statements execute different code based on the input value. In this case that would be the power mode.

This format (a switch statement using the power mode) is actually the standard way of doing different things if your power is active or not. You don't have to memorize it, just copy-paste it a bunch.

audio.addMusic plays the music (in a loop presumably) from startTime (in milliseconds) to endTime (in milliseconds).

The break statements prevent the code from considering other cases once one case has been run.<syntaxhighlight lang="javascript" line="1" start="149">
this.getCOUnitRange = function(co, map)
{
return 3;
};
this.getCOArmy = function()
{
return "OS";
};
</syntaxhighlight>getCOUnitRange should return the CO zone range, in this case 3.

getCOArmy should return a string corresponding to the co's country. In this case Andy is from Orange Star, so this function returns "OS". You can check other COs for their country's strings. <syntaxhighlight lang="javascript" line="1" start="158">
this.superPowerHeal = 5;
this.superPowerOffBonus = 30;
this.superPowerMovementBonus = 1;

this.powerDefBonus = 20;
this.powerOffBonus = 20;
this.powerHeal = 2;

this.d2dCoZoneOffBonus = 20;
this.d2dCoZoneDefBonus = 20;
</syntaxhighlight>These are variables for easy modification of Andy's numbers. If you check the in-game wiki, these numbers should line up with what you see there. As stated above, these variables make sure you don't accidentally change the numbers in one place but not another.<syntaxhighlight lang="javascript" line="1" start="169">
this.getOffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isDefender, action, luckmode, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Tagpower:
case GameEnums.PowerMode_Superpower:
return CO_ANDY.superPowerOffBonus;
case GameEnums.PowerMode_Power:
return CO_ANDY.powerOffBonus;
default:
if (co.inCORange(Qt.point(atkPosX, atkPosY), attacker))
{
return CO_ANDY.d2dCoZoneOffBonus;
}
break;
}
}
return 0;
};
</syntaxhighlight>getOffensiveBonus is called when you want to find the offensive bonus of a specific unit. There are a lot of parameters for this function, but honestly most of them are pretty self-explanatory (what do you expect defender to be).

if (CO.isActive(co)) just makes sure your CO is actually active and should be used.

The switch statement is explained above. In this case, it changes the offensive bonus depending on if the power is active or not.

Note the co.inCORange() function. This is a very easy way to check if a unit is in the CO zone or not. You may be curious why this check isn't in any other case. In the original AW DoR, where CO zones were first introduced, CO zones became global while using powers. This is carried over to COW, so not only would the check be redundant (you can be sure your unit is in the map-wide zone), it may not even work (sometimes when a CO unit is moved during powers, the zone shows up as range 0).

Also the break statement at the end. This is best practice in switch statements, as it ensures you get out of the switch right away and not accidentally fall into other cases. You don't need to do this after a return statement, because return sends you out of the function as well as the switch.<syntaxhighlight lang="javascript" line="1" start="191">
this.getDeffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isAttacker, action, luckmode, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() > GameEnums.PowerMode_Off)
{
return CO_ANDY.powerDefBonus;
}
else if (co.inCORange(Qt.point(defPosX, defPosY), defender))
{
return CO_ANDY.d2dCoZoneDefBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, except for one thing.

A funny thing about enums, they're actually numbers.

This allows for funky stuff like co.getPowerMode() > GameEnums.PowerMode_Off. This will be true if either CO power is active.

I don't personally use this, but this is an alternative to a switch statement.<syntaxhighlight lang="javascript" line="1" start="207">
this.getMovementpointModifier = function(co, unit, posX, posY, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() === GameEnums.PowerMode_Superpower ||
co.getPowerMode() === GameEnums.PowerMode_Tagpower)
{
return CO_ANDY.superPowerMovementBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, again

Since movement takes place outside of combat, you don't have attacker, attackerX, defender, and defenderY (some variables skipped for brevity). Instead you just have the unit you're moving. This shouldn't be too relevant, but beware accidentally copying attacker and not replacing it with unit.<syntaxhighlight lang="javascript" line="1" start="220">
this.getCOUnits = function(co, building, map)
{
if (CO.isActive(co))
{
var buildingId = building.getBuildingID();
if (buildingId === "FACTORY" ||
buildingId === "TOWN" ||
BUILDING.isHq(building))
{
return ["ZCOUNIT_REPAIR_TANK"];
}
}
return [];
};
</syntaxhighlight>This function gets your exclusive CO units. In Andy's case, we have repair tanks (internal ID ZCOUNIT_REPAIR_TANK). But since it's a land unit, we don't want to build it out of any building (as much as I think Andy forgetting what an airport is supposed to do is funny).

So we check the buildingId. For compatibility with Hachi and Hachi's soul, we also add the repair tank to the build lists of towns and hqs, even though they can't build anything.<syntaxhighlight lang="javascript" line="1" start="234">
this.getAiCoUnitBonus = function(co, unit, map)
{
return 1;
};
</syntaxhighlight>I actually had to look up what this does. If we step away from Andy for a bit and go to Sami's code [https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_sami.js#L305]:<syntaxhighlight lang="javascript" line="1" start="305">
this.getAiCoUnitBonus = function(co, unit, map)
{
if (unit.getUnitID !== "INFANTRY")
{
if (unit.getUnitType() === GameEnums.UnitType_Infantry)
{
return 8;
}
else if (unit.getBaseMaxRange() === 1)
{
return -1;
}
}
return 2;
};
</syntaxhighlight>It quickly becomes apparent what this method is used for. If the unit is an infantry, skip the if statement and return 2. If the unit is of type infantry (but not the 1k infantry, something like a commando), return 8. If it's a direct unit, return -1. And if it's an indirect, you go outside of the if statement and return 2.

In short, Sami prefers infantry type over infantry and indirects, and those over direct units (for CO units) (Thanks Sami!)

Andy returns 1 no matter what, so no preference.
[[Category:Modding tutorials]]

Andy Breakdown

2023-12-30T16:54:17Z

MrDuck557: Category added

'''Notice: Modding tutorials assume you know at least the basics of coding or scripting. Commander Wars uses Javascript as the Scripting Language.''' In case you want to learn more about Javascript, you can check the tutorial here: Derek Banas' Javascript tutorial , purchase O'Reilly's excellent book on the subject JavaScript: The Definitive Guide, or check out W3 Schools Interactive Tutorials

'''This tutorial references https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_andy.js, the source code of the actual vanilla Andy in COW.'''

'''THIS IS UNFINISHED DO NOT COMPLAIN ABOUT MISSING SECTIONS'''

== Small Disclaimer ==
This will only go through vanilla Andy's js code, and not any other files. This is intended for newer players to understand the workings of what the code they're copy-pasting actually does. If you want to make a brand new CO in a mod, a good starting point is [[Custom CO]]. Alternatively, download a mod and edit to suit your needs.

Also I refer to normal CO powers as COP and super CO powers as SCOP, just clearing that up

== Some stuff in the header ==
<syntaxhighlight lang="javascript" line="1" start="1">
var Constructor = function()
{
</syntaxhighlight>The very first line (or two) of code. This defines a variable called Constructor to be a function. What does the function do? It's defined in the curly brackets {} following it. Notice how only the opening bracket is present. This is a long function (the whole CO).<syntaxhighlight lang="javascript" line="1" start="3">
this.getCOStyles = function()
{
return ["+alt", "+alt2", "+alt3"];
};
</syntaxhighlight>Due to some js... weirdness, we treat functions as objects that you can define properties of. If we called Constructor.getCOStyles() after finishing the Constructor function, we would get this. Specifically it would return ["+alt", "+alt2", "+alt3"]. This is telling the game to look for alternate CO images labeled "andy+alt", "andy+alt2", and "andy+alt3" as well as simply "andy". If you look in the corresponding images folder ([https://github.com/Robosturm/Commander_Wars/tree/master/resources/images/co/os]), we do actually find said images. This is Commander Wars's way to get CO styles, so if you want to have extra costumes for your CO, this is how you do it.<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
}
};
</syntaxhighlight>This is a custom function for the AI behavior of Andy. If it looks scary, that's because <s>it kinda is</s> there's just a bunch of variables and if statements flying around. Let's break this down further<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{

</syntaxhighlight>Again, a function definition. But this time, with words inside the function() brackets. Those are called parameters, and how you can pass data into a function. Here, the game is passing in:

* The CO (co) (specifically the player's instance of a CO, in an andy mirror match both andys are actually considered different COs)
* The power charge more than what the COP needs (powerSurplus)
* The count of all owned units on the field (unitCount)
* Count of all units less than 10hp (repairUnits)
* Count of all units that can shoot at more than 1 range (indirectUnits)
* Count of all units not an indirect unit (directUnits)
* The number of enemy units
* The turn mode of the AI, set to start of day, during the day, and end of day.

The vast majority of the time, a significant portion of these will not be used (for example, Andy doesn't really care if his units are direct or indirect, so long as they're repaired)<syntaxhighlight lang="javascript" line="1" start="10">
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{

</syntaxhighlight>This checks that the turn mode is start of day. This makes sure that Andy only ever uses his power at the start of each day.<syntaxhighlight lang="javascript" line="1" start="12">
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
</syntaxhighlight>If Andy can use his SCOP of course he uses his SCOP<syntaxhighlight>
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
</syntaxhighlight>If Andy has at most 0.5 stars more than his COP (and if he can use his COP in the first place), return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);?

Referencing CO.getAiUsePowerAtUnitCount, it first checks if turnMode is equal to start of day, and also if repairUnits (in Andy's getAiUsePower at least, the name is changed during the function call to unitCount) is at least 5.

If either of these conditions are not fulfilled, don't use any power.

If both of these conditions are fulfilled, use SCOP is possible, and use COP if powerSurplus <= 0.5 (and if COP is usable in the first place)

So essentially, Andy doesn't want to Hyper Repair unless he has just enough power charge and if he can repair at least 5 units.<syntaxhighlight lang="javascript" line="1" start="21">
}
};
</syntaxhighlight>Closing brackets you always need those

You may be put off at the lack of a return statement here. Won't the code break if the function doesn't return anything?

I'm put off too.

Also the semicolon at the end? This is because we're actually defining a variable (getAiUsePower) as this function. Defining a variable is a code statement. We need semicolons after each code statement so the computer knows where to end each block of code. This is a property of c++ and java as well as javascript.

Next segment!

== Power stuff ==
<syntaxhighlight lang="javascript" line="1" start="24">
this.init = function(co, map)
{
co.setPowerStars(3);
co.setSuperpowerStars(3);
};
</syntaxhighlight>init() is generally a function called to make sure that something is ready and to set up any needed variables. In this case, the only things that are done are setting COP stars to 3 and setting SCOP stars to 3. Note how the SCOP does not cost 3 stars, rather this is 3 stars on top of the COP cost of 3 stars, for a total of 6 stars.

Since the next function probably won't fit on the screen all at once, I'll just break it down now.<syntaxhighlight lang="javascript" line="1" start="30">
this.activatePower = function(co, map)
{
var dialogAnimation = co.createPowerSentence();
var powerNameAnimation = co.createPowerScreen(GameEnums.PowerMode_Power);
dialogAnimation.queueAnimation(powerNameAnimation);
</syntaxhighlight>The function is called activatePower, which is used when you activate power (COP specifically)

dialogAnimation and powerNameAnimation are used for the flashy effects whenever you use a power, the ones that appear, fill the screen with the power name, and disappear before your units get sparkles on them.

.queueAnimation is used to make sure that the whole screen is filled after the dialog finishes.<syntaxhighlight lang="javascript" line="1" start="36">
var units = co.getOwner().getUnits();
var animations = [];
var counter = 0;
units.randomize();
</syntaxhighlight>To go through all the units and make animations, we'll need to get all the units and have a place to store all the animations. counter is set to 0 and will correspond to animations's size (incidentally both are 0 right now)

units.randomize() makes sure that the units will be considered in a random order. Since animations happen in the same order, the animations are randomized as well.<syntaxhighlight lang="javascript" line="1" start="40">
for (var i = 0; i < units.size(); i++)
{
var unit = units.at(i);
</syntaxhighlight>The for loop will iterate through the units, with i being the index and unit being the current unit. This is randomized because units was randomized beforehand.<syntaxhighlight lang="javascript" line="1" start="44">
var animation = GameAnimationFactory.createAnimation(map, unit.getX(), unit.getY());
animation.writeDataInt32(unit.getX());
animation.writeDataInt32(unit.getY());
animation.writeDataInt32(CO_ANDY.powerHeal);
animation.setEndOfAnimationCall("ANIMATION", "postAnimationHeal");
</syntaxhighlight>Here the animation is set up. The animation is created on the map at the unit's position in createAnimation. Then the unit's position is written to the animation and CO_ANDY.powerHeal. powerHeal is an integer specifying the COP healing, in this case 2. The variable is useful to avoid "magic numbers", constant values that are typed in directly. If you want to change a magic number, you have to manually go into the code and edit every instance of that magic number. Keeping your constants in variables like CO_ANDY.powerHeal allows you to change the value quickly and easily from one place. You'll see variables like this later in the code.

Note: CO_<co name> is standard convention for CO variables. Often, you'll store important variables for your CO on CO_<co name> like CO_ANDY.powerHeal. CO_<co name> is how other scripts are going to access your CO, and how your own script accesses your CO.

At the end of the animation, the units will be healed for 2 hp. postAnimationHeal uses the prior three values to know what position to heal as well as how much to heal. setEndOfAnimationCall tells the animation engine to call a function (in this case postAnimationHeal) from an object (ANIMATION) at the end of the animation. Here's the actual postAnimationHeal if you're curious. [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/resources/scripts/general/animation.js#L4]

Before going any further into the animation code, I want to go into the big picture of what is actually happening.

So first of all, when an animation is created, it's going to be handled by the Commander Wars engine no matter what. It doesn't matter if no variable in your script points to it, it's going to be saved in the core game and the core game will handle it.

The power animation for the units goes something like this: make an animation for every unit in a random order, but don't have more than 5 animations going on at the same time.

With that out of the way, here's the rest of the code<syntaxhighlight lang="javascript" line="1" start="49">
var delay = globals.randInt(135, 265);
if (animations.length < 5)
{
delay *= i;
}
animation.setSound("power0.wav", 1, delay);
</syntaxhighlight>delay is set to some random number between 135 and 265. Then, if the animation queue isn't filled (length is 5), multiply the delay by i.

What delay *= i will do is approximately make sure that the animations are in order. Say we happen to roll 200 3 times, the delays would be 200 (start at 200), 400, and 600. This will make the animations appear one after the other, kind of like how it works in the original advance wars. I'll explain what happens if the delay isn't multiplied later.

animation.setSound("power0.wav", 1, delay) sets the sound of the animation. power0.wav is the filename of the sound, 1 is the number of times to repeat (1 means 1 play) and delay is how delayed it is. If you want, I believe you can add another number for volume and also set if the oldest sound should be stopped. (animation.setSound("filename", repeats, delay, volume, stopOldestSound))<syntaxhighlight lang="javascript" line="1" start="55">
if (animations.length < 5)
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
powerNameAnimation.queueAnimation(animation);
animations.push(animation);
}
</syntaxhighlight>animations.length < 5 means the animation queue isn't full. It then adds a sprite (power0) and positions it accordingly.

Looking at the source of addSprite [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/game/gameanimation/gameanimation.cpp], it offsets the image so that the unit is in the center (-map.getImageSize()*1.27) (both of them), sets sleepAfterFinish (0 is no I think), sets the scale (2) and adds delay (delay). There's another parameter for loops, which would probably set repeats if you want the image to show up more than once.

powerNameAnimation.queueAnimation(animation) sets the current animation to fire right after powerNameAnimation (the screen fill with your power name). But while the animation starts right away internally, the sound and image are delayed (thanks to delay) so what you see and hear on screen actually starts a bit later (which is probably what you want). queueAnimation() is a function attached to the animation class in general, so don't be confused if you see a different animation object using this function.

animations.push(animation) sticks the current animation at the end of the animations list. This will become very relevant shortly.<syntaxhighlight lang="javascript" line="1" start="61">
else
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
animations[counter].queueAnimation(animation);
animations[counter] = animation;
counter++;
if (counter >= animations.length)
{
counter = 0;
}
}
</syntaxhighlight>else is for if the statement in the if block isn't true (in this case animations.length < 5). This would mean that the animation queue is full.

Just to recap, delay has not been multiplied by i, counter is the index of some animation in animation, and animations is full of animations.

We've seen the addSprite method before. What's different is animations[counter].queueAnimation(animation). Here, the current animation is set to fire right after animations[counter] finishes. Then the current animation replaces the old animation, and counter increases by 1. (++ does that) If counter >= animations.length (animations[counter] would throw an error), just set it back to 0.

Was that confusing? Here's a step by step diagram.

Right before the first instance of this, animations is filled with [0,1,2,3,4]. (not actually those numbers, just animations 0, 1, 2, 3, and 4)

On the first iteration of this else statement, counter is 0, so animation 0 will set 5 to fire right after it, then 5 takes 0's place. counter increases by 1.

The list looks like this: [5,1,2,3,4], and counter is 1 now.

Next iteration: [5,6,2,3,4] (6 is queued after 1, counter is 2)

Skip forwards a bit: [5,6,7,8,4] (7 after 2, 8 after 3, counter is 4)

Now the animations will do their dance [5,6,7,8,9], and counter increases by 1 to 5.

But animations[5] is not valid (remember 0 indexing), so counter is set back to 0, and the cycle repeats.

The delay works here, because we have 0,5,10,15 going "1 delay" after each other, 1,6,11,16 going "1 delay" after each other (but 1 is delayed by "1 delay" relative to 0) and the rest is similar. If you don't think this is good, feel free to mess around with the code and see what happens.<syntaxhighlight lang="javascript" line="1" start="72">
}
};
</syntaxhighlight>And that's that function done.

activateSuperpower is actually pretty similar, using much of the same mechanics to do basically the same thing.

Notable changes:<syntaxhighlight lang="javascript" line="1" start="92">
animation.writeDataInt32(CO_ANDY.superPowerHeal);
</syntaxhighlight>When using the SCOP, we use the superPowerHeal rather than the regular power heal.<syntaxhighlight lang="javascript" line="1" start="95">
if (animations.length < 7)
</syntaxhighlight>bigger queue, more animations at once<syntaxhighlight lang="javascript" line="1" start="99">
if (i % 2 === 0)
{
animation.setSound("power12_1.wav", 1, delay);
}
else
{
animation.setSound("power12_2.wav", 1, delay);
}

</syntaxhighlight>We have two sounds! i%2===0 will be true every other iteration, so we alternate between the two sounds.<syntaxhighlight lang="javascript" line="1" start="109">
animation.addSprite("power12", -map.getImageSize() * 2, -map.getImageSize() * 2, 0, 2, delay);
</syntaxhighlight>Different image, and the offset is bigger (because the image is bigger)

Again, it was basically the same thing, but with SCOP stuff.

You're asking how long the next functions are going to be?

Not very long actually, they're far simpler and mostly just for returning numbers.

== Music and Modifiers ==
Most of these functions will return a value. Not much logic in these.<syntaxhighlight lang="javascript" line="1" start="127">
this.loadCOMusic = function(co, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Power:
audio.addMusic("resources/music/cos/power.mp3", 992, 45321);
break;
case GameEnums.PowerMode_Superpower:
audio.addMusic("resources/music/cos/superpower.mp3", 1505, 49515);
break;
case GameEnums.PowerMode_Tagpower:
audio.addMusic("resources/music/cos/tagpower.mp3", 14611, 65538);
break;
default:
audio.addMusic("resources/music/cos/andy.mp3", 4466, 74972);
break;
}
}
};
</syntaxhighlight>co.getPowerMode() returns something based on what power is activated.

switch statements execute different code based on the input value. In this case that would be the power mode.

This format (a switch statement using the power mode) is actually the standard way of doing different things if your power is active or not. You don't have to memorize it, just copy-paste it a bunch.

audio.addMusic plays the music (in a loop presumably) from startTime (in milliseconds) to endTime (in milliseconds).

The break statements prevent the code from considering other cases once one case has been run.<syntaxhighlight lang="javascript" line="1" start="149">
this.getCOUnitRange = function(co, map)
{
return 3;
};
this.getCOArmy = function()
{
return "OS";
};
</syntaxhighlight>getCOUnitRange should return the CO zone range, in this case 3.

getCOArmy should return a string corresponding to the co's country. In this case Andy is from Orange Star, so this function returns "OS". You can check other COs for their country's strings. <syntaxhighlight lang="javascript" line="1" start="158">
this.superPowerHeal = 5;
this.superPowerOffBonus = 30;
this.superPowerMovementBonus = 1;

this.powerDefBonus = 20;
this.powerOffBonus = 20;
this.powerHeal = 2;

this.d2dCoZoneOffBonus = 20;
this.d2dCoZoneDefBonus = 20;
</syntaxhighlight>These are variables for easy modification of Andy's numbers. If you check the in-game wiki, these numbers should line up with what you see there. As stated above, these variables make sure you don't accidentally change the numbers in one place but not another.<syntaxhighlight lang="javascript" line="1" start="169">
this.getOffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isDefender, action, luckmode, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Tagpower:
case GameEnums.PowerMode_Superpower:
return CO_ANDY.superPowerOffBonus;
case GameEnums.PowerMode_Power:
return CO_ANDY.powerOffBonus;
default:
if (co.inCORange(Qt.point(atkPosX, atkPosY), attacker))
{
return CO_ANDY.d2dCoZoneOffBonus;
}
break;
}
}
return 0;
};
</syntaxhighlight>getOffensiveBonus is called when you want to find the offensive bonus of a specific unit. There are a lot of parameters for this function, but honestly most of them are pretty self-explanatory (what do you expect defender to be).

if (CO.isActive(co)) just makes sure your CO is actually active and should be used.

The switch statement is explained above. In this case, it changes the offensive bonus depending on if the power is active or not.

Note the co.inCORange() function. This is a very easy way to check if a unit is in the CO zone or not. You may be curious why this check isn't in any other case. In the original AW DoR, where CO zones were first introduced, CO zones became global while using powers. This is carried over to COW, so not only would the check be redundant (you can be sure your unit is in the map-wide zone), it may not even work (sometimes when a CO unit is moved during powers, the zone shows up as range 0).

Also the break statement at the end. This is best practice in switch statements, as it ensures you get out of the switch right away and not accidentally fall into other cases. You don't need to do this after a return statement, because return sends you out of the function as well as the switch.<syntaxhighlight lang="javascript" line="1" start="191">
this.getDeffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isAttacker, action, luckmode, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() > GameEnums.PowerMode_Off)
{
return CO_ANDY.powerDefBonus;
}
else if (co.inCORange(Qt.point(defPosX, defPosY), defender))
{
return CO_ANDY.d2dCoZoneDefBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, except for one thing.

A funny thing about enums, they're actually numbers.

This allows for funky stuff like co.getPowerMode() > GameEnums.PowerMode_Off. This will be true if either CO power is active.

I don't personally use this, but this is an alternative to a switch statement.<syntaxhighlight lang="javascript" line="1" start="207">
this.getMovementpointModifier = function(co, unit, posX, posY, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() === GameEnums.PowerMode_Superpower ||
co.getPowerMode() === GameEnums.PowerMode_Tagpower)
{
return CO_ANDY.superPowerMovementBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, again

Since movement takes place outside of combat, you don't have attacker, attackerX, defender, and defenderY (some variables skipped for brevity). Instead you just have the unit you're moving. This shouldn't be too relevant, but beware accidentally copying attacker and not replacing it with unit.<syntaxhighlight lang="javascript" line="1" start="220">
this.getCOUnits = function(co, building, map)
{
if (CO.isActive(co))
{
var buildingId = building.getBuildingID();
if (buildingId === "FACTORY" ||
buildingId === "TOWN" ||
BUILDING.isHq(building))
{
return ["ZCOUNIT_REPAIR_TANK"];
}
}
return [];
};
</syntaxhighlight>This function gets your exclusive CO units. In Andy's case, we have repair tanks (internal ID ZCOUNIT_REPAIR_TANK). But since it's a land unit, we don't want to build it out of any building (as much as I think Andy forgetting what an airport is supposed to do is funny).

So we check the buildingId. For compatibility with Hachi and Hachi's soul, we also add the repair tank to the build lists of towns and hqs, even though they can't build anything.<syntaxhighlight lang="javascript" line="1" start="234">
this.getAiCoUnitBonus = function(co, unit, map)
{
return 1;
};
</syntaxhighlight>I actually had to look up what this does. If we step away from Andy for a bit and go to Sami's code [https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_sami.js#L305]:<syntaxhighlight lang="javascript" line="1" start="305">
this.getAiCoUnitBonus = function(co, unit, map)
{
if (unit.getUnitID !== "INFANTRY")
{
if (unit.getUnitType() === GameEnums.UnitType_Infantry)
{
return 8;
}
else if (unit.getBaseMaxRange() === 1)
{
return -1;
}
}
return 2;
};
</syntaxhighlight>It quickly becomes apparent what this method is used for. If the unit is an infantry, skip the if statement and return 2. If the unit is of type infantry (but not the 1k infantry, something like a commando), return 8. If it's a direct unit, return -1. And if it's an indirect, you go outside of the if statement and return 2.

In short, Sami prefers infantry type over infantry and indirects, and those over direct units (for CO units) (Thanks Sami!)

Andy returns 1 no matter what, so no preference.
[[Category:Modding Tutorials]]

Andy Breakdown

2023-12-30T16:32:56Z

MrDuck557: Finish Music and Modifiers

'''Notice: Modding tutorials assume you know at least the basics of coding or scripting. Commander Wars uses Javascript as the Scripting Language.''' In case you want to learn more about Javascript, you can check the tutorial here: Derek Banas' Javascript tutorial , purchase O'Reilly's excellent book on the subject JavaScript: The Definitive Guide, or check out W3 Schools Interactive Tutorials

'''This tutorial references https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_andy.js, the source code of the actual vanilla Andy in COW.'''

'''THIS IS UNFINISHED DO NOT COMPLAIN ABOUT MISSING SECTIONS'''

== Small Disclaimer ==
This will only go through vanilla Andy's js code, and not any other files. This is intended for newer players to understand the workings of what the code they're copy-pasting actually does. If you want to make a brand new CO in a mod, a good starting point is [[Custom CO]]. Alternatively, download a mod and edit to suit your needs.

Also I refer to normal CO powers as COP and super CO powers as SCOP, just clearing that up

== Some stuff in the header ==
<syntaxhighlight lang="javascript" line="1" start="1">
var Constructor = function()
{
</syntaxhighlight>The very first line (or two) of code. This defines a variable called Constructor to be a function. What does the function do? It's defined in the curly brackets {} following it. Notice how only the opening bracket is present. This is a long function (the whole CO).<syntaxhighlight lang="javascript" line="1" start="3">
this.getCOStyles = function()
{
return ["+alt", "+alt2", "+alt3"];
};
</syntaxhighlight>Due to some js... weirdness, we treat functions as objects that you can define properties of. If we called Constructor.getCOStyles() after finishing the Constructor function, we would get this. Specifically it would return ["+alt", "+alt2", "+alt3"]. This is telling the game to look for alternate CO images labeled "andy+alt", "andy+alt2", and "andy+alt3" as well as simply "andy". If you look in the corresponding images folder ([https://github.com/Robosturm/Commander_Wars/tree/master/resources/images/co/os]), we do actually find said images. This is Commander Wars's way to get CO styles, so if you want to have extra costumes for your CO, this is how you do it.<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
}
};
</syntaxhighlight>This is a custom function for the AI behavior of Andy. If it looks scary, that's because <s>it kinda is</s> there's just a bunch of variables and if statements flying around. Let's break this down further<syntaxhighlight lang="javascript" line="1" start="8">
this.getAiUsePower = function(co, powerSurplus, unitCount, repairUnits, indirectUnits, directUnits, enemyUnits, turnMode)
{

</syntaxhighlight>Again, a function definition. But this time, with words inside the function() brackets. Those are called parameters, and how you can pass data into a function. Here, the game is passing in:

* The CO (co) (specifically the player's instance of a CO, in an andy mirror match both andys are actually considered different COs)
* The power charge more than what the COP needs (powerSurplus)
* The count of all owned units on the field (unitCount)
* Count of all units less than 10hp (repairUnits)
* Count of all units that can shoot at more than 1 range (indirectUnits)
* Count of all units not an indirect unit (directUnits)
* The number of enemy units
* The turn mode of the AI, set to start of day, during the day, and end of day.

The vast majority of the time, a significant portion of these will not be used (for example, Andy doesn't really care if his units are direct or indirect, so long as they're repaired)<syntaxhighlight lang="javascript" line="1" start="10">
if (turnMode === GameEnums.AiTurnMode_StartOfDay)
{

</syntaxhighlight>This checks that the turn mode is start of day. This makes sure that Andy only ever uses his power at the start of each day.<syntaxhighlight lang="javascript" line="1" start="12">
if (co.canUseSuperpower())
{
return GameEnums.PowerMode_Superpower;
}
</syntaxhighlight>If Andy can use his SCOP of course he uses his SCOP<syntaxhighlight>
else if (powerSurplus <= 0.5 &&
co.canUsePower())
{
return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);
}
</syntaxhighlight>If Andy has at most 0.5 stars more than his COP (and if he can use his COP in the first place), return CO.getAiUsePowerAtUnitCount(co, powerSurplus, turnMode, repairUnits);?

Referencing CO.getAiUsePowerAtUnitCount, it first checks if turnMode is equal to start of day, and also if repairUnits (in Andy's getAiUsePower at least, the name is changed during the function call to unitCount) is at least 5.

If either of these conditions are not fulfilled, don't use any power.

If both of these conditions are fulfilled, use SCOP is possible, and use COP if powerSurplus <= 0.5 (and if COP is usable in the first place)

So essentially, Andy doesn't want to Hyper Repair unless he has just enough power charge and if he can repair at least 5 units.<syntaxhighlight lang="javascript" line="1" start="21">
}
};
</syntaxhighlight>Closing brackets you always need those

You may be put off at the lack of a return statement here. Won't the code break if the function doesn't return anything?

I'm put off too.

Also the semicolon at the end? This is because we're actually defining a variable (getAiUsePower) as this function. Defining a variable is a code statement. We need semicolons after each code statement so the computer knows where to end each block of code. This is a property of c++ and java as well as javascript.

Next segment!

== Power stuff ==
<syntaxhighlight lang="javascript" line="1" start="24">
this.init = function(co, map)
{
co.setPowerStars(3);
co.setSuperpowerStars(3);
};
</syntaxhighlight>init() is generally a function called to make sure that something is ready and to set up any needed variables. In this case, the only things that are done are setting COP stars to 3 and setting SCOP stars to 3. Note how the SCOP does not cost 3 stars, rather this is 3 stars on top of the COP cost of 3 stars, for a total of 6 stars.

Since the next function probably won't fit on the screen all at once, I'll just break it down now.<syntaxhighlight lang="javascript" line="1" start="30">
this.activatePower = function(co, map)
{
var dialogAnimation = co.createPowerSentence();
var powerNameAnimation = co.createPowerScreen(GameEnums.PowerMode_Power);
dialogAnimation.queueAnimation(powerNameAnimation);
</syntaxhighlight>The function is called activatePower, which is used when you activate power (COP specifically)

dialogAnimation and powerNameAnimation are used for the flashy effects whenever you use a power, the ones that appear, fill the screen with the power name, and disappear before your units get sparkles on them.

.queueAnimation is used to make sure that the whole screen is filled after the dialog finishes.<syntaxhighlight lang="javascript" line="1" start="36">
var units = co.getOwner().getUnits();
var animations = [];
var counter = 0;
units.randomize();
</syntaxhighlight>To go through all the units and make animations, we'll need to get all the units and have a place to store all the animations. counter is set to 0 and will correspond to animations's size (incidentally both are 0 right now)

units.randomize() makes sure that the units will be considered in a random order. Since animations happen in the same order, the animations are randomized as well.<syntaxhighlight lang="javascript" line="1" start="40">
for (var i = 0; i < units.size(); i++)
{
var unit = units.at(i);
</syntaxhighlight>The for loop will iterate through the units, with i being the index and unit being the current unit. This is randomized because units was randomized beforehand.<syntaxhighlight lang="javascript" line="1" start="44">
var animation = GameAnimationFactory.createAnimation(map, unit.getX(), unit.getY());
animation.writeDataInt32(unit.getX());
animation.writeDataInt32(unit.getY());
animation.writeDataInt32(CO_ANDY.powerHeal);
animation.setEndOfAnimationCall("ANIMATION", "postAnimationHeal");
</syntaxhighlight>Here the animation is set up. The animation is created on the map at the unit's position in createAnimation. Then the unit's position is written to the animation and CO_ANDY.powerHeal. powerHeal is an integer specifying the COP healing, in this case 2. The variable is useful to avoid "magic numbers", constant values that are typed in directly. If you want to change a magic number, you have to manually go into the code and edit every instance of that magic number. Keeping your constants in variables like CO_ANDY.powerHeal allows you to change the value quickly and easily from one place. You'll see variables like this later in the code.

Note: CO_<co name> is standard convention for CO variables. Often, you'll store important variables for your CO on CO_<co name> like CO_ANDY.powerHeal. CO_<co name> is how other scripts are going to access your CO, and how your own script accesses your CO.

At the end of the animation, the units will be healed for 2 hp. postAnimationHeal uses the prior three values to know what position to heal as well as how much to heal. setEndOfAnimationCall tells the animation engine to call a function (in this case postAnimationHeal) from an object (ANIMATION) at the end of the animation. Here's the actual postAnimationHeal if you're curious. [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/resources/scripts/general/animation.js#L4]

Before going any further into the animation code, I want to go into the big picture of what is actually happening.

So first of all, when an animation is created, it's going to be handled by the Commander Wars engine no matter what. It doesn't matter if no variable in your script points to it, it's going to be saved in the core game and the core game will handle it.

The power animation for the units goes something like this: make an animation for every unit in a random order, but don't have more than 5 animations going on at the same time.

With that out of the way, here's the rest of the code<syntaxhighlight lang="javascript" line="1" start="49">
var delay = globals.randInt(135, 265);
if (animations.length < 5)
{
delay *= i;
}
animation.setSound("power0.wav", 1, delay);
</syntaxhighlight>delay is set to some random number between 135 and 265. Then, if the animation queue isn't filled (length is 5), multiply the delay by i.

What delay *= i will do is approximately make sure that the animations are in order. Say we happen to roll 200 3 times, the delays would be 200 (start at 200), 400, and 600. This will make the animations appear one after the other, kind of like how it works in the original advance wars. I'll explain what happens if the delay isn't multiplied later.

animation.setSound("power0.wav", 1, delay) sets the sound of the animation. power0.wav is the filename of the sound, 1 is the number of times to repeat (1 means 1 play) and delay is how delayed it is. If you want, I believe you can add another number for volume and also set if the oldest sound should be stopped. (animation.setSound("filename", repeats, delay, volume, stopOldestSound))<syntaxhighlight lang="javascript" line="1" start="55">
if (animations.length < 5)
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
powerNameAnimation.queueAnimation(animation);
animations.push(animation);
}
</syntaxhighlight>animations.length < 5 means the animation queue isn't full. It then adds a sprite (power0) and positions it accordingly.

Looking at the source of addSprite [https://github.com/Robosturm/Commander_Wars/blob/5a820a28c520f5cfa0c18a5fe1e82a916c927f6f/game/gameanimation/gameanimation.cpp], it offsets the image so that the unit is in the center (-map.getImageSize()*1.27) (both of them), sets sleepAfterFinish (0 is no I think), sets the scale (2) and adds delay (delay). There's another parameter for loops, which would probably set repeats if you want the image to show up more than once.

powerNameAnimation.queueAnimation(animation) sets the current animation to fire right after powerNameAnimation (the screen fill with your power name). But while the animation starts right away internally, the sound and image are delayed (thanks to delay) so what you see and hear on screen actually starts a bit later (which is probably what you want). queueAnimation() is a function attached to the animation class in general, so don't be confused if you see a different animation object using this function.

animations.push(animation) sticks the current animation at the end of the animations list. This will become very relevant shortly.<syntaxhighlight lang="javascript" line="1" start="61">
else
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
animations[counter].queueAnimation(animation);
animations[counter] = animation;
counter++;
if (counter >= animations.length)
{
counter = 0;
}
}
</syntaxhighlight>else is for if the statement in the if block isn't true (in this case animations.length < 5). This would mean that the animation queue is full.

Just to recap, delay has not been multiplied by i, counter is the index of some animation in animation, and animations is full of animations.

We've seen the addSprite method before. What's different is animations[counter].queueAnimation(animation). Here, the current animation is set to fire right after animations[counter] finishes. Then the current animation replaces the old animation, and counter increases by 1. (++ does that) If counter >= animations.length (animations[counter] would throw an error), just set it back to 0.

Was that confusing? Here's a step by step diagram.

Right before the first instance of this, animations is filled with [0,1,2,3,4]. (not actually those numbers, just animations 0, 1, 2, 3, and 4)

On the first iteration of this else statement, counter is 0, so animation 0 will set 5 to fire right after it, then 5 takes 0's place. counter increases by 1.

The list looks like this: [5,1,2,3,4], and counter is 1 now.

Next iteration: [5,6,2,3,4] (6 is queued after 1, counter is 2)

Skip forwards a bit: [5,6,7,8,4] (7 after 2, 8 after 3, counter is 4)

Now the animations will do their dance [5,6,7,8,9], and counter increases by 1 to 5.

But animations[5] is not valid (remember 0 indexing), so counter is set back to 0, and the cycle repeats.

The delay works here, because we have 0,5,10,15 going "1 delay" after each other, 1,6,11,16 going "1 delay" after each other (but 1 is delayed by "1 delay" relative to 0) and the rest is similar. If you don't think this is good, feel free to mess around with the code and see what happens.<syntaxhighlight lang="javascript" line="1" start="72">
}
};
</syntaxhighlight>And that's that function done.

activateSuperpower is actually pretty similar, using much of the same mechanics to do basically the same thing.

Notable changes:<syntaxhighlight lang="javascript" line="1" start="92">
animation.writeDataInt32(CO_ANDY.superPowerHeal);
</syntaxhighlight>When using the SCOP, we use the superPowerHeal rather than the regular power heal.<syntaxhighlight lang="javascript" line="1" start="95">
if (animations.length < 7)
</syntaxhighlight>bigger queue, more animations at once<syntaxhighlight lang="javascript" line="1" start="99">
if (i % 2 === 0)
{
animation.setSound("power12_1.wav", 1, delay);
}
else
{
animation.setSound("power12_2.wav", 1, delay);
}

</syntaxhighlight>We have two sounds! i%2===0 will be true every other iteration, so we alternate between the two sounds.<syntaxhighlight lang="javascript" line="1" start="109">
animation.addSprite("power12", -map.getImageSize() * 2, -map.getImageSize() * 2, 0, 2, delay);
</syntaxhighlight>Different image, and the offset is bigger (because the image is bigger)

Again, it was basically the same thing, but with SCOP stuff.

You're asking how long the next functions are going to be?

Not very long actually, they're far simpler and mostly just for returning numbers.

== Music and Modifiers ==
Most of these functions will return a value. Not much logic in these.<syntaxhighlight lang="javascript" line="1" start="127">
this.loadCOMusic = function(co, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Power:
audio.addMusic("resources/music/cos/power.mp3", 992, 45321);
break;
case GameEnums.PowerMode_Superpower:
audio.addMusic("resources/music/cos/superpower.mp3", 1505, 49515);
break;
case GameEnums.PowerMode_Tagpower:
audio.addMusic("resources/music/cos/tagpower.mp3", 14611, 65538);
break;
default:
audio.addMusic("resources/music/cos/andy.mp3", 4466, 74972);
break;
}
}
};
</syntaxhighlight>co.getPowerMode() returns something based on what power is activated.

switch statements execute different code based on the input value. In this case that would be the power mode.

This format (a switch statement using the power mode) is actually the standard way of doing different things if your power is active or not. You don't have to memorize it, just copy-paste it a bunch.

audio.addMusic plays the music (in a loop presumably) from startTime (in milliseconds) to endTime (in milliseconds).

The break statements prevent the code from considering other cases once one case has been run.<syntaxhighlight lang="javascript" line="1" start="149">
this.getCOUnitRange = function(co, map)
{
return 3;
};
this.getCOArmy = function()
{
return "OS";
};
</syntaxhighlight>getCOUnitRange should return the CO zone range, in this case 3.

getCOArmy should return a string corresponding to the co's country. In this case Andy is from Orange Star, so this function returns "OS". You can check other COs for their country's strings. <syntaxhighlight lang="javascript" line="1" start="158">
this.superPowerHeal = 5;
this.superPowerOffBonus = 30;
this.superPowerMovementBonus = 1;

this.powerDefBonus = 20;
this.powerOffBonus = 20;
this.powerHeal = 2;

this.d2dCoZoneOffBonus = 20;
this.d2dCoZoneDefBonus = 20;
</syntaxhighlight>These are variables for easy modification of Andy's numbers. If you check the in-game wiki, these numbers should line up with what you see there. As stated above, these variables make sure you don't accidentally change the numbers in one place but not another.<syntaxhighlight lang="javascript" line="1" start="169">
this.getOffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isDefender, action, luckmode, map)
{
if (CO.isActive(co))
{
switch (co.getPowerMode())
{
case GameEnums.PowerMode_Tagpower:
case GameEnums.PowerMode_Superpower:
return CO_ANDY.superPowerOffBonus;
case GameEnums.PowerMode_Power:
return CO_ANDY.powerOffBonus;
default:
if (co.inCORange(Qt.point(atkPosX, atkPosY), attacker))
{
return CO_ANDY.d2dCoZoneOffBonus;
}
break;
}
}
return 0;
};
</syntaxhighlight>getOffensiveBonus is called when you want to find the offensive bonus of a specific unit. There are a lot of parameters for this function, but honestly most of them are pretty self-explanatory (what do you expect defender to be).

if (CO.isActive(co)) just makes sure your CO is actually active and should be used.

The switch statement is explained above. In this case, it changes the offensive bonus depending on if the power is active or not.

Note the co.inCORange() function. This is a very easy way to check if a unit is in the CO zone or not. You may be curious why this check isn't in any other case. In the original AW DoR, where CO zones were first introduced, CO zones became global while using powers. This is carried over to COW, so not only would the check be redundant (you can be sure your unit is in the map-wide zone), it may not even work (sometimes when a CO unit is moved during powers, the zone shows up as range 0).

Also the break statement at the end. This is best practice in switch statements, as it ensures you get out of the switch right away and not accidentally fall into other cases. You don't need to do this after a return statement, because return sends you out of the function as well as the switch.<syntaxhighlight lang="javascript" line="1" start="191">
this.getDeffensiveBonus = function(co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isAttacker, action, luckmode, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() > GameEnums.PowerMode_Off)
{
return CO_ANDY.powerDefBonus;
}
else if (co.inCORange(Qt.point(defPosX, defPosY), defender))
{
return CO_ANDY.d2dCoZoneDefBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, except for one thing.

A funny thing about enums, they're actually numbers.

This allows for funky stuff like co.getPowerMode() > GameEnums.PowerMode_Off. This will be true if either CO power is active.

I don't personally use this, but this is an alternative to a switch statement.<syntaxhighlight lang="javascript" line="1" start="207">
this.getMovementpointModifier = function(co, unit, posX, posY, map)
{
if (CO.isActive(co))
{
if (co.getPowerMode() === GameEnums.PowerMode_Superpower ||
co.getPowerMode() === GameEnums.PowerMode_Tagpower)
{
return CO_ANDY.superPowerMovementBonus;
}
}
return 0;
};
</syntaxhighlight>Very similar, again

Since movement takes place outside of combat, you don't have attacker, attackerX, defender, and defenderY (some variables skipped for brevity). Instead you just have the unit you're moving. This shouldn't be too relevant, but beware accidentally copying attacker and not replacing it with unit.<syntaxhighlight lang="javascript" line="1" start="220">
this.getCOUnits = function(co, building, map)
{
if (CO.isActive(co))
{
var buildingId = building.getBuildingID();
if (buildingId === "FACTORY" ||
buildingId === "TOWN" ||
BUILDING.isHq(building))
{
return ["ZCOUNIT_REPAIR_TANK"];
}
}
return [];
};
</syntaxhighlight>This function gets your exclusive CO units. In Andy's case, we have repair tanks (internal ID ZCOUNIT_REPAIR_TANK). But since it's a land unit, we don't want to build it out of any building (as much as I think Andy forgetting what an airport is supposed to do is funny).

So we check the buildingId. For compatibility with Hachi and Hachi's soul, we also add the repair tank to the build lists of towns and hqs, even though they can't build anything.<syntaxhighlight lang="javascript" line="1" start="234">
this.getAiCoUnitBonus = function(co, unit, map)
{
return 1;
};
</syntaxhighlight>I actually had to look up what this does. If we step away from Andy for a bit and go to Sami's code [https://github.com/Robosturm/Commander_Wars/blob/master/resources/scripts/cos/co_sami.js#L305]:<syntaxhighlight lang="javascript" line="1" start="305">
this.getAiCoUnitBonus = function(co, unit, map)
{
if (unit.getUnitID !== "INFANTRY")
{
if (unit.getUnitType() === GameEnums.UnitType_Infantry)
{
return 8;
}
else if (unit.getBaseMaxRange() === 1)
{
return -1;
}
}
return 2;
};
</syntaxhighlight>It quickly becomes apparent what this method is used for. If the unit is an infantry, skip the if statement and return 2. If the unit is of type infantry (but not the 1k infantry, something like a commando), return 8. If it's a direct unit, return -1. And if it's an indirect, you go outside of the if statement and return 2.

In short, Sami prefers infantry type over infantry and indirects, and those over direct units (for CO units) (Thanks Sami!)

Andy returns 1 no matter what, so no preference.

Andy Breakdown

2023-12-19T19:51:17Z

MrDuck557: A bit of work on Music and Modifiers

Andy Breakdown

2023-12-19T18:47:42Z

MrDuck557: Started music and modifiers

Andy Breakdown

2023-12-19T18:26:07Z

MrDuck557: Power stuff finished. activatePower and activateSuperpower explained

Andy Breakdown

2023-12-18T17:42:02Z

MrDuck557: Animation stuff

Andy Breakdown

2023-12-18T16:14:27Z

MrDuck557: Added unfinished notice, did part of power animation code

Andy Breakdown

2023-12-17T14:59:09Z

MrDuck557: Header code. There's actually a lot of it.

Andy Breakdown

2023-12-17T14:03:07Z

MrDuck557: Created Andy Breakdown page, added basic intro text

Custom CO

2023-12-17T14:00:04Z

MrDuck557: Added a reference to a non-existent Andy Breakdown page to reference it later. Will create Andy Breakdown page.

'''Notice: Modding tutorials assume you know at least the basics of coding or scripting. Commander Wars uses Javascript as the Scripting Language.'''
In case you want to learn more about Javascript, you can check the tutorial here: [https://www.youtube.com/watch?v=fju9ii8YsGs Derek Banas' Javascript tutorial] , purchase O'Reilly's excellent book on the subject [https://www.amazon.com/JavaScript-Definitive-Most-Used-Programming-Language/dp/1491952024/ JavaScript: The Definitive Guide], or check out [https://www.w3schools.com/js/ W3 Schools Interactive Tutorials]

'''You may download the files of this tutorial on [https://discord.com/channels/615556870064832533/688802481504911372/1010627909133811785 Discord]'''

==Setup==
In this tutorial a basic CO will be created, with an Advance Wars 2 like set of powers. The mod must be created in the mods folder for the Javascript to be detected properly.

To simplify things, we will create a CO that simply boosts the defense and offense of all units and heals up during powers. However notes to modify specific units, adding custom weapon values to units will be linked at the end of the tutorial.

*Create the following folder and file structure, inside a new '''testco''' folder leave any files empty for now. The mp3 files can be any songs of your choice, so as long as they have the same file name. The '''png''' images will be added later in the tutorial.

<syntaxhighlight lang="apacheconf">
~/mods/testco
├── images
│   └── co
│   ├── co_test+face.png
│   ├── co_test+info.png
│   ├── co_test+nrm.png
│   └── res.xml
├── mod.txt
├── music
│   └── cos
│   ├── Power.mp3
│   ├── Super.mp3
│   └── Theme.mp3
└── scripts
└── cos
└── co_test.js

</syntaxhighlight>

*To the '''mod.txt''' file add the following content. This is required for the engine to detect compatibilities between mods, and to display what your mod does

<syntaxhighlight lang="apacheconf">
name=Test CO
description=This is a test CO.
version=N/A
compatible_mods=
incompatible_mods=
required_mods=
cosmetic=false

</syntaxhighlight>

==CO Constructor==
Inside '''co_test.js''' put the following code:

<syntaxhighlight lang="javascript">
var Constructor = function()
{
this.init = function(co,map)
{
co.setPowerStars(3);
co.setSuperpowerStars(3);
};

this.getCOArmy = function()
{
return "OS";
};

}

Constructor.prototype = CO;
var CO_TEST = new Constructor();
</syntaxhighlight>

This code simply inits the constructor to create our CO, '''this.init''' sets the stars that are required for the Power and Super Power respectively.
'''this.getCOArmy''' sets to which country the CO belongs to. In this case '''OS''' sets it for the Orange Star Army. The list of values are:
'''OS''' for Orange Star, '''BM''' for Blue Moon, '''YC''' for Yellow Comet, '''GE''' for Green Earth and '''BH''' for Black Hole. Custom factions will have their own, specific strings.

==CO Intel==
Up next, we will add the Intel information of our CO.
<syntaxhighlight lang="javascript">
var Constructor = function () {

this.init = function (co, map) {
co.setPowerStars(3);
co.setSuperpowerStars(3);
};

this.getCOArmy = function () {
return "OS";
};

this.getBio = function (co) {
return qsTr("A test CO.");
};

this.getHits = function (co) {
return qsTr("Hitting");
};

this.getMiss = function (co) {
return qsTr("Missing");
};

this.getCODescription = function (co) {
return qsTr("A Simple CO created for this tutorial. All units have 10% extra Firepower and Defense");
};

this.getPowerDescription = function (co) {
return qsTr("Increases the Firepower and Defense of all units by 20%, heals 2HP to all units");
};

this.getPowerName = function (co) {
return qsTr("Power Boost");
};

this.getSuperPowerDescription = function (co) {
return qsTr("Increases the Firepower and Defense of all units by 40%, heals 5HP to all units");
};

this.getSuperPowerName = function (co) {
return qsTr("Super Power Boost");
};

this.getPowerSentences = function (co) {
return [qsTr("Attack!"), qsTr("Destroy the Enemy!")];
};

this.getVictorySentences = function (co) {
return [qsTr("Victory!")];
};

this.getDefeatSentences = function (co) {
return [qsTr("Defeat...")];
};

this.getName = function () {
return qsTr("Test CO");
};

}

Constructor.prototype = CO;
var CO_TEST = new Constructor();
</syntaxhighlight>

The anonymous functions set the values for each of the respective values in the Engine. The '''qsTr()''' function is a Qt function which is used to generate translatable strings in the Engine. You can know more about the qsTr() function here: [https://doc.qt.io/qt-6/qtquick-internationalization.html: qsTr()]

'''this.getVictorySentences''', '''this.getDefeatSentences''', '''this.getPowerSentences''' all take arrays which are randomized when a Victory, Defeat or Power activation occur.

'''this.getPowerSentences''' lists the strings for both the CO Power and Super Power.

==Adding Offensive and Defensive stats==

To add Firepower and Defense in CoW-Engine Style we can use the following functions

<syntaxhighlight lang="javascript">
//Constructor code ommited for brevity
Constructor.prototype = CO;
var CO_TEST = new Constructor();

CO_TEST.getOffensiveBonus = function (co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isDefender, action, luckMode, map) {

switch (co.getPowerMode())
{
case GameEnums.PowerMode_Tagpower:
case GameEnums.PowerMode_Superpower:
return 50;
case GameEnums.PowerMode_Power:
return 30;
default:
if (co.inCORange(Qt.point(atkPosX, atkPosY), attacker))
{
return 10;
}
return 10;
break;
}
return 0;

}

CO_TEST.getDeffensiveBonus = function (co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isAttacker, action, luckMode,map) {

switch (co.getPowerMode())
{
case GameEnums.PowerMode_Tagpower:
case GameEnums.PowerMode_Superpower:
return 50;
case GameEnums.PowerMode_Power:
return 30;
default:
if (co.inCORange(Qt.point(atkPosX, atkPosY), attacker))
{
return 10;
}
return 10;
break;
}
return 0;

}

</syntaxhighlight>

This will set the Defense and Offense of all units to 10% inside the co-zone as the day to day ability.
And increase both to 30% during the Power activation, and to 50% during the Super Powers for all units.
All bonuses are applied independend of the fact if it's the first or second co.

The following example does the same but as an AW-DS-Style CO.

<syntaxhighlight lang="javascript">
//Constructor code ommited for brevity
Constructor.prototype = CO;
var CO_TEST = new Constructor();

CO_TEST.getOffensiveBonus = function (co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isDefender, action, luckMode, map) {

if (co.getIsCO0() === true) {
switch (co.getPowerMode()) {

case GameEnums.PowerMode_Superpower:
return 50;

case GameEnums.PowerMode_Power:
return 30;

default:
return 10;
break;
}
}
return 0;

}

CO_TEST.getDeffensiveBonus = function (co, attacker, atkPosX, atkPosY,
defender, defPosX, defPosY, isAttacker, action, luckMode,map) {

if (co.getIsCO0() === true) {
switch (co.getPowerMode()) {

case GameEnums.PowerMode_Superpower:
return 50;

case GameEnums.PowerMode_Power:
return 30;

default:
return 10;
break;
}
}
return 0;

}

</syntaxhighlight>

This will set the Defense and Offense of all units to 10% as the day to day ability, increase both to 30% during the Power activation, and to 50% during the Super Power.
If the CO is the currently the first one.

==Power and Super Power Animations==
To create the Power animation we will use the following code:

<syntaxhighlight lang="javascript">
//Rest of the code ommited for brevity
var Constructor = function () {
this.activatePower = function(co, map)
{
var dialogAnimation = co.createPowerSentence();
var powerNameAnimation = co.createPowerScreen(GameEnums.PowerMode_Power);
dialogAnimation.queueAnimation(powerNameAnimation);

var units = co.getOwner().getUnits();
var animations = [];
var counter = 0;
units.randomize();
for (var i = 0; i < units.size(); i++)
{
var unit = units.at(i);

var animation = GameAnimationFactory.createAnimation(map, unit.getX(), unit.getY());
animation.writeDataInt32(unit.getX());
animation.writeDataInt32(unit.getY());
animation.writeDataInt32(2);
animation.setEndOfAnimationCall("ANIMATION", "postAnimationHeal");
var delay = globals.randInt(135, 265);
if (animations.length < 5)
{
delay *= i;
}
animation.setSound("power0.wav", 1, delay);
if (animations.length < 5)
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
powerNameAnimation.queueAnimation(animation);
animations.push(animation);
}
else
{
animation.addSprite("power0", -map.getImageSize() * 1.27, -map.getImageSize() * 1.27, 0, 2, delay);
animations[counter].queueAnimation(animation);
animations[counter] = animation;
counter++;
if (counter >= animations.length)
{
counter = 0;
}
}
}
units.remove();
};

}

</syntaxhighlight>

And for the Super Power:

<syntaxhighlight lang="javascript">
//Rest of the code omitted for brevity
var Constructor = function () {
this.activateSuperpower = function(co, powerMode, map)
{
var dialogAnimation = co.createPowerSentence();
var powerNameAnimation = co.createPowerScreen(powerMode);
powerNameAnimation.queueAnimationBefore(dialogAnimation);

var units = co.getOwner().getUnits();
var animations = [];
var counter = 0;
units.randomize();
for (var i = 0; i < units.size(); i++)
{
var unit = units.at(i);

var animation = GameAnimationFactory.createAnimation(map, unit.getX(), unit.getY());
animation.writeDataInt32(unit.getX());
animation.writeDataInt32(unit.getY());
animation.writeDataInt32(5);
animation.setEndOfAnimationCall("ANIMATION", "postAnimationHeal");
var delay = globals.randInt(135, 265);
if (animations.length < 7)
{
delay *= i;
}
if (i % 2 === 0)
{
animation.setSound("power12_1.wav", 1, delay);
}
else
{
animation.setSound("power12_2.wav", 1, delay);
}
if (animations.length < 7)
{
animation.addSprite("power12", -map.getImageSize() * 2, -map.getImageSize() * 2, 0, 2, delay);
powerNameAnimation.queueAnimation(animation);
animations.push(animation);
}
else
{
animation.addSprite("power12", -map.getImageSize() * 2, -map.getImageSize() * 2, 0, 2, delay);
animations[counter].queueAnimation(animation);
animations[counter] = animation;
counter++;
if (counter >= animations.length)
{
counter = 0;
}
}
}
units.remove();
};

}
</syntaxhighlight>

==CO Images==
In the Setup step, we created a set of folders, '''"mods/testco/images/co/"''' is where all the images for this tutorial will go. Make sure you also created the '''res.xml''' file inside the '''"mods/testco/images/co/"''' folder.

Inside '''res.xml''' place the following:

<syntaxhighlight lang="xml">
<?xml version="1.0"?>
<resources>
<set path = "mods/testco/images/co/" />
<atlas linearFilter="false">
<set scale_factor = "1.0" />
<image file="co_test+nrm.png" />
<set scale_factor = "1.0" />
<image file="co_test+info.png" />
<image file="co_test+face.png" cols = "3" />
</atlas>
</resources>
</syntaxhighlight>

'''co_test+nrm.png''' is the image that will be displayed when the power and superpowers are activated. It will also show on the Intel options of the CO. This image has no set standard and can be of any size you choose, such that it fits on the screen.
[[File:Testco+nrm.png|thumb|center|co_test+nrm.png]]

'''co_test+info.png''' is the image that shows next to the Star Meter of the CO as well as in some menus of the game. The standard size for this image is 32x12.

[[File:Testco+info.png|thumb|center| co_test+info.png]]

'''co_test+face.png''' is the portrait picture of the CO, with three different facial expressions, the order of these facial expressions is normal, happy and sad, these can be given a rows argument to have Advance Wars style animations. You can use the '''scale_factor''' parameter to resize the images in-game. The standard for this image is 144x48 (48x48 for each facial expression).

[[File:Testco+face.png|thumb|center|co_test+face.png]]

==CO Music==
Inside the constructor of the CO, place the following code:

<syntaxhighlight lang="javascript">
var Constructor = function()
{
//Rest of the code ommited for brevity
this.loadCOMusic = function (co,map) {

switch (co.getPowerMode()) {
case GameEnums.PowerMode_Power:
audio.addMusic("mods/testco/music/cos/Power.mp3", 0, 0);
break;
case GameEnums.PowerMode_Superpower:
audio.addMusic("mods/testco/music/cos/Super.mp3", 0, 0);
break;
case GameEnums.PowerMode_Tagpower:
audio.addMusic("mods/testco/music/cos/Super.mp3", 0, 0);
break;
default:
audio.addMusic("mods/testco/music/cos/Theme.mp3", 0, 0);
break;
}
};

}

Constructor.prototype = CO;
var CO_TEST = new Constructor();
</syntaxhighlight>

Make sure the files are properly placed inside the path passed to the '''audio.addMusic()''' function.

==Activating the CO==
*Start the Game.
*Click 'Options'.
*On the right hand side of the Options menu, click 'Mods'.
*Activate the checkbox 'Test CO' and click 'Exit'.
After you do, the game will restart on its own. Once the game restarts, click on 'Style CO'. The test CO should show up under Orange Star.

== Further Information ==
To learn more about the details of how the code works, this page breaks down Andy and the specifics of each segment of code.

[[Andy Breakdown]]
[[Category:Modding tutorials]]