Skip to content

Commit

Permalink
feat: trash finesses & trash bluffs always unnecessary
Browse files Browse the repository at this point in the history
  • Loading branch information
Zamiell committed Nov 24, 2023
1 parent 99018a1 commit 4889cbe
Show file tree
Hide file tree
Showing 4 changed files with 21 additions and 7 deletions.
2 changes: 0 additions & 2 deletions docs/convention-attribution.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,6 @@ title: Convention Attribution
| The Trash Order Chop Move | Zamiel & Libster |
| Duplication Responsibility | Zamiel |
| The Promise Clue & The Promise Discard | Zamiel & Libster |
| The Unnecessary Trash Finesse/Bluff Chop Move | Libster |
| The Surreptitious Finesse | Sankala |
| The Early 5's Chop Move | Libster |
| The 5 Pull | Libster |
Expand All @@ -97,7 +96,6 @@ title: Convention Attribution
| The Inverted 5's Tempo Clue | NoMercy |
| Discharge | Razvogor |
| The Unknown Trash Discharge | Sankala |
| The Unnecessary Trash Push | sjdrodge |
| Trash Touch Elimination | sjdrodge |
| The Bad Chop Move Ejection | IAMJEFF |
| The 5 Color Ejection | IAMJEFF |
Expand Down
3 changes: 3 additions & 0 deletions docs/level-14.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,7 @@ import TrashPush from "@site/image-generator/yml/level-14/trash-push.yml";
- For example, if the red stack is played up to the red 3, then you **cannot** use a red clue to initiate a _Trash Bluff_, because a blind-play will make the clued card look like the red 5.
- For example, if the red stack is played up to the red 4, then you can use a red clue to initiate a _Trash Bluff_, because a blind-play will prove that the clued card is not a red 5.
- In the case where multiple cards are clued as part of a _Trash Bluff_, **all** of the touched cards are considered to be trash.
- For level 25 players, there are [additional rules](level-25.mdx#trash-finesses-and-trash-bluffs-are-always-unnecessary) relating to _Trash Bluffs_.

<br />

Expand Down Expand Up @@ -79,6 +80,8 @@ import TrashPush from "@site/image-generator/yml/level-14/trash-push.yml";

<TrashFinesseTwoCards />

- For level 25 players, there are [additional rules](level-25.mdx#trash-finesses-and-trash-bluffs-are-always-unnecessary) relating to \_Trash Finesses.

<br />

### The Reverse Trash Finesse
Expand Down
10 changes: 8 additions & 2 deletions docs/level-25.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,8 @@ import UnnecessaryBadChopMoveEjection from "@site/image-generator/yml/level-25/u

## Unnecessary Moves

- Experienced players will know about all sorts of tricky ways to "get" cards - the _Trash Bluff_, the _Trash Finesse_, the _Unknown Trash Discharge_, the _Trash Push_, and so forth.
- In most cases, these complicated moves end up being a 1-for-1, which is not very efficient. Consider that doing a complicated move like a _Trash Bluff_ as a 1-for-1 is pretty pointless if the cluer can instead just give a direct _Play Clue_ to the card that needs to be played as a 1-for-1. Giving "normal" _Play Clues_ is much less likely to go wrong!
- Experienced players will know about all sorts of tricky ways to "get" cards - the _Trash Push_, the _Unknown Trash Discharge_, and so forth.
- In most cases, these complicated moves end up being a 1-for-1, which is not very efficient. Consider that doing a complicated move like a _Trash Push_ as a 1-for-1 is pretty pointless if the cluer can instead just give a direct _Play Clue_ to the card that needs to be played as a 1-for-1. Giving "normal" _Play Clues_ is much less likely to go wrong!
- Therefore, advanced moves are generally used in situations where the card that needs to be played is hard to clue directly. For example:
- It could be "blocked" by other cards (e.g. two of the same card in the hand).
- It could be on chop and "blocked" in the sense that any clue given would look like a _Save Clue_ instead of a _Play Clue_.
Expand All @@ -29,6 +29,12 @@ import UnnecessaryBadChopMoveEjection from "@site/image-generator/yml/level-25/u

<br />

### Trash Finesses and Trash Bluffs Are Always Unnecessary

- As explained in the previous section, tricky moves can either be _necessary_ or _unnecessary_.
- However, we explicitly agree that _Trash Finesses_ and _Trash Bluffs_ are always treated as being _unnecessary_, regardless of whether it was actually possible to "get" the blind-played card with a normal clue.
- The reason for this special status is to simplify thing a little bit, as _Trash Finesses_ and _Trash Bluffs_ are really common, and it can be a real pain to figure out whether they are actually _necessary_ or not.

### Unnecessary Moves with Known Trash --> Ignition

- If **known trash** is used as clue target, the "extra" thing is an _Ignition_. The _Ignition_ must be on Bob, unless Alice had a very good reason not to let Bob give the clue, similar to how _Double Ignition_ works.
Expand Down
13 changes: 10 additions & 3 deletions misc/announcement-backlog.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,12 +6,21 @@ As noted in the [convention changes document](convention-changes.md), sometimes

## The Backlog (General Conventions)

n/a
@everyone Deleted conventions:

**Unnecessary Trash Finesse** & **Unnecessary Trash Bluff** (by pianoblook)

```text
- The special conventions called the **Unnecessary Trash Finesse** and the **Unnecessary Trash Bluff** are deleted.
- Now, all *Trash Finesses* and all *Trash Bluffs* are treated as unnecessary. In other words, all *Trash Finesses* and all *Trash Bluffs* perform *Chop Moves* or *Trash Pushes* when they are performed.
```

<br />

## The Backlog (Variant-Specific Conventions)

@everyone New variant-specific conventions:

**Red Fix Clue** (by Dr. Kakashi)

```text
Expand All @@ -20,6 +29,4 @@ n/a
- We arbitrarily choose red since it is the left-most color.
```

n/a

<br />

0 comments on commit 4889cbe

Please sign in to comment.