(Oct. 31, 2021 11:08 AM)CrisisCrusher07 Wrote: (Oct. 31, 2021 3:23 AM)th!nk Wrote: Crisis, you were credited with a lot of this decision, so sorry if this sounds pointed. So far you've said you used double drift and lost via "lucky KO" - attack is a major drift counter and this new rule actually hurts it significantly. The inexperienced blader with a double strategy made only top 8 (which is easy enough to do with using a variety of non doubled lad drivers). You've talked about theoretical advantages but there's no numbers that show it being markedly better than using multiple different lad drivers etc and the game hasn't had enough time to see if this becomes a problem past what the hype will get people to try out.
I really do fail to see the problem this solves, let alone why a blanket approach is the best way to do so. As I understand it the wbba does not consider these parts the same, so why are we panicking so suddenly? I've never seen this sort of reaction to a WBO decision before - surely that should make the staff pause for thought whether they like the tone of the reaction or not? People complain about transparency and then this rule comes out of nowhere - I note it wasn't on the watch list - when much of the small debate around it was "come on wait and see if it's a problem".
The lucky KO I lost from was from another drift combo. I also fail to see how this rule hurts attack significantly. Most attack combos right now use either some variant of xtreme, destroy, or drift. And I have yet to see a deck use multible variants of xtreme or destroy. What I’m finding hard to understand as that if you go back through the winning combos page you rarely ever saw 2 variants of the same driver being used in deck combos. However, now with double drift and bearing being possible you are seeing more of that happening.
Yeah right now it’s early I get that everyone is saying that. But if within the past couple of weeks the amount of decks using double versions of parts is already increasing and being shown in the data, then maybe it really is a problem and this is just being foreshadowed. From when the products were released there have been 4 standard tournaments before this rule was placed. 3/4 of them had at least 1 person in the top 3 use this strategy. 1 was first, 1 was second, and 1 was 3rd. That kind of data shows that it really could become a problem.
Now I will say if most of the backsplash to this rule was coming from hasbro only players then I could understand why they would be upset. This rule really constricts the hasbro side of the game.
So you're saying Dr can be knocked out? Hm. So a deck full of Dr and Br would be quite prone to being swept by attack? Hm. Generally double drift and double bearing didn't appear because well... Uh... There was only one of each. Variants this similar being viable together are a recent thing due to changes in part design making non-dash more viable and limiting efficacy of slower attack drivers.
It has also only been of concern for a month and people are still experimenting.
Interestingly if this has changed with the introduction of MDr and Br'... Why are we hitting everything and not just them???
People definitely run MX+X', or at least, definitely can run it - this is how my deck was structured for when I get Perth going, Dan runs it in TO, off the top of my head. It's a very good setup if you expect to face a lot of spamina - and now spamina doesn't have to fear it so much, while they still get to run different drivers - Dr, Br', HXt+', Zn'+Z, Al (it works to a degree with a full force scrape launch), Nv... C'mon. On top of this - tell me why we *should* be hitting these things. Does the meta need less attack? Or are we perhaps not addressing the problem directly?
Destroy is pretty bad at the moment (it's woeful on guilty), so no one should be running one, let alone two. Jl' is hard to get and from what I hear kinda hard rubber so less accurate than X'/MX. Qc' isn't fast enough to handle Vanish sufficiently on Guilty or to do much at all on Savior. Ev' and V' are basically plastic. Meanwhile the variety of spamina drivers are pretty solid and have been up til this point.
That data shows very little, the sample size is tiny, there has been no time for people to adapt to it. What is the difference between using two of the same spamina driver vs different ones? I suspect these people could have placed comfortably without it, and this is hardly an overwhelming dominance in the lists to have a few people top. You could ban using two different spamina drivers for the same.
You're really taking a very biased look at the data without considering any context or proper analysis, which I guess isn't surprising given you called for a ban
before there was any data at all. That's fine, it seems popular to do this now, but since when is this the approach the WBO itself takes? Sure, people can raise concerns, but since when do we act on those instead of solid data.
You're exactly right that it may be foreshadowing in that the issue is not here yet... Since when do we do something about a problem that "might" happen? Wait til we "foreshadow" some counters, such as MX+X' decks. This isn't like almight in classic where it weighs like twice as much as everything else, it's a major ruling change with no evidence which doesn't line up with the WBBA approach either as I understand it.
The meta is actually in the best place it has been in ages right now thanks to guilty and savior. Let it breathe. Let people adapt and overcome.
And keep in mind I'm not anti-ban-things. Heck, apparently certain committee members only remember me for the fact I lost my cool over a time they didn't ban something fast enough (from MFL, a format I helped design no less) - I am very much all for the committee being prompt, but there needs to be a decent sample size and proper consideration before something with this impact is done, coupled with watchlisting and community consultation around how it is addressed. It's very clear from various responses that many aspects weren't considered and to me that casts the entire rule into question.