Rest assured, everything remains fully functional. We are transitioning to a new bot, but both the old and new bots will continue to operate smoothly for the foreseeable future. For more details on why we're making this switch, please read the section below.
If you're not a server owner, admin, or don’t use our bot in a private server, this announcement likely won’t affect you, and can be disregarded.
For server owners and admins currently using our original (old) bot, we encourage you to invite the new, Discord-verified bot using this link: https://discord.com/oauth2/authorize?client_id=643262217428533250.
There are no changes to the bot's functionality. Once the new bot is added to your server, the old bot should automatically leave after confirming a successful transition. It will also send a parting message to let you know everything is complete.
Additionally, the original bot's bio and status will be updated to inform users to invite the new bot. If prompted or when a command is run, the old bot will send a one-time informational message, recommending to invite the new bot in the first channel where it has permission to send messages. In the future, this reminder may be sent once a week as we encourage all 5,000 servers (especially the most active ones) to make the switch to the new bot.
The transition to the new bot is quick and seamless. When a server with the original (old) bot invites the new bot, the old bot will automatically leave after confirming the successful invite with a message. This message will also include a friendly reminder to assign the new bot the same roles and permissions the old bot had. All existing server settings, such as admin roles/permissions and channel whitelists, will carry over and continue to function with the new bot.
We want to reassure you that there are no issues. Both bots maintain the highest security standards, and we will continue to follow strict safety protocols as always. Servers with the old bot may receive periodic reminders to invite the new bot. For more insight into why we're transitioning to a new bot, please refer to the section below.
New Verified Bot Invite Link: https://discord.com/oauth2/authorize?client_id=643262217428533250
We've been planning this change for some time and used the opportunity to apply for Discord's verification badge, which has already been granted to the new bot. The original (old) bot will lose its verification badge and status this November, as we're unable to renew its verification for reasons explained in the section below.
Some information regarding our bots:
Our latest new bot has the username NVST.ly#2640 with a Discord ID of 643262217428533250
Our original (old) bot has the username NVST.ly#8695 with a Discord ID of 901245095502819358
Why we are switching to a new bot & Discord's refusal to resolve it all
For nearly two years, after a dozen attempts to communicate with Discord's developer support, we've been forced to make a drastic change that we would have preferred to avoid. My (rich's) original Discord account, which held ownership of the Discord Developer Team managing the original NVSTly bot (along with others), was deleted some years ago. Unfortunately, the team ownership was never transferred to the next account in line—despite there being another account on the team, which would have been the logical course of action.
Recent updates from Discord have compounded this issue, leaving us in a difficult position for quite some time. Now, with the latest developments, we've reached the point where starting over with a new bot is our only option.
As you can see, the Developer Team Owner account has been deleted- the root of all this ruckus.
Discord has introduced several updates related to app and bot development, including changes to how bot verification applications are processed. Now, only the bot owner or accounts holding ownership of a developer team are eligible to apply for bot verification. This wasn't an issue for us initially, as our bot was verified long before these changes. However, a recent update now requires all verified bots to renew their status every 12 months. Since the ownership account on our developer team was deleted, it is now impossible for us to renew our bot’s verification—at least from our end.
Since the developer team ownership account was deleted, we’ve made multiple requests to Discord to transfer ownership to the only other account on the team. Why this isn't done automatically is beyond reason and lacks logical sense. We also proposed an alternative: transferring our original (old) verified bot to a team with an active ownership account. We've stressed the severity of the situation to them multiple times, explaining that we won't be able to renew the bot’s verification status this November when it's due.
Despite this, our requests were rejected, and we were advised to create a new developer team and bot. We tried reasoning with them, pointing out that it would take countless hours to get the 5,000 servers currently using our old bot to invite the new one. We also highlighted that asking servers to invite a new bot could seem suspicious, causing unnecessary concern. This situation is not only a major inconvenience for our team, but also for the servers and users who actively rely on our bot.
So here we are, forced to start over with a new bot. Discord support has been unhelpful in assisting us with transferring the developer team ownership or moving our important bot to a different team. Either of these actions would be an ideal solution that wouldn’t take more than a few minutes of their time, yet it would save us countless hours, as well as the time and energy of server owners and admins, as we reach out to nearly 5,000 servers to inform them about inviting our new bot.
Conclusion
While it’s unfortunate, we refuse to let this situation cripple us. This November, our original bot will lose its verification badge, meaning no new servers will be able to add it. However, our new bot has already passed Discord's verification and will be the primary bot listed in our documentation, bot listing platforms, and Discord's app directory.
Although it feels like we're starting over, we understand that not all 5,000 servers will invite the new bot—many may be inactive, test servers, or otherwise. Our primary goal is to encourage our most active servers to migrate to the new bot. Over time, as we continue to grow, we’re confident we will surpass the 5,000 server milestone with the new bot.
The original bot will remain operational, with only cosmetic changes such as its status and bio, which will inform servers about inviting the new bot. It will also periodically remind servers of this seamless transition when prompted or when a command is sent.
FAQs
I'm a server owner/admin, or use the bot in a private server. What do I need to do?
Simply invite the new (verified) bot using this invite link: https://discord.com/oauth2/authorize?client_id=643262217428533250
Once added, the old bot will automatically leave the server after sending a message in the first channel where it has permission to post. This message will confirm that the new bot has been successfully added and remind you to grant it the same roles and permissions as the old bot. All existing /setup settings will continue to work seamlessly during this transition. If you have any issues or questions, please reach out to us in the #help channel within our Discord community.
I just use a bot in a server I'm in, do I need to do anything?
No, you don’t need to take any action. Both the old and new bots will operate as intended. When the server you're in invites the new bot, the old bot will automatically leave, and nothing will change for you. You can remind the server admins or staff to invite the new bot if you'd like, but the old bot will also send friendly reminders periodically.
Will Discord DM notifications be effected at all?
No, your DM notifications will not be affected. If you're in multiple servers—some with the old bot and some with the new bot—only the new bot will send DM notifications. If none of the servers you’re in have added the new bot yet, you will continue to receive DM notifications from the original (old) bot.
Keep in mind that if you're in a server with the new bot but have DMs disabled for that server, you won't receive any notifications, even from the old bot in a server where DMs are enabled. We are looking into a solution for this, but in the meantime, we encourage you to ask your favorite servers using our bot to invite the new bot.
I see the new bot has a Store button, what is this?
Discord has introduced many features for developers over the past few years. Unfortunately, some of these features were unavailable to us due to the deletion of the ownership account on our developer team, which is required for accessing new developer tools and features.
The Store button is part of Discord's new app/bot monetization feature. For now, feel free to disregard this button, as we have not yet set up any subscriptions or items for purchase. However, be sure to check back often or stay updated on our changelogs, as we plan to utilize this store feature to allow users to subscribe to PRO Membership directly from Discord or purchase consumable items to personalize their Dashboard. Options may include overlay designs, colors, username colors, avatar design overlays, animations, and much more that we’re currently brainstorming!
Is there any issues or problems I should know about? If so, what should I do?
We will be closely monitoring both bots and will continue to implement any necessary features to ensure they operate in tandem without conflicts. If you encounter any bugs, issues, or anything unusual, please reach out to us directly. You can use the #help channel or send a DM to our support bot in our Discord community.
My friend or acquaintance works for Discord. Should I ask if they can help with transferring ownership of the developer team or the original bot?
Well, aren’t you an angel! It’s still early enough for us to benefit if Discord support could assist by either transferring ownership of our developer team to the only remaining account on the team or by transferring the original bot to another team or to that sole account as a personal bot. From there, we could manage the transfer to a new developer team ourselves.
If you happen to know a Discord employee and would be kind enough to pass along our request, we’d be extremely grateful. We’re confident that if even one Discord employee could spare a few minutes to discuss this with us on a personal level, they’d see how logical and convenient it would be to transfer either the team ownership or the bot itself. It would save us countless hours, headaches, and the unnecessary hassle of starting over with a new bot.
