OPTIONS=scores:own

From a beta tester six years ago:  specifying 'scores:own' resulted
in an option setting of 'scores:3 top/2 around/own' when player
wanted 'scores:0 top/0 around/own'.  Change it so that when fewer
than all three fields are given new values, the others are reset
rather than having their old values merge with new settings.

Also, 'scores:none' can be used to get 'scores:0 top/0 around/!own'
to skip the scores at the end without skipping notification of
whether the ending game's score made it into the top N list.
Options parsing accepts '!scores' and then ignores the negation.
Changing the optlist flags for 'scores' to allow negation resulted
in a complaint about missing value; I gave up instead of pursuing
that.  'scores:none' should suffice.

Setting 'scores:!top/own' or 'scores:!around/own' would behave as
'scores:1 top/!own' or 'scores:1 around/!own', respectively.
'scores:!top/!around/own' behaved as 'scores:1 top/1 around/own'
(note affect of two prior negations on final field compared to
single negation in the earlier two variations).  This fixes those.

doc/fixes37.0

@@ -455,6 +455,11 @@ if a branch has only one level (Fort Ludios), prevent creation of any level
 opening/unlocking magic zapped at monster holding the hero will release hold
 	(zap at engulfer already expels hero); zapping at self has same effect
 when riding, allow scroll of remove curse to affect to affect steed's saddle
+the 'scores' option for final top ten display left default values in place if
+	only some of the three settings were set; 'scores:own' should have
+	produced '0 top/0 around/own' but ended up as '3 top/2 around/own';
+	also, allow 'scores:none' as shorthand for 'scores:0 t/0 a/!o' (player
+	will to told whether new score made the list but no scores get shown)
 
 
 Fixes to 3.7.0-x Problems that Were Exposed Via git Repository