You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gigantamax formes and moves should not be included in the data files (they are not in the game data files, they are not formes/moves by that definition). PS has begun doing some work here, the most obvious being marking the 'formes'/'moves' as Nonstandard and adding Gigantamax: Yes to the importable. The following is all required:
support Gigantamax: Yes in imports (moveset_import.js)
Gigantamax should be a checkbox in the UI instead of a 'forme'.
Set import logic should switch to sets with gigantmax: true instead of the legacy -Gmax name approach
The main question is around moves - how should the Gmax version of a move be handled? This should probably block on PS implementing the Gmax data as a field on the base move.
The text was updated successfully, but these errors were encountered:
Gigantamax formes and moves should not be included in the data files (they are not in the game data files, they are not formes/moves by that definition). PS has begun doing some work here, the most obvious being marking the 'formes'/'moves' as
Nonstandard
and addingGigantamax: Yes
to the importable. The following is all required:Gigantamax: Yes
in imports (moveset_import.js)Gigantamax
from being special cased for inclusionotherFormes
hardcodes (in particular, Toxitricity/Urshifu) to remove the Gmax 'forme'gigantmax: true
instead of the legacy-Gmax
name approachThe main question is around moves - how should the Gmax version of a move be handled? This should probably block on PS implementing the Gmax data as a field on the base move.
The text was updated successfully, but these errors were encountered: