This is where we will discuss CAP 11's stat and movepool limits.
Our CAP so far:
This is a new addition to the process of creating a Pokemon, so I strongly recommend that you read this entire OP to understand what is to be discussed in this thread.
Stat Bias Limits
Stat bias limits set the general stat bias of a Pokemon from an offensive and defensive standpoint. Stat biases are not solely for limiting stats, but they also describe the overall build of the Pokemon in offensive and defensive terms. However, the stat spread is the only part of the project that will be specifically constrained by Stat Bias Limits; the other part will be explained below. There will be four stat biases selected and a total Base Stat Rating (BSR) limit. The Stat Biases are:
Physical Tankiness (PT)
Below Average
Base Stat Rating & Movepool Limits
The Base Stat Rating is simply the measurement of the overall "power-level" of the Pokemon's base stats. In the past, the Base Stat Total (BST) was used to measure the power of base statistics. BST is a very poor measurement for stat power, however, so the CAP project now uses Base Stat Rating (BSR) to determine the overall effectiveness of a Pokémon's base stats. The results are more useful and relevant to the relative power of a created Pokémon's stats.
The Base Stat Rating directly impacts the number of moves and Very Good Moves in a Pokemon's movepool. The higher BSR a Pokemon has, the smaller movepool and Very Good Movepool size it has. The BSR of a Pokémon is divided into 12 different categories, ranging from the exaggerated rating of Arceus and other Ubers to the awful rating of Pokémon like Unown and most baby Pokémon. A better description of these ratings can be found here. For the purposes of the movepool limitations linked to the BSR of Pokémon, only five of these categories are available as listed below. More details on what the Very Good Movepool of a Pokémon means can be found here. Below are the five categories along with what the movepool and Very Good Movepool size will be; examples are provided.
At the end of this thread, I will be posting the ranges for Stat Biases, Base Stat Rating, Total Movepool Size, and Total Very Good Movepool Size, depending on the arguments presented and what I think would work best.
Because this is probably the most confusing part of the process, I really want everyone to be sure you understand what is supposed to be discussed. Read and re-read this thread if you're lost, or you can always PM me if you want me to explain it to you. Also, I urge you to read through this article as it explains everything about this topic pretty clearly.
It should be noted that this thread is NOT going to lead up to a poll. After a period of about a day or two, I will be deciding the limits that all stat spreads must conform to.
Rules:
Our CAP so far:
Typing: Fighting/DarkDougJustDoug said:Name: Perfect Mate
General Description: Pick a good-but-not-great OU pokemon, and design the perfect teammate for it, similar to the way Celebi & Heatran, or Blissey & Skarmory complement each other so well on competitive teams.
Justification:
This would allow us to explore in detail how synergy between two pokemon can be achieved, because currently there are only a few perfect teammates in OU. And depending on the base pokemon we choose to give a "perfect mate", we can open a new niche in the metagame based around the efficient pairing.
The niche we create will be inherently tied to an existing pokemon in the metagame, which should provide a natural limitation to prevent this concept from being broken or "too different" from standard OU.
Questions To Be Answered:
- Is the base pokemon's usefulness (and usage) in the metagame increased as a result of having a "perfect mate"?
- What strategies are more effective for the base pokemon, as a result of having a perfect teammate?
- What are the most effective aspects of the new pokemon, for purposes of making a great teammate with the base pokemon?
- Is the new pokemon viable in the metagame without the base pokemon as a teammate
This is a new addition to the process of creating a Pokemon, so I strongly recommend that you read this entire OP to understand what is to be discussed in this thread.
Stat Bias Limits
Stat bias limits set the general stat bias of a Pokemon from an offensive and defensive standpoint. Stat biases are not solely for limiting stats, but they also describe the overall build of the Pokemon in offensive and defensive terms. However, the stat spread is the only part of the project that will be specifically constrained by Stat Bias Limits; the other part will be explained below. There will be four stat biases selected and a total Base Stat Rating (BSR) limit. The Stat Biases are:
Physical Tankiness (PT)
The rating of the Pokémon's physical defense.
Physical Sweepiness (PS)
The rating of the Pokémon's physical offense.
Special Tankiness (ST)
The rating of the Pokémon's special defense.
Special Sweepiness (SS)
The rating of the Pokémon's special offense.
An application for calculating the biases can be found here and the formulas themselves can be found here. For each individual bias, a named range will be specified by me at the end of this thread. These are the named ranges:
Below Average
A stat bias between 0-80
Average
A stat bias between 81-99
Above Average
A stat bias between 100-149
High
A stat bias greater than or equal to 150
Base Stat Rating & Movepool Limits
The Base Stat Rating is simply the measurement of the overall "power-level" of the Pokemon's base stats. In the past, the Base Stat Total (BST) was used to measure the power of base statistics. BST is a very poor measurement for stat power, however, so the CAP project now uses Base Stat Rating (BSR) to determine the overall effectiveness of a Pokémon's base stats. The results are more useful and relevant to the relative power of a created Pokémon's stats.
The Base Stat Rating directly impacts the number of moves and Very Good Moves in a Pokemon's movepool. The higher BSR a Pokemon has, the smaller movepool and Very Good Movepool size it has. The BSR of a Pokémon is divided into 12 different categories, ranging from the exaggerated rating of Arceus and other Ubers to the awful rating of Pokémon like Unown and most baby Pokémon. A better description of these ratings can be found here. For the purposes of the movepool limitations linked to the BSR of Pokémon, only five of these categories are available as listed below. More details on what the Very Good Movepool of a Pokémon means can be found here. Below are the five categories along with what the movepool and Very Good Movepool size will be; examples are provided.
Code:
+----------------------------------------------+ +----------------------------------------------------------------+
| Base Stats Rating | | Movepool |
+---------------+-------+----------------------+ +---------------+-------------+----------+-----------------------+
| Description | Limit | Examples | | Description | Total Moves | VG Moves | Examples |
+---------------+-------+----------------------+ +---------------+-------------+----------+-----------------------+
| Above Average | 250 | Spiritomb, Azumarill | --> | Fantastic | 95 | 45 | Tyranitar, Togekiss |
| Good | 300 | Swampert, Gliscor | --> | Excellent | 85 | 40 | Sceptile, Swampert |
| Very Good | 350 | Infernape, Lucario | --> | Very Good | 75 | 35 | Mismagius, Steelix |
| Excellent | 400 | Mew, Heatran | --> | Good | 65 | 30 | Walrein, Heracross |
| Fantastic | 450 | Deoxys, Garchomp | --> | Above Average | 55 | 25 | Jumpluff, Swellow |
+---------------------+------------------------+ +---------------+-------------+----------+-----------------------+
Because this is probably the most confusing part of the process, I really want everyone to be sure you understand what is supposed to be discussed. Read and re-read this thread if you're lost, or you can always PM me if you want me to explain it to you. Also, I urge you to read through this article as it explains everything about this topic pretty clearly.
It should be noted that this thread is NOT going to lead up to a poll. After a period of about a day or two, I will be deciding the limits that all stat spreads must conform to.
Rules:
- No poll jumping. We are only discussing Stat and Movepool Limits and nothing else. There should be absolutely no talk about specific stat spreads in this topic.
- No threadhogging. This is an open discussion and should not devolve into a back-and-forth between two people. This is something that can tend to happen at this point in the project a lot, so watch it.
- Don't get hung up on the same points. The discussion should remain fresh throughout the course of this thread, and you really shouldn't be posting the same arguments over and over.