summaryrefslogtreecommitdiffstats
path: root/crawl-ref/source/stairs.h
diff options
context:
space:
mode:
authorDracoOmega <draco_omega@live.com>2013-01-23 22:17:57 -0330
committerelliptic <hyperelliptical@gmail.com>2013-01-28 03:51:47 -0500
commit4c3727d17cec67a578a6b58bde42fad97303a07c (patch)
treea3a14cd144f332165d31d4f1736e5f8c5b17a3fe /crawl-ref/source/stairs.h
parent0c243a0bb3c584cba8ec9f2d75347c3b5c8b4613 (diff)
downloadcrawl-ref-4c3727d17cec67a578a6b58bde42fad97303a07c.tar.gz
crawl-ref-4c3727d17cec67a578a6b58bde42fad97303a07c.zip
More properly clean up the old level when using wizmode level teleport
This could cause a crash if an arcane familiar was stranded on an old level and you cast something which would trigger it to fire, but also it seems sensible that other bits of normal level cleanup should be executed after a wizmode level change.
Diffstat (limited to 'crawl-ref/source/stairs.h')
-rw-r--r--crawl-ref/source/stairs.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/crawl-ref/source/stairs.h b/crawl-ref/source/stairs.h
index fefed5a5c3..325d78e369 100644
--- a/crawl-ref/source/stairs.h
+++ b/crawl-ref/source/stairs.h
@@ -13,4 +13,5 @@ level_id stair_destination(coord_def pos, bool for_real = false);
void down_stairs(dungeon_feature_type force_stair = DNGN_UNSEEN);
void up_stairs(dungeon_feature_type force_stair = DNGN_UNSEEN);
void new_level(bool restore = false);
+void leaving_level_now(dungeon_feature_type stair_used);
#endif