All versions
1.4.1
Release
Souls Mod - 1.4.1last month 89
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
26.1.x - Medium Version Update - 1.4.1
Ghost Mode Changes
- Players in Ghost Mode can no longer see further than 32 Blocks when phasing through blocks to prevent them from finding structures and hidden bases
- Players in Ghost Mode can no longer open/view any containers
- The Colored Vignette effect has been toned down in intensity
- Improved Vignette/Blur effect accuracy based on depth/width
Corrupted Soul Changes
- The "main" Corrupted Soul user now Corrupts Players when using the Soulrender rather than stealing their soul
- The "main" Corrupted Soul user can place Corrupted Players Souls in Soul Lecterns and Shulker Boxes (Shulker Boxes holding Corrupted Souls cannot be stored into containers)
- Corrupted Soul Items are now destroyed upon the Players death or upon their cleansing
Soul Ingot Changes
- Soul Ingots can now be used to give your Armor Trims a Unique new color!
Soul Template Changes
- The Soul Template now takes 30 minutes to craft compared to 60 minutes previously
Souldex Changes
- The Souldex is now craftable using a Book (or Book and Quill) and a Bone
- The Souldex has gotten a new texture!
Added REI/JEI Support
- You can now view Soul Altar recipes when using REI/JEI!
Compatibility Changes
- Fixed a few inconsistencies in Recordings using the Flashback mod
Bug Fixes
- Fixed a bug where Players in Ghost Mode would sometimes be able to properly travel through blocks on the vertical axis
- Fixed a bug where Players would see 'Corrupted' as their Soul-type within their inventory in Ghost Mode, rather than it reverting to their original Soul
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:oMMuAlhQ:DYdb7pfz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oMMuAlhQ:DYdb7pfz"
}

