Hey all! I had originally set out to respond to each framework submitted after the first 24 hours of the thread being open but there have been some minor setbacks. I have a majority of the first day submissions written up, but I apologize if I did not quite get to yours yet. I am just running down submissions as they were posted: however, I will be grouping similar frameworks together as needed. I will be using spoiler tags to mitigate the size this post will occupy.
Normal-type CAP
Very straight forward in its proposal, a Normal-type framework would force us to build with a typing that we would naturally avoid in most other projects. The way it reads currently appears to favor a more offensive approach. Whether or not this was intentional, I think the framework could benefit from a slight change of wording to appear more neutral. I think regardless of direction, this mon would need a greater power budget and need to have a straight-forward role for teams comparable to mons like Mega-Lopunny or Blissey.
Two Forms/Counterparts
This will cover Genie/Deoxys Forms, Gender Differences, Giratina-style Forms, Counterparts CAP, and Two-Face.
Okay, so I have grouped all 5 of these frameworks as they end up playing around the same ideas. These frameworks fall into one of two categories: same and different species. In the case of the Genies, Giratina, and Indeedee, you are only able to use a single form on any given team because of species clause. (i.e. cannot have Thunderous-Incarnate and Thunderous-Therian simultaneously.) As for Gardevoir/Gallade, Nidoking/Nidoqueen, and Sawk/Throh, they are different species so you could use both on the same team if you wanted to. Beyond that, the differences between these frameworks seem so minor and usually only change which stages are identical versus similar. Comparing the categories, I personally find the idea of a mon limited by species clause more novel since we have yet to explore this in any project. I think I will inevitably have to pick a single framework from this group since slating two very similar concepts risks killing both options in the poll.
NFE/Evo Pair
I think there will be a group of people that view this project in passing as just a roundabout way of creating an eviolite framework. To those people, I would say this framework has more freedom than what is visible at a glance. Yes, the easiest path would be taking a Porygon-2/Porygon-Z route where the NFE takes on the defensive role using eviolite and the evolution takes on an offensive role: however, we do have the option to flip those roles and have the NFE be the offensive one. While more difficult, it would be the more unique route to pursue. Also, the inclusion of Scyther/Scizor as an example in the submission lets us consider the possibilities of what this framework could produce that is not just “the obvious eviolite answer.”
Move-Based Form Change Ability
I will start by saying this framework could probably benefit from being renamed. The way it reads currently has led me and others to assume that this form change is similar to Meloetta’s mechanic. As stated in the framework, Meloetta does NOT count. This is an ability-based form change that is triggered by a move. I do think this framework has some potential as written, but I also think this framework could benefit from just being a more general “in-battle form change” framework. This would allow Meloetta, Aegislash, Morpiko, and any other in-battle form change to be options. Going back to the as written framework, we would need to iron out whether this ability would track like Aegislash and reset every time the mon is switched out or if it would track like Eiscue and return to battle in the same form it left. No matter what, this framework will more than likely require a custom element since I do believe anything that currently exists is not worth exploring.
Edit: I just noticed Spoo jumped in with an in-battle form change too.
Legendaries
This will cover Legendary Duo and Cover Legend CAP.
I think these frameworks risk being detrimental to the metagame. I do not have faith in the community to navigate this type of project with the finesse it requires let alone twice. We have struggled in the past with power balance, especially during Jumbao’s, Equilibra’s, and Astrolotl’s projects. The last thing we need is to greenlight an excess amount of power (more than the example projects I listed) and not be able to responsibly build with it. I think there are only a few routes we could take that avoid an absurd final product and getting users onboard with these reasonable routes will potentially be a difficult task. I am willing to reconsider my stance, but I know for a fact a duo is beyond our capabilities as a community.
Steelsurge Setter
Oh, how I am torn over this framework. I consider this the most meta-focused framework posted as of right now (1am GMT-6), and I am SO interested in what this type of project could yield. I had honestly forgotten this mechanic existed since it is locked behind a max move. The problem here is that I do not know if this is even a legal framework. I will be inquiring with the mods about this as I can see both an argument for and against it. This could drastically alter our metagame and raise the level of entry for new users. Given that the project was designed to be parallel to OU, would a new entry hazard destabilize the ease of transitioning to our metagame and hurt our project as a result?
Ultra Beast
This seems fine, and I remember this being a popular option last framework. I do not have much to add about this project. To the dismay of many, I would recommend dropping the requirement for prime number stats. Naganadel breaks the prime stat rule with its speed, and I think it would allow for greater diversity when adhering to the BSR limits come stats stage. Most stat submissions that make slate follow a similar stat distribution, so I would not be surprised if submissions look nearly identical if users must select from the same handful of numbers. I will also mention that this framework did not stipulate the prime stats when it was last submitted for CAP 25 and placed 2nd to starters in the final poll and 1st in earlier polling.
A Pair of Fossils
I see that this was edited after I started writing last night. I do not have the time to fully rewrite about this, so I apologize. Is the restriction regarding base stats saying they will have the exact same spread or identical BST?
Silvally/Arceus-like Forms
I guess I am struggling to fully comprehend what it is this framework aims to do. You outline a Silvally/Arceus-like approach, but then address movepool and ability which make me think that you want this to end up as a Rotom-like pokemon. Would this need a custom ability to replicate the functionality of Arceus? Also, would we be aiming to make forms for each type or would we try to narrow the scope of this project so we do not create unnecessary bloat the way the unused Silvally forms do?
Regional Forms
I was anticipating seeing this again. I think the novelty of this idea has diminished with the introduction of CAP buffs. I know there is slightly more we could do here compared to a standard buff process since more fundamental elements of a CAP could be altered. A few of the mods are concerned with potential issues this could spark, mainly with art and permissions to redesign. Also, I would be worried about replicating A-Muk and just outclassing the original mon we select. Most of my commentary is reflected in the submission anyway.
Protean/Libero User
I appreciate the simplicity of this framework. While a very powerful option, I believe the community has better intuition when it would come to balancing protean/libero compared to the power granted from a legendary framework. I do think the questions posed at the end of this framework are underwhelming. The most important element would be how are we effectively preserving checks/counters? If we disregard prioritizing strong counterplay, we run into the problems seen with both Greninja and Cinderace.
CAP 30 Specific Buff Item
Why is it that “A knocked krill is a dead krill” rings out in my head? I have no major gripes with this framework. I think we risk balancing this mon around its boosting item too much and it becomes underwhelming without it. It is the same argument that dissuades us from selecting magic guard each project it is recommended (i.e. life orb dependency). Provided we manage to avoid that problem, this could be a promising framework.
Random Slate
I get to avoid the backlash that comes with creating slates? Sign me up! But in all seriousness, I am not opposed to this framework. I like the idea of having to MacGyver a solution from a random slate of tools. Also, I think it would be refreshing to have a stronger emphasis on debating between options versus trying to submit winning options.
-ate choice CAP
This is potentially very problematic. It reintroduces the same issues brought up when multi-attack was submitted for CAP 29’s concept. I think we would have to limit this framework to the Electric/Ice example shared in the post. It would need to pick an -ate ability to access one of its stabs, but it cannot use both stabs simultaneously. The issues are still there in that example, but at least it is more manageable.
Route 1 CAP
I have a feeling this is just going to end up as route 1 bird. I am unconvinced there would be major support to go for the other 2 routes proposed here. With the low BST and the bad typing limitations, rodents and bugs have failed to break through into OU the way birds have. If we could just focus on the low BST instead of the combination with type, I think this would instantly be an exciting challenge for the competitive side of the project but still provide the flavor aspect I know people want with a framework. I do believe low BST is a legal concept on its own too.
Multi-Ability Ability
I am going to say this illegal. The OP disallows large-scale custom elements which this is doing. I also think this would be a nightmare to implement since there would be so many combinations leadership would have to entertain. I think we risk creating something incredibly unbalanced since the only Pokémon we have as reference for this framework has one useless situational ability as part of the combination.
As a closing remark, I have noticed most frameworks have pushed for a flavor-focused idea.
I would like to see more ideas that push the structure of the project similar to Random Slate and Fight For Your Right
as well as frameworks that introduce meta-relevant ideas and mechanics like Steelsurge. This will help create an adequately diverse slate for the poll.