approved by ausma
banner made by royalfluxh thanks alot ^.^<3
The SM OU metagame is full of a plethora of both offensive and defensive threats, and this thread is dedicated to finding answers to a Pokemon each week!
Rules:
1. When nominating your check/counter take a gander at The Smog:
2. Only post Pokemon and Sets that are viable in SM OU. Try to stick to the Pokemon on the Viability Rankings.
3. Reservations are allowed, however if you don't complete your post within 24 hours someone else is free to take your Pokemon.
4. You can correct people, but obviously be nice.
5. Calcs are incredibly helpful, but not necessary.
6. Give explanations. Not a thesis or anything, but more than one sentence should be fine.
7. If someone posts a Pokemon with a certain set, you can only submit the same Pokemon if it has a directly different set.
banner made by royalfluxh thanks alot ^.^<3
The SM OU metagame is full of a plethora of both offensive and defensive threats, and this thread is dedicated to finding answers to a Pokemon each week!
Rules:
1. When nominating your check/counter take a gander at The Smog:
Pokémon A checks Pokémon B if, when Pokémon A is given a free switch into Pokémon B, Pokémon A can win every time, even under the worst case scenario, without factoring in hax.
Pokémon A counters Pokémon B if Pokémon A can manually switch into Pokémon B and still win every time, even under the worst case scenario, without factoring in hax.
There are some parts of those definitions that may be confusing to the unfamiliar, so now I'm going to make sure we're all on the same page. "Hax" does not mean cheats or codes used to win. "Hax" means, loosely, things that have a chance of happening but usually don't, for example, critical hits (under most circumstances), Ice Beam freezing, and Fire Blast missing. This means that we don't take into account these types of things when we analyze if one Pokémon checks or counters another. Despite this, it's unwise to declare that one Pokémon checks another when the victorious Pokémon relies on hitting Focus Blast three times in a row, or something like that. Basically, you're often okay ignoring hax unless something that doesn't have a high chance of happening must happen in order for a Pokémon to check or counter another.
There are some things, like flinching, which you would normally consider to be hax but aren't always so. For example, Jirachi has a 60% chance to flinch a slower opponent with Iron Head, so in this case, flinching is not hax because it happens over half the time. For things such as missing or secondary effects, such as a Scald burn or Special Defense drop from Seed Flare, that have a decently high chance of happening, you need to think about them when you analyze checks or counters. Even though they might fit the standard definition of hax, they happen often enough for you to expect to see them in real situations somewhat commonly. There's no official or best guideline, but in my opinion, if some form of "hax" has a 30% chance or higher of happening, you should keep it in the back of your mind because it's not a negligible occurrence.
Pokémon A counters Pokémon B if Pokémon A can manually switch into Pokémon B and still win every time, even under the worst case scenario, without factoring in hax.
There are some parts of those definitions that may be confusing to the unfamiliar, so now I'm going to make sure we're all on the same page. "Hax" does not mean cheats or codes used to win. "Hax" means, loosely, things that have a chance of happening but usually don't, for example, critical hits (under most circumstances), Ice Beam freezing, and Fire Blast missing. This means that we don't take into account these types of things when we analyze if one Pokémon checks or counters another. Despite this, it's unwise to declare that one Pokémon checks another when the victorious Pokémon relies on hitting Focus Blast three times in a row, or something like that. Basically, you're often okay ignoring hax unless something that doesn't have a high chance of happening must happen in order for a Pokémon to check or counter another.
There are some things, like flinching, which you would normally consider to be hax but aren't always so. For example, Jirachi has a 60% chance to flinch a slower opponent with Iron Head, so in this case, flinching is not hax because it happens over half the time. For things such as missing or secondary effects, such as a Scald burn or Special Defense drop from Seed Flare, that have a decently high chance of happening, you need to think about them when you analyze checks or counters. Even though they might fit the standard definition of hax, they happen often enough for you to expect to see them in real situations somewhat commonly. There's no official or best guideline, but in my opinion, if some form of "hax" has a 30% chance or higher of happening, you should keep it in the back of your mind because it's not a negligible occurrence.
2. Only post Pokemon and Sets that are viable in SM OU. Try to stick to the Pokemon on the Viability Rankings.
3. Reservations are allowed, however if you don't complete your post within 24 hours someone else is free to take your Pokemon.
4. You can correct people, but obviously be nice.
5. Calcs are incredibly helpful, but not necessary.
6. Give explanations. Not a thesis or anything, but more than one sentence should be fine.
7. If someone posts a Pokemon with a certain set, you can only submit the same Pokemon if it has a directly different set.
Last edited by a moderator: