Tags
Creators
Details
1.16.4-3.1.11-34
Compatibility
Required content
Changes
------------------------------------------------------
Version 3.1.11-34
------------------------------------------------------
- Fixed a crash on-launch from 3.1.11-33.
- Reworked and implemented the Potion Flask system! Quite a bit different than previous versions, so make sure to check the guide.
- New (and old) non-Vanilla potion effects include:
-> Bounce
-> Gravity
-> Grounded
-> Suspended
-> Heavy Heart
-> Passive
-> Hard Cloak
-> Obsidian Cloak
-> Flight
- Fixed server crash for the Reverence of the Condor ritual.
- Reimplemented Teleposers. Hurray!
- Reimplemented the Teleposition Sigil.
- Reimplemented the Sigil of Suppression.
- Reimplemented the Demon Pylon.
- Added Will Catalysts, which can be applied to Demon Will Clusters to dramatically increase their rate of growth.
- Changed the Hellfire Forge so that it can use Aspected Will in crafting operations.
- Modified the Ritual Diviner so that it can cycle through the ritual list backwards by left-clicking in the air.
- Added a new item, "Basic Routing Logic Upgrade", which increases the total throughput of the Master Routing Node's system.
- Reimplemented several rituals:
-> Crash of the Timberman
-> Dawn of the New Moon
-> Ritual of the Satiated Stomach
-> Speed Ritual
-> Ritual of the High Jump
-> Laying of the Filler
-> Gathering of the Forsaken Souls (reworked)
-> The Sinner's Burden (renamed from "Ritual of Grounding")
-> Mark of the Falling Tower (New meteor system! Oooh, sparkley~!)
- Added a new ritual, Yawning of the Void. Used to completely clear large areas of blocks.
- Tweaked recipe for Frame Parts to make them cheaper.
Optional dependencies
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:PbNc6qBY:6D9lsJNQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PbNc6qBY:6D9lsJNQ"
}

