You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed a small difference between lichess.org and the mobile app (v0.8.17) when premoving pieces. I play using drag & drop on both mobile and browser.
On lichess.org
On the website, I can make a premove. While the premove is active, I can pick up another piece to be ready to move it. Effectively, I've set up a premove and then prepared:
For the move after the premove (if the premove is played)
For an alternative move (if the premove is not played, e.g., a premoved capture cannot be played)
On Mobile
I tried to replicate the same on the mobile app. I set up a premove. When I grab a new piece to be ready for when the premove is resolved, the premove gets canceled.
To recap, on mobile, I cannot grab a new piece until the premove is resolved; otherwise, it gets canceled. This does not occur on the browser.
I think this difference might be negligible in most situations but could become advantageous for players using the browser in time scramble situations.
The text was updated successfully, but these errors were encountered:
I noticed a small difference between lichess.org and the mobile app (v0.8.17) when premoving pieces. I play using drag & drop on both mobile and browser.
On lichess.org
On the website, I can make a premove. While the premove is active, I can pick up another piece to be ready to move it. Effectively, I've set up a premove and then prepared:
On Mobile
I tried to replicate the same on the mobile app. I set up a premove. When I grab a new piece to be ready for when the premove is resolved, the premove gets canceled.
To recap, on mobile, I cannot grab a new piece until the premove is resolved; otherwise, it gets canceled. This does not occur on the browser.
I think this difference might be negligible in most situations but could become advantageous for players using the browser in time scramble situations.
The text was updated successfully, but these errors were encountered: