You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2022. It is now read-only.
With the recent updates to intents etc. and just some recent debugging I've realised that the local caches actually miss users a lot more often than I thought.
Possible solutions:
GetAllUsers
Fetch member manually (not possible as far as I can see, Unless I create a second client and set it to rest mode but even then I think that requries OAuth2 to work)
Make Polaris ID based
The latter is my current target. Polaris will be made more ID based - i.e. for commands like WHOIS it will validate the user snowflake consists of numbers but not that it exists in caches before checking for a link. This is far more resilient and a few other things may also need updated.
The text was updated successfully, but these errors were encountered:
Turns out rest mode is apparently "safe" for use with Gateway, meaning users can be individually fetched if they do not exist - fixing a signficant issue.
This means the bot token must now be prefixed, which I've already committed locally and will need to put out.
This means we can:
Get specific user
Get specific member
Get all members for a guild
and more, which should solve a lot of the bugs that have been appearing lately.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugSomething isn't workingenhancementNew feature or request
With the recent updates to intents etc. and just some recent debugging I've realised that the local caches actually miss users a lot more often than I thought.
Possible solutions:
The latter is my current target. Polaris will be made more ID based - i.e. for commands like WHOIS it will validate the user snowflake consists of numbers but not that it exists in caches before checking for a link. This is far more resilient and a few other things may also need updated.
The text was updated successfully, but these errors were encountered: