20 Jan 04
Originally posted by tejoThis is good.I just started a couple of clan games against your clan.I play for Veggies BTW.It is performance graph that is the big indicator of a mis-match.Someone could be on way to top twenty and can't play for months.After his rating dropped from time out lost games he comes back.He starts climbing up again.
A small idea:
Your profile shows how many games you played, won, lost and your rating. Why not your highest rating including when that was, because a year ago it was much harder to reach 1800 than it is now, and why not show the highest position. I love statistics.🙄
Sander
22 Jan 04
Originally posted by missleadFirst of all, I think the performance graph is a great idea, and it has been implemented well. Aside from what the previous posters mention, I only propose a small chang that is probably easy to add:
This is good.I just started a couple of clan games against your clan.I play for Veggies BTW.It is performance graph that is the big indicator of a mis-match.Someone could be on way to top twenty and can't play for months.After his rating dropped from time out lost games he comes back.He starts climbing up again.
When you mouse over a line in the performance graph, it tells you the rating of the player at that time, and the opponents rating, but it might be nice to show what the outcome of the game was, and how it was won (resign, timeout, mate, etc.) That way it might become obvious if someone had a huge slump that it was due to a bunch of timeouts.
Just my two cents,
greenphreak
30 Jan 04
Originally posted by thireAdding time per move would be OUTSTANDING! I came to the forums to suggest exactly this. Cumulative average time per move, not just the time per move on each game, would make this still better. It says far more about players than sometimes misleading Move Frequency profile information. It also covers eveyrone, not just those who write profiles. If our very talented programmers feel really creative they can add something like average timeouts over 30 minutes and drop these periods when in computing a Move Frequency when active.
perhaps it's interesting to calculate the average time that the player takes for a move and the average time his opponents do (in all games against him). with that I can easily decide weather he moves fast or slow.
th