ahawksfan Posted October 16, 2019 Share Posted October 16, 2019 Noticing with the A18 server console no information is being displayed other than {Date/Time} Win INF Thread started. In A17 there was events as the server processed them. Is there a "verbose" option when starting the server now? Thanks! Link to comment Share on other sites More sharing options...
SylenThunder Posted October 16, 2019 Share Posted October 16, 2019 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. Link to comment Share on other sites More sharing options...
ahawksfan Posted October 16, 2019 Author Share Posted October 16, 2019 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. Thanks for the reply. I now see the problem. I am getting: 2019-10-16T11:20:51 21.131 ERR Error sending to console server: I will open a case in the DEV thread. Link to comment Share on other sites More sharing options...
Cadamier Posted October 18, 2019 Share Posted October 18, 2019 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? How is the line supposed to read - it was mentioned in the release notes that the save location is supposed to be designated. Link to comment Share on other sites More sharing options...
SylenThunder Posted October 18, 2019 Share Posted October 18, 2019 Log path when starting the client has to be the absolute path, No relative shortcuts work currently. Before you could use... -logfile 7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt Now you have to use... -logfile D:\servers\7 Days to Die\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. <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 --> Link to comment Share on other sites More sharing options...
Cadamier Posted October 19, 2019 Share Posted October 19, 2019 Log path when starting the client has to be the absolute path, No relative shortcuts work currently. Before you could use... -logfile 7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt Now you have to use... -logfile D:\servers\7 Days to Die\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. <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? Link to comment Share on other sites More sharing options...
SylenThunder Posted October 19, 2019 Share Posted October 19, 2019 Yeah Link to comment Share on other sites More sharing options...
ahawksfan Posted October 24, 2019 Author Share Posted October 24, 2019 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. Link to comment Share on other sites More sharing options...
Smugger Posted October 29, 2019 Share Posted October 29, 2019 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. 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. Do you have Any solutions yet? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.