Wittle Defender Battle Stats Guide โ How to Actually Read Your Results
Battle stats show you what happened in a fight โ but most players read them wrong. This guide covers damage dealt, healing, shield absorption, carry performance, support value, and how to diagnose weak performers.
Quick Answer
Battle stats are the performance numbers shown after each fight in Wittle Defender. They tell you who dealt damage, how much healing happened, and how much damage the team absorbed. But reading them correctly requires context โ high damage dealt is not always good, zero healing can mean your team is invincible or that your healer is dead, and a hero with 5% of team damage might still be your most important hero. This guide teaches you to read battle stats like an analyst, not just a scoreboard.
What Battle Stats Show You
Post-battle stats in Wittle Defender typically display: Damage Dealt (per hero and total). Healing Done (per healer hero). Damage Taken (total incoming damage). Shield Absorbed (how much of incoming damage was blocked by shields). In some modes, additional breakdowns show hero-specific contribution percentages. The key insight: these numbers are a snapshot of one fight, not a universal verdict on hero quality. A hero that dealt 3% of total damage may have saved the run by keeping everyone alive.
How to Read Damage Dealt
Damage dealt is the most visible stat but the most misread. What it actually tells you: which hero is functioning as your primary carry. Whether the damage is distributed well or dangerously concentrated. What it does NOT tell you: whether that hero is being used correctly. Whether the damage capped at an enemy HP threshold (boss HP is finite โ overkill is invisible in damage numbers). Whether speed setting affected accuracy. Correct reading: if your 'carry' hero shows less damage than a support hero, investigate why. Common causes: carry is dying early and losing output time, carry has the wrong rune set, carry's Awakening-Core has not been unlocked yet, or the speed setting caused missed triggers.
How to Read Healing Done
Healing done shows total HP restored to your team by healing heroes. Important context: If healing done is very low: either your team is not taking damage (good โ it means shields or dodge are working), or your healer is dying early in fights (bad). If healing done is very high relative to team HP: your team is surviving on the healer's output, which means you are close to the edge โ reduce incoming damage or add another survival layer (AA shields, PD Rebirth). Healing done of zero from your healer: investigate immediately. Either the healer died before outputting, or the mode does not involve the healer (some modes bench specific heroes). FL vs. Seraph comparison via healing stats: FL will show lower raw healing but your team will survive better because she also provides DMG% buffs that reduce how long fights last.
How to Read Damage Taken and Shields
Damage taken shows total incoming damage before mitigation. Shield absorbed shows how much of that was blocked by AA's shields, Panda's bamboo shields, PK's team shields, and similar effects. The ratio tells you your survivability margin. Healthy ratio: if Damage Taken ร 60-80% is Shield Absorbed, your team is well-defended. Danger zone: if Damage Taken is high and Shield Absorbed is low with no healing, you are surviving on raw HP โ one harder stage will wipe you. Rune adjustment: if Damage Taken is consistently very high, consider switching from pure DPS runes to a HP-conditional set (4x Unshaken Will) for the main carry.
The Carry Performance Test
Use battle stats to verify your carry is actually carrying. The test: if your carry accounts for less than 40% of total damage dealt in a fight where they survived the full duration โ something is wrong. Check in order: Is the Awakening-Core unlocked? Are the ATK60 cards unlocked? Is the rune set correct for their role? Is SW designating them as Proxy? Is there an element synergy bonus active? Is the speed setting causing missed triggers? Fix the first issue you find, run again, check stats again. This methodical approach finds real problems instead of randomly swapping heroes.
Support Value Is Invisible in Stats
The most important lesson for reading battle stats: support heroes that are working correctly show LOW personal damage numbers but make your carry's numbers much higher. AA's correct battle stat: minimal personal damage, but your carry's damage doubled because AA kept the team alive and buffed CRIT DMG. FL's correct battle stat: her healing number may be low (because AA's shields prevented most damage), but your carry ran longer and hit harder. Panda's correct battle stat: Panda's personal damage is moderate, but WR's damage should be much higher with Panda than without. If you bench a 'low damage' support and your carry's damage also drops โ that support was doing their job. Never bench support heroes based purely on damage dealt numbers.
The Weak Performer Test
When a hero is underperforming, battle stats give you the first clue, but the diagnosis requires deeper investigation. If a DPS hero has unexpectedly low damage: Did they survive the fight? (Check if deaths are occurring early.) Did they have access to their best skill cards? (Was the draw pool too large?) Was the speed setting correct? (x3 can cause missed triggers.) Did the CRIT Rate show up correctly? (Is PD alive and at 1D?) Are their ATK60 cards unlocked? Run the same fight at x1 speed, with 3 heroes instead of 5, and see if the number improves. If yes: the issue is card pool or speed. If no: the issue is investment or build.
Battle Stats in Specific Modes
Guild Raid: Use damage dealt to compare your personal output across attempts. Your goal is to maximize personal damage for leaderboard ranking. If attempt 2 is lower than attempt 1 with the same team: the boss's HP scaling between tiers is increasing faster than your damage โ time to upgrade your team. Nightmare/Boss Challenge: Compare damage dealt at x1 vs. x3 speed on the same boss. The x3 number should be lower โ this is the most direct demonstration of the speed bug. Abyss Crusade: Healing done becomes more important on later floors where incoming damage scales up. Track if healer output keeps pace.
Using Stats to Validate Team Changes
The correct way to use battle stats for team optimization: run fight with Team A โ record damage dealt and fight duration. Make one change (swap one hero, change one rune, change speed). Run same fight with Team B โ compare. Never change two things simultaneously โ you will not know which change made the difference. Isolate one variable per test. Repeat 3 times before drawing conclusions (RNG in card draws can inflate or deflate results on any single run). This is the scientific method applied to Wittle Defender. It is how top players verify tier list claims instead of just accepting them.
Follow WittleAI Guides
Get notified when new Wittle Defender guides, builds, and tier lists go live.
Frequently Asked Questions
Why does my healer show 0 healing in battle stats?
Either the healer died before healing anyone, your team took no meaningful damage (shields/dodge absorbed it all), or there was a skill trigger issue from x3 speed. Check if your healer survived the full fight.
My carry shows only 30% of total damage โ is that a problem?
If they survived the full fight, it may mean supports are over-investing or your carry's skill cards are behind. If the carry is dying early, they are losing output time. Investigate carry survivability first.
How do I know if my shield hero is working?
Compare Damage Taken vs. Shield Absorbed in the post-battle stats. A working shield hero (AA, Panda, PK) should show significant Shield Absorbed relative to total Damage Taken.
Discuss this with the community
Join Apex Guild โ the #1 Wittle Defender community. Get codes the moment they drop, ask WAI in Discord, and talk strategy with top players.
Have a specific question about this topic?