Skip to content

Update tiering banlist information #5

Description

@scheibo

The tiering banlists are woefully out of data, from about ~2020.

stats/stats/src/reports.ts

Lines 483 to 515 in 652db3e

const SKIP = new Set([
'pichuspikyeared', 'unownb', 'unownc', 'unownd', 'unowne', 'unownf', 'unowng', 'unownh',
'unowni', 'unownj', 'unownk', 'unownl', 'unownm', 'unownn', 'unowno', 'unownp', 'unownq',
'unownr', 'unowns', 'unownt', 'unownu', 'unownv', 'unownw', 'unownx', 'unowny', 'unownz',
'unownem', 'unownqm', 'burmysandy', 'burmytrash', 'cherrimsunshine', 'shelloseast',
'gastrodoneast', 'deerlingsummer', 'deerlingautumn', 'deerlingwinter', 'sawsbucksummer',
'sawsbuckautumn', 'sawsbuckwinter', 'keldeoresolution', 'genesectdouse', 'genesectburn',
'genesectshock', 'genesectchill', 'basculinbluestriped', 'darmanitanzen', 'keldeoresolute',
'pikachucosplay',
]);
const BL: {[tier in Tier]?: Set<string>} = {
UU: new Set([
'hawlucha', 'dracozolt', 'diggersby', 'durant', 'weavile', 'ninetalesalola', 'gyarados',
'primarina', 'venusaur', 'haxorus', 'aegislash', 'conkeldurr', 'gengar', 'scolipede',
'lycanrocdusk',
]),
RU: new Set([
'barbaracle', 'pangoro', 'shiftry', 'slurpuff', 'chansey', 'indeedee', 'raichualola', 'linoone',
'sharpedo', 'zoroark', 'lucario', 'reuniclus', 'sirfetchd', 'heracross', 'sigilyph',
]),
NU: new Set([
'slurpuff', 'scrafty', 'haunter', 'linoone', 'chansey', 'indeedeef', 'porygon2', 'tauros',
'exeggutoralola', 'sneasel', 'snorlax', 'zygarde10', 'tyrantrum', 'kingdra',
]),
PU: new Set([
'arctozolt', 'arctovish', 'silvally', 'noctowl', 'silvallyground', 'silvallyfire',
'silvallyflying', 'silvallyfighting', 'scyther', 'magneton', 'porygon2', 'basculin',
'hitmontop', 'silvallypsychic', 'silvallyelectric', 'silvallygrass', 'rotomfrost', 'orbeetle',
'butterfree', 'golurk', 'flapple', 'thievul', 'sawk', 'galvantula', 'silvallydark', 'exeggutor',
'mesprit', 'guzzlord', 'magmortar', 'zygarde10', 'kingler', 'absol',
]),
ZU: new Set(['silvallyelectric', 'thwackey', 'ludicolo', 'musharna', 'grapploct', 'swoobat']),

Ideally, we can pull this information from the PS data (@pkmn/data), but there are potentially some gotchas. I don't know that in all cases we have scenarios where a Pokémon gets added to the xBL tier (eg. UU -> UUBL). In some cases the ban is an ability ban or implemented by some other means in the rule table which might complicate things (though hopefully not)?

Like with many things (#4), these banlists should also likely be generation aware (tiering by usage only actually takes place on the most recent generation, but Smogon still likes to report what would have shifted in old generations had this not been the policy)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    statsIssue related to @pkmn/stats

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions