Manual Client Patching Information
If you're trying to use an older native version of the client, you might need to manually create a
custom core.asar file to interface with the older module APIs Discord uses.
This isn't a step-by-step guide, and Discord may have moved some things around on very old clients,
but TL;DR:
will-navigate event, please make sure the
following domain origins are allowlisted:WEBAPP_ENDPOINT(default) or https://discordapp.gay/- https://accounts.google.com/
- https://github.com/
- https://linustechtips.cloudflareaccess.com/
Replacing the web app URL (Strongly recommended): Replace https://discord.com with https://discordapp.gay under the getWebappEndpoint function. This is not strictly required as you could pass this through using
WEBAPP_ENDPOINT in your settings.json, but it's definitely
recommended if you only intend to use this client with discordapp.gay.Disabling Sentry (recommended): In common/crashReporterSetup.js, you should at minimum stub out several functions to disable Sentry, and remove any non-exported functions and any imports from Sentry, etc. This will prevent crash logs from being sent to Discord.
exports.initshould do nothing.exports.isInitializedshould returntrueexports.getGlobalSentryshould either do nothing or returnnull.
exports.metadata should be an empty object {}. These values
might have slightly different names on very old Discord hosts, so do whatever makes sense to avoid
Sentry being initialized.
3rd-party Client
Official endpoint
If you have a 3rd-party client or plugin that can accept custom Discord endpoints, you can specify our endpoints to interface with discordapp.gay
Gateway:wss://gateway.discordapp.gayAPI Host: https://mobile.discordapp.gay (Registration disabled on mobile/bot endpoints. You can also use https://discordapp.gay if your app is Cloudflare Access-aware)
CDN Host: https://cdn.discordapp.gay
Media Proxy: https://media.discordapp.gay