CAP 18 CAP 18 - Part 9 - Attacking Moves Poll

Status
Not open for further replies.

jas61292

used substitute
is a Community Contributoris a Top CAP Contributoris a Forum Moderator Alumnusis a Battle Simulator Moderator Alumnus
This poll's purpose is to decide by vote whether the moves marked as Controversial in the Attacking Moves Discussion thread will be allowed for CAP 18's movepool. The linked thread contains the discussion that led to these moves being voted on. Note that while disallowed moves will not be allowed in any movepool submission, allowed moves will not necessarily make it to the winning movepool.

The controversial moves we will be voting on are listed below. Spell the move and its qualifying allow/disallow as you see it below when posting. Do not vote to both allow and disallow the same move, as that is nonsensical and will result in your vote being deleted.

Allow Overheat
Disallow Overheat
Allow Sludge Bomb
Disallow Sludge Bomb
Allow Sludge Wave
Disallow Sludge Wave
This poll operates on the multiple bold voting standard, which is detailed here. Make sure to bold your votes and nothing else. A typical vote looks like this:
Vote A
Vote B
Vote C

Any comments that the voter has would go below the votes in non-bold text. Bold text is used to determine what the user's votes are, so none of the supplementary text should be in bold.
CAP uses automated scripts to count votes. For this reason, it is very important for all ballots to be submitted correctly. If you do not compose a legal ballot, your post will be subject to moderation.
  • The scripts count bold words in ballots, so do NOT bold anything in your ballot other than the options you are voting for.
  • Do NOT put any formatting other than bold in your post.
  • Only one option per line.
  • Spelling of options must be EXACTLY correct and must match the spelling listed above.
  • Capitalization and spaces are ignored by the vote counting scripts, but you probably should not depend on it.
Composing a proper ballot is easy. Enter BBCode Edit Mode (the wrench in the upper right corner). Copy/paste the options directly from the OP to your ballot as plain unbolded text. Delete and/or rearrange the options to suit your preference and the poll type. Bold your vote text using bold tags or re-enter rich text mode, highlight your vote and click B. Spelling or formatting errors may spoil your ballot, so be careful!

This poll will run for 24 hours.

--------------------

CAP18 so far:

Leadership Team:

DetroitLolcat
- Topic Leader
jas61292 - Typing Leader
PttP - Ability Leader
srk1214 - Stats Leader
ginganinja - Movepool Leader
Concept: Major Third

General Description: A Pokemon that forms an effective offensive or defensive core with two lesser-used OU Pokemon.

Justification: Cores have always been an integral part of the metagame, whether you're running Talonflame/Staraptor to brute force everything, Slowbro/Amoonguss/Heatran for Regenerator-Leftovers stalling, or a whole team of Dragons + Magnezone. We've previously explored what it takes to make a successful partnership in CAP11 (Voodoom), but the metagame (and the simulator!) has changed dramatically since Voodoom's creation. I would also like to up the ante a little bit: Instead of just one, can we now take TWO Pokemon and find their missing piece? Whether we opt to build on an established two-Pokemon partnership or choose two previously unrelated Pokemon and put them together, I think that we can certainly find a Voodoom for a more offensive time.

Questions to Be Answered:
  • How do effective cores in the current metagame differ fundamentally from the cores of previous metagames, if at all?
  • Is synergy as important (relative to power) in the current metagame as it previously has been? (That is, has power creep rendered synergy unnecessary?)
  • What differences are there between tailoring a Pokemon to two others and tailoring it to one? What else must be considered besides weaknesses and resistances?
  • How does the addition of a Pokemon to a core change what other Pokemon can be effectively run alongside the core?
  • Does Team Preview make running cores more difficult?
  • Is it possible to create a core uncounterable by a single Pokemon? (For example, Celebi/Heatran/Jellicent was a very effective BW core that got slaughtered by Tyranitar. Can a core force opponents to counter it with another core?)
  • Tagging onto the above, what is required to "counter-core" a core? What combination of offensive and defensive characteristics among "counter-core" members achieves this?
Pokemon CAP18 should threaten:

It's important that, first and foremost, we threaten the Pokemon and strategies that our core has no answer to. In general, the degree to which a Pokemon threatens Latias and Lucario should be the degree to which CAP18 threatens that Pokemon.

Ghost-type Pokemon: Aegislash, Gengar
Fairy-type Pokemon: Clefable, Mawile predominantly. Togekiss, Sylveon and Azumarill to somewhat lesser extents.
Some Fire-type Pokemon: Mega Charizard Y, Heatran, Talonflame to a much lesser extent.
Bug-type Pokemon: Scizor, Forretress, Volcarona.
Ground-type Pokemon*: Landorus-Therian, Hippowdon, Excadrill.

When I say "to a lesser extent", I mean that CAP 18 should be a threatening presence to this Pokemon, but it should not be an ultra-reliable counter. CAP18 should perform well against every Pokemon on this list, but that doesn't mean CAP18 needs to unconditionally switch into and force out these Pokemon. It should likely be able to do one or the other, but countering all of these Pokemon is neither feasible nor recommended.

CAP18 should be able to handle, either by switching in or 1v1, the Pokemon that defeat at least one of our core members that the other one cannot switch into. For example, Mega Charizard X is a Pokemon that defeats Lucario 1v1 that Latias can't switch into. If Multiscale is active, so is Dragonite. Gyarados, before it Mega Evolves, fits this bill.

*With a weakness to Ground, this will be a difficult task. We should threaten these Pokemon as well as we can, but we should not expect to counter Ground-types, but rather defeat them 1v1.

Pokemon CAP18 should be threatened by:

We should be okay with CAP 18 losing to Pokemon that the rest of our core handles well. For example, Latias is a tremendous answer to Rotom-W, and CAP18 is weak to Electric and does not have a STAB that can hit Rotom-W even neutrally. Rotom-W isn't particularly bothered by Fire- and Water-type support options, so making Rotom-W anything other than a threat to CAP18 is fitting a square peg into a round hole. Keldeo is a similar example, although Keldeo is so commonly paired with Pursuit Aegislash (the bane of this core) that it's not safe to let Keldeo counter this CAP.

Bulky Waters: Rotom-W, Keldeo to a much smaller extent.
Bulky Dragons: Latias, Latios, Goodra.
Walls with minimal offensive presence: Chansey, Blissey.

Pokemon not on either of our threatlists should be overly specifically threatening or threatened by CAP 18. Just because a Pokemon is not in the second list doesn't mean it is our prerogative to beat it. The same goes with Pokemon not in the first list: we shouldn't be expected to lose to every Pokemon that we don't threaten.
Typing: Fire / Water
Abilities: Analytic / Infiltrator / ???
Stats: 100 HP / 45 Atk / 80 Def / 135 SpA / 100 SpD / 95 Spe
 
Status
Not open for further replies.

Users Who Are Viewing This Thread (Users: 1, Guests: 0)

Top