summaryrefslogtreecommitdiffstats
path: root/crawl-ref/source/dungeon.cc
diff options
context:
space:
mode:
authorNeil Moore <neil@s-z.org>2014-07-28 14:39:16 -0400
committerNeil Moore <neil@s-z.org>2014-07-28 15:19:53 -0400
commitc233d03cb8852cbff59ac5adefa3cbe34d0e1e35 (patch)
tree65b2a47ec2688c6aa30d4bde83848f55eb85092a /crawl-ref/source/dungeon.cc
parentba99023e2d48f18612eb27a9319e8c6cdf195909 (diff)
downloadcrawl-ref-c233d03cb8852cbff59ac5adefa3cbe34d0e1e35.tar.gz
crawl-ref-c233d03cb8852cbff59ac5adefa3cbe34d0e1e35.zip
Don't veto when failing to connect Abyss vaults
So they'll actually place. We should look more closely into *why* it fails to connect and whether that can/should be fixed; or, alternatively, whether we should make abyss vaults all no_exits. For now, this stopgap at least leaves us in the same situation we were in before the #8833 crashes began.
Diffstat (limited to 'crawl-ref/source/dungeon.cc')
-rw-r--r--crawl-ref/source/dungeon.cc3
1 files changed, 2 insertions, 1 deletions
diff --git a/crawl-ref/source/dungeon.cc b/crawl-ref/source/dungeon.cc
index c8e6650f00..0b5bd482c5 100644
--- a/crawl-ref/source/dungeon.cc
+++ b/crawl-ref/source/dungeon.cc
@@ -4372,7 +4372,8 @@ static const vault_placement *_build_vault_impl(const map_def *vault,
#endif
|| player_in_branch(BRANCH_SWAMP)
|| player_in_branch(BRANCH_SLIME);
- if (place.connect(spotty) == 0 && place.exits.size() > 0)
+ if (place.connect(spotty) == 0 && place.exits.size() > 0
+ && !player_in_branch(BRANCH_ABYSS))
{
throw dgn_veto_exception("Failed to connect exits for: "
+ place.map.name);