Stick a Slowbro on the team and go to town on the ladder. Slowbro's biggest nuisances are Grass types like Roserade and Shaymin which are easy pickings for Blizzard spam.Well, I changed my team to hail, and whoever had the idea of running 3 snow cloakers, AWESOME IDEA!
Aside from getting a lot of flack from others for being a haxer, my team is just wrecking. Only two pokemon really give me any trouble: Machamp and Darmanitan. The former doesn't give a damn about cloak with decent sp.d, and the latter is just a complete nuisance.
I tried out this team as a direct result of reading this post. It really is stupid how easy it is to ladder with. You just get bailed out so often and do things like kill Escavalier with Froslass, kill Suicune with Mamoswine, kill anything with Specs Glaceon... not only is it retarded but it's a solid rebuke to anyone who is saying that Froslass is the only problem with Snow Cloak. Some people have acknowledged that a miss on Mamoswine can ruin your day but honestly Glaceon has been much worse. Specs Blizzard just hits so ridiculously hard. Add in Paralysis support and it really gets out of hand. "Spizzblam" is now higher on the ladder than any of my real alts, after basically one night of heavy laddering, which is just dumb. Many of the more profitable wins were because of Snow Cloak hax. I even played against Jak3 several times, who was using the same lineup; guess how many of those matches were decided by hax?Been playing a lot with Aboma/Froslass/Mamoswine/Glaceon/Slowbro/Flygon and it's just been....too dumb. I hate it. I shouldn't get outplayed and then win because they can't hit my mons. I'll probably try it with Snover too.
As said again,many pokes with the Swift Swim ability were banned in Rain without being broken.Well if those three are broken because of Snow Cloak ban them, not Snow Cloak. Unless ALL pokemon with the ability are broken, I rather just ban the pokemon.
Playing the numbers game still pushes the ban against Snow Cloak. Everything else in the past we've banned due to a controversial ability were the sole examples. Garchomp with Sand Veil, Blaziken with Speed Boost, etc. Nothing else can use Speed Boost or Sand Veil as well as those two. The fact that three random Ice-types, one of which is normally a pretty mediocre Pokemon, are now considered broken under the clout of this ability alone pushes the bias against the ability.Well if those three are broken because of Snow Cloak ban them, not Snow Cloak. Unless ALL pokemon with the ability are broken, I rather just ban the pokemon.
Well, I think the ban lists should be easy for everyone to understand. I could easily get my head around some extremely "complex" bans, as I'm sure you could too, but I think most casual players would prefer simply a simple list of what they can't use, rather than a few paragraphs. The people that post in this thread are a minute proportion of the people that use the tier lists tbh.This seems like a good time to do a Snow Cloak + Snow Warning ban. A straight-up ban on any one part of the problem has negative consequences (SC ban soft-bans Froslass and Beartic, lol Snow Warning ban bans Abomasnow/Snover unnecessarily, the individual mons appear to not be broken in themselves with Froslass being a possible exception, just SC pushes them overboard) while a SC+SW ban doesn't. The only real problem with this solution is that it is a complex ban, and I'm going to be honest here: If something like "Pokemon with the abilities Snow Cloak and Snow Warning cannot be on the same team" is too "complex" for someone to grasp, they're probably not going to be very competitive in the first place.
You can say the same exact thing for Aldaron's proposal. Is Luvdisc broken with DrizzleSwim? Is Magikarp broken? No. It was Kingdra, Ludicolo, and Kabutops (mainly) that made it broken. UU had no problem banning Vulpix until Limbo, whats wrong with doing the same to Beartic?guys, banning snow cloak vs. banning its 3 users is the difference between banning and unbanning beartic. do you really care that much about beartic?
I don't think it's that bad. Here's an example:Well, I think the ban lists should be easy for everyone to understand. I could easily get my head around some extremely "complex" bans, as I'm sure you could too, but I think most casual players would prefer simply a simple list of what they can't use, rather than a few paragraphs. The people that post in this thread are a minute proportion of the people that use the tier lists tbh.
I was saying the opposite of what you interpreted.You can say the same exact thing for Aldaron's proposal. Is Luvdisc broken with DrizzleSwim? Is Magikarp broken? No. It was Kingdra, Ludicolo, and Kabutops (mainly) that made it broken. UU had no problem banning Vulpix until Limbo, whats wrong with doing the same to Beartic?
I personally don't think Glaceon is broken, or Mamo for that matter, I was just stating that I don't want any pokemon banned that are not broken. Froslass is the only I find broken. (and that is because with one miss it is pretty much for sure gets you three layers of spikes @.@)Playing the numbers game still pushes the ban against Snow Cloak. Everything else in the past we've banned due to a controversial ability were the sole examples. Garchomp with Sand Veil, Blaziken with Speed Boost, etc. Nothing else can use Speed Boost or Sand Veil as well as those two. The fact that three random Ice-types, one of which is normally a pretty mediocre Pokemon, are now considered broken under the clout of this ability alone pushes the bias against the ability.
One, then okay, let's just ban Froslass. Two abusers puts it up for debate. But three? What's next, Beartic-based teams? Are you really confident in your ability to counter that either when a miss means he is probably killing your Chandelure?
Mamoswine is always dangerous plain and simple, that is why I was always on the fence of calling it broken since Snow Cloak was always straddling a fence for me as that is one Pokemon you do not want to miss (especially since you already have such few checks/counters against it thanks to having such a great movepool). Glaceon on the other hand is a power house no doubt but has pretty bad coverage to work with. But I think Froslass is still the main culprit.I personally don't think Glaceon is broken, or Mamo for that matter, I was just stating that I don't want any pokemon banned that are not broken. Froslass is the only I find broken. (and that is because with one miss it is pretty much for sure gets you three layers of spikes @.@)
Gonna highlight this up because I feel this is the more elegant solution and voices my sentiments more accurately than I can myself, quite frankly I have to agree with this interpretation of the argument. It isn't SC so much that breaks Hail but its hazards in combination with SC with the difficulty in removing them which makes it hard to deal with.Had this discussion on IRC last night and I want to see how the general community feels.
We know that Froslass is the best abuser of Snow Cloak, and many of you think it is the best hail abuser period. However, due to Froslass' lackluster special attack, most of the free turns it gets through hax will be spent using Spikes. Many people believe that this is part of a larger problem: Spikes are too easy to set up and too easy to take advantage of in UU. They have a good point; Spikes abuse is the simplest and most effective way to win in this tier. It would seem to me that Spikes and its common users should be evaluated before hail. This way, if we determine that the common spikers (Froslass, Deoxys-D, Roserade) are simply too powerful for UU, we will have also solved the issue that most of you have with hail. This is much more time-efficient than evaluating hail then evaluating spikes. A ban on common spikers would mean that hail can't use its precious Froslass, which many of you blame for hail's dominance.
Any opposition / support?