'''Author: ''' ()
In this wiki I explain how you can write to custom logs and also write silently without having the console log open itself when the game starts!
To log to any custom file name that will appear in Saved/Logs, simply add this to your commandline when launching the game:
This will still open the console window, but will write to the file of your choosing, overwriting any previous contents.
The great part about this is if you routinely test multiplayer, you can easily delineate the logs of different clients in a way that makes sense to you, using different commandlines for each instance.
If you want to log but dont want to distract your user with the console log popping up all the time, you can add this switch:
so now you have:
You dont have to include -log in this case.
In fact omitting -log and just using LOG= seems to work the same as -silent as far as I can tell.
It is -log that causes the console window to open.
Please note that when you specify the name, it will overwrite previous log files, so if the user generates important log info but then plays again before telling you what happened, the log that occurred during the crash will be lost already.
To avoid this you can use -silent without specifying a name
This also appears to be the default behavior if you do not include any logging specifications on the commandline.
So the best use of specific log naming is for your own iterative testing where you expect to only want the latest logs :)