Tags
Creators
Details
1.12.2-2.4.0
Compatibility
Changes
Version 1.12.2-2.4.0:
- Every living entity can have superpowers now
- Overhauled ability system (more info down below)
- Fixed crafted injection losing their NBT data
- Removed custom JEI information category, use JEI's one instead
- Added mouse scrolling in ability & karma GUI
- Added sound for equipping infinity stones in gauntlet
- Hopefully fixed CustomNPC hitbox this time
- Fixed harvest levels for material blocks
- Fixed vibranium block models
Information for addonpack makers:
Your addonpacks should still work and load, BUT you might need to fix some minor problems. The toggle power ability no longer defines its abilities anymore, you need to set the dependent abilities of each to the toggle power one. Additionally, the way of adding abilities in json files should no longer be done with an array anymore, but it can still work until we update to 1.13/1.14. There is also a new way of adding conditions to abilities (with a handful of new ones) but the old ones (for required abilities, superpowers, etc.) will also work (I'll update a NEH or an example pack soon to let you see the changes)
On the bright side, you no longer need to wait for us to update the wiki anymore. The new system allows us to auto-generate a html-file in the addonpacks folder, which holds all the information you need for EVERY ability loaded ingame. You should also keep in mind that the settings of abilities are no longer mandatory, they have a fallback value and you dont need to set the title or icon in every case.
After all, this new system might have some bugs, so we would appreciate if you sent them in #bugs. Because of that we won't put the new updates on Craftfall yet.
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:4h2aTE5G:2w0QaUab"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4h2aTE5G:2w0QaUab"
}

