How to Read a Battle Report

A real report, opened in the correct order

A complete report is not one screen. Work through Heroes, Army and power sources, then Battle Statistics. Every English screen below comes from the same battle, so the comparisons and worked diagnosis remain consistent from beginning to end.

01

Heroes: formation, gear and skills

First confirm exactly who fought, where they were placed and how developed they were.

Formation

Confirm the front and back rows, hero level, stars, rarity and troop type. A lane mismatch can matter more than a small power gap.

Gang

Compare the same four slots hero by hero. Look for level, promotion dots and mythic progression rather than judging total squad power alone.

Skills and weapons

Scroll through every skill row and check exclusive-weapon milestones. Two identical portraits can perform very differently.

02

Army, drone and permanent power

Now separate the troop foundation from the extra systems strengthening the formation.

Army and soldiers

In the Army tab compare troop tier, quantity, morale, Attack, Defence and HP. If this base is weaker, do not blame the hero cards first.

Drone impact

Drone level, components and skill chips add power and battle effects. Keep the same preset when testing a hero change or the comparison is contaminated.

Wall of Honor

This permanent hero investment appears inside Hero Power. It can explain why apparently similar levels and stars still produce different real strength.

03

Battle Statistics: what happened

Only after checking the inputs should you diagnose casualties, hero damage, skill detail and drone contribution.

Troop result

Read killed, hospitalised, lightly wounded and surviving troops for both sides before looking for a cause.

Hero contribution

Compare each damage total with that hero’s battlefield job and survival time. The smallest bar is not automatically the failure.

Skill drill-down

Open the magnifying glass beside a hero to see which skills actually contributed. The total bar cannot show timing or missed casts.

Break down the Battle Statistics screen

The blue side won this example and retained 1,849 troops, while the red side had none remaining. The numbered key now matches the English labels visible in the report.

1
2
3
4
5
6

1. 1Troop outcomeKilled, hospitalised, lightly wounded and surviving troops for both sides.
2. 2Hero damageDamage attributed to each hero. Compare heroes by battlefield job, not by identical expectations.
3. 3Hero portraitsConfirm the exact formation, troop type, rarity, level and star development before judging the bars.
4. 4Damage barsA fast visual comparison of each hero’s contribution within this one fight.
5. 5Magnifying glassOpen it to inspect the hero’s skill-by-skill damage instead of relying on the total alone.
6. 6Drone damageThe drone has its own contribution. Do not accidentally credit this damage to a hero.

1. Start with the troop outcome

The four icons at the top represent troops killed, sent to hospital, lightly wounded and surviving. In this example:

This immediately tells us that the left squad won decisively enough to retain a substantial force. It does not yet tell us why. Troop tier, morale, formation, heroes, gear, drone, research and temporary bonuses can all contribute.

2. Confirm what each hero was supposed to do

Before comparing numbers, identify the five battlefield jobs. Defence heroes normally create time in the front row. Attack heroes convert that time into damage. Support heroes may raise team Attack, reduce incoming damage, heal, shield or disrupt the enemy.

The portraits also reveal troop type. Apply the counter cycle before diagnosing investment: Tank beats Missile, Missile beats Aircraft, Aircraft beats Tank. A counter disadvantage can change both survival time and damage output.

3. Read damage dealt without blaming the smallest bar

On blue, the five heroes dealt approximately 1.8M, 2.7M, 15.6M, 3.7M and 8.7M. Kimberly and Stetmann produced most of blue’s hero damage, which is healthy for the formation’s main damage dealers. On red, Kimberly led at 7.4M, but the other four heroes combined for only about 3.43M.

Use these three comparisons:

1. Compare the hero with its job. A defender and a damage dealer should not produce identical totals.
2. Compare the same hero across repeated fights. This is more useful than comparing unrelated heroes in one report.
3. Compare damage with survival time. A low total caused by an early death requires a survival fix before an Attack upgrade.

Damage dealt answers “how much?” The replay and skill drill-down answer “when, how and against whom?” You need both before spending.

4. Open the magnifying glass

Each magnifying-glass button opens that hero’s detailed damage information. Use it to separate the auto attack, tactics skill, exclusive-weapon effects and other recorded contributions where the live report exposes them.

The drill-down answers questions the total bar cannot:

• Did the hero activate its tactics skill at all?
• Did it complete one cycle or several?
• Did most damage come from the expected skill?
• Did an exclusive-weapon effect materially change the result?
• Was the hero alive but contributing very little?

If the main attacker died just before a major cast, improving the protecting defender, changing lanes or adding survival may produce more damage than upgrading the attacker’s gun.

5. Add damage taken and healing

Scroll further when the report includes damage-taken and healing sections. Interpret them as evidence of role performance:

6. Keep drone damage separate

The Equivalent Damage Output row records the separate drone contribution: approximately 4.6M for blue and 1.9M for red in this example. The Army screen helps explain that gap: blue has the higher Combat Boost level, more chip stars and stronger component-derived hero attributes.

When testing a hero or gear change, keep the same drone preset. Otherwise the before-and-after report contains two changed variables and cannot prove which one caused the result.

7. Use the replay to add the missing timeline

The statistics screen has totals, not a complete timeline. Watch the replay and record:

1. The first hero to die and the approximate time.
2. The lane that collapsed first.
3. Whether the main attacker used its important tactics skill before dying.
4. Whether control effects interrupted a cast.
5. Whether the battle ended through elimination or timeout.

A defender taking 30M damage over a long fight is different from a defender disappearing in the opening burst. An attacker dealing 8M before dying at five seconds may not need more Attack—it may need enough protection to reach the next cast.

Worked diagnosis: what this example really says

From the visible report we can safely conclude:

• Blue won and retained 1,849 troops; red had no survivors.
• Both sides received the same five-Tank 20% lineup bonus, so the result was not caused by one side missing its formation bonus.
• Blue began with more units and 1.06 times red’s morale, which the report states produced 106% battle damage.
• Blue Kimberly and Stetmann were its main hero damage sources at 15.6M and 8.7M.
• Blue’s equivalent damage contribution also led 4.6M to 1.9M, supported by a clear drone-development advantage.

We cannot safely conclude from this screen alone that one gear item, hero or skill caused the victory. A responsible diagnosis would next open the skill details, compare damage taken, check troop types and watch the first death in the replay.

The two-minute report checklist

1. Outcome: victory, defeat, timeout and troops remaining.
2. Context: troop types, counter, lineup bonus and mode rules.
3. First collapse: which hero and which lane failed first?
4. Damage: did the main attackers survive and perform their jobs?
5. Protection: did defenders absorb useful pressure or vanish early?
6. Support: judge buffs, healing and control—not only personal damage.
7. Skills: open the magnifying glass and check important activations.
8. Drone: keep its damage and preset separate from hero changes.
9. Test: change one variable and repeat the same matchup.

Choose the next action from the failure

Continue your War Room training

• Kampfgrundlagen — turn report evidence into controlled upgrades.
• Aufstellungen & Positionierung — understand lanes, roles and protection.
• Fahrzeugzähler — test when a counter swap is actually worthwhile.
• Mythisches Ausrüstungteil — match defensive and offensive gear to the visible constraint.

Referenzen und Nachweise

1. GzOn Academy live English battle report, captured 25 July 2026 (Heroes, Army, Statistics, gear, skills, drone, technology, units and Wall of Honor screens).
2. Official Last War Support — How to Build the Best Squad (roles, positions, troop counters and lineup bonuses).
3. Official Last War Support — Drone Development (drone attacks, hero bonuses and presets).
4. Last War Wiki — Understanding Troop Stats (power, morale and troop contributions).

Last evidence review: 25 July 2026. Every reproduced report screen belongs to the same English-language battle. Live game labels, battle rules and skill descriptions override this captured example after balance changes.