As a reminder while we finish up the art polls,, Art has no impact on movepool selection.
- - - - -
Welcome to the Moveset Discussion. Since this is the third project using our new moveset discussion, it is important to make sure you are familiar with all the rules outlined in this post. Be sure to pay attention to what our movepool leader Deck Knight has to say in this thread, as he will be leading the discussion and making the calls on which movesets we will ultimately be going with.
In this stage, we are determining the required and disallowed competitive moves by creating a list of approved movesets. The movesets will be decided based on the competitive needs and limitations of this project. We are not submitting full movepools at this time. There will be a later stage for movepool submissions (level-up sets, egg moves, etc) once the required and disallowed moves have been determined via the accepted movesets.
Moveset Discussion Rules & Guidelines
There should be four kinds of posts in the thread:
The general flow of this thread should go like this:
By the end of this discussion thread, we should have the following outputs:
-------------------
Moveset Submissions
Movesets should be posted in the following format:
Moveset Submission
Name: Choice Band
Move 1: Flare Blitz
Move 2: Sucker Punch
Move 3: U-turn
Move 4: Stone Edge
Ability: Guts
Item: Choice Band
EVs: 252 Atk / 252 Spd
Nature: Jolly
Please keep to the above format so the movepool leader can easily see which posts in the thread are proposing new moveset submissions, and can easily locate the information when updating the top post in the thread.
Ability, Item, EVs, and Nature are optional. All that is required are four moves, a name, and some descriptive information (in bullet form).
Any suggested moveset posted without any reasonable description will be deleted by the moderators. People should not spam movesets, post without checking the movesets already submitted, or post movesets without thinking them through.
Although we are not posting movesets in the full C&C analysis format, you should generally adhere to C&C standards where it makes sense. While there will not be excessively strict moderation on this, use common sense. Don't get too slash-happy with moves, no stupid names, use proper spelling and grammar, etc. These movesets will be put on the CAP subsite immediately at the end of the CAP for the playtest.
If you are unsure of the optimal ability, item, EVs, or nature -- you can leave it out and it can be edited in later over the course of the thread. By the end of the thread, every accepted moveset should be filled in completely. That doesn't mean we need to be 100% sure of every aspect of the moveset. It's fine if we go with our best guess and leave it to the playtest to optimize it.
-------------------
Moveset Edits/Option Submissions
Edits/options should be made by copying the most recent version of the moveset and description into an unattributed quote tags ([ QUOTE][ /QUOTE]). Then make any edits, additions, or replacements in bold text, removals should be in strike-through text. The most recent copy should taken from the top post or from the original submission post, depending on whichever one is most current.
Posters can and should comment on the reasoning and background for any proposed edits outside of Quote tags. Simple wording or spelling corrections do not need any explanation or commentary.
Additional move proposals must be made in the context of one or more movesets. The user cannot simply post "I suggest we add Taunt as an option to all non-choiced movesets", for example.
-------------------
Movepool Leader/Topic Leader Posts
The first post under the OP is reserved by the Movepool Leader, and will serve as the reference post for the current status of the discussion.
When the Movepool Leader determines that a moveset, option, or edit is accepted by intelligent community consensus, they will add/update a list of "Approved Movesets" in the first post. The Movepool Leader SHOULD NOT add every submission to the first post automatically, simply because it was posted in the thread. The Movepool Leader SHOULD NOT add a submission to the first post if it was not actively accepted by intelligent community consensus. "Lack of any response" is not the same as "acceptance". As with all CAP discussion threads, the leader should always use their best judgement.
If a proposal has received significant intelligent feedback (positive or negative), but it has not yet reached consensus, the Movepool leader should add it to an "Under Consideration" list in the first post. If the thread ends with controversial items that can't reach consensus, they will go to a community poll. In most cases, the "Under Consideration" list should be comprised of full movesets or additional option proposals. Edits to the description of most movesets, probably will not require extensive discussion or polling.
As the Movepool Leader makes updates to the first post, they should also post announcements in the thread indicating what they have added or updated. This will allow active discussion participants to easily track the progress of the thread. The Topic Leader should also post regular feedback in the thread, like every other competitive discussion.
---
Typing: Fairy/Fighting
Abilities: Natural Cure / Aroma Veil
Stats: 84/78/86/115/88/119
Leadership Team:
cbrevan - Topic Leader
Elite Lord Sigma - Typing Leader
snake_rattler - Abilities Leader
Snobalt - Stats Leader
Deck Knight - Movepool Leader
Concept:
- - - - -
Welcome to the Moveset Discussion. Since this is the third project using our new moveset discussion, it is important to make sure you are familiar with all the rules outlined in this post. Be sure to pay attention to what our movepool leader Deck Knight has to say in this thread, as he will be leading the discussion and making the calls on which movesets we will ultimately be going with.
In this stage, we are determining the required and disallowed competitive moves by creating a list of approved movesets. The movesets will be decided based on the competitive needs and limitations of this project. We are not submitting full movepools at this time. There will be a later stage for movepool submissions (level-up sets, egg moves, etc) once the required and disallowed moves have been determined via the accepted movesets.
Moveset Discussion Rules & Guidelines
There should be four kinds of posts in the thread:
- Moveset Submissions
- Moveset Edits/Option Submissions
- General Commentary
- Section Leader/Topic Leader Announcements/Updates
The general flow of this thread should go like this:
- People post moveset submissions in a prescribed format (see below)
- Other people suggest to add/remove moves or other options to previously posted movesets (see below)
- Other people propose edits to the descriptive information with previously posted movesets
- Other people comment on the competitive pros and cons of previously posted movesets, additions/removals, and proposed edits
- Continuously over the course of the thread, the movepool leader updates the first post in the thread with the "currently accepted" movesets and other information related to the status of the intelligent community consensus (see below)
By the end of this discussion thread, we should have the following outputs:
- The top post in the thread (maintained by the Movepool Leader) will contain a list of all edited, approved movesets
- The top post will list controversial movesets and/or optional moves that need to be voted on by the community
-------------------
Moveset Submissions
Movesets should be posted in the following format:
Moveset Submission
Name: Choice Band
Move 1: Flare Blitz
Move 2: Sucker Punch
Move 3: U-turn
Move 4: Stone Edge
Ability: Guts
Item: Choice Band
EVs: 252 Atk / 252 Spd
Nature: Jolly
- Because of CAP X's Fire typing, Flare Blitz does a lot of damage.
- Sucker Punch allows it priority, as well as the ability to handle Slowking.
- Stone Edge allows it to OHKO Talonflame
- U-Turn can be used to scout, as well as abuse predicted switches.
- Choice Band is used to amplify damage, and fulfil CAP X's role as a wallbreaker
- In case CAP X gets hit by status conditions, Guts raises its damage output to even higher levels.
Code:
[B]Moveset Submission[/B]
Name:
Move 1:
Move 2:
Move 3:
Move 4:
Ability: (optional)
Item: (optional)
EVs: (optional)
Nature: (optional)
[LIST]
[*]
[*]
[*]
[/LIST]
Please keep to the above format so the movepool leader can easily see which posts in the thread are proposing new moveset submissions, and can easily locate the information when updating the top post in the thread.
Ability, Item, EVs, and Nature are optional. All that is required are four moves, a name, and some descriptive information (in bullet form).
Any suggested moveset posted without any reasonable description will be deleted by the moderators. People should not spam movesets, post without checking the movesets already submitted, or post movesets without thinking them through.
Although we are not posting movesets in the full C&C analysis format, you should generally adhere to C&C standards where it makes sense. While there will not be excessively strict moderation on this, use common sense. Don't get too slash-happy with moves, no stupid names, use proper spelling and grammar, etc. These movesets will be put on the CAP subsite immediately at the end of the CAP for the playtest.
If you are unsure of the optimal ability, item, EVs, or nature -- you can leave it out and it can be edited in later over the course of the thread. By the end of the thread, every accepted moveset should be filled in completely. That doesn't mean we need to be 100% sure of every aspect of the moveset. It's fine if we go with our best guess and leave it to the playtest to optimize it.
-------------------
Moveset Edits/Option Submissions
Edits/options should be made by copying the most recent version of the moveset and description into an unattributed quote tags ([ QUOTE][ /QUOTE]). Then make any edits, additions, or replacements in bold text, removals should be in strike-through text. The most recent copy should taken from the top post or from the original submission post, depending on whichever one is most current.
Posters can and should comment on the reasoning and background for any proposed edits outside of Quote tags. Simple wording or spelling corrections do not need any explanation or commentary.
Additional move proposals must be made in the context of one or more movesets. The user cannot simply post "I suggest we add Taunt as an option to all non-choiced movesets", for example.
-------------------
Movepool Leader/Topic Leader Posts
The first post under the OP is reserved by the Movepool Leader, and will serve as the reference post for the current status of the discussion.
When the Movepool Leader determines that a moveset, option, or edit is accepted by intelligent community consensus, they will add/update a list of "Approved Movesets" in the first post. The Movepool Leader SHOULD NOT add every submission to the first post automatically, simply because it was posted in the thread. The Movepool Leader SHOULD NOT add a submission to the first post if it was not actively accepted by intelligent community consensus. "Lack of any response" is not the same as "acceptance". As with all CAP discussion threads, the leader should always use their best judgement.
If a proposal has received significant intelligent feedback (positive or negative), but it has not yet reached consensus, the Movepool leader should add it to an "Under Consideration" list in the first post. If the thread ends with controversial items that can't reach consensus, they will go to a community poll. In most cases, the "Under Consideration" list should be comprised of full movesets or additional option proposals. Edits to the description of most movesets, probably will not require extensive discussion or polling.
As the Movepool Leader makes updates to the first post, they should also post announcements in the thread indicating what they have added or updated. This will allow active discussion participants to easily track the progress of the thread. The Topic Leader should also post regular feedback in the thread, like every other competitive discussion.
---
Typing: Fairy/Fighting
Abilities: Natural Cure / Aroma Veil
Stats: 84/78/86/115/88/119
Leadership Team:
cbrevan - Topic Leader
Elite Lord Sigma - Typing Leader
snake_rattler - Abilities Leader
Snobalt - Stats Leader
Deck Knight - Movepool Leader
Concept:
Name: Last Act of Defiance
General Description: A Pokemon that is defined by its use of the move Parting Shot.
Justification: Parting Shot is another move that's pretty amazing on paper, but its true usage has yet to be fully explored because it's only available to Pangoro. Pangoro is not the most viable Pokemon OU and is nearly unusable in CAP due to its 4x weakness to Fairy. Moreover, when I've used it in RU (prior it to being banned) and UU, I found myself clicking an attacking move more often than not. With the optimal Parting Shot user in the CAP metagame, we may be able to tap into this move's potential and figure out how it is best utilized. Maybe Last Act of Defiance will be a fast Pokemon that aims to keep up offensive momentum. Maybe it'll use the move like it would use Memento to help a teammate use a boosting move. Maybe it'll be a slow, bulky pivot intended to discourage switching. Maybe it'll do something completely different.
This falls under both actualization and archetype in terms of being a concept. In terms of actualization, it will teach us how to use Parting Shot "properly." Clearly, no other Pokemon, not even Pangoro, comes close to it. Well, users of U-turn, Volt Switch, and Memento come somewhat close, but even then, we'll be able to see what makes Parting Shot different from (and possibly better than) them. In terms of archetype, Last Act of Defiance will give not just the CAP metagame, but also the whole game of Pokemon, a utility Pokemon that we've never seen before, as Parting Shot was not (and still isn't) one of Pangoro's most important assets. Because Parting Shot has so many potential uses, a utility Pokemon such as this can be the ultimate team player for offensive and defensive archetypes alike.
Questions To Be Answered:
- Whether it's pivoting, offensive momentum, Memento-esque support, or something else, what is the "ideal" way to use Parting Shot? Why?
- Considering Pangoro rarely finds the time to use the move, how much should a Pokemon be willing to sacrifice another offensive option for Parting Shot?
- What makes Parting Shot different or similar from Volt Switch, U-turn, and Memento?
- Pangoro is definitely not the ideal Parting Shot user, so what does the ideal user look like?
- What strategies, whether they be certain Pokemon, playstyles, or other factors, will rise to prominence to combat a Parting Shot user?
Last edited: