1 Discord
Miko edited this page 2026-10-31 00:30:48 +00:00

Discord

Optional. EveSynapse can connect a user's Discord account to their EveSynapse account, send their notifications to them on Discord, and, through one bot that can be added to any number of servers, give roles there and post new ops in a channel. It only ever sends to Discord; it reads nothing from any channel.

What the bot does in a server is not part of the install's settings. It is set on the site, per server, by the directors of the corporation or alliance the server belongs to.

Set the bot up (once, by whoever runs the site)

  1. At discord.com/developers/applications, create an application.

  2. On General Information, copy the Application ID. That is the client id.

  3. Under OAuth2, press Reset Secret and copy the Client Secret, and add this redirect, with your site's address: https://your.site/discord/callback.

  4. Under Bot, press Reset Token and copy the token. Switch on the Server Members Intent if any server is to use removals (below). No other privileged intent is needed. Leave Public Bot on if other corporations and alliances are to add it to their servers.

  5. Add to the server's .env and restart:

    DISCORD_CLIENT_ID=<the Application ID>
    DISCORD_CLIENT_SECRET=...
    DISCORD_BOT_TOKEN=...
    

Treat the secret and the token like passwords. With only the first two set, Connect Discord works and there is no bot.

Add the bot to a server

Who may: an account with a character that holds the Director role in the corporation (a CEO does), for that corporation's servers; and a Director of the alliance's executor corporation, for the alliance's. That character's link to EVE has to be working.

  1. On the site: bell, then Settings, then Discord, then Set up your corporation's or alliance's Discord server, then Add the bot to a server.

  2. Discord asks which server, and shows what the bot may do there: give roles, send messages, add members, and kick members (used only if removals are switched on). Only someone who can manage that server can add a bot to it.

  3. In that Discord server's Roles list, drag the bot's own role above the roles it is to give. Discord lets a bot manage only the roles below its own.

  4. Back on the site, write that server's role rules: "give these people this role", as many as there are roles to give. A member gets every role they qualify for. "These people" can be:

    • everyone there who has connected EveSynapse,
    • members of the corporation or alliance,
    • (alliance servers) members of one of its corporations,
    • the CEO,
    • holders of an in-game corporation role,
    • a group the directors keep themselves (below).

    Then, if wanted, pick the channel new ops are posted in.

Adding members automatically. Someone with a character in the corporation (or alliance) who has connected Discord is put in its server by the bot, with their roles, without needing an invite, on the worker's next pass after they qualify. Only people who belong are added; a rule that gives a role to "everyone connected" adds nobody. Each person agrees to it on Discord when they connect. Untick the box on the server's settings to switch it off.

Removals (off unless a server's directors switch it on). With it on, the bot removes from the server everyone who is owed no role by the server's rules: someone whose character left, whose account or Discord connection went, and also anyone who never connected EveSynapse. People are kicked, not banned, a few at a time, and can come back with an invite. Never removed: bots, the server's owner, anyone in their first 24 hours in the server, and holders of roles the directors tick as protected. A server with no rules removes nobody, and removals cannot be switched on for one. Press Show who would be removed first: it lists them and changes nothing.

Groups (under Groups on the site) are lists of characters that a corporation's or alliance's directors keep by hand: a special interest group, the fleet commanders, a logistics wing. A director makes a group, ticks the characters in it, and adds a rule giving the group a role; the bot does the rest.

Which channels a role can open is set on the same page, under Channels: pick a channel (or a category, or a voice channel) and tick the roles that may open it. The bot keeps it private to those roles. Saving a channel again replaces its list; saving it with nothing ticked stops the bot managing it.

Ops in an alliance's server. A corporation's ops are posted in its own servers. They are posted in its alliance's server only after a Director of that corporation ticks the box for it.

Removing a server first takes back the roles the bot gave there; press Remove again a few minutes later to finish, and the bot leaves.

What users do

On bell, then Settings, under Discord: Connect Discord and approve on Discord's page. Within a few minutes they are in their corporation's server and have their roles in every server that uses EveSynapse; Check my roles now does it at once. To get notifications there, tick "Send my notifications to me on Discord" and press Send a test message. Disconnect Discord removes the link and takes back the roles EveSynapse gave.

What the roles mean, and what they do not

  • A role follows the last sync: it is given when the connected account has a character, with a working EVE link, that the last sync saw in the corporation, as its CEO, holding the in-game role, or in the group, and taken away when that stops being true, each role on its own.
  • Roles are taken back when the account goes: deleting the EveSynapse account, disconnecting Discord, connecting a different Discord account, a character leaving, or its EVE access being revoked or expiring all remove them.
  • In a server the bot gives and takes only the roles named in that server's rules. Every other role is left as it is.
  • A role removed by hand from someone who still qualifies comes back within six hours.
  • It shows that someone controls a character in the corporation. It does not stop a member sharing their Discord account, and it is not a check of in-game roles.
  • If the bot is kicked from a server by hand, the roles it gave there stay until someone removes them: it can no longer act there.