prem

nonsense

Aug 6th, 2011
400
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.81 KB | None | 0 0
  1. Some thoughts that I wrote up a while ago:
  2.  
  3. Quote:
  4. Most of you know that there are flaws in our current suspect system. It works, yeah, but it could be better. I've been reading stuff in policy review about the rating system on PO, the suspect process, nominations et cetera.
  5.  
  6. There are a few problems with the suspect process. The round starts, we have an extended period to test the metagame and assess suspects, then nominate to ascertain suspects to be voted on. There's a double standard though. A notable portion of the community jump at the chance to ban something, but if you ask them to bring something down from ubers, you're shot mid-sentence. This creates problems. If a Pokemon is banned conditionally (manaphy) it has next to no chance of seeing OU ever again. I'm glad that so many people embraced a manaphy retest last round, but I was (IIRC) the first, and one of the only people to mention it. If people were suggesting a drizzle ban, there should have been mentions to test manaphy, as its uber status was largely due to drizzle. There seems to be some unspoken rule that states "Once it's uber it stays."
  7.  
  8. This factor, along with the length and complexity of suspect rounds seems to make voting results a kind of set in stone ultimatum. "We'd better be damn sure that drizzle is broken before we ban it, because it'll never come back." "We can't test Ho-Oh in OU because once we do, it'll be too difficult to reban it."
  9.  
  10. What I'm saying is that there's no flexibility in the suspect system. It's too easy to ban things, and way too difficult to unban things. Once we make a tiering decision, that's it. You've probably seen me talking about what I call the uber stigma before. Once something is in the uber tier it's automatically deemed to be horribly overpowering, soul crushingly broken, and would rip the OU tier from it's very foundations if it were to be unleashed. If we had freedom and flexibility we could test anything. I'm talking about a suspect ladder. I think we had something similar to this back on shoddy; A separate testing ground we could use to make changes to the metagame without upsetting the balance. There are several things we could do with this. The drizzle debate still rages, but we can't quantify the effects that drizzle has on the metagame without removing it. If we banned drizzle on the suspect ladder we could note what changes and see it's actual influence, if the metagame thrives without it, if sand really is held in check by it ect. We could then make informed decisions whether to ban it based on proof.
  11.  
  12. We could also test ubers. It might seem like I'm haphazardly suggesting random stuff for no good reason. I'm not. I believe that some ubers have a shot in OU, and should be given a chance. Why do it though? Why bother? Because it's part of the suspect process. If a pokemon is too much for OU it should be tested and banned, not exiled by default. It should go without saying that this doesn't apply to every uber, but I'm doubtful about some of them. Arceus and mewtwo are almost certainly uber material, but stuff like ho-oh and zekrom aren't so clear cut.
  13.  
  14. Some of you may think that testing ubers is a waste of time because they're ubers. They're all obviously too powerful, any test would be a waste of time, and it would almost ceratainly be a month of aboslute hell that would render the game unplayable.
  15.  
  16. I understand that I'm on the bad side of the argument here. It's my job to convince all of you, but I can't do it without a test. The problem is that nobody wants a test because it's a commitment. At the moment, all we can do is theorymon and ban. This requires commitment, because that's just the nature of the system. Imagine this scenario:
  17.  
  18. Someone wants to ban tyranitar. There are several concerns though, like "is the problem tyranitar or sand?" or "we can't ban tyranitar because he checks so many other things that banning him would uproot the metagame." These problems exist because we can't test a tyranitar ban. We can't ban him from the suspect ladder and see what happens, see if we can actually ban him safely. We just have to decide whether to ban him. Then what? Do we ban him then wait for someone to realize that it was a bad choice, renominate him, drag our feet, and finally reinstate him? Do we ban him for a month only? There's always the danger that, once banned, it could generate arguments on either side, and draw out the process even further. Due to the uber stigma, people might not want to unban him even if it were necessary. How many times have you read stuff like "Blaziken was proven too strong for OU and had to be banned." People would inevitably start making claims like this. The community's perception of tyranitar would change if it were banned. Not the whole community, but enough to create problems. This is the commitment problem that I'm talking about. If we could break the uber stigma, it would lessen the impact of tiering decisions and make the community more open towards complex tests. I think that this kind of action is necessary to deal with drizzle. Because it's not a single pokemon or a single effect, it's too hard to pinpoint the problem and say "right, there's the problem, ban that." We need to test it inside and out in controlled conditions if we're going to take every aspect and possibility into consideration.
  19.  
  20. As for ubers, I believe that the following are viable candidates for an initial test:
  21.  
  22. Manaphy (with or without drizzle)
  23. Reshiram
  24. Zekrom
  25.  
  26. I should point out that reshiram and zekrom were never tested in OU when gen V began.
  27. Basically, an action plan for drizzle that includes implementing a suspect ladder. This round seems to have slowed to a standstill. Noone's really discussing suspects at this point. What do you all think about drizzle at the moment?
  28.  
  29. As for Reshiram and Zekrom, I'll make a case for them below.
  30.  
  31. Firstly, Resh and Zek were never tested in OU. As far as I know, they weren't even discussed. I did some research and found these two threads:
  32.  
  33. http://www.smogon.com/forums/showthread.php?t=79694
  34.  
  35. http://www.smogon.com/forums/showthread.php?t=81568
  36.  
  37. Neither were mentioned in either thread. It seems to me that everyone said "Box legends with 680BSTs, uber."
  38.  
  39. A pokemon should never be judged on base stats. These two deserve a fair test in OU to properly ascertain their tiering. I realize that arceus has never been tested in OU either, but we had little to no experience with resh and zek back then.
  40.  
  41. Thoughts on Zekrom:
  42.  
  43. How exactly is this thing uber? What the hell does it do?
  44.  
  45. Pros:
  46.  
  47. Reasonably bulky.
  48. Quite powerful.
  49. Dragon/Electric typing gives it good neutral coverage and some nice resistances.
  50. Teravolt breaks through sturdy and multiscale.
  51.  
  52. Cons:
  53.  
  54. Barren movepool. Learns no physical ground or fighting moves, and only had focus blast on the special side. No fire moves either.
  55. Slow.
  56. Dragon, ice and ground weaknesses.
  57. Walled by ferrothorn and excadrill.
  58.  
  59. Why exactly is it uber? Decent bulk with 150 attack? Bolt strike? It seems so mediocre on paper. Base 150 attack is nothing to write home about. We already have haxorus, who has an eqaully powerful outrage, mold breaker EQ to deal with steels, and access to swords dance and dragon dance. Offensively, haxorus outshines zekrom by miles.
  60.  
  61. Let's see how it performs in OU. I'll use this spread:
  62.  
  63. Zekrom @ Life orb
  64. Nature: Lonely
  65. 136 Atk / 252 SpA / 120 Spe
  66.  
  67. Draco Meteor
  68. Bolt Strike
  69. Outrage
  70. HP Fire
  71.  
  72. It's the standard attacker from the uber analysis with the HP EVs relegated to speed to hit 245.
  73.  
  74. Ferrothorn
  75.  
  76. Resists dragon and electric. Can leech seed stall and twave in return.
  77.  
  78. Bolt strike: 34% - 40%
  79. Outrage: 32% - 38%
  80. Draco Meteor: 25% - 30%
  81. HP Fire: 69% - 81%
  82.  
  83. Tyranitar
  84.  
  85. Bandtar:
  86.  
  87. Zekrom uses:
  88. Bolt Strike: 71% - 83%
  89. Draco Meteor: 46% - 54%
  90.  
  91. Tyranitar uses:
  92. Stone Edge: 76% - 90%
  93. Crunch/Pursuit: 61% - 72%
  94. Earthquake: OHKO
  95.  
  96. Scarftar:
  97. Zekrom:
  98. Bolt Strike: 84% - 99%
  99. Draco Meteor: 54% - 64%
  100.  
  101. Tyranitar:
  102. Stone Edge: 46% - 55%
  103. Crunch/Pursuit: 37% - 44%
  104. Earthquake: 62% - 73%
  105.  
  106. Scizor
  107.  
  108. Can't do much.
  109.  
  110. Politoed
  111.  
  112. Nope.
  113.  
  114. Gliscor
  115.  
  116. Draco Meteor: 67% - 79%
  117. Outrage: 52% - 61%
  118.  
  119. Earthquake: 58% - 68%
  120.  
  121. Latios (Specs)
  122.  
  123. Zekrom:
  124. Bolt Strike: 61% - 73%
  125. Outrage: OHKO
  126. Draco Meteor: OHKO
  127.  
  128. Latios:
  129. Draco Meteor: 201% - 237%
  130.  
  131. Rotom-W (Standard)
  132.  
  133. Bolt Strike: OHKO
  134. Draco Meteor: 98% - 116%
  135.  
  136. Excadrill (Adamant LO)
  137. Outrage: 59% - 70%
  138. Draco Meteor: 54% - 64%
  139. HP Fire: 73% - 86%
  140.  
  141. +0 Earthquake: OHKO
  142.  
  143. Thundurus
  144. Dragonite
  145. Heatran
  146. Jirachi
  147. Reuniclus
  148. Skarmory
  149. Garchomp
  150. Conkeldurr
  151. Gengar
  152. Jellicent
  153. Starmie
  154. Magnezone
  155. Gyarados
  156. Blissey
  157. Haxorus
  158. Terrakion
  159. Volcarona
  160. Infernape
  161. Ninetales
  162. Espeon
  163. Forretress
  164. Salamence
  165. Vaporeon
  166. Toxicroak
  167. Landorus
  168. Latias
  169. Tentacruel
  170. Breloom
  171. Hydreigon
  172. Celebi
  173. Virizion
  174. Deoxys-S
  175. Bronzong
  176. Metagross
  177. Scrafty
  178. Swampert
  179. Mamoswine
  180. Lucario
  181. Cloyster
  182. Hippowdon
  183. Chandelure
  184. Mienshao
  185. Venusaur
  186. Darmanitan
  187. Machamp
Advertisement
Add Comment
Please, Sign In to add comment