Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation for Bot.change_presence missing a warning/note #6517

Closed
3 tasks done
pythonmcpi opened this issue Mar 7, 2021 · 1 comment
Closed
3 tasks done

Documentation for Bot.change_presence missing a warning/note #6517

pythonmcpi opened this issue Mar 7, 2021 · 1 comment
Labels
stale This issue is too old.

Comments

@pythonmcpi
Copy link

Summary

When running two instances of a bot on the same account (same token), the older instance controls the status (online, idle, dnd, invisible).

Reproduction Steps

Run two instances of a bot and have the younger instance try to change its status to dnd. The instance will think it changed its status, but the status displayed to users is still online. Changing the status on the older instance will change the actual status.

Expected Results

I expected some form of warning or note on the documentation for Bot.change_presence.

Actual Results

There was no note about an older instance of a bot controlling the bot status and led to a lot of head scratching.

Intents

discord.Intents.all()

System Information

  • Python v3.9.1-final
  • discord.py v1.6.0-final
  • aiohttp v3.7.3
  • system info: Windows 8.1 6.3.9600

Checklist

  • I have searched the open issues for duplicates.
  • I have shown the entire traceback, if possible.
  • I have removed my token from display, if visible.
@pythonmcpi pythonmcpi added the bug This is a bug with the library. label Mar 7, 2021
@scrazzz
Copy link
Contributor

scrazzz commented Mar 20, 2021

You normally wouldn't run two instances of the same bot. The bot instance which gets connected the last to the Discord API controls this presence (aka "status") afaik.

To understand this more clearly, it can be reproduced by self-botting and changing the presence on the client side. First, run the self-bot code and get connected to the Discord API (presence would be online if not specified). Then, login to that same account on the Discord client and change the presence to anything other than online, let's say we set it to Do Not Disturb. Now, even if you log out of the account on the client side, the presence stays to which one you set the last, that is, Do Not Disturb.

Again, you normally wouldn't run the same two instances of your bot as it's not practical to do so. I don't see the need for this to be mentioned in the docs.

@Rapptz Rapptz removed the bug This is a bug with the library. label Mar 24, 2021
@Rapptz Rapptz added the stale This issue is too old. label Mar 9, 2022
@Rapptz Rapptz closed this as completed Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale This issue is too old.
Projects
None yet
Development

No branches or pull requests

3 participants