Bots on Blisscord

Blisscord speaks Discord's own API: REST v9 and v10, the gateway, interactions, OAuth2 and voice. A bot written for Discord runs on Blisscord unchanged once its library is pointed at Blisscord's hosts instead of Discord's. You do not rewrite your bot, you reconfigure it.

Use Discord's documentation

Everything about how the API works (objects, endpoints, gateway events, intents, permissions, interactions, rate limits) is documented by Discord, and that is the reference to build against:

These pages only cover what is specific to Blisscord: which hosts to use, how to configure the common libraries, and the handful of places Blisscord behaves differently.

What you change

On DiscordOn Blisscord
REST APIhttps://discord.com/api/v10https://discord.community/api/v10 (v9 also served; no version means v9)
Gatewayfrom GET /gateway/botthe same call answers wss://gateway.discord.community
CDN (avatars, icons, attachments)https://cdn.discordapp.comhttps://cdn.discord.community
OAuth2 authorize pagehttps://discord.com/oauth2/authorizehttps://discord.community/oauth2/authorize
OAuth2 tokenhttps://discord.com/api/oauth2/tokenhttps://discord.community/api/oauth2/token
Developer portalhttps://discord.com/developers/applicationsdevelopers.discord.community
Bot tokenfrom Discord's portalfrom Blisscord's portal; a Discord token does not work here, and a Blisscord token does not work on Discord

Everything else (paths, JSON shapes, gateway opcodes, intents, permission bits, error codes, rate limit headers) is Discord's.

Next

  1. Getting started: create the application, get a token, invite the bot.
  2. Configuring your library: discord.js, discord.py, JDA, serenity, Eris and Athena, Lavalink, and anything else.
  3. Differences from Discord: the short list of things that behave differently here.
  4. Keeping your token off Discord: make sure nothing in your bot still calls Discord's hosts.

Building a chat surface into your own product rather than a bot? See chat integrations.