Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

User:XPDG/sandbox/DivosiLink: Difference between revisions

From Echoes of the Flesh
Content deleted Content added
mNo edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 7: Line 7:


== What DivosiLink stores (cache/log) ==
== What DivosiLink stores (cache/log) ==
DivosiLink keeps a cache of:
DivosiLink keeps a cache of:
* Your Roblox account ID
* Your Roblox account ID
* Your Discord account ID
* Your Discord account ID
Line 13: Line 13:


Every time you verify or your roles get updated, this cache updates too.
Every time you verify or your roles get updated, this cache updates too.

'''Downside:''' you might need to run <code>/verify</code> more times than you would with Bloxlink.


== Quick start ==
== Quick start ==
Line 33: Line 31:
| Everyone
| Everyone
| Shows the connected account + role(s)<br />(Roblox → Discord and Discord → Roblox)
| Shows the connected account + role(s)<br />(Roblox → Discord and Discord → Roblox)
| Is now bound to <code>sc.profile</code>. They will still work though.
| Useful to check what account is linked
|-
|-
| <code>sc.b_update</code><br /><code>/b_update</code>
| <code>sc.b_update</code><br /><code>/b_update</code>
| Karcist+<br />(some other roles also have permission)
| Võlutaar+<br />(some other roles also have permission)
| Update a user or role-group
| Update a user or role-group
|-
|<code>sc.b_man_verify</code>
|Unverified members
|Verify yourself using an older method of adding a "key" to your Roblox about-me
|
|}
|}

== Sub-Discord verification (cache) ==
When you verify in the sub-Discords, they use the DivosiLink cache.

This is needed because the Bloxlink Premium API (used by DivosiLink) is tied to one specific Discord server.

<small>We could buy Premium for all servers, but the current setup works fine.</small>

== DivosiSync (nickname sync) ==
DivosiLink also introduced '''DivosiSync'''.

DivosiSync syncs your nickname from this Discord to all other SC Discords.

It also syncs the Mod and Admin roles (not important for most users).

=== Opt out (don’t sync nickname) ===
Run: <code>sc.divosisync optout</code>


== Troubleshooting ==
== Troubleshooting ==
; Roles not updating / missing roles
; Roles not updating / missing roles
: Make sure you have the correct ranks in the roblox groups. If you do: run <code>/verify</code> again.
: Make sure you have the correct ranks in the ROBLOX groups. If you do: run <code>/verify</code> again.
:
; Still wrong after verifying
; Still wrong after verifying
: Ask staff to troubleshoot.
: Ask staff to troubleshoot.

Latest revision as of 17:12, 3 April 2026

DivosiLink is our Roblox ↔ Discord verification system. It replaces Bloxlink for the SC Discords.

Why we switched

We want to move away from the Bloxlink bot (often offline / a hassle), so everything is now handled by DivosiLink.

What DivosiLink stores (cache/log)

DivosiLink keeps a cache of:

  • Your Roblox account ID
  • Your Discord account ID
  • Which SC groups you’re in + your rank in those groups

Every time you verify or your roles get updated, this cache updates too.

Quick start

  1. Run /verify
  2. Finish the verification steps
  3. Your roles will be applied based on your SC groups/ranks

Commands

Command Who can use it? What it does Notes
sc.verify
/verify
Everyone Verify yourself (link Roblox + Discord, apply roles) Also runs automatically when you join this Discord server
sc.b_whois
/b_whois
Everyone Shows the connected account + role(s)
(Roblox → Discord and Discord → Roblox)
Is now bound to sc.profile. They will still work though.
sc.b_update
/b_update
Võlutaar+
(some other roles also have permission)
Update a user or role-group
sc.b_man_verify Unverified members Verify yourself using an older method of adding a "key" to your Roblox about-me

Troubleshooting

Roles not updating / missing roles
Make sure you have the correct ranks in the ROBLOX groups. If you do: run /verify again.
Still wrong after verifying
Ask staff to troubleshoot.