Hello dear KMines team, when you change the size and/or mine count of the custom minefield, the highscore for that needs to be reset, because times achieved on different minefields are obviously not comparable. On the standard sizes highscore tables, the omission of the reset option is respectable as a design decision, but not on the custom minefield highscore table. Reproducible: Always Steps to Reproduce: 1. play custom game 2. change custom game parameters 3. play custom game Actual Results: highscores for both games get entered in the same table Expected Results: Either 1. reset the custom highscore table on each change in the custom game settings or 2. hold one highscore table for each height/width/mine count-combination. Note: A reset switch for the custom highscore table I would only consider a half-solution. (One could argue that one table for each height*width/mine count-combination or even mine density is enough, but I would argue against that.)
Thank you for reporting this bug 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 "CONFIRMED" 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!