nethack-gwaa-kiwi/nethack
1
0
Fork 0
Code Pull Requests Activity

Merge branch 'NetHack-3.6.2'

Browse Source
This commit is contained in:
nhmall
2019-04-13 22:40:44 -04:00
parent 08af2b3b92 bc8ed91f2b
commit c4465c35ed
8 changed files with 93 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/Guidebook.tex
View File

@@ -4584,7 +4584,7 @@ Allowed colors are {\it black}, {\it red}, {\it green}, {\it brown},
{\it blue}, {\it magenta}, {\it cyan}, {\it gray}, {\it orange},
{\it light-green}, {\it yellow}, {\it light-blue}, {\it light-magenta},
{\it light-cyan}, and {\it white}.
And {\itno-color}, the default foreground color, which isn't necessarily
And {\it no-color}, the default foreground color, which isn't necessarily
the same as any of the other colors.
%.lp ""
@@ -4675,9 +4675,9 @@ the hitpoints field to display in the color red if your hitpoints
drop to or below a threshold of 30%:\\
\begin{verbatim}
OPTION=hilite_status:hitpoints/<=30%/red/normal
\end{verbatim}\\
(That example is actually specifying {\tt red\&normal} for <=30\%
and {\tt no-color\&normal} for >30\%.)\\
\end{verbatim}
(That example is actually specifying {\tt red\&normal} for {\tt <=30\%}
and {\tt no-color\&normal} for {\tt >30\%}.)\\
For another example, the following line in your configuration file will cause
wisdom to be displayed red if it drops and green if it rises:\\

7
doc/fixes36.2
View File

@@ -1,4 +1,4 @@
$NHDT-Branch: NetHack-3.6.2-beta01 $:$NHDT-Revision: 1.300 $ $NHDT-Date: 1554841009 2019/04/09 20:16:49 $
$NHDT-Branch: NetHack-3.6.2-beta01 $:$NHDT-Revision: 1.303 $ $NHDT-Date: 1555201701 2019/04/14 00:28:21 $
This fixes36.2 file is here to capture information about updates in the 3.6.x
lineage following the release of 3.6.1 in April 2018. Please note, however,
@@ -409,6 +409,8 @@ once a status highlight for a temporary rule ('up', 'down', 'changed') timed
if a migrating long worm couldn't be placed, or some other monster was given
an existing long worm's place and it couldn't be put somewhere else,
a "trying to place monster at <0,0>" warning would occur
if hero throws a pick-axe into a shop and shopkeeper catches it, shk will say
"get out of my way, scum" even if there's no monster at pick-axe spot
Fixes to Post-3.6.1 Problems that Were Exposed Via git Repository
@@ -465,6 +467,8 @@ when engulfed while in a shop, dropping an item into the engulfer and then
using ':' to look at current location could cause a crash
when items were on the floor just inside a shop's door where the shopkeeper
doesn't buy and sell stuff, those items showed a 'for sale' price
probing a monster inside a shop (including shopkeeper) showed 'for sale'
price for items in monster's minvent
applying a container while inside a shop and initiating a put-in operation
would show non-empty containers in inventory--including the one being
applied--with "for sale" amounts for the prices of their contents
@@ -681,6 +685,7 @@ include isaac64 for pseudo random number generation
core prng and display prng use different contexts
when healing magic other than unicorn horn cures blindness, cure deafness too
do less status updating when the 'time' option is on
slightly more thorough feedback when shop damage is repaired in hero's presence
curses: status display substantially revamped for both horizontal (via
'align_status:bottom' or 'top') and vertical (via 'align_status:left'
or 'right'); 3-line horizontal layout (via 'statuslines:3') added