🌐 Multi-Language (i18n) System
Alya delivers full, native internationalization across 10 global languages with 100.00% key completeness, zero placeholder English, and zero disk hits after boot.
🌍 Supported Languages
| Code | Flag | Language | Native Name | Status |
|---|---|---|---|---|
en | 🇺🇸 | English | English (US) | Reference (4,272 keys) |
id | 🇮🇩 | Indonesian | Bahasa Indonesia | 100% Native |
jp | 🇯🇵 | Japanese | 日本語 | 100% Native |
jv | 🇮🇩 | Javanese | Basa Jawa | 100% Native |
ko | 🇰🇷 | Korean | 한국어 | 100% Native |
zh | 🇨🇳 | Chinese | 简体中文 | 100% Native |
ru | 🇷🇺 | Russian | Русский | 100% Native |
de | 🇩🇪 | German | Deutsch | 100% Native |
es | 🇪🇸 | Spanish | Español | 100% Native |
fr | 🇫🇷 | French | Français | 100% Native |
🔄 Setting Your Server’s Language
Server administrators can switch the server’s language using the /language command or via the web dashboard:
/language set code:id
/language set code:jp
/language set code:enTo view the currently active server language:
/language⚡ High-Performance Architecture
- In-Memory Locale Cache: All translation dictionaries are loaded into memory during client initialization. Resolving a translation key executes in sub-millisecond memory lookups with zero filesystem I/O.
- Real-Time Dashboard Sync: When language settings are modified on the web dashboard, changes sync to the bot runtime within 15 seconds through an automated Redis bridge.
- Fail-Safe Fallbacks: If a server selects an unsupported locale, Alya gracefully defaults to English (
en) without crashing or showing blank responses. - Category Defense: Dynamic UI builders (such as
/help) include sanitization guards that format category keys into human-readable titles, preventing internal translation paths (e.g.commands.help.categories...) from ever leaking into user chats.
Last updated on