Bot Profile

Nexus or Professional: run Cyndrix as your own Discord bot — members see your bot's name, avatar, and slash commands, not Cyndrix.

What it does

On Nexus, Bot Profile lets this server run under a Discord bot you created. Cyndrix still does the work — tickets, automod, levels, everything you already configured — but members see your bot's username, avatar, bio and slash-command list. The Cyndrix bot leaves once yours is online, so there is only one bot in the server.

You do not recode anything. You make a Discord application, paste its bot token only (never the client secret), invite that bot here with Administrator, then Enable. Settings you already have stay. A second Nexus server does the same thing independently — each server has its own token and its own bot.

What you need first

• This server on Nexus ($7.99/mo), or covered by a Professional slot ($39.99/mo for 10 servers). Bot Profile is not on Premium or Ultimate.
• You must be the server owner. Admins can use the rest of the dashboard; they cannot bind a bot.
• A few minutes on the Discord Developer Portal. The switches below are the whole job — Code Grant and Public Bot decide whether the invite works; the two intents decide whether we can log in.

Open it from the dashboard too: Dashboard → Admin → Bot Profile. The five steps on that page match this guide.

Make the Discord application

1. Developer Portal → New Application. Name it whatever members should see (your community name is typical). Create.
2. Left sidebar → Bot. If there is no bot user yet, click Add Bot.
3. Leave Public Bot on so the dashboard invite link works.
4. Leave Requires OAuth2 Code Grant off. If this is on, Discord refuses a normal bot invite even with a perfect token. That is the most common reason the invite "just fails".
5. Under Privileged Gateway Intents, turn on Server Members Intent and Message Content Intent. Save Changes. Leave Presence off unless you know you need it.
6. On the same Bot tab, Reset Token and copy it. Treat it like a password. We encrypt it and never show it again after you save.

Do not paste the client secret, the application ID, or an OAuth redirect URL. Only the bot token. Resetting the token in Discord later will kick this profile offline until you paste the new one.

Paste the token and invite

1. Dashboard → Admin → Bot Profile → step 3. Paste the token → Validate & save.
2. If the token is good, step 4 shows Invite your bot. That link is locked to this server and asks for Administrator. Do not send it to a different server — it will not work there.
3. Accept the invite. You should see your new bot join the member list. Then come back and hit Recheck membership if the page still says it is waiting.

If Discord says the invite failed, go back to the Bot tab and confirm Requires OAuth2 Code Grant is off, then try the same link again. Public Bot must stay on. You do not need to paste the token a second time.

Enable — what happens, in order

Saving the token is not going live. Going live starts after the bot is in this server — often on its own a few seconds after you accept the invite, or when you press Enable if Status is still sitting idle. Recheck membership if the page still says to invite it.

Once we actually log it in, this is the sequence — it can take a minute:

1. We start a runner logged in as your bot (not as Cyndrix).
2. Slash commands are deployed on this server under that bot. Members will type / and see your bot's name, not Cyndrix.
3. Only after that bot is actually in this server and commands are up does Cyndrix leave. We will not kick Cyndrix first. If yours is not in yet, we wait — use the invite link, then Recheck membership. Status will say to invite the bot first; the badge reads WAITING FOR INVITE.
4. From then on there is one bot here. New messages, panels, and slash commands come from yours. The dashboard talks to Discord as that bot too, so the server picker should say Open Dashboard, not Invite.

Do not invite Cyndrix back while this is Enabled and online. If someone does, Cyndrix will leave again. That is on purpose: two bots at once would fight over the same panels.

After it is online

• Rebuild panels. Ticket, verify, reaction-role, giveaway, trap, and join-to-create (temp voice) buttons that Cyndrix posted cannot be pressed anymore — Discord will not let a different bot edit those messages. Hit Rebuild panels on Bot Profile. That posts fresh copies as your bot and deletes the dead ones. Do this once after the first takeover, and again if you later publish a panel that still looks stuck.
• Look & listening. PFP, banner, name, and bio go live on Discord immediately. Recommended: PFP 512 × 512 (shown as a circle), banner 680 × 240. PNG, JPG, WebP, or GIF. A large image opens an adjuster — drag and zoom, then save the crop. Cropping a GIF makes a still; to keep it moving, use Keep animated GIF (under 2 MB). "Listening to …" is saved now and shows under the name once the runner is connected.
• Everything else you already set — automod, welcome, autorole, economy — keeps working. Autorole applies on the next joins, once this bot is online. You do not reconfigure modules from scratch.

There are a small number of Bot Profile runners at a time. If the badge says WAITLISTED, your token is fine; you are in a short queue and it starts when a slot opens. You do not paste the token again.

Disable, unbind, kick — what each one actually does

These three get mixed up. They are not the same.

• Disable — stops the runner and keeps the encrypted token. Re-invite Cyndrix (the button on step 5) so the server is not empty. Your custom bot may still sit in the member list until you kick it; it will not be driven. Press Enable later and the same bot comes back without pasting the token again.
• Unbind & delete token — wipes the token from our side and stops the runner. We do not kick your Discord bot for you; it stays in the server until you remove it, so kick it yourself if you do not want it sitting there. Re-invite Cyndrix. Module settings stay. To use Bot Profile again you paste a new token and walk the steps.
• Someone kicks your custom bot by mistake, while it is still Enabled. Do not invite Cyndrix. Cyndrix will not stay — Enable is still on, so it leaves. Use Invite your bot and bring the same custom bot back. Settings survive. Buttons that bot posted still work if the messages are still there. Anything Cyndrix posted, or anything that got deleted, needs Rebuild. Autorole starts applying again on the next joins once it is online.

If you Unbind and then want Cyndrix: invite Cyndrix, not the custom bot. If you kicked the custom bot and still want Bot Profile: invite the custom bot, not Cyndrix.

When something does not work

• Invite fails / Discord error screen — Bot tab → turn Requires OAuth2 Code Grant off. Public Bot on. Try the same invite link. The token was probably already saved; you do not need to Validate again.
• Validate rejects the token — wrong paste (client secret, extra space), or the two privileged intents are off. Reset Token on the Bot tab if you are unsure you copied the current one.
• Badge says WAITING FOR INVITE (or Status tells you to invite the bot first) — the bot is not in this server yet. Use the invite link, then Recheck membership. We will not make Cyndrix leave until yours is actually here.
• Dashboard picker says Invite instead of Open Dashboard — wait until the badge says ONLINE, then refresh. If you just invited the custom bot, give it a minute.
• Ticket / reaction-role / verify buttons do nothing — those messages were posted by Cyndrix. Rebuild panels. If you already rebuilt and a module still looks wrong, open that module and Publish again.
• You invited Cyndrix "to help" while Bot Profile is Enabled — it will leave. That is the solo-identity rule. Either Disable first (then invite Cyndrix), or leave the custom bot running.

The bot token is stored encrypted, this server only, and never shown again after you save. Unbind deletes it. Do not drop it in a ticket or a chat — if it leaks, Reset Token in the Developer Portal and paste the new one here.

Commands

This module has no commands — it's configured entirely from the dashboard.

Related