domain

hey hey hey, new deevlogg!

So, there is not much visual progress made in these 6-7 hours.
However, I got the multiplayer setup started.
The first game mode is a 1v1, with 5 wordles each, with a maximum time of 2 minutes per word.
Users can now join the matchmaking queue, and it pairs random users.
Then, a SocketIO room is created between both, the game is stored in the database.
Now, i'll work on getting the UI for multioplauyer started, it will be copying the main one, however it'll be a bit different to make up for 5 words, and time limit.

fixed .lottie loader file bugs.
used a new library to make font-sizes responsive.
App is now responsive on all mobile phone sizes.

a lot of stuff!
bugfixes:
- fixed a bug where games did not load sometimes due to async issues. check that out on #4 on the github repo.

changes:
- changed the UI for the report card that comes after the review.
- added a moveList component, which shows a list of all the moves (not present in frontend v1!!)
- review is now divided into 2 pages, to make it less overwhelming.
- added chess.com profile pic retrieval
- made the chessboard's colors according to the website's theme

done with making the right side Review Panel, added two stages of Review. The first one now displays player info, accuracy and other game stats. the second one shows, list of moves, current move stat and openings. I am done with everything but the list of moves. this looks so much better than the previous version!!!

started working on a New UI Design --- designed by @Delana on Slack.
with this, I plan to get rid of the disgusting color scheme, the EW responsiveness and everything else which makes my eyes bleed. So far, i'm done with the new navbar, the new evalbar - chessboard and player nameplates. Beginning the work on the new right report card area.

fixed drawn games going undetected and games with checkmate failing to load.
not a lot of code, but took me time to find the place to change.

yaya! there was a bug where the game evaluation on the last move would be completely inaccurate. I FIXED IT!!
the event listener attached to stockfish was duping causing duped replies -> leading to inaccurate eval. this took time to debug 😭