diff options
author | j-p-e-g <j-p-e-g@c06c8d41-db1a-0410-9941-cceddc491573> | 2009-05-26 08:39:40 +0000 |
---|---|---|
committer | j-p-e-g <j-p-e-g@c06c8d41-db1a-0410-9941-cceddc491573> | 2009-05-26 08:39:40 +0000 |
commit | d73035c53987d171d07b7a39fdd23caf4f5967f5 (patch) | |
tree | 2ddfd427fd6d4242024a094f6d5fdf1ec0ba60ee /crawl-ref/source/enum.h | |
parent | 043b5d69de4ee9f8b952488b1dc7e64a12d22f21 (diff) | |
download | crawl-ref-d73035c53987d171d07b7a39fdd23caf4f5967f5.tar.gz crawl-ref-d73035c53987d171d07b7a39fdd23caf4f5967f5.zip |
Add a tutorial trigger for the highly unlikely case the player
encounters a monster (oklob plant, hostile statue) during the tutorial
that triggers an autoexclusion.
There really needs to be an in-game way of explaining what they're for
when such an autoexclusion happens to the player for the first time,
particularly for the tiles build where excluded grids are visibly
different from non-excluded ones. I'm afraid the FAQ is too obscure for
this one, as well. Maybe add something to descriptions of monsters that
have an exclusion centered on them?
git-svn-id: https://crawl-ref.svn.sourceforge.net/svnroot/crawl-ref/trunk@9831 c06c8d41-db1a-0410-9941-cceddc491573
Diffstat (limited to 'crawl-ref/source/enum.h')
-rw-r--r-- | crawl-ref/source/enum.h | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/crawl-ref/source/enum.h b/crawl-ref/source/enum.h index 1df5512b5a..e563735a17 100644 --- a/crawl-ref/source/enum.h +++ b/crawl-ref/source/enum.h @@ -2952,11 +2952,12 @@ enum tutorial_event_type TUT_MAP_VIEW, TUT_AUTO_EXPLORE, TUT_DONE_EXPLORE, // 75 + TUT_AUTO_EXCLUSION, TUT_STAIR_BRAND, TUT_HEAP_BRAND, TUT_TRAP_BRAND, - TUT_LOAD_SAVED_GAME, - TUT_EVENTS_NUM // 80 + TUT_LOAD_SAVED_GAME, // 80 + TUT_EVENTS_NUM // 81 }; // NOTE: For numbers higher than 85 change size of tutorial_events in externs.h. |