kenn said:1. How does an ability complement the idea of being a "fast wall"? Should we take advantage of our Speed or should we focus more on our defenses?
Seen a couple posts that felt this was suggesting Abilities that "influence" our Speed, credit to Ama for first addressing this notion as misguided but it bears repeating that
abilities which take advantage of our Speed don't need to be affecting Speed as much as they are affected by the Speed stat. This latter definition is better here as it encompasses the former while broadening the list of options. I.E. an ability such as Weak Armor which increases Speed conditionally is affected by our Speed as what exactly we can outpace at +2, +4, depends on how fast we are allowed to go initially: you benefit a lot more from Weak Armor if you're in the middle Speed tiers (let's say Base 60-90 range) versus the slowest tiers where the boosts still leave you outpaced, or the highest tiers where that additional Speed starts being superfluous. Of course, Abilities which are affected by Speed aren't always direct. The Multiscale example demonstrates this to a tee, as being able to heal before the opponent can hit us again reactivates Multiscale, bolstering our defense in a way a slower Wall could only dream of.
For the question proper, an Ability whose effectiveness is improved as a result of being faster than the opponent is significantly more novel than one that just makes us a better wall, especially when you consider than CAP 33 is poised to do this better than any other prospective wall we could make in the future by virtue of, that being the whole bloody point? This doesn't mean that an Ability which makes us stronger defensively is inherently bad, just less interesting in relation to the process. No matter the case, since our Speed and our functionality as a Wall is looking to be intertwined, there's not a wrong option here in my eyes, but rather a choice between focusing in on our Speed being the best defensive aspect, or solidifying our defensive profile to observe how being unusually fast influences such a Pokemon.
kenn said:2. Since most CAPs are built to be offensive, how do we want our ability to exemplify being defensive? Are immunity/resist giving abilities more important or do general purpose abilities sound more appealing?
Allow me to play the Devil's Advocate (I don't get to do this much we're not on good terms).
A lot of people have shown disinterest with immunities due to feeling less interesting, not really interacting much with our concept, and overall a feeling of being "overdone" or "lazy." In some ways, I agree, we tend to enjoy endowing our CAPs with immunities to shore up defensive holes we see, and sometimes this is done out of lack of confidence in our current direction. Here's the thing, though: we don't have to use immunities this way, and we've been significantly more nuanced about this in the past than you may think.
On the surface, Saharaja's Water Absorb may look like us going "oh, our mono-Ground type doesn't have a lot of benefits over other Ground-types, we should give it an immunity so it stands out among competition!" Such a view ignores how fantastic of an option Water Absorb was to support our concept. Yes, the benefit of being immune to Water on a Ground type is as simple as that, but being immune to Water
specifically was because Urshifu-Rapid's Surging Strikes was challenging the usefulness of Diamond Storm's +2 Defense boost due to the 100% crit chance. Being immune to this move was a great way to better leverage our Defense boost. Not only that, but since Diamond Storm is a strong physical move, and thus it was safe to assume we wanted at least the capacity to use our Attack stat, being immune to Scald and its high Burn chance was great to keep our offensive potential safe during a match. Water Absorb was more than just goodstuffs for the sake of goodstuffs: it actively improved the function of Diamond Storm, and thus wound up one of the most pro-concept choices available.
What I am illustrating here is that an immunity Ability shouldn't be off the table, especially if it directly improves our function as a fast wall. What I don't really want to see is us supporting an Ability like Sap Sipper because "we're weak to grass as a water type... but what if no????" or Levitate because "ahh we should be immune to baxcaliburrr earthquake or else we lose to +2!!" since that is the boring and tacky approach most people are distasteful of. Rather, there should be a specific reason as to why that Ability is benefitting our fast wall in a way a slower wall wouldn't appreciate.
Resist Abilities haven't seen the same backlash as we are still taking damage, and I feel similarly about them as well. Water/Fairy doesn't really need either but the immunities eat up a good deal of our power budget compared to a simple resist. Even for a Water type, Flash Fire sounds like a much better deal than Heatproof even when the latter reduces burn damage, simply because no damage is infinitely better than some, and it lets us remain a hard answer to Fire-type moves should we Terastallize. These abilities aren't super common and many feel redundant here, but there's nothing particularly bad about them.
As for general purpose Abilities, I still feel the more desirable options are those which our Speed stat directly influences the use of, but I am less stringent on this aspect here because a lot of the Abilities which fall under this category are more unique paths for us to pursue. There's a couple really strong Abilities in this camp I would like us to avoid using as a viability crutch for CAP 33, yet as I mentioned with regard to immunities, if it's pro-concept than we shouldn't be so quick to dismiss it.
kenn said:3. Should any defensively potent abilities with offensive potential baked into them, such as Water Bubble or Magic Guard, be discouraged? Yes? No? Why?
I'm in the camp of having our Primary Ability be geared towards walling specifically, and if we have the room to do so a Secondary that lets us be a more proactive threat. So you can imagine I'm not very high on Abilities which blur the line between defense and offense. These feel more restrictive on our build because of a cascading (water pun) effect on process scope. Being fast is a great trait in general, so although we want to be a wall, if our STABs and Ability let us play offensively than there's a good chance we do just that, unless we severely cripple our attacking stats to avoid this situation, at which point we aren't threatening offensively unless we go out of our way to be, and then we're probably overly passive and end up a less good wall out of a preemptive fear of not being one in the first place. If an ability lets us function a little better offensively that's fine, but we should be extra cautious here to make sure we're not overdoing the offensive potential of our CAP; this is something we can accomplish quite easily during Stats and Moves stages and don't need to make it a priority here, when our Ability can provide us a function the other two can't accomplish in the same manner.