6.4-26.2.x
Compatibility
Changes
๐ Version 6.4 โ 18 new languages
The plugin jumps from 12 to 30 supported languages in one go.
New languages
Western & Central Europe / Americas: Icelandic (is), Hungarian (hu), Romanian (ro), Czech (cs), Slovak (sk), Polish (pl)
Eastern Europe, Caucasus, Africa & Asia: Ukrainian (uk), Belarusian (be), Estonian (et), Latvian (lv), Lithuanian (lt), Serbian Latin (sr-latn), Bulgarian (bg), Georgian (ka), Swahili (sw), Indonesian (id), Japanese (ja), Korean (ko)
Notable choices
- Serbian: the Latin script (
sr-latn) was chosen over Cyrillic, since it's more common in everyday digital use, even though both have equal constitutional status in Serbia - Non-Latin scripts (Cyrillic for uk/be/bg, Georgian for ka, Japanese for ja, Korean for ko): no encoding or in-game rendering concerns โ all six are officially supported by Minecraft's own font system
- A few languages were considered and deliberately left out: "Australian" and "Canadian" English/French (already covered by
en/fr/fr-ca), "Mexican" Spanish (already covered byes), Guarani and Quechua (not part of Minecraft's own officially supported language list, which was the bar set for this batch)
Reliability
- Automated cross-check confirming all 30 language files share the exact same 36 keys, none missing
- The "invalid language" error message was shortened across all 12 previously-existing languages โ spelling out 30 language codes inline had become unreadable, so it now simply points to the plugin's Modrinth page for the full list
๐ท๏ธ Naming
- Minor version bump (6.3 โ 6.4) โ extending the existing language system, same pattern as v6.2
- Generated jar:
Waystone-6.4-26.2.x.jar - Like v6.0/6.1/6.2/6.3, this version only concerns the 26.2.x line
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:OHYwSMgX:BlNPvoJG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OHYwSMgX:BlNPvoJG"
}

