Catalogue · Mines
Mines grids and the rising cash-out
A Mines API provider publishes a grid, a mine count and a cash-out that rises with each safe pick. Mines integration means storing that mine count on the round, because a dispute is otherwise just a story about a cell.
Grid size and mine count are the rules
A mine ends the round. Studios ship their own grids.
A 5-by-5 grid with three mines is not the same risk as a larger grid with ten. Those values should be visible before the first reveal, because they are the whole game. If a studio lets the player pick the mine count, store that choice on the round so a dispute can be replayed. 'The game cheated' tickets on mines are almost always a mine count the player did not notice.
Spribe and BGaming both publish mines-style titles. They are different games with different certificates. Enable the one your market allows, and label the studio. The round is still that player's round, not a shared crash flight.
Each reveal can be its own step in the round. Some clients debit the stake up front and then only credit the cash-out. Others move money as the player continues. Read the wallet trace for the title you enabled before you write the help text. A generic 'one debit, one credit' sentence is how mines disputes get the wrong explanation.
What the round must store
A mines dispute is a grid, not a story
| Field | Why it has to be on the round |
|---|---|
| Grid size | A 5-by-5 board is not a 7-by-7 board |
| Mine count | Three mines and ten mines are different risks, even on the same art |
| Cells revealed | The player will point at a cell. You need the order |
| Cash-out step | The credit depends on how many safe picks happened before they stopped |
Product
Mines integration is mostly history quality
Show the count first
Mine count and grid size belong on screen before the first reveal. Hidden rules produce the cheating ticket.
Studio on the tile
A Spribe mines title and a BGaming mines title are different certificates. The art is not the identity.
Usually solo
The usual mines round is that player's grid. Do not describe it as multiplayer unless that specific game shares the board.
What a Mines API provider is selling
The studio sells a certified grid and a payout that rises with safe picks. You sell the lobby placement and the wallet that can answer the reveals. Neither of you needs a new contract per title if the studio is already enabled. You do need the market check, because some regulators treat very fast repeat-play differently from slots.
Auto-pick and random-cell features, where the client has them, are still that player's choices and should be stored as such. A player who says they did not pick a cell may have tapped random. The trace answers it.
Merchandising a mines title
- 01
Show the count
Display mine count and grid size before the first reveal.
- 02
Studio label
Name the studio. Mines-style titles are not interchangeable.
- 03
History
Store the mine count with the round id for disputes.
Store the mine count or the dispute is unwinnable
Mines titles sit in the instant catalogue and settle on the same wallet as slots and crash rounds. The extra field is the mine count. Without it, support is arguing about a picture.
The cash-out ladder, worked through
The round opens with the stake debited. Each safe pick moves the player one rung up the ladder that grid size and mine count certify, and a cash-out credits the rung reached. A mine does something harsher than end the winning streak: it forfeits the accumulated value as well. A player who picked four safe cells and stopped is credited the four-pick value; a player who picked four safe cells and then hit a mine is credited nothing at all.
That forfeiture is the fact that produces the angriest tickets, because the screen showed a rising figure the player felt they had earned. Say it in the help text before the first reveal, in one plain sentence, rather than after the complaint. The ladder itself is fixed by the certificate for that grid and mine count; if a build lets the player choose either value, the choice is part of the bet and belongs on the round record.
Support
Where mines tickets come from
Four symptoms cover most of the queue. Each has a record that closes it without an argument.
| Symptom | Usual cause | What answers it |
|---|---|---|
| 'It took my stake twice' | A reveal retried after a lost response and applied twice | The transaction-UUID dedupe on your wallet |
| 'My balance did not move between picks' | Client caching or a slow credit between reveals | The wallet trace for the round, call by call |
| 'I never clicked that cell' | An auto-pick feature or a misclick recorded as deliberate | The stored reveal order, and whether a random-pick feature was in use |
| 'The cash-out paid less than the screen showed' | The accepted value differed from the figure rendered at the tap | The accepted cash-out value on the round, not the screenshot |
Before a mines title is featured
- The debit pattern for this build: stake up front, or money moving per reveal. Read the trace of a live round rather than trusting the summary.
- Whether an auto cash-out on a chosen number of picks exists, and how the accepted value is recorded when it fires.
- Which grid sizes and mine counts the certificate covers; a preset the maths does not cover must not be selectable.
- Demo behaviour, confirmed against the demo-mode rules: no wallet movement, and a label the player can see.
- Contribution weighting if bonus play is allowed. Fast repeat rounds are why many operators weight instant titles down; see wagering contribution.
FAQ
Questions operators ask
Is the grid shared with other players?
On the usual mines title, no. It is that player's round. A shared crash round is a different format. Read the specific game before you describe it as multiplayer.
Can the player change the mine count after the first reveal?
No. The count is fixed for that round. A new count is a new round. If the client looks like it changed mid-round, treat it as a bug, not as a rule.
Does passing a crash load-test cover mines?
No. Mines reveals are a different call pattern from a shared crash cash-out. Test the title you are about to feature.
If a reveal request times out, is the pick lost?
No. A timeout means the answer did not arrive, not that the pick failed. Dedupe on the transaction UUID returns the first decision, the same behaviour described in the idempotent debits guide. Never let an agent re-send the reveal by hand.
Does auto cash-out exist on mines?
On some clients, as a target number of safe picks. As with a crash auto cash-out, it is a request the studio accepts on its own clock, so the credited value is the accepted one. Store the target and the accepted value both.
Can the player recover part of the stake after hitting a mine?
The usual rule is that a mine ends the round and the ladder value built so far is forfeited with it. Read the specific title's rules before writing the help screen, and state the forfeiture plainly rather than leaving it to be discovered.
Keep reading
Related pages
- Product · Instant gamesInstant gamesCrash, mines, plinko and instant-win titles settle on the same wallet and GGR report as slots, at a faster debit rate per minute.Read
- Studio · SpribeSpribeSpribe's Aviator and other turbo rounds debit the wallet more often than a slot spin. Size limits and reality checks for that.Read
- Studio · BGamingBGamingBGaming slots such as Aloha King Elvis and Bonanza Billion, plus instant titles in the mines and plinko style, all on one wallet.Read
- Catalogue · PlinkoPlinkoPlinko drops a ball through pegs into multiplier buckets. The player picks the risk row before the ball is released, not after.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.