Tags
Creators
Details
0.7.101
Compatibility
Required content
Changes
Cosmere and related sub module mods are considered to be in an alpha state! You have been warned :)
-
: Merge pull request #152 from SoaringEaqle/develop1 Saves power states and removes keybind modifiers.
-
: Bug Fixes Fixes the issue with the toggle activation by checking the current mode of all manifestations. Fixes a bug where save states would be deleted after quitting a world by saving a copy as nbt data attached to the SpiritwebCapability. Adds a text pop-up to help show what is happening when saving and activating power save states.
-
: Reformating Signed-off-by: SoaringEaqle 158627775+SoaringEaqle@users.noreply.github.com
-
: Bug Fixes, Patchouli Pages Fixes bugs Gerbagel mentioned. Adds translation keys for all new keybinds. Separates dedicated activators into their own section. Adds patchouli guide pages on key binds
-
: Reapply "Merge branch 'develop' into develop1" This reverts commit e324649e49c8b383effe639aa148ae5f0b7e4bdd.
-
: Revert "Merge branch 'develop' into develop1" This reverts commit 645e5422f5fb35fb3346a3e89b13de832d10fac0, reversing changes made to 44934bd3f236cce77a8d765d9a12603cb596e1cc.
-
: Merge branch 'develop' into develop1
-
: Saves power states and removes keybind modifiers. Removes unappreciated modifier keybinds for individual activators Adds power save states. Power save states can be saved by holding the "save power save" key and pressing a hotbar slot key, while having at least one manifestation active. Power save states can be activated by holding the "activate power save" key and pressing the hotbar key tied to the power save you wish to recall. Future plans: Chat message when power save state is saved or activated Save state toggle, turning those powers back off after use.
-
: [Cosmere] Added config option for player metalborn rates
-
: [Sandmastery] fix incorrect attribute modify for overmastery
-
: [Cosmere] Added config to allow for single metalborn players and adjustable distribution between misting and ferring
-
: [Allomancy] Ignored comodification exception in entity scanning Should be fine
-
: [Allomancy] Make lines thread restart on crash
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:ohwrIsCO:aGWWDodq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ohwrIsCO:aGWWDodq"
}












