phantom
Banned deucer.
SM RU Tiering Methodology
This generation tiering for RU will be done differently than it was in past generations, we will be doing something similar to UU. Here's an explanation for those who are not familiar.
SM RU Tiering System
As with every tier, tiering begins with the beta stage. At the very beginning of RU Beta, the most blatantly overpowered elements of RU were quickbanned by the tier leader.
Approximately once every week, each member of the RU council nominates elements of the metagame that they believe to be banworthy, and the council + 4 community members chosen for their contributions during the previous week will collectively vote on whether or not to ban each of these nominations. Nominations that receive a simple majority of "Ban" votes will be banned from the SM RU tier. This process will be repeated until RU is out of its beta stage, and by this time, everything that is potentially broken should be banned. From then on, suspects will be reintroduced to the tier individually via suspect ladders, and a suspect discussion thread will be opened to the general public. For each suspect, after an appropriate amount of time, the RU council will vote on whether or not to unban it. A simple majority of "Unban" votes will be required to permanently reintroduce the suspect to the RU tier. A vote will also be held following each major tier shift, where council members can nominate current metagame elements for a quickban as well as new drops from UU.
The purpose of this is to create a stable, healthy metagame in the shortest possible time frame. Once this metagame is achieved, we begin to introduce potentially broken elements one at a time into the tier to see if they are truly broken or not. By using a council-only system instead of a public system, we reduce the amount of time needed to get through all the suspects and ensure that the metagame is stable at any time bar the current suspect. Once the tier is deemed stable enough to not need constant quickbans and subsequent suspect tests, we can proceed with public suspect tests.
The Rotating Council
During each beta vote and the following resuspects 4 members of the community will be selected to join the council in voting based on their contributions to the forum, the PS room, and the RU discord channel, as well as tournament and ladder performance. Participation in discussion of suspects during the retest period is also expected from all members of the permanent council.
The RU Metagame
As RU is formed, it is going to be vastly different from its past iterations. While some "staples" may remain, others may find themselves with enough usage to stay in a higher tier or buffs that may send them to BL2. Accordingly, there are few constants between generations and a lot of Pokemon will have to be reexamined and reassessed, leading to this council-based approach and the necessity of many early bans on the notion of something being potentially broken or unhealthy.
Additional Purposes of this thread
This thread will chronologically list the history of RU bans and additions and removals to council. This will make it easier to quickly view how RU tiering history has changed over the years. In addition, this thread will also make note of rotating council members in the vote they participated in.
RU Old Gens Hub
At the beginning of RU, everything that is potentially broken is banned by a council. Then, each banned element is reintroduced to the tier one at a time, and the RU council votes on whether each suspect should be kept in RU or remain BL2.
SM RU Tiering System
As with every tier, tiering begins with the beta stage. At the very beginning of RU Beta, the most blatantly overpowered elements of RU were quickbanned by the tier leader.
Approximately once every week, each member of the RU council nominates elements of the metagame that they believe to be banworthy, and the council + 4 community members chosen for their contributions during the previous week will collectively vote on whether or not to ban each of these nominations. Nominations that receive a simple majority of "Ban" votes will be banned from the SM RU tier. This process will be repeated until RU is out of its beta stage, and by this time, everything that is potentially broken should be banned. From then on, suspects will be reintroduced to the tier individually via suspect ladders, and a suspect discussion thread will be opened to the general public. For each suspect, after an appropriate amount of time, the RU council will vote on whether or not to unban it. A simple majority of "Unban" votes will be required to permanently reintroduce the suspect to the RU tier. A vote will also be held following each major tier shift, where council members can nominate current metagame elements for a quickban as well as new drops from UU.
The purpose of this is to create a stable, healthy metagame in the shortest possible time frame. Once this metagame is achieved, we begin to introduce potentially broken elements one at a time into the tier to see if they are truly broken or not. By using a council-only system instead of a public system, we reduce the amount of time needed to get through all the suspects and ensure that the metagame is stable at any time bar the current suspect. Once the tier is deemed stable enough to not need constant quickbans and subsequent suspect tests, we can proceed with public suspect tests.
The Rotating Council
During each beta vote and the following resuspects 4 members of the community will be selected to join the council in voting based on their contributions to the forum, the PS room, and the RU discord channel, as well as tournament and ladder performance. Participation in discussion of suspects during the retest period is also expected from all members of the permanent council.
The RU Metagame
As RU is formed, it is going to be vastly different from its past iterations. While some "staples" may remain, others may find themselves with enough usage to stay in a higher tier or buffs that may send them to BL2. Accordingly, there are few constants between generations and a lot of Pokemon will have to be reexamined and reassessed, leading to this council-based approach and the necessity of many early bans on the notion of something being potentially broken or unhealthy.
Additional Purposes of this thread
This thread will chronologically list the history of RU bans and additions and removals to council. This will make it easier to quickly view how RU tiering history has changed over the years. In addition, this thread will also make note of rotating council members in the vote they participated in.
Arifeen (former TL)
Meru
-Tsunami- (former TL)
DTC
atomicllamas (former TL)
FlamingVictini
Kushalos
Nat
Meru
-Tsunami- (former TL)
DTC
atomicllamas (former TL)
FlamingVictini
Kushalos
Nat
RU Old Gens Hub
