CAS tournament rules text (charnel version)

@zango asked me for a plaintext version of the rules for XCAPS21 – same as the usual rules, just rearranged a bit – so I thought it would be easier to post them on the forum. Given below in a text block, since Discourse can’t attach non-image files.

[Intro text, replace this as you like]
Welcome to our [SEASON] tournament! As before, this is an experimental format. This time around, we’ll be trying out [FORMAT]. [BRIEF FORMAT DESCRIPTION]

This is a Swiss tournament, with one match per week, plus a grace period if your match overruns.

I’m planning to post the first round on [DAY OF WEEK, DATE].

---

#### General rules

* Late signups will be accepted without penalty until the second set of pairings are made. Signups after that may occur, but will be given one loss for each full round / “tournament week” that has elapsed. Please submit your entry to the tourney, via PM to me or reply in this thread, in order to sign up!
* I am accepting volunteers to help judge the event. You could be an authorised judge!
* New pairings will be posted roughly every Monday. Matches that are not progressing may be given an adjudicated result. The “tournament week” is considered to be from one round of pairings posted to the next (so possibly more or less than an actual calendar week, depending on how prompt I am with the Monday postings / others are at finishing games).
* Matches are 1 game.
* The first player is responsible for creating the match thread.
* Tag @[YOURNAME] when a winner has been determined.
* CAS tournaments use a “three strikes” rule - any player who has three losses will be automatically dropped from the tournament. Players may also drop out at any time.
* There is no “top cut”: the last player standing wins the event. Thanks to the “three strikes” rule, the field should narrow towards the end, and culminate in some exciting final few matches.
* The default is to play all matches as play-by-post within the forum. A match may be played in an alternate format – in person, on an alternate platform, via snail-mail, whatever – by mutual agreement, until the field is reduced to four or fewer players.
* If any rulings are necessary, any single judge who is not participating in that match may make a ruling.
* Rulings are subject to appeal only if the judge making the ruling is wrong about the facts of the game (e.g., forgetting that a Building Inspector is in play, or that the Shrine of Forbidden Knowledge only makes Demons unstoppable by units), or the rules/FAQ as noted in [the rulebook](http://sirlin.net/rules) and/or [the Rulings thread](//forums.sirlingames.com/t/rules-questions-thread/146/).
* Please note [the forum-suggested post generation spreadsheet](https://forums.sirlingames.com/t/about-the-codex-play-by-forum-category/36/9), or one of the other format suggestions (like [this](https://forums.sirlingames.com/t/about-the-codex-play-by-forum-category/36/5) or [this](https://forums.sirlingames.com/t/about-the-codex-play-by-forum-category/36/2)) such that it includes hand, tech and worker decisions, either in a details + spoiler combo,

[details=like this,]
[spoiler]Here’s my hidden stuff![/spoiler]
[/details]

* or in a linked source that I can get to. This helps with judgements, adjudication, as well as spectators. For games involving me, you can send a private link to a different judge if you so choose.
* As with all PbF games, the honour system is in place: don’t peek at your opponent’s spoilers, just as you wouldn’t grab cards out of your opponent’s hand / deck / discard / worker pile and look at them in a real-life tournament!

#### Other details

[details=Details for Swiss pairings]

Each round, pairings will be assigned as follows.

If the number of players is odd, a bye, which counts as a win for future pairings, will be assigned to the player who:

1. Has had the fewest byes in the tournament (normally zero)
2. Has played against all other players, or so many of the other players that a bye is needed to avoid a re-match elsewhere in the tournament (probably won’t happen)
3. Has the most losses
4. Has played against the most remaining players (this helps minimize re-matches, while also keeping more players in the tournament longer)
5. Was picked randomly from among players tied for criteria #4

Each remaining player will be paired with another player who

1. They have been paired against the fewest times (normally zero)
2. Has the same number of losses (an unfinished match is not counted as a loss for players with fewer than two losses)
3. Is randomly selected

The player to go first in a match will be chosen as follows:

1. If one player has gone first fewer times in the tournament (not counting byes), that player goes first. Otherwise, the first player is decided randomly.
2. If a re-match can not be avoided, and the number of P1 assignments is equal between the re-matching players, P1 will be assigned to the player with fewer P1 plays within the head-to-head.

I reserve the option to hand-craft pairings and/or the bye if necessary, to minimize the number of re-matches. This manual manipulation will not result in someone getting a second bye, unless all players have had a bye.

Players that have not completed their previous matches will be handled as follows:

1. If a match between two players who each have two losses is not completed when the next round is paired, a proxy of “the winner of x vs y” will be paired for the next round in lieu of either participant.
2. When the delayed match completes, the proxy will be replaced by the actual winner. This proxy is considered to have the combined opponent and bye history of both players, for purposes of making pairings.
3. Deliberately delaying a match, in an attempt to affect your pairing for the next round, is considered cheating, and is punishable by being disqualified from the tournament. Yes, this is technically “not enforceable” but it’s still illegal. Don’t do it.
[/details]

[details=Details for unfinished match adjudication]

1. Matches where Player 1 has posted their 5th turn within a week will not be adjudicated until 3 days after (10 days after pairings, Thursday by default).
2. Matches where Player 1 has posted their 10th turn 11 days after pairings (Friday by default) will not be adjudicated until two weeks after pairings (Monday by default).
3. Matches subject to adjudication may have a win declared, by opinion of the judges, for
a) the player that is “going to win” (having clear hand / tech spoilers is helpful for determining this);
b) the player that is less responsible for delaying the game;
c) for no one, if prior arrangements were made, or the match result isn’t critical for making the next round of pairings, or if a “catch up” week is coming up.
4. Generally, I will be pretty generous about allowing for extra time, provided I’m given notice of absence. If you ‘re ghosting the tourney with no notice, however, don’t be surprised if you’re given forfeit losses!
[/details]

[details=Details for correcting game errors]

In the event of a game error, one of three fixes will be implemented:

1. If a unit, hero, or building took the wrong amount of damage, and changing it to the correct amount does not cause anything to leave play or not leave play, then the damage will be corrected.
2. If not enough gold was spent, and the excess was floated, the gold total will be corrected. If too much gold was spent, the excess will be refunded. The possibility of theft (red starter, Anarchy, or Law) does not impact this, as both players are responsible for maintaining the game state. An actually executed theft (or failure to steal after taking the appropriate action) forecloses this remedy.
3. The game will be backed up to the turn of the error. In this case, having the decisions / game state noted is important for re-constructing things. Any random events that are undone (e.g. drawing cards) must be re-randomized, regardless of the size or type of error. Normally the entire turn containing the error will be backed up and re-done, but if knowledge has been gained, or cards drawn, and the error occurred after the new information was gained, the judge must only back up to the point where new information was revealed.
4. If neither of the above apply, or if I think a backup cannot be performed, the game will be left as-is. (For example, an error occurs on Turn 2, and it is now Turn 4, both players have made decisions, reshuffled, etc. based on the incorrect game state).

Regardless of remedy, players should feel free to use any information disclosed by their opponent’s error in making gameplay choices: for example, an opponent’s tech choice revealed via a card illegally played and then returned to hand.

In the case of repeated errors, or errors where the game state cannot be recovered, a game loss may be given if the error was substantial.
[/details]

#### List of players participating:

1. ...

#### Authorised judges

1. ...

You can find the tracker spreadsheet [here](DUMMYLINK).
2 Likes

Heh I was gonna do this same post Charnel, ty! Linked it in the “resources” thread as well

1 Like

Here’s the CAWS21 or “Standard” format. Haven’t “variable-ized” the places where edits need to go but maybe will later:

## [Tournament] Codex Asynchronous Winter Swiss (CAWS) 2021

### Now taking signups!

Welcome everyone to our quarterly tournament for the Winter! As per tradition, this will be a standard tournament, no weird changes to format or rules. (we have done experimental things Spring / Fall and standard in Summer / Winter for the past several years)

This will be a swiss tournament, one match per week, with a grace period if your match doesn't finish on time. 

Tradition is to start these on the Solstice or Equinox although starting right before Christmas holiday is a challenge for me, so first pairings will be posted **Around 10am CST (UTC-6) on Monday, January 3rd, 2022**

[details="Nit picky details of how pairings will work"]

[spoiler]

Each round, pairings will be assigned as follows:

1. If a match between two players who each have two losses is not completed when the next round is paired, a proxy of “the winner of x vs y” will be paired for the next round in lieu of either participant.

2. When the delayed match completes, the proxy will be replaced by the actual winner.This proxy is considered to have the combined opponent and bye history of both players, for purposes of making pairings.

3. Deliberately delaying a match in an attempt to affect your pairing for the next round is considered Cheating, and is punishable by being disqualified from the tournament.Yes, this is technically “not enforceable” but it 's still illegal. Don’t do it.

If the number of players is odd, a bye(which counts as a win) will be assigned to the player who:

1. Has had the fewest byes in the tournament(normally zero)

2. Has played against all other players, or so many of the other players that a bye is needed to avoid a re - match elsewhere in the tournament(probably won 't happen)

3. Has the most losses

4. Has played against the fewest remaining players (this helps minimize re-matches, while also keeping more players in the tournament longer)

5. Was picked randomly from among players tied for criteria #4

Each player will be paired with another player who

1. They have been paired against the fewest times (normally zero)

2. Has the same number of losses

3. An unfinished match is not counted as a loss for players with fewer than two losses Is randomly selected

4. I reserve the option to hand-craft pairings and/or the bye if necessary to minimize the number of re-matches. This manual manipulation will not result in someone getting a second bye unless all players have had a bye.

[/spoiler]

[/details]

## General Rules / TLDR of How Things Work:

* The player who goes first in each round will be pre-determined

* If one player has gone first fewer times in the tournament (not counting BYEs), that player goes first, otherwise, the first player is decided randomly.

* If a re-match cannot be avoided and overall number of P1 assignments is equal between the re-matching players, P1 will be assigned to the player with fewer P1 plays within the head-to-head

* The first player is responsible for creating the game thread

* Tag[ @FrozenStorm](http://forums.sirlingames.com/u/frozenstorm) when a winner has been determined.

* CAS tournaments use a “three strikes” rule - any player who has three losses will be automatically dropped from the tournament. Players may also drop at any time.

* There is no “cut” - the last player standing wins the event. Thanks to the “three strikes” rule, the field should narrow towards the end, and culminate in an exciting final few matches.

* Matches are 1 game.

* The default will be to play all matches as play-by-post within the forum, but a match may be played in an alternate format (in person, on an alternate platform, via snail-mail, whatever) by mutual agreement, until the field is reduced to four or fewer players. (Make sure to let the TO know if you are playing outside PbF)

* I am accepting volunteers to help Judge the event (adjudicate disagreements on rules and correcting errors in play). You could be an authorized judge! @zhavier has been authorized

* If any rulings are necessary, any single Judge who is not participating in that match may make a ruling.

* Rulings are subject to appeal only if the judge making the ruling is wrong about the facts of the game (eg, forgetting that a[ Building Inspector](https://www.codexcarddb.com/card/building_inspector?partner=AUTOANY&affiliate_id=autocard&utm_campaign=affiliate&utm_source=autocard&utm_medium=card) is in play, or the[ Shrine of Forbidden Knowledge](https://www.codexcarddb.com/card/shrine_of_forbidden_knowledge?partner=AUTOANY&affiliate_id=autocard&utm_campaign=affiliate&utm_source=autocard&utm_medium=card) only makes Demons unstoppable by units) or the rules/FAQ as noted at[ sirlin.net/rules](http://sirlin.net/rules) and/or the Rulings thread.

* Please note[ the forum suggested post generation spreadsheet](https://forums.sirlingames.com/t/about-the-codex-play-by-forum-category/36/9), or one of the other format suggestions (like[ this](https://forums.sirlingames.com/t/about-the-codex-play-by-forum-category/36/5) or[ this](https://forums.sirlingames.com/t/about-the-codex-play-by-forum-category/36/2)) such that it include hand, tech and worker decisions, either in a details + spoiler combo … *(cont below)*

[details="Like this"]

[spoiler]

Here’s my hidden stuff

[/spoiler]

[/details]

* *(cont above)*… or in a linked source that I can get to. This helps with judgements, adjudication, as well as spectators. For games involving me, you can send a private link to a different judge if you so choose, but as with all PbF games, honor system is in place: don’t peek at your opponent’s spoilers, just as you wouldn’t grab cards out of your opponent’s hand / deck / discard / worker pile and look at them in a IRL tournament!

New pairings will be posted roughly every Monday. Matches that are not progressing may be given an adjudicated result. The “tournament week” is considered to be from one round of pairings posted to the next (so possibly more or less than an actual calendar week, depending on how prompt I am with the Monday postings / others are at finishing games).

[details="Details of unfinished match adjudication"]

[spoiler]

1. Matches where Player 1 has posted their 5th turn within a week will not be adjudicated until 3 days after(Thursday)

2. Matches where Player 1 has posted their 10th turn by that Friday(11 days after pairings) will not be adjudicated until Monday(the two week mark).

3. Matches subject to adjudication may have a Win declared for the player who is, in the opinion of the Judges,

a. “going to win” (having clear hand / tech spoilers is helpful for determining this)

b. Less responsible for the delay of game, OR

c. For no - one, if prior arrangements were made, or the match result isn 't critical for making the next round of pairings, or if a “catch up” week is coming up.

4. Generally I will be pretty generous about allowing for extra time, provided I’m given notice of absence. If you ‘re ghosting the tourney with no notice however, don’t be surprised if you're given forfeit losses!

[/spoiler]

[/details]

[details="Nit-picky details about correcting game errors"]

[spoiler]

In the event of a game error, one of three fixes will be implemented:

1. If a unit, hero, or building took the wrong amount of damage, and changing it to the correct amount does not cause anything to leave play or not leave play, then the damage will be corrected.

a. If not enough gold was spent, and the excess was floated, the gold total will be corrected. If too much gold was spent, the excess will be refunded. The possibility of theft (red starter, Anarchy, or Law) does not impact this, as both players are responsible for maintaining the game state.

b. An actually executed theft (or failure to steal after taking the appropriate action) forecloses this remedy.

2. The game will be backed up to the turn of the error. In this case, having the decisions / game state noted is important for re-constructing things. Any random events that are undone (eg, drawing cards) must be re-randomized, regardless of the size or type of error. Normally the entire turn containing the error will be backed up and re-done, but if knowledge has been gained, or cards drawn, and the error occurred after the new information was gained, the Judge must only back up to the point where new information was revealed.

3. If neither of the above apply, or if I feel a backup cannot be performed, the game will be left as-is. (For example, an error occurs on Turn 2, and it is now Turn 4, both players have made decisions, reshuffled, etc. based on the incorrect game state).

4. Regardless of remedy, players should feel free to use any information disclosed by their opponent’

s error in making gameplay choices.For example, an opponent 's tech choice revealed via a card illegally played and then returned to hand.

5. In the case of repeated errors, or errors where the gamestate cannot be recovered, a game loss may be given if the error was substantial.

[/spoiler]

[/details]

Late signups will be accepted without penalty until the second set of pairings are made. Signups after that may occur, but will be given one loss for each full round / “tournament week” that has elapsed. As stated above, please submit deck choices with your entry to the tourney, via PM to me or reply in this thread, in order to sign up!

List of players participating:

1. FrozenStorm [[Necro]/Balance/Truth](https://www.codexcarddb.com/deck/necromancy/balance/truth) :white_check_mark:
2. Bomber678 [[Anarchy]/Strength/Growth](https://www.codexcarddb.com/deck/anarchy/strength/growth) :white_check_mark: 
3. zango [[Balance]/Anarchy/Peace](https://www.codexcarddb.com/deck/balance/anarchy/peace) :white_check_mark:  
4. zhavier [[Anarchy]/Strength/Growth](https://www.codexcarddb.com/deck/anarchy/strength/growth) :white_check_mark:  
5. Dreamfire [[Necro]/Discipline/Present](https://www.codexcarddb.com/deck/necromancy/discipline/present) :white_check_mark: 
6. OffKilter [[Finesse]/Feral/Truth](https://www.codexcarddb.com/deck/finesse/feral/truth) :white_check_mark: 
7. NekoAtl [[Balance/Growth]/Strength](https://www.codexcarddb.com/deck/balance/growth/strength) :white_check_mark: 
8. charnel_mouse  [[Law]/Fire/Growth](https://www.codexcarddb.com/deck/TBD) :white_check_mark:  
9. Moby_Dick [[Demonology]/Peace/Finesse](https://www.codexcarddb.com/deck/demonology/peace/finesse) :white_check_mark:  
10. bansa [[Blood/Fire]/Feral](https://www.codexcarddb.com/deck/blood/fire/feral) :white_check_mark: 

You can find the current standings[ on the “Tracker” tab of CAWS21 spreadsheet!](https://docs.google.com/spreadsheets/d/1Qc1nq2MeuDuGJMG2CDckExTqD4ndEfdoXqcZv0_Aeug/edit?usp=sharing)
2 Likes