Add files using upload-large-folder tool

.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

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

testbed/Cog-Creators__Red-DiscordBot/.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# These are supported funding model platforms
+
+patreon: Red_Devs

testbed/Cog-Creators__Red-DiscordBot/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,5 @@
+<!-- 
+Please be sure to use the correct template, 
+if your report doesn't have the correct template please open an issue describing your issue in detail
+For support regarding the bot itself please visit the discord server over at https://discord.gg/red
+-->

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?
+
+<!--
+Choose one (remove the line that doesn't apply):
+-->
+Yes
+No
+<!--
+If the question doesn't apply (for example, it's not a code change), choose Yes.
+
+Please respond to this question truthfully. We do not delay nor reject PRs
+based on the answer to this question but it allows to better review this PR.
+-->

testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE/bugfix.md

@@ -0,0 +1,15 @@
+# Bugfix request
+
+<!--
+THIS TEMPLATE IS CURRENTLY UNUSED DUE TO GITHUB LIMITATIONS!
+To be used for pull requests that fix a bug
+-->
+
+#### Describe the bug being fixed
+
+<!-- 
+If an issue exists for the bug, mention 
+that this PR fixes that issue
+-->
+
+#### Anything we need to know about this fix?

testbed/Cog-Creators__Red-DiscordBot/.github/PULL_REQUEST_TEMPLATE/release.md

@@ -0,0 +1,16 @@
+# New release
+
+<!--
+THIS TEMPLATE IS CURRENTLY UNUSED DUE TO GITHUB LIMITATIONS!
+To be used by collaborators for doing releases.
+Most contributors will not need to use this.
+-->
+
+#### Version
+
+
+
+#### Has a draft release been created for this?
+
+- [ ] Yes
+- [ ] No

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/**/*

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 }}

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}));

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

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())

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;
+})

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")

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

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)

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,
+    }

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

testbed/Cog-Creators__Red-DiscordBot/docs/_templates/layout.html

@@ -0,0 +1,18 @@
+{% extends '!layout.html' %}
+{% block document %}
+{% if version_slug == 'latest' %}
+<div class="admonition warning">
+    <p class="first admonition-title">Warning</p>
+    <p class="last">
+        This document is for Red's development version, which can be significantly different from previous releases.
+        If you're a regular user, you should read the <a href="{{ dict(versions)['stable'] }}">Red documentation for the current stable release</a>.
+    </p>
+</div>
+{% endif %}
+{{ super() }}
+<a href="https://github.com/Cog-Creators/Red-DiscordBot">
+    <img style="position: absolute; top: 0; right: 0; border: 0;"
+    src="https://github.blog/wp-content/uploads/2008/12/forkme_right_darkblue_121621.png?resize=149%2C149"
+    class="attachment-full size-full" alt="Fork me on GitHub">
+</a>
+{% endblock %}

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.

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
+
+    <?xml version="1.0" encoding="UTF-8"?>
+    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+    <plist version="1.0">
+        <dict>
+            <key>Label</key>
+            <string>red</string>
+            <key>ProgramArguments</key>
+            <array>
+                <string>path</string>
+                <string>-O</string>
+                <string>-m</string>
+                <string>redbot</string>
+                <string>instance-name</string>
+                <string>--no-prompt</string>
+            </array>
+            <key>RunAtLoad</key>
+            <true/>
+            <key>KeepAlive</key>
+            <dict>
+                <key>SuccessfulExit</key>
+                <false/>
+            </dict>
+            <key>StandardOutPath</key>
+            <string>/tmp/red_out.log</string>
+            <key>StandardErrorPath</key>
+            <string>/tmp/red_err.log</string>
+            <key>UserName</key>
+            <string>username</string>
+            <key>InitGroups</key>
+            <true/>
+        </dict>
+    </plist>
+
+.. 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

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 <virtualenv_name>
+    (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

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 <your instance name>
+
+    IF %ERRORLEVEL% NEQ 0 (
+        ECHO Restarting Red...
+        GOTO RED
+    )
+
+Replace ``<your instance name>`` 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.

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 <https://discord.com>`_.
+2. Navigate to the `application page <https://discord.com/developers/applications>`_
+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. <intents>`
+    \This section is required.
+
+1. Make sure you're logged on to the `Discord website <https://discord.com>`_.
+2. Navigate to the `application page <https://discord.com/developers/applications>`_
+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 <https://support.discord.com/hc/en-us/articles/360040720412>`_ which is not covered in this guide.
+    Remember that :ref:`we do not support public bots <intents>`. We encourage you to read that page before scaling up your bot.
+
+*Parts of this guide have been adapted from* `discord.py intro <https://discordpy.readthedocs.io/en/stable/discord.html#discord-intro>`_ *and* `discord.py privileged intents <https://discordpy.readthedocs.io/en/stable/intents.html#privileged-intents>`_.

testbed/Cog-Creators__Red-DiscordBot/docs/changelog.rst

@@ -0,0 +1,5 @@
+=========
+Changelog
+=========
+
+.. include:: ../CHANGES.rst

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

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 <selfrole>
+
+**Description**
+
+Add or remove a role from yourself. It must have been configured as user settable
+by admins using the :ref:`selfroleset command <admin-command-selfroleset>`.
+
+**Arguments**
+
+* ``<selfrole>``: 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 <selfrole>
+
+**Description**
+
+Add a role to yourself. It must have been configured as user settable
+by admins using the :ref:`selfroleset command <admin-command-selfroleset>`.
+
+**Arguments**
+
+* ``<selfrole>``: The role you want to attribute to yourself. |role-input|
+
+.. _admin-command-selfrole-remove:
+
+"""""""""""""""
+selfrole remove
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]selfrole remove <selfrole>
+
+**Description**
+
+Remove a role from yourself. It must have been configured as user settable
+by admins using the :ref:`selfroleset command <admin-command-selfroleset>`.
+
+**Arguments**
+
+* ``<selfrole>``: 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-selfrole>`.
+
+.. _admin-command-selfroleset-add:
+
+"""""""""""""""
+selfroleset add
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]selfroleset add <role>
+
+**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**
+
+* ``<role>``: 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 <role>
+
+**Description**
+
+Remove a role, or a selection of roles, from the list of available selfroles.
+
+**Arguments**
+
+* ``<role>``: 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 <rolename> [user]
+
+**Description**
+
+Adds a role to a member. If ``user`` is not given, it will be considered
+as yourself, the command author.
+
+**Arguments**
+
+* ``<role>``: 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 <rolename> [user]
+
+**Description**
+
+Removes a role from a member. If ``user`` is not given, it will be considered
+as yourself, the command author.
+
+**Arguments**
+
+* ``<role>``: 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 <role> <name>
+
+**Description**
+
+Edits the name of a role.
+
+**Arguments**
+
+* ``<role>``: The role name to edit. |role-input-quotes|
+
+* ``<name>``: 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 <role> <color>
+
+**Description**
+
+Edits the color of a role.
+
+**Arguments**
+
+* ``<role>``: The role name to edit. |role-input-quotes|
+
+* ``<color>``: 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 <message>
+
+**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**
+
+* ``<message>``: 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 <channel>
+
+**Description**
+
+Sets the channel where the bot owner announcements will be sent.
+
+**Arguments**
+
+* ``<channel>``: 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
+<admin-command-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
+    <https://discord.com/developers>`_, select your application, click "Bot" in
+    the sidebar, then untick "Public bot".
+
+    .. image:: ../.resources/admin/public_bot.png

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-command-alias-add>`.
+
+.. _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 <alias_name> <command>
+
+**Description**
+
+Creates an alias. It will be used like this ``[p]alias_name <arguments>``
+and will be equal to this ``[p]command <arguments>``.
+
+Let's develop the examples given :ref:`earlier <alias-usage>` 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**
+
+* ``<alias_name>``: The new command name.
+
+* ``<command>``: 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] <alias_name>
+
+**Description**
+
+Removes an alias from the list. Check the list with
+the :ref:`alias list <alias-command-alias-list>` command.
+
+**Arguments**
+
+* ``<alias_name>``: 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 <alias_name>
+
+**Description**
+
+Shows the command associated to the alias.
+
+**Arguments**
+
+* ``<alias_name>``: The alias you want information from.
+
+.. _alias-command-alias-help:
+
+""""""""""
+alias help
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]alias help <alias_name>
+
+**Description**
+
+Shows help message for an alias.
+
+**Arguments**
+
+* ``<alias_name>``: 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
+<alias-command-alias-add>`, :ref:`del
+<alias-command-alias-delete>` and :ref:`list
+<alias-command-alias-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 <arguments>``, do ``[p]alias
+global add <arguments>``.

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 <https://github.com/freyacodes/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<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<local-tracks>`)
+	* SoundCloud
+	* Spotify links via YouTube (:ref:`see here<spotify-playback-and-api-keys>`)
+	* 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 <url>`` 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<local-tracks>`.
+    
+**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<multibots>`. 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 <https://adoptium.net/temurin/releases/?version=11>`__.
+    
+    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 <path_to_java_11_executable>``, 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 <command>`` 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 <localtracks path>`` 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/<parent folder>/song.mp3``
+   * ``localtracks/<parent folder>/<child folder>/song.mp3``
+
+When using this localtracks feature, use ``[p]local`` commands. Use ``[p]play <parent folder>/song.mp3`` to play
+single songs. Use ``[p]local folder <parent folder>/<child 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 <https://discord.gg/red>`__ 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<remote-lavalink>`, 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 ``<datapath>/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 ``<datapath>`` 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<linux-audio-autorestart>` 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<obtaining-the-latest-lavalink>` 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
+``<datapath>/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 ``<Lavalink path>`` with the Lavalink path you generated earlier (``<datapath>/cogs/Audio``).
+
+.. code-block:: sh
+
+	chmod a+rx <Lavalink path>/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:
+
+* ``<Jar executable path>`` - You can find your Java path by running ``which java``.
+* ``<Lavalink path>`` - The parent folder where your Lavalink executable can be located (usually in ``<datapath>/cogs/Audio``).
+* ``<username>`` - Your username on the host machine (run ``echo $USER``).
+
+.. 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
+
+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 <https://github.com/Cog-Creators/Lavalink-Jars/releases/latest>`__,
+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 <https://discord.gg/red>`__, 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 <https://www.digitalocean.com/community/tutorials/how-to-create-a-new-sudo-enabled-user-on-ubuntu-20-04-quickstart>`__
+    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 <https://github.com/freyacodes/Lavalink/#requirements>`__ 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<obtaining-the-latest-lavalink>`.
+
+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 <https://www.yougetsignal.com/tools/open-ports/>`__ 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 <playlist_name_OR_id> [args]
+
+**Description**
+
+Set a playlist to auto-play songs from.
+
+**Args**
+
+The following are all optional:
+
+* --scope <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 <age>
+
+**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 <country>
+
+**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 <seconds>
+
+**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 <seconds>
+
+**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 <price>
+
+**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 <seconds>
+
+**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 <maximum volume>
+
+**Description**
+
+Set the maximum volume allowed in this server.
+
+.. _audio-command-audioset-mycountrycode:
+
+""""""""""""""""""""""
+audioset mycountrycode
+""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]audioset mycountrycode <country>
+
+**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 <keyword>
+
+**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 <keyword>
+
+**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 <keyword>
+
+**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 <keyword>
+
+**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 <keyword>
+
+**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 <keyword>
+
+**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 <keyword>
+
+**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 <keyword>
+
+**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 <role_name>
+
+**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 <percent>
+
+**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 <index>
+
+**Description**
+
+Bump a track number to the top of the queue.
+
+.. _audio-command-bumpplay:
+
+^^^^^^^^
+bumpplay
+^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]bumpplay [play_now=False] <query>
+
+**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 <eq_preset>
+
+**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 <eq_preset>
+
+**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 <band_name_or_position> <band_value>
+
+**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 <search_words>
+
+**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 <query>
+
+**Description**
+
+Play the specified track or search for a close match.
+
+To play a local track, the query should be ``<parentfolder>\<filename>``.
+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 <playlist_name_OR_id> <track_name_OR_url> [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 <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 <id_or_name> [args]
+
+**Description**
+
+Copy a playlist from one scope to another.
+
+**Args**
+
+The following are all optional:
+
+* --from-scope <scope>
+* --from-author [user]
+* --from-guild [guild] (**only the bot owner can use this**)
+* --to-scope <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 <name> [args]
+
+**Description**
+
+Create an empty playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope <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 <playlist_name_OR_id> [args]
+
+**Description**
+
+Remove duplicate tracks from a saved playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope <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 <playlist_name_OR_id> [args]
+
+**Description**
+
+Delete a saved playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope <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 <playlist_name_OR_id> [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 <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 <playlist_name_OR_id> [args]
+
+**Description**
+
+Retrieve information from a saved playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope <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 <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 <name> [args]
+
+**Description**
+
+Save the queue to a playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope <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 <playlist_name_OR_id> <url> [args]
+
+**Description**
+
+Remove a track from a playlist by URL.
+
+**Args**
+
+The following are all optional:
+
+* --scope <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 <playlist_name_OR_id> <new_name> [args]
+
+**Description**
+
+Rename an existing playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope <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 <name> <url> [args]
+
+**Description**
+
+Save a playlist from a URL.
+
+The following are all optional:
+
+* --scope <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 <playlist_name_OR_id> [args]
+
+**Description**
+
+Load a playlist into the queue.
+
+**Args**
+
+The following are all optional:
+
+* --scope <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 <playlist_name_OR_id> [args]
+
+**Description**
+
+Updates all tracks in a playlist.
+
+**Args**
+
+The following are all optional:
+
+* --scope <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 <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 <search_words>
+
+**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 <index_or_url>
+
+**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 <query>
+
+**Description**
+
+Pick a track with a search.
+
+Use ``[p]search list <search term>`` to queue all tracks found on YouTube. Use ``[p]search sc
+<search term>`` to search on SoundCloud instead of YouTube.
+
+.. _audio-command-seek:
+
+^^^^
+seek
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]seek <seconds>
+
+**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<managed-node-management-commands>`, 
+whilst commands for unmanaged Lavalink nodes can be found :ref:`here<unmanaged-node-management-commands>`.
+
+.. _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<multibots>`.
+
+.. _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.

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 <message_id> [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:**
+
+- ``<message_id>`` The id of the message to cleanup after. This message won't be deleted.
+- ``<delete_pinned>`` 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 <message_id> <number> [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:**
+
+- ``<message_id>`` The id of the message to cleanup before. This message won't be deleted.
+- ``<number>`` The max number of messages to cleanup. Must be a positive integer.
+- ``<delete_pinned>`` 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 <one> <two> [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:**
+
+- ``<one>`` The id of the message to cleanup after. This message won't be deleted.
+- ``<two>`` The id of the message to cleanup before. This message won't be deleted.
+- ``<delete_pinned>`` 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 <number> [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:**
+
+- ``<number>`` The max number of messages to cleanup. Must be a positive integer.
+- ``<delete_pinned>`` 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 <number> [delete_pinned=False]
+
+**Description**
+
+Delete the last X messages in the current channel.
+
+Example:
+    - ``[p]cleanup messages 26``
+
+**Arguments:**
+
+- ``<number>`` The max number of messages to cleanup. Must be a positive integer.
+- ``<delete_pinned>`` Whether to delete pinned messages or not. Defaults to False
+
+.. _cleanup-command-cleanup-self:
+
+""""""""""""
+cleanup self
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cleanup self <number> [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:**
+
+- ``<number>`` The max number of messages to cleanup. Must be a positive integer.
+- ``<match_pattern>`` The text that messages must contain to be deleted. Use "" to skip this.
+- ``<delete_pinned>`` 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:**
+
+- ``<number>`` 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 <text> <number> [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:**
+
+- ``<number>`` The max number of messages to cleanup. Must be a positive integer.
+- ``<delete_pinned>`` 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 <user> <number> [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:**
+
+- ``<user>`` The user whose messages are to be cleaned up.
+- ``<number>`` The max number of messages to cleanup. Must be a positive integer.
+- ``<delete_pinned>`` 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.

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 <cogmanagerui-command-paths>`, which
+will list you all of the currently set paths.
+
+You can add a path by using the :ref:`addpath <cogmanagerui-command-addpath>`
+command. All cogs in that path will be available for the bot and listed in
+the :ref:`cogs <cogmanagerui-command-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 <https://cogboard.discord.red>`_
+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 <cogmanagerui-command-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
+<your_path>``.
+
+.. 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 <getting-started-permissions>`. 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 <cogmanagerui-command-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 <cogmanagerui-command-reorderpath>` command
+to reorder the listed paths.
+
+.. tip:: The number before a cog path can be used for the
+    :ref:`removepath <cogmanagerui-command-removepath>` command.
+
+.. _cogmanagerui-command-addpath:
+
+^^^^^^^
+addpath
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]addpath <path>
+
+**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 <cogmanagerui-command-cogs>`.
+
+**Arguments**
+
+*   ``<path>``: 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 <path_numbers...>
+
+**Description**
+
+Removes one or more paths from the list of available paths. Its cogs won't be
+accessible anymore.
+
+**Arguments**
+
+*   ``<path_numbers>``: The number of the path(s) to remove. You can get it with
+    the :ref:`paths <cogmanagerui-command-paths>` command.
+
+.. _cogmanagerui-command-reorderpath:
+
+^^^^^^^^^^^
+reorderpath
+^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]reorderpath <from> <to>
+
+**Description**
+
+Reorders the paths listed with the :ref:`paths <cogmanagerui-command-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 <cogmanagerui-command-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 <cogmanagerui-command-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**
+
+*   ``<from>``: The index of the path you want to move.
+*   ``<to>``: 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 <cogmanagerui-command-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.

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 <users...>
+
+**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:**
+    - ``<users...>`` - 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 <users...>
+
+**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:**
+    - ``<users...>`` - 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 <user_or_role>
+
+**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:**
+    - ``<user_or_role>`` - The user or role to add immunity to.
+
+.. _core-command-autoimmune-isimmune:
+
+"""""""""""""""""""
+autoimmune isimmune
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]autoimmune isimmune <user_or_role>
+
+**Description**
+
+Checks if a user or role would be considered immune from automated actions.
+
+**Examples:**
+    - ``[p]autoimmune isimmune @Twentysix``
+    - ``[p]autoimmune isimmune @Mods``
+
+**Arguments:**
+    - ``<user_or_role>`` - 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 <user_or_role>
+
+**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:**
+    - ``<user_or_role>`` - 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 <name>
+
+**Description**
+
+Set bank's name.
+
+**Arguments**
+
+* ``<name>``: 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 <name>
+
+**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**
+
+* ``<name>``: 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 <amount>
+
+**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**
+
+*   ``<amount>``: 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**
+
+- ``<confirmation>`` 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**
+
+- ``<confirmation>`` This will default to false unless specified.
+
+.. _core-command-bankset-prune-user:
+
+""""""""""""""""""
+bankset prune user
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]bankset prune user <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**
+
+- ``<user>`` The user to delete the bank of. Takes mentions, names, and user ids.
+- ``<confirmation>`` This will default to false unless specified.
+
+.. _core-command-bankset-registeramount:
+
+""""""""""""""""""""""
+bankset registeramount
+""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]bankset registeramount <creds>
+
+**Description**
+
+Set the initial balance for new bank accounts.
+
+Example:
+    - ``[p]bankset registeramount 5000``
+
+**Arguments**
+
+- ``<creds>`` The new initial balance amount. Default is 0.
+
+.. _core-command-bankset-reset:
+
+"""""""""""""
+bankset reset
+"""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]bankset reset [confirmation=False]
+
+**Description**
+
+Delete all bank accounts.
+
+Examples:
+    - ``[p]bankset reset`` - Did not confirm. Shows the help message.
+    - ``[p]bankset reset yes``
+
+**Arguments**
+
+- ``<confirmation>`` This will default to false unless specified.
+
+.. _core-command-bankset-showsettings:
+
+""""""""""""""""""""
+bankset showsettings
+""""""""""""""""""""
+
+.. 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 showsettings
+
+**Description**
+
+Shows the current settings of your bank.
+
+This will display the following information:
+
+*   Name of the bank
+*   Scope of the bank (global or per server)
+*   Currency name
+*   Default balance
+*   Maximum allowed balance
+
+.. _core-command-bankset-toggleglobal:
+
+""""""""""""""""""""
+bankset toggleglobal
+""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]bankset toggleglobal [confirm=False]
+
+**Description**
+
+Makes the bank global instead of server-wide. If it
+is already global, the command will switch it back
+to the server-wide bank.
+
+.. warning:: Using this command will reset **all** accounts.
+
+**Arguments**
+
+* ``[confirm=False]``: Put ``yes`` to confirm.
+
+.. _core-command-blocklist:
+
+^^^^^^^^^
+blocklist
+^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]blocklist 
+
+.. tip:: Aliases: ``blacklist``, ``denylist``
+
+**Description**
+
+Commands to manage the blocklist.
+
+Use ``[p]blocklist clear`` to disable the blocklist
+
+.. _core-command-blocklist-add:
+
+"""""""""""""
+blocklist add
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]blocklist add <users...>
+
+**Description**
+
+Adds users to the blocklist.
+
+**Examples:**
+    - ``[p]blocklist add @26 @Will`` - Adds two users to the blocklist.
+    - ``[p]blocklist add 262626262626262626`` - Blocks a user by ID.
+
+**Arguments:**
+    - ``<users...>`` - The user or users to add to the blocklist.
+
+.. _core-command-blocklist-clear:
+
+"""""""""""""""
+blocklist clear
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]blocklist clear 
+
+**Description**
+
+Clears the blocklist.
+
+**Example:**
+    - ``[p]blocklist clear``
+
+.. _core-command-blocklist-list:
+
+""""""""""""""
+blocklist list
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]blocklist list 
+
+**Description**
+
+Lists users on the blocklist.
+
+**Example:**
+    - ``[p]blocklist list``
+
+.. _core-command-blocklist-remove:
+
+""""""""""""""""
+blocklist remove
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]blocklist remove <users...>
+
+**Description**
+
+Removes users from the blocklist.
+
+**Examples:**
+    - ``[p]blocklist remove @26 @Will`` - Removes two users from the blocklist.
+    - ``[p]blocklist remove 262626262626262626`` - Removes a user by ID.
+
+**Arguments:**
+    - ``<users...>`` - The user or users to remove from the blocklist.
+
+.. _core-command-command:
+
+^^^^^^^
+command
+^^^^^^^
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command 
+
+**Description**
+
+Commands to enable and disable commands and cogs.
+
+.. _core-command-command-defaultdisablecog:
+
+"""""""""""""""""""""""""
+command defaultdisablecog
+"""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command defaultdisablecog <cog>
+
+**Description**
+
+Set the default state for a cog as disabled.
+
+This will disable the cog for all servers by default.
+To override it, use ``[p]command enablecog`` on the servers you want to allow usage.
+
+.. Note:: This will only work on loaded cogs, and must reference the title-case cog name.
+
+
+**Examples:**
+    - ``[p]command defaultdisablecog Economy``
+    - ``[p]command defaultdisablecog ModLog``
+
+**Arguments:**
+    - ``<cog>`` - The name of the cog to make disabled by default. Must be title-case.
+
+.. _core-command-command-defaultenablecog:
+
+""""""""""""""""""""""""
+command defaultenablecog
+""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command defaultenablecog <cog>
+
+**Description**
+
+Set the default state for a cog as enabled.
+
+This will re-enable the cog for all servers by default.
+To override it, use ``[p]command disablecog`` on the servers you want to disallow usage.
+
+.. Note:: This will only work on loaded cogs, and must reference the title-case cog name.
+
+
+**Examples:**
+    - ``[p]command defaultenablecog Economy``
+    - ``[p]command defaultenablecog ModLog``
+
+**Arguments:**
+    - ``<cog>`` - The name of the cog to make enabled by default. Must be title-case.
+
+.. _core-command-command-disable:
+
+"""""""""""""""
+command disable
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command disable <command>
+
+**Description**
+
+Disable a command.
+
+If you're the bot owner, this will disable commands globally by default.
+Otherwise, this will disable commands on the current server.
+
+**Examples:**
+    - ``[p]command disable userinfo`` - Disables the ``userinfo`` command in the Mod cog.
+    - ``[p]command disable urban`` - Disables the ``urban`` command in the General cog.
+
+**Arguments:**
+    - ``<command>`` - The command to disable.
+
+.. _core-command-command-disable-global:
+
+""""""""""""""""""""""
+command disable global
+""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command disable global <command>
+
+**Description**
+
+Disable a command globally.
+
+**Examples:**
+    - ``[p]command disable global userinfo`` - Disables the ``userinfo`` command in the Mod cog.
+    - ``[p]command disable global urban`` - Disables the ``urban`` command in the General cog.
+
+**Arguments:**
+    - ``<command>`` - The command to disable globally.
+
+.. _core-command-command-disable-server:
+
+""""""""""""""""""""""
+command disable server
+""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command disable server <command>
+
+.. tip:: Alias: ``command disable guild``
+
+**Description**
+
+Disable a command in this server only.
+
+        **Examples:**
+            - ``[p]command disable server userinfo`` - Disables the ``userinfo`` command in the Mod cog.
+            - ``[p]command disable server urban`` - Disables the ``urban`` command in the General cog.
+
+        **Arguments:**
+            - ``<command>`` - The command to disable for the current server.
+
+.. _core-command-command-disablecog:
+
+""""""""""""""""""
+command disablecog
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command disablecog <cog>
+
+**Description**
+
+Disable a cog in this server.
+
+.. Note:: This will only work on loaded cogs, and must reference the title-case cog name.
+
+
+**Examples:**
+    - ``[p]command disablecog Economy``
+    - ``[p]command disablecog ModLog``
+
+**Arguments:**
+    - ``<cog>`` - The name of the cog to disable on this server. Must be title-case.
+
+.. _core-command-command-disabledmsg:
+
+"""""""""""""""""""
+command disabledmsg
+"""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command disabledmsg [message]
+
+**Description**
+
+Set the bot's response to disabled commands.
+
+Leave blank to send nothing.
+
+To include the command name in the message, include the ``{command}`` placeholder.
+
+**Examples:**
+    - ``[p]command disabledmsg This command is disabled``
+    - ``[p]command disabledmsg {command} is disabled``
+    - ``[p]command disabledmsg`` - Sends nothing when a disabled command is attempted.
+
+**Arguments:**
+    - ``[message]`` - The message to send when a disabled command is attempted.
+
+.. _core-command-command-enable:
+
+""""""""""""""
+command enable
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command enable <command>
+
+**Description**
+
+Enable a command.
+
+If you're the bot owner, this will try to enable a globally disabled command by default.
+Otherwise, this will try to enable a command disabled on the current server.
+
+**Examples:**
+    - ``[p]command enable userinfo`` - Enables the ``userinfo`` command in the Mod cog.
+    - ``[p]command enable urban`` - Enables the ``urban`` command in the General cog.
+
+**Arguments:**
+    - ``<command>`` - The command to enable.
+
+.. _core-command-command-enable-global:
+
+"""""""""""""""""""""
+command enable global
+"""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command enable global <command>
+
+**Description**
+
+        Enable a command globally.
+
+**Examples:**
+    - ``[p]command enable global userinfo`` - Enables the ``userinfo`` command in the Mod cog.
+    - ``[p]command enable global urban`` - Enables the ``urban`` command in the General cog.
+
+**Arguments:**
+    - ``<command>`` - The command to enable globally.
+
+.. _core-command-command-enable-server:
+
+"""""""""""""""""""""
+command enable server
+"""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command enable server <command>
+
+.. tip:: Alias: ``command enable guild``
+
+**Description**
+
+    Enable a command in this server.
+
+**Examples:**
+    - ``[p]command enable server userinfo`` - Enables the ``userinfo`` command in the Mod cog.
+    - ``[p]command enable server urban`` - Enables the ``urban`` command in the General cog.
+
+**Arguments:**
+    - ``<command>`` - The command to enable for the current server.
+
+.. _core-command-command-enablecog:
+
+"""""""""""""""""
+command enablecog
+"""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command enablecog <cog>
+
+**Description**
+
+Enable a cog in this server.
+
+.. Note:: This will only work on loaded cogs, and must reference the title-case cog name.
+
+
+**Examples:**
+    - ``[p]command enablecog Economy``
+    - ``[p]command enablecog ModLog``
+
+**Arguments:**
+    - ``<cog>`` - The name of the cog to enable on this server. Must be title-case.
+
+.. _core-command-command-listdisabled:
+
+""""""""""""""""""""
+command listdisabled
+""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command listdisabled 
+
+**Description**
+
+List disabled commands.
+
+If you're the bot owner, this will show global disabled commands by default.
+Otherwise, this will show disabled commands on the current server.
+
+**Example:**
+    - ``[p]command listdisabled``
+
+.. _core-command-command-listdisabled-global:
+
+"""""""""""""""""""""""""""
+command listdisabled global
+"""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command listdisabled global 
+
+**Description**
+
+List disabled commands globally.
+
+**Example:**
+    - ``[p]command listdisabled global``
+
+.. _core-command-command-listdisabled-guild:
+
+""""""""""""""""""""""""""
+command listdisabled guild
+""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command listdisabled guild 
+
+**Description**
+
+List disabled commands in this server.
+
+**Example:**
+    - ``[p]command listdisabled guild``
+
+.. _core-command-command-listdisabledcogs:
+
+""""""""""""""""""""""""
+command listdisabledcogs
+""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]command listdisabledcogs 
+
+**Description**
+
+List the cogs which are disabled in this server.
+
+**Example:**
+    - ``[p]command listdisabledcogs``
+
+.. _core-command-contact:
+
+^^^^^^^
+contact
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]contact <message>
+
+**Description**
+
+Sends a message to the owner.
+
+This is limited to one message every 60 seconds per person.
+
+**Example:**
+    - ``[p]contact Help! The bot has become sentient!``
+
+**Arguments:**
+    - ``[message]`` - The message to send to the owner.
+
+.. _core-command-diagnoseissues:
+
+^^^^^^^^^^^^^^
+diagnoseissues
+^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]diagnoseissues [channel] <member> <command_name>
+
+**Description**
+
+Diagnose issues with the command checks with ease!
+
+If you want to diagnose the command from a text channel in a different server,
+you can do so by using the command in DMs.
+
+**Example:**
+    - ``[p]diagnoseissues #general @Slime ban`` - Diagnose why @Slime can't use ``[p]ban`` in #general channel.
+
+**Arguments:**
+    - ``[channel]`` - The text channel that the command should be tested for. Defaults to the current channel.
+    - ``<member>`` - The member that should be considered as the command caller.
+    - ``<command_name>`` - The name of the command to test.
+
+.. _core-command-dm:
+
+^^
+dm
+^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]dm <user_id> <message>
+
+**Description**
+
+Sends a DM to a user.
+
+This command needs a user ID to work.
+
+To get a user ID, go to Discord's settings and open the 'Appearance' tab.
+Enable 'Developer Mode', then right click a user and click on 'Copy ID'.
+
+**Example:**
+    - ``[p]dm 262626262626262626 Do you like me? Yes / No``
+
+**Arguments:**
+    - ``[message]`` - The message to dm to the user.
+
+.. _core-command-embedset:
+
+^^^^^^^^
+embedset
+^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]embedset 
+
+**Description**
+
+Commands for toggling embeds on or off.
+
+This setting determines whether or not to use embeds as a response to a command (for commands that support it).
+The default is to use embeds.
+
+The embed settings are checked until the first True/False in this order:
+    - In guild context:
+        1. Channel override - ``[p]embedset channel``
+        2. Server command override - ``[p]embedset command server``
+        3. Server override - ``[p]embedset server``
+        4. Global command override - ``[p]embedset command global``
+        5. Global setting  -``[p]embedset global``
+
+    - In DM context:
+        1. User override - ``[p]embedset user``
+        2. Global command override - ``[p]embedset command global``
+        3. Global setting - ``[p]embedset global``
+
+.. _core-command-embedset-channel:
+
+""""""""""""""""
+embedset channel
+""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]embedset channel [enabled]
+
+**Description**
+
+Set's a channel's embed setting.
+
+If set, this is used instead of the guild and command defaults to determine whether or not to use embeds.
+This is used for all commands done in a channel.
+
+If enabled is left blank, the setting will be unset and the guild default will be used instead.
+
+To see full evaluation order of embed settings, run ``[p]help embedset``.
+
+**Examples:**
+    - ``[p]embedset channel False`` - Disables embeds in this channel.
+    - ``[p]embedset channel`` - Resets value to use guild default.
+
+**Arguments:**
+    - ``[enabled]`` - Whether to use embeds in this channel. Leave blank to reset to default.
+
+.. _core-command-embedset-command:
+
+""""""""""""""""
+embedset command
+""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]embedset command <command> [enabled]
+
+**Description**
+
+Sets a command's embed setting.
+
+If you're the bot owner, this will try to change the command's embed setting globally by default.
+Otherwise, this will try to change embed settings on the current server.
+
+If enabled is left blank, the setting will be unset.
+
+To see full evaluation order of embed settings, run ``[p]help embedset``.
+
+**Examples:**
+    - ``[p]embedset command info`` - Clears command specific embed settings for 'info'.
+    - ``[p]embedset command info False`` - Disables embeds for 'info'.
+    - ``[p]embedset command "ignore list" True`` - Quotes are needed for subcommands.
+
+**Arguments:**
+    - ``[enabled]`` - Whether to use embeds for this command. Leave blank to reset to default.
+
+.. _core-command-embedset-command-global:
+
+"""""""""""""""""""""""
+embedset command global
+"""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]embedset command global <command> [enabled]
+
+**Description**
+
+Sets a command's embed setting globally.
+
+If set, this is used instead of the global default to determine whether or not to use embeds.
+
+If enabled is left blank, the setting will be unset.
+
+To see full evaluation order of embed settings, run ``[p]help embedset``.
+
+**Examples:**
+    - ``[p]embedset command global info`` - Clears command specific embed settings for 'info'.
+    - ``[p]embedset command global info False`` - Disables embeds for 'info'.
+    - ``[p]embedset command global "ignore list" True`` - Quotes are needed for subcommands.
+
+**Arguments:**
+    - ``[enabled]`` - Whether to use embeds for this command. Leave blank to reset to default.
+
+.. _core-command-embedset-command-server:
+
+"""""""""""""""""""""""
+embedset command server
+"""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]embedset command server <command> [enabled]
+
+.. tip:: Alias: ``embedset command guild``
+
+**Description**
+
+Sets a command's embed setting for the current server.
+
+If set, this is used instead of the server default to determine whether or not to use embeds.
+
+If enabled is left blank, the setting will be unset and the server default will be used instead.
+
+To see full evaluation order of embed settings, run ``[p]help embedset``.
+
+**Examples:**
+    - ``[p]embedset command server info`` - Clears command specific embed settings for 'info'.
+    - ``[p]embedset command server info False`` - Disables embeds for 'info'.
+    - ``[p]embedset command server "ignore list" True`` - Quotes are needed for subcommands.
+
+**Arguments:**
+    - ``[enabled]`` - Whether to use embeds for this command. Leave blank to reset to default.
+
+.. _core-command-embedset-global:
+
+"""""""""""""""
+embedset global
+"""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]embedset global 
+
+**Description**
+
+Toggle the global embed setting.
+
+This is used as a fallback if the user or guild hasn't set a preference.
+The default is to use embeds.
+
+To see full evaluation order of embed settings, run ``[p]help embedset``.
+
+**Example:**
+    - ``[p]embedset global``
+
+.. _core-command-embedset-server:
+
+"""""""""""""""
+embedset server
+"""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]embedset server [enabled]
+
+.. tip:: Alias: ``embedset guild``
+
+**Description**
+
+Set the server's embed setting.
+
+If set, this is used instead of the global default to determine whether or not to use embeds.
+This is used for all commands done in a server.
+
+If enabled is left blank, the setting will be unset and the global default will be used instead.
+
+To see full evaluation order of embed settings, run ``[p]help embedset``.
+
+**Examples:**
+    - ``[p]embedset server False`` - Disables embeds on this server.
+    - ``[p]embedset server`` - Resets value to use global default.
+
+**Arguments:**
+    - ``[enabled]`` - Whether to use embeds on this server. Leave blank to reset to default.
+
+.. _core-command-embedset-showsettings:
+
+"""""""""""""""""""""
+embedset showsettings
+"""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]embedset showsettings [command]
+
+**Description**
+
+Show the current embed settings.
+
+Provide a command name to check for command specific embed settings.
+
+**Examples:**
+    - ``[p]embedset showsettings`` - Shows embed settings.
+    - ``[p]embedset showsettings info`` - Also shows embed settings for the 'info' command.
+    - ``[p]embedset showsettings "ignore list"`` - Checking subcommands requires quotes.
+
+**Arguments:**
+    - ``[command]`` - Checks this command for command specific embed settings.
+
+.. _core-command-embedset-user:
+
+"""""""""""""
+embedset user
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]embedset user [enabled]
+
+**Description**
+
+Sets personal embed setting for DMs.
+
+If set, this is used instead of the global default to determine whether or not to use embeds.
+This is used for all commands executed in a DM with the bot.
+
+If enabled is left blank, the setting will be unset and the global default will be used instead.
+
+To see full evaluation order of embed settings, run ``[p]help embedset``.
+
+**Examples:**
+    - ``[p]embedset user False`` - Disables embeds in your DMs.
+    - ``[p]embedset user`` - Resets value to use global default.
+
+**Arguments:**
+    - ``[enabled]`` - Whether to use embeds in your DMs. Leave blank to reset to default.
+
+.. _core-command-helpset:
+
+^^^^^^^
+helpset
+^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset 
+
+**Description**
+
+Commands to manage settings for the help command.
+
+All help settings are applied globally.
+
+.. _core-command-helpset-deletedelay:
+
+"""""""""""""""""""
+helpset deletedelay
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset deletedelay <seconds>
+
+**Description**
+
+Set the delay after which help pages will be deleted.
+
+The setting is disabled by default, and only applies to non-menu help,
+sent in server text channels.
+Setting the delay to 0 disables this feature.
+
+The bot has to have MANAGE_MESSAGES permission for this to work.
+
+**Examples:**
+    - ``[p]helpset deletedelay 60`` - Delete the help pages after a minute.
+    - ``[p]helpset deletedelay 1`` - Delete the help pages as quickly as possible.
+    - ``[p]helpset deletedelay 1209600`` - Max time to wait before deleting (14 days).
+    - ``[p]helpset deletedelay 0`` - Disable deleting help pages.
+
+**Arguments:**
+    - ``<seconds>`` - The seconds to wait before deleting help pages.
+
+.. _core-command-helpset-maxpages:
+
+""""""""""""""""
+helpset maxpages
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset maxpages <pages>
+
+**Description**
+
+Set the maximum number of help pages sent in a server channel.
+
+.. Note:: This setting does not apply to menu help.
+
+
+If a help message contains more pages than this value, the help message will
+be sent to the command author via DM. This is to help reduce spam in server
+text channels.
+
+The default value is 2 pages.
+
+**Examples:**
+    - ``[p]helpset maxpages 50`` - Basically never send help to DMs.
+    - ``[p]helpset maxpages 0`` - Always send help to DMs.
+
+**Arguments:**
+    - ``<limit>`` - The max pages allowed to send per help in a server.
+
+.. _core-command-helpset-pagecharlimit:
+
+"""""""""""""""""""""
+helpset pagecharlimit
+"""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset pagecharlimit <limit>
+
+**Description**
+
+Set the character limit for each page in the help message.
+
+.. Note:: This setting only applies to embedded help.
+
+
+The default value is 1000 characters. The minimum value is 500.
+The maximum is based on the lower of what you provide and what discord allows.
+
+Please note that setting a relatively small character limit may
+mean some pages will exceed this limit.
+
+**Example:**
+    - ``[p]helpset pagecharlimit 1500``
+
+**Arguments:**
+    - ``<limit>`` - The max amount of characters to show per page in the help message.
+
+.. _core-command-helpset-reacttimeout:
+
+""""""""""""""""""""
+helpset reacttimeout
+""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset reacttimeout <seconds>
+
+**Description**
+
+Set the timeout for reactions, if menus are enabled.
+
+The default is 30 seconds.
+The timeout has to be between 15 and 300 seconds.
+
+**Examples:**
+    - ``[p]helpset reacttimeout 30`` - The default timeout.
+    - ``[p]helpset reacttimeout 60`` - Timeout of 1 minute.
+    - ``[p]helpset reacttimeout 15`` - Minimum allowed timeout.
+    - ``[p]helpset reacttimeout 300`` - Max allowed timeout (5 mins).
+
+**Arguments:**
+    - ``<seconds>`` - The timeout, in seconds, of the reactions.
+
+.. _core-command-helpset-resetformatter:
+
+""""""""""""""""""""""
+helpset resetformatter
+""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset resetformatter 
+
+**Description**
+
+This resets Red's help formatter to the default formatter.
+
+**Example:**
+    - ``[p]helpset resetformatter``
+
+.. _core-command-helpset-resetsettings:
+
+"""""""""""""""""""""
+helpset resetsettings
+"""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset resetsettings 
+
+**Description**
+
+This resets Red's help settings to their defaults.
+
+This may not have an impact when using custom formatters from 3rd party cogs
+
+**Example:**
+    - ``[p]helpset resetsettings``
+
+.. _core-command-helpset-showaliases:
+
+"""""""""""""""""""
+helpset showaliases
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset showaliases [show_aliases]
+
+**Description**
+
+This allows the help command to show existing commands aliases if there is any.
+
+This defaults to True.
+Using this without a setting will toggle.
+
+**Examples:**
+    - ``[p]helpset showaliases False`` - Disables showing aliases on this server.
+    - ``[p]helpset showaliases`` - Toggles the value.
+
+**Arguments:**
+    - ``[show_aliases]`` - Whether to include aliases in help. Leave blank to toggle.
+
+.. _core-command-helpset-showhidden:
+
+""""""""""""""""""
+helpset showhidden
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset showhidden [show_hidden]
+
+**Description**
+
+This allows the help command to show hidden commands.
+
+This defaults to False.
+Using this without a setting will toggle.
+
+**Examples:**
+    - ``[p]helpset showhidden True`` - Enables showing hidden commands.
+    - ``[p]helpset showhidden`` - Toggles the value.
+
+**Arguments:**
+    - ``[show_hidden]`` - Whether to use show hidden commands in help. Leave blank to toggle.
+
+.. _core-command-helpset-showsettings:
+
+""""""""""""""""""""
+helpset showsettings
+""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset showsettings 
+
+**Description**
+
+Show the current help settings.
+
+.. Warning:: These settings may not be accurate if the default formatter is not in use.
+
+
+**Example:**
+    - ``[p]helpset showsettings``
+
+.. _core-command-helpset-tagline:
+
+"""""""""""""""
+helpset tagline
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset tagline [tagline]
+
+**Description**
+
+Set the tagline to be used.
+
+The maximum tagline length is 2048 characters.
+This setting only applies to embedded help. If no tagline is specified, the default will be used instead.
+
+**Examples:**
+    - ``[p]helpset tagline Thanks for using the bot!``
+    - ``[p]helpset tagline`` - Resets the tagline to the default.
+
+**Arguments:**
+    - ``[tagline]`` - The tagline to appear at the bottom of help embeds. Leave blank to reset.
+
+.. _core-command-helpset-usemenus:
+
+""""""""""""""""
+helpset usemenus
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset usemenus <"buttons"|"reactions"|"select"|"selectonly"|"disable">
+
+**Description**
+
+Allows the help command to be sent as a paginated menu instead of separate
+messages.
+
+When "reactions", "buttons", "select", or "selectonly" is passed, ``[p]help`` will
+only show one page at a time and will use the associated control scheme to navigate between pages.
+
+**Examples:**
+    - ``[p]helpset usemenus reactions`` - Enables using reaction menus.
+    - ``[p]helpset usemenus buttons`` - Enables using button menus.
+    - ``[p]helpset usemenus select`` - Enables buttons with a select menu.
+    - ``[p]helpset usemenus selectonly`` - Enables a select menu only on help.
+    - ``[p]helpset usemenus disable`` - Disables help menus.
+
+**Arguments:**
+    - ``<"buttons"|"reactions"|"select"|"selectonly"|"disable">`` - Whether to use ``buttons``,
+      ``reactions``, ``select``, ``selectonly``, or no menus.
+
+.. _core-command-helpset-usetick:
+
+"""""""""""""""
+helpset usetick
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset usetick [use_tick]
+
+**Description**
+
+This allows the help command message to be ticked if help is sent to a DM.
+
+Ticking is reacting to the help message with a ✅.
+
+Defaults to False.
+Using this without a setting will toggle.
+
+.. Note:: This is only used when the bot is not using menus.
+
+
+**Examples:**
+    - ``[p]helpset usetick False`` - Disables ticking when help is sent to DMs.
+    - ``[p]helpset usetick`` - Toggles the value.
+
+**Arguments:**
+    - ``[use_tick]`` - Whether to tick the help command when help is sent to DMs. Leave blank to toggle.
+
+.. _core-command-helpset-verifychecks:
+
+""""""""""""""""""""
+helpset verifychecks
+""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset verifychecks [verify]
+
+**Description**
+
+Sets if commands which can't be run in the current context should be filtered from help.
+
+Defaults to True.
+Using this without a setting will toggle.
+
+**Examples:**
+    - ``[p]helpset verifychecks False`` - Enables showing unusable commands in help.
+    - ``[p]helpset verifychecks`` - Toggles the value.
+
+**Arguments:**
+    - ``[verify]`` - Whether to hide unusable commands in help. Leave blank to toggle.
+
+.. _core-command-helpset-verifyexists:
+
+""""""""""""""""""""
+helpset verifyexists
+""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]helpset verifyexists [verify]
+
+**Description**
+
+Sets whether the bot should respond to help commands for nonexistent topics.
+
+When enabled, this will indicate the existence of help topics, even if the user can't use it.
+
+.. Note:: This setting on its own does not fully prevent command enumeration.
+
+
+Defaults to False.
+Using this without a setting will toggle.
+
+**Examples:**
+    - ``[p]helpset verifyexists True`` - Enables sending help for nonexistent topics.
+    - ``[p]helpset verifyexists`` - Toggles the value.
+
+**Arguments:**
+    - ``[verify]`` - Whether to respond to help for nonexistent topics. Leave blank to toggle.
+
+.. _core-command-ignore:
+
+^^^^^^
+ignore
+^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]ignore 
+
+**Description**
+
+Commands to add servers or channels to the ignore list.
+
+The ignore list will prevent the bot from responding to commands in the configured locations.
+
+.. Note:: Owners and Admins override the ignore list.
+
+
+.. _core-command-ignore-channel:
+
+""""""""""""""
+ignore channel
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]ignore channel [channel]
+
+**Description**
+
+Ignore commands in the channel, thread, or category.
+
+Defaults to the current thread or channel.
+
+.. Note:: Owners, Admins, and those with Manage Channel permissions override ignored channels.
+
+
+**Examples:**
+    - ``[p]ignore channel #general`` - Ignores commands in the #general channel.
+    - ``[p]ignore channel`` - Ignores commands in the current channel.
+    - ``[p]ignore channel "General Channels"`` - Use quotes for categories with spaces.
+    - ``[p]ignore channel 356236713347252226`` - Also accepts IDs.
+
+**Arguments:**
+    - ``<channel>`` - The channel to ignore. This can also be a thread or category channel.
+
+.. _core-command-ignore-list:
+
+"""""""""""
+ignore list
+"""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]ignore list 
+
+**Description**
+
+List the currently ignored servers and channels.
+
+**Example:**
+    - ``[p]ignore list``
+
+.. _core-command-ignore-server:
+
+"""""""""""""
+ignore server
+"""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]ignore server 
+
+.. tip:: Alias: ``ignore guild``
+
+**Description**
+
+Ignore commands in this server.
+
+.. Note:: Owners, Admins, and those with Manage Server permissions override ignored servers.
+
+
+**Example:**
+    - ``[p]ignore server`` - Ignores the current server
+
+.. _core-command-info:
+
+^^^^
+info
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]info 
+
+**Description**
+
+Shows info about Red.
+
+.. _core-command-invite:
+
+^^^^^^
+invite
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]invite 
+
+**Description**
+
+Shows Red's invite url.
+
+This will always send the invite to DMs to keep it private.
+
+This command is locked to the owner unless ``[p]inviteset public`` is set to True.
+
+**Example:**
+    - ``[p]invite``
+
+.. _core-command-inviteset:
+
+^^^^^^^^^
+inviteset
+^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]inviteset 
+
+**Description**
+
+Commands to setup Red's invite settings.
+
+.. _core-command-inviteset-perms:
+
+"""""""""""""""
+inviteset perms
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]inviteset perms <level>
+
+**Description**
+
+Make the bot create its own role with permissions on join.
+
+The bot will create its own role with the desired permissions when it joins a new server. This is a special role that can't be deleted or removed from the bot.
+
+For that, you need to provide a valid permissions level.
+You can generate one here: https://discordapi.com/permissions.html
+
+Please note that you might need two factor authentication for some permissions.
+
+**Example:**
+    - ``[p]inviteset perms 134217728`` - Adds a "Manage Nicknames" permission requirement to the invite.
+
+**Arguments:**
+    - ``<level>`` - The permission level to require for the bot in the generated invite.
+
+.. _core-command-inviteset-public:
+
+""""""""""""""""
+inviteset public
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]inviteset public [confirm=False]
+
+**Description**
+
+Toggles if ``[p]invite`` should be accessible for the average user.
+
+The bot must be made into a ``Public bot`` in the developer dashboard for public invites to work.
+
+**Example:**
+    - ``[p]inviteset public yes`` - Toggles the public invite setting.
+
+**Arguments:**
+    - ``[confirm]`` - Required to set to public. Not required to toggle back to private.
+
+.. _core-command-leave:
+
+^^^^^
+leave
+^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]leave [servers...]
+
+**Description**
+
+Leaves servers.
+
+If no server IDs are passed the local server will be left instead.
+
+.. Note:: This command is interactive.
+
+
+**Examples:**
+    - ``[p]leave`` - Leave the current server.
+    - ``[p]leave "Red - Discord Bot"`` - Quotes are necessary when there are spaces in the name.
+    - ``[p]leave 133049272517001216 240154543684321280`` - Leaves multiple servers, using IDs.
+
+**Arguments:**
+    - ``[servers...]`` - The servers to leave. When blank, attempts to leave the current server.
+
+.. _core-command-licenseinfo:
+
+^^^^^^^^^^^
+licenseinfo
+^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]licenseinfo 
+
+.. tip:: Alias: ``licenceinfo``
+
+**Description**
+
+Get info about Red's licenses.
+
+.. _core-command-load:
+
+^^^^
+load
+^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]load <cogs...>
+
+**Description**
+
+Loads cog packages from the local paths and installed cogs.
+
+See packages available to load with ``[p]cogs``.
+
+Additional cogs can be added using Downloader, or from local paths using ``[p]addpath``.
+
+**Examples:**
+    - ``[p]load general`` - Loads the ``general`` cog.
+    - ``[p]load admin mod mutes`` - Loads multiple cogs.
+
+**Arguments:**
+    - ``<cogs...>`` - The cog packages to load.
+
+.. _core-command-localallowlist:
+
+^^^^^^^^^^^^^^
+localallowlist
+^^^^^^^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]localallowlist 
+
+.. tip:: Alias: ``localwhitelist``
+
+**Description**
+
+Commands to manage the server specific allowlist.
+
+.. Warning:: When the allowlist is in use, the bot will ignore commands from everyone not on the list in the server.
+
+
+Use ``[p]localallowlist clear`` to disable the allowlist
+
+.. _core-command-localallowlist-add:
+
+""""""""""""""""""
+localallowlist add
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]localallowlist add <users_or_roles...>
+
+**Description**
+
+Adds a user or role to the server allowlist.
+
+**Examples:**
+    - ``[p]localallowlist add @26 @Will`` - Adds two users to the local allowlist.
+    - ``[p]localallowlist add 262626262626262626`` - Allows a user by ID.
+    - ``[p]localallowlist add "Super Admins"`` - Allows a role with a space in the name without mentioning.
+
+**Arguments:**
+    - ``<users_or_roles...>`` - The users or roles to remove from the local allowlist.
+
+.. _core-command-localallowlist-clear:
+
+""""""""""""""""""""
+localallowlist clear
+""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]localallowlist clear 
+
+**Description**
+
+Clears the allowlist.
+
+This disables the local allowlist and clears all entires.
+
+**Example:**
+    - ``[p]localallowlist clear``
+
+.. _core-command-localallowlist-list:
+
+"""""""""""""""""""
+localallowlist list
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]localallowlist list 
+
+**Description**
+
+Lists users and roles on the server allowlist.
+
+**Example:**
+    - ``[p]localallowlist list``
+
+.. _core-command-localallowlist-remove:
+
+"""""""""""""""""""""
+localallowlist remove
+"""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]localallowlist remove <users_or_roles...>
+
+**Description**
+
+Removes user or role from the allowlist.
+
+The local allowlist will be disabled if all users are removed.
+
+**Examples:**
+    - ``[p]localallowlist remove @26 @Will`` - Removes two users from the local allowlist.
+    - ``[p]localallowlist remove 262626262626262626`` - Removes a user by ID.
+    - ``[p]localallowlist remove "Super Admins"`` - Removes a role with a space in the name without mentioning.
+
+**Arguments:**
+    - ``<users_or_roles...>`` - The users or roles to remove from the local allowlist.
+
+.. _core-command-localblocklist:
+
+^^^^^^^^^^^^^^
+localblocklist
+^^^^^^^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]localblocklist 
+
+.. tip:: Alias: ``localblacklist``
+
+**Description**
+
+Commands to manage the server specific blocklist.
+
+Use ``[p]localblocklist clear`` to disable the blocklist
+
+.. _core-command-localblocklist-add:
+
+""""""""""""""""""
+localblocklist add
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]localblocklist add <users_or_roles...>
+
+**Description**
+
+Adds a user or role to the local blocklist.
+
+**Examples:**
+    - ``[p]localblocklist add @26 @Will`` - Adds two users to the local blocklist.
+    - ``[p]localblocklist add 262626262626262626`` - Blocks a user by ID.
+    - ``[p]localblocklist add "Bad Apples"`` - Blocks a role with a space in the name without mentioning.
+
+**Arguments:**
+    - ``<users_or_roles...>`` - The users or roles to add to the local blocklist.
+
+.. _core-command-localblocklist-clear:
+
+""""""""""""""""""""
+localblocklist clear
+""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]localblocklist clear 
+
+**Description**
+
+Clears the server blocklist.
+
+This disabled the server blocklist and clears all entries.
+
+**Example:**
+    - ``[p]blocklist clear``
+
+.. _core-command-localblocklist-list:
+
+"""""""""""""""""""
+localblocklist list
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]localblocklist list 
+
+**Description**
+
+Lists users and roles on the server blocklist.
+
+**Example:**
+    - ``[p]localblocklist list``
+
+.. _core-command-localblocklist-remove:
+
+"""""""""""""""""""""
+localblocklist remove
+"""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]localblocklist remove <users_or_roles...>
+
+**Description**
+
+Removes user or role from blocklist.
+
+**Examples:**
+    - ``[p]localblocklist remove @26 @Will`` - Removes two users from the local blocklist.
+    - ``[p]localblocklist remove 262626262626262626`` - Unblocks a user by ID.
+    - ``[p]localblocklist remove "Bad Apples"`` - Unblocks a role with a space in the name without mentioning.
+
+**Arguments:**
+    - ``<users_or_roles...>`` - The users or roles to remove from the local blocklist.
+
+.. _core-command-modlogset:
+
+^^^^^^^^^
+modlogset
+^^^^^^^^^
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modlogset 
+
+**Description**
+
+Manage modlog settings.
+
+.. _core-command-modlogset-cases:
+
+"""""""""""""""
+modlogset cases
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modlogset cases [action]
+
+**Description**
+
+Enable or disable case creation for a mod action, like disabling warnings, enabling bans, etc.
+
+**Examples:**
+    - ``[p]modlogset cases kick`` - Enables/disables modlog messages for kicks.
+    - ``[p]modlogset cases ban`` - Enables/disables modlog messages for bans.
+
+**Arguments:**
+    - ``[action]`` - The type of mod action to be enabled/disabled for case creation.
+
+
+.. _core-command-modlogset-modlog:
+
+""""""""""""""""
+modlogset modlog
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modlogset modlog [channel]
+
+.. tip:: Alias: ``modlogset channel``
+
+**Description**
+
+Set a channel as the modlog.
+
+**Arguments**
+
+* ``[channel]``: The channel to set as the modlog. If omitted, the modlog will be disabled.
+
+.. _core-command-modlogset-resetcases:
+
+""""""""""""""""""""
+modlogset resetcases
+""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modlogset resetcases 
+
+**Description**
+
+Reset all modlog cases in this server.
+
+.. _core-command-mydata:
+
+^^^^^^
+mydata
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata 
+
+**Description**
+
+Commands which interact with the data Red has about you.
+
+More information can be found in the :doc:`End User Data Documentation.<../red_core_data_statement>`
+
+.. _core-command-mydata-3rdparty:
+
+"""""""""""""""
+mydata 3rdparty
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata 3rdparty 
+
+**Description**
+
+View the End User Data statements of each 3rd-party module.
+
+This will send an attachment with the End User Data statements of all loaded 3rd party cogs.
+
+**Example:**
+    - ``[p]mydata 3rdparty``
+
+.. _core-command-mydata-forgetme:
+
+"""""""""""""""
+mydata forgetme
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata forgetme 
+
+**Description**
+
+Have Red forget what it knows about you.
+
+This may not remove all data about you, data needed for operation,
+such as command cooldowns will be kept until no longer necessary.
+
+Further interactions with Red may cause it to learn about you again.
+
+**Example:**
+    - ``[p]mydata forgetme``
+
+.. _core-command-mydata-getmydata:
+
+""""""""""""""""
+mydata getmydata
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata getmydata 
+
+**Description**
+
+[Coming Soon] Get what data Red has about you.
+
+.. _core-command-mydata-ownermanagement:
+
+""""""""""""""""""""""
+mydata ownermanagement
+""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata ownermanagement 
+
+**Description**
+
+Commands for more complete data handling.
+
+.. _core-command-mydata-ownermanagement-allowuserdeletions:
+
+"""""""""""""""""""""""""""""""""""""""""
+mydata ownermanagement allowuserdeletions
+"""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata ownermanagement allowuserdeletions 
+
+**Description**
+
+Set the bot to allow users to request a data deletion.
+
+This is on by default.
+Opposite of ``[p]mydata ownermanagement disallowuserdeletions``
+
+**Example:**
+    - ``[p]mydata ownermanagement allowuserdeletions``
+
+.. _core-command-mydata-ownermanagement-deleteforuser:
+
+""""""""""""""""""""""""""""""""""""
+mydata ownermanagement deleteforuser
+""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata ownermanagement deleteforuser <user_id>
+
+**Description**
+
+Delete data Red has about a user for a user.
+
+This will cause the bot to get rid of or disassociate a lot of non-operational data from the specified user.
+Users have access to a different command for this unless they can't interact with the bot at all.
+This is a mostly safe operation, but you should not use it unless processing a request from this user as it may impact their usage of the bot.
+
+**Arguments:**
+    - ``<user_id>`` - The id of the user whose data would be deleted.
+
+.. _core-command-mydata-ownermanagement-deleteuserasowner:
+
+""""""""""""""""""""""""""""""""""""""""
+mydata ownermanagement deleteuserasowner
+""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata ownermanagement deleteuserasowner <user_id>
+
+**Description**
+
+Delete data Red has about a user.
+
+This will cause the bot to get rid of or disassociate a lot of data about the specified user.
+This may include more than just end user data, including anti abuse records.
+
+**Arguments:**
+    - ``<user_id>`` - The id of the user whose data would be deleted.
+
+.. _core-command-mydata-ownermanagement-disallowuserdeletions:
+
+""""""""""""""""""""""""""""""""""""""""""""
+mydata ownermanagement disallowuserdeletions
+""""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata ownermanagement disallowuserdeletions 
+
+**Description**
+
+Set the bot to not allow users to request a data deletion.
+
+Opposite of ``[p]mydata ownermanagement allowuserdeletions``
+
+**Example:**
+    - ``[p]mydata ownermanagement disallowuserdeletions``
+
+.. _core-command-mydata-ownermanagement-processdiscordrequest:
+
+""""""""""""""""""""""""""""""""""""""""""""
+mydata ownermanagement processdiscordrequest
+""""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata ownermanagement processdiscordrequest <user_id>
+
+**Description**
+
+Handle a deletion request from Discord.
+
+This will cause the bot to get rid of or disassociate all data from the specified user ID.
+You should not use this unless Discord has specifically requested this with regard to a deleted user.
+This will remove the user from various anti-abuse measures.
+If you are processing a manual request from a user, you may want ``[p]mydata ownermanagement deleteforuser`` instead.
+
+**Arguments:**
+    - ``<user_id>`` - The id of the user whose data would be deleted.
+
+.. _core-command-mydata-ownermanagement-setuserdeletionlevel:
+
+"""""""""""""""""""""""""""""""""""""""""""
+mydata ownermanagement setuserdeletionlevel
+"""""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata ownermanagement setuserdeletionlevel <level>
+
+**Description**
+
+Sets how user deletions are treated.
+
+**Example:**
+    - ``[p]mydata ownermanagement setuserdeletionlevel 1``
+
+**Arguments:**
+    - ``<level>`` - The strictness level for user deletion. See Level guide below.
+
+Level:
+    - ``0``: What users can delete is left entirely up to each cog.
+    - ``1``: Cogs should delete anything the cog doesn't need about the user.
+
+.. _core-command-mydata-whatdata:
+
+"""""""""""""""
+mydata whatdata
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mydata whatdata 
+
+**Description**
+
+Find out what type of data Red stores and why.
+
+**Example:**
+    - ``[p]mydata whatdata``
+
+.. _core-command-reload:
+
+^^^^^^
+reload
+^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]reload <cogs...>
+
+**Description**
+
+Reloads cog packages.
+
+This will unload and then load the specified cogs.
+
+Cogs that were not loaded will only be loaded.
+
+**Examples:**
+    - ``[p]reload general`` - Unloads then loads the ``general`` cog.
+    - ``[p]reload admin mod mutes`` - Unloads then loads multiple cogs.
+
+**Arguments:**
+    - ``<cogs...>`` - The cog packages to reload.
+
+.. _core-command-restart:
+
+^^^^^^^
+restart
+^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]restart [silently=False]
+
+**Description**
+
+Attempts to restart Red.
+
+Makes Red quit with exit code 26.
+The restart is not guaranteed: it must be dealt with by the process manager in use.
+
+**Examples:**
+    - ``[p]restart``
+    - ``[p]restart True`` - Restarts silently.
+
+**Arguments:**
+    - ``[silently]`` - Whether to skip sending the restart message. Defaults to False.
+
+.. _core-command-servers:
+
+^^^^^^^
+servers
+^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]servers 
+
+**Description**
+
+Lists the servers Red is currently in.
+
+.. Note:: This command is interactive.
+
+
+.. _core-command-set:
+
+^^^
+set
+^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set 
+
+**Description**
+
+Commands for changing Red's settings.
+
+.. _core-command-set-api:
+
+"""""""
+set api
+"""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set api <service> <tokens>
+
+**Description**
+
+Commands to set, list or remove various external API tokens.
+
+This setting will be asked for by some 3rd party cogs and some core cogs.
+
+To add the keys provide the service name and the tokens as a comma separated
+list of key,values as described by the cog requesting this command.
+
+.. Note:: API tokens are sensitive, so this command should only be used in a private channel or in DM with the bot.
+
+
+**Examples:**
+    - ``[p]set api spotify redirect_uri localhost``
+    - ``[p]set api github client_id,whoops client_secret,whoops``
+
+**Arguments:**
+    - ``<service>`` - The service you're adding tokens to.
+    - ``<tokens>`` - Pairs of token keys and values. The key and value should be separated by one of `` ``, ``,``, or ``;``.
+
+.. _core-command-set-api-list:
+
+""""""""""""
+set api list
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set api list 
+
+**Description**
+
+Show all external API services along with their keys that have been set.
+
+Secrets are not shown.
+
+**Example:**
+    - ``[p]set api list``
+
+.. _core-command-set-api-remove:
+
+""""""""""""""
+set api remove
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set api remove <services...>
+
+**Description**
+
+Remove the given services with all their keys and tokens.
+
+**Examples:**
+    - ``[p]set api remove spotify``
+    - ``[p]set api remove github youtube``
+
+**Arguments:**
+    - ``<services...>`` - The services to remove.
+
+.. _core-command-set-bot:
+
+"""""""
+set bot
+"""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set bot
+
+**Description**
+
+Commands for changing Red's metadata.
+
+.. _core-command-set-bot-avatar:
+
+""""""""""""""
+set bot avatar
+""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set bot avatar [url]
+
+**Description**
+
+Sets Red's avatar
+
+Supports either an attachment or an image URL.
+
+**Examples:**
+    - ``[p]set bot avatar`` - With an image attachment, this will set the avatar.
+    - ``[p]set bot avatar`` - Without an attachment, this will show the command help.
+    - ``[p]set bot avatar https://links.flaree.xyz/k95`` - Sets the avatar to the provided url.
+
+**Arguments:**
+    - ``[url]`` - An image url to be used as an avatar. Leave blank when uploading an attachment.
+
+.. _core-command-set-bot-avatar-remove:
+
+"""""""""""""""""""""
+set bot avatar remove
+"""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set bot avatar remove 
+
+.. tip:: Alias: ``set bot avatar clear``
+
+**Description**
+
+Removes Red's avatar.
+
+**Example:**
+    - ``[p]set bot avatar remove``
+
+.. _core-command-set-bot-custominfo:
+
+""""""""""""""""""
+set bot custominfo
+""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set bot custominfo [text]
+
+**Description**
+
+Customizes a section of ``[p]info``.
+
+The maximum amount of allowed characters is 1024.
+Supports markdown, links and "mentions".
+
+Link example: ``[My link](https://example.com)``
+
+**Examples:**
+    - ``[p]set bot custominfo >>> I can use **markdown** such as quotes, ||spoilers|| and multiple lines.``
+    - ``[p]set bot custominfo Join my [support server](discord.gg/discord)!``
+    - ``[p]set bot custominfo`` - Removes custom info text.
+
+**Arguments:**
+    - ``[text]`` - The custom info text.
+
+.. _core-command-set-bot-description:
+
+"""""""""""""""""""
+set bot description
+"""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set bot description [description]
+
+**Description**
+
+Sets the bot's description.
+
+Use without a description to reset.
+This is shown in a few locations, including the help menu.
+
+The maximum description length is 250 characters to ensure it displays properly.
+
+The default is "Red V3".
+
+**Examples:**
+    - ``[p]set bot description`` - Resets the description to the default setting.
+    - ``[p]set bot description MyBot: A Red V3 Bot``
+
+**Arguments:**
+    - ``[description]`` - The description to use for this bot. Leave blank to reset to the default.
+
+.. _core-command-set-bot-nickname:
+
+""""""""""""""""
+set bot nickname
+""""""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set bot nickname [nickname]
+
+**Description**
+
+Sets Red's nickname for the current server.
+
+Maximum length for a nickname is 32 characters.
+
+**Example:**
+    - ``[p]set bot nickname 🎃 SpookyBot 🎃``
+
+**Arguments:**
+    - ``[nickname]`` - The nickname to give the bot. Leave blank to clear the current nickname.
+
+.. _core-command-set-bot-username:
+
+""""""""""""""""
+set bot username
+""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set bot username <username>
+
+.. tip:: Alias: ``set bot name``
+
+**Description**
+
+Sets Red's username.
+
+Maximum length for a username is 32 characters.
+
+.. Note:: The username of a verified bot cannot be manually changed.
+
+    Please contact Discord support to change it.
+
+**Example:**
+    - ``[p]set bot username BaguetteBot``
+
+**Arguments:**
+    - ``<username>`` - The username to give the bot.
+
+.. _core-command-set-colour:
+
+""""""""""
+set colour
+""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set colour [colour]
+
+.. tip:: Alias: ``set color``
+
+**Description**
+
+Sets a default colour to be used for the bot's embeds.
+
+Acceptable values for the colour parameter can be found at:
+
+https://discordpy.readthedocs.io/en/stable/ext/commands/api.html#discord.ext.commands.ColourConverter
+
+**Examples:**
+    - ``[p]set colour dark red``
+    - ``[p]set colour blurple``
+    - ``[p]set colour 0x5DADE2``
+    - ``[p]set color 0x#FDFEFE``
+    - ``[p]set color #7F8C8D``
+
+**Arguments:**
+    - ``[colour]`` - The colour to use for embeds. Leave blank to set to the default value (red).
+
+.. _core-command-set-deletedelay:
+
+"""""""""""""""
+set deletedelay
+"""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set deletedelay [time]
+
+**Description**
+
+Set the delay until the bot removes the command message.
+
+Must be between -1 and 60.
+
+Set to -1 to disable this feature.
+
+This is only applied to the current server and not globally.
+
+**Examples:**
+    - ``[p]set deletedelay`` - Shows the current delete delay setting.
+    - ``[p]set deletedelay 60`` - Sets the delete delay to the max of 60 seconds.
+    - ``[p]set deletedelay -1`` - Disables deleting command messages.
+
+**Arguments:**
+    - ``[time]`` - The seconds to wait before deleting the command message. Use -1 to disable.
+
+.. _core-command-set-errormsg:
+
+""""""""""""
+set errormsg
+""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set errormsg [msg]
+
+**Description**
+
+Set the message that will be sent on uncaught bot errors.
+
+To include the command name in the message, use the ``{command}`` placeholder.
+
+If you omit the ``msg`` argument, the message will be reset to the default one.
+
+**Examples:**
+    - ``[p]set errormsg`` - Resets the error message back to the default: "Error in command '{command}'.". If the command invoker is one of the bot owners, the message will also include "Check your console or logs for details.".
+    - ``[p]set errormsg Oops, the command {command} has failed! Please try again later.`` - Sets the error message to a custom one.
+
+**Arguments:**
+    - ``[msg]`` - The custom error message. Must be less than 1000 characters. Omit to reset to the default one.
+
+.. _core-command-set-fuzzy:
+
+"""""""""
+set fuzzy
+"""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set fuzzy 
+
+**Description**
+
+Toggle whether to enable fuzzy command search in DMs.
+
+This allows the bot to identify potential misspelled commands and offer corrections.
+
+Default is for fuzzy command search to be disabled.
+
+**Example:**
+    - ``[p]set fuzzy``
+
+.. _core-command-set-locale:
+
+""""""""""
+set locale
+""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set locale <language_code>
+
+**Description**
+
+Changes the bot's locale in this server.
+
+Go to `Red's Crowdin page <https://translate.discord.red>`_ to see locales that are available with translations.
+
+Use "default" to return to the bot's default set language.
+
+If you want to change bot's global locale, see ``[p]set locale global`` command.
+
+**Examples:**
+    - ``[p]set locale en-US``
+    - ``[p]set locale de-DE``
+    - ``[p]set locale fr-FR``
+    - ``[p]set locale pl-PL``
+    - ``[p]set locale default`` - Resets to the global default locale.
+
+**Arguments:**
+    - ``<language_code>`` - The default locale to use for the bot. This can be any language code with country code included.
+
+.. _core-command-set-locale-global:
+
+"""""""""""""""""
+set locale global
+"""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set locale global <language_code>
+
+**Description**
+
+Changes the bot's default locale.
+
+This will be used when a server has not set a locale, or in DMs.
+
+Go to `Red's Crowdin page <https://translate.discord.red>`_ to see locales that are available with translations.
+
+To reset to English, use "en-US".
+
+**Examples:**
+    - ``[p]set locale global en-US``
+    - ``[p]set locale global de-DE``
+    - ``[p]set locale global fr-FR``
+    - ``[p]set locale global pl-PL``
+
+**Arguments:**
+    - ``<language_code>`` - The default locale to use for the bot. This can be any language code with country code included.
+
+.. _core-command-set-locale-server:
+
+"""""""""""""""""
+set locale server
+"""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set locale server <language_code>
+
+.. tip:: Aliases: ``set locale local``, ``set locale guild``
+
+**Description**
+
+Changes the bot's locale in this server.
+
+Go to `Red's Crowdin page <https://translate.discord.red>`_ to see locales that are available with translations.
+
+Use "default" to return to the bot's default set language.
+
+**Examples:**
+    - ``[p]set locale server en-US``
+    - ``[p]set locale server de-DE``
+    - ``[p]set locale server fr-FR``
+    - ``[p]set locale server pl-PL``
+    - ``[p]set locale server default`` - Resets to the global default locale.
+
+**Arguments:**
+    - ``<language_code>`` - The default locale to use for the bot. This can be any language code with country code included.
+
+.. _core-command-set-ownernotifications:
+
+""""""""""""""""""""""
+set ownernotifications
+""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set ownernotifications 
+
+**Description**
+
+Commands for configuring owner notifications.
+
+Owner notifications include usage of ``[p]contact`` and available Red updates.
+
+.. _core-command-set-ownernotifications-adddestination:
+
+"""""""""""""""""""""""""""""""""""""
+set ownernotifications adddestination
+"""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set ownernotifications adddestination <channel>
+
+**Description**
+
+Adds a destination text channel to receive owner notifications.
+
+**Examples:**
+    - ``[p]set ownernotifications adddestination #owner-notifications``
+    - ``[p]set ownernotifications adddestination 168091848718417920`` - Accepts channel IDs.
+
+**Arguments:**
+    - ``<channel>`` - The channel to send owner notifications to.
+
+.. _core-command-set-ownernotifications-listdestinations:
+
+"""""""""""""""""""""""""""""""""""""""
+set ownernotifications listdestinations
+"""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set ownernotifications listdestinations 
+
+**Description**
+
+Lists the configured extra destinations for owner notifications.
+
+**Example:**
+    - ``[p]set ownernotifications listdestinations``
+
+.. _core-command-set-ownernotifications-optin:
+
+""""""""""""""""""""""""""""
+set ownernotifications optin
+""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set ownernotifications optin 
+
+**Description**
+
+Opt-in on receiving owner notifications.
+
+This is the default state.
+
+.. Note:: This will only resume sending owner notifications to your DMs.
+
+    Additional owners and destinations will not be affected.
+
+**Example:**
+    - ``[p]set ownernotifications optin``
+
+.. _core-command-set-ownernotifications-optout:
+
+"""""""""""""""""""""""""""""
+set ownernotifications optout
+"""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set ownernotifications optout 
+
+**Description**
+
+Opt-out of receiving owner notifications.
+
+.. Note:: This will only stop sending owner notifications to your DMs.
+
+    Additional owners and destinations will still receive notifications.
+
+**Example:**
+    - ``[p]set ownernotifications optout``
+
+.. _core-command-set-ownernotifications-removedestination:
+
+""""""""""""""""""""""""""""""""""""""""
+set ownernotifications removedestination
+""""""""""""""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set ownernotifications removedestination <channel>
+
+.. tip:: Aliases: ``set ownernotifications remdestination``, ``set ownernotifications deletedestination``, ``set ownernotifications deldestination``
+
+**Description**
+
+Removes a destination text channel from receiving owner notifications.
+
+**Examples:**
+    - ``[p]set ownernotifications removedestination #owner-notifications``
+    - ``[p]set ownernotifications deletedestination 168091848718417920`` - Accepts channel IDs.
+
+**Arguments:**
+    - ``<channel>`` - The channel to stop sending owner notifications to.
+
+.. _core-command-set-prefix:
+
+""""""""""
+set prefix
+""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set prefix <prefixes...>
+
+.. tip:: Alias: ``set prefixes``
+
+**Description**
+
+Sets Red's global prefix(es).
+
+.. Warning:: This is not additive. It will replace all current prefixes.
+
+
+See also the ``--mentionable`` flag to enable mentioning the bot as the prefix.
+
+**Examples:**
+    - ``[p]set prefix !``
+    - ``[p]set prefix "! "`` - Quotes are needed to use spaces in prefixes.
+    - ``[p]set prefix "@Red "`` - This uses a mention as the prefix. See also the ``--mentionable`` flag.
+    - ``[p]set prefix ! ? .`` - Sets multiple prefixes.
+
+**Arguments:**
+    - ``<prefixes...>`` - The prefixes the bot will respond to globally.
+
+.. _core-command-set-regionalformat:
+
+""""""""""""""""""
+set regionalformat
+""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set regionalformat <language_code>
+
+.. tip:: Alias: ``set region``
+
+**Description**
+
+Changes the bot's regional format in this server. This is used for formatting date, time and numbers.
+
+``language_code`` can be any language code with country code included, e.g. ``en-US``, ``de-DE``, ``fr-FR``, ``pl-PL``, etc.
+Pass "reset" to ``language_code`` to base regional formatting on bot's locale in this server.
+
+If you want to change bot's global regional format, see ``[p]set regionalformat global`` command.
+
+**Examples:**
+    - ``[p]set regionalformat en-US``
+    - ``[p]set region de-DE``
+    - ``[p]set regionalformat reset`` - Resets to the locale.
+
+**Arguments:**
+    - ``[language_code]`` - The region format to use for the bot in this server.
+
+.. _core-command-set-regionalformat-global:
+
+"""""""""""""""""""""""""
+set regionalformat global
+"""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set regionalformat global <language_code>
+
+**Description**
+
+Changes the bot's regional format. This is used for formatting date, time and numbers.
+
+``language_code`` can be any language code with country code included, e.g. ``en-US``, ``de-DE``, ``fr-FR``, ``pl-PL``, etc.
+Pass "reset" to ``language_code`` to base regional formatting on bot's locale.
+
+**Examples:**
+    - ``[p]set regionalformat global en-US``
+    - ``[p]set region global de-DE``
+    - ``[p]set regionalformat global reset`` - Resets to the locale.
+
+**Arguments:**
+    - ``[language_code]`` - The default region format to use for the bot.
+
+.. _core-command-set-regionalformat-server:
+
+"""""""""""""""""""""""""
+set regionalformat server
+"""""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set regionalformat server <language_code>
+
+.. tip:: Aliases: ``set regionalformat local``, ``set regionalformat guild``
+
+**Description**
+
+Changes the bot's regional format in this server. This is used for formatting date, time and numbers.
+
+``language_code`` can be any language code with country code included, e.g. ``en-US``, ``de-DE``, ``fr-FR``, ``pl-PL``, etc.
+Pass "reset" to ``language_code`` to base regional formatting on bot's locale in this server.
+
+**Examples:**
+    - ``[p]set regionalformat server en-US``
+    - ``[p]set region local de-DE``
+    - ``[p]set regionalformat server reset`` - Resets to the locale.
+
+**Arguments:**
+    - ``[language_code]`` - The region format to use for the bot in this server.
+
+.. _core-command-set-roles:
+
+"""""""""
+set roles
+"""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set roles
+
+**Description**
+
+Set server's admin and mod roles for Red.
+
+.. _core-command-set-roles-addadminrole:
+
+""""""""""""""""""""""
+set roles addadminrole
+""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set roles addadminrole <role>
+
+**Description**
+
+Adds an admin role for this guild.
+
+Admins have the same access as Mods, plus additional admin level commands like:
+ - ``[p]set serverprefix``
+ - ``[p]addrole``
+ - ``[p]ban``
+ - ``[p]ignore guild``
+
+ And more.
+
+ **Examples:**
+    - ``[p]set roles addadminrole @Admins``
+    - ``[p]set roles addadminrole Super Admins``
+
+**Arguments:**
+    - ``<role>`` - The role to add as an admin.
+
+.. _core-command-set-roles-addmodrole:
+
+""""""""""""""""""""
+set roles addmodrole
+""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set roles addmodrole <role>
+
+**Description**
+
+Adds a moderator role for this guild.
+
+This grants access to moderator level commands like:
+ - ``[p]mute``
+ - ``[p]cleanup``
+ - ``[p]customcommand create``
+
+ And more.
+
+ **Examples:**
+    - ``[p]set roles addmodrole @Mods``
+    - ``[p]set roles addmodrole Loyal Helpers``
+
+**Arguments:**
+    - ``<role>`` - The role to add as a moderator.
+
+.. _core-command-set-roles-removeadminrole:
+
+"""""""""""""""""""""""""
+set roles removeadminrole
+"""""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set roles removeadminrole <role>
+
+.. tip:: Aliases: ``set roles remadmindrole``, ``set roles deladminrole``, ``set roles deleteadminrole``
+
+**Description**
+
+Removes an admin role for this guild.
+
+**Examples:**
+    - ``[p]set roles removeadminrole @Admins``
+    - ``[p]set roles removeadminrole Super Admins``
+
+**Arguments:**
+    - ``<role>`` - The role to remove from being an admin.
+
+.. _core-command-set-roles-removemodrole:
+
+"""""""""""""""""""""""
+set roles removemodrole
+"""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set roles removemodrole <role>
+
+.. tip:: Aliases: ``set roles remmodrole``, ``set roles delmodrole``, ``set roles deletemodrole``
+
+**Description**
+
+Removes a mod role for this guild.
+
+**Examples:**
+    - ``[p]set roles removemodrole @Mods``
+    - ``[p]set roles removemodrole Loyal Helpers``
+
+**Arguments:**
+    - ``<role>`` - The role to remove from being a moderator.
+
+.. _core-command-set-serverfuzzy:
+
+"""""""""""""""
+set serverfuzzy
+"""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set serverfuzzy 
+
+**Description**
+
+Toggle whether to enable fuzzy command search for the server.
+
+This allows the bot to identify potential misspelled commands and offer corrections.
+
+.. Note:: This can be processor intensive and may be unsuitable for larger servers.
+
+
+Default is for fuzzy command search to be disabled.
+
+**Example:**
+    - ``[p]set serverfuzzy``
+
+.. _core-command-set-serverprefix:
+
+""""""""""""""""
+set serverprefix
+""""""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set serverprefix [prefixes...]
+
+.. tip:: Alias: ``set serverprefixes``
+
+**Description**
+
+Sets Red's server prefix(es).
+
+.. Warning:: This will override global prefixes, the bot will not respond to any global prefixes in this server.
+
+    This is not additive. It will replace all current server prefixes.
+
+    You cannot have a prefix with more than 25 characters.
+
+**Examples:**
+    - ``[p]set serverprefix !``
+    - ``[p]set serverprefix "! "`` - Quotes are needed to use spaces in prefixes.
+    - ``[p]set serverprefix "@Red "`` - This uses a mention as the prefix.
+    - ``[p]set serverprefix ! ? .`` - Sets multiple prefixes.
+
+**Arguments:**
+    - ``[prefixes...]`` - The prefixes the bot will respond to on this server. Leave blank to clear server prefixes.
+
+.. _core-command-set-showsettings:
+
+""""""""""""""""
+set showsettings
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set showsettings 
+
+**Description**
+
+Show the current settings for Red.
+
+.. _core-command-set-status:
+
+""""""""""
+set status
+""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set status
+
+**Description**
+
+Commands for setting Red's status.
+
+.. _core-command-set-status-competing:
+
+""""""""""""""""""""
+set status competing
+""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set status competing [competing]
+
+**Description**
+
+Sets Red's competing status.
+
+This will appear as ``Competing in <competing>``.
+
+Maximum length for a competing status is 128 characters.
+
+**Examples:**
+    - ``[p]set status competing`` - Clears the activity status.
+    - ``[p]set status competing London 2012 Olympic Games``
+
+**Arguments:**
+    - ``[competing]`` - The text to follow ``Competing in``. Leave blank to clear the current activity status.
+
+.. _core-command-set-status-dnd:
+
+""""""""""""""
+set status dnd
+""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set status dnd
+
+.. tip:: Aliases: ``set status donotdisturb``, ``set status busy``
+
+**Description**
+
+Sets Red's status to do not disturb.
+
+.. _core-command-set-status-idle:
+
+"""""""""""""""
+set status idle
+"""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set status idle
+
+.. tip:: Aliases: ``set status away``, ``set status afk``
+
+**Description**
+
+Sets Red's status to idle.
+
+.. _core-command-set-status-invisible:
+
+""""""""""""""""""""
+set status invisible
+""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set status invisible
+
+.. tip:: Alias: ``set status offline``
+
+**Description**
+
+Sets Red's status to invisible.
+
+.. _core-command-set-status-listening:
+
+""""""""""""""""""""
+set status listening
+""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set status listening [listening]
+
+**Description**
+
+Sets Red's listening status.
+
+This will appear as ``Listening to <listening>``.
+
+Maximum length for a listening status is 128 characters.
+
+**Examples:**
+    - ``[p]set status listening`` - Clears the activity status.
+    - ``[p]set status listening jams``
+
+**Arguments:**
+    - ``[listening]`` - The text to follow ``Listening to``. Leave blank to clear the current activity status.
+
+.. _core-command-set-status-online:
+
+"""""""""""""""""
+set status online
+"""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set status online
+
+**Description**
+
+Sets Red's status to online.
+
+.. _core-command-set-status-playing:
+
+""""""""""""""""""
+set status playing
+""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set status playing [game]
+
+.. tip:: Alias: ``set status game``
+
+**Description**
+
+Sets Red's playing status.
+
+This will appear as ``Playing <game>`` or ``PLAYING A GAME: <game>`` depending on the context.
+
+Maximum length for a playing status is 128 characters.
+
+**Examples:**
+    - ``[p]set status playing`` - Clears the activity status.
+    - ``[p]set status playing the keyboard``
+
+**Arguments:**
+    - ``[game]`` - The text to follow ``Playing``. Leave blank to clear the current activity status.
+
+.. _core-command-set-status-streaming:
+
+""""""""""""""""""""
+set status streaming
+""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set status streaming [(<streamer> <stream_title>)]
+
+.. tip:: Aliases: ``set status stream``, ``set status twitch``
+
+**Description**
+
+Sets Red's streaming status to a twitch stream.
+
+This will appear as ``Streaming <stream_title>`` or ``LIVE ON TWITCH`` depending on the context.
+It will also include a ``Watch`` button with a twitch.tv url for the provided streamer.
+
+Maximum length for a stream title is 128 characters.
+
+Leaving both streamer and stream_title empty will clear it.
+
+**Examples:**
+    - ``[p]set status stream`` - Clears the activity status.
+    - ``[p]set status stream 26 Twentysix is streaming`` - Sets the stream to ``https://www.twitch.tv/26``.
+    - ``[p]set status stream https://twitch.tv/26 Twentysix is streaming`` - Sets the URL manually.
+
+**Arguments:**
+    - ``<streamer>`` - The twitch streamer to provide a link to. This can be their twitch name or the entire URL.
+    - ``<stream_title>`` - The text to follow ``Streaming`` in the status.
+
+.. _core-command-set-status-watching:
+
+"""""""""""""""""""
+set status watching
+"""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set status watching [watching]
+
+**Description**
+
+Sets Red's watching status.
+
+This will appear as ``Watching <watching>``.
+
+Maximum length for a watching status is 128 characters.
+
+**Examples:**
+    - ``[p]set status watching`` - Clears the activity status.
+    - ``[p]set status watching [p]help``
+
+**Arguments:**
+    - ``[watching]`` - The text to follow ``Watching``. Leave blank to clear the current activity status.
+
+.. _core-command-set-usebotcolour:
+
+""""""""""""""""
+set usebotcolour
+""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set usebotcolour 
+
+.. tip:: Alias: ``set usebotcolor``
+
+**Description**
+
+Toggle whether to use the bot owner-configured colour for embeds.
+
+Default is to use the bot's configured colour.
+Otherwise, the colour used will be the colour of the bot's top role.
+
+**Example:**
+    - ``[p]set usebotcolour``
+    
+.. _core-command-set-usebuttons:
+
+""""""""""""""
+set usebuttons
+""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]set usebuttons [use_buttons]
+    
+**Description**
+
+Set a global bot variable for using buttons in menus. When enabled, all usage of
+cores menus API will use buttons instead of reactions. This defaults to False.
+Using this without a setting will toggle.
+
+**Examples:**
+- ``[p]set usebuttons True`` - Enables using buttons.
+- ``[p]helpset usebuttons`` - Toggles the value.
+
+**Arguments:**
+    - ``[use_buttons]`` - Whether to use buttons. Leave blank to toggle.
+
+.. _core-command-shutdown:
+
+^^^^^^^^
+shutdown
+^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]shutdown [silently=False]
+
+**Description**
+
+Shuts down the bot.
+
+Allows Red to shut down gracefully.
+
+This is the recommended method for shutting down the bot.
+
+**Examples:**
+    - ``[p]shutdown``
+    - ``[p]shutdown True`` - Shutdowns silently.
+
+**Arguments:**
+    - ``[silently]`` - Whether to skip sending the shutdown message. Defaults to False.
+
+.. _core-command-slash:
+
+^^^^^
+slash
+^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]slash 
+
+**Description**
+
+Base command for managing what application commands are able to be used on Red.
+
+.. _core-command-slash-disable:
+
+"""""""""""""
+slash disable
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]slash disable <command_name> [command_type]
+    
+**Description**
+
+Marks an application command as being disabled, preventing it from being added to the bot.
+See commands available to disable with ``[p]slash list``. This command does NOT sync the
+enabled commands with Discord, that must be done manually with ``[p]slash sync`` for
+commands to appear in users' clients.
+
+**Arguments:**
+    - ``<command_name>`` - The command name to disable. Only the top level name of a group command should be used.
+    - ``[command_type]`` - What type of application command to disable. Must be one of ``slash``, ``message``, or ``user``. Defaults to ``slash``.
+
+.. _core-command-slash-disablecog:
+
+""""""""""""""""
+slash disablecog
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]slash disablecog <cog_name>
+    
+**Description**
+
+Marks all application commands in a cog as being disabled, preventing them from being
+added to the bot. See a list of cogs with application commands with ``[p]slash list``.
+This command does NOT sync the enabled commands with Discord, that must be done manually
+with ``[p]slash sync`` for commands to appear in users' clients.
+
+**Arguments:**
+    - ``<cog_name>`` - The cog to disable commands from. This argument is case sensitive.
+
+.. _core-command-slash-enable:
+
+""""""""""""
+slash enable
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]slash enable <command_name> [command_type]
+    
+**Description**
+
+Marks an application command as being enabled, allowing it to be added to the bot.
+See commands available to enable with ``[p]slash list``. This command does NOT sync the
+enabled commands with Discord, that must be done manually with ``[p]slash sync`` for
+commands to appear in users' clients.
+
+**Arguments:**
+    - ``<command_name>`` - The command name to enable. Only the top level name of a group command should be used.
+    - ``[command_type]`` - What type of application command to enable. Must be one of ``slash``, ``message``, or ``user``. Defaults to ``slash``.
+
+.. _core-command-slash-enablecog:
+
+"""""""""""""""
+slash enablecog
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]slash enablecog <cog_name>
+    
+**Description**
+
+Marks all application commands in a cog as being enabled, allowing them to be
+added to the bot. See a list of cogs with application commands with ``[p]slash list``.
+This command does NOT sync the enabled commands with Discord, that must be done manually
+with ``[p]slash sync`` for commands to appear in users' clients.
+
+**Arguments:**
+    - ``<cog_name>`` - The cog to enable commands from. This argument is case sensitive.
+
+.. _core-command-slash-list:
+
+""""""""""
+slash list
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]slash list
+    
+**Description**
+
+List the slash commands the bot can see, and whether or not they are enabled.
+
+This command shows the state that will be changed to when ``[p]slash sync`` is run.
+Commands from the same cog are grouped, with the cog name as the header.
+
+The prefix denotes the state of the command:
+- Commands starting with ``- `` have not yet been enabled.
+- Commands starting with ``+ `` have been manually enabled.
+- Commands starting with ``++`` have been enabled by the cog author, and cannot be disabled.
+
+.. _core-command-slash-sync:
+
+""""""""""
+slash sync
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]slash sync [guild]
+    
+**Description**
+
+Syncs the slash settings to discord.
+Settings from ``[p]slash list`` will be synced with discord, changing what commands appear for users.
+This should be run sparingly, make all necessary changes before running this command.
+        
+**Arguments:**
+    - ``[guild]`` - If provided, syncs commands for that guild. Otherwise, syncs global commands.
+
+.. _core-command-traceback:
+
+^^^^^^^^^
+traceback
+^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]traceback [public=False]
+
+**Description**
+
+Sends to the owner the last command exception that has occurred.
+
+If public (yes is specified), it will be sent to the chat instead.
+
+.. Warning:: Sending the traceback publicly can accidentally reveal sensitive information about your computer or configuration.
+
+
+**Examples:**
+    - ``[p]traceback`` - Sends the traceback to your DMs.
+    - ``[p]traceback True`` - Sends the last traceback in the current context.
+
+**Arguments:**
+    - ``[public]`` - Whether to send the traceback to the current context. Leave blank to send to your DMs.
+
+.. _core-command-unignore:
+
+^^^^^^^^
+unignore
+^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]unignore 
+
+**Description**
+
+Commands to remove servers or channels from the ignore list.
+
+.. _core-command-unignore-channel:
+
+""""""""""""""""
+unignore channel
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]unignore channel [channel]
+
+**Description**
+
+Remove a channel, thread, or category from the ignore list.
+
+Defaults to the current thread or channel.
+
+**Examples:**
+    - ``[p]unignore channel #general`` - Unignores commands in the #general channel.
+    - ``[p]unignore channel`` - Unignores commands in the current channel.
+    - ``[p]unignore channel "General Channels"`` - Use quotes for categories with spaces.
+    - ``[p]unignore channel 356236713347252226`` - Also accepts IDs. Use this method to unignore categories.
+
+**Arguments:**
+    - ``<channel>`` - The channel to unignore. This can also be a thread or category channel.
+
+.. _core-command-unignore-server:
+
+"""""""""""""""
+unignore server
+"""""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]unignore server 
+
+.. tip:: Alias: ``unignore guild``
+
+**Description**
+
+Remove this server from the ignore list.
+
+**Example:**
+    - ``[p]unignore server`` - Stops ignoring the current server
+
+.. _core-command-unload:
+
+^^^^^^
+unload
+^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]unload <cogs...>
+
+**Description**
+
+Unloads previously loaded cog packages.
+
+See packages available to unload with ``[p]cogs``.
+
+**Examples:**
+    - ``[p]unload general`` - Unloads the ``general`` cog.
+    - ``[p]unload admin mod mutes`` - Unloads multiple cogs.
+
+**Arguments:**
+    - ``<cogs...>`` - The cog packages to unload.
+
+.. _core-command-uptime:
+
+^^^^^^
+uptime
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]uptime 
+
+**Description**
+
+Shows Red's uptime.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/customcommands.rst

@@ -0,0 +1,294 @@
+.. _customcommands:
+
+==============
+CustomCommands
+==============
+
+This is the cog guide for the customcommands 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 customcom
+
+.. _customcommands-usage:
+
+-----
+Usage
+-----
+
+This cog contains commands for creating and managing custom commands that display text.
+
+These are useful for storing information members might need, like FAQ answers or invite links.
+Custom commands can be used by anyone by default, so be careful with pings.
+Commands can only be lowercase, and will not respond to any uppercase letters.
+
+
+.. _customcommands-commands:
+
+--------
+Commands
+--------
+
+.. _customcommands-command-customcom:
+
+^^^^^^^^^
+customcom
+^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom 
+
+.. tip:: Alias: ``cc``
+
+**Description**
+
+Base command for Custom Commands management.
+
+.. _customcommands-command-customcom-cooldown:
+
+""""""""""""""""""
+customcom cooldown
+""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom cooldown <command> [cooldown] [per=member]
+
+**Description**
+
+Set, edit, or view the cooldown for a custom command.
+
+You may set cooldowns per member, thread/channel, or guild. Multiple
+cooldowns may be set. All cooldowns must be cooled to call the
+custom command.
+
+Examples:
+    - ``[p]customcom cooldown pingrole``
+    - ``[p]customcom cooldown yourcommand 30``
+    - ``[p]cc cooldown mycommand 30 guild``
+
+**Arguments:**
+
+- ``<command>`` The custom command to check or set the cooldown.
+- ``[cooldown]`` The number of seconds to wait before allowing the command to be invoked again. If omitted, will instead return the current cooldown settings.
+- ``[per]`` The group to apply the cooldown on. Defaults to per member. Valid choices are server / guild, user / member, and channel.
+
+.. _customcommands-command-customcom-create:
+
+""""""""""""""""
+customcom create
+""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom create <command> <text>
+
+.. tip:: Alias: ``customcom add``
+
+**Description**
+
+Create custom commands.
+
+If a type is not specified, a simple CC will be created.
+CCs can be enhanced with arguments, see the guide
+:ref:`here <cog_customcom>`.
+
+.. _customcommands-command-customcom-create-random:
+
+"""""""""""""""""""""""
+customcom create random
+"""""""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom create random <command>
+
+**Description**
+
+Create a CC where it will randomly choose a response!
+
+Note: This command is interactive.
+
+**Arguments:**
+
+- ``<command>`` The command executed to return the text. Cast to lowercase.
+
+.. _customcommands-command-customcom-create-simple:
+
+"""""""""""""""""""""""
+customcom create simple
+"""""""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom create simple <command> <text>
+
+**Description**
+
+Add a simple custom command.
+
+Example:
+    - ``[p]customcom create simple yourcommand Text you want``
+
+**Arguments:**
+
+- ``<command>`` The command executed to return the text. Cast to lowercase.
+- ``<text>`` The text to return when executing the command. See guide for enhanced usage.
+
+.. _customcommands-command-customcom-delete:
+
+""""""""""""""""
+customcom delete
+""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom delete <command>
+
+.. tip:: Aliases: ``customcom del``, ``customcom remove``
+
+**Description**
+
+Delete a custom command.
+
+Example:
+    - ``[p]customcom delete yourcommand``
+
+**Arguments:**
+
+- ``<command>`` The custom command to delete.
+
+.. _customcommands-command-customcom-edit:
+
+""""""""""""""
+customcom edit
+""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom edit <command> [text]
+
+**Description**
+
+Edit a custom command.
+
+Example:
+    - ``[p]customcom edit yourcommand Text you want``
+
+**Arguments:**
+
+- ``<command>`` The custom command to edit.
+- ``<text>`` The new text to return when executing the command.
+
+.. _customcommands-command-customcom-list:
+
+""""""""""""""
+customcom list
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom list 
+
+**Description**
+
+List all available custom commands.
+
+The list displays a preview of each command's response, with
+markdown escaped and newlines replaced with spaces.
+
+.. _customcommands-command-customcom-raw:
+
+"""""""""""""
+customcom raw
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom raw <command>
+
+**Description**
+
+Get the raw response of a custom command, to get the proper markdown.
+
+This is helpful for copy and pasting.
+
+**Arguments:**
+
+- ``<command>`` The custom command to get the raw response of.
+
+.. _customcommands-command-customcom-search:
+
+""""""""""""""""
+customcom search
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom search <query>
+
+**Description**
+
+Searches through custom commands, according to the query.
+
+Uses fuzzy searching to find close matches.
+
+**Arguments:**
+
+- ``<query>`` The query to search for. Can be multiple words.
+
+.. _customcommands-command-customcom-show:
+
+""""""""""""""
+customcom show
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]customcom show <command_name>
+
+**Description**
+
+Shows a custom command's responses and its settings.
+
+**Arguments:**
+
+- ``<command_name>`` The custom command to show.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/dev.rst

@@ -0,0 +1,254 @@
+.. _dev:
+
+===
+Dev
+===
+
+This is the cog guide for the dev 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 dev
+
+.. _dev-usage:
+
+-----
+Usage
+-----
+
+Various development focused utilities. All commands in this cog are
+restricted to the bot owners.
+
+.. note::
+
+    Unlike other cogs, the Dev cog is only loaded if the bot is
+    started with the ``--dev`` flag.
+
+    .. warning::
+
+        It is not suggested that you run Dev in production. Many
+        of these cog's commands may cause down-the-line complications if
+        not used appropriately.
+
+.. _dev-commands:
+
+--------
+Commands
+--------
+
+.. _dev-command-bypasscooldowns:
+
+^^^^^^^^^^^^^^^
+bypasscooldowns
+^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]bypasscooldowns [toggle]
+
+**Description**
+
+Give bot owners the ability to bypass cooldowns. Note that this bypass
+does not persist through restarts/shutdowns.
+
+**Arguments**
+
+* ``[toggle]``: |bool-input| Otherwise, defaults to the inverse of the current setting.
+
+.. _dev-command-debug:
+
+^^^^^
+debug
+^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]debug <code>
+
+**Description**
+
+Evaluate a statement of python code.
+
+The bot will always respond with the return value of the code.
+If the return value of the code is a coroutine, it will be awaited,
+and the result of that will be the bot's response.
+
+Note: Only one statement may be evaluated. Using certain restricted
+keywords, e.g. yield, will result in a syntax error. For multiple
+lines or asynchronous code, see [p]repl or [p]eval.
+
+**Environment Variables**
+
+* ``ctx``: Command invocation context
+* ``bot``: The bot object
+* ``channel``: The current channel object
+* ``author``: The current author's member object
+* ``guild``: The current guild object
+* ``message``: The command's message object
+* ``aiohttp``: The aiohttp library
+* ``asyncio``: The asyncio library
+* ``discord``: The discord.py library
+* ``commands``: The redbot.core.commands module
+* ``cf``: The redbot.core.utils.chat_formatting module
+* ``_``: The result from the last dev command
+
+**Arguments**
+
+* ``<code>``: The statement to run.
+
+.. _dev-command-eval:
+
+^^^^
+eval
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]eval <body>
+
+**Description**
+
+Execute asynchronous code.
+
+This command wraps code into the body of an async function and then
+calls and awaits it. The bot will respond with anything printed to
+stdout, as well as the return value of the function.
+
+The code can be within a codeblock, inline code or neither, as long
+as they are not mixed and they are formatted correctly.
+
+**Environment Variables**
+
+* ``ctx``: Command invocation context
+* ``bot``: The bot object
+* ``channel``: The current channel object
+* ``author``: The current author's member object
+* ``guild``: The current guild object
+* ``message``: The command's message object
+* ``aiohttp``: The aiohttp library
+* ``asyncio``: The asyncio library
+* ``discord``: The discord.py library
+* ``commands``: The redbot.core.commands module
+* ``cf``: The redbot.core.utils.chat_formatting module
+* ``_``: The result from the last dev command
+
+**Arguments**
+
+* ``<body>``: The code to evaluate.
+
+.. _dev-command-mock:
+
+^^^^
+mock
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mock <user> <command>
+
+**Description**
+
+Mock another user invoking a command. The prefix must not be entered.
+
+**Arguments**
+
+* ``<user>``: The user to mock. |user-input-quotes|
+* ``<command>``: The command to invoke.
+
+.. _dev-command-mockmsg:
+
+^^^^^^^
+mockmsg
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mockmsg <user> <content>
+
+**Description**
+
+Dispatch a message event as if it were sent by a different user.
+
+Current message is used as a base (including attachments, embeds, etc.),
+the content and author of the message are replaced with the given arguments.
+
+**Arguments**
+
+* ``<user>``: The member to mock. |user-input-quotes|
+* ``<content>``: The content used for the message.
+
+.. note:: 
+
+        If ``content`` isn't passed, the message needs to contain embeds, attachments,
+        or anything else that makes the message non-empty.
+
+.. _dev-command-repl:
+
+^^^^
+repl
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]repl 
+
+**Description**
+
+Open an interactive REPL.
+
+The REPL will only recognise code as messages which start with a
+backtick. This includes codeblocks, and as such multiple lines can be
+evaluated.
+
+Use ``exit()`` or ``quit`` to exit the REPL session, prefixed with
+a backtick so they may be interpreted.
+
+**Environment Variables**
+
+* ``ctx``: Command invocation context
+* ``bot``: The bot object
+* ``channel``: The current channel object
+* ``author``: The current author's member object
+* ``guild``: The current guild object
+* ``message``: The command's message object
+* ``aiohttp``: The aiohttp library
+* ``asyncio``: The asyncio library
+* ``discord``: The discord.py library
+* ``commands``: The redbot.core.commands module
+* ``cf``: The redbot.core.utils.chat_formatting module
+* ``_``: The result from the last dev command
+
+.. _dev-command-repl-pause:
+
+""""""""""
+repl pause
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]repl pause [toggle]
+
+**Description**
+
+Pauses/resumes the REPL running in the current channel.
+
+**Arguments**
+
+* ``[toggle]``: |bool-input| Otherwise, defaults to the inverse of the current setting.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/downloader.rst

@@ -0,0 +1,538 @@
+.. _downloader:
+
+==========
+Downloader
+==========
+
+This is the cog guide for the downloader 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 downloader
+
+.. _downloader-usage:
+
+-----
+Usage
+-----
+
+Install community cogs made by Cog Creators.
+
+Community cogs, also called third party cogs, are not included
+in the default Red install.
+
+Community cogs come in repositories. Repos are a group of cogs
+you can install. You always need to add the creator's repository
+using the ``[p]repo`` command before you can install one or more
+cogs from the creator.
+
+
+.. _downloader-commands:
+
+--------
+Commands
+--------
+
+.. _downloader-command-cog:
+
+^^^
+cog
+^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog 
+
+**Description**
+
+Base command for cog installation management commands.
+
+.. _downloader-command-cog-checkforupdates:
+
+"""""""""""""""""""
+cog checkforupdates
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog checkforupdates 
+
+**Description**
+
+Check for available cog updates (including pinned cogs).
+
+This command doesn't update cogs, it only checks for updates.
+Use ``[p]cog update`` to update cogs.
+
+.. _downloader-command-cog-info:
+
+""""""""
+cog info
+""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog info <repo> <cog>
+
+**Description**
+
+List information about a single cog.
+
+Example:
+    - ``[p]cog info 26-Cogs defender``
+
+**Arguments**
+
+- ``<repo>`` The repo to get cog info from.
+- ``<cog>`` The cog to get info on.
+
+.. _downloader-command-cog-install:
+
+"""""""""""
+cog install
+"""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog install <repo> <cogs...>
+
+**Description**
+
+Install a cog from the given repo.
+
+Examples:
+    - ``[p]cog install 26-Cogs defender``
+    - ``[p]cog install Laggrons-Dumb-Cogs say roleinvite``
+
+**Arguments**
+
+- ``<repo>`` The name of the repo to install cogs from.
+- ``<cogs...>`` The cog or cogs to install.
+
+.. _downloader-command-cog-installversion:
+
+""""""""""""""""""
+cog installversion
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog installversion <repo> <revision> <cogs...>
+
+**Description**
+
+Install a cog from the specified revision of given repo.
+
+Revisions are "commit ids" that point to the point in the code when a specific change was made.
+The latest revision can be found in the URL bar for any GitHub repo by `pressing "y" on that repo <https://docs.github.com/en/free-pro-team@latest/github/managing-files-in-a-repository/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit>`_.
+
+Older revisions can be found in the URL bar by `viewing the commit history of any repo <https://cdn.discordapp.com/attachments/133251234164375552/775760247787749406/unknown.png>`_
+
+Example:
+    - ``[p]cog installversion Broken-Repo e798cc268e199612b1316a3d1f193da0770c7016 cog_name``
+
+**Arguments**
+
+- ``<repo>`` The name of the repo to install cogs from.
+- ``<revision>`` The revision to install from.
+- ``<cogs...>`` The cog or cogs to install.
+
+.. _downloader-command-cog-list:
+
+""""""""
+cog list
+""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog list <repo>
+
+**Description**
+
+List all available cogs from a single repo.
+
+Example:
+    - ``[p]cog list 26-Cogs``
+
+**Arguments**
+
+- ``<repo>`` The repo to list cogs from.
+
+.. _downloader-command-cog-listpinned:
+
+""""""""""""""
+cog listpinned
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog listpinned 
+
+**Description**
+
+List currently pinned cogs.
+
+.. _downloader-command-cog-pin:
+
+"""""""
+cog pin
+"""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog pin <cogs...>
+
+**Description**
+
+Pin cogs - this will lock cogs on their current version.
+
+Examples:
+    - ``[p]cog pin defender``
+    - ``[p]cog pin outdated_cog1 outdated_cog2``
+
+**Arguments**
+
+- ``<cogs...>`` The cog or cogs to pin. Must already be installed.
+
+.. _downloader-command-cog-uninstall:
+
+"""""""""""""
+cog uninstall
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog uninstall <cogs...>
+
+**Description**
+
+Uninstall cogs.
+
+You may only uninstall cogs which were previously installed
+by Downloader.
+
+Examples:
+    - ``[p]cog uninstall defender``
+    - ``[p]cog uninstall say roleinvite``
+
+**Arguments**
+
+- ``<cogs...>`` The cog or cogs to uninstall.
+
+.. _downloader-command-cog-unpin:
+
+"""""""""
+cog unpin
+"""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog unpin <cogs...>
+
+**Description**
+
+Unpin cogs - this will remove the update lock from those cogs.
+
+Examples:
+    - ``[p]cog unpin defender``
+    - ``[p]cog unpin updated_cog1 updated_cog2``
+
+**Arguments**
+
+- ``<cogs...>`` The cog or cogs to unpin. Must already be installed and pinned.
+
+.. _downloader-command-cog-update:
+
+""""""""""
+cog update
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog update [cogs...]
+
+**Description**
+
+Update all cogs, or ones of your choosing.
+
+Examples:
+    - ``[p]cog update``
+    - ``[p]cog update defender``
+
+**Arguments**
+
+- ``[cogs...]`` The cog or cogs to update. If omitted, all cogs are updated.
+
+.. _downloader-command-cog-updateallfromrepos:
+
+""""""""""""""""""""""
+cog updateallfromrepos
+""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog updateallfromrepos <repos...>
+
+**Description**
+
+Update all cogs from repos of your choosing.
+
+Examples:
+    - ``[p]cog updateallfromrepos 26-Cogs``
+    - ``[p]cog updateallfromrepos Laggrons-Dumb-Cogs 26-Cogs``
+
+**Arguments**
+
+- ``<repos...>`` The repo or repos to update all cogs from.
+
+.. _downloader-command-cog-updatetoversion:
+
+"""""""""""""""""""
+cog updatetoversion
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]cog updatetoversion <repo> <revision> [cogs...]
+
+**Description**
+
+Update all cogs, or ones of your choosing to chosen revision of one repo.
+
+Note that update doesn't mean downgrade and therefore ``revision``
+has to be newer than the version that cog currently has installed. If you want to
+downgrade the cog, uninstall and install it again.
+
+See ``[p]cog installversion`` for an explanation of ``revision``.
+
+Example:
+    - ``[p]cog updatetoversion Broken-Repo e798cc268e199612b1316a3d1f193da0770c7016 cog_name``
+
+**Arguments**
+
+- ``<repo>`` The repo or repos to update all cogs from.
+- ``<revision>`` The revision to update to.
+- ``[cogs...]`` The cog or cogs to update.
+
+.. _downloader-command-findcog:
+
+^^^^^^^
+findcog
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]findcog <command_name>
+
+**Description**
+
+Find which cog a command comes from.
+
+This will only work with loaded cogs.
+
+Example:
+    - ``[p]findcog ping``
+
+**Arguments**
+
+- ``<command_name>`` The command to search for.
+
+.. _downloader-command-pipinstall:
+
+^^^^^^^^^^
+pipinstall
+^^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]pipinstall <deps...>
+
+**Description**
+
+Install a group of dependencies using pip.
+
+Examples:
+    - ``[p]pipinstall bs4``
+    - ``[p]pipinstall py-cpuinfo psutil``
+
+Improper usage of this command can break your bot, be careful.
+
+**Arguments**
+
+- ``<deps...>`` The package or packages you wish to install.
+
+.. _downloader-command-repo:
+
+^^^^
+repo
+^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]repo 
+
+**Description**
+
+Base command for repository management.
+
+.. _downloader-command-repo-add:
+
+""""""""
+repo add
+""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]repo add <name> <repo_url> [branch]
+
+**Description**
+
+Add a new repo.
+
+Examples:
+    - ``[p]repo add 26-Cogs https://github.com/Twentysix26/x26-Cogs``
+    - ``[p]repo add Laggrons-Dumb-Cogs https://github.com/retke/Laggrons-Dumb-Cogs v3``
+
+Repo names can only contain characters A-z, numbers, underscores, and hyphens.
+The branch will be the default branch if not specified.
+
+**Arguments**
+
+- ``<name>`` The name given to the repo.
+- ``<repo_url>`` URL to the cog branch. Usually GitHub or GitLab.
+- ``[branch]`` Optional branch to install cogs from.
+
+.. _downloader-command-repo-delete:
+
+"""""""""""
+repo delete
+"""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]repo delete <repo>
+
+.. tip:: Aliases: ``repo remove``, ``repo del``
+
+**Description**
+
+Remove repos and their files.
+
+Examples:
+    - ``[p]repo delete 26-Cogs``
+    - ``[p]repo delete 26-Cogs Laggrons-Dumb-Cogs``
+
+**Arguments**
+
+- ``<repos...>`` The repo or repos to remove.
+
+.. _downloader-command-repo-info:
+
+"""""""""
+repo info
+"""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]repo info <repo>
+
+**Description**
+
+Show information about a repo.
+
+Example:
+    - ``[p]repo info 26-Cogs``
+
+**Arguments**
+
+- ``<repo>`` The name of the repo to show info about.
+
+.. _downloader-command-repo-list:
+
+"""""""""
+repo list
+"""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]repo list 
+
+**Description**
+
+List all installed repos.
+
+.. _downloader-command-repo-update:
+
+"""""""""""
+repo update
+"""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]repo update [repos...]
+
+**Description**
+
+Update all repos, or ones of your choosing.
+
+This will *not* update the cogs installed from those repos.
+
+Examples:
+    - ``[p]repo update``
+    - ``[p]repo update 26-Cogs``
+    - ``[p]repo update 26-Cogs Laggrons-Dumb-Cogs``
+
+**Arguments**
+
+- ``[repos...]`` The name or names of repos to update. If omitted, all repos are updated.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/economy.rst

@@ -0,0 +1,391 @@
+.. _economy:
+
+=======
+Economy
+=======
+
+This is the cog guide for the economy 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 economy
+
+.. _economy-usage:
+
+-----
+Usage
+-----
+
+Get rich and have fun with imaginary currency!
+
+
+.. _economy-commands:
+
+--------
+Commands
+--------
+
+.. _economy-command-bank:
+
+^^^^
+bank
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]bank 
+
+**Description**
+
+Base command to manage the bank.
+
+.. _economy-command-bank-balance:
+
+""""""""""""
+bank balance
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]bank balance [user]
+
+**Description**
+
+Show the user's account balance.
+
+Example:
+    - ``[p]bank balance``
+    - ``[p]bank balance @Twentysix``
+
+**Arguments**
+
+- ``<user>`` The user to check the balance of. If omitted, defaults to your own balance.
+
+.. _economy-command-bank-set:
+
+""""""""
+bank set
+""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]bank set <to> <creds>
+
+**Description**
+
+Set the balance of a user's bank account.
+
+Putting + or - signs before the amount will add/remove currency on the user's bank account instead.
+
+Examples:
+    - ``[p]bank set @Twentysix 26`` - Sets balance to 26
+    - ``[p]bank set @Twentysix +2`` - Increases balance by 2
+    - ``[p]bank set @Twentysix -6`` - Decreases balance by 6
+
+**Arguments**
+
+- ``<to>`` The user to set the currency of.
+- ``<creds>`` The amount of currency to set their balance to.
+
+.. _economy-command-bank-transfer:
+
+"""""""""""""
+bank transfer
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]bank transfer <to> <amount>
+
+**Description**
+
+Transfer currency to other users.
+
+This will come out of your balance, so make sure you have enough.
+
+Example:
+    - ``[p]bank transfer @Twentysix 500``
+
+**Arguments**
+
+- ``<to>`` The user to give currency to.
+- ``<amount>`` The amount of currency to give.
+
+.. _economy-command-economyset:
+
+^^^^^^^^^^
+economyset
+^^^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]economyset 
+
+**Description**
+
+Base command to manage Economy settings.
+
+.. _economy-command-economyset-paydayamount:
+
+"""""""""""""""""""""""
+economyset paydayamount
+"""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]economyset paydayamount <creds>
+
+**Description**
+
+Set the amount earned each payday.
+
+Example:
+    - ``[p]economyset paydayamount 400``
+
+**Arguments**
+
+- ``<creds>`` The new amount to give when using the payday command. Default is 120.
+
+.. _economy-command-economyset-paydaytime:
+
+"""""""""""""""""""""
+economyset paydaytime
+"""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]economyset paydaytime <duration>
+
+**Description**
+
+Set the cooldown for the payday command.
+
+Examples:
+    - ``[p]economyset paydaytime 86400``
+    - ``[p]economyset paydaytime 1d``
+
+**Arguments**
+
+- | ``<duration>`` The new duration to wait in between uses of payday. Default is 5 minutes.
+  | Accepts: seconds, minutes, hours, days, weeks (if no unit is specified, the duration is assumed to be given in seconds)
+
+.. _economy-command-economyset-rolepaydayamount:
+
+"""""""""""""""""""""""""""
+economyset rolepaydayamount
+"""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]economyset rolepaydayamount <role> <creds>
+
+**Description**
+
+Set the amount earned each payday for a role.
+
+Set to 0 will remove the custom payday for that role instead.
+
+Only available when not using a global bank.
+
+Example:
+    - ``[p]economyset rolepaydayamount @Members 400``
+
+**Arguments**
+
+- ``<role>`` The role to assign a custom payday amount to.
+- ``<creds>`` The new amount to give when using the payday command.
+
+.. _economy-command-economyset-showsettings:
+
+"""""""""""""""""""""""
+economyset showsettings
+"""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]economyset showsettings 
+
+**Description**
+
+Shows the current economy settings
+
+.. _economy-command-economyset-slotmax:
+
+""""""""""""""""""
+economyset slotmax
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]economyset slotmax <bid>
+
+**Description**
+
+Set the maximum slot machine bid.
+
+Example:
+    - ``[p]economyset slotmax 50``
+
+**Arguments**
+
+- ``<bid>`` The new maximum bid for using the slot machine. Default is 100.
+
+.. _economy-command-economyset-slotmin:
+
+""""""""""""""""""
+economyset slotmin
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]economyset slotmin <bid>
+
+**Description**
+
+Set the minimum slot machine bid.
+
+Example:
+    - ``[p]economyset slotmin 10``
+
+**Arguments**
+
+- ``<bid>`` The new minimum bid for using the slot machine. Default is 5.
+
+.. _economy-command-economyset-slottime:
+
+"""""""""""""""""""
+economyset slottime
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]economyset slottime <duration>
+
+**Description**
+
+Set the cooldown for the slot machine.
+
+Examples:
+    - ``[p]economyset slottime 10``
+    - ``[p]economyset slottime 10m``
+
+**Arguments**
+
+- | ``<duration>`` The new duration to wait in between uses of the slot machine. Default is 5 seconds.
+  | Accepts: seconds, minutes, hours, days, weeks (if no unit is specified, the duration is assumed to be given in seconds)
+
+.. _economy-command-leaderboard:
+
+^^^^^^^^^^^
+leaderboard
+^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]leaderboard [top=10] [show_global=False]
+
+**Description**
+
+Print the leaderboard.
+
+Defaults to top 10.
+
+Examples:
+    - ``[p]leaderboard``
+    - ``[p]leaderboard 50`` - Shows the top 50 instead of top 10.
+    - ``[p]leaderboard 100 yes`` - Shows the top 100 from all servers.
+
+**Arguments**
+
+- ``<top>`` How many positions on the leaderboard to show. Defaults to 10 if omitted.
+- ``<show_global>`` Whether to include results from all servers. This will default to false unless specified.
+
+.. _economy-command-payday:
+
+^^^^^^
+payday
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]payday 
+
+**Description**
+
+Get some free currency.
+
+The amount awarded and frequency can be configured.
+
+.. _economy-command-payouts:
+
+^^^^^^^
+payouts
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]payouts 
+
+**Description**
+
+Show the payouts for the slot machine.
+
+.. _economy-command-slot:
+
+^^^^
+slot
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]slot <bid>
+
+**Description**
+
+Use the slot machine.
+
+Example:
+    - ``[p]slot 50``
+
+**Arguments**
+
+- ``<bid>`` The amount to bet on the slot machine. Winning payouts are higher when you bet more.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/filter.rst

@@ -0,0 +1,335 @@
+.. _filter:
+
+======
+Filter
+======
+
+This is the cog guide for the filter 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 filter
+
+.. _filter-usage:
+
+-----
+Usage
+-----
+
+This cog is designed for "filtering" unwanted words and phrases from a server.
+
+It provides tools to manage a list of words or sentences, and to customize automatic actions to be taken against users who use those words in channels or in their name/nickname.
+
+This can be used to prevent inappropriate language, off-topic discussions, invite links, and more.
+
+
+.. _filter-commands:
+
+--------
+Commands
+--------
+
+.. _filter-command-filter:
+
+^^^^^^
+filter
+^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter 
+
+**Description**
+
+Base command to add or remove words from the server filter.
+
+Use double quotes to add or remove sentences.
+
+.. _filter-command-filter-add:
+
+""""""""""
+filter add
+""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter add [words...]
+
+**Description**
+
+Add words to the filter.
+
+Use double quotes to add sentences.
+
+Examples:
+    - ``[p]filter add word1 word2 word3``
+    - ``[p]filter add "This is a sentence"``
+
+**Arguments:**
+
+- ``[words...]`` The words or sentences to filter.
+
+.. _filter-command-filter-channel:
+
+""""""""""""""
+filter channel
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter channel 
+
+**Description**
+
+Base command to add or remove words from the channel filter.
+
+Use double quotes to add or remove sentences.
+
+.. _filter-command-filter-channel-add:
+
+""""""""""""""""""
+filter channel add
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter channel add [words...]
+
+**Description**
+
+Add words to the filter.
+
+Use double quotes to add sentences.
+
+Examples:
+    - ``[p]filter channel add word1 word2 word3``
+    - ``[p]filter channel add "This is a sentence"``
+
+**Arguments:**
+
+- ``[words...]`` The words or sentences to filter.
+
+.. _filter-command-filter-channel-clear:
+
+""""""""""""""""""""
+filter channel clear
+""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter channel clear
+
+**Description**
+
+Clears this channel's filter list.
+
+.. _filter-command-filter-channel-list:
+
+"""""""""""""""""""
+filter channel list
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter channel list 
+
+**Description**
+
+Send a list of the channel's filtered words.
+
+.. _filter-command-filter-channel-remove:
+
+"""""""""""""""""""""
+filter channel remove
+"""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter channel remove [words...]
+
+**Description**
+
+Remove words from the filter.
+
+Use double quotes to remove sentences.
+
+Examples:
+    - ``[p]filter channel remove word1 word2 word3``
+    - ``[p]filter channel remove "This is a sentence"``
+
+**Arguments:**
+
+- ``[words...]`` The words or sentences to no longer filter.
+
+.. _filter-command-filter-clear:
+
+""""""""""""
+filter clear
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter clear
+
+**Description**
+
+Clears this server's filter list.
+
+.. _filter-command-filter-delete:
+
+"""""""""""""
+filter delete
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter delete [words...]
+
+.. tip:: Aliases: ``filter remove``, ``filter del``
+
+**Description**
+
+Remove words from the filter.
+
+Use double quotes to remove sentences.
+
+Examples:
+    - ``[p]filter remove word1 word2 word3``
+    - ``[p]filter remove "This is a sentence"``
+
+**Arguments:**
+
+- ``[words...]`` The words or sentences to no longer filter.
+
+.. _filter-command-filter-list:
+
+"""""""""""
+filter list
+"""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter list 
+
+**Description**
+
+Send a list of this server's filtered words.
+
+.. _filter-command-filter-names:
+
+""""""""""""
+filter names
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filter names 
+
+**Description**
+
+Toggle name and nickname filtering.
+
+This is disabled by default.
+
+.. _filter-command-filterset:
+
+^^^^^^^^^
+filterset
+^^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filterset 
+
+**Description**
+
+Base command to manage filter settings.
+
+.. _filter-command-filterset-ban:
+
+"""""""""""""
+filterset ban
+"""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filterset ban <count> <timeframe>
+
+**Description**
+
+Set the filter's autoban conditions.
+
+Users will be banned if they send ``<count>`` filtered words in
+``<timeframe>`` seconds.
+
+Set both to zero to disable autoban.
+
+Examples:
+    - ``[p]filterset ban 5 5`` - Ban users who say 5 filtered words in 5 seconds.
+    - ``[p]filterset ban 2 20`` - Ban users who say 2 filtered words in 20 seconds.
+
+**Arguments:**
+
+- ``<count>`` The amount of filtered words required to trigger a ban.
+- ``<timeframe>`` The period of time in which too many filtered words will trigger a ban.
+
+.. _filter-command-filterset-defaultname:
+
+"""""""""""""""""""""
+filterset defaultname
+"""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]filterset defaultname <name>
+
+**Description**
+
+Set the nickname for users with a filtered name.
+
+Note that this has no effect if filtering names is disabled
+(to toggle, run ``[p]filter names``).
+
+The default name used is *John Doe*.
+
+Example:
+    - ``[p]filterset defaultname Missingno``
+
+**Arguments:**
+
+- ``<name>`` The new nickname to assign.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/general.rst

@@ -0,0 +1,218 @@
+.. _general:
+
+=======
+General
+=======
+
+This is the cog guide for the general 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 general
+
+.. _general-usage:
+
+-----
+Usage
+-----
+
+This cog includes a miscellaneous group of games, useful
+tools, and informative commands such as ``serverinfo`` or ``urban``.
+
+.. _general-commands:
+
+--------
+Commands
+--------
+
+Here's a list of all commands available for this cog.
+
+.. _general-command-8:
+
+^^^^^^^^^
+8 (8ball)
+^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]8 <question>
+
+**Description**
+
+Ask 8 ball a question. 
+
+.. note:: Your question must end with a question mark.
+
+**Arguments**
+
+* ``<question>``: The question you would like to ask 8 ball.
+
+.. _general-command-choose:
+
+^^^^^^
+choose
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]choose <first> <second> [others...]
+
+**Description**
+
+Choose between multiple options.
+Options are separated by spaces.
+
+.. note::  There must be at least 2 options to pick from.
+.. note::  To denote options which include whitespace, you should enclose the option in double quotes.
+
+**Arguments**
+
+* ``<first>``: The first mandatory option.
+* ``<second>``: The second mandatory option.
+* ``[others...]``: Any remaining optional options.
+
+
+.. _general-command-flip:
+
+^^^^
+flip
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]flip [user]
+
+**Description**
+
+Flip a coin... or a user.
+
+**Arguments**
+
+* ``[user]``: The user to flip. Defaults to flipping a coin if no user is provided.
+
+.. _general-command-lmgtfy:
+
+^^^^^^
+lmgtfy
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]lmgtfy <search_terms>
+
+**Description**
+
+Create a lmgtfy link.
+
+**Arguments**
+
+* ``<search_terms>``: The terms used to generate the lmgtfy link.
+
+.. _general-command-roll:
+
+^^^^
+roll
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]roll [number=100]
+
+**Description**
+
+Roll a random number. The result will be between 1 and ``<number>``.
+
+**Arguments**
+
+* ``[number]``: The maximum number that can be rolled. Defaults to 100.
+
+.. _general-command-rps:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^
+rps (Rock Paper Scissors)
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]rps <your_choice>
+
+**Description**
+
+Play Rock Paper Scissors.
+
+**Arguments**
+
+* ``<your_choice>``: The choice that you choose.
+
+.. note:: Choices **must** be between ``rock``, ``paper``, or ``scissors``.
+
+.. _general-commands-serverinfo:
+
+^^^^^^^^^^
+serverinfo
+^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]serverinfo [details=False]
+
+**Description**
+
+Show server information.
+
+**Arguments**
+
+* ``[details]``: Show extra details about the server when set to True. Defaults to False.
+
+.. _general-commands-stopwatch:
+
+^^^^^^^^^
+stopwatch
+^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]stopwatch
+
+**Description**
+
+Start or stop the stopwatch.
+
+.. _general-commands-urban:
+
+^^^^^
+urban
+^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]urban <word>
+
+**Description**
+
+Search the Urban Dictionary.
+
+**Arguments**
+
+* ``<word>``: The term to search for.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/image.rst

@@ -0,0 +1,205 @@
+.. _image:
+
+=====
+Image
+=====
+
+This is the cog guide for the image 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 image
+
+.. _image-usage:
+
+-----
+Usage
+-----
+
+This cog provides commands for retrieving pictures from
+websites such as Giphy and Imgur.
+
+.. _image-commands:
+
+--------
+Commands
+--------
+
+Here's a list of all commands available for this cog.
+
+.. _image-command-gif:
+
+^^^
+gif
+^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]gif <keywords...>
+
+**Description**
+
+Retrieve the first search result from Giphy. This command requires API tokens
+to be set via the :ref:`giphycreds <image-command-giphycreds>` command.
+
+**Arguments**
+
+* ``<keywords...>``: The keywords used to search Giphy.
+
+.. _image-command-gifr:
+
+^^^^
+gifr
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]gifr <keywords...>
+
+**Description**
+
+Retrieve a random GIF from a Giphy search. This command requires API tokens
+to be set via the :ref:`giphycreds <image-command-giphycreds>` command.
+
+**Arguments**
+
+* ``<keywords...>``: The keywords used to generate a random GIF.
+
+.. _image-command-imgur:
+
+^^^^^
+imgur
+^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]imgur
+
+**Description**
+
+Retrieves pictures from Imgur. This command requires API tokens to be set
+via the :ref:`imgurcreds <image-command-imgurcreds>` command.
+
+.. _image-command-imgur-search:
+
+""""""""""""
+imgur search
+""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]imgur search [count=1] <terms...>
+
+**Description**
+
+Search for pictures on Imgur. This command requires API tokens to be set
+via the :ref:`imgurcreds <image-command-imgurcreds>` command.
+
+**Arguments**
+
+* ``[count]``: How many images should be returned (maximum 5). Defaults to 1.
+
+* ``<terms...>``: The terms used to search Imgur.
+
+.. _image-command-imgur-subreddit:
+
+"""""""""""""""
+imgur subreddit
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]imgur subreddit <subreddit> [count=1] [sort_type=top] [window=day]
+
+**Description**
+
+Get images from a subreddit. This command requires API tokens to be set
+via the :ref:`imgurcreds <image-command-imgurcreds>` command.
+
+**Arguments**
+
+* ``<subreddit>``: The subreddit to get images from.
+
+* ``[count]``: The number of images to return (maximum 5). Defaults to 1.
+
+* ``[sort_type]``: New, or top results. Defaults to top.
+
+* ``[window]``: The timeframe, can be the past day, week, month, year or all. Defaults to day.
+
+.. _image-command-giphycreds:
+
+^^^^^^^^^^
+giphycreds
+^^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]giphycreds
+
+**Description**
+
+Explains how to set GIPHY API tokens.
+
+**Getting your API key**
+
+1. Login (or create) a GIPHY account.
+2. Visit `this page <https://developers.giphy.com/dashboard>`__.
+3. Press 'Create an App'.
+4. Click 'Select API', and then 'Next Step'.
+5. Add an app name, for example 'Red'.
+6. Add an app description, for example 'Used for Red's image cog'.
+7. Click 'Create App'. You'll need to agree to the GIPHY API terms.
+8. Copy the API Key.
+9. In Discord, run the following command::
+
+        [p]set api GIPHY api_key <your_api_key_here>
+
+.. _image-command-imgurcreds:
+
+^^^^^^^^^^
+imgurcreds
+^^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]imgurcreds
+
+**Description**
+
+Explains how to set Imgur API tokens.
+
+**Getting your API key**
+
+1. Login to (or create) an Imgur account.
+2. Visit `this page <https://api.imgur.com/oauth2/addclient>`__.
+3. Add an app name for your application, for example 'Red'.
+4. Select 'Anonymous usage without user authorization' for the auth type.
+5. Set the authorization callback URL to ``https://localhost``
+6. Leave the app website blank.
+7. Enter a valid email address and a description.
+8. Check the captcha box and click next.
+9. Your Client ID will be on the next page.
+10. In Discord, run the following command::
+
+        [p]set api imgur client_id <your_client_id_here>

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/mod.rst

@@ -0,0 +1,763 @@
+.. _mod:
+
+===
+Mod
+===
+
+This is the cog guide for the mod 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 mod
+
+.. _mod-usage:
+
+-----
+Usage
+-----
+
+A range of highly customizable moderation tools used to protect your 
+guild from users who cannot follow the rules.
+
+
+.. _mod-commands:
+
+--------
+Commands
+--------
+
+.. _mod-command-ban:
+
+^^^
+ban
+^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]ban <user> [days] [reason]
+
+**Description**
+
+Ban a user from this server and optionally delete days of messages.
+
+``days`` is the amount of days of messages to cleanup on ban.
+
+**Arguments**
+
+* ``<user>``: The user to ban. |user-input|
+* ``[days]``: The amount of days of messages to cleanup on ban. This parameter defaults to the defaultdays setting, or no days if this has not yet been configured.
+* ``[reason]``: The reason why the user was banned (optional).
+
+**Example Usage**
+
+* ``[p]ban 428675506947227648 7 Continued to spam after told to stop.``
+    This will ban the user with ID 428675506947227648 and it will delete 7 days worth of messages.
+* ``[p]ban @Twentysix 7 Continued to spam after told to stop.``
+    This will ban Twentysix and it will delete 7 days worth of messages.
+
+A user ID should be provided if the user is not a member of this server.
+If days is not a number, it's treated as the first word of the reason.
+Minimum 0 days, maximum 7. If not specified, the defaultdays setting will be used instead.
+
+.. _mod-command-kick:
+
+^^^^
+kick
+^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]kick <member> [reason]
+
+**Description**
+
+Kick a user.
+
+**Arguments**
+
+* ``<member>``: The member to kick. |member-input|
+* ``[reason]``: The reason why the user was kicked (optional).
+
+**Example Usage**
+
+* ``[p]kick 428675506947227648 wanted to be kicked.``
+    This will kick the user with ID 428675506947227648 from the server.
+* ``[p]kick @Twentysix wanted to be kicked.``
+    This will kick Twentysix from the server.
+
+If a reason is specified, it will be the reason that shows up
+in the audit log.
+
+.. _mod-command-massban:
+
+^^^^^^^
+massban
+^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]massban <user_ids...> [days] [reason]
+
+.. tip:: Alias: ``hackban``
+
+**Description**
+
+Mass bans user(s) from the server.
+
+**Arguments**
+
+* ``<user_ids...>``: The users to ban. This must be a list of user IDs separated by spaces.
+* ``[days]``: The amount of days of messages to cleanup on massban.
+* ``[reason]``: The reason why these users were banned.
+
+**Example Usage**
+
+* ``[p]massban 345628097929936898 57287406247743488 7 they broke all rules.``
+    This will ban all the added userids and delete 7 days worth of their messages.
+
+.. _mod-command-modset:
+
+^^^^^^
+modset
+^^^^^^
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset 
+
+**Description**
+
+Manage server administration settings.
+
+.. _mod-command-modset-defaultdays:
+
+""""""""""""""""""
+modset defaultdays
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset defaultdays [days=0]
+
+**Description**
+
+Set the default number of days worth of messages to be deleted when a user is banned.
+
+The number of days must be between 0 and 7.
+
+**Arguments**
+
+* ``[days=0]``: The default number of days of messages to be deleted when a user is banned.
+
+.. note:: This value must be between 0 and 7.
+
+.. _mod-command-modset-defaultduration:
+
+""""""""""""""""""""""
+modset defaultduration
+""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset defaultduration <duration>
+
+**Description**
+
+Set the default time to be used when a user is tempbanned.
+
+Accepts: seconds, minutes, hours, days, weeks
+
+**Arguments**
+
+* ``<duration>``: The default duration for when a user is temporarily banned. Accepts seconds, minutes, hours, days or weeks.
+
+**Example Usage**
+
+* ``[p]modset defaultduration 7d12h10m``
+* ``[p]modset defaultduration 7 days 12 hours 10 minutes``
+
+.. _mod-command-modset-deletenames:
+
+""""""""""""""""""
+modset deletenames
+""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset deletenames [confirmation=False]
+
+**Description**
+
+Delete all stored usernames and nicknames.
+
+**Arguments**
+
+- ``<confirmation>``: Whether to delete all stored usernames and nicknames. |bool-input|
+
+.. _mod-command-modset-deleterepeats:
+
+""""""""""""""""""""
+modset deleterepeats
+""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset deleterepeats [repeats]
+
+**Description**
+
+Enable auto-deletion of repeated messages.
+
+**Arguments**
+
+* ``[repeats]``: The number of repeated messages needed before further messages are deleted.
+
+.. note:: Must be between 2 and 20. Set to -1 to disable this feature.
+
+.. _mod-command-modset-dm:
+
+"""""""""
+modset dm
+"""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset dm [enabled]
+
+**Description**
+
+Toggle whether a message should be sent to a user when they are kicked/banned.
+
+If this option is enabled, the bot will attempt to DM the user with the guild name
+and reason as to why they were kicked/banned.
+
+**Arguments**
+
+* ``[enabled]``: Whether a message should be sent to a user when they are kicked/banned. |bool-input|
+
+.. _mod-command-modset-hierarchy:
+
+""""""""""""""""
+modset hierarchy
+""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset hierarchy 
+
+**Description**
+
+Toggle role hierarchy check for mods and admins.
+
+.. warning:: Disabling this setting will allow mods to take actions on users above them in the role hierarchy!
+
+This is enabled by default.
+
+.. _mod-command-modset-mentionspam:
+
+""""""""""""""""""
+modset mentionspam
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset mentionspam 
+
+**Description**
+
+Manage the automoderation settings for mentionspam.
+
+.. _mod-command-modset-mentionspam-ban:
+
+""""""""""""""""""""""
+modset mentionspam ban
+""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset mentionspam ban <max_mentions>
+
+**Description**
+
+Set the autoban conditions for mention spam.
+
+Users will be banned if they send any message which contains more than
+``<max_mentions>`` mentions.
+
+**Arguments**
+
+* ``<max_mentions>``: Must be 0 or greater. Set to 0 to disable this feature.
+
+.. _mod-command-modset-mentionspam-kick:
+
+"""""""""""""""""""""""
+modset mentionspam kick
+"""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset mentionspam kick <max_mentions>
+
+**Description**
+
+Set the autokick conditions for mention spam.
+
+Users will be kicked if they send any message which contains more than
+``<max_mentions>`` mentions.
+
+**Arguments**
+
+* ``<max_mentions>``: Must be 0 or greater. Set to 0 to disable this feature.
+
+.. _mod-command-modset-mentionspam-strict:
+
+"""""""""""""""""""""""""
+modset mentionspam strict
+"""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset mentionspam strict [enabled]
+
+**Description**
+
+Setting to account for duplicate mentions.
+
+If enabled all mentions will count including duplicated mentions.
+If disabled only unique mentions will count.
+
+Use this command without any parameter to see the current setting.
+
+**Arguments**
+
+* ``[enabled]``: Whether all mentions will count, including duplicated mentions. |bool-input|
+
+.. _mod-command-modset-mentionspam-warn:
+
+"""""""""""""""""""""""
+modset mentionspam warn
+"""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset mentionspam warn <max_mentions>
+
+**Description**
+
+Sets the autowarn conditions for mention spam.
+
+Users will be warned if they send any messages which contain more than
+``<max_mentions>`` mentions.
+
+**Arguments**
+
+* ``<max_mentions>``: Must be 0 or greater. Set to 0 to disable this feature.
+
+.. _mod-command-modset-reinvite:
+
+"""""""""""""""
+modset reinvite
+"""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset reinvite 
+
+**Description**
+
+Toggle whether an invite will be sent to a user when unbanned.
+
+If this is True, the bot will attempt to create and send a single-use invite
+to the newly-unbanned user.
+
+.. _mod-command-modset-showsettings:
+
+"""""""""""""""""""
+modset showsettings
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset showsettings 
+
+**Description**
+
+Show the current server administration settings.
+
+.. _mod-command-modset-trackallnames:
+
+""""""""""""""""""""
+modset trackallnames
+""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset trackallnames [enabled]
+
+**Description**
+
+Toggle whether all name changes should be tracked.
+
+Toggling this off also overrides the tracknicknames setting.
+
+**Arguments**
+
+* ``[enabled]``: Whether all name changes should be tracked. |bool-input|
+
+.. _mod-command-modset-tracknicknames:
+
+"""""""""""""""""""""
+modset tracknicknames
+"""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]modset tracknicknames [enabled]
+
+**Description**
+
+Toggle whether nickname changes should be tracked.
+
+This setting will be overridden if trackallnames is disabled.
+
+**Arguments**
+
+* ``[enabled]``: Whether all nickname changes should be tracked. |bool-input|
+
+.. _mod-command-movedeletedelay:
+
+^^^^^^^^^^^^^^^
+movedeletedelay
+^^^^^^^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]movedeletedelay 
+
+**Description**
+
+Move deletedelay settings to core
+
+.. _mod-command-moveignoredchannels:
+
+^^^^^^^^^^^^^^^^^^^
+moveignoredchannels
+^^^^^^^^^^^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]moveignoredchannels 
+
+**Description**
+
+Move ignored channels and servers to core
+
+.. _mod-command-names:
+
+^^^^^
+names
+^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]names <member>
+
+**Description**
+
+Show previous names and nicknames of a member.
+
+**Arguments**
+
+* ``<member>``: |member-input|
+
+.. _mod-command-rename:
+
+^^^^^^
+rename
+^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]rename <member> [nickname]
+
+**Description**
+
+Change a member's nickname.
+
+Leaving the nickname empty will remove it.
+
+**Arguments**
+
+* ``<member>``: |member-input|
+* ``[nickname]``: The new nickname for the member.
+
+.. _mod-command-slowmode:
+
+^^^^^^^^
+slowmode
+^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]slowmode [interval=0:00:00]
+
+**Description**
+
+Changes thread's or channel's slowmode setting.
+
+Interval can be anything from 0 seconds to 6 hours.
+Use without parameters to disable.
+
+**Arguments**
+
+* ``[interval=0:00:00]``: The time for the thread's/channel's slowmode settings.
+
+.. note::
+    Interval can be anything from 0 seconds to 6 hours.
+    Use without parameters to disable.
+
+.. _mod-command-softban:
+
+^^^^^^^
+softban
+^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]softban <member> [reason]
+
+**Description**
+
+Kick a member and delete 1 day's worth of their messages.
+
+**Arguments**
+
+* ``<member>``: The member to softban. |member-input-quotes|
+* ``[reason]``: Reason for the kick (optional).
+
+.. _mod-command-tempban:
+
+^^^^^^^
+tempban
+^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]tempban <member> [duration] [days] [reason]
+
+**Description**
+
+Temporarily ban a user from this server.
+
+**Arguments**
+
+* ``<member>``: The member to temporarily ban. |member-input-quotes|
+* ``[duration]``: The amount of time the user should be banned for.
+* ``[days]``: The amount of days of messages to cleanup on tempban.
+* ``[reason]``: The reason for the tempban (optional).
+
+**Example Usage**
+
+* ``[p]tempban @Twentysix Because I say so``
+    This will ban Twentysix for the default amount of time set by an administrator.
+* ``[p]tempban @Twentysix 15m You need a timeout``
+    This will ban Twentysix for 15 minutes.
+* ``[p]tempban 428675506947227648 1d2h15m 5 Evil person``
+    This will ban the user with ID 428675506947227648 for 1 day 2 hours 15 minutes and will delete the last 5 days of their messages.
+
+.. _mod-command-unban:
+
+^^^^^
+unban
+^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]unban <user_id> [reason]
+
+**Description**
+
+Unban a user from this server.
+
+**Arguments**
+
+* ``<user_id>``: |user-input|
+* ``[reason]``: The reason for the unban (optional).
+
+.. _mod-command-userinfo:
+
+^^^^^^^^
+userinfo
+^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]userinfo [member]
+
+**Description**
+
+Show information about a user.
+
+This includes fields for status, discord join date, server
+join date, voice state and previous names/nicknames.
+
+If the user has no roles, previous names or previous nicknames,
+these fields will be omitted.
+
+**Arguments**
+
+* ``[member]``: |member-input|
+
+.. _mod-command-voiceban:
+
+^^^^^^^^
+voiceban
+^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]voiceban <member> [reason]
+
+**Description**
+
+Ban a user from speaking and listening in the server's voice channels.
+
+**Arguments**
+
+* ``<member>``: The member to ban from voice. |member-input|
+* ``[reason]``: The reason for the voiceban (optional).
+
+.. _mod-command-voicekick:
+
+^^^^^^^^^
+voicekick
+^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]voicekick <member> [reason]
+
+**Description**
+
+Kick a member from a voice channel.
+
+**Arguments**
+
+* ``<member>``: |member-input|
+* ``[reason]``: The reason for the voicekick (optional).
+
+.. _mod-command-voiceunban:
+
+^^^^^^^^^^
+voiceunban
+^^^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]voiceunban <member> [reason]
+
+**Description**
+
+Unban a user from speaking and listening in the server's voice channels.
+
+**Arguments**
+
+* ``<member>``: The member to unban from voice. |member-input-quotes|
+* ``[reason]``: The reason for the voiceunban (optional).

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/modlog.rst

@@ -0,0 +1,115 @@
+.. _modlog:
+
+======
+ModLog
+======
+
+This is the cog guide for the modlog 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 modlog
+
+.. _modlog-usage:
+
+-----
+Usage
+-----
+
+Browse and manage modlog cases.
+
+
+.. _modlog-commands:
+
+--------
+Commands
+--------
+
+.. _modlog-command-case:
+
+^^^^
+case
+^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]case <number>
+
+**Description**
+
+Show the specified case.
+
+**Arguments**
+
+* ``<case>``: The case number to get information for.
+
+.. _modlog-command-casesfor:
+
+^^^^^^^^
+casesfor
+^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]casesfor <member>
+
+**Description**
+
+Display cases for the specified member.
+
+**Arguments**
+
+* ``<member>``: The member to get cases for. |member-input|
+
+.. _modlog-command-listcases:
+
+^^^^^^^^^
+listcases
+^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]listcases <member>
+
+**Description**
+
+List cases for the specified member.
+
+**Arguments**
+
+* ``<member>``: The member to get cases for. |member-input|
+
+.. _modlog-command-reason:
+
+^^^^^^
+reason
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]reason [case] <reason>
+
+**Description**
+
+Specify a reason for a modlog case.
+
+Please note that you can only edit cases you are
+the owner of unless you are a mod, admin or server owner.
+
+**Arguments**
+
+* ``[case]``: The case number to update the reason for.
+* ``<reason>``: The new reason for the specified case.
+
+.. note:: If no case number is specified, the latest case will be used.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/mutes.rst

@@ -0,0 +1,410 @@
+.. _mutes:
+
+=====
+Mutes
+=====
+
+This is the cog guide for the mutes 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 mutes
+
+.. _mutes-usage:
+
+-----
+Usage
+-----
+
+Mute users temporarily or indefinitely.
+
+.. _mutes-commands:
+
+--------
+Commands
+--------
+
+.. _mutes-command-activemutes:
+
+^^^^^^^^^^^
+activemutes
+^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]activemutes 
+
+**Description**
+
+Displays active mutes on this server.
+
+.. _mutes-command-mute:
+
+^^^^
+mute
+^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mute <users...> [time_and_reason]
+
+**Description**
+
+Mute users.
+
+Examples:
+
+* ``[p]mute @member1 @member2 spam 5 hours``
+* ``[p]mute @member1 3 days``
+
+**Arguments**
+
+* ``<users...>``: A space separated list of usernames, ID's, or mentions.
+* ``[time_and_reason]``: The time and reason. If no time is provided, the mute will use the default set time or indefinite if this hasn't been configured.
+
+.. _mutes-command-mutechannel:
+
+^^^^^^^^^^^
+mutechannel
+^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mutechannel <users...> [time_and_reason]
+
+.. tip:: Alias: ``channelmute``
+
+**Description**
+
+Mute a user in the current text channel (or in the parent of the current thread).
+
+Examples:
+
+* ``[p]mutechannel @member1 @member2 spam 5 hours``
+* ``[p]mutechannel @member1 3 days``
+
+**Arguments**
+
+* ``<users...>``: A space separated list of usernames, ID's, or mentions.
+* ``[time_and_reason]``: The time and reason. If no time is provided, the mute will use the default set time or indefinite if this hasn't been configured.
+
+.. _mutes-command-muteset:
+
+^^^^^^^
+muteset
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]muteset 
+
+**Description**
+
+Mute settings.
+
+.. _mutes-command-muteset-defaulttime:
+
+"""""""""""""""""""
+muteset defaulttime
+"""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]muteset defaulttime [time]
+
+.. tip:: Alias: ``muteset time``
+
+**Description**
+
+Set the default mute time for the mute command.
+
+If no time interval is provided this will be cleared.
+
+**Arguments**
+
+* ``[time]``: The length of time for a default mute.
+
+.. _mutes-command-muteset-forcerole:
+
+"""""""""""""""""
+muteset forcerole
+"""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]muteset forcerole <true_or_false>
+
+**Description**
+
+Whether or not to force role only mutes on the bot.
+
+**Arguments**
+
+* ``<true_or_false>``: Whether to enable or disable this setting, must provide ``true`` or ``false``.
+
+.. _mutes-command-muteset-makerole:
+
+""""""""""""""""
+muteset makerole
+""""""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]muteset makerole <name>
+
+**Description**
+
+Create a Muted role.
+
+This will create a role and apply overwrites to all available channels
+to more easily setup muting a user.
+
+If you already have a muted role created on the server use
+``[p]muteset role ROLE_NAME_HERE``
+
+**Arguments**
+
+* ``<name>``: The name of the muted role to create.
+
+.. _mutes-command-muteset-notification:
+
+""""""""""""""""""""
+muteset notification
+""""""""""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]muteset notification [channel]
+
+**Description**
+
+Set the notification channel for automatic unmute issues.
+
+If no channel is provided this will be cleared and notifications
+about issues when unmuting users will not be sent anywhere.
+
+**Arguments**
+
+* ``[channel]``: The channel to receive unmute issue updates. |channel-input|
+
+.. _mutes-command-muteset-role:
+
+""""""""""""
+muteset role
+""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]muteset role [role]
+
+**Description**
+
+Sets the role to be applied when muting a user.
+
+If no role is setup the bot will attempt to mute a user by setting
+channel overwrites in all channels to prevent the user from sending messages.
+
+.. Note:: 
+    
+    If no role is setup a user may be able to leave the server
+    and rejoin no longer being muted.
+
+**Arguments**
+
+* ``[role]``: The role for muted users to receive. |role-input|
+
+.. _mutes-command-muteset-senddm:
+
+""""""""""""""
+muteset senddm
+""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]muteset senddm <true_or_false>
+
+**Description**
+
+Set whether mute notifications should be sent to users in DMs.
+
+**Arguments**
+
+* ``<true_or_false>``: Whether to enable or disable this setting, must provide ``true`` or ``false``.
+
+.. _mutes-command-muteset-settings:
+
+""""""""""""""""
+muteset settings
+""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]muteset settings 
+
+.. tip:: Alias: ``muteset showsettings``
+
+**Description**
+
+Shows the current mute settings for this guild.
+
+.. _mutes-command-muteset-showmoderator:
+
+"""""""""""""""""""""
+muteset showmoderator
+"""""""""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]muteset showmoderator <true_or_false>
+
+**Description**
+
+Decide whether the name of the moderator muting a user should be included in the DM to that user.
+
+**Arguments**
+
+* ``<true_or_false>``: Whether to enable or disable this setting, must provide ``true`` or ``false``.
+
+.. _mutes-command-unmute:
+
+^^^^^^
+unmute
+^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]unmute <users...> [reason]
+
+**Description**
+
+Unmute users.
+
+**Arguments**
+
+* ``<users...>``: A space separated list of usernames, ID's, or mentions.
+* ``[reason]``: The reason for the unmute.
+
+.. _mutes-command-unmutechannel:
+
+^^^^^^^^^^^^^
+unmutechannel
+^^^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]unmutechannel <users...> [reason]
+
+.. tip:: Alias: ``channelunmute``
+
+**Description**
+
+Unmute a user in this channel (or in the parent of this thread).
+
+**Arguments**
+
+* ``<users...>``: A space separated list of usernames, ID's, or mentions.
+* ``[reason]``: The reason for the unmute.
+
+.. _mutes-command-voicemute:
+
+^^^^^^^^^
+voicemute
+^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]voicemute <users...> [reason]
+
+**Description**
+
+Mute a user in their current voice channel.
+
+Examples:
+
+* ``[p]voicemute @member1 @member2 spam 5 hours``
+* ``[p]voicemute @member1 3 days``
+
+**Arguments**
+
+* ``<users...>``: A space separated list of usernames, ID's, or mentions.
+* ``[time_and_reason]``: The time and reason. If no time is provided, the mute will use the default set time or indefinite if this hasn't been configured.
+
+.. _mutes-command-voiceunmute:
+
+^^^^^^^^^^^
+voiceunmute
+^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]voiceunmute <users...> [reason]
+
+**Description**
+
+Unmute a user in their current voice channel.
+
+**Arguments**
+
+* ``<users...>``: A space separated list of usernames, ID's, or mentions.
+* ``[reason]``: The reason for the unmute.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/permissions.rst

@@ -0,0 +1,440 @@
+.. _permissions:
+
+===========
+Permissions
+===========
+
+This is the cog guide for the permissions 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 permissions
+
+.. _permissions-usage:
+
+-----
+Usage
+-----
+
+Customise permissions for commands and cogs.
+
+This cog extends the default permission model of the bot. By default, many commands are restricted based on what the command can do.
+This cog allows you to refine some of those restrictions. You can allow wider or narrower access to most commands using it. You cannot, however, change the restrictions on owner-only commands.
+
+When additional rules are set using this cog, those rules will be checked prior to checking for the default restrictions of the command.
+Global rules (set by the owner) are checked first, then rules set for servers. If multiple global or server rules apply to the case, the order they are checked in is:
+
+1. Rules about a user.
+2. Rules about the voice channel a user is in.
+3. Rules about the text channel or a parent of the thread a command was issued in.
+4. Rules about a role the user has (The highest role they have with a rule will be used).
+5. Rules about the server a user is in (Global rules only).
+
+
+.. _permissions-commands:
+
+--------
+Commands
+--------
+
+.. _permissions-command-permissions:
+
+^^^^^^^^^^^
+permissions
+^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions 
+
+**Description**
+
+Command permission management tools.
+
+.. _permissions-command-permissions-acl:
+
+"""""""""""""""
+permissions acl
+"""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions acl 
+
+**Description**
+
+Manage permissions with YAML files.
+
+.. tip:: See :ref:`here <cog_permissions>` for more information with configuring these yaml files.
+
+.. _permissions-command-permissions-acl-getglobal:
+
+"""""""""""""""""""""""""
+permissions acl getglobal
+"""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions acl getglobal 
+
+**Description**
+
+Get a YAML file detailing all global rules.
+
+.. _permissions-command-permissions-acl-getserver:
+
+"""""""""""""""""""""""""
+permissions acl getserver
+"""""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions acl getserver 
+
+**Description**
+
+Get a YAML file detailing all rules in this server.
+
+.. _permissions-command-permissions-acl-setglobal:
+
+"""""""""""""""""""""""""
+permissions acl setglobal
+"""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions acl setglobal 
+
+**Description**
+
+Set global rules with a YAML file.
+
+.. warning::    
+    This will override reset *all* global rules
+    to the rules specified in the uploaded file.
+
+This does not validate the names of commands and cogs before
+setting the new rules.
+
+.. _permissions-command-permissions-acl-setserver:
+
+"""""""""""""""""""""""""
+permissions acl setserver
+"""""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions acl setserver 
+
+**Description**
+
+Set rules for this server with a YAML file.
+
+.. warning::    
+    This will override reset *all* rules in this
+    server to the rules specified in the uploaded file.
+
+.. _permissions-command-permissions-acl-updateglobal:
+
+""""""""""""""""""""""""""""
+permissions acl updateglobal
+""""""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions acl updateglobal 
+
+**Description**
+
+Update global rules with a YAML file.
+
+This won't touch any rules not specified in the YAML
+file.
+
+.. _permissions-command-permissions-acl-updateserver:
+
+""""""""""""""""""""""""""""
+permissions acl updateserver
+""""""""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions acl updateserver 
+
+**Description**
+
+Update rules for this server with a YAML file.
+
+This won't touch any rules not specified in the YAML
+file.
+
+.. _permissions-command-permissions-acl-yamlexample:
+
+"""""""""""""""""""""""""""
+permissions acl yamlexample
+"""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions acl yamlexample 
+
+**Description**
+
+Sends an example of the yaml layout for permissions
+
+.. _permissions-command-permissions-addglobalrule:
+
+"""""""""""""""""""""""""
+permissions addglobalrule
+"""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions addglobalrule <allow_or_deny> <cog_or_command> <who_or_what...>
+
+**Description**
+
+Add a global rule to a cog or command.
+
+**Arguments**
+
+* ``<allow_or_deny>``: This should be one of "allow" or "deny".
+* ``<cog_or_command>``: The cog or command to add the rule to. This is case sensitive.
+* ``<who_or_what...>``: One or more users, channels or roles the rule is for.
+
+.. _permissions-command-permissions-addserverrule:
+
+"""""""""""""""""""""""""
+permissions addserverrule
+"""""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions addserverrule <allow_or_deny> <cog_or_command> <who_or_what...>
+
+**Description**
+
+Add a rule to a cog or command in this server.
+
+**Arguments**
+
+* ``<allow_or_deny>``: This should be one of "allow" or "deny".
+* ``<cog_or_command>``: The cog or command to add the rule to. This is case sensitive.
+* ``<who_or_what...>``: One or more users, channels or roles the rule is for.
+
+.. _permissions-command-permissions-canrun:
+
+""""""""""""""""""
+permissions canrun
+""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions canrun <user> <command>
+
+**Description**
+
+Check if a user can run a command.
+
+This will take the current context into account, such as the
+server and text channel.
+
+**Arguments**
+
+* ``<user>``: The user to check permissions for.
+* ``<command>``: The command to check whether the user can run it or not.
+
+.. _permissions-command-permissions-clearglobalrules:
+
+""""""""""""""""""""""""""""
+permissions clearglobalrules
+""""""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions clearglobalrules 
+
+**Description**
+
+Reset all global rules.
+
+.. _permissions-command-permissions-clearserverrules:
+
+""""""""""""""""""""""""""""
+permissions clearserverrules
+""""""""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions clearserverrules 
+
+**Description**
+
+Reset all rules in this server.
+
+.. _permissions-command-permissions-explain:
+
+"""""""""""""""""""
+permissions explain
+"""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions explain 
+
+**Description**
+
+Explain how permissions works.
+
+.. _permissions-command-permissions-removeglobalrule:
+
+""""""""""""""""""""""""""""
+permissions removeglobalrule
+""""""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions removeglobalrule <cog_or_command> <who_or_what...>
+
+**Description**
+
+Remove a global rule from a command.
+
+**Arguments**
+
+* ``<cog_or_command>``: The cog or command to remove the rule from. This is case sensitive.
+* ``<who_or_what...>``: One or more users, channels or roles the rule is for.
+
+.. _permissions-command-permissions-removeserverrule:
+
+""""""""""""""""""""""""""""
+permissions removeserverrule
+""""""""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions removeserverrule <cog_or_command> <who_or_what...>
+
+**Description**
+
+Remove a server rule from a command.
+
+**Arguments**
+
+* ``<cog_or_command>``: The cog or command to remove the rule from. This is case sensitive.
+* ``<who_or_what...>``: One or more users, channels or roles the rule is for.
+
+.. _permissions-command-permissions-setdefaultglobalrule:
+
+""""""""""""""""""""""""""""""""
+permissions setdefaultglobalrule
+""""""""""""""""""""""""""""""""
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions setdefaultglobalrule <allow_or_deny> <cog_or_command>
+
+**Description**
+
+Set the default global rule for a command or a cog.
+
+This is the rule a command will default to when no other rule
+is found.
+
+**Arguments**
+
+* ``<cog_or_command>``: The cog or command to add the rule to. This is case sensitive.
+* ``<who_or_what...>``: One or more users, channels or roles the rule is for.
+
+.. _permissions-command-permissions-setdefaultserverrule:
+
+""""""""""""""""""""""""""""""""
+permissions setdefaultserverrule
+""""""""""""""""""""""""""""""""
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]permissions setdefaultserverrule <allow_or_deny> <cog_or_command>
+
+**Description**
+
+Set the default rule for a command or a cog in this server.
+
+This is the rule a command will default to when no other rule
+is found.
+
+**Arguments**
+
+* ``<cog_or_command>``: The cog or command to add the rule to. This is case sensitive.
+* ``<who_or_what...>``: One or more users, channels or roles the rule is for.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/reports.rst

@@ -0,0 +1,141 @@
+.. _reports:
+
+=======
+Reports
+=======
+
+This is the cog guide for the reports 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 reports
+
+.. _reports-usage:
+
+-----
+Usage
+-----
+
+Create user reports that server staff can respond to.
+
+Users can open reports using ``[p]report``. These are then sent
+to a channel in the server for staff, and the report creator
+gets a DM. Both can be used to communicate.
+
+
+.. _reports-commands:
+
+--------
+Commands
+--------
+
+.. _reports-command-report:
+
+^^^^^^
+report
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]report [text]
+
+**Description**
+
+Send a report.
+
+Use without arguments for interactive reporting, or do
+``[p]report [text]`` to use it non-interactively.
+
+**Arguments**
+
+* ``[text]``: The content included within the report.
+
+.. _reports-command-report-interact:
+
+"""""""""""""""
+report interact
+"""""""""""""""
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]report interact <ticket_number>
+
+**Description**
+
+Open a message tunnel.
+
+This tunnel will forward things you say in this channel or thread
+to the ticket opener's direct messages.
+
+Tunnels do not persist across bot restarts.
+
+**Arguments**
+
+* ``<ticket_number>``: The ticket number to open the tunnel in.
+
+.. _reports-command-reportset:
+
+^^^^^^^^^
+reportset
+^^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]reportset 
+
+**Description**
+
+Manage Reports.
+
+.. _reports-command-reportset-output:
+
+""""""""""""""""
+reportset output
+""""""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]reportset output <channel>
+
+**Description**
+
+Set the channel where reports will be sent.
+
+**Arguments**
+
+* ``<channel>``: |channel-input|
+
+.. _reports-command-reportset-toggle:
+
+""""""""""""""""
+reportset toggle
+""""""""""""""""
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]reportset toggle 
+
+**Description**
+
+Enable or disable reporting for this server.  

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/streams.rst

@@ -0,0 +1,533 @@
+.. _streams:
+
+=======
+Streams
+=======
+
+This is the cog guide for the Streams 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 streams
+
+.. _streams-usage:
+
+-----
+Usage
+-----
+
+This cog provides commands to check if a channel 
+on a supported streaming service is live as well 
+as to create and manage alerts for channels.
+
+Supported streaming services are:
+
+- Twitch
+- Youtube
+- Picarto
+
+Youtube and Twitch both require setting authentication 
+details for commands for those services to work. See 
+:ref:`[p]streamset twitchtoken <streams-command-streamset-twitchtoken>` and 
+:ref:`[p]streamset youtubekey <streams-command-streamset-youtubekey>`
+for more information.
+
+.. _streams-commands:
+
+--------
+Commands
+--------
+
+.. _streams-command-streamset:
+
+^^^^^^^^^
+streamset
+^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset
+
+**Description**
+
+Manage stream alert settings.
+
+.. _streams-command-streamset-autodelete:
+
+^^^^^^^^^^^^^^^^^^^^
+streamset autodelete
+^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset autodelete <on_off>
+
+**Description**
+
+Toggles automatic deletion of stream alerts when the 
+stream goes offline.
+
+**Arguments**
+
+* ``<on_off>``: Whether to turn on or off
+
+.. _streams-command-streamset-ignorereruns:
+
+^^^^^^^^^^^^^^^^^^^^^^
+streamset ignorereruns
+^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset ignorereruns
+
+**Description**
+
+Toggles excluding reruns from the alerts.
+
+At this time, this functionality only applies to Twitch stream alerts.
+
+.. _streams-command-streamset-mention:
+
+^^^^^^^^^^^^^^^^^
+streamset mention
+^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset mention
+
+**Description**
+
+Toggle mentions for stream alerts.
+
+.. _streams-command-streamset-mention-all:
+
+^^^^^^^^^^^^^^^^^^^^^
+streamset mention all
+^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset mention all
+
+**Description**
+
+Toggle mentioning ``@everyone`` for stream alerts.
+
+.. _streams-command-streamset-mention-online:
+
+^^^^^^^^^^^^^^^^^^^^^^^^
+streamset mention online
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset mention online
+
+**Description**
+
+Toggle mentioning ``@here`` for stream alerts.
+
+.. _streams-command-streamset-mention-role:
+
+^^^^^^^^^^^^^^^^^^^^^^
+streamset mention role
+^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset mention role <role>
+
+**Description**
+
+Toggle mentioning a role for stream alerts.
+
+**Arguments**
+
+* ``<role>``: The role to toggle a mention for. |role-input|
+
+.. _streams-command-streamset-message:
+
+^^^^^^^^^^^^^^^^^
+streamset message
+^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset message
+
+**Description**
+
+Manage custom messages for stream alerts.
+
+.. _streams-command-streamset-message-mention:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^
+streamset message mention
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset message mention <message>
+
+**Description**
+
+Sets a stream alert message for when mentions are enabled.
+
+Use ``{mention}`` in the message to insert the selected mentions.
+
+Use ``{stream}`` in the message to insert the channel or user name.
+
+Use ``{stream.display_name}`` in the message to insert the channel's display name
+(on Twitch, this may be different from ``{stream}``).
+
+For example: ``[p]streamset message mention {mention}, {stream.display_name} is live!``
+
+**Arguments**
+
+* ``<message>``: Your alert message
+
+.. _streams-command-streamset-message-nomention:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+streamset message nomention
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset message nomention <message>
+
+**Description**
+
+Sets a stream alert message for when mentions are disabled.
+
+Use ``{stream}`` in the message to insert the channel or user name.
+
+Use ``{stream.display_name}`` in the message to insert the channel's display name
+(on Twitch, this may be different from ``{stream}``).
+
+For example: ``[p]streamset message nomention {stream.display_name} is live!``
+
+**Arguments**
+
+* ``<message>``: Your alert message
+
+.. _streams-command-streamset-message-clear:
+
+^^^^^^^^^^^^^^^^^^^^^^^
+streamset message clear
+^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset message clear
+
+**Description**
+
+Resets the stream alert messages for the server.
+
+.. _streams-command-streamset-timer:
+
+^^^^^^^^^^^^^^^
+streamset timer
+^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset timer <refresh_timer>
+
+**Description**
+
+Sets the refresh time for stream alerts (how frequently they will be checked).
+
+This cannot be set to anything less than 60 seconds.
+
+**Arguments**
+
+* ``<refresh_timer>``: The frequency with which streams should be checked, in seconds
+
+.. _streams-command-streamset-youtubekey:
+
+^^^^^^^^^^^^^^^^^^^^
+streamset youtubekey
+^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset youtubekey
+
+**Description**
+
+Explains how to set the YouTube token.
+
+To get one, do the following:
+
+1. Create a project
+(see https://support.google.com/googleapi/answer/6251787 for details)
+
+2. Enable the YouTube Data API v3
+(see https://support.google.com/googleapi/answer/6158841 for instructions)
+
+3. Set up your API key
+(see https://support.google.com/googleapi/answer/6158862 for instructions)
+
+4. Copy your API key and run the command ``[p]set api youtube api_key <your_api_key_here>``
+
+.. attention:: These tokens are sensitive and should only be 
+               used in a private channel or in DM with the bot.
+
+.. _streams-command-streamset-twitchtoken:
+
+^^^^^^^^^^^^^^^^^^^^^
+streamset twitchtoken
+^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamset twitchtoken
+
+**Description**
+
+Explains how to set the Twitch token.
+
+To set the Twitch API tokens, follow these steps:
+
+1. Go to this page: https://dev.twitch.tv/dashboard/apps.
+
+2. Click Register Your Application.
+
+3. Enter a name, set the OAuth Redirect URI to http://localhost, and select an Application Category of your choosing.
+
+4. Click Register.
+
+5. Copy your client ID and your client secret into:
+``[p]set api twitch client_id <your_client_id_here> client_secret <your_client_secret_here>``
+
+.. attention:: These tokens are sensitive and should only be 
+               used in a private channel or in DM with the bot.
+
+.. _streams-command-streamset-usebuttons:
+
+^^^^^^^^^^^^^^^^^^^^
+streamset usebuttons
+^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]streamset usebuttons
+
+**Description**
+
+Toggle whether to use buttons for stream alerts.
+
+.. _streams-command-picarto:
+
+^^^^^^^
+picarto
+^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]picarto <channel_name>
+
+**Description**
+
+Check if a Picarto channel is live.
+
+**Arguments**
+
+* ``<channel_name>``: The Picarto channel to check.
+
+.. _streams-command-twitchstream:
+
+^^^^^^^^^^^^
+twitchstream
+^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]twitchstream <channel_name>
+
+**Description**
+
+Check if a Twitch channel is live.
+
+**Arguments**
+
+* ``<channel_name>``: The Twitch channel to check.
+
+.. _streams-command-youtubestream:
+
+^^^^^^^^^^^^^
+youtubestream
+^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]youtubestream <channel_id_or_name>
+
+**Description**
+
+Check if a YouTube channel is live.
+
+**Arguments**
+
+* ``<channel_id_or_name>``: The name or id of the YouTube channel to be checked.
+
+.. _streams-command-streamalert:
+
+^^^^^^^^^^^
+streamalert
+^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamalert
+
+**Description**
+
+Manage automated stream alerts.
+
+.. _streams-command-streamalert-list:
+
+^^^^^^^^^^^^^^^^
+streamalert list
+^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamalert list
+
+**Description**
+
+Lists all active alerts in the current server.
+
+.. _streams-command-streamalert-picarto:
+
+^^^^^^^^^^^^^^^^^^^
+streamalert picarto
+^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamalert picarto <channel_name>
+
+**Description**
+
+Toggle alerts in the current channel for the 
+specified Picarto channel.
+
+**Arguments**
+
+* ``<channel_name>``: The Picarto channel to toggle the alert for.
+
+.. _streams-command-streamalert-twitch-channel:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+streamalert twitch channel
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamalert twitch channel <channel_name>
+
+**Description**
+
+Toggle alerts in the current channel for the 
+specified Twitch channel.
+
+**Arguments**
+
+* ``<channel_name>``: The Twitch channel to toggle the alert for.
+
+.. _streams-command-streamalert-youtube:
+
+^^^^^^^^^^^^^^^^^^^
+streamalert youtube
+^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamalert youtube <channel_name>
+
+**Description**
+
+Toggle alerts in the current channel for the 
+specified Picarto channel.
+
+**Arguments**
+
+* ``<channel_id_or_name>``: The name or id of the YouTube channel to be checked.
+
+.. _streams-command-streamalert-stop:
+
+^^^^^^^^^^^^^^^^
+streamalert stop
+^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+    
+    [p]streamalert stop [disable-all=No]
+
+**Description**
+
+Disable all stream alerts for this channel or server.
+
+**Arguments**
+
+* ``[disable-all]``: Defaults to ``no``. If this is set to ``yes``, all 
+  stream alerts in the current server will be disabled. 
+  If ``no`` or unspecified, all stream alerts in the 
+  current channel will be stopped. 

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/trivia.rst

@@ -0,0 +1,439 @@
+.. _trivia:
+
+======
+Trivia
+======
+
+This is the cog guide for the trivia 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 trivia
+
+.. _trivia-usage:
+
+-----
+Usage
+-----
+
+This cog allows for playing trivia with others. You may 
+choose to play just one category at a time or choose 
+multiple to add variety to your game. You can even create 
+your own lists!
+
+.. _trivia-commands:
+
+--------
+Commands
+--------
+
+Here is a list of all of the commands for this cog:
+
+.. _trivia-command-triviaset:
+
+^^^^^^^^^
+triviaset
+^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset
+
+**Description**
+
+Commands for managing trivia settings.
+
+.. _trivia-command-triviaset-botplays:
+
+^^^^^^^^^^^^^^^^^^
+triviaset botplays
+^^^^^^^^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset botplays <true_or_false>
+
+**Description**
+
+Sets whether the bot gains a point if nobody guesses correctly.
+
+**Arguments**
+
+- ``<true_or_false>`` If ``true``, the bot will gain a point if nobody
+  guesses correctly, otherwise it will not.
+
+.. _trivia-command-triviaset-maxscore:
+
+^^^^^^^^^^^^^^^^^^
+triviaset maxscore
+^^^^^^^^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset maxscore <score>
+
+**Description**
+
+Sets the total points required to win.
+
+**Arguments**
+
+- ``<score>`` The amount of points required to win.
+
+.. _trivia-command-triviaset-override:
+
+^^^^^^^^^^^^^^^^^^
+triviaset override
+^^^^^^^^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset override <enabled>
+
+**Description**
+
+Allow/disallow trivia lists to override the settings.
+
+**Arguments**
+
+- ``<enabled>`` Whether trivia lists should be able to override settings.
+
+.. _trivia-command-triviaset-payout:
+
+^^^^^^^^^^^^^^^^
+triviaset payout
+^^^^^^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset payout <multiplier>
+
+**Description**
+
+Sets the payout multiplier. 
+
+If a user wins trivia when at least 3 users are playing, they will receive credits; 
+the amount received is determined by multiplying their total score by this multiplier.
+
+**Arguments**
+
+- ``<multiplier>`` The amount to multiply the winner's score by to determine payout.
+  This can be any positive decimal number. Setting this to 0 will disable.
+
+.. _trivia-command-triviaset-revealanswer:
+
+^^^^^^^^^^^^^^^^^^^^^^
+triviaset revealanswer
+^^^^^^^^^^^^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset revealanswer <true_or_false>
+
+**Description**
+
+Sets whether or not the answer is revealed if the time limit for answering runs out.
+
+**Arguments**
+
+- ``<true_or_false>`` If ``true``, the bot will reveal the answer if there is no
+  correct guess within the time limit.
+
+.. _trivia-command-triviaset-showsettings:
+
+^^^^^^^^^^^^^^^^^^^^^^
+triviaset showsettings
+^^^^^^^^^^^^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset showsettings
+
+**Description**
+
+Shows the current trivia settings.
+
+.. _trivia-command-triviaset-stopafter:
+
+^^^^^^^^^^^^^^^^^^^
+triviaset stopafter
+^^^^^^^^^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset stopafter <seconds>
+
+**Description**
+
+Sets how long the bot should wait before stopping the trivia 
+session due to lack of response.
+
+**Arguments**
+
+- ``<seconds>`` The number of seconds to wait before stopping the session.
+
+.. _trivia-command-triviaset-timelimit:
+
+^^^^^^^^^^^^^^^^^^^
+triviaset timelimit
+^^^^^^^^^^^^^^^^^^^
+
+.. note:: |mod-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset timelimit <seconds>
+
+**Description**
+
+Sets the maximum time permitted to answer a question.
+
+**Arguments**
+
+- ``<seconds>`` The number of seconds to wait for an answer.
+
+.. _trivia-command-triviaset-custom:
+
+^^^^^^^^^^^^^^^^
+triviaset custom
+^^^^^^^^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset custom
+
+**Description**
+
+Manage custom trivia lists.
+
+.. tip:: 
+
+    Looking to learn how to create your own trivia lists?
+    See :ref:`here <guide_trivia_list_creation>` for more information.
+
+.. _trivia-command-triviaset-custom-upload:
+
+^^^^^^^^^^^^^^^^^^^^^^^
+triviaset custom upload
+^^^^^^^^^^^^^^^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset custom upload
+
+**Description**
+
+Upload a custom trivia list. The bot will prompt you to upload 
+your list as an attachment in Discord.
+
+.. _trivia-command-triviaset-custom-list:
+
+^^^^^^^^^^^^^^^^^^^^^
+triviaset custom list
+^^^^^^^^^^^^^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset custom list
+
+**Description**
+
+List all uploaded custom trivia lists.
+
+.. _trivia-command-triviaset-custom-delete:
+
+^^^^^^^^^^^^^^^^^^^^^^^
+triviaset custom delete
+^^^^^^^^^^^^^^^^^^^^^^^
+
+.. note:: |owner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]triviaset custom delete <name>
+
+**Description**
+
+Delete a custom trivia list.
+
+**Arguments**
+
+- ``<name>`` The name of the custom list to be deleted.
+
+.. _trivia-command-trivia:
+
+^^^^^^
+trivia
+^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]trivia <categories...>
+
+**Description**
+
+Start a trivia session on the specified category.
+
+Multiple categories can be listed, in which case the trivia session 
+will use all of the specified lists to select questions from.
+
+**Arguments**
+
+- ``<categories...>`` The category to play. Can be multiple.
+
+.. _trivia-command-trivia-leaderboard:
+
+^^^^^^^^^^^^^^^^^^
+trivia leaderboard
+^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]trivia leaderboard
+
+**Description**
+
+Shows the trivia leaderboard. Defaults to the top ten in the 
+current server, sorted by total wins. The subcommands provide 
+more customized leaderboards.
+
+.. _trivia-command-trivia-leaderboard-global:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^
+trivia leaderboard global
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]trivia leaderboard global [sort_by=wins] [top=10]
+
+**Description**
+
+The global trivia leaderboard.
+
+**Arguments**
+
+- ``[sort_by=wins]`` The method by which to sort the leaderboard (defaults to wins). Can be one of:
+
+    - ``wins`` Total wins
+    - ``avg`` Average score
+    - ``total`` Total correct answers from all sessions
+    - ``games`` Total games played.
+
+- ``[top=10]`` The number of ranks to show on the leaderboard. Defaults to 10
+
+.. _trivia-command-trivia-leaderboard-server:
+
+^^^^^^^^^^^^^^^^^^^^^^^^^
+trivia leaderboard server
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]trivia leaderboard server [sort_by=wins] [top=10]
+
+**Description**
+
+The trivia leaderboard for this server.
+
+**Arguments**
+
+- ``[sort_by=wins]`` The method by which to sort the leaderboard (defaults to wins). Can be one of:
+
+    - ``wins`` Total wins
+    - ``avg`` Average score
+    - ``total`` Total correct answers from all sessions
+    - ``games`` Total games played.
+
+- ``[top=10]`` The number of ranks to show on the leaderboard. Defaults to 10
+
+.. _trivia-command-trivia-list:
+
+^^^^^^^^^^^
+trivia list
+^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]trivia list
+
+**Description**
+
+Lists the available trivia categories
+
+.. _trivia-command-trivia-stop:
+
+^^^^^^^^^^^
+trivia stop
+^^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]trivia stop
+
+**Description**
+
+Stops an ongoing trivia session.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_guides/warnings.rst

@@ -0,0 +1,403 @@
+.. _warnings:
+
+========
+Warnings
+========
+
+This is the cog guide for the warnings 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 warnings
+
+.. _warnings-usage:
+
+-----
+Usage
+-----
+
+Warn misbehaving users and take automated actions.
+
+
+.. _warnings-commands:
+
+--------
+Commands
+--------
+
+.. _warnings-command-actionlist:
+
+^^^^^^^^^^
+actionlist
+^^^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]actionlist 
+
+**Description**
+
+List all configured automated actions for Warnings.
+
+.. _warnings-command-mywarnings:
+
+^^^^^^^^^^
+mywarnings
+^^^^^^^^^^
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]mywarnings 
+
+**Description**
+
+List warnings for yourself.
+
+.. _warnings-command-reasonlist:
+
+^^^^^^^^^^
+reasonlist
+^^^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]reasonlist 
+
+**Description**
+
+List all configured reasons for Warnings.
+
+.. _warnings-command-unwarn:
+
+^^^^^^
+unwarn
+^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]unwarn <member> <warn_id> [reason]
+
+**Description**
+
+Remove a warning from a member.
+
+**Arguments**
+
+* ``<member>``: The member to remove the warning from. |member-input-quotes|
+* ``<warn_id>``: The warning ID to remove from the member.
+* ``[reason]``: The reason for unwarning this member.
+
+.. _warnings-command-warn:
+
+^^^^
+warn
+^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warn <member> [points=1] <reason>
+
+**Description**
+
+Warn the user for the specified reason.
+
+**Arguments**
+
+* ``<member>``: The member to warn. |member-input-quotes|
+* ``[points]``: The number of points the warning should be for. If no number is supplied, 1 point will be given. Pre-set warnings disregard this.
+* ``<reason>``: The reason for the warning. This can be a registered reason, or a custom reason if ``[p]warningset allowcustomreasons`` is set.
+
+.. _warnings-command-warnaction:
+
+^^^^^^^^^^
+warnaction
+^^^^^^^^^^
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warnaction 
+
+**Description**
+
+Manage automated actions for Warnings.
+
+Actions are essentially command macros. Any command can be run
+when the action is initially triggered, and/or when the action
+is lifted.
+
+Actions must be given a name and a points threshold. When a
+user is warned enough so that their points go over this
+threshold, the action will be executed.
+
+.. _warnings-command-warnaction-add:
+
+""""""""""""""
+warnaction add
+""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warnaction add <name> <points>
+
+**Description**
+
+Create an automated action.
+
+Duplicate action names are not allowed.
+
+**Arguments**
+
+* ``<name>``: The name of the action.
+* ``<points>``: The number of points for this action.
+
+.. _warnings-command-warnaction-delete:
+
+"""""""""""""""""
+warnaction delete
+"""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warnaction delete <action_name>
+
+**Description**
+
+Delete the action with the specified name.
+
+**Arguments**
+
+* ``<action_name>``: The name of the action to delete.
+
+.. _warnings-command-warnings:
+
+^^^^^^^^
+warnings
+^^^^^^^^
+
+.. note:: |admin-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warnings <member>
+
+**Description**
+
+List the warnings for the specified member.
+
+**Arguments**
+
+* ``<member>``: The member to get the warnings for. |member-input|
+
+.. _warnings-command-warningset:
+
+^^^^^^^^^^
+warningset
+^^^^^^^^^^
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warningset 
+
+**Description**
+
+Manage settings for Warnings.
+
+.. _warnings-command-warningset-allowcustomreasons:
+
+"""""""""""""""""""""""""""""
+warningset allowcustomreasons
+"""""""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warningset allowcustomreasons <true_or_false>
+
+**Description**
+
+Enable or disable custom reasons for a warning.
+
+**Arguments**
+
+* ``<true_or_false>``: |bool-input|
+
+.. _warnings-command-warningset-senddm:
+
+"""""""""""""""""
+warningset senddm
+"""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warningset senddm <true_or_false>
+
+**Description**
+
+Set whether warnings should be sent to users in DMs.
+
+**Arguments**
+
+* ``<true_or_false>``: |bool-input|
+
+.. _warnings-command-warningset-showmoderator:
+
+""""""""""""""""""""""""
+warningset showmoderator
+""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warningset showmoderator <true_or_false>
+
+**Description**
+
+Decide whether the name of the moderator warning a user should be included in the DM to that user.
+
+**Arguments**
+
+* ``<true_or_false>``: |bool-input|
+
+.. _warnings-command-warningset-usewarnchannel:
+
+"""""""""""""""""""""""""
+warningset usewarnchannel
+"""""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warningset usewarnchannel <true_or_false>
+
+**Description**
+
+Set if warnings should be sent to a channel set with ``[p]warningset warnchannel``.
+
+**Arguments**
+
+* ``<true_or_false>``: |bool-input|
+
+.. _warnings-command-warningset-warnchannel:
+
+""""""""""""""""""""""
+warningset warnchannel
+""""""""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warningset warnchannel [channel]
+
+**Description**
+
+Set the channel where warnings should be sent to.
+
+**Arguments**
+
+* ``[channel]``: |channel-input| Leave empty to use the channel ``[p]warn`` command was called in.
+
+.. _warnings-command-warnreason:
+
+^^^^^^^^^^
+warnreason
+^^^^^^^^^^
+
+.. note:: |guildowner-lock|
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warnreason 
+
+**Description**
+
+Manage warning reasons.
+
+Reasons must be given a name, description and points value. The
+name of the reason must be given when a user is warned.
+
+.. _warnings-command-warnreason-create:
+
+"""""""""""""""""
+warnreason create
+"""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warnreason create <name> <points> <description>
+
+.. tip:: Alias: ``warnreason add``
+
+**Description**
+
+Create a warning reason.
+
+**Arguments**
+
+* ``<name>``: The name for the new reason.
+* ``<points>``: The number of points with the new reason.
+* ``<description>``: The description of the new warn reason.
+
+.. _warnings-command-warnreason-delete:
+
+"""""""""""""""""
+warnreason delete
+"""""""""""""""""
+
+**Syntax**
+
+.. code-block:: none
+
+    [p]warnreason delete <reason_name>
+    
+**Description**
+
+Delete a warning reason.
+
+**Arguments**
+
+* ``<reason_name>``: The name of the reason to delete.

testbed/Cog-Creators__Red-DiscordBot/docs/cog_permissions.rst

@@ -0,0 +1,98 @@
+.. Permissions Cog Reference
+.. _cog_permissions:
+
+=========================
+Permissions Cog Reference
+=========================
+
+------------
+How it works
+------------
+
+When loaded, the permissions cog will allow you to define extra custom rules for who can use a
+command.
+
+If no applicable rules are found, the command will behave normally.
+
+Rules can also be added to cogs, which will affect all commands from that cog. The cog name can be
+found from the help menu.
+
+-------------
+Rule priority
+-------------
+
+Rules set for subcommands will take precedence over rules set for the parent commands, which
+lastly take precedence over rules set for the cog. So for example, if a user is denied the Core
+cog, but allowed the ``[p]set token`` command, the user will not be able to use any command in the
+Core cog except for ``[p]set token``.
+
+In terms of scope, global rules will be checked first, then server rules.
+
+For each of those, the first rule pertaining to one of the following models will be used:
+
+1. User
+2. Voice channel a user is connected to
+3. The channel command was issued in (parent channel in case of invocations in threads)
+4. Channel category
+5. Roles, highest to lowest
+6. Server (can only be in global rules)
+7. Default rules
+
+In private messages, only global rules about a user will be checked.
+
+-------------------------
+Setting Rules From a File
+-------------------------
+
+The permissions cog can also set, display or update rules with a YAML file with the
+``[p]permissions yaml`` command. Models must be represented by ID. Rules must be ``true`` for
+allow, or ``false`` for deny. Here is an example:
+
+.. code-block:: yaml
+
+    COG:
+      Admin:
+        78631113035100160: true
+        96733288462286848: false
+      Audio:
+        133049272517001216: true
+        default: false
+    COMMAND:
+      cleanup bot:
+        78631113035100160: true
+        default: false
+      ping:
+        96733288462286848: false
+        default: true
+
+----------------------
+Example configurations
+----------------------
+
+Locking the ``[p]play`` command to approved server(s) as a bot owner:
+
+.. code-block:: none
+
+    [p]permissions setdefaultglobalrule deny play
+    [p]permissions addglobalrule allow play [server ID or name]
+
+Locking the ``[p]play`` command to specific voice channel(s) as a serverowner or admin:
+
+.. code-block:: none
+
+    [p]permissions setdefaultserverrule deny play
+    [p]permissions setdefaultserverrule deny "playlist start"
+    [p]permissions addserverrule allow play [voice channel ID or name]
+    [p]permissions addserverrule allow "playlist start" [voice channel ID or name]
+
+Allowing extra roles to use ``[p]cleanup``:
+
+.. code-block:: none
+
+    [p]permissions addserverrule allow cleanup [role ID]
+
+Preventing ``[p]cleanup`` from being used in channels where message history is important:
+
+.. code-block:: none
+
+    [p]permissions addserverrule deny cleanup [channel ID or mention]

testbed/Cog-Creators__Red-DiscordBot/docs/conf.py

@@ -0,0 +1,281 @@
+#!/usr/bin/env python3
+# -*- coding: utf-8 -*-
+#
+# Red - Discord Bot documentation build configuration file, created by
+# sphinx-quickstart on Thu Aug 10 23:18:25 2017.
+#
+# This file is execfile()d with the current directory set to its
+# containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#
+import os
+import sys
+import time
+
+sys.path.insert(0, os.path.abspath(".."))
+sys.path.insert(0, os.path.abspath("_ext"))
+
+os.environ["BUILDING_DOCS"] = "1"
+
+
+# -- General configuration ------------------------------------------------
+
+# If your documentation needs a minimal Sphinx version, state it here.
+#
+# needs_sphinx = '1.0'
+
+# Add any Sphinx extension module names here, as strings. They can be
+# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
+# ones.
+extensions = [
+    "sphinx.ext.autodoc",
+    "sphinx.ext.extlinks",
+    "sphinx.ext.intersphinx",
+    "sphinx.ext.viewcode",
+    "sphinx.ext.napoleon",
+    "sphinx.ext.doctest",
+    "sphinxcontrib_trio",
+    "sphinx-prompt",
+    "deprecated_removed",
+]
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ["_templates"]
+
+# The suffix(es) of source filenames.
+# You can specify multiple suffix as a list of string:
+#
+# source_suffix = ['.rst', '.md']
+source_suffix = ".rst"
+
+# The master toctree document.
+master_doc = "index"
+
+# General information about the project.
+project = "Red - Discord Bot"
+copyright = f"2018-{time.strftime('%Y')}, Cog Creators"
+author = "Cog Creators"
+
+# The version info for the project you're documenting, acts as replacement for
+# |version| and |release|, also used in various other places throughout the
+# built documents.
+#
+from redbot.core import __version__
+from discord import __version__ as dpy_version, version_info as dpy_version_info
+
+# The short X.Y version.
+version = __version__
+# The full version, including alpha/beta/rc tags.
+release = __version__
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#
+# This is also used if you do content translation via gettext catalogs.
+# Usually you set "language" from the command line for these cases.
+language = "en"
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+# This patterns also effect to html_static_path and html_extra_path
+exclude_patterns = [
+    "_build",
+    "Thumbs.db",
+    ".DS_Store",
+    # to ensure that include files (partial pages) aren't built, exclude them
+    "**/_includes/**",
+]
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = "default"
+
+# If true, `todo` and `todoList` produce output, else they produce nothing.
+todo_include_todos = False
+
+# Role which is assigned when you make a simple reference within backticks
+default_role = "any"
+
+# Includes substitutions for all files
+with open("prolog.txt", "r") as file:
+    rst_prolog = file.read()
+
+# Adds d.py version to available substitutions in all files
+rst_prolog += f"\n.. |DPY_VERSION| replace:: {dpy_version}"
+
+# Add release highlight indicator to available substitutions in all files
+rst_prolog += f"\n.. |cool| replace:: \N{HEAVY BLACK HEART}\N{VARIATION SELECTOR-16}"
+
+# -- Options for HTML output ----------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  See the documentation for
+# a list of builtin themes.
+#
+html_theme = "sphinx_rtd_theme"
+
+# Add any extra paths that contain custom files (such as robots.txt or
+# .htaccess) here, relative to this directory. These files are copied
+# directly to the root of the documentation.
+#
+html_extra_path = ["_html"]
+
+# Theme options are theme-specific and customize the look and feel of a theme
+# further.  For a list of options available for each theme, see the
+# documentation.
+#
+# html_theme_options = {}
+
+html_context = {
+    # Enable the "Edit in GitHub link within the header of each page.
+    "display_github": True,
+    "github_user": "Cog-Creators",
+    "github_repo": "Red-DiscordBot",
+    "github_version": "V3/develop/docs/",
+}
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+# html_static_path = ['_static']
+
+# Custom sidebar templates, must be a dictionary that maps document names
+# to template names.
+#
+# This is required for the alabaster theme
+# refs: http://alabaster.readthedocs.io/en/latest/installation.html#sidebars
+html_sidebars = {
+    "**": [
+        "about.html",
+        "navigation.html",
+        "relations.html",  # needs 'show_related': True theme option to display
+        "searchbox.html",
+        "donate.html",
+    ]
+}
+
+
+# -- Options for HTMLHelp output ------------------------------------------
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = "Red-DiscordBotdoc"
+
+
+# -- Options for LaTeX output ---------------------------------------------
+
+latex_elements = {
+    # The paper size ('letterpaper' or 'a4paper').
+    #
+    # 'papersize': 'letterpaper',
+    # The font size ('10pt', '11pt' or '12pt').
+    #
+    # 'pointsize': '10pt',
+    # Additional stuff for the LaTeX preamble.
+    #
+    # 'preamble': '',
+    # Latex figure (float) alignment
+    #
+    # 'figure_align': 'htbp',
+}
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title,
+#  author, documentclass [howto, manual, or own class]).
+latex_documents = [
+    (master_doc, "Red-DiscordBot.tex", "Red - Discord Bot Documentation", "Cog Creators", "manual")
+]
+
+
+# -- Options for manual page output ---------------------------------------
+
+# One entry per manual page. List of tuples
+# (source start file, name, description, authors, manual section).
+man_pages = [(master_doc, "red-discordbot", "Red - Discord Bot Documentation", [author], 1)]
+
+
+# -- Options for Texinfo output -------------------------------------------
+
+# Grouping the document tree into Texinfo files. List of tuples
+# (source start file, target name, title, author,
+#  dir menu entry, description, category)
+texinfo_documents = [
+    (
+        master_doc,
+        "Red-DiscordBot",
+        "Red - Discord Bot Documentation",
+        author,
+        "Red-DiscordBot",
+        "One line description of project.",
+        "Miscellaneous",
+    )
+]
+
+
+# -- Options for linkcheck builder ----------------------------------------
+
+# A list of regular expressions that match URIs that should not be
+# checked when doing a linkcheck build.
+linkcheck_ignore = [r"https://java.com*", r"https://chocolatey.org*"]
+linkcheck_retries = 3
+
+
+# -- Options for extensions -----------------------------------------------
+
+if dpy_version_info.releaselevel == "final":
+    # final release - versioned docs should be available
+    dpy_docs_url = f"https://discordpy.readthedocs.io/en/v{dpy_version}/"
+else:
+    # alpha release - `latest` version of docs should be used
+    dpy_docs_url = "https://discordpy.readthedocs.io/en/latest/"
+
+# Intersphinx
+intersphinx_mapping = {
+    "python": ("https://docs.python.org/3", None),
+    "dpy": (dpy_docs_url, None),
+    "motor": ("https://motor.readthedocs.io/en/stable/", None),
+    "babel": ("http://babel.pocoo.org/en/stable/", None),
+    "dateutil": ("https://dateutil.readthedocs.io/en/stable/", None),
+}
+
+# Extlinks
+# This allows to create links to d.py docs with
+# :dpy_docs:`link text <site_name.html>`
+extlinks = {
+    "dpy_docs": (f"{dpy_docs_url}/%s", None),
+    "issue": ("https://github.com/Cog-Creators/Red-DiscordBot/issues/%s", "#%s"),
+    "ghuser": ("https://github.com/%s", "@%s"),
+}
+
+# Doctest
+# If this string is non-empty, all blocks with ``>>>`` in them will be
+# tested, not just the ones explicitly marked with ``.. doctest::``
+doctest_test_doctest_blocks = ""
+
+# Autodoc options
+autodoc_default_options = {"show-inheritance": True}
+autodoc_typehints = "none"
+
+
+from docutils import nodes
+from sphinx.transforms import SphinxTransform
+
+
+# d.py's |coro| substitution leaks into our docs because we don't replace some of the docstrings
+class IgnoreCoroSubstitution(SphinxTransform):
+    default_priority = 210
+
+    def apply(self, **kwargs) -> None:
+        for ref in self.document.traverse(nodes.substitution_reference):
+            if ref["refname"] == "coro":
+                ref.replace_self(nodes.Text("", ""))
+
+
+def setup(app):
+    app.add_transform(IgnoreCoroSubstitution)