wikunia/ghess

Chess Engine in Go

ghess's Issues

Sacrificing material over a check

Hey,

in a game our engines played a few minutes ago, your engine went for a check, but sacrificed a piece for that.

I'm sure this will be hard to track down (it might have something to do with the QSearch depth or else), but maybe the position will help you!

Game: https://lichess.org/ECQ1WIJu/white#109
Move 55, Black plays Bf2+, which leads to the capture Rxf2. Black cannot capture the other bishop, as that would lead to a backrank mate.

EDIT:
Btw, I'm wondering: what time control/calculation do you use?

There is a bit of jitter in the move times, thus I'm not sure if you use a continous function to calculate the time ^^
Just curious

EDIT2: Nevermind, the peaks of the movetime chart show a continous function, the jitter comes from forced moves/simple decisions pruning a lot of time ^^

Move even if draw

Just make moves even if you think it's already a draw like for insufficient material