Ranks and points
Moving people up, and letting the bot do it for you.
Ranking somebody by hand
/promote user: @Ada
/demote user: @Ada
/setrank user: @Ada rank: Sentinel
/promote and /demote move one step. /setrank goes straight to a named
rank, so it is the one for a jump or a correction.
All three write the change to Roblox as well as Discord. The person's roles and nickname follow within seconds.
/promote and /demote sit at HR. /setrank is Management, because skipping
ranks is a different decision from moving somebody one step.
Points
/points give user: @Ada amount: 25 reason: hosted a patrol
/points remove user: @Ada amount: 10 reason: correction
/points check user: @Ada
/points history user: @Ada
Points live per group, so somebody with 300 points in one group starts at zero
in another. /leaderboard shows the standings for the server you run it in.
Always give a reason. /points history is the only record of why somebody has
what they have, and "no reason given" six months later helps nobody.
Auto-rank
Give a rank a points threshold and the bot promotes people who cross it, without anybody pressing anything.
Set thresholds on the dashboard under your group's settings. A rank with no threshold is never reached automatically, which is how you stop auto-rank running past the point where a human should be deciding.
Two ways up, in one group
Each rank chooses how people reach it:
| Mode | How somebody gets there |
|---|---|
| Points | They cross the threshold and the bot promotes them |
| Application | They apply, somebody approves it |
You set this per rank, not per group, so one group can run points up to Level 2 and applications above it. That is the usual shape: let the bot handle the early grind and put a person in front of the ranks that matter.
Rank history
Every rank change is recorded with why it happened: a promotion somebody ran, an application approval, a points threshold, or a drift correction where the bot found Roblox and Discord disagreeing and believed Roblox.
/record user: @Ada shows their standing record. The dashboard shows the same
thing with more room.
When Roblox and Discord disagree
Roblox wins. Somebody promoted inside the Roblox group without touching Discord still gets their Discord role, because the bot re-reads live ranks in the background and corrects what it finds.
That pass walks everybody continuously rather than all at once, so it takes a
while to reach any one person. /update skips the queue for one person.
It's not working
Somebody was promoted in Roblox but has the old role in Discord.
Run /update user: @them. If it still does not move, the group has no binding
for their new rank.
Auto-rank has not fired for somebody over the threshold. Check the rank is in points mode rather than application mode. A rank set to applications ignores points on purpose.
Points went to the wrong group.
Points are scoped to the group of the server you ran the command in. Run it
again in the right server, and take the wrong ones back off with
/points remove.
/setrank says the rank does not exist.
It matches on rank name or short name as configured, not on whatever Roblox
displays. /config view lists what the bot thinks the ranks are.
A promotion worked in Discord but not in Roblox. The bot needs an Open Cloud key for that group to write ranks back to Roblox. Without one it can read ranks but not set them. Ask Ben, since minting that key is not self-serve.