It's never too late! Sorry about this, but the new stage threw me for a loop. I interpreted it as an "early warning checks and counters discussion", which made sense to me to have after the overarching limits were set up. Anyway, this is a new stage that was introduced a mere month or so ago, and it is a place for speculation on those Pokemon that will give CAP 2 trouble and those that CAP 2 will give trouble simply by typing alone. There are some assumptions that must be made, such as that the CAP will probably have some form of STAB, and also remember that CAP 2 will have access to a single usage of Sketch.
Please read the below list for more details on the sorts of questions to answer here.
This discussion will be open for roughly 24 hours, after which I will reopen the stat limits discussion thread for continuance.
tl;dr: Quack! (Dusk sucks!)
Please read the below list for more details on the sorts of questions to answer here.
- Going specifically by typing, what Pokemon found in the OU (or relevant) metagame will be able to comfortably give this CAP 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 these set 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?
- What Pokemon do we want this project to counter entirely?
This discussion will be open for roughly 24 hours, after which I will reopen the stat limits discussion thread for continuance.
tl;dr: Quack! (Dusk sucks!)