1.17.1
Compatibility
Required content
Changes
The casino boards stop moving items around your inventory. Playing Double², Mines, blackjack, coinflip or a crate could pull an item out of your inventory into your hotbar, and the min/max stake buttons could leave a ghost copy of themselves there. Both are fixed, and only the left mouse button works the boards now.
Download the jar matching your Minecraft version:
- Minecraft 1.21.11:
mclabs-addons-1.17.1-mc1.21.11.jar - Minecraft 26.2:
mclabs-addons-1.17.1-mc26.2.jar
Fixed
- Playing a casino game no longer moves items around your inventory. Every button on the Double², Mines, blackjack, coinflip and crate boards is a real click on the menu underneath, and Minecraft used to act out each click on your side before the server answered, the way it does in a real chest. In these menus that was wrong every time. A click lifted the button's item onto your cursor, which the board hides, and letting go of the mouse then dropped it on whatever slot was under it. That was often one of your own inventory slots, so the server picked up your item instead and put it back in the first free slot when the menu reopened, usually your hotbar. The min and max stake buttons were worse: they are a shift-click, which moved the button itself into your hotbar until the server took it back. The boards now send the click and leave the result to the server, and letting go of or dragging the mouse over a board does nothing.
- Only the left mouse button works the casino boards. Any button used to count as a click, so a middle-click out of habit, or a side button you have bound to something else, could invest or reveal a tile. The other buttons now do nothing over a board.
Full changelog: https://github.com/Jade-Cod/mclabs-addons/compare/v1.17.0...v1.17.1
Optional dependencies
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:W09tZtbv:TvV4x1ug"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:W09tZtbv:TvV4x1ug"
}

