Search "user:likeawizard"

Comments on https://lichess.org/@/likeawizard/blog/tofiks-130-is-looking-good/USywLbiT

Comments on https://lichess.org/@/likeawizard/blog/tofiks-120/uRImUXfl

@nutnun said in #32: > Thanks, I will consider looking at it, but it sounds like your rep check approach is pretty much the same as mine; I have my own position hashes but I don't see a point of restr…

@dboing what I mean by predictability is that an engine can search millions of nodes to come to a conclusion on a move to play. That means that when you are debugging your code there is often no easy …

@TheKnightIsDark you're absolutely right on the move ordering. I will double check everything tomorrow but it seems while refactoring the capScore constant got lost in the mvv--lva part. That's a big …

@nutnun said in #20: Pretty simple. Have a look: https://github.com/likeawizard/tofiks/blob/master/pkg/evaluation/evaluation.go#L99 I just save Zobrist hashes of all previous positions. Then I check i…

@nutnun said in #14: It might be that with very efficient bookkeeping of pins and attackers you can make an efficient legal move generator. And I know exactly what en-passant move you are talking abou…

@Toadofsky said in #7: > the importance of a robust test suite. I really need to do that myself as well. Would take away some of the pain I talked about this blog. I of course have a perft command whi…

@Toscani, I had mostly forgotten that the feature exists. Might have to look through it. Who knows maybe it will give some insights where work needs to be done. But my engine is not really producing a…

@Georgii_Surov_Suslik said in #3: > Dude, @likeawizard . > Your bot is insane! It so fast! It's not that fast. When it has to think it will play at normal speed. I your game the bot just blitzed out o…