ipax77/sc2dsstats

Starcraft 2 - custom map Direct Strike replay analyzer

sc2dsstats's Issues

Installer CTD

Installer crashes about halfway through the progress bar.
v1.0.13

GUI reports no new replays when replays renamed

I name successful replays after the champion conflicts, such as 'Raynor vs Alarak.' I still have many replays that are losses, accumulating as I play.

But when I start the app, it says no new replays found

korean replay did not detected

direct strike is named '다이렉트 스트라이크' at korea so scdsstats can't detected replay can you fix it? or add some configuration

/sc2dsstats.lib/Data/DSdata.cs

public static Regex rx_ds = new Regex(@"(Direct Strike.).SC2Replay$|(DST.).SC2Replay$", RegexOptions.Singleline);

public static Regex rx_ds = new Regex(@"(다이렉트 스트라이크.).SC2Replay$|(DST.).SC2Replay$", RegexOptions.Singleline);

Multiple Usernames / Replay folder

With version 0.6.0.7 you can now add multiple player names (if you have multiple SC2 accounts) and multiple replay folder (for EU, NA, ..).

You can enter the information in the first run of the application or with File->Options. Separate the values with semicolon: e.g:
PLAYER => player1;player2;player3;
REPLAY_PATH => path1;path2;path3;

Make sure you do not have any spaces before or after the semicolon.
Make sure you keep the order of the replay folders intact and add new folder after the existing ones.

If you already did a workaround for that:

The application will now scan every folder given in REPLAY_PATH - so if you renamed and copied replays form one folder to another you can either delete/move the source files or you can delete the copied replays and rescan by renaming/deleting the stats.csv file.

If you renamed player names in the stats.csv file no changes are necessary.

The location of the stats.csv file can be found in File->Options => STATS_FILE

issue duringthe scan

Hi,
When i try to scan my replays or to show the results i get this,
do you know how to solve this issue ?
I delete and reinstalled the device.
Kind regards

Gametime error / miscalculation

Since 2019/02/28 the decoded timestamp from the DS-replays is wrong (-1 d) and so the inApp start-date / end-date filter are not working as expected.

IronPython not thread safe (?)

IronPython ‘sometimes’ fails loading the s2protocol header in the first one to three threads – if I enqueue them it is all good. Same behavior when I load one engine for each thread (at the cost of performance).