Some more attempts to prevent/catch/diagnose floating monster problems. Among

other things:

* If level generation leaves some monsters detached then this will be
  specifically noted.

* If applying _handle_monster_move() to a monster causes that monster to
  become detached it will be noted (those it won't catch *other* monster
  being detached by that monster moving).


git-svn-id: https://crawl-ref.svn.sourceforge.net/svnroot/crawl-ref/trunk@8009 c06c8d41-db1a-0410-9941-cceddc491573

1 files changed, 7 insertions, 0 deletions

diff --git a/crawl-ref/source/dungeon.cc b/crawl-ref/source/dungeon.cc
index 71dd75dd8a..aef1bd79dd 100644
--- a/crawl-ref/source/dungeon.cc
+++ b/crawl-ref/source/dungeon.cc
@@ -313,6 +313,13 @@ bool builder(int level_number, int level_type)
             Level_Unique_Maps.clear();
             Level_Unique_Tags.clear();
             _dgn_map_colour_fixup();
+
+#if DEBUG_MONS_SCAN
+            // If debug_mons_scan() find a problem while Generating_Level is
+            // still true then it will announce that a problem was caused
+            // during level generation.
+            debug_mons_scan();
+#endif
             return (true);
         }