Optional Move Pool Inheritance When Creating a Form

[AerunDev]

As an User creating a new Pokémon form
I want to choose whether the movepools of the base Pokémon should be copied
so that I can avoid manually removing inherited moves when the new form is intended to have a completely different learnset

Today, movepools are automatically copied from the base Pokémon when creating a form. While this is useful in many situations, it creates unnecessary work when the derived form is intentionally designed with a distinct move pool.

The goal is to make inheritance configurable at creation time while preserving the current workflow for the most common use cases.

Acceptance Criteria

• When creating a new Pokémon form, the user can choose whether movepools should be inherited from the base Pokémon.
• The option is enabled by default to preserve current behavior.
• If the option is enabled:
  • All current movepool data is copied as it is today.
• If the option is disabled:
  • The new form is created with empty movepool lists.
• Existing projects and workflows remain unaffected.
• The choice is presented clearly during form creation without introducing unnecessary complexity.

Identified and Relevant Use Cases

Relevant

• Regional forms with completely different movepools.
• Alternate forms designed around unique mechanics.

Not Prioritized / Out of Scope

• Fine-grained selection of which movepools to inherit.
• Templates for inheritance rules.
• Post-creation inheritance management.