Two Macau Dice Combo: How Many?

There are exactly 21 distinct combinations when you roll two Macau dice, and anyone who tells you 36 is either counting ordered outcomes or has never audited a live table's payout ledger. This is the single most misunderstood number in dice-based wagering, and it costs operators real money every night because floor staff and system architects keep confusing permutations with combinations.

The Combinatorial Ground Truth

Two standard six-sided dice produce 36 ordered outcomes, yes, but the moment you collapse duplicates β€” the 1-2 and 2-1 pairs β€” you drop to 21 unique faces. That's the number baked into every Macau dice combo calculation that actually matters for house edge modeling. Break it down: six doubles (1-1 through 6-6) plus fifteen mixed pairs equals 21. The probability distribution is brutally uneven, and that asymmetry is where the entire edge lives. The sum of 7 appears in six of the 36 permutations but only three of the 21 combos β€” a distinction that trips up every junior odds compiler I've ever trained. 🎲

Why the 21 Matters for Payout Architecture

Here's where the hardware and firmware crowd needs to pay attention. When you're auditing a dice combination count against the actual RNG output stream, the 21-combo framework reveals whether the machine is treating outcomes as weighted or flat. A flat 21-model implies each combo carries 1/21 probability, which is mathematically wrong for physical dice but alarmingly common in lazy software implementations. I've torn apart firmware on three separate continents where the paytable was calibrated to 21 equal buckets β€” that's a silent 4.7% leakage on certain bet types. The hardware doesn't lie; the code does.

The Doubles Trap and Edge Computation

Six of those 21 combos are doubles, giving a 6/21 surface probability but a true 6/36 roll frequency. Any operator pricing a doubles side bet off the 21-combo flat model is handing players a 14.3% overlay. Run the real math: true doubles probability sits at 16.67%, and if your payout assumes 28.57%, you've built a money furnace. This is the kind of error that survives months of Macau dice combo reporting because the variance masks it until a whale hammers the doubles line for a weekend. πŸ”

Permutation vs Combination in Live Audit Trails

Every hand-paid table log I've ever reconciled uses permutation counting for settlement but combination counting for game design. You need both. The 36-permutation view tells you what actually hit; the 21-combination view tells you what the game thinks can hit. When those two diverge in your reconciliation sheet, you've found either a dealer error, a firmware bug, or a calibration drift β€” and the gap between 36 and 21 is precisely where the forensic trail begins. The number is 21. Memorize it, build your paytables around the true weighted distribution, and stop letting flat-combo assumptions bleed your cage dry.