sann0638 wrote:Ah yes, the gremlins got fixed a couple of months ago - it was in the newsletter!

(noted: the Media position grants an extraordinary skill to shame the ignorant

Moderator: TFF Mods
sann0638 wrote:Ah yes, the gremlins got fixed a couple of months ago - it was in the newsletter!
Warpstone wrote: 2) Archive and shutter the current ranking system. The DB itself is not robust enough to handle problems like variant-rankings. To sort or delete Streetbowl, Beach Bowl, Deathbowl, Spacebowl (I kid on this one, but one day you know it's going to happen), you need meta-data that accounts for non-standard features. It's also profoundly pointless to have a system based purely on frequency of play as a large component of the scores themselves.
Build a new system based on:
* recording tournament meta-data. It will give us the abilty to filter based on common variations as well as other common rules factors such as custom stars/tables, game effects, pitches, etc. It's a pointless excercise to identify pure strains of Streetbowl let alone Blood Bowl, so just record variations and expose these options as filterable form that the individual users can use to satisfy their preferred criteria.
* make the default ranking based on performance over one calender year. You can still access lifetime stats or stats for a specified time period using filters, but turn the default view into one that reflects current and active players.
* introduce a decay factor on lifetime scores. If you don't play Skaven for 3 years, your lifetime ranking for that race shrinks by a factor of K (5% or even 15 points) until you reach starting ELO. Of course, your highest ever ranking will be recorded as well ("kids, I used to be the #1 Goblin player of all time...").
* integrate tournament management functionality in the backend reporting system. Kill two birds with one stone by making TOs only need to record data once! There's no reason why I can't input round 2's results directly into a web interface and then have the server spit back a round 3 swiss fixture list.
Most TOs reinvent the wheel for their events in order to accommodate concepts that have arbitrary variations (i.e. bonus points of different amounts). That's trivial to deal with if we're account for at the start of a new ranking system. Further, it allows us to record a more comprehensive story of what happened at the tournament (i.e. who scored the most TD, CAS, etc. is an easy tally when you're recording the entire tourny data set anyway).
* Regarding the programming, I know at least one of the NAF coders and he's an extremely competent guy. I sincerely think that he, I or a team of volunteers could collaborate to make the above rebuild happen. The problem though is direction. We're not getting it even we offer our time. You can't keep putting lipstick on a pig and that's about all you can do with the current infrastructure. You need Pippy and/or Lycos to make the call that current code is insufficient and spec out a more robust replacement.
Isn't that the crux of the discussion?robsoma wrote:Why be a member of an organisation if you a) do not like the gift that you receive for joining and b) do not attend tournaments? There is nothing that says you must be a member of the naf to be able to play bloodbowl?