Paleo said:This precedent should have been set for a while, even before the first sableye test. Overall, its a pretty poor argument to not ban a pokemon, as it never questions whether or not the pokemon at hand is broken or unhealthy, and rather points out how good said pokemon is. Why would you keep a pokemon on a type if it is broken? Why trade metagame health just to keep a type relevant? An easier and more relevant method would just be to argue that said pokemon isnt broken. Scpinion cited this as a poor argument during the last suspect as well, because saying ''Ghost will remain relevant if we don't ban sableye, so vote no ban!'' doesn't argue that sableye isnt unhealthy for the metagame.
So like I mainly agree with you, but I feel like there needs to be a balance. The type should be kept in mind when considering the mon, and have the types need for that mon stacked up against it's presence in the metagame. That is to say, if a mon in really broken then ban away, but if it is
manageable (even if it is annoying) and the type needs it to be at all relevant, those two things need to be compared. The type should at least be looked at. For example KyuW was a must for ice, but it was too broken. That is logical. But now take Hypothetical pokemon A, it is annoying as hell and kinda hard to deal with, but the type that it is on needs it desperately to remain remotely usable. That is a scenario in which the decision needs to be made on whether or not the type's need for that pokemon outweighs the general cons it has on the metagame. This metagame is made of 18 different types, not 8. I understand that it's impossible to make all types good, but I feel like we should make a effort towards getting close, so long as the metagame doesn't suffer too badly as a whole. But idk, think of it as like, "if mon A is too overpowered, to degree B, then it should be banned. However, if it is not
that broken (not to degree B), then we should compare it's cons to the metagame with the type's need for it. Idk