Originally posted by huckleberryhound
look, i can understand how this could be used when the position is hopeless, and there is only one way to proceed, but the site cant be programmed to identify this.
This is an over simplified example of my point.
My point about "if a=x let b=y" is that when a game begins, i could play e4 for example. Then preload the next two moves by guessing t ...[text shortened]... he has to make a move manually.
change for change's sake is not always the right option.
Yeah nice going talking about Queen's Gambit after 1. e4.
So wait, a player has the possibility to be able to leave the game for 9 days assuming that 1) he knows exactly which opening his opponent will play (possible if they've played before), 2) The opponent waits as long as possible between opening moves, 3) The opponent doesn't preload his opening moves too.
I mean if you play 1. e4 and preload 'if e5 then Nf3 and then if Nc6 then Bc4' based on the fact that opponent always plays the open game then your opponent could quite easily play e5 and load 'if Nf3 then Nc6 and then if Bc4 then Bc5' knowing that you always play the Italian Game. All they would need to do is look at your previous games. If they are too lazy to do so then that's their problem. Why should we cater to the lazy ones? If they did so then the first player would get back the game very quickly with him to play. It would be a godsend for times when I've had 20 or more games start up at once (large group tournaments or leagues). Do you know how tedious it is playing the same move twenty times?
This would in theory allow people who vary their openings to counter players looking at their past games to work out what they will play. Of course those players already enjoy that advantage as players can't book up on the relevant openings beforehand.
You claim that players who use the premove interface to their advantage will have an advantage over those who don't. But surely that is their prerogative. Database use is allowed here, those that choose not to use them (for whatever reason) are putting themselves at a disadvantage verses those who do. Should we ban database use by the same logic?
Change for Change's sake is not the right option however keeping the status quo because it's familiar isn't either.