... and another real-time based problem

[PowerWyrm]

At high level, I tend to rely too much on the character symbol (@, 6, 5...) to check my characters health and react accordingly. In most cases it's ok, but in the most difficult fights it's not enough. I've already had high level characters die because the monster wiped a high amount of HPs in two consecutive turns (like Morgoth's mana storms or Ungoliant's darkness storms), and I didn't have enough time to react before the second HP loss.

The problem is as follows:

server timeline
-----|------------------------------|------------------------------------|------------------------------------|---------------------------|----->
beginning...........players actions processed......monsters actions processed.......player status bar refreshed.....end of turn
of turn


...keypress............................................................................................................client status bar refreshed
-------|-------------------------------------------------------------------------------------------------------------------------------|-------->
client timeline

In most cases, the time to react to any event happening to a player (like a heavy injury) is really small compared to the duration of a turn. In some cases (lag), the client could be refreshed after the next turn has started on the server, leading to the "character is dead, but I don't know it yet so I press keys in vain" effect.
Nothing can be done about lag... but would it be possible to increase the time between status refresh at end of turn and events processed at beginning of next turn? I need to check the "bullet time" feature to see if it's helping...

[Ace]

Maybe this is just a balance issue.

Possible ways out
a) make those uber-monsters slower
b) limit the max. dam of these attacks
c) code it so they cannot do the most dangerous attack twice in a row

[Emulord]

Or make time pass more slower deeper in the dungeon. Ive noticed at high levels, I cant react fast enough to not waste time running, and if you're resting at the bottom, you're foolish. Time passes too fast at the bottom.

[schroeder]

But all that is just masking the problem. In an ideal world, you should always know your status by looking at the screen. I love mangband partly cus I know exactly what is going on, but i must admit that I do NOT know what happening sometimes when everything starts to go down at once, since things don't refresh enough. Masking the problem with bullet time, or just slowing it down more at greater depths just slows it down more so that it will refresh more. Creating a solution without slowing down gameflow would great. Its all about decreasing lag time between pressing a button and not dieing! No idea how this would get done, but yeah.

[Billsey]

It sounds like what you're asking for is two refreshes per player turn. One right away to refresh the player info based on what the player did (between 'players actions processed' and 'monsters actions processed'), then a second to reflect what the monsters did (that matches the current refresh). I'm not sure that that would really fix the problem, since the player info is liable to change (potentially radically) when the monsters do their thing. It would certainly double the bandwidth needed to 'feed' a client, which although it wouldn't affect stuff right now too badly, would certainly start to be a problem if we ever got a really busy server.

An overall solution (and also one that's not liable to happen) would be to run each player in their own thread, and the monsters in their own thread. This would allow a refresh of the player each time a player turn has passed, and monster effects at the first player turn after the monster does his thing.

Another path to take would be to optimize the monster processing. Things are fairly fast right now, but only because we're running on reasonably fast computers.

Anyone have suggestions on how best to implement any of these ideas? Or ideas that sound better? :-)