Gama Announcement for OP

By voidreturn, in X-Wing

It would be nice if some official tournament software with nice production values makes it out by regionals. I wonder if it really would be used instead of the Cryodex, though, haha

While Cryodex is nice and useful, it's not 100% accurate. I know others have complained about it messing up in later rounds, but I've had it pair the #3 guy against the #8 in the second round before. True, #5 and #6 had just played each other, so they couldn't match up, but my understanding is that 3 plays 4, 5 plays 7 and 6 plays 8... not 3 plays 8, 4 plays 5 and 6 plays 7.

Again, I still use Cryodex, and I think it's a wonderful program, but it is not without it's flaws. As such, if you rely on it without checking the pairings manually, you'll more than likely be making illegal pairings. However, if FFG was to release a TO software, even if it had a few bugs in it, at least you're using the official software to make the pairings and no one can complain.

FFG does have software out there, it's currently terrible. I'm hoping the new stuff is better.

I can't wait to see what they have for software. I sincerely hope it beats the crap out of Cryodex. Getting everyone running smooth and accurate tournaments is the end goal, and if that is achieved then I'll back it all the way.

I know it won't happen, but I'd love to get ahold of their code to see how they handle some of the "problems" with running a tournament. As mentioned above, dealing with duplicate pairings is prolly the hardest part. Sure it is easy to look at some rankings and determine the smallest impact change to allow the event to continue, but putting that into a programmatic function is a nightmare. Cryodex does the best it can and I'm sure I could look at your (Khyros) particular event and show you how it made complete sense to put 3 vs 8 (please message me if you're interested). Frankly, those odd cases are why there is a disclaimer whenever the program does that for you. TOs should be checking things out when that happens.

FFG does have software out there, it's currently terrible. I'm hoping the new stuff is better.

I missed out on top 4/5 finish at regionals last year because of both that software and the terrible user of it, the software calculated MoV incorrectly for multiple players, the judge refused to fix it, because FFG "had" to have everything done "by the book".

FFG does have software out there, it's currently terrible. I'm hoping the new stuff is better.

Where is it? I couldn't find it on their support or product pages.

they mean their OverPowered games. X-Wings are getting twelve attack dice soon, every other ship remains untouched. This is just one example.

I think the most interesting part of this is if they use data collected from tournaments to help balance and develop future products.

I know it won't happen, but I'd love to get ahold of their code to see how they handle some of the "problems" with running a tournament. As mentioned above, dealing with duplicate pairings is prolly the hardest part. Sure it is easy to look at some rankings and determine the smallest impact change to allow the event to continue, but putting that into a programmatic function is a nightmare. Cryodex does the best it can and I'm sure I could look at your (Khyros) particular event and show you how it made complete sense to put 3 vs 8 (please message me if you're interested). Frankly, those odd cases are why there is a disclaimer whenever the program does that for you. TOs should be checking things out when that happens.

How would you deal with duplicate pairings?

Seems like the easiest, fool proof way to fix them is simply to take the top ranked player, match him up against the highest ranked player he hasn't played yet, and then repeat until everyone is paired up. At least, that's how we've been doing it...

I wonder in what cases this wouldn't be the optimal method?

And how would you determine the optimal method, i.e. what are you trying to minimize/maximize?

Bubble sort. :P

I know it won't happen, but I'd love to get ahold of their code to see how they handle some of the "problems" with running a tournament. As mentioned above, dealing with duplicate pairings is prolly the hardest part. Sure it is easy to look at some rankings and determine the smallest impact change to allow the event to continue, but putting that into a programmatic function is a nightmare. Cryodex does the best it can and I'm sure I could look at your (Khyros) particular event and show you how it made complete sense to put 3 vs 8 (please message me if you're interested). Frankly, those odd cases are why there is a disclaimer whenever the program does that for you. TOs should be checking things out when that happens.

How would you deal with duplicate pairings?

Seems like the easiest, fool proof way to fix them is simply to take the top ranked player, match him up against the highest ranked player he hasn't played yet, and then repeat until everyone is paired up. At least, that's how we've been doing it...

I wonder in what cases this wouldn't be the optimal method?

And how would you determine the optimal method, i.e. what are you trying to minimize/maximize?

You can go in directly to change the duplicate matches, Killeradvark.

Yep, I do that as well in my Heroscape tournaments. (I use the software to run the tourneys; it's great for other gaming tourneys as well.