Thanks for the reply. I now see the problem. I am getting:I'm seeing the same stuff I saw before, except that after the server has been up several hours, I can't connect to telnet anymore.
Logging options are in the server config.
I do not see that option. What is the line supposed to be?I'm seeing the same stuff I saw before, except that after the server has been up several hours, I can't connect to telnet anymore.
Logging options are in the server config.
-logfile 7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt
-logfile D:\servers\7 Days to Die\7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt
<property name="HideCommandExecutionLog" value="0"/> <!-- Hide logging of command execution. 0 = show everything, 1 = hide only from Telnet/ControlPanel, 2 = also hide from remote game clients, 3 = hide everything -->
So now you have to have that when it starts up the startdedicated.bat?Log path when starting the client has to be the absolute path, No relative shortcuts work currently.
Before you could use...
Now you have to use...Code:-logfile 7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt
The logging options aren't new. They've been in since a16 at least.Code:-logfile D:\servers\7 Days to Die\7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt
Code:<property name="HideCommandExecutionLog" value="0"/> <!-- Hide logging of command execution. 0 = show everything, 1 = hide only from Telnet/ControlPanel, 2 = also hide from remote game clients, 3 = hide everything -->
Was your bug report ever re-opened? You should probably re-open it, cite your old report, and mention that the solution did not fix it.So I opened a bug report and then closed it thinking it was something I did by copying the player/map data. As it turns out that isn't the case. Sometimes when I start the server (with startdedicated bat) it will not be able to show any console data (log has an error). Other times it starts like normal. Haven't been able to diagnose it yet.