You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, while playing a long run correspondence game of Wildebeest Chess as Black versus shogi, I found out a critical bug that will certainly have to be fixed urgently. Also, it will not be too hard to fix with this issue sooner.
It is impossible to castle in Wildebeest Chess playing as Black with King from f10 to j10.
Playing from demo page, I had checked out this issue from quite a different few positions.
You might also want to check out if it is possible to reproduce this same issue from your side before working upon it in order to fix it.
Checking out from demo page is a good idea, not to interrupt with the seriously ongoing played game with shogi.
Although it is possible to castle by moving king to other squares playing as Black and all squares have no problems playing as White.
I am not sure whether there might be other variants of chess with the similar problem whenever the king is allowed to be chosen where to move to from among more than one square while castling.
I understand that your implementation uses king to move to the adjacent square while castling by clicking upon the rook and the king is not allowed to move to the farthest square originally occupied upon by the rook while castling.
I will certainly report similar problems in the future if I encounter with them in the other variants of chess.
Playing more games will help me to reveal such problems.
I wonder if no one has encountered with this problem yet, in order to not report it over hereby at all.
Probably that they might not know about Github website page, over hereby at all.
Playing for fun or revealing of bug issues - error fixes.
The text was updated successfully, but these errors were encountered:
raman22feb1988
changed the title
(Critical) Wildebeest Chess: Castling as Black - King f10 to j10.
(Major) Wildebeest Chess: Castling as Black - King f10 to j10.
Nov 2, 2017
Today, while playing a long run correspondence game of Wildebeest Chess as Black versus shogi, I found out a critical bug that will certainly have to be fixed urgently. Also, it will not be too hard to fix with this issue sooner.
It is impossible to castle in Wildebeest Chess playing as Black with King from f10 to j10.
Playing from demo page, I had checked out this issue from quite a different few positions.
You might also want to check out if it is possible to reproduce this same issue from your side before working upon it in order to fix it.
Checking out from demo page is a good idea, not to interrupt with the seriously ongoing played game with shogi.
Although it is possible to castle by moving king to other squares playing as Black and all squares have no problems playing as White.
I am not sure whether there might be other variants of chess with the similar problem whenever the king is allowed to be chosen where to move to from among more than one square while castling.
I understand that your implementation uses king to move to the adjacent square while castling by clicking upon the rook and the king is not allowed to move to the farthest square originally occupied upon by the rook while castling.
I will certainly report similar problems in the future if I encounter with them in the other variants of chess.
Playing more games will help me to reveal such problems.
I wonder if no one has encountered with this problem yet, in order to not report it over hereby at all.
Probably that they might not know about Github website page, over hereby at all.
Playing for fun or revealing of bug issues - error fixes.
The text was updated successfully, but these errors were encountered: