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

Extension suggestions for CustomNamer #20

Open
ivanlonel opened this issue Jan 20, 2024 · 0 comments · May be fixed by #21
Open

Extension suggestions for CustomNamer #20

ivanlonel opened this issue Jan 20, 2024 · 0 comments · May be fixed by #21

Comments

@ivanlonel
Copy link

ivanlonel commented Jan 20, 2024

Hi. I thought of some extensions that could be useful (the names could be different, of course):

  • ConditionalStatNature: would print the stat nature only if it's different from original nature, empty string otherwise. The printed string could be something like "➔Adamant" or "(Adamant)"
  • ConditionalGender: would print "♀" or "(Female)" if female, "♂" or "(Male)" if male and an empty string if genderless. Maybe leave an empty string anyway if Nidoran, which already has the gender symbol in the name.
  • ConditionalNickname: would print the nickname inside parentheses or quotes if the pokémon is nicknamed, empty string otherwise. I know {Nickname} already defaults to the species name if the pokémon isn't nicknamed, but if the pokémon is in a different language it will print the species name in that language, while {(Species)Species} always prints it in English. So it could be useful to be able to do {(Species)Species} {ConditionalNickname} instead.
  • The Scale property could show the HeighScalar for pk8, pb8 and pb7, since this property didn't exist until Legeds Arceus and it gets its value copied from HeightScalar anyway when the mon is transfered to newer games. Alternatively, there could be a new extension (ConditionalScale or something) that takes Scale if available, HeightScalar as a second option and an empty string for pre-Switch saves.
@ivanlonel ivanlonel linked a pull request Jan 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant