• Differentiate between 'racing' and 'non-racing' checkers in the
  gammon games where it matters.


• Highlight captured (but not yet removed) pieces in the various
  checkers and camelot games.


• In the Frog Finder/Frog Legs, mark squares that have been guessed,
  but do not have a frog.

• Make shooting the default in Frog Finder/Frog Legs; require only an
  extra click if you want to guess (as shooting occurs far more often
  than guessing). If you make guess/shoot a radio button (with 'guess'
  the default) one never needs two server requests to make a single
  move.


• Use some Javascript to allow people to select their colours for a
  guess in Logic. This reduces the number of server requests by nine
  for each turn.


• When setting up a position in (Crazy) Screen Chess, keep the current
  placed piece "active" after placing - if there's still such a piece
  in hand. This allows one to set up their pawns with 9 server requests
  instead of 16 requests.


• Don't force people to roll the dice in gammon games if they have a
  non-racing checker on the bar, and the opponent keeps their entire
  home blocked with at least 2 checkers on each point (that is, don't
  force the die to be rolled if there's no way a checker can be moved).

• A full autoplay (that is, the computer moves (or passes) on behalf of
  the player if the player has just one possible move. Useful for games
  like Ludo, the various Gammon variants, the Checkers variants (with
  their forced capturing), Camelot variants and to a lesser extend for
  the Chess variants.


• Since the above is unlikely to happen, how about having a button
  "Play forced move" which will be there when you only have one move
  available. Then you can play your forced moves with just one click.


• Better even, have a button "Play all forced moves" on the main page
  that playes all forced moves.

• Being able to create a tournament with "all games", where "all games"
  means "all games as exist when the tournament starts", as
  opposed to the current "all games as exist when the tournament is
  defined". If you have dozens of open tournaments, it takes
  a lot of work to add a game to all the tournaments.


• Elimination tournaments that allow for a number of players that isn't
  a power of 2. That way, you can have a large elimination tournament
  without having a high risk it gets deleted because you didn't guess the
  number of willing participants correctly.

• I'm only interested in a small fraction of the automated messages I get.
  I can easily do without the message you get when a game in a multi-point
  backgammon match ends (just notify me when the match is finished). I
  don't care whether a next round of a tournament I created starts. I'm
  not interested in the couple of pawns that sign up for a million tournaments
  and get booted off when the tournament starts because they don't have
  enough slots (how about removing pawns from *all* open tournaments when
  they filled up their slots?). I can do without messages about postponed
  or deleted tournaments. I'd like to see some configuration options about
  what kind of automated messages you want to get, and which ones you don't
  want.

• 9 Men Morris. (Well known game)
  
• Cats and Dogs. Played on an 8x8 (Go) board. Players alternate placing stones of their colour on the board, under the restriction you cannot put a stone horizontally or vertically adjacent to stone of your opponents colour. First player who cannot move loses.
  
• Roots. Played on a 19x19 board. Players start with 8 'roots' of one stone each (roots are set up in a 4 x 4 grid, evenly spread out over the board, in alternating colours). Players alternate placing a stone of their colour on the board under the condition that each placed stone is horizontally or vertically adjacent to exactly one stone of their colour - so the groups look like root systems. If after a stone is placed one or more root systems cannot expand any further, they are removed from the board immediately. Winner is the person who eliminates all root systems of the other player.
  
• Connection games, like hex, twixt, or Y.
  
• Clobber. Played on an NxM checkerboard (N and M cannot be both odd). Initially, all white squares are filled with white stones; all black squares with black stones. One player plays the white stones, the other the black. Players alternate moves. A move consist of taking one of your stones and moving it horizontally or vertically one square to a square occupied by a stone of your opponent. The opponents stone is removed. First player who cannot move loses.
  </ul>

Auto pass is an option that players can use or not, so i would like to know if there's the possibility to become this option compulsory for everybody, or at least for players with a high number of games like 500 or 1000, for example.

I say that because i'm playing with ladiesmaninny32 a game with 7 days per move that started on August and until now he only did 6 moves...6 moves in 6 months. Problem is not 7 days per move, but he use holidays and when holidays of 2008 finished, he won holidays of 2009.  This is ridiculous, the game will take a long time.

And ladiesmaninny32 is only an example, there're more players to do the same thing.