| 1 |
[quote] But then you can't balance teams by the "Everything" elo. Thats the wrong way.
|
1 |
[quote] But then you can't balance teams by the "Everything" elo. Thats the wrong way.
|
| 2 |
Like @TheSponge said. [/quote]
|
2 |
Like @TheSponge said. [/quote]
|
| 3 |
I think Sponge actually said the contrary: that one shouldn't include 1v1 data in teams elo calculations.
|
3 |
I think Sponge actually said the contrary: that one shouldn't include 1v1 data in teams elo calculations.
|
| 4 |
\n
|
4 |
\n
|
| 5 |
[quote]Well, it's not worth even trying until it has an official Licho seal of approval[/quote]
|
5 |
[quote]Well, it's not worth even trying until it has an official Licho seal of approval[/quote]
|
| 6 |
Teams
elo
vs
1v1
elo
has
already
been
split,
previously
there
was
just
one
ladder.
I
would
consider
inclusion
of
1v1
data
in
everything-elo
a
bug.
|
6 |
Teams
elo
vs
1v1
elo
has
already
been
split,
previously
there
was
just
one
ladder.
I
would
consider
inclusion
of
1v1
data
in
everything-elo
a
bug,
especially
since
it
currently
[url=http://zero-k.
info/Ladders]lies[/url]*
about
being
"teamgame
elo".
|
|
|
7 |
\n
|
|
|
8 |
(* See "Top 50 team players" - that's a lie because it includes 1v1 data).
|
| 7 |
\n
|
9 |
\n
|
| 8 |
Bugs
don't
require
any
explicit
authorization
to
be
fixed
(
unless
authored
in
some
way
that
makes
them
more
hideous)
.
|
10 |
Bugs
don't
require
any
explicit
authorization
to
be
fixed.
|
Team vs 1v1 Elo