throw error if user presence update fails, or add way to fetch current presence about discord.js HOT 7 CLOSED

You are correct in that it sets the presence without checking if the gateway call to set the presence succeeded. The reason for this is because there’s no way to check it did. It‘s not a REST call that has a response. It‘s also not issuing a websocket receive event (unless you have GuildPresences intent). And if it didn’t go through the only reason could be it was because the websocket itself was hung up or reconnecting. In both cases the payload to set the presence will remain in the queue until connected again and then it will change.

about that „bug“ in discord-api (which was closed because it really isn’t a bug): you don’t need to periodically reset the presence if you passed it in the identify call (which djs allows you to do by passing presence: {…} in the Client constructor).

from discord.js.

about that „bug“ in discord-api (which was closed because it really isn’t a bug): you don’t need to periodically reset the presence if you passed it in the identify call (which djs allows you to do by passing presence: {…} in the Client constructor).

Oh, I had not heard about that solution to the activity-disappearing issue. In the issue thread (here), it sounded like it was just a longstanding bug in Discord's backend that wipes bot activities whenever they deploy code.

Everyone else in that thread seems to be unaware of that solution. Would you mind posting it there so it can be more widely known? I think they'd really appreciate it - people have been complaining about the bug for 5 years.

from discord.js.

You are correct in that it sets the presence without checking if the gateway call to set the presence succeeded. The reason for this is because there’s no way to check it did. It‘s not a REST call that has a response. It‘s also not issuing a websocket receive event (unless you have GuildPresences intent). And if it didn’t go through the only reason could be it was because the websocket itself was hung up or reconnecting. In both cases the payload to set the presence will remain in the queue until connected again and then it will change.

Okay, that's understandable. If there's no response, then you can't guarantee the API call succeeded.

But what about adding a way to directly fetch the user's presence? If that's part of the Discord API, it would be good to add to d.js. My example use case isn't applicable, but some users might appreciate a way to directly fetch the real-time value of the presence, rather than rely on the eventually-consistent nature of the websocket queue.

Of course, if that's not possible with the Discord API, please disregard.

from discord.js.

But what about adding a way to directly fetch the user's presence? If that's part of the Discord API, it would be good to add to d.js. My example use case isn't applicable, but some users might appreciate a way to directly fetch the real-time value of the presence, rather than rely on the eventually-consistent nature of the websocket queue.

Of course, if that's not possible with the Discord API, please disregard.

Presences aren't defined on the User object, they're a property of GuildMember made available by the GuildPresences intent. Fetching your bot's GuildMember (or accessing guild.members.me) with presences enabled should provide this information.

from discord.js.

Presences aren't defined on the User object, they're a property of GuildMember made available by the GuildPresences intent. Fetching your bot's GuildMember (or accessing guild.members.me) with presences enabled should provide this information.

Okay! Is there no way to do it outside the context of Guilds? It's understandable that it would be limited to Guilds for other users (GuildMember), but what about for the ClientUser, where the presence should be independent of Guilds?

Considering it seems like my feature requests are either A) not possible, or B) already included, I think I'll close the issue after these questions. Thank you!

from discord.js.

Presences are inherently guild-based data, so they can just be retrieved within a guild context; this is a discord API limitation.
As for the sending of presences, Qjuh covered that above.

from discord.js.

Thank you for the explanations!

from discord.js.