fix #H4545 - stack of scrolls of scare monster
Reported 3.5 years ago. Specifying a count for pickup to pick up a subset of a stack was processed after scrolls of scare monster were handled, so a whole stack of those got picked up or crumbled to dust whether you gave a count or not. Also, if you were too encumbered to pick up the full stack, they still all crumbled or all changed state to crumble next time, then for the latter case you picked up as big a subset as you could handle.
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
$NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.118 $ $NHDT-Date: 1583315888 2020/03/04 09:58:08 $
|
||||
$NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.121 $ $NHDT-Date: 1583515468 2020/03/06 17:24:28 $
|
||||
|
||||
General Fixes and Modified Features
|
||||
-----------------------------------
|
||||
@@ -62,6 +62,8 @@ display wasn't updating immediately after toggling hilite_pet option
|
||||
randomly choosing role could lead to crash via segfault
|
||||
if eel bite attack caused hero to move (killed + rehumanized + crawled out
|
||||
of water), its grab attack could succeed even if no longer adjacent
|
||||
specifying a count when picking [part of] a stack of scrolls of scare monster
|
||||
ignored that count and the whole stack was affected
|
||||
|
||||
|
||||
Fixes to 3.7.0-x Problems that Were Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user