Tags
Creators
Details
3.0.1
Compatibility
Required content
Changes
Identica 3.0.1 fixes players left without a prompt or reason on the auth server, join restrictions and recognition that went stale across the proxies of a cluster, and SQLite keeping the rows of deleted accounts, old password hashes included.
Upgrading
- Replace the plugin and provider jars; the configuration and the database need no changes from you.
- SQLite: the first start deletes the rows that deleted accounts left behind, such as provider profiles and the Credential password history with its old password hashes. From then on SQLite deletes them with the account, like the other databases.
Changelog
Fixes
- Authentication: Fixed two renames to one username at once failing with a storage error instead of reporting it taken (#254)
- Authentication: Fixed players getting no prompt while allowResume is off (#240)
- Commands: Fixed the 2FA reset reporting success for a unique id without an account (#228)
- Credential: Fixed passwords longer than 72 bytes failing registration with bcrypt (#231)
- Database: Fixed SQLite keeping rows of deleted accounts (#251)
- Migration: Fixed a move confirmed too late being reported as not pending instead of expired (#235)
- Recognition: Fixed a proxy recognising a player from an address their latest login no longer used (#247)
- Restriction: Fixed a lifted join restriction staying in force on the other proxies of a cluster (#243)
- Routing: Fixed players turned away by the completion server staying on the auth server without a reason (#225)
Full Changelog: https://github.com/whereareiam/Identica/compare/3.0.0...3.0.1
Support
If you need help with setup, configuration, or upgrades, join us on Discord. If you find a bug or want to suggest a feature, use GitHub.
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:7mTkb4OS:NJ9HqWI7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7mTkb4OS:NJ9HqWI7"
}

