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.

Author: Sachess Editorial Team · Updated: 2026-06-22 · 3 Sources

Open Sachess

Home

Analyze Position

AI Analysis

Score Guide

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.

Steps

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

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

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

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

Details

What counts as a missed tactic, blunder, or questionable move

A missed tactic usually means a forcing resource was overlooked: check, capture, pin, or continuous threat. A blunder is more severe and often causes a clear evaluation drop after one move. A questionable move may not lose immediately, but it makes the position harder or structurally worse.

When checking with an engine, do not look only at the sign of the score. The key signal is the size of the swing and the gap between candidate moves. If the played move is far from the best line and the continuation is concrete, the node deserves separate review.

Missed tactics usually involve forcing resources.
Blunders often come with a clear score drop or direct tactical loss.
Questionable moves may not lose at once but reduce future position quality.

How to turn results into training

Knowing that one move was bad is not enough. Give the mistake a precise label: missed opponent check, captured before calculating counterplay, failed to keep initiative, or ignored back-rank weakness. The clearer the label, the easier it is to notice next time.

Review only the two or three most important mistake nodes from a game. Export those nodes as FEN and practice similar positions later. Over time, that is more useful than skimming the whole game.

Prioritize the two or three most important errors in each game.
Write specific error labels for later review.
Saved FEN nodes can become a personal blunder training set.

Common Pitfalls

Pitfall 1: Looking only at the final losing move

The real blunder often appears before the final collapse, so check the turning point.

Pitfall 2: Treating every score swing as a mistake

Some swings come from deeper search, so compare candidates and lines before judging.

Glossary

Missed tactic

A forcing resource for either side that was not seen.

Blunder

A move that clearly worsens the position and changes the result trend.

Examples

Calculation miss

Capturing before seeing the opponent’s continuous checks can make the score collapse at that node.

Training example

Save similar missed-tactic nodes and drill checks and forcing threats first.

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