If you like pointing and clicking, just set it to that, and don`t click the king then the rook, because logically speaking that would make you castle.
Can we PLEASE stop castling by clicking the rook?
Sort:
Yup happened to be many times now. Castling shouldn't be allowed by moving the rook. Sometimes you forget you already touched the king before trying to move your rook. Why make castling complicated when you can just move the king 2 squares to do it.
ChessicallyDisabled wrote:
That's correct, there's nothing like that in settings. If you happen to use Lichess however, in preferences (which is settings) under "Game behaviour" scroll to "Castling method" and click "Move king two squares" instead of "Move king onto rook". This will prevent castling in case you happen to either drag your king to the rook or click the king and then the rook.
I have also made the mistake of accidentally castling by clicking my king then rook. From ChessicallyDisabled's, it's clear that Lichess also thinks this is a problem worth solving and they even have a setting to choose the castling style. There is precedence.
It's also a common pattern in the game that clicking another piece allows you to "select" that piece to move, it works for any other piece except for the castling scenario. For example, you click a pawn and then a knight, the knight is now selected to move. You don't have to unselect the pawn by clicking the pawn again and then click the knight.
djconnel wrote:
This should solve it:
This doesn't solve it because what if I want to be able to click my pieces? I find that dragging pieces is less precise and potentially more error prone.
May 6, 2023
0
#47
Can we please add this setting, I've lost count of the number of games I've lost to this, it is the only circumstance in which clicking on your own piece will confirm a move and it's very easy to forget this under time pressure. And no, as others have explained multiple times, switching to "Drag only" is not a satisfactory solution, there are many reasons why somebody might prefer not to or would not be able to, including disability-related reasons. Simply unselecting the king before selecting your rook does in fact work, but as explained above this is easy to forget under time pressure especially since it is a scenario that comes up only every so often, and there's no good reason why players should have to keep this in mind at all times when a setting to disable this feature would allow everybody to have it work the way they prefer. As for how it affects 960 I don't see how this is an issue, if the option exists to allow castling by clicking king then rook then the UI could just force this option for 960
May 6, 2023
0
#48
introuble2 wrote:
Have lost many games like this, too. But as @baddogno said, it's how one castles in 960, so it's unlikely to change it; same platform. I was just wondering if techs could limit this kind of castling only by dragging K over R, and not just clicking. This would limit the move only to intended ones.
Accessibility issues I think
This is actually a horrible feature. I don't even know if anyone castles by touching their king and rook in the first place. Just moving the king is way faster and straight forward, it's almost like the feature is there to make you lose games unnecessarily. I've lost countless positions just because my board decided to be smart and do things I didn't ask for. It's totally annoying. I would've asked for the feature to be optional, but personally I think it should be removed entiirely. I don't think anyone ever complained of wanting to castle by touching their king and rook in the first place, and let's face it, every now and then one would run into a case where they want to move their king and then suddenly change their mind to move their rook instead, and when time is against you, you won't remember the castling feature at that point. Please remove this feature, it's annoying.
Jul 1, 2023
0
#51
Yep, just lost another game to this situation. You should be able to touch the rook after the king like any other piece. Just make the engine castle when you move the King 2 spaces. Dragging pieces leads to even more errors. Come on Chess.com. This should be an easy fix!
Jan 5, 2024
0
#52
this problem has recently been fixed by chess,com its not even possible to castle by clicking the rook.
I received a notification today that this method of castling will no longer work on chess.com
Hopefully this solves the problem
please bring it back its so annoying to castle now
Jan 5, 2024
0
#55
Vishal_504 wrote:
please bring it back its so annoying to castle now
You can still use the click method but now you click the king and the king's destination instead.
Martin_Stahl wrote:
Vishal_504 wrote:
please bring it back its so annoying to castle now
You can still use the click method but now you click the king and the king's destination instead.
it doesn't work is there a setting or something?
Jan 5, 2024
0
#57
There are settings about drag or click move but nothing specific to this change and the same they have always worked otherwise.
i had this problem when castling queenside
Jan 6, 2024
0
#59
squid wrote:
clicking the king and then rook will no longer castle
The change isn't rolled out to 100% of web users yet but should be early next week.
That`s why you just go to settings and fix the problem...