Popping in to give feedback on the first page of concept submissions. There's a lot to work through here, so apologies if it takes me a while to get to everyone. I'm beyond excited about this lineup of concepts, though -- I feel like I could already put together a strong slate, and it hasn't even been 24 hours, which is a great feeling. Anyways, let's get into the submissions!
Old Dog New Tricks -
quziel
Hide
I liked this concept the last time it was submitted and it's one that I'm still a fan of. You acknowledge the issue that many oldgen sets are impossible to mechanically replicate, and that's a concern I share; a lot of these strategies have also just aged very poorly, so our pool of options might be deceptively small. Still, given the sheer number of cool oldgen OU mons and strategies over the years, I don't think this would significantly impede the process. My other worry would be CAP's general unfamiliarity with oldgens (myself included), especially classic gens, so limiting the scope of what's allowed could be one way to improve accessibility. You might also be able to incorporate some of the questions from
the last time (iirc) the concept was submitted.
NAP TIME -
snake_rattler
Hide
I'm really torn with this submission: I think there's an incredible amount to explore about sleep as a mechanic, but I'm not sure if introducing something of this nature would be a positive addition to the metagame. On a lesser note, sleep's variability in turns makes it sort of difficult to design around -- in general I'm hesitant to put a somewhat unreliable mechanic at the center of a project. The final question here is the most interesting part of this concept to me, and does a great job at illustrating the kind of deep design space that this concept has, despite my concerns.
Schrodinger's CAP -
Explosion Badger
Hide
I think there's something awesome at the core of this concept but I don't love the way that it's written right now. We talked about this on discord a few days ago, so I'll just rehash my thoughts here -- the way I see it, the concept is asking to make a CAP that has two distinct roles as a result of two equally strong abilities, which is a solid starting point. The worry arises that we'd make an incoherent, bloated end product after trying to fit two Pokemon's worth of tools onto a singular chassis, but this is where the moveset restriction comes in: it's a way to narrow the focus of the process and avoid overloading the CAP with options, while simultaneously exploring unique moveset-ability interactions that will give the process depth. Framed like this, it's a concept that I actually like a lot, but the way I see it written doesn't justify why the moveset restriction is necessary; your current justification isn't one that I agree with, either, as I'd say anywhere between a third and a half of OU/CAP mons are heavily defined by their ability. If you frame your justification more like what I outlined here, I think you'll be in better shape. Two last things: ask a question about what we can learn from past CAP processes where we've tried to fit multiple roles onto one mon, and it could help to have one or two examples since your concept is on the more abstract side of things.
Extremist CAP -
Amamama
Hide
This one is fascinating, but it's also really broad. Each of the "extremes" you listed -- stats, typing, and movepool (no ability?) -- probably have enough depth to be their own individual concept. At the least, I would limit it to one extreme trait instead of allowing for several on the same build. This concept is also playing with fire in a way; when we go really hard in one direction, it becomes easier to misjudge exactly how much we need to compensate in the other direction, so there's a very delicate balancing act at play. I like your justification a lot though, CAP really never pursues the kind of builds you're outlining so I agree that there's a ton of value in going down that path.
Patchnote Specialist -
LBN
Hide
You mention wanting to test how effective the buffs/nerfs are, but do we need a CAP process to see that? The Protean nerf clearly worked as the 3 starters are now well-balanced, the weather nerf post-BW was effective otherwise we'd still be having weather wars, and so on. Picking a mechanic that was buffed/nerfed in, say, GSC, also seems sort of pointless -- after all this time, what left is there to learn about how it fares? I think I need to be convinced that these moves/mechanics/etc are ones worth pursuing. Narrowing the scope might help with this; if you only include things changed in Gen 9, you could argue that certain nerfed mechanics are interesting because they were previously too powerful and off-limits for CAP, while certain buffed mechanics present newly viable options for us to explore. Then again, I don't actually know how many things changed between SS and SV, so that might not work. Either way, food for thought.
Sleet Dreams -
sneakyjeans
Hide
Honestly, I'm not a big fan of this one. I think snow is much too niche of a playstyle to be exploring in any real depth -- it's not quite as hopeless as trying to make a Gravity abuser for example, but not much better, either. This concept is also retreading a lot of old ground, which I'd like to avoid if possible. I think there are other possible weather related concepts out there, but snow seems unwise to pursue.
King of Thieves -
SKIPPERGAMEZ
Hide
It would help to get clearer on the language being used here. What strategies are we disrupting exactly? Which playstyles do you think are easy to target? What do you mean by "disrupting the metagame," just not being OP? (This will be relevant for every concept.) Most importantly, what exactly is stealing? Does stealing necessitate gaining something from your opponent? If so, the Soak example is irrelevant. The notion of stealing momentum also introduces a whole new conceptual layer -- what about stealing information, or even "stealing the game" in the case of a setup sweeper? This seems much too broad to me; I think this concept would benefit by clarifying these issues and narrowing its focus.
Reliable Status Abuser -
Garrett
Hide
I like that this concept explores something that CAP rarely touches. There seem to be a lot of of cool routes here, far beyond the obvious Hex bot. I'm looking forward to seeing you develop your thoughts more.
Unorthodox Passivity -
Waldinji
Hide
There are only so many viable routes for resididual/passive damage to begin with, so I think the "unorthodox" restriction limits our scope too much. You ask about how we avoid this CAP being used on offense, but I don't see how that's a bad thing; you also say in your description that you want this CAP to cater to defensive teams, but nothing about the concept itself actually suggests that. If you want to make a concept to improve bulkier playstyles, then go ahead, but that's different than what you have here. You might be able to take some inspiration from
Game of Inches, a very similar concept that was subbed in the past.
Stick Together! -
dex
Hide
Another concept I feel really torn about. Right now, this reads like we just make a generically incredible mon, because that's really just what a glue mon is: a mon that can perform a lot of useful roles at once, and as a result, is really damn good. Glue is just so broad of a category that is almost doesn't exist at all, and the breadth of examples demonstrates this -- "glue mons" are like 50% of the A+ and above ranked mons from every tier ever, so I worry that this concept is too broad and lacks direction. What I do think is really cool about this concept is its relation to teambuilding. The laser focus on common building practices, dissecting the best cores to see what holes they have, breaking down the intricacies of role compression, etc, is all super interesting. Shifting the perspective from "make a really good mon" to "exploring teambuilding" (oversimplifying a bit) would be helpful I think.
Berry Good -
Bice
Hide
This concept has been submitted in some form a few times, and it's never really caught my eye. Berries are an inherently niche item choice for a reason; the item slot is just too valuable to be dedicating to something so situational and reactive, only compounded by the mere existence of Knock Off. It also doesn't help that Natural Gift isn't in SV, eliminating one of the more interesting routes from an already limited concept.
Bang Average -
D2TheW
Hide
I loved this concept the last time you submitted it. I won't make any comments since your post isn't done (or started) yet, but I'm happy to see this one make a return.
High BST Mon -
chartung17
Hide
I think that a BST of this degree would significantly warp the process. Of the three examples you gave for "balanced" high-BST mons, Kyurem and Kyurem-Black were banned in SS, while Hoopa-U was banned in ORAS and wasn't even present last generation. Certain solutions to this issue, specifically the detrimental abilities, have also been explored as recently as Chromera. Gimping the rest of the process to accomodate for a bloated Stats stage isn't something that personally interests me.
Jack of All Trades, Master of One -
Binacle Pinnacle
Hide
This one's not fully written yet, so I won't say much -- but isn't the saying jack of all trades, master of none? Making a mon that's both good at a lot of things + really good at one singular thing sounds potentially dangerous. As is, this sounds similar to dex's concept (giga viable role compression), so keep that in mind when you're fleshing things out.
Dead Men Walking -
Brambane
Hide
I'm more a fan of this than not, though I have a few questions. You ask how we should define "removing" a threat -- and I appreciate leaving it for the community to interpret -- but maybe getting a little clearer on what you're personally envisioning would help. Does the mere presence of an Arghonaut "remove" a Weavile from the game? What about, say, knocking Kril's Life Orb, or Heatran's leftovers? Tricking Pex a Sticky Barb? Block + Spite shenanigans? The line between "denying progress," "crippling," and "making entirely useless" seems a little blurred. If "removing" only means the last definition (Block + Spite, Trick AV, etc), our options seem really narrow and gimmicky; if "removing" is broad enough to include the first definition, I don't think there's much depth in simply making a counter to a strong threat. The most interesting design space, to me, is being really good at crippling foes without resorting to niche gimmicks -- there's a lot of options to work with here, and I could see many of them resulting in a rich process. But the vague language around "removing" sort of obfuscates what you're going for.
Switch Bait -
Enderwither02
Hide
I like this one a lot in theory, but I'm worried that it's a little limited. With the removal of Pursuit, I have a hard time coming up with a lot of directions to take this concept in, especially since you clarify that "the goal of this Pokémon is to directly punish the opponent for switching out of it,
as opposed to simply setting up on a switch or pivoting out to keep momentum" which further limits our routes. Your questions are a nice start, but you can go deeper; maybe take some inspiration from
Miasmaw's winning concept which has a lot of similarities to yours. Overall a great concept, but could it be broadened?
You Only Live Twice -
big pichu
Hide
Playing against Leppa Berry Pawmot has made me want to rip my hair out on a couple occasions, but putting my biases aside, I think there's a lot to consider here. What kinds of team styles/specific Pokemon appreciate Revival support the most or least? Are there any Pokemon/styles that would benefit too much from Revival support, and should thus be made to have poor synergy with us? What's most important in a good Revival Blessing user -- high Speed, strong offenses to force switches, or good bulk? How easy or hard should it be to get off a Revival Blessing in the first place? Feel free to use/edit these questions yourself, these are just things that come to mind off the top of my head. I think the most interesting part of this concept to me is the teambuilding aspect, i.e., designing ourselves to have synergy or anti-synergy with certain Pokemon (like a partner concept but less limited). Ultimately though, my thoughts on this are mostly the same as snake_rattler's concept: Revival Blessing has great design space, but it also legitimately feels like cheating and might not be healthy for the metagame.
Terrain Savant -
faithviolet
Hide
Off the bat, I don't think a terrain abuser is a good choice. The viability of abusers is tied to how good the setters are, and our best setter right now is Indeedee, which should be saying a lot. Focusing on only terrain setters is more limiting, but it's also much more interesting design space: each terrain offers unique support capabilities, and considering how awful our setters are right now, it's good real estate. I also might recommend shifting your focus from using less-prominent terrain effects to using terrain effects unselfishly? This would expand your scope to, say, an ETerrain setter that's intended to support Electric-types or teammates that use Electric-type coverage moves. I'll leave that up to you.
Speed Demon -
Pipotchi
Hide
I like this one. I wish I had more to say about it, but it's well written, the questions are interesting, and the concept itself is a compelling idea that would drive a good process.
CATCH THESE HANDS -
Rabia
Hide
This is a fun idea, but the choice of punching moves specifically feels arbitrary to me. Other than certain punching-specific items/abilities (Punching Gloves and Iron Fist), what do punching moves have going for them that makes them mechanically interesting and worth pursuing? You could concievably take this concept in a lot of directions, which I love -- AV user/drain tank, Choiced user, a revenge killer with priority, utilizing unique abilities like Poison Touch/Long Reach, and so on -- but why not just have a concept about contact moves more broadly? All of the same interesting routes would still be there, but with punching moves, it feels like we're narrowing our scope without good reason. Obviously this concept isn't finished yet, so I'm reserving my judgment; the above is just food for thought as you flesh out your submission.
FOR THE ONE TIME -
nutritious blend
Hide
I intially thought this one was a bit gimmicky and limited, but I think there are more possibilities than I first gave it credit for. I'm specifically reminded of Shadow Force being a possibility that I liked for CAP31. I also like the idea of exploring a mon that performs differently before and after consuming its item, but is viable in both roles -- say, an early-game tank that becomes an unburdern cleaner late-game. I'm not fully onboard yet, just because CAP has made a lot of these mons in the past: Cawmodore, Throat Spray Chromera, Stratagem, Necturna, WP Aurumoth, Sash Syclant, there might be more too. But these were usually side effects of the process rather than intentional design choices, so it could be interesting to explore this idea with more purpose.
Snowballer -
Joeshh
Hide
Finally a concept that lets me make Espathra 2.0, I'm in. Jokes aside, this concept is honestly great. I love your questions and explanation: they do a great job at illustrating the depth of play that a mon like this can bring to the game, and raise some incredibly important discussion points that I would have never considered. This concept would result in an interesting process every step of the way. My one hangup is that CAP has explored similar territory very recently with Saharaja and Venom-P, but that's a minor concern in the grand scheme of things.
Risky Business 2: Electric Spoogaloo -
Da Pizza Man
Hide
10/10 Name. The submission is intriguing in a lot of ways, letting us revisit a concept that didn't get a fair shake and seeing if we've learned anything since then -- we tried to balance risk/reward with Auru, but in the end, all of the risk ended up being the opponent's. Personally speaking though, mons with highly volatile performances usually don't interest me that much. I wouldn't be too excited to make a Cawm twin, or worse yet, NP Torn, but perhaps there are other routes I'm not considering to explore the concept of risk management.