So I had made a big post regarding this:
In which I argued for the need to discuss the effect Drought would have on the CAP metagame before simply throwing it in for "flavor" reasons.
Now DK and RD are assuring us that there would be a second discussion and vote before it would ever be released, which is sort of what I was asking for. However, I'm still not sure if it's fair to ask us to vote on Drought without discussing those obvious potential consequences, if the second vote won't even be open to us. Is this the case? Because if so, it's still a "flavor" decision that could end up having massive consequences on the CAP metagame, which the same people who voted might not have any control over. If that's the case, then we still have reason to express concerns about the CAP metagame, since this vote will be our last chance to actually do anything about it. I know the CAP metagame is pretty low on our list of priorities, but last time I checked so was flavor. If we aren't allowed to talk about any of the incredibly real (but not relevant?) consequences that Unreleased Drought could have, then can we just have traditional flavor abilities on the slate? Only one or the other makes sense to me. Either let us have a discussion tailored to the unexplored area of "unreleased 'flavor' ability that is actually one of the strongest abilities in the game" or let us only talk about flavor and only vote about flavor. The main reason we usually do not consider the CAP metagame is because we are supposed to craft a pokemon for the OU metagame, and any changes would affect its performance in both. However, we are clearly not affecting the playtest with an unreleased ability, so really there should be an exception (much like the one that allows Drought to be a flavor ability). I'm not saying this new wave of Drought is a malicious conspiracy but right now pushing an ability whose only possible effect is in the CAP metagame and then saying "nono, we don't talk about the CAP metagame" looks really bad, especially with an ability that was such a polarizing issue.
As for Drought flavor-wise, I think it makes no sense, and if flavor were truly the only thing we were deciding on, I don't think it would belong on the slate. It completely contradicts Dry Skin, an ability that implies the pokemon wants to stay moist. Really, the pokemon who currently have Dry Skin are a fungus (obvious relation to moisture) a frog (obvious relation to moisture) and an opera singer (less obvious relation to moisture but I'll argue it later). The battle effect of healing in rain and losing health in sun supports this completely. So we'd be painting an image of some Mollux who stay in moist habitats (underwater?) because of the potential dangers of their skin drying out, while others go around causing droughts by their mere presence (a predicament similar to DJD's radioactive dog perhaps). It really doesn't make sense at all, regardless of whether GF's previous picks for Drought have anything in common. Speaking of pokemon that GF gave Drought to, remember Groudon? The pokemon who wanted to dry out the oceans so that the land pokemon could thrive to the exclusion of the sea pokemon? Groudons whole purpose for being manifests in the game mechanics as its ability, Drought. Yet we want to give this same ability not only to a pokemon based on a species that is notoriously threatened by a lack of moisture (salt on slugs anyone?), but to such a pokemon whose other ability already reflects that aspect of its biology. To me, it makes no sense.
Of course, I might still vote for Drought since it would be cool in the CAP metagame.
[HIDE="reason for Jynx having Dry Skin]
Although the basis of Jynx' design is pretty hotly debated, it is safe to say from her sprite poses and pokedex description that she is some kind of performer (I say opera singer since she is singing in some sprites and looks like a stereotypical Wagnerian nordic character). As a performer and a female only humanshape pokemon, we can assume she is well versed in beauty and hygiene products. Many of these products are applied to the skin and can leave it dry if they are poor quality products or incorrectly used. Think about how many soaps and beauty products you've seen that advertise moisturizing the skin? Jynx is persnickety about her appearance and perhaps a bit of a drama queen, so she is very particular about her beauty products and will not stand for something that dries her skin. This is obviously a lot more subjective than the fungus or frog but I think my argument stands even if my reasoning is wrong and Jynx' Dry Skin is just an anomaly.
[/HIDE]
Deck Knight said:Drought Unreleased for the playtest, and immediately released in the general CAP metagame once the ladder is rebooted, because we're programming it in but it won't be available during the playtest just like unreleased DW abilities on Pokemon we already know are programmed for them.
In which I argued for the need to discuss the effect Drought would have on the CAP metagame before simply throwing it in for "flavor" reasons.
Now DK and RD are assuring us that there would be a second discussion and vote before it would ever be released, which is sort of what I was asking for. However, I'm still not sure if it's fair to ask us to vote on Drought without discussing those obvious potential consequences, if the second vote won't even be open to us. Is this the case? Because if so, it's still a "flavor" decision that could end up having massive consequences on the CAP metagame, which the same people who voted might not have any control over. If that's the case, then we still have reason to express concerns about the CAP metagame, since this vote will be our last chance to actually do anything about it. I know the CAP metagame is pretty low on our list of priorities, but last time I checked so was flavor. If we aren't allowed to talk about any of the incredibly real (but not relevant?) consequences that Unreleased Drought could have, then can we just have traditional flavor abilities on the slate? Only one or the other makes sense to me. Either let us have a discussion tailored to the unexplored area of "unreleased 'flavor' ability that is actually one of the strongest abilities in the game" or let us only talk about flavor and only vote about flavor. The main reason we usually do not consider the CAP metagame is because we are supposed to craft a pokemon for the OU metagame, and any changes would affect its performance in both. However, we are clearly not affecting the playtest with an unreleased ability, so really there should be an exception (much like the one that allows Drought to be a flavor ability). I'm not saying this new wave of Drought is a malicious conspiracy but right now pushing an ability whose only possible effect is in the CAP metagame and then saying "nono, we don't talk about the CAP metagame" looks really bad, especially with an ability that was such a polarizing issue.
As for Drought flavor-wise, I think it makes no sense, and if flavor were truly the only thing we were deciding on, I don't think it would belong on the slate. It completely contradicts Dry Skin, an ability that implies the pokemon wants to stay moist. Really, the pokemon who currently have Dry Skin are a fungus (obvious relation to moisture) a frog (obvious relation to moisture) and an opera singer (less obvious relation to moisture but I'll argue it later). The battle effect of healing in rain and losing health in sun supports this completely. So we'd be painting an image of some Mollux who stay in moist habitats (underwater?) because of the potential dangers of their skin drying out, while others go around causing droughts by their mere presence (a predicament similar to DJD's radioactive dog perhaps). It really doesn't make sense at all, regardless of whether GF's previous picks for Drought have anything in common. Speaking of pokemon that GF gave Drought to, remember Groudon? The pokemon who wanted to dry out the oceans so that the land pokemon could thrive to the exclusion of the sea pokemon? Groudons whole purpose for being manifests in the game mechanics as its ability, Drought. Yet we want to give this same ability not only to a pokemon based on a species that is notoriously threatened by a lack of moisture (salt on slugs anyone?), but to such a pokemon whose other ability already reflects that aspect of its biology. To me, it makes no sense.
Of course, I might still vote for Drought since it would be cool in the CAP metagame.
[HIDE="reason for Jynx having Dry Skin]
Although the basis of Jynx' design is pretty hotly debated, it is safe to say from her sprite poses and pokedex description that she is some kind of performer (I say opera singer since she is singing in some sprites and looks like a stereotypical Wagnerian nordic character). As a performer and a female only humanshape pokemon, we can assume she is well versed in beauty and hygiene products. Many of these products are applied to the skin and can leave it dry if they are poor quality products or incorrectly used. Think about how many soaps and beauty products you've seen that advertise moisturizing the skin? Jynx is persnickety about her appearance and perhaps a bit of a drama queen, so she is very particular about her beauty products and will not stand for something that dries her skin. This is obviously a lot more subjective than the fungus or frog but I think my argument stands even if my reasoning is wrong and Jynx' Dry Skin is just an anomaly.
[/HIDE]