toxicfrog / doomrl-server Goto Github PK

While playing earlier, something went wrong upon finishing a game, after it archived the ttyrec and mortem files but before it wrote the scoreline. (No bug report for this because DoomRL wasn't running in debug mode; I don't even have a useful error message.) This resulted in the scoreline getting lost. Due to the way the archive code is written that mortem and ttyrec wouldn't be overwritten, but neither would they show up in the output of 'scores', 'replay', or 'mortem' (although they'd still be accessible by number).

Ideally DoomRL should be robust enough that this never happens. Failing that, there should be an admin command to scan and rebuild the scorefiles.

E.g. display i, *i*, and %i% for imp/act, imp/hit and imp/die respectively.

DoomRL on the server runs without sound. But what if it had subtitles for the various sounds used?

Preliminary idea: provide a custom libSDL_mixer.so that implements the mixer API, but stub out most of the functions. When called upon to play a sound, match it against a (sound -> message) map and emit the message at the bottom of the screen.

We could also get fancier with this, e.g. with a "Heard:" line at the bottom where everything you hear appears there when heard and gradually fades out with time.

DoomRL's output is extremely noisy. At the moment a filter is installed between ttyrec and the output ttyrec file in order to strip this noise. Installing it between DoomRL and ttyrec would be even better, since it would reduce bandwidth usage to nearly zero. Some sort of timestamp correction would still be needed for the ttyrec file, but this could be done offline once the game is complete and the file is being archived.

Replace the / sounds with actual descriptions like "booted feet" or "a scream of pain" or the like.

At minimum it should let people download configs, mortems, and ttyrecs. Ideally, I'd like the following:

• output of scores
• output of scores <player>
• downloadable mortem and ttyrec for each scoreline
• stats page listing #games, %won, top killers

In particular, a new frame is written for every new sound. It should at least be possible to keep track of what the last frame looked like and not emit a new frame if there are no new sounds to display.