{"id":211,"date":"2026-07-25T17:44:00","date_gmt":"2026-07-25T17:44:00","guid":{"rendered":"https:\/\/gamezoneacademy.com\/mission-files\/battle-report-analysis\/"},"modified":"2026-07-29T18:33:58","modified_gmt":"2026-07-29T18:33:58","slug":"battle-report-analysis","status":"publish","type":"gza_mission_file","link":"https:\/\/gamezoneacademy.com\/fr\/mission-files\/battle-report-analysis\/","title":{"rendered":"Comment lire un rapport de bataille"},"content":{"rendered":"
R\u00e9ponse rapide<\/strong><\/p>\n

Read the report from top to bottom: battle outcome, troop condition, hero damage, skill drill-down and drone contribution. Then combine those totals with the replay. The lowest damage number is not automatically the problem, and the highest power number does not explain the result.<\/p>\n<\/div>\n

A real report, opened in the correct order<\/h2>\n

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

\n
\n
01<\/span><\/p>\n
\n

Heroes: formation, gear and skills<\/h2>\n

First confirm exactly who fought, where they were placed and how developed they were.<\/p>\n<\/div>\n<\/header>\n

\n
\"English
Overview:<\/strong> blue has 37.7M hero power against red\u2019s 29.2M. Both use five Tank heroes and receive the same 20% lineup bonus, so troop-type composition is not the differentiator.<\/figcaption><\/figure>\n
\"English
Gear:<\/strong> compare each hero\u2019s four equipment slots, level and promotion dots. Blue leads 5.2M to 3.8M in this section.<\/figcaption><\/figure>\n
\"English
Hero Skill:<\/strong> read each numbered skill and MAX label rather than relying on total hero power. Blue leads only slightly here, 1.5M to 1.4M.<\/figcaption><\/figure>\n<\/p><\/div>\n
\n
Formation<\/strong><\/p>\n

Confirm the front and back rows, hero level, stars, rarity and troop type. A lane mismatch can matter more than a small power gap.<\/p>\n<\/article>\n

Vitesse<\/strong><\/p>\n

Compare the same four slots hero by hero. Look for level, promotion dots and mythic progression rather than judging total squad power alone.<\/p>\n<\/article>\n

Skills and weapons<\/strong><\/p>\n

Scroll through every skill row and check exclusive-weapon milestones. Two identical portraits can perform very differently.<\/p>\n<\/article><\/div>\n<\/section>\n

\n
02<\/span><\/p>\n
\n

Army, drone and permanent power<\/h2>\n

Now separate the troop foundation from the extra systems strengthening the formation.<\/p>\n<\/div>\n<\/header>\n

\n
\"English
Drone:<\/strong> blue has Combat Boost 354 against 255 and 17 chip stars against 8. The report then translates the component gap into HP, Defence and Attack added to every hero.<\/figcaption><\/figure>\n
\"English
Technology and permanent bonuses:<\/strong> compare research percentages category by category, then decorations and cosmetics. Blue leads 6.2M to 4.5M in Tech and 2.7M to 1.0M in Decoration.<\/figcaption><\/figure>\n
\"English
Units and Wall of Honor:<\/strong> both use Level 10 troops, but blue fields 2,405 units with 1.80M morale against 2,255 units with 1.69M morale. The report explicitly states that blue therefore inflicts 106% damage.<\/figcaption><\/figure>\n<\/p><\/div>\n
\n
Army and soldiers<\/strong><\/p>\n

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.<\/p>\n<\/article>\n

Drone impact<\/strong><\/p>\n

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.<\/p>\n<\/article>\n

Mur d'honneur<\/strong><\/p>\n

This permanent hero investment appears inside Hero Power. It can explain why apparently similar levels and stars still produce different real strength.<\/p>\n<\/article><\/div>\n<\/section>\n

\n
03<\/span><\/p>\n
\n

Battle Statistics: what happened<\/h2>\n

Only after checking the inputs should you diagnose casualties, hero damage, skill detail and drone contribution.<\/p>\n<\/div>\n<\/header>\n

\n
\"English
Statistics, upper screen:<\/strong> the report starts with casualties and survivors, followed by damage from every hero and the separate equivalent damage contribution.<\/figcaption><\/figure>\n
\"English
Statistics, lower screen:<\/strong> Damage and DMG Taken must be read together. Blue\u2019s heroes dealt far more total damage while taking far less pressure.<\/figcaption><\/figure>\n<\/p><\/div>\n
\n
Troop result<\/strong><\/p>\n

Read killed, hospitalised, lightly wounded and surviving troops for both sides before looking for a cause.<\/p>\n<\/article>\n

Hero contribution<\/strong><\/p>\n

Compare each damage total with that hero\u2019s battlefield job and survival time. The smallest bar is not automatically the failure.<\/p>\n<\/article>\n

Skill drill-down<\/strong><\/p>\n

Open the magnifying glass beside a hero to see which skills actually contributed. The total bar cannot show timing or missed casts.<\/p>\n<\/article><\/div>\n<\/section>\n<\/div>\n

Break down the Battle Statistics screen<\/h2>\n

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

\n
\n
\n \"English
\n 1<\/span>
\n 2<\/span>
\n 3<\/span>
\n 4<\/span>
\n 5<\/span>
\n 6<\/span>\n <\/div>
Real Last War report used with source attribution. Values and heroes belong to this example only; the reading method applies to your own reports.<\/figcaption><\/figure>\n
    \n
  1. 1<\/b>Troop outcome<\/strong>Killed, hospitalised, lightly wounded and surviving troops for both sides.<\/span><\/li>\n
  2. 2<\/b>Hero damage<\/strong>Damage attributed to each hero. Compare heroes by battlefield job, not by identical expectations.<\/span><\/li>\n
  3. 3<\/b>Hero portraits<\/strong>Confirm the exact formation, troop type, rarity, level and star development before judging the bars.<\/span><\/li>\n
  4. 4<\/b>Damage bars<\/strong>A fast visual comparison of each hero\u2019s contribution within this one fight.<\/span><\/li>\n
  5. 5<\/b>Magnifying glass<\/strong>Open it to inspect the hero\u2019s skill-by-skill damage instead of relying on the total alone.<\/span><\/li>\n
  6. 6<\/b>Drone damage<\/strong>The drone has its own contribution. Do not accidentally credit this damage to a hero.<\/span><\/li>\n<\/ol>\n<\/div>\n

    1. Start with the troop outcome<\/h2>\n

    The four icons at the top represent troops killed, sent to hospital, lightly wounded and surviving. In this example:<\/p>\n

    \n\n\n\n\n\n\n
    Side<\/th>\nKilled<\/th>\nHospital<\/th>\nLightly wounded<\/th>\nSurvived<\/th>\n<\/tr>\n<\/thead>\n
    Left \/ blue<\/strong><\/td>\n105<\/td>\n334<\/td>\n117<\/td>\n1,849<\/td>\n<\/tr>\n
    Right \/ red<\/strong><\/td>\n0<\/td>\n1,355<\/td>\n900<\/td>\n0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

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

    Important distinction<\/strong><\/p>\n

    \u201cLightly wounded,\u201d \u201chospitalised\u201d and \u201ckilled\u201d are different outcomes. Do not describe every missing troop as permanently lost. The mode and its rules determine where casualties go.<\/p>\n<\/div>\n

    2. Confirm what each hero was supposed to do<\/h2>\n

    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.<\/p>\n

    \n\n\n\n\n\n\n\n
    R\u00f4le<\/th>\nReport question<\/th>\nDo not assume<\/th>\n<\/tr>\n<\/thead>\n
    D\u00e9fense<\/strong><\/td>\nDid the hero absorb pressure and remain alive long enough for the back row to cycle skills?<\/td>\nLow personal damage means the defender failed.<\/td>\n<\/tr>\n
    Attaque<\/strong><\/td>\nDid the hero survive long enough to use its important tactics skill, and did that skill hit useful targets?<\/td>\nThe highest final total always means correct positioning.<\/td>\n<\/tr>\n
    Soutien<\/strong><\/td>\nDid the team benefit from its buff, healing, protection or control effect?<\/td>\nIts value must appear in its own damage bar.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

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

    3. Read damage dealt without blaming the smallest bar<\/h2>\n

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

    Use these three comparisons:<\/p>\n

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

      Damage dealt answers \u201chow much?\u201d The replay and skill drill-down answer \u201cwhen, how and against whom?\u201d You need both before spending.<\/p>\n<\/blockquote>\n

      4. Open the magnifying glass<\/h2>\n

      Each magnifying-glass button opens that hero\u2019s 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.<\/p>\n

      The drill-down answers questions the total bar cannot:<\/p>\n