Command An Army BUGFIX and LEBALANCE
Day-two codes, launch lag, and how to spend gems when numbers move under your roster.
On September 6, 2026 — one day after the public launch — Command An Army shipped four codes at once: RELEASE, WAR, BUGFIX, and LEBALANCE. Two of those are celebration. Two of those are patch notes wearing gem labels. This page is how to read them without a formal changelog.
Working list and rewards stay on the codes hub. This page is the meaning.
BUGFIX — 250 gems
Players called the launch laggy and buggy in the same breath they called it fun. A code named BUGFIX is the developer saying “we touched stability.” What you should do:
- Rejoin if orders were dropping yesterday. Title updates on Roblox often need a fresh client.
- Shrink the army you try to micro if hitching remains. A 30-unit mess is worse after a physics hitch than a 12-unit wall.
- Do not assume every remaining bug is gone. Assume they shipped something, paid you 250 gems, and will ship again.
- Keep the codes button path from how to redeem in muscle memory. Utility HUD can move in bug passes.
If your “bug” is Cavalry dying to spears, that is not BUGFIX. That is infantry.
LEBALANCE — 150 gems
LEBALANCE means numbers moved. We will not invent which troop got the slider. We will tell you how to react:
- Play three matches before you sell the roster.
- If horses bounce more, Spearman did their job or got a buff — keep spears.
- If walls melt faster, buy more Shieldmen, not more mystery summons.
- If a unit you never fielded suddenly feels good, it is still C until you can place it in a formation.
- Update your mental tier list after you feel it, not after one thumbnail.
150 gems is a small payout compared with RELEASE and WAR. Treat it as a patch toast, not a second launch pile.
RELEASE and WAR still matter here
They are not balance notes, but they dropped in the same bundle. If you logged in on September 7 and skipped codes because you “already played launch,” you may have missed 1,000 gems sitting next to the patch codes. Always open the codes hub on the same day you read this page.
How we will log future patches
When the group posts a real changelog in Discord, it will be summarized here with a date. Until then the log is:
| Date | Signal | Player action |
|---|---|---|
| Sep 6, 2026 | BUGFIX code | Rejoin, simplify micro |
| Sep 6, 2026 | LEBALANCE code | Replay before rerolling |
| TBD | Next all-caps code | Redeem first, theorycraft second |
Scripts after a patch
Expect script videos to claim “UPDATED FOR LEBALANCE” the same afternoon. Most are the same auto-kill GUI with a new title. Offsets break in both directions. Read script safety. A patched anti-cheat plus a stale script is how day-two accounts disappear.
What not to change
- Do not abandon defend as the default. Map bias was a player read, not a number the LEBALANCE code obviously targeted.
- Do not abandon the Castle circle names. If a troop inside the circle got tweaked, the jobs remain.
- Do not buy Skip Summon Spin as a “balance response.” It skips animations.
If the next patch is a content drop (new map, new troop), it will get its own page under this hub. A gem code is not a new map.
Play the patch. Then edit the roster. That order keeps Command An Army from becoming a spreadsheet you never deploy.
Frequently Asked Questions
Quick answers for codes, troops, and match setups.
Did LEBALANCE nerf Cavalry?
Unknown until more matches land. Play first. Keep spears either way.
Is BUGFIX required to play?
No. It is a gem code that signals a stability pass. Redeem it on the codes hub.
Should I reroll summons after LEBALANCE?
No. Walls still win defense maps. See compositions.
Where will the next changelog go?
Discord first, then this page. Official invites are on links.