Links
Tags
Creators
Details
2.5
Compatibility
Required content
Changes
Blackjack 2.5
Play at a table without typing commands: right-click a chair to sit down, bet from a chip menu, and sneak to leave. It also runs on 1.20 again and fixes cards getting stuck on tables.
Added
- Chairs: right-click a chair (or the table) to sit down, and sneak to leave. Mid-round, a second sneak confirms, so you don't lose a hand by accident.
- Chip betting menu, with a custom amount you type in chat.
betting.menu: chatkeeps the old chat buttons. - Turn timer (
game.turn-timeout-seconds, 30 by default) with a countdown above the hotbar. - Players who can't cover the table's minimum bet can't sit down.
- Tables are stored in
tables.ymlwith IDs. New/bj tables, and/bj removetable [id]. Existing tables move over automatically. /bj cleanup [radius]to clear leftover cards.- Players are offered the Playing Cards pack when they sit down. On 1.20.3+ it's layered on top of your server pack.
- Korean, Turkish and Russian translations (
language:inconfig.yml). %blackjack_table_id%placeholder.
Changed
- Supports 1.20 through 26.3. On 1.20 to 1.21.1 the cards need Playing Cards 1.2.
- Removing a table also clears its blocks.
- Cards are never saved with the world. Teleporting, dying or changing worlds takes you off the table.
- Bets on the table are refunded when the server stops.
stats.ymlis only written when something changed.
Fixed
- Wouldn't load on 1.20 servers.
- Cards could get stuck on a table for good.
- Cards at the west and north chairs were upside down.
- A winning double down only broke even, and busting then leaving refunded the bet.
- Stats were wiped on the first hand after a restart.
- A rejected
/bj settablevalue still applied, andmax-playersabove 4 broke the table. - Custom sounds, button hover text, and payout lines in other languages.
Upgrading
Replace the jar and restart. New options are added to your config and message files automatically. If you used GSit to seat players, the plugin now does it itself; set table.seat-players: false to keep GSit.
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:yCepom43:9V9xhMMo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yCepom43:9V9xhMMo"
}

