Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated last year
All versions
1.0
Release
Slotsmachine 1.1 (GamblingMachine)2 years ago 116
Compatibility
Minecraft: Java Edition
1.21–1.21.4
Platform
Paper
Changes
GamblingMachine - Changelog v1.0.0
🎉 Initial Release
✨ Core Features
- Implemented fully functional GUI-based slot machine system
- Added secure random number generation for fair gameplay
- Integrated Vault economy support
- Created animated spinning mechanism with sound effects
💰 Economy & Betting
- Added configurable minimum and maximum betting limits
- Implemented 7 different symbols with unique multipliers:
- Diamond (100x)
- Gold (50x)
- Emerald (25x)
- Iron (10x)
- Copper (5x)
- Coal (3x)
- Redstone (2x)
- Added weighted probability system for balanced gameplay
🎮 Commands
- Added
/slots <amount>command for players - Added
/slots helpfor multiplier information - Implemented admin commands:
/slotadmin reload/slotadmin stats
⚙️ Configuration
- Added comprehensive config.yml with customizable:
- Betting limits
- Symbol multipliers
- Probability weights
- Sound settings
- Custom messages
🎨 Visual & Audio
- Added spinning animation with progressive speed
- Implemented win/lose particle effects
- Added configurable sound effects
- Created custom GUI border design
🛡️ Security & Protection
- Added inventory protection system
- Implemented secure transaction handling
- Added permission system:
gamblingmachine.usegamblingmachine.admin
📋 Requirements
- Minecraft 1.21
- Vault
- Economy plugin (any Vault-compatible)
This is the first stable release of GamblingMachine. Please report any bugs or issues you encounter. Your feedback is valuable for future improvements!
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:yChmYYl6:Q4p1C5SV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yChmYYl6:Q4p1C5SV"
}

