Skip to content

Refactor Form handling #16

@lramati

Description

@lramati

Currently, anything defined as a separate form by the Game Master is imported into GoIV.
This needlessly raises the complexity and fragility of form detection and makes the manual drop-down needlessly long.

Some attempt should be made to filter forms that are mechanically identical (in terms of stats)
I'd appreciate feedback about how to handle it in the manual drop-down.
Currently, next to each option it names the form (e.g. Deerling - Spring Form, Deerling - Winter Form)
Should we now list all forms on the line? (e.g. Deerling - Spring/Winter Forms) I'm afraid this will make the lines too long.
If so, I assume it makes sense to filter costume form names?

Stretch goal: Add a generic no-evolve costume form where relevant so that the Power Up tab after appraisal doesn't suggest evolving pokemon that can't be evolved (e.g. Halloween Bulbasaur)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions