r/ComputerChess • • 11h ago

Looking for chess engines

2 Upvotes

Hi,

I'm have an Android app and looking for different engines that I could integrate into it.

I'd prefer engines written in C#, but I'm open to other languages and willing to explore them as well.


r/ComputerChess • • 5h ago

[Beta] I built a chess app that finds your mistakes and missed chances and lets AI explain them. Looking for beta testers!

Thumbnail
reddit.com
1 Upvotes

r/ComputerChess • • 15h ago

I spent months building a free chess app with its own neural engine. It grades every move you play and explains why in plain English. Looking for feedback.

Thumbnail reddit.com
1 Upvotes

r/ComputerChess • • 12h ago

I built a free game review site on Stockfish 19 that labels every move from Brilliant to Blunder. Feedback on the classification welcome

0 Upvotes

I've been building **MoveLens**, a free game review site, and I'd like feedback from people who know engines.

**Try it:** https://sanjaymarathi-movelens.hf.space (no account, no ads, no daily limit)

Paste a PGN or import a game by Chess.com or Lichess username. Stockfish 19 analyses every position and each move gets one of 11 labels, with a coach comment, the better move as an arrow, an eval graph and accuracy for both players. You can also play your own moves on the board at any point and get an instant verdict, retry a mistake to find the better move, or show the top 3 engine lines.

**How the labels work**

- Every score is turned into a winning chance: `win% = 50 + 50 * (2 / (1 + e^(-0.00368 * cp)) - 1)`. A move's quality is the winning chance it gives away compared with the engine's best move.

- Excellent: loses under 2%. Good: under 5%. Inaccuracy: 5–10%. Mistake: 10–20%. Blunder: 20% or more.

- **Great:** the best move, and every alternative is at least 10% worse (the second MultiPV line is enough to check this).

- **Brilliant:** the best move, leaving 2+ pawns of material to be taken, when you weren't already winning and aren't worse afterwards.

- **Miss:** your opponent just erred and your move gives back 10% or more.

- Book moves come from 3,800 named openings, and accuracy uses the published Lichess formula.

**Depths:** Fast (the default) is depth 12 with at most 0.15 s per position, so a typical game is reviewed in about 10–15 seconds on the free server. Deep is depth 20 with at most 1.5 s per position.

No site publishes its exact thresholds, so I'd especially like opinions on the Brilliant and Great rules, and on games where you think a label is clearly wrong.

It's open source (MIT): https://github.com/SanjayMarathi/MoveLens


r/ComputerChess • • 19h ago

Engines tell you a move was bad. What would you want a coach to tell you instead?

0 Upvotes

Something I’ve noticed with club players I know: after a game they run it through an engine, see “−2.3, best was Nd5”, nod, and make the same kind of mistake the next week. The number is right, but it doesn’t teach anything.

A good human coach does something different. They say “your knight has no good square, give it one,” or “you pushed that pawn and left d5 for his knight,” or “this ending is a draw because your bishop doesn’t control the queening square.”

So I’ve been building a free coach that tries to do that. It’s my own project. It’s free, with no ads, no account and no app to install: it runs in the browser. You play a game against a bot, and after each move it comments on the idea: development, threats you missed, weak squares, pawn breaks, plans, and endings like Lucena and Philidor. An engine checks every comment, but the engine isn’t what talks to you. You can also paste a PGN of your own game and have it reviewed move by move.

https://caissahub.com/coach

What I’d really like from this sub:

When you review your games, what do you wish the engine told you that it doesn’t?

If you try it, where does it say something wrong, obvious or unhelpful? Stronger players will catch things I can’t.

Thanks, and I’m happy to answer questions.