Combat report .txt does not generate with --archive and an inaccurate .txt

[Lokasenna]

Well, I started this post because I thought I had a more serious bug in which a combatreport.txt might not be generated seemingly at random, but it's more benign than that - I caused it.


I am the Allies in a PBEM. I watched the replay. I later went to refer to the textfile, without having loaded anything other than the next turn's file, and there is no combat report for the associate turn. In my main save folder, there is a combatreport.txt from back in June from the last turn: August 13.

In the 'archive' folder (I do use the --archive switch), there is a combatreport_440814.txt because I incorrectly copied it in: my opponent had only sent me the replay and combatreport.txt from the August 13 turn, and I wanted to load Intel Monkey/etc so I copied the files into the archive folder manually and renamed them with dates. But I renamed the combat report file incorrectly at first and did not delete the duplicate.

When I then watched the August 14 replay, with the combatreport_440814.txt in the 'archive' folder, even the combatreport.txt in my 'save' directory did not update. Shouldn't it have done so, even if there is something built in to the --archive functionality that prevents overwriting a file?

I am going to delete the erroneous combatreport_440814.txt file that I created last month and run my replay again to properly generate the files, but if it's not too much trouble it might be nice to fix that to prevent user errors like this [:'(].