All versions
1.0.3
Release
Link 1.0.36 months ago 24
Compatibility
Minecraft: Java Edition
1.21.x
Platform
Folia
Changes
New Features
- Multi-database support — SQLite, H2, MySQL, MariaDB, and PostgreSQL are all supported. Configure the driver in database.yml.
- H2 as default database — Zero configuration needed. Just start the server and it works out of the box.
- Runtime library downloading — All external libraries are downloaded from Maven Central on first startup and cached in plugins/link/libraries/. Plugin JARs are now ~90 KB instead of ~30 MB.
- Configurable log levels — Control HikariCP and JDA log verbosity from config.yml under the logging section.
- Graceful startup without Discord token — If no token is configured, the plugin logs a clean error and continues starting the database instead of crashing.
Improvements
- Detailed config comments — discord.yml and database.yml now include helpful comments explaining every option, including how to obtain your Discord bot token, guild ID, and role ID.
- Cross-database SQL compatibility — All queries use bound parameters for full compatibility across every supported driver.
- File-based databases in plugin folder — SQLite and H2 databases are stored inside the plugin's data directory automatically.
- Cleaner console output — Noisy HikariCP and JDA log messages are suppressed by default. Configurable via config.yml.
- Smaller, faster JARs — Heavy dependencies are no longer bundled. They're downloaded once and cached locally.
Bug Fixes
- Fixed Velocity startup crash — Resolved NoClassDefFoundError caused by Guice scanning JDA classes before dependencies were loaded.
- Fixed driver registration — Database drivers now register correctly across all platforms.
- Fixed Jackson dependency version — Corrected a version mismatch that caused download failures on first startup.
- Fixed file-based database pool settings — Connection pool size is correctly limited for SQLite and H2.
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:ovEUdskQ:dMDv99Ob"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ovEUdskQ:dMDv99Ob"
}

