17 Nov 05
Originally posted by dmnelson84Game 1566651
I'm sorry! Wrong game number! 1566651. Watch it.
Definatly something weird happening at white move 13, says e2 to d1, which is illegal, if there was something there, if pawns could in fact move like that. Then on white move 14 the king is still in check, yet doesn't need to stop it??
- Joined
- 26 May 02
- Moves
- 72546
17 Nov 05
Originally posted by MarsIIYes, something very weird happened on move 13. White is in check but according to the PGN game notation he plays e2-d1, which is impossible. Perhaps the PGN file got corrupted in the RHP database. If an illegal move was actually made in the game then this could cause problems at a later point.
Game 1566651
Definatly something weird happening at white move 13, says e2 to d1, which is illegal, if there was something there, if pawns could in fact move like that. Then on white move 14 the king is still in check, yet doesn't need to stop it??
[Event "Open invite"]
[Site "http://www.timeforchess.com"]
[Date "2005.11.17"]
[Round "?"]
[White "dmnelson84"]
[Black "princessleah"]
[Result "*"]
[GameId "1566651"]
1. d4 d5 2. e3 Ng8f6 3. c4 Bc8e6 4. cxd5 Be6xd5 5. Ng1f3 Nb8c6 6. Bf1d3 Nc6b4
7. Bc1d2 Nb4xd3 8. Ke1f1 Bd5xf3 9. gxf3 Nd3xb2 10. Qd1b3 Qd8d5 11. Qb3xb2 O-O-O
12. Nb1c3 Qd5c4
13. e2d1 e6 14. Qb2b3 Qc4xb3 15. axb3 a6 16. Nc3a4 Nf6d5
17. e4 Nd5b4 18. Bd2xb4 Rd8xd4 19. Bb4d2 Bf8b4 20. Ra1a2 Rh8d8 21. d1e2 Bb4xd2
22. Rh1d1 b5 23. Na4c5 Bd2b4 24. Rd1xd4 Rd8xd4 25. Nc5xa6 Bb4d6 26. b4 Bd6xb4
27. Na6xb4 Rd4xb4 28. e2d3 *
17 Nov 05
just two days ago, I had a situation where my opponent moved a pawn to queening square, but it stayed as a pawn for a while. also, I didn't get the move-button. but after some time, the pawn turned into a queen, and after some more time (1h) I got my turn. other games functioned without a glitch during this.
while these weren't illegal moves, maybe these incidents are interconnected?
17 Nov 05
Originally posted by wormwoodYour issue is not related and is not an issue. The site regards moving a pawn to a promotion square and selecting the piece to promote to as two seperate moves.
just two days ago, I had a situation where my opponent moved a pawn to queening square, but it stayed as a pawn for a while. also, I didn't get the move-button. but after some time, the pawn turned into a queen, and after some more time (1h) I got my turn. other games functioned without a glitch during this.
while these weren't illegal moves, maybe these incidents are interconnected?
Your opponent moved the pawn to the promotion square but did not immediately choose which piece to promote to. Once he did this you can move. Yes, you can time out an opponent who neglects to select which piece and exceeds his timebank.
17 Nov 05
Originally posted by tmetzlerThe new code didn't affect the board or any features of the moving page only the My Games page.
Can we ASSume that somebody has PM'd Russ about this issue. It seems to be a fairly serious.
If I was to guess, it might have something to do with the new code build he just implemented.
--tmetzler
- Joined
- 03 Sep 03
- Moves
- 87628
17 Nov 05
Originally posted by XanthosNZWell if you had ever done any real programming/engineering in a RAD environment; you would understand that, quite often changes made to one component may introduce bugs into other interrelated components.
The new code didn't affect the board or any features of the moving page only the My Games page.
And having tracked down MANY bugs made by myself and other programmers I can tell you this:
When something works correctly for a LONG time; then something is changed (ie: new build rolled out) and a bug shows up. The majority of the time that bug is related to the new code/build/change.
--tmetzler
17 Nov 05
Originally posted by tmetzlerI assumed that the bug in question actually occured before the new code rollout considering the number of moves made after it occured.
Well if you had ever done any real programming/engineering in a RAD environment; you would understand that, quite often changes made to one component may introduce bugs into other interrelated components.
And having tracked down MANY bugs made by myself and other programmers I can tell you this:
When something works correctly for a LONG time; then s ...[text shortened]... ws up. The majority of the time that bug is related to the new code/build/change.
--tmetzler