summaryrefslogtreecommitdiffstats
path: root/crawl-ref/source/zap-data.h
diff options
context:
space:
mode:
authorDracoOmega <draco_omega@live.com>2014-03-22 01:08:37 -0230
committerDracoOmega <draco_omega@live.com>2014-03-22 01:41:39 -0230
commitfa59a01f93d0554f6bff16913938e437f8952a43 (patch)
treedf6fd485eaf830bc8cca47857cd8501cc839b50e /crawl-ref/source/zap-data.h
parent297819c9624760125d7a6668e28c86c926e3fac4 (diff)
downloadcrawl-ref-fa59a01f93d0554f6bff16913938e437f8952a43.tar.gz
crawl-ref-fa59a01f93d0554f6bff16913938e437f8952a43.zip
Reduce explosive bolt message spam just a little
The primary bolt of this effect isn't actually capable of doing damage itself, but would still print 'X appears unharmed.' whenever it hit something, which is both needless and a bit misleading. It unfortunately will still print the monster's wounded state upon impact, if they were previously wounded (even though this bolt cannot injure them further). Perhaps attacks that inflict no damage should simply not do this in general, rather than being special-cased here?
Diffstat (limited to 'crawl-ref/source/zap-data.h')
-rw-r--r--crawl-ref/source/zap-data.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/crawl-ref/source/zap-data.h b/crawl-ref/source/zap-data.h
index 2ee257153a..c0b8f95727 100644
--- a/crawl-ref/source/zap-data.h
+++ b/crawl-ref/source/zap-data.h
@@ -1122,7 +1122,7 @@ struct zap_info
new tohit_calculator<17, 1, 25>,
RED,
false,
- BEAM_FIRE,
+ BEAM_MISSILE, // To avoid printing needless messages for non-damaging hits
DCHAR_FIRED_ZAP,
true,
true,