YEA DAT WAY
Hey everyone, the OU tiering council has decided to test Dugtrio.
Dugtrio has been claimed to be the progenitor of the stall craze due to its incredible utility in trapping, and has thus led to further questioning of the role it plays in the metagame. In order to address a direct problem relating to the outcry against stall, we have decided due to popular consensus in the council and in the community, to suspect test Dugtrio.
Dugtrio itself possesses one of the greatest aids to defensive teams: the ability to trap would be stallbreakers and threats to defensive cores. By utilizing it's recent attack buff along with the wide amount of Pokemon it is able to neutralize, Dugtrio has become a favorite pick among defensive builds. With the ability Arena Trap, Dugtrio gains the ability to consistently pressure the opponent through the threat of completely throwing the momentum of the game by eliminating a key counter, or breaker, that threatens the team otherwise.
While at the start of generation seven stall did not see much play, slowly the community began to realize just how powerful a tool Dugtrio possessed in its ability. Dugtrio has the ability to pick apart teams and destroy otherwise solid measures against defensive builds, and is viewed by some to be a ridiculously centralizing force which pushes the need for niche counters onto the average builder. Outside of it's role as a utility 'mon for stall, Dugtrio can also function on more balanced teams which need an efficient way to eliminate select counters. Dugtrio can turn otherwise relatively equal matchups on their head by eliminating specific counters, destroying typical team structures. Dugtrio also functions as a revenge killer to set-up sweepers with its now increasingly common Choice Scarf set, which allows for the assured kill of certain sweepers through Arena Trap.
Due to the council's general belief that it is not Arena Trap that is intrinsically broken, but the user (Dugtrio), we have decided to exclusively suspect test this Pokemon.
For this round we are going to have two alternative ways to qualify for voting:
- Laddering: you will need to achieve a COIL rating of 2700 (or more) in a /!\ game limit of 70 games /!\ on the OU Suspect Test Ladder (in which Dugtrio is banned), that will be implemented very soon.
- Suspect Tours: check McMeghan's thread.
The suspect test will last for approximately 2 weeks and will end on February 23rd.
Use this thread to discuss the suspect and your thoughts on the suspect metagame. If you have any questions, then feel free to contact blunder, CrashinBoomBang, Finchinator, M Dragon, PDC, and/or TDK through a PM. These threads tend to get derailed so please make extra effort to stay on topic. Future suspects need not be discussed in this thread.
Keep in mind that, as usual, it's going to be up to the playerbase to decide the outcome of this test. Good luck and have fun laddering!
/!\Rules for posting in this thread/!\
- No one liners nor uninformed posts;
- No discussion on other potential suspects;
- No discussion on the suspect process;
- You are required to make respectful posts;
- You are required to read this thread before posting.
Failing to follow these simple guidelines will result into your post being deleted and infracted without any prior warning.
/!\ NOTICE /!\ OU will not be tolerating any form of voting manipulation. Any attempt to manipulate votes can result in an infraction, loss of eligibility to vote in the current test, and loss of the Tiering Contributor badge. While we won't necessarily enforce super strict punishment, this won't be tolerated and will be handled accordingly. Voting manipulation can simply be described as attempting to get people to vote a way on the test in inappropriate manners. Bribing with teams to vote a certain way, directly messaging people to vote a certain way, publicly announcing "vote this way" all fall under voting manipulation. If you have any further questions feel free to shoot TDK a PM.
Antar's edit: as with the previous OU tests, the B value for this test is 17.0. To figure out how many battles you will need to have in order to achieve reqs, first determine your GXE (shown on the ladder and when you type /rating) and plug that into the following formula:
N=17.0/log2(40*GXE/2700)
(Google calculator is awesome for this kind of thing).
Here are some sample values:
CODE:
GXE N 100 30 90 41 85 52 80 70 75 112 70 324
Tagging The Immortal so that this can be implemented on PS - thank you!
YEAH DAT WAY
Last edited by a moderator: