Writing PU 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 PU's needs.

It has come to the attention of various QC members that many analysis have been repeating similar mistakes. The goal of this thread is to mention some of those mistakes so that they don't continue to happen.

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.

Remember, copying someone else's analysis and not giving them credit is plagiarism. It is fine to copy someone else's skeleton as a basis, but the content must be in your own words and due credit must be given. This is a BANNABLE offense, so do your own work whenever possible. The QC moderators will not hesitate to infract you for this, so be warned.

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 Poliwrath, don't call it a frog, don't talk about how its macle's fetish animal, just call it Poliwrath 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 PU analysis, it's because either it earned that analysis by having an interesting niche, or it's PU, which means it earned the usage to stay in the PU tier.
  • 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 (Poliwrath is a fantastic glue Pokemon while Snow Warning Aurorus is a hard check to all weather 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 'Kadabra has a great base 120 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. What does a move target specifically? Be descriptive, and when moves are slashed, explain the benefits and downsides of each move.

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. 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 is worth using.

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 Leafeon's threats have been weakened or eliminated, in particularly removing Jumpluff and Scarf Haunter.
  • 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 (an example of this is Pawniard pairing well with Torterra [who can weaken walls like Poliwrath and Pelipper for Pawniard to sweep]).

Appropriate teammates to mention are
  • Pokemon who are supported well by your Pokemon.
  • Pokemon who check or counter threats to that Pokemon. For example, Flying-types such as Swanna and Dodrio check Grass-types (note when I say types, I give examples) such as Torterra and Leafeon.
  • If there is something specific to the playstyle. Weather generally likes other weather sweeper + Stealth Rock and weather setter + Prankster weather setter. Hyper Offense generally likes entry hazards (when mentioning entry hazards say some notable KOs they help to provide, all Pokemon like Entry Hazards but some might need them to turn a 3HKO into a 2HKO)

Remember if saying Pokemon types or move users e.g. Stealth users, give examples of Pokémon or I'll come to you asking why you think Wormadam-Sandy is a good Stealth Rock 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.

--

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 an PU C&C mod or PU QC member will answer.
 
i'd stress specificity very heavily in moves; if simipour uses ice beam for grass-types, what are its common targets? what targets are hit harder by psyshock on ninetales than dark pulse (and vice versa)? what targets do destiny bond/sub on haunter help against? such questions need to be answered with examples, and it's almost always preferred to give examples rather than generalizing which i would definitely stress.
 
Last edited:
Wanted to stress on Don't reserve analyses of Pokemon that you haven't used.
Because that really gets on my nerves and makes QC's job a lot more difficult. It is fine if you don't have particular experience with one of the sets of an analysis or if you have used the Pokemon only a handful of times but you should at least know what is going on in PU. Happy Writing!
 
http://www.smogon.com/forums/threads/the-new-analysis-formatting-guide.3537802/

Ok there was an update to the analysis format so be sure to follow it. For reference a copypaste of what your analyses should look like now.

[OVERVIEW]

Generalize what the Pokemon does in the metagame and as a whole and why you should or shouldn't consider using it on your teams.

[SET]
name: SET NAME
move 1:
move 2:
move 3:
move 4:
item:
ability:
nature:
evs:

[SET COMMENTS]
Moves
========

Describe what the moves on the set do.

Set Details
========

Describe the other aspects of the set such as what the EVs do and nature/item.

Usage Tips
========

Describe how to use the Pokemon in question.

Team Options
========

Describe some teammates that would be a good idea to pair with this Pokemon.

[STRATEGY COMMENTS]
Other Options
=============

List some options for the Pokemon user that are plausible but not always recommended due to either being not consistent enough or too outclassed by other Pokemon in the metagame.

Checks and Counters
===================

**Insert Threat Here**: Describe why the Pokemon is a threat.
 

WhiteDMist

Path>Goal
is a Site Content Manager Alumnusis a Team Rater Alumnusis a Forum Moderator Alumnusis a Community Contributor Alumnusis a CAP Contributor Alumnusis a Top Contributor Alumnus
Just an FYI, unless you have a blank skeleton or accidentally posted a thread twice, don't delete your threads in this OM C&C subforum. A mod will do so if deemed necessary. If the thread was an analysis, let the QC team reject it (seriously, it takes 3 rejections before removal).

Consider this less work for you! :)
 

Anty

let's drop
is a Site Content Manager Alumnusis a Team Rater Alumnusis a Community Leader Alumnusis a Community Contributor Alumnusis a Tiering Contributor Alumnusis a Top Contributor Alumnusis a Smogon Media Contributor Alumnus
Im posting here as i have noticed the same things that keep occurring among analysis' overviews.

Firstly please explain the niche of the Pokemon, ie why would you use this pokemon over other similar pokemon. For example in my Carracosta analysis i say:
Carracosta's good bulk and access to Aqua Jet give it a niche over Barbaracle, and Solid Rock and its Water typing justify use over defensive Golem or Piloswine.
This is just one line of information yet it is very important as it tells the reader why you should use it. I know now we are getting to worse Pokemon which have smaller niches, but it is still important to say its niche and also pokes that outclass it. For example in Raiza's wartortle analysis he says:
Wartortle is almost outclassed by other Pokemon that can keep entry hazard control, such as Armaldo, Pelipper, and Togetic, though Wartortle carries some slight niches that allow it to set itself apart from them, and be considered for a teamslot on a defensive team that struggles against entry hazards, even if it's extremely situational.

Secondly, try not to oversell the Pokemon. Yes, gigalith may have be incredibly powerful but it is almost entirely outclassed by golem which is important you state stuff like that in the analysis (note: this example is unrelated to the gigalith analysis). If your pokemon is in C/D rank, it is for a reason and we don't want to make users think gigalith is a top tier pokemon.

Lastly, information about the Pokemon you can find on the dex is worthless. Everyone knows that water types are weak to electric and grass, however, saying how that is relevant towards the metagame is helpful. Mentioning a Pokemon is weak to bug is not at all important due to the lack of bug types, however talking in detail about how a pokemon is weak to grass which limits its walling due to it being a common type, actually contains relevant information. Also talking about weaknesses tends to be more relevant for walls and possibly set up sweepers.
 
CLERIC SUPPORT, SLOW VOLT SWITCH/UTURN, HEALING WISH, DEFOG, AND MEMENTO ARENT YOUR GENERIC FREE PASS TO GET OVER TEAM OPTIONS

I mean literally everything appreciates that but team options have to be specific and its obvious that any Mon likes to have hazards removal or volt switch support so please don't put it on every Mon ever especially since me and the qc team tend to have you remove it. Stop with lazy writing :(
 

Anty

let's drop
is a Site Content Manager Alumnusis a Team Rater Alumnusis a Community Leader Alumnusis a Community Contributor Alumnusis a Tiering Contributor Alumnusis a Top Contributor Alumnusis a Smogon Media Contributor Alumnus
This should be obvious, but when implementing a check from a QC member you should implement everything, or if you disagree with a point you should bring it up with a reason as to why you disagree with it.
 
I've seen quite a few people do this over my time in C&C: please don't post a thread for your analysis until you at least have the set(s) filled out. It's generally not a huge deal but it can be annoying for QC members when they get an alert for a thread and then go to look at it to find a blank skeleton or an "I'll do this soon".
 

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

Top