summaryrefslogtreecommitdiffstats
path: root/crawl-ref/source/melee_attack.cc
diff options
context:
space:
mode:
authorNicholas Feinberg <pleasingfung@gmail.com>2014-07-13 21:29:53 -0700
committerNicholas Feinberg <pleasingfung@gmail.com>2014-07-13 21:29:59 -0700
commit4d463b29f770b39bc63ce32d438b0e2e433b45ef (patch)
treeb7978e023de51707b7e3100e0a4c66f964245f81 /crawl-ref/source/melee_attack.cc
parent257f14127322a5881d1b4f275062f79d76afd95b (diff)
downloadcrawl-ref-4d463b29f770b39bc63ce32d438b0e2e433b45ef.tar.gz
crawl-ref-4d463b29f770b39bc63ce32d438b0e2e433b45ef.zip
Remove a strange and unused case from AF_DRAIN_XP
It would only apply if a monster had a 0-damage AF_DRAIN_XP attack specification, which, as far as I can tell, can't happen? (The only way it could occur was if a creature with a 0-damage attack got spectralized... but I don't think we especially care about giving those an extra-high drain chance?)
Diffstat (limited to 'crawl-ref/source/melee_attack.cc')
-rw-r--r--crawl-ref/source/melee_attack.cc6
1 files changed, 1 insertions, 5 deletions
diff --git a/crawl-ref/source/melee_attack.cc b/crawl-ref/source/melee_attack.cc
index 39a25defed..2f759f8b78 100644
--- a/crawl-ref/source/melee_attack.cc
+++ b/crawl-ref/source/melee_attack.cc
@@ -3067,12 +3067,8 @@ void melee_attack::mons_apply_attack_flavour()
break;
case AF_DRAIN_XP:
- if (one_chance_in(30)
- || (damage_done > 5 && coinflip())
- || (attk_damage == 0 && !one_chance_in(3)))
- {
+ if (one_chance_in(30) || (damage_done > 5 && coinflip()))
drain_defender();
- }
break;
case AF_PARALYSE: