fix github issue #279 - boulder feedback
Polymophed into a giant and moving onto a boulder's location could yield "you easily pick it up" (without actually doing so) followed by "you see a boulder here". It would happen if autopickup was Off, or if the 'm' move-without-autopickup prefix was used, while either boulder was included in pickup_types (including when that is set for 'all') or hero had thrown that particular boulder and pickup_thrown was On. The check for whether auto-pick should try on an object relied on its caller verifying that autopickup was On. pickup() does that for pickup() -> autopick() -> autopick_testobj() but moverock() wasn't doing that for moverock() -> autopick_testobj() so the logic controlling moverock's message was subverted. I first thought that logic itself was incorrect and changed the message. This keeps the new message even though it turned out not to be cause of the problem. Fixes #279
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
$NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.62 $ $NHDT-Date: 1578764038 2020/01/11 17:33:58 $
|
||||
$NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.63 $ $NHDT-Date: 1578834315 2020/01/12 13:05:15 $
|
||||
|
||||
General Fixes and Modified Features
|
||||
-----------------------------------
|
||||
@@ -42,6 +42,8 @@ walking out of tethered-to-buried-object trap condition was supposed to
|
||||
reinstate punishment but wasn't finding the buried iron ball because
|
||||
the trap condition was cleared first to indicate escape; result was
|
||||
attached chain that got dragged around but had no ball attached
|
||||
when poly'd into a giant and moving onto a boulder's spot, message given was
|
||||
confused about whether autopickup would occur so could be misleading
|
||||
|
||||
|
||||
Fixes to 3.7.0-x Problems that Were Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user