Getting my two-cents in officially before this thread locks, wew lad, let's go. I've been commenting a lot in the discord about how I envision this project moving forward, but I think it's worth summarizing everything here at least.
- How important is defensive utility for a Pokemon whose primary function is to support its teammates?
There's part of me that really fears that this CAP might just turn into a weird wallbreaker or specialized pivot depending on how far or how short we go on the defensive utility on this mon. My ultimate vision of this is a mon that we can actually put onto this spectrum in a couple different ways. We don't want to pigeonhole ourselves in this problem. We have to adhere to the idea of "Offensive Support" in thihs concept, so regardless of whether or not we give CAP27 a more defensive utility oriented set, we will always need to keep the offensive prospects in mind. Whether or not the more offensive set becomes the favored set is something I guess we'll see further down the line.
That being said, defensive utility is quite important for a support mon as a whole. From the discord discussion, this mon is going to need to be a mon that can have points where it can absolutely switch in without fear but will also need to switch out at an appropriate time. While this does sound quite like a pivot, the switches can be defined as two specific cases: forced and unforced. Forced switches are pretty obvious, a mon comes in on CAP27 and it forces CAP27 to switch with its teammates (switching in a direct counter for example), while unforced switches are when CAP27 chooses to switch out (U-turn, wishpassing etc.) . Ideally in this case, CAP27 should be able to support its team in both cases ideally transforming forced switches into psuedo-unforced switches, and if that means that CAP27 needs more defensive utility to do so, then we have to do so.
Let me just give a brief example to explain what I mean: you have a Clefable with Wish and no fire coverage that you brought in on a choice locked Hydreigon using Draco Meteor. Your opponent also has a banded Aegislash that they will likely switch in on your Clef on the following turn. Instead of having Aegislash essentially check you, you can instead click Wish on the following turn so that when Aegislash comes into check you, you're essentially turning their attempt to force you out into a situation where you were planning to switch in the first place.
Of course, Wishpassing isn't even just the first defensive utility that might come to might, others might consider bulky stats or a good typing, but in general it might be best to have at least some defensive utility options in general, regardless if they're actively or passively used.
- Without Polljumping, how can we achieve defensive utility on a more offensive Pokemon?
To attain these defensive utility capabilities, we need to be very conscientious of how we determine our typing, movepool and statistics. I will refrain from any explicit suggestions to avoid polljumping, but instead will give a brief description of the way I would like to see this going down. To me, this mon is made or broken by its movepool and stats and that we'll need to likely be a little more liberal with these two options to make sure CAP27 succeeds. Therefore, I feel that with defensive utility we need to pick a typing that maybe lacks a little defensive capabilities, or at least a typing that's easily exploitable. Again, I'm not going to give explicit suggestions for this typing (see Discord for my not-so-shitposting on my favorite typing atm), but I will say that this typing needs to be easily exploitable so thhat we can prioritize movepool and stats.
By prioritizing movepool and stats we can give CAP27 as mouch offensive or defensive capabilities as we want. Sure, there will be some restrictions based on typing, but in general we can give ourselves some more status-y moves based on the typing that we assign CAP27. Furthermore, the stats on CAP27 should also allow CAP27 to switch into at least some common attacking moves, but also, once again, force it out in other situations (creating those forced switches I referenced earlier). But in general, the defensive utility from this CAP, in my opinion, will come from the moves and stats we give CAP27, not the typing.
- And now that we have a grasp on what we define as a support Pokemon - How offensive does CAP27 need to be in order to actualise our concept? Do we consider the above examples of Tornadus-T, Heatran, TankChomp, Cyrogonal etc as good examples of the balance between offense and support that we should aim for?
The typing however, will be crucial when we consider the offensive capabilities of CAP27. Like Tornadus-T and Hurricane, CAP27 is going to need some reliable and strong STAB move in order to threaten a good portion of the metagame. Like Torn-T being so good in the presence of so many bulky grass types in ORAS OU and SM OU, our CAP should be able to take advantage of a lot of common types with its STABs and its moves. Therefore, not only are our typing and movepool coupled in the defensive utility aspect, they're also incredibly linked in the offensive utility portion as well. There needs to be some kind of effective STAB option for CAP27 to put offensive presence and pressure into the game.
But I'd also like to once again to return to the idea of forced switches and how that limits CAP27's offensive presence. Like in the defensive sense, CAP27, needs to have things that ouright force it out, lest we become something like a CAP version of Clefable with all of its coverage options (because believe me, I've had people saying my concept is just CAP Clefable since I submitted it). There needs to be a gap in CAP27's coverage that forces it to switch out over the course of the battle.
I think that Heatran in SM OU is a place that we want to avoid. This problem isn't as prevalent this gen due to the fact that Z-Moves aren't a thing here, but consider. Bulky Water types were usually a pretty consistent check for Tran on most teams in Gens 4, 5, and 6. However, in Gen 7 , Heatran became even better beecause now it got a reliable way to beat previous checks with Bloom Doom. Is this a problem now? No. Not really. Will it be a problem? Probably not. But Heatran even having Solarbeam still does present the possibility of it being able to beat things it normally shouldn't be able to. CAP27 should not have the opportunity to beat any of its checks, even through cheesing (though isn't that just the definition of a counter?). But essentially my point is with Heatran, CAP27 should not have specific coverage options, that by not having, prevent it from having too much offensive coverage therein making it more of a sweeper etc.
That's my thoughts. Glad I could get them all in here. I'm sure a lot of this has been said, but this is how I'd envision this project happening. See you all in the Discord.
TL;DR - Exploitable typing that lets us have more freedom with moves and stats :]