Yea I agree it was super annoying, I just randomly had the idea for the easy way to fix it lol. Idk why I never thought of it before, never did put much thought into removing those.Although "HuK wins their next match in RO8, Heart finishes 4th place, Bomber finishes second place" is very different from just Huk winning WCS America, and I believe it's good that it's listed and tracked separately.

OMG, that was so annoying. Thanks for fixing that >.>There was also "HuK wins WCS America" and "HuK wins their next match in RO8, Heart finishes 4th place, Bomber finishes second place" type stuff. Glad to see this is fixed.

Can i just say your awesome. Really great how much time you put into this and how nice and easy it is to understand the standings.

Sorry about the delay guys, I was just making an improvement to remove duplicate events such as Player A wins their next match (against Player B), and then also showing Player B loses their next match (against Player A). For example we can look at Huk.Before, using the event filters "single positive notor", Huk had events like thisand events like thisBut now it's fixed to favor the current player like Huk winning and Huk losing, so it removes the events for Hyun winning and Hyun losing against Huk, and then after that it favors the winning event so it has soO winning and Innovation winning but it ditches the events for them losing. This works just by finding events that have the same exact number of occurances in the initial block (the first 500,000 samples) and also result in the exact same Blizzcon chances for that player, and then it picks the one with the highest score.This should make it much easier to read especially with the grouped events. I hope you like the change! Will be writing a bit to preview Dreamhack Stockholm Day 2 soon.

~ 43.57 % of the time soO wins their next match in GSL S3 Code S ro2 This would change HuK's Blizzcon chances from ~ 0.99 % to ~ 2.29 % ~ 43.57 % of the time INnoVation loses their next match in GSL S3 Code S ro2 This would change HuK's Blizzcon chances from ~ 0.99 % to ~ 2.29 % ~ 56.43 % of the time INnoVation wins their next match in GSL S3 Code S ro2 This would change HuK's Blizzcon chances from ~ 0.99 % to ~ 0 % ~ 56.43 % of the time soO loses their next match in GSL S3 Code S ro2 This would change HuK's Blizzcon chances from ~ 0.99 % to ~ 0 %

~ 40.33 % of the time HuK wins their next match in WCS AM S3 Premier ro8 This would change HuK's Blizzcon chances from ~ 0.99 % to ~ 2.47 % ~ 59.67 % of the time HuK loses their next match in WCS AM S3 Premier ro8 This would change HuK's Blizzcon chances from ~ 0.99 % to ~ 0 % ~ 40.33 % of the time HyuN loses their next match in WCS AM S3 Premier ro8 This would change HuK's Blizzcon chances from ~ 0.99 % to ~ 2.47 % ~ 59.67 % of the time HyuN wins their next match in WCS AM S3 Premier ro8 This would change HuK's Blizzcon chances from ~ 0.99 % to ~ 0 %