Tags
Creators
Details
Licensed Apache-2.0
Published 3 months ago
Updated last month
All versions
1.1.0
Release
SoulSnatcher 1.1.03 months ago 23
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.5–1.21.11
Platforms
Paper
Purpur
Changes
New Souls
- Hoglin: 40% of damage taken from mobs is split into 3 instances which are then taken over time.
- Guardian: When not attacking for 1.5s slowly charge up your next attack for a total of +50% melee damage. Infused mobs shoot at you with lasers instead.
- Magma Cube: When taking fire or lava damage, resist and heal by 0.5 HP. Infused mobs automatically set themselves on fire when engaging in combat.
- Vindicator: When sprinting while in combat gain +10% Movement Speed and +10% Attack Speed.
- Evoker: When attacking a target follow up with a line of fangs to attack combat targets every 2.5s.
- Ravager: When taking melee damage unleash a roar which pushed nearby entities away.
- Allay: When holding an item in hand, automatically pull all similar items in a short distance automatically towards you.
Soul Adjustments
- Fireballs shot through mobs infused with a ghast soul no longer destroy blocks directly
- Adjustet the timeout for a Zombified Piglin Soul to lose its mark and imporved handling of rengaging and mobs out of sight.
Other Improvements and Fixes
- Fixed soul orbits on bigger entities like ghasts, they now get a greater orbit radius and the soul heads become larger to make them easily visible
- Mobs spawned from trail spawners or raids now are also infused with souls
- Killed player now also drop their bound souls
- Fixed an issue where players could see their own souls when changing between being invisible and visible
- Made soul vials craftable
- Fixed an issue where soul rewards could end up in a stale state and were never removed
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:UJgvRLbX:YVSiiOLr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UJgvRLbX:YVSiiOLr"
}

