All ideas tagged "xlogfile"

#3087

 · 
SpliceHack

Rather than marathon mode using a fixed value of 999 HP, you can set an option to control how much HP is used. (If the option is not set, it will default to 999). The value should appear in both the xlogfile (so that tournaments can set some threshold of HP beyond which the game doesn’t count) and dumplogs.

#2384

 · 
vanilla

The xlogfile saves the spot on the high score list that you achieved at the time the game ended.

#2319

 · 
vanilla

The xlogfile shows which turn a conduct was first broken on, rather than compacting all conducts into a bitmask.

#1187

 · 
vanilla

The game records the number of times the mysterious force triggers in either the dumplog or the xlogfile, so that it can be observed and analyzed later.

#1115

 · 
vanilla

Track, and report at the end of the game in the dumplog or xlogfile, how many times the player prayed and sacrificed.

#155

 · 
vanilla

Have a record in the xlogfile of whether the game was likely a startscum, for analysis purposes. It’s easier for the game to track things like fountain quaffing and using obvious dangerous items. How exactly this would happen is not determined; the game probably shouldn’t try to make a decision itself, there will be some false negatives and positives, but storing fields for everything like “number of times quaffed from a fountain” is probably bad too. Also, if players are aware of a scum-detecting algorithm, some will deliberately work around it.