-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exercise goes for 1 move too long #15320
Comments
Before I dig too much further, would this not be an issue in the database? I presume if it's an issue in Lila that it would apply to every other lesson but it only applies to this one, correct? Edit: the chapter ID is |
@danispringer do you know where the practice puzzle data is loaded from? I checked the database and couldn't find it there. |
@BSmick6 sorry! No clue… |
isnt it fine for a lesson to feature another theme besides overloading? after trading a rook for a rook and a pawn, material is more or less equal, and a beginner might look at the aftermath and wonder if the exchange was worth it. but the idea isnt that white hasnt just won a pawn, white also won the safety of the black king, as it is now vulnerable to Qxg7. so the puzzle shows overloading and winning a favourable position, not necessarily material. moreover this is the 5th lesson on overloading, so i also think its appropriate at this point to feature puzzles where the overloading theme shares the spotlight with other important concepts. |
Exact URL of where the bug happened
https://lichess.org/practice/basic-tactics/overloaded-pieces/o734CNqp/bqmdo5fb
Steps to reproduce the bug
the overload motif is complete after Rx Kx Qx. having to find Qxg7 makes no sense. and if that happens to be the only move that keeps the advantage, then the exercise is not a overload motif and should be replaced/removed.
What did you expect to happen?
n/a
What happened instead?
n/a
Operating system
macos
Browser and version (or alternate access method)
brave
Additional information
No response
The text was updated successfully, but these errors were encountered: