[ Help | Earliest Comments | Latest Comments ][ List All Subjects of Discussion | Create New Subject of Discussion ][ List Latest Comments Only For Pages | Games | Rated Pages | Rated Games | Subjects of Discussion ]Comments/Ratings for a Single Item Later ⇩Reverse Order⇧ Earlier Colossus. 10x10 chess with 4 Rooks, 4 Knights, 4 Bishops, 10 Pawns, 1 Queen and 1 King![All Comments] [Add Comment or Rating]Carlos Cetina wrote on 2019-07-06 UTCHi Greg, I could already make the move. Thank you very much! Greg Strong wrote on 2019-07-06 UTCHi Carlos, Can you try your move again? Hopefully I've fixed it. Thanks! Carlos Cetina wrote on 2019-06-20 UTCFergus: To help you spot the bug that is in our Colossus game here is part of the program: Syntax Error on line 673 658 MOVE: r i3-j3 659 postauto2 660 moveindex 146 661 MOVE: B h1-j3 662 postauto1 663 moveindex 147 664 MOVE: q g3-j3 665 postauto2 666 set posvar join "b" join fencode boardflags 667 if >= var #posvar 3 668 say Three Times Repetition! Drawn Game! 669 drawn 670 elseif sub stalemated #K 671 if sub checked #K 672 say Checkmate! Black has won! 673 won: else: say Stalemate! The game is drawn. 674 drawn 675 endif 676 elseif >= #nopvc 100 677 say Fifty Moves Without Moving a Pawn or Capturing! Game Drawn! 678 drawn 679 elseif sub checked #K 680 say Check! 681 endif 682 end I understand the problem is the two points after the "won" word. Carlos Cetina wrote on 2019-06-20 UTCThere is a bug that prevents to make 66... Qxj3# A message appears saying "Syntax Error on line 673 ..." Fergus Duniho wrote on 2019-03-06 UTCThat information was already there in the Notation section. I tweaked it a little to make it clearer. Greg Strong wrote on 2019-03-05 UTCAwesome, thanks for the quick fix! I figured it had to be related to the unusual way that castling with a single-space king move was triggered. I would also suggest updating the mini-rules shown on that page to indicate the king's castling options and how to trigger the single-space castle by moving the rook on top of the king. I would have thought that such a move was unlikely to ever come up in real play, but in this game I had definite reasons for wanting to castle that way. Fergus Duniho wrote on 2019-03-05 UTCThat was indeed the problem. You castled by moving your Rook to the King's space, which was done as a Rook move, but castling this way did not include any code for updating the variable storing the King's position. There was an add command for moving the King, but it needed to be followed by a set command that otherwise looked the same. I have now added the appropriate set commands, and you can now capture the Bishop with your Pawn. Greg Strong wrote on 2019-03-05 UTCI've found a bug with this preset. In this position: https://www.chessvariants.com/play/pbm/play.php?game=Colossus&log=mageofmaple-ChessShogi-2019-61-909&userid=mageofmaple I cannot take the bishop with my pawn becuase it says I would be moving into check. I assume it is because of the way I castled (the King only moving a single space.) I believe the position of the king didn't get updated, so it thinks his queen will be attacking my king if I make the capture. 8 comments displayedLater ⇩Reverse Order⇧ EarlierPermalink to the exact comments currently displayed.