CAP 32 So Far
-----
Alright folks, we're officially a Fire/Fairy-type Pixilate user with some strong potential move options down the line like Extreme Speed, Boomburst, and Knock Off. Please pay very close attention to spoo's posts during this thread and remain on topic.
In this stage, we will try to analyze which Pokemon sets could threaten or be threatened by us. Based on our typing and concept we will also decide which specific threats we should focus on later stages, and which ones should be mostly left alone. Then, the Topic Leader will organize them into a list, following this basic format:
The following is a set of questions that we should try to answer during this discussion:
Guidelines:
1) Pay close attention to the Topic Leader during this discussion. Their job is to keep us focused and to bring insight.
2) Do not poll jump. Poll jumping is a serious offense in these threads, and you can get infracted for it. Poll jumping is when you discuss something that should be discussed in the future, like specifying a CAP's stats or typing. You're allowed to hint at such things to conclude a point or to provide an example, but do not centralize your post on a poll jump. Poll jumping hurts the focus of early threads and can cause us to go off on a tangent. If you're not sure if a particular argument is poll jumping or not, err on the side of caution and don't post it.
3) Refer to Pokemon by specific sets. This way we can clearly identify which specific sets we should be focusing on, and what specific characteristics makes us threaten or threatened by them. Adding complete movesets, EV spreads and Natures is recommended, but not mandatory.
4) Assume that Stealth Rock is on both sides of the field, unless otherwise specified. This can be changed by the Topic Leader during the discussion.
4) This are the exact definitions of check and counter that we will be working with:
-Pokémon A checks a Pokémon B set if, when Pokémon A is given a free switch into that Pokémon B set, Pokémon A can win every time, even under the worst case scenario, without factoring in hax.
-Pokémon A counters a Pokémon B set if Pokémon A can manually switch into that Pokémon B set, and still win every time, even under the worst case scenario, without factoring in hax.
-----
Alright folks, we're officially a Fire/Fairy-type Pixilate user with some strong potential move options down the line like Extreme Speed, Boomburst, and Knock Off. Please pay very close attention to spoo's posts during this thread and remain on topic.
In this stage, we will try to analyze which Pokemon sets could threaten or be threatened by us. Based on our typing and concept we will also decide which specific threats we should focus on later stages, and which ones should be mostly left alone. Then, the Topic Leader will organize them into a list, following this basic format:
- Switch in: The list of Pokemon on which we should be able to have a easy time switching in and then forcing them out, more than once in a game. This doesn't mean that we should be able to come into any of their moves, just their most commonly used ones.
- Pressure: The list of Pokemon that might threaten us, but should not be able to switch in easily. They should not be able to check us easily.
- Checks and Counters: The list of Pokemon should, in some way, threaten us. This might mean that they will probably be able to beat us 1v1, or at least severely cripple us. Certain Pokemon, in particular Revenge Killers might be included both in here and in Pressure, because once they switch in, they should be able to check us.
The following is a set of questions that we should try to answer during this discussion:
- Going specifically by typing, what Pokemon found in the CAP metagame will be able to comfortably give this project trouble?
- What Pokemon will be major threats to this project right off the bat?
- What Pokemon have the potential to become counters?
- What Pokemon may end up as threats, but must be contained or dealt with per the concept?
- Will the concept succeed with this list of threats?
- Is this list of threats acceptable for the project?
- What Pokemon will be threatened by the CAP based off of typing?
- Are these Pokemon targets that we want CAP to hit?
- Will these targets be "unavoidable" to threaten based solely on the typing?
- What direction must the project go in now that a set list of basic threats has been identified?
- What must be done in order to make these threats "wanted counters" or these threats be eliminated from counter discussion?
- Are there any Pokemon that we want to completely counter?
Guidelines:
1) Pay close attention to the Topic Leader during this discussion. Their job is to keep us focused and to bring insight.
2) Do not poll jump. Poll jumping is a serious offense in these threads, and you can get infracted for it. Poll jumping is when you discuss something that should be discussed in the future, like specifying a CAP's stats or typing. You're allowed to hint at such things to conclude a point or to provide an example, but do not centralize your post on a poll jump. Poll jumping hurts the focus of early threads and can cause us to go off on a tangent. If you're not sure if a particular argument is poll jumping or not, err on the side of caution and don't post it.
3) Refer to Pokemon by specific sets. This way we can clearly identify which specific sets we should be focusing on, and what specific characteristics makes us threaten or threatened by them. Adding complete movesets, EV spreads and Natures is recommended, but not mandatory.
4) Assume that Stealth Rock is on both sides of the field, unless otherwise specified. This can be changed by the Topic Leader during the discussion.
4) This are the exact definitions of check and counter that we will be working with:
-Pokémon A checks a Pokémon B set if, when Pokémon A is given a free switch into that Pokémon B set, Pokémon A can win every time, even under the worst case scenario, without factoring in hax.
-Pokémon A counters a Pokémon B set if Pokémon A can manually switch into that Pokémon B set, and still win every time, even under the worst case scenario, without factoring in hax.