I voted ban to Arctozolt in the council vote posted here: https://www.smogon.com/forums/threa...nutes-community-surveys.3665716/#post-8970908
I generally follow Smogon tiering principles when voting. That means there are three main reasons to ban something.
1) Too strong (broken) - if Kyogre was in UU, it would be too strong
2) Too haxy (uncompetitive) - this is the logic of banning Double Team/Evasion clause
3) Makes the tier significantly worse (unhealthy) - this is the logic of banning fishy styles like at one point in this tier sun
I picked the third reason to ban Arctozolt, it makes the tier significantly worse and makes many match ups fishy. By fishy, I just mean match ups are much riskier but frankly Arctozolt is good enough that there isn't even too much risk. Counterplay to Arctozolt exists but is rare, strange, and generally otherwise poor in the metagame. I refer to Piloswine when speaking of defensive counterplay. I do not consider Umbreon reliable counter as Bolt Beak is a near 2HKO given hail and SR chip. Offensive counterplay is also limited but the teams that Arctozolt are on generally use two ice types (Arctozolt + Ninetailes) so there can be defensive holes. It's not enough for me to vote do not ban though.
I think it is a no brainer to select Arctozolt. I don't think we should even call this a hail suspect at all, Arctozolt's hail abuse is a different order of magnitude to the next best abusers like Weather Ball Thundurus-T/Volcanion and Snow Cloak Mamoswine. Arctozolt is clearly the broken element so Arctozolt should be banned. Again, I follow Smogon tiering principles which says to do simple bans. In my view, a simple ban is a non complex ban. A complex ban is a non-Pokemon ban (banning abilities, making conditions, banning items, etc).
I apologize for the off the cuff nature of this post. This is not a thorough analysis of why Arctozolt should or should not be banned nor does it represent anyone's view except my own. I thought to post these rough thoughts as I believe we would be remiss to have a tiering decision without any discussion in our official UU NP thread.
I generally follow Smogon tiering principles when voting. That means there are three main reasons to ban something.
1) Too strong (broken) - if Kyogre was in UU, it would be too strong
2) Too haxy (uncompetitive) - this is the logic of banning Double Team/Evasion clause
3) Makes the tier significantly worse (unhealthy) - this is the logic of banning fishy styles like at one point in this tier sun
I picked the third reason to ban Arctozolt, it makes the tier significantly worse and makes many match ups fishy. By fishy, I just mean match ups are much riskier but frankly Arctozolt is good enough that there isn't even too much risk. Counterplay to Arctozolt exists but is rare, strange, and generally otherwise poor in the metagame. I refer to Piloswine when speaking of defensive counterplay. I do not consider Umbreon reliable counter as Bolt Beak is a near 2HKO given hail and SR chip. Offensive counterplay is also limited but the teams that Arctozolt are on generally use two ice types (Arctozolt + Ninetailes) so there can be defensive holes. It's not enough for me to vote do not ban though.
I think it is a no brainer to select Arctozolt. I don't think we should even call this a hail suspect at all, Arctozolt's hail abuse is a different order of magnitude to the next best abusers like Weather Ball Thundurus-T/Volcanion and Snow Cloak Mamoswine. Arctozolt is clearly the broken element so Arctozolt should be banned. Again, I follow Smogon tiering principles which says to do simple bans. In my view, a simple ban is a non complex ban. A complex ban is a non-Pokemon ban (banning abilities, making conditions, banning items, etc).
I apologize for the off the cuff nature of this post. This is not a thorough analysis of why Arctozolt should or should not be banned nor does it represent anyone's view except my own. I thought to post these rough thoughts as I believe we would be remiss to have a tiering decision without any discussion in our official UU NP thread.