- 📁 Create a new file in the
localesdirectory with the name of the language in the formatlanguage_code.json. For example,en-US.jsonfor English,ms-MY.jsonfor Melayu and etc. - 📋 Copy the contents of the
en-US.jsonfile into the new file. - 🌐 Translate the strings in the new file to the desired language.
- English (US) -
en-US.json(Default) - Indonesian -
id-ID.jsonby @iaMJ - Japanese -
ja-JP.jsonby @iaMJ (Not Accurate) - Polish -
pl-PL.jsonby @JellyTyan - Russian -
ru-RU.jsonby @JellyTyan
-
🔒 Do NOT translate or modify any text within double curly braces
{{}}. These are variables that will be replaced with actual values.- Example:
"{{prefix}}play"must stay as"{{prefix}}play" - Example:
"Page {{current}}/{{total}}"must stay as"Page {{current}}/{{total}}"
- Example:
-
🔗 Do NOT translate or modify markdown links
[text](url).- Example:
[here](https://discord.com/...)- translate only "here", URL must stay unchanged
- Example:
-
✨ Keep all formatting symbols like
**,*,\n, etc.- Example:
"**Hello!**"- translate only "Hello",**must stay - Example:
"Line 1\nLine 2"-\nmust stay for line breaks
- Example:
-
🎯 Keep the same JSON structure and keys, only translate the values.
{ "key": "Translate this value", "nested": { "key": "Translate this value" } } -
📝 Keep command names exactly as they are.
- Example:
/play,/help,/bassboostmust stay unchanged
- Example:
-
🚫 Do not add or delete any JSON keys - only translate the values.
-
✅ Make sure JSON syntax stays valid after translation.