Blunder Free Chess – visualize which squares are attacked

I think it's fairly obvious the name is to help the user prevent blunders, not that blunders are literally impossible by both players.

>those colors are horrible to see

After someone gave me feedback on lichess, I tried a heatmap instead (with green for white and red black), I'm not sure it's an improvement but you can see if you like it any better: https://taonexus.com/blunderfreechess2.html

On Lichess you can visualize then confirm your move, helps a lot

>I love the concept.

Thanks!

>I had a situation where my queen was being attacked by a bishop, and the board showed a "safe" space to move my queen, but that queen would have still been attacked by the bishop along that diagonal.

Are you sure? Can you send a screenshot? Any place the opposing bishop attacks would have a dot on it. (The green highlighting when you pick up a piece shows all legal moves, not just safe moves.)

I've played hundreds of games and I'm not sure a single one hasn't been decided by a "basic blunder", and I mean very basic. I bet the only games in which I've not committed one myself (and only gone on to win if it was overlooked, which they often are) were ones in which I fool's-mated someone.

There's chess-people's experience of the game, then there's how every single other person, including those who play it quite a bit, experiences the game. A "normal game" in the sense of the average of all games played, maybe that features very few basic blunders, just because chess people play so very many games (though huge numbers of people play a lifetime count of like ten to one thousand games, and never move out of basic blunders being pretty common, so I wouldn't bet on that describing an average game, but maybe) but the average person's experience of the game is that it's entirely about basic blunders, like, that's the main thing on which the game turns.

Looks like computer moves randomly:

    /*************************************************************
     * Computer Move (random)
     *************************************************************/
    function computerMove(){
      if (gameOver) return;
      let wasWhite=whiteToMove;
      let moves=generateLegalMoves(wasWhite);
      if (moves.length===0){
        detectGameState();
        return;
      }
      let randIndex=Math.floor(Math.random()*moves.length);
      let move=moves[randIndex];
      makeMove(move);
      renderBoard();
      detectGameState();

      if (!wasWhite){
        fullmoveNumber++;
      }
    }

Close your eyes when you make your moves to increase difficulty

They wrote their own because it's more fun to do that, and also because they really wanted me to win. The computer is really really bad

>I'm curious as to why you wrote your own chess implementation

I was investigating whether AI can write a complete game of chess in one shot, I livestreamed that here[1] and the answer is no (conclusion: major rules are there, but buggy), but I was able to get it into a working state after many hours of back and forth.

The original implementation froze whenever a pawn got to the seventh rank, and allowed castling out of and through check (illegal), it was very buggy.

Iterating with the AI, I added tons of stuff like drag to move pieces, mobile support, and, yes, computer play. When that was finished (it is available at: https://taonexus.com/chess.html ) I had it make this blunder-free variant and it got it pretty fast.

[1] https://www.youtube.com/watch?v=AhJ07anVkYk

That'll be a little bit unfair

I'm extremely mediocre and also found the instant-black-move a bit confusing. Would definitely be an improvement to add a "trail."