more object->dknown handling
Fix a couple of places that set obj->dknown to 0 to deal with some special cases where it should be left at 1. (Other places do that but deal with potions where hardcoded 0 remains appropriate.)
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
/* NetHack 3.7 mthrowu.c $NHDT-Date: 1620329778 2021/05/06 19:36:18 $ $NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.113 $ */
|
||||
/* NetHack 3.7 mthrowu.c $NHDT-Date: 1620923922 2021/05/13 16:38:42 $ $NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.114 $ */
|
||||
/* Copyright (c) Stichting Mathematisch Centrum, Amsterdam, 1985. */
|
||||
/*-Copyright (c) Pasi Kallinen, 2016. */
|
||||
/* NetHack may be freely redistributed. See license for details. */
|
||||
@@ -505,7 +505,7 @@ m_throw(
|
||||
|
||||
singleobj->owornmask = 0; /* threw one of multiple weapons in hand? */
|
||||
if (!canseemon(mon))
|
||||
singleobj->dknown = 0;
|
||||
clear_dknown(singleobj); /* singleobj->dknown = 0; */
|
||||
|
||||
if ((singleobj->cursed || singleobj->greased) && (dx || dy) && !rn2(7)) {
|
||||
if (canseemon(mon) && flags.verbose) {
|
||||
|
||||
Reference in New Issue
Block a user