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
Pokémon Showdown! is exhaustive source of information about Pokémon games since gen III. It has two advantages over veekun:
Bigger community, meaning faster support for new games
Movesets include event moves
It would be great if our data-manager could support Pokémon Showdown! files as data sources.
For starters, it could use Pokémon Showdown! as only source of data. Eventually it should be able to read veekun data and add missing pieces from Pokémon Showdown!.
Pokémon Showdown! data is held in JavaScript arrays that are not readable by standard JSON parsers. It must be first transformed to JSON. See data-manager/data-source/js-to-json.sh in ac3d664 for one way to transform it.
Both Pokémon and move names differ a little between veekun and Pokémon Showdown!. Some way to transform names from one space to another must be found. Similar problem must be solved as part of Issue #9. It would be really cool if we could find a way to solve both without code duplication.
The text was updated successfully, but these errors were encountered:
Pokémon Showdown! is exhaustive source of information about Pokémon games since gen III. It has two advantages over veekun:
It would be great if our data-manager could support Pokémon Showdown! files as data sources.
For starters, it could use Pokémon Showdown! as only source of data. Eventually it should be able to read veekun data and add missing pieces from Pokémon Showdown!.
Pokémon Showdown! data is held in JavaScript arrays that are not readable by standard JSON parsers. It must be first transformed to JSON. See
data-manager/data-source/js-to-json.sh
in ac3d664 for one way to transform it.Both Pokémon and move names differ a little between veekun and Pokémon Showdown!. Some way to transform names from one space to another must be found. Similar problem must be solved as part of Issue #9. It would be really cool if we could find a way to solve both without code duplication.
The text was updated successfully, but these errors were encountered: