Xiangqi Blunder Checker

Xiangqi Blunder Checker

Use AI analysis to find missed tactics, blunders, and turning points, then understand why a move made the position worse.

A blunder checker should not merely say that a move was bad. It should show where the mistake happened, why it happened, and how to avoid the same pattern later. The most important nodes are usually where the score changes sharply, a threat appears, or an advantage disappears.

Sachess Editorial Team · 2026-06-08 · 3 sources
Open Sachess Analysis

Highlights

  • Use score changes to locate blunders and questionable moves.
  • Compare the played move with engine candidates to find steadier choices.
  • Classify missed tactics, greed, slow tempo, and other error patterns.
  • Useful for reviewing real games and checking your own analysis lines.
01

Load the full history or a FEN with moves so the page can replay the position before and after each move.

02

Watch where the engine score changes the most and mark those nodes for priority review.

03

Compare the played move with engine candidates and decide whether the mistake came from tactics, structure, or tempo.

04

Save the conclusion as an error label such as missed check, greedy capture, weak king, or slow transition.

FAQ

How do I know whether a move is a blunder
If the score gets clearly worse and there is a concrete better candidate move, it is worth reviewing as a blunder.
Is blunder checking only about score
No. Score is only the entry point; candidate moves, forcing lines, and position structure must support the judgment.
How many mistakes should I check per game
Start with the two or three biggest turning points. More than that can dilute attention.
Can it check opening mistakes
Yes, but opening checks should use both cloud book and engine because some common moves come from practical experience.

Sources

Sachess analysis page Pikafish project Pikafish knowledge wiki

Related Pages

AI Analysis Score Guide Review Workflow Cloud vs Engine