Skip to content

Commit

Permalink
Update level-5.mdx (#1144)
Browse files Browse the repository at this point in the history
Fix a typo.
  • Loading branch information
mwoghiren authored Dec 5, 2023
1 parent 54993e4 commit 8b1427f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/level-5.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@ import UrgencyPrinciple from "@site/image-generator/yml/level-5/urgency-principl
- Sometimes, players who have been _Layered Finessed_ cannot blind-play their cards right away. When this happens, they will be giving clues or discarding.
- Thus, it is possible for a person who has been _Layered Finessed_ to accidentally give a _Play Clue_ to a card in someone else's hand that was already "gotten" inside of the _Layered Finesse_ of their own hand.
- When this occurs, one of two things usually happen:
- If Bob (the person who was clued) knows the exact identity of the card, then it is obvious that Alice accidentally duplicated it. In this case, Bob can safely discard the card to pass it back to Alice. (This is important to prevent a bomb later on when Alice "unravels" the _Layered Finessed_.)
- If Bob (the person who was clued) knows the exact identity of the card, then it is obvious that Alice accidentally duplicated it. In this case, Bob can safely discard the card to pass it back to Alice. (This is important to prevent a bomb later on when Alice "unravels" the _Layered Finesse_.)
- If Bob (the person who was clued) does not know the exact identity of the card, then he is forced into just playing the card. Bob is not allowed to "dick around" in this situation, as that might cause even more confusion for the team. After Bob plays the card, if it was indeed duplicated, then the team must now give a _Fix Clue_ to Alice. At first, Alice will be surprised that a clue is being targeted to a card "inside of her layer". But when combined with the context of Alice giving a clue to a similar card, it should be obvious what is happening.

<br />
Expand Down

0 comments on commit 8b1427f

Please sign in to comment.