Skip to content
§ DS2000 — Discord setupRev A

Discord setup

Discord only lets an application control your microphone if you own that application. That is why DS2000 does not ship one: you create your own in Discord's developer portal. It is free, done once, and needs no programming.

Before you start

  • The DS2000 app installed.
  • The Discord desktop app open and signed in.
  • A browser to open the developer portal.
§01 — Create the application in Discord

Create the application in Discord

  1. Open the developer portal

    Go to discord.com/developers/applications with your Discord account and click New Application, top right.

    Screenshot pending
    Discord developer portal with the New Application button
    discord-01-new-application.webp

  2. Name it

    Any name works, for example DS2000. Accept Discord's terms and click Create.

    Screenshot pending
    Create an application dialog with the name DS2000
    discord-02-create.webp

  3. Copy the Client ID

    In the left menu, open OAuth2. Copy the Client ID with the Copy button and keep it for the last step.

    Screenshot pending
    OAuth2 page with the Client ID and the Copy button
    discord-03-client-id.webp

  4. Generate the Client Secret

    On the same page, click Reset Secret and confirm. Discord may ask for your two-factor code. Copy the secret: Discord shows it only once. If you lose it, generate another. Do not share it with anyone.

    Screenshot pending
    A freshly generated Client Secret, blurred, with the Copy button
    discord-04-client-secret.webp

  5. Add the redirect

    Further down, under Redirects, click Add Redirect, type exactly http://localhost/ (with the trailing slash) and click Save Changes. Without it the connection fails.

    Screenshot pending
    Redirects section with http://localhost/ entered and the Save Changes button
    discord-05-redirect.webp
§02 — Connect the DS2000 app

Connect the DS2000 app

  1. Paste the credentials

    In DS2000, open the Discord tab, paste the Client ID and the Client Secret, and click Connect.

    Screenshot pending
    The DS2000 app's Discord tab with both fields filled in
    discord-06-app-credentials.webp

  2. Authorise in Discord

    Discord shows an authorisation request with your application's name. Click Authorize.

    Screenshot pending
    Discord authorisation request for the DS2000 application
    discord-07-authorize.webp

  3. Done

    The Discord tab reads Connected to Discord., and Settings → Connections reads Discord: Connected. Try the keys: mute, deafen and disconnect. The credentials are saved, so this is not repeated.

    Screenshot pending
    The DS2000 app showing Discord: Connected
    discord-08-connected.webp

The Client Secret and the tokens are stored in Windows Credential Manager, on your computer. They are sent to nobody but Discord, and never to Mechardo Labs.

§03 — If something does not work

If something does not work

It stays on “Credentials saved. Waiting for Discord…”

The Discord desktop app has to be running. Open it; DS2000 connects on its own within a few seconds.

I accepted the authorisation but it does not connect

Check that Redirects holds exactly http://localhost/, with the trailing slash, and that the changes were saved.

I lost the Client Secret

Generate another with Reset Secret and paste the new one in DS2000's Discord tab. Leaving the field empty keeps the old one.

I want to unlink the application

In DS2000's Discord tab, Unlink deletes the saved credentials. To delete the application as well, remove it from the developer portal.