Run some sanity checks when loading ghosts. If anything seems fishy

* don't load the ghost(s)
* print an error message mentioning the bones file
* don't delete the bones file, so players can attach it to a bug report

The last point means that the player (or admin, in the case of the
servers) has to delete a buggy bones file themselves, but the benefits
of making tracking down bugs easier should outweigh that inconvenience.

Add a new wizmode command that calls debug_stethoscope even if the game 
is not compiled in debugging mode.

Also, Stone Soup 0.5 bones files are now officially incompatible with 0.4.
(The changes to the spell ids cause ghosts casting spells to crash the
game.)


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

1 files changed, 6 insertions, 0 deletions

diff --git a/crawl-ref/source/directn.cc b/crawl-ref/source/directn.cc
index 756b9a5e3b..e68d8e3f9e 100644
--- a/crawl-ref/source/directn.cc
+++ b/crawl-ref/source/directn.cc
@@ -1559,6 +1559,12 @@ void direction(dist& moves, targeting_type restricts,
                 wizard_polymorph_monster(m);
             break;
 
+        case CMD_TARGET_WIZARD_DEBUG_MONSTER:
+            if (!you.wizard || !in_bounds(moves.target))
+                break;
+            if (monster_at(moves.target))
+                debug_stethoscope(mgrd(moves.target));
+            break;
 #endif
         case CMD_TARGET_DESCRIBE:
             full_describe_square(moves.target);