sdraught

i think the universe will end before i fix these bugs

• Added Tests for various different functions not 100% test coverage tho
• Implemented movement for pawn’s this is what took the majority of time
  my head was about to explode when implementing enpassant
• Added a simple board visualizer so my life becomes a bit easier

I am seeing like 14hrs of work and the only shit i did was add pawn movement and tests god dammit i spent some hrs trying to implement the sliding pieces too but i just couldn’t get that shit to work. I’ll try again and post a devlog over here soon

Okk so a lot has happened so because the idiot i am i accidentally deleted the implementation for the movement of the rook i was working on for 5 hours. A lot of the code that i made is gone now

I also started working on the gui but realized it was probably a good idea to stablize the engine part first and then work on the gui. What i have worked on the gui is on the github for the project.

Dont bully me for the gui plzz it took me lot’s of time to even make this

HOLY SHIT THERES A FUCK TON OF BUGS.

Anyways spent 2 hours fixing all the bugs in the setpos function and finished it up. I think i am done with this now. So im gonna start working on the movement of pieces next.

Maybe i can create a function called checklegality. This function will take the piece and the square that is being moved to and check if that piece can move to that square or not but to do that ill also need a function to extract the piece and square from the given chess notation like “Qf3”

I worked on the Setpos and s2s functions today. The Setpos function takes a fen string as a argument and sets the values of blackQueen, blackKing, castle, enpassant squares,etc.

s2s function is a function which takes any square in the chess board in the form of ‘e3’ or ‘e4’ and returns the bit board associated with the square on success
returns either ENGINE_INVALID_SQUARE or ENGINE_UNKWN_ERR on faliure

uhh idk what to add in the attachment so here is a cat