lichess.org
Donate

Sideways catpures

Has anyone else on Lichess noticed that capturing a piece by moving diagonally forward with a pawn often fails, and instead just moves the pawn forward; loosing the game, unless the pawn is dropped in a (too) exact way? Seems to happen many times a day to me. Maybe instead of just highlighting the square where a piece can move to, Lichess should graphically mark the boundaries for move interpretation. And thus the corridor for sideways diagonal captures might look too small too be optimal. Maybe they could allow each player to choose those boundaries. Thus, for example, if I hit the *far* left edge of the square infront of a pawn, then my pawn would capture, not just slide forward by the side of the piece to its left, as is the way Lichess now handles that.
Treat yourself to a new mouse. If you click literally anywhere inside the squares (with a functioning mouse) you will never have this problem; clearly you're clicking in the wrong square. There's no software solution for this because it's not a software problem.
@Doofenshmirtz
Please read what I wrote *before* replying, because I just have to repaste it here: this is what I wanted:"Thus, for example, if I hit the *far* left edge of the square infront of a pawn, then my pawn would capture". You wrote on a different topic instead: "literally anywhere inside the squares" and "clearly you're clicking in the wrong square" but you have not thought about what square you mean, nor what square I said needed to be used. I am saying the square infront of the pawn, if clicked very far to the left or right edge, should also be used to determine a pawn capture. The way it is now; having to aim at the tiny triangle shaped area of the square to the left or right is too error prone, I thought. Can you now address that issue instead, please. I have used many different mouses, I do not believe this is related to mouse Brand attributes.
@erikbergren You have to click *inside* the square you're moving *from*, and then, afterwards, click *inside* the *destination* square. If you do this, you will feel the need to post about your problems in this regard the same number of times as everyone else does: precisely zero.

I have no idea what you mean when you describe a "tiny triangle shaped area", nor why you desire the ability to click on a different square to the one you wish to move your piece into. If you can legally move a pawn 1) forward a square, and 2) to the square in front and to the left of the current square to capture a piece, then why would anyone want the ability to click in the former square if they intend to actually move into the latter? Then you really would start to see posts in the forum about "I clicked here but it went there"! Why don't you just click in the squares you're moving between? Which problem would your suggestion solve?
"If you do this, you will feel the need to post about your problems in this regard the same number of times as everyone else does: precisely zero." "Treat yourself to a new mouse." That replier "Doofenshmirtz" talks just like american cops talk. I will not follow his demands, that's my right, at least on Lichess, if not against police. I communicate with people to help make our lives work better, not to tell them to address problems "Precisely zero" times, as he has demanded of me. How has humanity made so many mistakes that one now days can not even talk anywhere without being silenced by violence, or shouts of "do like everyone else does"? Who would ever even desire such a thing (or admit such a desire on a forum like this) except a source and cause of failure for our World? How can Lichess's interface be improved: I've made lots of suggestions for Lichess since 2013, and everytime all the replies were anger at me for posting them. Many have nevertheless been incorporated here (such as the 10 second warning before one's clock runs out, all repliers on that wrote me "what a terrible idea"and "that would be the most annoying thing", and so I left Lichess for several years until they incorporated that idea). If I could just write an interface for myself to use that would send moves to Lichess, then I could fix any problem I wanted, but maybe that is not allowed by anti-cheating algorithms here, does anyone know if that's allowed?
<Comment deleted by user>
@BerserkAsIfUWereMad
Thank you for that informative reply. I was going to repost that last sentence I wrote, but your answer covers it. I guess I might spend some time studying how to do those programming things. I tried the popular hover/keyboard method earlier this year, but if I write it myself then I'll be more at home with the environment.
A quick recap in case I'm missing something:

q: "Maybe instead of just highlighting the square where a piece can move to, Lichess should graphically mark the boundaries for move interpretation."

a: "...you click literally anywhere inside the squares..."

q: "The way it is now; having to aim at the tiny triangle shaped area of the square to the left or right is too error prone"

a: "I have no idea what you mean when you describe a "tiny triangle shaped area" and "You have to click *inside* the square you're moving *from*, and then, afterwards, click *inside* the *destination* square."

response: "That replier "Doofenshmirtz" talks just like american cops talk. I will not follow his demands"

LOL! Not really a demand - just a suggestion as to how to get the best out of this site. If you ignore the imaginary triangles (or perhaps your computer is broken) and just click inside the squares you won't have a problem.

btw: what's up with sending me this direct message:

----
This account spends all its time harassing posters, with false forcing statements like "do yourself a favor...", "do not post on lichess" "use only two square clicks piece moves"as though Lichess belongs to him and he is giving them a warning authorized by this website, and never giving reasons for those declarations. According to his activity profile he has been doing nearly only that this whole week, rather than chess. I would like such *only* destructive accounts removed from Lichess to improve it.
----

You didn't mention which account, so it looks like you're attempting to report me, but making a bit of a mess of it and sending it straight to me! How embarrassing! Perhaps Lichess should change the way the buttons work there too, huh? I didn't say any of those things, or even anything remotely like them (the third doesn't even make sense, and not being American I wouldn't spell favour that way); something anybody handling your complaint (assuming you managed to do that properly) would immediately be able to see. Not sure I'm that destructive - there seems to be a pretty clear pattern in how the emoticon/voting is going in this thread. Probably best to not waste anyone's time with lies and work instead on your chess?

Edit: Even after I posted the above you persist in sending me further unwanted, nonsensical direct messages containing lies, misquotes etc! Please stop.
@erikbergren Regarding the fifth post he was telling you how to move. If you are not going to do it correctly, don't do it wrong and complain.
@PravinNH2020
"don't do it wrong"?<-- out of place words by you. The goal is not to move the piece for your approval. Instead: the Lichess interface has two ways to move pieces, which you can choose between to move your pieces on the board: either "drag and drop" or "click move 'from' square, then click move 'to' square". In that first case your mouse and the piece you are dragging pass over (on diagonal moves) at least *three* squares since it is (essentially) impossible to pass exactly through the corner pixel of the squares (on pawn captures in particular, you must move over the square infront of the pawn (unless you take a long path around it or hit pixels of the square on the pawn's left or right) giving a risk of landing there). Also, since the piece is an extended object, the square it ends up on has to be interpreted by both the interface and the player. On top of that, internet transmission delays can cause the piece to drop mid-drag. Thus if I start to move a pawn roughly diagonally I would like my interface to always complete that goal automatically for me, it could sense early on the pixels I move over and thus know my goal of straight ahead or not. Then I will not loose pawn piece captures that I intended. The way Lichess does it now: if your angle doesn't slope enough, your pawn is just pushed forward, loosing a whole piece. When I want to move a pawn straight forward, I can easily aim the slide to about +/- 20 degrees. I will program all other angles to register a sideways capture, and so I will win more games (assuming I spend the time to study and complete such programming). Not sorry if you think that is "wrong to do" (unless you have some more deeper thought on that, or can at least explain your use of "wrong" a little more). I am never sorry for complaining, that is what progress often comes from, so I would like you to not order such things.

This topic has been archived and can no longer be replied to.