The solver for golf incorrectly reports some games as non-winnable that are in fact winnable. This seems to happen when two play paths result in the same configuration, but the solver only "accepts" one of the two paths. Drawing a card resets the solver state to winnable. Reproducible: Always Steps to Reproduce: 1. Start golf game 868257851 2. Play: JC QH (JD) (9S) 8H (5H) 6C 7H 8S (8C) (KD) (10S) JH (9C) (AD) 2H AC 2C (Parentheses indicate a card drawn from the talon.) Actual Results: At this point, the game is reported as winnable, and either AH 2D 3D (QC) or 3D 2D AH (QC) can be played to achieve (effectively) the same state. Playing AH causes the solver to indicate that the game is not winnable. Playing 2D 3D (QC) causes the solver to switch back to reporting that the game is winnable. Expected Results: Game is reported winnable after playing either the AH or 3D.
Created attachment 86513 [details] Screen shot of game in confused solver state
Likewise, KPat Grandfather game 264639045 reports not being winnable, though I managed to get it into a state where the status switched to "This game is winnable" after the second Redeal.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!