lichess-org/lila

Board editor: possibly disable 960 Castling in standard

Open

#12,926 opened on May 29, 2023

View on GitHubContributor guide
 (8 comments) (0 reactions) (0 assignees)Scala (2,661 forks)batch import
good first issue

Repository metrics

Stars
 (18,196 stars)
PR merge metrics
 (Avg merge 2d 18h) (151 merged PRs in 30d)

Description

Exact URL of where the bug happened

https://lichess.org/analysis/r5k1/1pp1qb1p/1p1r1p2/2n1pPp1/4P3/P2P1NP1/1PR1Q1BP/1R4K1_b_q_-_0_1?color=black

Steps to reproduce the bug

  1. Set up the position with white to move.
  2. Turn on Analysis
  3. The illegal queen-side castling recommendation will display (see screenshot) after a short time.
  4. I am then able to castle (illegally) on the queen's side.

image

What did you expect to happen?

I did not expect to be able to castle !!

What happened instead?

See screenshot - a suggested move is to castle long: image

Operating system

Windows 10 and Android

Browser and version (or alternate access method)

Vivaldi (Windows 10) and Chrome (Android)

Additional information

No response

Contributor guide

Research direction
Investigate the board editor logic for castling validation in standard chess. Locate the code that handles castling suggestions and ensure it correctly checks king and rook positions and move legality according to standard chess rules.
Tech stack
scala
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70