summaryrefslogtreecommitdiffstats
path: root/crawl-ref/source/evoke.cc
diff options
context:
space:
mode:
authorgammafunk <gammafunk@gmail.com>2014-05-25 10:01:22 -0500
committergammafunk <gammafunk@gmail.com>2014-05-28 12:50:50 -0500
commit4412034ca0e58c61c99658f6d498f3415480dcfa (patch)
tree22ac0e79d4fd247aeda996849a566b2d205a8c96 /crawl-ref/source/evoke.cc
parent12a312a68c4aae7d6e8dc669c6b782327fbb9be9 (diff)
downloadcrawl-ref-4412034ca0e58c61c99658f6d498f3415480dcfa.tar.gz
crawl-ref-4412034ca0e58c61c99658f6d498f3415480dcfa.zip
Destroy item destruction
Now that inventory weight and player burden states are gone, item destruction doesn't serve one purpose it clearly accomplished: help prevent the player from being at or next to burden capacity at all times. Outright destruction of strategic consumables encourages more needless inventory management, so we'd like to exclude these from any form of destruction and possibly prevent them from taking up inventory space at all. Denial of tactical consumables, either temporarily or permanently, is something we're going to look into later on, possibly in the release after next, since it can create interesting and generally not frustrating gameplay if done correctly. Needless to say, item destruction wasn't a player favorite and may have a sparsely attended funeral. RIP in peace. For now we aren't adjusting the rate of consumable generation to compensate for no item destruction, but that balancing will happen after play-testing shows how much adjustment is necessary.
Diffstat (limited to 'crawl-ref/source/evoke.cc')
-rw-r--r--crawl-ref/source/evoke.cc1
1 files changed, 0 insertions, 1 deletions
diff --git a/crawl-ref/source/evoke.cc b/crawl-ref/source/evoke.cc
index f1689d7c8c..781e0796dd 100644
--- a/crawl-ref/source/evoke.cc
+++ b/crawl-ref/source/evoke.cc
@@ -401,7 +401,6 @@ static void _fiery_explosion()
beam.ex_size = 2;
beam.is_explosion = true;
beam.effect_known = true;
- beam.affects_items = true;
beam.thrower = KILL_YOU;
beam.beam_source = NON_MONSTER;