Discord roles, sync and "Suspended member"

In short. With the Discord bot set up, each forum group can be linked to a Discord role. Giving the group gives the role, removing the group removes the role. The Suspended member setting decides what happens to roles during a suspension.

Link a group to a role #

1. Set up the bot: see Connect Discord.
2. Administration → Configuration → Discord connection, Discord roles for groups section.
3. For each group, pick the role from your server's role list.
4. Save.

A role shown as "⚠ role not found" was deleted on Discord: pick another one. A role "(managed by an integration)" cannot be assigned. If a role does not arrive, remember a bot can only give roles placed below its own: see Missing Discord permission; Discord's official help explains the hierarchy: Discord Roles and Permissions.

A role that is too high is refused up front #

A role the bot will not be able to give (placed above its own or at the same rank, or managed by an integration) is greyed out in the list, with the reason. Picking it anyway (stale form) is refused when saving: nothing is written. If Discord does not answer, the save still goes through, with a warning. If you later move roles in Discord, the mappings that became impossible show in red in Administration → Configuration → Discord connection, under Mappings Discord will refuse, with an Open in the Discord app button to the screen where you fix them. The same rule applies to the MDT rank roles (see below).

When roles move #

The Administration → Configuration → Discord connection banner shows the number of sync failures. A member's page shows the latest Discord calls (the sync log is kept for 90 days).

• A role the member holds through another group is never removed. Removing a group, or changing rank, does not strip a role that another of their groups gives them.
• A role that Discord refuses to remove is reported on screen instead of a misleading "done", and the refusal is recorded in Administration → Errors.
• The role menu marks power roles (Administrator, Ban, Manage roles…). An application that grants a group linked to one of them can only be accepted by an administrator, like a power group of the site.

When Discord is the source of truth: "Sync Discord → Agora" #

By default, Agora pushes: giving the group gives the role. For a group whose roles you already manage in Discord (a whitelist role given by another bot, a subscriber role…), you can reverse the direction, group by group. Below the group's mapping, the Sync Discord → Agora box is unticked by default. Ticked:

• a member who receives that role on Discord is added to the group on the site; if they lose it (or leave the server), they are removed from the group;
• Agora no longer pushes anything to Discord for that group: the member's page shows "managed by Discord";
• the role's rank no longer matters (the bot never assigns it, it listens to it);
• each addition or removal is written to the administration log, author Discord.

Never for a power group: the box is greyed out (and refused when saving) for admin, moderateur, the groups of the Staff page, groups that carry rights and application-examiner groups. MDT ranks are not concerned: they come from the game.

How it works. Agora listens to Discord through an open connection only when at least one box is ticked (no periodic task), and applies the events to accounts linked by their Discord ID. A member without an account is aligned at their first sign-in. At startup and after any reconnection that was not resumed, Agora re-reads the linked members' roles once to catch a missed event; the Resync button does the same read on demand. The last re-read date only appears if Discord was really read: with no date, nothing has been re-read yet (for example, the connection to Discord is not established).

Two modes (the screen says which one is active):

To go from fallback to full mode: enable Server Members Intent, then click Resync. If it does not work: Missing Discord permission, cause 5.

Discord roles of ranks (MDT) #

In MDT → Settings, the Service Discord block can give one role per job rank. Agora sets the role of the rank held and removes the other rank roles of that job:

• when the MDT is opened (at most every 10 minutes per member);
• as soon as the game announces a job or rank change (hire, promotion, leaving), even if the member no longer has any MDT department: someone who leaves the police loses their rank role without opening anything. The announced rank needs the up-to-date resource; an older resource only reports the job change (see Update the resource).

Safety rules:

• A rank role of a job the member never held (set by hand) is not removed by this change.
• Roles held through a forum group are never removed.
• The jobs of all their characters count: the role stays as long as one of their characters still holds the rank. With multi-job (Qbox), switching the active job removes nothing; only jobs really left count.
• A suspended member with the "remove their roles" option also loses their rank roles; they come back on lifting.

The "Suspended member" setting #

Administration → Configuration → Discord connection, Suspended member block:

For the connection refusal:

• you need resource 1.9.8 or newer;
• the player is recognised by their game link (their account linked with a code);
• they see "Your community account is suspended until …: connection to the game server is refused during the suspension", with the reason;
• if Agora does not answer, the connection is let through.

Every change of this setting is written to the administration log.