Duplication / Import with Optional Preservation of Multilanguage Data

[AerunDev]

As a User working on a multilanguage project,
I want to be able to preserve multilanguage data (names, trainer classes, plural forms, descriptions) when duplicating or importing certain entities (e.g. Trainers, Items),
so that I can reduce manual re-entry, maintain linguistic consistency, and speed up the creation of similar or recurring content.

This preservation must be optional and entity-type dependent, in order to avoid irrelevant behavior in certain cases (e.g. Pokémon).

Link to the Discord suggestion by Tyfa

Acceptance Criteria

• When duplicating or importing an eligible entity, one or more options are displayed allowing the user to choose whether multilanguage data should be preserved or reset.
• If the “preserve multilanguage data” option is enabled:
  • Multilanguage names are copied.
  • Multilanguage trainer classes are copied.
  • Multilanguage plural names (when applicable) are copied.
  • Multilanguage descriptions are copied.
• If the option is not enabled: The current behavior is preserved (multilanguage fields are empty or set to default values).
• The available options depend on the entity type: Entities for which multilanguage preservation is not relevant (e.g. Pokémon) do not expose this option.
• The flow remains simple and easy to understand:
  • No requirement to configure each language individually.
  • No unnecessary UI or logic complexity.

Identified and Relevant Use Cases

Trainers

• Duplicating Gym Leaders while keeping the same trainer class in multiple languages.
• Creating repeat battles against the same character while preserving localized names (katakana, Korean, etc.). May be not relevant because we'll implement Character database with version 3.
• Quickly creating variants of the same trainer without re-entering translations.

Items

• Duplicating TMs/HMs where only the number changes.
• Creating items with very similar descriptions (e.g. drop bags, reward items).
• Preserving multilanguage grammatical structures in item descriptions.

Non-relevant Use Cases (Excluded)

• Pokémon: duplication without preserving multilanguage names or descriptions, as this is generally not desired.