fix #K4202 - O/mO for prompted values treated \

player's input as a comma-separated list of option:value settings

Several compound values that aren't amenable to menus prompt for a
line of input and pass it to parseoptions() as if it came from the
run-time configuration file.  That shouldn't be treating commas as
option separators.

The fix is trival, at least for handling the text properly without
introducing new warnings to complain about rejections.  Some options
notice an unwanted comma and complain, others don't notice and the
extra text gets ignored.
This commit is contained in:
PatR
2024-07-15 13:13:01 -07:00
parent 1dc9f7324a
commit 61affaed37
2 changed files with 19 additions and 5 deletions

View File

@@ -1445,6 +1445,10 @@ some theft messages by nymphs force "she", others use default monster naming
if a nymph stole worn armor and got killed (perhaps by pet) before hero's next
turn, feedback would be "You finish taking off your suit." regardless
of the type of armor being taken off
when setting an option interactively [via O or 3.7's mO], if the particular
option uses a prompt to get a line of input (for compounds: 'fruit',
'scores', most numeric ones), input was treated as a comma-separated
list of option[:value] rather than just the new value of that option
Fixes to 3.7.0-x General Problems Exposed Via git Repository