chessathome
chessathome copied to clipboard
sylvinus
Chess@home
1318946429614 'Fetched computing games : ' 1 1318946429682 'Fetching unresolved pos for game' 4e8dc6af85b793867c0003ad /home/deploy/app/source/www/master/engines/distributed-mongo.js:179 models.Position.count({resolved:false,fen:{$in:_.keys(pos.children)}}, ^ TypeError: Object.keys called on non-object at Function.keys (native) at Promise. (/home/deploy/app/source/www/master/engines/distributed-mongo.js:179:58) at Promise....
"suicidal" moves (gave a lot of quality pieces) once seen problematic situation - resign would be more elegant...
It would be good to ask user if castling was intended. Sometimes, by error, piece can "fall" to wrong cell and elegant castling is not possible any more. Maybe also...
support endgame tablebase there is at least one public tablebase web service at http://www.lokasoft.nl/tbapi.aspx it does not have (most of) 6 men positions, but it's a good start
Show last move (easier than to look/scroll history, sometimes also history is cleared...). Usually this is implemented by highlighting (border) cell holding piece that did last move (on demand action)
Currently pawns automatically become queens upon promotion. A user needs to be able to select which piece to promote to (rook, bishop, knight or queen). Also, I don't know if...
