Tags
Creators
Details
4.16.15-beta.6
Compatibility
Changes
StackReference Breaking Change
StackReferences Identifier is Nullable now when the specified parser is not available (e.g. when a third-party plugin isn't available), or the parser fails to parse the item.
To reflect those changes, the StackReference#identifier() returns an Optional instead, and you may fall back to StackReference#originalStack when it is not present.
Changelog
- #69 — Optional StackReference Identifiers
4da9339c— Fix NullPointerEexceptions in StackIdentifiers & prevent possible NPEs. This fixes & prevents NPEs in:- EcoStackIdentifier
- ExecutableBlocksStackIdentifier
- ExecutableItemsStackIdentifier
- ItemsAdderStackIdentifier
- MMOItemsStackIdentifier
- MythicMobsStackIdentifier
- FancyBagsStackIdentifier
Full Changelog: v4.16.15-beta.5...v4.16.15-beta.6
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:l1d4bZ1h:AevL8YYo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:l1d4bZ1h:AevL8YYo"
}

