Hello Forum,
I’d like to present my arguments for why Pestilent Double Bluff (PDB) is stronger, clearer, and more broadly useful than Promise Double Bluff (PrDB) and why PDB should be the default convention used on BGA in the majority of games.
Because these two conventions directly conflict, only one can be active at a time. Below I explain why PDB > PrDB in practice.
Why Pestilent Double Bluff Matters
PDB appears frequently in real games. Consider a very common situation:
A clues 2 on the green 2 to D
B plays 1y, believing it is 1g
C plays 1b to repair the situation
D now knows the 2 cannot be yellow or blue—otherwise only one of those cards would have played
When C plays to fix the broken situation, they are healing the clue and preventing D from bombing. This “healing” element is the core of Pestilent Double Bluff: a broken situation must be repaired to prevent the destination card from bombing.
This act of healing is what gives PDB both its name and its structure.
What a Double Bluff Actually Is
A double bluff is a clue that targets a destination card and allows two cards to play in sequence. Both cards played do not match the sequence to the destination card but are played without causing any bombs.
- A potentially connecting card
- A healing card
At first glance, the clue looks like a simple finesse:
1r is played on the stacks.
A clues 3 to D. To D, this presents itself as 3r being the destination card in their hand.
B plays 2r (the connecting card)
C plays 1w (the healing card)
D now knows the 3 is not red since C played to heal the situation.
This pattern is simple, efficient, and highly replicable.
Why PDB Should Be the Default
Greater frequency.
PDB is easier to use, more intuitive, and appears naturally in many board states. Situations where a player can give a PDB occur in roughly one out of every three games, making it far more common than PrDB.
Its reliability and frequency make it a strong candidate for the default double‑bluff convention on BGA.
Where PDB and PrDB Diverge
Promise Double Bluff requires significantly more conditions to be met.
Example:
A clues 3 on 3r to D
B plays 1b
C plays 1y
D, when receiving the clue, must scan the table for a 2 in the leftmost position or behind a playable card of B or C that could connect to their 3
Only if such a 2 exists can D interpret the clue as a Promise Double Bluff.
The odds of this alignment are extremely low. Yes, it does happen but rarely. And when it does, the payoff (card plays, card identity resolution) is not meaningfully greater than what PDB already provides.
So the question becomes:
Why prioritize a convention that is exponentially rarer, harder to spot, and offers little additional value?
PDB gives the same benefits while occurring far more often and with far clearer structure.
I’d like to present my arguments for why Pestilent Double Bluff (PDB) is stronger, clearer, and more broadly useful than Promise Double Bluff (PrDB) and why PDB should be the default convention used on BGA in the majority of games.
Because these two conventions directly conflict, only one can be active at a time. Below I explain why PDB > PrDB in practice.
Why Pestilent Double Bluff Matters
PDB appears frequently in real games. Consider a very common situation:
A clues 2 on the green 2 to D
B plays 1y, believing it is 1g
C plays 1b to repair the situation
D now knows the 2 cannot be yellow or blue—otherwise only one of those cards would have played
When C plays to fix the broken situation, they are healing the clue and preventing D from bombing. This “healing” element is the core of Pestilent Double Bluff: a broken situation must be repaired to prevent the destination card from bombing.
This act of healing is what gives PDB both its name and its structure.
What a Double Bluff Actually Is
A double bluff is a clue that targets a destination card and allows two cards to play in sequence. Both cards played do not match the sequence to the destination card but are played without causing any bombs.
- A potentially connecting card
- A healing card
At first glance, the clue looks like a simple finesse:
1r is played on the stacks.
A clues 3 to D. To D, this presents itself as 3r being the destination card in their hand.
B plays 2r (the connecting card)
C plays 1w (the healing card)
D now knows the 3 is not red since C played to heal the situation.
This pattern is simple, efficient, and highly replicable.
Why PDB Should Be the Default
Greater frequency.
PDB is easier to use, more intuitive, and appears naturally in many board states. Situations where a player can give a PDB occur in roughly one out of every three games, making it far more common than PrDB.
Its reliability and frequency make it a strong candidate for the default double‑bluff convention on BGA.
Where PDB and PrDB Diverge
Promise Double Bluff requires significantly more conditions to be met.
Example:
A clues 3 on 3r to D
B plays 1b
C plays 1y
D, when receiving the clue, must scan the table for a 2 in the leftmost position or behind a playable card of B or C that could connect to their 3
Only if such a 2 exists can D interpret the clue as a Promise Double Bluff.
The odds of this alignment are extremely low. Yes, it does happen but rarely. And when it does, the payoff (card plays, card identity resolution) is not meaningfully greater than what PDB already provides.
So the question becomes:
Why prioritize a convention that is exponentially rarer, harder to spot, and offers little additional value?
PDB gives the same benefits while occurring far more often and with far clearer structure.