661 lines
36 KiB
Markdown
661 lines
36 KiB
Markdown
# OFFICIAL REGULATIONS 2024/2025 - VERSION 1.1
|
|
|
|
## Second season
|
|
|
|
## Table of Contents
|
|
|
|
- [Second season](#second-season)
|
|
- [Table of Contents](#table-of-contents)
|
|
- [1. Introduction](#1-introduction) - [A.](#a) - [B.](#b) - [C.](#c)
|
|
- [2. Registration, entry, participation, and permanence](#2-registration-entry-participation-and-permanence) - [A.](#a-1) - [B.](#b-1) - [C.](#c-1) - [D.](#d) - [E.](#e) - [F.](#f) - [G.](#g) - [H.](#h) - [I.](#i) - [J.](#j) - [K.](#k)
|
|
- [3. Tournament format](#3-tournament-format) - [A. GROUP STAGE](#a-group-stage) - [B. KNOCKOUT STAGE](#b-knockout-stage)
|
|
- [4. Channel map](#4-channel-map) - [A.](#a-2) - [B.](#b-2) - [C.](#c-2) - [D.](#d-1)
|
|
- [6. Responsibilities by Role](#6-responsibilities-by-role)
|
|
- [A. Fighter Responsibilities](#a-fighter-responsibilities)
|
|
- [B. Captain Responsibilities](#b-captain-responsibilities)
|
|
- [C. Staff Responsibilities](#c-staff-responsibilities)
|
|
- [D. Manager Responsibilities](#d-manager-responsibilities)
|
|
- [7. Creation of Pokémon Battle Teams](#7-creation-of-pokémon-battle-teams)
|
|
- [8. Matches, Point System, and Tiebreaker Criteria](#8-matches-point-system-and-tiebreaker-criteria)
|
|
- [A. Matches](#a-matches)
|
|
- [B. Games](#b-games)
|
|
- [C. Point System](#c-point-system)
|
|
- [9. Submission of Rosters](#9-submission-of-rosters)
|
|
- [10. Submission of templates](#10-submission-of-templates)
|
|
- [A. Submission Process](#a-submission-process)
|
|
- [B. Template Requirements](#b-template-requirements)
|
|
- [C. Delay in Submission](#c-delay-in-submission)
|
|
- [10. Schedules, Start of the Round, and Opening of Channels](#10-schedules-start-of-the-round-and-opening-of-channels)
|
|
- [A. Round Timing](#a-round-timing)
|
|
- [B. Match Channels](#b-match-channels)
|
|
- [C. Schedule Command](#c-schedule-command)
|
|
- [D. Star Match](#d-star-match)
|
|
- [11. Contact and Coordination Procedure](#11-contact-and-coordination-procedure)
|
|
- [A. Contact Window](#a-contact-window)
|
|
- [B. Confirmation](#b-confirmation)
|
|
- [C. Responsibility](#c-responsibility)
|
|
- [D. Availability](#d-availability)
|
|
- [E. Time Format](#e-time-format)
|
|
- [F. Message Editing](#f-message-editing)
|
|
- [G. Fixed Schedule](#g-fixed-schedule)
|
|
- [H. Schedule Agreement](#h-schedule-agreement)
|
|
- [I. Schedule Conflict](#i-schedule-conflict)
|
|
- [J. Organization Decision](#j-organization-decision)
|
|
- [K. Match Advancement](#k-match-advancement)
|
|
- [L. No Response](#l-no-response)
|
|
- [M. Uncoordinated Matches](#m-uncoordinated-matches)
|
|
- [N. Effective Contact](#n-effective-contact)
|
|
- [O. Last-Minute Coordination](#o-last-minute-coordination)
|
|
- [P. Ineffective Coordination](#p-ineffective-coordination)
|
|
- [12. Combat Team Exchange Procedure](#12-combat-team-exchange-procedure)
|
|
- [A. Team Templates](#a-team-templates)
|
|
- [B. Rule Violation](#b-rule-violation)
|
|
- [C. Channel Usage](#c-channel-usage)
|
|
- [D. Team History](#d-team-history)
|
|
- [13. Substitute Usage Procedure](#13-substitute-usage-procedure)
|
|
- [A. Substitute Notification](#a-substitute-notification)
|
|
- [B. Irreversible Request](#b-irreversible-request)
|
|
- [C. Delay in Substitution](#c-delay-in-substitution)
|
|
- [D. Single Substitution](#d-single-substitution)
|
|
- [E. Repeated Substitutions](#e-repeated-substitutions)
|
|
- [14. Combat Procedure](#14-combat-procedure)
|
|
- [A. Match Duration](#a-match-duration)
|
|
- [B. Illegal Combat Team](#b-illegal-combat-team)
|
|
- [C. Notification of Anomaly](#c-notification-of-anomaly)
|
|
- [D. Abandoning Match](#d-abandoning-match)
|
|
- [E. Pokémon Modification](#e-pokémon-modification)
|
|
- [F. Pokémon Selection Time](#f-pokémon-selection-time)
|
|
- [G. Connection Issues](#g-connection-issues)
|
|
- [H. Match Registration](#h-match-registration)
|
|
- [I. Dispute Formation](#i-dispute-formation)
|
|
- [J. Screenshot Request](#j-screenshot-request)
|
|
- [15. Dispute Procedure and Evidence Submission](#15-dispute-procedure-and-evidence-submission)
|
|
- [A. Dispute Request](#a-dispute-request)
|
|
- [B. Video Evidence](#b-video-evidence)
|
|
- [C. Evidence Submission](#c-evidence-submission)
|
|
- [D. Result Reporting](#d-result-reporting)
|
|
- [E. Evidence Requirement](#e-evidence-requirement)
|
|
- [F. Staff Requests](#f-staff-requests)
|
|
- [G. Rematch Request](#g-rematch-request)
|
|
- [16. Result Reporting Procedure](#16-result-reporting-procedure)
|
|
- [A. Reporting Results](#a-reporting-results)
|
|
- [B. Reporting Example](#b-reporting-example)
|
|
- [C. Captain Reporting](#c-captain-reporting)
|
|
- [D. Agreement on Result](#d-agreement-on-result)
|
|
- [E. Result Confirmation](#e-result-confirmation)
|
|
- [F. Dispute Resolution](#f-dispute-resolution)
|
|
- [17. Internal and External Technical Problems](#17-internal-and-external-technical-problems)
|
|
- [A. Internal Technical Problems](#a-internal-technical-problems)
|
|
- [B. External Technical Problems](#b-external-technical-problems)
|
|
- [C. Staff Tools](#c-staff-tools)
|
|
- [18. Anomaly Reports and Staff Response Time](#18-anomaly-reports-and-staff-response-time)
|
|
- [A. Anomaly Notification](#a-anomaly-notification)
|
|
- [B. Staff Response Time](#b-staff-response-time)
|
|
- [C. Immediate Response](#c-immediate-response)
|
|
- [D. Evidence Verification](#d-evidence-verification)
|
|
- [E. Staff Anomalies](#e-staff-anomalies)
|
|
- [19. Strike, Suspension, and Warning System](#19-strike-suspension-and-warning-system)
|
|
- [A. Warnings](#a-warnings)
|
|
- [B. Warning Accumulation](#b-warning-accumulation)
|
|
- [C. Suspension Sanction](#c-suspension-sanction)
|
|
- [D. Strikes](#d-strikes)
|
|
- [E. Suspensions](#e-suspensions)
|
|
- [F. Bans](#f-bans)
|
|
- [20. Guide to Violations and Punishments](#20-guide-to-violations-and-punishments)
|
|
- [A. Conduct Violations](#a-conduct-violations)
|
|
- [B. Slow Play Violations](#b-slow-play-violations)
|
|
- [C. Absence Violations](#c-absence-violations)
|
|
- [D. Violations for Incorrect Information](#d-violations-for-incorrect-information)
|
|
- [E. Penalties for Unsportsmanlike Conduct](#e-penalties-for-unsportsmanlike-conduct)
|
|
- [21. Recognition System](#21-recognition-system)
|
|
- [A. Punctuality and Responsibility](#a-punctuality-and-responsibility)
|
|
- [B. Fair Play](#b-fair-play)
|
|
- [Prizes](#prizes)
|
|
|
|
## 1. Introduction
|
|
|
|
#### A.
|
|
|
|
BOX STADIUM is a community created in 2020 with the purpose of holding international tournaments, creating an open and fair competitive scene for professional, amateur, and emerging teams, with the aim of having fun and learning, but above all shining and gaining notoriety in private and public spheres, regionally, nationally, and internationally, regardless of their geographical location. The laws and rules included in this document, and any other document created by BOX STADIUM, are designed to promote fair and professional play.
|
|
|
|
#### B.
|
|
|
|
Competitors are responsible for knowing and studying any set of rules required for this tournament. Those who violate these regulations are subject to results and sanctions according to the level of infraction, up to permanent prohibition from participating in BOX STADIUM tournaments. Any request for validation of the regulations must be made through the ongoing confrontation channel. Likewise, each coordination must be individual for each team member and not an external person to the encounter in the confrontation channel if necessary the captain can support in the coordination of the meeting schedules, if the captain designates a schedule for his player this will be the official schedule of the encounter.
|
|
|
|
#### C.
|
|
|
|
BOX STADIUM reserves the right to modify, interpret, clarify or issue changes to these rules without prior notice and at any time. Of course, the organization promises to notify each modification in a timely manner through its official channels and from the moment it is published or announced, it will come into effect, taking effect immediately and not retroactively. At no time can the application of the regulations be made retroactively to the date of its last update. It is the responsibility of the competitors to ensure they take into account these updates and inform themselves of the announced changes.
|
|
|
|
## 2. Registration, entry, participation, and permanence
|
|
|
|
#### A.
|
|
|
|
Invited teams will be selected as follows:
|
|
|
|
#### B.
|
|
|
|
From the previous season, the champion and runner-up will get a direct pass to the league.
|
|
|
|
#### C.
|
|
|
|
From the trios tournament, the top three places will get direct passes.
|
|
|
|
#### D.
|
|
|
|
From the qualifier tournament, the top four places will get direct passes.
|
|
|
|
#### E.
|
|
|
|
The rest of the participating teams will be selected and invited according to their current performance in the different tournaments and leagues that the organization considers.
|
|
|
|
#### F.
|
|
|
|
All captains who have confirmed their participation through the provided communication channel will be sent an access link to the server where the tournament will take place, as well as detailed information about the tournament. Teams with affiliates in the tournament cannot be in the same group and will be assigned the corresponding group by draw.
|
|
|
|
#### G.
|
|
|
|
Teams must register at least ten competitors. With a maximum of 12 members per team, they can also add a manager as the team leader. Competitors cannot compete in two teams at the same time, if their participation is found in more than one team they will be immediately removed from the competition and the team will not be able to assign a backup player, TEAMS WILL HAVE UNTIL NOVEMBER 3, 2024, AT 11:59 PM GMT-6 (Central Mexico time) TO REGISTER ALL THEIR PLAYERS ON THE SERVER.
|
|
|
|
#### H.
|
|
|
|
By participating, it is accepted that the members of each team have read and consciously accepted these regulations. Ignorance of the regulations does not exempt them from compliance and application before, during, and after the competition, and could also be grounds for expulsion from the tournament, depending on the case and context. The responsibility of being aware of the updates to the regulations is exclusively the competitor's.
|
|
|
|
#### I.
|
|
|
|
Competitors may not change their Nick during the tournament, and they must have the same Nick on our Discord server to facilitate account identification. The competitor who incurs this fault will be expelled. Likewise, competitors who are found with more than one account in the tournament will be expelled.
|
|
|
|
#### J.
|
|
|
|
The use of third-party applications that falsify their GPS location or exploit game errors to gain unfair advantages is strictly prohibited.
|
|
|
|
#### K.
|
|
|
|
To withdraw from the tournament:
|
|
|
|
1. **Individual:** The player must notify their manager or captain.
|
|
2. **Team:** The manager or captain must notify the staff that one of their players or the team will no longer be part of the competition.
|
|
3. If a team withdraws, all previous results before their removal will remain the same and future matches will be 14-0.
|
|
|
|
## 3. Tournament format
|
|
|
|
Remote format, with rounds of 5 days. The tournament consists of ten (10) dates divided into the following blocks:
|
|
|
|
#### A. GROUP STAGE
|
|
|
|
Consisting of 7 dates, the registered teams will compete in their battle fronts to reach the top of their front and qualify for the knockout stage, with the top two places from each group qualifying.
|
|
|
|
#### B. KNOCKOUT STAGE
|
|
|
|
Consisting of 3 dates, the top 2 teams from each front will qualify to face others in a knockout format. They must win to advance to the next round.
|
|
|
|
## 4. Channel map
|
|
|
|
On our Discord server, you can find the map-of-the-server channel where you will find detailed information on what each channel is for.
|
|
|
|
#### A.
|
|
|
|
The channels in the BOX STADIUM category are for public use by the community. There you will find announcements, general chat channels, promotional channels, friends of the house, general community tournaments, and soon we will enable the Hall of Fame channel.
|
|
|
|
#### B.
|
|
|
|
The channels in the BOX STADIUM LEAGUE category are for use by teams and competitors. There you will find announcements, tournament regulations, important links, and graphic elements, the captains' chat, withdrawal requests, and general chat channels.
|
|
|
|
#### C.
|
|
|
|
The channels in the Front category are for use by teams and competitors of each front. There you will find your team's personal channel where you must send disputes and resolve doubts from the staff to the competitors and a general chat for each front.
|
|
|
|
#### D.
|
|
|
|
In each front channel, there will be a #team-history channel, where you can see the teams used in the previous round by each team.
|
|
|
|
## 6. Responsibilities by Role
|
|
|
|
### A. Fighter Responsibilities
|
|
|
|
In addition to the rest of the rules in these regulations, the responsibilities of the FIGHTER include, but are not limited to:
|
|
|
|
- Being familiar with and following the latest version of the rules, as well as any set of rules required for a specific phase or edition.
|
|
- Meeting the deadlines established by the regulations, in the messages sent by the staff for coordinating, interacting, fighting, and reporting their matches in the requested manner.
|
|
- Proceeding with respectful and cordial contact, maintaining an active chat in their confrontation channel with their opponent, coordinating, and confirming a single fixed day and time for their match.
|
|
- Verifying that both their Pokémon battle team and their opponent's are in compliance before, during, and after the match. This is the sole responsibility of each competitor. The staff will not be responsible for illegal teams presented by competitors, whether by error, omission, or bad intentions.
|
|
|
|
### B. Captain Responsibilities
|
|
|
|
The responsibilities of the CAPTAINS are the same as those of the competitors, but also include, but are not limited to:
|
|
|
|
- Meeting the deadlines established for contacts and reports in the regulations, in the messages sent by the staff and by the various bots programmed for sending rosters and contacting the opposing team.
|
|
- Proceeding with respectful and cordial contact, maintaining an active chat with the opposing captain in the encounter channel.
|
|
- Coordinating and confirming that their players manage to coordinate their respective matches in a timely manner, as well as moderating their behavior on the server.
|
|
- Establishing timely contact with the staff members in case of disputes, conflicts, or anomalies during the encounter both in the private channel and in the encounter channel. Any request related to the tournament should not be made privately to the staff members. The staff reserves the right to respond or not to inquiries through private messages, both on Discord and WhatsApp and similar messaging applications.
|
|
|
|
### C. Staff Responsibilities
|
|
|
|
The responsibilities of the STAFF include, but are not limited to:
|
|
|
|
- Guiding and providing the tools available so that both competitors and captains fulfill their roles and deadlines.
|
|
- Enforcing the regulations using their own judgment, without the influence of the competitors, considering all possibilities tirelessly to impart equality and consistency in the development of the tournament.
|
|
- Using their powers to enforce the regulations, intervening as mediators in the encounters to ensure a smooth development of the same and if necessary, to take disciplinary measures against violations of the regulations, the organization, the teams, the competitors, the values, and good customs.
|
|
- The staff has the power to analyze and interpret the actions of the competitors and use the points of these regulations as a guide to reach a fair decision.
|
|
- Establishing, regulating, interpreting, and assisting in the use of the regulations, as well as preventing the abusive use of its limitations, to achieve better competitiveness and interaction among BOX STADIUM competitors.
|
|
|
|
### D. Manager Responsibilities
|
|
|
|
The responsibilities of the manager include, but are not limited to:
|
|
|
|
- Supporting the coordination of each team member's battles.
|
|
- Supporting by providing both written themes and visual resources to the team members.
|
|
|
|
## 7. Creation of Pokémon Battle Teams
|
|
|
|
Depending on their role, the competitor must choose six (6) different species to build their Pokémon team, with mega evolutions excluded by default for ultra league and super league. Each competitor must comply with the rules and restrictions of the competition meta:
|
|
|
|
- **SUPERBALL LEAGUE COMPETITORS:** Slot pick format with a maximum selection score.
|
|
- **ULTRABALL LEAGUE COMPETITORS:** Slot pick format with a maximum selection score.
|
|
- **MASTERBALL LEAGUE COMPETITORS:** Slot pick format with a maximum selection score.
|
|
- **THEMATIC COMPETITORS:** Selection of a team of 6 Pokémon based on the guidelines and restrictions of each theme to be played.
|
|
|
|
## 8. Matches, Point System, and Tiebreaker Criteria
|
|
|
|
### A. Matches
|
|
|
|
Matches last one hundred and twenty (120) hours. Each match consists of seven (7) individual games, in which two (2) competitors, one (1) from each team, face each other with a common role.
|
|
|
|
### B. Games
|
|
|
|
A game consists of three (3) battles, which the competitors must complete and report within the 120 hours of the current round.
|
|
|
|
### C. Point System
|
|
|
|
The winner of a game is decided by the best of three (3) battles (Bo3 system). While a game of three battles counts as three (3) points in favor of their team on the match scoreboard, each battle won in a game means 1 (one) point in favor of their team in the victory point difference (goals). This score will be used as a tiebreaker criterion at the end of the Group Stage and in case two or more teams tie in points on the general table of each front, so it is necessary to play the 3 battles per match. If a rival refuses to play the third game, it will automatically be in favor of the opponent.
|
|
|
|
## 9. Submission of Rosters
|
|
|
|
- The manager or captain must send the list of their players no later than 20:00 hrs GMT-6. If a team does not send the roster on time, they will be penalized with a 0-2 against for each player.
|
|
- If neither team sends the roster on time, the score will be 0-0.
|
|
- Rosters must be sent in the corresponding private channels for each team in the following order:
|
|
- Super player
|
|
- Ultra player
|
|
- Master player
|
|
- Thematic player 1
|
|
- Thematic player 2
|
|
|
|
## 10. Submission of templates
|
|
|
|
### A. Submission Process
|
|
|
|
The submission of templates will be in the designated match channel for each confrontation between captains or team managers no later than 24 hours after the start of the round until 22:00 hrs GMT-6 on Mondays.
|
|
|
|
### B. Template Requirements
|
|
|
|
Templates must indicate the best buddy for the three leagues and in master must declare which mega evolution will be used in their team if used. Failure to do so and using it during the match will be penalized with the loss of that match and it cannot be used in the following battles.
|
|
|
|
### C. Delay in Submission
|
|
|
|
- A delay of up to 9 minutes: the captain gets a strike.
|
|
- From 10 to 20 minutes: results in a three-battle game declared as a loss. The captain or manager can choose which player will get the negative result.
|
|
- After 30 minutes: they automatically lose the round while the captain gets a strike. Repeating this fault results in a strike and a one-round suspension even if the delay is one (1) minute.
|
|
|
|
## 10. Schedules, Start of the Round, and Opening of Channels
|
|
|
|
### A. Round Timing
|
|
|
|
Rounds start at 22:00 GMT-6 on Sundays, with the end of the rounds on Fridays at 22:00 GMT-6.
|
|
|
|
### B. Match Channels
|
|
|
|
Staff members will create the match channels and they will be visible even before the current round ends. Competitors can enter the match once the staff announces the start of the round.
|
|
|
|
### C. Schedule Command
|
|
|
|
You can request the staff to execute the schedule command at any time.
|
|
|
|
### D. Star Match
|
|
|
|
The administration will designate a match from each encounter in each round of the league as a star match, which players can choose to record their matches and send them to the medium determined by the organization or play it live on the league platform.
|
|
|
|
## 11. Contact and Coordination Procedure
|
|
|
|
### A. Contact Window
|
|
|
|
Competitors have 24 hours from 22:00 hrs GMT-6 to contact their rivals. They must maintain an active chat in the match channel until they effectively agree on a fixed schedule.
|
|
|
|
### B. Confirmation
|
|
|
|
Confirmation will be considered successful when competitors agree on a fixed schedule, verifying the time difference.
|
|
|
|
### C. Responsibility
|
|
|
|
Competitors have the responsibility to check the match channel in case of mentions. There will be no consideration if a successful coordination is not completed.
|
|
|
|
### D. Availability
|
|
|
|
Competitors must mention their rival and clarify which days and times they are available to play the game. Both will try to reach an agreement on a single fixed schedule.
|
|
|
|
### E. Time Format
|
|
|
|
All provided schedules must be informed in 24-hour format (23:59).
|
|
|
|
### F. Message Editing
|
|
|
|
Editing messages sent in the match channel during the first twenty-four (24) hours, intended for coordination, is prohibited. Messages that serve as a summary of coordination are exempt.
|
|
|
|
### G. Fixed Schedule
|
|
|
|
Competitors must negotiate a single fixed schedule. Only messages that meet this requirement will be considered as a fixed schedule confirmation.
|
|
|
|
### H. Schedule Agreement
|
|
|
|
If your opponent proposes a range of schedules that is within your possibilities, you must indicate an exact time for the match and wait for confirmation.
|
|
|
|
### I. Schedule Conflict
|
|
|
|
If your opponent proposes a time range in which you cannot fight, you must express it and negotiate your time ranges. If an agreement cannot be reached, you must mention it to the captains and staff members.
|
|
|
|
### J. Organization Decision
|
|
|
|
This member of the organization will determine what is appropriate, whether it is the use of a substitute, default loss, cancellation, or rescheduling of the match or matches.
|
|
|
|
### K. Match Advancement
|
|
|
|
Competitors can propose to their opponents to bring forward the matches, and the latter can accept if they are available to play the match on the current date.
|
|
|
|
### L. No Response
|
|
|
|
If you do not receive a response from your opponent one hour before the coordination stage ends, you are responsible for tagging the staff according to your front, the opposing team, and your captains.
|
|
|
|
### M. Uncoordinated Matches
|
|
|
|
If the coordination stage ends and there are pairs that have not yet coordinated a fixed combat time, the staff will analyze the chat between competitors and determine if the match requires the substitution of one or two players, or the cancellation or rescheduling of the match.
|
|
|
|
### N. Effective Contact
|
|
|
|
Messages sent through channels or private messages outside the match channel of the current date will not be considered as "effective contact attempts."
|
|
|
|
### O. Last-Minute Coordination
|
|
|
|
If the opposing player arrives within 30 minutes or less before the coordination stage ends, they must adapt to the proposed time by the player.
|
|
|
|
### P. Ineffective Coordination
|
|
|
|
If the previous procedures are followed and the opponent does not appear in the match channel for effective coordination, the player of that match must send a message using @captain @opposingteam and @staff explicitly requesting either the applicable sanction for ineffective coordination or a rescheduling of the match.
|
|
|
|
## 12. Combat Team Exchange Procedure
|
|
|
|
### A. Team Templates
|
|
|
|
Teams must be informed using the template provided by the organization, clearly showing the Pokémon's CP, its shadow or purified form, if it has a best friend ribbon, mega evolution, clarifying all variants.
|
|
|
|
### B. Rule Violation
|
|
|
|
Using an unregistered Pokémon, incorrect CP, or undeclared mega evolution will be penalized with the loss of that match. The opponent must stop the match to inform the rival player of the rule violation.
|
|
|
|
### C. Channel Usage
|
|
|
|
The entire combat team exchange procedure must be carried out in the corresponding channel of the current date's match.
|
|
|
|
### D. Team History
|
|
|
|
The team templates used per round will be shared with the participants of their front in the #team-history channel to create a more competitive and strategic environment.
|
|
|
|
## 13. Substitute Usage Procedure
|
|
|
|
### A. Substitute Notification
|
|
|
|
Teams can use a substitute if one of their main players is unable to attend the match of the current date. Any competitor must inform the player change on behalf of the team to the staff members of each front from the start of the current date until five (5) minutes before the time agreed by the main player.
|
|
|
|
### B. Irreversible Request
|
|
|
|
Once requested, it cannot be reversed. Substitutes must use the Pokémon team of the main player they are replacing.
|
|
|
|
### C. Delay in Substitution
|
|
|
|
If the use of substitutes occurs with a delay of up to fifteen (15) minutes from the agreed time by the main player, the incoming player must start the match with one (1) combat against them.
|
|
|
|
### D. Single Substitution
|
|
|
|
The same player who is being substituted cannot be substituted again.
|
|
|
|
### E. Repeated Substitutions
|
|
|
|
If a team repeatedly requests substitutions, the staff may decide whether to grant or deny the possibility of a change.
|
|
|
|
## 14. Combat Procedure
|
|
|
|
### A. Match Duration
|
|
|
|
Competitors must complete and report their matches within the ONE HUNDRED TWENTY (120) hour duration of the current date.
|
|
|
|
### B. Illegal Combat Team
|
|
|
|
If a competitor enters the battlefield with an illegal combat team, they will be allowed to rectify their team for the next match, but it will be marked as a loss in the affected match.
|
|
|
|
### C. Notification of Anomaly
|
|
|
|
The opponent, upon noticing this anomaly, must immediately notify their rival and the staff.
|
|
|
|
### D. Abandoning Match
|
|
|
|
If this anomaly is clearly noticeable at the beginning of the match, the competitor can abandon it.
|
|
|
|
### E. Pokémon Modification
|
|
|
|
Once the matches have started, competitors cannot change their Pokémon partner or modify the registered Pokémon's fast or charged attacks.
|
|
|
|
### F. Pokémon Selection Time
|
|
|
|
The Pokémon selection before the match in the Pokémon GO application cannot take more than two (2) minutes in any of the three (3) matches.
|
|
|
|
### G. Connection Issues
|
|
|
|
In case of any connection issues, lag, or anomalies during the matches, the competitor must immediately notify their rival of this issue.
|
|
|
|
### H. Match Registration
|
|
|
|
The match of the encounter comprises the first three (3) matches registered in the trainer's diary.
|
|
|
|
### I. Dispute Formation
|
|
|
|
In case of a dispute, the competitor who does not make the claim will have the right to choose the formation for the rematch.
|
|
|
|
### J. Screenshot Request
|
|
|
|
The staff can request a screenshot of their diary at any time.
|
|
|
|
## 15. Dispute Procedure and Evidence Submission
|
|
|
|
### A. Dispute Request
|
|
|
|
After playing the three (3) matches and the mandatory provisional rematch, competitors must use the command !dispute followed by the reason for the dispute to request the intervention of a referee.
|
|
|
|
### B. Video Evidence
|
|
|
|
The video evidence must be at normal speed and not edited in any way.
|
|
|
|
### C. Evidence Submission
|
|
|
|
Once the evidence is uploaded to the Stremeable or Google Drive server, the competitor who claims must share the link in their team's private channel tagging the staff corresponding to their front.
|
|
|
|
### D. Result Reporting
|
|
|
|
If there is an open dispute, the result cannot be reported until the arbitration team or staff notifies a verdict.
|
|
|
|
### E. Evidence Requirement
|
|
|
|
Any dispute request not accompanied by evidence will be dismissed.
|
|
|
|
### F. Staff Requests
|
|
|
|
The arbitration team or staff may request recordings of the match and screenshots of the IVs of the used specimens from the competitors.
|
|
|
|
### G. Rematch Request
|
|
|
|
In no case can the person who requested a rematch request a new rematch on the rematch.
|
|
|
|
## 16. Result Reporting Procedure
|
|
|
|
### A. Reporting Results
|
|
|
|
After concluding the three (3) match game, competitors must report the result using the designated command: !report
|
|
|
|
### B. Reporting Example
|
|
|
|
- If won: `!report @me 2-1 @opponent`
|
|
- If lost: `!report @me 1-2 @opponent`
|
|
|
|
### C. Captain Reporting
|
|
|
|
Captains can also report the result of one of their players' matches.
|
|
|
|
### D. Agreement on Result
|
|
|
|
Reporting a match means agreeing with the result. You cannot request a dispute after reporting the match results.
|
|
|
|
### E. Result Confirmation
|
|
|
|
To confirm a result reported by an opponent, the competitor must react to the Bot message indicating the match result.
|
|
|
|
### F. Dispute Resolution
|
|
|
|
After the dispute resolution, the verdict will be given and the players will be informed to record the result.
|
|
|
|
## 17. Internal and External Technical Problems
|
|
|
|
### A. Internal Technical Problems
|
|
|
|
These refer to technical issues caused by the state of the game or its server. Some issues, such as the inability to switch a Pokémon or the desynchronization of fast attacks, are not grounds for a rematch.
|
|
|
|
### B. External Technical Problems
|
|
|
|
These refer to technical issues caused by low battery or device settings, connectivity signal issues, or background applications that slow down the game rendering.
|
|
|
|
### C. Staff Tools
|
|
|
|
The tournament staff has several tools for reviewing evidence to give a verdict appropriate to the circumstance.
|
|
|
|
## 18. Anomaly Reports and Staff Response Time
|
|
|
|
### A. Anomaly Notification
|
|
|
|
If one or more competitors detect an anomaly, it must be notified immediately using @administrator.
|
|
|
|
### B. Staff Response Time
|
|
|
|
The staff response time to a dispute or help request can be up to 24 hours.
|
|
|
|
### C. Immediate Response
|
|
|
|
Requests requiring an immediate response must be notified to a member with an administrator rank.
|
|
|
|
### D. Evidence Verification
|
|
|
|
The staff has tools to identify deleted, edited, forwarded messages, as well as the use of commands not provided for the competition.
|
|
|
|
### E. Staff Anomalies
|
|
|
|
In case of any anomaly with the staff, players must report to a member with an administrator rank for evidence review and case analysis.
|
|
|
|
## 19. Strike, Suspension, and Warning System
|
|
|
|
### A. Warnings
|
|
|
|
These are the sanctions and suspensions given to a competitor who commits one or more rule violations.
|
|
|
|
### B. Warning Accumulation
|
|
|
|
Accumulating 3 warnings automatically results in a strike.
|
|
|
|
### C. Suspension Sanction
|
|
|
|
The staff will give this type of sanction to verify and analyze the case in question to give a fair ruling and an exemplary punishment.
|
|
|
|
### D. Strikes
|
|
|
|
Strikes are given for a medium severity violation. Accumulating 3 strikes results in expulsion from the server.
|
|
|
|
### E. Suspensions
|
|
|
|
Suspensions are applied in parallel to warnings or strikes as a complementary form of punishment.
|
|
|
|
### F. Bans
|
|
|
|
A ban implies the permanent expulsion of the team member or user from the server to which it is applied. This includes the Discord server and the competition.
|
|
|
|
## 20. Guide to Violations and Punishments
|
|
|
|
This section of the rules can be used by the staff as a guide on how to proceed in case of a violation. Any detected violation not covered in this section or any content in these rules can be interpreted and resolved by the staff in the way they deem appropriate, setting a precedent for its future inclusion.
|
|
|
|
### A. Conduct Violations
|
|
|
|
1. **Towards competitors, staff, organizers, or organization**: Insulting, harassing, intimidating, threatening, provoking, harassing, discriminating based on race, gender, religion, age, sexual orientation, or other similar attributes or protected groups, whether through audio, images, messages, emojis, or reactions. These types of violations, depending on the context, have punishments ranging from warnings, isolations, mutes, and strikes to loss of points, matches, suspensions, or temporary or permanent bans.
|
|
|
|
### B. Slow Play Violations
|
|
|
|
1. **Delay in submitting rosters**:
|
|
- Delay of up to 14 minutes: the captain receives a strike.
|
|
- Delay from 15 to 29 minutes: a three-match game against. The captains choose which player will receive the negative result.
|
|
- Delay from 30 minutes: Automatic defeat + strike to the captain.
|
|
- Recurrence: strike to the captains + suspension date for a 1-minute delay.
|
|
|
|
2. **Delay in scheduling**: Up to 10 minutes warning. After that time, a strike is appropriate.
|
|
|
|
3. **Delay in scheduled match time**:
|
|
- Delay of up to 15 minutes results in a strike.
|
|
- From 16 minutes, it is a match against.
|
|
- Up to 30 minutes, it is a match against with mandatory use of substitutes.
|
|
- After 30 minutes will be a 3-0 score against the player who does not show up for the match. In this case, the affected player must use @staff of their front requesting the corresponding sanction. If the message is not explicit, the sanction will not be granted, and the match will be canceled.
|
|
|
|
4. **Delay in submitting the team template**: Exceeding the 2-minute limit between messages, the sanction can range from a warning to loss of points.
|
|
|
|
5. **Delay in sending or rematching**: Exceeding the 2-minute limit of waiting, reading, and choosing a team between matches, the sanction is a match against.
|
|
|
|
6. **Delay in reporting the match**: Exceeding the 1-hour limit after the three-match game, the corresponding sanction is a warning or strike.
|
|
|
|
7. **Delay of both players to finish and report a match within the established deadline**: If two competitors from different teams start their matches before the end of the round, complete them, and report after the end of the same or have an approved and expressed time extension by a staff member, they cannot request reviews for dispute, extensions, or intervention requests of any kind to any staff member. If two competitors start their matches after the end of the date, not only do they not have the right to dispute, but they will also be sanctioned with a warning according to the context.
|
|
|
|
8. **Refusing to play the provisional match**: It is mandatory to play the 4th match in case of a dispute. A match against (0-1) will be sanctioned to those who refuse to play it. **IT IS NOT NECESSARY TO WAIT FOR THE STAFF RESOLUTION TO PLAY THE PROVISIONAL MATCH.**
|
|
|
|
### C. Absence Violations
|
|
|
|
1. **Absence in scheduling**: Warnings to loss of points.
|
|
2. **Absence in scheduled match time**: Match against, use of substitute, and strikes for the team captains.
|
|
3. **Absence in the middle of an ongoing match**: Depending on the reasons and time, the match may be considered lost. Absence is considered when a competitor exceeds the 30-minute delay regarding the established deadlines and/or schedules.
|
|
|
|
### D. Violations for Incorrect Information
|
|
|
|
1. **Incorrect information about schedules and time differences**: Providing incorrect or omitting schedule or time difference information may result in penalties ranging from warnings to strikes.
|
|
|
|
### E. Penalties for Unsportsmanlike Conduct
|
|
|
|
1. **Being aggressive**: Strike.
|
|
2. **Not following staff instructions**: Strike.
|
|
3. **Trying to provoke a rival or staff**: Strike.
|
|
4. **Mocking a rival**: Strike.
|
|
5. **Mocking a mistake in any way**: Strike.
|
|
|
|
## 21. Recognition System
|
|
|
|
The recognition system aims to distinguish players who excel in the tournament both for their skill and behavior. Teams and competitors who achieve any of these accomplishments will receive an exclusive role and an honorable mention on BOX STADIUM's Instagram. This system, as well as the guide, is subject to constant updates.
|
|
|
|
### A. Punctuality and Responsibility
|
|
|
|
- **PUNCTUAL**: Teams that accumulate 10 matches without payroll delays, 10 matches without coordination delays, and/or 10 matches without combat delays.
|
|
- **RELIABLE**: Teams that accumulate 6 matches without payroll delays, 6 matches without coordination delays, and/or 6 matches without combat delays.
|
|
- **STRIKE REMOVAL**: Teams that accumulate 4 matches without payroll delays, 4 matches without coordination delays, and/or 4 matches without combat delays.
|
|
|
|
### B. Fair Play
|
|
|
|
- **EXEMPLARY TEAM**: Teams with the fewest infractions and complaints.
|
|
- **FAIR PLAY TEAM / FAIR PLAYER**: Competitors who intervene in conflicts to resolve them, who do not complain about very minimal delays or small errors from the rival, who maintain a diplomatic stance in disagreements with the rival team, and/or who help and guide their teammates.
|
|
|
|
### Prizes
|
|
|
|
- **1st Place**: 1000 USD
|
|
- **2nd Place**: 500 USD
|
|
- **3rd Place**: 250 USD
|
|
- **Group stage top scorer**: 100 USD
|
|
- **Finals stage top scorer**: 100 USD
|
|
|
|
To claim the prize, the teams in the final and third place must send recordings of the 21 matches played on that date for league publicity purposes, including videos from the fourth place. In case of a tie in the score table for the top scorer prizes, a match will be held between the players to determine the prize winner.
|
|
|
|
With potential changes in attacks for the season starting in December, the league reserves the right to take a break, either for one week for minor changes, resuming matches on December 9, 2024. In case of major changes, the league will resume on January 6.
|