Metagame SV OU Metagame Discussion v4

So what will happen if the people who are allowed to vote end up not voting by the time of the deadline? Do we just take what the majority is, or does it have to be 60%
 
im_platinum said:
So what will happen if the people who are allowed to vote end up not voting by the time of the deadline? Do we just take what the majority is, or does it have to be 60%
Click to expand...
You can still divide by the number who voted. So if 10% of the vote is left, and there were 137 eligible voters, that would be about 13.7 who haven't voted, Call it 14 and say they didn't vote. You would instead need 74 of 123 voters to get 60% rather than the 83 needed for the 137 votes. And this could be applied for however many didn't vote. So if 4 abstained, that would mean you'd need only 80 of 133 to vote ban.
 
Bold School said:
You can still divide by the number who voted. So if 10% of the vote is left, and there were 137 eligible voters, that would be about 13.7 who haven't voted, Call it 14 and say they didn't vote. You would instead need 74 of 123 voters to get 60% rather than the 83 needed for the 137 votes. And this could be applied for however many didn't vote. So if 4 abstained, that would mean you'd need only 80 of 133 to vote ban.
Click to expand...
So according to the fact that we need 83 or more pro ban votes for a ban and we only have less than 10% of players left, I don't know how much percent less than 10% so I'm going to use 10% percent for now. that means about 14 or less players have not voted yet. With this knowledge I can guesstimate that approximately 47 players have voted DNB and 76 voted for a ban if we are splitting it half and half. My math is very likely vague because i don't know the exact numbers so this is just an estimate
 
Finchinator said:
Kyurem still too close to call with less than 10% of the vote left.
Click to expand...
GX3S66aWIAAbuD_.jpg
 
PastaMechKaku said:
By the by, what are some other good use cases of SpDef Corv aside from being a Kyurem sponge?
Click to expand...
it's a better switch-in to glimm and can pivot in and out of ghold, both of which are really good for a hazard control mon. it's also way better into glowking, several special valiant sets, most enamorus sets, and plenty of other special attackers, especially if they're carrying supereffective coverage—the spdef investment usually makes a hell of a difference between a 2hko and a 3hko, which allows you to uturn out more safely, chip them more easily, roost off the damage and pressure-stall their coverage if you need to, and occasionally you can just outdamage them altogether and either kill or trade with mons that physdef corv can't handle
 
Avira said:
I did warn you more than once that Kyurem could actually survive its suspect test and that good players don't overwhelmingly find Kyurem broken like they did with Gouging Fire. I expect a DNB verdict.
Click to expand...
All due respect, for someone seemingly pro-ban you really posted little of substance in the actual suspect thread, at worst just making posts fawning over certain dnb posters. I don't mind if kyurem is banned or not; I accepted openly that it was a distinct possibility it didn't go, and there have been very good players who stepped up in favour of a dnb verdict. But regardless of the verdict, that doesn't make the suspect a waste, and I at least know I did my best in advocating for something I believed in. You repeatedly made a point of not doing so, and then doomsaying when a sizable portion of players still wanted to try for a Kyurem suspect. I'm not saying your assertion that there were good players who didn't find Kyurem broken was wrong, it clearly wasn't. Rather, I'm just wondering what point you even think you're trying to make here. That Kyurem isn't broken? That we should've waited and that maybe some of them would've changed their minds in the future, despite subtect sets having controversially blown up? Because if Kyurem just became less broken over time, I'm not even certain why we'd even have a suspect at all in that case. I'm actually not sure, but given that you almost made a point of not advocating for your stance beyond just doomsaying, I don't think you have any right to point to me in the case of whatever the test results in. If you wanted Kyurem banned, you should've acted like it.
 
HunterNeverHere9 said:
how good is a bo core of gliscor+primarina+glowking+bolt?
Click to expand...
Generally speaking this is a fine core even without knowing the set's but you'd need some sort of hazard removal for the Primarina. This core is also pretty slow and since it is a bulky Offense you'd definitely need some form of speed control, you can probably do something like Cinderace + Zamazenta or Scarf Trick Darkrai as last 2 slots and it should help with those issues a bit? Really you could go Great Tusk > Gliscor as well which is a bit faster and saves on a team slot in regards to hazard control, while having a crucial Kingambit check without having to add Zamazenta + Gliscor which feels redundant. Of course since there's not too much information given there's not much to go off of but I hope my rambling can give you some needed guidance.
 
This was an incredibly close vote, and puts into perspective: if you think your voice doesn’t matter, it can always come down to the wire like this. This was a pretty intense suspect, and while I’m glad it’s over, there were definitely things we learned from it that will be taken into consideration for the future. Let’s keep paving a path forward!

And be sure to wish Finchinator a happy birthday!
 
I guess Gliscor will be better, and teambuilding will be easier. I think Ogerpon W will be stronger, especially because ground type mons will be better without Kyurem in the tier. Now we can focus on finding new ways to deal with Darkrai, Waterpon and Gliscor.
This ban may be good for dragon types also, maybe we'll see some of them rise in usage. Weavile and Meowscarada have one less check but they really struggle against moltres and helmet mons.

Happy birthday Finchinator!
 
You must log in or register to reply here.
Back
Top