AI Translation (PRO) 1.1.2

TRANSLATE EVERY PLUGIN. CONNECT EVERY PLAYER.

AI Translation Pro expands the controlled translation workflow to several target locales, bounded bulk operations across loaded plugins and optional global-chat translation for consenting players. Every provider request remains subject to local validation, privacy and usage controls.

MULTI-LOCALE FILES. BOUNDED BULK. CONSENT-FIRST CHAT.

PRIVACY BEFORE CONVENIENCE

• Explicit consent — unknown consent or a storage failure is treated as opted out.
• Permission checks — both sender and translated recipients require aitranslationpro.chat.use.
• Global chat only — team and non-global channels remain unchanged, and a failed translation delivers the original message.
• Redacted diagnostics and local guardrails — tokens, translated content and provider bodies are not logged; chat size, locale fan-out, cooldowns and shared budgets remain configurable.

THREE WORKFLOWS, ONE CONTROL PLANE

1. Translate one installed plugin into several target locales with one administrator command.
2. Run a bounded bulk operation across loaded plugin language files.
3. Offer optional global-chat translation only to players who explicitly opt in.
4. Validate every file or chat response before replacement or delivery.
5. Keep queueing, rate, retry, bulk, chat and token budgets under server-owner control.

COMMANDS THAT SCALE

Use server console or RCON for paid translation operations. Translate one installed plugin into several locales, run bounded bulk work across loaded plugins, or let players manage their own global-chat consent.

aitpro.translateplugin MyPlugin fr de
ait.translateplugin MyPlugin fr de

ait.translateallplugins fr de
/ait.chat on | off | status

PRO EDITION AT A GLANCE

• Translate one plugin into several locales per command.
• Translate a bounded set of loaded plugins with MaxBulkPlugins.
• Provide opt-in global-chat translation with explicit player consent.
• Use native global chat or optional BetterChat formatting.
• Validate exact keys, placeholders, completeness and response size before file replacement.
• Share queue, rate, retry, daily and local token budgets across file and chat work.

Pro runs on Oxide or Carbon. AI Translation Free and Pro are separate, mutually exclusive editions; Pro takes priority automatically when both are present.

REQUIREMENTS

• Rust server running Oxide or Carbon.
• AI Translation Pro 1.1.2.
• An owner-supplied OpenAI API token with available provider credit.
• English source files under oxide/lang/en for file translation.
• BetterChat only when you want its optional formatting route.

SUPPORT AND RECOVERY

If file translation does not start, confirm the token, source file, authorization, enabled route, local limits and absence of unresolved recovery material. If translated chat is missing, verify global chat, stored consent and aitranslationpro.chat.use for both participants.

For support, include the Pro version, Oxide or Carbon version, BetterChat state, command or chat route and a redacted error code. Never share the OpenAI token, player chat or language-file contents.

CONFIGURATION THAT MATTERS

The server owner supplies the OpenAI token and remains responsible for provider availability, pricing and charges. Privacy, queueing, concurrency, request, chat and token budgets remain explicit and local.

{
  "OpenAIToken": "PASTE_TOKEN_HERE",
  "ChatConfiguration": {
    "Enabled": true,
    "Model": {
      "Model": "gpt-5.6-luna",
      "MaxTokens": 512
    }
  },
  "LangFilesConfiguration": {
    "Enabled": true,
    "Model": {
      "Model": "gpt-5.6-luna",
      "MaxTokens": 4096
    }
  },
  "Privacy": {
    "RequireExplicitConsent": true
  },
  "Limits": {
    "MaxQueued": 32,
    "MaxConcurrent": 2,
    "MaxRequestsPerMinute": 30,
    "MaxRequestsPerDay": 1000,
    "DailyTokenBudget": 500000,
    "MaxRetries": 2,
    "MaxChatCharacters": 500,
    "MaxChatLocalesPerMessage": 4,
    "ChatSenderCooldownSeconds": 5,
    "MaxBulkPlugins": 100
  }
}