Tags
Creators
Details
1.5.0+26.1.2-fabric
Compatibility
Required content
Changes
v1.5.0 is a major update.
What's Changed
-
26.1 support
-
Table rules
Each table can now have its own set of house rules! Thanks VengeancePC for the inspiration.
The settings panel can be accessed with the "Rules" button on the seat management screen.Available options include Stacking (respond to +2 with another +2, or +4 with +4, passing cumulative draws to the next player) (On by default), Jump-In (play an identical card even when it's not your turn) (On by default), Seven Rule (playing a 7 lets you swap hands with another player), Zero Rule (playing a 0 rotates all hands in the direction of play), Draw Until Match (keep drawing until you get a playable card), Force Play (must immediately play a drawn card if it's playable), and Wild +4 Free Use (removes the "no matching color" restriction on Wild Draw Four).
Server operators can lock a table's rules with the
/minopp set_table_rules_fixedcommand. -
MinoBot
MinoBot can now be crafted in survival mode with a Mino++ Table, an Iron Helmet, and a Redstone Torch.
The underlying AI algorithm for MinoBots has also been improved. -
Redesigned action display
The HUD area that shows game events has been rebuilt from scratch, so that it is more compact and easier to read at a glance. -
Other changes
- Tables return to idle state after 3 minutes of inactivity once a game ends.
- YACL (YetAnotherConfigLib) is now a required dependency.
- Visual and audio tweaks.
- Spanish translation by @A-J-Mortimer in #18.
-
Bug fixes
- Fixed a network buffer issue that could occur with mods like NotEnoughBandwidth.
Full Changelog: https://github.com/zbx1425/Minopp/compare/v1.4.0...v1.5.0
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:4QitwNm0:wDe5lXCZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4QitwNm0:wDe5lXCZ"
}

