Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle asymmetrical portraits correctly #176

Open
tech-ticks opened this issue May 22, 2022 · 0 comments
Open

Handle asymmetrical portraits correctly #176

tech-ticks opened this issue May 22, 2022 · 0 comments

Comments

@tech-ticks
Copy link
Owner

tech-ticks commented May 22, 2022

  • Unk. Bit1 in graphics flags seems to specify whether the Pokémon uses a different portrait when it's female. It should be named correctly in the UI.

    • What happens if the file name is changed for the female form in general (e.g. Raichu's female form uses raichuu instead of raichu_f)? I guess it might work too if the flag is not set?
    • Female portaits already work correctly, see e.g. Wobbuffet
  • Unk. Bit9 in graphics flags specifies whether the Pokémon uses asymmetrical portraits. It should be named correctly in the UI.

  • Add support for importing female and asymmetrical portraits. The file for asymmetrical Pokémon must be named {normal file name}_hanten.ab. Female forms are named {normal file name}_f_[hanten].ab, where hanten is appended based on whether it's also asymmetrical. (the combination of female + asymmetical isn't used in-game). This is due to a string hardcoded concat in ActObjCharactor_c_DisplayClass74_0__TryLoadAndInit_b__0:

image

@tech-ticks tech-ticks changed the title Handle female and asymmetrical portraits correctly Handle asymmetrical portraits correctly May 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant