Links
Tags
Creators
Details
3.2.0
Compatibility
Changes
Notice 3.2.0
Highlights
- Added single-JAR support for stable Paper releases from 1.16.5 through 26.2.
- Added Korean and English administrator messages with
language: ko|enand/notice language <ko|en>. - Preserved legacy and hex color codes across the full compatibility range.
- Kept MariaDB work off the server main thread and retained failure-safe state updates.
- Added compatibility and database regression coverage.
Compatibility
Use the Java version required by your Paper release:
- Paper 1.16.5: Java 16
- Paper 1.17–1.19.4: Java 17
- Paper 1.20–1.21.11: Java 21
- Paper 26.1–26.2: Java 25
Existing commands, permissions, plugins/Notice data, YAML configuration, and MariaDB table names remain unchanged. No data migration is required.
Folia, prerelease/RC builds, and hot reload are not supported.
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:pCaYVbZF:7uAKyEBf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pCaYVbZF:7uAKyEBf"
}

