Tags
Creators
Details
All versions
1.10
Release
Version 1.10 - Gradient Styling and Readability Fixes6 months ago 768
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Modrinth Update Details
changes from versions 1.2 through 1.10 are listed here.
Version 1.2
- Added Java 21 support
- Added Paper 1.21.11 compatibility
Version 1.3
- Added support for modern dotted sound keys like
ENTITY.WITHER.SPAWN - Fixed deprecated sound API usage for better forward compatibility
- Fixed death sound resolution so both dotted modern keys and legacy underscore names work
Version 1.4
- Added configurable death sound range for nearby-only playback
- Added chat control modes for disabled chat and proximity chat
- Added configurable death punishments with kick or ban actions
- Added
/unstablesmp reloadfor reloading config changes
Version 1.5
- Added proximity-based join, quit, and death messages
- Changed the plugin and jar name to
UnstableSMPDeathSound - Changed the command namespace to
/unstablesmp - Fixed death kick/ban handling so the configured punishment runs correctly
Version 1.6
- Fixed the broken in-plugin immortality implementation ahead of the legacy-system restore
Version 1.7
- Added the full
/immortalcommand workflow - Added immortality config sections and persistent player data handling
- Fixed immortality behavior by restoring the legacy subsystem
Version 1.8
- Fixed the immortality command setup so it stays on
/immortalonly
Version 1.9
- Added small-caps styling for plugin-generated messages
- Added gradient styling for plugin-generated messages
Version 1.10
- Added a lighter indigo gradient for the
[UnstableSMP]prefix - Added a pink gradient for the rest of plugin-generated messages
- Fixed permission-denied plugin messages so they remain plain and readable
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:xY3B0rLE:SyHZxplV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xY3B0rLE:SyHZxplV"
}

