crashing mods causes output_log.txt to be overwritten, causing all info regarding the crash to be lost

When a mod crashes, it will usually write a lot of useful information to output_log.txt. However the game is prone to delete the log shortly after a crash, usually before the log is read and/or submitted with a bug report.

1: the game crashes during startup. A window tells that the mods will be disabled and there is a restart button. Clicking on this button will make the game restart. On restart, a new log is written, overwriting whatever mod errors were in the log.

2: "An error occurred, Please restart game" window shows up ingame. If the player does as it says (restarts), the log will be overwritten.

In either case when the mod creator hears about the issue, the log containing the interesting information will already be gone. This makes bug reports for mods much harder to deal with.

This could be solved by on crash, copy the log to another filename and until restart, write to both logs. The result would be the current log and a log from the last crash, which won't be overwritten unless there is a new crash. This will prevent important information from being lost if a player restarts after a crash. This could be useful for both modded and unmodded crash reports.

Note: yeah I know technically this isn't "client crash" category type of bug (unmodded game doesn't crash), but it's the closest category to the issue. Maybe it's time to add a mod support/API category.