Tags
Creators
Details
0.10.0
Compatibility
Changes
uxmEssentials 0.10.0
A server can now keep its players in its own language, and a staff member can set another player's language.
Requires Paper 26.2 on Java 25, same as 0.9.0.
Read this before you update
messages.default-locale becomes the language block. config.conf now carries this block, the same one every UXPLIMA plugin reads:
language {
default = "en"
follow-client = true
force = ""
}
Your old messages.default-locale keeps working. When the update appends the block to your file, your old value still wins over the shipped "en". If you write a default in the new block and it differs from the old line, the console warns you: remove the old line then.
A player's choice moves. /lang now keeps the choice on the player's own data under uxmlib:language. A choice saved under the old key is moved the first time the player is seen. Nobody has to choose again.
Languages (#2)
A server can keep its own language. Before, a player whose client read English read English, even on a server whose default was German. Now:
defaultis what a player reads when nothing else answers.follow-client = falsestarts every player in the default. They may still choose another with/lang.force = "de"puts everybody in one language, whatever they chose./langthen says so instead of changing anything.
One choice for every plugin of ours. A language chosen with /lang is read by every UXPLIMA plugin on the server, and a choice made in any of them is read here. uxmLang is not needed for this. With uxmLang installed, the choice also follows the player between servers.
Set another player's language.
/lang set <player> <language>/lang reset <player>
Both work for a player who is offline: the choice is kept and applied when they next join. Both need uxmessentials.lang.others.
Every new line is in all twelve catalogues.
Under the hood
- On uxmLib 0.163.0.
- The order a language is picked in lived in four places and now lives in one.
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:IpIrzRV9:RAk7yGrH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IpIrzRV9:RAk7yGrH"
}

