Welcome to Week 4 everyone! As always this week will be closing on Monday, August 10. Make sure to get in contact ASAP and get those matches done!
Jumbo Jumbaos (4)
vs Perilous Pinecos (2)
SS Bo3: Jrdn vs Lasen
SS1: Ho3nConfirm3d vs Rage.Spam.Quit
SS2: Rabia vs maroon
SS3: 85percent vs againa
SM1: Finchinator vs Snorlax in the way
SM2: quziel vs Marjane
Surging Snaelstroms (3)
vs Galactic Astrolotls(3)
SS Bo3: xavgb vs -Voltage-
SS1: pinkdragontamer vs lyd
SS2:Clefable aesf vs snake_rattler
SS3: Andyboy vs atha
SM1: Jho vs GardeLame
SM2: Jordy vs Wulfanator72
Choice Band Revenankhs (3)
vs Punny Privatykes (2) 
SS Bo3: DetroitLolcat vsTerracotta K3ppr
SS1: Scizivire vs Orig Stall Guy
SS2: Tadasuke vs Nalei
SS3: Heaven Jay vs MrDollSteak
SM1: Maple vs Aetherl
SM2: G-Luke vs Airwind
Jumbo Jumbaos (4)
vs Perilous Pinecos (2)SS Bo3: Jrdn vs Lasen
SS1: Ho3nConfirm3d vs Rage.Spam.Quit
SS2: Rabia vs maroon
SS3: 85percent vs againa
SM1: Finchinator vs Snorlax in the way
SM2: quziel vs Marjane
Surging Snaelstroms (3)
vs Galactic Astrolotls(3)
SS Bo3: xavgb vs -Voltage-
SS1: pinkdragontamer vs lyd
SS2:
SS3: Andyboy vs atha
SM1: Jho vs GardeLame
SM2: Jordy vs Wulfanator72
Choice Band Revenankhs (3)
vs Punny Privatykes (2) SS Bo3: DetroitLolcat vs
SS1: Scizivire vs Orig Stall Guy
SS2: Tadasuke vs Nalei
SS3: Heaven Jay vs MrDollSteak
SM1: Maple vs Aetherl
SM2: G-Luke vs Airwind
- Unless you are playing in SS Bo3, all matches will default to Bo1.
-All matches played must have a replay saved. It is the winner of the match who has responsibility to post the replay for match, though the loser is definitely allowed to confirm the loss with a reply as well, and teammates are allowed to post replays as well; the main point is that replays have to be presented. It is unfair to NOT have your match's replay shared because if every replay is available then it presents an equal access to the proof of the players' skills in the context of this tournament. Not sharing replays makes it harder for a particular player to be studied, which is unfair to the players that do put themselves in the public eye via this tournament and their replays.
-Matches must be played in their corresponding format. Do not play in Custom Battles.
-Try to contact your opponent immediately and VM them/post a message on their Smogon wall. Keep scheduling public so that your scheduling attempts can be verified. If you are having trouble contacting your opponent for match scheduling, contact the opposing team to help notify your opponent or get a substitution for them if necessary. If you opponent agrees on a scheduled time but does not show up for the match, then record proof of this via a screenshot, video, etc and post it in this thread or PM it to LucarioOfLegends. If your opponent misses a scheduled match on a Saturday or Sunday, you may use your screenshot as proof for an activity victory. If you opponent misses a scheduled match before a Saturday, it is expected that some sort of serious rescheduling effort is made by both parties unless you specifically stated earlier that you would not be available Saturday/Sunday and your opponent acknowledged this. If there is a serious time conflict between players, then at the earliest available opportunity a substitution should be made.Captains and Co-Captains are the only ones allowed to make substitutions, and they can do so by replying to this thread by stating which of their two subs are subbing in for which starting player. More often than not if an opponent misses a scheduled time during the beginning of a week, it is expected that serious rescheduling efforts will take place and no immediate activity win will be given. If you scheduled a match and then realize you can't make it, it is 100% in your best interest to let your opponent know ASAP so that rescheduling or subbing can be done.
If a team is 1 vs 1 (or 0 vs 0) and all remaining matches have questionable activity calls, then the CAPPL Johning Clause will activate and both teams will end up losing the week. It should be every team's top interest to avoid a draw situation by having at the bare minimum 3 matches played each week, though obviously having all 6 matches played is preferable. This clause exists because it's flat out ridiculous if a team can't play more than half of their matches every week. [This rule is making it's return from CAPTT I. It's never had to be activated before and let's keep it that way. Note that this clause do NOT impact a matchup where it is clear that one team deserves multiple activity wins. This clause is reserved for when there's no appropriate contact between multiple sets of opponents between two teams. Again, the clause has never had to be activated in the past and this is more of a harsh deterrent against lack of scheduling.]
-Ghosting is not allowed, nor is any form of psuedo ghosting. Giving advice to a teammate or friend while they are playing a CAPPL match is not allowed. Planning any sort of schedule to ghost is not allowed. Any ghosting or planned ghosting that is found out will result in the offending team automatically losing the week. If a team is found to have ghosted in at least 2 weeks, they will be disqualified from the tournament and the offending captain and/or players might face bans from future CAP meta tournaments. "Public Ghosting" is not allowed either and any offenders will meet immediate and harsh punishment.
-Try to have good sportsmanship and don't be a dick. Poor sportsmanship may result in being kicked from the tournament.
-In the event of a disconnect/timeout, the offending player should show proof that the disconnect was genuine. Acceptable proof would include a photographic picture of your computer's disconnect message or blue screen or whatnot with enough external variation to assume you just didn't google the image or whatever. If the proof of the disconnect is determined to be valid and both players have submitted their teams in a spot the hosts have access to prior to their match, then the match should try to be recreated as close as humanly possible to the way it was at the point of the disconnect (this is the most preferable method-- using server leaders/admins might help in this if they are available and willing). Having neutral parties start with the original teams and giving the original players player status at the start of the match should be done if the same teams are used, since this prevents team changes from being made. In such a case, LucarioOfLegends should retrieve the teams from the team conversation if available, since a good team has them posted before each match for review anyway. If the player that disconnects does not have a valid copy of their team submitted, then that player does not have the ability to recreate the match and they will lose the matchup if their opponent wishes. In extra-ordinary situations that do not follow the above "best practices" then LucarioOfLegends will decide how to best move forward and may consult other Smogon tournament leaders as applicable.
-All matches played must have a replay saved. It is the winner of the match who has responsibility to post the replay for match, though the loser is definitely allowed to confirm the loss with a reply as well, and teammates are allowed to post replays as well; the main point is that replays have to be presented. It is unfair to NOT have your match's replay shared because if every replay is available then it presents an equal access to the proof of the players' skills in the context of this tournament. Not sharing replays makes it harder for a particular player to be studied, which is unfair to the players that do put themselves in the public eye via this tournament and their replays.
-Matches must be played in their corresponding format. Do not play in Custom Battles.
-Try to contact your opponent immediately and VM them/post a message on their Smogon wall. Keep scheduling public so that your scheduling attempts can be verified. If you are having trouble contacting your opponent for match scheduling, contact the opposing team to help notify your opponent or get a substitution for them if necessary. If you opponent agrees on a scheduled time but does not show up for the match, then record proof of this via a screenshot, video, etc and post it in this thread or PM it to LucarioOfLegends. If your opponent misses a scheduled match on a Saturday or Sunday, you may use your screenshot as proof for an activity victory. If you opponent misses a scheduled match before a Saturday, it is expected that some sort of serious rescheduling effort is made by both parties unless you specifically stated earlier that you would not be available Saturday/Sunday and your opponent acknowledged this. If there is a serious time conflict between players, then at the earliest available opportunity a substitution should be made.
If a team is 1 vs 1 (or 0 vs 0) and all remaining matches have questionable activity calls, then the CAPPL Johning Clause will activate and both teams will end up losing the week. It should be every team's top interest to avoid a draw situation by having at the bare minimum 3 matches played each week, though obviously having all 6 matches played is preferable. This clause exists because it's flat out ridiculous if a team can't play more than half of their matches every week. [This rule is making it's return from CAPTT I. It's never had to be activated before and let's keep it that way. Note that this clause do NOT impact a matchup where it is clear that one team deserves multiple activity wins. This clause is reserved for when there's no appropriate contact between multiple sets of opponents between two teams. Again, the clause has never had to be activated in the past and this is more of a harsh deterrent against lack of scheduling.]
-Ghosting is not allowed, nor is any form of psuedo ghosting. Giving advice to a teammate or friend while they are playing a CAPPL match is not allowed. Planning any sort of schedule to ghost is not allowed. Any ghosting or planned ghosting that is found out will result in the offending team automatically losing the week. If a team is found to have ghosted in at least 2 weeks, they will be disqualified from the tournament and the offending captain and/or players might face bans from future CAP meta tournaments. "Public Ghosting" is not allowed either and any offenders will meet immediate and harsh punishment.
-Try to have good sportsmanship and don't be a dick. Poor sportsmanship may result in being kicked from the tournament.
-In the event of a disconnect/timeout, the offending player should show proof that the disconnect was genuine. Acceptable proof would include a photographic picture of your computer's disconnect message or blue screen or whatnot with enough external variation to assume you just didn't google the image or whatever. If the proof of the disconnect is determined to be valid and both players have submitted their teams in a spot the hosts have access to prior to their match, then the match should try to be recreated as close as humanly possible to the way it was at the point of the disconnect (this is the most preferable method-- using server leaders/admins might help in this if they are available and willing). Having neutral parties start with the original teams and giving the original players player status at the start of the match should be done if the same teams are used, since this prevents team changes from being made. In such a case, LucarioOfLegends should retrieve the teams from the team conversation if available, since a good team has them posted before each match for review anyway. If the player that disconnects does not have a valid copy of their team submitted, then that player does not have the ability to recreate the match and they will lose the matchup if their opponent wishes. In extra-ordinary situations that do not follow the above "best practices" then LucarioOfLegends will decide how to best move forward and may consult other Smogon tournament leaders as applicable.
Week 1:
Perilous Pinecos vs. Choice Band Revenankhs
Punny Privatykes vs. Surging Snaelstroms
Galactic Astrolotls vs Jumbo Jumbaos
Week 2:
Perilous Pinecos vs Punny Privatykes
Galactic Astrolotls vs Choice Band Revenanks
Jumbo Jumbaos vs Surging Snaelstroms
Week 3:
Perilous Pinecos vs Galactic Astrolotls
Jumbo Jumbaos vs Punny Privatykes
Surging Snaelstroms vs Choice Band Revenankhs
Week 4:
Jumbo Jumbaos vs Perilous Pinecos
Surging Snaelstroms vs Galactic Astrolotls
Choice Band Revenankhs vs Punny Privatykes
Week 5:
Surging Snaelstroms vs Perilous Pinecos
Choice Band Revenankhs vs Jumbo Jumbaos
Punny Privatykes vs Galactic Astrolotls
Standings: W/T/L (Individual Battle W-L)
Jumbo Jumbaos: 1/1/1 (9-9)
Choice Band Revenankhs: 1/1/1 (10-8)
Galactic Astrolotls: 1/2/0 (10-8)
Perlious Pinecos: 0/1/2 (6-12)
Surging Snaelstroms: 3/0/0 (14-4)
Punny Privatykes: 0/1/2 (5-13)
Perilous Pinecos vs. Choice Band Revenankhs
Punny Privatykes vs. Surging Snaelstroms
Galactic Astrolotls vs Jumbo Jumbaos
Week 2:
Perilous Pinecos vs Punny Privatykes
Galactic Astrolotls vs Choice Band Revenanks
Jumbo Jumbaos vs Surging Snaelstroms
Week 3:
Perilous Pinecos vs Galactic Astrolotls
Jumbo Jumbaos vs Punny Privatykes
Surging Snaelstroms vs Choice Band Revenankhs
Week 4:
Jumbo Jumbaos vs Perilous Pinecos
Surging Snaelstroms vs Galactic Astrolotls
Choice Band Revenankhs vs Punny Privatykes
Week 5:
Surging Snaelstroms vs Perilous Pinecos
Choice Band Revenankhs vs Jumbo Jumbaos
Punny Privatykes vs Galactic Astrolotls
Standings: W/T/L (Individual Battle W-L)
Jumbo Jumbaos: 1/1/1 (9-9)
Choice Band Revenankhs: 1/1/1 (10-8)
Galactic Astrolotls: 1/2/0 (10-8)
Perlious Pinecos: 0/1/2 (6-12)
Surging Snaelstroms: 3/0/0 (14-4)
Punny Privatykes: 0/1/2 (5-13)
Last edited:
