All versions
3.0.0
Release
Cobblemon Gamble 3.0.03 months ago 137
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
CobbleGamble 3.0.0 โ Crash & Plinko Update
Two brand-new animated games join the casino! ๐ฐ
๐ New Game โ Crash
- Bet, then watch the multiplier line climb smoothly from 1.00x and rising โ cash out before it busts!
- Live CASH OUT button shows your potential payout as it grows; win and it's yours, wait too long and it crashes.
- Auto-scaling graph, glowing tip, screen-shake + explosion on a crash, and a win burst on a cash out.
- Fair 3% house edge. Its own Crash Table + dealer, with live spectating.
๐ฏ New Game โ Plinko
- Drop a ball down a peg board and watch it bounce its way into a multiplier bucket.
- Choose your Rows (8 / 12 / 16) and Risk (Low / Medium / High) โ edges pay big (up to ~1000x), the center pays small.
- Smooth, slow ball physics with a little bounce off every peg; buckets flash on the landing.
- Drop balls back-to-back. Fair 3% house edge, its own Plinko Table + dealer, with live spectating.
โจ Improvements
- Balance no longer spoils the result. Across all games, your balance and Last Win now update when the result reveals (the ball lands / the line stops / the wheel settles) instead of the instant you bet.
- Plinko bucket multipliers are now fully readable โ big values compact to
1kstyle and always fit inside their tiles.
๐ Everything else
- Both new games feed
/gamblestatsand the stat leaderboards like the rest. - Each has its own configurable max bet (
maxBetCrash,maxBetPlinkoinconfig/gamblepokemon.json).
That's 7 games total: Roulette, Blackjack, Poker, Coin Flip, Pokรฉmon Race, Crash, and Plinko.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:u4fOOHc8:if7CvPqw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:u4fOOHc8:if7CvPqw"
}

