Virtual Server Admin

Wreckfest server management tool

A tool to manage launch and maintenance of Wreckfest servers, also report player stats such as race damage scores into the chat.

BACK UP YOUR CONFIGURATION FILE BEFORE EDITING IT IN THIS APPLICATION.

IF YOU DOWNLOAD A NEW VERSION DO NOT OVERWRITE YOUR EXISTING WFDamageTracker.exe.config FILE WITH THE ONE INSIDE THIS ZIP FILE

Download the Virtual Server Admin Tool here..

The damage scores / server chat part will only work if you have full console access to the PC / server that is running your Wreckfest game server

If you use a remote server, you'll need to use a full console remote access tool such as VNC to access it, this app won't work properly over Teminal Services / RDP

If you don't have the above, or use a rented server, this app can still be used to log all players' race scores, they'll be visible on this website.

I'm working on more REST API endpoints, so that your server data will be available to you in JSON objects that you can consume on your own websites / Discord etc.

When / if Bugbear release new tracks / seasons, this application will screw up its track indexes and report incorrect tracks. A new version of the track list will need to be generated before it's fixed. The application downloads track lists from the website so that new versions of the application will not need to be distributed each time there's an update. Hopefully.

Due to continuing updates provided by Bugbear - new tracks etc. - I've tried to make the app as 'dumb' as possible with all config file processing, track lists stored on the server in order to try to minimise the amount of new versions / downloads required after each update.

You can contact me via the Discord link on the Home page.

More info in the Readme file included in the download.

Change Log

  • 2022-01-06 - Added derby maps to tracks database so more event loops should load
  • 2022-01-06 - Automatically disable reporting of current / next event in event loop if voting is enabled
  • 2022-01-06 - Better handling of unrecognised track names in event loop. Events with unrecognised names are now skipped from event loop loading and a notification added to the log window
  • 2022-01-06 - Handling of server names containing one or multiple = characters
  • 2022-01-06 - Initial power management handling introduced. The app won't currently restart or close your WF server, but it will add a notification in the log at the point where it would have done.

Power Management

I'd like my WF server to be self sustaining and restart itself when it needs to. In my experience, WF servers that have been left running, and have been busy, for a few days, get a bit sluggish and laggy.

The app has the ability to restart the WF server based on two thresholds - number of players and number of minutes.

For example, if you set the players threshold to 16 and the minutes threshold to 1440 (one day) then the app will automatically restart the WF server once both of these thresholds have passed. So if at any point, the number of players at one time has exceeded 16 and the server has been up for longer than 1440 minutes, the app will set a flag to restart the server next time it is empty (eg when the last player leaves).

This is still in the testing stage, so the app will do all the checks, fire up the warnings, but not actually restart the server, just put a note in the log window that it would have done.