Confirm moves against bots!

Sort:
Maroni-Edgardo

Can the team add the the “Confirm Moves” option while playing bots? I know it’s available while online against other users on the mobile app, or on the website. Why can’t this feature be added while playing against bots? Telling me that I could play with different star ratings isn’t an answer to my question, neither is using a different method of moving my pieces. I have lost count of how many times I’ve been practicing or trying to beat a bot with a great endgame only to screw up because I accidentally touched the screen.

Yosyp00

I'd desperately need this too.

DoomSwitched

Exactly, I don't want to play with take backs, and I also don't want to glich my rook one square instead of across the board.

KestrelPi

I see topics about this going back three years, and it feels like it would be straightforward to implement given it already exists for the other modes. It would be a massive quality of life fix for a lot of people like me who use bots to practice but want the games to work similar to matches against a person, where I always confirm moves.
I don't mind turning on undo moves when I'm playing a coaching bot and getting feedback on my plays, but when it's the bots on this site I'm trying to stretch myself and punch a little above my weight with no take backs.

FatLittleDanny
This is truly the biggest gripe that I have with the app, and I’d be grateful if it was fixed. I have problems with hand mobility, so I’m constantly making unintended moves when I play bots on my phone. I get that you can enable take backs, but then you’re not really playing unassisted because now you’ve seen how the bot would respond to the recalled move. Plus, you don’t earn 3 ‘crowns’.
SacrifycedStoat
Please add this!!

I made a forum on other problems with the app, but this is a problem with the site!
KestrelPi

Revisiting my post from a few days ago, I think it's fair to say that I was, in my frustration, a little hasty in suggesting that it should be 'straightforward to implement' - it's true that I think that it's definitely worthwhile add in terms of a quality of life feature - easily worth the effort in my estimation. But also speaking from experience as someone who works in support for developers, it's also true that it's changes are nearly always a little more complicated than they might appear at first glance, and it's always a balancing act deciding what features to focus on.
I have reason to think they've heard our pleas, and hopefully they'll get to this. The comment a couple of posts above that it could also be considered an accessibility feature is also a great point, in my opinion.

FatLittleDanny
KestrelPi, I work in web development and I appreciate and agree with your view that fixing, testing, and deploying changes is usually less straightforward than you’d hope or expect. It would be reassuring if the chess.com team could commit to fitting this into their roadmap. I haven’t been able to find a current roadmap, but I know this is a feature that has been brought up quite a bit over the years, so hoping this makes the cut for 2025!🤞
Maroni-Edgardo

https://www.chess.com/forum/view/site-feedback/confirm-moves-against-bots?newCommentCount=1&page=1#comment-110083859

I'm not a computer science major but I have studied computer technology. This required some knowledge of coding and HTML. If you have a function to confirms moves, whether it is through JavaScript or any other language; it can be easily copied and pasted in the right locations. Add the button to confirm moves, and pass it off to mobile app development to complete their end of the program to ensure it works with all platforms. Test and done... Please don't make it sound difficult because it isn't.

KestrelPi

I'm not implying that it's a nightmare to implement - a lot of the bones are already in place, so that makes it easier, and it's not a particularly complicated feature inherently. But there's still stuff to think about, probably a bunch of stuff that wouldn't occur to you or me. All I'm really saying is trust me, as someone who works daily with developers and regularly sees comments like "this'll be easy to do, why isn't this done already" that 90% of the time that just isn't really true and there's something that makes it more complex that might not seem obvious. And even in the best case scenario where it's not difficult at all, actually doing it and testing it and adding the feature still takes a bit of time, so they still might be weighing it against tasks that they might consider higher priority on the roadmap. This is why I retract my suggestion that it ought to be straightforward, because, while I doubt it's highly complex, I'm not on the team and I don't know all the things they have to consider.