Translate plugin files and global chat.
Translate English plugin files for a multilingual server, and let players read global chat in their own language.
- Plugin files: choose several target languages per command, or translate loaded plugins in bulk.
- Global chat: translate messages for players with permission who have enabled translation.
- File checks and backups: JSON keys and recognized placeholders must be preserved; existing targets are backed up before replacement.
Oxide + Carbon · BetterChat optional · Own OpenAI key required. The Pro purchase and API usage are separate costs.
Illustrated chat example. Global chat only. Both players need chat permission and /ait.chat on. If translation fails, the original message is delivered.
What will the API cost?
Estimated API costs in USD.
| Usage | GPT-5.6 Luna | GPT-6 Luna |
|---|---|---|
| 1 file → 1 language | 0.0028 | 0.0012 |
| 10 files → 3 languages | 0.084 | 0.036 |
| 30,000 chat translations / month | 2.16 | 0.96 |
Open PimpMyRust to estimate file or chat costs →
Files: 2,000 input + 2,000 output tokens per file and language. Chat: 120 input + 40 output tokens per translation, with 1,000 eligible messages/day × one target language × 30 days.
For each chat message, players sharing a target language share one translation. Additional target languages add requests.
Standard USD prices, 18 October 2026. Actual costs depend on token usage, model and retries; taxes and extra reasoning are excluded. No cache or Batch discount is assumed. Pricing: GPT-5.6 Luna · GPT-6 Luna.
Configure and translate with PimpMyRust
Illustrated overview based on the PimpMyRust interface.
- Visual configuration: edit settings in guided fields, import existing JSON and export your configuration.
- Server sync: load your server's configuration, edit it in the browser and apply changes to your connected server.
- File translation: open a plugin's language files from its configuration and translate its English messages into your chosen languages with Pro on your server.
- Cost estimates: estimate file translation before sending a request. Use the chat-cost simulator to compare message volume, length, target languages and time period.
Server features require a signed-in account and a configured server connection. Translation requires Pro and your own OpenAI key with credit.
Browser file translation requires Pro 1.1.3. Cost estimation also works with Pro 1.1.2.
Which edition fits your server?
| You need… | Free | Pro |
|---|---|---|
| Plugin language files | One target per command | Several targets per command |
| Bulk loaded plugins | — | Yes |
| Global player chat | — | Yes, after activation |
| Oxide / Carbon | Yes | Yes |
Choose Pro for several languages, bulk work and chat. Only translating an occasional file? Free covers that workflow. Run one edition at a time.
Start with one plugin
-
Install
AITranslationPro.csand configure your OpenAI key, model and limits. - Run from server console/RCON:
aitpro.translateplugin MyPlugin fr de
On Oxide, the English source is oxide/lang/en/MyPlugin.json; Carbon uses its own language directory. Check the French and German output files before using them with players.
Enable global chat for a group
From server console/RCON, grant chat permission to your group, for example default:
oxide.grant group default aitranslationpro.chat.use
Each player who wants to send and receive translated chat also runs this in game:
/ait.chat on
/ait.chat off disables it; /ait.chat status checks activation. The recipient's Oxide/Carbon language setting determines the translation language.
Bulk commands, access and limits
ait.translateallplugins fr de
Processes loaded plugins with English files, subject to queue and usage limits. Check results and retry skipped work. MaxBulkPlugins caps plugins considered, not successful translations.
The historical ait.translateplugin alias has the same arguments as aitpro.translateplugin. File commands require server console, RCON, Rust administrator access or aitranslationpro.admin for a trusted operator.
Checks cover JSON structure, exact keys, string values, recognized placeholders, completion and size. Existing targets are backed up; unresolved recovery files can block replacement. Review translation accuracy yourself.
Local request/token limits control workload, not a currency spending cap. Selected file contents or eligible global-chat messages are sent to OpenAI. API keys, chat contents and provider response bodies are not written to plugin logs.
Requirements: Rust with Oxide/Carbon, your own OpenAI key with credit, English source files for file translation. Pro takes priority if Free is also installed.
