Smogon Snake Draft II - Stage 1, Phase 2

Status
Not open for further replies.
#1
Welcome to the second edition of the Smogon Snake Draft. This year's tournament has 3 stages: a group stage, a round robin with the remaining teams, and a final. The tiers will be 4 OU / 1 Ubers / 1 UU / 1 RU / 1 NU / 1 DOU / 1 LC.

The group stage will consist of the 10 teams getting separated into two groups of 5. In each of those groups, every team will play every other team in two phases that last two weeks apiece. However, teams will not just be facing 2 other teams at the same time; depending on the slot, they may face different teams. UU A may face UU B and UU C, for example, whereas NU A faces NU D and NU E during the same phase. In this stage, the total amount of wins matters, and the 3 teams with the most wins per group will advance.

The 6 remaining teams will face off in "weeks" as we know them from SPL for the second stage. Here, rather than total wins, winning weeks against other teams to accumulate points will matter. Winning a week is worth 2 points, drawing it is worth 1 point, and losing it will yield no points. The top 2 teams at the end of this phase will advance to the final, in which they will both play each other again.

While this format may seem odd, it does provide a couple of advantages. First, the tournament will last 10 weeks, potentially slightly longer if tiebreaks are involved. This will mean there is ample time to cool down before SPL. Secondly, 4 teams will be eliminated relatively early on, and the TD team hopes this will cause the second phase to be more competitive as there will be less teams with little incentive to keep trying. We hope you enjoy the second edition of the Smogon Snake Draft.

The 6 remaining teams will face off in "weeks" as we know them from SPL for the second stage. Here, rather than total wins, winning weeks against other teams to accumulate points will matter. Winning a week is worth 2 points, drawing it is worth 1 point, and losing it will yield no points. At the end of this stage, the top seeded team will go straight to finals, while the top 2 and top 3 will face off to earn a spot in finals.

Standard Tournament Rules and Procedures:
On... Sportsmanship

Note the sportsmanship infraction may be used liberally, and any unsportsmanlike conduct on the forums, in #wcop / #pokemon / any of the semiofficial tier channels, or in opposing wcop team channels (I won't infract for you being a dick in your own wcop team channel unless the situation is so extreme I feel I absolutely have to make an exception (consider basically any masterclass interaction ever)), will be grounds for an infraction. We encourage you to play semi-aggressively, but don't be a masterclass.

~ Aldaron

On... Scheduling Matches

I'm sure plenty of you have come across coin flipping / who to activity drama while scheduling matches. I'm here to reduce the arbitrary element associated with some of these decisions. It is entirely your decision to adhere to these STRONG RECOMMENDATIONS, but note that if you choose not to, I'll most likely ignore any pleading from your end and default you to a coin flip, regardless of what you claim is your Discord or forum activity. By signing up for this tournament, you are agreeing to this condition, that adhering to what I outline will protect you from coinflips / activity and that not adhering to it will subject you to coinflips / activity regardless of your proposed justification.
YOU MUST ACTIVATE YOUR VM WALL IF YOU WISH TO PLAY IN THIS TOURNAMENT. THIS IS HOW ALL OFFICIAL SCHEDULING WILL BE HANDLED.

Once that round's thread is posted, you have up to 48 hours to contact your opponent ON HIS VM WALL and mention your timezone and exactly what dates, what time ranges you are available, and where you will battle. Note that the default accepted sim and server is the official server on Showdown. You must provide at least 3 different time ranges at least 48 hours from the timestamp of your message, with at least 2 that are 24-hours apart from each other. The minimum and maximum length for 1 time range is 30 minutes, and the minimum difference between the 3 required time ranges is 3 hours. If you give 3 time ranges that stick with this policy, you can give any additional time ranges at any time you please.

NOTE THAT THIS SCENARIO INVOLVES RESPONSE DYNAMICS; THERE IS SOMEONE WHO WILL CONTACT FIRST AND SOMEONE WHO RESPOND...THESE REQUIREMENTS ARE NOT FOR BOTH OF YOU TO ASSUME TO YOU CAN BE FIRST CONTACTS...WHOEVER CONTACTS FIRST IS THE FIRST, AND THE OTHER DEFAULTS TO THE RESPONDER. THIS SHOULD BE OBVIOUS BUT SOME OF YOU ARE DUMB.

Once your opponent has contacted you, you now have up until 72 hours after the round's thread has been posted (NOT after your opponent's message) to respond with times that are good for you. What this means is that if both of you spend the maximum time contacting and responding, you should have back and forth collaboration at a maximum of 72 hours after the round has been posted, with both parties given an additional 24 hours to prepare for the battle should it be scheduled as soon as required. If none of the opponent's proposed time ranges are good for you, you must respond with alternative time ranges.

The first opponent now has X hours to prepare for the battle (if the second opponent agreed to some time) or 24 hours to contact a TD if, for whatever reason, this second set of time ranges does not suit the first opponent. Note this should be an absolute last measure and that more often than not, the TDs will likely force one (or both) sides to sub out.

Once a time is agreed upon, please make a message on your opponent's vm wall between 10 minutes and 1 second before the agreed upon time and say you are ready to battle and then get to agreed upon location (regardless of whether or not your opponent sends you a response vm). Please protect yourself by making this message, as it makes decisions much easier. You will be required to be wait for your opponent for the duration of the time range.

If neither of you contact each other before 48 hours after the thread has been posted, you're both opening yourself up to a potential coin flip. If I look at the situation, I might just determine I'm going to sub both of you out, coin flip you, or whatever based on however I'm feeling at that moment. Don't leave yourself and your team vulnerable to this.

Just because at anytime one of the responders does not respond within the given range does not give you automatic activity win credentials. If they don't contact at all on your vm wall up until 48 hours before the end of the round (note, I'm not going to take Discord or sim messages as evidence due to how easily they can be doctored...so if you want to protect yourself, stick to the vm messages), then you obviously have activity win justification. Note to team captains, if one of your players does not contact all his opponents before 48 hours before the end of the round, I will FORCE a sub, no questions asked. You WILL contact your opponent in a timely manner. However, if they do contact you at all after the suggested response time and before 48 hours before the end of the round, you are required to respond before 24 hours before the end of the round with 2 1-hour time ranges at least 1 hour apart before the end of the round. The opponent, since he did not stick to the proposed response schedule, WILL BE REQUIRED TO PLAY AT ONE OF YOUR NEWLY SUGGESTED TIMES, so you have the advantage here. This obviously puts a bit of an emphasis on the last 48 hours of each round (as is standard operating procedure for most of our official team tournaments anyway), so I will try my best to keep the last 48 hours of the round as close to the majority of the weekend for as much of the world as I can.

If you follow all of these guidelines, you will a.) most likely get your match done with minimal issue or b.) protect yourself and your team from an undue coin flip or activity decision. Yes, I hate activity decisions in official tournaments. Yes, I will do my best to prevent activity decisions in the playoffs (the qualifying round is fair game however and I will have no problem issuing an activity call here), but don't push your luck.

Here is an example of how following this would work:

Round 1 thread is posted June 7, 2015 at 10:00PM. Its deadline is June 14, 2015 at 11:59PM. User A and User B are matched up. User A contacts User B on his vm wall on June 9, at 9:00 PM (47 hours after the thread was posted, so ok), and gives 4 time ranges: June 10, from 7:00-7:30 PM (22 hours after the timestamp of his message, which is only ok so long as at minimum 3 of the other proposed time ranges adhere to the requirements), June 11, from 9:00-9:30 PM (48 hours after the timestamp of his message, which is ok), June 12, from 6:00-6:30 PM (69 hours after timestamp of his message, so ok, but only 21 hours after the earliest time range that is 48 hours after the timestamp), and June 12, from 9:00-9:30 PM (72 hours after the timestamp, so ok, and 24 hours after a legal time range and 3 hours after another legal time range). The June 11 and both June 12 time ranges satisfy the requirements, so User A can propose his first June 10 time range as well. User B responds on June 10, at 8:00 PM (23 hours after User A contacted him, so ok), and picks June 11, at 9:00 PM to battle, which is ok because it is 24 hours after his own response.

You'll note I made most of my response ranges multiples of 24 hours, but also included 24 hours. This means I expect you to be able to check Smogon at least once a day. If that is not feasible, you put yourself at risk.

~ Aldaron

On "Self-KO Clause" and Ties:
Self-KO Clause is an antiquated concept that is not used in Smogon tournaments. The one exception to the rule is if the tournament is live (weekly Smogon Tour, Suspect Tours, etc.). For all standard tournaments here this rule does not exist. It Does Not Exist.

If both Pokemon faint simultaneously in DPP, ADV, GSC, or RBY, the game is ruled as a tie. Tied games do not count as played games in overall standings and will be expected to be replayed within the round's initial deadline. Similarly to this, tied games do not count towards the total number of games played in "best of X" series. In other words, if a tournament includes "Bo3" RBY, what is really being played is "first to two wins" RBY.

However, ties simply don't exist in later generations. The developers removed ties from BW and have not added them back since. There's a lot of inconsistency with the mechanics of their tiebreaking system but Smogon follows them to stay true to the cartridge. The main ones are listed below:

Note: The following list is for SM, XY, and BW, and not for DPP, ADV, GSC, or RBY

Self-KO Moves (Destiny Bond, Explosion, Final Gambit, etc.):
Attacking Pokemon Loses

Offensive Recoil (Life Orb; Double-Edge, Flare Blitz, etc.):
Attacking Pokemon Wins

Defensive Recoil (Rocky Helmet; Iron Barbs, Rough Skin):
Attacking Pokemon Wins (SM)
Attacking Pokemon Loses (XY and BW)

Passive Damage (Status, Weather, etc.):
Faster Pokemon Loses

Disconnections and Timer
For information on our disconnection and timer rules, refer to this thread.

Tiebreaks:
If teams are in a position to move on and are tied for wins in Stage 1, points and bd in Stage 2 or just tie in the final match in Stage 3, a tiebreak Best-of-3 series will be played to determine which team advances. The first match will be standard SM OU, with each of the teams in the tiebreak picking another tier to be played. This tier can be another SM OU, and multiple SM OU matches can be played. However, as every team should only have to aim to draft 1 player for every other tier, no other tier can be repeated.

For Stage 1, if a tiebreak occurs, the team that had more wins in the head-to-head matchups will pick second. If the teams were tied in head-to-head, strength of schedule is used to determine the higher seed instead.

For Stage 2, largely the same metrics are used as for stage 1. The first denominator to determine the higher seed will be Stage 2's head-to-head matchup. If this resulted in a tie, the number of total wins from Stage 1 will be used. Should this also be the same, strength of schedule in Stage 2 is used.

For Stage 3, the team with the higher ranking in Stage 2 will be the higher seed. If this was identical, the number of total wins in Stage 1 is used. If this also results in a tie, the Stage 2 head-to-head matchup will break the tie. In case this fails, strength of schedule will be the fallback.

If, during any stage, all parameters listed here are tied, we will publicly use the !pick command on the Smogtours server to determine the higher seed.

Substitutions:
During Stage 1, subsitutions are allowed during each phase, and a player getting subbed in has to play all the remaining opponents of the player he is replacing. A player that has been subbed out during a phase may not be subbed into any other slot. Multiple substitutions may occur in the same slot. Of course, Phase 2 may use a different lineup than Phase 1, and substitutes will be "reset", meaning everyone on the bench can be subbed in once again. For Stage 2 and 3, substitutions work like they do in SPL.

Substitutions will be not be allowed in tiebreak series unless the hosts mandate it. However, since we prioritise games being played, we will consider extension requests so long as they're reasonable. We will also be reluctant to give activity wins to those who are clearly fishing for them.


Simulator:
Pokémon Showdown is the main simulator for this tournament, and Smogtours is the main server. If both players agree and there is a valid reason that a match cannot be played on Smogtours, it may be played on the main server as well.
 
#2
Matchups:

Sun Division:
USUM OU #1:
SoulWind [NAGA] vs. Tamahome [COBR]
SoulWind [NAGA] vs. UltraBallz [SIDE]
Tamahome [COBR] vs. Hayburner [BUSH]
Hayburner [BUSH] vs. 1 True Lycan [GLID]
1 True Lycan [GLID] vs. UltraBallz [SIDE]

USUM OU #2:
Kory2600 [NAGA] vs. CaronSmith [COBR]
Kory2600 [NAGA] vs. Eo Ut Mortus [SIDE]
CaronSmith [COBR] vs. rozes [BUSH]
rozes [BUSH] vs. FMG [GLID]
FMG [GLID] vs. Eo Ut Mortus [SIDE]

USUM OU #3:
Sacri' [NAGA] vs. Cdumas [COBR]
Sacri' [NAGA] vs. yjh971203 [SIDE]
Cdumas [COBR] vs. BKC [BUSH]
BKC [BUSH] vs. soulgazer [GLID]
yoppie [GLID] vs. yjh971203 [SIDE]

USUM OU #4:
Updated Kanto [NAGA] vs. Kickasser [COBR]
Updated Kanto [NAGA] vs. aim [SIDE]
Kickasser [COBR] vs. Gondra [BUSH]
Gondra [BUSH] vs. Empo [GLID]
Empo [GLID] vs. aim [SIDE]

USUM DOU:
Ezrael [NAGA] vs. SMB [COBR]
Ezrael [NAGA] vs. Lunar. [SIDE]
SMB [COBR] vs. EmbCPT [BUSH]
EmbCPT [BUSH] vs. emforbes [GLID]
emforbes [GLID] vs. Lunar. [SIDE]

USUM UU:
HT [NAGA] vs. pasy_g [BUSH]
HT [NAGA] vs. TDK [GLID]
Lycans [COBR] vs. TDK [GLID]
Lycans [COBR] vs. Shiba [SIDE]
pasy_g [BUSH] vs. Shiba [SIDE]

USUM RU:
MrAldo [NAGA] vs. col49 [BUSH]
MrAldo [NAGA] vs. Welli0u [GLID]
Scythe. [COBR] vs. Welli0u [GLID]
Scythe. [COBR] vs. Nat [SIDE]
col49 [BUSH] vs. Nat [SIDE]

USUM NU:
Kushalos [NAGA] vs. Nintendi [BUSH]
Kushalos [NAGA] vs. lax [GLID]
Stone_Cold [COBR] vs. lax [GLID]
HANTSUKI [COBR] vs. FLCL [SIDE]
Nintendi [BUSH] vs. FLCL [SIDE]

USUM LC:
Heysup [NAGA] vs. Corporal Levi [BUSH]
Heysup [NAGA] vs. trash [GLID]
jake [COBR] vs. trash [GLID]
jake [COBR] vs. Sken [SIDE]
Corporal Levi [BUSH] vs. Sken [SIDE]

USUM Ubers:
GaryTheGengar [NAGA] vs. The Trap God [BUSH]
GaryTheGengar [NAGA] vs. HunterStorm [GLID]
KyogreF4N [COBR] vs. HunterStorm [GLID]
KyogreF4N [COBR] vs. Zesty43 [SIDE]
The Trap God [BUSH] vs. Zesty43 [SIDE]


Moon Division:
USUM OU #1:
LittleBigPlanet2 [MAMB] vs. CKW [ASTR]
LittleBigPlanet2 [MAMB] vs. Eternam [TAIP]
blarghlfarghl [ASTR] vs. suapah [SERP]
suapah [SERP] vs. Hiye [LEVI]
Hiye [LEVI] vs. Eternam [TAIP]

USUM OU #2:
Santu [MAMB] vs. Mncmt [ASTR]
FlamingVictini [MAMB] vs. Spectear [TAIP]
Ciele [ASTR] vs. Ojama [SERP]
Ojama [SERP] vs. Lopunny Kicks [LEVI]
Lopunny Kicks [LEVI] vs. xray [TAIP]

USUM OU #3:
Bro Kappa [MAMB] vs. Eternal Spirit [ASTR]
Bro Kappa [MAMB] vs. bro fist [TAIP]
Eternal Spirit [ASTR] vs. RedEmption [SERP]
RedEmption [SERP] vs. KingKdot [LEVI]
KingKdot [LEVI] vs. bro fist [TAIP]

USUM OU #4:
Malekith [MAMB] vs. Tricking [ASTR]
Charmflash [MAMB] vs. Lavos [TAIP]
Tricking [ASTR] vs. Posho [SERP]
ramboss [SERP] vs. Finchinator [LEVI]
Finchinator [LEVI] vs. Lavos [TAIP]

USUM DOU:
miltankmilk [MAMB] vs. stax [ASTR]
miltankmilk [MAMB] vs. Demantoid [TAIP]
stax [ASTR] vs. Biosci [SERP]
Biosci [SERP] vs. MajorBowman [LEVI]
MajorBowman [LEVI] vs. Demantoid [TAIP]

USUM UU:
McMeghan [MAMB] vs. Pak [SERP]
McMeghan [MAMB] vs. robjr [LEVI]
Manipulative [ASTR] vs. robjr [LEVI]
Manipulative [ASTR] vs. Sage [TAIP]
Pak [SERP] vs. Sage [TAIP]

USUM RU:
Aeroblacktyl [MAMB] vs. Ajna [SERP]
Alpha Rabbit [MAMB] vs. KW [LEVI]
lighthouses [ASTR] vs. KW [LEVI]
lighthouses [ASTR] vs. august [TAIP]
Ajna [SERP] vs. august [TAIP]

USUM NU:
Hootie [MAMB] vs. Tangelo [SERP]
Hootie [MAMB] vs. Eternally [LEVI]
Realistic Waters [ASTR] vs. Eternally [LEVI]
Realistic Waters [ASTR] vs. Rodriblutar [TAIP]
Tangelo [SERP] vs. Rodriblutar [TAIP]

USUM LC:
dcae [MAMB] vs. teal6 [SERP]
dcae [MAMB] vs. OP [LEVI]
Dundies [ASTR] vs. OP [LEVI]
Dundies [ASTR] vs. Kingler12345 [TAIP]
teal6 [SERP] vs. Kingler12345 [TAIP]

USUM Ubers:
Exiline [MAMB] vs. Leru [SERP]
Exiline [MAMB] vs. Garay oak [LEVI]
Fireburn [ASTR] vs. Garay oak [LEVI]
Fireburn [ASTR] vs. Cynara [TAIP]
Leru [SERP] vs. Cynara [TAIP]


Deadline will be September 16th, 10:00 PM EST.
 
Last edited by a moderator:
#17
尸尺乇尸卂尺乇 下口尺 丅尺口凵乃乚乇! 卂刀 从卂长乇 工丅 刀口凵乃乚乇! 丅口 尸尺口丅乇匚丅 丅卄乇 山口尺乚刀 下尺口从 刀乇リ卂丂丅卂丅工口! 丅口 凵工丅乇 卂乚乚 尸乇口尸乚乇丂 山工丅卄工 口凵尺 卂丅工口! 丅口 刀乇口凵匚乇 丅卄乇 乇リ工乚丂 口下 丅尺凵丅卄 卂刀 乚口リ乇! 丅口 乇乂丅乇刀 口凵尺 尺乇卂匚卄 丅口 丅卄乇 丂丅卂尺丂 卂乃口リ乇! 丁乇丂丂工乇! 丁卂从乇丂! 丅乇卂从 尺口匚长乇丅 乃乚卂丂丅丂 口下下 卂丅 丅卄乇 丂尸乇乇刀 口下 乚工厶卄丅! 丂凵尺尺乇刀乇尺 口山, 口尺 尸尺乇尸卂尺乇 丅口 下工厶卄丅! 从乇口山丅卄! 丅卄卂丅'丂 尺工厶卄丅!

bushmasters omfl

 
Status
Not open for further replies.

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

Top