Fix wizmakemap leaving genocided monsters on map

If a genocided monster was in "limbo" (migrating to the same level),
wizmakemap put it back on map.

diff --git a/doc/fixes36.3 b/doc/fixes36.3
index c767a776fbd7210e74b5a3301835774a34a1b59c..3b9997702d410f8ac8404568826dc6c9e11a69f2 100644 (file)
--- a/doc/fixes36.3
+++ b/doc/fixes36.3
@@ -207,6 +207,7 @@ mimic immitating a slime mold would change fruit type when player assigned new
 parsing for the argument to 'scores' option was sloppy; "3a/o" (slash) and
        "3a 1o" (space and digit one, not lowercase L) both worked but "3a o"
        (just space) was supposed to but didn't
+wizmakemap could leave genocided monsters on map
 
 
 Fixes to Post-3.6.2 Problems that Were Exposed Via git Repository

diff --git a/src/cmd.c b/src/cmd.c
index e6c4049b1899d7fc06f1793215aef89d6d86837d..e739172d528691a8d441261622258d57eb3f6389 100644 (file)
--- a/src/cmd.c
+++ b/src/cmd.c
@@ -861,6 +861,7 @@ wiz_makemap(VOID_ARGS)
         u_on_rndspot((u.uhave.amulet ? 1 : 0) /* 'going up' flag */
                      | (was_in_W_tower ? 2 : 0));
         losedogs();
+        kill_genocided_monsters();
         /* u_on_rndspot() might pick a spot that has a monster, or losedogs()
            might pick the hero's spot (only if there isn't already a monster
            there), so we might have to move hero or the co-located monster */