Tags
Creators
Details
All versions
2.0
Release
v2.04 years ago 5,154
Compatibility
Minecraft: Java Edition
1.19–1.19.3
1.18.1–1.18.2
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Unavailable version
Unavailable version
Changes
A few things first;
- Thanks for all the support since I released this project!
- v2.0 is (by far) the biggest update so far, which is why it has taken so long. Among other things, I moved the entire mod over to .lang files from hard coded text, which means that it can now be (somewhat) easily translated.
- Thank you to everyone who has reported bugs or suggested balances. Because of you, I have been able to make changes I never would have been able to find/think of alone. Please continue to do so on my GitHub.
- There is now a wiki listing all origins and their powers. This will (hopefully) be reworked at some point into a graphic which will also be posted here on Modrinth.
- Origins++ now has a CrowdIn page if you would like to help translate the mod to another language
- Going forward, I plan to release more frequent, smaller updates to get bug fixes and balances out to you sooner.
Release Highlights:
- Many missing assets have been added, which should make playing the Automaton, Deathsworn, Ebon-Wing, Emblazing Warrior, and Technomancer more enjoyable
- A lot of internal renaming has been done, which should make navigating the config easier
- Several origins have been reworked, notably: Blob, Dark Mage, End Mage, Illusioner, Light Mage, Manipulator.
- The Voidborne origin has been changed to the original, which means that it now has three tiers: Voidling, Voidborne and Supreme Voidborne
- Many origins have been balanced to make the overall experience better
- Many, many bugs have been fixed
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:npBe7UbS:YCZ0jQZo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:npBe7UbS:YCZ0jQZo"
}

