OMGeeky/hcsalmon1-Chess-Engine-Test
1
0
Fork 0
mirror of https://github.com/OMGeeky/hcsalmon1-Chess-Engine-Test.git synced 2025-12-26 16:27:23 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Coding with Tom
2025-01-20 17:09:56 +00:00
committed by GitHub
parent a5952c3af1
commit 812485bd23
1 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -64,7 +64,15 @@ This is where the code extracted into functions and made clearer. However this a
I normally don't code this way. I extract functions and hate over nesting. I only did it here to maximize performance.
Another reason why I didn't extract functions and refactor is because you create the most amount of bugs imaginable with a project like this.
One small flaw in logic and you can break the entire thing:
-Did you change sides correctly?
-Should you use the WHITE_OCCUPANCIES or BLACK_OCCUPANCIES when searching for pins?
-Did you use WHITE_PAWN_ATTACKS to look for a black pawn check and BLACK_PAWN_ATTACKS to look for a white pawn check?
-Does en passant work?
-Does castling work correctly? Does the king go through check?
-Do pins work correctly? Was the king captured?
In the C# clean version folder I also added my debug perft. This is what you can use to debug any changed you make to make sure you don't have bugs.
With so much debugging you can find almost any bug you create while refactoring.