• Follow our Instagram!
  • Curious about what we're currently doing about bots? Check out the latest updates from staff in this thread.

Proposal Allow Sorting Pokémon in the Teambuilder by Usage

Are you in favour of allowing Pokémon to be sorted by usage in the Teambuilder?

  • Yes

    Votes: 54 67.5%
  • No

    Votes: 10 12.5%
  • Indifferent

    Votes: 16 20.0%

  • Total voters
    80
  • Poll closed .

Hydrametr0nice

Simulator Developer
is a Programmeris a Pokemon Researcheris a Battle Simulator Moderator
Hi. Yesterday, I opened a PS suggestion thread proposing the ability to sort Pokémon entries in the teambuilder by their usage rate from the previous month. This option would only appear for formats that actually have usage statistics and exceed a minimum battle threshold (for example, 1,000 battles). One open question was whether we should also display the usage percentages directly in the builder.

This was initially a simple PS-only matter, until Marty pointed out that the top 6 Pokémon appearing at the top of the builder have their usage rates slightly skewed. Because of that, the suggestion should go through a Policy Review thread before being implemented.

Since I support this implementation, here are some arguments for why it would be a beneficial change and why it would not create any significant additional problems:
  • All of this information is already publicly available and presented in a user-friendly way on websites such as Pikalytics.
  • For most formats that use or have used usage-based tiering, sorting by usage rate is essentially an extension of sorting by tier, but with greater granularity.
  • For new players, choosing not to implement this change means leaving an unnecessary barrier to entry in place. The information is already available and provided by PS! itself.
  • This change would be useful while building teams, not only when choosing Pokémon, but also for understanding which Pokémon you should prepare for the most.
  • The current tier-based + alphabetical ordering would remain the default. Users would simply have an additional option to sort entries by usage rate.
  • Regarding usage-rate skewing, while alphabetical ordering slightly increases the usage of Pokémon whose names start with letters such as A and B, this change would instead slightly increase the usage of Pokémon that are already the most used. However, these Pokémon are generally not at risk of dropping to a lower tier. Therefore, aside from reducing the usage of other Pokémon (something that already happens with alphabetical ordering), the effect would shift a bit to the Pokémon that are already the most used, rather than on Pokémon whose names happen to start with letters such as A or B.
In practice, the discussion essentially comes down to whether we're comfortable shifting some of the existing alphabetical-ordering bias to usage-rate bias, whether usage-rate bias could increase the overall amount of bias, and whether the benefits of this change outweigh these possible drawbacks.

That's it. Have a nice day.

Edit: It would use the 1630 usage files, and the 1695 files for OU and Doubles OU.
 
Last edited:
If it's just another sorting option, I doubt this would change usage much. Someone who picks a Pokémon because it's the first thing in the default sort probably won't change the sort. How many people are there who will pick the first mon they see, who would instead change the sort and THEN pick the first mon they see, given the option?

Even if that isn't the case, I still think it's worth doing. Unless we randomize the default sorting per-user, some mons are going to be advantaged. It's not clear to me why alphabetical bias would be more desirable than usage bias. And usage ordering would be convenient to have.

I wonder if there would be support for having the default list be ordered randomly? That would eliminate bias entirely. I don't really think this is an issue, but if people want to get rid of it, there is a way.
 
seems like a pretty harmless addition tbh. Would prob prefer if this becomes the default option cause that would make sure certain pokes like azu and arcanine in their respective tiers get used less and such, but considering smogon hates changing the norm even if its for the benefit, that would be too much of a hassle.
 
Blizihguh said:
I wonder if there would be support for having the default list be ordered randomly? That would eliminate bias entirely. I don't really think this is an issue, but if people want to get rid of it, there is a way.
For someone that only uses the teambuilder once in a blue moon, even I would find this to be a nightmare to find stuff without searching directly. I don't think this is worth it for the usability cost.
fiish said:
If this gets added, could an option to sort the teambuilder by VR ranking also be added?
This should probably be in a separate PS suggestion thread as VR rankings are not already in PS code and would require some sort of manual inputting, as parsing those is unlikely to be a viable method.
 
Kalalokki said:
For someone that only uses the teambuilder once in a blue moon, even I would find this to be a nightmare to find stuff without searching directly. I don't think this is worth it for the usability cost.
Not sure if I'm reading this correctly, and I'm mostly neutral on the matter of randomizing the list of mons provided the option to sort remains -- two intuitive clicks and you back to alphabetized sorting -- but how do you play the game if you never use the teambuilder, and doesn't not using the teambuilder kind of disqualify your position? Unless you're a randbats player who finds breaking into building prohibitively difficult due to builder illiteracy, this fundamentally changes nothing and negatively affects no one? I'm trying to understand why never using the builder better qualifies this kind of opinion than using the builder like your life depends on it.

Ftr, I think it would be annoying to learn something new, and I would like the option to preset my builder menu to alphabetized -- or at least for the builder to remember what I last set it to -- because I build hundreds of teams in bursts, and it would be annoying to have to search for the mons every time I'm in the mood to build, several dozens of times in a short span, particularly on mobile. But those are just my two cents.
 
Reiterating Kalalokki's points:
  1. Sorting randomly is a very poor design choice. Respectfully, I don't think that idea is even worth entertaining.
  2. While VR ranking would be possible, it should be discussed in a separate thread. It would require some manual input and a way for TLs to modify it. Putting the responsibility for updates on developers every time a VR changes seems unfeasible.
Here are some screenshots of how the usage sorting could look. Usage only appears after sorting by "Tier/Use". If you click the header again, it goes back to alphabetical sorting. It doesn't make sense to sort incrementally by usage. In tiers with no usage data, the header only shows "Tier".
Default (sorted by tier-alphabetical)
1780736081765.png
Sorted by usage:
1780736109281.png
 
Last edited:
I’m honestly open to literally anything that doesn’t sort pokes by smogon tier. As someone who doesn’t play smogon tiers at all it is completely useless to me and actually can make finding the mons I want harder since they might move tiers and be in a different spot etc. it’s a small nitpick but genuinely anything whether it be class (legendary, sub legendary, etc) or usage within the tier being built for, I’m all for it.
 
Back
Top