GNOME Bugzilla – Bug 427114
Pawn makes en Passant move
Last modified: 2018-04-24 16:52:12 UTC
Please describe the problem: A black pawn eats a white pawn located right from it, but then moves diagonally as it should. I'm running the game on Ubuntu 7.04 Steps to reproduce: From the AI Information log: xboard depth 4 Chess Adjusting HashSize to 1024 slots Search to a depth of 4 force b2b4 go 1. b2b4 1. ... e7e5 My move is: e7e5 force c2c3 go 2. c2c3 2. ... g8f6 My move is: g8f6 force a2a4 go 3. a2a4 3. ... d7d5 My move is: d7d5 force a4a5 go 4. a4a5 4. ... c8f5 My move is: c8f5 force d2d3 go 5. d2d3 5. ... d5d4 My move is: d5d4 force e2e4 go 6. e2e4 6. ... d4e3 My move is: d4e3 Actual results: Expected results: Does this happen every time? Yes. Other information: I saved the game and this is what the saved game file contains: [Event "Človek versus GNU Chess"] [Site "?"] [Date "????.??.??"] [Round "?"] [White "White"] [Black "GNU Chess"] [Result "*"] [BlackAI "GNU Chess"] [BlackLevel "normal"] 1. b4 e5 2. c3 Nf6 3. a4 d5 4. a5 Bf5 5. d3 d4 6. e4 e3 *
Never mind. I just read the rules and it's supposed to be that way. Sorry.
Now worries, thanks for taking the time to make the report. When I first wrote glhChess I had to be told about that rule too!
*** Bug 452646 has been marked as a duplicate of this bug. ***
These players are seeing the "en passant" rule: http://en.wikipedia.org/wiki/En_passant
*** Bug 530875 has been marked as a duplicate of this bug. ***
*** Bug 545987 has been marked as a duplicate of this bug. ***
*** Bug 568720 has been marked as a duplicate of this bug. ***
*** Bug 789235 has been marked as a duplicate of this bug. ***
*** Bug 787970 has been marked as a duplicate of this bug. ***
*** Bug 779928 has been marked as a duplicate of this bug. ***
*** Bug 638440 has been marked as a duplicate of this bug. ***
*** Bug 623648 has been marked as a duplicate of this bug. ***
*** Bug 687170 has been marked as a duplicate of this bug. ***
*** Bug 765868 has been marked as a duplicate of this bug. ***
*** Bug 789942 has been marked as a duplicate of this bug. ***
*** Bug 795495 has been marked as a duplicate of this bug. ***
Pushed changes to make this more understandable to users in bug #485246.