tennisace
not quite too old for this, apparently
Hi there.
Here are the drafts of two new pages to go into the SCMS. Copyediting and comments would be much appreciated.
Threat Discussion
Counters Discussion:
Here are the drafts of two new pages to go into the SCMS. Copyediting and comments would be much appreciated.
Threat Discussion
HTML:
[title]
Threat Discussion
[page]
<p>After the Typing Poll, the topic leader should post a thread asking questions about which Pokemon should be able to check or counter the CAP. Specifically, these questions should be posted in the OP:</p>
<div style="
border: 1px solid black;
background-color: #E4E4FF;
margin: 0 10em 2em 5em;
padding: 0 1em 0em 1em;
height: 20em;
overflow: auto;">
<ul>
<li><p>Going specifically by typing, what Pokemon found in the OU (or relevant) metagame will be able to comfortably give this CAP project trouble?</p></li>
<li><p>What Pokemon will be major threats to this project right off the bat?</p></li>
<li><p>What Pokemon have the potential to become counters?</p></li>
<li><p>What Pokemon may end up as threats, but must be contained or dealt with per the concept?</p></li>
<li><p>Will the concept succeed with these set list of threats?</p></li>
<li><p>Is this list of threats acceptable for the project?</p></li>
<li><p>What Pokemon will be threatened by the CAP based off of typing?</p></li>
<li><p>Are these Pokemon targets that we want CAP to hit?</p></li>
<li><p>Will these targets be "unavoidable" to threaten based solely on the typing?</p></li>
<li><p>What direction must the project go in now that a set list of basic threats has been identified?</p></li>
<li><p>What must be done in order to make these threats "wanted counters" or these threats be eliminated from counter discussion?</p></li>
<li><p>What Pokemon do we want this project to counter entirely?</p></li>
</ul>
</div>
<p>Be aware that this list of questions is not a checklist, and not every question must be definitively answered in every response. </p>
HTML:
[title]
Counters Discussion
[page]
<p>The Counters Discussion occurs before the Movepool Discussions and is a continuation of the Threat Discussion. The difference between the two is that the Counters Discussion is more concrete given that the Stat Spread, Typing, and Abilities of the Pokemon will be decided already, narrowing (or maybe widening) the list of potential checks and counters. The TL will post these guide questions in the OP of the Counter Discussion thread:</p>
<div style="
border: 1px solid black;
background-color: #E4E4FF;
margin: 0 10em 2em 5em;
padding: 0 1em 0em 1em;
height: 20em;
overflow: auto;">
<ul><li><p>Given the combination of typing, ability, and stat pool now decided, which previously defined threats are considered hard counters to the project?</p></li>
<li><p>Which Pokemon are regarded as basic counters?</p></li>
<li><p>Which Pokemon are checks?</p></li>
<li><p>Are the Pokemon that are currently able to counter the project the Pokemon we want/need to counter the project?</p></li>
<li><p>If not, what must be done to handle these Pokemon? Is it unavoidable?</p></li>
<li><p>What Pokemon have arisen in discussions that were not brought up before? As in, are there Pokemon that counter/check this concept on concepts that are not focused around its typing? Where should they be placed in the discussion?</p></li>
<li><p>Which Pokemon have been taken out of the counters discussion due to the stat pool and ability?</p></li>
<li><p>Which Pokemon have moved from threats purely by typing to checks? To neutral match-ups?</p></li>
<li><p>Which Pokemon are now countered by the project fully? Which are checked by the project? Which have become neutral match-ups against the project?</p></li>
<li><p>With this set list of counters and checks, does this fulfill the concept's goal?</p></li></ul>
</div>
<p>The end goal of the Counters discussion will be the basis for limiting Attacking Moves and non-Attacking Moves. A few Pokemon will be selected as Pokemon that should Hard Counter the CAP based on fulfilling three of six criteria:</p>
<ul>
<li><p>Can switch into this CAP's Strongest reliable STAB attacks at least three times from full health.</p></li>
<li><p>Can switch into this CAP's strongest possible coverage move at least twice from full health.</p></li>
<li><p>Can stall this CAP indefinitely using its recovery options either forcing the CAP out or healing enough that the stalling Pokemon can alternate between recovery and attacking.</p></li>
<li><p>Can OHKO or 2HKO the CAP with one of the moves on that Pokemon's relevant official Smogon moveset.</p></li>
<li><p>Can cripple this CAP with a permanent status move without risking a OHKO.</p></li>
<li><p>Can set up, use hazards, weather, or otherwise execute an opponent's strategy without risking a 2HKO.</p></li>
</ul>
<p>Attacking Moves that would turn Pokemon on the CAP's list of Hard Counters into Checks under ordinary circumstances will not be allowed. Non-Attacking Moves such as stat boosters or Taunt that would turn Pokemon on the CAP's list of Hard Counters into Checks will not be allowed.</p>
<p><em><b>Note:</b> If it would take both an attacking and a non-attacking move to alter a Hard Counter, whichever discussion comes first will limit the second discussion.</em></p>
<p>For example, if Dragon Dance + Close Combat would turn a Pokemon from a Hard Counter into a Check, where neither Dragon Dance nor Close Combat alone would do so (e.g. Only +1 LO CC OHKOs, but the counter is ordinarily faster and can OHKO the CAP after taking a +0 LO Hit from Close Combat) then if Dragon Dance is selected first, Close Combat cannot be selected. If Close Combat is selected first, then Dragon Dance cannot be selected.</p>