i'd like to change topic for a little bit, because i noticed something very troubling while i was looking at the "movesets" section of the 1695 stats. in that section, it has a list of other details, like who a mon's most common partners are, but there's one thing the 1695 stats have that the 1825 ones don't: the list of checks and counters. basically, it shows all the mons that either ko or force out a given mon a majority of the time—what i personally would refer to as consistent checks. normally, a pokemon has plenty of these. for example, here's the list of great tusk's consistent checks/counters:
most pokemon tend to have around ten of these or so, even problematic ones like gliscor:
of course, these statistics don't communicate the situation perfectly—statistics rarely do. some mons don't ko or force out things on their own, but will do something else instead, like inflicting a status condition and then pivoting to something else. so it's possible that some mons have a shorter list of checks and counters because of that, or lack of data, or because a mon's main way of forcing things out might be through phazing, or other things. for example, despite not being a mon anyone is really complaining about or considering broken, dragonite has a surprisingly low number of consistent checks listed, likely because one of its biggest weaknesses is status conditions so a lot of its actual checks pivot out:
but despite these shortcomings that make the "checks and counters" list not entirely indicative of how problematic or strong a given mon is, i think it can serve as a potential indicator of problems, as seen by the list for roaring moon being quite short:
now, keeping that in mind, this is the list of consistent checks and counters for sneasler.
i think we might have a problem here
most pokemon tend to have around ten of these or so, even problematic ones like gliscor:
of course, these statistics don't communicate the situation perfectly—statistics rarely do. some mons don't ko or force out things on their own, but will do something else instead, like inflicting a status condition and then pivoting to something else. so it's possible that some mons have a shorter list of checks and counters because of that, or lack of data, or because a mon's main way of forcing things out might be through phazing, or other things. for example, despite not being a mon anyone is really complaining about or considering broken, dragonite has a surprisingly low number of consistent checks listed, likely because one of its biggest weaknesses is status conditions so a lot of its actual checks pivot out:
but despite these shortcomings that make the "checks and counters" list not entirely indicative of how problematic or strong a given mon is, i think it can serve as a potential indicator of problems, as seen by the list for roaring moon being quite short:
now, keeping that in mind, this is the list of consistent checks and counters for sneasler.
i think we might have a problem here