This thread is similar to the concept assessment thread, in that we're not going to be voting or deciding on anything here, but we'll instead try to come to a consensus on what we want this Pokemon to be incapable of handling (which would be reflected in the later move discussions).
The actual definition of a counter is something that can switch into any one of the common movesets a specific threat runs, and become a threat immediately. For example, Heatran is a counter to Skarmory, because Skarmory can't really do anything to it while Heatran can hit Skarmory with its Fire STAB. A "check" is a Pokemon that can switch into one or more of a Pokemon's common attacks and force it out. For example, Latias is a check to Salamence, because it can switch into Fire/Ground/Fighing attacks and threaten an OHKO with its Dragon STAB. However, it can't switch into one of Salamence's Dragon attacks, and if it Dragon Dances on the switch, it will be outrun and OHKOed. Counters, checks, and anything in between for CAP10 are grounds for discussion here.
Here is our Pokemon:
Stat Spread: 151/84/73/83/74/105
Ability: Trace
Ability: Magic Guard
Important: I'm very aware that the concept of a utility counter, something that can be customized to deal with virtually anything, is something that's difficult to customize "counters" to. However, it is very important to discuss the extent to which we want this Pokemon to be dominating what it switches into and make sure that it doesn't cover too many threats at a time. In addition, walls are not Pokemon to be countered, but broken, and I'm pretty sure we're all agreed on the fact that this is not supposed to be a wall breaker. So bringing up defensive counters is a valid way to discuss this as well.
Rules:
The actual definition of a counter is something that can switch into any one of the common movesets a specific threat runs, and become a threat immediately. For example, Heatran is a counter to Skarmory, because Skarmory can't really do anything to it while Heatran can hit Skarmory with its Fire STAB. A "check" is a Pokemon that can switch into one or more of a Pokemon's common attacks and force it out. For example, Latias is a check to Salamence, because it can switch into Fire/Ground/Fighing attacks and threaten an OHKO with its Dragon STAB. However, it can't switch into one of Salamence's Dragon attacks, and if it Dragon Dances on the switch, it will be outrun and OHKOed. Counters, checks, and anything in between for CAP10 are grounds for discussion here.
Here is our Pokemon:
Typing: Water/Electricreachzero said:Name: Utility Counter
General Description: This Pokemon is capable of being customized to counter virtually any specific Pokemon, but is incapable of countering a large number of Pokemon at the same time.
Justification: It is not unusual for people to say that "versatility is broken" from an offensive standpoint; less attention is given to versatile defensive Pokemon such as Zapdos or Hariyama. This Pokemon would allow us to study the impact of having a Pokemon that is capable of dealing with such varied threats as Salamence, Lucario, and Gengar....but not all at once.
Questions To Be Answered:
--How useful is defensive versatility in a metagame with so many different threats to account for?
--Given the existence of a Pokemon that can hard counter only specific major threats, which threats will be prepared for the most?
--How would team building change if certain difficult-to-prepare-for threats became easier to prepare for?
--Which is more useful, a Pokemon that can somewhat handle a wide range of threats, or a Pokemon that can handle a few threats extremely well?
Stat Spread: 151/84/73/83/74/105
Ability: Trace
Ability: Magic Guard
Important: I'm very aware that the concept of a utility counter, something that can be customized to deal with virtually anything, is something that's difficult to customize "counters" to. However, it is very important to discuss the extent to which we want this Pokemon to be dominating what it switches into and make sure that it doesn't cover too many threats at a time. In addition, walls are not Pokemon to be countered, but broken, and I'm pretty sure we're all agreed on the fact that this is not supposed to be a wall breaker. So bringing up defensive counters is a valid way to discuss this as well.
Rules:
- My definitions of counter/check are the ones you will be following. This is very simple, but important. A lot of people mix up check and counter on a regular basis, and it's important to reference the definitions in the OU to make sure that you aren't confusing people, especially me.
- No threadhogging. This is an open forum for discussion, and it's REALLY annoying when this kind of thing becomes a back-and-forth between a few users. I understand this can be a bit tough when the thread lasts for a while, so I'll be sure to not let this drag.
- No poll jumping. This actually isn't as big of a deal at this point, considering we only need to work on the movepools at this point, but I would appreciate it if you didn't reference entire movepools in your posts. It's okay to talk about this Pokemon not getting a particular type of move if we want a certain Pokemon to be able to check/counter it.
- Don't get hung up on one threat. Like all discussions, this ought to remain fresh throughout the time it's up. One particular scenario/threat/etc should not be dominating the discussion for a long time, so I urge you to keep bringing up new points consistently.
- Shut up with the bandwagoning. In pretty much any discussion, this one being no exception, you are trying to convince me of your points. I don't care if you agree with a user and want to express it by saying "I agree with this user for the reasons they stated". Post if you have something new to express.