From 0493b20f780959f560670b1d62b460940c0b2a18 Mon Sep 17 00:00:00 2001 From: Albionthegreat <74660626+Albionthegreat@users.noreply.github.com> Date: Tue, 5 Nov 2024 16:33:49 +0100 Subject: [PATCH 1/6] Update `Official tournament support` --- wiki/Tournaments/Official_support/en.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/wiki/Tournaments/Official_support/en.md b/wiki/Tournaments/Official_support/en.md index 9c13b415017c..77a27eeef042 100644 --- a/wiki/Tournaments/Official_support/en.md +++ b/wiki/Tournaments/Official_support/en.md @@ -27,7 +27,8 @@ Officially supported tournaments have access to: Community-run tournaments which abide by the following hard criteria are eligible for support: - The tournament series must run no more than two times per year. -- The tournament must operate on a Round of 16 double-elimination format at a minimum. +- The tournament must operate on a Round of 16 double-elimination or a round of 32 single-elimination format at a minimum. + - LAN tournaments must operate on a Round of 8 double-elimination or a round of 16 single-elimination format at a minimum. - Larger formats, such as group stages and Swiss brackets, may also be used so long as they start with at least 16 teams and, if applicable and if starting with only 16 teams, break to a double-elimination bracket afterwards. - Tournaments that feature a draft format may operate on a Round of 8 double-elimination bracket provided the tournament meets the following additional criteria: - The tournament is open rank. @@ -86,8 +87,7 @@ In addition, all promotional material or any services associated with a tourname - All registrants must be screened by the account support team before play commences.[^play-commence] See [tournament screening](#tournament-screening) for more details. - If a user satisfies the sign-up criteria (if any) and is not [filtered](#registrant-filtering-and-seeding) out through other means, the tournament must not prevent those who pass the screening from participating without both ample evidence presented publicly against them and the approval of the account support team. - This includes preventing users who are perceived to be "sandbagging" from play. Should an organiser have valid concerns about the presence of such players affecting the competitive integrity of their tournament, they may raise the issue to the [Tournament Committee](/wiki/People/Tournament_Committee) for a case-by-case review using the [tournament reports form](https://pif.ephemeral.ink/tournament-reports). -- A dedicated referee must be present during every match, or be available to be summoned with minimal delay (2–5 minutes) if appropriate permission for automated software has been granted and is being used for assistance. Players cannot "self-ref". - - The use of bots is allowed on qualifier stage matches, provided that it is supervised by a staff member. +- A dedicated referee must be present during every match, or be available to be summoned with minimal delay (2–5 minutes) if appropriate permission for [automated software](#Automated-refereeing) has been granted and is being used for assistance. Players cannot "self-ref". - Every match within the same bracket or qualifier stage should be held in a consistent format. For example, in a tournament which uses a qualifier stage and a double-elimination bracket stage, bracket matches should all be played either synchronously or asynchronously, but not both. - All multiplayer matches relevant to the tournament must be created with the `!mp make` command, so that they do not expire. The results must be recorded and made publicly available on the original tournament forum post or an outside source linked on the forum post in a clear and accessible format. - All rule changes should be communicated clearly to all participants. Those should keep the expectations noted [above](#tournaments). @@ -96,7 +96,9 @@ Once the tournament has concluded, the tournament organisers will need to submit - A list of applicable badge recipients (a.k.a. the winners of your tournament). - An appropriately designed badge ([see below](#profile-badges)). -- A link to the publicly viewable catalogue of your tournament's match history. +- A Link to the tournament's wiki page or spreadsheet(s) with: + - The publicly viewable catalogue of your tournament's match history, including qualifiers where applicable. + - The publicly viewable catalogue of your tournament's mappools. ### Programs @@ -141,7 +143,7 @@ With regards to staff roles, the following rules apply: Users under an active tournament ban are expected to disclose their tournament ban status to any officially supported tournament they intend to help with. They may be enlisted as streamers, commentators, or graphic designers at the host's discretion, but we encourage careful consideration of such choices as said individuals have already infringed upon the rules once (or more). They may not act as any other staff role UNLESS the host requests an exemption for them when sending in their initial request for support. The account support team will then assess these on a case-by-case basis with the user's history in mind. -At the support team's discretion, staff members whose conduct directly results in a tournament losing its official support may not fulfil the same roles in, nor be the host or admin of, another badged tournament for at least 4 months. In the event this cooldown is applied to a user, they will be informed directly through the [tournament team](mailto:tournaments@ppy.sh). +At the support team's discretion, staff members whose conduct directly results in a tournament losing its official support may not fulfil the same roles in, nor be the host or admin of, another badged tournament for at least 4 months. In the event where a staffing ban is applied to a user, they will be informed directly through the [tournament team](mailto:tournaments@ppy.sh). A list of all tournament staff must be publicly visible in an easily accessible location. This list may be contained within the tournament's forum post, wiki page, website, or spreadsheet. From 270b12d1d1d72c0ad859029cca40a889d4a90f5d Mon Sep 17 00:00:00 2001 From: Albionthegreat <74660626+Albionthegreat@users.noreply.github.com> Date: Tue, 5 Nov 2024 18:07:48 +0100 Subject: [PATCH 2/6] Change wording --- wiki/Tournaments/Official_support/en.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/wiki/Tournaments/Official_support/en.md b/wiki/Tournaments/Official_support/en.md index 77a27eeef042..2450d084c32c 100644 --- a/wiki/Tournaments/Official_support/en.md +++ b/wiki/Tournaments/Official_support/en.md @@ -27,8 +27,8 @@ Officially supported tournaments have access to: Community-run tournaments which abide by the following hard criteria are eligible for support: - The tournament series must run no more than two times per year. -- The tournament must operate on a Round of 16 double-elimination or a round of 32 single-elimination format at a minimum. - - LAN tournaments must operate on a Round of 8 double-elimination or a round of 16 single-elimination format at a minimum. +- The tournament must operate on a Round of 16 double-elimination or a Round of 32 single-elimination format at a minimum. + - LAN tournaments must operate on a Round of 8 double-elimination or a Round of 16 single-elimination format at a minimum. - Larger formats, such as group stages and Swiss brackets, may also be used so long as they start with at least 16 teams and, if applicable and if starting with only 16 teams, break to a double-elimination bracket afterwards. - Tournaments that feature a draft format may operate on a Round of 8 double-elimination bracket provided the tournament meets the following additional criteria: - The tournament is open rank. @@ -87,7 +87,7 @@ In addition, all promotional material or any services associated with a tourname - All registrants must be screened by the account support team before play commences.[^play-commence] See [tournament screening](#tournament-screening) for more details. - If a user satisfies the sign-up criteria (if any) and is not [filtered](#registrant-filtering-and-seeding) out through other means, the tournament must not prevent those who pass the screening from participating without both ample evidence presented publicly against them and the approval of the account support team. - This includes preventing users who are perceived to be "sandbagging" from play. Should an organiser have valid concerns about the presence of such players affecting the competitive integrity of their tournament, they may raise the issue to the [Tournament Committee](/wiki/People/Tournament_Committee) for a case-by-case review using the [tournament reports form](https://pif.ephemeral.ink/tournament-reports). -- A dedicated referee must be present during every match, or be available to be summoned with minimal delay (2–5 minutes) if appropriate permission for [automated software](#Automated-refereeing) has been granted and is being used for assistance. Players cannot "self-ref". +- A dedicated referee must be present during every match, or be available to be summoned with minimal delay (2–5 minutes) if appropriate permission for [automated software](#Automated-refereeing) has been granted and is being used for assistance. Players may not "self-ref". - Every match within the same bracket or qualifier stage should be held in a consistent format. For example, in a tournament which uses a qualifier stage and a double-elimination bracket stage, bracket matches should all be played either synchronously or asynchronously, but not both. - All multiplayer matches relevant to the tournament must be created with the `!mp make` command, so that they do not expire. The results must be recorded and made publicly available on the original tournament forum post or an outside source linked on the forum post in a clear and accessible format. - All rule changes should be communicated clearly to all participants. Those should keep the expectations noted [above](#tournaments). @@ -96,9 +96,10 @@ Once the tournament has concluded, the tournament organisers will need to submit - A list of applicable badge recipients (a.k.a. the winners of your tournament). - An appropriately designed badge ([see below](#profile-badges)). -- A Link to the tournament's wiki page or spreadsheet(s) with: - - The publicly viewable catalogue of your tournament's match history, including qualifiers where applicable. - - The publicly viewable catalogue of your tournament's mappools. +- Links to the tournament's wiki page, website and/or publicly viewable spreadsheet(s) with: + - The tournament's match history with links to all matches, including qualifiers where applicable. + - The tournament's mappools. + - The qualifier results — for tournaments that use qualifiers. ### Programs From 6887c58852350dc1fe3b435f2d65102b9231bb94 Mon Sep 17 00:00:00 2001 From: Albionthegreat <74660626+Albionthegreat@users.noreply.github.com> Date: Sun, 10 Nov 2024 22:07:49 +0100 Subject: [PATCH 3/6] Require all staff lists to be up to date and in sync --- wiki/Tournaments/Official_support/en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/Tournaments/Official_support/en.md b/wiki/Tournaments/Official_support/en.md index 2450d084c32c..ecfe29358a35 100644 --- a/wiki/Tournaments/Official_support/en.md +++ b/wiki/Tournaments/Official_support/en.md @@ -146,7 +146,7 @@ Users under an active tournament ban are expected to disclose their tournament b At the support team's discretion, staff members whose conduct directly results in a tournament losing its official support may not fulfil the same roles in, nor be the host or admin of, another badged tournament for at least 4 months. In the event where a staffing ban is applied to a user, they will be informed directly through the [tournament team](mailto:tournaments@ppy.sh). -A list of all tournament staff must be publicly visible in an easily accessible location. This list may be contained within the tournament's forum post, wiki page, website, or spreadsheet. +A list of all tournament staff must be publicly visible in an easily accessible location. This list may be contained within the tournament's forum post, wiki page, website, or spreadsheet. If there are multiple lists of staff, they must all be up to date and in sync with one another. ### Players From 0d2b849550738763f53a57d436ea5104c27cfa6e Mon Sep 17 00:00:00 2001 From: Albionthegreat <74660626+Albionthegreat@users.noreply.github.com> Date: Mon, 11 Nov 2024 19:50:48 +0100 Subject: [PATCH 4/6] Apply Stage's review Co-authored-by: hburn7 <38370573+hburn7@users.noreply.github.com> --- wiki/Tournaments/Official_support/en.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/wiki/Tournaments/Official_support/en.md b/wiki/Tournaments/Official_support/en.md index ecfe29358a35..aa82713cd593 100644 --- a/wiki/Tournaments/Official_support/en.md +++ b/wiki/Tournaments/Official_support/en.md @@ -99,7 +99,7 @@ Once the tournament has concluded, the tournament organisers will need to submit - Links to the tournament's wiki page, website and/or publicly viewable spreadsheet(s) with: - The tournament's match history with links to all matches, including qualifiers where applicable. - The tournament's mappools. - - The qualifier results — for tournaments that use qualifiers. + - The tournament's qualifier results, where applicable. ### Programs @@ -144,7 +144,7 @@ With regards to staff roles, the following rules apply: Users under an active tournament ban are expected to disclose their tournament ban status to any officially supported tournament they intend to help with. They may be enlisted as streamers, commentators, or graphic designers at the host's discretion, but we encourage careful consideration of such choices as said individuals have already infringed upon the rules once (or more). They may not act as any other staff role UNLESS the host requests an exemption for them when sending in their initial request for support. The account support team will then assess these on a case-by-case basis with the user's history in mind. -At the support team's discretion, staff members whose conduct directly results in a tournament losing its official support may not fulfil the same roles in, nor be the host or admin of, another badged tournament for at least 4 months. In the event where a staffing ban is applied to a user, they will be informed directly through the [tournament team](mailto:tournaments@ppy.sh). +At the support team's discretion, staff members whose conduct directly results in a tournament losing its official support may not fulfil the same roles in, nor be the host or admin of, another officially-supported tournament for at least 4 months. In the event a staffing ban is applied to a user, they will be informed directly through the [tournament team](mailto:tournaments@ppy.sh). A list of all tournament staff must be publicly visible in an easily accessible location. This list may be contained within the tournament's forum post, wiki page, website, or spreadsheet. If there are multiple lists of staff, they must all be up to date and in sync with one another. From 115483f88b86a7abd4bf1ef95d7f78916bf42d81 Mon Sep 17 00:00:00 2001 From: Hivie <62819481+Hiviexd@users.noreply.github.com> Date: Tue, 12 Nov 2024 10:51:18 +0100 Subject: [PATCH 5/6] fix wikilink --- wiki/Tournaments/Official_support/en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/Tournaments/Official_support/en.md b/wiki/Tournaments/Official_support/en.md index aa82713cd593..c85df877ab8b 100644 --- a/wiki/Tournaments/Official_support/en.md +++ b/wiki/Tournaments/Official_support/en.md @@ -87,7 +87,7 @@ In addition, all promotional material or any services associated with a tourname - All registrants must be screened by the account support team before play commences.[^play-commence] See [tournament screening](#tournament-screening) for more details. - If a user satisfies the sign-up criteria (if any) and is not [filtered](#registrant-filtering-and-seeding) out through other means, the tournament must not prevent those who pass the screening from participating without both ample evidence presented publicly against them and the approval of the account support team. - This includes preventing users who are perceived to be "sandbagging" from play. Should an organiser have valid concerns about the presence of such players affecting the competitive integrity of their tournament, they may raise the issue to the [Tournament Committee](/wiki/People/Tournament_Committee) for a case-by-case review using the [tournament reports form](https://pif.ephemeral.ink/tournament-reports). -- A dedicated referee must be present during every match, or be available to be summoned with minimal delay (2–5 minutes) if appropriate permission for [automated software](#Automated-refereeing) has been granted and is being used for assistance. Players may not "self-ref". +- A dedicated referee must be present during every match, or be available to be summoned with minimal delay (2–5 minutes) if appropriate permission for [automated software](#automated-refereeing) has been granted and is being used for assistance. Players may not "self-ref". - Every match within the same bracket or qualifier stage should be held in a consistent format. For example, in a tournament which uses a qualifier stage and a double-elimination bracket stage, bracket matches should all be played either synchronously or asynchronously, but not both. - All multiplayer matches relevant to the tournament must be created with the `!mp make` command, so that they do not expire. The results must be recorded and made publicly available on the original tournament forum post or an outside source linked on the forum post in a clear and accessible format. - All rule changes should be communicated clearly to all participants. Those should keep the expectations noted [above](#tournaments). From dc7742cee8065aafa72e0c8b3306d67a325b29f1 Mon Sep 17 00:00:00 2001 From: Hivie <62819481+Hiviexd@users.noreply.github.com> Date: Tue, 12 Nov 2024 10:51:57 +0100 Subject: [PATCH 6/6] outdate translations --- wiki/Tournaments/Official_support/es.md | 2 ++ wiki/Tournaments/Official_support/fr.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/wiki/Tournaments/Official_support/es.md b/wiki/Tournaments/Official_support/es.md index 544673f70a52..d2c00e368dbc 100644 --- a/wiki/Tournaments/Official_support/es.md +++ b/wiki/Tournaments/Official_support/es.md @@ -1,4 +1,6 @@ --- +outdated_translation: true +outdated_since: 0493b20f780959f560670b1d62b460940c0b2a18 tags: - badge - badges diff --git a/wiki/Tournaments/Official_support/fr.md b/wiki/Tournaments/Official_support/fr.md index 7a93729c653a..098437232179 100644 --- a/wiki/Tournaments/Official_support/fr.md +++ b/wiki/Tournaments/Official_support/fr.md @@ -1,4 +1,6 @@ --- +outdated_translation: true +outdated_since: 0493b20f780959f560670b1d62b460940c0b2a18 no_native_review: true tags: - badge