Every launch truncated rpl4.log, so a tester who played six races and hit
trouble in the second had nothing to send: the evidence was overwritten by
the races that came after. Collecting it meant copying the file aside
between games, which nobody remembers to do while five other people are
waiting to start - and the logs that did arrive were a scatter of rpl4
(2).log through rpl4 (16).log that had to be sorted out afterwards.
It appends now. Each run opens with a rule and the wall-clock time it
started, because that is what a report is made of - "the third race, about
nine" - and nothing else in the log carries the time of day. Play the
evening, send one file.
It rolls once to rpl4.prev.log past 64 MB rather than growing without
limit; only the per-frame diagnostics can manage that in an evening, but a
log nobody can open is no more use than one that was overwritten.
RP412LOGAPPEND=0 restores the old behaviour.
Verified: three launches in a scratch install take the file 1521 -> 3042
-> 4563 bytes with three stamped separators, and RP412LOGAPPEND=0 puts it
back to one run of 1368.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CydandClaude Opus 5
54738d3259