Lapor • Board Game Arena

Semua Laporan

Catur melaporkan

#2852: "Castling Error"

fixed: Bug telah dibaiki

Apakah laporan ini berkenaan?

Catur #13624156

Apakah yang berlaku? Sila pilih pilihan di bawah

Peraturan: sebuah peraturan permainan ini tidak dihormati

Apakah yang berlaku? Sila pilih pilihan di bawah

Peraturan: sebuah peraturan permainan ini tidak dihormati

Sila semak apakah sudah ada laporan mengenai subjek yang sama

Jika ya, sila nyatakan untuk laporan ini. Laporan dengan undian yang paling diberikan PRIORITI!

#	Status	Votes	Game	Type	Title	Last update

Penerangan yang terperinci

Laporan masa lalu

Apr 22 nd 2015 21:16 • Minion Number Q • Bug belum dihasilkan semula oleh pembanguna:

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.

Apr 22 nd 2015 23:45 • Een • Bug telah dibaiki:

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.

Apr 22 nd 2015 23:53 • Minion Number Q • Bug telah dibaiki:

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.

Apr 23 rd 2015 09:05 • Een • Bug telah dibaiki:

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.

Apr 23 rd 2015 18:19 • Minion Number Q • Bug telah dibaiki:

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

Apr 24 th 2015 22:27 • Een • Bug telah dibaiki:

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.

Apr 24 th 2015 23:46 • Minion Number Q • Bug telah dibaiki:

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.

Apr 26 th 2015 12:15 • Een • Bug disahkan oleh penerbit:

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.

Apr 26 th 2015 15:28 • Minion Number Q • Bug disahkan oleh penerbit:

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

Apr 27 th 2015 13:38 • Minion Number Q • Bug disahkan oleh penerbit:

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.

Apr 28 th 2015 22:50 • Een • Bug disahkan oleh penerbit:

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.

Apr 29 th 2015 13:25 • Een • Bug disahkan oleh penerbit:

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.

Apr 30 th 2015 10:11 • Een • Bug disahkan oleh penerbit:

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.

Apr 30 th 2015 10:11 • Een • Bug telah dibaiki:

Tambah sesuatu untuk laporan ini

Sila tambahkan di sini apa-apa yang kelihatan relevan untuk menghasilkan semula bug ini atau memahami cadangan anda:

ID meja yang lain / gerakkan ID
Adakah F5 meyelesaikan masalah ity?
Adapah masalah itu berlaku beberapa kali? Selalu? Sekali-sekala?
Sekiranya anda ada screenshot bug ini (amalan yang baik), anda boleh gunakan Imgur.com untuk muatnaik dan copy/paste pautan itu di sini.

Batal Kemaskinikan laporan

#2852: "Castling Error"

Apakah laporan ini berkenaan?

Apakah yang berlaku? Sila pilih pilihan di bawah

Apakah yang berlaku? Sila pilih pilihan di bawah

Sila semak apakah sudah ada laporan mengenai subjek yang sama

Penerangan yang terperinci

Laporan masa lalu

Tambah sesuatu untuk laporan ini

Tukar status laporan kepada:

Tolong

Menyumbang

Navigasi

Ikut kita