Tags
Creators
Details
2.2.1
Compatibility
Changes
This update focuses on authentication reliability for mixed premium and credential setups.
Premium authentication now works consistently in both seamless and interactive flows, and fallback authentication preserves the correct provider context and result messages.
What's Changed
Fixes
- Premium: allow premium authentication to complete correctly in seamless mode
- Engine: preserve provider subject when switching to fallback providers
- Engine: keep provider-specific fallback denial results instead of showing a generic authentication failure
Full Changelog: https://github.com/whereareiam/Identica/compare/2.2.0...2.2.1
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:DDxUcAy9:zKFJzOJX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DDxUcAy9:zKFJzOJX"
}

