new status conditions

Several conditions result in stale data on the status line when
starting or stopping because things which didn't used to affect it
haven't been setting context.botl to force an update.  This wasn't
systematic; there are bound to be lots more.
This commit is contained in:
PatR
2020-02-15 15:41:24 -08:00
parent c78a69bc44
commit 2d150d323b
6 changed files with 28 additions and 19 deletions

View File

@@ -1,4 +1,4 @@
/* NetHack 3.6 hack.c $NHDT-Date: 1579261288 2020/01/17 11:41:28 $ $NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.245 $ */
/* NetHack 3.6 hack.c $NHDT-Date: 1581810065 2020/02/15 23:41:05 $ $NHDT-Branch: NetHack-3.7 $:$NHDT-Revision: 1.247 $ */
/* Copyright (c) Stichting Mathematisch Centrum, Amsterdam, 1985. */
/*-Copyright (c) Derek S. Ray, 2015. */
/* NetHack may be freely redistributed. See license for details. */
@@ -2925,10 +2925,11 @@ monster_nearby()
void
nomul(nval)
register int nval;
int nval;
{
if (g.multi < nval)
return; /* This is a bug fix by ab@unido */
g.context.botl |= (g.multi >= 0);
u.uinvulnerable = FALSE; /* Kludge to avoid ctrl-C bug -dlc */
u.usleep = 0;
g.multi = nval;
@@ -2942,6 +2943,7 @@ void
unmul(msg_override)
const char *msg_override;
{
g.context.botl = 1;
g.multi = 0; /* caller will usually have done this already */
if (msg_override)
g.nomovemsg = msg_override;