Links
Tags
Creators
Details
1.3.1
Compatibility
Changes
๐ชช BedrockPassport 1.3.1
BedrockPassport 1.3.1 expands the localization system with automatic per-player language selection and fixes configuration migration for existing installations.
๐ Automatic player language
- Added automatic Bedrock client language detection for player-facing Passport forms and disconnect messages.
- Locale selection is scoped per connection, so players using different client languages can receive different Passport interfaces at the same time.
- Added
language.use-player-locale. - Added configurable
language.player-locale-fallback. - Disabling automatic detection preserves the previous
language.messagesbehavior. - Regional language variants are matched by language family where possible.
๐ฃ๏ธ New player-facing locales
Player-facing Passport flows now support:
en_USโ Englishru_RUโ ะ ัััะบะธะนuk_UAโ ะฃะบัะฐัะฝััะบะฐde_DEโ Deutsches_ESโ Espaรฑol
English and Russian remain the full administrator/config localizations. Ukrainian, German and Spanish currently focus on the player-facing Passport flow and fall back to English for untranslated administrator or console keys.
๐ LOCAL and JAVA_ACCOUNT coverage
Per-player localization is applied across both identity providers, including:
- account selectors and management forms;
- LOCAL identity creation;
- JAVA_ACCOUNT sign-in and re-authentication flows;
- allowlist denial messages;
- timeout and reconnect messages;
- duplicate-session/session-protection messages;
- fail-closed LOCAL identity handoff messages.
โ๏ธ Configuration schema v4
The configuration schema is now v4.
New settings:
language:
config: en_US
messages: en_US
use-player-locale: true
player-locale-fallback: en_US
๐ Config migration fix
- Fixed existing
config.ymlfiles not receiving newly introduced settings after a plugin update. - The migrator now distinguishes values actually stored in the user's config from bundled defaults.
- Missing settings and sections are written automatically.
- Existing administrator-defined values are preserved.
config-versionis now correctly persisted into the user's config.- Legacy timeout migration now checks the real saved configuration instead of bundled defaults.
- Configuration comments continue to be regenerated using
language.config.
You should no longer need to delete or recreate config.yml just to receive new settings after updating BedrockPassport.
๐ ๏ธ Administration
/bp status now also reports:
- whether automatic player language detection is enabled;
- the configured player-language fallback.
โ Runtime verification
Automatic player localization and the updated configuration migration flow were runtime-tested successfully.
The release version is 1.3.1.
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:xlbqOfvO:h4OGyRZE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xlbqOfvO:h4OGyRZE"
}

