Update Log - Command An Army Wiki

Overview

This is the running record of changes that have already gone live. It starts with the game's first release on June 02, 2026 and tracks the store page's most recent update date, September 10, 2026. Read it beside What's Coming Next so you never confuse a shipped change with a rumour.

Because this is an independent community wiki, every entry says where it came from. Dates and headline features come from the public Roblox store page and the developer's own Events listing; anything else is clearly labelled community observation. That habit keeps the log honest when details are scarce. Check the Update 1 page for the newest drop.

See a Recent Update in Action

When a patch adds troops, the fastest way to see them in practice is gameplay footage rather than a wall of text. This episode shows a recent run where a new unit had just been unlocked, which is exactly the kind of change the log exists to record. Follow it with the Best Units page.

How Entries Are Written

Each entry is deliberately short. It names the date, states what is publicly confirmed, and stops there instead of guessing at numbers. That means you will sometimes read 'not yet public' rather than a figure, because inventing upgrade costs or patch numbers would be worse than admitting the detail is missing. See the Ultimate Guide.

The log is built from three source types: the Roblox store page, the developer's Events listing, and observable in-game changes. Where the community disagrees, the log says so instead of picking a side. Cross-check anything that affects your spending against the live game, then confirm with the Discord Server.

Confirmed Timeline So Far

The table lists only the milestones that can be verified from the public store page and the developer's Events feed. Treat it as the backbone of the log: everything else is detail hanging off these fixed points. For what is still ahead, use the update roadmap.

How to Check If a Patch Changed Your Build

After a patch lands, run this check before you spend a single gem. It takes only a few minutes and stops you rebuilding around a change that never actually happened. Keep the Unit Tier List open while you work through the list below.

Work top to bottom: confirm the update date, check whether units you run were touched, then re-test one match before committing upgrades. Skipping the re-test is how players waste gems on a build that no longer fits, as the Gems Guide warns.

What Each Log Entry Covers

Every entry answers the same handful of questions, so you can skim a date and immediately know whether it matters to you. If an entry cannot answer one of these, it says so plainly rather than filling the gap. That is the standard the Best Strategy page also follows.

Because the developer rarely posts long patch notes, most entries are short. A date, a headline and a source label often say everything known. When more detail arrives later, the entry is expanded rather than rewritten, so the history in the Update Log stays intact.

Confirmed vs Unconfirmed

Keep this split in mind whenever you read about a new update. The confirmed column is safe to plan around; the unconfirmed column is worth watching but not worth spending on. Anything that changes your gem budget belongs in the confirmed list first. Start with the new units update.

• Confirmed: first release date, June 02, 2026.
• Confirmed: the most recent update date, September 10, 2026.
• Confirmed: the UPDATE 1 event on the official Events listing.
• Unconfirmed: exact patch numbers and balance values.
• Unconfirmed: the full roster and costs added in Update 1.
• Unconfirmed: any reward amounts tied to the event.