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
My Serverlatenz is on 1ms. My Networkconnection with LAN Cable is 20ms. I work for an Internetprovider. I can check the connections as well. My Internet or ping on other games is stabile and good. Only on lichess, its depends form other player, often my time run out faster as from my oppnement. Sometimes my time run out allthough i make an premove. It feels like some player use lagswitcher tools for lichess. Can you say when the problem will be fixed?
I can understand that lichess will make the game for all players fair, but at the moment it seems unfair for player who want play chess without any lagswitchertools. This kind of players makt lichess plattform unattractive.
Expected behavior
please fix the problem
Device
Notebook
Operating system
Windows 11
App version
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
What happened?
lichess Bullet time is lagging
How can we reproduce the bug?
My Serverlatenz is on 1ms. My Networkconnection with LAN Cable is 20ms. I work for an Internetprovider. I can check the connections as well. My Internet or ping on other games is stabile and good. Only on lichess, its depends form other player, often my time run out faster as from my oppnement. Sometimes my time run out allthough i make an premove. It feels like some player use lagswitcher tools for lichess. Can you say when the problem will be fixed?
I can understand that lichess will make the game for all players fair, but at the moment it seems unfair for player who want play chess without any lagswitchertools. This kind of players makt lichess plattform unattractive.
Expected behavior
please fix the problem
Device
Notebook
Operating system
Windows 11
App version
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: