(*** This bug was imported into bugs.kde.org ***) Package: kbackgammon Version: KDE 2.2.0 Beta1 Severity: normal Installed from: Unspecified Linux Compiler: Not Specified OS: Linux OS/Compiler notes: Not Specified If in the middle of a turn the player has no legal move (e.g. on a roll of 2 and 6 the player can move the 6 but not the 2) the game does not recognize this and endlessly prompts for a move. The "Done moving" button is inoperative. The only recourse is to cancel the game and start over. (Submitted via bugs.kde.org)
On Wednesday 01 August 2001 11:30 am you wrote: > Package: kbackgammon > Version: KDE 2.2.0 Beta1 > Severity: normal > Installed from: Unspecified Linux > Compiler: Not Specified > OS: Linux > OS/Compiler notes: Not Specified > > If in the middle of a turn the player has no legal move (e.g. on a roll > of 2 and 6 the player can move the 6 but not the 2) the game does not > recognize this and endlessly prompts for a move. The "Done moving" button > is inoperative. The only recourse is to cancel the game and start over. > > (Submitted via bugs.kde.org) Could you please tell me which engine you are using? -- Cheers Jens
Jens Hoefkens wrote: > > If in the middle of a turn the player has no legal move (e.g. on a roll > > of 2 and 6 the player can move the 6 but not the 2) the game does not > > recognize this and endlessly prompts for a move. The "Done moving" button > > is inoperative. The only recourse is to cancel the game and start over. > > > > (Submitted via bugs.kde.org) > > Could you please tell me which engine you are using? Open Board. I haven't yet used the Online with FIBS engine so I can't say whether the problem is there too. ____________________________________________________________________ Public safety can always be had at the price / Patrick Wrigley / of civil liberties but the safety never / eirehound1@home.com / lasts and the liberties seldom come back. /_____________________/
Hello Jens I'm using kbackgammon 2.5.0 with KDE 3.0.3 - and have seen this problem in= =20 older versions of kbackgammon too - the problem appears also with FIBS. As far as I can observe it happens especially when *conditions to remove*= =20 pieces from board are given and player can only remove 1 piece because the= =20 other is blocked by opposite pieces. I have seen this in endgames *only*- there is another strange effect in tha= t=20 situation -- I can better explain with an image: 654321 X-X-O- X-X-O- X rolls 4 and 4 -- can remove only two pieces 4-off 4-off But kbg does not recognize there are only 2 pieces to move instead it is= =20 possible to remove 2 pieces from 4 and ONE pieces from 6(!) and it removes= =20 one of that too. After that nothing more can be done than disconnect=20 reconnect and resume (at least it does recognize that something illegal=20 happened :) *Before* removing illegal 6-off it is possible to refresh (or undo) and move manually by typing "4 off 4 off" and everything is fine (that is my=20 workaround because most people don't understand why I want to reconnect an= d=20 resume ;-)=20 After making the illegal move - there is no way to do anything (must reconn= ect=20 and resume and type in manually) Another more simple situation: 654321 X---XO X---XO X rolls 2 and 5 - and can only remove piece on 2 no possibility to move from 6 because 1 is blocked but kbg does not recognize it. Even after reconnect= =20 and resume it is only possible to move manually. I hope that helped. Thanks for kbackgammon! Nicolai P.S.: there are some more strange bugs in my new kbackgammon (but I guess t= his=20 is caused by using kde 3.0.3 from debian packets they didn't appear in kde3= .0=20 before - I compiled version 3.0 by myself and that worked well - so that=20 these bugs are in the deb-packets only I think -- where to report that?) --=20 PGP Key-ID 57567751
Encountered a similar bug, but not exactly. In the late section of my game, I'm at : 123456 oxxx-x oxxx-x xx xx x I rolled a double 5, an impossible move in this situation-- I can neither bear off nor move into the 1 slot. (This is not in the middle of a move as with the other bug) It failed to recognize that this was an invalid move and continued to request me to move 4 pieces. We ended our game. (Our first game together, alas, ended untimely. Or maybe it was better for all concerned:) But we would like to try again. Don't make us go to Playsite hell...:) In love, K.H. and K.S
Replaced eirehound1@home.com with null@kde.org due to bounces by reporter
Please confirm if this bug still exists in a recent version of KDE, such as 3.5.8.
As proposed on http://techbase.kde.org/Contribute/Bugsquad/Bugs_to_be_done this bug is marked as closed (no response within 30 days). If the problem still exists please re-open.