> For the complete documentation index, see [llms.txt](https://organized-chaos.gitbook.io/organized-chaos-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://organized-chaos.gitbook.io/organized-chaos-docs/chess/game-review.md).

# Game review

Every move of a finished game judged by the computer, with each player's accuracy.

After a game either player can have it reviewed: **Review the game**, on the card at the end of the game or beside the moves. The computer goes through every position of the game and judges every move against the best there was.

<figure><img src="https://3924607527-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkrCqB30nvL5PDNUr89iF%2Fuploads%2FLDA9DMAd7eCt4cZsSEh7%2Fchess-review.webp?alt=media" alt="The review of a game, stepped to a blunder"><figcaption><p>A blunder marked on the board, the better move as a green arrow, and both players' accuracy.</p></figcaption></figure>

## The marks

| Mark          | Meaning                               |
| ------------- | ------------------------------------- |
| ★ Best        | The computer's own choice, or as good |
| ! Excellent   | All but as good                       |
| ✓ Good        | A little less                         |
| ?! Inaccuracy | Gave away some of the chance to win   |
| ? Mistake     | Gave away more                        |
| ?? Blunder    | Gave away much more                   |
| ≡ Book        | A known opening move                  |
| → Forced      | The only legal move                   |

How much a move gives away is counted in the mover's chance to win, worked out from the advantage as Lichess counts it. From the same chances comes each player's **accuracy**, from 0 to 100.

## Reading the review

* Beside the moves: both accuracies, and how many moves of each kind each side played.
* In the move list every move carries its mark.
* Stepping through the game (a click on a move, or the arrow keys) shows the mark on the square the move went to, a **green arrow** for the better move where one was missed, and a **bar beside the board** with how the game stood: in pawns, or mate in so many moves.

A move that looks like a mistake is looked at again, much deeper, before it is called one. A sacrifice whose point lies a few moves on, such as a queen given for a mate, is not taken for a blunder.

## On the server

One game is reviewed at a time. The search runs in slices, `Config.BotSlice` milliseconds of every server tick, like the computer opponent's, so the server stays smooth. Further reviews wait their turn.

| Option               | Default | Meaning                                                                          |
| -------------------- | ------- | -------------------------------------------------------------------------------- |
| `Config.Review`      | `true`  | Offer the review after a game                                                    |
| `Config.ReviewNodes` | `6000`  | How many positions the computer looks at per move. More is more exact and slower |

A game of 40 moves is usually done well within a minute. Everyone with the board open gets the review, spectators included. A new game at the table ends a review that has not finished.