Expired Command An Army Codes

Command An Army codes are time-limited. The first public batch dropped on September 6, 2026, one day after the Roblox launch. As of that update, no code from the launch set is confirmed expired. This page still exists because players will paste yesterday’s list into next week’s patch and then assume the wiki is wrong.

When a code dies, it leaves the working codes table and lands here with the last known reward. Do not redeem from this page. Use it as a stop list.

Current expired list

Code	Last known reward	Status
—	—	No confirmed expired codes yet

That empty table is intentional. Inventing expired codes would be as bad as inventing live ones. If RELEASE, WAR, BUGFIX, or LEBALANCE starts failing for multiple accounts, we move it here the same day.

How we mark a code expired

A code is expired when:

• The redeem window returns an expired or invalid state on a fresh account that never claimed it.
• Multiple players report the same failure after a title update.
• The official Discord (discord.gg/commandrblx) or group shout retires it.

A code is not expired when:

• You already redeemed it (that is “already used,” not dead).
• You typed Releace or added a space.
• You are still in the tutorial and the button is missing.
• You are redeeming a code from Control Army, Make a Military Army, or Command Your Clone Army. Those are different Roblox games.

If your attempt fails, walk the checklist on how to redeem codes before you declare the whole list dead.

Why launch codes will die

Roblox army games use codes as a patch drumbeat. RELEASE exists to celebrate the September 5, 2026 public launch. WAR is a theme code. BUGFIX is an apology code for launch lag and bugs. LEBALANCE is a numbers-tweak code tied to the first balance patch. Theme codes almost always expire after the next content drop. Treat 1,400 gems as a launch bonus, not a salary.

When they expire, your gem income shifts to matches, summons, and whatever the next update ships. That is why the gem planner tells you to spend RELEASE and WAR on a core roster instead of saving “for later” with no later plan.

What to do the day a code dies

1. Stop retrying it. Spamming redeem does not revive a server-side flag.
2. Check the codes hub for a replacement. New codes often land in the same patch that killed the old ones.
3. Read the updates hub so you know whether the patch also changed troop math. A dead LEBALANCE plus a silent Cavalry nerf is a different problem than a dead code alone.
4. Join the Discord listed on official links. Codes are posted there first.
5. Keep playing. Expired codes do not wipe gems you already claimed.

Lookalike codes to ignore

The name “Command An Army” collides with older army titles in search. If a blog lists Release for gold, mushrooms, or ancient fragments, that is not this game. Command An Army payouts at launch are gems. If a code promises a Humvee, a Healer Barrack, or clone camp levels, you are on the wrong wiki.

Our working list is only:

• RELEASE — 500 gems
• WAR — 500 gems
• BUGFIX — 250 gems
• LEBALANCE — 150 gems

Anything else should be treated as unverified until it is reproduced in-game and added to the hub.

Expired codes and scripts

Script videos will keep showing the launch list weeks after it dies. Auto-redeem tools cannot create a code the server has retired. If a script GUI still lists RELEASE in green, ignore the color. Confirm on this page and the codes hub. Running a script to brute-force old codes is a good way to trip whatever anti-cheat the group adds later. See script safety.

Keep a personal log

Write the four launch codes down and tick them when you redeem. When the table on this page finally has rows, you will know instantly whether a failure is “already used” or “now expired.” Share that log if you switch accounts; codes do not transfer.

For the live list, go back to working codes. For the button location, stay on how to redeem. For why the first codes were named after bugs and balance, read the September release recap.