- Command an Army unit stats should be tracked by role, performance, upgrade value, and battlefield use.
- No verified numeric stat sheet is established here, so avoid treating estimated damage or health values as official.
- Attack and defense roles require different evaluations, especially around objective control and formation support.
- Upgrade priority should favor frequently used troops that improve several battle situations.
- Reliable records should include the unit name, role, observed behavior, upgrade level, and practical result.
Command an Army Unit Stats Explained
Command an Army unit stats are most useful when they help you make a better army-building decision. A raw number alone does not reveal whether a troop belongs in your frontline, protects a capture point, supports an advance, or works best as a reserve. Evaluate every unit through its battlefield role and the situations where it consistently contributes.
The confirmed gameplay loop centers on recruiting troops, arranging formations, upgrading units, capturing points, and choosing between attacking or defending. That means a useful stat guide should connect unit information to those systems rather than present unsupported damage, health, or speed values as fact.
| Stat Category | What to Record | Why It Matters |
|---|---|---|
| Combat role | Frontline, attack, defense, support, specialized | Shows where the unit fits in an army |
| Offensive value | Pressure, target access, attack contribution | Helps assess pushes and breakthroughs |
| Defensive value | Holding power, response value, objective protection | Helps evaluate defensive formations |
| Mobility | Movement behavior and repositioning needs | Affects advances, retreats, and flanks |
| Upgrade value | Improvement after investment | Supports resource planning |
| Team synergy | Useful combinations and formation fit | Prevents isolated unit choices |
Combat Performance
Judge how consistently a troop contributes during direct engagements. Consider whether it reaches the fight, stays useful, and supports the army’s main objective.
Objective Value
A unit may be valuable because it helps capture or hold an important point. Objective usefulness can matter more than isolated damage.
Upgrade Efficiency
Prioritize troops whose improvements affect many battles. Frequently used core units usually offer more dependable value than narrow specialists.
Treat unit stats as a decision tool, not a leaderboard. A balanced troop with strong formation fit can outperform a seemingly stronger unit used in the wrong situation.
Verified Data and Safe Stat Tracking
A responsible unit database separates confirmed information from player observation. The available game information confirms the presence of recruitable and upgradeable troops, formations, capture points, and Attack or Defend objectives. It does not establish a reliable public table of exact unit health, damage, attack speed, range, movement speed, or total troop counts.
For that reason, this page uses a practical tracking model instead of inventing numerical values. When official in-game values become visible, add them to the same framework and label the upgrade level or version clearly.
| Data Field | Current Status | How to Handle It |
|---|---|---|
| Unit identity | Track individually | Use the exact in-game unit name |
| Unit role | Practical classification | Mark frontline, attack, defense, support, or specialized |
| Health value | Not verified here | Record only from an official in-game display |
| Damage value | Not verified here | Do not estimate from a single battle |
| Range or reach | Not verified here | Test consistently before publishing |
| Movement speed | Not verified here | Compare under similar battlefield conditions |
| Upgrade effect | Requires observation | Record the level and visible improvement |
| Formation fit | Strategy assessment | Note compact, wide, advance, or reserve use |
When you record observations, keep the conditions consistent. Compare units at the same progression stage where possible, use similar formations, and consider whether the troop was attacking, defending, or contesting a capture point. A unit that looks weak in an open push may be useful when protecting a narrow approach or reinforcing a threatened objective.
Recommended record format:
- Unit name: Exact displayed name.
- Role: Primary battlefield assignment.
- Upgrade level: The level used during observation.
- Best situation: Attack, defense, capture, reserve, or mixed combat.
- Formation fit: The formation where the unit performed most reliably.
- Observed weakness: The situation that reduces its value.
- Upgrade recommendation: High, medium, situational, or low priority.
Unverified numbers can mislead players and quickly make a wiki unreliable. If a value is observed rather than officially displayed, label it as an observation and include the test conditions.
Step-by-Step Unit Stat Comparison
Use the following process whenever you need to compare troops or update a unit page. It works for new players building a first army and for experienced players reviewing a formation after an upgrade or balance change.
Define the Battlefield Job
Decide what the unit is expected to do before judging its performance. A frontline troop, objective defender, attack specialist, and reserve unit should not be measured by exactly the same standard.
Record Confirmed Information
Write down the displayed unit name, visible role, upgrade level, unlock information, and any official values shown in the experience. Leave unsupported fields marked as unverified instead of filling them with guesses.
Test Formation Compatibility
Compare the troop in a compact formation, a wider defensive line, or a reserve group when appropriate. Note whether it stays with the army or becomes exposed during movement.
Evaluate Attack and Defense Use
Review the unit during both pressure and protection. Ask whether it helps reach an enemy position, maintain a push, defend a capture point, or respond to a counterattack.
Set an Upgrade Priority
Give the unit a high priority when it is frequently used, improves several matchups, and contributes to the army’s main plan. Use a situational rating for narrow counters.
| Comparison Stage | Main Question | Useful Result |
|---|---|---|
| Role check | What job does this troop perform? | Prevents unfair comparisons |
| Formation test | Does it stay effective when organized with allies? | Identifies practical deployment |
| Battle test | Does it help attack, defend, or capture? | Connects stats to objectives |
| Upgrade review | Does investment improve repeated battles? | Establishes resource priority |
| Weakness review | Where does the troop lose value? | Creates honest strategy notes |
A good comparison should end with a recommendation that players can act on. Instead of writing “Unit A is better,” explain which unit is more appropriate for a compact attack, a capture-point defense, a mixed formation, or a reserve group. This keeps the guide useful even when team compositions and battlefield conditions change.
Make recommendations by scenario. “Best for holding a capture point” is more useful and more accurate than calling one troop the best in every situation.
Using Unit Stats in Formations
Unit information becomes meaningful when it changes how you arrange and command the army. Formations should match the current objective, and the same troop can have different value depending on whether the team is advancing, holding ground, or preparing a counterattack.
| Formation | Best Use | Stat Priorities | Common Risk |
|---|---|---|---|
| Compact | Direct attacks and concentrated fights | Combat value, survivability, support fit | Overcommitting to one area |
| Wide | Holding ground and covering approaches | Defensive value, consistency, response range | Groups become isolated |
| Advance | Moving toward enemy territory | Mobility, cohesion, sustained pressure | Forward units lose support |
| Objective Defense | Protecting capture points | Holding power, reinforcement value | Stacking every troop on one spot |
| Flanking Group | Pressuring an exposed side | Mobility, independence, timing | Main force becomes too weak |
| Reserve Group | Reinforcing or counterattacking | Flexibility, response value, matchup coverage | Reserves arrive too late |
Use compact formations when the army needs concentrated strength. They are easier to command during a direct push and reduce the chance that separate groups enter the fight at different times. However, do not move the full formation forward without checking whether the target position can be held afterward.
Use wide formations for controlled defense, but avoid excessive spacing. A defensive line should cover important approaches while keeping nearby groups close enough to support one another. If every subgroup can be defeated separately, the formation is too wide for the current threat.
An objective defense formation should include both a holding force and a response force. Keep enough troops near the capture point to maintain control, but position additional units where they can intercept an incoming push. This is often more reliable than placing the entire army directly on the objective.
Attack Build
Combine dependable combat troops with enough support to maintain pressure. Advance together, focus on the objective, and reorganize after gaining ground.
Defense Build
Protect the most important approaches first. Keep reinforcement strength available so one enemy push does not force the entire army away from the point.
Flexible Build
Use a strong core, a smaller specialist group, and a reserve. This setup gives the team options when the battlefield changes quickly.
Do not judge a unit outside the formation it was designed to support. Position, timing, and nearby allies can change the practical value of the same troop.
Unit Review Checklist and FAQ
Use this checklist before publishing a unit page, changing a tier placement, or spending resources on an unfamiliar troop. It helps keep the wiki accurate and focused on useful decisions.
Unit Review Checklist:
- Confirm the exact in-game unit name and current upgrade level
- Separate official values from player observations
- Assign the troop a clear primary battlefield role
- Test the unit in attack, defense, or objective-focused situations
- Record formation fit, weaknesses, and upgrade priority
| Rating | Meaning | Recommended Use |
|---|---|---|
| High Priority | Strong repeated value across common battles | Core army upgrades |
| Medium Priority | Useful in regular but limited situations | Supporting investments |
| Situational | Valuable against specific setups or objectives | Counter or specialist roles |
| Low Priority | Limited value when stronger options are available | Temporary or gap-filling use |
The strongest unit page is not necessarily the one with the most numbers. It is the page that tells players what the troop does, where it belongs, what it supports, and when another option may be more appropriate. Keep revisions tied to visible game changes, tested observations, and clearly labeled upgrade stages.
Q: What should Command an Army unit stats include?
A useful entry should include the exact unit name, battlefield role, visible upgrade information, formation fit, attack and defense use, objective value, weaknesses, and upgrade priority. Add numerical health, damage, range, or speed only when those values are officially displayed or consistently verified.
Q: Are exact troop damage and health values confirmed in this guide?
No. Unsupported numerical values are not presented as official data. Use the tracking framework to record values from a reliable in-game display or a repeatable test, and label observations with their upgrade level and conditions.
Q: How do I decide which troop deserves upgrades first?
Start with frequently used core troops that contribute to several battles. Favor units that support your regular attack and defense plans before investing heavily in narrow specialists used only for specific matchups.
Q: Can a defensive unit be useful during an attack?
Yes. A defensive troop can protect a newly captured point, cover an approach, or remain as a reserve while the main force advances. Its value depends on the objective and formation rather than its label alone.
Keep every stat entry version-aware and scenario-focused. Clear labels, honest uncertainty, and practical formation advice make a unit database more useful than unsupported rankings.