Woodruff wrote:ubersky wrote:Seems like the easiest thing to do is for the TO to be able to set slot/game reservations (unordered) to which the password mechanism currently used would be replaced with a simple lookup list of members allowed to join the game.
Sounds interesting, but I'm not sure I follow your terminology. Could you explain it a bit better for those of us who...uh...read slower than others? <laughing>
lol

Basically right now the only way to regulate joins is with a password, and that can lead to mistakes for large Tournaments, especially with the auto-join.
Since the Games backend should have access to the memberlist, whomever is creating the game can simply set a list of members that can join the game.
Since join order determines color, and some might get upset of the TO orders them wrong, I wouldn't set the reservations on the exact slot, just simply restrict which members can join a game. (Implement team reservations for team based games).
This way a password would no longer be needed for Tournament games because anyone not on the memberlist for that game, would not be allowed to join it.
You can build in some automation to the game creation process, so that after the game is created, and the memberlist is set, the TO can push a button and notify all of the members in the game of the games existence, and provide a link to join. This would streamline the game creation process, and reduce some of the paper-work the TO's have to do and manage.
I know that it's been said that there is a large Tournament automation rework in theworks, but a memberlist should be easier to implement in the short term and would have good benefits IMHO.

You can also add the reserved games to the Awaiting tab on the My Games list, or even add a Tournament tab