Skip to main content

Adding the bot

Getting Utilities into your server and bound to your Roblox group.

Before you start​

You need three things:

  1. Manage Server in the Discord server, or to own it
  2. A rank in the Roblox group you are binding to, high enough that the bot accepts you as its owner
  3. The bot invited, which is not something you do from a listing site. Ask Ben.

The wizard does most of it​

Go to titanite.family, sign in, and open the setup wizard. It walks three steps and takes about five minutes.

Step 1, prove you run the server. Paste the Discord server ID. The site checks the bot is in it and that you hold Manage Server.

Step 2, prove you run the group. Paste the Roblox group ID. The site checks your rank in it.

Step 3, point ranks at roles. The wizard lists every rank in your Roblox group and lets you pick a Discord role for each. It can create the roles for you if they do not exist yet.

Finish and the bind is live. Anyone who verifies from then on gets the right role automatically.

Doing it from Discord instead​

/config link group_id: 1234567 binds the server to a Roblox group.

Then, per rank:

/bind add rank: 100 role: @Sentinel

/bind list shows what you have so far, and /bind sync applies it to everyone already verified.

The wizard is easier. The commands exist for the cases the wizard does not cover, like changing one rank six months later.

Nickname formats​

/bind add takes an optional nickname format, which decides what the bot renames people to:

You writeThey become
{displayName}Ada
[{rankName}] {displayName}[Sentinel] Ada
D-{serial} {displayName}D-4471 Ada
@{username}@ada_l

Discord caps nicknames at 32 characters and cuts the end off, so put anything that must survive at the front. A 40-character display name will eat everything after it.

Group binds​

/bind group add gives a role to anyone in a Roblox group, whatever their rank and whether or not that group is yours.

That is how you give allied-group members a visitor role, or mark everyone from a partner org.

Turning features on and off​

/config module name: events enabled: false switches a whole module off in your server. Its commands stop existing there.

The repair commands stay available no matter what, so a switch can never lock you out of the tools that turn it back on.

It's not working​

"Titanite Utilities isn't in that server." Usually true, occasionally not. If the bot is plainly sitting in your member list, the site is failing to check and reporting it as an absence. Tell Ben, and say which server ID you used.

"You need Manage Server to bind it." You hold the permission through a role the bot cannot see, or you are checking a different server than you think. Server owners always pass.

"This server is already bound to another group." Moving a server between groups is a migration rather than a setting, because every existing member's roles have to move with it. Ask in Discord.

The wizard finished but nobody has roles. Run /bind sync. The bind applies to people who verify after it; existing members need one pass to catch up.

A rank has no role option in the wizard. The wizard reads live ranks from Roblox. A rank added after you opened the page will not be there. Reload it.