Today I received several emails from users reporting that the API started sending the opponent's incorrect castling move, causing the rook to disappear and the king to end up in the corner. Were there any such changes to the moves? Or could it be a server bug?
#[SOLVED] API bug?
celest pawn
bleak acorn
There was a recent change. See recent discussion in #lichess-bots
celest pawn
Thank you. This is very sad news. I'll have to re-release my app in the Apple Store and Google Play. It looks like I won't be able to do this for iOS, since I was supporting version 9.0 there.
celest pawn
api/board/game/stream/ That's what the server is reporting. {"type":"gameState","moves":"d2d4 d7d5 c2c4 d5c4 b1c3 g7g6 e2e3 f8g7 f1c4 e7e6 g1f3 g8e7 d1c2 e8h8 e1h1","wtime":876250,"btime":831130,"winc":0,"binc":0,"status":"started"} The King cannot move like this in standard chess, "e8h8" "e1h1".
celest pawn
{"id":"OnQE5fRL","variant":{"key":"standard","name":"Standard","short":"Std"},"speed":"rapid","perf":{"name":"Rapid"},"rated":false,"createdAt":1758868720056,"white":{"id":"greatgamer","name":"GreatGamer","title":null,"rating":2025,"provisional":true},"black":{"aiLevel":6},"initialFen":"startpos","clock":{"initial":900000,"increment":0},"type":"gameFull","state":{"type":"gameState","moves":"e2e4 e7e5 g1f3 f7f5 d2d3 f5e4 d3e4 g8f6 f1d3 f8c5 e1h1 d7d5","wtime":859240,"btime":884690,"winc":0,"binc":0,"status":"started"}}
Also "e1h1"
bleak acorn
Yes, that castling-form had been used elsewhere in the Lichess APIs for quite some time. And recently /api/board/game/stream and /api/bot/game/stream are using it too.
wide hull
This bug has completely broken my games playability that uses the lichess api. Are there plans on fixing it?
celest pawn
Fixed. Thanks.