preliminary fix for github issue #726 - restdamage
Reported by entrez, restoring a saved game runs the shop wall/floor damage repair routine. It was taking place before attached ball and chain were fully restored so the repair routine treated them as ordinary objects if they happened to be in a wall gap that gets fixed on the same turn as restore takes place. They could end up being moved to a spot that's too far from the hero and then trigger an impossible "b&c distance". This restores ball and chain before shop damage repair takes place so the repair routine deals with them sanely and the impossible won't occur any more. However, the repair still happens before the current level's map has been displayed and that looks pretty strange during the shopkeeper's message. Also, if the hero and the ball start on opposite sides of the gap, after the gap is repaired the ball will still be shown as a remembered object at its old spot even though it ends up being located at the hero's feet. Closes #726 but more work is needed...
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.864 $ $NHDT-Date: 1649269126 2022/04/06 18:18:46 $
|
||||
NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.870 $ $NHDT-Date: 1649530942 2022/04/09 19:02:22 $
|
||||
|
||||
General Fixes and Modified Features
|
||||
-----------------------------------
|
||||
@@ -872,6 +872,9 @@ object detection always showed a mimic imitating a statue as a tengu even if
|
||||
it had information available about some other type of monster
|
||||
avoid "the Lord Surtur's corpse glows iridescently" when shk_your() or the()
|
||||
is applied to the corpse of unique monster with a personal name
|
||||
restoring while attached ball or chain is on floor in a breach of a shop wall
|
||||
could have it be moved out of wall gap as that gets repaired, then
|
||||
might trigger an impossible about being positioned too far from hero
|
||||
|
||||
|
||||
Fixes to 3.7.0-x Problems that Were Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user