gulpmm "placing <mon> over itself"

Reported direclty to devteam by a hardfought player:
|placing tame fire vortex <56,18> over itself at <56,18>, [...]

An old map fixup when an engulfer and its victim temporarily share
the same map location got impacted by changes made a month or two
back for removing dead or migrated monsters from the map.  The old
fixup (for putting the engulfer back after removing the victim also
removed it) was no longer needed and using it resulted in a warning
from place_monster() about putting a monster on top of itself.
This commit is contained in:
PatR
2022-07-14 16:13:47 -07:00
parent 5ddf8c9815
commit 66dc16b61f
2 changed files with 30 additions and 9 deletions

View File

@@ -1300,6 +1300,8 @@ save files created with SCORE_ON_BOTL disabled were erroneously being rejected
avoid "It suddenly appears!" if a monster with the STRAT_APPEARMSG attribute
is seen to teleport away then not seen at its destination
avoid boulder-on/in-water sanity_check warnings on the Plane of Water
when one monster swallowed/engulfed another and killed it, impossible
"placing <mon> over itself ..." could be given by place_monster()
curses: 'msg_window' option wasn't functional for curses unless the binary
also included tty support