Descent 3 -
Descent 3 dedicated server tool for Windows
|
Written by Thomas
|
Saturday, 03 October 2009 13:34 |
Page 15 of 16
2009-12-20
- The time a server must have been empty before an automatic restart has been changed from 90 seconds to 130 seconds. This spans more than two $player queries to the server and decreases the likelyhood that a server with players in it is restarted automatically.
2009-12-19
- The behaviour for "Loop: on/off" has again changed. Previous versions of the server tool would not remove or touch msn files when they existed already. This version overwrites the file with the current settings and also tries to delete the file when found at server launch. This is actually not very nice when a custom msn file has been created, but I think it is what most people expect. One of the next versions will contain a global option to keep or remove existing msn files.
- Some adjustments and text changes in the tooltips.
2009-12-10
- Tooltips for the console and logging options added. Many other tooltips corrected/extended.
- When min and max time values for the powerup respawns are different, D3Server3 had sent the $setrespawntime command regularly to the Descent 3 server. This version of the tool only sends the $setrespawntime command when its value really changes.
2009-12-07
- Bug fix with "Loop: on/off" (formerly "Warp: on/off"). The configuration could run into a condition where a mission would always branch back to the current level, no matter what the new setting is like. This was because previous versions only removed the branch in one location, which could not be reached anymore when the software or Windows had crashed at the wrong time.
- The time to wait for servers when they are stopping has changed from 5000 ms to 2000 ms. Average computers are much faster now than they were a few years ago.
2009-12-03
- Tooltips changed to baloons for better flexibility. This allows to extend the information shown if required.
- New button "Stop & Exit" added. When used, it stops all servers and then closes the application. It is basically a combination of the buttons "Stop all servers" and "Exit".
- The function to automatically launch servers at program start now doesn't care anymore about servers that failed to start. If a server fails, it is removed from the launch. Before it was possible that D3Server ran into an infinite loop trying to launch a server that permanently failed, but not accepting any user input to prevent its autostart.
2009-11-28
- Global option to use logtext.dll for the event log added.
- Global option to automatically download and install updates added. The software WaitMutCopy is now embedded in D3Server3 to handle automatic updates. Download URI is provided in the update file (see top of this article).
- The DLL logtext.dll is now only used when found in the application folder. Earlier versions also use the DLL when LoadLibrary () can find them somewhere else. This could potentially have lead to versioning conflicts later.
- Some messages changed/corrected.
- Global event log message for the configuration folder added.
- The global setting for the Logtext DLL is stored in and retrieved from the registry rather than the MFC object storage files. This makes the setting available before the config files are loaded.
- Configuration checkbox for each server added to select whether it should be enabled for the global option "Auto launch servers at program start".
- The way "Auto launch servers at startup" works has changed. The previous behaviour of this checkbox is now default and independant of the setting. The new "Auto launch servers" launches all servers that are not marked to be excluded from this function.
- For this purpose, the new setting in the server configuration dialog window had to be made operational ("Enable this server for auto launch at startup").
- Bug fix with version info stored in object configuration files. The version is now taken from the executable's resource.
- Bug fix with "New version available". D3Server3 had not reported the additional information (release date and features) correctly.
2009-11-20
- Players found by D3Server3 now only take one line in the log file. In earlier versions they required two lines.
2009-11-01
- Fixed a buffer overrun in the logging function for the remote console.
- The server tool now waits for the Descent 3 server to respond in the remote console for 500 ms before it starts reading data. This ensures that the telegram coming from the server is complete.
|
Last Updated on Wednesday, 22 October 2014 13:15 |
to post comments.