Howdy folks, i just updated the Control Center to version 2.0.1. Even from the 2.0.0 Beta standpoint, this thing is UPDATED... Thousands of lines of code were updated, tweaked and Rewritten to make this thing run as smooth and bug free as possible on your machine. There was quite a few changes to the Stats Python files as well, So you will need to update those by pressing the "Restore Ranked Python Files" button on the Bf2 Server Settings Tab. Don't worry though, i updated that feature as well, and your custom python scripts and medal data files will NOT be removed when the restore feature happens .
WARNING: You will need Uninstall your old Stats Python files BEFORE updating to the new Control Center!
Speaking of Medal Data, your old medal data files will no longer fully work . Some changes were made to the medal data files and you will need to delete your medal data profiles. They will still... technically work, but whenever...
Hey everyone, I've been working diligently on the new version of the BF2Statistics Control Center, and decided it was time to upgrade the framework on which the control center was built on, and take advantage of the newer C# 5.0 features. I've done quite a bit of testing myself, but as always, i cannot find all the bugs . Below i will include a link to the new 2.0 version, and you guys post any issues you find in this thread so i can get any bugs i may have missed fixed before release.
One of the big changes was switching installers! The control center will now use Install Shield installer instead of the crappy Microsoft one from before, so heads up on that . Also, the installer should automatically install the required .Net framework and C++ redistributes if they are not already installed on your system.
Just dropping in to let everyone know that Version 1.9.0 of the Control Center has been released! You can download the new version by clicking the "Resources" button in the navigation pane, and then selecting "BF2Statistics Control Center". If anyone has any issues with the new version, please create a new issue on the Github site located here.