Keep the conditions comparable
Record the target, battle type, troop tier/count, formation, hero investment and relevant active buffs before comparing two fights. If several change together, the result cannot isolate which upgrade helped.
Begin with a clear symptom: frontliners die early, a damage source contributes little, the fight times out, or losses are too expensive for the reward. A higher displayed power figure does not answer those questions.
Separate damage, injuries and permanent losses
The official release history describes a casualty-rule breakdown under Battle Report, Battle Statistics and Unit Casualty Rules. Use the actual labels in your client to inspect the sources contributing to serious injuries and deaths.
Do not carry a casualty rule from one event into ordinary world combat. Some event references explicitly describe automatic recovery or no deaths; those exceptions do not establish a game-wide protection rule.
Make one practical change
Keep a short before/after note and repeat a suitable fight when practical. Look for consistent improvement in the intended job, not a universal ranking from one victory. Include the extra resource bill if a stronger result uses more troops or recovery.
Use the skill references to explain a possible result, then check the report. Target counts, cooldown configuration and damage coefficients alone do not provide a validated full combat simulation.
Start with the conditions, then the result
Record the target and mode, your formation, troop tier and starting count. Note any obvious mismatch in equipment or active effects. These conditions explain why two reports that look similar may not be comparable.
Look for the failure that matters. Did the front row disappear before important skills could fire? Did the squad survive but fail to finish? Were losses acceptable for the reward? A large damage total does not answer all three questions.
| Record | Why it matters |
|---|---|
| Target and mode | Different rules and enemies change the test |
| Formation and starting troops | A different starting state can explain the result |
| Hero levels, skills and gear | Identify the investment actually tested |
| Damage, survival and losses | Separate output from the cost of achieving it |
| One changed variable | Avoid giving all credit to one upgrade |
Test an idea you can act on
Choose a change with a clear reason. If the front row falls, test a survival option. If you time out, inspect relevant damage and support. Read the effect before moving resources; the word support alone does not tell you who receives its benefit.
Use a repeatable target when possible, and keep the old result. If the opponent or starting troops change, describe the comparison as limited rather than declaring a best team from one win.
Before you commit
- Fight conditions recorded.
- Specific failure identified.
- One change chosen.
- Comparable target used.
- Losses reviewed alongside damage.
Common questions
Can the website predict a battle from squad power?
No validated battle simulator is provided. The tools organize formations and recorded effects; actual reports help you test them in context.
Read next
Game records and coverage
Written for Top Lords using the site’s recorded game references and selected client observations. Reference tables were collected 24–25 October 2026; the explanations were expanded on 26 October. Current availability, version differences and unresolved costs stay separate.
How the data is checked