EPT
Hi all, I’m the SC2 Product Manager at DreamHack and want to touch on what happened here and where we’re at.
First, this is our mistake on the DreamHack side and I apologize for that. We messed up and it’s caused a lot of grief to players and fans who are affected by it. We had a bracket up all day on Sunday for the Europe qualifiers that was not correct and we didn’t properly catch and act on it until far too late. Our typical process for making and communicating these brackets involves a step where people double check them, because it’s a complex system that isn’t done easily or quickly (we rank players by WCS points separately for those who are 1st and 2nd place finishers in their groups, and then swap matchups to avoid anyone facing someone from their group immediately in the bracket). This is why we didn’t show the Ro16 bracket immediately on the Day 2 broadcast of the events last year for instance, or why those at the event are used to repeatedly asking the admins if the brackets are done yet.
Unfortunately that system failed this time and the bracket had not been gone through with a fine tooth comb as usual last night. To compound it, our admins weren’t available to answer questions on the bracket before play started so people went ahead and played. These are both serious mistakes on our part.
We were able to take a look at it today but not until people were already competing, which means when it was fixed people had new opponents though they may have been mid-match. 'm sorry for that, it disrupts everyone’s flow for who they prepare for and plan their event and the competitors deserve more than what we gave them tonight. I’ll be checking to make sure we have the proper redundancies for communication and bracket seeding in the future so situations like this aren’t possible.
First, this is our mistake on the DreamHack side and I apologize for that. We messed up and it’s caused a lot of grief to players and fans who are affected by it. We had a bracket up all day on Sunday for the Europe qualifiers that was not correct and we didn’t properly catch and act on it until far too late. Our typical process for making and communicating these brackets involves a step where people double check them, because it’s a complex system that isn’t done easily or quickly (we rank players by WCS points separately for those who are 1st and 2nd place finishers in their groups, and then swap matchups to avoid anyone facing someone from their group immediately in the bracket). This is why we didn’t show the Ro16 bracket immediately on the Day 2 broadcast of the events last year for instance, or why those at the event are used to repeatedly asking the admins if the brackets are done yet.
Unfortunately that system failed this time and the bracket had not been gone through with a fine tooth comb as usual last night. To compound it, our admins weren’t available to answer questions on the bracket before play started so people went ahead and played. These are both serious mistakes on our part.
We were able to take a look at it today but not until people were already competing, which means when it was fixed people had new opponents though they may have been mid-match. 'm sorry for that, it disrupts everyone’s flow for who they prepare for and plan their event and the competitors deserve more than what we gave them tonight. I’ll be checking to make sure we have the proper redundancies for communication and bracket seeding in the future so situations like this aren’t possible.
Thanks [16thSq]Kuro for posting on page 2
The bracket stage of WCS Regional Challengers for Leipzig were supposed to begin today at 19:00 CET.
Games were underway at the appropriate start time with several players already concluding their first games. However, it was brought to attention that the seeding for the bracket stage was actually incorrect.
*original incorrectly seeded bracket
*ShoWTimE noticing possible incorrect seeding in the group stage as well
There were no admins available to check on the bracket seeding at the start of the competition, which led to players beginning matches for which they had spent the night preparing. An admin finally confirmed that the matches were incorrectly seeded about 30 minutes after the start time of the event.
One player, Serral, had already won his match and qualified based on the incorrect bracket
It was ruled that the completed matches would be voided and the bracket would be correctly reseeded to the intended matches. There was a 2 hour delay issued for the event with the reasoning of giving players time to prepare for their new match ups.
The correct bracket has
Elazer vs Bly
uThermal vs StephanoSerral vs 
HarstemThe
Snute vs Nerchio match has been left unchanged.The NA Challengers bracket appears to be correct from the start. No changes will be needed
This is not the first issue with WCS this season, as in the NA Challenger events, Scarlett and Hunta restarted a match after playing most of it with skins active (skins must be turned off during WCS events).
