Tournament Infractions
A quick reference to Riftbound Tournament Rules infractions, penalties, and remedies.
Game Play Errors
- 702.2.
Missed Trigger [No Penalty]: The accountable player for a triggered ability doesn’t demonstrate awareness of the trigger before the first time it would have an observable impact on the game.
- 702.2.a.
See 506 for definition of triggered abilities.
- 702.2.b.
After the initial point at which a triggered ability is missed, any further errors related to that trigger are considered a General Error instead. See 702.16 for more information about General Errors.
- 702.2.c.
Players may not attempt to cause triggered abilities where an opponent is the accountable player to be missed by taking game actions or otherwise prematurely advancing the game, including through otherwise acceptable shortcuts.
- 702.2.d.
A triggered ability is considered to have triggered even if it was subsequently missed. Effects that count or restrict the number of times that ability can trigger will count the missed one.
- 702.2.e.
If a mandatory trigger is missed by its accountable player and missing that trigger is advantageous for them, this penalty is a [Warning] instead.
- 702.2.f.
Remedies:
- 702.2.f.1.
If the trigger was missed during a previous turn, instruct the players to continue playing.
- 702.2.f.2.
Otherwise, the next opponent in turn order of the player who missed the trigger chooses whether to resolve the trigger immediately or miss it altogether.
- 702.3.
Forgetting to Score a Point [No Penalty]: A player is entitled to a point from conquering or holding a battlefield but fails to track it.
- 702.3.a.
This does not apply to points that would be scored from card triggers such as Ahri, Alluring.
- 702.3.b.
Remedies:
- 702.3.b.1.
If the correct score can be determined and no more than a full round cycle has passed, increment the appropriate player’s score to that total.
- 702.3.b.2.
Otherwise, instruct the players to continue playing.
- 702.4.
Forgetting to Draw Cards [No Penalty]: A player is obligated to draw a card, either as part of their draw phase or instruction from a card, but fails to do so.
- 702.4.a.
Remedies:
- 702.4.a.1.
If the missed draws can be determined and no more than a full round cycle has passed, the appropriate player draws the missing cards.
- 702.4.a.2.
Otherwise, instruct the players to continue playing.
- 702.4.b.
If forgetting to draw was advantageous to the erroring player (example: the player is near burning out), this penalty is a [Warning] instead.
- 702.5.
Looking at Extra Cards [Warning]: While taking a game action that allows a player to look at cards from a deck, they look at more cards than they are entitled to.
- 702.5.a.
Cards being looked at from secret information such as a deck are added to a private information group while they are being looked at.
- 702.5.b.
Once extra cards being looked at have touched a new private or secret group from their original source, they become part of that group. If the extra cards have not touched a new group, this is instead a Looking at Secret Information error. See 702.10. for more on Looking at Secret Information errors.
- 702.5.b.1.
For example, if a player plays a Stacked Deck and adds a fourth card to the private set of cards they are looking at, it is Looking at Extra Cards. If they correctly look at the top three, but knock the top card of their Main Deck over without adding it to the private group, it is Looking at Secret Information.
- 702.5.c.
Remedies:
- 702.5.c.1.
If the error is caught while the erroring player is looking at the extra cards, the next opponent in turn order of the erroring player looks at the private group and chooses the appropriate number of extra cards to shuffle back into the randomized portion of the appropriate deck.
- 702.5.c.1.a.
If one or more of the cards has already been added to a new group of cards, the next opponent in turn order of the erroring player looks at that group and chooses the appropriate number of cards to return to the original group of cards being looked at. Then perform 702.5.c.1
- 702.5.c.2.
If the error is caught at a later stage in the game, instruct players to continue playing.
- 702.6.
Channeling Too Many Runes [Warning]: A player channels a number of runes greater than they are entitled to under the Core Rules as the result of a limited action.
- 702.6.a.
Errors of this sort are generally public, and all players are expected to be mindful of game state.
- 702.6.b.
Remedies:
- 702.6.b.1.
If the additional runes have been used to pay for actions, rewind if possible. If rewinding is not possible, this is a General Error instead. See 702.15 for more information about General Errors.
- 702.6.b.2.
If the additional runes are caught and no more than a full round cycle has passed, shuffle them appropriately into the rune deck.
- 702.6.b.2.a.
If the specific runes can’t be identified, shuffle random runes instead.
- 702.6.b.3.
Otherwise, instruct the players to continue playing.
- 702.7.
Channeling Too Few Runes [No Penalty]: A player channels a number of runes less than what they are entitled to under the Core Rules as the result of a limited action.
- 702.7.a.
Errors of this sort are generally public, and all players are expected to be mindful of game state.
- 702.7.b.
Remedies:
- 702.7.b.1.
If no more than a full round cycle has passed, allow the player to channel the appropriate number of runes.
- 702.7.b.2.
Otherwise, instruct the players to continue playing.
- 702.7.c.
If forgetting to channel runes was advantageous to the erroring player, this penalty is a [Warning] instead.
- 702.8.
Overpayment for Cost [No Penalty]: A player pays a cost overpaying its power or energy cost.
- 702.8.a.
Errors of this sort are generally public, and all players are expected to be mindful of game state.
- 702.8.b.
Remedies:
- 702.8.b.1.
If possible, perform a simple rewind to before the card or ability was put on the chain. If a simple rewind is not possible, instruct the players to continue playing.
- 702.8.b.1.a.
If overpaying a cost was advantageous to the erroring player, this penalty is a [Warning] instead.
- 702.8.b.1.b.
If overpaying a cost caused a result that would not otherwise have happened, it is a General Error. See 702.15 for more information about General Errors.
- 702.9.
Mispayment for Cost [Warning]: A player pays a cost underpaying its requirements or using the incorrect requirements. See CR 201. Costs for more detail on costs.
- 702.9.a.
Errors of this sort are generally public, and all players are expected to be mindful of game state.
- 702.9.b.
Remedies:
- 702.9.b.1.
If possible, perform a simple rewind to before the card or ability was put on the chain.
- 702.9.b.2.
If a simple rewind is not possible, correct the cost paid if possible.
- 702.9.b.2.a.
If runes were incorrectly recycled as part of the cost, rewind if possible.
- 702.9.b.3.
If neither is possible, instruct the players to continue playing.
- 702.10.
Looking at Secret Information [Warning]: A player looks at information that is not available to any player. See CR 128. Privacy for information types.
- 702.10.a.
Players should not be penalized via a remedy for errors their opponents make. Example: If one of your opponents inappropriately flips over the top card of their deck, you do not receive a penalty if you see it.
- 702.10.b.
Remedies:
- 702.10.b.1.
If possible, take involved cards in the now-known secret information and re-randomize them with the original randomized source of appropriate cards to remove the information advantage.
- 702.10.b.2.
If this is not possible, reveal the information to all players to remove the information advantage and instruct the players to continue playing.
- 702.11.
Looking at Opponent Private Information [Warning]: A player accidentally looks at information that is private to their opponent. See CR 128. Privacy for information types.
- 702.11.a.
Players should not be penalized via a remedy for errors their opponents make. Example: If one of your opponents inappropriately drops a card from their hand on the table, you do not receive a penalty if you see it.
- 702.11.b.
Remedies:
- 702.11.b.1.
The opponent whose private information it is may decide whether to take involved cards in the now-known private information and re-randomize them with the original randomized source of appropriate cards.
- 702.11.b.2.
If they decide not to, instruct the players to proceed.
- 702.12.
Drawing Extra Cards [Warning]: A player draws more cards than they are entitled to under the Core Rules as the result of a limited action or a player draws cards when they are not entitled to under the Core Rules.
- 702.12.a.
Drawing extra cards is also looking at extra cards, but only this error should be recorded.
- 702.12.b.
Remedies:
- 702.12.b.1.
If the error is caught before the extra cards drawn are added to a private set, shuffle them into the main deck appropriately to remove the information advantage.
- 702.12.b.2.
If the error is caught when a player draws their opening hand during the start of game procedure and the player has not performed their mulligan yet, shuffle the extra cards into the main deck appropriately to remove the information advantage.
- 702.12.b.3.
If the error is caught after the cards drawn are added to a private set and it is within the round cycle, the next opponent in turn order of the erroring player looks at that player’s hand and chooses the appropriate number of cards to shuffle into the main deck appropriately.
- 702.12.b.4.
If at a later stage in the game it is determined a player has more cards in hand than they should, the remedy should be applied at this time.
- 702.13.
Facedown Card Error [Warning]: A player adds a card to a facedown zone or removes a card from a facedown zone in a manner other than how they are entitled to under the Core Rules.
- 702.13.a.Example: Hiding a card that does not have the Hidden keyword.
- 702.13.b.Example: Moving a hidden card from a battlefield to a hand or Main Deck illegally.
- 702.13.c.
Remedies for illegally added cards:
- 702.13.c.1.
If the error is caught by the erroring player immediately and before any additional game actions have been taken, return the card to the zone it came from and resume play.
- 702.13.c.2.
If the error is caught after additional game actions have been taken but before any unknown cards have been added to the zone where the illegal card came from (such as a new card being drawn), return the illegal card to the zone it came from and replace it with a random card from that zone that is legal for the facedown zone and resume play.
- 702.13.c.2.a.
If there is no available legal replacement, this penalty upgrades to [Game Loss].
- 702.13.c.2.b.
If the error is caught after unknown cards have been added to the zone where the illegal card came from, this penalty upgrades to [Game Loss].
- 702.13.d.
Remedies for illegally removed cards:
- 702.13.d.1.
If the error is caught during the turn it occurred, and the card is easily identifiable and recoverable, return the card to the zone it came from and resume play.
- 702.13.d.2.a.
If the error is caught on a later turn or the card is not easily identifiable and recoverable, this penalty upgrades to[Game Loss].
- 702.14.
Mulligan Procedure Error [Warning]: A player performs the mulligan procedure incorrectly.
- 702.14.a.
Remedies:
- 702.14.a.1.
If a player recycled and replaced more than 2 cards during their mulligan, the next opponent in turn order of the erroring player looks at that player’s hand and may choose cards up to the number of extra cards mulliganed to have that player recycle and replace.
- 702.14.a.1.a.Example: If a player accidentally mulliganed 3 cards, the next opponent in turn order would look at that player's hand and may choose up to one card to have that player recycle and replace.
- 702.14.a.2.
If this error is caught after gameplay has begun, instruct the players to proceed.
- 702.15.
Forgetting to Ready During the Awaken Phase [No Penalty]: A player forgets to ready one or more game objects during their Awaken Phase.
- 702.15.a.
Remedies:
- 702.15.a.1.
If it is still the turn the erroring player forgot to awaken, ready all game objects that should have been readied. If a game object being readied this way would put a trigger on the chain, it is not put on the chain instead.
- 702.15.a.2.
If it is no longer the turn the erroring player forgot to awaken, leave game objects in their current state and proceed with play.
- 702.15.b.
If forgetting to ready was advantageous to the erroring player, this penalty is a [Warning] instead.
- 702.16.
General Error [Warning]: Any other violation of the Rules of Riftbound.
- 702.16.a.
This is a catch-all for any other game play error.
- 702.16.b.
Errors of this sort are generally public, and all players are expected to be mindful of game state.
- 702.16.c.
Remedies:
- 702.16.c.1.
Rewind if possible.
- 702.16.c.2.
Otherwise, instruct the players to continue playing.
- 702.17.
Failure to Maintain Game State [Warning]: A player does not call out another player’s failure to maintain the proper game state, including missed scoring from hold and conquer.
- 702.17.a.
Generally this error occurs when a player’s opponent commits a game play error (excluding missed beneficial triggers) and the player doesn’t call a judge immediately.
- 702.17.b.
Unlike other Game Play Errors, this error is primarily for tracking and never upgrades unless specifically instructed by the head judge.
Tournament Errors
- 703.2.
Slow Play [Warning]: A player is performing their start of game procedure or is playing mid-game at an unreasonably slow pace.
- 703.2.a.
Players must take their turns in a timely manner, appropriate to a judge according to the state of the game at the time, and adhere to time limits specified for the tournament.
- 703.2.b.
Players may ask a judge to watch their game for slow play.
- 703.2.c.
Intentionally stalling to gain an advantage is cheating. See 704.8 for more information about cheating.
- 703.3.
Decklist Error [Game Loss]: A player submits a decklist for registration that contains illegal elements.
- 703.3.a.
Examples:
- 703.3.a.1.
More or fewer cards than appropriate deck size. See 402 for more information about deck size.
- 703.3.a.2.
Cards not legal in the format of the tournament.
- 703.3.a.3.
More than 3 copies of a main deck card between main deck and sideboard.
- 703.3.a.4.
Cards that do not match the domain of the registered legend.
- 703.3.a.5.
A chosen champion that does not match the identity of the legend.
- 703.3.a.6.
A player’s decks contain cards that do not match their registered decklist.
- 703.3.b.
Remedies:
- 703.3.b.1.
If the player’s registered decklist is illegal, the player must correct their decklist to a legal state making as little change as possible and ensure that their deck matches the newly registered deck.
- 703.3.b.2.
If the player’s presented decks do not match their registered decklist but their presented decks are legal, the player must change their registered decklist to match their presented deck.
- 703.3.b.3.
If the cards required to correct a decklist cannot be acquired in a timely manner, the head judge can issue a proxy.
- 703.4.
Deck Presentation Error [Warning]: A player’s deck’s contents are illegal during presentation to an opponent or during gameplay.
- 703.4.a.
Examples:
- 703.4.a.1.
A player submits a battlefield they have already used in the match.
- 703.4.a.2.
A player forgets to restore their deck to a pre-sideboard state for the first game of a match.
- 703.4.a.3.
A player forgets to take their chosen champion from their main deck and place it in the chosen champion zone.
- 703.4.a.4.
A player’s deck is the incorrect deck size. See 402 for more information about deck size. (Examples: A player misplaced a card, a player forgot to shuffle their banished cards back into their deck between games, a player's deck has an extra card or is missing a card due to an effect like Possession from a previous game.)
- 703.4.a.5.
A player has cards in their deck box with their deck that are not part of the registered contents of their decklist. Promotional cards given out as part of the event, tokens, and damaged cards replaced with official proxies are allowed to be stored this way and do not warrant this error.
- 703.4.b.
Remedies when a player forgets to select their Chosen Champion during setup:
If the error is caught before the start of the first player’s turn, restore the deck to its correct state and instruct players to proceed.
- 703.4.b.1.
At Casual OPL, if the error is caught after the start of the first player’s turn, instruct the erroring player to search the randomized portion of their main deck, their hand and sideboard for a legal chosen champion and place it in their chosen champion zone, then shuffle the randomized portion of their main deck. If the champion came from their hand, instruct them to draw a card.
- 703.4.b.1.a.
If none are found, instruct players to continue playing with the erroring player’s chosen champion zone empty.
- 703.4.b.2.
At Competitive OPL, if the error is caught after the start of the first player’s turn, a judge searches the randomized portion of the erroring player’s main deck and hand for a copy of their registered game one chosen champion and move it to their chosen champion zone, then shuffle the randomized portion of their main deck. If the champion came from their hand, instruct them to draw a card.
- 703.4.b.2.a.
If none are found, instruct players to proceed with the erroring player’s chosen champion zone empty.
At Professional OPL, if the error is caught after the start of the first player’s turn, instruct players to proceed with the erroring player’s chosen champion zone empty.
- 703.4.b.3.
Purposely leaving your Chosen Champion zone empty during setup to gain an advantage is cheating. See 704.8 for more information about cheating.
- 703.4.c.
Other Remedies:
- 703.4.c.1.
If the error is caught before opening hands have been drawn, restore the deck to its correct state if possible and instruct players to proceed.
- 703.4.c.2.
If the error is caught by the erroring player after opening hands have been drawn and it is easily possible, restore the deck to its correct state and instruct players to proceed. For example:
- 703.4.c.2.a.
In game one of a match a player realizes they forgot to restore their deck to a pre-sideboard state.
- 703.4.c.2.a.1.
A judge can restore their deck to the appropriate state by returning cards to the main deck and sideboard as needed.
- 703.4.c.2.a.1.a.
If sideboard cards are in the player's hand, they are replaced randomly by main deck cards that were incorrectly in the sideboard.
- 703.4.c.2.a.2.
Shuffle the randomized portion of the main deck once this process is complete.
- 703.4.c.3.
If the error is caught by anyone other than the erroring player after opening hands have been drawn, the penalty is upgraded to [Game Loss].
- 703.4.c.4.
In either case, if restoring the deck to its correct state is not possible, the penalty is upgraded to [Game Loss].
- 703.4.c.4.a.Example: A player has two total copies of Traveling Merchant on their registered decklist, one in their Main Deck and one in their Sideboard. During game one of a match a player draws and plays one Traveling Merchant. On a later turn, they draw the second copy and realize they forgot to de-sideboard. At this point, since both Traveling Merchants have been drawn, restoring the deck is not possible as there is no easy 1 to 1 swap that can be made to restore the correct deck state.
- 703.4.c.5.
At Professional OPL, extra cards in a player’s deck box as described in 703.4.a.5. upgrades this penalty to [Game Loss].
- 703.4.d.
For all deck presentation errors, if the cards required to correct the deck cannot be acquired in a timely manner, the head judge can issue a proxy.
- 703.4.e.
During matches, players may request a judge check an opponent’s deck for legality. (Example: A player believes an opponent has a sideboard card in the first game.)
- 703.5.
Communication Violation [Warning]: A player does not effectively communicate with their opponents during gameplay.
- 703.5.a.
This error includes any unintentional violation of the communication policies listed in section 500.
- 703.5.b.
Remedies:
- 703.5.b.1.
If any incorrect information was communicated, the correct information is supplied.
- 703.5.b.2.
If any decisions were made based on incorrect communication, perform a rewind if possible.
- 703.6.
Marked Cards [Warning]: A player’s cards are possible to identify without seeing their face.
- 703.6.a.
This includes but is not limited to scratches, discoloration, and bends.
- 703.6.b.
If a player’s cards are sleeved, the cards must be examined while in the sleeves to determine if they are marked.
- 703.6.c.
The Head Judge has the authority to determine if a card in a player’s deck is marked.
- 703.6.d.
Remedies
- 703.6.d.1.
Judges may request that a player remove their current sleeves or replace any of the deck’s current sleeves or cards immediately, or before the next round.
- 703.6.d.2.
If the cards required to correct the deck cannot be acquired in a timely manner, the head judge can issue a proxy.
- 703.7.
Insufficient Randomization [Warning]: A player did not sufficiently randomize their deck when required to.
- 703.7.a.
If a player believes an opponent has not sufficiently randomized their Main Deck or Rune Deck before presenting them, they may call a judge.
- 703.7.b.
Pile shuffling is not a sufficient randomization method and should only be used as a counting method.
- 703.7.c.
Remedies:
- 703.7.c.1.
A judge may instruct a player to rerandomize their deck.
- 703.7.c.2.
A judge may randomize the player’s deck for them.
- 703.8.
Late to Match: A player arrives at their assigned match after the round clock has started.
- 703.8.a.
If the player arrives within 2 minutes of the round start, the penalty is a [Warning] and a time extension is issued.
- 703.8.b.
If the player arrives within 10 minutes of the round start, the penalty is a [Warning] and a time extension is issued. At high OPL the penalty is upgraded to [Game Loss].
- 703.8.c.
If the player arrives after 10 minutes of the round start, the penalty is a [Match Loss].
- 703.8.d.
If a player never arrives for their match, the penalty is a [Match Loss] and the player is dropped from the tournament unless they report to a judge before the next match begins.
- 703.8.e.
Players may call a judge before the round clock starts or in between games of a match to request up to a 10 minute time extension in lieu of penalty at the judge’s discretion. (Example: A player requests to use the restroom.)
- 703.9.
Outside Assistance: A player receives advice or strategic assistance from an individual outside of the match.
- 703.9.a.
If the player receiving the advice actively refuses the advice by calling a judge, they receive a [Warning]. Otherwise, that player receives a [Match Loss]. This penalty does not apply if the head judge deems the advice was delivered maliciously.
- 703.9.b.
If the player receiving the advice solicited the advice, it is cheating. See 704.8 for more information about cheating.
- 703.9.c.
If the spectator giving the outside assistance is also a player in the event, this penalty is also applied to them.
- 703.9.d.
Spectators providing advice may be barred from the tournament venue if the advice was given maliciously or knowingly.
- 703.9.e.
It is not outside assistance to receive strategic advice from a teammate in the 2v2 format or in other team formats when specified.
- 703.9.f.
At a judge’s discretion, a player may receive assistance with the physical logistics of the competition, including game actions such as shuffling or card movement. This is not considered outside assistance.
- 703.9.g.
Violating electronic devices policies will result in an outside assistance [Warning].
- 703.10.
Improperly Determining a Winner [Match Loss]: Games and matches of Riftbound must be decided by playing Riftbound appropriate to the tournament format.
- 703.10.a.
Other methods, including but not limited to flipping a coin, rolling dice, or playing other games, may not be used to determine a winner.
- 703.10.b.
Playing other formats of Riftbound other than the one designated for the tournament with the appropriate decklist may not be used to determine a winner.
- 703.10.c.
Offering or accepting such offers is considered improperly determining a winner.
- 703.10.d.
A Professional OPL, the penalty is upgraded to [Disqualification]. This should be clearly communicated to all players at the start of a Professional OPL event.
- 703.10.e.
Knowingly attempting to improperly determine a winner or attempting to goad an opponent into doing so is cheating. See 704.8 for more information about cheating.
Unsporting Conduct
- 704.2.
Unsporting Minor [Warning]:
- 704.2.a.
Examples include but are not limited to:
- 704.2.a.1.
Disrespecting attendees or spectators
- 704.2.a.2.
Bullying
- 704.2.a.3.
Poor hygiene
- 704.2.a.4.
Offensive play materials
- 704.3.
Unsporting Major [Disqualification]:
- 704.3.a.
Examples include but are not limited to:
- 704.3.a.1.
Use of racial slurs
- 704.3.a.2.
Physical violence or the threat of physical violence
- 704.3.a.3.
Displaying aggression
- 704.3.a.4.
Intentionally misgendering an event attendee
- 704.3.b.
This penalty often comes with ejection from the venue at the discretion of tournament officials.
- 704.4.
Angle Shooting [Warning]: A player intentionally uses the technical precision of the rules to gain an advantage where the spirit of the rules would not have garnered that advantage.
- 704.4.a.
Examples include but are not limited to:
- 704.4.a.1.
Asking a player to state a choice that they would make on resolution prior to deciding whether to react.
- 704.4.a.2.
Taking actions quickly to prevent opponents from having time to have priority.
- 704.4.a.3.
Promising a concession to garner additional information before making a different decision.
- 704.4.a.4.
Attempting to mislead an opponent during gameplay based on cards that have rules errata.
- 704.4.a.5.
Baiting an opponent into a rules violation.
- 704.4.a.6.
Intentionally distracting an opponent to get them to miss their priority window.
- 704.4.a.7.
Using sloppy play or game state representation to obscure strategy or information.
- 704.5.
Bribery [Match Loss]: Tournament attendees and spectators may not bribe tournament players or tournament officials.
- 704.5.a.
The outcome of tournament games may not be influenced by offers of out-of-game rewards or incentives.
- 704.5.a.1.
Making or accepting such an offer is considered bribery.
- 704.5.a.2.
Bribery applies to actions within a game, not just the final results.
- 704.5.a.3.
Receiving an offer is not considered bribery unless entertained or accepted, but the receiving player must inform a judge.
- 704.5.b.
Sharing prizes that have not yet been awarded in the current tournament does not constitute bribery. Players are permitted to make such agreements before or during their match, provided that the prize sharing is not offered or accepted in return for the outcome of a game or match, any in-game action, or a player dropping from the tournament.
- 704.5.c.
It is not bribery when players in the single-elimination portion of a tournament offering only items such as cash, store credit, and/or unopened product, with the competition organizer’s permission, agree to divide the subsequent tournament prizes evenly. All players still in the tournament must agree to the arrangement.
- 704.5.c.1.
Players may end their participation in the tournament at this point or continue to play. If this is a major streamed event, players must continue to play for final rankings.
- 704.5.d.
It is not bribery when, in the final round of the single-elimination portion of a tournament, with the competition organizer’s permission, players mutually agree on a winner and how to divide the remaining prizes. In such cases, one player must agree to drop from the tournament. Prizes are then awarded based on each player’s final standing.
- 704.6.
Wagering [Disqualification]: Tournament attendees may not wager on any portion of a tournament, match, or game, including its outcome.
- 704.7.
Theft [Disqualification]: Stealing or attempting to steal the property of a tournament attendee, spectator, vendor, or event organizer.
- 704.8.
Cheating [Disqualification]: Riftbound does not tolerate cheating at any level of play.
- 704.8.a.
Cheating includes but is not limited to performing any action that results in a penalty listed under 702 or 703 if it is done knowingly or maliciously to obtain an advantage.
- 704.8.a.1.
This includes attempting to create game errors to use a remedy to the player’s advantage.
- 704.8.a.2.
If judges suspect a player is violating the rules knowingly or maliciously, the head judge may initiate an investigation to determine if cheating occurred.
- 704.8.b.
Lying to a tournament official is cheating.
- 704.8.c.
Intentionally neglecting to indicate a teammate's error is cheating.
- 704.8.d.
The head judge has ultimate discretion to issue penalties for cheating.
How was this page?