muse wand/horn feedback
One of the claims in #H8849 was that a monster which zapped a wand that the hero had fully identified made hero's knowledge of it revert to "a wand". That doesn't happen; it had to have been a different wand which hadn't been seen up close yet. But the hero should lose track of known number of charges if a wand is zapped outside his/her view. When implementing that I noticed that a monster playing a fire horn to burn away slime was using the routine that gives wand feedback. Add a separate, similar routine for magical horn feedback. Half this diff is due to moving a naming support routine from mhitm.c to do_name.c.
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
$NHDT-Branch: NetHack-3.6 $:$NHDT-Revision: 1.49 $ $NHDT-Date: 1560089250 2019/06/09 14:07:30 $
|
||||
$NHDT-Branch: NetHack-3.6 $:$NHDT-Revision: 1.50 $ $NHDT-Date: 1560161804 2019/06/10 10:16:44 $
|
||||
|
||||
This fixes36.3 file is here to capture information about updates in the 3.6.x
|
||||
lineage following the release of 3.6.2 in May 2019. Please note, however,
|
||||
@@ -68,6 +68,11 @@ unlike watching a monster trying to swap out a cursed weapon for some other
|
||||
that weapon becoming welded to the monster's hand/claw/whatever
|
||||
accept "hidden" as an attribute for wizard mode ^G monster creation; created
|
||||
monsters which can't be seen will have their locations highlighted
|
||||
don't give feedback for monster zapping a wand if a monster plays a fire horn
|
||||
directed at self to burn away slime
|
||||
if hero knows the number of charges in a wand or magical horn and a monster
|
||||
acquires it and zaps/plays it when not in view, remove the hero's
|
||||
memory of the number of charges
|
||||
|
||||
|
||||
Fixes to Post-3.6.2 Problems that Were Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user