dfxh

My feedback

  1. 323 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    dfxh commented  · 

    We have exactly the same problem. We want to use challonge to live-document sports events who use some other scheems of seeding. The winner bracket can be manually rearranged. However the Losers/Hope Bracket is fixed.
    However I propose a more general scheme:
    Add the feature to challonge to generally define the seedings in brackets (an "external" numbering of players and matches), not as a default but as an OPTION. This would just need an intermediate absract layer and ANYTHING can be achieved.

    dfxh supported this idea  · 
    An error occurred while saving the comment
    dfxh commented  · 

    Seeding is also a big issue for me.
    However I think it has to be adressed in general to enable all kinds of neccessities.
    So maybe it can be pre-organized somehow for the developers to draw their conclusions.

    A) we should differ between static seeding and dynamic seeding.
    - with static seeding I mean there is only the first draw: all matches and ways are set.
    - "dynamic seeding": after each round, or elimination round there can/will be a new drawing. This can again depend on certain criteria, such as divide (put them on the most distant branches) the strongest players or players which are locally more close or distant. With this you can try to "enforce" stronger endgames and reduce the risk that weak players end in endgames by lucky draws. (if you want that)

    B) RULES and Criteria to seed.
    B1) Initial static seed and dynamic seeds
    I think it will be hard or impossible to provide "all/any" criteria. Maybe it will be a start to consider each player/team with "attributes". Ideally a "real" value. I think without restricting generality we could call this "strenght". The seeding algorithm can then have the option (or multiple options) to put the most strongest players as distant as possible. And that for every round with a new draw, depending of who wins and looses. (Something like the chess ELO-number) could be a critera. Other criteras could be "vicinity" of players. You probably do not want to have players of one team fight against each other in the beginning, but allow them all/both to reach the final.

    B2) double elimination. Also here modified seeds for the loosers round would be a valuable addition.

    B3) The "strenght" number could change during the game. (such as the premention ELO number). even if all players at the beginning will start with the same value, the performance of the guys in the "loosers" round could "rankup" or "rankdown" the "strength" number in the winnersround. This can help to put the stronger guys on more distant branches and avoid the strong clashes in the early rounds and spare them for true finals. It also would help to equilibrate the chances in the loosers round.

  2. 16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    dfxh commented  · 

    We have exactly the same problem. We want to use challonge to live-document sports events who use some other scheems of seeding. The winner bracket can be manually rearranged. However the Losers/Hope Bracket is fixed.
    However I propose a more general scheme:
    Add the feature to challonge to generally define the seedings in brackets (and "external" numbering of players and matches). This would just need an intermediate absract layer and ANYTHING can be achieved.

  3. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    dfxh shared this idea  · 

Feedback and Knowledge Base