
SharedSoul
Experience true cooperative survival where all players share health, hunger, inventory, XP, and death. When one player takes damage, everyone feels it. When one dies, all die together. Perfect for close-knit groups seeking the ultimate teamwork challenge.
1.2.0
Compatibility
Changes
SharedSoulSurvival Plugin - Update Highlights v1.2.0
Version: 1.2.0
Release Date: August 4, 2025
Hey adventurers! ๐
Weโve rolled out a big update to the SharedSoulSurvival plugin, and weโre excited to share whatโs new. This version brings smoother co-op gameplay, better synchronization, and fixes to the most frustrating issues reported by players. Letโs break it down:
๐ง Major Fixes:
-
Inventory & Block Interaction Now in Sync
- Player Two can now place and break blocks just like Player One โ no more ghost blocks or weird inventory glitches.
- Items are now correctly picked up, placed, or removed on both sides without duplication or disappearing acts.
๐ฏ Gameplay Feel & Feedback:
-
Damage Effects Are Now Shared
- When one player takes damage, both players now experience the same hit effects โ screen shake, knockback, and all.
- This makes the shared health system feel much more immersive and fair.
๐ Advancements Reimagined:
-
Shared Progression
- Unlocking an advancement? Your partner gets it too! No more lagging behind in progress โ youโre truly in this together.
โ Under-the-Hood Tweaks:
- Improved the way the plugin syncs world and inventory changes.
- Added extra protection against item duplication bugs and sync delays.
๐ Final Notes:
This update is a big step forward for the SharedSoulSurvival experience. If youโre running a server, we highly recommend updating to v1.2.0 for a smoother, bug-free adventure.
Thanks for being part of the journey. More magic coming soon! ๐ซ
โ Rocket Studio
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:sSiX0oB0:Cj8UFbnn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sSiX0oB0:Cj8UFbnn"
}
