Six Balls, Two Wickets and Run Deductions
Choose target eight, twelve, eighteen or twenty-four before the over. You have at most six deliveries. Each delivery produces zero, one, two, three, four or six runs, or a wicket. Run outcomes add their value; zero adds nothing. A wicket first subtracts two runs from the current total, floored at zero, and consumes one wicket. One run followed by a wicket therefore leaves zero runs and one wicket lost. Success settles immediately when the target is reached before the second wicket. The second wicket, or ball six with the target still unmet, ends the over with zero gross credit.
Choose a Shot, Then Sample Its Outcome
You choose Defend, Drive, Cut or Sweep before each delivery. You do not choose the resulting runs or wicket. In outcome order 0, 1, 2, 3, 4, 6, W, the integer probabilities out of 100 are Defend: 20,38,22,10,6,1,3; Drive: 15,25,25,10,15,4,6; Cut: 18,18,20,8,22,6,8; Sweep: 20,10,12,5,25,15,13. Every row sums to 100. The browser samples one outcome after the chosen shot using an unbiased uint32 rejection sampler. Earlier outcomes do not alter a row, although the current score, wickets and balls remaining affect which shot maximizes the chance of success.
Optimal Success Chance and Gross Credit
For each target, a finite-state recursion considers the remaining deliveries, current credited runs and wickets lost. It evaluates each shot’s possible next states and chooses the greatest success probability. Let P be that optimal initial probability for the selected target. A successful over returns the whole captured stake times 0.96 divided by P; an unsuccessful over returns zero. The maximum exact unrounded expected gross credit is therefore 96% of stake under an optimal adaptive shot policy. This is not a 96% win probability or a promised wallet result. Other policies may have lower expectation. The current hint identifies a shot with maximal success chance in the actual state.
Saved Wallet and Manual Refill
The initial wallet holds 1000 free coins. Settled wallet values and fractional-credit carry persist in browser localStorage; reloading does not reset those saved values. While idle with fewer than ten coins, manual refill sets the balance to 1000 and keeps carry. It never adds 1000 and is not an automatic response to a wicket or a lost over. Keep an active over open until it settles; persistence of a settled wallet does not promise recovery of interrupted play. Clearing browser cache alone may leave localStorage intact.
Frequently asked questions
What are the seven delivery outcomes?
Zero, one, two, three, four or six runs, and a wicket. You choose a shot, and its probability row determines the random delivery outcome.
When does an over end?
Success settles immediately on reaching the selected target before the second wicket. Otherwise the second wicket or six deliveries with an unmet target ends in zero gross credit.
How does a wicket affect runs?
It subtracts two credited runs, floored at zero, and consumes one wicket. A second wicket ends the over.
What does 96% describe?
It is the maximum exact unrounded expected gross credit under an optimal adaptive shot policy. It is not the winning frequency or a session guarantee.
Can I collect before the target?
There is no cashout. The over settles on success, a second wicket or its six-ball limit.
If you choose to explore our original free virtual-coin demo, set a stopping time and take breaks. Play the free demo
