Custom roles
The role a member draws for themselves: a name, a colour, and the slot the server opens for them.
In short
A custom role belongs to one member and to them alone. The server decides how many it opens and for whom; the member decides the name and the colour.
A member owns 1 custom role, never two. They claim it, name it, colour it, and may lend it to other members without those members ever owning it.
Slots are counted for the whole server, not per member. A fresh server opens 0: until that number is raised, nobody claims anything. The ceiling is 250.
The server may set up to three entry conditions: an EnderBot level, a server level, a list of roles. They read as OR, so meeting a single one is enough.
The life of a role fits in eight moves: claim it, name it, colour it, lend it, take it back, give it up.
Six levers for the whole server
Two doors set the same levers. Nothing is open by default: a fresh server carries 0 slot and no anchor.
| Lever | What it takes | Default | What it changes |
|---|---|---|---|
| Reference role | A role of the server | None | Every created role is filed right below it. While it is missing, no claim goes through. |
| Open slots | From 1 to 250 | 0 | The number of live roles on the server, all members together. |
| Prefix | Free text | None | Glued in front of every name; prefix included, the whole stays under 100 characters. |
| EnderBot level | A player level | None | The game level to reach, the one the account carries rather than the server. |
| Server level | A local tier | None | The tier of the local ladder, the one messages and voice climb. |
| Required roles | A list of roles | Empty | Wearing a single one of the listed roles opens the door; the list never stacks, it adds itself to the two other conditions. |
- The system stays off until
>customrole enableis typed: the six levers can be set beforehand, they only act once the switch is open.
What the claim checks
A claim walks six steps in this order: the first one that refuses stops everything, and nothing is created.
- >customrole enable has been typed
- A reference role is set
- You own no role here
- Live roles sit under the open slots
- Your EnderBot or server level reaches the tier
- Or you wear one of the listed roles
- The Discord role is created
- It is filed under the anchor, then comes to you
A server that sets no condition leaves the condition gate open: only the anchor and the free slot are left to pass.
A member who leaves the server loses their role: the Discord role is deleted, its slot reopens, and the loans they had granted fall with it.
Eight moves, a single counter
One command, >customrole, followed by the word below. Every gesture shares the same pace: 3 actions per 2 minutes, per member.
- A colour is written in hexadecimal (
#7c3aed,#7ae) or by name: 141 CSS names are recognised.
The screen, for real
What >customrole information sends back: the state of the system, your role with its prefix kept under 100 characters, and the moves left to you.
Custom roles
- The title
The name of the system, never the name of your role.
- The server state
What the server has set: the switch, the anchor, the prefix, the conditions in place.
- Your role
The full name, server prefix included, and the colour it carries.
- The counter
The slots taken out of those the server opened, never more than 250.
- The dashboard button
A single link button, the only control the screen carries: the rest of the work happens on the web page.
- The screen only offers the moves your state allows: with no role it offers to claim, with a role it offers to name and colour it.
The commands
Manage custom roles in this server · servers only
<user>The user to grant the role to
abandoncolordisableenablenamerevokeunclaim