Automated Analysis

Automated analysis runs the engine on every position in a game and inserts move classifications — inaccuracy, mistake, blunder — directly into the game’s move tree. The results are cached, so subsequent views of the same game are instant.

Analysing a single game

1. Open a game on the Board page.
2. Click the Analyse button in the board toolbar.
3. Masterboard runs the engine at depth 18 on every position. Analysis runs in the background — you can continue navigating the game or use the rest of the app while it runs.
4. When complete, move classifications and accuracy percentages appear automatically.

Bulk analysis

You can analyse multiple games from the Games page without opening each one:

1. Select one or more games in the Games list (Shift+click or Ctrl+click for multi-select).
2. Right-click the selection and choose Analyse N games (where N is the number selected).
3. Analysis runs in the background for each game in turn.

Tip

Bulk analysis is useful after a tournament or after importing a batch of games — select all new games and let the engine classify them overnight.

What gets annotated

After analysis, each move is classified based on how much it deviates from the engine’s best move:

Symbol	Name	Meaning
?!	Inaccuracy	Small mistake; better was available
?	Mistake	Significant error that changes the evaluation
??	Blunder	Severe error — a lost advantage, tactic missed, or losing move

For each classified move, Masterboard inserts the engine’s best move as an alternative variation in the move tree, so you can immediately see what you should have played.

Accuracy percentage

After analysis completes, the Notation panel header shows per-player accuracy percentages using the same formula as Lichess (WDL-based). A score of 100% means every move was the engine’s top choice; lower scores reflect how often and how severely you deviated.

Cached results

Analysis results are stored in the local database. Reopening an analysed game does not re-run the engine — results are shown instantly from the cache. To re-analyse a game (e.g. with a different engine or higher depth), use the Analyse button again; the old annotations are replaced.