Tournament Rules - v1.3 → v1.4
18 added • 5 removed • 15 changed (759 unchanged hidden, expand any "↕" to view)
|
↕ 149 unchanged rules between start and 402.2.
|
|
| 402.2. |
Otherwise, deck construction is defined in the Core Rules. |
| 403. |
Sideboard |
| 403.1. |
In certain competitions, players may have a group of additional cards (outside of their starting configuration) called a sideboard. See 600 for more information on sideboards based on competition formats. |
| 403.10. |
If a game ends in a draw, neither player may sideboard for the following game. |
| 403.10. → 403.11. |
If a game restarts due to an in-game effect or due to corrective action by judges, the state of each player’s deck and sideboard must remain the same in the restarted game. |
| 403.2. |
Sideboard size and contents are dictated by the competition format. |
| 403.3. |
Limits on copies of named cards as defined by competition format apply to the combination of Main Deck and sideboard. |
|
↕ 5 unchanged rules between 403.3. and 403.6.
|
|
| 403.6. |
Players may count the cards in their opponents’ sideboards at any time. |
| 403.7. |
A player may look at their own sideboard at any time, but must keep it distinguishable from other cards. |
| 403.8. |
A player’s deck and sideboard must be returned to their registered states before the first game of the next match. |
| 403.9. |
If a match completely skips the first game due to a |
| 404. |
Match |
| 404.1. |
A match of Riftbound consists of a series of games that are played until one side has won a predetermined number of games. |
| 404.2. |
Most matches of Riftbound are “best of 3,” meaning the predetermined number of games to win is 2. |
|
↕ 5 unchanged rules between 404.2. and 405.2.
|
|
| 405.2. |
Players must arrive at their seats prior to the start of the round. |
| 406. |
Start of Game Procedure |
| 406.1. |
The setup process for a game of _Riftbound is de_fined in the Core Rules. See CR 110. Setup Process. Additionally: |
| 406.1.a. |
In competitions where sideboards are allowed, players may exchange cards from their main deck and their sideboard after each game of a match. See 403 for more information on sideboards. |
| 406.1.b. |
If a game ends in a draw, players must use the same battlefields for the following game. |
| 406.1.b. → 406.1.c. |
Each player must shuffle their Main Deck and their Rune Deck. See 420 for more information on shuffling. |
| 406.1.c. → 406.1.d. |
Each player must present their Main Deck, Rune Deck, and sideboard (if applicable to the format) to their opponents. |
| 406.1.d. → 406.1.e. |
Each player may shuffle the Main Deck and Rune Deck of each of their opponents. |
|
↕ 0 unchanged + 8 renumbered rules between 406.1.e. and 406.1.g.4.
|
|
| 406.1.f.4. → 406.1.g.4. |
The designated player chooses if they would like to go first or last. |
| 406.1.f.5. → 406.1.g.5. |
Players then have the opportunity to sideboard as if they were in between games of a “best of 3” match. See 403 for more information on sideboards. |
| 406.1.f.6. → 406.1.g.6. |
After sideboarding is complete, each player separates their Chosen Champion and places it in the Champion Zone. |
| 406.1.f.7. |
Players perform shuffling steps 406.1.b.-406.1.d.3. listed above, then proceed to CR 116. Setup Process. |
| 406.1.g.7. |
Players perform shuffling steps 406.1.c.-406.1.e.3. listed above, then proceed to CR 116. Setup Process. |
| 407. |
Play First Rule |
| 407.1. |
For the first game of a match, a designated player decides whether they wish to play first or last. |
| 407.2. |
Any random method that is agreed upon by all players in the current game may be used to determine the designated player. |
|
↕ 138 unchanged rules between 407.2. and 502.
|
|
| 502. |
Information |
| 502.1. |
Cards have a level of privacy as specified in CR 127. Privacy. These apply to levels of information accessible to the players as well. |
| 502.10. |
Judges are encouraged to help players determine public information, but not derived information. |
| 502.11. |
In 2v2, teammates may share Private information, including directly showing each other the cards in their hand as defined by 484.8.e. in the Core Rules. |
| 502.2. |
In addition to these levels of information, some information is derived. |
| 502.2.a. |
Derived information is a combination of public information and a player’s own skill or calculation. |
| 502.2.b. |
Players are not required to assist opponents in determining derived information. |
|
↕ 90 unchanged rules between 502.2.b. and 509.1.
|
|
| 509.1. |
In competitions, players are responsible for considering options before taking actions. |
| 509.2. |
Once an action is communicated to an opponent, that action can’t generally be taken back. |
| 509.3. |
At low OPL, a player can reverse their most recent action and make a different decision for that action (including not taking it at all) as long as no new action has been taken by either player. The change in decision does not need to be immediate. |
| 509.4. |
At high OPL, a player can reverse their most recent action and make a different decision for that action (including not taking it at all) if no new action has been taken by either |
| 509.4.a. |
The player wants to make a different decision for a spell or ability immediately after all choices have been made and communicated for putting it onto the chain. Example: |
| 509.4.a.1. |
A player plays Discipline indicating a unit. They immediately change their mind and choose a different unit, or choose not to play the Discipline at all. |
| 509.4.b. |
The player wants to make a different decision for playing a unit or gear immediately after playing it to a location. Example: |
100 more diff entries…