1.1.0
Compatibility
Changes
NotMines v1.1.0 — Compatibility & Polish
This release modernizes NotMines with wider Paper compatibility, refreshed interfaces, safer configuration updates, and additional customization.
Highlights
- Expanded compatibility target from Paper
1.20.xthrough26.x - Refreshed the game, stats, and leaderboard interfaces
- Reworked default messages with cleaner formatting and colors
- Added configurable layered sounds for leaderboard navigation
- Added automatic configuration versioning
- Added a detailed startup banner with version and integration information
- Improved comments throughout
config.yml,messages.yml, andgui.yml
New Configuration
- Toggle bStats metrics
- Toggle safe-pick chat messages
- Toggle board-close reminders
- Require both a minimum multiplier and payout for big-win announcements
- Toggle big-win announcements in the console
- Configure sounds for opening, filtering, paging, and closing the leaderboard
- Use Bukkit sound names, namespaced sound keys, or custom resource-pack sounds
Fixes
- Configuration errors during startup now disable the plugin cleanly instead of leaving it partially enabled
- Configuration migration and file-writing errors are now handled properly by
/mines reload - Existing configuration values are preserved when new defaults and comments are added
- Configurations newer than the bundled version now produce a warning instead of being silently downgraded
- Sound loading no longer depends directly on version-specific Bukkit sound enums
- Low-value wins can be excluded from global announcements
- Release builds now consistently target Java 17 bytecode
- Added tests for bundled YAML files, configuration versions, GUI materials, sounds, permissions, and the API baseline
Important Upgrade Notes
Public identifiers now use the shorter nmines namespace.
Update permissions:
notmines.use→nmines.usenotmines.stats.others→nmines.stats.othersnotmines.admin→nmines.admin
Update PlaceholderAPI placeholders:
%notmines_*%→%nmines_*%
Player statistics and customized configuration values are not reset by this update.
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:gBOp9Vun:W0FC9egM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gBOp9Vun:W0FC9egM"
}

