Hi! I don't post that much in the competitive/policy side of the site, because I only seriously play a few formats, and I'm generally not that fussed about Pokemon tiering even when I disagree with the outcomes. But this whole debacle is actively bothering me, so I figure I should post my thoughts. I'm not the greatest ADV player in the world, but I'm at least competent enough to get to upper-mid ladder consistently, so the outcome here affects me directly. I don't have a problem with the Smogon tiering/suspect system, and I'm not saying that I should be entitled to a vote just because I write a wall of text about it. But I feel like the way this suspect is being handled is, at best, extremely disingenuous.
People involved with tiering in an official capacity, most notably the ADV council, have been vocal about
how very tiring it is to deal with Baton Pass. And I can sympathize: it's annoying having to deal with something you don't like repeatedly. But nobody held a gun to your head and forced you to take a leadership position in ADV. If you don't like making PR posts and running suspect tests, it sounds like you don't enjoy the main thing that councils do, so... why bother in the first place? Having a PR thread every 6-18 months to address some new gimmick tech is pretty typical for oldgens, right? Frankly I'm not sure why else we have a council -- is the ADV council doing a ton of other stuff in an official capacity? I mean that sincerely: if I'm missing a ton of behind-the-scenes work, let me know.
I want to be very careful here not to imply that the ADV council, tiering staff, or whoever else is somehow plotting against the ADV community. I don't think anybody is trying to do anything nefarious. But it's clear that the council has presupposed what the "right" answer to the suspect test is, and the normal process for holding a suspect test is being seen as a formality.
To be frank, I can see the anti-BP point of view. Why make incremental changes when we can just rip the bandaid off? But in this case, incremental change is absolutely the better option. ADV is a stable and very popular meta. Making large changes carries a big risk of messing with something that's working well. On the other hand, making small changes every 6 months and seeing how they go carries basically no downside. Even assuming that BP ultimately gets the boot, what's the rush? People are going to have to play ADV with AgiliZap for another 6 months? Boo hoo. The format has been going strong for over a decade now, heaven forbid we have another tournament with basically the same ruleset. ADV is the most popular oldgen by far, with double the ladder activity of the next highest (SM) and an order of magnitude more than anything after that. If it was in the kind of dire state that demands immediate action, it would not be the most popular and broadly well-regarded oldgen format.
But I guess it is seen as a Big Urgent Problem, because the whole process for this vote has been super rushed. The PR thread about the issue opened with a unilateral decision that the only option is axing SpeedPass. A week later we have a suspect, despite a complete lack of consensus in the thread, with unusually strict requirements for reqs. And the suspect period is only 10 days long, overlapping Christmas Eve through New Year's. So if you happen to have any preexisting plans for that period -- I can't imagine why anyone would! -- you've really only got a few days to grind out 40+ games.
If the suspect matched the
previous test -- two weeks, not during any major holidays, 1500+ elo -- would things turn out different? I dunno, maybe. I sure would like to participate, but unfortunately it's just too important that this 20-year-old game have all its meta issues solved
right now, holidays be damned.
I care a lot less about the outcome of the vote and more about the process being reasonably fair and democratic. I would rather play in a format with some annoying tech than a format where major lines of play are at risk of being eradicated because staff is vehemently against banning Sand Attack(???).