Dota 2 · Axe · Battle Hunger
How to remove Axe Battle Hunger without waiting it out
On this page
Secure a kill on another unit to end Battle Hunger early. Valve also lists destroying a building as a removal condition. Simply walking away does not remove the damage-over-time effect.
What to do next ↓ · Find the failure cause ↓Mechanics source checked October 17, 2026 · Not match-tested · Practical recommendations are editorial, not guaranteed outcomes.


Identify this ability in your client: Battle Hunger. Icon © Valve. Official Axe page.
Battle Hunger is particularly awkward when you are already losing access to the creep wave. The answer is not necessarily to run farther: the skill has a specific early-removal condition that a retreat alone does not satisfy.
What to do, in order
- Read the debuff and confirm the damage is Battle Hunger, rather than a different damage-over-time effect.
- Look for a unit you can safely finish. Prepare a last hit instead of repeatedly attacking a healthy creep and leaving the kill to someone else.
- Secure the killing blow, then check that the debuff disappears. Do not assume being near another unit’s death satisfies the condition.
- If reaching a last hit would expose you to a kill, prioritise staying alive and wait out the debuff rather than walking into Axe to clear it.
- Once the effect ends, return to your normal lane plan. Do not keep taking unnecessary attacks just because you have solved the debuff.
Match the symptom to the cause
I attacked a creep but still have the debuff
Damage is not a kill. Check who actually landed the finishing blow. The removal condition is killing a unit.
I ran away and took more damage
Duration and damage do not stop merely because the distance grows. The slow is conditional on facing away from Axe, which makes an unplanned retreat more expensive.
I cannot reach a safe last hit
There may be no safe immediate removal. Compare the risk of stepping forward with the remaining duration; survival takes priority over forcing the mechanic.
See the ability in the game
Apply it to one concrete situation
If a low-health enemy creep is available beside you, finishing it can solve two problems at once: obtain the last hit and clear Battle Hunger. Chasing a healthy ranged creep through Axe’s attack range merely because it might eventually die is a different, much riskier decision.
Current base tooltip values
Values below are the unmodified fields in Valve’s dated English ability data. Slash-separated entries are listed level values, not a recommended skill build. Read the field label: damage, range, duration and percentages have different meanings. Upgrades and modifiers can change your client’s values.
| Tooltip field | Listed base value(s) |
|---|---|
| Mana cost | 50 / 60 / 70 / 80 |
| Cooldown (seconds) | 20 / 15 / 10 / 5 |
| DURATION | 12 |
| MOVEMENT SLOW | 18 / 22 / 26 / 30 |
| DAMAGE PER SECOND | 12 / 16 / 20 / 24 |
Limits that matter
This page does not claim a particular deny interaction, universal dispel list or safe last-hit threshold. Those are separate mechanics and depend on the unit and client state.
Related questions
Does breaking line of sight remove Battle Hunger?
The official description does not list losing vision as a removal condition. Use the kill condition or wait for the duration instead of relying on fog.
Why does it feel worse while retreating?
The slow applies while the affected unit faces away from Axe. The damage-over-time and facing condition are separate parts of the spell.
Sources and review date
Valve’s English Axe ability data, retrieved October 17, 2026, supplies the mechanics and numeric fields used here. Valve’s official hero page supplies the ability identity and official presentation. Our diagnostic sequence and worked situations are independently written explanations, not copied match reports. No ranked win-rate, personal playtest or current item-build claim is made.