"Public Bot" feature #1498
-
Hi, when updating the bot, I got the following message: [ERROR] [JMusicBot]: JMusicBot cannot be run on this Discord bot: "Public Bot" is enabled. Using JMusicBot as a public bot is not supported. Please disable it in the Developer Dashboard. I was wondering why this is the case? I know how to disable it, but I was wondering why public bot is not supported. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 10 replies
-
I was wondering the same. I used this bot because people could invite and use it without them needing to give me administrative privileges. Why did it need removing? |
Beta Was this translation helpful? Give feedback.
-
I'm currently wondering the same thing. Why would this feature be removed? I doubt it's necessary for the operation of the program — wasn't it perfectly able to operate in public mode before? |
Beta Was this translation helpful? Give feedback.
-
Same question, is this a setting we need to change or do I have to revert? |
Beta Was this translation helpful? Give feedback.
-
It seems to be a result of PR #1486, and the reasoning is explained in #568. Notably, because the bot can't shard, it will completely stop working once it hits ~2500 guilds (to my understanding). |
Beta Was this translation helpful? Give feedback.
-
JMusicBot's internals are not designed around nor optimized for being a public bot on a lot of servers. The setup instructions have always instructed you to disable the bot from being public. Version 0.4.0 is just the first version to actually enforce this; this is one of several warnings that were added to help alleviate issues that people frequently run into when they haven't set the bot up correctly on the developer dashboard. It is very likely that the majority of users running into this error message didn't realize that their developer dashboard settings were incorrect; there is a long history of people needing support because someone added their bot without their permission and needed help removing it from other servers. Unverified bots are also hard-capped at 100 servers. When a bot hits that, its invite status effectually becomes "locked," where it can't be added to any new servers (even if the bot is removed from some to put it back below 100). Additionally, the bot's intent settings become "locked," preventing any further change to what the bot will have access to. Note that this check only happens when the bot starts; if you want a friend to add the bot, you can temporarily make it public so they can add it, and then make it private again afterwards. Alternatively, your friend could temporarily grant you Manage Server permissions for you to add the bot to their server (the bot's owner can still add a bot to servers even if the bot is private). Again, because this bot is designed to be private, you should really know about every time someone is adding it. |
Beta Was this translation helpful? Give feedback.
-
bro I have "saved" up to my 100th time at this point ticking it off
2024년 7월월 2일 (화) 10:11 오전, Lillie ***@***.***(mailto:2024년 7월월 2일 (화) 10:11 오전, Lillie <<a href=)> 작성됨:
… ***@***.***(https://github.com/thickmelon) Make sure you're clicking the save button in the developer page. If it's still happening, you can work around the issue by using [my fork of JMusicBot.](https://github.com/sks316/MusicBot)
—
Reply to this email directly, [view it on GitHub](#1498 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMAG7MBEJVGRL2UICOTQFT3ZKH43TAVCNFSM6AAAAABEOCWECCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMZQHA4TM).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
yeah alr I'll try that
2024년 7월월 2일 (화) 10:16 오전, John Grosh ***@***.***(mailto:2024년 7월월 2일 (화) 10:16 오전, John Grosh <<a href=)> 작성됨:
… Make sure that you disable the install link (set it to None) on the "Installation" page as well; this seems to be a new change by Discord that breaks the public bot checkbox.
—
Reply to this email directly, [view it on GitHub](#1498 (reply in thread)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AMAG7MDRH3RVIOSYICQGG3TZKH5P3AVCNFSM6AAAAABEOCWECCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMZQHEZTC).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
JMusicBot's internals are not designed around nor optimized for being a public bot on a lot of servers. The setup instructions have always instructed you to disable the bot from being public. Version 0.4.0 is just the first version to actually enforce this; this is one of several warnings that were added to help alleviate issues that people frequently run into when they haven't set the bot up correctly on the developer dashboard.
It is very likely that the majority of users running into this error message didn't realize that their developer dashboard settings were incorrect; there is a long history of people needing support because someone added their bot without their permission and need…