Loethor / Loethor/ruce

Implement check

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

movement generation
Dominant language
Rust
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

When the king is in check, not all the moves are allowed: you must execute a move that removes the check.
These moves can be:

  • Moving the king out of danger
  • Putting a piece in between the king and the aggressor, blocking the check
  • Capturing the aggressor

Any other move is illegal and thus, it must not be included in the move generation from that turn. This affects the rest of the move generation.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by locating the move-generation logic and tracing how the engine handles a king in check. Done means generated moves are limited to moving the king, blocking the check, or capturing the aggressor, with other moves excluded.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
game-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.