vpassos wrote:I think Chesscube should change things to stop the time when someone disconnects. I don't think give win to other player is fair in most of cases.
To the case of people using disconnection to avoid losing games it could be adjourned for a time (couple of minutes, hours) with a chance to resume when the oponent get online. After that time, if the player who got disconnected doesn't resume the game, the other one can clain win.
Most users play blitz or bullet chess and do not want to have to wait more minutes or hours to resolve a game. A disconnected user has time remaining OR 2 minutes to reconnect, which should be fine for most users. I think users just get annoyed with having to remember what they were thinking about the game a couple hours later - so it is generally much better to resolve the game then and there.
vpassos wrote:Other important thing about time is the lag taking your game time. When you got short on time it gets most annoying. The server should be able to deliver the move with the correct time, without discount on the time the lag takes to show it. Other servers have it, and it really makes the game more fair.
timestamp for moves, as other servers do. We also, however, have an upper threshold of lag allowance
(about 2 seconds) - this is more than suitable for most users and again prevents annoyance - why play someone a bullet game when they are lagging 5 seconds a move? For example, for 60 moves in what was meant to be a bullet game, instead of finishing in a maximum of 2 minutes (60 seconds each) the game can last 7+ minutes if we let a bad lagger play without consequence. If you are lagging badly, you should consider a slower time control in which the time deductions do not have that much influence on the game outcome.
The features we develop - as with 2 minute disconnect loss or lag penalties - are designed for the benefit of most users in the community. Yes, there will be some users - frequent disconnectors or bad laggers - we are adversely affected by this, but we cannot please everyone
Bug/feature status: Working as specified - we have no plans on changing existing functionality