ChessMoveCalc is run by one independent developer, so replies usually take a few working days. We read everything, including short notes about typos.
What to include
| If you are writing about… | Please include |
|---|---|
| A bug in a tool | The page address, your device and browser, what you did, and what happened. For the solver or converter, paste the FEN or PGN you used. |
| A mistake in a guide | The article link and the sentence or diagram that is wrong. If you can, cite the rule or source (for example, the FIDE Laws of Chess). |
| A feature idea | What you were trying to do and how you do it today. |
| Privacy or data requests | What you are asking for (for example, information about cookies). We do not hold accounts, so we usually do not have personal data that identifies you. See the Privacy Policy. |
| Advertising or partnerships | Who you are and what you propose. We do not publish paid links or sponsored articles disguised as guides. |
Before you write
- "The engine move looks wrong." Check that the side to move and castling rights in your FEN are correct; these are the most common causes. Our guide how to use FEN to analyze positions shows how each field changes the legal moves.
- "My rating change doesn't match the site." Chess.com and Lichess use Glicko-based systems, not FIDE Elo, so their numbers will differ from our Elo calculator. See Chess.com vs Lichess vs FIDE ratings.
- "Can you help me during my online game?" No. Using engine help while playing is cheating. Our tools are for studying after the game.