Rapport • Board Game Arena

Alle rapporten

Schaken rapporten

#2852: "Castling Error"

fixed: Bug is opgelost

Waarover gaat dit rapport?

Schaken #13624156

Wat is er gebeurd? Selecteer uit het onderstaande

Regels: een spelregel werd niet gerespecteerd

Wat is er gebeurd? Selecteer uit het onderstaande

Regels: een spelregel werd niet gerespecteerd

Controleer of er al een rapport is over hetzelfde onderwerp

Zo ja, gelieve dan voor dit rapport te STEMMEN. Rapporten met de meeste stemmen krijgen VOORRANG!

#	Status	Votes	Game	Type	Title	Last update

Gedetailleerde beschrijving

Rapportgeschiedenis

22 Apr 2015 21:16 • Minion Number Q • Bug is nog niet gereproduceerd door de ontwikkelaars:

I was able to castle kingside, despite having moved the kingside rook in Chess960.
Additionally, I was not able to castle queenside.
At the turn where I castled, the interface only gave the options to move my king to d2, to c1 or to castle kingside and no option to castle queenside.

22 Apr 2015 23:45 • Een • Bug is opgelost:

There was indeed a typographical error in the code allowing castling with a rook having already moved. It's now fixed, thanks for your report.

22 Apr 2015 23:53 • Minion Number Q • Bug is opgelost:

Thanks. And what in Chess960 if the king starts on b1 or d1? Then there's only the option to move the king to c1 and not a separate option to castle. Similarly for the other side etc.

23 Apr 2015 09:05 • Een • Bug is opgelost:

In that case, there should be a separate option to castle in the status bar (on the right of "[propose draw]").

I checked on #941 (after moving the C1 rook away) and it's available. If you find an configuration when it's not there while it should, please give me the game number where it happened.

23 Apr 2015 18:19 • Minion Number Q • Bug is opgelost:

In table 13475644 it gives the option to "[castle g-side]", but not the other side.

24 Apr 2015 22:27 • Een • Bug is opgelost:

That's not a bug, you are white and your king is already on C1 (this would be its destination in a "c-side" castling). So in this configuration, there is indeed only one castling move available.

24 Apr 2015 23:46 • Minion Number Q • Bug is opgelost:

Ah fair enough. The way I understood castling in chess960 was that you would end up in the end position as castling normally. So it would be possible to have "Rook-move-only castling".

Could I suggest that at some point the castling rules for chess960 should be detailed on the game page? Especially as the FIDE rules linked to from the page would suggest castling is done differently.

Thanks for all the help.

26 Apr 2015 12:15 • Een • Bug is bevestigd door de ontwikkelaars:

Well, castling in chess 960 _was_ difficult figuring out.
My reference was the FIDE rules, but I might have strayed elsewhere on the web looking for examples.

And FIDE rules do indeed specify that you can make a rook only castling.
So it seems that you are right, I'll reopen this as a bug for further examination.

26 Apr 2015 15:28 • Minion Number Q • Bug is bevestigd door de ontwikkelaars:

Yeah the castling rules really are confusing in chess960. Thanks for looking into this.

27 Apr 2015 13:38 • Minion Number Q • Bug is bevestigd door de ontwikkelaars:

Another scenario I'm unsure about:
imgur.com/MnG3dxJ
In table 13704763 at move 17 I have option to castle g-side. Should I be able to as the square e1 is under attack? I couldn't see in the FIDE rules if castling should be allowed. Wikipedia would indicate that none of the squares between the king's start and end position can be under attack.

Sorry for potentially finding more work.

28 Apr 2015 22:50 • Een • Bug is bevestigd door de ontwikkelaars:

On the contrary, anything worth doing is worth doing well, so thank you for your help in identifying border cases.

I'll probably get some time to look a that tomorrow on the train.

29 Apr 2015 13:25 • Een • Bug is bevestigd door de ontwikkelaars:

For table 13704763, in fact all castling move are proposed even if not possible due to a square being currently under attack.

Then if that move is selected, a check is made for squares under attack on the path and the move is forbidden if there is any, with an appropriate explanatory message. I thought it was better that not showing the possibility.

So if you try to castle g-side you'll get an error message.

30 Apr 2015 10:11 • Een • Bug is bevestigd door de ontwikkelaars:

For castling with chess 960, I have made the change needed to allow for rook-move-only castling (king-move-only castling was already possible).

So everything should be in accordance with FIDE rules now. Thanks for your reports.

30 Apr 2015 10:11 • Een • Bug is opgelost:

Dit rapport aanvullen

Gelieve hier alle informatie toe te voegen die relevant is om deze bug te reproduceren of jouw suggestie te begrijpen:

Andere tafel ID / zet ID
Loste F5 het probleem op?
Kwam het probleem meerdere keren voor? Altijd? Willekeurig?
If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.

Annuleer Werk rapport bij

#2852: "Castling Error"

Waarover gaat dit rapport?

Wat is er gebeurd? Selecteer uit het onderstaande

Wat is er gebeurd? Selecteer uit het onderstaande

Controleer of er al een rapport is over hetzelfde onderwerp

Gedetailleerde beschrijving

Rapportgeschiedenis

Dit rapport aanvullen

Wijzig rapportstatus naar:

Help

Draag bij

Navigeren

Volg ons