With how many changes the CAP metagame brings from regular SVOU, there are always new and creative ways to beat CAP Pokemon and base game Pokemon, so with that I present Whack-A-Pokemon!
(art to come)
Rules:
1. I will post a Pokemon or core to break, wall or generally win against in especially interesting or effective ways. You will have a specified window of time given by me (around a week) in which you can make submissions and after that time you will have some time (around 3 days) to vote on your favourite submission. You may submit one Pokemon.
2. Pokemon may be used by multiple people but the set must be diffrent in significant ways from the people before you.
3. Pokemon may be reserved with the set specified, though once 24h pass and your submission isn't done it will be opened again.
4. Mostly Pokemon on the SV CAP Viability Rankings including unranked CAP Pokemon are allowed, UU Pokemon are still fine but RU and under is very much pushing it and will be reviewed case by case. Try keeping the sets as viable as possible, as this can also serve as a rescource for teambuilding.
5. An explanation is required however short or long. Calcs to support your submission are also encouraged.
6. Follow the general smogon rules and be respectful when, for example, making a correction.
7. Before submitting take a look at the Smogs definition of a check/counter
Approved by Spammernoob
Managed by CapitanPabloskii and Airwind
(art to come)
Rules:
1. I will post a Pokemon or core to break, wall or generally win against in especially interesting or effective ways. You will have a specified window of time given by me (around a week) in which you can make submissions and after that time you will have some time (around 3 days) to vote on your favourite submission. You may submit one Pokemon.
2. Pokemon may be used by multiple people but the set must be diffrent in significant ways from the people before you.
3. Pokemon may be reserved with the set specified, though once 24h pass and your submission isn't done it will be opened again.
4. Mostly Pokemon on the SV CAP Viability Rankings including unranked CAP Pokemon are allowed, UU Pokemon are still fine but RU and under is very much pushing it and will be reviewed case by case. Try keeping the sets as viable as possible, as this can also serve as a rescource for teambuilding.
5. An explanation is required however short or long. Calcs to support your submission are also encouraged.
6. Follow the general smogon rules and be respectful when, for example, making a correction.
7. Before submitting take a look at the Smogs definition of a check/counter
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 analyse 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 analyse 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.
Cycle 1 :obliteryx::
:kommo-o: - AthenaStrive9
Cycle 2 :garganacl::
:hydrapple: - Ixkukul
Cycle 3: :arghonaut: + Bulk Up:
:arghonaut: - traceyscetchit
Cycle 4: :kyurem:
:moltres: - Guingil
Cycle 5: :snaelstrom: + :equilibra:
:venomicon: - Spammernoob
Cycle 6: :Zamazenta:
:cresceidon: - traceyscetchit
Cycle 7: :venomicon:
:gholdengo: - AthenaStrive9
Cycle 8: :cresceidon:
:mollux: - Docter_Peng99
Cycle 9: :gliscor:
:hydreigon: - traceyscetchit
Cycle 10: :ting-lu: + :snaelstrom:
:rillaboom: - CapitanPabloskii
Cycle 11: :hatterene:
:heatran: - AthenaStrive9
Cycle 12: :hemogoblin:
:skeledirge: - realOzone
Cycle 13: :cresselia:
:tyranitar: - traceyscetchit
Cycle 14: :necturna:
:kommo-o: - AthenaStrive9
Cycle 2 :garganacl::
:hydrapple: - Ixkukul
Cycle 3: :arghonaut: + Bulk Up:
:arghonaut: - traceyscetchit
Cycle 4: :kyurem:
:moltres: - Guingil
Cycle 5: :snaelstrom: + :equilibra:
:venomicon: - Spammernoob
Cycle 6: :Zamazenta:
:cresceidon: - traceyscetchit
Cycle 7: :venomicon:
:gholdengo: - AthenaStrive9
Cycle 8: :cresceidon:
:mollux: - Docter_Peng99
Cycle 9: :gliscor:
:hydreigon: - traceyscetchit
Cycle 10: :ting-lu: + :snaelstrom:
:rillaboom: - CapitanPabloskii
Cycle 11: :hatterene:
:heatran: - AthenaStrive9
Cycle 12: :hemogoblin:
:skeledirge: - realOzone
Cycle 13: :cresselia:
:tyranitar: - traceyscetchit
Cycle 14: :necturna:
Managed by CapitanPabloskii and Airwind
Last edited:
