At the event Oren references, we had 127 players without byes. Following Method #2, our SK launched the event. However, he accepted the default round count of 7. We also had 5 players with byes giving us a true count of 132 players for 8 rounds which was announced.
We didn't know there was an issue until the last entry in round 7 and the prompt for playoffs. When we tried changing the round count, WER disallowed it because we were in the final round.
The Fix:
Collect the round's pairings and results slips.
Delete the round in WER.
From the second-to-last round, correct the round count.*
Start the new second-to-last round and manually recreate matches.
Input existing results (be careful that the player order on screen may not match on slip).
Start the actual final round.
* The Weird:
What was especially strange is that the system didn't seem to be able to take the round change. Our SK got errors even after deleting the incorrect “final” round when trying to change the rounds count. The box pops up with a field for a number already populated, and clicking the field gives an error and doesn't let you replace the highlighted number with a new number…
Click next to the bad round number so there is a cursor by the number, not highlight over the number. Ex: 7|
Type the correct round number next to the bad one. Ex. 78|
Move the cursor if needed and delete or backspace the bad number. Ex. 7|8, backspace, |8
Save the new number.
Originally posted by Dominik Chlobowski:
Can you explain what the problem was? To the best of my knowledge, it's been possible to change the amount of rounds since a good amount of updates ago.
W dniu poniedziałek, 11 sierpnia 2014 Oren Firestein <
forum-11791-e236@apps.magicjudges.org> napisał(a):
> If you go with method #2, make sure that you manually set the correct number of rounds …
> We had this happen at an event in Seattle a couple weeks ago, and it was messy to fix.