disallow assigning type name to Amulet of Yendor
Something I noticed when testing the item-action handling for name and call; applies to the C/#name command too. You were allowed to call the real Amulet something and allowed to call fake ones something [else]. If you did that, xname/doname didn't show it but the discoveries list did, giving away information when the player had access to more than one unID'd Amulet of Yendor. Rather than messing about with discovery handling, make real and fake Amulet be ineligible from being given a type name. (They can still be given individual names.)
This commit is contained in:
@@ -882,6 +882,7 @@ putting objects into a container with menustyle=traditional and then taking
|
||||
bit being set if sanity_check was On
|
||||
when drinking or dipping, allow the 'm' prefix to be used to skip asking
|
||||
about fountains and pools
|
||||
calling real or fake Amulet something could give away information about them
|
||||
|
||||
|
||||
Fixes to 3.7.0-x Problems that Were Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user