Yes. The dedicated bot add-on ($7/month, on Pro) runs OnyxBot under a bot you own: your name, your avatar, your presence in the member list. See what Pro costs.
What it is
Instead of the shared OnyxBot bot, your server gets its own dedicated instance signed in with your bot's token. Members see your brand everywhere: on panels, in tickets, on AI answers.
What you need
A Discord application you create in the Discord developer portal (five minutes, free). You provide its token in the dashboard and OnyxBot handles the rest, including keeping your instance online.
Keep that token for OnyxBot only. Discord sends every button click to every program signed in with a bot's token and keeps only the first answer, so if anything else runs on it (txAdmin, another bot, a hosting panel), your ticket buttons start replying with that program's messages instead of OnyxBot's. If you need another bot, give it its own application.
Moving over from the shared bot? OnyxBot moves your panels and open tickets to your bot once it is online. Keep the shared bot in the server until then, then kick it. The section below on what happens when the bot changes has the details.
Changing the token or the bot later
Open Configuration. The Your bot card shows which bot OnyxBot runs as, with two buttons:
- Replace token: after you press Reset Token in the Discord Developer Portal, paste the new token here. OnyxBot checks it, restarts your bot with it and tells you when it is back online. Nothing else changes.
- Use a different bot: run OnyxBot as another application. The new bot has to join your server, so Discord asks you to authorize it. OnyxBot moves your panels and open tickets to it once it is online; kick the old bot after that.
Both check that Message Content Intent is on and that no Interactions Endpoint URL is set on the application before saving, since either one stops OnyxBot from working. Changing the bot needs the Manage servers permission on your team.
What happens to panels and open tickets when the bot changes
Discord ties every button to the bot that posted it, and a ticket channel is private to the bot that opened it, so OnyxBot moves both across whenever your server changes bots: from the shared bot to your own, from one of your bots to another, or back to the shared bot if the add-on ends (as long as the shared bot is still in your server).
- Open tickets. The bot that was serving your server lets the new one into every open ticket. That is why the old bot has to stay in the server until the new one is online.
- Panels. The new bot republishes each panel and removes the old one. If it cannot post in a panel's channel, the Panels page under Tickets says why.
- Ticket buttons. In every open ticket, the new bot re-posts the opening message and the staff briefing so their buttons work, and removes the old copies. Those two messages move to the bottom of the ticket. Nobody is pinged again.
Buttons on AI answers the old bot posted stop working; members can still reply in the ticket. And if the old bot's token no longer works (you reset it before switching), it cannot let the new bot in: tickets it opened stay hidden from the new bot until you add the new bot to those channels in Discord.
What changes functionally
Nothing. Same features, same dashboard, same knowledge. It is purely identity, plus the isolation of running as your own instance.