
Unstable SMP Scripted Plugin
UnstableSMP Plugin is a hardcore-style SMP plugin that combines immortality, death bans, and immersive proximity features. It adds intense gameplay with smart Totem handling, Wither death sounds, and fully configurable mechanics.
3.0
Compatibility
Changes
UnstableSMP v3.0 - Changelog ๐ Major Changes โ Persistent Nickname & Skin System
Nicknames and skins now save automatically when you disconnect Data persists between sessions and only resets on server restart Stored in nickname-data.yml for reliability
๐ง Settings GUI Improvements
Fixed all crashes and stability issues Removed nickname protection feature (incompatible with offline-mode) Death Sound simplified to toggle ON/OFF only (change sound in config.yml) Cleaner, more intuitive interface
๐ฎ Enhanced Command Support
Commands now recognize custom nicknames /tp, /msg, /kill, etc. work with changed nicknames Example: If you're "Dream", /tp player Dream works correctly
๐ Death Sound Updates
Removed in-game sound selector to prevent crashes Toggle ON/OFF directly in GUI Change sound type in config.yml More stable and reliable
๐ Bug Fixes
Fixed skin system crashes on offline-mode servers Fixed async errors when applying skins Fixed config null pointer exceptions in GUI Fixed death sound crashes after changing settings Improved Ashcon API integration for skin fetching
๐จ Features
Nickname System - Change your display name Custom Skins - Apply any Minecraft player's skin Immortality Mode - Admin-controlled invincibility Death Ban System - Hardcore-style death penalties Keep Inventory - Toggle inventory preservation Proximity Messages - Location-based join/leave/death messages Resource Pack Management - Force or optional resource packs Death Ban Bypass - Exempt specific players from death bans
๐ Notes
Requires Paper 1.21+ or compatible fork Works on offline-mode servers All data saves to plugins/UnstableSMP/ folder
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:FeAzfn41:dpl5koxd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FeAzfn41:dpl5koxd"
}
