Very insightful Tomi, very insightful.
New Draw UI Is Poorly Coded
Sort:
Of course, I don't know Chess.com's Codebase and can't provide a more specific solution.
B1ZMARK wrote:
yo when did i start following this dude
I added you over a year ago.
Great, thanks for sharing Tomi.
If you offer a draw and the game ends, the draw offer doesn't go away. We easily recreated this in a 10 second game as you can see above. Making the draw offers go away after the game ends is fairly simple in Java. Here's how to do it:
Identify the function that handles the logic for ending the game and handling draw offers. This function might be responsible for updating the game state, removing any pending draw offers, and displaying the appropriate message to the user.
Check the code for any potential bugs or errors that might prevent the function from working correctly. For example, there could be a syntax error or a logic error that causes the function to fail.
Test the function with different scenarios and inputs to ensure that it works correctly in all cases. This can include testing with different types of games, different game states, and different types of draw offers.
Use debugging tools and logs to track the execution of the function and identify any issues that might be causing the pending draw offers to remain on the screen.
Once the issue has been identified, make the necessary changes to the code to fix the problem. This might involve modifying the function itself or making changes to other parts of the code that interact with the function.