About this site

Who maintains this site

Command An Army Wiki is an independent, community-run reference maintained by CT, the site maintainer. It is not affiliated with, endorsed by or sponsored by Roblox Corporation or Fight, Fight, Fight!. Game trademarks, artwork and copyrights belong to their respective owners.

How we verify

• Roblox endpoints are read directly for game facts: the games, votes, groups, badges, game pass and virtual event APIs, plus the Discord invite API.
• Gameplay mechanics come from recorded creator sessions. When two independent creators describe the same thing, it is treated as community-verified; when only one does, the page says so.
• Where sources disagree, both versions are published with their sources attached. The code list is the clearest example.
• Every page carries the date its content was last changed, derived from this site's own history rather than a build timestamp.

How numbers are sourced

Damage and health values come from the developer where they are published, star costs from the official product listing, and Robux prices from the official product endpoint - all re-checked on 2026-11-05. Where the developer has not published a value, that field reads "not published" instead of carrying an estimate. If a figure disagrees with your game, send it through the corrections channel below and it is fixed with the change noted.

Update cadence

The game updates roughly weekly, so this site is reviewed on the same rhythm. Live game figures are re-read from the Roblox endpoints, codes are rechecked against both trackers, star costs are revised when creators disagree with the published values, and the event feed is re-synced so a newly announced window appears without anyone typing a date by hand. Guides change less often than the data, because the mechanics behind them are more stable than the numbers.

Why the site looks like this

The layout is deliberately narrow and dark, with the numbers given equal weight to the prose. Game reference pages are read in a hurry, usually on a phone, next to a second screen running the game, so the priority is that a star cost, a counter or a date can be found in one glance rather than scrolled for. Tables, badges and short labelled blocks do that better than long paragraphs, which is why the deeper explanation always sits below the data rather than in front of it.

It also means the site works with a slow connection. Every image is compressed and sized, the tool runs without a round trip to a server, and the advertising and analytics that fund and measure the site are loaded only after the page you asked for is interactive, so they do not compete with it for bandwidth on first paint. Which partners we work with, and how to turn them off, is set out in the privacy policy.

Corrections

If something here is wrong, say so and it will be fixed: email [email protected]. The most useful report includes what the page currently says, what your game shows, and a screenshot or clip if you have one. Accepted corrections are attributed by changing the data file and, where the change is a reversal of a previous claim, by noting what changed.