Links
Tags
Creators
Details
Licensed MIT
Published 10 months ago
Updated 10 months ago
All versions
2.1.3
Release
SoulBind 2.1.310 months ago 36
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
SoulBind - Release Notes
🚀 v2.1.3 - January 2, 2026
✨ New Features
LuckPerms Integration
- Granular Permission System: Added 5 new permissions for fine-grained control
soulbind.admin- Full administrative accesssoulbind.reload- Reload configurationsoulbind.toggle- Toggle mechanics (reserved for future)soulbind.bypass- Survive global death eventssoulbind.notify- Receive admin notifications
- Non-OP Management: Staff can now manage the plugin without OP permissions
- Permission Hierarchy: Parent-child permission structure for easier management
Death Bypass System
- VIP Death Immunity: Players with
soulbind.bypasspermission survive global deaths - Protected Count Display: Shows how many souls were protected in broadcast message
- Bypass Notification: Protected players receive a confirmation message
- Smart Filtering: Only counts and affects players without bypass permission
Notification System
- Reload Notifications: Players with
soulbind.notifypermission get notified when config is reloaded - Shows Reloader: Notification includes who triggered the reload
- Targeted Messaging: Only sends to players with the permission (reduces spam)
🔧 Improvements
- Configurable Permissions: All permission nodes are now configurable in
config.yml - Better Permission Checks: Uses config-defined permissions instead of hardcoded values
- Enhanced Messages: Added 4 new message templates for bypass and notification features
- Plugin Size: Increased to 10 KB (from 8.9 KB) due to new features
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:rVnFvwsy:z6qQqbJv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rVnFvwsy:z6qQqbJv"
}

