Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 6 years ago
Updated 4 years ago
All versions
2.0.0-beta.10
Beta
2.0.0-beta.104 years ago 621
Compatibility
Minecraft: Java Edition
1.19
Platform
Quilt
Supported environments
Client and server
Changes
Version 2.0.0 - Beta 10
- Updated to 1.19
- Requiem is now a Quilt mod. You can install the Quilt loader from quiltmc.org. Also note that you now need Quilt Standard Libraries instead of Fabric API.
- You can now use a soul vessel to steal souls from wardens and withers, damaging them in the process (this does not allow possession)
- Rifts now need to be witnessed before players can teleport to them (simply right click them for that)
- Obelisk runestones now show how much power they get from the surrounding soul blocks
- Experience now stays with your soul instead of with your body when you split
- Experience accumulated while vagrant will now be added instead of overwritten when merging with a shell
- Fixed an incompatibility with the Collective library which was preventing any special item interaction during possession (most notably curing)
- Fixed soul rifts breaking in all sorts of ways
- Fixed possessed mobs going ZOOM when swimming with Origins installed
- Fixed splitting not respecting the
requiem:possessionKeepInventorygamerule - Fixed vagrant players activating weighted pressure plates
- Fixed possessed chicken outright flying instead of falling slowly
- Fixed reclamation displaying particles when applied by obelisks
- Fixed mob limbs moving twice as fast as they should
- Fixed possessed mobs picking up items on their own, fixing some duplication issues
- Fixed selected slot desync when merging with a shell
Supplementary resources
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:bYmqMxlQ:XG6NG9aX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bYmqMxlQ:XG6NG9aX"
}

