Looking for structured feedback for my chess engine on C.

I wrote chess engine that played with stockfish and my engine survived until the endgame.

Engine searchs the best move using alpha beta pruning, based on Negamax.
Also, engine has transposition tables, killer moves, qsearch, ordering moves.

Evaluation functions evaluates material balance, uses PeSTO tables and divides games to midgame and endgame.

Engine supports uci protocol.

github: https://github.com/0sewter0/chess\_engine.git

reddit.com
u/Sewter0 — 10 days ago

Chess engine on C, looking for critic.

After implementing legal move generation in C, I verified it using standard perft positions up to depth 7. All node counts matched the reference values. This involved handling castling, en passant, promotions, checks, and pinned pieces correctly.

Right now, my engine can evaluate position and search the best move with algorithm alpha-beta pruning.

It’s my second big project on C, so I am waiting technical assistance if my code is wrong.

Should I make UCI protocol?
The Universal Chess Interface (UCI) protocol is an open, text-based communication standard created in November 2000 by Rudolf Huber and Stefan Meyer-Kahlen. It allows chess engines (like Stockfish) to talk to graphical user interfaces (GUIs like ChessBase or Lichess-compatible tools) without licensing fees.

reddit.com
u/Sewter0 — 17 days ago

Looking for feedback on my C interpreter project.

Hi everyone!

I’ve been learning C and built a small interpreter from scratch. It currently supports arithmetic expressions, variables, conditionals, user-functions, dynamic arrays, and few built-in functions.

I’m mainly looking for feedback on the code quality, architecture, parser design, and memory management. Any suggestions are welcome.
Github: https://github.com/0sewter0/Interpreter.git

(I am new in reddit, and I am from kazakhstan, so I am not speak english well)

reddit.com
u/Sewter0 — 23 days ago