Creators
Details
Licensed ARR
Published 5 months ago
Updated 2 months ago
All versions
1.1
Release
Ludka 1.12 months ago 180
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Changes
Fixed
- Roulette could get stuck permanently if the world was reloaded while the wheel was spinning.
- Bets were lost when the world reloaded — chips were deducted but never given back.
- Chips reset to zero on death.
- Chips showed as zero after respawning until something else refreshed them.
- Players who walked up mid-round could not see the chips already on the table.
- Breaking a table no longer swallows the bets on it; they are refunded.
- The table model disappeared when its main block moved off-screen.
- The ball hung in the air at the start of a spin and stuttered on the way down.
- Russian translation did not load at all.
- Wrong or missing text in every language; several command messages printed raw placeholders.
- The chip item had no name and was missing from the creative tab.
- An old error message could reappear in the betting screen after a successful bet.
- Warnings and the win popup ran faster or slower depending on framerate.
- Pressing E while typing a bet closed the screen.
- The 1-18 and 19-36 buttons never highlighted on hover.
/chips balancerequired operator; now anyone can check their own balance.- Missing block model and a sound entry pointing at a file that does not exist.
Security
- A modified client could crash the server with a malformed bet packet.
- Bets could be placed on any table in the world without being near it.
Changed
- Chip balance is synced through the loader's attachment system instead of a custom packet.
- Chip rendering is significantly cheaper with many bets on the table.
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:50ZMVk31:Fs42q4Dc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:50ZMVk31:Fs42q4Dc"
}

