Tags
Creators
Details
1.4.1.1
Compatibility
Changes
MCLocalAuth v1.4.1.1 — Velocity
Type: Update - Multi-language System
Date: July 4, 2026
Status: BÉTA ⚠️
File: MCLocalAuth-Velocity-v1.4.1.1.jar
✨ New Features
🌍 Multi-language System
All player-facing messages are now externalized into editable language files.
Included languages:
- 🇫🇷 French (
fr_FR) - 🇺🇸 English (
en_US) — default - 🇪🇸 Spanish (
es_ES) - 🇵🇱 Polish (
pl_PL)
Configuration:
language: "en_US" # Change to fr_FR, es_ES or pl_PL
Translated player messages (editable):
- Kick messages (first join, unauthorized IP)
- Bedrock kick messages (no color codes)
/authcommands (help, errors, results)- Discord embeds (authentication, status, admin)
- Discord slash command descriptions
- Bot activity text
Translated console messages (not editable):
- Startup messages (storage, Discord)
- Error messages (token, permissions, connection)
- Admin log messages (IP add/remove/reset)
- Update available notifications
Language files:
Files are generated on first startup in plugins/mclocalauth/messages/:
en_US.yml,fr_FR.yml,es_ES.yml,pl_PL.yml
You can edit these files to customize player messages.
ℹ️ Console messages follow the selected language but are not editable (built into the plugin).
🔄 Automatic Migration
- The
language:key is automatically added to the top of existingconfig.yml
📊 Compatibility
| Platform | Versions |
|---|---|
| Velocity | 3.3.0+ ✅ |
Java: 17+
🚀 Installation / Update
- Download
MCLocalAuth-Velocity-v1.4.1.1.jar - Replace the old JAR in
plugins/ - Restart the proxy
- The
language:key is automatically added toconfig.yml - Change the language if needed (
fr_FR,es_ES,pl_PL) - Language files are in
plugins/mclocalauth/messages/
🐛 Known Issues
No known bugs at this time.
Build: Maven 3.9.5 + Java 17
Status: BÉTA ⚠️
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:znkt8N7X:rBzQymEf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:znkt8N7X:rBzQymEf"
}

