WARNING
The following thread is intentionally designed as an offshoot of the typical Create-A-Pokemon Project. If you are new to the CAP Project, please read through previous processes to gain a full understanding of what is different here. If you are familiar with the CAP Process, give this policy thread a good read. Join us on Discord if you have any further questions!
https://discord.gg/6YC7Ab
The following thread is intentionally designed as an offshoot of the typical Create-A-Pokemon Project. If you are new to the CAP Project, please read through previous processes to gain a full understanding of what is different here. If you are familiar with the CAP Process, give this policy thread a good read. Join us on Discord if you have any further questions!
https://discord.gg/6YC7Ab
Hello everyone and welcome to twenty-fifth iteration of the Create-A-Pokemon Project. Unlike all other CAPs, this CAP is a Celebration CAP, meaning that it will be allowed to break some of the previous conventions we have for Pokemon creation. As a result, this thread will be for framework submissions to determine which rules we would like to break. This is new territory for the CAP Project, so the moderators ask that we as a community exhibit a heightened sense of patience and understanding. As always, please read all of the rules before making your post.
We will adhere to the following for the duration of CAP25:
- This Pokemon will be playable in the CAP Metagame. Furthermore, it will be reasonably balanced for competitive battles, specifically not a broken threat that negatively centralizes the metagame.
- The creation of this Pokemon will ONLY break CAP creation guidelines based on the Framework we select. For example, if we choose to create a Pokemon with an illegal ability as our Framework, we will not also allow a custom move for it during Movepool Submissions.
- This creation will not allow any non-intuitive custom elements. This includes custom typings, abilities with entirely new mechanics, or moves with entirely new mechanics. For example, an ability that changes a Pokémon's form based on terrain would be allowed, but not an ability that summons a new type of weather.
- This creation will be designed with positive optics in mind. As this Pokemon will join the past 24 Pokemon in our playable metagame, it needs to be something we are proud of presenting to the public.
- This Pokemon will have a Framework that alters, at maximum, two stages of the process. An example of this would be a framework that dictates CAP25's typing and primary ability. An illegal Framework would also mandate a specific stat bias on top of those restrictions. Furthermore, the two stages trivialized must be linked (e.g. an Ultra Beast that requires Beast Boost and a 570 BST).
For a fully detailed list of reasoning for each of these rules, please consult this thread. Other rules that will continue for Framework Submissions are as follows:
- One submission per person. You may edit your Framework, but you may not change the fundamental premise after it has been posted. If editing your Framework, please edit the original post instead of posting a new revision. Do not bump your Framework after you have posted it. If people do not comment on it, so be it.
- Do not duplicate or closely-resemble Framework already posted by others. It is your responsibility to read through all previous submissions in this thread to ensure you are complying with this rule. Ignorance or laziness is not an excuse.
- Do not refer to any part of the Pokemon's artistic design. For example, the following phrases would be illegal:
"This is a bright blue Pokemon..."
"The Pokemon looks like a..."
"The Pokemon uses its long tail to..."
- A Framework Submission must be submitted in the proper format. The format is described below. If the proper format is not used, the moderators will not evaluate the submission, regardless of content.
Framework Submission Format
Use this format for all concept submissions: Here is the format with tags. Just copy/paste this into your post, and fill it out:
- Name - Unlike Concept Submissions, your name CANNOT be anything cutesy. Please list EXACTLY which process rule(s) you intend to break with the name. Some examples would be "Multitype CAP" and "Ultra Beast CAP."
- Description - This is the official description of the concept, and must follow ALL the content rules listed above. Do not make this a long description. Long descriptions are invariably too specific or too convoluted. Keep it short. Any more than a sentence or two is TOO MUCH. Do NOT include your Explanation of the concept in the Description. See "Explanation" below.
- Explanation - This can contain just about anything. This is where you can explain your concept without restraint. You may make suggestions, even specific suggestions, regarding the possible implementation of the Framework. This explanation should help facilitate discussion of the Framework -- but the Explanation is NOT part of the Framework and will be omitted from the polls and any future use of the Framework. Since your explanation is non-binding, regarding future polls and threads, it will not be evaluated for purposes of determining if your Framework is legal or illegal. Although it is tempting, refrain from making too long of an explanation; it will deter readers from fully considering your Framework.
In one week's time, the CAP moderators will make a large slate of CAP25 Frameworks into a large, multibold vote, similar to Art Poll 1. In order to be slated, make sure that you are following the guidelines listed above.
Best of luck, and enjoy our celebration!