LRPGM · Skip to content / Ir para o conteúdo / Lewati ke konten
Help Center articleTranslation

Translation and review

Configure languages and provider

Choose a target language and translation service for the project and account.

Engine: MV · MZ · XP · VX · VX Ace

Access: Free · Basic · Plus

Available options depend on the app version and your account access.

Official content by LRPGM

Objective: Choose a target language and translation service for the project and account.

Applies to: An eligible translation workflow that uses a provider. Revise of an existing translation does not require a provider. Free uses automatic source detection; Basic has simplified selection; Plus has advanced groups and forced-source options. App language, plugin menu language and translated game text are separate settings.

Before starting: Have a connection and any credentials required by the external service. Integration does not include external credits, subscriptions or a guarantee of language coverage.

Steps

  1. Open translation configuration for the added game.
  2. Check that you are starting a new translation or an eligible update. To edit an existing result with Basic/Plus, use Revise.
  3. Select the target language and check its code when regional variants exist.
  4. Check the source options available to your plan. Only force sources or change language groups when you know which text belongs to each source.
  5. Choose an enabled provider. Google V3 [LRPGM] and Google Old are available in all three plans; Bing, Azure, DeepLX and DeepL Free/Pro require Plus online.
  6. Enter and save service-specific keys, endpoints or other settings where requested. Use the offered connection test; success does not guarantee every subsequent translation will finish.
  7. Confirm that the provider accepts the language pair. Inclusion in the LRPGM catalog does not establish support by every provider.
  8. Confirm the configuration and select content.

Expected result: The target and provider are configured with required credentials. Confirm translation output after processing.

If it fails: Distinguish invalid credentials, unsupported language pair, network failure and service quota. Never publish your key when requesting help. Changing provider can change cost and results. Google V3 [LRPGM] is not Google Cloud Translation API. Local LLM translation is disabled; installing models or CUDA does not enable it.

Content that complements this guide and helps with the next steps.

Need help?

Didn’t find the answer in the articles? Get in touch and tell us what happened with your project.

You can change your choice anytime in the footer. Your preference stays in this browser for up to a year.

About cookies and storage
Configure languages and provider | LRPGM