Closed h2o-DS closed 3 weeks ago
zukan translates to pokedex, I forget how much of that is able to be translated file name wise but you should incorporate where you can
zukan translates to pokedex, I forget how much of that is able to be translated file name wise but you should incorporate where you can
Everything except for the final NARC name can be translated, essentially
I only used zukan in reference to filenames, like how shinzukan and pl_pokezukan are currently implemented.
I don't love the data.json variable names I came up with though, so if you have a better idea than "trainer_scale_f" let me know. Maybe they should be in a "pokedex_data" list or something so their application is more obvious.
pokedex_data
I think this would be fine. I also wouldn't shy away from using names that are descriptive as possible, in general. The more obvious data files are to end users, the better.
Extracted data from application/zukanlist/zkn_data/zukan_list.narc
Individual pokemon data was appended to their data.json file
Body shapes were added as an enum in consts.pokemon
A make.py script was added to tool/scripts
Corresponding meson files were changed
prebuilt narc was deleted