Writing Battle Spot Analyses - REQUIRED READING

Ares

Fool me...can't get fooled again
is a Site Content Manager Alumnusis a Team Rater Alumnusis a Forum Moderator Alumnusis a Community Contributor Alumnusis a Tiering Contributor Alumnusis a Contributor Alumnus
Shamelessly stolen from other similar threads in OU and Doubles with modifications and additions to meet Battle Spot's needs.

So seeing as Battle Spot analyses are starting out and a lot of new contributors have a lot of questions on how to write, I'm posting this to help writers avoid some of the common mistakes seen in analyses.

General

Don't reserve analyses of Pokemon that you haven't used. We can tell just by reading through it, and analyses that show this are generally reassigned. Generally, we try to work with the analysis writer to bring the analysis up to par, but if it is so far out there that QC members have to basically write the analysis for the person (dictating everything about the sets, redundant details or lack thereof, misinformation), the analysis will be reassigned.

Be detailed. When experienced writers and players (both groups individually) write analyses, the quality is much higher because they include a lot of the finer details. QC can help with this, but only so much. You shouldn't be writing a novel, but when your sections are two or three lines long (this excludes Set Details, which is generally shorter if there isn't much to say), you haven't included enough detail.

Stay on top of your analyses. This means that you should be active in implementing QC comments and concerns, as well as GP checks. If we have to hunt you down to implement a check more than once there is a good chance your analysis will get reassigned.

Overview

The purpose of the Overview is to provide a basic overview of the Pokemon. There was an Overview Revamp thread in BW QC, and while I don't believe that is necessary now, many of the points mentioned in that thread hold true.
  • Cut the fluff. This is a competitive Pokemon site, not the Pokemon Fan Club. We don't care how dashing your Rapidash's flowing mane is, and honestly we don't even really care that it's a horse on fire. Additionally, cut the metaphors, similes, or cute pet names for the Pokemon. If we're talking about Lopunny, don't call it a bunny, don't talk about it scooping up all the field mice and bopping them on the head, just call it Lopuny and concentrate on its competitive aspects.
  • Don't sell the Pokemon. Overviews are about describing the Pokemon, not trying to make people use it. Describe the Pokemon, tell people what they're getting into, and let people decide what Pokemon works for their team. It is not your job to try and convince people that they should use the Pokemon in the analysis. This is something that tends to pop up a lot when people are writing about their "favorite Pokemon" and think that the Pokemon they're writing about gets a short shrift in the metagame, and overhype it in order to make up for it.
  • Don't undersell the Pokemon. I know this seems like it contradicts #2, but there's something to remember: if a Pokemon has an Battle Spot analysis, it's because either it earned that analysis by having an interesting niche within the Battle Spot meta. There is no teiring to go off of, but there are Battle Spot stats to show how much a Pokemon is getting usage. If it is very low then there is a good chance there is a reason for that. QC will have the final say on whether or not something gets an analysis after they've tested said Pokemon's effectiveness in the current meta.
  • Brevity is your friend. Make sure that your writing is flowing and easy to read, but still concise. Overviews should generally not be longer than 2 paragraphs- 1 about strong suits, 1 about weaknesses / issues.
  • There's a difference between concise and short. Make sure that while you don't get all fluffy and overly wordy, you also don't leave out significant detail. An overview should be a general introduction to the Pokemon's strengths and weaknesses, not a couple words about some things the Pokemon can do.
  • This is more stylistic than a "rule", but the first sentence should go out of its way to pull the reader in. You only get one chance to make a first impression, and analyses are no exception. The best analyses have a first sentence that captures the attention of the reader and makes them want to read the rest of the analysis.
General Questions / Statements to answer in the overview
  • What does the Pokemon beat? Notable individual Pokemon, groups, or whole playstyles (Aegislash is really good at taking on multiple threats while something like Tyranitar is a good check to Sun and Rain teams).
  • What general role the Pokemon takes / What teams it fits best on (Stall / Balance / Bulky Offense / Hyper Offense)
  • What threatens this Pokemon? Notable individual Pokemon, groups, or whole playstyles

On top of these points, don't state information that you can see in the dex entry. The typing, ability, and stats are at the top of the page. It is fine to talk about how a Pokemon's defensive typing lets it handle [x threats], how its STABs and coverage make it an excellent wallbreaker, or how its Speed stat puts it above the majority of the tier. What isn't fine is statements like 'Gengar has a great base 130 Special Attack stat'. This provides no useful information to the reader.

The first sentence in the Overview should provide a concise, honest depiction of the Pokemon in the metagame. You should talk about its useful competitive attributes and niche in the metagame, as well as its flaws. A note on flaws: minor things like low Speed for a defensive Pokemon, just because they are technically 'flaws', aren't generally important to mention. You should only talk about major flaws and issues that the Pokemon has. Don't end the overview negatively; it reads strangely and is off-putting to the reader.

Set

Remember that moves should be in order of importance. Generally, moves with more slashes should be further down on the set, and the most important moves should be listed first.

Moves

Don't just say that a move is a good move, especially for STABs. Why is it a good move? It might seem obvious to you, but a newer player won't know the implied meaning. Be descriptive, and when moves are slashed, explain the benefits and downsides of each move.

Include what Pokemon the move hits, don't just say Thunderbolt hits Water-types hard, list relevant threats that the move is useful for. Say its useful for hitting Water-types such as Azumarill, Slowbro, and Suicune, as well as providing neutral coverage on relevant Pokemon.

Set Details

Don't be redundant and obvious when describing EV spreads and natures. Everyone understands that a Jolly nature makes the Pokemon faster and that an Impish nature allows the Pokemon to take physical hits better. Mention specific reasons for spreads and don't say like '4 EVs in Defense boosts the Pokemon's Defense stat', as such a boost is so minuscule that it's pointless to mention.

Don't mention redundant pieces of information like the effect of the ability or that a Mega Stone makes a Pokemon Mega Evolve. However, you should talk about the effect of items like Leftovers and Life Orb; specifically, it is important to discuss how they benefit the Pokemon.

Other things to mention in this section include alternate spreads and items, you should explain why this alternate spread or item is worth using over the main item / spread.

Usage Tips

This section is important, and it seems that some writers just rush through it. Usage Tips should go in-depth on handling common situations encountered with a Pokemon and how it should be played. Remember that newer players read the analyses, so being clear and detailed is especially important in this section.

Tell me how to use the Pokemon. This should focus primarily on the main uses of Pokemon. Things you need to mention
  • When should you use your Pokemon. For example as a lead, late-game, as a switch-in to these types of attacks, after a KO. You should briefly state why too e.g. late-game when Azumarill's threats have been weakened or eliminated, in particularly removing Mega-Venusaur
  • Role of the Pokemon. For example, late-game sweeper, tank, set up weather
  • Important tips specific to the Pokemon.

Remember the focus is about how to use the Pokemon. All the little stuff may still be important, but if your entire Usage Tips is about little details, you've written it wrong.

Team Options

This is another section where being descriptive and thorough is important. Be sure to mention all of the following: what types of teams the Pokemon is useful on, support it needs whether defensively or offensively with multiple examples of partners to fill those roles, and Pokemon that it partners well with in general.

Appropriate teammates to mention are
  • Pokemon who are supported well by your Pokemon. For example, For example, Bisharp discourages Pokemon with Intimidate from switching in, so Pokemon that dislike Intimidate enjoy Bisharp's support, such as Terrakion and Mega Lopunny.
  • Pokemon who check or counter threats to that Pokemon. For example, For example, Flying-types such as Talonflame and Mega Salamence check Grass-types (note when I say types, I give examples)
  • If there is something specific to the playstyle.

Remember if saying Pokemon types or move users e.g. Belly Drum users, give examples of Pokémon or I'll come to you asking why you think Magmar is a good Belly Drum user.

Also try to make Team Options flow well. For example, mention speed control options together where possible instead of all over the paragraph.

Other Options

Please don't mention things that are bad here. The only exception to this is when something might look good at first glance to someone who doesn't understand the Pokemon well, but actually isn't. In this case, you want to explain the supposed merits of the option and why it isn't a good option. Here, you should be mentioning sets, moves, abilities, items, etc. that have niche use on the Pokemon (i.e. for certain teams). Don't add options for the sake of doing so; if a Pokemon doesn't have a bunch of viable additional options, it just doesn't.

Some things are almost viable to get an analysis, but QC decides to stick it in oo for whatever reason. If this is the case place that set at the beginning and give a detailed description of it including spread (if there is a unique spread) or other moves, other things after this that don't come close to warranting a set just get a brief mention.

Checks and Counters

This section should outline specific scenarios that a Pokemon will encounter against said Check / Counter, make sure to be thorough and mention what you can. Remember, you should be approaching this from the perspective of someone trying to prepare for this Pokemon, so include all of the options and techniques that they can use to counteract that Pokemon. Also, make sure you have specific examples and not just general statements.

Some things to remember is that if multiple Pokemon can fall under one category, create one category for them. Do not create multiple sections for individual Pokemon, unless they are a direct hard counter to that Pokemon and deserve a separate mention. An example of this would be that a hard counter to Azumarill is Mega Venusaur, so it would get its own section. Where as Grass-types such as Ferrothorn and Serperior are similar enough to stick under the category of Grass-types. You would then mention the most relevant Grass-types and explain how they take Azumarill on. i.e. Ferrothorn resists Azumarill's STAB moves but has to be wary of Superpower where as Serperior can't switch in on a Play Rough but makes a good check to the Belly Drum variant which relies on Aqua Jet to KO faster threats.

--

Hopefully you took the time to read all of this and have learned from it so the QC team does not have to spend as much time going through and checking your analysis. If you have a general question on the subject feel free to ask, and a Battle Spot C&C mod or Battle Spot QC member will answer.
Venusaur
 

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

Top