Post by TopCat on Feb 20, 2008 3:54:28 GMT -5
Alright, here are my rules. If you have any problems with any, post them and I'll consider changes.
Now, since alliance is essentially a 1v1, I'm going to incorporate the Elo rating system to manage points during the ladder. I'm contemplating adding an "adjustment" to the EA formula that under-calculates expected wins due to Culdcept having random elements. I'd not expect people to win as often as they would in a game of pure skill, like chess or go, at any given player rating. This I can play around with myself in Mathematica so it's no concern of anyone else. Just stating at this point.
The following rules are debatable and open to criticism and suggestion. If you wish to offer advice or criticise a rule, please quote only the rule in question in your response.
I may also miss a rule or two that I intended to type, or may implement a change that is suggested. These additions will be highlighted in the rules until the next time I modify the post, at which point the highlighting will be removed.
As an early note, random pairing my be an option. I'm not going to use it right now since I want this first ladder to be a dry-run of the rules that get ironed out. Also, it presents a problem. Challenges would interfere with the pairings.
General Rules:
1) Teams consist of only two members. If at any point a team plays without its two founding members, the team forfeits their match. Two instances and the team is disqualified.
As this is a voluntary ladder tournament I don't see how anyone could benefit from ringers, so I'm trusting people not to use them or play under multiple names. This is to help protect against selective pairing to pad a team's rank.
2) If a team disbands or is disqualified, the members are allowed to start new teams and re-enter the ladder. They cannot recreate the team just eliminated, except as noted below. A new team will enter as new entrants and have thier score reset. A new team created will re-enter the ladder at the start of the next week.
A team can recreate itself, but is only eligible to re-enter the ladder at the start of the second week after elimination.
3) Matches will have standard rules that are issued before the ladder starts. Any match not utilizing the exact ruleset is not a valid ladder match.
This is another honor-system rule so I hope the fact that it's a voluntary ladder means that no one ruins it.
4) Teams must have a minimum of one ladder match per week and can have a maximum of three ladder matches per week. If a team plays less than one match during a week they will be warned (or penalized with losses as the differnece between the minimum and the number of games played, but not at this time). A second week without meeting the minimum and the team is disqualified. This is to help protect against rating protection by inactivity.
You are not allowed to re-play an opponent team during the same week in which you have concluded a match. Thus, you can play any team at most once per week. This is also to help limit the effects of selective pairing.
A team cannot play more than two ladder matches in one day. This is to prevent a team from intentionally avoiding challenges.
5) A match will consist of a "best of n games" format where n is an odd natural number. The first team to reach a number of wins greater than n/2 wins the match. A draw will count as a win for each team as this limit is concerned. As such, a draw must still be reported as a draw as it will effect rating differently than a win or loss when n = 1.
6) Mic communication between teams is not required, but is suggested in the lobby before a game begins. Before a game begins players may move to private chat.
7) If a player on a team intentionally drops a game, that team forfeits the game. Any remaining games in the match may still be played.
If a player desyncs during a game, the game is null and may be replayed immediately or any time during the week. A desync is categorized as when a player's connection becomes unstable and results in that player being in a game with all AI opponents. Since he can still communicate with the other players, a desync is easy to recognize. It can also be recognized by viewing the player's gamer status and seeing that they are still in a match and not on the dashboard or offline.
If, due to a desync, teams do not finish a match during that same week, they results of any other games they played in the match are discarded. As a corollary, each incomplete match is considered "in progress" and count towards a team's maximum games per week limit. If a team was losing a match that is incomplete and refuses to play again, the ladder coordinator should be notified.
Disc read errors and game freezes are prevelant and harder to distinguish from intentional drops. As such, when the reason a player drop from a game is vague, the game may be replayed once. If it happens again in the next game, that team forfeits the game.
8) Players may decide on a host beforehand. As a note, the host must have access to the map. If no player has access to the map then the teams may not play a ladder match until somebody does.
Challenge Rules:
1) Once per week, any team with a rating n points (TBD) below the starting rating may issue a challenge. They must challenge a team with a rating above the starting rating. This challenge must be issued in this thread as timing is sensitive. I understand that not everyone visits the site daily so a PM should also be sent to a challenged member so they may receive an e-mail to help notify them.
No team may be challenged more than twice per week.
2) A challenged team will accept challenges in the order they were issued. A challenged team must accept the challenge within two days or forfeit the match. Once the challenge is accepted, the match must be played during the week. If it is not, the team responsible for not playing forfeits.
If a challenge is incomplete, the challenged team may accept the next challenge. An incomplete challenge is subject to the normal challenge rules as concerns forfeiture.
3) In a challenge match, the special challenge K value will be used to affect rating. This value will be higher than any other K value. This has the benefit of increasing the challenging team's rating more than normal and decreasing the challenged team's rating more than normal if the challenging team wins. However, caution must be used as the opposite is also possible, thus, challenges should not be issued recklessly.
Ladder Rules:
Okay, so I hope to iron out rules within in the next week. I advise everyone to start getting their teams together. Please don't use this thread to announce your availability for a team. However, once you have decided on a team, please post it up in here with a team name and members.
As of right now, I'm anticipating starting this dry run on 9 March to give us time to get teams together and iron out certain details. New weeks will begin on Sundays thereafter. A 3 to 4 week run should be good for now.
With all of that being said, now feel free to voice comments, additions, suggestions, teams, and anything else relevant.
Oh, actually, I forgot about our new Calendar. Whenever people schedule a match I think it'd be prudent if they posted it up on the calendar so we all know who battled and when. This could help make it easier to keep track of who played and when.
Teams:
*TopCat [El Funk]
*Kuroi Kenshi [Mr Qoo]
Now, since alliance is essentially a 1v1, I'm going to incorporate the Elo rating system to manage points during the ladder. I'm contemplating adding an "adjustment" to the EA formula that under-calculates expected wins due to Culdcept having random elements. I'd not expect people to win as often as they would in a game of pure skill, like chess or go, at any given player rating. This I can play around with myself in Mathematica so it's no concern of anyone else. Just stating at this point.
The following rules are debatable and open to criticism and suggestion. If you wish to offer advice or criticise a rule, please quote only the rule in question in your response.
I may also miss a rule or two that I intended to type, or may implement a change that is suggested. These additions will be highlighted in the rules until the next time I modify the post, at which point the highlighting will be removed.
As an early note, random pairing my be an option. I'm not going to use it right now since I want this first ladder to be a dry-run of the rules that get ironed out. Also, it presents a problem. Challenges would interfere with the pairings.
General Rules:
1) Teams consist of only two members. If at any point a team plays without its two founding members, the team forfeits their match. Two instances and the team is disqualified.
As this is a voluntary ladder tournament I don't see how anyone could benefit from ringers, so I'm trusting people not to use them or play under multiple names. This is to help protect against selective pairing to pad a team's rank.
2) If a team disbands or is disqualified, the members are allowed to start new teams and re-enter the ladder. They cannot recreate the team just eliminated, except as noted below. A new team will enter as new entrants and have thier score reset. A new team created will re-enter the ladder at the start of the next week.
A team can recreate itself, but is only eligible to re-enter the ladder at the start of the second week after elimination.
3) Matches will have standard rules that are issued before the ladder starts. Any match not utilizing the exact ruleset is not a valid ladder match.
This is another honor-system rule so I hope the fact that it's a voluntary ladder means that no one ruins it.
4) Teams must have a minimum of one ladder match per week and can have a maximum of three ladder matches per week. If a team plays less than one match during a week they will be warned (or penalized with losses as the differnece between the minimum and the number of games played, but not at this time). A second week without meeting the minimum and the team is disqualified. This is to help protect against rating protection by inactivity.
You are not allowed to re-play an opponent team during the same week in which you have concluded a match. Thus, you can play any team at most once per week. This is also to help limit the effects of selective pairing.
A team cannot play more than two ladder matches in one day. This is to prevent a team from intentionally avoiding challenges.
5) A match will consist of a "best of n games" format where n is an odd natural number. The first team to reach a number of wins greater than n/2 wins the match. A draw will count as a win for each team as this limit is concerned. As such, a draw must still be reported as a draw as it will effect rating differently than a win or loss when n = 1.
6) Mic communication between teams is not required, but is suggested in the lobby before a game begins. Before a game begins players may move to private chat.
7) If a player on a team intentionally drops a game, that team forfeits the game. Any remaining games in the match may still be played.
If a player desyncs during a game, the game is null and may be replayed immediately or any time during the week. A desync is categorized as when a player's connection becomes unstable and results in that player being in a game with all AI opponents. Since he can still communicate with the other players, a desync is easy to recognize. It can also be recognized by viewing the player's gamer status and seeing that they are still in a match and not on the dashboard or offline.
If, due to a desync, teams do not finish a match during that same week, they results of any other games they played in the match are discarded. As a corollary, each incomplete match is considered "in progress" and count towards a team's maximum games per week limit. If a team was losing a match that is incomplete and refuses to play again, the ladder coordinator should be notified.
Disc read errors and game freezes are prevelant and harder to distinguish from intentional drops. As such, when the reason a player drop from a game is vague, the game may be replayed once. If it happens again in the next game, that team forfeits the game.
8) Players may decide on a host beforehand. As a note, the host must have access to the map. If no player has access to the map then the teams may not play a ladder match until somebody does.
Challenge Rules:
1) Once per week, any team with a rating n points (TBD) below the starting rating may issue a challenge. They must challenge a team with a rating above the starting rating. This challenge must be issued in this thread as timing is sensitive. I understand that not everyone visits the site daily so a PM should also be sent to a challenged member so they may receive an e-mail to help notify them.
No team may be challenged more than twice per week.
2) A challenged team will accept challenges in the order they were issued. A challenged team must accept the challenge within two days or forfeit the match. Once the challenge is accepted, the match must be played during the week. If it is not, the team responsible for not playing forfeits.
If a challenge is incomplete, the challenged team may accept the next challenge. An incomplete challenge is subject to the normal challenge rules as concerns forfeiture.
3) In a challenge match, the special challenge K value will be used to affect rating. This value will be higher than any other K value. This has the benefit of increasing the challenging team's rating more than normal and decreasing the challenged team's rating more than normal if the challenging team wins. However, caution must be used as the opposite is also possible, thus, challenges should not be issued recklessly.
Ladder Rules:
- 50 cards per book (No E-cards allowed)
- Alliance match set to standard alliance
- Best of 1 w/ 9000G magic limit or best of 3 with 6000G magic limit. (TBD)
- 70 round limit or 50 round limit, respectively
- 25s round time
- Random lands
- No sudden death
- Virtual Books are permitted
- Map rotation TBD (to be determined) shortly
Okay, so I hope to iron out rules within in the next week. I advise everyone to start getting their teams together. Please don't use this thread to announce your availability for a team. However, once you have decided on a team, please post it up in here with a team name and members.
As of right now, I'm anticipating starting this dry run on 9 March to give us time to get teams together and iron out certain details. New weeks will begin on Sundays thereafter. A 3 to 4 week run should be good for now.
With all of that being said, now feel free to voice comments, additions, suggestions, teams, and anything else relevant.
Oh, actually, I forgot about our new Calendar. Whenever people schedule a match I think it'd be prudent if they posted it up on the calendar so we all know who battled and when. This could help make it easier to keep track of who played and when.
Teams:
*TopCat [El Funk]
*Kuroi Kenshi [Mr Qoo]