Battle Reports are one of the most useful tools for understanding combat results in Last War: Survival.

A Battle Report is more than a victory or defeat screen. It can show the armies involved, troop results, hero performance, damage, survivability, and other combat information depending on the type of battle.

The real value of a Battle Report is not simply knowing who won.

It is understanding:

Why did the battle end this way, and what should I change before the next fight?

What Is a Battle Report?

After a combat encounter, Last War: Survival records the result in your reports/mail system.

Depending on the battle type, the report can provide information about:

• Attacker and defender
• Heroes used
• Troop type
• Army statistics
• Troop results
• Hero performance
• Damage dealt
• Damage received
• Battle result
• Remaining forces
• Rally participation
• Special battle objectives

The exact information displayed can vary depending on the type of battle.

Examples include:

• World Map PvP
• PvE battles
• Rally attacks
• Rally defense
• Base defense
• Garrison battles
• City/territory combat
• Other special battle content

The Most Important Rule

Do not judge a Battle Report from a single number.

For example:

• Higher Power does not automatically explain a win.
• Higher damage does not automatically mean the formation was optimal.
• More casualties do not automatically mean the squad was weak.
• A victory does not automatically mean there is nothing to improve.

Instead, read the report as a complete picture.

A useful analysis order is:

1. Battle Result
       ↓
2. Troop Matchup
       ↓
3. Army / Morale
       ↓
4. Hero Survivability
       ↓
5. Hero Damage & Skills
       ↓
6. Troop Results
       ↓
7. Formation Problems
       ↓
8. Upgrade Priority

Battle Result

The first thing to check is obviously the result.

But do not stop there.

A result tells you what happened, not necessarily why it happened.

Victory

A victory can happen because of:

• Higher combat stats
• Better heroes
• Better Hero Skills
• Better equipment
• Better troop tier
• More troops
• Better troop matchup
• Better formation
• Better morale
• Rally support
• Other combat bonuses

A victory against a significantly weaker opponent provides limited information about your actual build.

The most useful reports are often close battles.

Defeat

A defeat does not automatically mean:

"I need more Power."

Instead, determine whether the problem was:

• Troop counter
• Hero composition
• Formation
• Hero survivability
• Damage output
• Troop quantity
• Troop tier
• Morale
• Equipment
• Skills
• Research
• Rally composition

The objective is to identify the limiting factor.

Attacker vs Defender

Always establish which side you are analyzing.

Check:

• Your side
• Enemy side
• Attack/defense role
• Number of participating squads
• Whether the fight was solo or rally-based

This matters because the same formation can perform differently depending on the situation.

For example, a report involving a rally, garrison, or multiple participating squads should not be interpreted exactly like a simple one-squad PvP battle.

Army Information

The Army section is one of the most important parts of a Battle Report.

Depending on the report type, it can show information related to:

• Troop type
• Troop quantity
• Troop tier
• Morale
• Army strength
• Other combat-related values

Do not ignore these numbers.

A hero lineup can look stronger on paper while the actual army entering combat is weaker.

Troop Type Matchup

The Last War combat triangle is fundamental to Battle Report analysis.

The basic relationship is:

Tank
  ↓
beats
  ↓
Missile

Missile
  ↓
beats
  ↓
Aircraft

Aircraft
  ↓
beats
  ↓
Tank

In other words:

• Tank counters Missile
• Missile counters Aircraft
• Aircraft counters Tank

A significant type disadvantage can heavily affect the result of a close fight.

citeturn0search0turn0search5

Never Compare Power Without Checking the Counter

This is one of the most common mistakes when analyzing reports.

Example:

Your Squad
Power: 25M
Type: Tank

Enemy Squad
Power: 24M
Type: Aircraft

The Power values are close, but the matchup is unfavorable for the Tank squad.

Therefore, simply saying:

"I lost even though I had more Power."

does not provide enough information.

Always check the troop-type matchup first.

Morale

Morale is another important factor that can be overlooked.

Morale affects combat performance and can create meaningful differences between otherwise similar armies.

The Battle Report can be used to compare the morale of the participating armies.

Morale can be affected by factors including:

• Troop tier
• Troop quantity
• Research
• March/troop capacity
• Other progression bonuses

A larger or better-developed army can therefore have a meaningful combat advantage that is not obvious from Hero Power alone. citeturn1search12turn1search7

Practical Rule

If two squads look similar but one consistently performs much better, check:

• Morale
• Troop quantity
• Troop tier
• Research
• March size

before assuming the difference comes from Heroes alone.

Troop Results

Battle Reports can show what happened to your troops during the battle.

Depending on the battle type, results may include categories such as:

• Killed
• Hospitalized
• Injured
• Survived

These categories should not automatically be treated as identical.

For example, not every troop that fails to continue fighting represents a permanent troop loss.

Always consider the battle type and the game's current rules when interpreting casualty categories.

Surviving Troops

Surviving troops are important because they show how much of your army remained operational after the fight.

A victory with very heavy losses can tell a completely different story from a clean victory.

For example:

Battle A
Win
Very low losses
        ↓
Strong advantage

Battle B
Win
Very heavy losses
        ↓
Possible weakness

The second battle may indicate that your squad is winning, but only because it has just enough power to overcome the opponent.

Hero Performance

Hero performance is one of the most useful sections of a Battle Report.

Look at:

• Damage dealt
• Heroes surviving
• Heroes dying early
• Skill contribution
• Relative performance between heroes

The goal is not necessarily to find the hero with the highest number.

You want to understand the role each hero played.

Damage Dealers

If a damage hero consistently produces high damage, the hero is performing its primary role.

If the same hero repeatedly produces very low damage, investigate:

• Position
• Survivability
• Hero Skills
• Equipment
• Enemy matchup
• Hero synergy
• Troop composition

Do not immediately replace the hero.

First determine why the damage is low.

Frontline Heroes

Frontline heroes are responsible for absorbing pressure and protecting the backline.

If both frontline heroes die extremely early, your damage heroes may not have enough time to perform.

This can produce a report pattern like:

Frontline dies quickly
        ↓
Backline exposed
        ↓
Damage output collapses
        ↓
Battle ends quickly

The solution may be:

• Better defensive equipment
• Higher Hero Skills
• Better formation
• Stronger frontline heroes
• More appropriate squad composition

Backline Heroes

Backline heroes generally need enough protection to remain active long enough to perform their role.

If your backline survives but damage remains low, investigate:

• Hero Skills
• Equipment
• Offensive stats
• Hero synergy
• Troop matchup
• Enemy defenses

Do not automatically assume the frontline is the problem.

Hero Death Order

One of the most useful things to observe is which heroes die first.

If the same hero repeatedly dies first across multiple comparable reports, investigate that hero's role and position.

For example:

Report 1 → Front hero dies first
Report 2 → Same front hero dies first
Report 3 → Same front hero dies first

This is much more meaningful than a single unusual result.

Repeated patterns are the key.

Hero Skills

A hero's total damage does not tell the entire story.

Hero Skills can contribute:

• Direct damage
• Buffs
• Debuffs
• Defense
• Survivability
• Energy generation
• Team utility

A support hero may therefore appear to deal less damage while still being extremely valuable.

Do not judge a support hero solely by its damage number.

Formation Analysis

Formation can be the difference between a win and a loss.

A common structure is:

FRONT ROW
[ Hero ] [ Hero ]

BACK ROW
[ Hero ] [ Hero ] [ Hero ]

The frontline generally needs to protect the backline.

The exact optimal positions depend on:

• Hero abilities
• Hero roles
• Enemy formation
• Squad type
• Combat mode

Frontline Problems

If the frontline disappears very quickly:

Check:

• Hero HP
• Hero Defense
• Equipment
• Defensive skills
• Hero level
• Stars
• Troop quantity
• Troop tier
• Formation

The objective is not simply to make the frontline stronger.

It is to keep the frontline alive long enough for the squad's win condition to work.

Backline Problems

If the backline survives but the enemy does not take enough damage:

Check:

• Damage heroes
• Hero Skills
• Equipment
• Offensive stats
• Hero synergy
• Troop matchup

This is a different problem from a frontline collapse.

Battle Duration

Battle duration can provide useful context.

Short Battle + Heavy Loss

Possible causes:

• Large Power difference
• Severe troop counter
• Weak frontline
• Large stat difference
• Poor formation

Short Battle + Strong Victory

Usually indicates a significant advantage.

Long Battle + Small Advantage

This can indicate that both armies are relatively close.

Long Battle + Defeat

Possible causes include:

• Insufficient damage
• Poor offensive investment
• Weak matchup
• Enemy defensive advantage
• Inability to finish the enemy

Battle duration should be used as a clue, not as proof of a specific problem.

Damage Analysis

Damage is one of the most useful measurements in the report.

Compare:

• Your total damage
• Enemy total damage
• Individual Hero damage
• Damage relative to survivability

The most important question is:

Was the squad able to deal enough damage before losing its ability to fight?

High Damage + Fast Defeat

If your squad deals significant damage but collapses quickly, investigate survivability.

Possible causes:

• Weak frontline
• Poor defensive equipment
• Incorrect formation
• Hero dying too early
• Troop disadvantage

Possible solutions:

• Improve frontline survivability
• Adjust formation
• Improve defensive equipment
• Improve relevant Hero Skills
• Correct the troop matchup

Low Damage + Long Battle

This usually suggests that the squad can survive but is struggling to finish the opponent.

Investigate:

• Damage heroes
• Hero Skills
• Equipment
• Offensive stats
• Hero synergy
• Troop matchup

Possible improvements:

• Upgrade damage skills
• Improve offensive equipment
• Improve relevant research
• Improve damage-focused heroes

Low Damage + Fast Defeat

This usually indicates a major disadvantage.

Possible causes include:

• Large Power difference
• Severe troop counter
• Weak troop tier
• Small march size
• Low morale
• Weak Hero development
• Poor formation

Do not immediately change one hero.

First identify whether the problem is account-wide or squad-specific.

Comparing Damage Correctly

Do not compare damage numbers between completely different battles.

For meaningful testing, keep as many variables as possible consistent:

• Same enemy
• Same enemy formation
• Same troop type
• Similar troop quantity
• Same combat mode
• Same buffs
• Same Hero lineup except for the variable being tested

This creates a much cleaner test.

Controlled Testing

Battle Reports are extremely useful for testing changes.

Use a simple method:

Baseline
   ↓
Record Report
   ↓
Change ONE Variable
   ↓
Fight Again
   ↓
Compare Reports
   ↓
Keep or Revert

Examples of one-variable tests:

• Change one Hero
• Move one Hero
• Upgrade one Skill
• Change one Equipment piece
• Change troop type
• Change one relevant research upgrade

Changing everything at once destroys the usefulness of the comparison.

Comparing Multiple Reports

One report can be misleading.

Three or more comparable reports are much more useful.

Look for repeated patterns:

• Same hero dies first
• Same hero consistently deals low damage
• Same troop matchup causes losses
• Same formation repeatedly fails
• Same enemy defeats you in the same way
• Similar casualty patterns

Repeated results are much stronger evidence than a single battle.

Before vs After Testing

When testing an upgrade, save the old report.

For example:

BEFORE

Damage: 12.4M
Frontline survival: Low
Battle duration: 19s


AFTER

Damage: 14.1M
Frontline survival: Improved
Battle duration: 23s

The second result provides evidence that the change improved the squad.

This is much more useful than simply looking at the Power increase.

Battle Reports and Equipment Testing

Battle Reports can help determine whether equipment changes actually improve your squad.

Test one meaningful change at a time.

For example:

Before:
Equipment A

After:
Equipment B

Then compare:

• Hero damage
• Hero survival
• Total damage
• Battle duration
• Troop losses

A small Power increase does not automatically mean the equipment change was better.

Battle Reports and Hero Testing

When testing a Hero:

1. Keep the formation the same.
2. Keep troop type the same.
3. Keep the enemy the same.
4. Keep equipment as consistent as possible.
5. Change only the Hero.
6. Run multiple tests.
7. Compare the reports.

This helps separate actual Hero performance from unrelated variables.

Battle Reports and Research

Research changes can be difficult to evaluate from Power alone.

Use Battle Reports to determine whether a combat research upgrade produces a meaningful improvement.

Compare:

• Damage
• Survivability
• Troop results
• Battle duration
• Win/loss consistency

This is particularly useful when deciding between multiple upgrades with similar Power gains.

Battle Reports and Troop Tier

Troop tier is an important part of army strength.

When comparing two armies, consider:

• Troop tier
• Troop quantity
• Troop stats
• Morale
• Research
• March size

A higher Hero Power number does not compensate for every difference in army development.

Troop stats contribute to the combat strength of the Heroes in the squad, so troop development should always be considered when reading reports. citeturn0search6

Rally Battle Reports

Rally reports require additional care.

A rally is not simply one player fighting one opponent.

Multiple players may contribute troops and Heroes.

When analyzing a rally report, consider:

• Rally leader
• Rally members
• Individual squad composition
• Troop types
• Hero contribution
• Total damage
• Total losses
• Enemy defense
• Garrison composition

Do not judge a rally member only by their individual damage without considering their role in the overall rally.

Rally Leader vs Rally Member

The Rally Leader has a particularly important role because the rally's composition and leader-related bonuses can affect the overall result.

When comparing rallies, keep the following consistent where possible:

• Rally leader
• Number of members
• Member strength
• Enemy
• Target
• Combat conditions

Otherwise, the reports may not be directly comparable.

Defense and Garrison Reports

When analyzing a defensive battle, remember that the defender may have:

• Wall Heroes
• Garrison troops
• Reinforcements
• Multiple squads
• Defensive bonuses

A defensive report therefore should not be interpreted exactly like a solo open-field battle.

Ask:

What was actually defending the target when the attack happened?

This is especially important when evaluating whether a player can successfully defend a base.

City and Durability Reports

Some attacks target structures with Durability rather than simply trying to defeat a normal squad.

In these situations, the Battle Report can contain information relevant to:

• Durability damage
• Troop losses
• Combat result
• Contribution to the objective

Durability damage is a separate combat objective and should not be confused with normal unit damage.

For city and base attacks, checking the durability result can help determine which players and buffs are contributing most effectively. citeturn0reddit12turn1search8

PvE Battle Reports

PvE reports should be interpreted differently from PvP reports.

In PvE, you may be fighting:

• Zombies
• Bosses
• Special monsters
• Seasonal enemies
• Event enemies

The enemy may have fixed mechanics or stats.

When testing PvE damage, try to keep:

• Enemy level
• Formation
• Hero lineup
• Troop type
• Buffs
• Number of attacks

consistent.

This allows you to measure improvements much more accurately.

PvP Battle Reports

PvP reports are more variable because the opponent is another player.

Always check:

• Enemy troop type
• Enemy formation
• Hero lineup
• Equipment
• Troop tier
• Troop quantity
• Morale
• Research
• Buffs

A single PvP result is therefore rarely enough to prove that one formation is universally better.

What Power Can and Cannot Tell You

Power is useful.

But it is only one part of the picture.

Power can help estimate overall development.

It cannot reliably tell you:

• Which Hero is performing best
• Whether your formation is optimal
• Whether you have a troop counter
• Whether your frontline survives long enough
• Whether your damage is properly distributed
• Whether a support Hero is providing enough utility

That is why Battle Reports are so valuable.

Common Battle Report Mistakes

Looking Only at Victory or Defeat

A result is not an explanation.

Better approach: Read the complete report.

Looking Only at Power

Power does not show every combat interaction.

Better approach: Check matchup, army, Heroes, damage, and casualties.

Blaming Heroes Immediately

Low Hero damage does not always mean the Hero is bad.

The Hero may have:

• Died early
• Had poor positioning
• Faced a counter
• Lacked equipment
• Been part of an incompatible formation

Changing Everything at Once

If you change:

• Heroes
• Formation
• Equipment
• Research
• Troops

at the same time, you cannot determine what caused the improvement.

Better approach: Change one meaningful variable at a time.

Testing Against Different Enemies

A stronger result against a different opponent does not prove your build improved.

Better approach: Test against the same or very similar target.

Ignoring Troop Type

A troop counter can heavily influence a close battle.

Better approach: Check the combat triangle before changing your squad.

Ignoring Morale

Two armies with similar Power can still perform differently.

Better approach: Check Army information and morale.

Judging Support Heroes by Damage Alone

Support Heroes can provide significant value without topping the damage chart.

Better approach: Consider their buffs, utility, survivability, and team contribution.

Battle Report Analysis Checklist

When you lose a battle, go through this checklist.

BATTLE RESULT
□ Was the battle close?
□ Was there a major Power difference?

TROOPS
□ Did I use the correct troop type?
□ What troop tier did both sides use?
□ How many troops entered the battle?
□ What were the troop losses?

ARMY
□ What was my morale?
□ What was the enemy morale?
□ Was there a significant march-size difference?

HEROES
□ Which Hero died first?
□ Which Hero dealt the most damage?
□ Which Hero dealt unexpectedly low damage?
□ Did my damage Heroes survive long enough?
□ Were support Heroes contributing their intended utility?

FORMATION
□ Did the frontline survive?
□ Did the backline become exposed?
□ Is the Hero placement appropriate?

DAMAGE
□ Was my total damage sufficient?
□ Did I take too much damage?
□ Was the battle too short?
□ Was the battle unusually long?

UPGRADES
□ Is Equipment holding me back?
□ Are Hero Skills developed?
□ Is Research sufficient?
□ Are my troops strong enough?

TESTING
□ Can I change one variable?
□ Can I test against the same opponent?
□ Can I compare multiple reports?

A Simple Diagnostic System

You can use the following framework when analyzing a loss.

Problem: Frontline Dies First

Check:

Formation
↓
Frontline Hero Development
↓
Equipment
↓
Defense / HP
↓
Troop Quantity
↓
Troop Matchup

Problem: Frontline Survives but Damage Is Low

Check:

Damage Heroes
↓
Hero Skills
↓
Equipment
↓
Offensive Research
↓
Troop Matchup
↓
Hero Synergy

Problem: Everything Dies Quickly

Check:

Power Gap
↓
Troop Counter
↓
Troop Tier
↓
Morale
↓
March Size
↓
Major Account Development Gap

Problem: Results Are Inconsistent

Check:

Enemy Variation
↓
Different Troop Matchups
↓
Different Buffs
↓
Different March Sizes
↓
Different Battle Conditions

If the conditions are not consistent, do not draw strong conclusions.

How to Find the Best Upgrade

Battle Reports should help answer:

What is the next upgrade that gives me the most useful improvement?

For example:

Repeated frontline deaths
        ↓
Defensive weakness identified
        ↓
Improve frontline

Or:

Frontline survives
        ↓
Damage remains low
        ↓
Offensive weakness identified
        ↓
Improve damage source

Or:

Similar stats
        ↓
Repeated losses to same troop type
        ↓
Counter problem identified
        ↓
Change matchup

This is much more efficient than upgrading randomly.

The Golden Rule of Battle Report Analysis

Do not ask:

"How do I get more Power?"

Ask:

"What is the weakest part of this battle?"

Then fix that specific problem.

This approach produces much more efficient account development.

Summary

Battle Reports are one of the best tools available for improving combat performance in Last War: Survival.

Use them to analyze:

• Battle result
• Troop matchup
• Morale
• Troop quantity
• Troop tier
• Hero performance
• Hero Skills
• Formation
• Damage
• Survivability
• Casualties
• Rally contribution
• Durability objectives

The most important habits are:

1. Check the troop matchup.
2. Compare Army information and morale.
3. Look at which Heroes survive and which die first.
4. Analyze damage instead of only looking at Power.
5. Compare multiple similar reports.
6. Change one variable at a time when testing.
7. Fix the actual weakness instead of blindly increasing Power.

A Battle Report should not simply tell you:

"You won."

or

"You lost."

It should tell you:

"This is why the battle ended this way — and this is what you should improve next."