Skip to content

Commit

Permalink
Update level-22.mdx
Browse files Browse the repository at this point in the history
  • Loading branch information
Zamiell authored Dec 20, 2023
1 parent 6e351bc commit 1fa7aa3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/level-22.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ import ChopMoveIgnitionInteraction from "@site/image-generator/yml/level-22/chop
- _Double Ignition_ does not necessarily have to be on the next two players. It can be on anyone.
- In most circumstances, a _Double Ignition_ should be clear. This is because the two players that have a playable card will each see that the clue giver should have clued the other playable card directly (instead of giving a "useless" clue).
- Sometimes, an _Ambiguous Double Ignition_ can happen (when three or more players have a playable card on _Finesse Position_). In this situation:
- The first _Ignition_ **must always be on Bob**, unless Bob has a known-playable card already. Then, it would be on the first player without a known-playable card already.
- The first _Ignition_ **must always be on Bob**, unless Bob has a known-playable card already. Then, it would be on the first player that does not already have a known-playable card.
- The second _Ignition_ **must always be on the last player with a playable card**. (This is because the players in the middle will think that the last person is supposed to play, similar to how a normal _Ambiguous Finesse_ works.)

<br />
Expand Down

0 comments on commit 1fa7aa3

Please sign in to comment.