fix #K4025 - #saveoptions vs cond_ options
Confusion between 'o_status_cond' and 'pfx_cond_'. Still confusing but I think now working as intended and expected. If any cond_xyz option has been loaded from the RC file or changed via 'm O', #saveoptions still saves the full set rather than just the ones that are different from their default value.
This commit is contained in:
@@ -1710,6 +1710,10 @@ applying a wielded lump of royal jelly but not picking something to rub it on
|
||||
"addinv: null obj after quiver merge" (like applying lit potion of oil)
|
||||
ceiling hider could become hidden when there was no ceiling, triggering a
|
||||
warning if sanity_check was On
|
||||
experimental #saveoptions wasn't saving the set of cond_xyz options correctly;
|
||||
if player viewed the 'm O' submenu for status conditions, they would
|
||||
get saved even if not changed; otherwise, ones that came in from the
|
||||
old RC file wouldn't be included in the new one
|
||||
|
||||
|
||||
Fixes to 3.7.0-x Platform and/or Interface Problems Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user