benchmarking saves

[drdozer]

I've been doing some benchmarking using the --benchmark option on the binary. It's much better than simply running the game. However, can I request a couple of simple improvements?

1. An option to save out the world at the end of the benchmark run. The reason is that it is often necessary to inspect the state of the game at the end to check that the benchmark was benchmarking what you thought it was. For example, if you are running a megabase for 10k ticks, you want to be sure that at the end of the benchmark that the world is running, rather than it having been eaten by biters. If it got eaten, then you aren't benchmarking the efficiency of your base, but the cycles cost of biter attacks.

2. An option to save out production stats. Again, to make sure that you are benchmarking what you think you are, it is necessary to know the production stats for key items. For example, to ensure that you have been launching 2rpm throughout, or to run 5 smelter setups and validate that each was producing the same number of plates and that you haven't ended up measuring that the more performant build was the one that produced 20% less output.

I know this isn't the primary concern of most players, but these seem to me to be fairly minor changes, and they would be very, very useful for us who like to min/max our worlds.