Chessconnect: a free chrome extension for electronic chessboards

Without a token. Tokens are just there for backwards compatibility. I.e. for users who already entered a working token. New users should just ignore this.

It's just a token gesture then? ;o)

I had an issue just now playing rapid on Lichess. My opponent long castled, and Chessconnect wanted me to move the king two squares while leaving the rook on the starting square. I ended up turning off the board and reconnecting, then the same thing happened when I long castled. Has anyone else encountered this?

@montagdude: Do you have the game ID or URL for me? Which chess board did you use?

Here is the game: https://lichess.org/JLK2xeWHPybk

I use a Chessnut Air.

Again, I am unable to recreate the problem. But I get the feeling that there is a problem with castling on lichess.

Since @stealthbook seems to be able to recreate it: is anybody else able to make Chessconnect stall on castling on lichess using stealthbook's recipe? (Post #1138)

I will take a look a little later today (working right now).

I will also try it with several bots to see if I can reproduce.

Just with Chessnut boards so far, or other boards as well? I have Chessnut, Pegasus, e-One, and a Chessup1.

I tried following stealthbook's recipe but was not able to reproduce the issue with my Chessnut Air. However, the issue in my game also had to do with long castling. (Never had an issue with short castling, but I haven't played in a few days, so it could be new, maybe.) I'll try to reproduce with a bot match later.

Thank you, @Rsava. DGT and Chessnut so far. But my guess is that the board is irrelevant as long as it has full piece recognition.

Queenside castling in Lichess is the problem I mentioned a few days ago.

I was able to reproduce the issue with a bot match. Just emailed you a log.

@joernupbde - thank you again for you brilliant work on Chessconnect. Just now, I published a video on my channel using the Chessnut GO to play unrated random games on Chess.com, through Chessconnect (Chrome + Windows 11). The experience was flawless for me.

Article: https://www.chess.com/blog/vitualis/chessnut-go-noob-vs-noob-unplugged-9-jaenisch-gambit-casual-chess-jazz

Thanks for sending me the log. I think I found the problem. I will release a fix as soon as possible. Thank you all for your patience and support!

I have submitted version 4.4.6 to the web store. It is now waiting for approval by Google. This should fix the long castling problem on lichess which I sadly introduced with version 4.4.3.

Also happened with the Pegasus, playing against Maia5 bot on Lichess. Black (Maia5) long castling. King move accepted, Rook move not accepted, flashing led rings. All fine on online board, however. Thanks for the "hotfix".

Thank you joernupbde. We are so lucky to have such a dedicated developer.

Ah, well, it happens ... you are doing fantastic job and service for the chess world.

4.4.6 is now being rolled out. It would be great, if someone could confirm that the problem has indeed been fixed.

I just tried it, and the issue is gone. Thanks for the super quick fix!

confirmed, i just opened the same position that i had on the old version from the bug report, and the issue is gone. thank you for a quick fix!