1.0.1
Compatibility
Changes
🛠 Version 1.0.1 – "Loaded First, Serves All"
Released on: 15.05.2025
✨ Changes
The plugin is now configured to load before any other plugin, including critical ones like LuckPerms.
This ensures the MySQL JDBC driver is available before any plugin attempts to establish a database connection.
Adjusted internal plugin ID (aa_jsmysqlfix) to enforce priority loading order during server startup.
🐛 Fixes
Improved handling of .downloading files to avoid corruption during interrupted downloads.
More robust SHA-256 checksum verification for downloaded drivers, enhancing security.
📌 Note
This update is primarily intended for users who experienced issues with plugins relying on MySQL being initialized before the driver was available.
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:lHrMzA61:eh5hdN39"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lHrMzA61:eh5hdN39"
}

