it has been mentioned in another thread, but there was hardly any discussion about the topic at all.
what do you guys think?
what does TFC think?

Afaik this is something that needs to be done by autohosts and Licho's autohost already does this, it's just a matter of getting optional support for autobalance in spads and lobby hosts.

Best way to get better matchmaking - don't use autohosts and have host that isn't intent on stacking.

Actually, Springie-ELO retrieving system has been implemented and tested in SPADS about 10 monhts ago. It's just disabled currently because I don't think using ELO indexed on player names would be effective in BA world, where players rename every day... As explained here, I'd rather use account IDs to index ELO. Maybe ELO is indexed on account IDs now, but I didn't get answer last time I asked.

elo doesnt really need that many games to adjust... also new names could have their k-value, like, tripled for the first 5 games, or something like that... or have it doubled until they lose a game

Elo used by springies adapts quickly due to changing weight factory we added.
Its still based on player name.

If you wish to improve the system, its open source!
http://code.google.com/p/summerspring/s ... e/springie web

Make ELO tracking mandatory, but use of it in autobalance optional. Base it on playerIDs. Give client-side support and display ELOs for each player in the lobby.

Already done in SpringDownloader.


Yes please.
Basing it on names is a bad idea imo.
I can't even change a tag without Springie forgetting me, and /stats treating me as newb with 0 games played...


I would very much like the Elo system integrated in all autohost. From my experience it works really well on Springie CA autohosts. On the other hand the rank based balance on Spads BA hosts is very unreliable and stacked games happen much more often.

Nobody cares about SpringDownloader.

But I guess I'm glad the API is there?

bump with inspiring content:

viewtopic.php?f=42&t=25385