Your premove doesn't work corrrectly, I premoved to TAKE the Queen, if the Queen moves from that position it should obviously not apply the premove.
Your premove doesn't work corrrectly, I premoved to TAKE the Queen, if the Queen moves from that position it should obviously not apply the premove.
It is not a bug; premoves are designed around moving pieces, not capturing them.
Suggestion: Disable takebacks and practise better movement accuracy.
It is not a bug; premoves are designed around moving pieces, not capturing them.
Suggestion: Disable takebacks and practise better movement accuracy.
@shadow1414 said ^
It is not a bug; premoves are designed around moving pieces, not capturing them.
Disable takebacks and practise better movement accuracy.
It's definitely a bug, if your premove involves clicking on the another piece it's obviously a CAPTURE premove, if that piece is no longer there it shouldn't apply the premove.
@shadow1414 said [^](/forum/redirect/post/gE84w3n3)
> It is not a bug; premoves are designed around moving pieces, not capturing them.
>
> Disable takebacks and practise better movement accuracy.
It's definitely a bug, if your premove involves clicking on the another piece it's obviously a CAPTURE premove, if that piece is no longer there it shouldn't apply the premove.
<Comment deleted by user>
@Viohl said ^
Your premove doesn't work corrrectly, I premoved to TAKE the Queen, if the Queen moves from that position it should obviously not apply the premove.
Ridiculous.
Where does this rule come from?
Lmao.
@Viohl said ^
Your premove doesn't work corrrectly, I premoved to TAKE the Queen, if the Queen moves from that position it should obviously not apply the premove.
Ridiculous.
Where does this rule come from?
Lmao.
I just disagree with that design DECISION (not chess rule)
In a real game of chess I can have the move lined-up in my head, if I see the Queen is moved I go for the Rook immediately instead.
You're describing online chess design decisions, not chess rules.
@Viohl said [^](/forum/redirect/post/8i2KuGLg)
> > Your premove doesn't work corrrectly, I premoved to TAKE the Queen, if the Queen moves from that position it should obviously not apply the premove.
>
> Ridiculous.
> Where does this rule come from?
> Lmao.
@Viohl said [^](/forum/redirect/post/8i2KuGLg)
> > Your premove doesn't work corrrectly, I premoved to TAKE the Queen, if the Queen moves from that position it should obviously not apply the premove.
>
> Ridiculous.
> Where does this rule come from?
> Lmao.
I just disagree with that design DECISION (not chess rule)
In a real game of chess I can have the move lined-up in my head, if I see the Queen is moved I go for the Rook immediately instead.
You're describing online chess design decisions, not chess rules.
The alternative design behaviour of /cancelling/ a pre-move just because a piece moved away from the target square would be even more annoying if it caused you to lose a tight game on time, which it surely would soon enough...
The alternative design behaviour of /cancelling/ a pre-move just because a piece moved away from the target square would be even more annoying if it caused you to lose a tight game on time, which it surely would soon enough...
There is no rule that involves premoves in chess as they don't exist over the board.
You premove to a square, not a piece. Your concept of premoves is flawed.
There is no rule that involves premoves in chess as they don't exist over the board.
You premove to a square, not a piece. Your concept of premoves is flawed.
@pcbpcb said ^
The alternative design behaviour of /cancelling/ a pre-move just because a piece moved away from the target square would be even more annoying if it caused you to lose a tight game on time, which it surely would soon enough...
They should give the user the choice on how that situation is handled, it's not a set in stone chess rule, it's some arbitrary design decision.
If captured premove is no longer available: cancel premove [] | move to empty square []
fixed.
@pcbpcb said [^](/forum/redirect/post/gKEm5J5d)
> The alternative design behaviour of /cancelling/ a pre-move just because a piece moved away from the target square would be even more annoying if it caused you to lose a tight game on time, which it surely would soon enough...
They should give the user the choice on how that situation is handled, it's not a set in stone chess rule, it's some arbitrary design decision.
If captured premove is no longer available: cancel premove [] | move to empty square []
fixed.
@Deadban said ^
There is no rule that involves premoves in chess as they don't exist over the board.
You premove to a square, not a piece. Your concept of premoves is flawed.
Well we're getting into the subtle nuances, online chess is a representation of physical chess. You absolutely think in your head "I'm taking the queen on my turn if it hasn't moved"
it's whatever, I came up with the solution that handles this arbitrary DESIGN decision:
If captured premove is no longer available: cancel premove [] | move to empty square []
@Deadban said [^](/forum/redirect/post/UN1qVfEG)
> There is no rule that involves premoves in chess as they don't exist over the board.
>
> You premove to a square, not a piece. Your concept of premoves is flawed.
Well we're getting into the subtle nuances, online chess is a representation of physical chess. You absolutely think in your head "I'm taking the queen on my turn if it hasn't moved"
it's whatever, I came up with the solution that handles this arbitrary DESIGN decision:
If captured premove is no longer available: cancel premove [] | move to empty square []
Premoves are a bet: if you guess right you make a move without losing time, if you guess wrong you may lose worsen your position.
You want too much.
Premoves are a bet: if you guess right you make a move without losing time, if you guess wrong you may lose worsen your position.
You want too much.