Just a bit more Favorite Pokémon Picker. After the last update, Torch commented suggesting the ability to choose whether to use male or female as the default gender when gender differences are not included. This sounded like a neat simple thing, and would address something that'd been kind of bugging me too about treating the male as the default, so I started doing it... and then immediately proceeded to run into a series of headaches with the implementation of it.

First it was how it interacted with the shareable lists (in order for your list to be shared correctly, we need the shareable list URL to include the default gender setting... and not just the default gender setting, but also the included forms and major only settings, since otherwise it wouldn't know whether gender differences were included separately); then I realized the results would be counterintuitive if you had the default female setting on and then went on to change the included gender differences setting; then I got preoccupied with trying to implement all that in a sufficiently tidy way for the generic open-source picker script (which I really have been meaning to update).

At any rate, the default gender setting has now been added, and the way it works is as follows:

• When you have picked female as the default gender, and a given Pokémon's gender difference is not included, the 'main' item that represents the species as a whole is displayed as female instead of male. It still represents the species as a whole, will be labeled with just the name of the species, and has the same shortcode as if the default gender were male.
• Regardless of which is set as the default gender, if a given Pokémon's gender difference is included, then the male and female form will show up as separate entries, with what would otherwise have been the default species entry now representing specifically the male form, similar to how it has always worked. However, because it seemed appropriate to the same spirit and had been bugging me personally, both will now be labeled with their gender: where previously, if you included all gender differences you'd see male Butterfree labeled as just "Butterfree" while the female Butterfree was labeled as "Female Butterfree", they will now be explicitly labeled "Male Butterfree" and "Female Butterfree", specifically when they are both included as separate items. (This should apply both to the image alt/title texts and to the written labels on the shareable favorite list page.)
• When you have picked female as the default gender on a non-untouched state and then change other settings in such a way as to add some gender differences to the Pokémon pool, you will be prompted for whether you want the current placement of the species to apply to the male or female. In other words, if you for instance already had the species entry for Butterfree (which is being displayed as female) on your favorite list, and then add gender differences which would make that entry represent the male Butterfree, the prompt allows you to swap it out for the female Butterfree, so that you will end up with female Butterfree in that spot on the favorite list while the male gets treated as a newly added form (otherwise, the Butterfree on the favorite list turns male, and the female is newly added). If the default gender is set to male, then it always works like it used to: the default Butterfree becomes the male, and the female is added as a new form.
• Similarly, when you have picked female as the default gender on a non-untouched state and then change other settings in such a way as to remove some gender differences from the Pokémon pool, you will be prompted for whether you want the generic species entry for those Pokémon to replace the male or female. For instance, if you already had female Butterfree on your favorite list and male Butterfree in your currently evaluating batch, then the prompt lets you choose whether you end up with the single generic displayed-female Butterfree entry on your favorite list or in your evaluating batch. If male is the default gender, this will always work like it used to work – the female Butterfree disappears and the male stays.

This isn't 100% ideal – there's still a certain asymmetry between the genders, but it would've been hell to make it completely symmetrical while still remaining backwards-compatible. I have been waffling on whether I should always give the prompts when you add or remove gender differences from the pool, rather than just when the default gender is female, but I really prefer to minimize that sort of thing, and the main purpose of the prompt is to make it very explicit what's happening if you do choose to have it modify your state to swap the male and female around, which there's basically no reason for you to do if you've got male as the default.

Anyway, this all came with a couple of other changes:

• As I mentioned, the default gender setting necessitated sharing the values of more settings with your favorite list link. That was probably a good idea anyway, since it allows it to be unambiguous exactly what forms you were including, rather than trying to guess based on your list (it will still try to guess as backup if there's no explicit shared setting).
• Since there were getting to be a lot of settings, I figured I'd try to organize them a little better. The picker's options are now split into three sets, "Display options", "Pokémon filters" and "Alternate forms", which should hopefully make it easier to find the setting you're looking for at a glance.
• Finally, I noticed I had the female partner Eevee from Let's Go listed as a Gen VIII form, but by now it's officially just been made into a regular gender difference for all Eevee, and being Gen VIII was inconsistent with how gender differences are otherwise always treated as introduced with the base Pokémon and would have required sharing even more settings with the favorite list just to determine which Eevee to display in case Eevee was on the list. All in all, I just figured I might as well treat it like other gender differences at this point and labeled it as Gen I instead.

Hopefully this all works smoothly as it should. Let me know if you have any issues, as always.

Comment on this - View comments