Allow Manual Input Of Round Robin Matches Ordering
Have an option to manually input the order of matches in a round robin. Right now, when I drag the participants to a different spot to re-order the matches, Challonge automatically changes other matches around, even the ones I had previously manually edited. And I'm not even allowed to drag an entire match to a different spot in the same round (which theoretically shouldn't affect any other round), I'm only allowed to drag a single participant at a time, which affects all other rounds. I just want an option to manually input the order of the matches and then click save; nothing should be automatically moved for me while I'm in editing mode still. There can be a verification after I'm done editing to ensure it's a valid round robing schedule, but please don't automatically change things around while I'm still editing. This editing mode doesn't even need to be a drag-and-drop interface; I would be perfectly happy with a text box or a file upload to manually input the ordering.
My use case is that Challonge doesn't optimally distribute when participants play. For example, with a round robin of 7 participants, often a participant has to play twice in a row, and sometimes they have to wait 7 matches before they play again after their last match. This is bad because sometimes participants don't get a break, and other times, they complain that they're playing cold and need a warm-up again before their match because it was so long since their last match. A participant playing twice in a row also causes conflicts when we're running multiple matches in parallel. Challonge has not found a way to fix this scheduling issue, but I have. I've written a script that given n participants, finds an optimally distributed round robin schedule. For example, with 7 participants, my script will output a round robin schedule where every participant gets a minimum break of 2 matches in between their own matches, and a maximum break of 3 matches. But Challonge won't let me input this schedule, so I'm still stuck with using Challonge's inoptimal scheduling if I want to use Challonge at all.