Customizing Evidence Bot Translations
Select English or Spanish in Evidence Bot, create a custom locale catalog, edit messages safely and understand the built-in English fallback.
Evidence Bot Translations
The core package includes readable translation files under locale/. You can use the included English or Spanish catalog, or create a custom catalog for your server.
Editable bot translations
Select a language
The core package includes readable translation files under locale/:
| File | Language | .env setting |
|---|---|---|
locale/en.json | English | LOCALE=en |
locale/es.json | Spanish | LOCALE=es |
locale/custom.json | Your own catalog | LOCALE=custom |
Set the desired language in the actual .env file, not just .env.example:
LOCALE=es
Restart the bot after changing the selection or editing a catalog. Startup prints the loaded language and filename. Existing Discord messages are not rewritten — only messages sent after the restart use the new language.
Customize messages
Copy an included file to locale/custom.json, then edit values under messages, keeping the English keys:
{
"messages": {
"Evidence recorded": "Evidencia registrada",
"Reviewer assigned": "Revisor asignado"
}
}
- Partial catalogs are fine — any entry you don't translate just uses English.
- Filenames accept letters, numbers, underscores, and hyphens, with an optional
.jsonextension. A path (with/or..) is not accepted. - Values must be non-empty strings of at most 2,000 characters.
- Whatever formatting you put in a value is what displays — it's preserved as written.
Payload text is still bounded to Discord's normal limits. An overly long custom translation can get trimmed the same way any other field would.
English fallback
A missing file, malformed JSON, invalid filename, or invalid messages object falls back to the bot's built-in English — not the editable locale/en.json file, which means a broken or accidentally deleted English catalog can't take the fallback down with it. Missing, empty, non-string, and oversized individual values fall back the same way, one at a time, rather than failing the whole catalog. The terminal reports whenever fallback text is used, so a partially-broken custom.json is visible in the console rather than silently showing English for everything.
Translation coverage
Catalogs translate shared embed headings, field labels, catalogued reply phrases, status displays, and next-step text. What they don't translate:
- Evidence text and notes inside code blocks
- URLs and mentions
- Ordinary field values (the actual reason, player name, etc. you typed in)
- Stored status keys, forum tag names, webhook intake field labels, slash command names themselves, exports, addon websites, and terminal diagnostics — these all keep their original format regardless of
LOCALE
Uncatalogued sentences remain in English. The included Spanish catalog doesn't yet cover every possible command sentence word-for-word.
Locale JSON files ship as plain, readable assets in the base package — they bypass JavaScript obfuscation and get the same checksum verification as other customer-editable files, so you can open and edit them directly.
For other maintenance tasks, see Evidence Bot Maintenance & Backups.