Closed GoogleCodeExporter closed 9 years ago
Well, this is because you actually should be using tournaments in each season.
So, for example:
Every year some national league (containing the entire pool of teams),
consisting of four divisions (say north, south, east and west) each have a
tournament to decided the winners of these divisions. These then compete in
some finals tournament in a separate division to find the winner of the season.
Now, next season/year you keep the league and division structure, but simply
create a second set of tournaments within the division representing the next
season. This way the season stats are contained within the tournaments, whilst
the inter-season stats for each division and entire league are contained as the
division and league stats. This is just one way you can use the node structure
of obblm. There are really no limits or no proper way of using them, but one
should be aware that stats accumulate in the division and league layers are
more and more tournaments are held. Regarding how you conferences module works
in this setup I don't know :-).
I hope I understood you correctly.
Original comment by Nimda...@gmail.com
on 3 Oct 2012 at 5:36
Bump...
Original comment by Nimda...@gmail.com
on 23 Dec 2012 at 3:21
Okay, so I decided to add this as an option. However, I found it is not
possible with the current way getPTS() is written.
In getPTS() there is no way to differentiate between match stats of regular
rounds and those of finals when calculating points. Therefore, the stats which
are used to calculate points upon (cas etc.) cannot be filtered for only those
of regular rounds.
If you very much miss this feature I suggest you implement it yourself, but
don't add it to the trunk yet - trying to make a stable/tested release
candidate for 0.95 now and will therefore not add it any time soon.
Original comment by Nimda...@gmail.com
on 23 Dec 2012 at 9:01
Original issue reported on code.google.com by
doublesk...@gmail.com
on 11 Jan 2012 at 2:03