Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Le merge #1

Merged
merged 4 commits into from
May 25, 2024
Merged

Le merge #1

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1b6d2e0
Update `Tournaments/Official_Support` with Expectations for Programs
Albionthegreat May 23, 2024
d059a86
Update wording and clarify further.
Albionthegreat May 23, 2024
4b15e45
smol addition
Albionthegreat May 23, 2024
37dd403
shmol ficc
Albionthegreat May 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 29 additions & 8 deletions wiki/Tournaments/Official_support/en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ In addition, all promotional material or any services associated with a tourname
**The tournament must also abide by the following practices throughout:**

- 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), 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.
- If a user satisfies the sign-up criteria (if any) and is not [filtered](#registrant-filtering-seeding-and-automated-refereeing) 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.
Expand All @@ -91,16 +91,37 @@ Once the tournament has concluded, the tournament organisers will need to submit
- An appropriately designed badge ([see below](#profile-badges)).
- A link to the publicly viewable catalogue of your tournament's match history.

#### Referee bots/automation
### Registrant Filtering, Seeding and Automated Refereeing

The use of bots/automation to aid in the running of officially supported tournament matches is permitted *with some caveats to reflect their cutting-edge nature*, so long as any applicable software/workflows meet the requirements listed below:
#### Expectations for Programs

- The bot/automation must be made publicly and functionally available as an open-source repository.
- The bot/automation should abide by the expectations laid out for [bot accounts](/wiki/Bot_account) for general in-game use. Referee-related tools and software can be run directly from a user's own account.
- If a bot/automation is used for refereeing, a human referee must always be available to respond to calls for support from participants within a reasonable timeframe (2–5 minutes), and be able to be summoned remotely via the use of a chat command inside the lobby itself (we recommend `!panic` as a global alias for this).
- Where a bot/automation workflow is present, any ongoing lobbies should be able to be manually taken over by a human referee with minimal interference whilst also retaining any previous logs of play and chat.
Third-party programs designed to filter registrants, seed players, or automate the job of a referee must be open, transparent, and documented. Any third-party tool used for these purposes must:

Approval for the use of referee bots/automation **must** be granted by the osu! support team. In addition, this approval is required for **every individual instance where a referee bot/automation is used**. We expect to relax some of these requirements in the future as the technology surrounding these bots develops and experience with using them grows.
- Be made publicly and functionally available as an open-source repository.
- Be completely documented in an easily readable & digestable format.

Currently, approval for the use of any such tool must be **explicitly granted** by the osu! support team. Additionally, this approval must be granted for **every tournament where programs for registrant filtering, seeding, or automated refereeing are used.** We expect to relax some of these requirements in the future as the technology surrounding these programs develops and experience with using them grows.

#### Registrant Filtering and Seeding

Registrant filtering, not to be confused with [screening](#tournament-screening), is the process of using any program, algorithm, mathematical formula, or other objective means to remove otherwise good-standing players from a tournament. The standard use of such tools or systems is to reduce the variance in skill within a tournament. One such system that may come to mind is [BWS](/wiki/Tournaments/Badge-weighted_seeding).

In addition to the expectations for programs above, tools or systems used to filter registrants or seed players must also abide by the following practices:

- If a dataset is used, it must be up to date, publicly available and downloadable. Documentation must be provided explaining how to recreate the dataset and reproduce the results using it — including code where applicable.
- When doing qualifiers, the formula or method used to determine seeding must be included in the tournament's ruleset.

A third party should be able to get the same results without needing additional information. Manually filtering players or adjusting their seeds is strictly prohibited.

#### Automated Refereeing

The use of automated refereeing tools are permitted *with some caveats to reflect their cutting-edge nature*. Automated refereeing tools, including bots, may receive approval for use in badged tournaments so long as certain requirements are met.

In addition to the expectations for programs above, automated refereeing tools must also adhere to the following expectations:

- Potential bots must abide by the expectations laid out for [bot accounts](wiki/Bot_account) for general in-game use. Referee-related tools and software could alternatively be run directly from a user's own account.
- A human referee must always be available to respond to calls for support from participants within a reasonable timeframe (2–5 minutes), and be able to be summoned remotely via the use of a `!panic` command inside the lobby itself. When this command is used, all automation should stop until resumed by the human referee.
- Any ongoing lobbies should be able to be manually taken over by a human referee with minimal interference whilst also retaining any previous logs of play and chat.

### Staff

Expand Down
Loading