saving/freeing ball and chain
Reported by entrez: fix memory being accessed after having been freed by trying to keep ball&chain data up to date when they're processed by the save code. This fix is a little more elaborate than this suggested one. I'm crossing my fingers on this one....
This commit is contained in:
+2
-1
@@ -1,4 +1,4 @@
|
||||
HDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.945 $ $NHDT-Date: 1654886097 2022/06/10 18:34:57 $
|
||||
HDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.946 $ $NHDT-Date: 1654931291 2022/06/11 07:08:11 $
|
||||
|
||||
General Fixes and Modified Features
|
||||
-----------------------------------
|
||||
@@ -924,6 +924,7 @@ be less specific when cause of death is "handling a <ring or wand>" that
|
||||
"a silver wand" rather than "ring of searching" or "wand of locking"
|
||||
adjust the row placement of copyright and early startup messages so that
|
||||
aren't partially overwritten by prompts that follow
|
||||
ball and chain could be accessed after having been freed if bones were saved
|
||||
|
||||
|
||||
Fixes to 3.7.0-x Problems that Were Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user