diff --git a/.gitattributes b/.gitattributes
index 4acff489ca641bfc95dcd8f508665f199b03a40c..ce1fba5a839ff0e1aa6c5bb705ec3882cb49bdb2 100644
--- a/.gitattributes
+++ b/.gitattributes
@@ -124,3 +124,5 @@ testbed/huggingface__pytorch-image-models/notebooks/GeneralizationToImageNetV2.i
testbed/gradio-app__gradio/js/app/public/static/img/Duck.glb filter=lfs diff=lfs merge=lfs -text
testbed/gradio-app__gradio/test/test_files/playable_but_bad_container.mkv filter=lfs diff=lfs merge=lfs -text
testbed/gradio-app__gradio/demo/model3D/files/Duck.glb filter=lfs diff=lfs merge=lfs -text
+testbed/fairlearn__fairlearn/fairlearn/widget/static/index.js.map filter=lfs diff=lfs merge=lfs -text
+testbed/fairlearn__fairlearn/fairlearn/widget/static/extension.js.map filter=lfs diff=lfs merge=lfs -text
diff --git a/testbed/Aider-AI__aider/assets/robot-flowchart.png b/testbed/Aider-AI__aider/assets/robot-flowchart.png
new file mode 100644
index 0000000000000000000000000000000000000000..7b61e51f6f58d3666bc947d2aef7b3ce0d63cf21
--- /dev/null
+++ b/testbed/Aider-AI__aider/assets/robot-flowchart.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:125308605b0a851296001af18843145464abf2a26cce2e43077b9870315dc440
+size 716411
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/CODEOWNERS b/testbed/Cog-Creators__Red-DiscordBot/.github/CODEOWNERS
new file mode 100644
index 0000000000000000000000000000000000000000..830d67f64ed84468234e70dc106ed4e673ed458e
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/CODEOWNERS
@@ -0,0 +1,30 @@
+# Cogs
+/redbot/cogs/audio/** @aikaterna @PredaaA
+/redbot/cogs/downloader/* @Jackenmen
+/redbot/cogs/streams/* @palmtree5
+/redbot/cogs/mutes/* @TrustyJAID
+
+# Docs - Install and update guides
+/docs/install_guides/** @Jackenmen
+/docs/update_red.rst @Jackenmen
+
+# Docs - Version guarantees
+/docs/version_guarantees.rst @Jackenmen
+
+# Trivia Lists
+/redbot/cogs/trivia/data/lists/whosthatpokemon*.yaml @aikaterna
+
+# Tests
+/redbot/pytest/downloader* @Jackenmen
+/tests/cogs/downloader/* @Jackenmen
+
+# Schemas
+/schema/* @Jackenmen
+
+# CI
+/.travis.yml @Kowlin
+/crowdin.yml @Kowlin
+/.github/workflows/* @Kowlin
+
+# Excludes
+**/locales/* @ghost
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/FUNDING.yml b/testbed/Cog-Creators__Red-DiscordBot/.github/FUNDING.yml
new file mode 100644
index 0000000000000000000000000000000000000000..45ab9faf9b2df19b69ad6f927b8d13a6346ddb0a
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/FUNDING.yml
@@ -0,0 +1,3 @@
+# These are supported funding model platforms
+
+patreon: Red_Devs
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/ISSUE_TEMPLATE.md b/testbed/Cog-Creators__Red-DiscordBot/.github/ISSUE_TEMPLATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5eacf103d3c203b9ea70559e687322d064ebf5e
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/ISSUE_TEMPLATE.md
@@ -0,0 +1,5 @@
+
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE.md b/testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..f019030049792309c4e6b6fde6097fe4145bdc11
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,17 @@
+### Description of the changes
+
+
+
+### Have the changes in this PR been tested?
+
+
+Yes
+No
+
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE/bugfix.md b/testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE/bugfix.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0215ce01a35d954aa69449d53edfa05618af1d7
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE/bugfix.md
@@ -0,0 +1,15 @@
+# Bugfix request
+
+
+
+#### Describe the bug being fixed
+
+
+
+#### Anything we need to know about this fix?
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE/release.md b/testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE/release.md
new file mode 100644
index 0000000000000000000000000000000000000000..371861627b81ec37586636b5853e3f8183809e4f
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE/release.md
@@ -0,0 +1,16 @@
+# New release
+
+
+
+#### Version
+
+
+
+#### Has a draft release been created for this?
+
+- [ ] Yes
+- [ ] No
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/labeler.yml b/testbed/Cog-Creators__Red-DiscordBot/.github/labeler.yml
new file mode 100644
index 0000000000000000000000000000000000000000..aa1a8b41cc90cb5dae42537a7b30a75d5382aad2
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/labeler.yml
@@ -0,0 +1,326 @@
+"Category: CI":
+ - .github/workflows/**/*
+
+
+"Category: Cogs - Admin":
+ # Source
+ - redbot/cogs/admin/*
+ # Docs
+ - docs/cog_guides/admin.rst
+ - docs/.resources/admin/**/*
+"Category: Cogs - Alias":
+ # Source
+ - redbot/cogs/alias/*
+ # Docs
+ - docs/cog_guides/alias.rst
+ # Tests
+ - redbot/pytest/alias.py
+ - tests/cogs/test_alias.py
+ - docs/.resources/alias/**/*
+"Category: Cogs - Audio":
+ # Source
+ - any:
+ - redbot/cogs/audio/**/*
+ - "!redbot/cogs/audio/**/locales/*"
+ # Docs
+ - docs/cog_guides/audio.rst
+"Category: Cogs - Bank": [] # historical label for a removed cog
+"Category: Cogs - Cleanup":
+ # Source
+ - redbot/cogs/cleanup/*
+ # Docs
+ - docs/cog_guides/cleanup.rst
+"Category: Cogs - CustomCommands":
+ # Source
+ - redbot/cogs/customcom/*
+ # Docs
+ - docs/cog_customcom.rst
+ - docs/cog_guides/customcommands.rst
+"Category: Cogs - Dev":
+ # Source
+ - redbot/core/dev_commands.py
+ # Docs
+ - docs/cog_guides/dev.rst
+"Category: Cogs - Downloader":
+ # Source
+ - redbot/cogs/downloader/*
+ # Docs
+ - docs/cog_guides/downloader.rst
+ # Tests
+ - redbot/pytest/downloader.py
+ - redbot/pytest/downloader_testrepo.*
+ - tests/cogs/downloader/**/*
+"Category: Cogs - Economy":
+ # Source
+ - redbot/cogs/economy/*
+ # Docs
+ - docs/cog_guides/economy.rst
+ # Tests
+ - redbot/pytest/economy.py
+ - tests/cogs/test_economy.py
+"Category: Cogs - Filter":
+ # Source
+ - redbot/cogs/filter/*
+ # Docs
+ - docs/cog_guides/filter.rst
+"Category: Cogs - General":
+ # Source
+ - redbot/cogs/general/*
+ # Docs
+ - docs/cog_guides/general.rst
+"Category: Cogs - Image":
+ # Source
+ - redbot/cogs/image/*
+ # Docs
+ - docs/cog_guides/image.rst
+"Category: Cogs - Mod":
+ # Source
+ - redbot/cogs/mod/*
+ # Docs
+ - docs/cog_guides/mod.rst
+ # Tests
+ - redbot/pytest/mod.py
+ - tests/cogs/test_mod.py
+"Category: Cogs - Modlog":
+ # Source
+ - redbot/cogs/modlog/*
+ # Docs
+ - docs/cog_guides/modlog.rst
+"Category: Cogs - Mutes":
+ # Source
+ - redbot/cogs/mutes/*
+ # Docs
+ - docs/cog_guides/mutes.rst
+"Category: Cogs - Permissions":
+ # Source
+ - redbot/cogs/permissions/*
+ # Docs
+ - docs/cog_guides/permissions.rst
+ - docs/cog_permissions.rst
+ # Tests
+ - redbot/pytest/permissions.py
+ - tests/cogs/test_permissions.py
+"Category: Cogs - Reports":
+ # Source
+ - redbot/cogs/reports/*
+ # Docs
+ - docs/cog_guides/reports.rst
+"Category: Cogs - Streams":
+ # Source
+ - redbot/cogs/streams/*
+ # Docs
+ - docs/cog_guides/streams.rst
+"Category: Cogs - Trivia":
+ # Source
+ - redbot/cogs/trivia/*
+ # Docs
+ - docs/cog_guides/trivia.rst
+ - docs/guide_trivia_list_creation.rst
+ - docs/.resources/trivia/**/*
+ # Tests
+ - tests/cogs/test_trivia.py
+"Category: Cogs - Trivia - Lists":
+ - redbot/cogs/trivia/data/lists/*
+"Category: Cogs - Warnings":
+ # Source
+ - redbot/cogs/warnings/*
+ # Docs
+ - docs/cog_guides/warnings.rst
+
+
+"Category: Core - API - Audio": [] # potential future feature
+"Category: Core - API - Bank":
+ # Source
+ - redbot/core/bank.py
+ # Docs
+ - docs/framework_bank.rst
+"Category: Core - API - App Commands Package":
+ # Source
+ - redbot/core/app_commands/*
+ # Tests
+ - tests/core/test_app_commands.py
+"Category: Core - API - Commands Package":
+ # Source
+ - any:
+ - redbot/core/commands/*
+ - "!redbot/core/commands/help.py"
+ # this isn't in commands package but it just re-exports things from it
+ - redbot/core/checks.py
+ # Docs
+ - docs/framework_checks.rst
+ - docs/framework_commands.rst
+ # Tests
+ - tests/core/test_commands.py
+"Category: Core - API - Config":
+ # Source
+ - any:
+ - redbot/core/drivers/**/*
+ - "!redbot/core/drivers/**/locales/*"
+ - redbot/core/config.py
+ # Docs
+ - docs/framework_config.rst
+ # Tests
+ - tests/core/test_config.py
+"Category: Core - API - Other":
+ # Source
+ - redbot/__init__.py
+ - redbot/core/__init__.py
+ - redbot/core/cog_manager.py # TODO: privatize cog manager module
+ - redbot/core/data_manager.py
+ - redbot/core/errors.py
+ - redbot/core/tree.py
+ # Docs
+ - docs/framework_cogmanager.rst # TODO: privatize cog manager module
+ - docs/framework_datamanager.rst
+ - docs/framework_tree.rst
+ # Tests
+ - redbot/pytest/cog_manager.py # TODO: privatize cog manager module
+ - redbot/pytest/data_manager.py
+ - tests/core/test_cog_manager.py
+ - tests/core/test_data_manager.py
+ - tests/core/test_version.py
+"Category: Core - API - Utils Package":
+ # Source
+ - any:
+ - redbot/core/utils/*
+ - "!redbot/core/utils/_internal_utils.py"
+ # Docs
+ - docs/framework_utils.rst
+ # Tests
+ - tests/core/test_utils.py
+"Category: Core - Bot Class":
+ # Source
+ - redbot/core/bot.py
+ # Docs
+ - docs/framework_apikeys.rst
+ - docs/framework_bot.rst
+"Category: Core - Bot Commands":
+ # Source
+ - redbot/core/core_commands.py
+ - redbot/core/_diagnoser.py
+ # Docs
+ - docs/.resources/cog_manager_ui/**/*
+ - docs/cog_guides/cog_manager_ui.rst
+ - docs/cog_guides/core.rst
+"Category: Core - Command-line Interfaces":
+ - redbot/__main__.py
+ - redbot/logging.py
+ - redbot/core/_debuginfo.py
+ - redbot/core/cli.py
+ - redbot/setup.py
+"Category: Core - Help":
+ - redbot/core/commands/help.py
+"Category: Core - i18n":
+ # Source
+ - redbot/core/i18n.py
+ # Locale files
+ - redbot/**/locales/*
+ # Docs
+ - docs/framework_i18n.rst
+"Category: Core - Modlog":
+ # Source
+ - redbot/core/generic_casetypes.py
+ - redbot/core/modlog.py
+ # Docs
+ - docs/framework_modlog.rst
+"Category: Core - Other Internals":
+ # Source
+ - redbot/core/_sharedlibdeprecation.py
+ - redbot/core/events.py
+ - redbot/core/global_checks.py
+ - redbot/core/settings_caches.py
+ - redbot/core/utils/_internal_utils.py
+ # Tests
+ - redbot/pytest/__init__.py
+ - redbot/pytest/core.py
+ - tests/core/test_installation.py
+"Category: Core - RPC/ZMQ":
+ # Source
+ - redbot/core/rpc.py
+ # Docs
+ - docs/framework_rpc.rst
+ # Tests
+ - redbot/pytest/rpc.py
+ - tests/core/test_rpc.py
+ - tests/rpc_test.html
+
+
+"Category: Docker": [] # potential future feature
+
+
+"Category: Docs - Changelogs":
+ - CHANGES.rst
+ - docs/changelog.rst
+"Category: Docs - For Developers":
+ - docs/framework_events.rst
+ - docs/guide_cog_creation.rst
+ - docs/guide_cog_creators.rst
+ - docs/guide_migration.rst
+ - docs/guide_publish_cogs.rst
+"Category: Docs - Install Guides":
+ - docs/about_venv.rst
+ - docs/autostart_*.rst
+ - docs/.resources/bot-guide/**/*
+ - docs/bot_application_guide.rst
+ - docs/install_guides/**/*
+ - docs/update_red.rst
+"Category: Docs - Other":
+ - docs/host-list.rst
+ - docs/index.rst
+ - docs/version_guarantees.rst
+ - README.md
+"Category: Docs - User Guides":
+ - docs/getting_started.rst
+ - docs/intents.rst
+ - docs/red_core_data_statement.rst
+ # TODO: move these to `docs/.resources/getting_started` subfolder
+ - docs/.resources/red-console.png
+ - docs/.resources/code-grant.png
+ - docs/.resources/instances-ssh-button.png
+ - docs/.resources/ssh-output.png
+
+
+"Category: Meta":
+ # top-level files
+ - any:
+ - '*'
+ - '!README.md'
+ - '!CHANGES.rst'
+ # .gitattributes files
+ - '**/.gitattributes'
+ # GitHub configuration files, with the exception of CI configuration
+ - .github/*
+ - .github/ISSUE_TEMPLATE/*
+ - .github/PULL_REQUEST_TEMPLATE/*
+ # documentation configuration, extensions, scripts, templates, etc.
+ - docs/conf.py
+ - docs/_ext/**/*
+ - docs/_html/**/*
+ - docs/make.bat
+ - docs/Makefile
+ - docs/prolog.txt
+ - docs/_templates/**/*
+ # empty file
+ - redbot/cogs/__init__.py
+ # can't go more meta than that :)
+ # TODO: remove this useless file
+ - redbot/meta.py
+ # py.typed file
+ - redbot/py.typed
+ # requirements files
+ - requirements/*
+ # schema files
+ - schema/*
+ # tests configuration, global fixtures, etc.
+ - tests/conftest.py
+ - tests/__init__.py
+ - tests/*/__init__.py
+ # repository tools
+ - tools/*
+
+
+# "Category: RPC/ZMQ methods": [] # can't be matched by file patterns
+
+
+"Category: Vendored Packages":
+ - redbot/vendored/**/*
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/crowdin_upload_strings.yml b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/crowdin_upload_strings.yml
new file mode 100644
index 0000000000000000000000000000000000000000..f476ec9166d6184c7d0408111b71266c7013c4b2
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/crowdin_upload_strings.yml
@@ -0,0 +1,32 @@
+name: Crowdin - Upload strings
+on:
+ push:
+ branches:
+ - V3/develop
+
+jobs:
+ deploy:
+ if: github.repository == 'Cog-Creators/Red-DiscordBot'
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - name: Set up Python
+ uses: actions/setup-python@v4
+ with:
+ python-version: '3.8'
+ - name: Install dependencies
+ run: |
+ curl https://artifacts.crowdin.com/repo/GPG-KEY-crowdin | sudo apt-key add -
+ echo "deb https://artifacts.crowdin.com/repo/deb/ /" | sudo tee -a /etc/apt/sources.list
+ sudo apt-get update -qq
+ sudo apt-get install -y crowdin
+ pip install redgettext==3.4.2
+ - name: Generate source files
+ run: |
+ make gettext
+ - name: Upload source files
+ run: |
+ make upload_translations
+ env:
+ CROWDIN_API_KEY: ${{ secrets.crowdin_token}}
+ CROWDIN_PROJECT_ID: ${{ secrets.crowdin_identifier }}
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/prepare_release.yml b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/prepare_release.yml
new file mode 100644
index 0000000000000000000000000000000000000000..d4be0f2152740b5ae8c3d41a540e180ee1a3b0ba
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/prepare_release.yml
@@ -0,0 +1,130 @@
+name: Prepare Release
+on:
+ workflow_dispatch:
+ inputs:
+ new_stable_version:
+ description: Version number for the new stable release (leave empty to just strip `.dev1`)
+ required: false
+ default: 'auto'
+
+permissions:
+ contents: write
+ pull-requests: write
+
+jobs:
+ crowdin_download_translations:
+ needs: pr_stable_bump
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v3
+ - name: Set up Python
+ uses: actions/setup-python@v4
+ with:
+ python-version: '3.8'
+ - name: Install dependencies
+ run: |
+ curl https://artifacts.crowdin.com/repo/GPG-KEY-crowdin | sudo apt-key add -
+ echo "deb https://artifacts.crowdin.com/repo/deb/ /" | sudo tee -a /etc/apt/sources.list
+ sudo apt-get update -qq
+ sudo apt-get install -y crowdin
+ pip install redgettext==3.4.2
+
+ - name: Generate source files
+ run: |
+ make gettext
+ - name: Download translations
+ run: |
+ make download_translations
+ env:
+ CROWDIN_API_KEY: ${{ secrets.crowdin_token}}
+ CROWDIN_PROJECT_ID: ${{ secrets.crowdin_identifier }}
+
+ - name: Create Pull Request
+ id: cpr_crowdin
+ uses: peter-evans/create-pull-request@v4
+ with:
+ token: ${{ secrets.GITHUB_TOKEN }}
+ commit-message: Automated Crowdin downstream
+ title: "[i18n] Automated Crowdin downstream"
+ body: |
+ This is an automated PR that is part of Prepare Release automated workflow (2 out of 2).
+ Please ensure that there are no errors or invalid files are in the PR.
+ labels: "Automated PR, Category: i18n, Changelog Entry: Skipped"
+ branch: "automated/i18n"
+ author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
+ milestone: ${{ needs.pr_stable_bump.outputs.milestone_number }}
+
+ - name: Close and reopen the PR with different token to trigger CI
+ uses: actions/github-script@v6
+ env:
+ PR_NUMBER: ${{ steps.cpr_crowdin.outputs.pull-request-number }}
+ PR_OPERATION: ${{ steps.cpr_crowdin.outputs.pull-request-operation }}
+ with:
+ github-token: ${{ secrets.cogcreators_bot_repo_scoped }}
+ script: |
+ const script = require(
+ `${process.env.GITHUB_WORKSPACE}/.github/workflows/scripts/close_and_reopen_pr.js`
+ );
+ console.log(script({github, context}));
+
+ pr_stable_bump:
+ runs-on: ubuntu-latest
+ outputs:
+ milestone_number: ${{ steps.get_milestone_number.outputs.result }}
+ steps:
+ # Checkout repository and install Python
+ - uses: actions/checkout@v3
+ - name: Set up Python
+ uses: actions/setup-python@v4
+ with:
+ python-version: '3.8'
+
+ # Create PR for stable version bump
+ - name: Update Red version number from input
+ id: bump_version_stable
+ run: |
+ python .github/workflows/scripts/bump_version.py
+ env:
+ PYTHONPATH: ${{ github.workspace }}:${{ env.PYTHONPATH }}
+ NEW_STABLE_VERSION: ${{ github.event.inputs.new_stable_version }}
+
+ # Get milestone number of the milestone for the new stable version
+ - name: Get milestone number
+ id: get_milestone_number
+ uses: actions/github-script@v6
+ env:
+ MILESTONE_TITLE: ${{ steps.bump_version_stable.outputs.new_version }}
+ with:
+ script: |
+ const script = require(
+ `${process.env.GITHUB_WORKSPACE}/.github/workflows/scripts/get_milestone_number_by_exact_title.js`
+ );
+ return await script({github, context});
+
+ - name: Create Pull Request
+ id: cpr_bump_stable
+ uses: peter-evans/create-pull-request@v4
+ with:
+ token: ${{ secrets.GITHUB_TOKEN }}
+ commit-message: Version bump to ${{ steps.bump_version_stable.outputs.new_version }}
+ title: Version bump to ${{ steps.bump_version_stable.outputs.new_version }}
+ body: |
+ This is an automated PR that is part of Prepare Release automated workflow (1 out of 2).
+ Please ensure that there are no errors or invalid files are in the PR.
+ labels: "Automated PR, Changelog Entry: Skipped"
+ branch: "automated/pr_bumps/${{ steps.bump_version_stable.outputs.new_version }}"
+ author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
+ milestone: ${{ steps.get_milestone_number.outputs.result }}
+
+ - name: Close and reopen the PR with different token to trigger CI
+ uses: actions/github-script@v6
+ env:
+ PR_NUMBER: ${{ steps.cpr_bump_stable.outputs.pull-request-number }}
+ PR_OPERATION: ${{ steps.cpr_bump_stable.outputs.pull-request-operation }}
+ with:
+ github-token: ${{ secrets.cogcreators_bot_repo_scoped }}
+ script: |
+ const script = require(
+ `${process.env.GITHUB_WORKSPACE}/.github/workflows/scripts/close_and_reopen_pr.js`
+ );
+ console.log(await script({github, context}));
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/run_pip_compile.yaml b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/run_pip_compile.yaml
new file mode 100644
index 0000000000000000000000000000000000000000..47a47083fa168a6bc74934dc51a24c77de63bcb3
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/run_pip_compile.yaml
@@ -0,0 +1,84 @@
+name: Generate requirements files with pip-compile.
+
+on:
+ workflow_dispatch:
+
+jobs:
+ generate_requirements:
+ name: Generate requirements files for ${{ matrix.os }} platform.
+ runs-on: ${{ matrix.os }}
+ strategy:
+ matrix:
+ os:
+ - ubuntu-latest
+ - windows-latest
+ - macos-latest
+ steps:
+ - name: Checkout the repository.
+ uses: actions/checkout@v3
+
+ - name: Set up Python 3.8.
+ uses: actions/setup-python@v4
+ with:
+ python-version: '3.8'
+
+ - name: Install dependencies
+ run: |
+ python -m pip install -U pip
+ python -m pip install -U pip-tools
+
+ - name: Generate requirements files.
+ id: compile_requirements
+ run: |
+ python .github/workflows/scripts/compile_requirements.py
+
+ - name: Upload requirements files.
+ uses: actions/upload-artifact@v3
+ with:
+ name: ${{ steps.compile_requirements.outputs.sys_platform }}
+ path: requirements/${{ steps.compile_requirements.outputs.sys_platform }}-*.txt
+
+ merge_requirements:
+ name: Merge requirements files.
+ needs: generate_requirements
+ runs-on: ubuntu-latest
+ steps:
+ - name: Checkout the repository.
+ uses: actions/checkout@v3
+
+ - name: Set up Python 3.8.
+ uses: actions/setup-python@v4
+ with:
+ python-version: '3.8'
+
+ - name: Install dependencies
+ run: |
+ python -m pip install -U "packaging>=22.0"
+
+ - name: Download Windows requirements.
+ uses: actions/download-artifact@v3
+ with:
+ name: win32
+ path: requirements
+ - name: Download Linux requirements.
+ uses: actions/download-artifact@v3
+ with:
+ name: linux
+ path: requirements
+ - name: Download macOS requirements.
+ uses: actions/download-artifact@v3
+ with:
+ name: darwin
+ path: requirements
+
+ - name: Merge requirements files.
+ run: |
+ python .github/workflows/scripts/merge_requirements.py
+
+ - name: Upload merged requirements files.
+ uses: actions/upload-artifact@v3
+ with:
+ name: merged
+ path: |
+ requirements/base.txt
+ requirements/extra-*.txt
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/scripts/check_label_pattern_exhaustiveness.py b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/scripts/check_label_pattern_exhaustiveness.py
new file mode 100644
index 0000000000000000000000000000000000000000..1982b0b693618faa7d270277490e88a4bb81da65
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/scripts/check_label_pattern_exhaustiveness.py
@@ -0,0 +1,215 @@
+import itertools
+import operator
+import os
+import subprocess
+from pathlib import Path
+from typing import Any, Dict, Iterable, List, Optional
+from typing_extensions import Self
+
+import rich
+import yaml
+from rich.console import Console, ConsoleOptions, RenderResult
+from rich.tree import Tree
+from pathspec import PathSpec
+from pathspec.patterns.gitwildmatch import GitWildMatchPattern
+
+
+ROOT_PATH = Path(__file__).resolve().parents[3]
+
+
+class Matcher:
+ def __init__(self, *, any: Iterable[str] = (), all: Iterable[str] = ()) -> None:
+ self.any_patterns = tuple(any)
+ self.any_specs = self._get_pathspecs(self.any_patterns)
+ self.all_patterns = tuple(all)
+ self.all_specs = self._get_pathspecs(self.all_patterns)
+
+ def __repr__(self) -> str:
+ return f"Matcher(any={self.any_patterns!r}, all={self.all_patterns!r})"
+
+ def __eq__(self, other: Any) -> bool:
+ if isinstance(other, self.__class__):
+ return (
+ self.any_patterns == other.any_patterns and self.all_patterns == other.all_patterns
+ )
+ return NotImplemented
+
+ def __hash__(self) -> int:
+ return hash((self.any_patterns, self.all_patterns))
+
+ @classmethod
+ def _get_pathspecs(cls, patterns: Iterable[str]) -> List[PathSpec]:
+ return tuple(
+ PathSpec.from_lines(GitWildMatchPattern, cls._get_pattern_lines(pattern))
+ for pattern in patterns
+ )
+
+ @staticmethod
+ def _get_pattern_lines(pattern: str) -> List[str]:
+ # an approximation of actions/labeler's minimatch globs
+ if pattern.startswith("!"):
+ pattern_lines = ["*", f"!/{pattern[1:]}"]
+ else:
+ pattern_lines = [f"/{pattern}"]
+ if pattern.endswith("*") and "**" not in pattern:
+ pattern_lines.append(f"!/{pattern}/")
+ return pattern_lines
+
+ @classmethod
+ def get_label_matchers(cls) -> Dict[str, List[Self]]:
+ with open(ROOT_PATH / ".github/labeler.yml", encoding="utf-8") as fp:
+ label_definitions = yaml.safe_load(fp)
+ label_matchers: Dict[str, List[Matcher]] = {}
+ for label_name, matcher_definitions in label_definitions.items():
+ matchers = label_matchers[label_name] = []
+ for idx, matcher_data in enumerate(matcher_definitions):
+ if isinstance(matcher_data, str):
+ matchers.append(cls(any=[matcher_data]))
+ elif isinstance(matcher_data, dict):
+ matchers.append(
+ cls(any=matcher_data.pop("any", []), all=matcher_data.pop("all", []))
+ )
+ if matcher_data:
+ raise RuntimeError(
+ f"Unexpected keys at index {idx} for label {label_name!r}: "
+ + ", ".join(map(repr, matcher_data))
+ )
+ elif matcher_data is not None:
+ raise RuntimeError(f"Unexpected type at index {idx} for label {label_name!r}")
+
+ return label_matchers
+
+
+class PathNode:
+ def __init__(self, parent_tree: Tree, path: Path, *, label: Optional[str] = None) -> None:
+ self.parent_tree = parent_tree
+ self.path = path
+ self.label = label
+
+ def __rich__(self) -> str:
+ if self.label is not None:
+ return self.label
+ return self.path.name
+
+
+class DirectoryTree:
+ def __init__(self, label: str) -> None:
+ self.root = Tree(PathNode(Tree(""), Path(), label=label))
+ self._previous = self.root
+
+ def __bool__(self) -> bool:
+ return bool(self.root.children)
+
+ def __rich_console__(self, console: Console, options: ConsoleOptions) -> RenderResult:
+ yield from self.root.__rich_console__(console, options)
+
+ def add(self, file: Path) -> Tree:
+ common_path = Path(os.path.commonpath([file.parent, self._previous.label.path]))
+
+ parent_tree = self._previous
+ while parent_tree != self.root and parent_tree.label.path != common_path:
+ parent_tree = parent_tree.label.parent_tree
+
+ for part in file.relative_to(common_path).parts:
+ if parent_tree.label.path.name == "locales":
+ if not parent_tree.children:
+ parent_tree.add(PathNode(parent_tree, parent_tree.label.path / "*.po"))
+ continue
+ parent_tree = parent_tree.add(PathNode(parent_tree, parent_tree.label.path / part))
+
+ self._previous = parent_tree
+ return parent_tree
+
+
+class App:
+ def __init__(self) -> None:
+ self.exit_code = 0
+ self.label_matchers = Matcher.get_label_matchers()
+ self.tracked_files = [
+ Path(filename)
+ for filename in subprocess.check_output(
+ ("git", "ls-tree", "-r", "HEAD", "--name-only"), encoding="utf-8", cwd=ROOT_PATH
+ ).splitlines()
+ ]
+ self.matches_per_label = {label_name: set() for label_name in self.label_matchers}
+ self.matches_per_file = []
+ self.used_matchers = set()
+
+ def run(self) -> int:
+ old_cwd = os.getcwd()
+ try:
+ os.chdir(ROOT_PATH)
+ self._run()
+ finally:
+ os.chdir(old_cwd)
+ return self.exit_code
+
+ def _run(self) -> None:
+ self._collect_match_information()
+ self._show_matches_per_label()
+ self._show_files_without_labels()
+ self._show_files_with_multiple_labels()
+ self._show_unused_matchers()
+
+ def _collect_match_information(self) -> None:
+ tmp_matches_per_file = {file: [] for file in self.tracked_files}
+
+ for file in self.tracked_files:
+ for label_name, matchers in self.label_matchers.items():
+ matched = False
+ for matcher in matchers:
+ if all(
+ path_spec.match_file(file)
+ for path_spec in itertools.chain(matcher.all_specs, matcher.any_specs)
+ ):
+ self.matches_per_label[label_name].add(file)
+ matched = True
+ self.used_matchers.add(matcher)
+ if matched:
+ tmp_matches_per_file[file].append(label_name)
+
+ self.matches_per_file = sorted(tmp_matches_per_file.items(), key=operator.itemgetter(0))
+
+ def _show_matches_per_label(self) -> None:
+ for label_name, files in self.matches_per_label.items():
+ top_tree = DirectoryTree(f"{label_name}:")
+ for file in sorted(files):
+ top_tree.add(file)
+ rich.print(top_tree)
+ print()
+
+ def _show_files_without_labels(self) -> None:
+ top_tree = DirectoryTree("\n--- Not matched ---")
+ for file, labels in self.matches_per_file:
+ if not labels:
+ top_tree.add(file)
+ if top_tree:
+ self.exit_code = 1
+ rich.print(top_tree)
+ else:
+ print("--- All files match at least one label's patterns ---")
+
+ def _show_files_with_multiple_labels(self) -> None:
+ top_tree = DirectoryTree("\n--- Matched by more than one label ---")
+ for file, labels in self.matches_per_file:
+ if len(labels) > 1:
+ tree = top_tree.add(file)
+ for label_name in labels:
+ tree.add(label_name)
+ if top_tree:
+ rich.print(top_tree)
+ else:
+ print("--- None of the files are matched by more than one label's patterns ---")
+
+ def _show_unused_matchers(self) -> None:
+ for label_name, matchers in self.label_matchers.items():
+ for idx, matcher in enumerate(matchers):
+ if matcher not in self.used_matchers:
+ print(
+ f"--- Matcher {idx} for label {label_name!r} does not match any files! ---"
+ )
+ self.exit_code = 1
+
+
+if __name__ == "__main__":
+ raise SystemExit(App().run())
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/scripts/get_milestone_number_by_exact_title.js b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/scripts/get_milestone_number_by_exact_title.js
new file mode 100644
index 0000000000000000000000000000000000000000..b7d734b5dd5338cb32abb9c919120159719c886a
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/scripts/get_milestone_number_by_exact_title.js
@@ -0,0 +1,49 @@
+module.exports = (async function ({github, context}) {
+ const milestone_title = process.env.MILESTONE_TITLE;
+ const [repo_owner, repo_name] = process.env.GITHUB_REPOSITORY.split('/');
+
+ const {
+ repository: {
+ milestones: {
+ nodes: milestones,
+ pageInfo: {hasNextPage}
+ }
+ }
+ } = await github.graphql({
+ query: `
+ query getMilestoneNumberByTitle(
+ $repo_owner: String!
+ $repo_name: String!
+ $milestone_title: String!
+ ) {
+ repository(owner:$repo_owner name:$repo_name) {
+ milestones(query:$milestone_title states:OPEN first:100) {
+ nodes {
+ number
+ title
+ }
+ pageInfo {
+ hasNextPage
+ }
+ }
+ }
+ }`,
+ repo_owner: repo_owner,
+ repo_name: repo_name,
+ milestone_title: milestone_title,
+ });
+
+ if (hasNextPage) {
+ // this should realistically never happen so let's just error
+ core.setFailed('Impossible happened! :)');
+ return;
+ }
+
+ for (const milestone of milestones)
+ if (milestone.title === milestone_title)
+ return milestone.number;
+
+ // if no exact match is found, assume the milestone doesn't exist
+ console.log('The milestone was not found. API returned the array: %o', milestones);
+ return null;
+})
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/scripts/merge_requirements.py b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/scripts/merge_requirements.py
new file mode 100644
index 0000000000000000000000000000000000000000..4ad2822b207759d4fd99c5fe75b8faa396899717
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/scripts/merge_requirements.py
@@ -0,0 +1,134 @@
+import os
+from pathlib import Path
+from typing import List, TextIO
+
+from packaging.markers import Marker
+from packaging.requirements import Requirement
+
+
+REQUIREMENTS_FOLDER = Path(__file__).parents[3].absolute() / "requirements"
+os.chdir(REQUIREMENTS_FOLDER)
+
+
+class RequirementData:
+ def __init__(self, requirement_string: str) -> None:
+ self.req = Requirement(requirement_string)
+ self.comments = set()
+
+ @property
+ def name(self) -> str:
+ return self.req.name
+
+ @property
+ def marker(self) -> Marker:
+ return self.req.marker
+
+ @marker.setter
+ def marker(self, value: Marker) -> None:
+ self.req.marker = value
+
+
+def get_requirements(fp: TextIO) -> List[RequirementData]:
+ requirements = []
+
+ current = None
+ for line in fp.read().splitlines():
+ annotation_prefix = " # "
+ if line.startswith(annotation_prefix) and current is not None:
+ source = line[len(annotation_prefix) :].strip()
+ if source == "via":
+ continue
+ via_prefix = "via "
+ if source.startswith(via_prefix):
+ source = source[len(via_prefix) :]
+ current.comments.add(source)
+ elif line and not line.startswith(("#", " ")):
+ current = RequirementData(line)
+ requirements.append(current)
+
+ return requirements
+
+
+names = ["base"]
+names.extend(file.stem for file in REQUIREMENTS_FOLDER.glob("extra-*.in"))
+base_requirements = []
+
+for name in names:
+ # {req_name: {sys_platform: RequirementData}
+ input_data = {}
+ all_platforms = set()
+ for file in REQUIREMENTS_FOLDER.glob(f"*-{name}.txt"):
+ platform_name = file.stem.split("-", maxsplit=1)[0]
+ all_platforms.add(platform_name)
+ with file.open(encoding="utf-8") as fp:
+ requirements = get_requirements(fp)
+
+ for req in requirements:
+ platforms = input_data.setdefault(req.name, {})
+ platforms[platform_name] = req
+
+ output = base_requirements if name == "base" else []
+ for req_name, platforms in input_data.items():
+ req = next(iter(platforms.values()))
+ for other_req in platforms.values():
+ if req.req != other_req.req:
+ raise RuntimeError(f"Incompatible requirements for {req_name}.")
+
+ req.comments.update(other_req.comments)
+
+ base_req = next(
+ (base_req for base_req in base_requirements if base_req.name == req.name), None
+ )
+ if base_req is not None:
+ old_base_marker = base_req.marker
+ old_req_marker = req.marker
+ req.marker = base_req.marker = None
+ if base_req.req != req.req:
+ raise RuntimeError(f"Incompatible requirements for {req_name}.")
+
+ base_req.marker = old_base_marker
+ req.marker = old_req_marker
+ if base_req.marker is None or base_req.marker == req.marker:
+ continue
+
+ if len(platforms) == len(all_platforms):
+ output.append(req)
+ continue
+ elif len(platforms) < len(all_platforms - platforms.keys()):
+ platform_marker = " or ".join(
+ f"sys_platform == '{platform}'" for platform in platforms
+ )
+ else:
+ platform_marker = " and ".join(
+ f"sys_platform != '{platform}'" for platform in all_platforms - platforms.keys()
+ )
+
+ new_marker = (
+ f"({req.marker}) and ({platform_marker})"
+ if req.marker is not None
+ else platform_marker
+ )
+ req.marker = Marker(new_marker)
+ if base_req is not None and base_req.marker == req.marker:
+ continue
+
+ output.append(req)
+
+ output.sort(key=lambda req: (req.marker is not None, req.name))
+ with open(f"{name}.txt", "w+", encoding="utf-8") as fp:
+ for req in output:
+ fp.write(str(req.req))
+ fp.write("\n")
+ comments = sorted(req.comments)
+
+ if len(comments) == 1:
+ source = comments[0]
+ fp.write(" # via ")
+ fp.write(source)
+ fp.write("\n")
+ else:
+ fp.write(" # via\n")
+ for source in comments:
+ fp.write(" # ")
+ fp.write(source)
+ fp.write("\n")
diff --git a/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/tests.yml b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/tests.yml
new file mode 100644
index 0000000000000000000000000000000000000000..3ce7319283b6bdb170e06efdd8f267f28e7a1bcb
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/.github/workflows/tests.yml
@@ -0,0 +1,107 @@
+name: Tests
+on:
+ pull_request:
+ push:
+ repository_dispatch:
+ types:
+ - dispatched_test
+
+env:
+ ref: ${{ github.event.client_payload.ref || '' }}
+
+jobs:
+ tox:
+ runs-on: ubuntu-latest
+ strategy:
+ matrix:
+ python_version:
+ - "3.8"
+ tox_env:
+ - style
+ - docs
+ include:
+ - tox_env: py38
+ python_version: "3.8"
+ friendly_name: Python 3.8 - Tests
+ - tox_env: py39
+ python_version: "3.9"
+ friendly_name: Python 3.9 - Tests
+ - tox_env: py310
+ python_version: "3.10"
+ friendly_name: Python 3.10 - Tests
+ - tox_env: py311
+ python_version: "3.11"
+ friendly_name: Python 3.11 - Tests
+ - tox_env: style
+ friendly_name: Style
+ - tox_env: docs
+ friendly_name: Docs
+ fail-fast: false
+ name: Tox - ${{ matrix.friendly_name }}
+ steps:
+ - uses: actions/checkout@v3
+ with:
+ ref: ${{ env.ref }}
+ - name: Set up Python
+ uses: actions/setup-python@v4
+ with:
+ python-version: ${{ matrix.python_version }}
+ - name: Install tox
+ run: |
+ python -m pip install --upgrade pip
+ pip install tox
+ - name: Tox test
+ env:
+ TOXENV: ${{ matrix.tox_env }}
+ run: tox
+
+ tox-postgres:
+ runs-on: ubuntu-latest
+ strategy:
+ matrix:
+ python_version:
+ - "3.8"
+ - "3.9"
+ - "3.10"
+ - "3.11"
+ fail-fast: false
+ name: Tox - Postgres
+ services:
+ postgresql:
+ image: postgres:10
+ ports:
+ - 5432:5432
+ env:
+ POSTGRES_DB: red_db
+ POSTGRES_PASSWORD: postgres
+ POSTGRES_USER: postgres
+ steps:
+ - uses: actions/checkout@v3
+ with:
+ ref: ${{ env.ref }}
+ - name: Set up Python
+ uses: actions/setup-python@v4
+ with:
+ python-version: ${{ matrix.python_version }}
+ - name: Install tox
+ run: |
+ python -m pip install --upgrade pip
+ pip install tox
+ - name: Tox test
+ env:
+ TOXENV: postgres
+ PGDATABASE: red_db
+ PGUSER: postgres
+ PGPASSWORD: postgres
+ PGPORT: 5432
+ run: tox
+ - name: Verify no errors in PostgreSQL logs.
+ run: |
+ logs="$(docker logs "${{ job.services.postgresql.id }}" 2>&1)"
+ echo "---- PostgreSQL logs ----"
+ echo "$logs"
+ echo "---- PostgreSQL logs ----"
+ error_count="$(echo "$logs" | { grep -c 'ERROR: ' || true; })"
+ if [[ $error_count -gt 0 ]]; then
+ exit 1
+ fi
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/Makefile b/testbed/Cog-Creators__Red-DiscordBot/docs/Makefile
new file mode 100644
index 0000000000000000000000000000000000000000..a192210bed9943fd980dfddcca386df6a97bb3b2
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/Makefile
@@ -0,0 +1,20 @@
+# Minimal makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line.
+SPHINXOPTS =
+SPHINXBUILD = python3 -msphinx
+SPHINXPROJ = Red-DiscordBot
+SOURCEDIR = .
+BUILDDIR = _build
+
+# Put it first so that "make" without argument is like "make help".
+help:
+ @$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
+
+.PHONY: help Makefile
+
+# Catch-all target: route all unknown targets to Sphinx using the new
+# "make mode" option. $(O) is meant as a shortcut for $(SPHINXOPTS).
+%: Makefile
+ @$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/_ext/deprecated_removed.py b/testbed/Cog-Creators__Red-DiscordBot/docs/_ext/deprecated_removed.py
new file mode 100644
index 0000000000000000000000000000000000000000..b1488eef19d1d23ee2fe0964309c9246791e96cd
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/_ext/deprecated_removed.py
@@ -0,0 +1,129 @@
+"""
+A Sphinx extension adding a ``deprecated-removed`` directive that works
+similarly to CPython's directive with the same name.
+
+The key difference is that instead of passing the version of planned removal,
+the writer must provide the minimum amount of days that must pass
+since the date of the release it was deprecated in.
+
+Due to lack of a concrete release schedule for Red, this ensures that
+we give enough time to people affected by the changes no matter
+when the releases actually happen.
+
+`DeprecatedRemoved` class is heavily based on
+`sphinx.domains.changeset.VersionChange` class that is available at:
+https://github.com/sphinx-doc/sphinx/blob/0949735210abaa05b6448e531984f159403053f4/sphinx/domains/changeset.py
+
+Copyright 2007-2020 by the Sphinx team, see AUTHORS:
+https://github.com/sphinx-doc/sphinx/blob/82f495fed386c798735adf675f867b95d61ee0e1/AUTHORS
+
+The original copy was distributed under BSD License and this derivative work
+is distributed under GNU GPL Version 3.
+"""
+
+import datetime
+import multiprocessing
+import subprocess
+from typing import Any, Dict, List, Optional
+
+from docutils import nodes
+from sphinx import addnodes
+from sphinx.application import Sphinx
+from sphinx.util.docutils import SphinxDirective
+
+
+class TagDateCache:
+ def __init__(self) -> None:
+ self._tags: Dict[str, datetime.date] = {}
+
+ def _populate_tags(self) -> None:
+ with _LOCK:
+ if self._tags:
+ return
+ out = subprocess.check_output(
+ ("git", "tag", "-l", "--format", "%(creatordate:raw)\t%(refname:short)"),
+ text=True,
+ )
+ lines = out.splitlines(False)
+ for line in lines:
+ creator_date, tag_name = line.split("\t", maxsplit=1)
+ timestamp = int(creator_date.split(" ", maxsplit=1)[0])
+ self._tags[tag_name] = datetime.datetime.fromtimestamp(
+ timestamp, tz=datetime.timezone.utc
+ ).date()
+
+ def get_tag_date(self, tag_name: str) -> Optional[datetime.date]:
+ self._populate_tags()
+ return self._tags.get(tag_name)
+
+
+_LOCK = multiprocessing.Manager().Lock()
+_TAGS = TagDateCache()
+
+
+class DeprecatedRemoved(SphinxDirective):
+ has_content = True
+ required_arguments = 2
+ optional_arguments = 1
+ final_argument_whitespace = True
+
+ def run(self) -> List[nodes.Node]:
+ # Some Sphinx stuff
+ node = addnodes.versionmodified()
+ node.document = self.state.document
+ self.set_source_info(node)
+ node["type"] = self.name
+ node["version"] = tuple(self.arguments)
+ if len(self.arguments) == 3:
+ inodes, messages = self.state.inline_text(self.arguments[2], self.lineno + 1)
+ para = nodes.paragraph(self.arguments[2], "", *inodes, translatable=False)
+ self.set_source_info(para)
+ node.append(para)
+ else:
+ messages = []
+
+ # Text generation
+ deprecation_version = self.arguments[0]
+ minimum_days = int(self.arguments[1])
+ tag_date = _TAGS.get_tag_date(deprecation_version)
+ text = (
+ f"Will be deprecated in version {deprecation_version},"
+ " and removed in the first minor version that gets released"
+ f" after {minimum_days} days since deprecation"
+ if tag_date is None
+ else f"Deprecated since version {deprecation_version},"
+ " will be removed in the first minor version that gets released"
+ f" after {tag_date + datetime.timedelta(days=minimum_days)}"
+ )
+
+ # More Sphinx stuff
+ if self.content:
+ self.state.nested_parse(self.content, self.content_offset, node)
+ classes = ["versionmodified"]
+ if len(node):
+ if isinstance(node[0], nodes.paragraph) and node[0].rawsource:
+ content = nodes.inline(node[0].rawsource, translatable=True)
+ content.source = node[0].source
+ content.line = node[0].line
+ content += node[0].children
+ node[0].replace_self(nodes.paragraph("", "", content, translatable=False))
+
+ node[0].insert(0, nodes.inline("", f"{text}: ", classes=classes))
+ else:
+ para = nodes.paragraph(
+ "", "", nodes.inline("", f"{text}.", classes=classes), translatable=False
+ )
+ node.append(para)
+
+ ret = [node]
+ ret += messages
+
+ return ret
+
+
+def setup(app: Sphinx) -> Dict[str, Any]:
+ app.add_directive("deprecated-removed", DeprecatedRemoved)
+ return {
+ "version": "1.0",
+ "parallel_read_safe": True,
+ }
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/_html/robots.txt b/testbed/Cog-Creators__Red-DiscordBot/docs/_html/robots.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9d253d1bbd6cc10e104cb26db893050b63123a23
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/_html/robots.txt
@@ -0,0 +1,6 @@
+User-agent: *
+Disallow: /
+Allow: /en/stable
+Allow: /en/latest
+
+Sitemap: https://docs.discord.red/sitemap.xml
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/_templates/layout.html b/testbed/Cog-Creators__Red-DiscordBot/docs/_templates/layout.html
new file mode 100644
index 0000000000000000000000000000000000000000..996058f31020000ee8ed083cd242dd38c596ba01
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/_templates/layout.html
@@ -0,0 +1,18 @@
+{% extends '!layout.html' %}
+{% block document %}
+{% if version_slug == 'latest' %}
+
+{% endif %}
+{{ super() }}
+
+
+
+{% endblock %}
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/about_venv.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/about_venv.rst
new file mode 100644
index 0000000000000000000000000000000000000000..1b10c0fc02d7dcd1170039a15772187e15f8f2d9
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/about_venv.rst
@@ -0,0 +1,39 @@
+.. _about-venvs:
+
+==========================
+About Virtual Environments
+==========================
+Creating a virtual environment is really easy and usually prevents many common installation
+problems.
+
+**What Are Virtual Environments For?**
+
+Virtual environments allow you to isolate Red's library dependencies, cog dependencies and python
+binaries from the rest of your system. There is no performance overhead to using virtual environment
+and it saves you from a lot of troubles during setup. It also makes sure Red and its dependencies
+are installed to a predictable location which makes uninstalling Red as simple as removing a single folder,
+without worrying about losing your data or other things on your system becoming broken.
+
+
+--------------------------------------------
+Virtual Environments with Multiple Instances
+--------------------------------------------
+If you are running multiple instances of Red on the same machine, you have the option of either
+using the same virtual environment for all of them, or creating separate ones.
+
+.. note::
+
+ This only applies for multiple instances of V3. If you are running a V2 instance as well,
+ you **must** use separate virtual environments.
+
+The advantages of using a *single* virtual environment for all of your V3 instances are:
+
+- When updating Red, you will only need to update it once for all instances (however you will still need to restart all instances for the changes to take effect)
+- It will save space on your hard drive
+
+On the other hand, you may wish to update each of your instances individually.
+
+.. important::
+
+ Windows users with multiple instances should create *separate* virtual environments, as
+ updating multiple running instances at once is likely to cause errors.
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/autostart_mac.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/autostart_mac.rst
new file mode 100644
index 0000000000000000000000000000000000000000..4a6b7cc71b437b55d9070baa573175231ac00221
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/autostart_mac.rst
@@ -0,0 +1,110 @@
+.. launchd guide
+
+==============================
+Setting up auto-restart on Mac
+==============================
+
+-----------------------
+Creating the plist file
+-----------------------
+
+Start by activating your venv. Then run the following command:
+
+.. code-block:: none
+
+ which python
+
+Copy the output of that command.
+
+Now run :code:`sudo nano /Library/LaunchDaemons/red.plist`
+
+Paste the following and replace the following:
+
+- :code:`username` (but not :code:`UserName`) with your Mac username
+- :code:`path` with the path you copied earlier
+- :code:`instance-name` with your instance name:
+
+.. code-block:: none
+ :emphasize-lines: 9, 13, 28
+
+
+
+
+
+ Label
+ red
+ ProgramArguments
+
+ path
+ -O
+ -m
+ redbot
+ instance-name
+ --no-prompt
+
+ RunAtLoad
+
+ KeepAlive
+
+ SuccessfulExit
+
+
+ StandardOutPath
+ /tmp/red_out.log
+ StandardErrorPath
+ /tmp/red_err.log
+ UserName
+ username
+ InitGroups
+
+
+
+
+.. note::
+
+ You may add any additional arguments you need to add to the :code:`redbot` command by
+ adding them to the end of the array under :code:`ProgramArguments`
+
+.. note::
+
+ Should you need to set up auto-restart for additional bots, create a :code:`.plist` file for
+ each bot under a different file name, and use the respective file names for the commands below.
+
+Save and exit :code:`ctrl + O; enter; ctrl + x`
+
+-------------------------------
+Starting and loading the plist
+-------------------------------
+
+To start the bot and set it to start on boot, you must run the following command:
+
+.. prompt:: bash
+
+ sudo launchctl load -w /Library/LaunchDaemons/red.plist
+
+If you need to shutdown the bot, you can use the ``[p]shutdown`` command or
+type the following command in the terminal:
+
+.. prompt:: bash
+
+ sudo launchctl stop red
+
+To start the bot again after a shutdown, run the following:
+
+.. prompt:: bash
+
+ sudo launchctl start red
+
+To stop the bot and set it to not start on boot anymore, run the following:
+
+.. prompt:: bash
+
+ sudo launchctl unload -w /Library/LaunchDaemons/red.plist
+
+To view Red's log, run the following (:code:`red_out.log` is for the console output, and
+:code:`red_err.log` for the error logs):
+
+.. prompt:: bash
+
+ nano /tmp/red_out.log
+ nano /tmp/red_err.log
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/autostart_systemd.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/autostart_systemd.rst
new file mode 100644
index 0000000000000000000000000000000000000000..45e2b018d260f76117012d01f4c167d74ae26d0f
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/autostart_systemd.rst
@@ -0,0 +1,104 @@
+.. _systemd-service-guide:
+
+==============================================
+Setting up auto-restart using systemd on Linux
+==============================================
+
+.. note:: This guide is for setting up systemd on a Linux environment. This guide assumes that you already have a working Red instance.
+
+-------------------------
+Creating the service file
+-------------------------
+
+In order to create the service file, you will first need to know two things, your Linux :code:`username` and your Python :code:`path`
+
+First, your Linux :code:`username` can be fetched with the following command:
+
+.. prompt:: bash
+
+ whoami
+
+Next, your python :code:`path` can be fetched with the following commands:
+
+.. prompt:: bash
+ :prompts: $,(redenv) $
+ :modifiers: auto
+
+ # If redbot is installed in a venv
+ $ source ~/redenv/bin/activate
+ (redenv) $ /usr/bin/which python
+
+ # If redbot is installed in a pyenv virtualenv
+ $ pyenv shell
+ (redenv) $ pyenv which python
+
+Then create the new service file:
+
+:code:`sudo nano /etc/systemd/system/red@.service`
+
+Paste the following in the file, and replace all instances of :code:`username` with the Linux username you retrieved above, and :code:`path` with the python path you retrieved above.
+
+.. code-block:: none
+ :emphasize-lines: 8-10
+
+ [Unit]
+ Description=%I redbot
+ After=multi-user.target
+ After=network-online.target
+ Wants=network-online.target
+
+ [Service]
+ ExecStart=path -O -m redbot %I --no-prompt
+ User=username
+ Group=username
+ Type=idle
+ Restart=on-abnormal
+ RestartSec=15
+ RestartForceExitStatus=1
+ RestartForceExitStatus=26
+ TimeoutStopSec=10
+
+ [Install]
+ WantedBy=multi-user.target
+
+Save and exit :code:`ctrl + O; enter; ctrl + x`
+
+---------------------------------
+Starting and enabling the service
+---------------------------------
+
+.. note:: This same file can be used to start as many instances of the bot as you wish, without creating more service files, just start and enable more services and add any bot instance name after the **@**
+
+To start the bot, run the service and add the instance name after the **@**:
+
+.. prompt:: bash
+
+ sudo systemctl start red@instancename
+
+To set the bot to start on boot, you must enable the service, again adding the instance name after the **@**:
+
+.. prompt:: bash
+
+ sudo systemctl enable red@instancename
+
+If you need to shutdown the bot, you can use the ``[p]shutdown`` command or
+type the following command in the terminal, still by adding the instance name after the **@**:
+
+.. prompt:: bash
+
+ sudo systemctl stop red@instancename
+
+.. warning:: If the service doesn't stop in the next 10 seconds, the process is killed.
+ Check your logs to know the cause of the error that prevents the shutdown.
+
+To set the bot to not start on boot anymore, you must disable the service by running the following command, adding the instance name after the **@**:
+
+.. prompt:: bash
+
+ sudo systemctl disable red@instancename
+
+You can access Red's log through journalctl:
+
+.. prompt:: bash
+
+ sudo journalctl -eu red@instancename
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/autostart_windows.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/autostart_windows.rst
new file mode 100644
index 0000000000000000000000000000000000000000..a55d8df116582cff3e94da28b7ebc7a72859451d
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/autostart_windows.rst
@@ -0,0 +1,48 @@
+.. _autostart_windows:
+
+==============================================
+Setting up auto-restart using batch on Windows
+==============================================
+
+.. note:: This guide assumes that you already have a working Red instance.
+
+-----------------------
+Creating the batch file
+-----------------------
+
+Create a new text document anywhere you want to. This file will be used to launch the bot, so you may want to put it somewhere convenient, like Documents or Desktop.
+
+Open that document in Notepad, and paste the following text in it:
+
+.. code-block:: batch
+
+ @ECHO OFF
+ :RED
+ CALL "%userprofile%\redenv\Scripts\activate.bat"
+ python -O -m redbot
+
+ IF %ERRORLEVEL% NEQ 0 (
+ ECHO Restarting Red...
+ GOTO RED
+ )
+
+Replace ```` with the instance name of your bot.
+If you created your VENV at a location other than the recommended one, replace ``%userprofile%\redenv\Scripts\activate.bat`` with the path to your VENV.
+
+Click "File", "Save as". Change the dropdown "Save as type" to "All Files (*.*)". Set the filename to ``start_redbot.bat``, and click save.
+
+There should now be a new file in the location you created the text document in. You can delete that text document as it is no longer needed.
+You can now use the ``start_redbot.bat`` batch file to launch Red by double clicking it.
+This script will automatically restart red when the ``[p]restart`` command is used or when the bot shuts down abnormally.
+
+-------------------------
+Launch the bot on startup
+-------------------------
+
+Create a shortcut of your ``start_redbot.bat`` file.
+
+Open the "Run" dialogue box using Windows Key + R.
+
+Enter ``shell:startup`` if you want the bot to launch only when the current user logs in, or ``shell:common startup`` if you want the bot to launch when any user logs in.
+
+Drag the shortcut into the folder that is opened. The bot will now launch on startup.
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/bot_application_guide.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/bot_application_guide.rst
new file mode 100644
index 0000000000000000000000000000000000000000..dccfbddd0d0659ae1a16b0c195446b777511a95b
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/bot_application_guide.rst
@@ -0,0 +1,80 @@
+===========================================
+Creating a bot account
+===========================================
+
+To use Red you will require a bot account and to enable privileged intents. Both these steps will be covered below.
+
+.. _creating-a-bot-account:
+
+-------------------------------
+Creating the bot application
+-------------------------------
+
+In order to use Red, we must first create a Discord Bot account.
+
+Creating a Bot account is a pretty straightforward process.
+
+1. Make sure you're logged on to the `Discord website `_.
+2. Navigate to the `application page `_
+3. Click on the "New Application" button.
+
+ .. image:: /.resources/bot-guide/discord_create_app_button.png
+ :alt: The new application button.
+
+4. Give the application a name and click "Create".
+
+ .. image:: /.resources/bot-guide/discord_create_app_form.png
+ :alt: The new application form filled in.
+
+5. Create a Bot User by navigating to the "Bot" tab and clicking "Add Bot".
+
+ - Click "Yes, do it!" to continue.
+
+ .. image:: /.resources/bot-guide/discord_create_bot_user.png
+ :alt: The Add Bot button.
+6. If you want others to be able to invite your bot tick the **Public Bot**. Keeping it unticked will prevent others from inviting your bot to their servers and only you will be able to add the bot to servers (provided that you have needed permissions in the server you want to add the bot to).
+
+ - Make sure **Require OAuth2 Code Grant** is unchecked.
+
+ .. image:: /.resources/bot-guide/discord_bot_user_options.png
+ :alt: How the Bot User options should look like for most people.
+
+7. Copy the token using the "Copy" button.
+
+ - **This is not the Client Secret at the General Information page**
+
+ .. warning::
+
+ Do not share your token as it is like your password.
+ If you shared your token you can regenerate it.
+
+Continue to the next section to enable privileged intents.
+
+.. _enabling-privileged-intents:
+
+-------------------------------
+Enabling Privileged Intents
+-------------------------------
+.. warning::
+ :ref:`Red Bot requires all intents. `
+ \This section is required.
+
+1. Make sure you're logged on to the `Discord website `_.
+2. Navigate to the `application page `_
+3. Click on the bot you want to enable privileged intents for.
+4. Navigate to the bot tab on the left side of the screen.
+
+ .. image:: /.resources/bot-guide/discord_bot_tab.png
+ :alt: The bot tab in the application page.
+
+5. Scroll down to the "Privileged Gateway Intents" section, enable all three privileged intents and save your changes.
+
+ .. image:: /.resources/bot-guide/discord_privileged_intents.png
+ :alt: The privileged gateway intents selector.
+
+.. warning::
+
+ Red bots with over 100 servers require `bot verification `_ which is not covered in this guide.
+ Remember that :ref:`we do not support public bots `. We encourage you to read that page before scaling up your bot.
+
+*Parts of this guide have been adapted from* `discord.py intro `_ *and* `discord.py privileged intents `_.
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/changelog.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/changelog.rst
new file mode 100644
index 0000000000000000000000000000000000000000..26a877a07e4b101385a79d6adbd4ddede9193a55
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/changelog.rst
@@ -0,0 +1,5 @@
+=========
+Changelog
+=========
+
+.. include:: ../CHANGES.rst
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/cog_customcom.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_customcom.rst
new file mode 100644
index 0000000000000000000000000000000000000000..18e7347d228be390666a2ce578611e4c71924f84
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_customcom.rst
@@ -0,0 +1,110 @@
+.. CustomCommands Cog Reference
+.. _cog_customcom:
+
+============================
+CustomCommands Cog Reference
+============================
+
+------------
+How it works
+------------
+
+CustomCommands allows you to create simple commands for your bot without requiring you to code your own cog for Red.
+
+If the command you attempt to create shares a name with an already loaded command, you cannot overwrite it with this cog.
+
+---------
+Cooldowns
+---------
+
+You can set cooldowns for your custom commands. If a command is on cooldown, it will not be triggered.
+
+You can set cooldowns per member or per thread/channel, or set a cooldown guild-wide. You can also set multiple types of cooldown on a single custom command. All cooldowns must pass before the command will trigger.
+
+------------------
+Context Parameters
+------------------
+
+You can enhance your custom command's response by leaving spaces for the bot to substitute.
+
++-----------+--------------------------------------------------+
+| Argument | Substitute |
++===========+==================================================+
+| {message} | The message the bot is responding to. |
++-----------+--------------------------------------------------+
+| {author} | The user who called the command. |
++-----------+--------------------------------------------------+
+| {channel} | The channel or thread the command was called in. |
++-----------+--------------------------------------------------+
+| {server} | The server the command was called in. |
++-----------+--------------------------------------------------+
+| {guild} | Same as with {server}. |
++-----------+--------------------------------------------------+
+
+You can further refine the response with dot notation. For example, {author.mention} will mention the user who called the command.
+
+------------------
+Command Parameters
+------------------
+
+You can further enhance your custom command's response by leaving spaces for the user to substitute.
+
+To do this, simply put {#} in the response, replacing # with any number starting with 0. Each number will be replaced with what the user gave the command, in order.
+
+You can refine the response with colon notation. For example, {0:Member} will accept members of the server, and {0:int} will accept a number. If no colon notation is provided, the argument will be returned unchanged.
+
++-----------------+--------------------------------+
+| Argument | Substitute |
++=================+================================+
+| {#:Member} | A member of your server. |
++-----------------+--------------------------------+
+| {#:TextChannel} | A text channel in your server. |
++-----------------+--------------------------------+
+| {#:Role} | A role in your server. |
++-----------------+--------------------------------+
+| {#:int} | A whole number. |
++-----------------+--------------------------------+
+| {#:float} | A decimal number. |
++-----------------+--------------------------------+
+| {#:bool} | True or False. |
++-----------------+--------------------------------+
+
+You can specify more than the above with colon notation, but those are the most common.
+
+As with context parameters, you can use dot notation to further refine the response. For example, {0.mention:Member} will mention the Member specified.
+
+----------------
+Example commands
+----------------
+
+Showing your own avatar
+
+.. code-block:: none
+
+ [p]customcom add simple avatar {author.display_avatar}
+ [p]avatar
+ https://cdn.discordapp.com/avatars/133801473317404673/be4c4a4fe47cb3e74c31a0504e7a295e.webp?size=1024
+
+Repeating the user
+
+.. code-block:: none
+
+ [p]customcom add simple say {0}
+ [p]say Pete and Repeat
+ Pete and Repeat
+
+Greeting the specified member
+
+.. code-block:: none
+
+ [p]customcom add simple greet Hello, {0.mention:Member}!
+ [p]greet Twentysix
+ Hello, @Twentysix!
+
+Comparing two text channel's categories
+
+.. code-block:: none
+
+ [p]customcom add simple comparecategory {0.category:TextChannel} | {1.category:TextChannel}
+ [p]comparecategory #support #general
+ Red | Community
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/admin.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/admin.rst
new file mode 100644
index 0000000000000000000000000000000000000000..decf426d98ccd1c5bd6e51b7542089c605f4682e
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/admin.rst
@@ -0,0 +1,454 @@
+.. _admin:
+
+=====
+Admin
+=====
+
+This is the cog guide for the admin cog. You will
+find detailed docs about usage and commands.
+
+``[p]`` is considered as your prefix.
+
+.. note:: To use this cog, load it by typing this::
+
+ [p]load admin
+
+.. _admin-usage:
+
+-----
+Usage
+-----
+
+This cog will provide tools for server admins and bot owners.
+
+It can add or remove a role to a member, edit one or make some available
+for members so they can self-assign them as they wish.
+
+It also provides tools for the bot owner such as server locking (once enabled,
+the bot will instantly leave new servers it joins) and announcements, which
+can send something in all the servers of the bot.
+
+.. _admin-commands:
+
+--------
+Commands
+--------
+
+Here's a list of all commands available for this cog.
+
+.. _admin-command-selfrole:
+
+^^^^^^^^
+selfrole
+^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]selfrole
+
+**Description**
+
+Add or remove a role from yourself. It must have been configured as user settable
+by admins using the :ref:`selfroleset command `.
+
+**Arguments**
+
+* ````: The role you want to attribute or remove from yourself. |role-input|
+
+.. _admin-command-selfrole-add:
+
+""""""""""""
+selfrole add
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]selfrole add
+
+**Description**
+
+Add a role to yourself. It must have been configured as user settable
+by admins using the :ref:`selfroleset command `.
+
+**Arguments**
+
+* ````: The role you want to attribute to yourself. |role-input|
+
+.. _admin-command-selfrole-remove:
+
+"""""""""""""""
+selfrole remove
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]selfrole remove
+
+**Description**
+
+Remove a role from yourself. It must have been configured as user settable
+by admins using the :ref:`selfroleset command `.
+
+**Arguments**
+
+* ````: The role you want to remove from yourself. |role-input|
+
+
+.. _admin-command-selfrole-list:
+
+"""""""""""""
+selfrole list
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]selfrole list
+
+**Description**
+
+List all of the available roles you can assign to yourself.
+
+.. _admin-command-selfroleset:
+
+^^^^^^^^^^^
+selfroleset
+^^^^^^^^^^^
+
+.. note:: |admin-lock| This is also usable by the members with the
+ ``Manage roles`` permission.
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]selfroleset
+
+**Description**
+
+Define the list of user settable roles. Those roles will be available to any
+member using the :ref:`selfrole command `.
+
+.. _admin-command-selfroleset-add:
+
+"""""""""""""""
+selfroleset add
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]selfroleset add
+
+**Description**
+
+Add a role, or a selection of roles, to the list of available selfroles.
+
+.. warning:: Members will be able to assign themselves the role.
+ Make sure it doesn't give extra perms or anything that can break
+ your server's security.
+
+**Arguments**
+
+* ````: The role to add to the list. |role-input|
+
+.. _admin-command-selfroleset-clear:
+
+"""""""""""""""""
+selfroleset clear
+"""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]selfroleset clear
+
+**Description**
+
+Clear the list of available selfroles for this server.
+
+.. _admin-command-selfroleset-remove:
+
+""""""""""""""""""
+selfroleset remove
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]selfroleset remove
+
+**Description**
+
+Remove a role, or a selection of roles, from the list of available selfroles.
+
+**Arguments**
+
+* ````: The role to remove from the list. |role-input|
+
+.. _admin-command-addrole:
+
+^^^^^^^
+addrole
+^^^^^^^
+
+.. note:: |admin-lock| This is also usable by the members with the ``Manage
+ roles`` permission.
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]addrole [user]
+
+**Description**
+
+Adds a role to a member. If ``user`` is not given, it will be considered
+as yourself, the command author.
+
+**Arguments**
+
+* ````: The role to add to the member. |role-input-quotes|
+
+* ``[user]``: The member you want to add the role to. Defaults to the
+ command author. |member-input|
+
+.. _admin-command-removerole:
+
+^^^^^^^^^^
+removerole
+^^^^^^^^^^
+
+.. note:: |admin-lock| This is also usable by the members with the
+ ``Manage roles`` permission.
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]removerole [user]
+
+**Description**
+
+Removes a role from a member. If ``user`` is not given, it will be considered
+as yourself, the command author.
+
+**Arguments**
+
+* ````: The role to remove. |role-input-quotes|
+
+* ``[user]``: The member to remove the role from. |member-input| Defaults
+ to the command author.
+
+.. _admin-command-editrole:
+
+^^^^^^^^
+editrole
+^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]editrole
+
+**Description**
+
+Edits the settings of a role.
+
+.. _admin-command-editrole-name:
+
+"""""""""""""
+editrole name
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]editrole name
+
+**Description**
+
+Edits the name of a role.
+
+**Arguments**
+
+* ````: The role name to edit. |role-input-quotes|
+
+* ````: The new role name. If it has spaces, you must use quotes.
+
+.. _admin-command-editrole-color:
+
+""""""""""""""
+editrole color
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]editrole color
+
+**Description**
+
+Edits the color of a role.
+
+**Arguments**
+
+* ````: The role name to edit. |role-input-quotes|
+
+* ````: The new color to assign. |color-input|
+
+**Examples**
+
+* ``[p]editrole color "My role" #ff0000``
+
+* ``[p]editrole color "My role" dark_blue``
+
+.. _admin-command-announce:
+
+^^^^^^^^
+announce
+^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]announce
+
+**Description**
+
+Announce your message to all of the servers the bot is in.
+
+The bot will announce the message in the guild's announcements channel.
+If this channel is not set, the message won't be announced.
+
+**Arguments**
+
+* ````: The message to send.
+
+.. _admin-command-announce-cancel:
+
+"""""""""""""""
+announce cancel
+"""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]announce cancel
+
+**Description**
+
+Cancels an active announcement.
+
+.. _admin-command-announceset:
+
+^^^^^^^^^^^
+announceset
+^^^^^^^^^^^
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]announceset
+
+**Description**
+
+Change how announcements are received in this guild.
+
+.. _admin-command-announceset-channel:
+
+"""""""""""""""""""
+announceset channel
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]announceset channel
+
+**Description**
+
+Sets the channel where the bot owner announcements will be sent.
+
+**Arguments**
+
+* ````: The channel that will be used for bot announcements.
+ |channel-input|
+
+.. _admin-command-announceset-clearchannel:
+
+""""""""""""""""""""""""
+announceset clearchannel
+""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]announceset clearchannel
+
+**Description**
+
+Disables announcements on your server. To enable them again, you will have to
+re-enter your announcements channel with the :ref:`announceset channel
+` command.
+
+.. _admin-command-serverlock:
+
+^^^^^^^^^^
+serverlock
+^^^^^^^^^^
+
+.. note:: |owner-lock| This is also usable by the members with the
+ ``Administrator`` permission.
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]serverlock
+
+**Description**
+
+Lock a bot to its current servers only.
+
+This means that, once you enable this, if someone invites the bot to a new
+server, the bot will automatically leave the server.
+
+.. tip:: Another way to prevent your bot from being invited on more servers is
+ making it private directly from the developer portal.
+
+ Once a bot is private, it can only be invited by its owner (or team
+ owners). Other users will get an error on Discord's webpage explaining that
+ the bot is private.
+
+ To do this, go to the `Discord developer portal
+ `_, select your application, click "Bot" in
+ the sidebar, then untick "Public bot".
+
+ .. image:: ../.resources/admin/public_bot.png
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/alias.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/alias.rst
new file mode 100644
index 0000000000000000000000000000000000000000..dd49db36189ef887bcb77468b9bf7b558435908a
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/alias.rst
@@ -0,0 +1,277 @@
+.. _alias:
+
+=====
+Alias
+=====
+
+This is the cog guide for the alias cog. You will
+find detailed docs about the usage and the commands.
+
+``[p]`` is considered as your prefix.
+
+.. note:: To use this cog, load it by typing this::
+
+ [p]load alias
+
+.. _alias-usage:
+
+-----
+Usage
+-----
+
+This cog is used to create shortcuts for commands.
+
+Here's an example:
+
+.. code-block:: python
+
+ [p]play
+ # with an alias, you can call the command above with a shortcut like this:
+ [p]p
+ # "p" is now a shortcut for "play"
+
+In this example, we made an alias named ``p`` that will
+invoke the ``play`` command. If you use ``[p]play`` or ``[p]p``, the result will
+be the same.
+
+----
+
+Here's another example
+
+.. code-block:: python
+
+ [p]cleanup messages
+ # now we're creating another alias that will group both the command and the subcommand into this:
+ [p]clear
+ # "clear" is now a shortcut for "cleanup messages"
+
+In this second example, we made an alias called ``clear`` that will
+invoke the ``cleanup messages`` subcommand. Now if you use ``[p]cleanup
+message`` or ``[p]clear``, the result will be the same.
+
+----
+
+This is the basic usage, where you can define an alias for the first part of
+the command and give the second part when invoking the command. A more advanced
+usage of aliases is the usage of arguments.
+
+Let's suppose you want to make an alias to ban someone, delete 7 days of
+messages and set the reason to "Spam bot.", that cannot be done with a classic
+alias since the required member argument is the first one. If you create the
+alias "spamban" using arguments like this ``ban {0} 7 Spam bot.``, ``{0}`` will
+be replaced by the first argument of your alias:
+
+.. code-block:: none
+
+ # we created the following alias named "spamban"
+ [p]spamban Slime#3160
+ # this alias will execute the following command:
+ [p]ban Slime#3160 7 Spam bot.
+
+For a more detailed explanation, read :ref:`this `.
+
+.. _alias-commands:
+
+--------
+Commands
+--------
+
+.. _alias-command-alias:
+
+^^^^^
+alias
+^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]alias
+
+**Description**
+
+This is the main command used for setting up the cog.
+It will be used for all other commands.
+
+.. _alias-command-alias-add:
+
+"""""""""
+alias add
+"""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]alias add
+
+**Description**
+
+Creates an alias. It will be used like this ``[p]alias_name ``
+and will be equal to this ``[p]command ``.
+
+Let's develop the examples given :ref:`earlier ` a bit more,
+the left part of the command is the alias (blue), and the right part is the
+parameters members have to give for the command (orange).
+
+.. image:: ../.resources/alias/example-1.png
+
+One more thing you can do with aliases is using arguments, a bit like
+CustomCommands. Let's suppose you want an alias that bans x member and deletes
+7 days of messages. Without aliases, the command would look like this:
+
+``[p]ban NotSoTrustyJAID#0001 7 My random reason``
+
+A classic alias wouldn't work because the member argument is the first one,
+and you can only shorten the left part before the required argument.
+
+An alias with arguments can fix that, you can define the alias on the whole
+command and replace the required argument by ``{0}``, which will be replaced
+by the first parameter given when invoking the alias.
+
+Back to our example, let's make an alias named ``bigban`` which will be
+assigned to this expression: ``ban {0} 7``
+
+.. image:: ../.resources/alias/example-2.png
+
+You can see in blue the "static" part of the alias, what is contained and
+doesn't need to be given, the orange part is the arguments given at the end of
+the command, just like a classic alias, and the green part is the positional
+argument we defined: the first argument of the alias will be the green part.
+
+You can add as many arguments as you want, they can start at ``{0}`` or ``{1}``
+and must be in order: ``{1}`` will be the first argument, ``{2}`` will be the
+second one...
+
+.. attention:: The numbers must be in order, you cannot use ``{0}`` and ``{2}``
+ without using ``{1}``.
+
+Here are more examples:
+
+* * Full command: ``[p]cleanup messages 75 True``
+ * Alias: ``[p]alias add fullclear cleanup messages {0} True``
+ * Invoked alias: ``[p]fullclear 75``
+
+ *The* ``True`` *at the end tells the bot to also clear pinned messages.*
+
+* * Full command: ``[p]repo add SinbadCogs
+ https://github.com/mikeshardmind/SinbadCogs v3``
+
+ * Alias: ``[p]alias add newrepo repo add {2} https://github.com/{1}/{2}``
+ * Invoked with alias: ``[p]newrepo mikeshardmind SinbadCogs v3``
+
+**Arguments**
+
+* ````: The new command name.
+
+* ````: The command to execute when ``[p]alias_name`` is invoked.
+
+.. _alias-command-alias-delete:
+
+""""""""""""
+alias delete
+""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]alias [delete|remove|del]
+
+**Description**
+
+Removes an alias from the list. Check the list with
+the :ref:`alias list ` command.
+
+**Arguments**
+
+* ````: The alias' name to delete.
+
+.. _alias-command-alias-list:
+
+""""""""""
+alias list
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]alias list
+
+**Description**
+
+Shows all of the existing aliases on the current server.
+
+.. _alias-command-alias-show:
+
+""""""""""
+alias show
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]alias show
+
+**Description**
+
+Shows the command associated to the alias.
+
+**Arguments**
+
+* ````: The alias you want information from.
+
+.. _alias-command-alias-help:
+
+""""""""""
+alias help
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]alias help
+
+**Description**
+
+Shows help message for an alias.
+
+**Arguments**
+
+* ````: Alias you want to get help from.
+
+.. _alias-command-alias-global:
+
+""""""""""""
+alias global
+""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]alias global
+
+**Description**
+
+Another group command which contains the :ref:`add
+`, :ref:`del
+` and :ref:`list
+` commands.
+
+They work the same, except the created aliases will be
+global instead of being only server-wide.
+
+Please refer to these docs for the commands, they work with the
+same arguments. For example, if you want to add a global alias,
+instead of doing ``[p]alias add ``, do ``[p]alias
+global add ``.
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/audio.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/audio.rst
new file mode 100644
index 0000000000000000000000000000000000000000..0fd228cc47b664b481d5289ce4e90537bc110aa6
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/audio.rst
@@ -0,0 +1,3764 @@
+.. _audio:
+
+=====
+Audio
+=====
+
+This is the cog guide for the audio cog. You will
+find detailed docs about usage and commands.
+
+``[p]`` is considered as your prefix.
+
+.. note:: To use this cog, load it by typing this::
+
+ [p]load audio
+
+
+You can see additional help for any command in this guide by using ``[p]help`` with the
+command name, like ``[p]help playlist append``.
+
+In this guide, you will see references to "Lavalink" or the "Lavalink.jar". `Lavalink `_ is the
+Java-based audio backend we use to be able to play music through the bot. Most users will
+not have to worry much about Lavalink or what it is, as Audio manages this process for you
+by default. Advanced users can read more about Lavalink and special cases under the
+:ref:`Lavalink - Red Community-Supported Advanced Usage` section below.
+
+You will also see references to ``managed`` or ``unmanaged`` in regards to the Lavalink.jar.
+The default is ``managed``, as Audio manages the Lavalink.jar in this state. If it is run as an
+``unmanaged`` process, this means you as the bot owner will be managing the Lavalink process yourself.
+
+When the Audio cog is first loaded, it will contact GitHub and download the newest Lavalink.jar file
+for your bot to use. Any time Red is updated and you update your bot, it will probably download a new,
+updated Lavalink.jar for your bot. It is important to keep your bot updated as fixes are provided for Lavalink frequently.
+
+.. warning::
+
+ All commands should be used in a Discord server, and not in Direct Messages as Audio is not available there.
+
+.. _basic-audio-use:
+
+----------------
+Basic Audio Use
+----------------
+
+The following commands are used for controlling the audio being played, such as starting, stopping, and altering volume.
+
+* ``[p]play`` - Play a single song or a playlist URL or use this command with words to search for a song.
+* ``[p]search`` - Search for a track on YouTube. Searching on Soundcloud can be done with ``[p]search sc`` and the keywords to search for.
+* ``[p]stop`` - Stops playback and clears the queue.
+* ``[p]pause`` - This is a toggle. Use ``[p]pause`` again to resume the music.
+* ``[p]prev`` - Stops playback of the current song and returns to the start of the previous song played.
+* ``[p]skip`` - Skip to the next song in the queue, if there is one.
+* ``[p]seek`` - Seek ahead to a specific track time, or seek ahead by seconds.
+* ``[p]now`` - Show what song is currently playing.
+* ``[p]volume`` - Set the volume from 0% to 150%. 100% is the default. Discord server owners can set a limit to the volume with ``[p]audioset maxvolume``.
+
+.. note::
+
+ The following services are currently supported through ``[p]play``:
+
+ * Bandcamp
+ * HTTPS Icecast Streams
+ * HTTPS Shoutcast Streams
+ * Local file playback (:ref:`see here`)
+ * SoundCloud
+ * Spotify links via YouTube (:ref:`see here`)
+ * Twitch
+ * Vimeo
+ * YouTube
+ * Other AAC, MP3, or OGG-encoded streams
+
+.. note::
+
+ ``[p]audioset restrict`` is a toggle that only allows commercial site (YouTube, Soundcloud, etc) playback by default.
+ When toggled off, users will be able to play songs from HTTPS streams or arbitrary sites, but this could be a
+ security issue as your bot's IP address will be sent to any site it's connecting to, per standard internet protocol.
+
+.. _faq:
+
+--------------------------
+Frequently Asked Questions
+--------------------------
+
+**Q: I used a playlist link with some of the playlist related commands and it tells me that it can't find it.
+How can I use this playlist link with playlist commands in audio?**
+
+ Audio uses Red playlists in its commands that take playlist arguments.
+ These playlists can be created and modified using the ``[p]playlist`` group command.
+ When a playlist or song(s) are saved as a Red playlist, it is assigned an ID automatically,
+ and it is also assigned the one-word name you provided it when creating the playlist.
+ Either one of these identifiers can be used with playlist-related commands.
+
+ .. tip::
+
+ If you have a playlist URL, use ``[p]playlist save `` to save it as a Playlist
+ with Audio.
+
+**Q: How do I turn off autoplay?**
+
+ Use the ``[p]audioset autoplay toggle`` command.
+
+**Q: How do I get the bot to disconnect from the channel when it's done playing?**
+
+ ``[p]audioset dc`` will make the bot auto-disconnect when playback completes and the
+ queue is empty.
+ ``[p]audioset emptydisconnect`` with a seconds argument greater than 0 will make the bot
+ auto-disconnect once it's alone in the channel, after the amount of seconds given to the
+ command. This setting takes precedence over ``[p]audioset dc`` if both settings are active.
+
+**Q: How do I use localtracks?**
+
+ See the :ref:`local tracks section`.
+
+**Q: My console is saying that "Port 2333 is already in use". How can I fix this?**
+
+ If you are trying to run multiple bots with Audio, you should follow our guide on
+ :ref:`setting up Audio for multiple bots`. Otherwise, another process is using the
+ port, so you need to figure out what is using port 2333 and terminate/disconnect it yourself.
+
+**Q: My terminal is saying that I "must install Java 11 for Lavalink to run". How can I fix this?**
+
+ You are getting this error because you have a different version of Java installed, or you don't have
+ Java installed at all. As the error states, Java 11 is required, and can be installed from
+ `here `__.
+
+ If you have Java 11 installed, and are still getting this error, you will have to manually tell Audio where your Java install is located.
+ Use ``[p]llset java ``, to make Audio launch Lavalink with a
+ specific Java binary. To do this, you will need to locate your ``java.exe``/``java`` file
+ in your **Java 11 install**.
+
+ Alternatively, update your PATH settings so that Java 11 is the one used by ``java``. However,
+ you should confirm that nothing other than Red is running on the machine that requires Java.
+
+.. _queue_commands:
+
+----------------------
+Queue Related Commands
+----------------------
+
+* ``[p]queue`` - Shows the queue of playing songs and current settings for the server for shuffle and repeat.
+* ``[p]remove`` - Remove a song from the queue. This command uses the track position in the queue for identification, e.g. ``[p]remove 10`` will remove
+ the 10th song in the queue.
+* ``[p]shuffle`` - Toggle random song playback from the queue.
+* ``[p]queue shuffle`` - Shuffles the queue.
+* ``[p]repeat`` - Toggle adding songs back into the queue when they are finished playing.
+* ``[p]playlist queue`` - Save the current queue to a Red playlist.
+* ``[p]audioset persistqueue`` - Can be used to reinstate existing queues when the bot is restarted. This is an owner-only command.
+* ``[p]audioset globaldailyqueue`` - Will toggle saving the day's worth of tracks to a Global-level Red playlist, for every day. This is an owner-only command.
+
+.. _playlist_commands:
+
+-----------------
+Playlist Commands
+-----------------
+
+Playlists can be saved locally on the bot in a variety of different scopes:
+
+* Global - The playlist will be available on all servers.
+* Guild (default scope) - The playlist will be available only in a specified guild.
+* User - The playlist will be available in any guild that the user shares with the bot.
+
+Some of the most relevant playlist commands include:
+
+* ``[p]playlist append`` - Add a track URL, playlist link, or quick search to a playlist.
+* ``[p]playlist create`` - Creates an empty playlist.
+* ``[p]playlist delete`` - Delete a saved playlist.
+* ``[p]playlist info`` - Retrieve information about a saved playlist.
+* ``[p]playlist list`` - List saved playlists.
+* ``[p]playlist queue`` - Save the currently playing queue to a playlist.
+* ``[p]playlist remove`` - Remove a track from a playlist by URL.
+
+As always, you can run ``[p]help playlist `` for more information.
+
+.. _owner-audioset-commands:
+
+----------------------------
+Owner-Only Audioset Commands
+----------------------------
+
+* ``[p]audioset cache`` - This sets the local metadata caching level for Audio. By default, this is set to on as it helps
+ reduce 429 Forbidden errors from song services, and also caches Spotify song lookups. Most users will not need to touch this option.
+* ``[p]audioset cacheage`` - How long the entries in the cache last. By default, song metadata is cached for 365 days (1 year).
+* ``[p]audioset status`` - Show the now playing song in the bot's status, or show how many servers the bot is playing music on, if more than one.
+* ``[p]audioset restrictions global`` - Manage the keyword blocklist/allowlist for the whole bot.
+
+.. _guild-audioset-commands:
+
+-----------------------------
+Guild-based Audioset Commands
+-----------------------------
+
+* ``[p]audioset notify`` - Toggle extra messages: Audio will display a notification message when a track starts,
+ showing the song title, artist, and the thumbnail (if enabled and present). This notify message follows the last
+ invoking Audio command - if an Audio command is used in one channel and this setting is on, the notify messages
+ will start to appear in the channel where the command was used. If another Audio command is used in another
+ channel, notify messages will start appearing in the second channel instead of the first command channel.
+* ``[p]audioset maxvolume`` - Set the max volume for the guild.
+* ``[p]audioset autodeafen`` - Toggle the bot being auto-deafened upon voice channel join.
+* ``[p]audioset restrictions`` - Manage the keyword blocklist/allowlist for the guild.
+* ``[p]audioset lyrics`` - Searching for tracks will prefer songs with 'lyrics' in the name, to avoid videos with long story intros or outros.
+
+.. _spotify-playback-and-api-keys:
+
+------------------------------
+Spotify Playback and API Keys
+------------------------------
+
+We will never be able to play directly from Spotify itself as it is against their Terms of Service. Audio can play
+single tracks or playlists from Spotify by looking up the song(s) on YouTube and playing those tracks instead.
+This is possible by providing your bot with a YouTube API key and a Spotify API key. Instructions for setting both
+can be found under ``[p]audioset youtubeapi`` and ``[p]audioset spotifyapi``.
+
+The YouTube API keys that are being given out currently only have 10000 units of quota per day, which is equivalent to
+100 Spotify song lookups. There is a local metadata cache that Audio uses to be able to retain information about song
+lookups. For example, with a 500 song Spotify playlist, the bot will be able to fetch the first 100 songs the
+first day the Spotify playlist URL is used with Audio, then the next day it will be able to use the first 100 lookups
+from the local cache, and use the API credits to look up the next 100 songs. After 5 days of playing the Spotify playlist
+through Audio, that playlist will be fully cached locally until the cached entries are set to expire and will not require
+any API credits to play songs.
+
+The following commands are relevant:
+
+* ``[p]genre`` - Lets users pick a Spotify music genre to queue music from.
+* ``[p]audioset countrycode`` - Lets guild owners specify what country code to prefer for Spotify searches, for the guild.
+* ``[p]audioset mycountrycode`` - Lets individual users pick what country code to prefer for Spotify searches of their own.
+
+.. _local-tracks:
+
+------------
+Local Tracks
+------------
+
+Audio can play music from a ``localtracks`` folder on the device where the bot is hosted. This feature is only available
+if your bot and your Lavalink.jar are on the same host, which is the default setup.
+
+To use this feature:
+
+1. Create a "localtracks" folder anywhere where Lavalink/your bot user has permissions to access, on the system.
+2. Use ``[p]audioset localpath `` to set the folder created above as the localtracks folder.
+3. Create/move/copy/symlink your album folders (Subfolders containing your tracks) to the folder created in Step 1.
+4. Put any of Audio's supported files in the following folders:
+
+ * ``localtracks//song.mp3``
+ * ``localtracks///song.mp3``
+
+When using this localtracks feature, use ``[p]local`` commands. Use ``[p]play /song.mp3`` to play
+single songs. Use ``[p]local folder /`` to play the entire folder.
+
+The following formats are supported:
+
+* MP3
+* FLAC
+* Matroska/WebM (AAC, Opus or Vorbis codecs)
+* MP4/M4A (AAC codec)
+* OGG streams (Opus, Vorbis and FLAC codecs)
+* AAC streams
+
+The following files are partially supported:
+
+* .ra
+* .wav
+* .opus
+* .wma
+* .ts
+* .au
+* .mov
+* .flv
+* .mkv
+* .wmv
+* .3gp
+* .m4v
+* .mk3d
+* .mka
+* .mks
+
+The following files are **NOT** supported:
+
+* .mid
+* .mka
+* .amr
+* .aiff
+* .ac3
+* .voc
+* .dsf
+* .vob
+* .mts
+* .avi
+* .mpg
+* .mpeg
+* .swf
+
+.. _dj-role-and-voteskip:
+
+--------------------
+DJ Role and Voteskip
+--------------------
+
+Audio has an internal permissions system for restrictions to audio commands while other people are listening to
+music with the bot. Bot owners, server admins and mods bypass these restrictions when they are in use.
+
+``[p]audioset dj`` will turn on the DJ role restriction system, ``[p]audioset role`` will let you choose or
+reassign the DJ role, and if you wish to make non-privileged users vote to skip songs, voteskip can be enabled
+with ``[p]audioset vote``.
+
+If a non-privileged user is listening to music alone in the channel, they can use commands without restrictions,
+even if DJ role or voteskip settings are active.
+
+.. _sound-quality-issues:
+
+--------------------
+Sound Quality Issues
+--------------------
+
+Laggy audio is most likely caused by:
+
+* A problem with the connection between the machine that is hosting Lavalink and the Discord voice server.
+* Issues with Discord.
+
+You can try the following to resolve poor sound quality:
+
+* Don't host on home internet, especially over a WiFi connection. Try hosting your bot elsewhere.
+* Try the web browser instead of the desktop client for listening.
+* Simply wait, as audio quality may improve in due course.
+* Restart your bot.
+* Check to make sure it's not just a bad quality song (try a different song).
+* Try to listen on a different Discord server or server region.
+* If not everyone is experiencing the issue, it's a Discord client issue.
+
+.. _no-sound:
+
+^^^^^^^^
+No Sound
+^^^^^^^^
+
+If the bot's speaking light is active, but there is no sound, troubleshoot the following:
+
+1. Is the bot's user volume turned up? (right click on the bot in Discord, see the slider).
+2. Is the bot muted or deafened? Are you deafened? Are you deaf?
+3. Check Discord audio device settings and volume (cog icon next to your username in the bottom left, click "Voice and Video").
+4. Try dragging and dropping the bot back to the voice channel.
+5. Check system audio device settings and volume.
+6. Ask another member to come into the voice channel to confirm that it's not just you.
+
+If the track progress is stuck on 00:00 when you run ``[p]now``:
+
+1. Try to run ``[p]disconnect`` and replay the song.
+2. Try to reload the audio cog with ``[p]audioset restart``.
+3. Make sure the firewall on the host is configured properly.
+
+.. _advanced-usage:
+
+-------------------------------------------------
+Lavalink - Red Community-Supported Advanced Usage
+-------------------------------------------------
+
+.. _multibots:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Setting up Multiple Red Instances with Audio on the Same Host
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. warning::
+
+ This section provides instructions for setting up an unmanaged Lavalink node that is on the same machine
+ as the Red bot(s) that need to connect to it. This configuration is supported by the Red community, so
+ if you need additional help, feel free to join the `Red Support Server `__ and ask in the #support channel.
+
+ If you are looking to set up a remote, unmanaged Lavalink node on a different vps or host than the Red
+ bot(s) that will connect to it, we provide basic instructions in this guide :ref:`here`, but that
+ configuration is partially unsupported as we do not provide help with network configuration or system
+ administration. You will be responsible for configuring your network, firewall, and other system
+ properties to enable playback and for the bot to connect to the remote unmanaged Lavalink server.
+
+If you are wanting to use multiple bots with Audio on the same machine, you'll need to make a few
+necessary modifications.
+
+Firstly, stop all Red bots. For each bot using Audio:
+
+1. Start the bot.
+2. Run the command ``[p]llset unmanaged``.
+3. Stop the bot.
+
+Next, open a command prompt/terminal window. Navigate to ``/cogs/Audio`` for any of your bot
+instances - it doesn't matter which bot as all your bots will now use this single instance of Lavalink.
+You can find your ```` with the ``[p]datapath`` command.
+
+Now you need to determine your RAM needs. If your bot has 1GB RAM available, Lavalink should be restricted
+to perhaps 384MB -> 768MB, depending on the cogs you have installed. If your bot has 2GB of RAM available,
+a good amount may be 512MB -> 1GB.
+
+Run the following command, where ``Xmx`` specifies the RAM value you have just determined. The MB suffix
+is M and the GB suffix is G.
+
+.. code-block:: ini
+
+ java -jar -Xmx768M Lavalink.jar -Djdk.tls.client.protocols=TLSv1.2
+
+Leave this command prompt/terminal window open (you will need to do this every time you want to start Lavalink
+for your bots). Once Lavalink says it has fully started, you can start your bots back up.
+
+.. note::
+
+ If you are on Linux, this process can be automated using systemd, for unmanaged
+ Lavalink backends **only**. See :ref:`here` for details.
+
+.. warning::
+
+ By running multiple bots that use Audio, the responsibility for keeping the Lavalink.jar updated will now be
+ in your hands, as Red will no longer manage it through the Audio cog. See :ref:`here` for guidance.
+
+.. _linux-audio-autorestart:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Linux Lavalink Auto-Restart
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Auto-restarting Lavalink is possible on Linux with systemd, for unmanaged Lavalink backends.
+
+Firstly, find out what your datapath is with the ``[p]datapath`` command. Your Lavalink path is
+``/cogs/Audio``. Create a file named ``auto_update.sh`` in your Lavalink path.
+
+Inside this newly created file, paste the following text:
+
+.. code-block:: sh
+
+ curl -LOz Lavalink.jar https://github.com/Cog-Creators/Lavalink-Jars/releases/latest/download/Lavalink.jar
+
+Run the following, replacing ```` with the Lavalink path you generated earlier (``/cogs/Audio``).
+
+.. code-block:: sh
+
+ chmod a+rx /auto_update.sh
+
+Now we need to create a service file so that systemd can do its magic. Run the following command:
+
+.. code-block:: sh
+
+ sudo -e /etc/systemd/system/lavalink.service
+
+Next, paste in the example below, but replacing the following:
+
+* ```` - You can find your Java path by running ``which java``.
+* ```` - The parent folder where your Lavalink executable can be located (usually in ``/cogs/Audio``).
+* ```` - Your username on the host machine (run ``echo $USER``).
+
+.. code-block:: ini
+
+ [Unit]
+ Description=lavalink
+ After=multi-user.target
+
+ [Service]
+ ExecStart= -Djdk.tls.client.protocols=TLSv1.2 -jar < Lavalink path >/Lavalink.jar
+ WorkingDirectory=
+ User=
+ Group=
+ ExecStartPre=/bin/bash /auto_update.sh # Comment this line out if you did not create the auto_update.sh
+ Type=idle
+ Restart=always
+ RestartSec=15
+
+ [Install]
+ WantedBy=multi-user.target
+
+Finally, we need to start and enable the service. Run the following commands, separately.
+
+.. code-block:: sh
+
+ sudo systemctl start lavalink
+ sudo systemctl enable lavalink
+
+These commands always need to be ran when starting the lavalink service to ensure that the
+service runs in the background.
+
+Finally, you can run the following to retrieve logs for the service, when you need them:
+
+.. code-block:: sh
+
+ sudo journalctl -u lavalink
+
+.. _obtaining-the-latest-lavalink:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Obtaining the latest Lavalink.jar on a Red update
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**To manually download the jar**
+
+Stop your bot. Download the Lavalink.jar file from `here `__,
+which could alternatively be downloaded by running the following command:
+
+.. code-block:: sh
+
+ curl -LOz Lavalink.jar https://github.com/Cog-Creators/Lavalink-Jars/releases/latest/download/Lavalink.jar
+
+Next, stop all instances of Red running on the host, and stop the Lavalink process. Move the new Lavalink.jar
+to where your old Lavalink.jar is located, overwriting the old file.
+
+Finally, start up the new Lavalink.jar process via a process manager like systemd, or by running the following command:
+
+.. code-block:: sh
+
+ java -jar Lavalink.jar -Djdk.tls.client.protocols=TLSv1.2
+
+Start up your bots, and now they will use the latest Lavalink.jar!
+
+.. _remote-lavalink:
+
+---------------------------------------------------------------
+Setting up an unmanaged Lavalink node on a remote VPS or server
+---------------------------------------------------------------
+
+.. attention::
+
+ We'd like to thank BreezeQS, as this guide is a supersession of their unofficial bare-bones guide.
+
+This guide explains how to set up an unmanaged Lavalink node on a separate server running Ubuntu 20.04 LTS.
+It is assumed your bot currently uses a managed Lavalink server (Red's default).
+
+.. warning::
+
+ This guide is provided for advice on this topic and this is generally not a supported configuration for
+ Red's usage of Lavalink, as it involves system administration and network configuration. However, if you
+ run into any issues, feel free to ask for help in the `Red Support Server `__, in the #general channel.
+
+.. warning::
+
+ For security purposes DO NOT follow this guide while logged in as the root user. You should create
+ a separate non-root user instead. You can follow
+ `this guide `__
+ from DigitalOcean if you need help about how this is done.
+
+^^^^^^^^^^^^^^^^^^^^^^^^^
+Prerequisite Installation
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+We will first install Lavalink and lay the foundation for our finished server. There are some prerequisites
+that must be installed on the server you aim to use for running Lavalink. To set those up, run each of the
+following commands one by one.
+
+.. code-block:: sh
+
+ sudo apt update
+ sudo apt upgrade -y
+ sudo apt install curl nano -y
+
+If you have no preference in which Java version you install on your target system, Red
+uses OpenJDK 11 in the managed Lavalink configuration. It can be installed by running:
+
+.. code-block:: sh
+
+ sudo apt install openjdk-11-jre-headless -y
+
+Otherwise, Lavalink works well with most versions of Java 11, 13, 15, 16, 17, and 18. Azul
+Zulu builds are suggested, see `here `__ for more information.
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Setting Up The Lavalink Folder
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Lavalink itself, its configuration, and its logs will all be kept in a single directory. In this guide,
+we will simply call this directory lavalink and it will be located in the home directory of the user you
+are logged in as.
+
+We need to create a new directory called **lavalink**, and then switch to it as the upcoming sections of
+this guide require your current directory to be the **lavalink** folder. We can achieve this by running
+the following commands one by one:
+
+.. code-block:: sh
+
+ cd
+ mkdir lavalink
+ cd lavalink
+
+^^^^^^^^^^^^^^^^^^^
+Installing Lavalink
+^^^^^^^^^^^^^^^^^^^
+
+The Lavalink executable used in Red-Discordbot is slightly modified and is not the same as stock Lavalink,
+it ensures proper operation when used with Red-Discordbot and compatibility with systems and libraries that
+Red uses to operate. It's required to use this Lavalink.jar when running unmanaged Lavalink servers to not
+void your privilege to receive support. Assuming your current directory is the lavalink folder as you ran
+the ``cd lavalink`` command in the previous section, you can run the following commands one by one to install it:
+
+.. code-block:: sh
+
+ curl https://raw.githubusercontent.com/freyacodes/Lavalink/master/LavalinkServer/application.yml.example > application.yml
+ curl -LOz Lavalink.jar https://github.com/Cog-Creators/Lavalink-Jars/releases/latest/download/Lavalink.jar
+
+If you did it properly, the files ``Lavalink.jar`` and ``application.yml`` will show up when we run ``ls``, the Linux command
+to list the contents of the current directory.
+
+^^^^^^^^^^^^^^^^^^^^
+Configuring Lavalink
+^^^^^^^^^^^^^^^^^^^^
+
+Lavalink stores its settings inside the ``application.yml`` file located in the same directory as the executable jar itself.
+You have to edit this file and change some settings for security purposes.
+
+First, let's open the file. You can use any text editor you want, but in this guide we will use nano.
+Run the following command:
+
+.. code-block:: sh
+
+ nano application.yml
+
+You will be dropped into the nano text editor with ``application.yml`` opened. The two important fields that we will modify
+are the ``port`` and ``password`` fields.
+
+The ``port`` field is the TCP port your Lavalink server will be accessible at. The default value is 2333, and you can set this
+to any positive integer smaller than 65535 and greater than 1000. It is advised to change it to aid in security.
+
+The ``password`` field is the password that will be required for accessing your Lavalink server and by default the password is
+``youshallnotpass``. You should absolutely change this to a secure password.
+
+Those two fields are important and you should take note of the new values you entered, as
+they will be later required to connect your bot to the Lavalink server.
+
+At the bottom of the screen, the nano text editor displays some keys that can be used to carry out various tasks.
+In this case, we want to save and exit. Keys prefixed with the caret (^) sign means they are used in conjunction
+with the ctrl key. So we press Ctrl+X to exit.
+
+Nano will ask if you want to save the changes that were made. Answer with ``y`` and hit enter to exit.
+
+^^^^^^^^^^^^^^^^^
+Starting Lavalink
+^^^^^^^^^^^^^^^^^
+
+Now that Lavalink has been installed and configured, we can start it up. To do so, run the following command, making sure
+that you are inside the lavalink folder, of course:
+
+.. code-block:: sh
+
+ java -Djdk.tls.client.protocols=TLSv1.2 -jar Lavalink.jar
+
+On successful start, Lavalink will greet you with a line mentioning that it is ready to accept connections and you can now
+try connecting to it with your bot.
+
+Since we did not configure autostart for Lavalink, you will have to keep the console window open or it will be shut down
+and all connections will be dropped. This is similar to how it happens in Red-Discordbot itself.
+
+This also means that you will have to restart Lavalink manually each time you log on. This is often done in testing environments.
+You can restart Lavalink manually by running the following commands one by one:
+
+.. code-block:: sh
+
+ cd
+ cd lavalink
+ java -Djdk.tls.client.protocols=TLSv1.2 -jar Lavalink.jar
+
+You can stop Lavalink and reclaim the console by hitting ``CTRL+C``.
+
+^^^^^^^^^^^^^^^^^
+Updating Lavalink
+^^^^^^^^^^^^^^^^^
+
+With new releases of Red-Discordbot, sometimes new Lavalink jars are also released. Using an obsolete version of Lavalink
+with newer versions of Red-Discordbot can cause all sorts of problems.
+
+Normally, users do not have to worry about this as when Red-Discordbot is configured to use a managed Lavalink server
+(the default setting) Lavalink is automatically updated when a new release comes out.
+
+However, since you are running a Lavalink instance yourself you are responsible for keeping it up to date.
+When a new release of Red-Discordbot also requires a update to the Lavalink jar, you will be informed in the changelogs
+posted in our documentation.
+
+When a new Lavalink.jar comes out, you can easily update the existing one. First, you should stop Lavalink if it's currently
+running. Once you have done this, you can follow the instructions on how to :ref:`obtain the latest Lavalink.jar on a Red update`.
+
+In the next section we will see how you can configure Lavalink to automatically update, automatically start, and run as
+a background process which is much more convenient for non-testing deployments.
+
+^^^^^^^^^^^^^^^^^^^^^^
+Setting up Auto Update
+^^^^^^^^^^^^^^^^^^^^^^
+
+As previously covered, running Lavalink in a simple terminal session is fragile. Not only does it need you to manually
+intervene each time you login, reboot, or just have to restart Lavalink for any reason you also have to update it manually
+when a new Lavalink jar comes out.
+
+First of all, we will configure a script for updating Lavalink that runs before each time Lavalink starts. This step is
+highly recommended. But if you know what you are doing, you can skip it if you want to update Lavalink manually.
+
+First, run the following commands:
+
+.. code-block:: sh
+
+ cd
+ cd lavalink
+ nano auto_update.sh
+
+You'll see that running nano has opened a file. Paste the following code into the file:
+
+.. code-block:: sh
+
+ #!/bin/sh
+ curl -LOz Lavalink.jar https://github.com/Cog-Creators/Lavalink-Jars/releases/latest/download/Lavalink.jar
+
+Now save the file and exit (``CTRL+X``, then ``y``).
+
+Now, run the following command, which will make the script possible to run:
+
+.. code-block:: sh
+
+ chmod a+rx auto_update.sh
+
+If you did it right, the command itself will not output anything. And when running ``ls``, the script will show up in green.
+
+""""""""""""""""""""""""""""""
+Setting Up the Systemd Service
+""""""""""""""""""""""""""""""
+
+We will now register Lavalink as a system service, allowing it to run in the background without user intervention.
+But before that, we need to gather some information. While in the lavalink folder, run the following commands one by one
+and note their output somewhere, because we will need them:
+
+.. code-block:: sh
+
+ pwd
+ which java
+ echo "$USER"
+
+Now run the following command:
+
+.. code-block:: sh
+
+ sudo -e /etc/systemd/system/lavalink.service
+
+On new systems it may ask for a choice of editor. Nano is the best choice. To select it, press 1 and hit enter.
+The nano text editor will now open. Now copy and paste the following text into it:
+
+.. code-block:: ini
+
+ [Unit]
+ Description=lavalink
+ After=multi-user.target
+
+ [Service]
+ ExecStart=< Java executable path > -Djdk.tls.client.protocols=TLSv1.2 -jar < Lavalink path >/Lavalink.jar
+ WorkingDirectory=< Lavalink path >
+ User=< username >
+ Group=< username >
+ ExecStartPre=/bin/bash < Lavalink path >/auto_update.sh # Comment this line out if you did not create the auto_update.sh
+ Type=idle
+ Restart=always
+ RestartSec=15
+
+ [Install]
+ WantedBy=multi-user.target
+
+* Replace all occurrences of ``< Lavalink path >`` with the output of ``pwd`` you noted earlier.
+* Replace all occurrences of ``< Java executable path >`` with the output of ``which java`` you noted earlier.
+* Replace all occurrences of ``< username >`` with the output of echo ``"$USER"`` you noted earlier.
+
+Hit ``CTRL+X``, ``y`` and then ENTER to save and exit. We have now registered Lavalink as a service.
+
+""""""""""""""""""""""""""""""""""""""""""
+Starting and Enabling the Lavalink Service
+""""""""""""""""""""""""""""""""""""""""""
+
+Now run the following command to start the Lavalink service and wait for 10-15 seconds:
+
+.. code-block:: sh
+
+ sudo systemctl start lavalink
+
+You can check the service status with the following command:
+
+.. code-block:: sh
+
+ sudo journalctl -u lavalink
+
+Keep in mind this will occupy your terminal and you have to hit CTRL+C to stop it before doing something else.
+This will only close the log viewer, Lavalink itself will continue to run in the background.
+
+You may now run the following to make Lavalink auto-restart each boot:
+
+.. code-block:: sh
+
+ sudo systemctl enable lavalink
+
+.. tip::
+
+ You can stop the Lavalink service with the following when you need to e.g. for troubleshooting:
+
+ .. code-block:: sh
+
+ sudo systemctl stop lavalink
+
+ You can also check the logs Lavalink persists by checking the ``spring.log`` file in the ``lavalink/logs/`` folder.
+
+Congratulations, you are almost ready.
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Connecting to Your New Lavalink Server
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+If your Red instance and Lavalink server will communicate over the Internet, make sure the Lavalink port is accessible
+from the internet. Click `here `__ and test if the port you set in the ``application.yml``
+is accessible on the public ip address of your Lavalink server. This step isn't necessary if your Lavalink server and Red
+instance will communicate over LAN. If you get connectivity errors, make sure there are no firewalls blocking the port and
+you are using the correct port.
+
+If successful, run each of the following commands one by one on your bot. Replace ``"yourlavalinkip"`` with the ip of your Lavalink server.
+Change ``"port"`` with the port you set up in the application.yml. Change ``"password"`` with the password you set up in the application.yml.
+Do not use quotes in these commands. For example, ``[p]llset host 192.168.10.101`` or ``[p]llset password ahyesverysecure``.
+
+.. code-block:: none
+
+ [p]llset unmanaged
+ [p]llset host "yourlavalinkip"
+ [p]llset port "port"
+ [p]llset password "password"
+
+Reload audio with ``[p]reload audio`` and give it a few seconds to connect.
+
+You now (hopefully) have a functioning Lavalink server on a machine separate to the one running your Red instance. Good luck!
+
+.. _audio-commands:
+
+--------
+Commands
+--------
+
+.. _audio-command-audioset:
+
+^^^^^^^^
+audioset
+^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset
+
+**Description**
+
+Music configuration options.
+
+.. _audio-command-audioset-autodeafen:
+
+"""""""""""""""""""
+audioset autodeafen
+"""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset autodeafen
+
+**Description**
+
+Toggle whether the bot will be auto deafened upon joining the voice channel.
+
+.. _audio-command-audioset-autoplay:
+
+"""""""""""""""""
+audioset autoplay
+"""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset autoplay
+
+**Description**
+
+Change auto-play setting.
+
+.. _audio-command-audioset-autoplay-playlist:
+
+""""""""""""""""""""""""""
+audioset autoplay playlist
+""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset autoplay playlist [args]
+
+**Description**
+
+Set a playlist to auto-play songs from.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example Usage**
+
+* ``[p]audioset autoplay playlist MyGuildPlaylist``
+* ``[p]audioset autoplay playlist MyGlobalPlaylist --scope Global``
+* ``[p]audioset autoplay playlist PersonalPlaylist --scope User --author Draper``
+
+.. _audio-command-audioset-autoplay-reset:
+
+"""""""""""""""""""""""
+audioset autoplay reset
+"""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset autoplay reset
+
+**Description**
+
+Resets auto-play to the default playlist.
+
+.. _audio-command-audioset-autoplay-toggle:
+
+""""""""""""""""""""""""
+audioset autoplay toggle
+""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset autoplay toggle
+
+**Description**
+
+Toggle auto-play when there are no songs in the queue.
+
+.. _audio-command-audioset-cache:
+
+""""""""""""""
+audioset cache
+""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset cache [level]
+
+**Description**
+
+Sets the caching level.
+
+Level can be one of the following:
+
+* ``0``: Disables all caching
+* ``1``: Enables Spotify Cache
+* ``2``: Enables YouTube Cache
+* ``3``: Enables Lavalink Cache
+* ``5``: Enables all Caches
+
+If you wish to disable a specific cache use a negative number.
+
+.. _audio-command-audioset-cacheage:
+
+"""""""""""""""""
+audioset cacheage
+"""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset cacheage
+
+**Description**
+
+Sets the cache max age. This commands allows you to set the max number of
+days before an entry in the cache becomes invalid.
+
+.. _audio-command-audioset-countrycode:
+
+""""""""""""""""""""
+audioset countrycode
+""""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset countrycode
+
+**Description**
+
+Set the country code for Spotify searches.
+
+.. _audio-command-audioset-dailyqueue:
+
+"""""""""""""""""""
+audioset dailyqueue
+"""""""""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset dailyqueue
+
+**Description**
+
+Toggle daily queues. Daily queues creates a playlist for all tracks played today.
+
+.. _audio-command-audioset-dc:
+
+"""""""""""
+audioset dc
+"""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset dc
+
+**Description**
+
+Toggle the bot auto-disconnecting when done playing. This setting takes precedence
+over ``[p]audioset emptydisconnect``.
+
+.. _audio-command-audioset-dj:
+
+"""""""""""
+audioset dj
+"""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset dj
+
+**Description**
+
+Toggle DJ mode. DJ mode allows users with the DJ role to use audio commands.
+
+.. _audio-command-audioset-emptydisconnect:
+
+""""""""""""""""""""""""
+audioset emptydisconnect
+""""""""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset emptydisconnect
+
+**Description**
+
+Auto-disconnect from channel when bot is alone in it for x seconds, 0 to disable.
+``[p]audioset dc`` takes precedence over this setting.
+
+.. _audio-command-audioset-emptypause:
+
+"""""""""""""""""""
+audioset emptypause
+"""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset emptypause
+
+**Description**
+
+Auto-pause after x seconds when the channel is empty, 0 to disable.
+
+.. _audio-command-audioset-globaldailyqueue:
+
+"""""""""""""""""""""""""
+audioset globaldailyqueue
+"""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset globaldailyqueue
+
+**Description**
+
+Toggle global daily queues. Global daily queues creates a playlist
+for all tracks played today.
+
+.. _audio-command-audioset-jukebox:
+
+""""""""""""""""
+audioset jukebox
+""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset jukebox
+
+**Description**
+
+Set a price for queueing tracks for non-mods, 0 to disable.
+
+.. _audio-command-audioset-localpath:
+
+""""""""""""""""""
+audioset localpath
+""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset localpath [local_path]
+
+**Description**
+
+Set the localtracks path if the Lavalink.jar is not run from the Audio data folder.
+Leave the path blank to reset the path to the default, the Audio data directory.
+
+.. _audio-command-audioset-logs:
+
+"""""""""""""
+audioset logs
+"""""""""""""
+
+.. note:: |owner-lock|
+
+.. note::
+
+ This command is only available for managed Lavalink servers.
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset logs
+
+**Description**
+
+Sends the Lavalink server logs to your DMs.
+
+.. _audio-command-audioset-lyrics:
+
+"""""""""""""""
+audioset lyrics
+"""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset lyrics
+
+**Description**
+
+Prioritise tracks with lyrics.
+
+.. _audio-command-audioset-maxlength:
+
+""""""""""""""""""
+audioset maxlength
+""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset maxlength
+
+**Description**
+
+Max length of a track to queue in seconds, 0 to disable. Accepts seconds or a value
+formatted like 00:00:00 (``hh:mm:ss``) or 00:00 (``mm:ss``). Invalid input will turn
+the max length setting off.
+
+.. _audio-command-audioset-maxvolume:
+
+""""""""""""""""""
+audioset maxvolume
+""""""""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset maxvolume
+
+**Description**
+
+Set the maximum volume allowed in this server.
+
+.. _audio-command-audioset-mycountrycode:
+
+""""""""""""""""""""""
+audioset mycountrycode
+""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset mycountrycode
+
+**Description**
+
+Set the country code for Spotify searches.
+
+.. _audio-command-audioset-notify:
+
+"""""""""""""""
+audioset notify
+"""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset notify
+
+**Description**
+
+Toggle track announcement and other bot messages.
+
+.. _audio-command-audioset-persistqueue:
+
+"""""""""""""""""""""
+audioset persistqueue
+"""""""""""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset persistqueue
+
+**Description**
+
+Toggle persistent queues. Persistent queues allows the current queue
+to be restored when the queue closes.
+
+.. _audio-command-audioset-restart:
+
+""""""""""""""""
+audioset restart
+""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restart
+
+**Description**
+
+Restarts the lavalink connection.
+
+.. _audio-command-audioset-restrict:
+
+"""""""""""""""""
+audioset restrict
+"""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrict
+
+**Description**
+
+Toggle the domain restriction on Audio.
+
+When toggled off, users will be able to play songs from non-commercial websites and links.
+When toggled on, users are restricted to YouTube, SoundCloud, Vimeo, Twitch, and
+Bandcamp links.
+
+.. _audio-command-audioset-restrictions:
+
+"""""""""""""""""""""
+audioset restrictions
+"""""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions
+
+**Description**
+
+Manages the keyword whitelist and blacklist.
+
+.. _audio-command-audioset-restrictions-blacklist:
+
+"""""""""""""""""""""""""""""""
+audioset restrictions blacklist
+"""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions blacklist
+
+**Description**
+
+Manages the keyword blacklist.
+
+.. _audio-command-audioset-restrictions-blacklist-add:
+
+"""""""""""""""""""""""""""""""""""
+audioset restrictions blacklist add
+"""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions blacklist add
+
+**Description**
+
+Adds a keyword to the blacklist.
+
+.. _audio-command-audioset-restrictions-blacklist-clear:
+
+"""""""""""""""""""""""""""""""""""""
+audioset restrictions blacklist clear
+"""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions blacklist clear
+
+**Description**
+
+Clear all keywords added to the blacklist.
+
+.. _audio-command-audioset-restrictions-blacklist-delete:
+
+""""""""""""""""""""""""""""""""""""""
+audioset restrictions blacklist delete
+""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions blacklist delete
+
+**Description**
+
+Removes a keyword from the blacklist.
+
+.. _audio-command-audioset-restrictions-blacklist-list:
+
+""""""""""""""""""""""""""""""""""""
+audioset restrictions blacklist list
+""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions blacklist list
+
+**Description**
+
+List all keywords added to the blacklist.
+
+.. _audio-command-audioset-restrictions-global:
+
+""""""""""""""""""""""""""""
+audioset restrictions global
+""""""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global
+
+**Description**
+
+Manages the global keyword whitelist/blacklist.
+
+.. _audio-command-audioset-restrictions-global-blacklist:
+
+""""""""""""""""""""""""""""""""""""""
+audioset restrictions global blacklist
+""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global blacklist
+
+**Description**
+
+Manages the global keyword blacklist.
+
+.. _audio-command-audioset-restrictions-global-blacklist-add:
+
+""""""""""""""""""""""""""""""""""""""""""
+audioset restrictions global blacklist add
+""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global blacklist add
+
+**Description**
+
+Adds a keyword to the blacklist.
+
+.. _audio-command-audioset-restrictions-global-blacklist-clear:
+
+""""""""""""""""""""""""""""""""""""""""""""
+audioset restrictions global blacklist clear
+""""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global blacklist clear
+
+**Description**
+
+Clear all keywords added to the blacklist.
+
+.. _audio-command-audioset-restrictions-global-blacklist-delete:
+
+"""""""""""""""""""""""""""""""""""""""""""""
+audioset restrictions global blacklist delete
+"""""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global blacklist delete
+
+**Description**
+
+Removes a keyword from the blacklist.
+
+.. _audio-command-audioset-restrictions-global-blacklist-list:
+
+"""""""""""""""""""""""""""""""""""""""""""
+audioset restrictions global blacklist list
+"""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global blacklist list
+
+**Description**
+
+List all keywords added to the blacklist.
+
+.. _audio-command-audioset-restrictions-global-whitelist:
+
+""""""""""""""""""""""""""""""""""""""
+audioset restrictions global whitelist
+""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global whitelist
+
+**Description**
+
+Manages the global keyword whitelist.
+
+.. _audio-command-audioset-restrictions-global-whitelist-add:
+
+""""""""""""""""""""""""""""""""""""""""""
+audioset restrictions global whitelist add
+""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global whitelist add
+
+**Description**
+
+Adds a keyword to the whitelist. If anything is added to whitelist,
+it will blacklist everything else.
+
+.. _audio-command-audioset-restrictions-global-whitelist-clear:
+
+""""""""""""""""""""""""""""""""""""""""""""
+audioset restrictions global whitelist clear
+""""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global whitelist clear
+
+**Description**
+
+Clear all keywords from the whitelist.
+
+.. _audio-command-audioset-restrictions-global-whitelist-delete:
+
+"""""""""""""""""""""""""""""""""""""""""""""
+audioset restrictions global whitelist delete
+"""""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global whitelist delete
+
+**Description**
+
+Removes a keyword from the whitelist.
+
+.. _audio-command-audioset-restrictions-global-whitelist-list:
+
+"""""""""""""""""""""""""""""""""""""""""""
+audioset restrictions global whitelist list
+"""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions global whitelist list
+
+**Description**
+
+List all keywords added to the whitelist.
+
+.. _audio-command-audioset-restrictions-whitelist:
+
+"""""""""""""""""""""""""""""""
+audioset restrictions whitelist
+"""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions whitelist
+
+**Description**
+
+Manages the keyword whitelist.
+
+.. _audio-command-audioset-restrictions-whitelist-add:
+
+"""""""""""""""""""""""""""""""""""
+audioset restrictions whitelist add
+"""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions whitelist add
+
+**Description**
+
+Adds a keyword to the whitelist. If anything is added to whitelist,
+it will blacklist everything else.
+
+.. _audio-command-audioset-restrictions-whitelist-clear:
+
+"""""""""""""""""""""""""""""""""""""
+audioset restrictions whitelist clear
+"""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions whitelist clear
+
+**Description**
+
+Clear all keywords from the whitelist.
+
+.. _audio-command-audioset-restrictions-whitelist-delete:
+
+""""""""""""""""""""""""""""""""""""""
+audioset restrictions whitelist delete
+""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions whitelist delete
+
+**Description**
+
+Removes a keyword from the whitelist.
+
+.. _audio-command-audioset-restrictions-whitelist-list:
+
+""""""""""""""""""""""""""""""""""""
+audioset restrictions whitelist list
+""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset restrictions whitelist list
+
+**Description**
+
+List all keywords added to the whitelist.
+
+.. _audio-command-audioset-role:
+
+"""""""""""""
+audioset role
+"""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset role
+
+**Description**
+
+Set the role to use for DJ mode.
+
+.. _audio-command-audioset-settings:
+
+"""""""""""""""""
+audioset settings
+"""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset settings
+
+**Description**
+
+Show the current settings.
+
+.. _audio-command-audioset-spotifyapi:
+
+"""""""""""""""""""
+audioset spotifyapi
+"""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset spotifyapi
+
+**Description**
+
+Instructions to set the Spotify API tokens.
+
+.. _audio-command-audioset-status:
+
+"""""""""""""""
+audioset status
+"""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset status
+
+**Description**
+
+Enable/disable tracks' titles as status.
+
+.. _audio-command-audioset-thumbnail:
+
+""""""""""""""""""
+audioset thumbnail
+""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset thumbnail
+
+**Description**
+
+Toggle displaying a thumbnail on audio messages.
+
+.. _audio-command-audioset-vote:
+
+"""""""""""""
+audioset vote
+"""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset vote
+
+**Description**
+
+Percentage needed for non-mods to skip tracks, 0 to disable.
+
+.. _audio-command-audioset-youtubeapi:
+
+"""""""""""""""""""
+audioset youtubeapi
+"""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audioset youtubeapi
+
+**Description**
+
+Instructions to set the YouTube API key.
+
+.. _audio-command-audiostats:
+
+^^^^^^^^^^
+audiostats
+^^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]audiostats
+
+**Description**
+
+Audio stats.
+
+.. _audio-command-autoplay:
+
+^^^^^^^^
+autoplay
+^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]autoplay
+
+**Description**
+
+Starts auto play.
+
+.. _audio-command-bump:
+
+^^^^
+bump
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]bump
+
+**Description**
+
+Bump a track number to the top of the queue.
+
+.. _audio-command-bumpplay:
+
+^^^^^^^^
+bumpplay
+^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]bumpplay [play_now=False]
+
+**Description**
+
+Force play a URL or search for a track.
+
+.. _audio-command-disconnect:
+
+^^^^^^^^^^
+disconnect
+^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]disconnect
+
+**Description**
+
+Disconnect from the voice channel.
+
+.. _audio-command-eq:
+
+^^
+eq
+^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]eq
+
+**Description**
+
+Equalizer management.
+
+Band positions are 1-15 and values have a range of -0.25 to 1.0.
+Band names are 25, 40, 63, 100, 160, 250, 400, 630, 1k, 1.6k, 2.5k, 4k,
+6.3k, 10k, and 16k Hz.
+Setting a band value to -0.25 nullifies it while +0.25 is double.
+
+.. _audio-command-eq-delete:
+
+"""""""""
+eq delete
+"""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]eq delete
+
+**Description**
+
+Delete a saved eq preset.
+
+.. _audio-command-eq-list:
+
+"""""""
+eq list
+"""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]eq list
+
+**Description**
+
+List saved eq presets.
+
+.. _audio-command-eq-load:
+
+"""""""
+eq load
+"""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]eq load
+
+**Description**
+
+Load a saved eq preset.
+
+.. _audio-command-eq-reset:
+
+""""""""
+eq reset
+""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]eq reset
+
+**Description**
+
+Reset the eq to 0 across all bands.
+
+.. _audio-command-eq-save:
+
+"""""""
+eq save
+"""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]eq save [eq_preset]
+
+**Description**
+
+Save the current eq settings to a preset.
+
+.. _audio-command-eq-set:
+
+""""""
+eq set
+""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]eq set
+
+**Description**
+
+Set an eq band with a band number or name and value.
+
+Band positions are 1-15 and values have a range of -0.25 to 1.0.
+Band names are 25, 40, 63, 100, 160, 250, 400, 630, 1k, 1.6k, 2.5k, 4k,
+6.3k, 10k, and 16k Hz.
+Setting a band value to -0.25 nullifies it while +0.25 is double.
+
+.. _audio-command-genre:
+
+^^^^^
+genre
+^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]genre
+
+**Description**
+
+Pick a Spotify playlist from a list of categories to start playing.
+
+.. _audio-command-local:
+
+^^^^^
+local
+^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]local
+
+**Description**
+
+Local playback commands.
+
+.. _audio-command-local-folder:
+
+""""""""""""
+local folder
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]local folder [folder]
+
+**Description**
+
+Play all songs in a localtracks folder.
+
+**Example usage**
+
+* ``[p]local folder`` - Open a menu to pick a folder to queue.
+* ``[p]local folder folder_name`` - Queues all of the tracks inside the folder_name folder.
+
+.. _audio-command-local-play:
+
+""""""""""
+local play
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]local play
+
+**Description**
+
+Play a local track.
+
+To play a local track, either use the menu to choose a track or enter in the track path directly
+with the play command. To play an entire folder, use ``[p]help local folder`` for instructions.
+
+**Example usage**
+
+* ``[p]local play`` - Open a menu to pick a track.
+* ``[p]play localtracks\album_folder\song_name.mp3``
+* ``[p]play album_folder\song_name.mp3`` - Use a direct link relative to the localtracks folder.
+
+.. _audio-command-local-search:
+
+""""""""""""
+local search
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]local search
+
+**Description**
+
+Search for songs across all localtracks folders.
+
+.. _audio-command-now:
+
+^^^
+now
+^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]now
+
+**Description**
+
+Now playing.
+
+.. _audio-command-pause:
+
+^^^^^
+pause
+^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]pause
+
+**Description**
+
+Pause or resume a playing track.
+
+.. _audio-command-percent:
+
+^^^^^^^
+percent
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]percent
+
+**Description**
+
+Queue percentage.
+
+.. _audio-command-play:
+
+^^^^
+play
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]play
+
+**Description**
+
+Play the specified track or search for a close match.
+
+To play a local track, the query should be ``\``.
+If you are the bot owner, use ``[p]audioset info`` to display your localtracks path.
+
+.. _audio-command-playlist:
+
+^^^^^^^^
+playlist
+^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist
+
+**Description**
+
+Playlist configuration options.
+
+**Scope information**
+
+* Global: Visible to all users of this bot. Only editable by bot owner.
+* Guild: Visible to all users in this guild. Editable by bot owner, guild owner,
+ guild admins, guild mods, DJ role and playlist creator.
+* User: Visible to all bot users, if ``--author`` is passed. Editable by bot owner and playlist creator.
+
+.. _audio-command-playlist-append:
+
+"""""""""""""""
+playlist append
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist append [args]
+
+**Description**
+
+Add a track URL, playlist link, or quick search to a playlist. The track(s) will be
+appended to the end of the playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist append MyGuildPlaylist Hello by Adele``
+* ``[p]playlist append MyGlobalPlaylist Hello by Adele --scope Global``
+* ``[p]playlist append MyGlobalPlaylist Hello by Adele --scope Global --Author Draper#6666``
+
+.. _audio-command-playlist-copy:
+
+"""""""""""""
+playlist copy
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist copy [args]
+
+**Description**
+
+Copy a playlist from one scope to another.
+
+**Args**
+
+The following are all optional:
+
+* --from-scope
+* --from-author [user]
+* --from-guild [guild] (**only the bot owner can use this**)
+* --to-scope
+* --to-author [user]
+* --to-guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist copy MyGuildPlaylist --from-scope Guild --to-scope Global``
+* ``[p]playlist copy MyGlobalPlaylist --from-scope Global --to-author Draper#6666 --to-scope User``
+* ``[p]playlist copy MyPersonalPlaylist --from-scope user --to-author Draper#6666 --to-scope Guild --to-guild Red - Discord Bot``
+
+.. _audio-command-playlist-create:
+
+"""""""""""""""
+playlist create
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist create [args]
+
+**Description**
+
+Create an empty playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist create MyGuildPlaylist``
+* ``[p]playlist create MyGlobalPlaylist --scope Global``
+* ``[p]playlist create MyPersonalPlaylist --scope User``
+
+.. _audio-command-playlist-dedupe:
+
+"""""""""""""""
+playlist dedupe
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist dedupe [args]
+
+**Description**
+
+Remove duplicate tracks from a saved playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist dedupe MyGuildPlaylist``
+* ``[p]playlist dedupe MyGlobalPlaylist --scope Global``
+* ``[p]playlist dedupe MyPersonalPlaylist --scope User``
+
+.. _audio-command-playlist-delete:
+
+"""""""""""""""
+playlist delete
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist delete [args]
+
+**Description**
+
+Delete a saved playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist delete MyGuildPlaylist``
+* ``[p]playlist delete MyGlobalPlaylist --scope Global``
+* ``[p]playlist delete MyPersonalPlaylist --scope User``
+
+.. _audio-command-playlist-download:
+
+"""""""""""""""""
+playlist download
+"""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist download [v2=False] [args]
+
+**Description**
+
+Download a copy of a playlist.
+
+These files can be used with the ``[p]playlist upload`` command.
+Red v2-compatible playlists can be generated by passing True
+for the v2 variable.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist download MyGuildPlaylist True``
+* ``[p]playlist download MyGlobalPlaylist False --scope Global``
+* ``[p]playlist download MyPersonalPlaylist --scope User``
+
+.. _audio-command-playlist-info:
+
+"""""""""""""
+playlist info
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist info [args]
+
+**Description**
+
+Retrieve information from a saved playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist info MyGuildPlaylist``
+* ``[p]playlist info MyGlobalPlaylist --scope Global``
+* ``[p]playlist info MyPersonalPlaylist --scope User``
+
+.. _audio-command-playlist-list:
+
+"""""""""""""
+playlist list
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist list [args]
+
+**Description**
+
+List saved playlists.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist list``
+* ``[p]playlist list --scope Global``
+* ``[p]playlist list --scope User``
+
+.. _audio-command-playlist-queue:
+
+""""""""""""""
+playlist queue
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist queue [args]
+
+**Description**
+
+Save the queue to a playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist queue MyGuildPlaylist``
+* ``[p]playlist queue MyGlobalPlaylist --scope Global``
+* ``[p]playlist queue MyPersonalPlaylist --scope User``
+
+.. _audio-command-playlist-remove:
+
+"""""""""""""""
+playlist remove
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist remove [args]
+
+**Description**
+
+Remove a track from a playlist by URL.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist remove MyGuildPlaylist https://www.youtube.com/watch?v=MN3x-kAbgFU``
+* ``[p]playlist remove MyGlobalPlaylist https://www.youtube.com/watch?v=MN3x-kAbgFU --scope Global``
+* ``[p]playlist remove MyPersonalPlaylist https://www.youtube.com/watch?v=MN3x-kAbgFU --scope User``
+
+.. _audio-command-playlist-rename:
+
+"""""""""""""""
+playlist rename
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist rename [args]
+
+**Description**
+
+Rename an existing playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist rename MyGuildPlaylist RenamedGuildPlaylist``
+* ``[p]playlist rename MyGlobalPlaylist RenamedGlobalPlaylist --scope Global``
+* ``[p]playlist rename MyPersonalPlaylist RenamedPersonalPlaylist --scope User``
+
+.. _audio-command-playlist-save:
+
+"""""""""""""
+playlist save
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist save [args]
+
+**Description**
+
+Save a playlist from a URL.
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist save MyGuildPlaylist https://www.youtube.com/playlist?list=PLx0sYbCqOb8Q_CLZC2BdBSKEEB59BOPUM``
+* ``[p]playlist save MyGlobalPlaylist https://www.youtube.com/playlist?list=PLx0sYbCqOb8Q_CLZC2BdBSKEEB59BOPUM --scope Global``
+* ``[p]playlist save MyPersonalPlaylist https://open.spotify.com/playlist/1RyeIbyFeIJVnNzlGr5KkR --scope User``
+
+.. _audio-command-playlist-start:
+
+""""""""""""""
+playlist start
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist start [args]
+
+**Description**
+
+Load a playlist into the queue.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist start MyGuildPlaylist``
+* ``[p]playlist start MyGlobalPlaylist --scope Global``
+* ``[p]playlist start MyPersonalPlaylist --scope User``
+
+.. _audio-command-playlist-update:
+
+"""""""""""""""
+playlist update
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist update [args]
+
+**Description**
+
+Updates all tracks in a playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist update MyGuildPlaylist``
+* ``[p]playlist update MyGlobalPlaylist --scope Global``
+* ``[p]playlist update MyPersonalPlaylist --scope User``
+
+.. _audio-command-playlist-upload:
+
+"""""""""""""""
+playlist upload
+"""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]playlist upload [args]
+
+**Description**
+
+Uploads a playlist file as a playlist for the bot.
+
+V2 and old V3 playlist will be slow.
+V3 Playlist made with ``[p]playlist download`` will load a lot faster.
+
+**Args**
+
+The following are all optional:
+
+* --scope
+* --author [user]
+* --guild [guild] (**only the bot owner can use this**)
+
+**Scope** is one of the following:
+
+* Global
+* Guild
+* User
+
+**Author** can be one of the following:
+
+* User ID
+* User Mention
+* User Name#123
+
+**Guild** can be one of the following:
+
+* Guild ID
+* Exact guild name
+
+**Example usage**
+
+* ``[p]playlist upload``
+* ``[p]playlist upload --scope Global``
+* ``[p]playlist upload --scope User``
+
+.. _audio-command-prev:
+
+^^^^
+prev
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]prev
+
+**Description**
+
+Skip to the start of the previously played track.
+
+.. _audio-command-queue:
+
+^^^^^
+queue
+^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]queue [page=1]
+
+**Description**
+
+List the songs in the queue.
+
+.. _audio-command-queue-clean:
+
+"""""""""""
+queue clean
+"""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]queue clean
+
+**Description**
+
+Removes songs from the queue if the requester is not in the voice channel.
+
+.. _audio-command-queue-cleanself:
+
+"""""""""""""""
+queue cleanself
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]queue cleanself
+
+**Description**
+
+Removes all tracks you requested from the queue.
+
+.. _audio-command-queue-clear:
+
+"""""""""""
+queue clear
+"""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]queue clear
+
+**Description**
+
+Clears the queue.
+
+.. _audio-command-queue-search:
+
+""""""""""""
+queue search
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]queue search
+
+**Description**
+
+Search the queue.
+
+.. _audio-command-queue-shuffle:
+
+"""""""""""""
+queue shuffle
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]queue shuffle
+
+**Description**
+
+Shuffles the queue.
+
+.. _audio-command-remove:
+
+^^^^^^
+remove
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]remove
+
+**Description**
+
+Remove a specific track number from the queue.
+
+.. _audio-command-repeat:
+
+^^^^^^
+repeat
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]repeat
+
+**Description**
+
+Toggle repeat.
+
+.. _audio-command-search:
+
+^^^^^^
+search
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]search
+
+**Description**
+
+Pick a track with a search.
+
+Use ``[p]search list `` to queue all tracks found on YouTube. Use ``[p]search sc
+`` to search on SoundCloud instead of YouTube.
+
+.. _audio-command-seek:
+
+^^^^
+seek
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]seek
+
+**Description**
+
+Seek ahead or behind on a track by seconds or to a specific time. Accepts seconds or
+a value formatted like 00:00:00 (``hh:mm:ss``) or 00:00 (``mm:ss``).
+
+.. _audio-command-shuffle:
+
+^^^^^^^
+shuffle
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]shuffle
+
+**Description**
+
+Toggle shuffle.
+
+.. _audio-command-shuffle-bumped:
+
+""""""""""""""
+shuffle bumped
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]shuffle bumped
+
+**Description**
+
+Toggle bumped track shuffle.
+
+Set this to disabled if you wish to avoid bumped songs being shuffled. This takes priority
+over ``[p]shuffle``.
+
+.. _audio-command-sing:
+
+^^^^
+sing
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]sing
+
+**Description**
+
+Make Red sing one of her songs.
+
+.. _audio-command-skip:
+
+^^^^
+skip
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]skip [skip_to_track]
+
+**Description**
+
+Skip to the next track, or to a given track number.
+
+.. _audio-command-stop:
+
+^^^^
+stop
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]stop
+
+**Description**
+
+Stop playback and clear the queue.
+
+.. _audio-command-summon:
+
+^^^^^^
+summon
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]summon
+
+**Description**
+
+Summon the bot to a voice channel.
+
+.. _audio-command-volume:
+
+^^^^^^
+volume
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]volume [vol]
+
+**Description**
+
+Set the volume, 1% - 150%.
+
+.. _llset-commands:
+
+-----------------------
+Lavalink Setup Commands
+-----------------------
+
+``[p]llset`` group commands are used for advanced management of the connection to the Lavalink
+server. The subcommands are dynamically available depending on whether Red is managing your
+Lavalink node or if you are connecting to one you manage yourself, or a service that offers Lavalink
+nodes.
+
+Commands specifically for managed Lavalink nodes can be found in :ref:`this section`,
+whilst commands for unmanaged Lavalink nodes can be found :ref:`here`.
+
+.. _audio-command-llset:
+
+^^^^^
+llset
+^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset
+
+**Description**
+
+Manage Lavalink node configuration settings. This command holds all commands to
+manage an unmanaged (user-managed) or managed (bot-managed) Lavalink node.
+
+.. warning::
+
+ You should not change any command settings in this group command unless you
+ have a valid reason to, e.g. been told by someone in the Red-Discord Bot support
+ server to do so. Changing llset command settings have the potential to break
+ Audio cog connection and playback if the wrong settings are used.
+
+"""""""""""""""
+llset unmanaged
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset unmanaged
+
+or
+
+.. code-block:: none
+
+ [p]llsetup unmanaged
+
+**Description**
+
+Toggle using unmanaged (user-managed) Lavalink nodes - requires an existing Lavalink
+node for Audio to work, if enabled. This command disables the managed (bot-managed)
+Lavalink server: if you do not have an unmanaged Lavalink node set up, you will be
+unable to use Audio while this is enabled.
+
+""""""""""
+llset info
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset info
+
+**Description**
+
+Display Lavalink connection settings.
+
+"""""""""""
+llset reset
+"""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset reset
+
+**Description**
+
+Reset all ``[p]llset`` changes back to their default values.
+
+.. _managed-node-management-commands:
+
+--------------------------------
+Managed Node Management Commands
+--------------------------------
+
+.. _audio-command-llset-config:
+
+^^^^^^^^^^^^
+llset config
+^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config
+
+**Description**
+
+Configure the managed Lavalink node runtime options.
+
+All settings under this group will likely cause Audio to malfunction if changed
+from their defaults, only change settings here if you have been advised to by #support.
+
+.. _audio-command-llset-config-bind:
+
+^^^^^^^^^^^^^^^^^
+llset config bind
+^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config bind [host=localhost]
+
+**Description**
+
+Set the managed Lavalink node's binding IP address.
+
+**Arguments**
+
+* ``[host]``: The node's binding IP address, defaulting to "localhost".
+
+.. _audio-command-llset-config-port:
+
+^^^^^^^^^^^^^^^^^
+llset config port
+^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config port [port=2333]
+
+**Description**
+
+Set the managed Lavalink node's connection port.
+
+This port is the port the managed Lavalink node binds to, you should
+only change this if there is a conflict with the default port because
+you already have an application using port 2333 on this device.
+
+**Arguments**
+
+* ``[port]``: The node's connection port, defaulting to 2333.
+
+.. _audio-command-llset-config-server:
+
+^^^^^^^^^^^^^^^^^^^
+llset config server
+^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config server
+
+**Description**
+
+Configure the managed node authorization and connection settings.
+
+.. _audio-command-llset-config-server-buffer:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+llset config server buffer
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config server buffer [milliseconds=400]
+
+**Description**
+
+Set the managed Lavalink node JDA-NAS buffer size. Only
+change this if you have been directly advised to,
+changing it can cause significant playback issues.
+
+**Arguments**
+
+* ``[milliseconds]`` - The buffer size, defaults to 400.
+
+.. _audio-command-llset-config-server-framebuffer:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+llset config server framebuffer
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config server framebuffer [milliseconds=1000]
+
+**Description**
+
+Set the managed Lavalink node framebuffer size. Only
+change this if you have been directly advised to,
+changing it can cause significant playback issues.
+
+**Arguments**
+
+* ``[milliseconds]`` - The framebuffer size, defaults to 1000.
+
+.. _audio-command-llset-config-source:
+
+^^^^^^^^^^^^^^^^^^^
+llset config source
+^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config source
+
+**Description**
+
+Toggle audio sources on/off.
+
+By default, all sources are enabled, you should only use commands here to
+disable a specific source if you have been advised to, disabling sources
+without background knowledge can cause Audio to break.
+
+.. _audio-command-llset-config-source-bandcamp:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+llset config source bandcamp
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config source bandcamp
+
+**Description**
+
+Toggle Bandcamp source on or off. This toggle controls the playback
+of all Bandcamp related content.
+
+.. _audio-command-llset-config-source-http:
+
+^^^^^^^^^^^^^^^^^^^^^^^^
+llset config source http
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config source http
+
+**Description**
+
+Toggle HTTP direct URL usage on or off. This source is used to
+allow playback from direct HTTP streams (this does not affect direct URL
+playback for the other sources).
+
+.. _audio-command-llset-config-source-local:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^
+llset config source local
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config source local
+
+**Description**
+
+Toggle local file usage on or off.
+This toggle controls the playback of all local track content,
+usually found inside the ``localtracks`` folder.
+
+.. _audio-command-llset-config-source-soundcloud:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+llset config source soundcloud
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config source soundcloud
+
+**Description**
+
+Toggle SoundCloud source on or off.
+This toggle controls the playback of all SoundCloud related content.
+
+.. _audio-command-llset-config-source-twitch:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+llset config source twitch
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config source twitch
+
+**Description**
+
+Toggle Twitch source on or off.
+This toggle controls the playback of all Twitch related content.
+
+.. _audio-command-llset-config-source-vimeo:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^
+llset config source vimeo
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config source vimeo
+
+**Description**
+
+Toggle Vimeo source on or off.
+This toggle controls the playback of all Vimeo related content.
+
+.. _audio-command-llset-config-source-youtube:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+llset config source youtube
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config source youtube
+
+**Description**
+
+Toggle YouTube source on or off (**this includes Spotify**).
+This toggle controls the playback of all YouTube and Spotify related content.
+
+.. _audio-command-llset-config-token:
+
+^^^^^^^^^^^^^^^^^^
+llset config token
+^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset config token [password=youshallnotpass]
+
+**Description**
+
+Set the managed Lavalink node's connection password.
+This is the password required for Audio to connect to the managed Lavalink node.
+The value by default is ``youshallnotpass``.
+
+**Arguments**
+
+* ``[password]`` - The node's connection password, defaulting to ``youshallnotpass``.
+
+.. _audio-command-llset-heapsize:
+
+^^^^^^^^^^^^^^
+llset heapsize
+^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset heapsize [size=3G]
+
+**Description**
+
+Set the managed Lavalink node maximum heap-size.
+
+By default, this value is 50% of available RAM in the host machine
+represented by [1-1024][M|G] (256M, 256G for example).
+
+This value only represents the maximum amount of RAM allowed to be
+used at any given point, and does not mean that the managed Lavalink
+node will always use this amount of RAM.
+
+**Arguments**
+
+* ``[size]`` - The node's maximum heap-size, defaulting to ``3G``.
+
+.. _audio-command-llset-java:
+
+^^^^^^^^^^
+llset java
+^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset java [javapath]
+
+**Description**
+
+Change your Java executable path.
+
+This command shouldn't need to be used most of the time,
+and is only useful if the host machine has conflicting Java versions.
+
+If changing this make sure that the Java executable you set is supported by Audio.
+The current supported version is Java 11.
+
+**Arguments**
+
+* ``[java]`` - The java executable path, leave blank to reset it back to default.
+
+.. _audio-command-llset-yaml:
+
+^^^^^^^^^^
+llset yaml
+^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset yaml
+
+**Description**
+
+Uploads a copy of the application.yml file used by the managed Lavalink node.
+
+.. _unmanaged-node-management-commands:
+
+----------------------------------
+Unmanaged Node Management Commands
+----------------------------------
+
+.. note::
+
+ A normal Red user should never have to use these commands unless they are :ref:`managing multiple Red bots with Audio`.
+
+.. _audio-command-llset-host:
+
+^^^^^^^^^^
+llset host
+^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset host [host=localhost]
+
+**Description**
+
+Set the Lavalink node host. This command sets the connection host which
+Audio will use to connect to an unmanaged Lavalink node.
+
+**Arguments**
+
+* ``[host]`` - The connection host, defaulting to "localhost".
+
+.. _audio-command-llset-password:
+
+^^^^^^^^^^^^^^
+llset password
+^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset password [password=youshallnotpass]
+
+**Description**
+
+Set the Lavalink node password. This command sets the connection password which
+Audio will use to connect to an unmanaged Lavalink node.
+
+**Arguments**
+
+* ``[password]`` - The connection password, defaulting to "youshallnotpass".
+
+.. _audio-command-llset-port:
+
+^^^^^^^^^^
+llset port
+^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset port [port=2333]
+
+**Description**
+
+Set the Lavalink node port. This command sets the connection port which
+Audio will use to connect to an unmanaged Lavalink node.
+
+**Arguments**
+
+* ``[password]`` - The connection password, defaulting to 2333.
+
+.. _audio-command-llset-secured:
+
+^^^^^^^^^^^^^
+llset secured
+^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]llset secured
+
+**Description**
+
+Set the Lavalink node connection to secured. This toggle sets the connection type
+to secured or unsecured when connecting to an unmanaged Lavalink node.
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/cleanup.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/cleanup.rst
new file mode 100644
index 0000000000000000000000000000000000000000..edc0fd468e346f660d5c95555922f87911feeb0e
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/cleanup.rst
@@ -0,0 +1,333 @@
+.. _cleanup:
+
+=======
+Cleanup
+=======
+
+This is the cog guide for the cleanup cog. You will
+find detailed docs about usage and commands.
+
+``[p]`` is considered as your prefix.
+
+.. note:: To use this cog, load it by typing this::
+
+ [p]load cleanup
+
+.. _cleanup-usage:
+
+-----
+Usage
+-----
+
+This cog contains commands used for "cleaning up" (deleting) messages.
+
+This is designed as a moderator tool and offers many convenient use cases.
+All cleanup commands only apply to the channel the command is executed in.
+
+Messages older than two weeks cannot be mass deleted.
+This is a limitation of the API.
+
+
+.. _cleanup-commands:
+
+--------
+Commands
+--------
+
+.. _cleanup-command-cleanup:
+
+^^^^^^^
+cleanup
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanup
+
+**Description**
+
+Base command for deleting messages.
+
+.. _cleanup-command-cleanup-after:
+
+"""""""""""""
+cleanup after
+"""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanup after [delete_pinned=False]
+
+**Description**
+
+Delete all messages after a specified message.
+
+To get a message id, enable developer mode in Discord's
+settings, 'appearance' tab. Then right click a message
+and copy its id.
+
+**Arguments:**
+
+- ```` The id of the message to cleanup after. This message won't be deleted.
+- ```` Whether to delete pinned messages or not. Defaults to False
+
+.. _cleanup-command-cleanup-before:
+
+""""""""""""""
+cleanup before
+""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanup before [delete_pinned=False]
+
+**Description**
+
+Deletes X messages before the specified message.
+
+To get a message id, enable developer mode in Discord's
+settings, 'appearance' tab. Then right click a message
+and copy its id.
+
+**Arguments:**
+
+- ```` The id of the message to cleanup before. This message won't be deleted.
+- ```` The max number of messages to cleanup. Must be a positive integer.
+- ```` Whether to delete pinned messages or not. Defaults to False
+
+.. _cleanup-command-cleanup-between:
+
+"""""""""""""""
+cleanup between
+"""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanup between [delete_pinned=False]
+
+**Description**
+
+Delete the messages between Message One and Message Two, providing the messages IDs.
+
+The first message ID should be the older message and the second one the newer.
+
+Example:
+ - ``[p]cleanup between 123456789123456789 987654321987654321``
+
+**Arguments:**
+
+- ```` The id of the message to cleanup after. This message won't be deleted.
+- ```` The id of the message to cleanup before. This message won't be deleted.
+- ```` Whether to delete pinned messages or not. Defaults to False
+
+.. _cleanup-command-cleanup-bot:
+
+"""""""""""
+cleanup bot
+"""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanup bot [delete_pinned=False]
+
+**Description**
+
+Clean up command messages and messages from the bot in the current channel.
+
+Can only cleanup custom commands and alias commands if those cogs are loaded.
+
+**Arguments:**
+
+- ```` The max number of messages to cleanup. Must be a positive integer.
+- ```` Whether to delete pinned messages or not. Defaults to False
+
+.. _cleanup-command-cleanup-messages:
+
+""""""""""""""""
+cleanup messages
+""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanup messages [delete_pinned=False]
+
+**Description**
+
+Delete the last X messages in the current channel.
+
+Example:
+ - ``[p]cleanup messages 26``
+
+**Arguments:**
+
+- ```` The max number of messages to cleanup. Must be a positive integer.
+- ```` Whether to delete pinned messages or not. Defaults to False
+
+.. _cleanup-command-cleanup-self:
+
+""""""""""""
+cleanup self
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanup self [match_pattern] [delete_pinned=False]
+
+**Description**
+
+Clean up messages owned by the bot in the current channel.
+
+By default, all messages are cleaned. If a second argument is specified,
+it is used for pattern matching - only messages containing the given text will be deleted.
+
+Examples:
+ - ``[p]cleanup self 6``
+ - ``[p]cleanup self 10 Pong``
+ - ``[p]cleanup self 7 "" True``
+
+**Arguments:**
+
+- ```` The max number of messages to cleanup. Must be a positive integer.
+- ```` The text that messages must contain to be deleted. Use "" to skip this.
+- ```` Whether to delete pinned messages or not. Defaults to False
+
+.. _cleanup-command-cleanup-spam:
+
+""""""""""""
+cleanup spam
+""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanup spam [number=50]
+
+**Description**
+
+Deletes duplicate messages in the channel from the last X messages and keeps only one copy.
+
+Defaults to 50.
+
+**Arguments:**
+
+- ```` The number of messages to check for duplicates. Must be a positive integer.
+
+.. _cleanup-command-cleanup-text:
+
+""""""""""""
+cleanup text
+""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanup text [delete_pinned=False]
+
+**Description**
+
+Delete the last X messages matching the specified text in the current channel.
+
+Example:
+ - ``[p]cleanup text "test" 5``
+
+Remember to use double quotes.
+
+**Arguments:**
+
+- ```` The max number of messages to cleanup. Must be a positive integer.
+- ```` Whether to delete pinned messages or not. Defaults to False
+
+.. _cleanup-command-cleanup-user:
+
+""""""""""""
+cleanup user
+""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanup user [delete_pinned=False]
+
+**Description**
+
+Delete the last X messages from a specified user in the current channel.
+
+Examples:
+ - ``[p]cleanup user @Twentysix 2``
+ - ``[p]cleanup user Red 6``
+
+**Arguments:**
+
+- ```` The user whose messages are to be cleaned up.
+- ```` The max number of messages to cleanup. Must be a positive integer.
+- ```` Whether to delete pinned messages or not. Defaults to False
+
+.. _cleanup-command-cleanupset:
+
+^^^^^^^^^^
+cleanupset
+^^^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanupset
+
+**Description**
+
+Manage the settings for the cleanup command.
+
+.. _cleanup-command-cleanupset-notify:
+
+"""""""""""""""""
+cleanupset notify
+"""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cleanupset notify
+
+**Description**
+
+Toggle clean up notification settings.
+
+When enabled, a message will be sent per cleanup, showing how many messages were deleted.
+This message will be deleted after 5 seconds.
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/cog_manager_ui.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/cog_manager_ui.rst
new file mode 100644
index 0000000000000000000000000000000000000000..f6f8979dbbb995e3d5ee1dc867cb6759d06d5f41
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/cog_manager_ui.rst
@@ -0,0 +1,251 @@
+.. _cogmanagerui:
+
+==============
+Cog Manager UI
+==============
+
+This is the cog guide for the core cog. You will
+find detailed docs about usage and commands.
+
+``[p]`` is considered as your prefix.
+
+.. note:: This cog is not like the other cogs. It is loaded by default, not
+ included in the cogs paths and it cannot be unloaded. It contains needed
+ commands for cog management.
+
+.. _cogmanagerui-usage:
+
+-----
+Usage
+-----
+
+This cog allows you to manage your cogs and where you can install them. Unlike
+V2, which had a ``cogs`` folder where everything was installed, you can
+install V3 cogs everywhere, and also make them cross-compatible with other
+instances!
+
+If you want to install your cogs using a Github repo (usually what you will
+always be looking for), you need to use the downloader cog. However, if you
+have the files of a cog or want to code one, this cog is what you should be
+looking for.
+
+The most basic command is :ref:`paths `, which
+will list you all of the currently set paths.
+
+You can add a path by using the :ref:`addpath `
+command. All cogs in that path will be available for the bot and listed in
+the :ref:`cogs `. You can then load
+or unload them.
+
+.. TODO add ref to load and unload commands
+
+.. _cogmanagerui-usage-installation:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+How to install a local package without using downloader
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Let's suppose you made a cog request on the `cog board `_
+and now you want to add your own cog to Red. You should have a folder that
+looks like this:
+
+.. image:: ../.resources/cog_manager_ui/custom-cog-example.png
+
+You will first need to add a cog path to your instance. For that, use the
+:ref:`addpath ` command with a new directory.
+
+Create a folder somewhere (should stay accessible) and copy its path. A path
+looks like this:
+
+* Windows: ``C:\Users\username\Documents\MyCogs``
+* macOS: ``/Users/username/Documents/MyCogs``
+* Linux: ``/home/username/Documents/MyCogs``
+
+You can now use the command we talked about before: type ``[p]addpath
+``.
+
+.. attention:: A path shouldn't have spaces in it. If it does, add quotation
+ marks around the path, or a backslash before the space.
+
+In that ``MyCogs`` folder, you can drop your cog folder. You should now have
+something that looks like this:
+
+.. image:: ../.resources/cog_manager_ui/cog-path.png
+
+Now if you type ``[p]cogs``, your new cog should be listed, and you will be
+able to load it!
+
+.. _cogmanagerui-commands:
+
+--------
+Commands
+--------
+
+.. note:: The whole cog is locked to the
+ :ref:`bot owner `. If you are not the owner
+ of the instance, you can ignore this.
+
+.. _cogmanagerui-command-cogs:
+
+^^^^
+cogs
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]cogs
+
+**Description**
+
+Returns a list of loaded and unloaded cogs on the bot.
+
+Cogs are unloaded by default. This is where you can find your cogs if you
+installed some recently.
+
+All of the cogs located inside a cog path will be listed here. You can see a
+list of the paths with the :ref:`paths ` command.
+
+.. _cogmanagerui-command-paths:
+
+^^^^^
+paths
+^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]paths
+
+**Description**
+
+Lists the registered cog paths, with the install path for the downloader and
+the core path for the core cogs.
+
+.. TODO add ref to downloader
+
+You can use the :ref:`reorderpath ` command
+to reorder the listed paths.
+
+.. tip:: The number before a cog path can be used for the
+ :ref:`removepath ` command.
+
+.. _cogmanagerui-command-addpath:
+
+^^^^^^^
+addpath
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]addpath
+
+**Description**
+
+Adds a path to the list of available cog paths. This means that all valid cogs
+under the path will be added to the list of available cogs, listed in
+:ref:`cogs `.
+
+**Arguments**
+
+* ````: A path that should look like this and point to a folder:
+
+ * Windows: ``C:\Users\username\Documents\MyCogs``
+ * macOS: ``/Users/username/Documents/MyCogs``
+ * Linux: ``/home/username/Documents/MyCogs``
+
+ Try to avoid paths with spaces. If there are spaces, add a backslash before
+ the space on Linux. Add quotation marks around the path if needed.
+
+.. _cogmanagerui-command-removepath:
+
+^^^^^^^^^^
+removepath
+^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]removepath
+
+**Description**
+
+Removes one or more paths from the list of available paths. Its cogs won't be
+accessible anymore.
+
+**Arguments**
+
+* ````: The number of the path(s) to remove. You can get it with
+ the :ref:`paths ` command.
+
+.. _cogmanagerui-command-reorderpath:
+
+^^^^^^^^^^^
+reorderpath
+^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]reorderpath
+
+**Description**
+
+Reorders the paths listed with the :ref:`paths `
+command. The goal of this command is to allow the discovery of different cogs.
+If there are multiple packages with the same names, the one that is inside the
+highest folder in the list will be kept and the other ones will be ignored.
+
+For example, let's suppose this is the output of
+:ref:`paths `:
+
+ 1. ``/usr/local/lib/python3.7/site-packages/redbot/cogs``
+ 2. ``/home/laggron/custom_cogs``
+ 3. ``/mnt/not_suspicious_usb_drive/not_suspicious_cogs``
+
+The folders 2 and 3 both have a package named ``leveler`` while being different
+cogs, and you want to load the one located in the 3rd folder. To do that, you
+have to put the 3rd path higher than the 2nd path, let's swap them! Type
+``[p]reorderpath 2 3`` and the output of
+:ref:`paths ` will then be the following:
+
+ 1. ``/usr/local/lib/python3.7/site-packages/redbot/cogs``
+ 2. ``/mnt/not_suspicious_usb_drive/not_suspicious_cogs``
+ 3. ``/home/laggron/custom_cogs``
+
+**Arguments**
+
+* ````: The index of the path you want to move.
+* ````: The location where you want to insert the path.
+
+.. _cogmanagerui-command-installpath:
+
+^^^^^^^^^^^
+installpath
+^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]installpath [path]
+
+**Description**
+
+Shows the install path, or sets a new one.
+
+If you want to set a new path, the same rules as for
+:ref:`addpath ` apply
+
+.. warning:: If you edit the install path, the cogs won't be transferred.
+
+**Arguments**
+
+* ``[path]``: The absolute path to set. If omitted, the current path will
+ be returned instead.
diff --git a/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/core.rst b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/core.rst
new file mode 100644
index 0000000000000000000000000000000000000000..1a66dfef5740a8c7c13a40e3a84bcc9c65a0098b
--- /dev/null
+++ b/testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/core.rst
@@ -0,0 +1,4340 @@
+.. _core:
+
+====
+Core
+====
+
+This is the cog guide for the core cog. You will
+find detailed docs about usage and commands.
+
+``[p]`` is considered as your prefix.
+
+.. _core-usage:
+
+-----
+Usage
+-----
+
+The Core cog has many commands related to core functions.
+
+These commands come loaded with every Red bot, and cover some of the most basic usage of the bot.
+
+
+.. _core-commands:
+
+--------
+Commands
+--------
+
+.. _core-command-allowlist:
+
+^^^^^^^^^
+allowlist
+^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]allowlist
+
+.. tip:: Alias: ``whitelist``
+
+**Description**
+
+Commands to manage the allowlist.
+
+.. Warning:: When the allowlist is in use, the bot will ignore commands from everyone not on the list.
+
+
+Use ``[p]allowlist clear`` to disable the allowlist
+
+.. _core-command-allowlist-add:
+
+"""""""""""""
+allowlist add
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]allowlist add
+
+**Description**
+
+Adds users to the allowlist.
+
+**Examples:**
+ - ``[p]allowlist add @26 @Will`` - Adds two users to the allowlist.
+ - ``[p]allowlist add 262626262626262626`` - Adds a user by ID.
+
+**Arguments:**
+ - ```` - The user or users to add to the allowlist.
+
+.. _core-command-allowlist-clear:
+
+"""""""""""""""
+allowlist clear
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]allowlist clear
+
+**Description**
+
+Clears the allowlist.
+
+This disables the allowlist.
+
+**Example:**
+ - ``[p]allowlist clear``
+
+.. _core-command-allowlist-list:
+
+""""""""""""""
+allowlist list
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]allowlist list
+
+**Description**
+
+Lists users on the allowlist.
+
+**Example:**
+ - ``[p]allowlist list``
+
+.. _core-command-allowlist-remove:
+
+""""""""""""""""
+allowlist remove
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]allowlist remove
+
+**Description**
+
+Removes users from the allowlist.
+
+The allowlist will be disabled if all users are removed.
+
+**Examples:**
+ - ``[p]allowlist remove @26 @Will`` - Removes two users from the allowlist.
+ - ``[p]allowlist remove 262626262626262626`` - Removes a user by ID.
+
+**Arguments:**
+ - ```` - The user or users to remove from the allowlist.
+
+.. _core-command-autoimmune:
+
+^^^^^^^^^^
+autoimmune
+^^^^^^^^^^
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]autoimmune
+
+**Description**
+
+Commands to manage server settings for immunity from automated actions.
+
+This includes duplicate message deletion and mention spam from the Mod cog, and filters from the Filter cog.
+
+.. _core-command-autoimmune-add:
+
+""""""""""""""
+autoimmune add
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]autoimmune add
+
+**Description**
+
+Makes a user or role immune from automated moderation actions.
+
+**Examples:**
+ - ``[p]autoimmune add @Twentysix`` - Adds a user.
+ - ``[p]autoimmune add @Mods`` - Adds a role.
+
+**Arguments:**
+ - ```` - The user or role to add immunity to.
+
+.. _core-command-autoimmune-isimmune:
+
+"""""""""""""""""""
+autoimmune isimmune
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]autoimmune isimmune
+
+**Description**
+
+Checks if a user or role would be considered immune from automated actions.
+
+**Examples:**
+ - ``[p]autoimmune isimmune @Twentysix``
+ - ``[p]autoimmune isimmune @Mods``
+
+**Arguments:**
+ - ```` - The user or role to check the immunity of.
+
+.. _core-command-autoimmune-list:
+
+"""""""""""""""
+autoimmune list
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]autoimmune list
+
+**Description**
+
+Gets the current members and roles configured for automatic moderation action immunity.
+
+**Example:**
+ - ``[p]autoimmune list``
+
+.. _core-command-autoimmune-remove:
+
+"""""""""""""""""
+autoimmune remove
+"""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]autoimmune remove
+
+**Description**
+
+Remove a user or role from being immune to automated moderation actions.
+
+**Examples:**
+ - ``[p]autoimmune remove @Twentysix`` - Removes a user.
+ - ``[p]autoimmune remove @Mods`` - Removes a role.
+
+**Arguments:**
+ - ```` - The user or role to remove immunity from.
+
+.. _core-command-bankset:
+
+^^^^^^^
+bankset
+^^^^^^^
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]bankset
+
+**Description**
+
+Base command for configuring bank settings.
+
+.. _core-command-bankset-bankname:
+
+""""""""""""""""
+bankset bankname
+""""""""""""""""
+
+.. note:: |owner-lock| However, if the bank is server-wide, the
+ server owner or an administrator can use this command.
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]bankset bankname
+
+**Description**
+
+Set bank's name.
+
+**Arguments**
+
+* ````: The new bank's name.
+
+.. _core-command-bankset-creditsname:
+
+"""""""""""""""""""
+bankset creditsname
+"""""""""""""""""""
+
+.. note:: |owner-lock| However, if the bank is server-wide, the
+ server owner or an administrator can use this command.
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]bankset creditsname
+
+**Description**
+
+Change the credits name of the bank. It is ``credits`` by default.
+
+For example, if you switch it to ``dollars``, the payday
+command will show this:
+
+.. TODO reference the payday command
+
+.. code-block:: none
+
+ Here, take some dollars. Enjoy! (+120 dollars!)
+
+ You currently have 220 dollars.
+
+**Arguments**
+
+* ````: The new credits name.
+
+.. _core-command-bankset-maxbal:
+
+""""""""""""""
+bankset maxbal
+""""""""""""""
+
+.. note:: |owner-lock| However, if the bank is server-wide, the
+ server owner or an administrator can use this command.
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]bankset maxbal
+
+**Description**
+
+Defines the maximum amount of money a user can have with the bot.
+
+If a user reaches this limit, they will be unable to gain more money.
+
+**Arguments**
+
+* ````: The maximum amount of money for users.
+
+.. _core-command-bankset-prune:
+
+"""""""""""""
+bankset prune
+"""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]bankset prune
+
+**Description**
+
+Base command for pruning bank accounts.
+
+.. _core-command-bankset-prune-global:
+
+""""""""""""""""""""
+bankset prune global
+""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]bankset prune global [confirmation=False]
+
+**Description**
+
+Prune bank accounts for users who no longer share a server with the bot.
+
+Cannot be used without a global bank. See ``[p]bankset prune server``.
+
+Examples:
+ - ``[p]bankset prune global`` - Did not confirm. Shows the help message.
+ - ``[p]bankset prune global yes``
+
+**Arguments**
+
+- ```` This will default to false unless specified.
+
+.. _core-command-bankset-prune-server:
+
+""""""""""""""""""""
+bankset prune server
+""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]bankset prune server [confirmation=False]
+
+.. tip:: Aliases: ``bankset prune guild``, ``bankset prune local``
+
+**Description**
+
+Prune bank accounts for users no longer in the server.
+
+Cannot be used with a global bank. See ``[p]bankset prune global``.
+
+Examples:
+ - ``[p]bankset prune server`` - Did not confirm. Shows the help message.
+ - ``[p]bankset prune server yes``
+
+**Arguments**
+
+- ```` This will default to false unless specified.
+
+.. _core-command-bankset-prune-user:
+
+""""""""""""""""""
+bankset prune user
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+ [p]bankset prune user [confirmation=False]
+
+**Description**
+
+Delete the bank account of a specified user.
+
+Examples:
+ - ``[p]bankset prune user @Twentysix`` - Did not confirm. Shows the help message.
+ - ``[p]bankset prune user @Twentysix yes``
+
+**Arguments**
+
+- ```` The user to delete the bank of. Takes mentions, names, and user ids.
+- ``