1.0.2
Compatibility
Changes
šØ v1.0.2 - Critical Database Fix
Highly recommended update for all users.
š§ What's fixed
Fixed a critical bug where the plugin would fail to load on restart due to a known sqlite-jdbc 3.49+ regression with timestamp parsing. All timestamp columns now use BIGINT epoch millis - dialect-independent, future-proof, and significantly faster.
āļø Migration
- Automatic. Existing databases migrate on first startup (Migration V4) - no manual action needed.
- Safe. All existing data preserved during conversion.
- Idempotent. Already-converted columns are skipped.
š¦ Update steps
- Stop your server
- Replace the old JAR with v1.0.2
- Start the server - migration runs automatically
- Look for
ā V4 applied successfullyin console
š¬ Issues? Join our Discord Server
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:YfzR3CbJ:R1QzGmrw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YfzR3CbJ:R1QzGmrw"
}

