Closed GoogleCodeExporter closed 9 years ago
* Ranking system for counting CAS and TD's as points, in addition to W/D/L
points.
* The ranking system I said was "bad" has one good point: A bonus point for
loser
when losing by one TD. It was the points for win and draw that were too low
compared
to losing by one TD, which was bad. (W:4p, D:3p, L:1p, +1p for loosing by 1 TD.
IMO,
should have been W:6p, D:3p, L:0p, +1 for loosing by 1 TD. I wasn't commish for
that
league...As it was, coaches went for a safe draw instead of risking loosing a
point.)
The point of having different examples of ranking systems is that ppl can
(easily?)
meddle with the points to fit their league.
Original comment by blodae@gmail.com
on 16 Feb 2009 at 9:33
Yes, but TD and CAS are already available with the latest change to the RSs?
Yep, that is the point, but it's problematic making all team fields available
for
each tour's RS calculation since I suspect that this will slow obblm down a lot
-
I'll have to check if this is true. Which is sad since it leads to confusion
that not
all team fields are available for picking amongst when making new RSs.
Original comment by Nimda...@gmail.com
on 18 Feb 2009 at 3:39
I just listed the first one to have it in one place. It is implemented. (Thanks
Nicholas!)
Original comment by blodae@gmail.com
on 18 Feb 2009 at 4:10
Okey, from now on this issue-thread is dedicated to more special ranking
systems,
like RS includning field like "+1 point for loosing by 1 TD".
I've made a easy method via settings.php for adding RS in the future, which do
not
require fields like the one described above.
Daniel, if you have problems with having to copy/paste because of your special
field
(the one above), then add your RS to the repository code - I'm sure others will
use
that RS too.
Original comment by Nimda...@gmail.com
on 12 Mar 2009 at 5:55
Closing this one for the sake of tidying a little up. People will be likely to
make
new threads/issues anyway.
Original comment by Nimda...@gmail.com
on 6 Apr 2009 at 10:44
Original issue reported on code.google.com by
Nimda...@gmail.com
on 13 Feb 2009 at 12:53